Question

A CUCM administrator configures globalized call routing but notices that when an internal user dials a directory URI (user@company.com) from a Jabber client, the call fails while dialing the same user's DN succeeds. SIP route patterns for other external domains work correctly. What is the MOST likely cause of the directory URI call failure?

Accepted Answer

The directory URI is not associated with a partition that is included in the calling device's calling search space

Answer

The company.com domain is missing a matching SIP route pattern pointing to the local cluster

Answer

The cluster-wide 'Organization Top Level Domain' enterprise parameter is left blank

Answer

Jabber must use +E.164 dialing exclusively and cannot resolve alphanumeric URIs