You’ll notice in the SRV record itself that TCP is called out. In the outputs above, you’ll see the SRV record and its priority, weight, port and host the has the service. **There are additional records required for Collaboration Edge** The following is an example of the _cuplogin SRV record: The following is an example of the _cisco-uds SRV record: – What SRV records do we need to add? Cisco gives us a good run down in the document referenced above, I copied the below passage from that document. My system is a 2008 Server Standard instance. I realize that not every enterprise uses Windows for internal DNS, but since the majority seem to, we’ll cover Windows DNS. You may have, at your disposal, wonderful Server Engineers who know DNS like you know Call Manager, but not every situation is that clean. So we know that SRV records are important, but are they really our problem as Collaboration Engineers? I guess that depends on how broad your IT shop or your customer’s IT shop is. Without SRV records flexible Jabber deployment becomes difficult and Collaboration Edge integration becomes next to impossible. There are SRV records that Jabber looks for for directory services as well as Collaboration Edge (Cisco Expressway) which is its own animal. The record above points at the IM & Presence service across port 8443 which happens to be what Jabber/IM&P uses for authentication. _ is an SRV record the Jabber looks for during service discovery and sign-in. SRV records allow servers to advertise service locations within the core of the DNS architecture. If you don’t know about them or if you are a little rusty, Cisco has a good document (link below) that you should get to know intimately… If you’ve deployed Cisco’s IM & Presence (formerly Cisco Unified Presence or CUPS) and its associated Jabber product line, you know all about DNS SRV records, or at least you should.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |