Cisco Cisco TelePresence Video Communication Server Expressway
Endpoint configuration (with or without TelePresence Conductor)
Cisco TelePresence Multiway Deployment Guide (Cisco VCS X7.2 and Conductor XC2.2)
Page 21 of 41
l
If you are using TelePresence Conductor, set MultiWay Address to an alias matching the pattern used
on the search rule to route Multiway aliases to TelePresence Conductor
on the search rule to route Multiway aliases to TelePresence Conductor
Cisco TelePresence System MXP Series
n
MXP must be running F8.0 or later code
n
F8.1 or later is recommended for mixed H.323 and SIP Multiway conferences
n
F8.2 or later is recommended if TLS is used to connect the MCU and VCS
You can configure Multiway through either a web browser or from the MXP itself.
To configure Multiway through a web browser:
1. Enter the IP address of the MXP into the web browser.
2. Go to
Endpoint configuration > General
.
3. Scroll to the bottom of page (MultiPoint Call Options).
4. Set Multi point to Multiway.
5. Configure the MultiWay URI setting:
l
If you are not using TelePresence Conductor, set MultiWay URI to the Conference Factory Alias as
set up on the VCS.
set up on the VCS.
l
If you are using TelePresence Conductor, set MultiWay URI to an alias matching the pattern used on
the search rule to route Multiway aliases to TelePresence Conductor
the search rule to route Multiway aliases to TelePresence Conductor
6. Go to
Control panel (spanner) > General > Multipoint call options
.
7. Set Multi point to Multiway.
8. Set Multiway URI to the Conference Factory Alias as set up on the VCS.
Note that:
n
If Multiway URI is configured with “sip:” at the start, e.g. sip:multiway@domain then the MXP will request
the Multiway conference call using SIP.
If there is no “sip:” at the start of the Multiway URI, e.g. multiway@domain then the MXP will request the
Multiway conference call using H.323. (For clarity if you want to force the Multiway conference call request
to use H.323, an “h323:” can be put at the start of the Multiway URI.)
the Multiway conference call using SIP.
If there is no “sip:” at the start of the Multiway URI, e.g. multiway@domain then the MXP will request the
Multiway conference call using H.323. (For clarity if you want to force the Multiway conference call request
to use H.323, an “h323:” can be put at the start of the Multiway URI.)
n
The Multiway URI must be in the format [sip:|h323:]name@domain, e.g. multiway@domain or
h323:multiway@domain for H.323 or sip:multiway@domain for SIP.
h323:multiway@domain for H.323 or sip:multiway@domain for SIP.
Two additional advanced parameters are available on the command line interface:
n
xconfiguration Multipoint MultiwayMultiprotocol: On|Off
l
On allows the “Merge” button when one call is H.323 and the other is SIP
l
Off only allows the “Merge” button if both calls are the same protocol
n
xconfiguration Multipoint MultiwayStartupPeriod: 0..21
Defines the delay before audio and video is enabled after connecting to the MCU. By using a small number
it reduces messages/sounds occurring as all 3 participants join the conference.
Defines the delay before audio and video is enabled after connecting to the MCU. By using a small number
it reduces messages/sounds occurring as all 3 participants join the conference.
If MXP F8.1 code and SIP calling is used, either the connection from the MXP to the MCU must support
secure connection, or the MXP must have Security > Encryption set to Off. If set to On or Auto, the MXP
will demand a secure connection from the MCU. If any link between the MXP and MCU is TCP (rather than
TLS) security cannot be supported and the Multiway join will fail for this party.
secure connection, or the MXP must have Security > Encryption set to Off. If set to On or Auto, the MXP
will demand a secure connection from the MCU. If any link between the MXP and MCU is TCP (rather than
TLS) security cannot be supported and the Multiway join will fail for this party.