Which dial plan characteristic is most obviously improved by dropping a number translation step?
A.
Availability
B.
Post-dial delay
C.
Scalability
D.
Hierarchical design
Explanation:
Introduction This document provides a sample configuration for creating scalable dial plans for aVoIPnetwork using IOS translation rules.As you install integrated voice and data networks, one issue frequently encountered is how to manage the numbering plans of theindialranges at different locations. Depending on the type of exchange, signaling protocol standards and even location, the service provider could pass similar number ranges to the subscriber equipment at each remote site. If these calls are being routed back to a central site, there could be an overlap in the called numbers that originate from each of the remote sites. Since the PBX makes the routing decision based on unique called numbers, this could cause problems with automatic call distribution (ACD) queues on private branch exchange (PBX) systems . For example, calls from each site may need to be directed to particular operators who speak the local language from where the call originated. If the called numbers from each site overlap, there is not any way of identifying the origin of a call, therefore the PBX is not able to route the call to the correct ACD queue.
Some remote sites may be provided with a 2-digitindialnumber range while other sites may have 3- or 4-digit indialranges, so the called numbers could be from [00 – 99] to [0000 – 9999]. With these number ranges, the main site router would need configurations to handle 2-, 3- and 4-digit numbering plans. This could add to the overall complexity of the router configuration.
The solution to these issues is to use IOS digit translation rules at each remote site toprependdigits to the number range that comes in from the telephone network. This then creates a standard numbering plan across the customer’s network and allows new sites to be gradually added without major changes to the rest of the network.