Cisco Cisco TelePresence Video Communication Server Expressway
Endpoint requirements
(those that can be joined to a Multiway™ conference)
Endpoint requirements
(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.
Message.
Endpoints supporting this include:
Cisco TelePresence MXP (version F8.0 or later)
TANDBERG MXP (version L6.0 or later)
TANDBERG Classic endpoints (must have encryption disabled)
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:
Cisco IP Video Phone E20 (version TE 1.0 or later)
Cisco TelePresence MXP (version F8.0 or later)
Cisco TelePresence Movi (version 3.1 or later)
most SIP endpoints (all that support REFER)
Other devices (IP PBXs, gateways etc …)
H.323 devices need to support the routeToMC Facility Message
SIP devices need to support the SIP REFER message
the alias created by the conference factory must be an alias that is routable by the device
Note: The alias created by the Conference Factory (from the template) will be in URI form
(name@domain), it cannot be in E164 format – devices only supporting E164 routing will not be able
to be joined into a Multiway™ conference.
(name@domain), it cannot be in E164 format – devices only supporting E164 routing will not be able
to be joined into a Multiway™ conference.
Cisco VCS Deployment Guide: Multiway™ (Cisco VCS X5)
Page 16 of 25