Cisco Cisco TelePresence Video Communication Server Expressway
Multiway Conference
Initiator Party 2 Party 3 VCS MCU
Initiator Party 2 Party 3 VCS MCU
Bye (2)
Refer Party 3 to conf
Refer Party 3 to conf
Accepted
Accepted
INVITE (<alias
defined by
Conference Factory
template>)
INVITE (<alias
defined by
Conference Factory
template>)
OK
OK
Notify
Notify
Bye (3)
Bye (3)
All 3 parties in an MCU hosted conference call
H.323
H.323 works in a similar manner, using routeCallToMC H.225 ‘Facility’ messages to indicate which
conference ID to dial:
conference ID to dial:
n
VCS interworks H.323 calls to Conference Factory into SIP, so the Conference Factory always sees an
INVITE when “Merge” is pressed, and responds with the 302 temporarily moved. VCS interworking
converts the 302 into a routeCallToMC facility message.
INVITE when “Merge” is pressed, and responds with the 302 temporarily moved. VCS interworking
converts the 302 into a routeCallToMC facility message.
n
The initiating H.323 endpoint then sends routeCallToMC facility messages to the endpoints that are to join
the Multiway conference.
the Multiway conference.
Cisco TelePresence Multiway™ Deployment Guide (X8.2, XC2.3)
Page 31 of 36
Appendix 3: Call flows for Multiway without TelePresence Conductor