<span style="font-family:arial,sans-serif;font-size:13px">Hi Jeff,</span><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">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.</span><br>
</div><div class="gmail_extra"><br>Regards,<div><br></div><div>Chris</div><div><br><div>Chris Lee</div><div>Variphy, Inc.</div><div>Austin, Texas USA</div><div><span style="font-family:arial,sans-serif;font-size:13px">Google Voice: </span><span style="font-size:13px;font-family:arial,sans-serif">+1-409-2SOLAR9 </span><a value="+14092765279" style="font-size:13px;font-family:arial,sans-serif">[409-276-5279</a><span style="font-size:13px;font-family:arial,sans-serif">] (office)(US Central: GMT-6)</span></div>
</div><div><span style="font-size:13px;font-family:arial,sans-serif"><br></span></div><br><div class="gmail_quote">On Fri, Nov 9, 2012 at 11:27 AM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div style="font-size:10pt;font-family:Verdana"><br>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.<br>
<ul><li>grab a "show voip rtp connections detail"</li><li>grab a "show voice call status"</li><li>from the rtp output, find the call you're looking for based on the IP address of the person with the issue.</li>
<li>grab the dstCallId from that call, convert to hex</li><li>find the hex call id in the voice call output</li></ul><p>it would be one heck of a coincidence that the callid numbers are the same but mean different things. and i would be unhappy.</p>
<p><br></p><br><hr><font face="Courier New, courier, monaco, monospace, sans-serif">vgw-annu-a#show voip rtp connections detail<br>VoIP RTP active connections :<br>No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP<br>
1 320480 320479 <a href="tel:21848%C2%A0%C2%A0%C2%A0%2023226" value="+12184823226" target="_blank">21848 23226</a> 10.104.13.203 10.104.165.28<br> callId 320480 (dir=2): called= calling= redirect= loopback=NO<br>
dest callId 320479: called= calling= redirect=<br> 1 context 13CD06C0 xmitFunc 8381200<br>2 320644 320643 19402 21102 10.104.13.203 10.104.148.250<br> callId 320644 (dir=2): called= calling= redirect= loopback=NO<br>
dest callId 320643: called= calling= redirect=<br> 1 context 2108D28 xmitFunc 8381200<br>3 320646 320645 27818 17814 10.104.13.203 10.104.13.201<br> callId 320646 (dir=2): called= calling= redirect= loopback=NO<br>
dest callId 320645: called= calling= redirect=<br> 1 context 426B7CA0 xmitFunc 8381200<br>4 320652 320651 19400 18924 10.104.13.203 10.104.149.119<br> callId 320652 (dir=2): called= calling= redirect= loopback=NO<br>
dest callId 320651: called= calling= redirect=<br> 1 context 13E5E824 xmitFunc 8381200<br>5 320656 320655 29128 27008 10.104.13.203 10.104.87.40<br> callId 320656 (dir=2): called= calling= redirect= loopback=NO<br>
dest callId 320655: called= calling= redirect=<br> 1 context 426D39E4 xmitFunc 8381200<br>6 320660 320659 19196 17758 10.104.13.203 10.104.13.201<br> callId 320660 (dir=2): called= calling= redirect= loopback=NO<br>
dest callId 320659: called= calling= redirect=<br> 1 context 13CBEC9C xmitFunc 8381200<br>Found 6 active RTP connections<br></font><hr><font face="Courier New, courier, monaco, monospace, sans-serif">vgw-annu-a#show voice call status<br>
CallID CID ccVdb Port Slot/DSP:Ch Called # Codec MLPP Dial-peers<br>0x4E3DF 1AE 0x422E9FEC 0/0/0:23.4 0/1:17 * g711ulaw 0/0<br>0x4E483 200 0x422E9FEC 0/0/0:23.5 0/1:3 * g711ulaw 0/0<br>
0x4E485 201 0x0202F1B8 0/0/3:23.1 0/1:7 * g711ulaw 0/0<br>0x4E48B 204 0x422E9FEC 0/0/0:23.1 0/1:2 * g711ulaw 0/0<br>0x4E48F 206 0x422E9FEC 0/0/0:23.6 0/1:5 * g711ulaw 0/0<br>
0x4E493 208 0x0202F1B8 0/0/3:23.2 0/1:6 * g711ulaw 0/0<br>0x4E497 20A 0x422E9FEC 0/0/0:23.2 0/1:1 * g711ulaw 0/0<br>7 active calls found</font><br><hr><br><span><br><span name="x"></span>---<br>
Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr><b>From: </b>"Jeff B. Orr" <<a href="mailto:JOrr@parknationalbank.com" target="_blank">JOrr@parknationalbank.com</a>><br>
<b>To: </b><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Sent: </b>Friday, November 9, 2012 11:31:54 AM<br><b>Subject: </b>[cisco-voip] Find specific PRI channel used by a call<div>
<div class="h5"><br><br>
<div>
<p class="">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.</p>
<p class=""> </p>
<p class="">I am trying to track down an issue that appears to be related to one specific B-channel and need to busyout it.</p>
<p class=""> </p>
<p class="">Thanks!</p>
<p class="">Jeff</p>
</div>
<br></div></div>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div>
</div>