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

Fri Jul 27 12:51:29 EDT 2018

Using PG Explorer in configuration manager will tell you which routing client id is associated with each routing client.  You can run the PG setup without committing any changes, however we have only done this during maintenance windows.

Sean Davis

-----Original Message-----
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of cisco-voip-request at puck.nether.net
Sent: Friday, July 27, 2018 11:00 AM
To: cisco-voip at puck.nether.net
Subject: cisco-voip Digest, Vol 177, Issue 16

Send cisco-voip mailing list submissions to
cisco-voip at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
cisco-voip-request at puck.nether.net

You can reach the person managing the list at
cisco-voip-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific than "Re: Contents of cisco-voip digest..."

Today's Topics:

   1. wondering what these UCCx backup files are... (Lelio Fulgenzi)
   2. Re: wondering what these UCCx backup files are... (Brian Meade)
   3. UCCE: How to match Routing Client to IP address of Peripheral
      (Ryan Burtch)

----------------------------------------------------------------------

Message: 1
Date: Thu, 26 Jul 2018 18:05:31 +0000
From: Lelio Fulgenzi <lelio at uoguelph.ca>
To: "voyp list, cisco-voip (cisco-voip at puck.nether.net)"
<cisco-voip at puck.nether.net>
Subject: [cisco-voip] wondering what these UCCx backup files are...
Message-ID:
<YQBPR0101MB09456116197F427DFDB862B9AC2B0 at YQBPR0101MB0945.CANPRD01.PROD.OUTLOOK.COM>

Content-Type: text/plain; charset="utf-8"

Anyone know what the following backups files are for? I noticed one is small, and one is zero length. It?s sending my backup check script into a frenzy. ?

_UCCX_PHX_RPT.tar
_UCCX_PHX_CONFIG.tar

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 18688 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180726/9b4a4d77/attachment-0001.bin>

------------------------------

Message: 2
Date: Thu, 26 Jul 2018 14:25:37 -0400
From: Brian Meade <bmeade90 at vt.edu>
To: Lelio Fulgenzi <lelio at uoguelph.ca>
Cc: cisco-voip voyp list <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] wondering what these UCCx backup files
are...
Message-ID:
<CAGcuYh0u+S=4rB6vFppWctsnuZqhj9uyB==JbnphUt+LD-J7kg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Phoenix I think was the code name for Finesse.  So sounds like it's Finesse configuration related.

On Thu, Jul 26, 2018 at 2:05 PM Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

>
> Anyone know what the following backups files are for? I noticed one is
> small, and one is zero length. It?s sending my backup check script
> into a frenzy. ?
>
> _UCCX_PHX_RPT.tar
> _UCCX_PHX_CONFIG.tar
>
>
> ---
> Lelio Fulgenzi, B.A. | Senior Analyst
> Computing and Communications Services | University of Guelph Room 037
> Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
>
> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on
> Instagram, Twitter and Facebook
>
> [University of Guelph Cornerstone with Improve Life tagline]
>
> _______________________________________________
> 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/20180726/7443095f/attachment-0001.html>

------------------------------

Message: 3
Date: Fri, 27 Jul 2018 10:30:49 -0500
From: Ryan Burtch <rburtch3 at gmail.com>
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] UCCE: How to match Routing Client to IP address
of Peripheral
Message-ID:
<CAK+Shf65n7TNVOt58d1VQg=hHnd+Drju1OO28Sy2Y2m6im5NSA at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180727/1b8b7d28/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

------------------------------

End of cisco-voip Digest, Vol 177, Issue 16
*******************************************

Confidentiality Notice: This message (including any attachments) is only for the use of the person(s) for whom it is intended. It may contain confidential, proprietary and/or trade secret information. If you are not the intended recipient, you are forbidden to copy, distribute or use this information for any purpose, and you should inform the sender immediately and delete this e-mail.