300-085 · Question #221
You configure a Cisco Unity Express module to integrate with Cisco Unified Communications Manager Express. You can use the following command to connect to the module from the Cisco Unified…
The correct answer is C. Add an IP address to the ISM interface in the same subnet as Cisco Unified Communications. IP connectivity between CME and the CUE module requires the ISM interface on CME to have an IP address in the same subnet as the module; without this, pings and web access fail even though the internal backplane session still works.
Question
You configure a Cisco Unity Express module to integrate with Cisco Unified Communications Manager Express. You can use the following command to connect to the module from the Cisco Unified Communications Manager Express CLI:
ABC_CORP#service-module integrated-Service-Engine 0/0 session Trying 10.1.10.2, 2002 … Open se-10-1-10-1# However, you cannot pint the module from Cisco Unified Communications Manager Express and cannot use a web browser to connect the module. You see this message:
ABC_CORP#ping 10.1.10.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.1.10.1, timeout is 2 seconds:
Success rate is 0 percent (0/5) How can you fix this problem?
Options
- AEnable ICMP and web services on the Cisco Unity Express module.
- BEnable the ISM interface on Cisco Unified Communications Manager Express
- CAdd an IP address to the ISM interface in the same subnet as Cisco Unified Communications
- DAdd a host route from Cisco Unified Communications Manager Express to Cisco Unity Express
How the community answered
(23 responses)- A4% (1)
- B4% (1)
- C78% (18)
- D13% (3)
Why each option
IP connectivity between CME and the CUE module requires the ISM interface on CME to have an IP address in the same subnet as the module; without this, pings and web access fail even though the internal backplane session still works.
ICMP and web services are enabled on CUE by default; the connectivity failure is caused by the missing IP address on the CME-side ISM interface, not by any service or firewall setting on the module itself.
Simply enabling the ISM interface without assigning it an IP address in the same subnet as the CUE module still provides no routed IP path, so pings and web access would continue to fail.
The ISM interface on the CME router serves as the IP-layer gateway to the CUE module. Without an IP address on that interface in the same subnet as the module's IP, no routed path exists between CME and CUE. The service-module session command uses an internal backplane connection that is independent of IP routing, which is why it succeeds while ICMP ping and HTTPS browser access both fail.
A static host route on CME cannot forward packets to the CUE module when the ISM interface has no IP address, because there is no valid local interface to use as the outbound path.
Concept tested: CUE ISM interface IP addressing for CME integration
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/unity_exp/rel8_6/config/guide/ise/cue86ise.html
Topics
Community Discussion
No community discussion yet for this question.