Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Routing outgoing calls 
197 Setting up shortcut dialing 
8
Use AAR/ARS shortcut dialing to modify your dial plan and expand the 
capabilities of automatic routing. For example, with shortcut dialing, users can 
make AAR and ARS calls without dialing the Feature Access Code (FAC). Also, 
you can add 6- and 7-digit extensions to a 5-digit dial plan. Shortcut dialing works 
with dial plans that use 2-digit through 20-digit dialing, depending on your digit 
analysis tables. 
NOTE:
If you use 6 or 7 digits shortcut dialing numbers in a 5-digit UDP, those 
calls lose DCS transparency.
Before you start
Verify that the AAR/ARS Shortcut Dialing, ARS, and Private Networking fields 
on the System Parameters Customer Options screen are all set to y.
Instructions
You may want to let users dial an emergency number without having to dial the 
feature access code (FAC) to make an external call. For example, administrators in 
the U.S may want to allow 911 emergency calls to be made without first dialing 
the ARS access code of 9.
To allow direct-dialed 911 emergency calls, complete the following steps: 
1. Type 
change dial plan and press RETURN.
The Dial Plan Record appears.
 Page 1 of 1
                                 DIAL PLAN RECORD 
Local Node Number: 1
ETA Node Number: _
          Uniform Dialing Plan: 4-digit ETA Routing Pattern: _
UDP Extension Search Order: local-extensions-first
FIRST DIGIT TABLE
  First                               Length
  Digit   -1-         -2-         -3-         -4-         -5-         -6-
1: __________ __________ __________ extension_ __________ __________
2: __________ __________ __________ extension_ __________ __________
3: __________ __________ __________ extension_ __________ __________
4: __________ __________ __________ extension_ __________ __________
5: __________ __________ __________ extension_ __________ __________
6: __________ __________ __________ __________ __________ __________
7: __________ __________ __________ __________ __________ __________
8: __________ __________ __________ __________ __________ __________
9: fac_______ __________ ars_______ __________ __________ __________
0: attd______ __________ __________ __________ __________ __________
*: __________ __________ __________ __________
#: __________ __________ __________ __________   
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Routing outgoing calls 
198 Setting up shortcut dialing 
8
2. Type ars in First Digit row 9, Length column 3.
This allows direct dialing of the emergency number, 911. ARS analysis 
begins when the number dialed starts with 9 and the switch collects 3 or 
more digits before an interdigit timeout. 
3. Press 
ENTER to save your changes.
Add numbers to a DCS network
You can use shortcut dialing to add numbers to a DCS network. As an example, 
let’s use a DCS network with switches in Chicago, Denver, and Boston. The 
4-digit UDP allows internal DCS calls between Chicago and Denver. We want to 
add Boston to the network, but do not have enough 4-digit extensions available. 
We’ll add ARS shortcut dialing to the dial plan to allow 7-digit shortcut dialing 
from Chicago and Denver to Boston.
The following table shows the dialing instructions for the extended 4-digit UDP 
network, and will help you understand the steps on how to set up shortcut dialing 
on the Dial Plan Record. 
The dial plan is set up to allow 4-digit extensions that start with digits 2, 3, 4, 5, 
and 6. The 
fac entry in First Digit 8 corresponds to a standard AAR Feature 
Access Code, and the 
fac entry in First Digit * corresponds to a standard ARS 
Feature Access Code. Digit analysis routes 4-digit calls that start with 6 to Denver, 
and 4-digit calls that start with 4 to Chicago. 
The capacity of the dial plan in Boston allows calls from Boston to the rest of the 
network to be dialed using 4 digits. However, DCS is not available because of the 
dialing limitations on calls to Boston.
Calls from Calls to Dialing instructions DCS
Denver,
Chic ag oDenver 6-xxx yes
Chic ag o 4-xxx yes
Boston 332-xxxx, 949-xxxx no
p rivate network (AAR) 8 +  p rivate-network numb er no
public network (ARS) *9 + public network number n/a
Boston Denver 6-xxx no
Chicago 4-xxx no
Boston 2-xxx, 9-xxx yes
public network (ARS *9 + public network number n/a 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Routing outgoing calls 
199 Setting up shortcut dialing 
8
Instructions
To add 7-digit shortcut dialing to a 5-digit uniform dial plan:
1. Type 
change dial plan and press RETURN.
The Dial Plan Record screen appears.
2. Type 
aar in First Digit row 3, Length column 5.
This allows numbers that begin with 3 and are 5 or more digits long to use 
aar shortcut dialing to access the DCS node in Boston. DCS transparency is 
lost on these calls.
3. Type 
ars in First Digit row 9, Length column 3.
This allows numbers that begin with 9 and are 3 or more digits long to use 
ars shortcut dialing to access the DCS node in Boston. DCS transparency is 
lost on these calls.
This also allows direct dialing of the emergency number, 911.
4. Press 
ENTER to save your changes.
Related topics
Refer to ‘‘
Understanding the dial plan’’ on page 19 for information on modifying 
a dial plan. 
Refer to ‘‘
Automatic routing — general’’ on page 1167 for more information on 
AAR and ARS.
 Page 1 of 1
                                 DIAL PLAN RECORD 
Local Node Number: 1
ETA Node Number: _
          Uniform Dialing Plan: 4-digit ETA Routing Pattern: _
UDP Extension Search Order: local-extensions-first
FIRST DIGIT TABLE
  First                               Length
  Digit   -1-         -2-         -3-         -4-         -5-         -6-
1: __________ __________ __________ __________ __________ __________
2: __________ __________ __________ extension_ __________ __________
3: __________ __________ __________ extension_
aar_______ __________
4: __________ __________ __________ extension_ __________ __________
5: __________ __________ __________ extension_ __________ __________
6: __________ __________ __________ extension_ __________ __________
7: __________ __________ __________ __________ __________ __________
8: fac_______ __________ __________ __________ __________ __________
9: __________ __________
ars________________ __________ __________
0: __________ __________ __________ __________ __________ __________
*: __________ fac_______ __________ __________
#: __________ __________ __________ __________   
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Routing outgoing calls 
200 Setting up shortcut dialing 
8 
						

							Managing multimedia calling 
201 Multimedia Applications Server Interface 
9
DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
9
Managing multimedia calling
Multimedia Applications Server 
Interface 
The Multimedia Applications Server Interface (MASI) defines a protocol and a set 
of operations that are used to extend DEFINITY ECS feature functionality to a 
Multimedia Communications Exchange (MMCX) system. MASI architecture fits 
the client/server model, where the DEFINITY ECS functions as a server for 
MMCX clients. Examples of features supported by MASI include Call Detail 
Recording (CDR), AUDIX/I
NTUITY voice mail integration, and AAR/ARS. 
MMCX can make use of both MASI features and MMCX autonomous features. 
Autonomous features are those that MMCX provides, even if MASI is not 
enabled. This document does not discuss them unless there is a consideration for 
MASI administration. 
Some autonomous MMCX features:
nBasic Call (Place/Drop)
nCall Coverage 
nConference
nTransfer
DEFINITY/MASI features:
nBasic Call (Place/Drop) — DEFINITY ECS tracks the status of all calls 
placed to or from a MASI terminal.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
202 Multimedia Applications Server Interface 
9
nCall Detail Recording — DEFINITY ECS tracks calls to and from MASI 
terminals and can produce call records that indicate if a call uses MASI. 
nCall Coverage — DEFINITY ECS tracks MMCX calls that are sent to 
coverage. A DEFINITY coverage path can contain both MASI terminals 
and DEFINITY stations. 
nConference — DEFINITY ECS tracks conference calls that involve MASI 
terminals, if a DEFINITY station originates the conference. Conferences 
that involve MASI terminals and DEFINITY stations are voice-only. If the 
DEFINITY station originates the call, the caller can use the consultative 
form of conference or transfer. 
nWorld Class Routing (AAR or ARS) — Calls from MASI terminals can 
take advantage of DEFINITY ECS World Class Routing capabilities. 
nVoice messaging access to AUDIX/INTUITY — MMCX users can take 
advantage of AUDIX voice messaging, and receive message waiting 
indication. 
nMMCX trunking — By assigning DEFINITY trunk access codes to 
interfaces from the MMCX to other MMCXs or the PSTN, DEFINITY 
ECS can monitor traffic over those interfaces. 
Before you start
!CAUTION:
DEFINITY ECS offers a wide range of features, and MMCX users may want 
to take advantage of this. In some cases, these features will operate as 
expected. However, some features are not supported for use over the MASI 
link, and their behavior is unpredictable. You may cause harm to your 
system by attempting to use these features. The Interactions section contains 
a list of features, and lists those features that are absolutely not supported 
for use with MASI. If you administer features on the DO NOT ADMINISTER 
list, Lucent Technologies cannot be responsible for the result. 
For purposes of administration, there are feature buttons and groups of users that 
you must not administer with MASI terminal extensions. There are also features 
that you simply cannot administer for a MASI terminal, because the software does 
not allow it. 
About this document
The following section describes the Multimedia Applications Server Interface, 
and provides instructions on how to set it up, including administration and 
monitoring. It also includes a section on troubleshooting. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
203 Multimedia Applications Server Interface 
9
You need to use both the DEFINITY system administration terminal (SAT) and 
the MMCX administration terminal to administer MASI. This document describes 
what you need to do at the DEFINITY SAT. It also occasionally mentions 
administration that you must do at the MMCX administration terminal. For more 
detailed MMCX information, see the MMCX Technical Reference. 
List of terms
This is a list of terms that are specific to MASI, or that have meanings in the 
context of MASI that are not standard. 
nchgmasi — The command you use to administer MASI at the MMCX 
administration terminal. 
nInterserver — Connections between MMCX terminals on different 
MMCX servers/nodes.
nMASI domain — A MASI domain consists of a DEFINITY system and 
one or more MASI nodes that share the same dial plan. That is, the 
extension numbers on the MMCX are known to the DEFINITY, and fit in 
the DEFINITY dial plan.
nMASI interworking — MASI interworking refers to the completion of a 
voice connection within a DEFINITY system, involving at least one MASI 
terminal and a MASI path. 
nMASI link — The connection between the MMCX and the DEFINITY 
ECS. 
nMASI node — A single MMCX server. You may connect more than one 
MASI node to a DEFINITY system. Each node has a separate number. This 
node number needs to be consistent whenever referring to a specific 
MMCX server. 
nMASI non-interworking — MASI non-interworking refers to the 
completion of a call by MMCX, not involving a MASI path.
nMASI path — The ISDN B-channels between MMCX and DEFINITY 
ECS in a MASI environment. Paths are used for voice and data connections 
between DEFINITY ECS and MMCX.
nMASI signaling link — ISDN D-channel used to transport a new ISO 
protocol called the MASI protocol between the DEFINITY ECS and the 
MMCX.
nMASI terminal — The DEFINITY system representation of MMCX 
terminals in a MASI environment.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
204 Multimedia Applications Server Interface 
9
nMMCX interface — PRI interface for connecting an MMCX server to other 
public, private or WAN switching systems or equipment that is part of the 
public network. Similar to a DEFINITY trunk group. These may include 
non-MASI trunks connecting the DEFINITY ECS and the MMCX.
nMMCX trunk — The DEFINITY system representation of trunk or network 
facilities terminating on MMCX. For purposes of MASI, they are called 
“interfaces.” 
Planning for MASI
Before you start to administer MASI, you should make a plan for how to do it. 
Among the configurations on the following pages, there is probably one that 
matches the configuration of your system fairly closely. You might want to either 
write on these pages, or draw up your own configuration. It may help you if you 
have already determined trunk group and signaling group numbers, unused 
extensions, and so on. The following are things you need to consider: 
nEstablish the dial plan on the MMCX to agree with that of the DEFINITY 
ECS. If you use Universal Dial Plan and MMCX, you may need to make 
adjustments for the MMCX dial plan. 
nFind unused extensions and trunk group numbers. You need:
— one trunk group number for each ISDN-PRI connection to the 
MMCX
— one signaling group number for each MASI node and an unused 
DEFINITY extension for the signaling group
— one unused DEFINITY extension for the Near-End Path 
Termination number for all MASI Paths to this ECS. You can use 
the same number for all MASI nodes in the domain.
— two unused MMCX extensions for the nearpath and tscnum 
arguments to the 
chgmasi command. This is the command you use 
to administer MASI on the MMCX. 
MASI configurations
There are several ways to set up combinations of MASI nodes and DEFINITY 
servers.The following figures depict several possible configurations.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
205 Multimedia Applications Server Interface 
9
Figure 5. MASI domain of one DEFINITY ECS and one MMCX
The parts of this drawing, for MASI, are as follows:
nTrunk 1 — This is any type of trunk connection to the public network. 
nTrunk 2 — This is the link between the DEFINITY ECS and the MMCX, 
and requires a TN464C or later DS1 circuit pack. You administer this link 
as an ISDN-PRI trunk group, a MASI path and an NCA-TSC. 
nI1 and I2 — These are MMCX interfaces to destinations other than 
DEFINITY ECS. Administer as MASI trunks.
nE1 and E2 — Endpoints (terminals) belonging to the MMCX. Administer 
as MASI terminals. 
nMMCX — Determine a node number for each MMCX server. This can be 
any number from 1–15. Once established, DEFINITY ECS informs the 
MMCX of its node number.
nS1 — DEFINITY station. 
DEFINITY
PSTN
PSTN WAN
AUDIX
S1Trunk 2 Trunk 1
MMCX
1 DEFINITY
1
LAN
E1 E2
cydfdda1 LJK 071597
12
SG1 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
206 Multimedia Applications Server Interface 
9
Figure 6. MASI domain of one DEFINITY ECS and two (or more) MMCXs 
DEFINITY
PSTN
PSTN WAN
AUDIX
S1Trunk 1
Trunk 3
Trunk 2SG2
SG1
MMCX
1 MMCX
2
DEFINITY
1
LAN LAN
E1 E3
E2 E4
cydfdda2 LJK 071597
34
12