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

Feature Reference
Uniform Dial Plan
1750 Administrator’s Guide for Avaya Communication Manager
November 2003
UDP conversion is specified for individual extensions or groups of extensions sharing the same leading
digits, via the UDP screen and the matching pattern. A matching pattern is the desired leading digits of an
extension. For example, with a 5-digit UDP “123” is the matching pattern for all 100 possible 5-digit
extensions beginning with “123”. By contrast, “12345” would be a matching pattern specifying a single
extension.
Each extension code can be assigned to 1 of 6 possible treatments.
•
UDPCode — Conversion to AAR with given location code, further conversion suppressed
•
AARCode — Conversion to AAR with given location code, further conversion allowed
•
ENPCode — Conversion to private network number (via ENP screen), route to given node
number routing
•
TempOOS — Temporarily out of service, give reorder
•
Local — Local range of extensions
•
blank — Similar to local; however, this extension is not chosen when the system is asked to “add
a station”
When a user on an included server in a UDP dials an extension, Communication Manager first checks to
see if the extension is assigned to a local station on that server. If so, the call is routed to the station, and
UDP is not invoked. If the extension is not found locally, the system checks to see if the extension
matches an assigned extension code. If the extension matches an assigned extension code, the system
performs the specified conversion into a private network number and routes the call as specified. If more
than one extension code matches, the “best” match (most explicit digits) is used. For example, 1234 is
chosen over 123 if 12345 is dialed. However, 123 is chosen if 12355 is dialed. If no matching extension
code is found, the user receives intercept treatment. Or, if Extended Trunk Access (ETA) is enabled, the
call routes via ETA.
Example of how UDP works
To administer, assign each UDP code:
•
To a private network location code (RNX) or node number. (The RNX is equivalent to an office
code of a central office in a public network. This RNX determines how a UDP call is routed.)
•
Assign each UDP code as either local or remote to Communication Manager.
To understand the function of a UDP, review the following example.
A given station is called using the same 5-digit extension regardless of where in the ETN the call
originates. Three media servers or switches are included in the example. Each has been assigned a list of
RNX and UDP codes. See
Figure 401, UDP Example, on page 1751.
M.SERVER RNX UDP CODE
A 224 41
C 223 51
C 223 52
B 222 60
B 222 61