[cisco-voip] Find specific PRI channel used by a call
Chris Lee
chris at variphy.com
Fri Nov 9 16:29:59 EST 2012
Hi Jeff,
I thought for 'UCM-aware' Gateway types (e.g. PRI, MGCP) the CDR does
include and show the channel/span number as either the Originating Span or
Terminating Span value.
Regards,
Chris
Chris Lee
Variphy, Inc.
Austin, Texas USA
Google Voice: +1-409-2SOLAR9 [409-276-5279] (office)(US Central: GMT-6)
On Fri, Nov 9, 2012 at 11:27 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
> i think it's much easier if you're running h323, but i'm running MGCP.
> here's what i've figured out so far, with some help from the list.
>
> - grab a "show voip rtp connections detail"
> - grab a "show voice call status"
> - from the rtp output, find the call you're looking for based on the
> IP address of the person with the issue.
> - grab the dstCallId from that call, convert to hex
> - find the hex call id in the voice call output
>
> it would be one heck of a coincidence that the callid numbers are the same
> but mean different things. and i would be unhappy.
>
>
>
> ------------------------------
> vgw-annu-a#show voip rtp connections detail
> VoIP RTP active connections :
> No. CallId dstCallId LocalRTP RmtRTP
> LocalIP RemoteIP
> 1 320480 320479 21848 23226
> 10.104.13.203 10.104.165.28
> callId 320480 (dir=2): called= calling= redirect= loopback=NO
> dest callId 320479: called= calling= redirect=
> 1 context 13CD06C0 xmitFunc 8381200
> 2 320644 320643 19402 21102
> 10.104.13.203 10.104.148.250
> callId 320644 (dir=2): called= calling= redirect= loopback=NO
> dest callId 320643: called= calling= redirect=
> 1 context 2108D28 xmitFunc 8381200
> 3 320646 320645 27818 17814
> 10.104.13.203 10.104.13.201
> callId 320646 (dir=2): called= calling= redirect= loopback=NO
> dest callId 320645: called= calling= redirect=
> 1 context 426B7CA0 xmitFunc 8381200
> 4 320652 320651 19400 18924
> 10.104.13.203 10.104.149.119
> callId 320652 (dir=2): called= calling= redirect= loopback=NO
> dest callId 320651: called= calling= redirect=
> 1 context 13E5E824 xmitFunc 8381200
> 5 320656 320655 29128 27008
> 10.104.13.203 10.104.87.40
> callId 320656 (dir=2): called= calling= redirect= loopback=NO
> dest callId 320655: called= calling= redirect=
> 1 context 426D39E4 xmitFunc 8381200
> 6 320660 320659 19196 17758
> 10.104.13.203 10.104.13.201
> callId 320660 (dir=2): called= calling= redirect= loopback=NO
> dest callId 320659: called= calling= redirect=
> 1 context 13CBEC9C xmitFunc 8381200
> Found 6 active RTP connections
> ------------------------------
> vgw-annu-a#show voice call status
> CallID CID ccVdb Port Slot/DSP:Ch Called # Codec
> MLPP Dial-peers
> 0x4E3DF 1AE 0x422E9FEC 0/0/0:23.4 0/1:17 * g711ulaw 0/0
> 0x4E483 200 0x422E9FEC 0/0/0:23.5 0/1:3 * g711ulaw 0/0
> 0x4E485 201 0x0202F1B8 0/0/3:23.1 0/1:7 * g711ulaw 0/0
> 0x4E48B 204 0x422E9FEC 0/0/0:23.1 0/1:2 * g711ulaw 0/0
> 0x4E48F 206 0x422E9FEC 0/0/0:23.6 0/1:5 * g711ulaw 0/0
> 0x4E493 208 0x0202F1B8 0/0/3:23.2 0/1:6 * g711ulaw 0/0
> 0x4E497 20A 0x422E9FEC 0/0/0:23.2 0/1:1 * g711ulaw 0/0
> 7 active calls found
> ------------------------------
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it.
> - LFJ (with apologies to Mr. Popeil)
>
>
> ------------------------------
> *From: *"Jeff B. Orr" <JOrr at parknationalbank.com>
> *To: *cisco-voip at puck.nether.net
> *Sent: *Friday, November 9, 2012 11:31:54 AM
> *Subject: *[cisco-voip] Find specific PRI channel used by a call
>
>
> Does anyone know how to show the specific PRI channel being used by a
> call? This is a Call Manager 8.5 environment with a 2900 router running (4)
> PRIs.
>
>
>
> I am trying to track down an issue that appears to be related to one
> specific B-channel and need to busyout it.
>
>
>
> Thanks!
>
> Jeff
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121109/324763e3/attachment.html>
More information about the cisco-voip
mailing list