Nortel Meridian 1 PC Console Interface Unit User manual

553-3001-358
Meridian 1, Succession 1000, Succession 1000M
Meridian Integrated Conference
Bridge
Service Implementation Guide
MICB 3 Standard 1.00 October 2003

Test this out
Meridian 1, Succession 1000, Succession 1000M
Meridian Integrated Conference Bridge
Service Implementation Guide
Document Number: 553-3001-358
Product Release: MICB 3
Document Release: Standard 1.00
Date: October 2003
Copyright © 2003 Nortel Networks
All Rights Reserved
Produced in Canada
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant. This equipment has been tested and found to comply with the limits for a
Class A digital device pursuant to Part 15 of the FCC rules, and the radio interference regulations of Industry Canada. These limits
are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses and can radiate radio frequency energy, and if not installed and used in accordance
with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential
area is likely to cause harmful interference in which case the user will be required to correct the interference at their own expense.
SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

Meridian Integrated Conference Bridge Service Implementation Guide
Page 5 of 208
Revision history
October 2003 Standard 1.00. This document is a new document for Succession 3.0.
It was created to support a restructuring of the Documentation Library.
This document contains information previously contained in the
following legacy document, now retired: Meridian Integrated
Conference Bridge: Description, Installation, Administration, and
Maintenance (553-3001-102, 555-4001-135).

Page 6 of 208
553-3001-358 Standard 1.00 October 2003

Meridian Integrated Conference Bridge Service Implementation Guide
Page 7 of 208
Contents
About this document 9
Product description 15
Purpose 15
MICB description 15
Hardware overview 19
MICB operation 24
Engineering guidelines 31
Purpose 31
System requirements 31
System compatibility 33
Automatic call distribution resource allocation 33
LAN configuration 35
Installation and configuration 41
Purpose 41
Getting started 41
Succession 1000M, Succession 1000, and Meridian 1 configuration 42
Meridian SL-100 configuration 51
MICB installation and configuration procedures 61
MICB Installation Wizard 68
Browser User Interface 77
Purpose 77
Overview 77
Scheduling BUI 83
Chairperson operations 93
Administration BUI 98
Telephone User Interface 127
Purpose 127
Overview 127
TUI operation during an active conference 128
TUI services 138

Page 8 of 208
553-3001-358 Standard 1.00 October 2003
Maintenance 143
Purpose 143
Maintenance overview 143
Diagnostic tools 145
CLI command summary 149
MICB fault isolation and correction 152
Error message handling 154
Backup and restore procedures 158
Reports 165
Purpose 165
Overview 165
Short Connection Report 167
Meetings Log Report 168
Overbooking Report 170
Billing Report 172
Maintenance (Error) Report 179
Upgrades 183
Purpose 183
Overview 183
Planning for an upgrade 185
Upgrade procedures 186
Appendix A: Password security 193
Purpose 193
Access permissions 194
Unsuccessful login attempt handling 195
Password parameters summary 196
Reset passwords 197
Appendix B: Product integrity 201
Purpose 201
Environmental specifications 201
Regulatory standards 202
List of terms 205

Meridian Integrated Conference Bridge Service Implementation Guide
Page 9 of 208
About this document
This document is a global document. Contact your system supplier or
your Nortel Networks representative to verify that the hardware and
software described are supported in your area.
Subject
The subject of this document is the installation, configuration,
operation, and maintenance of the Meridian Integrated Conference
Bridge (MICB) as a part of the overall system. The MICB card allows
you to schedule and configure multiple simultaneous conferences.
You can install the MICB card in Succession 1000M, Succession 1000,
Meridian 1, or Meridian SL-100 systems. In the majority of places the
MICB operates the same way regardless of the system in which you
install it. When the information differs between systems, this guide
contains separate sections for the Meridian SL-100 and the
Succession 1000M, Succession 1000, and Meridian 1 (for example,
configuration information).
Note on legacy products and releases
This NTP contains information about systems, components, and
features that are compatible with Succession 3.0 Software. For more
information on legacy products and releases, click the
Technical Documentation link under Support on the Nortel Networks
home page:
http://www.nortelnetworks.com/
Applicable systems
This document applies to the following systems:
• Meridian 1 Option 11C Chassis
• Meridian 1 Option 11C Cabinet
• Meridian 1 Option 51C
• Meridian 1 Option 61

Page 10 of 208
553-3001-358 Standard 1.00 October 2003
• Meridian 1 Option 61C
• Meridian 1 Option 61C CP PII
• Meridian 1 Option 81
• Meridian 1 Option 81C
• Meridian 1 Option 81C CP PII
• Succession 1000
• Succession 1000M Cabinet
• Succession 1000M Chassis
• Succession 1000M Half Group
• Succession 1000M Single Group
• Succession 1000M Multi Group
Note that memory upgrades may be required to run Succession 3.0
Software on CP3 or CP4 systems (Options 51C, 61, 61C, 81, 81C).
System migration
When particular Meridian 1 systems are upgraded to run
Succession 3.0 Software and configured to include a Succession
Signaling Server, they become Succession 1000M systems. Table 1
lists each Meridian 1 system that supports an upgrade path to a
Succession 1000M system.
Table 1
Meridian 1 systems to Succession 1000M systems (Part 1 of 2)
This Meridian 1 system... Maps to this Succession 1000M system
Meridian 1 Option 11C Chassis Succession 1000M Chassis
Meridian 1 Option 11C Cabinet Succession 1000M Cabinet
Meridian 1 Option 51C Succession 1000M Half Group
Meridian 1 Option 61 Succession 1000M Single Group
Meridian 1 Option 61C Succession 1000M Single Group
Meridian 1 Option 61C CP PII Succession 1000M Single Group
Meridian 1 Option 81 Succession 1000M Multi Group

Page 11 of 208
Meridian Integrated Conference Bridge Service Implementation Guide
Note the following:
• When an Option 11C system is upgraded to run Succession 3.0
Software, that system becomes a Meridian 1 Option 11C Cabinet.
• When an Option 11C Mini system is upgraded to run
Succession 3.0 Software, that system becomes a Meridian 1
Option 11C Chassis.
For more information, see one or more of the following NTPs:
•Small System: Upgrade Procedures (553-3011-258)
•Large System: Upgrade Procedures (553-3021-258)
•Succession 1000 System: Upgrade Procedures (553-3031-258)
Intended audience
This document is intended for system administrators and installers.
Conventions
Terminology
In this document, the following systems are referred to generically as
“system”:
• Meridian 1
• Succession 1000
• Succession 1000M
The following systems are referred to generically as “Small System”:
• Succession 1000M Chassis
• Succession 1000M Cabinet
• Meridian 1 Option 11C Chassis
• Meridian 1 Option 11C Cabinet
Meridian 1 Option 81C Succession 1000M Multi Group
Meridian 1 Option 81C CP PII Succession 1000M Multi Group
Table 1
Meridian 1 systems to Succession 1000M systems (Part 2 of 2)
This Meridian 1 system... Maps to this Succession 1000M system

Page 12 of 208
553-3001-358 Standard 1.00 October 2003
The following systems are referred to generically as “Large System”:
• Meridian 1 Option 51C
• Meridian 1 Option 61
• Meridian 1 Option 61C
• Meridian 1 Option 61C CP PII
• Meridian 1 Option 81
• Meridian 1 Option 81C
• Meridian 1 Option 81C CP PII
• Succession 1000M Half Group
• Succession 1000M Single Group
• Succession 1000M Multi Group
The call processor in Succession 1000 and Succession 1000M
systems is referred to as the “Succession Call Server”.
Related information
This section lists information sources that relate to this document.
NTPS
The following NTPs are referenced in this document:
•Transmission Parameters (553-3001-182)
•Features and Services (553-3001-306)
•Software Input/Output: Administration (553-3001-311)
•Call Detail Recording: Description and Formats (553-3001-350)
•Large System: Planning and Engineering (553-3021-120)
•Large System: Maintenance (553-3021-500)
•Succession 1000 System: Installation and Configuration
(553-3031-210)
•Succession 1000 System: Maintenance (553-3031-500)
If you are installing the MICB in a Meridian SL-100, see the following
documents for additional information:
•IPE Reference Manual (555-4001-129)
•Alarm Clearing Procedures (555-4031-543)
•Routine Maintenance Procedures (555-4031-546)

Page 13 of 208
Meridian Integrated Conference Bridge Service Implementation Guide
•Card Replacement Procedures (555-4031-547)
•Log Report Reference Manual (555-4031-840)
The following documents apply to all platforms:
•Meridian Integrated Conference Bridge User Guide (P0989944)
shows end users how to schedule and manage a conference using
either the Telephone User Interface or the Browser User Interface.
•Meridian Integrated Conference Bridge Quick Reference Card
(P0989945) provides a list of Telephone User Interface Commands;
comes in a package of 20.
Online
To access Nortel Networks documentation online, click the Technical
Documentation link under Support on the Nortel Networks
homepage:
http://www.nortelnetworks.com/
CD-ROM
To obtain Nortel Networks documentation on CD-ROM, contact your
Nortel Networks customer representative.

Page 14 of 208
553-3001-358 Standard 1.00 October 2003

Page 15 of 208
Meridian Integrated Conference Bridge Service Implementation Guide
Product description
Purpose
This chapter describes the functional and physical characteristics of the
Meridian Integrated Conference Bridge (MICB) Release 3. Technicians
can install the MICB Intelligent Peripheral Equipment (IPE) card in a
Succession 1000M, Succession 1000, Meridian 1, or Meridian SL-100.
The chapter contains the following sections:
•“MICB description” on page 15 – describes the MICB card and
the role it plays in conference calls. Summarizes MICB features and
services.
•“Hardware overview” on page 19 – describes the hardware
components of the MICB system.
•“MICB operation” on page 24 – shows how MICB conferences
operate.
MICB description
Conference administration
The MICB card allows users to schedule and administer multiple
simultaneous conferences. Schedule conferences based on
time-of-day, duration of each conference, and number of individuals
(conferees) participating in, or ports allocated, for each conference.
Schedule a conference using either of the following:
•Browser User Interface – point and click web-page application
•Telephone User Interface – telephone keypad entries
The MICB card provides announcements and tones that relate to
specific events during conferences. These events include the following:
• advising the chairperson and conferees of the status of the
conference connection
• indicating when a conferee joins or leaves the conference, and
• warning the chairperson and the conferees when the conference is
about to expire.

Page 16 of 208
553-3001-358 Standard 1.00 October 2003
Technicians can install multiple MICB cards into a single Intelligent
Peripheral Equipment (IPE) module, a Succession 1000M or
Meridian 1 Option 11C Cabinet shelf, or a Succession 1000 Media
Gateway slot. Each MICB card can operate independently, providing up
to 32 ports for a single conference. The MICB card can support up to
ten simultaneous, separate conferences.
Each MICB card supports up to 200 users.
When users establish a single-card conference, they use the 32 ports
on the card. If two conferences are held at the same time, they need to
share the 32 ports. For example, if one user sets up a 10-port
conference, the other can set up a 22-port conference.
Technicians can connect two MICB cards to provide up to 62 ports for
a single conference. In dual mode, there can be only one dual-card
meeting per pair of cards.
The MICB supports several simultaneous conferences. The number of
conferences depends on the number of MICB ports available and the
number of participants (conferees) in each conference. The MICB
supports the following:
• maximum number of participants as follows:
— single-card: 32 participants
— dual-card: 62 participants (unless Chairperson Control over a
Dual-card Meeting is activated, in which case it is 60
participants)
• any number of conferences (up to 10) with one or more participants
in each conference
The MICB communicates with the system software by emulating a
digital line card, which allows existing software to control the operation
of the MICB. Configure each MICB port as an Automatic Call
Distribution (ACD) M2616 digital telephone set.
System overview
The MICB comes as a single card, or a pair of cards if additional ports
are required to support a dual-card meeting. Each card stands alone,
even in the dual-card configuration. For dual-card meetings, the

Page 17 of 208
Meridian Integrated Conference Bridge Service Implementation Guide
primary card uses ports on the secondary card. The following rules
apply:
• Each card (that is, the primary and secondary) has its own set of
users. There is no “common list” for both cards.
• To schedule a conference, the user logs into the card in which their
account is defined. If the user has two accounts, one on each card,
they must try each card separately to find available resources for the
conference. There is no automatic pooling between cards.
• A user or super-user can have accounts on many cards at a
company (that is, a customer can have one person who administers
multiple bridges for their company).
• Dual-card conferences can only be scheduled by users on the
primary card.
MICB conference feature summary
The MICB:
• Allows volume control by conference participants.
• Offers customized conference-specific greetings.
• Enables users to acquire and release chairperson control while in a
conference.
• Delivers pre-meeting and post-meeting participants notifications.
• Allows one chairperson per conference.
• Offers optional chairperson control on the secondary card of a
dual-card conference.
• Provides for one or more permanent bridge configurations.
• Supports multiple conferences simultaneously.
• Provides chairperson commands during an active conference.
• Provides conferee commands during an active conference.
• Allows conference extension beyond the scheduled time.
• Issues a 10-minute warning, before the conference termination.
• Supports multiple languages, including N.A. English, Spanish,
French, Brazilian Portuguese, L.A. Spanish, Mandarin, Japanese,
Korean, U.K. English, French, German, and Italian.
• Provides conference password security, requiring the chairperson
and/or the conferees to enter a Dual-Tone Multifrequency (DTMF)
password before entering the conference.
• Automatically starts and terminates conferences based on
reservations scheduled in advance.

Page 18 of 208
553-3001-358 Standard 1.00 October 2003
• Provides Group Call with smart retry.
• Provides the ability to reserve a port in each conference for the
chairperson.
• Provides “Block scheduling” for recurrent conferences, up to one
year in advance and up to 30 iterations of recurrent conferences.
• Offers an over-booking option, enabling the administrator to allocate
up to 125% of port resources (based on the idea that most
conferences are scheduled with more ports than are required).
• Provides an emergency bridge option, which creates a permanent
bridge that automatically dials a pre-determined list of DNs when
someone dials the emergency bridge DN. The emergency bridge
does not support the dual-card configuration.
• Provides automatic conference expansion, allowing additional
conferees to join the conference. For the expansion to work, the
ports hosting the additional conferees must be both unassigned and
available.
• Provides entry and 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 the first conferee joining the conference to turn off and turn
on conference music.
• 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.
• Provides recorded announcements to conferees who attempt to
enter a meeting too early or after a meeting has ended.
• Issues audible responses to conferees based on the conference
activity.
• Allows recording of a brand line (custom) greeting to replace
standard greeting.
• Provides a scheduling display that indicates meeting reference
number and whether a custom greeting has been created.
• Provides scheduling receipts e-mailed to users (receipt includes the
direct meeting access DN or the single DN access DN.

Page 19 of 208
Meridian Integrated Conference Bridge Service Implementation Guide
Hardware overview
Figure 1 shows an MICB system.
Figure 1
MICB system composition
MICB hardware design characteristics
The MICB occupies one slot in an IPE module (Succession 1000M
Cabinet or Meridian 1 Option 11C Cabinet shelf, or Succession Media
553-AAA071
2
Intelligent Peripheral
Equipment (IPE) Module
PC Client
running Netscape
or Explorer
PC Client
running Netscape
or Explorer CRT
(for initial
setup only)
2.You connect cards to the corporate Intranet/Internet through a TCP/IP Ethernet
LAN, which is a 10BaseT physical connection.
3.You connect a CRT or Terminal Emulator directly to the serial port of the MICB 3.
You require this terminal for initial installation only.You perform all administration
and maintenance activities remotely.
4. Users and administrators access the cards from their desktops, which can be on
the global internet behind a firewall.
5. MICB 3 can co-exist with MICB 2 on the same switch, with or without the MICB 2
server. There is no interaction between MICB 2 and MICB 3.
Router
TCP/IP
LAN
LAN-to-Switch
Links
1.You install up to six MICB 3 cards in an IPE shelf of the system. Each of the
MICB cards serves a specific set of users.
Intranet or
Internet
MICB 3
card(s)

Page 20 of 208
553-3001-358 Standard 1.00 October 2003
Gateway slot in the Succession 1000). The MICB card has the following
hardware interface characteristics:
• Uses the microprocessor unit (MPU) based on the 25MHz
MC68EN360 Integrated Communications Controller.
• Uses standard interface buses and personal computer memory
card international association (PCMCIA) cards and handles files
that are compatible with MS-DOS operating system on the PCMCIA
storage device.
• Accesses all 32 DS-30X voice/signaling timeslots.
• Provides echo cancelling and automatic gain control.
• Supports both the A-law and the m-law signal coding/decoding.
• Emulates an M2616 digital telephone set on each MICB port.
• Supports Card-LAN interfaces.
• Performs X12 signaling protocol messages for input/output.
• Uses digital signal processor (DSP) for conferencing and DTMF
detection.
• The DSP firmware:
— Analyzes the loudness off all received signals continuously and
selects the two loudest signals to be the active speakers.
— Handles two-way conversation in conferences with three to 62
conferees.
— Normalizes the pulse code modulation (PCM) input samples.
— Provides gain control on all output samples.
— Provides software upgrades using a PCMCIA Flash card.
• Provides self-tests of internal hardware components and allows
card monitoring and maintenance through the maintenance port;
provides enable/disable capabilities similar to existing system
cards.
• Provides one RS-232 serial port for administration and maintenance
access.
• Provides enhanced Call Detail Recording (CDR –
Succession 1000M, Succession 1000, and Meridian 1 only) and
billing options.
• Provides an optional Ethernet interface over a Maintenance
interface.