When the services key is pressed Cisco Extension Mobility does not show up. What is the cause of the issue?

• A.The URL configured for Cisco Extension Mobility is not correct.
• B.Cisco Extension Mobility Service is not running.
• C.The phone is not subscribed to Cisco Extension Mobility Service.
• D.Cisco Extension Mobility is not enabled in the Phone Configuration Window (Device > Phone)

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

Users report that outbound PSTN calls from phones registered to Cisco Unified Communications Manager are not completing. The local service provider in North America has a requirement to receive calls in 10-digit format. The Cisco Unified CM sends the calls to the Cisco Unified Border Element router in a globalized
E.164 format. There is an outbound dial peer on Cisco Unified Border Element configured to send the calls to the provider. The dial peer has a voice translation profile applied in the correct direction but an incorrect voice translation rule applied, which is shown in the exhibit. Which rule modified DNIS in the format that the provider is expecting?

• A.rule 1/^\+1\([2-9]..[2-9]......$\)/ /\1/
• B.rule 1 /^/+\([^1].*\)/ /011\1/
• C.rule 1 /^\+1\([2-9]..[2-9]......$\)/ /\0/
• D.rule 1 /^\([2-9]..[2-9]......$\)/ /\1/

Comment: *

Name: *

Email: *

Verification: *

You see the voice register pool 1 command in your Cisco Unified Communications Manager Express configuration. Which configuration is occurring in this section?

• A.configuration for a pool of SIP phones (similar to device pool on Cisco Unified Communications Manager)
• B.configuration for a single SIP phone
• C.configuration items common for all SIP phones
• D.configuration for SIP registrar service

Comment: *

Name: *

Email: *

Verification: *

What is first preference condition matched in a SIP-enabled incoming dial peer?

• A.incoming uri
• B.target carrier-id
• C.answer-address
• D.incoming called-number

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

An administrator has configured a SIP trunk between two Cisco UCM clusters. For calls that should use the trunk, the calls fail with a fast busy. The administrator checks the Cisco CallManager SDL traces and found that the cluster to which the calling device is registered never sends an INVITE to the destination cluster. The administrator also verifies that all nodes from both clusters are powered on, and the CallManager service is running. How is this issue resolved?

• A.The administrator must allow connectivity so that TCP connections do not fail between the nodes.
• B.The administrator must associate the route pattern with a calling search space the device can dial.
• C.The administrator needs to disable OPTIONS pings on the SIP trunks for both clusters.
• D.The administrator needs to enable OPTIONS pings on the SIP trunks for both clusters.

Comment: *

Name: *

Email: *

Verification: *