Which method is recommended to implement high availability when configuring the Extension Mobility phone service?

Which method is recommended to implement high availability when configuring the Extension Mobility phone service?
A. unique phone service for each Cisco Unified Communications Manager server
B. automatically handled by Cisco Unified Communications Manager
C. server load balancer virtual IP
D. DNS A record with multiple IPs listed

cisco-exams

5 thoughts on “Which method is recommended to implement high availability when configuring the Extension Mobility phone service?

  1. I agree Answer C.

    High Availability for Extension Mobility:
    From a redundancy perspective, the following component levels of redundancy must be considered for full EM resiliency:
    Cisco CallManager Cisco IP Phone Services
    High availability for the CallManager Cisco IP Phone Services is obtained by using the Services Provisioning service parameter or by using an “SLB” device pointing to multiple Unified CM nodes running the Cisco CallManager Cisco IP Phone Services. For more details, see High Availability for IP Phone Services.

    https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab10/collab10/cmapps.html

  2. From Cisco SRND:
    High availability for the Cisco Extension Mobility service is obtained by activating the Cisco Extension Mobility service on multiple Unified CM nodes.

    I think the answer is B. Cisco NEVER uses server load balancing, so it can’t be C.

  3. I agree Answer C
    Without a server load balancer, load balancing would be uneven and the redundancy would be manual.

  4. Srnd:Cisco CallManager Cisco IP Phone Services
    High availability for the CallManager Cisco IP Phone Services is obtained by using the Services Provisioning service parameter or by using an SLB device pointing to multiple Unified CM nodes running the Cisco CallManager Cisco IP Phone Services. For more details, see High Availability for IP Phone

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.