210-065 · Question #219
Refer to the exhibit. You must dial the interactive response system of the multipoint control unit. What are the appropriate dual-tone multi-frequency digits to create an ad-hoc conference with an…
The correct answer is D. 5919*2345#. To dial an MCU IVR and create an ad-hoc conference, the full DTMF string must include the MCU access number, an asterisk separator, the conference ID, and a terminating pound sign.
Question
Refer to the exhibit. You must dial the interactive response system of the multipoint control unit. What are the appropriate dual-tone multi-frequency digits to create an ad-hoc conference with an identifier of 2345?
Options
- A2345
- B2345#
- C5919*2345
- D5919*2345#
How the community answered
(31 responses)- A10% (3)
- B3% (1)
- C3% (1)
- D84% (26)
Why each option
To dial an MCU IVR and create an ad-hoc conference, the full DTMF string must include the MCU access number, an asterisk separator, the conference ID, and a terminating pound sign.
Entering only 2345 provides just the conference ID with no MCU access number or terminating character, so the IVR cannot resolve which MCU to contact or confirm the entry.
2345# supplies the conference ID with a terminator but omits the MCU access number and asterisk separator needed to address the IVR system.
5919*2345 includes the MCU number, asterisk, and conference ID but lacks the terminating # that the IVR requires to confirm and initiate conference creation.
The string 5919*2345# follows the standard MCU IVR input format where 5919 is the MCU dial-in access number, the asterisk separates the access number from the conference identifier, 2345 is the ad-hoc conference ID, and the trailing # signals end-of-input so the IVR processes and creates the conference. Omitting any element leaves the IVR unable to parse and route the request correctly.
Concept tested: MCU IVR DTMF ad-hoc conference dialing sequence
Topics
Community Discussion
No community discussion yet for this question.