Wednesday, September 14, 2016

Cisco Meeting Server (CMS) Part 3 - Integrating Core and Edge

Part 1 - Making your first call to CMS
Part 2 - XMPP and CMA
Part 3 - Integrating Core and Edge

In this post, we are going to deploy a single CMS Core and a single CMS Edge.

1. Certificate for Core and Edge.  Like our previous posts in Part 1 and Part 2, I am going to use self signed cert for simplicity.

CMS Core:
pki selfsigned core

CMS Edge:
pki selfsigned edge

2. Using WinSCP or other SCP / sFTP client, to download the CMS Core certificate, in my case it is core.crt.  Copy this Core certificate to Edge using your SCP client.

In CMS Edge, create the loadbalancer service module and config the certificate for authentication.  You will need to trust your Core certificate in Edge.  In my lab it is a single NIC Edge.

CMS Edge:
loadbalancer auth edge edge.key edge.crt core.crt
loadbalancer trunk edge a:4999
loadbalancer trunk public edge a:5222 lo:5222
loadbalancer enable edge

3. In CMS Core, you are required to create a trunk.  Similarly, copy the edge certificate to core, you will need to trust the edge certificate in core. is the edge IP address.

CMS Core:
trunk create trunktoedge xmpp
trunk auth trunktoedge core.key core.crt edge.crt
trunk edge trunktoedge 4999
trunk enable trunktoedge

You can use the trunk debug trunktoedge (the tag name) to see whether the trunk is up on core.

4. There are a few service modules can be enabled on Edge.  If you want to enable SIP Edge, you will need the below command:

CMS Edge:
sipedge public a:5061
sipedge public-ip
sipedge private a:3061
sipedge certs sipedge.key sipedge.crt

5. Another service module on Edge is TURN.  To enable TURN, you will need the following command:

turn credentials admin admin
turn listen a
turn public-ip
turn enable

From the web user interface, you can enter the details under "TURN Server settings".  TURN Server Address (Server) is the intenal server IP address that the Call Bridge will use to access the TURN server.  TURN Server Address (Clients) is the public IP address assigned to the TURN server that external clients will use to access the TURN server.

6.  Finally you can enable the webbridge module on Edge, it will allow internal and external participants to join a meeting with their WebRTC capable browser.

First of all, certificate again.

CMS Edge:
pki csr webbridge
pki selfsigned webbridge

Copy your core CallBridge certificate to Edge, your webbridge service needs to trust your callbridge cert.  Then config the webbridge parameters:
webbridge listen a
webbridge certs webbridge.key webbridge.crt
webbridge trust callbridge.crt
webbridge http-redirect enable
webbridge enable

After configured, you can type "webbridge" to check your configured parameters.

Go to Configuration > General, enter your Guest account client URI, for example  The Guest Account JID domain is your domain, in my case it is

Depends on your DNS settings, you might need a few static entries on your edge, to resolve the xmpp SRV to your local loadbalancer FQDN.

dns add rr " IN A"
dns add rr " 86400 IN SRV 0 5 5269"
dns add rr " 86400 IN SRV 0 5 5222"

After all these steps, you should be able to use webbridge to join a meeting with WebRTC.

In summary, we have covered the integration between core and edge in a single split deployment, and we can enable a few service modules on edge including SIP Edge, TURN and WebBridge, for different call scenarios especially for B2B calls.

Part 1 - Making your first call to CMS
Part 2 - XMPP and CMA
Part 3 - Integrating Core and Edge


lindt said...

Awesome thanks!

lindt said...

HI there

you missed a command under the loadbalancer it should have

ACANO> loadbalancer create edge

and then your list of commands

lindt said...

sorry to message again,

in the loadbalancer commands it should read:

loadbalancer public edge a:5222 lo:5222

and not

loadbalancer TRUNK public edge a:5222 lo:5222

Tian wang said...

Hi Panda,
Can you please share the instruction of recording feature?
Thanks said...

Hi Mr. Wong.

Any chance of you going through the TURN elements , webbridge and customerization of bacground, logo and prompts.

Ali Bakhtiari said...


Jacky Lam said...

Thanks your instruction.

memble said...

hi all,

do i need to add xmpp-server & xmpp-client srv record to External DNS, if my deployment is CMS over expressway E?

any response really appreciate,
thank you

M.Kemal YENİGÜN said...

Hi Dear

I want to deploy single server combined model CMS application using with WebRTC expressway integration.

I could not clarfy it my mind.How calls come my endpoint if i use private ip on CMS ?

For example: if my CMS server wil be

In this guide I can see that multiple a /AAA record like that

for example my cms server:


Sould I define like this? on page 103.

All component wil work one box.

Can you please advice me more much.