CMS design

[rperez1976]

Hi team,

We are facing a project in which we have 4xCMS2K. We are thinking about using a pair of Exp-E as traversal connected to a pair of Exp-C. We plan to deploy  CMSs as internal resources. So it seems that we have to turn on "TURN services" on the expressway so we can give access to webRTC clients to join spaces. We are a bit confused about the configuration, because it seems that CMS2K does not support TURN services and ,at least ,as we understand besides of turning on TURN services on E-E and point the E-C to CMS (srv_external) , we must enable TURN on CMS.  That doesn´t make sense.

What is the recommended configuration or deployment?

[Haydn von Imhof]

Good Day,

In your deployment are you looking for clarity on Internal webRTC users or external webRTC users connecting to your CMS's?

If internal, clients can talk directly to the CMS Web bridge and call bridge so there would be no need for a Exp E or C or TURN services.

If you are looking to connect external webRTC users then its recommended you use a Expressway E & C pair as both a web proxy and TURN server. There is no need to configure the turn service on the CMS itself as you will add the Expressway-E as TURN server onto the CMS.

You can find more information here:

https://www.cisco.com/c/en/us/support/docs/conferencing/meeting-server/210800-configure-cms-webrtc-proxy-over-expressw.html

Also note that Cisco plans to remove the TURN server component from the Cisco Meeting Server software in a future version so its best to start your setup with TURN using Expressways.

Hope this helps,