300-085 · Question #198
Which definition of Caller Input on Cisco Unity Connection is true?
The correct answer is A. It defines actions that Cisco Unity Connection takes in response to phone keys that are pressed. Caller Input in Cisco Unity Connection defines the actions taken when a caller presses a key (DTMF tone) during playback of a call handler greeting.
Question
Which definition of Caller Input on Cisco Unity Connection is true?
Options
- AIt defines actions that Cisco Unity Connection takes in response to phone keys that are pressed
- BIt defines actions that Cisco Unity Connection takes in response to a preconfigured call handler.
- CTransfers all incoming calls to the Opening Greeting call handler.
- DPlays a brief goodbye message and then hangs up.
How the community answered
(30 responses)- A90% (27)
- C3% (1)
- D7% (2)
Why each option
Caller Input in Cisco Unity Connection defines the actions taken when a caller presses a key (DTMF tone) during playback of a call handler greeting.
Caller Input is a per-call-handler configuration that maps individual phone keypad inputs (0-9, *, #) to specific actions such as transfers, skipping to the next greeting, or taking a message, responding dynamically to caller DTMF signals during greeting playback.
Caller Input responds to live keypad presses from callers, not to a preconfigured call handler trigger; call handler routing is a separate concept from Caller Input mappings.
Transferring all incoming calls to the Opening Greeting call handler describes the default call routing behavior, not the definition of Caller Input.
Playing a goodbye message and hanging up describes the 'Say Goodbye' system call handler action, which is a separate feature unrelated to Caller Input configuration.
Concept tested: Unity Connection Caller Input DTMF action mapping
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/14/administration/guide/b_14cucsag/b_14cucsag_chapter_0100.html
Topics
Community Discussion
No community discussion yet for this question.