Avaya Communication Manager, Руководство администратора, Страница: 1752 / 1854

Feature Reference
Uniform Dial Plan
1752 Administrator’s Guide for Avaya Communication Manager
November 2003
Whenever UDP is used to route a call to another server or switch, the correct digit deletion and insertion
must be specified within the route pattern so that the receiving switch gets digits in the format it expects.
Avaya Communication Manager can be configured in several different ways.
•
If AAR is available on the receiving server or switch, Subnet Trunking can be used to insert the
AAR feature access code on the originating server or switch or digit insertion may be used to
insert it on the receiving server. The receiving server then uses AAR digit conversion to convert
222 with 7 digits to an extension by deleting 3 digits and inserting a 6.
•
If AAR is not available on the receiving media server, Subnet Trunking must be used on the
originating server or switch to delete the 222 and insert the digit 6 at the beginning of the
extension number so that the receiving server can continue to route correctly.
If the user at extension 51234 on Media Server C dials extension 61234, the call must first go through
Media Server A before proceeding to Mdia Server B. When 61234 is dialed, the system recognizes 61 as
a UDP code, determines the associated RNX (222), and uses AAR to route the call. The AAR feature
access code plus 222-1234 are outpulsed to Media Server A. Media Server A then recognizes the RNX
222 as a remote server/switch and routes the call to Media Server B and extension 61234. This same type
of call routing occurs when an extension at Media Server B calls an extension at Media Server C.
If extension 61234 on Media Server B calls extension 61235, Communication Manager recognizes 61 as
a local UDP code and routes the call directly to extension 61235.
Considerations
•
In North American network environments, extensions beginning with 0 may route to an attendant.
You are encouraged to use another number as the leading digit when assigning extensions.
•
When you call an extension on another server, there may be a slight delay before call-progress
tones are applied. This delay is due to the trunk signaling necessary to complete the call to the
remote server/switch.
•
When you select the option to look at the UDP table first, calls that might otherwise terminate at a
local extension route over the network. This is easily reversed. When you remove the extensions
from the UDP table, the local extension can be dialed again.
•
If AAR is active, facility restriction levels (FRLs) and Traveling Class Marks (TCMs) can be sent
along with the private network number. UDPCode and AARCode conversions use the FRL
assigned to the caller. ENPNode conversion always raises the FRL to the maximum (7).
If an FRL is insufficient to access the facility, access is denied. There is no prompt for an
authorization code even if authorization codes are enabled and administered.
•
If AAR is not active, tandem-tie trunks should not be used to transport UDP numbers. The TCM
is not recognized at the terminating server.
NOTE:
Never use tandem-tie trunks to transport UDP numbers (the TCM and Hop count will not
be recognized as such following the extension received at the receiving media server or
switch).