Hy Look here https://developer.cisco.com/media/cisco-user-data-serviccs-usd-dev-guide/index.html?getting_started.html
The Client goes to the UDS Service and get's all he needs to know where to go cheers -- Florian Kroessbacher [email protected] [image: Twitter] <https://twitter.com/flohATinnsbruck> [image: Google Plus] <https://plus.google.com/+FlorianKroessbacher> [image: Linkedin] <https://www.linkedin.com/profile/view?id=115928906> 2015-01-03 20:54 GMT+01:00 Ed Leatherman <[email protected]>: > 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 > >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
