JohnnyOduya
IS-IT--Management
Wierd behavior on IPO500 V9 and ATT PRI. The 4th or sometimes the 5th active call does not completely connect and the call is disonnected. VCM channels are free, PRI channels are free. In testing what I did is make 3 outbound calls, then on the 4th outbound call in system status the logs show that the ISDN handhsake completes and immidiately there is a call disconnection with a status code 90 (normal call clearing).
Could it be a carrier issue? It looks like the Avaya is disconnecting the call from this system status trace, or is it ATT?
There is a VCM32 V2/PRIS U card.
Call Proceed:
142426233mS ISDNL3Rx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Local)
Message Type = CallProceeding
InformationElement = CHI
0000 18 03 a9 83 94 .....
142426233mS ISDNL3Evt: v=5 stacknum=5 State, new=Proceeding, old=Initiated id=7050
142426234mS CMARS: LINE ep Received: CMProceeding - child->state = CMCSOffering - ARS Call State = CMCSOverlapRecv
142426234mS CMARS: LINE IS NOW THE B END OF THE CALL - CMARSEndpoint::RequestEnd()
142426234mS CMARS: CMARSEndpoint::CallLost(cause=124) - Address: c0a82a0200001b87 0.7049.0 1556 ARS for Main - Call State: CMCSOverlapRecv
142426234mS CMCallEvt: c0a82a0200001b87 0.7049.0 -1 ARS for Main: StateChange: END=X CMCSOverlapRecv->CMCSDelete
142426236mS CMCallEvt: c0a82a0200001b8a 0.7050.0 1556 Q931 Trunk:5 CHAN=20: StateChange: END=B CMCSOffering->CMCSAccept
142426236mS CMCallEvt: c0a82a0200001b87 267.7047.0 1556 JonD.0: StateChange: END=A CMCSDialling->CMCSDialled
142426238mS CMCallEvt: c0a82a0200001b87 0.7049.0 -1 BaseEP: DELETE CMEndpoint f499cbfc TOTAL NOW=8 CALL_LIST=4
Call Disconnect:
142456233mS ISDNL3Evt: v=5 stacknum=5 State, new=DiscReq, old=Proceeding id=7050
142456233mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Remote)
Message Type = Disconnect
InformationElement = CAUSE
0000 08 02 80 90 ....
142456260mS ISDNL3Rx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Local)
Message Type = Release
InformationElement = CAUSE
0000 08 02 80 90 ....
142456260mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Remote)
Message Type = ReleaseComplete
Could it be a carrier issue? It looks like the Avaya is disconnecting the call from this system status trace, or is it ATT?
There is a VCM32 V2/PRIS U card.
Call Proceed:
142426233mS ISDNL3Rx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Local)
Message Type = CallProceeding
InformationElement = CHI
0000 18 03 a9 83 94 .....
142426233mS ISDNL3Evt: v=5 stacknum=5 State, new=Proceeding, old=Initiated id=7050
142426234mS CMARS: LINE ep Received: CMProceeding - child->state = CMCSOffering - ARS Call State = CMCSOverlapRecv
142426234mS CMARS: LINE IS NOW THE B END OF THE CALL - CMARSEndpoint::RequestEnd()
142426234mS CMARS: CMARSEndpoint::CallLost(cause=124) - Address: c0a82a0200001b87 0.7049.0 1556 ARS for Main - Call State: CMCSOverlapRecv
142426234mS CMCallEvt: c0a82a0200001b87 0.7049.0 -1 ARS for Main: StateChange: END=X CMCSOverlapRecv->CMCSDelete
142426236mS CMCallEvt: c0a82a0200001b8a 0.7050.0 1556 Q931 Trunk:5 CHAN=20: StateChange: END=B CMCSOffering->CMCSAccept
142426236mS CMCallEvt: c0a82a0200001b87 267.7047.0 1556 JonD.0: StateChange: END=A CMCSDialling->CMCSDialled
142426238mS CMCallEvt: c0a82a0200001b87 0.7049.0 -1 BaseEP: DELETE CMEndpoint f499cbfc TOTAL NOW=8 CALL_LIST=4
Call Disconnect:
142456233mS ISDNL3Evt: v=5 stacknum=5 State, new=DiscReq, old=Proceeding id=7050
142456233mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Remote)
Message Type = Disconnect
InformationElement = CAUSE
0000 08 02 80 90 ....
142456260mS ISDNL3Rx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Local)
Message Type = Release
InformationElement = CAUSE
0000 08 02 80 90 ....
142456260mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=006E(Remote)
Message Type = ReleaseComplete