Managing MultiMedia Calling
Multimedia Applications Server Interface
Administrator’s Guide for Avaya Communication Manager
251
November 2003
Avaya Communication Manager 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 Avaya Communication Manager. If you do not, you will
not be able to dial this extension from Avaya Communication Manager.
Figure 25: MASI Terminal screen — page 1
•
Extension
— This field displays the extension that you entered on the command line.
•
BCC
— 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.
•
MASI Node Number
— The number of the node on which this terminal resides.
•
TN
— 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.
•
COR
— The class of restriction associated with this terminal.
•
Name
— The name associated with the terminal. This can be any alphanumeric string up to 27
characters.
•
Send Display Info
— Indicates whether Avaya Communication Manager should forward display
information associated with a call. Set to y.
Figure 26: MASI Terminal screen — page 2
MASI TERMINAL
Extension: 1000
BCC: 0
MASI Node Number: __ TN: 1__
COR: 1_
Name: ___________________________
TERMINAL OPTIONS
Send Display Info? y
MASI TERMINAL
FEATURE OPTIONS
LWC Reception: none___
CDR Privacy? n
AUDIX Name: ________