[cisco-voip] CCM Trace - MAC & IP: Source/Dest?

Tue Mar 11 12:28:42 EDT 2008

Hello and good afternoon:

            I have a few questions regarding CCM traces. I’ve read through my fair share of trace files but I recently noticed something within CCM traces that doesn’t quite make sense to me. Below is an excerpt of a CCM trace for an on-net call. The calling device is SEP001C58A2B308 (DN 3500/Line1_RTP – IP 192.168.102.175) and the called device is SEP001C58F075EA (DN 3037/Line1_RTP – IP 192.168.102.203). I’ve omitted a large portion of the trace and only included relevant lines. Questions listed below trace lines.

::::: Note the message ID, MAC, and IP ::::
::::: Calling party pressing NewCall softkey ::::
03/07/2008 12:01:21.055 CCM|StationInit: (0044624) SoftKeyEvent softKeyEvent=2(NewCall) lineInstance=1 callReference=0.|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362322><IP::192.168.102.175><DEV::SEP001C58A2B308>
03

::::: Msg ID stays the same ::::
::::: CCM instructing phone to display “Enter Number” on LCD screen ::::
03/07/2008 12:01:21.055 CCM|StationD:    (0044624) DisplayPromptStatus timeOut=0 Status='€ ' content='Enter Number' line=1 CI=16777355 ver=8570000c.|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362322><IP::192.168.102.175><DEV::SEP001C58A2B308>

::::: Skipping traces… CCM tells phone to play inside tone… user dials “3037”… DA matches correct DN/partition ::::::::::::::::

::::: CCM checks busy trigger of called device… CCM instructs called phone to display “From 3500” on LCD screen :::::
::::: CCM instructs called phone to play inside ring :::::
::::: NOTICE the message ID change for the new call leg. In addition, notice how the MAC and IP add are kept the same when this is clearly destined for the called device :::::
03/07/2008 12:01:23.805 CCM|StationD:    (0044522) DEBUG  whatToDo: busy trigger not hit... send to open appearance|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362326><IP::192.168.102.175><DEV::SEP001C58A2B308>

03/07/2008 12:01:23.805 CCM|StationD:    (0044522) DisplayPromptStatus timeOut=0 Status='€_3500' content='From 3500' line=1 CI=16777356 ver=8570000c.|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362326><IP::192.168.102.175><DEV::SEP001C58A2B308>

03/07/2008 12:01:23.805 CCM|StationD:    (0044522) SetRinger ringMode=2(InsideRing).|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362326><IP::192.168.102.175><DEV::SEP001C58A2B308>

::::: Called party answers call :::::
::::: Notice the MAC and IP changes for the called device :::::
03/07/2008 12:01:28.695 CCM|StationInit: (0044522) SoftKeyEvent softKeyEvent=11(Answer) lineInstance=1 callReference=16777356.|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362329><IP::192.168.102.203><DEV::SEP001C58F075EA>

::::: CCM instructs calling device to start sending RTP packets to called device :::::
::::: Notice myIP is .175 (calling device) and remoteIP is the called device, but the IP and MAC at the end of the trace shows the called device :::::

03/07/2008 12:01:28.805 CCM|StationD:    (0044624) startMediaTransmission conferenceID=16777355 passThruPartyID=16777905 remoteIpAddress=cb66a8c0(192.168.102.203)             remotePortNumber=26544 milliSecondPacketSize=20 compressType=4(Media_Payload_G711Ulaw64k) qualifierOut=?. myIP: af66a8c0 (192.168.102.175)                   mediaEncryption algorithmID=0 keylen=0 saltlen=0|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362331><IP::192.168.102.203><DEV::SEP001C58F075EA>

      QUESTIONS:

-    For sent StationD and received StationInit SCCP messages, aren’t the IP and MAC addresses located at the end of the trace line supposed to specify the source or destination of the message? As you can see above, CCM was instructing the called device to display “From 3500” on its LCD screen, yet the MAC and IP addresses at the end of the trace line was for the calling device. I thought the message identifier would be consistent with this information too.

-    The Cisco IPTT book mentions that TCP Handle are assigned to IPT devices upon boot up and can be tracked by searching through keepalives. Am I correct to assume this was removed from CCM traces at some point? I always review CCM traces when logging levels are set to Detailed, yet I fail to find the TCP Handles anywhere within the trace files.

Thanks ahead of time for your input on this!

Daniel Rodriguez, CCVP
Fidelus Technologies, LLC
240 West 35th Street | 6th Floor | New York, NY 10001
o: 212.616-7843 | c: 917-797-2543 | f: 212.616-7850
e: drodriguez at fidelus.com<mailto:drodriguez at fidelus.com> | www.fidelus.com<http://www.fidelus.com>
[cid:image001.jpg at 01C88372.E30AB7E0]

________________________________
NOTICE: This e-mail and any attachment contain confidential information that may be legally privileged. If you are not the intended recipient, you must not review, retransmit, print, copy, use or disseminate it. Please immediately notify us by return e-mail and delete it. If this e-mail contains a forwarded e-mail or is a reply to a prior e-mail, the contents may not have been produced by the sender and therefore we are not responsible for its contents.
This notice is automatically appended to each e-mail. It is the recipient's responsibility to take measures to ensure that this e-mail is virus free, and no responsibility is accepted by Fidelus Technologies LLC for any loss or damage arising in any way from its use.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080311/42b9096f/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2185 bytes
Desc: image001.jpg
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20080311/42b9096f/attachment-0001.jpg 