Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Managing multimedia calling 217 Multimedia Applications Server Interface 9 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. 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.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Managing multimedia calling 218 Multimedia Applications Server Interface 9 nMASI terminal — The DEFINITY system representation of MMCX terminals in a MASI environment. 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.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Managing multimedia calling 219 Multimedia Applications Server Interface 9 MASI configurations There are several ways to set up combinations of MASI nodes and DEFINITY servers.The following figures depict several possible configurations. 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.1 June 2000 Managing multimedia calling 220 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
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Managing multimedia calling 221 Multimedia Applications Server Interface 9 Figure 7. Two separate MASI domains DEFINITY PSTN PSTN WAN AUDIX S1Trunk 1 Trunk 4Trunk 3 Trunk 2SG2 SG1MMCX 1 MMCX 2 DEFINITY 1 DEFINITY AUDIX S2DEFINITY 2 LAN LAN E1 E3 E2 E4 cydfdda3 LJK 071897 34 12
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Managing multimedia calling 222 Multimedia Applications Server Interface 9 Figure 8. One MASI domain, and one non-MASI MMCX The MASI node must be directly connected to the DEFINITY ECS for MASI features to work. In this configuration, terminals that belong to MMCX 2 (E3 and E4), do not take advantage of MASI capabilities. DEFINITY PSTN PSTN WAN INTUITY S1Trunk 1 Trunk 2 SG1MMCX 1 MMCX 2 DEFINITY 1 LAN LAN E1 E3 E2 E4 cydfdda4 LJK 071897 34 12
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Managing multimedia calling 223 Multimedia Applications Server Interface 9 How to administer MASI This section discusses the administration required to make MASI work. You perform most of this administration from the DEFINITY administration terminal. However, there are a few things you must do at the MMCX administration terminal. This section sometimes refers to the chgmasi command. This is the command you use to administer MASI parameters on the MMCX. For more information about using the chgmasi command, refer to your MMCX Technical Reference. Step 1 — Establish customer options (Lucent Technologies) A Lucent Technologies representative must activate MASI using the System-Parameters Customer-Options form. The representative should also verify that ISDN-PRI (G3r configurations) or ISDN-PRI over PACCON (G3si/csi configurations), and AAR/ARS are enabled. On the MMCX, MASI must be enabled using the chgmasi command. Step 2 — Establish maintenance parameters and alarming options (Lucent Technologies) Ensure that the Maintenance-Related System Parameters form, Packet Bus Activated field = y. Using the set options command (Lucent Technologies init or inads logins only), set MASI alarming options. For more information, see DEFINITY ECS Maintenance for the appropriate model. Step 3 — Establish the physical connection Establish the physical connection between the DEFINITY ECS and the MMCX. For more information about installing the cables, see Installation for Adjuncts and Peripherals.
DEFINITY ECS Release 8.2
Administrator’s Guide 555-233-506 Issue 1.1
June 2000
Managing multimedia calling
224 Multimedia Applications Server Interface
9
Step 4 — Administer circuit pack
Using the DS1 Circuit Pack form, verify that the DS1 circuit pack you use to
establish the MASI link is administered as follows:
nBit Rate = 1.544
nLine Coding = b8zs
nLine Compensation = 1
nSignaling Mode = isdn-pri
nInterface = network
nCountry Protocol = 1
nProtocol Version = a
Step 5 — Administer a signaling group
For each MASI node, you need to establish a unique signaling group. Use the
command
add signaling-group xxx to access the Signaling Group form.
Screen 1. Signaling Group Form (Page 1 of 5)
For each link, establish a Non-Call Associated Temporary Signaling Connection
(NCA-TSC) with the following attributes:
nAssociated Signaling — MASI requires Facility Associated Signaling, so
this field must be set to y.
nPrimary D-channel — Enter a 6- to 7-character port number associated
with the DS1 Interface circuit pack port. The port address of the PRI that
carries D-channel signaling.
The port number is used to assign the primary D-channel in the Signaling
Group. For 24-channel facilities, the 24th port is assigned as the D-channel.
For 32-channel facilities, the 16th port is assigned as the D-channel.
nMax Number of NCA TSC — For MASI, this must be 1.
nMax number of CA TSC — Leave the default of 0.
nTrunk Group For NCA TSC — This can be left blank.
nTrunk Group for Channel Selection — This can be left blank.
Page 1 of 5
SIGNALING GROUP
Group Number: _ Associated Signaling? y Max number of NCA TSC: __
Primary D-Channel: ______ Max number of CA TSC: __
Trunk Group for NCA TSC: __
Trunk Group for Channel Selection: ___
DEFINITY ECS Release 8.2
Administrator’s Guide 555-233-506 Issue 1.1
June 2000
Managing multimedia calling
225 Multimedia Applications Server Interface
9
Screen 2. Administered NCA TSC Assignment page of the Signaling Group form
nService/Feature — Leave blank.
nAs-needed Inactivity Time-out (min) — This field only applies to
as-needed NCA-TSCs. Since MASI requires a permanent connection,
leave blank.
nTSC Index — This display-only field specifies the administered
NCA-TSCs assigned.
nLocal Ext — Enter a valid, unassigned DEFINITY ECS extension. This
extension does not need a port assignment and does not need to correspond
to any other administration.
nEnabled — Enter
\ to enable the administered NCA-TSC. You may want
to wait to enable this link until all other administration is in place. If this is
y, DEFINITY ECS attempts to establish the connection as soon as you
submit the form. This may cause your system to alarm, if other
administration is not finished.
nEstablish — Used to indicate the strategy for establishing this
administered NCA-TSC. Enter permanent for MASI.
nDest. Digits — A valid MMCX extension. This must correspond to the
value of the tscnum argument to the
chgmasi command.
NOTE:
These digits are sent as entered to the destination MMCX; no routing
or other digit manipulation is performed.
ADMINISTERED NCA TSC ASSIGNMENT Page 2 of 5
Service/Feature: __________ As-needed Inactivity Time-out (min): __
TSC Local Mach.
Index Ext. Enabled Established Dest. Digits Appl. ID
1: _____ _ _________ _______________ _______ __
2: _____ _ _________ _______________ _______ __
3: _____ _ _________ _______________ _______ __
4: _____ _ _________ _______________ _______ __
5: _____ _ _________ _______________ _______ __
6: _____ _ _________ _______________ _______ __
7: _____ _ _________ _______________ _______ __
8: _____ _ _________ _______________ _______ __
9: _____ _ _________ _______________ _______ __
10: _____ _ _________ _______________ _______ __
11: _____ _ _________ _______________ _______ __
12: _____ _ _________ _______________ _______ __
13: _____ _ _________ _______________ _______ __
14: _____ _ _________ _______________ _______ __
15: _____ _ _________ _______________ _______ __
16: _____ _ _________ _______________ _______ __
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Managing multimedia calling 226 Multimedia Applications Server Interface 9 nAppl. — Specifies the application this administered NCA-TSC is going to be used for. Enter masi. nMachine ID — Used to indicate the MASI node to which this administered NCA-TSC is connected. This number should be the same as the MASI node number found on other forms. How to list TSCs or determine status of the TSC To determine which TSCs are designated for MASI, use the list masi tsc command. Screen 3. MASI Temporary Signaling Connections (TSC) Display This command displays the following: nSig Grp — The number of the signaling group to which this TSC belongs nPrimary D-Channel — Port location of the Primary D-channel nTSC Index — The number of the MASI TSC within the signaling group nLocal Ext. — DEFINITY extension associated with the TSC nEnabled — Indicates the state of the connection - enabled (y/n) nEstablished — Value of established flag (as-needed/permanent) nDest. Digits — The MMCX extension that indicates the TSC destination nMach. ID — MASI node number Once you establish and enable the signaling group, you need to verify that it is active. Use the command status signaling-group signaling-group# or status tsc-administered signaling-group# [/tsc-index] [print] to determine if the link is active. MASI TEMPORARY SIGNALING CONNECTIONS (TSC) Sig. Primary TSC Local Mach. Grp D-Chan Index Ext. Enabled Established Dest. Digits ID xxx xxxxxxx xxx xxxxx x xxxxxxxx xxxxxxxxxxxxxxx xx xxx xxxxxxx xxx xxxxx x xxxxxxxx xxxxxxxxxxxxxxx xx xxx xxxxxxx xxx xxxxx x xxxxxxxx xxxxxxxxxxxxxxx xx