Incoming calls cut off over non-geo numbers.. sanity check please.

[dudspog]

Hi,

Hopefully this wil be an easy one!

It's an old 2.1.31 IP412 (DT handsets), so no support from Avaya.

Incoming calls via non geographic numbers ring for a minute, then cut off.
Doesn't matter if you point the calls at a group or individual extn, always cut off.

If you ring the underlying DDI direct, it's fine.

The non-geographic provider say the IP office is sending them SIP "BYE" messages, so they hang up the call.... hmmmmn.

Here's a trace of the last part of a call cutting off.
If I'm reading it right, about 5 lines down I'm getting a "Disconnect" message from the remote end....

Am I right?????


4032274278mS ISDNL1Rx: v=6 peb=6
0000 02 01 ec 8e 08 02 00 09 45 08 02 80 90 ........E....
4032274278mS ISDNL2Rx: v=6 peb=6
0000 02 01 ec 8e 08 02 00 09 45 08 02 80 90 ........E....
4032274278mS ISDNL3Rx: v=6 peb=6
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0009(Remote)
Message Type = Disconnect
InformationElement = CAUSE
0000 08 02 80 90 ....
4032274278mS ISDNL3Evt: v=6 stacknum=6 State, new=ReleaseReq, old=Received id=24
4032274278mS ISDNL3Tx: v=6 peb=6
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0009(Local)
Message Type = Release
4032274278mS ISDNL2Tx: v=6 peb=6
0000 00 01 8e ee 08 02 80 09 4d ........M
4032274279mS ISDNL1Tx: v=6 peb=6
0000 00 01 8e ee 08 02 80 09 4d ........M
4032274296mS ISDNL1Rx: v=6 peb=6
0000 00 01 01 90 ....
4032274296mS ISDNL2Rx: v=6 peb=6
0000 00 01 01 90 ....
4032274328mS ISDNL1Rx: v=6 peb=6
0000 02 01 ee 90 08 02 00 09 5a ........Z
4032274328mS ISDNL2Rx: v=6 peb=6
0000 02 01 ee 90 08 02 00 09 5a ........Z
4032274328mS ISDNL3Rx: v=6 peb=6
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0009(Remote)
Message Type = ReleaseComplete
4032274328mS ISDNL3Evt: v=6 stacknum=6 State, new=NullState, old=ReleaseReq id=24
4032274329mS ISDNL2Tx: v=6 peb=6
0000 02 01 01 f0 ....
4032274329mS ISDNL1Tx: v=6 peb=6
0000 02 01 01 f0 ....
4032274334mS CMLineRx: v=6
CMReleaseComp
Line: type=Q931Line 6 Call: lid=6 id=24 in=1
Cause=16, Normal call clearing
4032274334mS CMCallPkt: v=24
CMReleaseComp
Line: type=Q931Line 6 Call: lid=6 id=24 in=1
Cause=16, Normal call clearing



Thanks in advance for any input,
Mark.

 

[hairlessupportmonkey]

OK the software is ancient, and these are ISDN calls. The IPO could not possibly be sending SIP BYE when a) its ISDN, and b) the software version doesnt do SIP trunks.

If the DDI works OK, then it must be a network / provider fault.

ACSS - SME
General Geek

 

[dudspog]

Absolutely, completley agree.
This is what I've been telling them, it's all ISDN, but the non geo guys are bamboozling the customer with so much horse poo, I'm beginning to doubt myself.

I just want to be sure I've read the disconnect part of the trace right so I'm 100% sure and can tell them (very politely) to go forth.