Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Office dropping some calls on E1-PRI

Status
Not open for further replies.

dzajroo

IS-IT--Management
Oct 27, 2010
22
AU
Hi All,

Got 9.1.4 500v2 with E1-PRI30 card and 10 digital 1608 handsets. Client reporting that some calls are getting dropped (disconnects the call with busy signal).

The configuration is basic, whole 100 range goes to 1 hunt group with multiple extensions in it with collective ringing and Queuing is ON. We did some few test calls 7, from 7 calls 2 got disconnected, however monitor trace captured all 7 incoming calls...Not sure what could be the problem (don't believe it's the PRI card). Any tip would be greatly appreciated. Carrier responded that they can see few calls with reason 17 error code (busy client).

Below is the trace:

WORKING INCOMING CALL

0000 6c 0c 21 83 30 34 31 37 38 39 39 37 37 38 l.!.0417899778
InformationElement = CalledPartyNumber
0000 70 0b c1 30 33 39 34 39 39 35 33 36 36 p..0394995366
15:41:02 1740011638mS ISDNL3Evt: v=5 stacknum=5 State, new=Present, old=NullState id=9
15:41:02 1740011638mS ISDNL2Tx: v=5 peb=5
0000 02 01 01 b6 ....
15:41:02 1740011639mS ISDNL1Tx: v=5 peb=5
0000 02 01 01 b6 ....
15:41:02 1740011639mS CMLineRx: v=5
CMSetup
Line: type=Q931Line 5 Call: lid=5 id=9 in=1
Called[0394995366] Type=SubscriberNumber (4) Reason=CMDRdirect SndComp Calling[00417899778] Type=National Plan=ISDN Pres=Allowed (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
BChan: slot=0 chan=6
15:41:02 1740011639mS PRN: Q931Trunk: Found QBChannel to match 0.6 --> 3.7


FAILED INCOMING CALL

0000 6c 0c 21 83 30 34 31 37 38 39 39 37 37 38 l.!.0417899778
InformationElement = CalledPartyNumber
0000 70 0b c1 30 33 39 34 39 39 35 33 36 36 p..0394995366
15:40:45 1739994800mS ISDNL3Evt: v=5 stacknum=5 State, new=NullState, old=NullState id=23
15:40:45 1739994800mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=7D06(Local)
Message Type = ReleaseComplete
InformationElement = CAUSE
0000 08 02 80 91 ....
15:40:45 1739994800mS ISDNL2Tx: v=5 peb=5
0000 00 01 dc b4 08 02 fd 06 5a 08 02 80 91 ........Z....
15:40:45 1739994800mS ISDNL1Tx: v=5 peb=5
0000 00 01 dc b4 08 02 fd 06 5a 08 02 80 91 ........Z....
15:40:45 1739994812mS ISDNL1Rx: v=5 peb=5
0000 00 01 01 de ....
15:40:45 1739994812mS ISDNL2Rx: v=5 peb=5
0000 00 01 01 de ....
15:40:52 1740001482mS CMExtnEvt: Station 7: No user activity
15:40:55 1740004730mS ISDNL1Rx: v=5 peb=5
0000 02 01 01 df ....
15:40:55 1740004730mS ISDNL2Rx: v=5 peb=5
0000 02 01 01 df ....
15:40:55 1740004730mS ISDNL2Tx: v=5 peb=5
0000 02 01 01 b5 ....
15:40:55 1740004730mS ISDNL1Tx: v=5 peb=5
0000 02 01 01 b5 ....
15:40:55 1740004804mS R2DSP: PRIU DSP 2: is alive
 
In the failed trace, I'm missing the

Called[0394995366] Type=SubscriberNumber (4) Reason=CMDRdirect SndComp Calling[00417899778] Type=National Plan=ISDN Pres=Allowed (0)


So IP Office does not know where to route the call to.

Contact your provider.



 
joe2938 -> correct 1608 is IP 1408 is digital ( was typo on my end, I've been dealing with IPO since SoE edition...)

Okkie26 -> thanks for that, it turns out that customer "lied" to us regarding the PRI Trunk. Customer kept telling us they paying and have PRI20 services however carrier later confirmed that they running PRI30 service. Changing the E1 trunk from 20 to 30 channels fixed the issue.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top