Nortel Meridian Option81c Document

Nortel Meridian Option81c Document

Contents
1. An introduction to Nortel Meridian Option81c…………………………………..03

2. Option81c Switch Room Layout…………………………………………………..05
3. Power supply to Option81c
03.1 Rectifier Units
4. Hardware Installation
4.1 Core/Network Module
4.2 Network Module
4.3 IPE Module
5. Software Configuration
5.1 System Configuration
5.2 Customer Configuration
6. Meridian Mail
6.1 Installation
6.2 Hardware interface between Meridian mail and Option81c
6.3 Software configuration
7. Meridian Integrated Recorded Announcement (MIRAN)
8. Meridian Integrated Conference Bridging (MICB)
1
An Introduction To Nortel Meridian Option81c

The Meridian 1 Option 81C with Call Processor PII (CP PII) provides the capacity and
speed to meet the current and future communications demands of large and growing
organizations. The CP PII offers a scalable, redundant architecture to ensure
uninterrupted voice and messaging services. The CP PII open architecture provides
seamless upgrades to increased capacity and to future generations of Intel Pentium
processors.
Dual Core architecture

Each CP PII includes two identical Core circuit card packs; while one Core processes
calls, the other Core monitors the health of the system and waits to take control if the first
Core fails.
Uninterrupted call processing

Redundancy ensures that call processing will continue if a Core/Net module or circuit
card fails. Each Core regularly checks the status of the other Core. Data and memory
from the active Core is continually backed up onto the standby Core. If a failure occurs,
the standby Core immediately takes over the system. Since the data and memory from the
original Core is used to process calls, there is no noticeable difference to end users.
Redundant links
This redundant system is made possible through the Core to Core Ethernet connection
(LAN 2 to LAN 2).
2
Power Supply To Option81c
The main power components of Option81c include a Power Control unit in the pedestal,
and the module power supplies.
• The power distribution unit located in the pedestal functions as a distribution unit
for the input voltage to each of the modules and protects them from current
overload.
3
• Power supplies Units are located in each module, rather than in separate
centralized power shelves.
03.1. Rectifier Units
4
Hardware Installation
Pedestals
Each column sits on a pedestal that contains power, cooling and monitoring equipment,
as follows:
• A Power Distribution Unit in the back of the pedestal supplies DC power to the column.
• A System Monitor checks the column’s cooling and power systems.
• A blower unit (accessible from the front of the pedestal) forces air up through the
modules to cool the circuit cards.
Top Caps
A top cap is mounted on the top module of each column, and contains the following:
• Air exhaust grills in the cap that release air from the blowers in the pedestal.
• A heat sensor that monitors the temperature of the column.
• A red LED in the front of the cap’s exhaust grill that lights if the system overheats or if
a power outage occurs.
• Ladder racks for routing cables, can also be fitted to the top caps.
5
Columns are grouped together in rows

• Columns are attached in rows. Column 0 is always the Column containing
the“Core/Net 0” module.
• Column 1 is placed to the left of Column 0 and ALWAYS contains the “Core/Net
1” module.
Core/Network Module
These modules contain the main processor cards and the first Network group. Each
system includes two Core/Net modules.
The NT4N41 CP PII Core/Net module contains a card cage. The card cage contains both
the main processor cards and the first Network group. Two Core/Net modules are
installed side-by-side in each system.
Core shelf
The Core side of the module contains the circuit cards that process calls, manage network
resources, store system memory, maintain the user database, and monitor the health of the
system. These circuit cards also provide administration interfaces through a terminal,
modem, or local area network. The Core shelves on the right side of the modules run in
redundant mode: one Core operates the system while the other Core runs diagnostic
checks and remains ready to take over if an error occurs in the active Core. Both Cores
are connected to each Network group. If one Core fails, the second Core immediately
takes over call processing. The Core shelf backplane is a compact PCI data bus.
Core circuit cards

The Core circuit cards are installed on the “Core” side of the Core/Net module. All Core
circuit cards are installed in the factory prior to shipping.
CNI: PCI Core to Network Interface (NT4N65AB)

The CNI cards connect the Core module cards to the 3PE cards in the Network modules.
Each Core module contains between one and four CNI cards. Since each CNI card can
connect to two Network groups, each Core is connected to a minimum of two groups and
a maximum of eight groups. The number of CNI cards in a system depends on the
number of Network groups in that system. The first CNI card that connects to Network
group 0 and group 1 is installed in slot c9 of each Core/Net module. Each additional CNI
card is installed in ascending order from slots c10 to c12.
CNI Transition card: PCI Core to Network Interface Transition (NT4N66AB)

The CNI Transition cards provide the cable connections to the 3PE Termination Panel in
the rear of the module. A CNI Transition card is mounted directly behind each CNI card
(on the back side of the Core backplane). Four CNI Transition cards for Core/Net Module
are installed in the factory regardless of how many CNI main cards are configured for the
system.
6
Sys Util: System Utility (NT4N67AA)

The System Utility card supports Card ID. The card provides an interface between the
security device and the computer, and an interface between the XSM and display panel
for each PCI core/net card cage. This card also includes a switch on the faceplate to
enable or disable the Core cards. One System Utility card is installed in slot c15 of each
Core/Net module.
System Utility Transition card (NT4N68AA)

The System Utility Transition card provides connections for the security device, the
system monitor, and the status panel. This Transition card is mounted on the rear of the
backplane (back side) directly behind the System Utility card. One System Utility
Transition card is installed in each Core/Net module.
CP PII: Call Processor Pentium II (A0810496)

The CP PII card contains a Pentium II processor to process calls, manage memory and
monitor the system. This card also provides serial and Ethernet interfaces used to manage
the system.
MMDU: Multi-Media Disk Unit (NT4N43AA)

This MMDU card contains the drives that store system software and databases. This card
includes:
•a hard disk to store the system database and software.
•a floppy disk to install software or back up databases
•a CD-ROM to install system software
One MMDU card is installed in the far right of each Core/Net module.
Core/Net ID switch (description)

Option switches on the side of the System Utility Transition card identify Core/Net
modules as “Core 0” or “Core 1. The Core ID switches are set in the factory. The
Core/Net ID settings are:
Core module ID switch settings (System Utility Transition card)

Core 0 All switches are set to ON
Core 1 Switch 1 is set to OFF
Switches 2 through 8 are set to ON
7
Network modules
These modules contain the Network equipment that provides the timeslots, or data paths,
for the transmission of voice and data signals. Each system requires a minimum of two
Network modules in addition to the Core/Net modules.
Timeslots
When analog signals are converted into digital form by the Line and Trunk cards in the
IPE modules, the data is routed to a Network card in a Network or Core/Net module.
Network cards provide timeslot paths for the electronic transmission of voice and signal
data. Each phone conversation utilizes two of these timeslots: one for each end of the
conversation.
Loops
Timeslots are organized into loops. Each loop contains 32 timeslots, 30 of which are
available for phone conversations (two timeslots are used for signaling). Each network
slot in a Network module supports 2 loops (64 total timeslots, 60 usable timeslots).
Network and Superloop cards

ENET Network cards (QPC414) provide the capacity for two loops of 60 usable
timeslots. Network cards occupy one Network slot. SNET Superloop cards (NT8D04)
provide the capacity for four loops of 120 usable timeslots. Superloop cards occupy one
slot but utilize the capacity from two adjacent Network slots. When a Superloop card is
installed, the adjacent Network slot is left empty.
Network circuit cards

OCMC: Optical Cable Management (NTRE39) - for CP PII with
Fiber Network Fabric system only
Fiber optic cable used in Network group configuration is easily damaged if bent. The
OCMC card is installed in Network modules to store and protect excess cable length. The
OCMC card ensures that the fiber cable is not bent beyond a 30 mm bend radius. The
OCMC contains no electronic components and is not powered. OCMC is a optional
single width card installed between the Power supply and slot 1 in the Network modules.
OCMC cards cannot be installed in Core/Net modules.
3PE: 3 Port Extender (QPC441)

The 3PE card extends CPU data, address, and control signals to network loops. The 3PE
cards connect to the 3PE Termination Panel in the back of the Core/Net modules. One
3PE card is installed in slot 1 of each Network module and slot 11 of each Core/Net
module.
8
FIJI Fiber Junctor Interface (NTRB33) - for CP PII with Fiber

Network Fabric system only
FIJI cards are connected with fiber optic cable to form the Dual Ring Fiber Network. This
Fiber Network provides uninterrupted voice and data communication between Network
groups. The FIJI Cards also connect to the Clock Controller cards for precise
management of voice and signal data. FIJI cards require two slots. In Network modules,
one FIJI card is installed in slots 2 and 3. In Core/Net modules, one FIJI card is installed
in slots 8 and 9.
Dual Ring Fiber Network

The Network groups communicate through the Dual Ring Fiber Network. Calls and
conversations are switched and routed across various Network groups as needed. This
Network consists of two distinct rings of fiber optic cable: one ring connects all the FIJI
cards in Network shelf 0’s while the second ring connects all the FIJI cards in Network
shelf 1’s. This network communicates on a subset of the Sonet OC12c protocol (622 Mb
bandwidth on each ring).
Intergroup switching
This Dual Ring fiber optic cable configuration provides complete non-blocking
communication between the network groups; this eliminates the incidence of busy signals
for calls switched between groups. Each FIJI card can handle 32 PCM links. A system of
eight Network groups provides 7680 timeslots for 3840 simultaneous conversations.
Redundancy
This Dual Ring network is fully redundant: each of the fiber optic cable rings is capable
of handling the traffic for an entire eight group network. If a fault in one ring is detected,
the other ring automatically takes over call processing. No calls are lost during the
switchover.
Ring states
The Dual Ring Fiber Network operates under four states
Drives Half (normal state)
• Both Rings share call processing functions.
• Traffic is shared between the two Rings.
• Each FIJI card drives 480 timeslots.
9
Per Sig: Peripheral Signaling (QPC43)

Provides a signaling interface between the CPU and IPE through the network cards.
Provides basic bit rate 2.048 MHz clock and timing signals for real-time functions. One
Per Sig card is installed in slot 4 of each Network module, and slot 10 of each Core/Net
module.
XNET: Superloop (NT8D04)

Superloop cards provide the timeslots, or data paths for the transmission of voice signals.
These cards connect to the IPE modules, which connect to the telephone lines and trunks.
Each Superloop card controls the capacity of two slots. When a Superloop card is
installed, the adjacent slot is left empty. In Network modules, up to four Superloop cards
are installed in slots 5 to 12. In Core/Net modules, three Superloop cards can be installed
in slots 0 to 7.
ENET: Network (QPC414)

ENET cards provide the same function as Superloop cards. These cards require a single
Network slot and offer half the capacity of the Superloop cards. In Network modules, the
Network cards are installed in slots 5 to 12. In Core/Net modules, the Network cards are
installed in slots 0 to 7. A combination of Network and Superloop cards can be used.
Conference/TDS card (NT8D17)

The Conference/TDS card provides conference call capability, dial tones, and
Multifrequency Sender (MFS) functionality. One Conference/TDS card is located in slot
0 of each Core/Net module.
CC: Clock Controller (QPC471 or QPC775)

The Clock Controller cards synchronize the Meridian 1 system with an external source
clock. This clock transmits timing signals to the CPU, Network groups and other
equipment for the precise management of voice and signal data.
• Two Clock Controller cards are installed in each system. In Fiber Network Fabric
network systems, the Clocks are connected to each other and to the FIJI cards in
Network group 0.
• Clock Controllers must not be installed in Network shelf 0.
• Clock Controllers in a two group system are both installed in Network shelf 1.
• Clock Controllers, where possible, are installed in different Network groups. For
example, one Clock Controller installed in a Network shelf 1. The other Clock
Controller must be installed in a Network shelf 2.
• Clock Controllers are installed in separate columns for power and cooling redundancy.
10
Intelligent Peripheral Equipment

The Intelligent Peripheral Equipment (IPE) modules contain equipment for physically
connecting phone lines and trunks to the Meridian 1 CP PII system. The equipment in
these modules converts the analog voice signals from those telephone and trunk lines into
digital data. When the analog voice and data signal is converted into digital form by the
Line or Trunk Cards in the IPE module, the signal is routed to a Network card (SNET and
ENET) in a Network module. Superloop (SNET) and Network (ENET) cards provide
timeslot paths for the electronic transmission of data. Each phone conversation utilizes
two of these timeslots: one for each end of the conversation.
IPE circuit cards
Line cards
The line cards convert analog voice signals into digital data. These cards connect to
internal telephone lines through the I/O panel on the back of the module. The external
lines are routed through the Modular Distribution Frame (MDF). Line cards are installed
in slots 0 through 15.
Trunk cards
The trunk cards convert analog voice signals into digital data. These cards connect to
external telephone trunk lines through the I/O panel on the back of the module. The
external lines are routed through the Modular Distribution Frame (MDF). Trunk cards are
installed in slots 0 through 15.
Controller card (NT8D01)

The Controller card provides the interface to the Superloop cards in the Network
modules. One Controller card is installed in the center slot of each IPE module.
11
Software Configuration
Customer Data
_______________________________________________________________________
Configuring 3903 digital set in ld 11
DES SAS
TN 020 0 05 02
TYPE 3903
CDEN 8D
CTYP XDLC
CUST 0
FDN 7000
TGAR 1
LDN NO
NCOS 1
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
SCPW 3039
SFLT NO
CAC_MFC 0
CLS TLD FBD WTA LPR MTD FNA HTA TDD HFA GRLD CRPD STSD
MWA RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG2
POD DSX VMD CMSD CCSA-CSI SWD LNA CNDA
CFTA SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTR
GPUD DPUD DNDA CFXD ARHD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ
12
UDI RCC HBTD AHA DDGA NAMA MIND PRSD NRWD NRCD
NRO DRDD EXR0 USRD ULAD RTDD RBDD RBHD PGND OCBD
FLXD FTTC MCBN
CPND_LANG ENG
RCO 0
EFD 7000
HUNT 7000
EHT 7000
LHK 1
PLEV 02
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY 00 SCR 3039 0 MARP
CPN D_LANG ROMAN
NAME Sridhar
XPLN 27
DISPLAY_FMT FIRST,LAST
16 MWK 7000
17 TRN
18 AO6
19 CFW 16 7000
13
______________________________________________________________________________________
Configuration of analog 500 set in LD - 10
DES SAS
TN 084 0 11 00
TYPE 500
CDEN 4D
CUST 0
WRLS NO
DN 1000 0 MARP
CPND
CPND_LANG ROMAN
NAME FAC-M/C-FMS
XPLN 27
AST NO
IAPG 0
HUNT
TGAR 1
LDN NO
NCOS 3
SGRP 0
RNPG 0
XLST
SCI 0
SCPW 3039
SFLT NO
CAC_MFC 0
CLS TLD DTN FBD XFD WTA THFD FND HTD ONS
LPR XRD CWD SWD MWD RMMD SMWD LPD XHD CCSA-
CSI LND TVD
CFTD SFD MRD C6D CNID CLBD AUTR
ICDD CDMD LLCN EHTA MCTD
GPUD DPUD CFXD ARHD OVDD AGTD CLTD LDTD ASCD
MBXD CPFA CPTA UDI RCC HBTD DDGA NAMA MIND
NRWD NRCD NROD CRD PRSD MCRD
EXR0 SHL ABDD CFHD
USRD BNRD OCBD RTDD RBDD RBHD FAXA PGND FTTC
PLEV 02
AACS NO
MLWU_LANG 0
FTR HOT D 0
14
Configuration of 3902 Phones
DES TELNET
TN 008 0 09 00
TYPE 3902
CDEN 8D
CTYP XDLC
CUST 0
FDN 5050
TGAR 1
LDN NO
NCOS 0
SGRP 0
RNPG 80
SCI 0
SSU
LNRS 16
XLST 0
SCPW 6190
SFLT NO
CAC_MFC 0
CLS TLD FBD WTA LPR PUA MTD FND HTD ADD HFA GRLD
POD DSX VMD CMSD SLKD CCSA-CSI SWD LNA CNDA
CFTA SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUA DPUA DNDA CFXD ARHD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
UDI RCC HBTD AHA DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3
MCBN
FDSD NOVD
CPND_LANG ENG
RCO 0
EFD 5050
HUNT 5050
EHT 5050
LHK 0
PLEV 02
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
15
DNDR 0
01 CFW 4
02 AO6
03 RNP
04 TRN
05
DATE 20 APR 2005
Configuration of 3901 phones
DES HP
TN 008 0 09 12
TYPE 3901
CDEN 8D
CTYP XDLC
CUST 0
FDN 5050
TGAR 1
LDN NO
NCOS 0
SGRP 0
RNPG 3
SCI 0
SSU
LNRS 16
XLST 0
SCPW 1111
SFLT NO
CAC_MFC 0
CLS SRE FBD WTA LPR PUA MTD FND HTD NDD
POD DSX VMD CMSD SLKD CCSA-CSI SWD LNA CNDD
CFTA SFD MRD DDV CNID MSID BFED RCBD
GPUA DPUA DNDD CFXD ARHD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD
UDI RCC HBTD AHA DDGA NAMA MIND PRSD NRWD NRCD NROD
DRDD EXR0
16
USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3
MCBN
FDSD NOVD
RCO 0
EFD 5050
HUNT 5050
EHT 5050
LHK 0
PLEV 02
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
01 TRN
02 AO6
03 CFW 4
04 RGA
05 ADL 16
DATE 29 SEP 2004
_____________________________________________________________
Configuration of Route Data Block in LD – 16
Route configured for CO lines circuit
TYPE RDB
CUST 00
ROUT 1
DES CTS
TKTP COT
NPID_TBL 0
PRIV NO
RPA NO
SAT NO
RCLS EXT
DTRK NO
17
ISDN NO
PTYP ACO
AUTO YES
ACMP NO
ICOG IAO
RANX NO
SRCH RRB
TRMB YES
STEP
ACOD 7101
TARG 02
BILN NO
OABS
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 256
FLH 510
GTO 896
GTI 896
ARP 3
SFB 3
CRD 0
TFD 0
LEXT 100
SST 30
DTD NO
SCDT NO
2 DT NO
NEDC ETH
FEDC ETH
CPDC NO
SPCT IMM
HOLD 02 02 40
SEIZ 02 02
RGFL 02 02
RVSD 08 31
ILLR 02 02
DDO NO
DRNG NO
CDR YES
18
INC NO
LAST NO
QREC NO
OAL YES
AIA YES
OAN YES
OPD YES
NDP EXC 0
CDRX NO
NATL YES
SSL
CFWR NO
IDOP NO
MUS YES
MRT 41
MR RVB
PANS YES
MANO NO
EQAR NO
FRL 00
FRL 11
FRL 22
FRL 33
FRL 44
FRL 55
FRL 66
FRL 77
OHQ NO
OHQT 00
TDET NO
TTBL 1
OHTD NO
PLEV 2
OPR NO
RCAL NO
MCTS NO
ALRM NO
ART 0
PECL NO
DCTI 0
SGRP 0
AACR NO
19
_______________________________________________________________________
_
Route configured for PRI circuit
TYPE RDB
CUST 00
ROUT 5
DES SASKENPRI
TKTP COT
NPID_TBL 0
PRIV NO
RPA NO
SAT NO
RCLS EXT
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
MODE PRA
IFC EURO
CNTY ETSI
20
SBN NO
NCNA NO
NCRD NO
ISAR NO
IEC ???
CPFXS YES
DAPC NO
INTC NO
DSEL VOD
PTYP DCO
AUTO YES
ACMP NO
ICOG IAO
RANX NO
SRCH RRB
TRMB YES
STEP 1
ACOD 0
TCPP NO
TARG
BILN NO
OABS
ICIS YES
OGIS YES
PTUT 0
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 256
FLH 510
GTO 896
GTI 896
ARP 3
SFB 3
CRD 512
NBS 2048
NBL 4096
TFD 0
LEXT 100
DTD NO
SCDT NO
21
2 DT NO
DDO NO
DRNG NO
CDR YES
INC NO
LAST YES
QREC YES
OAL YES
AIA YES
OAN YES
OPD YES
NDP EXC 0
CDRX NO
NATL YES
SSL
CFWR NO
IDOP NO
MUS YES
MRT 41
MR NO
PANS YES
EQAR NO
FRL 00
FRL 11
FRL 22
FRL 33
FRL 44
FRL 55
FRL 60
FRL 70
OHQ NO
OHQT 00
TDET YES
TTBL 1
PLEV 2
OPR NO
RCAL NO
MCTS NO
ALRM NO
ART 0
PECL NO
DCTI 0
SGRP 1
AACR NO
22
23
TYPE RDB
CUST 00
ROUT 35
DES DID 25045
TKTP DID
TW_ROUTE NO
NPID_TBL_NUM 0
SAT NO
RCLS EXT
DTRK YES
DGTP DTI2
ISDN NO
DSEL VOD
PTYP DCO
AUTO NO
DNIS NO
ICOG ICT
STEP
ACOD 1201
TARG
BILN NO
OABS
INST
IDC YES
DCNO 30 *
NDNO 30
DEXT NO
DNAM NO
MFC R2MF
INDMF YES
CLEN 10
MFCI 1
R2MD NO
SGL NO
BSSU NO
OPP NORM
SWP NORM
ICIS YES
ICNP UKWN
ICNT UKWN
ICPS YES
TIMR MFC 12032
MFO 0
MFID 0
ICF 512
OGF 512
24
EOD 3968
DSI 34944
NRD 3968
DDL 70
ODT 4096
RGV 256
FLH 510
GTO 896
GTI 896
SFB 3
IENB 5
TFD 0
VSS 0
VGD 6
SST 5 0
SCDT NO
2 DT NO
PAGE 002
NEDC ETH
FEDC ETH
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR YES
INC YES
LAST NO
QREC NO
OAL YES
AIA NO
OAN YES
OPD NO
NDP EXC 0
CDRX NO
NATL YES
CFWR NO
IDOP NO
VRAT NO
MUS YES
MRT 80
PANS YES
25
RACD NO
MANO NO
FRL 0 0
FRL 1 1
FRL 2 2
FRL 3 3
FRL 4 4
FRL 5 5
FRL 6 6
FRL 7 7
OHQ NO
OHQT 00
TTBL 1
PNNC NO
ATAN NO
OHTD NO
PLEV 2
OPR NO
RCAL NO
MCTS NO
ALRM NO
BTT 30
NCNI 0
CNIE NO
CNIT NO
CTAT YES
ART 1
OPDL 0
PECL NO
DCTI 0
TIDY 1201 35
NADT 0
SGRP 0
AACR NO
_______________________________________________________________________
_
26
Configuration of Trunks in LD – 14
Trunk configured for CO circuit
TN 020 0 00 00
TYPE COT
CDEN 8D
CUST 0
XTRK EXUT
FWTM NO
TIMP 600
BIMP 600
AUTO_BIMP NO
TRK ANLG
NCOS 3
RTMB 11
ATDN 7001
SIGL LOP
SUPN YES
STYP PIP
AST NO
IAPG 0
SEIZ NO
CLS UNR DTN CND WTA LPR APN THFD BARD CLID
P10 NTC LOL
_______________________________________________________________________
_
27
Trunk configured for PRI circuit
TN 058 30
TYPE COT
CDEN SD
CUST 0
TRK PRI2
PDCA 1
PCML A
NCOS 3
RTMB 5 30
B-CHANNEL SIGNALING
ATDN 7001
AST NO
IAPG 0
CLS UNR DTN CND WTA LPR APN THFD BARD CLID
P10 VNL
Configuration of DTI Trunk.
DES DID 25045XXX

TN 018 04
TYPE DID
CUST 0
TRK DTI2
SICA 1
PDCA 1
PCML A
NCOS 0
RTMB 35 4
NITE
AST NO
IAPG 0
CLS UNR MFC CND WTA LPR APN THFD BARD CLID
P10
MFL 0
MFPD NO
28
TKID
DTCR NO
DATE 10 APR 2004
_______________________________________________________________________
_
Defining PRI D-Channel in LD – 17
DCHL(D-Channel loop) 58 should be defined in LD – 17 CEQU (Common Equipment)

before configuring the D-Channel.
ADAN DCH 15
CTYP MSDL
GRP 1
DNUM 15
PORT 0
DES PRA1
USR PRI
DCHL 58
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC EURO
CNTY ETSI
ISDN_MCNT 300
CLID OPT1
PROG NCHG
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
MBGA NO
OVLR NO
OVLS NO
T310 120
INC_T306 120
OUT_T306 120
T200 3
T203 10
N200 3
N201 260
K 7
29
Configuring scheduled data block ACD in LD 23
TYPE SCB
CUST 0
CPRD 01 01 12 31
SHR 0
EHR 23
DOW 1 2 3 4 5 6 7
RFRQ 3
SFRQ 1
ROPT 1 2 3 4
PRIO
PAGE NO
AID YES
IDLB 1111
IDUB 9999
LOG 30
SRPT YES
TOT4 YES
Configuring of ACD
TYPE ACD
CUST 0
ACDN 9701
MWC NO
DSAC NO
MAXP 100
SDNB NO
BSCW NO
ISAP NO
AACQ NO
RGAI NO
ACAA NO
FRRT
SRRT
NRRT
FROA NO
NCFW
FNCF NO
CWTT NONE
HMSB YES
ACPQ NO
30
FORC NO
RTQT 0
SPCP YES
OBTN NO
RAO NO
CWTH 1
NCWL NO
BYTH 0
OVTH 2047
TOFT NONE
HPQ NO
OCN NO
OVDN
IFDN
OVBU LNK LNK LNK LNK
EMRT
MURT
RTPC NO
STIO
TSFT 20
HOML YES
RDNA NO
NRAC NO
DAL NO
RPRT YES
RAGT 4
DURT 30
RSND 4
FCTH 20
CRQS 100
IVR NO
CWNT NONE
31
Configuring of CDN
TYPE CDN
CUST 0
CDN 5230
FRRT
SRRT
FROA NO
MURT
DFDN 9427
CEIL 2047
OVFL NO
TDNS NO
RPRT YES
AACQ YES
ASID 16
SFNB
USFB 1 3 4 5 6 7 9 10 11 12 13 14 15
CALB 0 1 2 3 4 5 6 8 9 10 11 12
CNTL YES
VSID
HSID
CWTH 1
BYTH 0
OVTH 2047
STIO
TSFT 20
Configuring Network Class Of Service & FCR In LD – 87 & LD – 49
Creation of NCOS – 0 in LD – 87
FEAT nctl
NRNG 0
SOHQ NO
SCBQ NO
NCOS 0
EQA NO
FRL 0
RWTA NO
OHQ NO
CBQ NO
32
SPRI 0
MPRI 0
PROM 0
_______________________________________________________________________
_
FEAT nctl
NRNG 1
SOHQ NO
SCBQ NO
NCOS 1
EQA NO
FRL 1
RWTA NO
OHQ NO
CBQ NO
SPRI 0
MPRI 0
PROM 0
_______________________________________________________________________
_
FEAT nctl
NRNG 2
SOHQ NO
SCBQ NO
NCOS 2
EQA NO
FRL 2
RWTA NO
OHQ NO
CBQ NO
SPRI 0
MPRI 0
33
PROM 0
_______________________________________________________________________
_
FEAT nctl
NRNG 3
SOHQ NO
SCBQ NO
NCOS 3
EQA NO
FRL 3
RWTA NO
OHQ NO
CBQ NO
SPRI 0
MPRI 0
PROM 0
_______________________________________________________________________
_
Configuring of Flexible Code Restriction ( FCR ) In LD - 49
TYPE fcr
CUST 0
CRNO
CRNO 0
INIT DENY
CRNO 1
INIT ALOW
DENY 95
0
34
CRNO 2
INIT ALOW
DENY 00
CRNO 3
INIT ALOW
_______________________________________________________________________
35
Customer Data Block Creation In LD – 15
AML Data Creation
AML_DATA
OPT DNI
VSID 6
GP02
GP03
GP04
GP05
GP06
GP07
GP08
GP09
GP10
GP11
GP12
GP13
GP14
GP15
_______________________________________________________________________
_
ANI Data Creation
ANI_DATA
ANAT 1111
ANLD 111
_______________________________________________________________________
_
36
ATT Data Creation
ATT_DATA
OPT ABDA AHA BIND BIXA BLA BOHD DRE
DNI DRE FACA IC2 XTG IDP XLF XBL
FKA MCTD NCD CUI MWUD LOD PSD RECA
REA SYA SLD SIAD THPD ATDA
ATDN 9
NCOS 3
CWUP YES
CWCL 16
CWTM 06
CWBZ YES YES
MATT NO
RTIM 30 30 30
ATIM 0
AQTT 30
AODN 1335
SPVC 00
SBLF NO
RTSA RSAD
SACP NO
ABDN NO
IRFR NO
XRFR NO
ADHT 0
IDBZ NO
PBUZ 02 10
ICI 00 IAT
ICI 01 IEN
ICI 02 INT
ICI 03
ICI 04
ICI 05
ICI 06
ICI 07
ICI 08
ICI 09
ICI 10
ICI 11
ICI 12
ICI 13
_______________________________________________________________________
_
37
CCS Data Creation
CCS_DATA
CCRS SRE
ECC1 SRE
ECC2 SRE
CNCS 0
PELK NO
_______________________________________________________________________
_
CDR Data Creation
CDR_DATA
CDR YES
IMPH NO
OMPH NO
AXID NO
TRCR YES
CDPR NO
ECDR NO
BDI NO
OTCR YES
PORT 23
CNI DGTS
BCAP NO
CHLN 0
FCAF NO
_______________________________________________________________________
_
FFC Data Creation
FFC_DATA
CCRS SRE
SCPL 4
SBUP YES
FFCS NO
STRL 0
STRG
ADLD 0
38
_______________________________________________________________________
_
FTR Data Creation
FTR_DATA
OPT ABDA AHA BIND BIXA BLA BOHD CFO CFRD
COX CPD CTD DBD DNI DSX DRE
DSTD FACA HTU HVD XBL IC2 IDP XLF
IHD XTG FKA LOD LRA MCI MCTD CUI
MWUD NCD PCMD PSD PVCA RECA REA RND
RTR RTD ROX SBD SDDE SIAD SLD SYA
THPD TTAD VOBD CWRD HLPD HRLD
CXOD
DGRP 0
IRNG NO
PKND 1
DNDL NO
SPRE 8886
LINK NO
PREO 0
BPSS NO
SRCD 9001
EEST YES
DTMF YES
EESD YES
TTBL 1
MUS YES
MUSR 41
HCC NO
RECD NO
PORT 0
TFDR NO
RPA NO
MCDC NO
NAUT NO
IDEF NO
MTAR NO
LEND NO
MSCD NO
CPCI NO
CONF_DSP
CNFFIELD NO
CNF_NAME CONF
INTFIELD NO
_______________________________________________________________________
_
39
IMS Data Creation
IMS_DATA
IMS YES
IMA YES
APL NONE
UST YES
APL NONE
UMG YES
APL NONE
_______________________________________________________________________
_
NET Data Creation
NET_DATA
OPT RTD
AC2
FNP YES
ISDN YES
PINX_DN
MBG 0
BSGC 65535
PFX1
PFX2
HLOC
LSC
RCNT 5
PSTN YES
TNDM 15
PCMC 15
SATD 1
OCLI NO
DASC
DITI NO
TRNX NO
EXTT NO
FTOP FRES
APAD 0 0
VNR NO
NIT 8
FOPT 14
CNIP YES
_______________________________________________________________________
_
40
NIT Data Creation
NIT_DATA
NIT1 8887
TIM1
NIT2
TIM2
NIT3
TIM3
NIT4
TIM4
RPNS NO
ENS NO
_______________________________________________________________________
_
RDR Data Creation
RDR_DATA
OPT CFO CFRD DSTD PVCA CWRD
FNAD FDN
FNAT FDN
FNAL FDN
CFTA NO
CCFWDN
CFN0 4
CFN1 4
CFN2 4
DFN0 4
DFN1 4
DFN2 4
DNDH NO
MDID NO
NDID NO
MWFB NO
TRCL 0
DFNR 0
CRT0 00 00 00 00
CRT1 00 00 00 00
CRT2 00 00 00 00
CRT3 00 00 00 00
DAY0
DAY1
______________________________________________________________________
_
41
Configuring Operator Console In LD – 12
TN 024 0 04 00
TYPE 2250
CDEN 8D
CTYP XDLC
CUST 0
SGRP 0
SETN 024 0 04 01
ANUM 03
IADN
ALPD NO
SSU
ICDR ICDD
ABAN ABDD
CPND CNDA
AADN
DNDI DNDA
DAPC DAPA
LANG 00
KEY 00 BVR
KEY 01 BIN
KEY 02 BKI
KEY 03
KEY 04
KEY 05 EES
KEY 06 MDT
KEY 07 MTM
KEY 08
KEY 09
KEY 10
KEY 11
KEY 12
KEY 13
KEY 14
_______________________________________________________________________
_
42
Configuring Flexible Feature Codes ( FFC ) In LD – 57

TYPE ffc
CUST 0
CODE all
CUST 00
FFCT YES
ASRC *40
AUTH *80
CFWA #1
CFWD #1
ELKA *78
ELKD *79
PLDN 8000
USE GPHT
LSNO 4
HTYP RRB
CFWI NO
MQUE ALL
PLDN 8887
USE GPHT
LSNO 3
HTYP LIN
CFWI NO
MQUE ALL
HOLD #4
RCFA *71
RCFD *72
RCFV *73
SCPC *77
SPCC #2
SPCU #3
CPP *99
_______________________________________________________________________
_
43
Configuring Authorization Data Block In LD – 88
TYPE aub
CUST 0
SPWD xxxx
CUST 00
ALEN 04
ACDR NO
AUTHCOD_ALRM OFF
ACLE NO
BRST 00
AUTO NO
CLAS 000 001 002 003
COS CTD TLD TLD TLD
TGAR 01 00 00 00
NCOS 00 01 02 03
After the Authorization Data Block (AUB) is created Authorization Codes (AUT) are
configured in the same overlay LD – 88.
• Auth Codes (AUT) with Class Code (CLAS) “000” will not allow any external
calls. Only internal calls can be made.
• Auth Codes (AUT) with Class Code (CLAS) “001” will allow only local calls.
• Auth Codes (AUT) with Class Code (CLAS) “002” will allow local and STD
calls.
• Auth Codes (AUT) with Class Code (CLAS) “003” will not have any restrictions.
Sets with Auth Code having Class Code will be able to make local, STD and ISD
calls.
For configuring set based authorization codes, the class of service (CLS) AUTR
(Restricted Authorization Code) should be enabled while programming a set. The CLS
AUTR will enable maximum of 6 auth codes to be used from a set. The Auth Codes can
be assigned to the sets by giving the command MAUT (Modify Auth Code) at the prompt
ITEM while programming a set.
_______________________________________________________________________
_
44
Configuring Group Hunt In LD – 18
TYPE ght
LSNO
GHLN 0001
GHT
PLDN 8888
DNSZ 4
STOR 0 1007
GHLN 0003
GHT
PLDN 8887
DNSZ 4
STOR 0
STOR 1 1333
STOR 2 1335
GHLN 0004
GHT
PLDN 8000
DNSZ 16
STOR 00 6000
STOR 01 6001
STOR 02 6002
STOR 03 6003
STOR 04 6004
STOR 05 6005
STOR 06 6006
STOR 07 6007
After a GHT is created in LD – 18 a Pilot DN (PLDN) needs to be configured in

LD – 57. The pilot number created in LD – 57 should be referred to the GHT List
Number (LSNO).
Configuring PLDN In LD – 57
45
TYPE ffc
CUST 0
CODE pldn
CUST 00
FFCT YES
PLDN 8000
USE GPHT
LSNO 4
HTYP RRB
CFWI NO
MQUE ALL
The PLDN 8000 is created for accessing the RAS (Remote Access Server) which hunts a
group of 8 DNs. All these 8 extension numbers are connected to individual modems in
the IT-Operations Network Room.
Users who want to access the RAS will have to dial the fac-Z pilot number followed by
the RAS hunt number 8000.
Configuring of short Dialing for external calls
LD 87(cdp,dsc) LD 86 (RLB),(DGT) E.g.: short dialing of 1001=00441452569135
Create a digit manipulation index
Ld 86
REQ new
CUST 0
FEAT dgt
DMI 40
DMI 40
DEL 4
INST 00441452569135
CTYP NCHG
REQ new
CUST 0
FEAT dgt
DMI 44
DEL 4
INST 888441452569135
46
CTYP NCHG
REQ prt
CUST 0
FEAT rlb
RLI 44
ENTR 0
LTER NO
ROUT 33 Onnet route No
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 0
DMI 44
FCI 0
FSNI 0
BNE NO
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO
ENTR 1
LTER NO
ROUT 36 Onnet route No
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 0
DMI 44
FCI 0
FSNI 0
BNE NO
47
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO
ENTR 2
LTER NO
ROUT 75 PSTN route No
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 0
DMI 40
FCI 0
FSNI 0
BNE NO
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0
REQ new
CUST 0
FEAT cdp
TYPE dsc
DSC 1001
FLEN 4
DSP LSC
RRPA NO
RLI 44
48
NPA
NXX
System Data
Setting System Date & Time in LD - 2
To print the current time and date

TTAD day-of-week day month year hour minute second
49
Example
TTAD WED 24 11 1976 15 41 49
To set the time and date:

STAD DAY MONTH YEAR HOUR MINUTE SECOND
Example
STAD 24 11 1976 15 41 49
Note: Except for the year, the other entries in the time of day output are 2-digit numbers.
The year may be any year from 1901 to 2099 inclusive. It may be input as a full 4-digit
field or as a 2-digit short form. The 2-digit short form is assumed to be in the range 1976
to 2075 and the appropriate addition is made when calculating the day-of-week and leap
years.
_______________________________________________________________________
_
Configuring Superloop Data Block In LD – 97

Prompt Response Comment
REQ aaa Request (CHG, END, PRT)
TYPE SUPL Type = SUPL (Superloop)
SUPL 0-156
0-252
Superloop number in multiples of 4
Option 81C with Fiber Network Fabric
SLOT a Network Card is in Left or Right Slot (x = (L) or R)

SUPT aaaa Superloop type (aaaa = (STD), CARR, or FIBR)
50
XPE0 xyz Extended Peripheral Equipment controller 0 (STD)

XPE1 xyz Extended Peripheral Equipment controller 1 (STD)
XPEC 1-95 Extended Peripheral Equipment Controller
TYPE supl
SUPL
SUPL SUPT SLOT XPEC0 XPEC1
004 STD LEFT 04 0 3 -- - - (004 to 084 are Superloop Numbers)
008 STD LEFT 06 0 3 -- - - (01 to 07 are IPE numbers)
020 STD LEFT 01 0 3 -- - - (0 – 3 is IPE segment number)
024 STD LEFT 02 0 3 -- - -
052 STD LEFT 03 0 3 -- - -
068 STD LEFT 07 0 3 -- - -
084 STD LEFT 05 0 3 -- - -
TYPE xpe
XPEC
S0 S1 S2 S3 LOC DIS R GTP
01 020 020 020 020 NO 08
02 024 024 024 024 NO 08
03 052 052 052 052 NO 08
04 004 004 004 004 NO 08
05 084 084 084 084 NO 08
06 008 008 008 008 NO 08
07 068 068 068 068 NO 08
After the superloops are configured in LD – 97, they are enabled in LD – 32. The
following are superloop commands used in LD – 32 to enable the S-NET card and the
IPE shelf.
ENLL sl Enable specified Superloop

ENXP x Enable Controller x and associated PE cards, download software
ENXP XPC x Enable Controller x, do not enable the associated PE cards,
download software
51
Configuring TTY Ports In LD - 17
TTY Port “0” created for CPU-0
ADAN TTY 0
CTYP QSDI
GRP 0
DNUM 0
DES
FLOW NO
USER MTC
XSM YES
TTYLOG 0
BANR YES
This port is configured for communication with the PBX through CPU-0
_______________________________________________________________
TTY Port “1” created for OA & M
ADAN TTY 0
CTYP QSDI
GRP 0
DNUM 0
DES
FLOW YES
BCST YES
USER MTC TRF SCH CTY BUG
XSM NO
TTYLOG 0
BANR YES
This port is configured for Office Administration & Maintenance
_________________________________________________________
TTY Port “2” created for Manoj’s Call Billing
52
ADAN TTY 2
CTYP QSDI
GRP 0
DNUM 2
DES CDR
FLOW YES
BCST YES
USER CTY
XSM NO
This port is configured for sending CDR required for Manoj’s Billing Software
_________________________________________________________________
TTY Port “3” created for Com-South Call Billing
ADAN TTY 3
CTYP QSDI
GRP 0
DNUM 3
DES CDR-COMSOUTH
FLOW YES
BCST YES
USER CTY
XSM NO
This port is configured for sending CDR required for COM-SUOTH Billing Software
_______________________________________________________________________
_
TTY Port “4” created for CPU – 1
53
ADAN TTY 4
CTYP CPSI
DNUM 4
PORT 0
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC TRF SCH BUG
XSM NO
TTYLOG 0
BANR YES
This port is configured for communication with the PBX through the CPU-1
________________________________________________________________
PTY Port “9” created for Ethernet ( Communication via LAN)
ADAN TTY 9
CTYP PTY
DNUM 9
PORT 0
DES ethernet
FLOW NO
USER MTC SCH BUG
XSM NO
TTYLOG 0
BANR YES
For communicating with the PBX through LAN, a Pseudo Terminal (PTY) should be
configured. This PTY port will be used while communicating with the PBX through
LAN.
_______________________________________________________________________
_
Configuring System Timers In LD – 73
54
Prompt Response Comment

REQ aaa Request (aaa = CHG, END, NEW, OUT, or PRT)
TYPE aaaa Type (aaaa = DTI2, PRI2, or JDMI)
FEAT SYTI Feature = SYTI (System timers)
CLKN xx Card number for Clock Controller
CC0 xx Card number for Clock Controller 0
PREF CK0 1-9 Card number of DTI2/PRI2/SILC containing the primary
clock reference for the main cabinet
SREF CK0 1-9 Card number of DTI2/PRI2/SILC containing the secondary
clock reference for the main cabinet
clock reference for IP expansion cabinet 1
CCGD 0- (15)-1440 Clock Controller free run Guard time
CCAR 0- (15) Clock Controller Audit Rate
EFCS (NO) YES Enable Fast Clock Switching
SYTI configured for PRI circuit in LD - 73
55
TYPE pri2
FEAT syti
PREF CK0 58
SREF CK0 58
PREF CK1 58
SREF CK1 58
CCGD 7
CCAR 5
EFCS YES
After the System Timer (SYTI) is configured in LD – 73, the primary clock reference is
locked to the PRI loop by giving the command TRCK PCK in LD – 60.
_______________________________________________________________________
_
Creation of PAD table for PRI circuit

PDCA 2
PRI2/BRIT/BRIL PDCA
ONP 17 0
OPX 17 0
DTT 0 0
DCO 0 0
NTC 4 1
TRC 4 1
DTR 0
VNL 4 1
ACO 4 1
AFX 4 1
ADD 4 1
PRI 0 0
DSET 6 0
BRIL 0 0
BRIT 0 0
WRLS 0 0
_______________________________________________________________________
_
56
Creation of Loop Timer (LPTI) for PRI circuit
TYPE pri2
FEAT lpti
LOOP 58
MFF AFF
ACRC NO
ALRM REG
RAIE NO
G1OS YES
SLP 255 1S 255 1S
BPV 128 122
CRC 201 97
FAP 28 1
RATS 10
GP2 255 1S 1S 1S 1S
MNG1 1M
NCG1 1M
OSG1 1M
MNG2 1M
NCG2 1M
OSG2 1M
PERS 50
CLRS 50
OOSC 5
Interfacing the PBX to LAN in LD - 117
57
LD 117 uses a command line input interface (input parser) which has the following
general structure (where “=>” is the command prompt). The following commands are
used for defining the IP address and the Subnet Mask.
NEW HOST PRIMARY_IP 10.1.0.251

NEW HOST SECONDARY_IP 10.1.0.252 (for Dual CPU only)
NEW HOST GATEWAY_IP 10.1.0.1
CHG MASK 255.255.255.0
Verify the IP address for Ethernet by entering the command PRT ENLK and verify host
and subnet mask setting by entering the command PRT HOST and PRT MASK
respectively.
IP address and subnet mask configured for the PBX
=> prt host
ID Hostname IP Address
1 LOCAL_PPP_IF 137.135.192.4
2 REMOTE_PPP_IF 100.1.1.1
3 SUBNET_ MASK 255.255.255.0
4 PRIMARY_IP 10.1.0.251
5 SECONDARY_IP 10.1.0.252
6 GATEWAY_IP 10.1.0.1
=> prt mask
SUBNET MASK: "255.255.240.0"
After all the IP addresses and the Subnet mask are appropriately entered, the ethernet link
should be enabled in LD – 137 using the command ENL ENLK. This command enables
the ethernet link on the active IOP pack. The status of the ethernet link can be obtained by
giving the command STAT ELNK in LD – 137.
Creation of TONE table in -LD 56

54
Flexible Tones and Cadences
58
Flexible Tones and Cadences (FTC) is an optional feature which is used to customize the
tones provided to telephone users. FTC is primarily intended for international markets
where tones which are different from the North American defaults are required.
Overlay program 56 allows the implementation and administration of tone and ringing
parameters for one or more customers. If the FTC feature (package 125) is not equipped,
North American tones and cadences are used. An FTC table number can be entered for
each trunk route at prompt TTBL in LD 16. Table 0 is the default for all trunk routes and
contains the defaults for North America.
What are tones and cadences?

Tones are used to provide call status to telephone users. A tone is defined by both the
frequency and volume of the sound. Tones are provided in on and off phases. One or
more cycles of on/off cycles make up a tone's cadence. For example, the default cadence
for normal North American ringing is 2 seconds on, 4 seconds off, 2 seconds on, 4
seconds off, and so on.
Flexible Tone and Cadence (FTC) Tables

FTC tables define the tones and cadences used for various calling features. Up to 31 FTC
tables can be created. Each table can be associated with one or more trunk routes by
entering the table number in response to prompt TTBL in LD 16.
Master Cadence Table (MCAD)

The Master Cadence Table (MCAD) defines cadences that are controlled by software.
These are used for single line sets (500/2500) and digital sets. The MCAD can have 256
entries (0-255). Each entry can have up to 10 on/off phases each. Entry 0 is reserved for
continuous tone and cannot be changed. Entries 1-15 are reserved for ringing cadences.
Most of the software cadences are continuously repetitive unless it is specified that the
tone should end after the last phase.
TDS and NT8D17 Conference/TDS/MFS cards

There are two types of cards providing tones and cadences
• Tone and Digit Switch (TDS) cards
• NT8D17 Conference, TDS and Multi-Frequency (MF) Sender card
There are a variety of TDS cards. Each card provides a different set of tones and
cadences. When a TDS card is used for SL-1 sets, each tone and cadence is identified by
a hexadecimal code. The decimal equivalents for these hex codes are entered at the
TDSH prompt for each calling feature.
When the NT8D17 Conference/TDS/MFS cards are used, the tones and cadences are
defined by the following prompts
• XCAD = 0-255 - entry in the Firmware Cadence Table (FCAD)
• XTON = 0-255 - tone stored in the card firmware
• CDNC = 0-255 - entry in Master Cadence Table (MCAD)
The ringing cadences for all telephones use the Master Cadence Table (MCAD). MCAD
entries 1-15 are downloaded to the Peripheral Controller to provide ringing.
59
Tone Table Configured In LD – 56

DIAL
XTON 105
XCAD 000
SPCL
XTON 106
XCAD 000
CDT
XTON 008
XCAD 000
CFDT
XTON 100
XCAD 000
MWDT
XTON 004
XCAD 017
CFMW
XTON 004
XCAD 018
BUSY
XTON 158
XCAD 017
60
Meridian Mail
Maintenance Data
61
Meridian Mail
General description
Introduction Meridian Mail is a comprehensive voice processing system
designed for use with Nortel (Northern Telecom)Meridian 1Communication
Systems.
Basic features
Each Meridian Mail user is assigned a private voice mailbox number which
is set up by the administrator. Users log on to their mailboxes using a
password which they create it.Using simple commands at the keypads on
their touch tone telephones, users can compose and listen to voice
messages,and perform general messaging functions such as replying
to,forwarding, and deleting messages.
Meridian Mail can be integrated with the call-processing capabilities of your

switching system to provide messaging features such as Call Answering and
Voice Messaging.
Call Answering prompts callers to leave messages when there is no answer
or the extension is busy; Voice Messaging allows users to compose messages
to, and receive composed messages from, other Meridian Mail users.
In all its applications, Meridian Mail provides recorded prompts to guide the
inexperienced user. These prompts remind the user of available functions
and provide instructions suited for novices. The system detects delays in
user input and supplies additional information to assist the hesitant user.
Optional services
In addition to the basic features, the following optional services are

available:
Networking
62
• Meridian Networking (MMUI)

• Enterprise Networking (MMUI)
• Virtual Node AMIS (MMUI)
• Network Message Service (MMUI for single-customer,
Meridian 1 systems only)
• AMIS Networking (MMUI and VMUIF)
Multimedia
• Voice Menus
• Voice Forms
• Fax on Demand
• Meridian ACCESS
Optional services can be tailored to the needs of Meridian Mail users.
Administration
Meridian Mail is administered through a simple, menu-driven administrative

interface available at a terminal or personal computer (PC). Using the
administration menus, the administrator performs the initial configuration of
the Meridian Mail system, maintains the user information base, creates voice
applications such as announcements and Voice Menus, and monitors system
usage and performance. The administrator also uses the menus to perform
routine maintenance on the system. If you have a Multi-customer system,
the administrative tasks can be assigned to several administrators. For
example, a system administrator would be responsible for setting up both the
Meridian Mail system and customer groups to meet specific requirements
and preferences.
To maintain the customers on the system, a customer administrator may

then be assigned to each customer or a group of customers. Of course, you
may still have just one administrator overseeing the whole system. In this
case, the administrator would perform both system and customer
administration tasks.
In the option 81c the ACDN has to be created in LD 23.
REQ new
63
TYPE acd
CUST 0
ACDN
TYPE ACD
CUST 0
ACDN 7000 THIS IS MAIN HUNT NUMBER FOR VMAIL
MWC YES
IMS YES
CMS YES
IMA YES
IVMS YES
EES YES
VSID 6 THE VAS ID NUMBER
UST NO
UMG NO
MAXP 48 MAXIMUM PORT ASSIGNMENT
SDNB NO
ISAP NO
AACQ NO
ALOG YES
RGAI NO
ACAA NO
FRRT
SRRT
NRRT
FROA NO
NCFW 9
FNCF NO
CWTT NONE
HMSB YES
ACPQ NO
FORC NO
RTQT 0
SPCP NO
OBTN NO
RAO NO
CWTH 1
NCWL NO
64
BYTH 0
OVTH 2047
TOFT NONE
HPQ NO
OVDN
IFDN
EMRT
MURT 41
IVR NO
The terminal number (TN) will be created in LD –11
REQ : new
DES MMAIL
TN 034 0 02 00
TYPE SL1
CDEN DD
CUST 0
KLS 1
FDN
TGAR 0
LDN NO
NCOS 0
SGRP 0
RNPG 0
SCI 0
SSU
XLST
SCPW
SFLT NO
65
CAC_MFC 0
CLS UNR FBD WTA LPR MTD FND HTD NDD
MWD RMMD SMWD AAD IMA XHD IRD NID OLD VCE
POD DSX VMA CMSD CCSD SWD LND CNDD
CFTD SFD MRD DDV CNID MSID BFED RCBD
GPUD DPUD DNDD CFXD ARHD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID
UDI RCC HBTD AHD DDGA NAMA MIND PRSD NRWD
USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD
HUNT
PLEV 02
SPID NONE
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY 00 ACD 7000 0 7501
AGN
01 SCN 7801 0 MARP
02 MSB
03 NRD
04 AO3
05 TRN
06 RLS
07 RLS
08 RLS
09 RLS
The following TN’s created for Mmail:--
Sl.no TN ACD DN SCN
1 034-0-02-00 7000 7801

2 034-0-02-01 7000 7802
66
3 034-0-02-02 7000 7803

4 034-0-02-03 7000 7804
5 034-0-02-04 7000 7805
6 034-0-02-05 7000 7806
7 034-0-02-06 7000 7807
8 034-0-02-07 7000 7808
9 034-0-03-00 7000 7809
10 034-0-03-01 7000 7810
11 034-0-03-02 7000 7811
12 034-0-03-03 7000 7812
Sl.no TN ACD DN SCN
13 034-0-03-04 7000 7813

14 034-0-03-05 7000 7814
15 034-0-03-06 7000 7815
16 034-0-03-07 7000 7816
17 034-1-02-00 7000 7825
18 034-1-02-01 7000 7826
19 034-1-02-02 7000 7827
20 034-1-02-03 7000 7828
21 034-1-02-04 7000 7829
22 034-1-02-05 7000 7830
23 034-1-02-06 7000 7831
24 034-1-02-07 7000 7832
In loop number 35 the TN’s are as follows:--
Sl.no TN ACD DN SCN
1 035-0-02-00 7000 7833

2 035-0-02-01 7000 7834
3 035-0-02-02 7000 7835
67
4 035-0-02-03 7000 7836

5 035-0-02-04 7000 7837
6 035-0-02-05 7000 7838
7 035-0-02-06 7000 7839
8 035-0-02-07 7000 7840
The AML link creation is in LD 17
REQ PRT
Type ADAN
ADAN AML 6
CTYP ESDI
GRP 0
DNUM 6
DES MMail
BPS 4800
CLOK INT
IADR 003
RADR 001
T1 10
T2 000
T3 040
N1 128
N2 08
K 7
RXMT 05
CRC 10
ORUR 005
ABOR 005
68
The meridian adminstration console looks as follows:-
Logon/Status
MMM MMMERIDIAN
MMMMM MMMMM
MMMMMM MMMMMM
MMM MMM MMM MMM MMM MMMAIL
MMM MMMMM MMM MMMMM MMMMM
MMM MMM MMM MMMMMM MMMMMM
MMM MMM MMM MMM MMM MMM
MMM MMM MMM MMMMM MMM
MMM MMM MMM MMM MMM
MMM MMM MMM MMM
MMM MMM MMM MMM
MMM MMM MMM MMM
MMM MMM MMM MMM
MMM MMM MMM MMM
Copyright (c) Nortel Networks, 1999

ﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄ
Select a softkey >
Logon System Status Silence Alarm DSP Port

Status
Logon using sy ste m and the password is net sol
The main menu appears as below
69
Main Menu
1 User Administration
2 General Administration
3 Voice Administration
4 Hardware Administration
5 System Status and Maintenance
6 Operational Measurements
7 Class of Service Administration
8 Bulk Provisioning
The mailbox user creation as follows:--
User Administration
1 Local Voice User
2 Directory Entry User
3 Distribution Lists
Select an item >
User Administration
To display the List of Local Voice Users select

the Find softkey followed by the List softkey.
WARNING: If the switch software release is X11R19 or later and
70
the IMA feature on the switch is enabled then the Administration of mailboxes
can also be performed on the switch. Any additions, modifications, or deletions
of mailboxes done via Meridian Mail Administration could be overridden by the
switch administration of these same mailboxes.
Select a softkey >
Exit Add View/Modify Delete Find
The example one user given below
User Administration
View/Modify Local Voice User
Mailbox Number: 1395 Volume ID: 202
Storage Used: 0
Last Name: sasken
First Name: Initials:
Department:
Class of Service: Personal 001_COS1 002_COS2

(Use More Detail Key)
Primary DN: 1395
Extension DNs:
Revert DN: 9
Message Waiting Indication DNs: 1395
Personal Verification Recorded (Voice): No
Monitor Mailbox during Monitoring Period: No Yes
Disable Message Reception: No Yes Yes_if_TAG_Recorded
Revert if Message Reception Disabled: No Yes
Name Dialable by External Callers: No Yes
71
Logon Status: Disabled Enabled
Session Default Playback Speed: Normal Level1 Level2 Level3
Speed changed via Telset applies to: CurrentMsg AllMsgs WholeSession
Session Default Volume Level: Normal Level1 Level2 Level3
Volume changed via Telset applies to: CurrentMsg AllMsgs WholeSession
Invalid Logon Attempts: 0
Time of Last Logon: 10/01/01 10:41
Internal Personal Greeting Recorded: No
External Personal Greeting Recorded: No
Temporary Absence Greeting Recorded: No
Password Last Changed: 9/18/01 12:36

Save Cancel More Detail Change Voice

Password
The general administration for the back up and changing time- date
General Administration
1 General Options
2 Volume and Selective Backup
3 Restore from Selective Backup
4 Change System Administrator Password
5 Change PC Application Password
6 Change System Time
7 Dialing Translation
72
Select an item >
Enter a number in the range 1 to 7.
Exit
For the backup procedure on tape using the existing tape drive:-
General Administration
Volume and Selective Backup
Volume Use Volume Size Usage(%Full) Number of

Name Data Voice Data Voice Mailboxes
(KBytes) (KBytes) (hh:mm)
VS1 System 35904 29696 3:39 52 1 0
VS2 Users 8160 219776 26:57 14 20 202
VS202 Users 9856 204672 25:05 25 25 670
Selective Messages&PDLs
Selective Services
Total number of mailboxes on the system 872
Move the cursor to the desired items and press the space bar to select.
Exit Backup Backup Backup view/Delete Schedule

To Tape To Disk Status
73
Voice Administration as follows:--
Voice Administration
1 Voice Messaging Options
2 Voice Security Options
3 Restriction/Permission Lists
4 Voice Services Administration
5 Voice Form Definitions
6 Outcalling Administration
7 Remote Notification Class of Service Administration
Select an item >
Exit
74
Voice Services Administration
1 Voice Services-DN Table
2 Voice Services Profile
3 Announcement Definitions
4 Thru-Dial Definitions
5 Time-of-Day Control Definitions
6 Voice Menu Definitions
Select an item >
Enter a number in the range 1 to 6.

exit Set Display Find Subset of Options
VSDNs/Services
The Thru-dail management is as follows:--

Thru-Dial Definitions
ID Title
101 WelcomeMessage
201 welcome greeting
Move the cursor to the item and press the space bar to select.
Exit Add View/Modify Delete Find
75
The thru dial example is given below:--

View/Modify a Thru-Dial Definition
Thru-Dial ID: 101 Title: WelcomeMessage
Revert DN: 9#
Access Password: Update Password: 123456
Monitor this service during monitoring period: No Yes
Greeting Recorded (Voice): Yes
Dial by: Number
DN Length: Variable Fixed

Digits: 4 Left Pad: Suppress Prompt: No Yes
Restriction/Permission Set: 0 List Name: Custom
Restriction Codes:
Permission Codes:
Select a softkey >
ﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄ
Save Cancel Voice
voice Services-DN Table created as below:---
DN Service ` Comment
7000 VM VoiceMessaging
7001 TS 201 ThruDial
7002 EM ExpressMessaging
7003 PM PromptMaintenance
view/Modify DN Information
76
Choice of Services:
AS Announcement Service CA Call Answering EM Express Messaging
PM Prompt Maintenance RA Remote Activation TS Thru-Dial Service
TD Time-of-Day Control TR Transcription Service VF Voice Forms Service MS Voice
Menu Service VM Voice Messaging
Access DN: 7000
Service: VM
Comment: VoiceMessaging

View/Modify DN Information
Choice of Services:
PM Prompt Maintenance RA Remote Activation TS Thru-Dial Service
TD Time-of-Day Control TR Transcription Service VF Voice Forms Service MS Voice
Menu Service VM Voice Messaging
Access DN: 7001
Service: TS Thru-Dial ID: 201
Comment: ThruDial
Select a softkey >
Save Cancel
Choice of Services:
PM Prompt Maintenance RA Remote Activation TS Thru-Dial Service TD Time-of-
Day Control TR Transcription Service VF Voice Forms Service MS Voice Menu Service
VM Voice Messaging
77
Access DN: 7002
Service: EM Mailbox ID:
Comment: ExpressMessaging
Select a softkey >
Hardware Administration
1 Node Configuration
2 Data Port Configuration
3 Print All Node Information
4 Print All Data Port Information
Select an item >
Exit
The hardware configuaration is as follows:-
Node Configuration
78
Node Card_1 Card_2 Card_3 Card_4 Card_5 Card_6 Card_7 Card_8

1 VP8 VP8 VP8 Empty Empty UTIL MMP40 Empty
2 MMP40 VP8 Empty Empty Empty Empty Empty Empty
View Node 1 (C=Card D=DSP P=Port)
C-D-P Card_Type Port_Type Attributes
1 VP8
1-1-1 Voice: TN: Double 34 -0-2 -0 AgtPosId: 9999
2 VP8
3 VP8
Terminal Printer NWModem ICLink AML/CSL SMDI PMS

Modem
79
6 2 Data: Terminal Printer NWModem ICLink AML/CSL SMDI PMS

Modem
Modem
Modem
7 MMP40
Modem
Modem
8 Empty
View Node 2 (C=Card D=DSP P=Port)
C-D-P Card_Type Port_Type Attributes
1 MMP40
Modem
Modem
2 VP8
3 Empty
4 Empty
5 Empty
6 Empty
80
7 Empty
8 Empty
1 System Status
2 Card Status
3 DSP Port Status
4 Channel Allocation Table
5 Disk Maintenance
6 Diagnostic Schedules
7 System Event and Error Reports
Select an item >
Exit Silence Alarm
System Status and Maintenance

System Status: InService Alarm Status: Critical=On Major=Off Minor=On
Last Event: 22-32 VM:Non-User forwarded to VM, Mbox: 6234 rc: 2236 10/01 11:21
Link Status: 1-7-2: InService
DSP Port Status Storage Left

Node Type Status Active Idle OutSv Faulty Pending Others Voice Text
1 MSP InService 23 0 0 0 0 20:56 86%
2 SPN InService 0 0 8 0 0 0 18:11 75%
81
ﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄﾄ
Card Status for Node 1
Card# Location Description Status
1 1-1-0 Voice Processor InService

4 1-4-0 Empty Unequipped
5 1-5-0 Empty Unequipped
6 1-6-0 Utility InService
7 1-7-0 16 Megabyte Meridian Mail Processor InService

Card Status for Node 2
Card# Location Description Status
1 2-1-0 16 Megabyte Meridian Mail Processor InService


Channel Allocation Table for Node 1 (C=Card D=DSP P=Port)
82
Choice of Services:
ALL All Services AS Announcement Service EM Express Messaging
PM Prompt Maintenance RA Remote Activation OC RN/DNU Outcalling
TS Thru-Dial Service TR Transcription Service VF Voice Forms Service MS Voice
Menu Service VM Voice Messaging VS Voice Softkey
Limit; MaxVoice MinMulti; MaxFull; ---------Allocated---------

32 32 0 32 M/F: 0 V/F: 32 V/B: 0
# C-D-P TN ACD DN SCN Type Capability Outbound

1 1-1-1 034-0-02-00 7000 7801 Voice Full Basic ALL
Channel Allocation Table for Node 2 (C=Card D=DSP P=Port)
Choice of Services:
ALL All Services AS Announcement Service EM Express Messaging
PM Prompt Maintenance RA Remote Activation 0C RN/DNU Outcalling
TS Thru-Dial Service TR Transcription Service VF Voice Forms Service MS
Voice Menu Service VM Voice Messaging VS Voice Softkey
Limit; MaxVoice MinMulti; MaxFull; ---------Allocated---------

32 32 0 32 M/F: 0 V/F: 32 V/B: 0
83
# C-D-P TN ACD DN SCN Type Capability Outbound

Th e s eri al n um ber an d k ey c od e f or t he Mm ail

2: Serial Number : Z03055 Original Serial Number : Z03055
3: Platform : EC
4: Hours on System : 54
5: Release Number :13.12.1
6: Number Of Nodes : 2
7: Max allowed Languages : 1
8: Maximum Full Service : 32
9: Basic Service : 0
10: Minimum MultiMedia : 0
11: Voice Channels : 32
12: Physical Channels : 32
13: SMDI Link : No
14: Meridian ACCESS : No
84
15: AdminPlus/MMR : No
16: AMIS : No
17: Hospitality : No
18: Networking : No
19: NMS : No
20: OutCalling : Yes
21: Voice Forms : Yes
22: Alternate UI : 1
23: Multi ADMIN : No
24: Meridian Connections : No
25: Text Notification : 1
26: VMUIF : No
27: Personal Mailbox Admin : No
28: Fax On Demand : No
29: MMail AutoAdmin : 1
30: Web OA&M : No
31: SNMP Support for SEERs : 1

32: SNMP Support for OMs : 1
33: Multi SMDI : No
34: Multi Customer : No
35: Dual Language Prompting : No
36: Voice Menus : Yes
37: Integrated Mailbox Admin: Yes
38: Maximum NMS Locations: 0
39: Max PMA Users : 0
40: Max Web OA&M Sessions: 0:
Keycode : JVVD 8XCR FE4Q GC6F A3LF 58EC YR8D
85
Meridian Integrated Conference Bridge
86
Meridian Integrated Conference Bridge

System overview:--
The MICB is an Intelligent Peripheral Equipment (IPE) card compatible

with Meridian 1 options 21E, 51, 51C, 61, 61C, 71, 81, and 81C. It is also
compatible with Option 11E/11C system.
The system software required to support all 32 MICB ports in each MICB
card is X11 release 22 or later.
The system software must contain the automatic call distribution (ACD)
features and routing software modules to support the MICB operation. You
must consider the ACD resources in the incremental software management
(ISM) of the configuration, where each MICB port represents an ACD agent
that uses a TN from the system resources.
The MICB communicates with X11 system software by emulating a digital

line card, which allows the use of the existing software to control the MICB
operation. Each MICB port is defined as an ACD agent. All MICB ports are
members of the same ACD DN assigned to the MICB card.
MICB description
You can install the Meridian Integrated Conference Bridge (MICB) card into
any IPE card slot that is associated with full 50-pin I/O cables.
A single MICB card provides up to 32 ports that you can partition into
groups from 1 to 10, where each group represents an independent
conference. Alternatively, you can connect two MICB cards together to
provide up to 62 ports for a single conference.
87
Note: Systems with X11 release 22 or higher support 32 MICB ports per
card; systems with X11 releases 19 through 21 support only 16 ports per
card.
Each MICB port is configured as an ACD M2616 digital telephone set. The
Meridian 1 system ACD function routes the incoming calls to the MICB,
where each MICB port is treated as an ACD agent. All MICB ports belong
to the same ACD queue and are treated as a pool of ports with equal status.
The MICB supports several conferences simultaneously. The number of

conferences depends on the number of MICB ports available and the number
of participants (conferees) in each conference. For an MICB with 32ports,
there can be a maximum of 10 conferences with three or four participants in
each conference, 1 conference with a maximum of 32 participants, or any
combination in between.
The DNs and the corresponding TNs are system resources, which when
assigned to the MICB ports cannot be used for other Meridian 1 station. For
an MICB with 32 ports, a maximum of 10 simultaneous conferences would
require 20 ACD DNs for the conferees and chairpersons to dial to enter the
conferences, 32 TNs assigned to the ports, and one ADC DN assigned to the
MICB card. Please be aware of this use of system resources when
configuring the MICB card. Conference/TDS card is not used in any
application with the MICB card.
MICB functional characteristics
The function of the MICB card is to schedule and administer multiple

simultaneous conferences. These conferences are scheduled based on time-
of-day, duration of each conference, and number of conferees or ports
allocated for each conference.
The MICB card provides pre-programmed announcements and tones that

correspond to specific events during conferences. These events include
advising the chairperson and other conferees of the status of the conference
connection, indicating when a conferee joins or leaves the conference,
warning the chairperson and the conferees when the scheduled conference
time is about to expire, etc.
88
MICB Release 2.0 card features:
• Compatible with the IPE module in any system that supports IPE,
including the SL-100
• occupies one slot in an IPE shelf or an Option 11
• emulates an M2616 digital telephone set on each MICB port
• supports both the A-law and the m-law signal coding/decoding
• provides full duplex communication
• supports DTMF detection
• Command Line Interface (CLI), accessible by direct connection, modem
Or telnet for performing certain OA&M functions
• Browser User Interface (BUI), accessible through a common web browser
for conference and user administration and maintenance
• Telephone User Interface (TUI), accessible through any DTMF telephone
for reserving simple conferences
• Dual-card configuration to allow up to 62 ports in a single conference
(Does not require new software)
MICB conference features:-
• One chairperson per conference.

• provides for one or more permanent bridge configurations
• supports multiple conferences simultaneously
• provides automatic conference expansion, allowing additional conferees to
join the conference (Note: For the expansion to work, the ports hosting the
additional conferees must be both unassigned and available. Also,
expansion ports are assigned on a first come, first serve basis.)
• supports the following languages for the North American, CALA, and Asia
Pacific markets: N.A. English, French, Brazilian Portuguese, L.A. Spanish,
Chinese, Japanese, Korean, and U.K. English
• supports the following languages for the European market: U.K. English,
N.A. English, French, German, and Italian
• Conference password security, requiring the chairperson and/or the
conferees to enter a DTMF password before entering the conference
• Automatically starts and terminates conferences based on reservations
scheduled in advance
• provides email notification to conference scheduler of conference attributes
• provides the ability to reserve a port from each conference for the
chairperson
89
• Emergency bridge option which creates a permanent bridge that

automatically dials a pre-determined list of DNs when someone dials the
emergency bridge DN
• issues 10-minute warning before the conference termination
• Entry & exit indications—provides four options to indicate the entry and
exit of a conference participant:
— entry by name, exit by name
— entry by name, exit by tone
— entry by tone, exit by tone
— silent entry and exit
• allows conference music turn off and turn on for the first conferee joining
the conference
• controls access to the conference in progress by monitoring the maximum
number of scheduled attendees at each conference
• manages time and date for scheduled conferences and reserves ports for
each conference
• Conference password security, requiring the chairperson and/or the
conferees to enter a DTMF password before entering the conference
• provides recorded announcements and tones to ports and conferences by
playing pre-recorded files stored on the PCMCIA hard drive card
• supports administration features such as system configuration, scheduling,
management, and report generation
• Routes conferees to the appropriate conference based on the dialed
directory number (DN)
• allows recording of a brand line (custom) greeting for each language
• Issues audible responses to conferees based on the conference activity
• provides enhanced CDR and billing options
• provides conference traffic report
• Chairperson command features:
• Dial-out, enabling the chairperson to call a non-participant (The
chairperson can then return to the conference with or without the person he
or she called.)
• Redial last dialed DN
• Mute/unmute all ports
• Mute/unmute self
• Group call-out, enabling the chairperson to call several people on a
pre-defined list simultaneously
• Lock/unlock conference, enabling the chairperson to deny/allow the
joining of new participants
90
• Count conferees and announce names of participants to all participants or

just the chairperson
• Drop all conferees
• Drop last dial-out participant
• Drop last dial-in participant
• Conference duration expansion, enabling the chairperson to immediately
extend the length of the conference by 15 minutes
Configuring the MICB ports:-
Ports on the MICB card are configured as ACD digital sets, where each port
is considered to be an ACD agent. Each port must be assigned a terminal
number (TN). All ports on an MICB card belong to an ACD queue (group).
This ACD queue is identified with an ACD DN that handles the connection
of conferees (ACD agents) to the appropriate conference. Furthermore, each
conference is assigned a main DN and a chairperson DN, where the main
DN is the number the conferees dial to get into the conference and the
chairperson DN is the number the chairperson dials.
The DNs are configured in Meridian 1 at the time the MICB card is
installed. The total number of DNs is equal to two times the number of
simultaneous conferences you wish to allow. For example, if there are ten
conferences, there will be twenty DNs—ten main DNs and ten chairperson
DNs.
The creation of ACD DN is in LD-23 :--
TYPE ACD
CUST 0
ACDN 7951
MWC NO
DSAC NO
MAXP 32
SDNB NO
ISAP NO
AACQ NO
RGAI NO
ACAA NO
91
FRRT
SRRT
NRRT
FROA NO
NCFW 7900
FNCF NO
CWTT NONE
HMSB YES
ACPQ NO
FORC NO
RTQT 0
SPCP
OBTN NO
RAO NO
CWTH 1
NCWL
BYTH 0
OVTH 2047
TOFT
HPQ NO
OVDN
IFDN
EMRT
MURT
IVR NO
92
The creation of TN’s is in LD-11 :--
DES MICB
TN 068 0 08 06
TYPE 2616
CDEN 8D
CTYP XDLC
CUST 0
AOM 0
FDN
TGAR 1
LDN NO
NCOS 0
SGRP 0
RNPG 0
SCI 0
SSU
XLST
SCPW 1234
SFLT NO
CAC_MFC 0
CLS CTD FBD WTA LPR MTD FND HTD ADD HFD
MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE
DRG1 POD DSX VMD CMSD CCSD SWD LND CNDD
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTR
GPUD DPUD DNDD CFXD ARHD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ
UDI RCC HBTD AHD DD*GA NAMA MIND PRSD NRWD NRCD
NROD DRDD EXR0 USRD ULAD RTDD RBDD RBHD PGND
OCBD FLXA FTTC MCBN
CPND_LANG ENG
HUNT
PLEV 02
SPID NONE*
AST
IAPG 0
AACS NO
ITNA NO
DGRP
93
MLWU_LANG 0
DNDR 0
DTMK
KEY 00 ACD 7900 0 7916
AGN
01 SCN 7856 0 MARP
02
03 MSB
04 TRN
05
06
07
08
09
10
11
12
13
14
15
The TN’s used for MICB are as follows total 32 ports:--
From 68 0 8 0
Up to 68 0 8 31
Joining the conference
When several conferences take place simultaneously in the same MICB

card, 4the conferee dials the DN assigned to a specific conference. The
MICB card recognizes the dialed DN and routes the conferee to the
appropriate conference represented by that specific DN.
All ports belonging to an MICB card are routed to the appropriate
conference through the ACD DN assigned to that MICB card, i.e., that ACD
queue. The chairperson dials the chairperson DN to access his or her specific
94
conference. This number is different from the DN dialed when the conferees
are accessing that same conference.
The MICB performs DTMF detection on all MICB ports so that both the
chairperson and the conferees can enter certain commands. A conference can
start without the chairperson, and if all allocated ports for a conference are
occupied with conferees, the chairperson cannot join the conference unless a
port is specifically reserved for the chairperson or conference expansion is
allowed and there are free, un-scheduled (floating) ports available.
The first participant joining the conference hears an announcement that
indicates that no other conferee has joined the conference yet, and this
announcement is followed by 60 seconds of music. This announcement with
60 seconds of music is repeated continuously until at least one more
participant joins the conference.
The MICB provides flexibility in configuring conferences. They can be

configured as:
• Pre-scheduled conference with fixed number of ports and fixed start and
stop times
• Pre-scheduled elastic conference with variable number of ports, where they
are added when required (if available) and subtracted as people leave the
conference
• Permanent bridge with a fixed number of ports that can be used without
pre-scheduling the conference
Expanding the conference
You can allow or deny conference expansion by checking the appropriate

box on the MICB Conference Reserver page. If allowed, the number of
conferees belonging to a conference can be expanded as long as there are
remaining MICB ports that are both unassigned and unused.
When reserving the MICB ports for each simultaneous conference, specific
ports are not tagged for a specific conference. The MICB counts the number
of reserved ports and compares them against the total number of ports
provided by the MICB card and makes sure that the reserved ports do not
exceed the total number of ports provided by the MICB card.
Note: If you enable the conference over-booking option, the total number of
ports reserved for conferences can equal, but not exceed, 125% of the port
capacity.
95
If additional (not scheduled) callers attempt to join a conference, but they are
not allowed due to lack of floating ports or locked conference, the MICB
card will issue an overflow tone and then disconnect the call.
If un-scheduled (floating) ports are released from a conference, they are

immediately available to be used by other conferences that have the
expansion feature enabled.
The minimum duration of a conference is 15 minutes and the maximum

duration of a time-limited conference is 12 hours. Schedule conference
starting times and conference durations in increments of 15 minutes.
Ending the conference
When a conference is scheduled, the conference’s number of ports, start

time, and duration are specified. The conference ends at the predetermined
time, which is determined by the start time and conference duration. Ten
minutes before the end of a conference, the MICB card issues an
announcement warning the conferees that the conference must terminate in
10 minutes. When the conference time is up, the MICB card issues the final
warning to the conferees. The MICB also sends the release message to
Meridian 1 for all the associated MICB ports. These ports now become
available for the next pre-scheduled conference, or if not scheduled, they
become floating ports not reserved for any other conference and are
available to expand conferences in progress.
Individual conferees can leave a conference in progress at any time. The

MICB detects a conferee leaving the conference and inserts an exit prefix
announcement in the conference and the conferee’s name is announced, if
this feature is enabled.
Note: A conference can begin and end two minutes before the specified time.
This feature allows the system to close all terminating conferences two
minutes earlier and start all conferences that should be started immediately
after the terminating conferences are closed. This feature is important when
terminating and starting conferences use some of the same DNs.
96
Chairperson’s function:--
To become a chairperson, you must be the first to dial the chairperson DN.
The chairperson can control conference activities by executing commands
on his or her DTMF telephone. These commands consist of a star (*)
followed by one or two digits. If only a star (*) is dialed, after 5 seconds the
command times out.
Dual-card conferences require two chairpersons, one for the primary card
and one for the secondary card. The primary card chairperson can control
conference activities only on the primary card. Therefore, a secondary card
chairperson is necessary for controlling conference activities on the
secondary card. One exception to this restriction is the Group Call-out
feature. The primary chairperson can activate a group call-out to all
participants in a dual-card conference.
These following paragraphs detail the chairperson commands.
Dial-out:--
The chairperson can dial out and call a new party outside of the conference,
with the intention to confer only with the party or to bring the party into the
conference.
To do this, the chairperson dials *0DN# to dial a party outside the

conference, or *0# to access the operator. The chairperson can then decide to
bring the party into the conference by dialing *2 or disconnect the call by
dialing *3. If you dial the wrong number, you can dial *3 and re-dial. To
redial the last number dialed, the chairperson dials *#.
The MICB card selects the port for dialing out. The port is available if the
number of ports reserved for the conference is greater than the number of
conferees that have joined the conference. The port can also be available if
all the reserved ports are occupied for that conference, but there are some
un-reserved ports available on the MICB card and the port expansion feature
is enabled for that conference. If all reserved ports are occupied and there
are no unscheduled ports available, the call cannot be completed.
97
All ports mute/unmute toggle
The chairperson can place all conference participants on mute, excluding

him or herself, by dialing *10. While on mute, the participants can still listen
to the conference. To unmute the participants the chairperson dials *10
again.
Because there is one command for mute and unmute, the system announces
to the chairperson one of two possible voice messages: “All participants
have been muted” or “All participants have been unmuted”. Only the
chairperson hears the mute/unmute announcement.
Self mute/unmute toggle
Any conference participant, including the chairperson, can put himself or

herself on mute by dialing *19. While on mute, the participant can still
listen to the conference.
To unmute, the participant dials *19 again. Because there

is one command for mute and unmute, the system announces to the
participant one of two possible voice messages: “Muted” or “Unmuted”.
Only the participant that activates the command hears the mute/unmute
announcement.
The mute/unmute command is available not only to those

participants who enter the conference by dialling in, but also to those
participants who are brought into the conference through the chairperson’s
dial-out command.
Lock or unlock the conference:--
The chairperson can lock the conference to prevent any new conferees from
joining by dialing *4. The chairperson can unlock the conference by dialing
*4 again and thereby allow new conferees to join the conference.
A caller attempting to join a locked conference hears an announcement

indicating that the conference is locked, and the call is disconnected. The
chairperson can dial-out and include a conferee even if the conference is
locked.
98
Because there is one command for lock and unlock, the system announces to
the chairperson one of two possible voice messages: “Meeting is locked” or
“Meeting is unlocked”. Only the chairperson that activates the command
hears the lock/unlock announcement.
Count conferees
The chairperson can execute one of two commands to count the conferees
and play a list of all of the participants. With the execution of either of these
commands, the MICB card issues a string of voice prompts, one for each
conferee in the conference. If a new conferee joins the conference after the
chairperson activates either command, the MICB card does not count that
new conferee.
Note: To announce the names of the conferees through either command,

the conference scheduler must define an Entry & Exit Indication that
requires entry by name.
The two options for counting conferees are:
• Chairperson dials *60 to count the conferees and play the list of
participants for all of the participants. When the list is over, the
conference returns to normal state.
• Chairperson dials *69 to count the conferees and play the list of
participants for only the chairperson. Dialing *69 puts the chairperson
into a “scrolling state” where he or she can execute the following
commands:
When the playlist is over, the MICB automatically returns the chairperson to
the conference unless the chairperson dials #.
Drop all conferees:--
The chairperson can drop all conferees from the conference except the
chairperson by dialing *90. No announcement is issued to the conferees
before disconnecting them. The MICB card issues an announcement to the
chairperson indicating that no conferees are connected to the conference,
followed by 60 seconds of music. The conference is still active, so conferees
can dial in again.
99
Chairperson dials... In order to...
# Stop and start the playlist (Chairperson must

dial # after dialing *69 to start the playlist.)
0 Consult privately with the conferee
1 Mute/unmute the conferee
2 Announce the current conferee’s name greeting
4 Select and announce the previous conferee
6 Select and announce the next conferee
9 Disconnect the current conferee
*3 Return to the conference
** Start and stop the help menu
Drop last dialed conferee:--
The chairperson can drop the last conferee to join the conference through
chairperson dial-out by dialing *91. The chairperson can drop the last
conferee to dial in by dialing *92. These commands are not repeatable; that
is, the chairperson can drop the last conferee to dial in but not the
second-to-last to dial in. If the chairperson is the last to dial into the
conference, the MICB card cannot execute the *92 command.
Conference duration expansion:--
The chairperson can expand the duration of a conference by 15 minutes by

dialing *98. The chairperson receives the voice message, “Your meeting
duration has been expanded” if the expansion is successful. If the duration
expansion is not successful due to a lack of resources, such as ports or DNs
100
that have already been reserved for other meetings, the chairperson receives
the voice message, “Your meeting duration has not been expanded”.
The maximum conference duration, including all chairperson expansions, is
12 hours. The MICB card does not permit conference duration expansion to
a conference that is scheduled to end within three minutes of the expansion
request.
Chairperson help
The chairperson can access a help menu by dialing **. The help menu is a
voice recording of all chairperson command options. The chairperson can
stop the help menu before it finishes by dialing ** again.
The help command is sensitive to where the chairperson is in the command

structure. For example, if the conference is in the normal active state, the
chairperson hears the main list of commands after dialing **.
If the chairperson dials out to someone and then dials **, the chairperson
hears the list of commands relevant to dialing out. And if the chairperson
dials *69 to count conferees, and then dials **, the chairperson hears the list
of commands relevant to counting conferees.
Conferees can also dial ** to hear a list of command options available to

conferees. Only the participant who dials **, whether the chairperson or a
conferee, hears the relevant list of commands.
Summary of chairperson commands

lists of conference commands that one can execute on the telephone set
while the conference is in progress.
Conference commands
Chairperson Command Description:--
*0<DN># Dials out to a DN (called party directory

number, which is not a conference participant)
*0# Dials out to the assistant DN
*# Redials last dialed DN
101
*10 All ports mute/unmute toggle
*19 Self mute/unmute toggle
*2<GN># Group call-out, where GN is the group number

to call
*2 Returns to the conference with dialed party
*3 Returns to the conference without dialed party
*4 Locks or unlocks the conference
*60 Counts conferees and plays list of participants

and their port numbers to all participants
*69 Counts conferees and plays list of participants

and their port numbers to chairperson only.
*90 Drops all ports except the chairperson’s port
*91 Drops the last dialed-out port
*92 Drops the last dialed-in port
*98 Extends the conference by 15 minutes
*99 Stops or starts the initial conference music.

This is possible only when the conferee is the
first person to join the conference. The first
entry stops it, the second entry starts it.
* Aborts current command
** Starts or stops help menu
Conferee command Description:--
102
*19 Self mute/unmute toggle
*99 Stops or starts the initial conference music.

This is possible only when the conferee is the
first person to join the conference. The first
entry stops it, the second entry starts it.
* Aborts current command
** Starts or stops help menu
List of commands the chairperson can execute after he or she dials *69.
Chairperson Command Description
# Stop and start the playlist of participants
0 Consult privately with the participant
1 Mute or unmute the participant
2 Announce the current conferee’s name

greeting
4 Select and announce the previous conferee
6 Select and announce the next conferee
9 Disconnect the current participant
*3 Return to the conference
** Start or stop the help menu
Browser user interface (BUI) in MICB
Configuring MICB
Before you can proceed with conference administration through the BUI,
you must:
103
1 Configure a VT100 terminal for CLI(command line interface)

access.
2 Enter the keycode information.
3 Set the LAN parameters, including IP address, gateway address,
and subnet mask.
4 Restart the card.
5 Define card and user details through the BUI.
The following sections describe each of these steps.
Configuring the VT100 terminal for CLI access
To access the CLI, you must use a VT100-type terminal.

Specify the VT100-type terminal interface characteristics to ensure
compatibility with the
MICB RS-232 interface.

Set the interface parameters as follows:
• Transmission speed: 9600 bps
• Data bits: 8
• Stop bit: 1
• Parity: No
• Flow control: none
Note: Do not use XON/XFF flow control.
Enter the keycode information

When you first connect a VT100 terminal to your MICB card, the CLI
appears and prompts you to enter keycode information. To enter the keycode
information, do the following:
1 At the “Modify, Save, Cancel:” prompt, enter m to Modify.
2 At the “max conf_ports (0):” prompt, enter the number of ports that
corresponds to your MICB Release 2.0 keycode (e.g., 32).
3 At the “Card Feature (BASIC, (1-ADVANCED)):” prompt, press

Return for BASIC functionality.
Note: The ADVANCED option is in place for future call accounting
104
capability. This capability is not available at the time of the printing of

this document.
4 At the “Modify, Save, Cancel:” prompt, enter s to Save your
modifications.
5 At the keycode prompts, enter “(key-code1)13531573”,
“(key-code2)15061470”, and “(key-code3)41774113”
(eight characters each) for MICB Release 2.0 functionality.
Set the LAN parameters:--
If the keycode entry is successful, the CLI notifies you and presents you
with a login prompt. You can now enter the LAN parameters for your MICB
with the following procedure:
1 Once the system successfully registers the MICB Release 2.0

keycode, log into the CLI as admin.
2 At the “SAdmin, SMint, PAdmin, PMaint, RGen, LOgout, ?:” prompt,

enter sa to access System Administration.
3 At the “SYstem, REcorder, ?:” prompt, enter sy to access System

Attributes.
4 Enter the system attributes of the MICB Release 2.0 card, including
the IP address, gateway, and subnet mask.
5 At the “Modify, Save, Cancel:” prompt, enter s to Save the system

attributes.
6 At the “Restart MICB?” prompt, enter Yes.
7 From a PC terminal, “ping” the MICB card to ensure that it has a

proper connection to the LAN. To ping an MICB card, do the
following:
— Click on the Start button and select Run from the Start Menu.
— In the “Open:” field, enter “ping <IP address>” where <IP
address> is the IP address of the MICB card.
105
— Click the OK button, and observe the DOS window that opens.
If you receive the message, “Reply from <IP address>...”, you have
set
up the LAN connection properly and you can proceed. If you receive
the message, “Request timed out.”, there is a problem with the LAN
connection.
Define card and user details through the BUI:--
Note: You are now ready to access the Browser User Interface (BUI) to
configure card attributes, users, and conferences. To access the BUI, you
must have Netscape Communicator 4.5+ or Internet Explorer 4.01+ with
service pack 1.
Before you can administer conferences on an MICB card, you must first
define the card’s details through the BUI. To define an MICB Release 2.0
card’s details, do the following:
1 Open your web browser on your PC, enter the following in URL
field:
<MICB card IP address>/micb.htm for an embedded server, or
<PC server IP address>/micb/micb.html for an external server,
and press Return.
2 At the MICB Release 2.0 login page, enter admin for the login and
000000 (six zeros) for the password. This brings you to the MICB
Administration Utility.
3 Click on the Cards tab of the MICB Administration Utility to

configure card attributes.
4 Click on an open field in the “Card Name” column and enter a

name for the card, up to 20 characters.
Note: If you entered a card name in the System Attributes of the CLI,
and you are using the embedded server option, the name of the card
will already be in the “Card Name” column.
5 Click on the “Card ID” field next to the card name and enter the
appropriate card ID.
6 Click on the Display Details button at the bottom-left of the screen.
106
This displays (at the right side of the screen) the details of the
selected card.
Note: If you use the embedded server option, certain details of the
card already appear at the right, such as hardware and software
information and the card’s IP address.
7 In the card details section, enter the appropriate details for the
selected card, including the card type, the TUI DN, and the
conference DN pairs.
Note: If you use the external server option, you must first enter the
card’s IP address and select the appropriate card type; then click
Apply. This establishes the external server’s connection to the card.
You can then proceed to configure the rest of the card attributes.
8 Be sure to configure any necessary Group Calls and Weekdays

settings.
9 Program any permanent bridges from the original MICB in the
Permanent Conferences settings.
10 Click Apply to save all of the card attributes.

11 At the top-left of the MICB Administration Utility, click on the
Properties button to open the “System Properties” dialog box.
Enter the ‘Mail server IP address’ and
Click OK to establish email notification to users.

Note: For email notification to work, the mail server IP address must
be ‘unrestricted’ and able to send email to everyone on the network.
12 Click on the Users tab of the MICB Administration Utility to

configure users for your MICB card.
13 Click Apply after you define each user to save all of the user
attributes.
14 Notify the users of their user (login) ID and passwords so that they
can access the BUI and TUI.
Users can now access the BUI and the TUI to define and manage
conferences.
107
MICB password security

To protect functional and software upgrades, the MICB provides the
Protected Administration menu, accessible in the CLI. This menu allows you
to edit passwords and perform functional and software upgrades.
The Login window
The first window you see when you point your web browser to the MICB
BUI is the login window. To point your browser to the MICB BUI, enter <IP
address>\micb.htm in the URL field and press Return. <IP address> is the
IP address of the MICB card or the external server.
At the LOGIN prompt, enter your login ID(admin). The administrator

determines each user’s login ID. At the PASSWORD prompt, enter the
password(123456) The password is six digits and is the same one you use to
access the TelephoneUser Interface (TUI). The first time you log in as a user
or super-user, you use a default password that the administrator determines.
After you log in, you can change the password by clicking on the key icon in
the Conference Manager window.
When you log in to the MICB BUI, the login ID connects you to the server
as a particular user type. The administrator determines what user type each
user is. The three user types and their functionality are:
• User—A user can reserve conferences under his or her account as well
as modify and delete his or her own conferences. A user can also view all
108
scheduled conferences.
• Super-user—In addition to the normal user functionality, a super-user

can reserve conferences under other users’ accounts. A super-user can
modify and delete the conferences of other users.
• Administrator—The administrator manages MICB system parameters,

including user IDs, group-call tables, permanent bridges, and other
MICB features.
Users and super-users use the same BUI, while the administrator BUI is
different. The user/super-user BUI handles conferences. The administrator
BUI is only for system management and does not schedule conferences. The
administrator can create permanent bridges, while the user and super-user
cannot. In the external server configuration, each user/super-user is
associated with one MICB card only and has no access to other cards. The
administrator manages all MICB cards that the web server controls.
Note: The administrator must first define all card attributes and user
attributes before user and super-users can access the BUI to schedule
conferences.
MICB administration utility

To enter the MICB administrator BUI, enter the administrator login ID and
password at the login window.
Figure shows the MICB Administration Utility window, which is the main
administration window.
Across the top of the main administration window are five buttons:
• Properties button opens the Properties window
• Password button opens the Change Password dialog box, which allows
the administrator to change the administrator password .
• Apply button saves the current data
109
• Help button opens the online help
• Exit button terminates the BUI session and logs you out
Administration page and the Users administration page. Click on the tab for
the page you want to view.
Users administration
Manage MICB user parameters from the Users page of the MICB
Administration Utility In the external server configuration, the
external web server stores all user data. In the embedded server
configuration, each MICB card stores its own user data.
The table on the left side of the Users page lists all of the users, listing for
each user the user name (up to 20 characters) and the login ID (up to 10
characters).
110
You can sort the list by either user name or user ID by clicking on the title of
the appropriate column. For example, to sort the list alphabetically by user
ID, click on the User ID column head. You can select a particular user by
clicking on it; the selected user is highlighted, and the user details appear on
the right.
Note: The “User ID” functions as the login ID for the user.
The Add User button below the table opens a new line below the currently
selected user. You can enter a new user in this new line.
The Remove User button deletes the currently selected user.

You can define up to 1000 users in the external server configuration or up to
100 users in the embedded server configuration. A user can be assigned to
only one MICB card. The ‘Filter’ area at the bottom of the Users page
allows you to display a select subset of users. When you click the Filter
button, only users matching the ‘Text to Find:’ field appear in the users list.
The Show All button cancels the filter and re-displays the entire list of users.
User details
The parameters of the selected user appear on the right-hand side of the
Users page. You can configure the following attributes for each user:
User type: The type of user, either user, super-user, or administrator.
Note: Initially, there is one user of type ‘administrator’ with password

‘000000’ and billing account number of 1. This is for the first login after
installation.
Telephony ID: The user ID for user login to the TUI, up to six digits in
length.
e-mail: The e-mail address of the user, for receiving reservation

confirmation by e-mail, up to 36 characters in length.
Billing account: The account number of the user, up to nine digits, for
111
billing purposes. This number appears in the billing

reports and in Meridian 1 CDR records for conferences
owned by the user.
MICB Card name: The name of the card the user is assigned to. Only the
external server configuration supports this field.
Click the Reset Password button to reset the selected user’s password to the
initial password.
Group-call configuration
For each MICB card, you can define groups for the group-call feature. To
enter the group-call setup, click on the Group Calls... button on the cards
page of the main administration window. The Group Calls dialog box then
appears, as Figure shows.
The table on the left side of the Group Calls dialog box lists all of the groups
defined for the selected card. You can define up to 64 group-call lists per
card.The group number is the number that the chairperson dials when
executing the group-call command. The group name is up to 20 characters of
free text that describes the group. The BUI sorts the group-call lists by group
number.
112
You can select a group by clicking on a particular row of the table. The
group is then highlighted and the group’s details appear at the right.
The Add Group button below the table opens a new line below the currently
selected group. You can enter a new group in this new line.
The Remove Group button deletes the currently selected group.
Group details
The group details on the right side of the Group Calls dialog box lists the
DNs assigned to the selected group. The order of the DNs indicates the
priority of calling; for example, when a conference has seven ports available,
the MICB dials only the first seven DNs on the list. A group call list can
contain up to 61 DNs.
The Add DN button to the right of the table opens a new line below the
currently selected DN. You can enter a new DN, up to 20 digits, in this new
113
line. The MICB sets the DN number in the left-hand column automatically.
The Remove DN button deletes the currently selected DN.

You can also configure the following attributes for each group:
Wait time for answer: The number of seconds to wait for a called party
to answer when dialling the selected group. The range is
15-90 seconds.
Default: 30 seconds
Number of call attempts: The number of times to dial each number in the
group call list. The MICB card can re-dial a number in
the case of failure. A value of 1 means only one attempt
with no retries. The range is 1-3 attempts.
Default: 1 attempt
Time period between attempts: In case of dialing failure, the number of

seconds the MICB card waits before re-dialing the
number. The range is 5-30 seconds.
Default: 10 seconds
Permanent-conference configuration
For each MICB card, you can define permanent conferences, or bridges. To
enter the permanent-conference setup, click on the Permanent
conferences... button on the cards page of the main administration window.
The Permanent Conferences dialog box then appears.
\Note: MICB Release 2.0 does not support dual-card permanent

conferences. However, you can define permanent conferences on either
of the cards in a dual-card configuration, as long as the number of
participants does not exceed the number available on that particular card
(maximum of 32).
114
The table on the left side of the Permanent Conferences dialog box lists all
of the permanent conferences defined for the selected card. The conference
name is up to 20 characters of free text that describes the conference.
You can select a conference by clicking on a particular row of the table. The
conference is then highlighted and the conference’s details appear at the
right.
The New button below the table opens a new line below the currently
selected permanent conference. You can enter a new conference in this new
line.
The Submit button sets the currently defined permanent conference.
115
The Delete button deletes the currently selected permanent conference.
Conference details
For a selected conference, you can configure the following details shown on
the right side of the Permanent Conference dialog box:
Owner ID: The user ID of the owner of the permanent conference.
Title: The title of the permanent conference.
Participants: The number of ports to reserve for the permanent

conference, up to the number of ports configured on the
MICB card.
DN: The DN that conferees must dial to enter the permanent

conference.
Configure the Language, Entry & Exit Indications, Chairperson Password,
Conference Password, Reserve port for chairperson, and Use custom
greeting attributes the same way as those explained for the MICB
Conference
Check the Emergency conference box at the bottom of the dialog box to
activate the Emergency Conference feature. An emergency conference has
an associated group-call list, which you select in the adjacent combo-box.
When somebody dials the DN for an emergency conference, the MICB
immediately dials every DN on the selected group calls list.
After you add or modify a permanent conference, press the Submit button to
save the conference attributes before proceeding to the next conference.
After you press the Submit button, an acknowledgment window appears,
which specifies whether the Submit operation was successful.
If you abandon pending modifications (i.e., not pressing the Submit button)
by selecting another permanent conference or by pressing the New or Exit
buttons, a dialog box appears asking you whether to discard the pending
modifications or set them.
.
Setting a conference
116
Once you have entered all of the parameters for a particular conference,
press the Submit button in the MICB Conference Reserver window to
reserve the conference on the MICB card. If the reservation is successful, an
acknowledgment box appears
.
The window is the same for a single or recurrent conference. The window
shows the main conference parameters: DNs, passwords, number of ports,
date, time, and duration. If you set a recurrent conference, you can also view
all successful recurrence dates in this window. You can view all other
parameters of the conference in the MICB Conference Reserver window,
which is still in view.
Note: It is especially important to note the contents of the Conference

reservation acknowledgment window if you had the MICB card set the
DNs and/or passwords automatically.
You can copy the text in the white portion of the Conference reservation
acknowledgment window and paste it elsewhere. The operation for copying
and pasting the text is the same as for most word processors.
Conference reservation acknowledgment window
117
Reservation failure
If the MICB card cannot reserve a requested single conference, the Single
conference ‘Set’ failure message appears .The failure message gives the
reason for the reservation failure. If the reason for failure is insufficient
ports, you have the option to set the conference anyway with a smaller
number of ports by pressing Set Anyway.
Otherwise, you can press Cancel and reconfigure the conference. If the
reason for failure is that a DN is not available, you must reconfigure the
conference.For a recurrent conference, pressing Submit reserves the
conference for all of the requested dates that are available. If the list of dates
actually set differs from the list shown in the ‘Verify’ result, the Recurrent
conference ‘Set’ failure message window appears
Single conference ‘Set’ failure message
118
Recurrent conference ‘Set’ failure message
Email confirmation
When conference setup is successful, MICB automatically sends the

conference owner an email with the details. Table 14 gives an example of the
email format.
119
Conference Manager
Click on the Manager button at the top of the Conference Reserver window
(shown in Figure 30). The Conference Manager window displays all the
meetings scheduled for a selected day on that one MICB card. The
Conference Manager window has an auxiliary Calendar window to select
dates. The Conference Manager and Calendar windows appear side by side.
User privileges
A user can schedule meetings only for himself or herself.
Email confirmation
Your tele-conference meeting has been booked by MICB as follows:
Owner ID: yousuf
Conference DN: 1157
Chairperson DN: 1126
Conference password: 1234
Chairperson password: 4321
Date: 10 sept 2001
Start time: 10:45
Duration: 30 min
Por t s: 6
Recurrence dates: 11 sept 2001
18 sept. 2001
19 sept. 2001
Options:
Chairperson name: yousuf khan
Language :English
Entry & exit indications: Name, Name
Reserve port for chairperson: yes
.Use custom greeting: no
Allow port expansion: no
Conference Manager
Click on the Manager button at the top of the Conference Reserver window
The Conference Manager window displays all the meetings scheduled for a
selected day on that one MICB card. The Conference Manager window has
an auxiliary Calendar window to select dates. The Conference Manager and
Calendar windows appear side by side.
120
User privileges
A user can schedule meetings only for himself or herself.
Super-user privileges
A super-user can schedule meetings for all users.
Conference Manager window
conference manager description
Across the top of the Conference Manager window are six buttons:
• Edit button brings you to the Conference Reserver window to edit the
details of a conference that you highlighted in the Conference Manager
window.
• Delete button deletes a conference that you selected, if you have
permission.
• Submit button submits the details of a conference that you are first
defining or modifying for the MICB to save.
121
• Calendar button opens the auxiliary Calendar window so that you can
select which day’s conferences you want to view.
• Password button opens the Change Password dialog box so that you can
change your user password.
• Close button closes the Conference Manager window and returns you to
the Conference Reserver window. You will lose all changes to
conferences unless you first clicked on the Submit button.
The main part of the Conference Manager window shows the conferences
scheduled for the selected day. The horizontal scale indicates the time. The
vertical scale indicates the conference DNs. A colored, horizontal bar
represents each conference. Immediately below the body of the window is a
key to the colored bars:
• Orange indicates conferences that the current user owns.
• Yellow indicates conferences that others own.
• Lavender indicates a permanent bridge.
• Dark blue indicates a conference that the user is defining or modifying
but has not yet submitted.
The letter ‘R’ on a conference bar indicates a recurrent conference.

The vertical, dotted line in the body of the window indicates the separation
between days. The window shows two days—the day selected and the day
following.
To edit or delete a conference, click on a conference and press the Edit or

Delete buttons at the top of the Conference Manager.
The bottom row of the Conference Manager window displays the main
details of the selected conference. When a user clicks on a field in this row,
its contents appear in the ‘Edit Box’ above. The user can edit the selected
field’s contents. After you edit the contents of the selected field, press
Return and click on the Submit button to set the changes.
Note: Users can only edit or delete their own conferences.
User operation
122
Users can define a new conference by dragging the mouse from left to right
in the row of the desired DN. The new conference you are defining appears
in the lower table; you can enter the conference title and the number of ports,
or conferees, there. You can adjust the duration of the conference by
adjusting the size of the conference bar or by updating the ‘Duration’
column in the lower table.
You can view details of a selected conference in the MICB Conference

Reserver window, which is the main window. To return to the main
window, click on the Edit button at the top of the Conference Manager
window. The main window contains the parameters of the conference that
you selected in the Conference Manager window. In the main window, a
user can modify the parameters of the selected conference if he or she owns
the conference. A super-user can modify the parameters of any of the
conferences.
Note: If a user is viewing the parameters of any conference, the
passwords do not appear.
Click on the Delete button to delete the selected conference. This opens a
dialog box for confirmation. If the selected conference is a recurrent
conference, the dialog box gives you two delete options:
• The selected instance only
• All instances of the recurrent conference
Click on the Submit button to reserve, or save the modifications of, the
selected conference. If the reservation is successful, an acknowledgment
box appears
Click on the Calendar button to display or hide the auxiliary Calendar
window.
Click on the Password button to open a dialog box for modifying the user’s
(or super-user’s) password. The password can be up to six characters in
length.
Click on the Close button to return to the MICB Conference Reserver
window without the attributes of a selected conference.
The auxiliary Calendar window
123
Figure shows the Calendar window, which appears when you click on the
Calendar button in either the Conference Reserver window or the
Conference Manager window. The window opens to the current day.
The year and month appear at the top of the window. The down arrows to the
right of the year and month open combo boxes that allow you to select the
desired year and month. The MICB card allows reservations up to one year
in advance. Once you have selected the desired year and month, select the
desired day by clicking on that day. A black box frames the selected day.
Click the Today button to return the calendar to the current day.
Click the Apply button to set the conference date in the Conference
Reserver window or to update the Conference Manager window to the
selected date.
Click the OK button to set the conference date in the Conference Reserver
window, or to update the Conference Manager window to the selected date,
and close the calendar.
124
Click the Cancel button to close the calendar window and keep the current
date.
125
126
Meridian Integrated RAN
127
Meridian Integrated RAN
MIRAN quick installation procedure
1 Request an IP address, subnet mask, and Gateway from your

system administrator. This step is only necessary if you intend to
connect the MIRAN to your LAN.
2 Insert the security device onto the MIRAN board. You must install
the security device with the Nortel Networks logo and the 8-digit
inscription facing away from the board.
Note: You can correctly insert the security device in only one
position.
3 Connect the 50-pin female connector of the multi-I/O adapter cable

to the I/O panel. Connect the RJ45 connector to your LAN hub; use
an RJ45 coupler and additional RJ45 cable, if necessary. Connect the
50-pin male connector to the MDF cable.
4 Connect a VT-100 terminal to the MIRAN using the provided

NTAG81GA cable.
Note: You can use the NTAG81CA cable to connect a terminal to
the J2 faceplate connector.
5 Configure the terminal in VT-100 mode at 9600 baud, 8 data bits, 1

stop bit, and no parity.
6 Insert the MIRAN card into an unequipped IPE slot and watch the
terminal screen for boot-up commands. This requires approximately
90 seconds.
Note: Before you install a MIRAN card into an IPE slot, ensure that
no cross-connect wires from another product remain attached to this
slot Cross-connect wires that carry a ringing voltage can damage the
MIRAN card.
7 At the logon screen of the text-based user interface, ensure that the
128
cursor is in the ‘User Name:’ field. Then log on by doing the following:
— Type in the user name (admin), and press the ‘down’ arrow.
— Type in the administrator default password (admin000), and press
the ‘down’ arrow again.
— Press <CR> at the ‘Login’ prompt.
Note: If you receive an ‘Access denied’ response, press the ‘Shift’ key
and tilde (~) to refresh the screen. Then repeat step 7. You can repeat
step 7 up to three times. If you receive an ‘Access denied’ response for a
third time, the MIRAN card locks you out for 20 minutes.
8 At the Main menu:

—Select 2, “Pack Administration”
— Then select 2, “Keycode Entry”
Note: The keycodes are on a label that accompanies the security

device. Pull off this keycode label and attach it to the MIRAN
faceplate. Between the brackets, type in the 24-character keycode
with a space between each set of eight characters. Select Execute to
execute the keycode. Wait for a keycode validation response
(‘Keycode validated’). Then select Exit to return to the Pack
Administration menu.
Note: If you do not need ethernet capability for your MIRAN, you can
omit step 9 and just log out of the text-based user interface after step 8.
9 At the Pack Administration menu, select 6, “Ethernet Configuration”.

At the Ethernet Configuration screen, enter the new IP address,
subnet mask, Gateway, and IP method of the MIRAN card, which you
received from your network administrator. Select Set to set the
ethernet configuration parameters. Then select Exit to return to the
Pack Administration screen. Finally, log out of the text-based user
interface by selecting 9 from the menu screen until the Main Menu
screen appears.
10 Reboot the MIRAN card by pressing the reset switch on the front
of the pack. This causes the keycode to take effect. Wait for the card
129
to reboot and the Login screen to come up on the maintenance

terminal.
This also requires approximately 90 seconds.
11 Log into the Meridian 1 system. Program a DID route and

configure a DID trunk on MIRAN unit 7. Use the TN for the loop, shelf
and card slot into which the MIRAN card is plugged.
TYPE TLST
TKTP DID
ROUT 8
DES
TN 052 0 01 07 MBER 1
The DID unit to allow local telephone access for the recording of RAN
announcements.
Note: You can perform this step first.
12 Use a local DTMF telephone to dial the DID access code for
MIRAN unit 7.
Note: The local DTMF telephone must have an ‘unrestricted’ Class of

Service; that is, CLS = UNR in Overlay 11.
Enter the number sign (#), then the user name (‘user’=8737)
followed by star (*), then the password (87370000) followed by star
(*). Next,press 5 and then press 5 again to begin recording a RAN
announcement. When you have finished recording, press 3 to stop
the recording and press 1 to save the announcement. Because
MIRAN writes the recording to flash memory, it can take 30 seconds
or longer for MIRAN to respond that it has saved the announcement.
Please be patient.
13 Program RAN and Music routes and trunks for the remaining
channels. For example, program channel 0 as a Music trunk and
channel 1 as a RAN trunk.
130
Note: MIRAN Release 2.0 comes with royalty-free music

pre-assigned to channel 0 and set to play ‘always’. Therefore, Nortel
Networks recommends that you configure channel 0 as a Music
route.
However, you can remove this assignment and assign any other
announcement or music file in its place.
WARNING
After you press 1 to save the announcement, do not hang-up, but wait
for MIRAN to state that it has saved the announcement and tagged the
announcement with an announcement identifier (example:
‘Announcement has been saved as announcement 1’).
14 Log in to the MIRAN using the default user name (user) and
password (user0000). You can log in to the text-based user interface
through the maintenance terminal as before. Or, if you have
connected the MIRAN to the ethernet, you can access the MIRAN
browser user interface (BUI) by pointing your web browser to the IP
address of the MIRAN card. To assign a announcement to a MIRAN
channel, do the following:
— At the Main Menu select (1) “MIRAN Administration...”.
— At the MIRAN Administration menu select (1) “Announcement
Configuration...”.
— At the Announcement Configuration menu select (1) “Calendar
Operations...”.
— At the Calendar Operations menu select (1) “Calendar
Assignment with Descriptor”.
— At the Calendar Assignment with Descriptor screen, enter first the
channels (ports) for a particular announcement to play on. For
example, if the TN for a RAN trunk is 52 0 1 5, then you can assign
a announcement to channel 5.
— At the ‘Filename:’ prompt, enter the filename of the

announcement that must play on the channels you selected. You
can ‘Browse’ the list of available announcements to select one.
131
— At the ‘Descriptor’ prompt, enter the descriptor that defines when

the selected announcement will play on the selected channels.
You can ‘Browse’ the list of available descriptors to select one.
(Remember that you can define your own descriptors if the
pre-configured descriptors do not meet your needs.)
— Move the cursor to ‘Add to Calendar’ and press <CR> to create
the calendar assignment with descriptor.
15 To test RAN announcements, dial the trunk access code for the
desired RAN route and listen to the announcement that plays.
16 Manually back up RAN announcements and configuration in the

eventc of a power loss or MIRAN re-boot. To complete a back-up, do
the following:
— At the Main Menu select (1) “MIRAN Administration...”.
— At the MIRAN Administration menu select (3) “Backup
Configuration”.
— At the ‘Device:’ prompt, enter the drive you want to make a backup
to. For example, enter A: to back up the MIRAN configuration
information to a PCMCIA card in drive A:.
Select from the choices below. The list below does not appear on the
menu screen. Perform the backup procedure twice: once on Internal
Storage C, and once on device “A” or “B”, if equipped.
• Internal Storage C (old s/w Rls. 1.39 or 1.46 backup

s/w to internal storage “C”)
• External ATA A Backup when using a spare
PCMCIA
• Internal ATA B When PCMCIA resides on the
MIRAN card
• Exit out to the Main Menu
Note: MIRAN provides an automatic save function after you exit the
telephone user interface (TUI). If you make changes through the

text-based user interface or the browser user interface (BUI), you
must back up manually.
Configuring RAN routes

The MIRAN card emulates an Enhanced Universal Trunk (EXUT) card in
the Meridian 1 system. Therefore, you configure RAN routes and trunks for
the MIRAN card in the same way you do for the EXUT card. For detailed
132
information on overlays Trunk Route Administration (LD 16) and Trunk

Administration (LD 14).
To configure the RAN propagation route and the mode of activating the
recorded announcement, you must define its parameters using Trunk Route
Administration program LD 16. The MIRAN emulates the Enhanced
Universal Trunk characteristics and does not require modification of LD 16
to configure the MIRAN functions. Specifically, the MIRAN and the
Enhanced Universal Trunk card support the following modes of operation:
— Delay Dial Continuous RAN (DDL)
— Immediate Start Continuous RAN (IMM)
— Level Start/Stop RAN (LVL, MLSS, or MLVL)
The MIRAN supports all of the above on two, four, or eight independent
ports. Thus, you can assign the same RAN announcement to different ports,
thereby allowing multiple callers to hear the same announcement at the same
time.
Note: With X11 release 23 and the availability of RAN Broadcast, up to
30 callers can simultaneously listen to the same RAN announcement on
a single RAN port.
Continuous RAN routes (Delay Dial and Immediate Start)
Continuous (immediate or delay) RAN plays an announcement over and

over again. Callers “barge in” on a announcement playing on an Immediate
Start RAN route. Callers receive a ringback tone for an announcement
playing on a Delay Dial RAN route until the announcement begins again. At
the end of each announcement, a pulse is issued on the control pulse line that
is used by the trunk unit to cut through to the waiting call. External channels
barge in at any time during the announcement, internal ports/channels wait

until the announcement starts to be connected to a RAN announcement.
To configure a continuous RAN route, load Route Data Block program LD

16 using the system TTY and enter the appropriate responses to the prompts
.
Note 1: These prompts only appear if RTYP = MCON.
133
Note 2: The ‘BDCT’ prompt appears only if customer has package

327 (RANBRD).
Ld-16
REQ: prt
TYPE RDB
CUST 00
ROUT 10
DES
TKTP RAN
NPID_TBL_NUM 0
RTYP CON
GRD IDLE
REP 1
POST DIS
STRT IMM
WAIT MUS
MRT 41
BDCT NO
ASUP YES
ACOD 6543
TARG
CDR NO
NATL YES
CFWR NO
IDOP NO
MUS NO
PANS YES
TTBL 1
OHTD NO
ALRM NO
SGRP 0
AACR NO
Music-on-hold activation and route configuration
Music-on-hold (MOH) operates in a continuous mode with an immediate
134
connection to the music source. The music source plays continuously.

Callers “barge in” on playing music.
To specify the conference loop for the MOH, you must access the
Configuration Record program LD 17, as shows.
Adds or changes conference loop for MOH (LD 17)
REQ CHG Define change existing configuration

TYPE CFN Configuration record
CEQU Yes (No) Change common equipment parameters
XCT 0-158 Loop number for NT8D17 Conference/TDS
card.
CONF 0-158 Conference loop should be an even number.
Configuring the DID route for the TUI
To configure MIRAN for TUI (telephone-based OA&M) access using

internal one-to-one port 7, you must configure the appropriate route and
trunk data blocks. Table 16 lists Route Data Block program LD 16
commands to define the DID route data block.
Defines a DID route for the TUI (LD 16)
REQ NEW Define new or change existing configuration

TYPE RDB Route data block
CUST 0- Customer number
ROUT 0-511 Route number
TKTP DID Trunk type for telephone-based OA&M
access
ICOG IAO Incoming and outgoing trunk
ACOD Trunk route access code
CNTL Yes Gate opener for control timers
NEDC ETH Near end. Both ends have disconnect control.
FEDC ETH Far end. Both ends have disconnect control.
135
ASUP NO
YES
CO Do not return answer supervision
Return answer supervision
Return answer supervision if originator is a
CO trunk
Configuring the MIRAN trunks

After you configure a RAN, Music, or DID route, you can configure the
route’s corresponding trunk. A trunk data block specifies the parameters for
a particular trunk. Because the MIRAN emulates the Enhanced Universal
Trunk card, you can define the MIRAN parameters using the Trunk
Administration program LD 14 on the system TTY.
REQ: prt
TYPE: ran
TN 052 0 01 00
TYPE RAN
CUST 0
XTRK EXUT
TIMP 600
BIMP 600
AUTO_BIMP NO
RTMB 10 1
Connecting an external audio device
You can connect an analog audio source and receiver to the MIRAN for the
following purposes:
— recording music or announcements to the Flash memory
— backing up announcements from the MIRAN to a tape or to another
MIRAN card
— connecting directly through a trunk emulation port/channel into the
Meridian 1 for MOH.

You can connect the analog device to either of the following:
— the 3.5 mm Audio Jack on the MIRAN faceplate
— at the MDF
136
Analog to internal pass-thru switchover

For Music-on-Hold, both analog ports can be used at the same time, each
assigned to different internal channels.To allow switching from an analog
source to an internal channel, the configuration of each channel is polled
every 30 seconds to check for an assignment switchover. If the assignment is
for a voice file, the playthrough will be stopped and the voice file started
immediately, and vice versa. This switchover always occur at the end of the
file to avoid hearing truncated announcements.
Connecting audio devices to the MIRAN faceplate

The MIRAN has a 3.5 mm Audio Jack at the top part of the faceplate. This
jack provides one audio input and one audio output.
To connect the external audio source to the MIRAN faceplate audio jack:
1 Plug the 3.5 mm jack on the common side of the NTAG81AA Audio
Cable into the 3.5 mm Audio Jack on the MIRAN backplane.
2 Plug the audio input end of the NTAG81AA cable connector into the
audio source device. If the source is at a distance from the MIRAN,
you may have to use an extension (not supplied).
3 Plug the audio output end of the NTAG81AA cable connector into
the audio receiver device (for announcement backup). If the source
is at a distance from the MIRAN, you may have to use an extension
(not supplied).
Connecting audio devices at the MDF

The MIRAN provides two audio inputs and two audio outputs at the MDF.
Analog device connection at the MDF
137
To connect the external audio devices at the MDF, refer to Figure and
follow these steps:
1 Position the audio devices in a convenient location.
2 Obtain the required audio cables of the appropriate length. The

cable should have open wires at one end to connect to the MDF
connector block.
3 Connect each audio cable to the appropriate Analog GND and Port
terminal on the MDF. Refer to Figure for signal name and color code
of the 25-pair tip/ring cable pairs.
4 Plug the other end of each audio cable into the appropriate audio
device, as shown in the Figure.
Note: The multi-I/O adapter cable connects the I/O panel to the MDF.
Figure illustrates the external audio source and backup device connections
at the MDF. It shows two audio inputs that provide external music or
138
announcements to the MIRAN and two audio recorders that provide backup
of announcements located in the MIRAN. Analog audio sources have a
separate analog ground (AGND), and analog audio backup devices have
their own separate (AGND). An audio cable extends from the MDF to the
audio device.
Customer License(key code’s)
139
System limits
slt
TNS 32000 LEFT 30331 USED 1669

ACDN 300 LEFT 256 USED 44
AST 5000 LEFT 5000 USED 0
LTID 100 LEFT 100 USED 0
DCH 256 LEFT 255 USED 1
AML 16 LEFT 14 USED 2
RAN CON 100 LEFT 100 USED 0
RAN RTE 128 LEFT 128 USED 0
MUS CON 64 LEFT 64 USED 0
140
IDLE_SET_DISPLAY SASKEN
ACD AGENTS 100 LEFT 70 USED 30
ANALOGUE TELEPHONES
164 LEFT 145 USED 19
BRI DSL 64 LEFT 63 USED 1
DIGITAL TELEPHONES
1500 LEFT 59 USED 1441
INTERNET TELEPHONES 0 LEFT 0 USED 0
WIRELESS TELEPHONES 0 LEFT 0 USED 0
ITG ISDN TRUNKS 24 LEFT 24 USED 0
issp
VERSION 3311
RELEASE 25
ISSUE 15
IDLE_SET_DISPLAY SASKEN
IN-SERVICE PATCHES : 0
TAPE ID:
LOADED Z05
DISK/TAPE Z03055
PACKAGES
141
pkg
OPTF 1
CUST 2
CDR 4
CTY 5
RAN 7
TAD 8
DNDI 9
EES 10
INTR 11
ANI 12
ANIR 13
BRTE 14
DNDG 16
MSB 17
SS25 18
DDSP 19
ODAS 20
DI 21
DISA 22
CHG 23
CAB 24
BAUT 25
BQUE 28
NTRF 29
NCOS 32
CPRK 33
SSC 34
IMS 35
UST 35
UMG 35
ROA 36
BACD 40
ACDB 41
MUS 44
ACDA 45
MWC 46
AAB 47
142
GRP 48
NFCR 49
LNK 51
FCA 52
SR 53
AA 54
HIST 55
AOP 56
BARS 57
NARS 58
CDP 59
PQUE 60
FCBQ 61
OHQ 62
SNR 64
TDET 65
HOT 70
DHLD 71
LSEL 72
SS5 73
DRNG 74
PBXI 75
DLDN 76
CSL 77
OOD 79
SCI 80
CCOS 81
CDRQ 83
TENS 86
FTDS 87
DSET 88
TSET 89
LNR 90
DLT2 91
PXLT 92
SUPV 93
CPND 95
DNIS 98
BGD 99
RMS 100
143
MR 101
AWU 102
PMSI 103
OPAO 104
LLC 105
MCT 107
ICDR 108
APL 109
TVS 110
TOF 111
IDC 113
DCP 115
CBC 117
CCDR 118
EMUS 119
PLDN 120
COMDT 122
IDA 122
FTC 125
BKI 127
MFC 128
DTI2 129
SUPP 131
TBAR 132
ENS 133
LSCM 137
DTD 138
FFC 139
DCON 140
MPO 141
ABCD 144
ISDN 145
PRA 146
DNXP 150
CDRE 151
IAP3P 153
PRI2 154
THF 157
FNP 160
ISDN INTL SUP 161
144
SAR 162
MINT 163
LAPW 164
GPRI 167
COOP 169
ARIE 170
CPGS 172
ECCS 173
AAA 174
HVS 179
DKS 180
SACP 181
TFM 182
OVLP 184
EDRG 185
POVR 186
RPA 187
SECL 191
RCK 193
FAXS 195
FFCSF 198
IPRA 202
XPE 203
XCT0 204
XCT1 205
MLWU 206
HSE 208
MAID 210
MLIO 211
VAWU 212
EAR 214
ECT 215
BRI 216
IVR 218
MSDL 222
MSDL SDI 227
MSDL STA 228
SSAU 229
BRIT 233
FCDR 234
145
BRIL 235
ACRL 236
MCMO 240
MULTI_USER 242
ALRM_FILTER 243
SYS_MSG_LKUP 245
VMBA 246
CALL ID 247
DPNA 250
SCDR 251
ARFW 253
PHTN 254
INBD 255
ADMINSET 256
ATX 258
CDRX 259
EURO 261
UIGW 283
ADSP 289
BTD 294
MAT 296
CORENET 299
CPP 301
CPRKNET 306
PAGENET 307
PTU 308
MASTER 309
CPCI 310
OPEN ALARM 315
ETSI-SS 323
NGEN 324
RANBRD 327
MUSBRD 328
TWR1 347
ACLI 349
MC32 350
DBA 351
FDID 362
NMCE 364
FIBN 365
146
CPP_CNI 368
STS_MSG 380
CDIR 381
MERIDIAN MAIL KEYCODE
2: Serial Number : Z03055

Original Serial Number : Z03055
3: Platform : EC
4: Hours on System : 54 5: Release Number
:13.12.1
6: Number Of Nodes : 2 7: Max allowed Languages : 1
8: Maximum Full Service : 32 9: Basic Service : 0
10: Minimum MultiMedia : 0 11: Voice Channels : 32
12: Physical Channels : 32 13: SMDI Link : No
14: Meridian ACCESS : No 15: AdminPlus/MMR : No
16: AMIS : No 17: Hospitality : No
18: Networking : No 19: NMS : No
20: OutCalling : Yes 21: Voice Forms : Yes
22: Alternate UI : 1 23: Multi ADMIN : No
24: Meridian Connections : No 25: Text Notification : 1
26: VMUIF : No 27: Personal Mailbox Admin : No
28: Fax On Demand : No 29: MMail AutoAdmin : 1
30: Web OA&M : No 31: SNMP Support for SEERs : 1
32: SNMP Support for OMs : 1 33: Multi SMDI : No
34: Multi Customer : No 35: Dual Language Prompting : No
36: Voice Menus : Yes 37: Integrated Mailbox Admin: Yes
38: Maximum NMS Locations: 0
39: Max PMA Users : 0
40: Max Web OA&M Sessions: 0
41: Keycode : JVVD 8XCR FE4Q GC6F A3LF 58EC YR8D
147
MICB keycode
CONSOLE ID :100973318
KEYCODE1 :13531573
KEYCODE2 :15061470
KEYCODE3 :41774113
MAT KEYCODE
MAT 6.6 KEYCODE
9494- 3CDQ- H9FN – A21C
SL.NO. Z0305500
ORDER NO. Z03055
End User : M1 system
Application supported:
1.Station Adminstration.
2.M1 common sevices
3.ITG M1 IP trk.
4.ITG M1 Tele Commuter
5. ITG ISDN IP trk.
6.ITG IP phones.
148

Nortel Meridian Option81c Document

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nortel Meridian Option81c Document

Uploaded by

Copyright:

Available Formats

Nortel Meridian Option81c Document

Nortel Meridian Option81c Document

1. An introduction to Nortel Meridian Option81c…………………………………..03

An Introduction To Nortel Meridian Option81c

Dual Core architecture

Uninterrupted call processing

Power Supply To Option81c

03.1. Rectifier Units

Columns are grouped together in rows

Core circuit cards

CNI: PCI Core to Network Interface (NT4N65AB)

CNI Transition card: PCI Core to Network Interface Transition (NT4N66AB)

Sys Util: System Utility (NT4N67AA)

System Utility Transition card (NT4N68AA)

CP PII: Call Processor Pentium II (A0810496)

MMDU: Multi-Media Disk Unit (NT4N43AA)

Core/Net ID switch (description)

Core module ID switch settings (System Utility Transition card)

Network and Superloop cards

Network circuit cards

3PE: 3 Port Extender (QPC441)

FIJI Fiber Junctor Interface (NTRB33) - for CP PII with Fiber

Dual Ring Fiber Network

Per Sig: Peripheral Signaling (QPC43)

XNET: Superloop (NT8D04)

ENET: Network (QPC414)

Conference/TDS card (NT8D17)

CC: Clock Controller (QPC471 or QPC775)

Intelligent Peripheral Equipment

IPE circuit cards

Controller card (NT8D01)

Configuration of analog 500 set in LD - 10

Configuration of 3902 Phones

Configuration of 3901 phones

Configuration of Route Data Block in LD – 16

Route configured for CO lines circuit

Route configured for PRI circuit

Trunk configured for CO circuit

Trunk configured for PRI circuit

Configuration of DTI Trunk.

DES DID 25045XXX

Defining PRI D-Channel in LD – 17

DCHL(D-Channel loop) 58 should be defined in LD – 17 CEQU (Common Equipment)

Configuring scheduled data block ACD in LD 23

Configuring Network Class Of Service & FCR In LD – 87 & LD – 49

Configuring of Flexible Code Restriction ( FCR ) In LD - 49

Customer Data Block Creation In LD – 15

AML Data Creation

ANI Data Creation

ATT Data Creation

CCS Data Creation

CDR Data Creation

FFC Data Creation

FTR Data Creation

IMS Data Creation

NET Data Creation

NIT Data Creation

RDR Data Creation

Configuring Operator Console In LD – 12

Configuring Flexible Feature Codes ( FFC ) In LD – 57

Configuring Authorization Data Block In LD – 88

Configuring Group Hunt In LD – 18