cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6303
Views
0
Helpful
6
Replies

CMS DNS record configuration

anthonykaune
Level 4
Level 4

I'm looking at the deployment with CMS 2.1.5 and Expressway 8.9.2 to support the HTTS Proxy of WebRTC.  My domain is xyz.com and I currently have an Expressway pair setup for MRA, B2B, and XMPP federation.  

It looks like I would just create my CMS as eg: cms1.xyz.com, but I see there are XMPP SRV records.  I already have _xmpp-server._tcp.xyz.com and _xmpp-client._tcp.xyz.com externally which proxy through the Expressways to the CUCM IMP server.  Am I missing something here, or do I need to do something special to support CMS and have Jabber Federated?

Thanks in advance for any help.

1 Accepted Solution

Accepted Solutions

Patrick Sparkman
VIP Alumni
VIP Alumni

The WebRTC client doesn't require XMPP SRV records, that is only for the Cisco Meeting App native app.  Take a look at the Expressway with CMS and Microsoft Federation (X8.9.1) to configure the CMS Web Proxy, note the guide hasn't been updated for X8.9.2 which fully supports the web proxy, so the guide will still say it's unsupported even though it is if you're running X8.9.2.

View solution in original post

6 Replies 6

Patrick Sparkman
VIP Alumni
VIP Alumni

The WebRTC client doesn't require XMPP SRV records, that is only for the Cisco Meeting App native app.  Take a look at the Expressway with CMS and Microsoft Federation (X8.9.1) to configure the CMS Web Proxy, note the guide hasn't been updated for X8.9.2 which fully supports the web proxy, so the guide will still say it's unsupported even though it is if you're running X8.9.2.

Thank you!  If I did want to use the native Cisco Meeting App, then a separate subdomain would need to be used?  Also am I correct that the native Meeting App still requires an edge Server for CMS and not proxying through the expressway?

You can use the same domain as CMA will use SRV records to locate CMS, and yes, CMA still requires the use of the CMS Edge.  No idea when, but eventually the CMS Edge will be consolidated into the VCS/Expressway products reducing the number of required Edge components.

you would need a separate domain (or better yet a subdomain) if you needed to keep your XMPP clients separate (one for Expressway one for CMS). So you could use something like

_xmpp-client._tcp.cms.xyz.com

so it doesn't conflict with yopur base XMPP

I'd like to add a question about multiple Expressways. How's the DNS record will be look like if there is a Expressway Cluster. for example, I have expe-1.example.com and expe-2.example.com. 

Do we just point the A record join.example.com(webbridge) to the two expressways?

 

There's no perfect solution, you could use DNS round robin, or alternatively have the A record point to a load balancer which balanced betweren both Expressway-Es.