[cisco-voip] call tracking question

[Ahmed Abd EL-Rahman]

Thanks Daniel.



Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer - KSA

From: Daniel Pagan [mailto:dpagan at fidelus.com]
Sent: Sunday, November 15, 2015 11:44 PM
To: Ahmed Abd EL-Rahman <Ahmed.Rahman at bmbgroup.com>; Sreekanth Narayanan (sreenara) <sreenara at cisco.com>; cisco-voip at puck.nether.net
Subject: RE: call tracking question

Sreekanth: Really enjoyed your LUA scripting video.

Ahmed: Adding to this, you can use the Call-ID header for identifying a specific SIP call flow in the output of debug ccsip messages. The Call-ID header field is a unique identifier for the SIP dialog, which means the Call-ID header field for the incoming call-leg will be different from the outgoing call-leg, but persistent for the duration of the dialog (not guaranteed to be the entire call, but more than likely the entire call). There are other unique headers fields within SIP, all helpful and used in their own way, but the Call-ID header is very useful for a high-level view of transactions involved in a dialog. For information on SIP signaling, I suggest starting with online articles by Andrew Prokop (google his name...). He talks on Avaya platforms but focuses heavily on RFC concepts.

Hope this helps.
- Dan

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ahmed Abd EL-Rahman
Sent: Sunday, November 15, 2015 6:27 AM
To: Sreekanth Narayanan (sreenara) <sreenara at cisco.com<mailto:sreenara at cisco.com>>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] call tracking question

Many thanks Sreekanth, really appreciated.



Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer - KSA
From: Sreekanth Narayanan (sreenara) [mailto:sreenara at cisco.com]
Sent: Sunday, November 15, 2015 2:11 PM
To: Ahmed Abd EL-Rahman <Ahmed.Rahman at bmbgroup.com<mailto:Ahmed.Rahman at bmbgroup.com>>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: call tracking question

You'll firstly need to find the call using the called or calling number, and then you can track it using the Global call identifier in the CCAPI logs.
For example, in this line:
8261462: Sep 29 14:31:10.720: //640449/14CF2490BDF1/CCAPI/cc_api_call_connected:
   Call Entry(Connected=TRUE, Responsed=TRUE, Retry Count=0)

14CF2490BDF1 is the GCID. This will remain constant on the call, and you will see 2 different legs (if it is a simple call, and doesn't include conference).
640449 is the leg ID. There will be one matching the incoming side, and the other for the outgoing side.
You can use Notepad++ or Jedit to highlight the GCID and the leg numbers to track the call then.
I'd suggest logging all the debugs to the buffer so you don't lose any information. This is a usual template you can use.

Router(config)#service timestamps debug datetime msec
Router(config)#logging buffered <buffer size> debugging
Router(config)#service sequence
Router(config)#no logging rate-limit
Router#term no mon

Then output all the logs using show logging command

Thanks
Sreekanth


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ahmed Abd EL-Rahman
Sent: Sunday, November 15, 2015 4:30 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] call tracking question

Hi Gents,

If I'm executing debug commands like debug voice ccapi inout and debug csip messages on a voice router and I need to track a certain call among a lot of calls passing through the VGW at the same moment, how can I do that ?




Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer - KSA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151124/184e2c1a/attachment.html>