Re: [cisco-voip] Are there any gotchas to watch out for switching to FQDN server names from IP address server names?

I forgot to put a smiley face in that email, I wasn't trying to be a jerk with my Trivial File Transfer Protocol jab :) On Thu, Dec 1, 2016 at 9:54 PM, Nick Barnett wrote: > By definition, TFTP is trivial. > > The service either needed deactivated or the server needed to

Re: [cisco-voip] Are there any gotchas to watch out for switching to FQDN server names from IP address server names?

By definition, TFTP is trivial. The service either needed deactivated or the server needed to restart. Either way, the TFTP server is going down to regenerate the certs. On Thu, Dec 1, 2016 at 4:41 PM, Ryan Huff wrote: > Anthony and James have highlighted one of the

Re: [cisco-voip] Are there any gotchas to watch out for switching to FQDN server names from IP address server names?

The question I pose in response to that line of thinking is: Why is a client pulling TFTP from the server while you're deactivating the services, and why do you not have redundant TFTP? The scenario I mentioned regarding the phone needing a restart would only be necessary if the phone was in a

Re: [cisco-voip] Are there any gotchas to watch out for switching to FQDN server names from IP address server names?

Anthony and James have highlighted one of the greater weaknesses of thinking like an engineer. As an engineer, we look at TFTP service interruption and see all the potential outcomes and things that could happen. We think about a firmware download being interrupted on an endpoint and realize

Re: [cisco-voip] Are there any gotchas to watch out for switching to FQDN server names from IP address server names?

If the endpoint is 8000 miles away from you and located in a nuclear power plant, that TFTP interruption wasn't so trivial. On Thu, Dec 1, 2016 at 5:10 PM, Ben Amick wrote: > An endpoint in the middle of an upgrade has already entirely downloaded > the firmware into memory,

Re: [cisco-voip] Are there any gotchas to watch out for switching to FQDN server names from IP address server names?

An endpoint in the middle of an upgrade has already entirely downloaded the firmware into memory, and would not be affected. If it is mid-download then it would have no affect other than breaking the operation and perhaps requiring a manual restart if it is coming off a factory reset Ben Amick

Re: [cisco-voip] Are there any gotchas to watch out for switching to FQDN server names from IP address server names?

Is TFTP really that trivial? What would happen to an endpoint, which is in the middle of a firmware upgrade, when you deactivate TFTP? On Thu, Dec 1, 2016 at 2:51 PM, Nick Barnett wrote: > I figured that a reboot would work, but TAC told me it wouldn't... and > rather

Re: [cisco-voip] Call Recording with CUCM9.1

And if you have centralized call ingress/egress, like with enterprise SIP trunks, you can use media class forking on the CUBE to cut down on WAN usage. On Thu, Dec 1, 2016 at 8:22 AM, Ryan Huff wrote: > Cisco MediaSense is a great (and admittedly, simple) option for BIB >

Re: [cisco-voip] TP Room Endpoints - Name and Number on TV Display

This worked beautifully. And yes, setting it on other side: codec side or CM side, forced an update to the opposite side. Also, no Apply Config/Reset/Restart required, the display at the top just changes. Dangso simple. Well, I guess that's ignorance for you. I'm new to Telepresence.

Re: [cisco-voip] TP Room Endpoints - Name and Number on TV Display

All the settings on the Device page correspond pretty directly to the endpoint’s xconfig equivalent. In later TC code and UCM it will even push an update you make on the endpoint up to UCM (for one of those fields). There used to be an Admin guide for TP Enpoints with CUCM but I don’t know if

Re: [cisco-voip] TP Room Endpoints - Name and Number on TV Display

Do you have a link you can refer me to which explains how this setting is used? And, do you know if all TP endpoints support that field equally? I'll give this a try in a few minutes and report back. Thanks Ryan! On Thu, Dec 1, 2016 at 12:53 PM, Ryan Ratliff (rratliff)

Re: [cisco-voip] TP Room Endpoints - Name and Number on TV Display

I’d recommend setting the System Name on the Device page for the C20. That will sync up with the endpoint’s local setting and avoid any interop issues with the Line value. -Ryan On Dec 1, 2016, at 1:27 PM, Anthony Holloway wrote: Hi All, I am wondering if

Re: [cisco-voip] Cisco Webex Meetings Server Error 23

I'm not aware of the connection between Verisign and CWMS. How did you even think to do that? Random guess? I do know that CWMS certs signed by an intermediate CA will require you to upload the chain in a single file, in order for CWMS to present the chain to the client machine. You can click

Re: [cisco-voip] Call Recording with CUCM9.1

Cisco MediaSense is a great (and admittedly, simple) option for BIB recording; just need to purchase the RTU and put it on some virtual hardware. Sent from my iPhone On Dec 1, 2016, at 9:17 AM, Brian Meade > wrote: You're probably much better using

Re: [cisco-voip] Call Recording with CUCM9.1

You're probably much better using BIB(built-in bridge)-based/network recording instead. It uses the Built-in-bridge of the phones to send duplicate RTP streams to a recording server. Most recording servers out there now prefer this method. It's technically possible to route the span sessions

[cisco-voip] Cisco Unity Data Dump Auto-config

Does anyone know if the Cisco UDD program from UnityTools has any way it can be programmed to automatically add new users to the file? It's been set up in our environment for ever that we use that program to produce reports that are harvested by as SQL script for reporting purposes, but it's