nerdexam
Exams300-070Questions#199
Cisco

300-070 · Question #199

300-070 Question #199: Real Exam Question with Answer & Explanation

The correct answer is B: voice service voip. A '403 Forbidden' error from Cisco Unified Border Element (CUBE) during a SIP call typically indicates that the CUBE is rejecting the incoming SIP request because the source IP address is not trusted or because SIP-to-SIP call routing is not explicitly permitted. The two most com

Question

Refer to the exhibit. An engineer is working on a ticket that reports TEL1 cannot call TEL2. These dial peers are configured to route the call between the endpoints. dial-peer voice 2001voip destination-pattern 2001 session protocol sipv2 session target ipv4:10.1.1.2 incoming called-number . codec g722-64 video codec h264 dtmf-relay rtp-nte sip-notify sip-kpml no vad dial-peer voice 3001 voip destination-pattern 3001 session protocol sipv2 session target ipv4:10.3.1.2 incoming called-number . codec g722-64 video codec h264 dtmf-relay rtp-nte sip-notify sip-kpml no vad While troubleshooting, the engineer discovers that the Cisco Unified Border Element is giving the error "SIP/2.0 403 Forbidden". Which two Cisco Unified Border Element configurations resolve this issue? (Choose two.)

Options

  • Avoice service voip
  • Bvoice service voip
  • Cvoice service voip
  • Dvoice service voip
  • Evoice service voip

Explanation

A '403 Forbidden' error from Cisco Unified Border Element (CUBE) during a SIP call typically indicates that the CUBE is rejecting the incoming SIP request because the source IP address is not trusted or because SIP-to-SIP call routing is not explicitly permitted. The two most common fixes applied under the 'voice service voip' configuration context are: (1) adding 'allow-connections sip to sip' to explicitly permit SIP-to-SIP call routing through the CUBE (without this, CUBE drops inter-SIP calls by default in many IOS versions), and (2) configuring IP address trust - either by adding the peer's IP to the trusted list via 'ip address trusted list' or disabling strict source validation with 'no ip address trusted authenticate' - so that CUBE does not reject the signaling from an untrusted source. The dial-peer configurations shown (g722-64 codec, h264 video, rtp-nte DTMF) are valid and are not the source of the 403 error, so the fix must be at the global voice service voip level.

Community Discussion

No community discussion yet for this question.

Full 300-070 Practice