Cisco Cisco TelePresence Video Communication Server Expressway
Request must be authenticated
Configure this setting according to your authentication policy
Conference name
\1
Priority
5
Pattern string
(.*)\.meet@<SIP domain>
Conference template
Select a conference template appropriate to your TelePresence
Conductor deployment. It must be a meeting-type conference.
Conductor deployment. It must be a meeting-type conference.
5. Click Create conference alias.
Configuring the endpoints using Cisco TMSPE
This part of the guide does not cover configuring Cisco TMSPE on the VCS and the Cisco TMS. It assumes
that the template schemas are already configured with enough information to create a point to point call
between two provisioned endpoints.
that the template schemas are already configured with enough information to create a point to point call
between two provisioned endpoints.
1. Log in to Cisco TMS.
2. Go to
Systems > Provisioning > Users
.
3. Click Configuration templates.
4. Click on the template you want to edit.
5. Click Edit configurations.
6. Configure the Multiway parameters for the endpoint as per the table below.
E20
SIP Profile MultiWayConference
(if using multiple SIP Profiles, this will be "SIP Profile # MultiWayConference" where #
is the profile number)
is the profile number)
EX series
NetworkServices MultiWay Address
{username}.meet@<SIP domain>
NetworkServices MultiWay Protocol
Configure as per your network, generally Auto
(the default) suffices.
(the default) suffices.
MX200
NetworkServices MultiWay Address
{username}.meet@<SIP domain>
NetworkServices MultiWay Protocol
Configure as per your network, generally Auto
(the default) suffices.
(the default) suffices.
Jabber Video
Multiway Participant URI
{username}.meet@<SIP domain>
Configuring the endpoints manually for use with
TelePresence Conductor
TelePresence Conductor
Cisco TelePresence Multiway Deployment Guide (Cisco VCS X8.1 and Conductor XC2.2)
Page 10 of 36
Cisco Multiway with TelePresence Conductor