Cisco Cisco TelePresence Video Communication Server Expressway
available
n
MXP F8.2 and later can have encryption either set to Off or Auto
TANDBERG MXP – L Series
L Series currently do not support initiating Multiway calls.
Endpoint requirements
(those that can be joined to a Multiway conference)
(those that can be joined to a Multiway conference)
H.323
H.323 endpoints that can be joined into a Multiway call must support the H.323 routeToMC Facility Message.
Endpoints supporting this include:
n
Cisco TelePresence System MXP (version F8.0 or later)
n
Cisco TelePresence System EX Series (version TC4.2 or later)
n
Cisco TelePresence System C Series (version TC4.0 or later)
n
TANDBERG 150 MXP (version L6.0 or later)
n
TANDBERG Classic endpoints (must have encryption disabled)
n
Sony PCS G50 and Sony PCS TL30
SIP
SIP endpoints that can be joined into a Multiway call must support the SIP REFER message.
Endpoints supporting this include:
n
Cisco IP Video Phone E20 (version TE1.0 or later)
n
Cisco TelePresence System MXP (version F8.0 or later)
n
Cisco Jabber Video for TelePresence (version 3.1 or later)
n
Cisco TelePresence System EX Series (version TC4.2 or later)
n
Cisco TelePresence System C Series (version TC4.0 or later)
n
most SIP endpoints (all that support REFER)
Other devices (IP PBXs, gateways and so on)
n
H.323 devices need to support the routeToMC Facility Message
n
SIP devices need to support the SIP REFER message
n
the alias created by the Conference Factory must be an alias that is routable by the device
Note that the alias created by the Conference Factory (from the template) is in URI form (name@domain).
The alias cannot be in E.164 format – devices that only support E.164 routing cannot be joined into a
Multiway conference.
The alias cannot be in E.164 format – devices that only support E.164 routing cannot be joined into a
Multiway conference.
Cisco TelePresence Multiway™ Deployment Guide (X8.2, XC2.4)
Page 23 of 42
Endpoint configuration (with or without TelePresence Conductor)