Refer to the exhibit. An engineer is troubleshooting a call-establishment problem between Cisco Unified Border Element and Cisco UCM. Which command set corrects the issue?

Question

Exhibit

Options

• Avoice service voip sip bind media source-interface GigabitEthernet0/0/0 bind sip in sip configuration mode: voice service voip sip
• Bsip bind control source-interface GigabitEthernet0/0/1 bind media source-interface GigabitEthernet0/0/1 sip bind in dial-peer configuration mode: dial-peer voice 300 voip voice-class sip bind control source-interface GigabitEthernet0/0/1 voice-class sip bind media source-interface GigabitEthernet0/0/1
• Csip bind control source-interface GigabitEthernet0/0/1 bind media source-interface GigabitEthernet0/0/1
• Dsip bind in dial-peer configuration mode: dial-peer voice 300 voip voice-class sip bind control source-interface GigabitEthernet0/0/0 voice-class sip bind media source-interface GigabitEthernet0/0/0

• A
  5% (1)
• B
  5% (1)
• C
  15% (3)
• D
  75% (15)

Explanation

In a Cisco Unified Border Element (CUBE) scenario with multiple interfaces, SIP signaling (control) and media (RTP) must be bound to the correct interface for calls to establish properly toward each peer. The exhibit (not shown here) would indicate that calls toward Cisco UCM should use GigabitEthernet0/0/0. The correct approach per Option D is to configure SIP binding at the dial-peer level using 'voice-class sip bind control source-interface GigabitEthernet0/0/0' and 'voice-class sip bind media source-interface GigabitEthernet0/0/0' under the specific dial peer facing UCM (dial-peer voice 300 voip). Dial-peer level binding is more granular and overrides global binding, ensuring that only calls matching that dial peer use the specified interface, preventing source IP mismatches that would cause call setup failures.

No community discussion yet for this question.