 |
|
 |
|
09-20-07 06:12 PM
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
[ Post a follow-up to this message ]
|
|
|
 |
|
 |
|
 |
|
|
 |
Re: H.323 disconnect issue |
 |
 |
|
|
09-20-07 06:12 PM
Hello Dave.
Codec mismatch ??
But it will be better if you collect damp of this call.
-----------------------
Sincerely Yours,
Konstantin Fedorov
_____
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Dave Wolgast
Sent: Thursday, September 20, 2007 7:54 PM
To: cisco VOIP Newsletter - puck.nether.net
Subject: [cisco-voip] H.323 disconnect issue
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
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
|
|
Re: H.323 disconnect issue |
|
|
|
|
|
|
|
|
|
|
Re: H.323 disconnect issue |
|
|
|
|
09-20-07 06:12 PM
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@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 u
p
> the call, the skinny phone gets reorder tone rather than disconnecting. T
he
> 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 issu
e
> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
--
Dave Wolgast
Livonia, NY
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
|
|
Re: H.323 disconnect issue |
|
|
|
|
|
|
|
|
|
|
Re: H.323 disconnect issue |
|
|
|
|
09-20-07 06:12 PM
Here is a trace of what the gatekeeper sees (trace data is newest first and
IP Addresses scrubbed):
============================ <09:20:07 13:46:43>
============================
DRQ Received
'requestSeqNum' 5997
'endpointIdentifier' 4 '1040'
'conferenceID' 16 '02 28 5C FB 6C 80 6C 1F 02 26 76 77 E4 4D 02 13 '
'callReferenceValue' 37896
'disengageReason' 18007
'undefinedReason' -123
'callIdentifier' -111
'guid' 16 '02 28 5C FB 6C 80 6C 1F 02 25 76 77 E4 4D 02 13 '
'gatekeeperIdentifier' 7 'PN:PLCM'
'tokens' 1
'1' -111
'tokenOID' 11 '60 86 48 01 86 F8 71 01 02 81 33 '
'nonStandard' -111
'nonStandardIdentifier' 11 '60 86 48 01 86 F8 71 01 02 81 33 '
'data' 149 '02 E0 25 00 1D 01 00 20 01 09 E0 25 00 1E 01 00 30 80 82 44 49
53 43 4F 4E 4E 45 43 54 5F 52 45 41 53 4F 4E 3D 32 2C 54 49 4D 45 3D 31 31
39 30 33 31 30 36 32 34 2C 44 55 52 41 54 49 4F 4E 3D 39 2C 44 49 53 43 4F
4E 4E 45 43 54 5F 53 54 52 49 4E 47 3D 6E 6F 72 6D 61 6C 2C 20 75 6E 73 70
65 63 69 66 69 65 64 2E 2C 4F 52 49 47 49 4E 3D 30 2C 4C 49 4E 45 5F 4E 55
4D 42 45 52 3D 4D 47 43 42 30 31 61 2C 4F 55 54 42 4F 55 4E 44 5F 47 57 5F
49 50 3D '
'answeredCall' 1
ProcessDRQ
Source of Msg is <MY CALLMANAGER SUBSCRIBER>:50311
Searching for ConfID 02285cfb-6c80-6c1f-0226-7677e44d0213 CallID
02285cfb-6c80-6c1f-0225-7677e44d0213
Found for CallInternalID 11780115
Source is Destination
DRQ 0x2b3c013 - in disconnect - release.
DRQ Call released
Sending DCF
'requestSeqNum' 5997
============================ <09:20:07 13:46:43>
============================
DRQ Received
'requestSeqNum' 21265
'endpointIdentifier' 4 '1039'
'conferenceID' 16 '02 28 5C FB 6C 80 6C 1F 02 26 76 77 E4 4D 02 13 '
'callReferenceValue' 18031
'disengageReason' 12561
'normalDrop' -123
'callIdentifier' -111
'guid' 16 '02 28 5C FB 6C 80 6C 1F 02 25 76 77 E4 4D 02 13 '
'gatekeeperIdentifier' 7 'PN:PLCM'
'answeredCall' 0
ProcessDRQ
Source of Msg is 10.133.21.200:1719
Searching for ConfID 02285cfb-6c80-6c1f-0226-7677e44d0213 CallID
02285cfb-6c80-6c1f-0225-7677e44d0213
Found for CallInternalID 11780115
Source is Origin
DRQ 0x1b3c013 - in disconnect - release.
Sending DCF
'requestSeqNum' 21265
============================ <09:20:07 13:46:43>
============================
ReleaseComplete Received
Dial - Address: 22*8995
Stack Conference Id:02285cfb6c806c1f02267677e44d0213
CallID: Display information :02285cfb6c806c1f02257677e44d0213
Reason is cmReasonTypeUndefinedReason(11)
Direction is OrigSegment
PN Segment id: 0X1b3c013
state = cmCallStateDisconnected
stateMode = cmCallStateModeDisconnectedNormal
ReleaseComplete Sent
Dial - Address: 22*8995
Stack Conference Id:02285cfb6c806c1f02267677e44d0213
CallID: Display information :02285cfb6c806c1f02257677e44d0213
Direction is DestSegment
PN Segment id: 0X2b3c013
============================ <09:20:07 13:46:43>
============================
Disconnect - wait for DRQ: Seg 0x1b3c013, tr:<VSX8000>:1720
via:<VSX8000>:1720
============================ <09:20:07 13:46:43>
============================
Disconnect - wait for DRQ: Seg 0x2b3c013, tr:>MY CALLMANAGER
SUBSCRIBER>:54136 via:<MY CALLMANAGER SUBSCRIBER>:54136
I see a ReleaseComplete message with reason code 11
'cmReasonTypeUndefinedReason'
I am trying to get through some CCM traces to see if I can determine what
the phone is seeing.
On 9/20/07, Jeffrey C. Ollie <jeff@ocjtech.us> wrote:
>
> On Thu, 2007-09-20 at 12:55 -0400, Dave Wolgast wrote:
>
> Span the port that the VSX plugs into and use Wireshark[1] to capture
> the H.323 traffic.
>
> Wireshark does a decent job of decoding VoIP protocols.
>
> Jeff
>
> [1] http://www.wireshark.org/
>
>
--
Dave Wolgast
Livonia, NY
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
|
|
Re: H.323 disconnect issue |
|
|
|
|
|
|
|
|
|
|
Re: H.323 disconnect issue |
|
|
|
|
09-21-07 12:11 AM
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)|<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)|<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@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/...080094e89.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/
>
> /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@cisco.com> <wsisk@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 u
p
> the call, the skinny phone gets reorder tone rather than disconnecting. T
he
> 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 issu
e
> 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 listcisco-voip@puck.nether.nethttps://puck.nether.net/m
ailman/listinfo/cisco-voip
>
>
--
Dave Wolgast
Livonia, NY
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
|
|
Re: H.323 disconnect issue |
|
|
|
|
09-21-07 12:11 AM
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@cisco.com <mailto:wsisk@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/...080094e89.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:
>
>
>
>
> --
> Dave Wolgast
> Livonia, NY
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
|
|
|
Re: H.323 disconnect issue |
|
|
|
|
09-21-07 12:11 AM
Wes,
I actually forgot to edit the bit about only skinny messages out...I turned
on H.245 tracing on on the Sub with the H.323 trunk, did a new call, and got
them. H.323 traces were in the collection I attached.
On 9/20/07, Wes Sisk <wsisk@cisco.com> wrote:
>
> 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:
> statsProcessingMode=0(clearStats)|<CLID::HNNYCMB1-Cluster><NID::SUBSCRIBER
> screen.
> http://www.cisco.com/en/US/partner/...080094e89.shtml
> telnet
> documentation
> wrote:
> goes onhook?
> Not IOS).
> 4-digit dial
> to hang up
> disconnecting. The
> message sent
> similar issue
> how I
>
--
Dave Wolgast
Livonia, NY
[ Post a follow-up to this message ]
|
|
|
|
|
|
|
|
Sponsored Links |
|
|
|
|
 |
All times are GMT. The time now is 10:05 PM. |
 |
|
|
 |
|
 |
|
|
 |
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
|
|
|
|
Medical and Health forum | Computer Games Reviews | Graphics design forum
|
 |
|
 |
|
