210-065 · Question #277
When placing a Multiway call through a Cisco TelePresence Conductor, which IP address on the Conductor should the call be routed to?
The correct answer is A. Rendezvous IP address. Multiway calls routed through Cisco TelePresence Conductor must target the Rendezvous IP address, which is the dedicated address for on-demand, in-call conference escalation.
Question
When placing a Multiway call through a Cisco TelePresence Conductor, which IP address on the Conductor should the call be routed to?
Options
- ARendezvous IP address
- BAd hoc IP address
- CScheduled conference IP address
- DManagement IP address
How the community answered
(21 responses)- A81% (17)
- B10% (2)
- C5% (1)
- D5% (1)
Why each option
Multiway calls routed through Cisco TelePresence Conductor must target the Rendezvous IP address, which is the dedicated address for on-demand, in-call conference escalation.
The Rendezvous IP address on the Conductor is specifically designated for Multiway conference requests, where an in-progress point-to-point call is escalated into a multipoint conference. The calling endpoint dials the Rendezvous address to trigger the Conductor to allocate a conference bridge resource dynamically. This is distinct from other IP address pools on the Conductor that serve different conference initiation methods.
The Ad hoc IP address is used for conferences initiated directly from an endpoint or MCU without a prior point-to-point call, not for Multiway escalation.
The Scheduled conference IP address is reserved for pre-booked conferences coordinated through Cisco TMS, not for spontaneous Multiway calls.
The Management IP address is used for administrative access and configuration of the Conductor appliance, not for routing media or signaling traffic.
Concept tested: Cisco TelePresence Conductor Multiway conference routing
Source: https://www.cisco.com/c/en/us/td/docs/telepresence/infrastructure/conductor/admin_guide/Cisco-TelePresence-Conductor-Administrator-Guide.html
Topics
Community Discussion
No community discussion yet for this question.