Refer to the exhibit. An engineer configures Cisco Unified Border Element to connect the enterprise VoIP network with a SIP telephony provider. Calls are not working in either direction. What must be

The correct answer is C. session-protocol sipv2. When configuring a VoIP dial peer on a CUBE for SIP connectivity, the command 'session protocol sipv2' must be explicitly added. Without it, the dial peer defaults to H.323, causing SIP calls to fail in both directions because the signaling protocol does not match the provider's

Session Border Controller and Voice Gateway Technologies

Question

Refer to the exhibit. An engineer configures Cisco Unified Border Element to connect the enterprise VoIP network with a SIP telephony provider. Calls are not working in either direction. What must be configured in the dial peer 1 to fix the issue?

Options

Aanswer-address 555 "".
Bcodec g729
Csession-protocol sipv2
Dincoming called number 555"".

How the community answered

(37 responses)

B
3% (1)
C
95% (35)
D
3% (1)

Explanation

When configuring a VoIP dial peer on a CUBE for SIP connectivity, the command 'session protocol sipv2' must be explicitly added. Without it, the dial peer defaults to H.323, causing SIP calls to fail in both directions because the signaling protocol does not match the provider's SIP trunk. Option A ('answer-address') is used on POTS dial peers to match incoming caller ID and is not relevant here. Option B (codec g729) would affect media negotiation but would not cause a complete bidirectional failure. Option D ('incoming called-number') helps match inbound calls but does not fix the protocol mismatch causing total call failure.

Topics

#Cisco Unified Border Element (CUBE)#SIP Dial Peer#Voice Gateway Configuration#SIP Signaling

Community Discussion

No community discussion yet for this question.

Full 300-815 Practice