Thanks Brian! Good to know. I also had an aha moment today and realized for the uds method to work the end user account must have "home cluster" checked on a cluster somewhere. Makes sense, if it was in the docs though I completely missed it. It was the other "glue" I couldn't figure out that ties things together.
On Tue, Jan 6, 2015, 7:38 PM Brian Meade <[email protected]> wrote: > Ed, > > I've been testing some UDS stuff and it looks like all servers with TFTP > activated are listed in the UDS response for: > https://x.x.x.x:8443/cucm-uds/user/bmeade/devices > under the provision section of the CSF device: > > <name>CSFbmeade</name> > <model>Cisco Unified Client Services Framework</model> > <product>390</product> > <description/> > <protocol>SIP</protocol> > <provision> > <uri>http://x.x.x.x:6970/CSFbmeade.cnf.xml</uri> > <uri>http://y.y.y.y:6970/CSFbmeade.cnf.xml</uri> > <uri>http://z.z.z.z:6970/CSFbmeade.cnf.xml</uri> > </provision> > > You just need to replace "bmeade" with your username and login with your > end user credentials. > > I don't see any way to change this behavior or set any priorities that I > have found. > > On Sat, Jan 3, 2015 at 3:59 PM, Ed Leatherman <[email protected]> > wrote: > >> Anthony, >> >> Thanks, I wondered at that too; after some closer inspection I found at >> the top of that same section: >> >>> Attention: >>> If the client gets the _cisco-uds SRV record from a DNS query, it can >>> automatically locate the user's home cluster. As a result, the client can >>> also locate the Cisco Unified Communications Manager TFTP service. >>> You do not need to specify your TFTP server address if you deploy the >>> _cisco-uds SRV record. >> >> >> The document is a bit confusing but probably because I appear to be >> implementing more of a corner case scenario. Not sure how it determines >> what TFTP server to use though yet. I will ask for the SRV record this week >> and test things out. >> >> >> Florian, Thanks for that link interesting to see what data is coming >> through the UDS connection. >> >> >> >> >> >> On Sat, Jan 3, 2015 at 3:16 PM, Anthony Holloway < >> [email protected]> wrote: >> >>> What version of Jabber are you deploying? According to the Jabber 10.5 >>> deployment guide, in Phone Only mode, there's only three ways to set the >>> TFTP server info, none of which are DNS SRV based: >>> >>> *Specify TFTP Servers in Phone Mode* >>> If you deploy the client in phone mode you can provide the address of >>> the TFTP server as follows: >>> >>> - Users manually enter the TFTP server address when they start the >>> client. >>> - You specify the TFTP server address during installation with the >>> TFTP argument. >>> - You specify the TFTP server address in the Microsoft Windows >>> registry. >>> >>> *Source: >>> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber_chapter_01001.html#CJAB_TK_SB10BC4C_00 >>> <http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber_chapter_01001.html#CJAB_TK_SB10BC4C_00>* >>> >>> Did I miss something and phone only mode can discover TFTP via DNS SRV >>> despite what the documentation states? I've never deployed phone only >>> mode, so I really don't know for sure. I'm just going by what the doc says. >>> >>> On Sat Jan 03 2015 at 1:59:02 PM Ed Leatherman <[email protected]> >>> wrote: >>> >>>> Interesting, thanks Josh. So does the client just pick a node running >>>> tftp service on it's own then based on the information from UDS? The reason >>>> I ask is I only have 2 nodes running that right now and its sounds like >>>> either one could potentially be used by a client at any given time. >>>> >>>> On Sat, Jan 3, 2015 at 12:31 PM, Josh Warcop <[email protected]> wrote: >>>> >>>>> Great question. There is a mixture of TFTP/UDS and version 9.x or 10.x >>>>> determines what is used and when. >>>>> >>>>> If you deploy the _cisco-uds SRV record you don't need to specify TFTP >>>>> because the client discovers that service via UDS from the cluster. >>>>> >>>>> >>>>> ------------------------------ >>>>> Date: Sat, 3 Jan 2015 10:38:57 -0500 >>>>> Subject: Re: [cisco-voip] Basic Jabber Deploy question >>>>> From: [email protected] >>>>> To: [email protected] >>>>> CC: [email protected]; [email protected] >>>>> >>>>> >>>>> Thanks Josh, >>>>> >>>>> As a follow up question then, lets say my jabber client happens to >>>>> resolve _cisco-uds to a node that isn't running TFTP service - what tells >>>>> it an IP address/hostname of a TFTP node to collect the "phone" >>>>> configuration, or is that delivered via the UDS connection? >>>>> >>>>> Kevin: CUCM v9, not running IM&P just using jabber in phone-only mode. >>>>> Literally just using it as softphone/video client on some laptops. >>>>> >>>>> On Wed, Dec 31, 2014 at 3:57 PM, Josh Warcop <[email protected]> wrote: >>>>> >>>>> Seems to be some confusion in this area... >>>>> >>>>> UDS runs on Tomcat and accessed over HTTPS and with recent versions >>>>> supports SAML SSO. It's throttled so there isn't any difference pointing >>>>> to >>>>> subscribers or publisher first. The UDS service is a network service on >>>>> each node and cannot be disabled. It has no direct dependencies on Call >>>>> Manager or TFTP running on the same node. >>>>> >>>>> >>>>> >>>>> ------------------------------ >>>>> From: [email protected] >>>>> To: [email protected]; [email protected] >>>>> Date: Wed, 31 Dec 2014 20:24:43 +0000 >>>>> Subject: Re: [cisco-voip] Basic Jabber Deploy question >>>>> >>>>> >>>>> What version of CUCM/IM&P? >>>>> >>>>> *From:* cisco-voip [mailto:[email protected]] *On >>>>> Behalf Of *Ed Leatherman >>>>> *Sent:* Wednesday, December 31, 2014 3:06 PM >>>>> *To:* Cisco VOIP >>>>> *Subject:* [cisco-voip] Basic Jabber Deploy question >>>>> >>>>> Hello, >>>>> >>>>> I'm working on a project to deploy jabber in a limited roll-out as >>>>> phone-only mode for a specific application. I'm interested in using srv >>>>> records as it looks like it might be easier for end-user/students to sign >>>>> into the client, so my question is related to that. I see that the >>>>> _cisco-uds record is used for the client to find call manager; does this >>>>> srv need to point to the publisher node, TFTP node, or CM node(s)? If not >>>>> the TFTP node, how does the client know where pull it's configuration from >>>>> once it has authenticated? >>>>> >>>>> I have jabber working OK manually just by configuring the client - >>>>> I'm just looking for ease-of-use here for the students and staff that will >>>>> be using it. >>>>> >>>>> Thanks for any clarification, most of the documents are centered >>>>> around IM&P which isn't what i'm after right now. >>>>> >>>>> Happy New Year! >>>>> >>>>> >>>>> -- >>>>> Ed Leatherman >>>>> >>>>> _______________________________________________ cisco-voip mailing >>>>> list [email protected] https://puck.nether.net/ >>>>> mailman/listinfo/cisco-voip >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Ed Leatherman >>>>> >>>> >>>> >>>> >>>> -- >>>> Ed Leatherman >>>> _______________________________________________ >>>> cisco-voip mailing list >>>> [email protected] >>>> https://puck.nether.net/mailman/listinfo/cisco-voip >>>> >>> >> >> >> -- >> Ed Leatherman >> >> _______________________________________________ >> cisco-voip mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-voip >> >> >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
