[cisco-voip] UCCE: How to match Routing Client to IP address of Peripheral

[Dave, Pavan]

Ryan,

Here is a sample query for that gets you half way there to make it easier to troubleshoot.

select P.EnterpriseName, T.PeripheralID, *
FROM lab_hds.dbo.t_Termination_Call_Detail T
LEFT JOIN lab_awdb.dbo.Peripheral P ON P.PeripheralID = T.PeripheralID

You can work on that query to get more info but I found at least getting the 500x correlated to a name cuts down some of the time.

EnterpriseName               PeripheralID
VRU_PIM1          5001
CUCM_PIM1      5000
VRU_PIM1          5001
MR_PIM1            5002
CUCM_PIM1      5000
MR_PIM1            5002

Regards,



From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Burtch
Sent: Friday, July 27, 2018 10:31 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] UCCE: How to match Routing Client to IP address of Peripheral

EXTERNAL EMAIL





I work in Managed Services.  I have to get into different customer environments when issues happen. Many times, I'm researching a dropped call or something like that via the AW/HDS.



I see the calls come into RCD/TCD via some Routing Client '5001, 5002, etc', but I need a way to correlate these routing clients to the actual peripheral's IP ADDRESS (CVP1,2,3, CUCM, etc.)



I know I can get this from PG setup, but I can't take the environment down when I'm troubleshooting, plus I have no idea which PG to pull from as many of these environments are quite large.



Is there any other way to get this info quickly?  Thoughts.




Sincerely,

Ryan Burtch

Pavan Dave | Sr. Contact Center Engineer
Presidio (NASDAQ: PSDO) | presidio.com<http://presidio.com>
1955 Lakeway Drive Suite 220, Lewisville, TX 75057
D: 469.464.1283 | C: 832.860.5465 | pdave at presidio.com<mailto:pdave at presidio.com>





This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments. Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180727/bb5ba023/attachment.html>