cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
150
Views
0
Helpful
0
Replies
Beginner

(CUCM SIP->H323) call immediately drops after connecting; Reason: Q.850;cause=86

Call Flow: (used my cell)PSTN caller->VGW1->CUCM->UCCX->Agent xfers to internal operator-> Internal Operator blind xfers to end user-> end user has cfwd all set to his cell phone-> SIP Trunk ->Cube/VGW2 ->H.323 PRI -> PSTN

 

Facts

Call connects for 1 second then drops

If I call the end user directly the call connects fine(Call comes in and exits on VGW2 not VGW1)

I collected debugs on VGW2 (can't share entire debugs - customer info)

VGW2 disconnects the call (Sends BYE to CUCM and Disconnect MSG to Provider)

 

BELOW: BYE MESSAGE FROM VGW2 TO CUCM

User-Agent: Cisco-SIPGateway/IOS-16.6.5
Max-Forwards: 70
Timestamp: 1571343244
CSeq: 101 BYE
Reason: Q.850;cause=86

 

BELOW: DISCONNECT MSG TO PRI PROVIDER

065077: Oct 17 15:14:04.974: ISDN Se0/1/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x0146
Cause i = 0x80EF - Protocol error; unspecified

(See screenshots of Translator X diagram (debugs from VGW2) attached)

 

In comparing calls

I see a reinvite coming from CUCM (INVITE 105) that swaps out the Operator's PAsserted ID and Contact with my cell info. When that gets passed to the provider it shows plan: uknown/unknown. Not sure if this is the cause.

 

Could it be a callerID issue where callerID is provided but in an unsupported IE by the provider? A call status did get generated with a call state and no mechanism for recovery thus a drop? See below from provider after disconnect.

 

065078: Oct 17 15:14:05.019: ISDN Se0/1/0:23 Q931: RX <- STATUS pd = 8 callref = 0x8146
Cause i = 0x82E16E - Message type not implemented
Call State i = 0x0A

 

 

ask for any info and I will provide it as best I can.

JC

 

 

 

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards