Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
237 Multimedia Applications Server Interface 
9
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. 
The following are the CDR capabilities of MASI. Administration information is 
under the heading ‘‘
How to administer MASI’’ on page 223.
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. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
238 Multimedia Applications Server Interface 
9
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. 
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.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
239 Multimedia Applications Server Interface 
9
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.
!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.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
240 Multimedia Applications Server Interface 
9
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.
nPull transfer — MASI terminals cannot perform a pull transfer operation. 
You must not administer this feature on an ECS where MASI is active. This 
applies only in Italy. 
nStation Hunting — You must not administer a MASI terminal as part of a 
station hunting path. 
nTerminating Extension Groups — You must not administer a MASI 
terminal as part of a TEG. 
Other interactions
The following section describes feature behaviors that may not be as expected, but 
that are not likely to be destructive. 
Attendant features
nDial Access to the Attendant — MASI terminals will be able to dial the 
attendant access code, if it is administered in the MMCX dial plan. 
nAttendant Direct Extension Selection — Attendants are able to access 
MASI terminals via DXS buttons and busy lamp indicates status of the 
MASI terminal. 
nEmergency Access to the Attendant — MASI terminals have emergency 
access using the attendant access code, if it is administered in the MMCX 
dial plan. However, off-hook alerting is not administrable.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
241 Multimedia Applications Server Interface 
9
nAttendant Intrusion — Attendants are able to activate intrusion towards 
MASI terminals. 
nAttendant Override — Attendants are not able to activate override towards 
MASI terminals. 
nAttendant Recall — MASI terminals cannot activate attendant recall. 
nAttendant Remote Trunk Group Select — Attendants cannot use this 
feature to select MASI remote trunks.
nAttendant Return Call — Operates normally if a MASI terminal is the 
called party.
nAttendant Serial Call — Serial calls are denied if the calling party is an 
MMCX interface.
nAttendant Straightforward Outward Completion — The attendant is able to 
complete calls to DEFINITY trunks for MASI terminals. 
nAttendant Through Dialing —The attendant can use Through Dialing to 
pass dial tone to MASI terminals. 
nAttendant Timers — Attendant timers work the same no matter what kind 
of terminal is involved. 
nAttendant Trunk Group Busy/Warning Indicators — You cannot administer 
Busy/Warning indicators for MASI trunks because they are not standard 
DEFINITY trunks. However, you can administer these indicators for the 
trunk group administered for MASI paths. 
nAttendant Trunk Identification — The attendant is not able to identify the 
trunk name via button pushes. 
Basic features 
nAbbreviated Dialing — A DEFINITY station can enter an MMCX 
extension in an AD list. However, MASI terminals cannot use AD. 
nAdministered Connections — MASI terminals must not be the originator 
nor the destination of an administered connection. 
nAutomatic Callback — Automatic callback does not work towards a MASI 
terminal. 
nAutomatic Circuit Assurance — You must not administer a MASI terminal 
as an ACA referral destination. You cannot administer ACA for MASI 
remote trunks. 
nBusy Verification of Terminals and Trunks — You cannot use Busy 
Verification for MASI terminals or remote trunks.
nCall Detail Recording — CDR Account Code Dialing and Forced Entry of 
Account Codes are not supported for MASI terminals. See Call Detail 
Recording in Detailed Description for more information.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
242 Multimedia Applications Server Interface 
9
nCall Park — The attendant can park calls at the extension of a MASI 
terminal, but users can only retrieve these calls from a DEFINITY station, 
since MASI terminals cannot dial the Answer Back FAC. 
nData Call Setup — DEFINITY users cannot place data calls to MASI 
terminals. 
nFacility Busy Indication — You can use FBI to track the status of MASI 
terminals. The FBI button and indicator lamp must be on a DEFINITY 
station. You cannot use FBI to track MMCX interfaces. 
nFacility Test Calls — DEFINITY users cannot make test calls to MMCX 
interfaces. 
nGo to Cover — MASI terminals cannot activate this feature. 
nLeave Word Calling — The only valid LWC destination for a MASI 
terminal is AUDIX. You cannot administer SPE-based LWC. MASI 
terminals cannot send LWC messages to DEFINITY stations or MASI 
terminals. 
nLoudspeaker paging — You can administer a MASI terminal as a code 
calling extension. 
nMalicious Call Trace — MASI terminals cannot initiate malicious call 
trace. 
nMessage Retrieval — MMCX users can only retrieve messages through 
AUDIX. 
nMusic on Hold — Music on hold will only be available if a DEFINITY 
station has placed the call on hold.
nOverride — Executive override does not work towards MASI terminals. 
nPriority Calling — Priority calling is not supported for calls to or from 
MASI terminals. 
nRingback Queueing — Ringback Queueing is not supported for MASI 
terminals. 
nSend All Calls — MMCX has an autonomous SAC function. See Call 
Redirection for more information. 
nTenant Partitioning — All MASI terminals exist in tenant 1, and you 
cannot change the tenant number. 
nTime of Day coverage — As with all coverage, DEFINITY does not 
control coverage of the MASI terminal.
nTransfer out of AUDIX — A MASI terminal cannot use *T to transfer 
from AUDIX to another MASI terminal.  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
243 Multimedia Applications Server Interface 
9
Hospitality features
nDo Not Disturb — MASI terminals cannot activate Do Not Disturb. 
Multimedia features 
nMultimedia Call Handling — DEFINITY MMCH users are not able to 
make H.320 calls to MASI terminals over the MASI link. Calls between 
MMCX terminals and MMCH terminals are voice only. 
Troubleshooting
Verify proper operation using the following commands and follow normal 
escalation procedures to resolve any failures detected by the demand test. 
1. Verify the DS1 trunk using the 
test board  long 
command.
2. Verify the ISDN Signaling Group using the 
test signaling-group 
 command. Also verify proper administration. 
3. Verify the temporary signaling connection using the 
test tsc-administered 

 command. Also verify proper administration.
Common error conditions 
If the cable from the ECS to the MMCX becomes disconnected, you should see 
alarms raised against ISDN-SGRP and UDS1-BD. In particular, you should 
observe ISDN-SGRP errors such as 769, 1793, and 257. To resolve, reconnect the 
cable and follow normal test procedures. 
If the far-end path termination number is incorrect, you should observe 
MASI-PTH error 513. To resolve, correct administration using the MASI Path 
Parameters form. 
If the Layer 3 TSC is not administered properly or is out of service, you should 
observe errors (but no alarms) raised against TSC-ADM. Verify the signaling 
group administration and follow normal escalation procedures for TSC-ADM. 
See the appropriate DEFINITY ECS Maintenance manual for more information. 
If the TSC fails to come up even through Layer 2 Signaling Group and below pass 
tests, you may run
 test tsc-administered  to force a switch 
heartbeat test, or simply wait 5–10 minutes for the link to recover. This situation 
may happen if the switch is rebooted or if the MASI interface is administered 
before the MMCX is properly administered. 
You may want to use busy port and release port commands to unlock things if 
features are not working. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
244 Multimedia Call Handling 
9
Multimedia Call Handling
Multimedia Call Handling (MMCH) enables users to control voice, video, and 
data transmissions using a telephone and PC. Users can conduct video 
conferences and route calls like a standard voice call. They can also share PC 
applications to collaborate with others working from remote sites. 
Operations in Basic or Enhanced modes
There are two distinct levels of functionality: Basic and Enhanced. The Basic 
mode of operation treats a standard-protocol H.320 multimedia call as a data call. 
If the call is redirected, it is converted to a voice call. As a voice call, certain 
features are enabled, such as coverage, voice mail, and multiparty video 
conferencing. 
The Enhanced mode of operation allows a multifunction telephone to control a 
multimedia call as if it were a standard voice call. Spontaneous video 
conferencing, call forwarding, call coverage, hold, transfer and park, along with 
many routing features, are available to multimedia calls. Both modes of operation 
allow data collaboration between multiple parties using the T.120 standard 
protocol. 
Definitions: MMCH features and components 
Multimedia call
A multimedia call, for MMCH, is one that conforms to the H.320 and T.120 suite 
of protocol standards. These standards allow video-conferencing packages from 
different vendors to communicate with one another. The capabilities of the 
individual multimedia-endpoint package can vary, however. 
nAn H.320 call can contain voice, video and data. 
nThe bandwidth for MMCH calls is limited to 2 B-channels. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
245 Multimedia Call Handling 
9
Figure 9. MMCH multimedia complex
Basic multimedia complex
A Basic multimedia complex consists of a BRI-connected multimedia-equipped 
PC and a non-BRI-connected multifunction telephone administered in Basic 
mode. With a Basic multimedia complex, users place voice calls at the 
multifunction telephone and multimedia calls from the multimedia equipped PC. 
Voice calls will be answered at the multifunction telephone and multimedia calls 
will alert first at the PC and, if unanswered, will next alert at the voice station. A 
Basic multimedia complex provides a loose integration of the voice station and 
H.320 DVC system.
Enhanced multimedia complex
An Enhanced multimedia complex consists of a BRI-connected 
multimedia-equipped PC and a non-BRI-connected multifunction telephone 
administered in Enhanced mode. The Enhanced multimedia complex acts as 
though the PC were directly connected to the multifunction telephone. Thus, voice 
call control, multimedia call control and call status are enabled at the telephone. 
An Enhanced multimedia complex provides a tight integration of the voice station 
and H.320 DVC system.
BRI
port
circuit
card
DCP
port
circuit
card
DEFINITY
cydfdvc1 LJK 121997
Any vendors
H.320 DVC
product
DEFINITY
DCP
multifunction
telephone 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing multimedia calling 
246 Multimedia Call Handling 
9
Multimedia endpoint
The multimedia endpoint is a user’s PC that has been equipped with an H.320 
multimedia package. The PC is physically connected to the DEFINITY ECS with 
a BRI line.
Figure 10. Enhanced MMCH service link 
Enhanced mode service link
The service link is the combined hardware and software multimedia connection 
between the user’s multimedia endpoint and the DEFINITY ECS which 
terminates the H.320 protocol. The service link provides video, data, and, 
optionally, voice streams to augment the capabilities of the telephone and PC. A 
service link only applies to an Enhanced multimedia complex, never to a Basic 
multimedia complex. The service link is administered on the station form and can 
be either “permanent” or “as-needed.” 
DEFINITY
cydfdvc2 LJK 011498
BRI
H.320
protocolsAudio
conditioning
Audio stream
Video stream
Data stream VC
MMI