Page 1 553-3001-358 Meridian 1, Succession 1000, Succession 1000M Meridian Integrated Conference Bridge Service Implementation Guide MICB 3 Standard 1.00 October 2003...
Page 3 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.
Page 5: Revision History
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 Page 6 of 208 553-3001-358 Standard 1.00 October 2003...
Page 7: Table Of Contents
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...
Page 8 Page 8 of 208 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...
Page 9: About This Document
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.
Page 10 Page 10 of 208 • 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 •...
Page 11 Table 1 Meridian 1 systems to Succession 1000M systems (Part 2 of 2) This Meridian 1 system... Meridian 1 Option 81C Meridian 1 Option 81C CP PII 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.
Page 12: Related Information
Page 12 of 208 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 •...
Page 13 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/...
Page 14 Page 14 of 208 553-3001-358 Standard 1.00 October 2003...
Page 15: Product Description
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: •...
Page 16 Page 16 of 208 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.
Page 17 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.
Page 18 Page 18 of 208 • 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. •...
Page 19: Hardware Overview
Hardware overview Figure 1 shows an MICB system. Figure 1 MICB system composition PC Client running Netscape or Explorer Intranet or Internet PC Client running Netscape or Explorer 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.
Page 20 Page 20 of 208 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.
Page 21 • Provides a Command Line Interface (CLI) accessible by direct connection, modem, telnet, or BUI emulation for performing OA&M functions. • Enables the reservation of one port on each card for TUI-only interaction. • Provides an embedded web-based server. • Provides a customized MICB BUI login window.
Page 22 Page 22 of 208 Figure 2 MICB card Lock Latch Maintenance LED PCMCIA Activity LED Type II/III PCMCIA Slot (for firmware upgrades and backing up and restoring data) PCMCIA Ejector PCMCIA Activity LED Type II/III PCMCIA Slot (contains configuration and application software) PCMCIA Ejector Lock Latch...
Page 23 Type II/III PCMCIA slots – The MICB faceplate provides two Type II/III PCMCIA card slots. These slots house the PCMCIA cards. Install the PCMCIA hard drive card that stores voice prompts and firmware code in the lower slot. Use the upper slot for upgrading the firmware, and backing up and restoring customer data.
Page 24: Micb Operation
Page 24 of 208 MICB operation The MICB provides flexibility in configuring conferences. Configure conferences as follows: • pre-scheduled conferences with a fixed number of ports and start/stop times • pre-scheduled conferences with a variable numbers of ports, where ports are added when required (if available) and subtracted by the system automatically as conferees leave the conference •...
Page 25 Figure 3 shows the call routing for three conferences and shows the conference chairperson access DN for each conference. The figure also shows the ACD DN for the ACD queue that controls the path of all ports on an MICB card. The right-hand side of the figure shows the distribution of MICB ports as ACD agents.
Page 26 Page 26 of 208 assigns all ports on the MICB card to the appropriate conference through the ACD DN assigned to that MICB card. The chairperson dials the chairperson DN to a specific conference. This number is different from the DN dialed by the conferees for the same conference. The MICB performs DTMF detection on MICB ports identified as chairperson ports.
Page 27 Figure 4 Single DN access method (one MICB card) Single-access DN for conferences dial-in TUI services dial-in (scheduling, recording) The DNs on the left in Figure 4 can be Phantom DNs or CDNs, instead of ACD DNs. The DNs must be DID numbers. In a dual-card system, each card requires its own single-access DN.
Page 28 Page 28 of 208 Figure 5 Single DN access method (two MICB cards) Single-access DN for simple meetings TUI services dial-in (scheduling, recording) Dual meeting chairperson DN DN ACD time overflow Single-access DN for simple meetings TUI services dial-in (scheduling, recording) Legend ACD DN...
Page 29 method; the system does not support combinations on the card or card pair. Callers to all meetings access the MICB by dialing one common fixed number. The MICB prompts the caller for the meeting or chairperson DN to enter the required meeting. In this mode of operation, configure the single-access DN in the system and MICB only.
Page 30 Page 30 of 208 Conferees can exit a conference at any time. The MICB detects when a conferee exits the conference. If enabled, the MICB announces the conferee’s name. When one conferee is on the conference, the system issues an announcement that only one conferee is present, followed by 60 seconds of music.
Page 31: Engineering Guidelines
Engineering guidelines Purpose This chapter provides guidelines for engineering MICB Release 3. Engineering guidelines can vary depending on the system platform. The chapter includes the following sections: • “System requirements” on page 31 hardware requirements for the Succession 1000M, Succession 1000, Meridian 1, and Meridian SL-100. •...
Page 32 Page 32 of 208 • End-to-end signaling (10) – required if chairperson calls locally within the same switch • Network ACD Enhanced Overflow (178), optional, but required for the dual-card configuration • The following packages are optional, but are required for billing: —...
Page 33: System Compatibility
Table 3 Hardware specifications (Part 2 of 2) Item Descriptions Real time impact Comparable to that of a digital line card (DLC). Multi-Card Maximum number of supported cards: Application Server • Dual card applications up to 5 cards • 2 Dual card applications up to 10 cards System compatibility Succession 1000M, Succession 1000, and Meridian 1 MICB 3 is compatible with the following systems:...
Page 34 Page 34 of 208 Each MICB card, using the direct meeting access method, requires the following: • One ACD group for each MICB card. • Assign ACD agent TNs/LENs and corresponding M2616 digital sets. Each configured MICB port appears as an M2616 digital set of an ACD agent.
Page 35: Lan Configuration
— 1 DN for the transfer DN, non-DID — 2 DNs for TUI access (1 for each card) This provides a total of 170 DNs, 40 of which are DID. • Assign an Ethernet port to each MICB card with an IP address, subnet mask, and gateway during installation.
Page 36 Green and Red LAN from the C-LAN. Devices that can be accessed from the World Wide Web are put into this segregated LAN segment. Nortel Networks recommends that the Green and Red LAN be the location of the MICB connection.
Page 37 Table 4 summarizes the recommended access permissions allowed by the firewall. All other paths not in the table should be denied. Table 4 Firewall access permissions Source C-LAN MICB MICB MICB Notes Take the following notes into consideration: • Technically, a firewall can be configured to enforce these access restrictions even when the MICB is in the C-LAN.
Page 38 Page 38 of 208 Figure 7 LAN/intranet access only – C-LAN connection MICB BUI MICB BUI CLAN 10/100 Base-T or 100 Base-T MICB BUI Router ELAN 10 Base-T 1. The MICB is open to Customer LAN (CLAN) tr affic, including services such as Telnet and FTP.
Page 39 E-LAN is completely separated from the C-LAN, the MICB cannot be in the E-LAN. • Nortel Networks recommends that customer try not to put any BUI traffic on the E-LAN if possible. • Each site should select the most convenient option, taking into account the physical LAN endpoints available near the MICB card.
Page 40 C-LAN. • The MICB has a broadcast-storm protection mechanism: it shuts off the LAN port (temporarily) when traffic is too heavy. Nortel Networks recommends that the MICB be put in a “quiet” LAN segment to get a better response time.
Page 41: Installation And Configuration
Installation and configuration Purpose This chapter describes how to: • prepare the system for MICB installation • install the MICB into the IPE module (Succession 1000M Cabinet or Meridian 1 Option 11C Cabinet shelf, or Succession Media Gateway slot in the Succession 1000) •...
Page 42: Succession 1000M, Succession 1000, And Meridian 1 Configuration
Remove equipment carefully from its packaging. Save the packaging, in case the card has to be returned. Inspect the equipment for faults or damage. Report any damaged component to your Nortel Networks representative and the company who delivered the equipment. Take inventory After unpacking and inspecting the equipment, verify that all necessary components are on site before beginning the installation.
Page 43 Summary The following summarizes the tasks for configuring the Succession 1000M, Succession 1000, and Meridian 1: 1 LD 23 – Define the ACD DN assigned to the MICB card. 2 Define DNs using either: LD 23 – Define ACD DNs and assign them to the MICB card. LD 10 –...
Page 44 Page 44 of 208 Table 7 LD 23 – Assign the ACD DNs for the MICB card. (Part 2 of 2) Prompt Response NCFW xxxx Note: Repeat commands in this table for each ACD DN being configured. Note: The number of DNs defined for each MICB card using direct meeting access depends on the number of conferences and bridges specified on the card.
Page 45 Figure 9 Phantom TN definitions (LD 10 MICB TYPE 500 CDEN 4D CUST 0 WRLS NO xxxx IAPG 0 HUNT TGAR 1 NCOS 0 SGRP 0 RNPG 0 XLST SCPW SFLT NO CFTD ICDD CDMD GPUD DPUD MBXD CPFA NRWD NRCD EXRO CWND...
Page 46 Page 46 of 208 Table 8 LD 11 – Configure MICB ports as digital sets. (Part 2 of 2) Prompt Response FLXA VCE, 0 ACD <ACD DN> <CLI> <pos ID> 1 SCR <any DN> 2 NRD 3 MSB 4 TRN Note: The administrator should consider chairperson dial-out restrictions through the MICB ports to prevent international dial-out.
Page 47 Page 47 of 208 Figure 10 LD 20 MICB configuration Meridian Integrated Conference Bridge Service Implementation Guide...
Page 48 Page 48 of 208 Configure DNs for a dual-card conference When a dual-card conference is defined, two meetings are defined on two cards. First, the meeting is booked on the primary card allocating the maximum free ports. Second, the meeting is booked on the secondary card allocating the rest of free ports for the dual-card conference.
Page 49 For the secondary card, configure the following DNs: • DN pairs (up to nine) – These pairs serve as chairperson and conferee DNs for single-card conferences (less than 32 ports) on the secondary card. Note: If single-number access is being used, DN pairs are not required.
Page 50 Page 50 of 208 Table 9 LD 23 – Configure the main DN for dual-card conferences. (Part 2 of 2) Prompt Response Note: Carriage return to the end and start again. TYPE NACD CUST ACDN xxxx TABL - TRGT xxxx 0 - TRGT yyyy 2 Table 10 shows a sample dialing plan for a 62-port dual-card...
Page 51: Meridian Sl-100 Configuration
Note: Because of the number and variety of DNs programmed for the dual-card setup, Nortel Networks recommends creating a dialing plan chart similar to configuring the primary and secondary card attributes, including the dual-card settings, in the administration BUI. Finally, configure each port on the primary and secondary cards as a digital set.
Page 52 Page 52 of 208 Configuration procedure Single-card installation enables up to 10 conferences on one 32-port MICB card. Each MICB card can use one MICB ACD Group to handle all the access DNs required To configure an MICB single-card conference with direct meeting access, from a maintenance administration position (MAP) terminal follow the steps in Procedure 2.
Page 53 Figure 12 LNINV example LEN CARDCODE PADGRP STATUS GND BNV MNO CARDINFO ---------------------------------------------------------------------------------------- IPE1 00 0 00 00 5D51AB NPDGP WORKING N NL Y FLXA Note: Cardcode can also be configured as an 8D02 digital line card. Figure 13 ACDGRP example ACDNAME CUSTGRP ACDRNGTH THROUTE NSROUTE PRIOPRO DBG MAXCQSIZ MAXWAIT ACDMIS MSQS DISTRING OBSWTONE FRCNGTSV OPTIONS...
Page 54 Page 54 of 208 The ACD login ID must match the MICB physical port connection to the Meridian SL-100. The ACD agents login must be in descending order, otherwise the MICB card cannot login the agents. After adding the ACD login IDs, enter the first agent’s ID in the MICB BUI (see Settings”...
Page 55 Figure 18 QLEN example LEN: IPE1 00 0 00 00 TYPE: SINGLE PARTY LINE SNPA: 214 DIRECTORY NUMBER: LINE CLASS CODE: M2616 WITH DISPLAY AND HANDSFREE CUSTGRP: ACDKEY: INCALLS CARDCODE: 5D51AB PM NODE NUMBER PM TERMINAL NUMBER : DNGRPS OPTIONS: OPTIONS: COMMUNICTR ACDNR...
Page 56 Page 56 of 208 Dual-card configuration The dual-card configuration enables a single conference to occur on two cards and have up to 62 participants depending on access type. In the dual-card configuration, one card is the primary card, and the other is the secondary card.
Page 57 Figure 20 Dual-card conference, 1 conference, 62 ports Table DNROUTE MICB1 997-1400 Table OFRT 601 997-1400 Table DNROUTE MICB1 MICB1 997-1601 997-1701 997-1602 997-1702 997-1603 997-1703 997-1604 997-1704 997-1605 997-1705 997-1606 997-1706 997-1607 997-1707 997-1608 997-1708 997-1609 997-1709 Not used for dual card conference Table DNROUTE MICB2...
Page 58 Page 58 of 208 Service Orders Add an additional ACD group for the second card. Figure 21 ACDGRP example ACDNAME CUSTGRP ACDRNGTH THROUTE NSROUTE PRIOPRO DBG MAXCQSIZ MAXWAIT ACDMIS MSQS DISTRING OBSWTONE FRCNGTSV OPTIONS ---------------------------------------------------------------------------- MICB2 BNRRCH 12 OFRT 601 OFRT 601 0 Y 2 0 N N NONE N N (ACDDISP 4) (NONIMCUT ) $ Add additional ACD subgroup information for the second card.
Page 59: Configuration Procedure
Figure 24 DNROUTE example AREACODE OFCCODE STNCODE DNRESULT ------------------------------------------------------------------ 214 997 1600 FEAT ACD MICB2 PRIM 0 0 214 997 1401 FEAT ACD MICB1 SUPP 0 (Used for Dual Card MAIN Conference) 214 997 1402 FEAT ACD MICB1 SUPP 0 (Used for Dual Card Card 1 chairperson) 214 997 1403 FEAT ACD MICB2 SUPP 0 (Used for Dual Card Card 2 chairperson) 214 997 1404 FEAT ACD MICB2 SUPP 0 (Used for Dual Card Transfer DN) 214 997 1405 FEAT ACD MICB2 SUPP 0 (Used for Dual Card Link DN)
Page 60 Page 60 of 208 Procedure 3 Configure a dual-card conference Install the two cards and their Ethernet adapters identical to single-card installation. See Note: There is no need for the two cards to be next to each other in the shelf or cabinet.
Page 61: Micb Installation And Configuration Procedures
MICB installation and configuration procedures Once the site is prepared for installation and the system software is configured, use the steps in Table 11 to complete the MICB installation. Table 11 MICB installation summary Step Description Install a serial Maintenance terminal for preliminary card setup using the following procedures: •...
Page 62 Page 62 of 208 Procedure 4 Install the Ethernet Adapter card Remove the cover plate from the I/O panel at the rear of the IPE module. Remove the I/O panel retaining screws and lift the I/O panel from the module. Set up the I/O panel filter connector for the card slot you have assigned for the MICB card installation.
Page 63 Refer to Figure 27 when connecting the Maintenance terminal (that is, VT100) in the following procedures. Figure 27 Terminal connection through the Ethernet Adapter Backplane MICB Card Indicate three ways of connecting the terminal. Procedure 5 Access the MICB directly Position the Maintenance terminal on a desk near the system.
Page 64 Page 64 of 208 Procedure 6 Access the MICB remotely using a modem Verify that the Ethernet Adapter card is on the I/O panel as described in Procedure 4 on page Plug the terminal cable DB-9 female connector into the DB-9 male connector on the Ethernet Adapter card on the I/O panel.
Page 65 Table 13 describes the DB-9 pin assignment that the next two procedures use. Table 13 DB-9 RS-232 port pin out 9-pin (male) serial connector pin # Procedure 8 Access the MICB directly – Succession 1000, Succession 1000M Cabinet, and Meridian 1 Option 11C Cabinet Position the Maintenance terminal on a desk near the system.
Page 66 Page 66 of 208 Insert the other end of the RJ11 plug into the RJ11 jack on the wall. Procedure 10 Access the MICB remotely using a LAN hub – Succession 1000, Succession 1000M Cabinet, and Meridian 1 Option 11C Cabinet Verify that the Ethernet Adapter/MAU is installed.
Page 67 • Parity: No • Flow control: none Note: Do not use XON/XFF flow control. The next step is to define IP parameters using the CLI. Procedure 13 Configure initial card parameters using the CLI From the VT-100 type terminal press the Enter key. The logon window appears.
Page 68: Micb Installation Wizard
Page 68 of 208 MICB Installation Wizard Overview The MICB Installation Wizard provides an easy method for configuring new systems. Only a user who logs in as an administrator can use the Installation Wizard. An administrator accesses the Installation Wizard by clicking on the Install Wizard link on the BUI’s MICB Dashboard.
Page 69 Conventions All Installation Wizard windows list the steps on the left of the window. During installation advance step-by-step by clicking on the Submit & Continue button. After installation is complete, access a specific step directly by clicking on its name in the list. Step 1 –...
Page 70 Page 70 of 208 Table 14 Basic Card Settings parameters (Part 1 of 2) Item Description Name Enter the card’s name. Range: Free text up to 20 characters. IP Address Shows the IP address of the card, which appears as view only. Note: Define the card address using the CLI.
Page 71 Table 14 Basic Card Settings parameters (Part 2 of 2) Item Description “From” E-mail Enter the E-mail address which the MICB uses to identify itself when sending address E-mails. This item appears in the “From:” field of sent E-mails. Note 1: Some E-mail servers require this information as a mandatory field. It cannot be empty, but it can be a non-existent address.
Page 72 Page 72 of 208 Step 2 – Access Numbers Use this step to define the access method, direct meeting or single-number, and the DNs according to system configuration. Figure 29 shows the Access Numbers window. Figure 29 Installation Wizard: Step 2 – Access Numbers window Discard input and return to previous step.
Page 73 Table 15 describes the parameters, from top to bottom, of the Access Numbers window. Configure all the DNs in this window according to system configuration. Table 15 Access Numbers parameters Item Description Use a single Enter the single DN to use for accessing all conferences. access number Use a list of This field requires a list of DN pairs, because with direct meeting access users...
Page 74 Page 74 of 208 Input the data in this window is allowed only on the primary card; on the secondary card this window appears as view only. Note: The secondary MICB card must be installed and configured first. Dual-card meeting parameters and DNs are defined in the primary MICB only.
Page 75 Table 16 describes the parameters, from top to bottom, of the Dual Card Meetings window. Table 16 Dual Card Meetings parameters Item Description IP address of Enter the IP address of the secondary card. secondary card Conference Enter the DN of the dual-card meeting. Callers will dial this number to access the access number dual-card meeting.
Page 76 Page 76 of 208 553-3001-358 Standard 1.00 October 2003...
Page 77: Browser User Interface
Browser User Interface Purpose This chapter describes how to use the Browser User Interface (BUI), a web-based application, for conference scheduling, chairperson operations, and system administration. The chapter contains the following sections: • “Overview” on page 77 and its system requirements. •...
Page 78 Page 78 of 208 User types When logging in to the MICB BUI, your login ID connects you to the server as a distinct user type. The administrator determines the user type for each user. Table 17 shows the three user types and their functionality.
Page 79 Follow the steps in Procedure 15 to login. Procedure 15 Login to the BUI Click on the LOGIN button. The window in Figure 32 appears. Figure 32 Login dialog box (Internet Explorer) Enter your login ID in the “User name” field. To log into the administrator BUI, enter an administrator ID.
Page 80 Page 80 of 208 Depending on the login ID type, Table 18 shows the windows that open when entering the BUI. Table 18 Login entry point Login entry BUI Application Regular or super-user ID Scheduling BUI. Schedule meetings from this window. Administrator user ID MICB Dashboard.
Page 81 The title bar is fixed through the entire BUI session. The following are the prerequisites for using this feature: • The image must fit reasonably in the browser window. Nortel Networks recommends that the image be no larger than 690 pixels wide and 420 pixels high.
Page 82 Page 82 of 208 Help window Clicking on the Help button on the title frame opens a separate browser window in which it displays the Help window. This enables users to continue with BUI operations while the on-line help is open. The following four different help files exist, according to user type and role: •...
Page 83: Scheduling Bui
Scheduling BUI Figure 35 shows the navigation between the Scheduling BUI windows. Figure 35 Scheduling BUI navigation flowchart Meeting control window Meetings List window Figure 36 on page 84 directly after user login. This window displays a table of the user’s meetings and provides access to scheduling operations.
Page 84 Page 84 of 208 Figure 36 Meetings List window (super-user’s display) Today – takes the current date as starting day and re-displays the table. The user can modify the date and/or the number of days and click the GO button to show a different list. If this window is accessed by a user, the window displays the conferences scheduled by that user only.
Page 85 The BUI can display past conferences, up to the “aging” factor that an administrator defines (see reaches the aging factor, the conference is deleted from the list. A super-user can view permanent conferences, but cannot edit or delete them. Therefore, the system does not display the Edit and Delete icons next to permanent conferences that are not accessed by an administrator.
Page 86 Page 86 of 208 To schedule a new conference, click on the New Conference button on the top left-hand corner of the window. A new window appears (see Figure 37). Scheduling window Click on the New Conference button, or click on the edit icon (a pencil), in the row of an already scheduled conference to open the Scheduling window.
Page 87 After scheduling a conference, view the Scheduling Confirmation window to verify the entries. See Table 20 describes the fields in the Scheduling window, by section. Table 20 Scheduling window fields (Part 1 of 2) Field Description Subject Enter text that describes the purpose of the conference. Range: Enter up to 20 characters or leave this field empty.
Page 88 Page 88 of 208 Table 20 Scheduling window fields (Part 2 of 2) Field Description Start time Enter the time that the conference starts. The minutes box shows 15-minute increments (that is, 0, 15, 30, and 45). Range: Hours/15-minute increments. Default: Current time.
Page 89 Free Ports section Figure 38 shows the how the scheduling window is expanded after clicking on the Free Ports button. The information in this window refers to the date set above it in the Scheduling window. The time scale covers 12 hours in 15-minute increments.
Page 90 Page 90 of 208 Table 21 describes the fields in the Options section. Table 21 Scheduling window – Options section fields (Part 1 of 2) Field Description User Password Enter an optional password for the conference. If configured, callers must enter this password to join the conference.
Page 91 Table 21 Scheduling window – Options section fields (Part 2 of 2) Field Description Language Select the language the system uses for voice prompts during the conference. The pull-down menu offers the set of languages available in the system. The default is the MICB card’s default language that an administrator selects using the Installation Wizard (see using single-number access, the preferred language takes affect after the caller...
Page 92 Page 92 of 208 Figure 40 Scheduling Confirmation window Click on the Edit Conference button to modify the conference. The system returns to the Scheduling window with the conference’s details displayed. In the case of a recurrent meeting, a Conference Dates section appears at the bottom of this window.
Page 93: Chairperson Operations
In the previous example, the system denied one date, because the ports were not available. Recurrent Meeting Verify Result window Figure 42 shows the window that the system displays when the Verify button is clicked when setting up a recurrent conference. Figure 42 Recurrent Conference Verify Result window The window displays the success result for each date specified in the...
Page 94 Page 94 of 208 The BUI allows only one active window per meeting. The associated voice port is the one identified as chairperson by access number. Figure 43 shows the window when a chairperson is on the call. There is a different window when there is no chairperson present (see 45 on page Figure 43 Meeting Control window –...
Page 95 Table 22 Meeting Control window fields (Part 2 of 3) Field Description Active chairperson If the chairperson joins the conference by dialing in, this field shows the CLID of the call, if available. If not available, the window displays “number not available”.
Page 96 Page 96 of 208 Table 22 Meeting Control window fields (Part 3 of 3) Field Description Status Shows regular, dial-out, or expand. Consult/End consultation Click on this button to invoke a private call with the participant. When in a button private call, an icon appears indicating this status.
Page 97 Figure 45 Meeting Control window – Chairperson not present The following features are unavailable in this mode: • Self mute/unmute • Stop/play music • Volume control • Dial out • Consult with participant After the chairperson joins the conference the window changes to the one that Figure 43 on page 94 Meridian Integrated Conference Bridge...
Page 98: Administration Bui
Page 98 of 208 Dual-card meeting Commands that a chairperson operates from the BUI in a dual-card meeting apply to participants in both cards. The feature operates as follows in a dual-card conference: • Dial-out to a specified number – dial-out works only with the “full chairperson control”...
Page 99 Figure 46 Administration BUI navigation flowchart MICB Home Page MICB Home Page MICB Dashboard Install Wizard Basic settings Access numbers Define first user Dual-card meetings Meridian Integrated Conference Bridge LOGIN (Administrator login) Login dialog box Return to Dashboard Links Settings General Confirmation E-mail Greetings...
Page 100 Page 100 of 208 MICB Dashboard The MICB organizes the Dashboard as an internet portal. The Dashboard groups links by subject (see Figure 47). Figure 47 Administration BUI MICB Dashboard window The title frame on top, which is present for all administration windows, contains the following buttons: •...
Page 101 The MICB Dashboard has the following sections: • MICB Installation Wizard • Settings • Users • Permanent Conferences • Upgrades • Call-out Groups • Reports • Backup Settings This subject groups several parameters and definitions. Links to sub-subjects appear on the Dashboard. General Settings window Figure 48 shows the General Settings window Figure 48...
Page 102 Page 102 of 208 Table 23 General Settings window fields Field Description Administration Enter the E-mail address to which the MICB sends administration material, E-mail including backup files. Billing option Select a billing option for this card from the pull-down menu. The options are as follows: •...
Page 103 E-mail template Figure 49 shows the window in which an administrator can customize the scheduling confirmation E-mail. Figure 49 MICB Dashboard – Confirmation E-mail Settings Click here to open a window that shows how the E-mail looks when the data in the window is applied. The window shows the layout of the E-mail.
Page 104 Page 104 of 208 Table 24 describes the options available in the Confirmation E-mail Settings window. Table 24 Confirmation E-mail Settings fields Field Description From The sender’s address defined in the first step of the Install Wizard. This field is view only.
Page 105 Figure 50 MICB Dashboard – Greeting Settings window Click here to submit the changes and return to the Dashboard. Note: This button does not affect the actions of the Upload and Delete buttons. The table in this window lists the available languages. For each language, the factory-made greetings can be replaced with a customized greeting in the form of a .WAV file.
Page 106 Page 106 of 208 Procedure 17 Replace the brandline greeting Upload the .WAV file from your computer to the MICB using your computer’s operating system. Click on the radio button next to the language in the table to select the language.
Page 107 Page 107 of 208 Company images upload Figure 51 shows the window that an administrator can use to customize the MICB home page image and the customer’s logo on the title frame. Images must be in GIF format. Figure 51 MICB Dashboard –...
Page 108 Page 108 of 208 Procedure 18 Use a customized image Click on the Browse button. A choose local file dialog box provided by your computer’s operating system opens. This window allows an administrator to select a file in their computer. Navigate to the folder that contains the file to upload, select the file and click on the Open button.
Page 109 Upgrades “Upgrade procedures” on page 186 how to use the Dashboard to perform card and firmware upgrades. Users This section enables an administrator to go directly to the following windows: • Users List • New User • Search Users List Figure 52 shows the User List window which is the main window for users administration.
Page 110 Page 110 of 208 The window displays a list of users in the form of a table that the systems sorts alphabetically by name. The table shows 10 users, with each user in a separate row. Click on the “Next 10” or “Previous 10” links to view additional users.
Page 111 Figure 53 MICB Dashboard – Users > Edit User Details window Submit changes to save new user definitions and return to Users List window. Add new user Click on the New User button in the User List window to access the New User window.
Page 112 Submit changes to save new user definitions and return to Users List window. Note: The password for a new user is initially 000000 (that is, six zeros). Nortel Networks recommends that the user change it during the first login session. Search for a user When the Search for User button in the Users List window is clicked, the Search for a User window opens.
Page 113 Figure 55 MICB Dashboard – Users > Search for a User window Click on one of the Search by: radio buttons to specify the field to search.The following options are available: • Name (the system treats the whole name as one string and makes no distinction between first and last name) •...
Page 114 Page 114 of 208 Import users Use the Import User button in the User List window to import the user list from the mate MICB card in a dual-card pair. This button only appears in a primary or secondary MICB card; it does not appear in stand-alone MICB configurations.
Page 115 Click on the OK button to start the import process.When the system completes the import, it updates the User List window to include imported users. At this point, the user can be deleted or modified as per normal operation. Call-out Groups This section enables an administrator to go directly the following windows: •...
Page 116 Page 116 of 208 The window displays a list of groups in the form of a table, sorted by group number. The table is read-only. Table 27 describes the information that appears in the table’s columns. Table 27 Call-Out Group List table columns Column Description Group #...
Page 117 Figure 58 MICB Dashboard – Call-Out Groups > Details window The window shows the members and properties of the selected group. The members appear in a table, with one member per row. Click on the “Next 10” or “Previous 10” link to view additional group members. Table 28 describes the columns in the Group Members table.
Page 118 Page 118 of 208 Table 28 Group Members table columns (Part 2 of 2) Column Description Checkboxes Click on a check box to select a member of the group. The Delete button at the bottom of the window can then be used to delete the group member. Before deleting the group, the system displays the following dialog box, for example: “Are you sure you want to delete these five members?”...
Page 119 Figure 59 MICB Dashboard – Call-Out Groups > Details > Add Members window Submit changes to save new user definitions and return to Group Details window. Add members by entering the phone number directly in the table. The default “Wait for Confirmation” option setting is active (that is, checked in the corresponding checkbox).
Page 120 Page 120 of 208 Figure 60 MICB Dashboard – Call-Out Groups > Details > Edit Members window Submit input to save the change and return to Group Details window. Edit the number directly in the text box. Change the “Wait for Confirmation”...
Page 121 Figure 61 MICB Dashboard – Call-Out Groups > Details > Modify Group Settings window Submit changes to save the change and return to Call-Out Group Details window. The Group number is view only. The name and parameters can be modified as described in Add a New Group Click on the New Call-Out Group button in the Call-Out Group List window to open the <New Group>...
Page 122 Page 122 of 208 Figure 62 MICB Dashboard – Call-Out Groups > <New Group> Details window Submit changes to save the new group and return to Call-Out Group List window. This window has the same layout as the Call-Out Group Details window (see Figure 58 on page Group number pull-down menu shows only available numbers (that is,...
Page 123 Figure 63 MICB Dashboard – Permanent Conferences List window The Conference List table shows a list of permanent conferences in the card. This table is similar to the regular conference table (see on page 84), except that the time-related fields (that is, start and duration) do not exist.
Page 124 Page 124 of 208 Figure 64 MICB Dashboard – New/Edit Permanent Conference window Submit the request for execution. The system responds with either a Confirmation window or an Error message. This window is similar to the regular conference scheduling window (see “Scheduling window”...
Page 125 Unlike the regular scheduling window that has pop-up sections, all fields and options appear on the basic window. Table 30 Permanent Conference New/Edit parameters (Part 1 of 2) Field Description Subject Enter text that describes the purpose of the conference. Range: Enter up to 20 characters, or leave this field empty.
Page 126 Page 126 of 208 Table 30 Permanent Conference New/Edit parameters (Part 2 of 2) Field Description Emergency Click in this box to define an emergency conference with an associated call conference group. The system automatically calls the specified group’s members from the conference when the chairperson dials the conference.
Page 127: Telephone User Interface
Telephone User Interface Purpose This chapter describes how to use the Telephone User Interface (TUI) • invoke commands during an active conference • schedule conferences and record greetings The chapter contains the following sections: • “Overview” on page 127 Interface. •...
Page 128: Tui Operation During An Active Conference
Page 128 of 208 Note: If the second feature is disable by the administrator (see the user directly enters the scheduling menu. • Administrator – An administrator does not schedule a conference. The TUI responds with a voice menu with the following two items: —...
Page 129 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. When all reserved ports are taken, the port can be available, if there are un-reserved ports on the MICB card and the port expansion feature is enabled for that conference.
Page 130 Page 130 of 208 Figure 65 Dial-out Authorization dialing example Auth Access # (Meridian SL-100) Note: In BUI, define the same sequence as above, except do not enter the command code * 0. If using this feature and Group Call, make sure that the authorization access code precedes the restricted DNs in the group call list.
Page 131 The administrator defines group call-out lists through the BUI (see “Call-out Groups” on page the MICB PCMCIA disk. The administrator must define the following options for each group list: • number of dial-out retries allowed (range: 1-3, default: 1) • time between each dial-out retry (range: 15-90 seconds, default: 30) The chairperson on an active conference can call all members of a group call-out list by dialing the following: *2 <group list number>...
Page 132 Page 132 of 208 Group Call-out Smart Retry – When the chairperson makes a group call-out to the same group for the second time, the system repeats the call-out only to numbers that are not connected in the conference. The second call-out includes calls to the following: •...
Page 133 Drop all conferees The chairperson can drop all conferees from the conference, except the chairperson, by dialing *90. The MICB does not issue an announcement to the conferees before disconnecting. After the system disconnects the conferees, the MICB card issues an announcement to the chairperson indicating that there are no conferees on the conference.
Page 134 Page 134 of 208 Table 31 Chairperson commands (Part 2 of 2) Chairperson Command Description All ports mute/unmute toggle. Self mute/unmute toggle. Release chairperson control. Count conferees and announces names to all participants. Count conferees and announces names to chairperson only. Activates a scrolling menu for the chairperson (see Drop all ports, except the chairperson’s port.
Page 135 While the system is announcing the list of conference participants after the chairperson enters *69, the chairperson can execute the commands in Table 33. Table 33 Chairperson commands during count command Chairperson dials ... Features available to all participants Self mute/unmute toggle All conference participants, including the chairperson, can put themselves on mute by dialing *19.
Page 136 Page 136 of 208 Adjust the audio volume of a conference Follow the steps in Procedure 19 to adjust the volume of a conference. Procedure 19 Adjust the conference audio volume Dial *7 to adjust the volume. Figure 66 shows how the keypad operates this feature.
Page 137 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 a person and then dials **, the chairperson hears the list of commands relevant to dialing out.
Page 138: Tui Services
Page 138 of 208 Table 34 Conferee commands (Part 2 of 2) Conferee command TUI services This sections describes TUI services that are used when there is no active conference. Schedule a conference When using the TUI scheduler, first enter the TUI user ID and password.
Page 139 Procedure 21 Use the TUI to schedule a conference Dial the TUI DN. At the prompt, enter your TUI user ID. At the prompt, enter your password (6 digits). At the prompt, enter the date and time of the conference (optional). The default is the current day and time.
Page 140 Page 140 of 208 The maximum length of the greeting is 10 seconds. The system plays greetings to conference participants in the following order: 1 Initial greeting a MICB factory greeting – “Welcome to the conference call.” b Brandline greeting – “Welcome to Company XYZ’s conference call.”...
Page 141 Page 141 of 208 After recording the greeting, it can be later verified, re-recorded, or deleted. Meeting details displayed in the BUI indicate whether or not a greeting exists. This feature also applies to always-on conferences. However, for always-on conferences, only the administrator can record the conference-specific greeting.
Page 142 Page 142 of 208 553-3001-358 Standard 1.00 October 2003...
Page 143: Maintenance
Maintenance Purpose This chapter describes how to maintain and troubleshoot the MICB card and associated equipment. The chapter contains the following sections: • “Maintenance overview” on page 143 maintenance strategy. • “Diagnostic tools” on page 145 tools. • “CLI command summary” on page 149 technicians can use from the CLI to perform maintenance activities.
Page 144 Page 144 of 208 To conduct conference OA&M for an MICB card, connect a terminal to the RS-232 port or the Ethernet connector associated with that MICB card. The maintenance terminal connects to each MICB card through an IPE module I/O panel connector or through the Ethernet adapter card.
Page 145: Diagnostic Tools
Problem solving A problem can have more than one cause. To isolate the cause, a knowledge of MICB operation is required. After identifying the cause, the problem can be corrected by replacing defective cards, connecting accidentally disconnected cables, or correcting software security problems.
Page 146 Page 146 of 208 or manual busy (Man). The card goes through a series of tests. When inserted into the slot or reset, the card: • blinks three times during self-test • runs software files from the PCMCIA to the MICB card •...
Page 147 Table 35 MICB self-test sequence (Part 2 of 2) Item tested Description PCMCIA hard drive Checks the presence of the hard drive and checks the configuration information. PCMCIA Flash card Checks the presence of Flash memory and checks configuration information. Sanity monitoring Sanity monitoring is a background routine that checks the operation of system resources, such as CPU activity and memory allocation.
Page 148 Page 148 of 208 Table 36 Commands to enable/disable MICB channels (Part 2 of 2) Command LOOP STAT UNTT Meridian SL-100 diagnostic commands Each card performs diagnostic tests as part of the daily routines. Diagnostic tests can be activated from the MAP terminal on the Meridian SL-100.
Page 149: Cli Command Summary
TCP/IP connectivity test Maintenance technicians can use “ping” to test if the LAN connection is installed and configured properly. Perform a ping test in one of the following ways (they are equivalent so there is no need to try both): •...
Page 150 Page 150 of 208 Table 40 Modifying objects Command Result <cr> Accepts the current value when the Enter key is pressed. value <cr> Changes the attribute with a new value when the value is entered and the Enter key is pressed. Cancels the modification and allows the object to keep its previous value.
Page 151 MICB CLI commands Table 41 shows MICB-specific CLI commands. Table 41 MICB CLI command summary (Part 1 of 2) Menu and command Items and commands System administration: System Attributes Editor: SY Use the System Attributes Editor for initial card configuration (see Procedure 13 on page •...
Page 152: Micb Fault Isolation And Correction
Page 152 of 208 Table 41 MICB CLI command summary (Part 2 of 2) Menu and command Items and commands Protected administration: Password Editor: PS Edit passwords (see Functionality Upgrade: FU Performs a functionality upgrade. The system prompts for the number of ports and for the keycode that must be entered in three rows of eight characters each.
Page 153 Note: If the problem cannot be solved after using all available diagnostic tools and test procedures, list the symptoms observed and contact your Nortel Networks representative. Table 42 MICB equipment problems Symptoms Diagnosis Red card LED on Card is disabled or the MICB is faulty.
Page 154: Error Message Handling
Page 154 of 208 The new card reuses the keycode. The keycode remains on the PCMCIA card, which was removed from the old MICB. Enable the new card. Package the old MICB card using the packaging material from the new card. Ship the card to the repair center.
Page 155 Error messages format The general format of error messages is as follows: <serial number> <severity> <error code> <timestamp> <error text> Table 43 describes the error message fields. Table 43 Error message field formats Field Description <serial number> Four digits that provide a sequence for the messages. It starts at 0001 at power-up and increments by one for each message issued.
Page 156 Page 156 of 208 Error message procedures Follow the steps in Procedure 25 to view the on-line error message documentation. Procedure 25 Access the on-line error message analysis tool Access the CLI SM directory and enter the following: The CLI prompts you for to enter the error code. Enter the error code for which you want information: For example, enter: MNGMMI109...
Page 157 The filtering criteria are as follows: • Severity of messages – only messages with the selected severity levels appear. Any combination is possible. • Firmware component – only messages with the selected firmware component appear. Any combination is possible. • Detailing level: —...
Page 158: Backup And Restore Procedures
Page 158 of 208 Critical: yes // yes means that the message will appear MAJOR: yes MINOR: yes WARNING: yes INFO: yes DEBUG: yes Modify, Next section, Cancel // next: go to next section section [DISK_SEVERITY_FILTER] // filter CLI messages in disk file Critical: yes // yes means that the message will appear MAJOR: yes MINOR: yes...
Page 159 Backup An administrator schedules the backup from the administration BUI. Table 44 shows the items to consider when scheduling an automatic backup. Some of these items also apply to an immediate backup. Table 44 Backup considerations Item Description Content Specify which of the following items to backup (the default is never; that is, no backup; however, if another option is selected in the “Schedule”...
Page 160 Page 160 of 208 Scheduled Backup Figure 68 shows the Scheduled Backup window accessed from the MICB Dashboard. For more information about the MICB Dashboard, “MICB Dashboard” on page Figure 68 MICB Dashboard – Scheduled Backup window The administrator defines the time, destination and contents of the backup.
Page 161 Table 45 Scheduled Backup parameters (Part 2 of 2) Section Description Destination Click on an radio button to define the backup destination as follows: • • • Contents Click on one or more box as shown in the window to select the contents of the backup.
Page 162 Page 162 of 208 The Destination and Contents sections are the same as for an automatic backup. Open A CLI window by clicking on the CLI button on the top frame of the dashboard. Click on the Do Backup button to activate an immediate backup according to your selected options.
Page 163 Run the REstordb command with the parameter indicating this is a restore following an FTP download. The system prompts for the source. Select FTP. The system prompts for the following parameters: IP address, path to file, login, and password. Enter the information as appropriate and press the Enter key. The system restores the data.
Page 164 Page 164 of 208 553-3001-358 Standard 1.00 October 2003...
Page 165: Reports
Reports Purpose This chapter describes the reports that the MICB can generate. The chapter contains the following sections: • “Overview” on page 165 MICB can generate and describes where to view them. • “Short Connection Report” on page 167 Connection Report. •...
Page 166 Page 166 of 208 Table 46 describes the reports that the MICB generates. Table 46 Report summary Report Purpose Short Connection Detect faulty behavior (users are not serviced). Meetings Log Conference activity log. Overbooking Track actual usage of ports. Billing Provide billing records.
Page 167: Short Connection Report
An administrator can download the report to their PC by clicking on the Download button. The file downloads to the location defined in the local file selection dialog box of the Windows operating system. The following sections in this chapter show the report formats. Short Connection Report BUI Short Connection Report Figure 71 shows how the Short Connection Report looks when...
Page 168: Meetings Log Report
Page 168 of 208 Short port occupancy can indicate a fault condition on a port or can indicate that a user is dialing the incorrect DN. Set the short occupancy range in the System Attributes Editor menu, which can range from 0 to 30 seconds.
Page 169 Figure 72 Meetings Log Report BUI example CLI Meetings Log Report The CLI Meeting Log Browser menu displays a log of conference events for a specified date. After the system displays data, it returns to the year-month-day prompt using the last selected date as default. To interrupt the log display, enter * and press the Enter key.
Page 170: Overbooking Report
Page 170 of 208 2230 2001 15:00:45 (2220) expanded 15:01:00 (2220) entry: 24 15:03:23 (2230) ch_entry: 4 15:03:56 (2220) exit: 14 16:35:09 (2230) mmi_op lock 16:44:15 (2220) mmi_op unlock 16:45:00 (2220) closed 16:56:02 (2230) ch_com dial_out: 395945 16:57:00 (2230) ch_com return 16:58:20 (2230) ch_com redial: 395945 //Chair redialed last dialed DN// 16:59:16 (2230) ch_com ret with_party //Chair returns with called party/ 16:58:45 (2230) ch_com count...
Page 171 The table in the report shows the contents of the Overbooking Report which the BUI translates from a .CSV file. The columns in the table are as follows: • Hour – The hour of the day, from 0 to 23 where: —...
Page 172: Billing Report
Page 172 of 208 17,<max port>,<duration minutes>,<duration seconds> 18,<max port>,<duration minutes>,<duration seconds> 19,<max port>,<duration minutes>,<duration seconds> 20,<max port>,<duration minutes>,<duration seconds> 21,<max port>,<duration minutes>,<duration seconds> 22,<max port>,<duration minutes>,<duration seconds> 23,<max port>,<duration minutes>,<duration seconds> Billing Report Introduction Users can be charged for conference reservations and dial-out calls during a conference.
Page 173 BUI Billing Report Figure 74 shows how the Billing Report appears when accessed from the BUI. The table in the window shows the contents of the Billing Report which the BUI translates from the .CSV file. Figure 74 Billing Report BUI example The “Event”...
Page 174 Page 174 of 208 The file’s names consist of capital letter “B” and the date of the report (year, month and day) in the following format: Byyymmdd and have the extension CSV, where: • yyy – indicates the year (for example, “099” for 1999, “100” for 2000, “101”...
Page 175 Table 47 Billing Report contents (Part 2 of 2) Field Contents 10th Meeting start time in minutes (00-59). 11th Meeting start time in seconds (00-59). 12th Duration in hours (01-12). 13th Duration in minutes (00-59). 14th Ports (02-40). Note: For a permanent bridge the meeting date, start time, and duration fields are irrelevant and always appear as zero.
Page 176 Page 176 of 208 A billing file includes the following records: • Date stamp, for example: DATE: Aug 7 1998 • Header: time stamp hours, time stamp minutes, time stamp seconds, event, card ID, meeting ID, billing account, date, start time hours, start time minutes, start time seconds, duration hours, duration minutes, and ports •...
Page 177 Table 48 Event examples (Part 2 of 2) Example Meeting Ended – In these examples, the time stamp, card ID, meeting ID, and billing account information was available. Examples report this event for three different cases: The meeting was cancelled before it began. 10,05,00,05,1234,7,999,00 The active meeting was cancelled after it began.
Page 178 Page 178 of 208 Charge Account feature To define the CDR with Charge Account feature, refer to Call Detail Recording: Description and Formats (553-3001-350) and Features and Services (553-3001-306). When a user dials out with the Billing and CDR Reports option selected, the MICB card takes the Charge Account key (consisting of the first eight digits of the user's account ID), the call ID, and the meeting ID from the charge account field for the CDR record.
Page 179: Maintenance (Error) Report
N 041 00 5211 T095019 1203 11.47 00:22:08 A 333 & CDR example scenarios The conference call was booked using the BUI by a user whose billing account is 9134513, on July 19, 1999 at 06:15 p.m., for July 20, 1999 from 08:00 a.m.
Page 180 Page 180 of 208 Figure 75 Maintenance (Error) Report BUI example Severity Err code Timestamp 0001 10:00:03 Minor BBF050 0002 10:22:43 PH603 Info 0003 11:30:08 BBF050 Minor 0004 12:15:00 BBF050 Minor 0005 12:43:20 Info PH000 0006 14:01:22 BBF050 Minor The Maintenance (Error) Report appears in the table in this window. The window shows the same text lines as those generated by the CLI SMaint/MReport command.
Page 181 The selected date must be in the past. The system discards old files that exceed the report aging number of days. If the date entered is too old, an error message appears. If the date is within the correct date range, but there are no report entries for that day, a message indicating there are no messages appears.
Page 182 Page 182 of 208 553-3001-358 Standard 1.00 October 2003...
Page 183: Upgrades
Upgrades Purpose This chapter provides procedures for upgrading your system to MICB 3 from previous releases and for upgrading sub-issues of MICB 3. The chapter contains the following sections: • “Overview” on page 183 • “Planning for an upgrade” on page 185 help prepare for an upgrade.
Page 184 Page 184 of 208 Insert a PCMCIA card into the top PCMCIA slot accessible through the MICB faceplate for external memory expansion, new voice announcements, and firmware upgrades.The available storage for voice prompts on the PCMCIA disk is 130 Mbytes, providing 260 minutes of voice recording.
Page 185: Planning For An Upgrade
A keycode protects against unauthorized MICB feature use. The keycode restricts upgrades of either the number of ports or application software to a given MICB card. Nortel Networks tracks the keycodes to allow for accurate handling of field repairs and incremental upgrades.
Page 186: Upgrade Procedures
Page 186 of 208 Managing the user community during an upgrade An important part of planning an upgrade is managing the user community. Table 51 lists items that will impact the user community during an upgrade to MICB3. Table 51 User community upgrade considerations Item Description...
Page 187 “administrator” users. Instead the system creates one default administrator, “admin” with a password of “000000”. Remove the PCMCIA from the upper socket. Nortel Networks recommends that you keep it, in case the customer wants to revert back to MICB 2.
Page 188 Page 188 of 208 Figure 77 MICB Dashboard – Card Upgrade window A ports upgrade is purchased from Nortel Networks, it comes with a new keycode for the card. Follow the steps in Procedure 31 to perform the port upgrade.
Page 189 Figure 78 MICB Dashboard – FIrmware Upgrade window The top-right corner of the window shows the current hardware and firmware versions. The firmware version takes the form of “3.xx”, where 3 is the MICB release and xx is the firmware version number. The MICB can retrieve firmware upgrade files from the following two sources: 1 A PCMCIA disk in the upper socket of the card.
Page 190 Page 190 of 208 Procedure 33 Firmware upgrade using FTP Click on the FTP Server radio button. Enter the FTP parameters in the fields the window provides as follows: Click on the Get Files button to start the FTP transfer session. After the previous steps finishes, click on the Upgrade &...
Page 191 Instruct users to dial the single DN for future conferences. Note: Make sure the notification E-mail content is still valid. Upgrade from a stand-alone to a dual-card MICB This section describes how to upgrade an MICB 3 card operating as a stand-alone MICB to be either the primary or secondary card in a dual-card configuration.
Page 192 Page 192 of 208 Procedure 36 Stand-alone card to primary card Access the MICB Installation Wizard: Step 1 – Basic Card Settings window (see radio button “Dual Card – Primary.” Click the Submit & Continue button. If 10 DN pairs are configured, the system deletes one automatically. The MICB first attempts to delete a DN pair that has no conferences scheduled against it.
Page 193: Appendix A: Password Security
Appendix A: Password security Purpose This chapter describes MICB 3 password protection and access restrictions. The chapter contains the following sections: • “Access permissions” on page 194 available with the MICB 3 system. • “Unsuccessful login attempt handling” on page 195 how the MICB handles unsuccessful logins.
Page 194: Access Permissions
Page 194 of 208 Access permissions MICB 3 provides strict password protections and other mechanisms to restrict access from unauthorized personnel (see Table 52). Table 52 Access permissions (Part 1 of 2) Access type Description of permissions Login name and password. The login name is a combination of letters and digits (HTTP server up to 10 characters in length.
Page 195: Unsuccessful Login Attempt Handling
Table 52 Access permissions (Part 2 of 2) Access type Description of permissions Remote access using FTP requires a dedicated login name and password. The (server access) name and password can contain letters and digits. The system records every successful login as an informational message in the error log.
Page 196: Password Parameters Summary
Page 196 of 208 Password parameters summary Table 53 shows the MICB 3 default login names and passwords. Table 53 Default login names and passwords Access type User BUI login (multiple users) Administration BUI login (multiple administrators) TUI login (multiple users) CLI first level CLI second level Telnet...
Page 197: Reset Passwords
Table 54 Security parameters summary (Part 2 of 2) Parameter Telnet blocking period after “maximum unsuccessful login:” is exceeded Telnet maximum unsuccessful login attempts Telnet inactivity time-out FTP inactivity time-out BUI inactivity time-out Reset passwords Follow the steps in Procedure 39 when a user forgets their password. Procedure 39 Reset forgotten passwords The administrator can reset any BUI password through the user management...
Page 198 Page 198 of 208 Follow the steps in Procedure 40 to edit or view a password from the second level of the CLI. Procedure 40 Use the second-level CLI edit password command Enter the second-level login name and password. Enter PA Admin (or pa). The CLI displays a list of available commands.
Page 199 CLI Password Editor editing session The following is a example of using a CLI password editing session to change an FTP password. Table 55 shows the font conventions that the example uses. Table 55 Password example font conventions Font Mono Bold // Italics Values in the examples are not necessarily the defaults.
Page 200 Page 200 of 208 section [TELNET] Telnet user name: micbtln Telnet password: xyzu1234 Maximum allowed Telnet login attempts: 3 Blocking period (minutes) after login failures: 60 Telnet idle timeout in minutes: 20 Modify, Next section, Cancel: // next: go to next section section [FTP] FTP user name: micbftp3 FTP password: abcd1234...
Page 201: Appendix B: Product Integrity
Appendix B: Product integrity Purpose This chapter describes MICB 3 product integrity. The chapter contains the following sections: • “Environmental specifications” on page 201 environmental specifications required by the MICB 3 system. • “Regulatory standards” on page 202 standards met or exceeded by the MICB 3 system. Environmental specifications MICB environmental requirements meet, or exceed, system requirements.
Page 202: Regulatory Standards
Page 202 of 208 Table 56 MICB environmental specifications (Part 2 of 2) Specification Storage Long Term Temperature Relative humidity Short Term (less than 72 hr.) Temperature Temperature Shock In three minutes In three minutes Regulatory standards The following tables list the safety and electromagnetic compatibility regulatory standards for the MICB, by geographic region.
Page 203 Table 57 Safety regulations (Part 2 of 2) Regulation Identifier AS3260, TS001 - TS004, TS006 JATE Electromagnetic compatibility (EMC) Table 58 lists electromagnetic emissions regulations met by the MICB card, along with the standard that lists each regulation. Table 58 Electromagnetic emissions Regulation Identifier FCC part 15 Class A...
Page 204 Page 204 of 208 Table 59 Electromagnetic immunity (Part 2 of 2) Regulation Identifier IEC 801-5 (level 4, preliminary) IEC 801-6 (preliminary) BAKOM SR 784.103.12/4.1/1 SS-447-20-22 AS/NZS 3548l NFC 98020 553-3001-358 Standard 1.00 Regulatory Agency Surge Immunity (Basic Standard) Conducted Disturbances (Basic Standard) EMC/Safety (Switzerland) Sweden EMC standard...
Page 205: List Of Terms
List of terms Automatic Call Distribution. Browser User Interface An interface that allows the administration of OA&M functions on conferences, users, and cards through a standard web browser. See Browser User Interface. Chairperson DN The directory number the conference chairperson dials to enter the conference.
Page 206: Standard 1.00 October
Page 206 of 208 DTMF Dual Tone Multi-frequency. A term describing push-button or touch-tone dialing. Electro-Magnetic Compatibility. Refers to equipment units that perform their functions without causing or suffering unacceptable electromagnetic interference from other equipment in the same environment. Electro-Magnetic Interference. Unwanted electromagnetic coupling, such as a ham radio heard on an electric organ or church music heard in hearing aids.
Page 207 MTBF Mean Time Between Failure. A measure of reliability: the time that a user may reasonably expect a device or system to work before an incapacitating fault occurs. Also, the average number of hours between one random failure and the next under stated conditions. OA&M Operations, Administration, and Maintenance.
Page 208 Page 208 of 208 553-3001-358 Standard 1.00 October 2003...
Page 210 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.

This manual is also suitable for:

Meridian 1 Succession 1000m 1000 con?guration guide

Nortel Meridian Meridian 1 Implementation Manual

About this Document

Product Description

Engineering Guidelines

Installation and Configuration

Browser User Interface

Telephone User Interface

Maintenance

Reports

Upgrades

Appendix A: Password Security

Appendix B: Product Integrity

List of Terms

Standard 1.00 October

Quick Links

Related Manuals for Nortel Meridian Meridian 1

Summary of Contents for Nortel Meridian Meridian 1

This manual is also suitable for:

Table of Contents