Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Call dropped

03/21/2006 14:55:20.417 CCM|StationInit - InboundStim - KeepAliveMessage - Send KeepAlive to Device Controller. DeviceName=SEP000F1FA22BB9, TCPHandle=000131522, IPAddr=192.168.2.36, Port=1709, Device Controller=[3,89,21226]|<CLID::ICSCCM1-Cluster><NID::172.17.0.21><CT::3,100,90,1.49638806><IP::192.168.2.36><DEV::SEP000F1FA22BB9>

03/21/2006 14:55:20.837 CCM|StationInit - InboundStim - KeepAliveMessage - Send KeepAlive to Device Controller. DeviceName=SEP000D29F62398, TCPHandle=000118079, IPAddr=172.17.0.75, Port=51842, Device Controller=[3,89,20748]|<CLID::ICSCCM1-Cluster><NID::172.17.0.21><CT::3,100,90,1.49638807><IP::172.17.0.75><DEV::SEP000D29F62398>

03/21/2006 14:55:21.008 CCM|StationInit - InboundStim - KeepAliveMessage - Send KeepAlive to Device Controller. DeviceName=SEP000D288E2E96, TCPHandle=000131378, IPAddr=172.17.0.153, Port=1028, Device Controller=[3,89,21224]|<CLID::ICSCCM1-Cluster><NID::172.17.0.21><CT::3,100,90,1.49638808><IP::172.17.0.153><DEV::SEP000D288E2E96>

03/21/2006 14:55:21.218 CCM|StationInit - InboundStim - KeepAliveMessage - Send KeepAlive to Device Controller. DeviceName=SEP000D29F62801, TCPHandle=000118048, IPAddr=172.17.0.101, Port=53100, Device Controller=[3,89,20717]|<CLID::ICSCCM1-Cluster><NID::172.17.0.21><CT::3,100,90,1.49638809><IP::172.17.0.101><DEV::SEP000D29F62801>

03/21/2006 14:55:21.318 CCM|StationInit - InboundStim - KeepAliveMessage - Send KeepAlive to Device Controller. DeviceName=SEP000D6507C67A, TCPHandle=000118040, IPAddr=172.17.0.62, Port=52716, Device Controller=[3,89,20698]|<CLID::ICSCCM1-Cluster><NID::172.17.0.21><CT::3,100,90,1.49638810><IP::172.17.0.62><DEV::SEP000D6507C67A>

-----------------------

Can somebody help to explain this?

Thanks

3 REPLIES
Cisco Employee

Re: Call dropped

the traces you have sent above shows only keepalives. What is the problem?

New Member

Re: Call dropped

Call dropped for extision 205 around 10:46 this time, I attached the more detailed log from CCM, can you help to explain why this call dropping happened?

Thanks

Cisco Employee

Re: Call dropped

This is an incomplete trace..Here is what I can tell:

Kim Glen called 94162489195

'0040373C87D8B11D781C0000AC110094'H is the H323 Call ID. it goes from setup to connect state (it has already gone thru alerting, which means the user heard a half a ring).. After the connected state, I expect to see media capabilities exchange, which is not in the trace. I have a feeling that is where it fails... So, Make another call and get a complete trace, till you see the H323 disconnect..

Also find out if the far end is capable of routing 9+ 10 digits (without the leading 1)

Thanks!

262
Views
0
Helpful
3
Replies
CreatePlease login to create content