210-060 · Question #392
Company A merged with company B. An engineer is asked to register some IP phones from company B to Cisco Unified Communications Manager of company A. The engineer correctly added the devices in…
The correct answer is B. Configure H.323. When IP phones from a merged company fail to register despite correct device and network configuration, the phones may be using H.323 signaling which must be explicitly enabled on the target Cisco Unified Communications Manager.
Question
Company A merged with company B. An engineer is asked to register some IP phones from company B to Cisco Unified Communications Manager of company A. The engineer correctly added the devices in Cisco Unified CM and the network parameters for the IP phone are correct, but the IP phone is not registering. Which action resolves this issue?
Options
- AErase CTL configuration.
- BConfigure H.323.
- CChange the device template.
- DEnable SIP Proxy.
How the community answered
(51 responses)- A14% (7)
- B59% (30)
- C22% (11)
- D6% (3)
Why each option
When IP phones from a merged company fail to register despite correct device and network configuration, the phones may be using H.323 signaling which must be explicitly enabled on the target Cisco Unified Communications Manager.
Erasing the CTL addresses phone security token trust issues with secured CUCM clusters or SRST, but does not resolve a signaling protocol mismatch preventing initial registration.
If Company B's IP phones use H.323 as their signaling protocol rather than SCCP or SIP, they cannot register with CUCM until H.323 support is configured. Adding H.323 gateway support in CUCM provides the necessary protocol infrastructure for those phones to complete registration. Protocol mismatches are a common cause of registration failure during UC infrastructure mergers.
Changing the device template affects default configuration values pushed to phones but cannot resolve a fundamental inability to register caused by an unsupported signaling protocol.
Enabling a SIP Proxy assists SIP-based devices and does not address H.323 phones, so it would not resolve registration failure for non-SIP endpoints.
Concept tested: H.323 protocol configuration for cross-company CUCM phone registration
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_01000111.html
Topics
Community Discussion
No community discussion yet for this question.