Issue with R2-Random calls are droped

[Loremtz]

Hi guys!
I need you help with a IPO Server issue.
I have an IPO Server Edtion 9.1.11 with ACCS and an IPO 500 expansion with 4 E1s.
the problem is than in a period of time some calls than arrive in the IPO are dropped with a message from ISP "at this moment all lines are busy". But in the IPO the E1R2 trunk line are busy just in 35%.
It seems like a Service Provider problem, but I see some log in the SSA and monitor and I can see the call arrive from the SP and is droped after 3 seconds. This is the process:
- The call arrived in the channel 23 on E1R2 trunk, I can see the ANI and the "Alerting Message" in the channel, all counters going to 0:00.
- After 3 seconds, and after hear the "at this moment all lines are busy" message the call is dropped with the "Disconnect from Starter Terminal" in SSA

My question is, if is a SP problem, why I am seeing the try to connect the call in SSA? in the logs I see this message


2017-07-17T11:26:48 898644617mS PRN: R2 CAS: R2_MEX_1.23:: Receive: 0001 -> 1001
2017-07-17T11:26:48 898644617mS R2Channel: R2_MEX_1.23: EventRx: Clear Forward State: Answer
2017-07-17T11:26:48 898644837mS R2Channel: R2_MEX_1.23: EventTx: Idle State: Answer
2017-07-17T11:26:48 898644837mS PRN: R2 CAS: R2_MEX_1.23:: Transmit: 0101 -> 1001
2017-07-17T11:26:48 898644837mS R2Channel: R2_MEX_1.23: State Change Answer -> Idle
2017-07-17T11:26:48 898644837mS R2Channel: R2_MEX_1.23: EventTx: Idle State: Idle

********** Warning: Missed 1 packet(s) Total late 0 packet(s) **********
2017-07-17T11:26:48 898644838mS R2Line: line: 1.23: State Change Active -> Idle
2017-07-17T11:26:48 898644839mS CMLineRx: v=1
CMReleaseComp
Line: type=R2Line 1 Call: lid=1 id=146177 in=1
Cause=16, Normal call clearing
2017-07-17T11:26:48 898644839mS CMCallEvt: 0a02210700023b01 1.146177.1 48406 R2 Trunk:1 CHAN=23: StateChange: END=A CMCSConnected->CMCSCompleted
2017-07-17T11:26:48 898644841mS CMLineTx: v=17
CMFacility
Line: type=IPLine 17 Call: lid=0 id=146179 in=0
IE CMIEFastStartInfoData (6) 2 item(s)
IE CMIEDtmf (209) CMIEDtmf oob 1, txp 101, rxp 101, fmtp = <null>, misc 3 (misc oob 0 misc rfc2833 0 prio oob 1 prio rfc2833 1)
2017-07-17T11:26:48 898644843mS CMLOGGING: CALL:2017/07/1711:26,00:00:02,000,8110019910,I,505251,5251,,,,0,,"",0,n/a
2017-07-17T11:26:48 898644843mS CD: CALL: 1.146177.1 BState=Connected Cut=2 Music=0.0 Aend="Line 1" (1.25) Bend="Line 17" [Line 17] (267.20) CalledNum=505251 () CallingNum=8110019910 () Internal=0 Time=2533 AState=Idle
2017-07-17T11:26:48 898644843mS CD: CALL: 1.146177.1 Deleted
2017-07-17T11:26:48 898644843mS CMCallEvt: 0a02210700023b01 1.146177.1 -1 R2 Trunk:1 CHAN=23: StateChange: END=X CMCSCompleted->CMCSDelete
2017-07-17T11:26:48 898644845mS CMLineTx: v=17
CMReleaseComp
Line: type=IPLine 17 Call: lid=0 id=146179 in=0
Cause=16, Normal call clearing
2017-07-17T11:26:48 898644845mS CMCallEvt: 0a022105000e4889 0.146179.0 -1 H323TrunkEP: StateChange: END=X CMCSConnected->CMCSDelete
2017-07-17T11:26:48 898644846mS CMCallEvt: 0a022105000e4889 0.146179.0 -1 BaseEP: DELETE CMEndpoint f1724b84 TOTAL NOW=59 CALL_LIST=29
2017-07-17T11:26:48 898644847mS CMCallEvt: END CALL:48406 (f16e1134)
2017-07-17T11:26:48 898644848mS CMCallEvt: 0a02210700023b01 1.146177.1 -1 BaseEP: DELETE CMEndpoint f18a9a74 TOTAL NOW=58 CALL_LIST=29
2017-07-17T11:26:48 898644848mS R2Line: line: 1.23: Clear Call
2017-07-17T11:26:48 898644851mS CMMap: PCG::UnmapBChan pcp[207]b1r0 cp_b f5607f18 other_cp_b f5661ebc
2017-07-17T11:26:48 898644851mS CMMap: a=0.33 b=1.25 M02
2017-07-17T11:26:48 898644852mS CMMap: PlatformConnectionAudioSAP:isconnectRtpFilter rtpRelay ID: 20 Close success
2017-07-17T11:26:48 898644852mS H323Evt: SESS bcd9 SetOperational local 10.2.33.7:46788 remote 10.2.33.9:20126 to 0
2017-07-17T11:26:48 898644852mS CMMap: PCG::UnmapBChan pcp[630]b0r1 cp_b 0 other_cp_b 0


I appreciate you help!
Regards!

 

[holdmusic34]

Cause=16, Normal call clearing

this is a normal disconnect. the IP Office may be hanging up the call because it doesn't know where to route it.
In your line settings, remove the prefix, national prefix and international prefix entries.

Remember your training and you will make it back alive!

 

[intrigrant]

I am stunned everytime I see a post about a full featured server edition where the poster obviously doesn't have a clue how to diagnose problems.
As a advise I would suggest to use SSA only as a quick lookup tool and not for fault finding.
Use system monitor for fault finding and use the right filters and call someone who knows how to setup the right filter and how to interpret the logs.

 

[IPOLackey]

You're showing the time the call disconnects there, but not three seconds before when the initial targeting would have happened. Take a look at the targeting and see why it failed to get to ext 5251.