Refer to the exhibit.
When a Cisco IP Communicator phone roams from San Jose (SJ) to RTP, the Cisco IP
Communicator physical location and the device mobility group change from SJ to RTP All route
patterns are assigned a route list that points to the local route group All device pools are
configured to use the local route group Which statement is true when the roaming phone places
an AAR call?
A.
Since globalized call routing is not configured, then the SJ gateway will be used in this case
B.
The phone will use the AAR CSS that contains the SJ_PSTN partition. The call will egress at
the SJ gateway
C.
The phone will use the AAR CSS that contains the RTP_PSTN partition. The call will egress at
the SJ gateway
D.
The phone will use the AAR CSS that contains the SJ_PSTN partition. The call will egress at
the RTP gateway.
E.
The phone will use the AAR CSS that contains the RTP_PSTN partition The call will egress at
the RTP gateway
Explanation:
Cisco Unified Communications Manager Version 7.0 introduced the Local Route Group
feature.When using local route groups, gateway selection is totally independent of the matched
route pattern and referenced route list and routegroup. The use of the Local Route Group feature
makes no changes regarding roaming-sensitive settings. The application of these settings always
makes sense when roaming between sites. The settings have no influence to the gateway
selection and the dial rules that a user must follow. However, the dial planrelated part of Device
Mobility changes substantially withthe new dial plan concept, This concept allows a roaming user
to follow the home dial rules for external calls but use the local gateway of the roaming site In this
case, When the device mobility group is not the same for San Jose and RTP, the Device Mobility
related settings are not applied. The phone device keeps its San Jose-specific configuration
Despite the San Jose-specific configuration on the phone, the PSTN calls that originate from the
roaming phone are routed via the local PSTN gateway (RTP GW) and are based on the route list
and device pool local route group settings.
The San Jose-specific dial plan is used. Also, AAR
remains configured with the San Jose-specific configuration, but if the San Jose dial plan and San
Jose AAR CSS permit and if the AAR group contains the prefix that can be applied in RTP, then
AAR can work