300-070 · Question #405
You are a Voice Engineer working at ABC Company. You are asked to configure Cisco Unified Border Element in Cisco Unified Communications Manager. Which configuration is required?
The correct answer is A. Change the SIP trunk security profile to a nonsecure SIP trunk profile. Integrating CUBE with CUCM via SIP trunk requires setting the SIP Trunk Security Profile to non-secure so CUCM communicates with CUBE using standard SIP on port 5060.
Question
You are a Voice Engineer working at ABC Company. You are asked to configure Cisco Unified Border Element in Cisco Unified Communications Manager. Which configuration is required?
Options
- AChange the SIP trunk security profile to a nonsecure SIP trunk profile.
- BUnder the SIP information configuration, set the destination port to 5061.
- CBind the SIP signaling to the Cisco Unified Border Element interface.
- DConfigure dial peers on Cisco Unified Border Element for inbound and outbound calls
How the community answered
(22 responses)- A68% (15)
- B18% (4)
- C9% (2)
- D5% (1)
Why each option
Integrating CUBE with CUCM via SIP trunk requires setting the SIP Trunk Security Profile to non-secure so CUCM communicates with CUBE using standard SIP on port 5060.
CUCM's default SIP trunk security profile enforces TLS on port 5061, which is not required for standard CUBE integration. Changing to a non-secure SIP trunk security profile allows CUCM to communicate with CUBE over standard SIP (UDP/TCP port 5060), which is the baseline configuration needed for CUBE to register and process calls with CUCM.
Port 5061 is reserved for SIP over TLS; manually setting the destination port to 5061 configures secure transport, which contradicts the non-secure profile requirement and would cause a mismatch with a standard CUBE SIP listener.
Binding SIP signaling to a specific interface is performed on the CUBE router itself using the IOS 'bind' command under the voice service voip configuration, not within the CUCM administration GUI.
Dial peers for inbound and outbound call routing are configured directly on the CUBE router using 'dial-peer voice' commands, not through any setting inside CUCM.
Concept tested: CUCM SIP trunk security profile for CUBE
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/12_5_1/systemConfig/cucm_b_system-configuration-guide-1251/cucm_b_system-configuration-guide-1251_chapter_01001101.html
Topics
Community Discussion
No community discussion yet for this question.