I put up a call with the monitoring enabled on the gateway (the DX) and received the following output in the event log:
————— START LOG DATA —————
ch |01/01| 2008/03/05|08:19:40:485 |sip[0/0]: chsipTG: SIP CallID :call-714BC969-B9CC-2A10-0A1A-2287
sip[0/0]: SipReleaseComplete rcvd at SipTermCall
sip[27527/0]: tsipcall:RcvRelComp, cause=16
CallInfo[27527]: disconnected event. cause=16 legno=1 leg=1 sentLeg=0.
CallInfo [27527]: discTickm(448245816) connTickm(447881608) duration (1821)
.
tsi disconnect: 1016 113 11
OBCSM[27527]: Release from peer=0x960c8308 cause=0x10 redir=.
TBCSM [27527]: Release complete from peer=0x9684fcc8.
sip[0/0]: sipTG::term releaseCall:remove call from list
OBCSM[27527]: pRouteInfo 968b44d8 state 8 ivrType 0 h323RetCode -1 cause 10.
CallInfo[27527]: disconnected event. cause=16 legno=0 leg=1 sentLeg=0.
CallInfo [27527]: discTickm(448245816) connTickm(447881608) duration (1821)
.
CallInfo[27527]: send eventDisconnected 1821.
PRI(2,0,2,0×2286): sending DISC_REQ to L3.
ch |01/01| 2008/03/05|08:19:40:530 |PRI(2,0,2,0×9581): received DISC_IND from L3.
PRI(2,0,2,0×9581): sending CLEAR_REQ to L3.
CallInfo[27526]: disconnected event. cause=16 legno=1 leg=1 sentLeg=0.
CallInfo [27526]: discTickm(448245825) connTickm(447881618) duration (1821)
.
tsi disconnect: 093 1005 11
OBCSM[27526]: Release from peer=0x967b3ccc cause=0x10 redir=.
TBCSM [27526]: Release complete from peer=0x96024e10.
OBCSM[27526]: pRouteInfo 96921cd8 state 8 ivrType 0 h323RetCode -1 cause 10.
CallInfo[27526]: disconnected event. cause=16 legno=0 leg=1 sentLeg=0.
CallInfo [27526]: discTickm(448245825) connTickm(447881618) duration (1821)
.
CallInfo[27526]: send eventDisconnected 1821.
————— END LOG DATA —————
The cause code is 16 which translates to “Normal Call Clearing – This is one of the most common cause codes and is received for many reasons. It usually occurs
because someone hung up the call at one side or the other.”
This has me thinking that 3Com is wrong and that it must be some setting on the VCX.