[cisco-voip] H.323 disconnect issue
Wes Sisk
wsisk at cisco.com
Thu Sep 20 16:16:04 EDT 2007
make sure the tick the box for q931/h225 messages in TranslatorX is
selected so messages are displayed. If still no h.323 messages, then
calls are being processes on a different CM node in your cluster.
/wes
Dave Wolgast wrote:
> I only see Skinny messages.
>
> (I actually had gathered them using Triple Combo before I got your
> message).
>
> Relevant here (I think) are the events that occurred at 15:14:41.
>
> 09/20/2007 15:14:41.786 CCM|H245ASN - TtPid=(7,100,144,444) -Incoming
> -value MultimediaSystemControlMessage ::= command : endSessionCommand
> : disconnect : NULL|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER 4>
>
> 09/20/2007 15:14:41.786 CCM|H245ASN - TtPid=(7,100,144,444) -Outgoing
> -value MultimediaSystemControlMessage ::= command : endSessionCommand
> : disconnect : NULL|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER 4>
>
> 09/20/2007 15:14:41.786 CCM|IsdnMsgData1= 08 02 14 16 5A 7E 00 27 05
> 25 C0 06 00 08 91 4A 00 04 58 88 C0 11 00 02 28 5D 1C 4F 01 45 13 02
> 26 76 77 E4 4D 02 13 01 00 01 40 10 80 01 00
> |<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER 4>
> (translation: H.225 0x1416 RELEASE_COMP RX<-- GATEKEEPER
> RELEASE_COMP pd=8 callref=0x1416
>
> 09/20/2007 15:14:41.856 CCM|StationD: (0000867) CloseReceiveChannel
> conferenceID=117614940 passThruPartyID=118606929. myIP: 2a1a850a
> (10.133.26.42
> <http://10.133.26.42>)|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132, 2522.1><IP::GATEKEEPER><DEV::>
>
> 09/20/2007 15:14:41.856 CCM|StationD(867): StationCtiD -
> CtiStopReceptionNotify
> CI=117614940|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132,2522.1><IP::GATEKEEPE><DEV::>
>
> 09/20/2007 15:14:41.856 CCM|StationD(867): StationCtiD -
> CtiStopReceptionNotify
> CI=117614940|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132,2522.1><IP::GATEKEEPE><DEV::>
>
> 09/20/2007 15:14:41.856 CCM|StationD: (0000867)
> StopMediaTransmission conferenceID=117614940
> passThruPartyID=118606929. myIP: 2a1a850a (10.133.26.42
> <http://10.133.26.42>)|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132, 2522.1><IP::GATEKEEPER><DEV::>
>
> 09/20/2007 15:14:41.856 CCM|StationD(867): StationCtiD -
> CtiStopTransmissionNotify
> CI=117614940|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132,2522.1><IP::GATEKEEPER><DEV::>
>
> 09/20/2007 15:14:41.856 CCM|StationD(867): StationCtiD -
> CtiStopTransmissionNotify
> CI=117614940|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132,2522.1><IP::GATEKEEPER><DEV::>
>
> 09/20/2007 15:14:41.856 CCM|StationD: (0000867)
> StopTone.|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132,2522.1><IP::GATEKEEPER><DEV::>
>
> 09/20/2007 15:14:41.856 CCM|StationD: (0000867) StartTone
> tone=37(ReorderTone),
> direction=0.|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132,2522.1><IP::GATEKEEPER><DEV::>
>
> 09/20/2007 15:14:41.856 CCM|StationD: (0000867) SelectSoftKeys
> instance=1 reference=117614940 softKeySetIndex=8
> validKeyMask=fffeffff.|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132,2522.1 ><IP::GATEKEEPER><DEV::>
>
> 09/20/2007 15:14:41.856 CCM|StationD: (0000867)
> ConnectionStatisticsReq directoryNum=8995 callIdentifier=117614940
> statsProcessingMode=0(clearStats)|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> 1><CT::7,100,132, 2522.1><IP::GATEKEEPER><DEV::>
>
> There is no RELEASE_COMP from the phone until 6 seconds later when I
> hang up the receiver.
>
> On 9/20/07, *Wes Sisk* <wsisk at cisco.com <mailto:wsisk at cisco.com>> wrote:
>
> In Callmanager turn on detailed CallManager traces
> check the h245 box in the upper left of CM trace configuration screen.
> http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_tech_note09186a0080094e89.shtml
>
> collect CM sdi traces (c:\program files\cisco\trace\ccm) and look
> for problem call.
> TranslatorX is your friend for parsing the h323/q931 messages:
> http://www.employees.org/~pgiralt/TranslatorX/
> <http://www.employees.org/%7Epgiralt/TranslatorX/>
>
> /Wes
>
>
> Dave Wolgast wrote:
>> No, and I'm not sure how I am going to find out. I think I can telnet
>> into the VSX and collect some kind of H323 traces...I just have to
>> figure out how, because there doen't seem to be a ton of documentation
>> on in-depth troubleshooting for the VSX
>>
>>
>> On 9/20/07, Wes Sisk <wsisk at cisco.com> <mailto:wsisk at cisco.com> wrote:
>>
>>> Any insight on the h.323 signaling polycom sends when it goes onhook?
>>>
>>> /Wes
>>>
>>>
>>> Dave Wolgast wrote:
>>>
>>> Hello,
>>>
>>> I have a Polycom VSX8000 connecting with a skinny IP phone via
>>> gatekeeper-controlled H.323 trunk (Gatekeeper is Polycom SE200 -- Not IOS).
>>> Calls are connected successfully in both directions using our 4-digit dial
>>> plan. However, when the Polycom H.323 VSX endpoint is the first to hang up
>>> the call, the skinny phone gets reorder tone rather than disconnecting. The
>>> display on the IP phone continues to say 'connected.'
>>>
>>> At first glance, it seems as if there is never a disconnect message sent
>>> from the H.323 side of the call. (We are also experiencing a similar issue
>>> with an H.323 IVR that is defined as an H.323 gateway).
>>>
>>> Can anyone make any suggestions as to what is going on here, and how I
>>> should proceed?
>>>
>>> Thanks!
>>>
>>> --
>>> Dave Wolgast
>>> Inergex, Inc.
>>> Buffalo, New York
>>>
>>> ________________________________
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
>
>
>
> --
> Dave Wolgast
> Livonia, NY
More information about the cisco-voip
mailing list