Certkiller has four locations total, all connected via an IP WAN. Each location has a Cisco Unified CallManager cluster, and the headquarters cluster is connected to all other clusters via intercluster trunks. ABC wants to allow up to eight simultaneous calls across the IP WAN. To call between sites, an employee dials a 2-digit access code plus a 4-digit extension. If more than eight calls are made, or if the IP WAN is not available, calls should be sent to Certkiller’s preferred long-distance carrier. If the trunk to the long-distance carrier is not available, the local provider should be used. The long-distance carrier requires 10 digits to complete a long-distance call. The local provider requires 11 digits to complete a long-distance call but only 7 digits for local
calls.What is the minimum number of route lists required at the headquarters location?
A.
4
B.
6
C.
5
D.
1
E.
2
F.
3
Explanation:
With route lists, you can implement features, such as toll bypass and PSTN fallback, because within the route list you can prioritize route groups that contain different types of gateways, such as IP WAN, PSTN, and so on. For this scenario, you will need a RL for the IP WAN dialing, RL for local 7 digit dialing to the PSTN, and another RL for the long distance dialing (IXC).
I dont think above explanation is correct. You can have diff digit manipulations for different RGs. So one RL should suffice. To me the reason of three RLs is that HQ is connected to three remote sites each having a diff side code, so separate Route Patterns would be setup for each location. Now these RPs need to point to an RL which points to the repsective Intercluster trunk for that site specifically.
So from HQ there will be three trunks going out each being used as the first option of the RL to that location ..
ISN’t IT?