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
Managing multimedia calling 
217 Multimedia Applications Server Interface 
9
Screen 7. Status masi trunk-group output 
Step 9 — Administer MASI terminals 
Use the 
add masi terminal xxxxx or next command to administer each MASI 
terminal as a MASI terminal. You use available extensions on the ECS, so they 
need to conform to DEFINITY ECS dial plan. The extension must match the 
DEFINITY dial plan, and for the add command, the extension must not already be 
in use.The extension of the MASI terminal must match the number of the MASI 
terminal.
DEFINITY ECS users dial the MASI Terminal Extension to reach MMCX users.
NOTE:
Anytime you add a terminal or other extension to the MMCX, you must 
administer a corresponding MASI terminal on the DEFINITY ECS. If you 
do not, you will not be able to dial this extension from the DEFINITY ECS.
Screen 8. MASI Terminal Form — page 1
  MASI TRUNK GROUP STATUS 
Group Number: xxx Number of Active MMCX Trunk Calls: xxx
MASI Node Number: xx
Remote Group Number: xxx
MASI TERMINAL
Extension: 1000  BCC: 0
MASI Node Number: __ TN: 1__
COR: 1_
Name: ___________________________
TERMINAL OPTIONS
Send Display Info? y 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
218 Multimedia Applications Server Interface 
9
nExtension — This field displays the extension that you entered on the 
command line. 
nBCC — This field displays the bearer capability class of the terminal, and 
identifies the type of traffic the terminal supports. For MASI, this is always 
0, for voice or voice-grade data. 
nMASI Node Number — The number of the node on which this terminal 
resides. 
nTN — The tenant partition in which this terminal resides. At present, all 
MASI terminals must reside within tenant 1. This field is display-only, and 
always 1. 
nCOR — The class of restriction associated with this terminal. 
nName — The name associated with the terminal. This can be any 
alphanumeric string up to 27 characters. 
nSend Display Info — Indicates whether DEFINITY ECS should forward 
display information associated with a call. Set to y.
Screen 9. MASI Terminal form — page 2 
nLWC Reception — This field indicates whether the terminal can receive 
Leave Word Calling messages. Valid values are none, audix, and spe (for 
G3r configurations) or mas-spe (for G3si/csi configurations). SPE-based 
LWC is not supported for MASI terminals. However, if DEFINITY 
AUDIX is used without a Data Control Link, you must administer MASI 
terminals to receive SPE-based LWC messages. For such cases, the LWC 
feature is used by AUDIX to activate and deactivate message waiting lamps 
on MASI terminals.
nCDR Privacy — Indicates whether CDR Privacy is supported for this 
terminal. See ‘‘
Call Detail Recording’’ on page 1221 for more information. 
MASI TERMINAL
FEATURE OPTIONS
LWC Reception: none___
CDR Privacy? n
AUDIX Name: ________ 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
219 Multimedia Applications Server Interface 
9
nAUDIX Name — This field only appears on G3r configurations. This field 
contains the name of the AUDIX adjunct for LWC messages. If LWC 
reception field is set to audix, this field must contain a name. The name 
must match a machine name on the Adjunct Names form. 
Screen 10. MASI Terminal Form — page 3
nRoom — Enter up to 10 characters to identify the MASI terminal location. 
This field may be blank.
nJack — Enter up to 5 characters to identify the location where the MASI 
terminal is connected. This field may be left blank. 
nCable — Enter up to 5 characters to identify the cable that connects the 
MASI terminal to the system. This field may be left blank. 
nFloor — Enter up to 7 characters to identify the floor where the MASI 
terminal is located.
nBuilding — Enter up to 7 characters to identify the building where the 
MASI terminal is located. Valid entries are listed in the site table.
nButton Assignments — This field contains a call appearance button and 
is display only.
Duplicate MASI terminal 
Once you have one MASI terminal administered to your liking, you can use the 
duplicate masi terminal command to administer other stations with the same 
characteristics. 
MASI TERMINAL
SITE DATA
       Room: _______ 
       Jack: _____ 
      Cable: _____ 
      Floor: _______ 
   Building: _______ 
BUTTON ASSIGNMENTS
1: call-appr 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
220 Multimedia Applications Server Interface 
9
Screen 11. Duplicate MASI Terminal form
How to list and status MASI terminals
To view a list of all the MASI terminals administered on the ECS, use the 
command 
list masi terminals.This command only lists terminals within the 
domain of the DEFINITY ECS from whose SAT you issue the command. 
Screen 12. List MASI Terminal output
To view the active or idle status of a specific MASI terminal, use the command 
status masi terminal (extension). 
MASI TERMINAL
Ext Name Room Jack Cable
77777 ___________________________ _________ _____ _____
77778 ___________________________ _________ _____ _____
77779 ___________________________ _________ _____ _____
77781 ___________________________ _________ _____ _____
77782 ___________________________ _________ _____ _____
77783 ___________________________ _________ _____ _____
_____ ___________________________ _________ _____ _____
_____ ___________________________ _________ _____ _____
_____ ___________________________ _________ _____ _____
_____ ___________________________ _________ _____ _____
_____ ___________________________ _________ _____ _____
_____ ___________________________ _________ _____ _____
_____ ___________________________ _________ _____ _____
_____ ___________________________ _________ _____ _____
_____ ___________________________ _________ _____ _____
MASI TERMINALS
Node
Ext Name  Number CDR COR TN
 
xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xx x xx xxx
xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xx x xx xxx
xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xx x xx xxx
xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxx xx x xx xxx 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
221 Multimedia Applications Server Interface 
9
Screen 13. Status MASI terminal command 
To determine which extension you assigned as the MASI Near-End Path 
Termination extension, use the command 
list extension-type. This command 
displays the extension number and type (attendant, masi-terminal, etc.), as well as 
other information about the extension. 
Screen 14. List extension type 
Step 10 — Administer features
AAR/ARS
1. AAR/ARS is an optional feature on DEFINITY ECS, and you need to 
purchase this option to use it with MMCX. To verify that this feature is 
enabled, use the command 
display system-parameters 
customer-options
. If it is not enabled, contact your Lucent Technologies 
representative. 
GENERAL STATUS
TYPE: MASI Service State: active
Extension: 54001 
MASI Node Number: 14
EXTENSION TYPE
Cv1/
Ext Type Name COR TN COS Cv2 
--- ---- ---- --- -- --- ----
1234 masi-terminal 1 1 1
4077 term-masi-path-call  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
222 Multimedia Applications Server Interface 
9
2. The MMCX dial plan must use the same feature access codes as the 
DEFINITY ECS. If this is not already the case, modify the MMCX dial 
plan using the 
chgdp command. See the MMCX Technical Reference for 
more information. 
3. Include this feature access code in the 
chgmasi command. 
CDR
1. To get call detail records for calls over MMCX interfaces, set 
CDR Reports = y on the MASI Trunk Group form. 
2. To get call records for calls over the ISDN-PRI trunk group, set 
CDR Reports = y on the ISDN-PRI Trunk Group form.
3. To track calls between a MASI terminal and other MASI terminals or 
DEFINITY stations, enter the MASI terminal extension on the Intraswitch 
CDR form. 
4. Enter n in the Record Non-Call Assoc TSC field on the CDR System 
Parameters form. 
NOTE:
If you use the same PRI trunks for MASI and non-MASI calls, it is strongly 
recommended that you do not enable CDR for these calls. Establish a 
separate trunk group for non-MASI calls and set CDR Reports = n. 
Coverage
To establish coverage from a MASI terminal to AUDIX:
1. Use the MMCX user interface to enter the AUDIX hunt group extension as 
the coverage point. You cannot use DEFINITY coverage administration for 
MASI terminals. 
2. If AUDIX ports are not administered on DEFINITY, do so. 
3. Set up the MASI terminal as an AUDIX subscriber. Enter the MASI 
terminal extension in the extension field on the Subscriber Administration 
form.
To establish coverage from a MASI terminal to another MMCX terminal or 
DEFINITY station:
1. Use the MMCX user interface to enter the desired extension as the 
coverage point for the MASI terminal. You cannot use DEFINITY 
coverage administration for MASI terminals.
Step 11 — Verify administration
Make test calls from DEFINITY to MMCX, ensure that you can indeed place and 
receive calls.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
223 Multimedia Applications Server Interface 
9
Call an unattended MASI terminal. Verify that the call goes to AUDX. Retrieve 
the call from the MASI terminal. Verify that all works as expected. 
MASI command permissions
If you are the super-user for your system, you can restrict other administrative 
logins from changing MASI administration. To do this, use the 
change 
permissions (login-ID) 
command. Enter y in the Additional Restrictions field, 
then move to the Restricted Object List page of the form.
You may restrict the following MASI-related objects:
nmasi-path-parameters
nmasi-terminal
nmasi-trunk-group
nmasi-tsc
Detailed description of features
AAR/ARS
MMCX can take advantage of advanced routing features for voice-only calls to 
the PSTN or a DEFINTY system private network. Users must enter the AAR/ARS 
access code before the rest of the dialed digits. MASI will route the call over the 
DEFINITY private network (AAR) or the public network (ARS), based on the 
digits supplied by the MMCX user. 
Routing patterns must contain only trunk groups that actually terminate on the 
DEFINITY ECS. Calls from one MMCX to another do not use AAR/ARS. 
Authorization codes are not supported. 
Call Detail Recording
Using the MASI link, DEFINITY is able to track call detail information for calls 
made using MMCX terminals and interfaces. CDR records all calls originating 
from or terminating at a MASI terminal. MASI CDR does not record ineffective 
call attempts when all MASI paths are busy. 
The Resource Flag value of 8 indicates a MASI call. This field appears in 
unformatted, int-isdn, expanded and customized CDR formats. For formats other 
than these, you can determine that a call involves a MASI terminal or trunk by the 
TAC, dialed number or calling number fields.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
224 Multimedia Applications Server Interface 
9
The following are the CDR capabilities of MASI. Administration information is 
under the heading ‘‘
How to administer MASI’’ on page 208.
nIncoming/Outgoing Trunk Call Splitting
Call splitting does not produce separate records for MMCX calls that are 
transferred or conferenced. 
nIntraswitch CDR
You can administer intraswitch CDR to monitor MASI terminals. To do 
this, simply add the MASI terminal extension on the Intraswitch CDR 
form. DEFINITY then monitors calls from MASI terminals to other MASI 
terminals, and calls between MASI terminals and DEFINITY stations. 
nCDR Privacy
You can administer a MASI terminal for CDR Privacy. 
nAccount Code Dialing and Forced Entry of Account Codes
This is not supported for MASI terminals. Therefore, make sure the COR 
you assign does not force entry of account codes.
nTrunk CDR
You can get call detail records for all incoming and outgoing calls made 
over MMCX interfaces.
Call redirection / Voice-messaging access 
MMCX users can enter a DEFINITY extension, including an AUDIX hunt group, 
Callmaster agent, attendant console or telephone as their coverage point. 
If AUDIX is established as the MASI terminal’s coverage point, the MASI 
terminal receives message waiting indication, and dials the AUDIX hunt group 
extension to retrieve messages. Once connected to AUDIX, operation for the 
MMCX user is the same as for a DEFINITY station user, including use of # to 
identify the extension, if desired. 
NOTE:
It is not possible to determine the call coverage status of a MASI terminal. 
DEFINITY tracks calls to MASI terminals that follow the autonomous coverage 
path from the MASI terminal. MMCX calls redirected to DEFINITY stations 
contain display information. 
MASI terminals that dial AUDIX directly, or that place calls to MASI terminals 
that cover to AUDIX, do not receive ringback if all AUDIX ports are busy. 
Instead, these callers see a message that the called party is busy, and the call drops.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
225 Multimedia Applications Server Interface 
9
Transfer
MASI terminals cannot transfer calls to DEFINITY stations, and cannot transfer a 
call to another MASI terminal if the call involves a DEFINITY station. 
Conferencing 
Conferences can involve both MASI terminals and DEFINITY stations, and either 
one may initiate the conference. DEFINITY stations participate in such 
conferences in voice-only mode. If an MMCX user initiates a conference that 
involves DEFINITY stations, the conference will drop when the initiator drops 
from the call. If a DEFINITY station initiates the conference, that station may 
drop without affecting the other conferees.
Status tracking - terminals and trunks 
DEFINITY ECS tracks the active/idle status of all MASI terminals, and monitors 
traffic over MMCX interfaces. 
Trunk groups
For MASI purposes, there are two kinds of trunk groups: the ISDN-PRI trunk 
groups that serve as paths for establishing calls between DEFINITY stations or 
trunks and MASI terminals or interfaces, and the remote trunks that are interfaces 
from the MMCX to other entities. Each MASI remote trunk group appears to the 
switch as a single unit, with no concept of members within the group. 
NOTE:
You cannot test, busy out, or release MASI remote trunk groups, since you 
cannot dial a MASI remote trunk TAC from the DEFINITY ECS. The TAC 
merely identifies the trunk to the switch for status and CDR.
You cannot administer MASI trunks as part of DEFINITY route patterns. 
Interactions & Unsupported Features
We can generalize feature interactions to some extent. For example, since there 
are no buttons available to a MASI terminal, any feature that requires a button is 
also not available. MASI cannot support features that require the user to dial a 
trunk access code for a MASI remote trunk, or a feature access code other than 
AAR/ARS. The MMCX dial plan may contain only those feature access codes 
that are supported. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing multimedia calling 
226 Multimedia Applications Server Interface 
9
!CAUTION:
DO NOT ADMINISTER the following features! The following features are not 
supported for use over the MASI link, and Lucent Technologies cannot be responsible 
for the results if you attempt to administer them. 
Unsupported Call Center features
nASAI — You must not administer a MASI terminal in an ASAI domain. 
MASI terminals and MMCX trunks are not monitored by ASAI. It may be 
possible for a MASI terminal to place a call to a DEFINITY station that is 
part of an ASAI domain. ASAI will not be blocked from controlling this 
call, but there may be unpredictable results. The same is true for calls 
originating from an ASAI domain terminating at MASI terminals, and for 
ASAI-monitored hunt groups that contain MASI terminals. 
nAutomatic Call Distribution — You must not include a MASI terminal 
extension as part of an ACD hunt group. You must not mix MASI 
administration with anything related to ACD, including Outbound Call 
Management and PASTE. 
nCall Vectoring — You must not include MASI terminal extensions in any 
step of a vector. 
Unsupported Basic features
nBridged Call Appearances — You must not administer a bridged 
appearance that involves a MASI terminal. 
nCall Coverage — You must not administer a MASI terminal in a 
DEFINITY station’s coverage path. 
nCall Forwarding — You must not forward a DEFINITY station to a MASI 
terminal. 
nCall Pickup — You must not administer a MASI terminal as part of a 
pickup group. 
nIntercom — You must not administer MASI terminals as members of any 
type of intercom group.
nManual Message Waiting — You must not administer a manual message 
waiting button (man-msg-wt) with a MASI terminal as the referenced 
extension.
nManual Signaling — You must not administer a manual signaling button 
(signal) with a MASI terminal as the referenced extension. 
nNight Service — You must not administer a MASI terminal as a night 
service destination.