Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Instructions Manual

							Distributed Communications System 
351
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
UDP conversion is specified for individual extensions or groups of extensions sharing 
the same leading digits, via the UDP form and extension codes. An extension code is 
the desired leading digits of an extension followed by an “x” (wildcard). For example, 
“123xx” “12345”is the extension code for all 100 possible extensions beginning with 
“123” plus two wild cards. “12345” is an extension code specifying one 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 form), 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 at a switch that is included in a UDP dials an extension, DEFINITY ECS 
first checks to see if the extension is assigned to a local station on that switch. 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, 1234x is chosen over 123xx if 12345 is dialed. However, 123xx 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 
worksTo 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 the switch.
To understand the function of a UDP, review the following example. 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
352
A given station is called using the same 5-digit extension regardless of where in the 
ETN the call originates. Three switches are included in the example. Each has been 
assigned a list of RNX and UDP codes. See Figure 7.
Figure 7. UDP Example
SWITCH RNX UDP CODE
A 224 41
C 223 51
C 223 52
B 222 60
B 222 61
3
45
12
7
6
8r764905 CJL 062296
1. Switch A
Dial Plan for extensions is 
41XXX 
RNX=224
2. Switch B:
Dial Plan for Extensions is 
60XXX  and 61XXX RNX=222
3. Switch C:
Dial Plan for extensions is 
51XXX  and 52XXX RNX=2234. Extension 41000
5. Extension 61234
6. Extension 60123
7. Extension 51234
8. Extension 5200 
						

							Distributed Communications System 
353
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
If a user at extension 41000 wants to call extension 61234, there are two choices: 
•Dial 61234
•Dial the AAR access code followed by 222-1234
If 61234 is dialed, the system recognizes 61 as a remote UDP, determines the 
associated RNX (222), and uses AAR to route the call to 222-1234.
If the AAR access code and 222-1234 are dialed, the system finds the route pattern 
for RNX 222 and routes the call to the switch associated with that RNX.
Whenever UDP is used to route a call to another 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. DEFINITY ECS can be configured in several different 
ways.
•If AAR is available on the receiving switch, Subnet Trunking can be used to insert 
the AAR feature access code on the originating switch or digit insertion may be 
used to insert it on the receiving switch. The receiving switch 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 switch, Subnet Trunking must be used on 
the originating switch to delete the 222 and insert the digit 6 at the beginning of 
the extension number so that the receiving switch can continue to route correctly.
If the user at extension 51234 on Switch C dials extension 61234, the call must first 
go through Switch A before proceeding to Switch 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 
Switch A. Switch A then recognizes the RNX 222 as a remote switch and routes the 
call to Switch B and extension 61234. This same type of call routing occurs when an 
extension at Switch B calls an extension at Switch C.
If extension 61234 on Switch B calls extension 61235, the system 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 switch, 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 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. 
						

							Distributed Communications System B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
354
•If AAR is active, 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 switch.
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 switch).
Interactions •Automatic Alternate Routing
AAR routes UDP calls. (Included with UDP is the required AAR subset.) If AAR 
is enabled in addition to UDP, then the 7-digit AAR number provides the same 
routing as UDP.
•Dial Plan
~All of the extension numbers on a switch are not necessarily part of UDP. Any 
that do not belong to UDP are handled by a regular, non-UDP Dial Plan 
associated with the switch.
~When administering the Dial Plan form and designating a group of extensions 
as UDP non-local, you can specify whether you want to search for local 
extensions first or last. This allows flexibility to change extensions from local 
to non-local and vice-versa.
•DID Trunk Group
DID calls to 5-digit UDP extension numbers require that the DID trunk group 
insert enough digits to make a 5-digit extension number.
•Distributed Communications System
UDP is required when DCS is provided. The necessary UDP software is provided 
with the DCS software.
•Extension Number Portability
If an extension code is administered to use ENP node routing, ENP routes the call 
to the correct switch. If AAR is enabled in addition to UDP, the 7-digit AAR 
number provides the same routing as UDP (that is, via ENP). 
						

							ISDN Feature Plus 
355
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
ISDN Feature Plus
This feature allows you to have basic feature transparency over public networks 
without having a dedicated leased line. This provides a lower cost option for using the 
switched public network.
How to administer ISDN Feature Plus
Note:Only Lucent representatives perform step 1.
1  On the System-Parameters Customer-Options form, set the:
~ G3 Version field to V8.
~ISDN Feature Plus field to y.
2  On the same form, set either or both of the following:
~ISDN-PRI field to y, or
~ISDN-BRI Trunks field to y.
3  Set either or both of the following:
~ISDN-BRI Trunk Group — Set the Supplementary Service Protocol 
field to f
~ISDN-PRI Trunk Group — Set the Supplementary Service Protocol 
field to f.
4  On the Feature Related System Parameters form, set the Feature Plus Ext field 
to the local extension used to terminate Feature Plus signaling for ISDN Feature 
Plus.
5  On the Hunt Group form, to add a centralized AUDIX, set the Message Center 
field to fp-mwi.
To start administration for Message Waiting Indication at the Message Center PBX:
1  On the Feature Related System Parameters form, set the MWI - Number of 
Digits per AUDIX Subscriber field to the desired number. 
2  On the Processor Channel Assignment, set the Application field to fp-mwi. 
3  Administer the Message Waiting Indication Subscriber Number Prefixes form. To 
start the Calling Name feature:
4  On the ISDN-BRI or ISDN-PRI trunk group form (whichever you are using), set 
the Send Name field to y. 
						

							ISDN Feature Plus B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
356
Description
ISDN Feature Plus uses a DEFINITY ECS proprietary signaling protocol. The 
features do not function in the same way as their QSIG or DCS counterparts.
To use Feature Plus, Phase I, you need DID extensions. In addition to the general 
Feature Plus call handling, Feature Plus includes the following features:
•Centralized AUDIX — A simple, one step “coverage” to voice mail. If voice mail 
is unavailable for any reason, the call does not cover elsewhere.
•Call Diversion — You can divert (or forward) calls unconditionally, upon busy or 
no reply, to another extension including forwarding voice mail.
•Calling Number ID — You can display the calling party’s number to the called 
party during alerting and after answer.
•Calling Name — You can assign the Calling Name Feature Plus identifier with a 
maximum size of 15 bytes or the maximum network subaddress size, whichever is 
lower.
•Connected Line Identification Presentation (COLP) — You can assign display 
forwarded-to party information to the calling user’s display.
•Call Transfer - Basic — You can assign transfer calls between parties across the 
public network is supported. Display updates at the time of transfer or upon 
completion of transfer, however, are not supported.
•Served User PBX for Centralized AUDIX — Determines where to send messages 
destined for the AUDIX hunt group.
•Message Waiting Indication — You can assign display a message waiting 
indication on a user’s voice terminal.
Differences in Inserted Digits field
There is a difference in how the Inserted Digits to form Complete Number 
field on the Message Waiting Indication Subscriber Number Prefixes form is used for 
QSIG and Feature Plus. This difference is due to the difference in how the Feature 
Plus and QSIG-TSC platforms operate. 
For Feature Plus, the Feature Plus extension must be included in the Inserted Digits 
to form Complete Number field, while for QSIG, only the higher order digits 
need to be included. (In QSIG MWI, the subscriber number is appended to the 
inserted digits and the resulting number is used to route over a QSIG TSC.) For 
example, Dallas is a Message Center PBX and Chicago is a remote PBX:
•If Feature Plus is running between Dallas and Chicago and the Feature Plus 
extension in Chicago is 82000, the Inserted Digits to form Complete 
Number field administered in Dallas to get to Chicago must be 3035382000. The 
Routing Digits (AAR/ARS Access Code) field also needs to be filled in 
appropriately.
•If QSIG is running between Chicago and Dallas, the Inserted Digits to form 
Complete Number field must contain 30353. The Routing Digits 
(AAR/ARS Access Code) field also must be filled in appropriately.) 
						

							ISDN Feature Plus 
357
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
Interrogation
When performing an audit, the Served User PBX sends a request towards the 
Message Center PBX. As a Message Center PBX, the DEFINITY ECS receives the 
request message, maps it into a MW STATUS REQUEST - SINGLE STATION 
message, and sends it to AUDIX on the BX.25 link. When AUDIX replies to the 
DEFINITY on the BX.25 link with a MW STATUS UPDATE, the Message Center 
PBX sends the information on to the appropriate Served User PBX.
•If it is a Message Center PBX, the MW STATUS UPDATE indicates whether 
there are any messages waiting, not how many messages are waiting or what 
media types are these messages. If the MW STATUS UPDATE indicates that there 
are new messages, then the Message Center PBX sends a message telling the 
Served User PBX to activate the message waiting indication. Similarly, if the MW 
STATUS UPDATE indicates that there are no new messages, then the Message 
Center PBX sends a message telling the Served User PBX to deactivate the 
message waiting indication.
•If it is a Served User PBX, when the Served User PBX receives the result, it 
makes sure that the result received from the Message Center matches the state of 
the Served User’s light.
Interactions
•Automatic Circuit Assurance
Automatic Circuit Assurance (including Referrals) is not activated for calls 
terminating at the Feature Plus extension.
•Distributed Communication System (DCS)
Feature Plus signaling links do not support DCS.
•Feature Plus Centralized AUDIX
~Calling Line Identification Presentation (CLIP)
If the public network supports CLIP and the called user has subscribed to the 
service, calling party information is available to the called user when messages 
are retrieved.
~Feature Plus Diversion
Feature Plus Centralized AUDIX relies upon Feature Plus Diversion. When a 
call covers to AUDIX, it must invoke Feature Plus Diversion to identify the 
called party to AUDIX.
~Feature Plus Message Waiting
When a calling party leaves a message using Feature Plus Centralized AUDIX, 
Feature Plus Message Waiting engages and turns on that subscriber’s message 
waiting indicator. 
						

							ISDN Feature Plus B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
358
•Feature Plus Forwarding (Diversion)
~Calling Line Identification Presentation (CLIP)
If the public network supports CLIP and the forwarded-to user has subscribed 
to the service, then calling party information is available to the forwarded-to 
user’s display.
~Connection Line Identification Presentation (COLP)
If the public network supports COLP and the calling user has subscribed to the 
service, then forwarded-to party information is available to the calling user’s 
display.
~Feature Plus Centralized AUDIX
Feature Plus Centralized AUDIX relies upon Feature Plus Diversion. Invoke 
Feature Plus Diversion first to enable the Centralized AUDIX feature.
~Call Coverage
•Terminating call has coverage active
If a call is forwarded off-switch, and the terminating switch has call 
coverage activated and the criteria is met, the call will not go to the 
forwarding coverage path. It goes to the terminating coverage path.
•Forwarding and Coverage
If the last coverage point in the coverage path is a number that 
routes over an ISDN SSF trunk, no Feature Plus Diversion 
information passes to the coverage PBX.
~Automatic Callback
If automatic callback was activated before the called voice terminal user 
activated Call Forwarding over an ISDN SSF trunk, the callback call attempt is 
redirected to the forwarded-to party over the SSF trunk.
~Call Park
If a forwarded-to (diverted-to) extension user parks a call that has been 
forwarded from an ISDN SSF trunk, the call normally is parked on the 
forwarded-to extension, not on the forwarded-from (called user) of the ISDN 
SSF trunk. 
						

							ISDN Feature Plus 
359
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
B  Private Networking
•Feature Plus Message Waiting Indication
~Audio Information Exchange (AUDIX)
Feature Plus MWI depends on the presence of a Message Center. Whenever 
DEFINITY ECS acts as a Message Center switch, there is an interaction 
between DEFINITY ECS and AUDIX. DEFINITY ECS must be able to 
receive messages from AUDIX then, if applicable, send the appropriate 
Feature Plus MWI message to the network. Similarly, if DEFINITY ECS 
receives a Feature Plus MWI message, DEFINITY ECS translates the Feature 
Plus message into the appropriate AUDIX message and passes it to AUDIX.
The only messages that DEFINITY ECS handles are AUDIX messages along 
the BX.25 link. Feature Plus MWI can interwork with Basic AUDIX, 
including INTUITY AUDIX, and with DEFINITY AUDIX with the DCIU 
control link. Feature Plus MWI does not work with the DEFINITY AUDIX 
that emulates a DCP voice terminal or with versions of AUDIX that 
communicate to DEFINITY ECS mode codes.
DEFINITY ECS implementation requires that all users on a Served User PBX 
use the same Feature Plus Message Center. Some of the served users can use a 
Feature Plus Message Center, while others use a local message center and/or a 
DCS Remote Message Center and/or a QSIG Message Center. However, some 
served users on a PBX cannot use one Feature Plus Message Center while 
other served users on the same PBX use a different Feature Plus Message 
Center.
~Off-Premise Station
Feature Plus MWI does not work with an off-premise station implemented 
with a DS1 circuit pack.
•QSIG
Feature Plus signaling links do not support QSIG. 
						

							QSIG B  Private Networking
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
360
QSIG
QSIG is the generic name for a family of signaling protocols. The Q reference point 
or interface is the logical point where signaling is passed between two switches in a 
private network. QSIG signaling allows certain features to work in a single-vendor or 
multi-vendor network. QSIG complies with the International Organization for 
Standardization (ISO) Integrated Services Digital Network (ISDN) 
private-networking specifications. QSIG is defined by ISO as the worldwide standard 
for private networks. QSIG uses ISO standard protocols as well as call independent 
signaling connections (CISCs), administered as non-call-associated temporary signal 
(NCA-TSCs).
DEFINITY ECS provides six levels of QSIG functionality (each level is turned on or 
off on page 6 of the Customer Options screen):
QSIG Category Supported Features
Basic Call Setup
•Basic Call Setup
•Number Transport 
Basic Supplementary 
Services•Called/Busy Name
•Name Identification Services
•Call Forwarding (Diversion)
•Call Transfer
•Centralized AUDIX
•Call Offer
•Call Completion (Automatic Callback)
Centralized Attendant
•Centralized Attendant Service (CAS). 
Supplementary Services 
with Rerouting •Call Forwarding (Diversion) with Reroute 
(using Path Replacement)
•Call Transfer with Reroute (using Path 
Replacement)
Transfer into Lucent QSIG 
Voice Mail•Call Transfer into QSIG Voice Mail
Value-Added Lucent (VALU)
•Displays of called party number to the calling 
party when the called number is ringing or 
busy (Called/Busy Number)
•Distinctive Ringing to identify 
internal/external and priority calls
•Call Coverage to networked switches.