Jabber DNS Records

[JustForVoice_2]

Hello,

Could you please help me to know the required records to be added for Jabber to work with Expressway C&E

Regards,

[JustForVoice_2]

from my reading in Cisco documentations, I found the following :

Public DNS
The public (external) DNS must be configured with _collab-edge._tls.<domain> SRV records so that endpoints can discover the expressway-Es to use for mobile and remote access. SIP service records are also required (for general deployment, not specifically for mobile and remote access). For example, for cluster of 2 expressway systems

example.com >> collab-edge >>  expe1.example.com
example.com >>  collab-edge >> expe2.example.com
example.com>>   sips >>  expe1.example.com
example.com>>  sips >>  expe2.example.com

Local DNS
The local (internal) DNS requires _cisco-uds._tcp.<domain> and _cuplogin._tcp.<domain> SRV records

example.com >> cisco-uds >> cucmserver.example.com
example.com >> cuplogin >>   cupserver.example.com

Could you please confirm if these are the required records to deploy Jabber with Expressway C&E. Is there any other record that I should ask my customer to create before starting the deployment? Other records needed for some cases?

Thanks

[JustForVoice_2]

Table:

Public DNS
The public (external) DNS must be configured with _collab-edge._tls.<domain> SRV records so that endpoints can discover the expressway-Es to use for mobile and remote access. SIP service records are also required (for general deployment, not specifically for mobile and remote access). For example, for cluster of 2 expressway systems
No#	Domain	Service	Protocol	Priority	Weight	Port	Target host
1	example.com	collab-edge	tls	10	10	8443	expe1.example.com
2	example.com	collab-edge	tls	10	10	8443	expe2.example.com
3	example.com	sips	sip	10	10	5061	expe1.example.com
4	example.com	sips	sip	10	10	5061	expe2.example.com
Local DNS
The local (internal) DNS requires _cisco-uds._tcp.<domain> and _cuplogin._tcp.<domain> SRV records
No#	Domain	Service	Protocol	Priority	Weight	Port	Target host
1	example.com	cisco-uds	tcp	10	10	8443	cucmserver.example.com
2	example.com	cuplogin	tcp	10	10	8443	cupserver.example.com

Thanks

[Ayodeji Okanlawon]

Before we talk about DNS requirements, please understand your customers domain  infrastructure before proceeding with any deployment . 

Does your customer have a single domain that is used both internally and externally. If this is not the case then you need to consider how to address this. 

Now to DNS. 

You need a minimum of two SRV records 

1. Internal DNS.. 

_cisco-uds._tcp.domain

This SRV will point to your Uds server(s) 

2. External DNS 

_collab-edge._tls.domain

This will point to expwe server 

3. DNS A Records 

Expwe can be deployed either using a single NIC using dual NIC. Dual NIC is easier from a firewall perspective. 

If you are using a Dual NIC, then you need an A record for expwe in your internal DNS that will resolve to the internal ip address of expwe. This is what you will use for the traversal connection from expwc. 

You will also need Arecord for your Uds servers. 

Nb: it is better to deploy your cucm servers with FQDN,when deploying jabber due to certificate issues. If your  cucm is already deployed with IP address, the you need to add these IP to each SAN of your  csr request before sending the certs off to be signed by a CA 

Lots to consider.. Lots

[JustForVoice_2]

Thank you for your support again,

let me discuss it one by one. for customer DNS domain, they have two:

example.local

example.com

but I asked them to add zone in the DNS to resolve the names as it they are example.com. and the names for UC server are

UCXXX.example.com.

In this case shall I consider my customer has one domain?

[Ayodeji Okanlawon]

Your customer has two domains. One is routable example.com and the other is not.. example.local

I do not see how your UC servers are in example.com unless they have implemented split DNS. So you need to verify this as this is the only way jabber Mra works with this setup. 

[JustForVoice_2]

I Think you mean by split DNS is, they have a local DNS server and a DNS in public. I think this is the scenario,

when I asked them to create the A records for my UC servers they said this is not routable by default but we can do it.

and I tested in my lab by creating forward lookup zone for example.com and I was able to resolve the names of my servers

[Ayodeji Okanlawon]

It looks like they have already implemented split DNS. 

You need to do internal SRV  DNS query for Cisco-uds record and be sure it's setup as required 

[JustForVoice_2]

what about cuplogin? do I need it? I think it's only for version 8.

I'm using 10

and for cisco-uds, I think I have to create a record for each Call manager node?

[Ayodeji Okanlawon]

No you don't need cup-login. You don't  need to create a record for each cucm node.  Yiu should have at least two servers or load balancing. Jabber will use the serves defined in the Cisco-uds SRV record to discover the cucm servers for the user trying to login, so you do the need to Configure all of them