300-815 · Question #37
Where is the dtmf-relay command configured on Cisco Unified Border Element?
The correct answer is D. in the VoIP or POTS dial peers. dtmf-relay is a dial-peer level command, and it applies to both VoIP and POTS dial peers on CUBE - making D the most complete answer. On the inbound side a POTS dial peer may handle the call leg, and on the outbound side a VoIP dial peer carries it; DTMF relay can be tuned on eit
Question
Options
- Ain the voice-class VoIP configuration
- Bin the VoIP dial peer
- Cin global SIP configuration
- Din the VoIP or POTS dial peers
How the community answered
(21 responses)- A5% (1)
- B10% (2)
- C5% (1)
- D81% (17)
Explanation
dtmf-relay is a dial-peer level command, and it applies to both VoIP and POTS dial peers on CUBE - making D the most complete answer. On the inbound side a POTS dial peer may handle the call leg, and on the outbound side a VoIP dial peer carries it; DTMF relay can be tuned on either leg depending on where tone translation or signaling conversion is needed.
Why the distractors are wrong:
- A (voice-class VoIP): This is a reusable template that gets applied to dial peers, but
dtmf-relayitself is not a valid command inside a voice-class VoIP stanza. - B (VoIP dial peer only): Partially true but incomplete - limiting it to VoIP peers misses the POTS peer scenario, which is a common exam trap.
- C (global SIP configuration): Global SIP (
sip-uaorvoice service voip > sip) handles things like registrar, timers, and codec options - not per-call DTMF relay behavior.
Memory tip: Think "DTMF is a dial-peer decision" - you're deciding per-peer how tones travel (RFC 2833/RTP-NTE, SIP-INFO, inband, etc.), so the command always lives on a dial peer, not globally. If you see a distractor that names only one peer type, remember CUBE bridges two legs and either leg might need it.
Topics
Community Discussion
No community discussion yet for this question.