g450 Upgrade

Installing and Upgrading the Avaya G450 Media Gateway

03-602054Issue 1

January 2008

© 2008 Avaya Inc.All Rights Reserved.

NoticeWhile reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases.

For full legal page information, please see the complete document, Avaya Legal Page for Software Documentation, Document number 03-600758.To locate this document on the website, simply go to http://www.avaya.com/support and search for the document number in the search box.

Documentation disclaimerAvaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User.

Link disclaimerAvaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages.

WarrantyAvaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site:http://www.avaya.com/support

Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law.

Avaya supportAvaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site:http://www.avaya.com/support

http://www.avaya.com/support

http://www.avaya.com/support/


Issue 1 January 2008 3

About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Downloading this book and updates from the Web . . . . . . . . . . . . . . . . . 13

Downloading this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Safety labels and security alert labels . . . . . . . . . . . . . . . . . . . . . . . . 13Related resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Technical assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Within the US. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16International . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Sending us comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 1: Before you install . . . . . . . . . . . . . . . . . . . . . . . . 19Before going to site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Preparing required equipment . . . . . . . . . . . . . . . . . . . . . . . . . . 19Equipment required for installation . . . . . . . . . . . . . . . . . . . . . 19Equipment required for mounting . . . . . . . . . . . . . . . . . . . . . . 19Equipment required for installing an S8300 Server . . . . . . . . . . . . . 20Equipment required if you are not installing an S8300 Server . . . . . . . 20

Obtaining the G450 serial number . . . . . . . . . . . . . . . . . . . . . . . . 20Obtaining RFA access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Checking license file and Avaya CommunicationManager versions for a Local Survivable Processor (LSP) . . . . . . . . . . 21

Downloading a G450 license file to your laptop . . . . . . . . . . . . . . . . . 21Downloading CM license and authentication files to your laptop . . . . . . . 21Running the Automatic Registration Tool (ART)for the RAS IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Obtaining the RAS IP address and password . . . . . . . . . . . . . . . . 22Downloading recent firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . 24Obtaining the Electronic Preinstallation Worksheet (EPW). . . . . . . . . . . 24

Site requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Environmental verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Power verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Grounding verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Package contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Removing power supply units . . . . . . . . . . . . . . . . . . . . . . . . . . 27Unpacking and checking package contents . . . . . . . . . . . . . . . . . . . 27

Chapter 2: Installing the Avaya G450 Media Gateway . . . . . . . . . . 29Step 1: Mounting the G450 chassis . . . . . . . . . . . . . . . . . . . . . . . . . 29

Mounting the G450 in a rack . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Contents

4 Installation and Upgrades for the Avaya G450 Media Gateway

Brackets without cable guides . . . . . . . . . . . . . . . . . . . . . . . . 30Brackets with cable guides . . . . . . . . . . . . . . . . . . . . . . . . . . 30Attaching each mounting bracket to the G450. . . . . . . . . . . . . . . . 31Before mounting the G450 . . . . . . . . . . . . . . . . . . . . . . . . . . 31Mounting the G450 in the rack . . . . . . . . . . . . . . . . . . . . . . . . 32

Mounting the G450 on a wall . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Attaching brackets to the G450 for wall mounting . . . . . . . . . . . . . 32Fastening the G450 to the wall . . . . . . . . . . . . . . . . . . . . . . . . 33

Placing the G450 on a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Step 2: Installing the Power Supply Units . . . . . . . . . . . . . . . . . . . . . . 33Step 3: Installing the media modules. . . . . . . . . . . . . . . . . . . . . . . . . 34

Before inserting media modules into the G450 chassis . . . . . . . . . . . . 34Combination limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Allocating slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Inserting the S8300 Server module . . . . . . . . . . . . . . . . . . . . . . . . 37

Inserting media modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Step 4: Attaching ground conductors . . . . . . . . . . . . . . . . . . . . . . . . 40

General grounding requirements . . . . . . . . . . . . . . . . . . . . . . . . . 40Installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Ground conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Ground block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Restricted Access Location . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Approved grounds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Connecting the safety ground . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Attaching the ground wires . . . . . . . . . . . . . . . . . . . . . . . . . . 43Step 5: Connecting power to the G450 . . . . . . . . . . . . . . . . . . . . . . . . 44

PWR LED indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 3: Connecting devices. . . . . . . . . . . . . . . . . . . . . . . 47Step 1: Connecting data and voice devices . . . . . . . . . . . . . . . . . . . . . 47

Connecting a switch or a network data port . . . . . . . . . . . . . . . . . . . 47Connecting a computer to the Services port . . . . . . . . . . . . . . . . 48

Connecting an IP telephone. . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Connecting the telephone to the G450 . . . . . . . . . . . . . . . . . . . . 49

Connecting an ISDN BRI station . . . . . . . . . . . . . . . . . . . . . . . . . 49Connecting one ISDN BRI station to one ISDN port . . . . . . . . . . . . . 49Connecting two ISDN BRI stations to one ISDN port . . . . . . . . . . . . 49

Connecting an analog telephone . . . . . . . . . . . . . . . . . . . . . . . . . 50Connecting a DCP telephone to anMM712 or MM717 media module . . . . . . . . . . . . . . . . . . . . . . . . 52


Connecting an analog trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Connecting an E1/T1 trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Connecting an ISDN BRI trunk . . . . . . . . . . . . . . . . . . . . . . . . . . 54Connecting devices to the MM717 and MM716 media modules . . . . . . . . 55

Connecting the MM716 or MM717 front panel connectorto a punch down block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Step 2: Installing circuit protection. . . . . . . . . . . . . . . . . . . . . . . . . . 56Step 3: Connecting to the Wide Area Network (WAN). . . . . . . . . . . . . . . . 57

Connecting a WAN to the G450 . . . . . . . . . . . . . . . . . . . . . . . . . . 57Connecting a WAN link to the MM342 media module . . . . . . . . . . . . 57Connecting an E1/T1 WAN link to the MM340 media module. . . . . . . . 58Connecting an Ethernet WAN link . . . . . . . . . . . . . . . . . . . . . . 58

Connecting an external router to the G450 . . . . . . . . . . . . . . . . . . . 58Step 4: Installing the Coupled Bonding Conductor . . . . . . . . . . . . . . . . . 58

Installing the CBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Step 5: Installing the Avaya Partner Contact Closure Adjunct . . . . . . . . . . . 59

Installing the contact closure . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Step 6: Installing an 808A Emergency Transfer Panel and associated telephones 60

Chapter 4: Connecting and enabling a modem for remote access . . . 63Connecting and enabling a modem (G450 without S8300) . . . . . . . . . . . . . 63

Connecting and enabling a serial modem . . . . . . . . . . . . . . . . . . . . 63Connecting and enabling a USB modem (G450 without S8300) . . . . . . . . 68Testing the modem connection (G450 without S8300) . . . . . . . . . . . . . 73

Connecting and enabling a USB modem (G450 with S8300) . . . . . . . . . . . . 74Maintenance web pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Accessing the Maintenance web pages . . . . . . . . . . . . . . . . . . . 74Changing the modem settings on the Configure Server MaintenanceWeb Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Connecting and enabling a USB modem (G450 with S8300) . . . . . . . . . . 78Connecting and enabling the modem . . . . . . . . . . . . . . . . . . . . 78

Testing the modem connection (G450 with S8300) . . . . . . . . . . . . . . . 79If a USB CD-ROM drive is required to download software upgrades . . . . . 79

Chapter 5: Configuring the G450 . . . . . . . . . . . . . . . . . . . . . . 81

Chapter 6: After installation. . . . . . . . . . . . . . . . . . . . . . . . . 83Step 1: Testing the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Testing data connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Testing telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83


Testing trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83LSP failover testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Step 2: Removing the installation equipment . . . . . . . . . . . . . . . . . . . . 85

Chapter 7: Adding media modules and devices. . . . . . . . . . . . . . 87Adding a media module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Adding voice modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Adding WAN modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Adding a LAN device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Configuring the LAN device on the G450 . . . . . . . . . . . . . . . . . . . . 88

Recording LAN information for software configuration. . . . . . . . . . . 88Testing the LAN device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Adding a telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Connecting the telephone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Configuring the telephone on the G450 . . . . . . . . . . . . . . . . . . . . . 89

Recording telephone information for software configuration . . . . . . . 89Testing the telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Adding a trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Ordering the trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Special considerations when ordering an analog trunk . . . . . . . . . . 90Connecting the trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Configuring the trunk on the G450 . . . . . . . . . . . . . . . . . . . . . . . . 91

Recording trunk information for software configuration . . . . . . . . . . 91Testing the trunk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Adding a WAN line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Ordering the WAN line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Connecting the WAN line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Configuring the WAN line on the G450. . . . . . . . . . . . . . . . . . . . . . 92

Recording WAN information for software configuration . . . . . . . . . . 92Testing the WAN link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Adding an Avaya Partner Contact Closure Adjunct . . . . . . . . . . . . . . . . . 92

Chapter 8: Upgrading and replacing Field Replaceable Units . . . . . . 93Adding or removing G450 main board modules. . . . . . . . . . . . . . . . . . . 93

Removing and inserting the G450 main board . . . . . . . . . . . . . . . . . 93Adding or removing VoIP modules: MP20 and MP80 . . . . . . . . . . . . . . 94

Replacing the fan tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Replacing a power supply unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97


Chapter 9: Upgrading the AvayaCommunication Manager software . . . . . . . . . . . . . . 99

Upgrading the software using a CD-ROM drive . . . . . . . . . . . . . . . . . . . 99Local configuration with S8300 Media Gateway . . . . . . . . . . . . . . . . . 99

Upgrading the software without a CD-ROM drive . . . . . . . . . . . . . . . . . . 100Remote configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Performing the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Chapter 10: Upgrading the G450 firmware. . . . . . . . . . . . . . . . . 101Upgrading G450 firmware using Avaya Software Update Manager . . . . . . . . 101Upgrading G450 firmware from the primary controller . . . . . . . . . . . . . . . 102Upgrading G450 firmware using Gateway Installation Wizard (GIW). . . . . . . . 102Upgrading G450 firmware and Avaya CommunicationManager software using Avaya Installation Wizard (IW) . . . . . . . . . . . . . . 103

Upgrading G450 firmware using the CLI via FTP/TFTP . . . . . . . . . . . . . . . 104CLI commands for upgrading G450 firmware via FTP/TFTP . . . . . . . . . . 104Example upgrade via FTP/TFTP using the CLI . . . . . . . . . . . . . . . . . 105Preparing installation worksheets . . . . . . . . . . . . . . . . . . . . . . . . 105

Entering values in Server Values worksheet. . . . . . . . . . . . . . . . . 106Setting up a TFTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Setting up a TFTP on the LAN . . . . . . . . . . . . . . . . . . . . . . . . . . 107Downloading G450 firmware files to a local TFTP server . . . . . . . . . . . . 108Installing firmware from the TFTP server on the S8300 Server. . . . . . . . . 109

Copying firmware files to the /tftpboot directory of an S8300 Server . . . 110Upgrading G450 firmware using the CLI via a USB device . . . . . . . . . . . . . 111

CLI Commands for upgrading G450 firmware via a USB device . . . . . . . . 111Example upgrade using the CLI via a USB device . . . . . . . . . . . . . . . 111Downloading G450 firmware files to a local PC . . . . . . . . . . . . . . . . . 112

Chapter 11: Upgrading IP phone configuration and firmware files . . . 113Administering the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Upgrading the IP telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115TFTP IP telephone upgrade examples . . . . . . . . . . . . . . . . . . . . . . . . 116

Upgrading the 4602SW and 4602D phones . . . . . . . . . . . . . . . . . . . 117Upgrading 4620 IP phones after the script files are already stored in NVRAM 119

Failure scenarios and repair actions . . . . . . . . . . . . . . . . . . . . . . . . . 120Upgrading considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121


Chapter 12: Backing up and restoring the G450 . . . . . . . . . . . . . 123

Chapter 13: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . 125One telephone stops working. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Identifying the problem when one phone stops working . . . . . . . . . . . . 125Several telephones stop working. . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Identifying the problem when several phones stop working . . . . . . . . . . 126No power on the G450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126A trunk stops working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126A WAN line stops working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127CLI is not accessible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Appendix A: Front panel description . . . . . . . . . . . . . . . . . . . 131The front panel of the Avaya G450 Media Gateway chassis without media modules 131

Media module slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131System LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132USB ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Console port (CON) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Services port (SERVICES). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Emergency Transfer Relay port (ETR) . . . . . . . . . . . . . . . . . . . . . . 133Contact Closure port (CCA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Implement the Contact Closure feature . . . . . . . . . . . . . . . . . . . 133Router ports (ETH WAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Switch ports (ETH LAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Reset (RST) and Alternate Software Bank (ASB) buttons. . . . . . . . . . . . 134

Load firmware from a bank other than the default bank during startup . . 134The front panel of the Avaya S8300 Server . . . . . . . . . . . . . . . . . . . . . 134

S8300 Server ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135S8300 Server port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

The front panel of the Avaya MM340 media module. . . . . . . . . . . . . . . . . 136MM340 ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136MM340 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136



The front panel of the Avaya MM711 media module. . . . . . . . . . . . . . . . . 139


MM711 ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139MM711 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140







Appendix B: Technical specifications . . . . . . . . . . . . . . . . . . . 149G450 Media Gateway specifications . . . . . . . . . . . . . . . . . . . . . . . . . 149Power cord specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Appendix C: Running the Avaya Installation Wizard (Avaya IW) . . . . . 151Accessing Avaya IW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Preliminary screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153MGC configuration and upgrade options . . . . . . . . . . . . . . . . . . . . . . 156

Configuring and upgrading the server . . . . . . . . . . . . . . . . . . . . . . 156Upgrading an existing MGC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Configuring the primary controller IP addresses . . . . . . . . . . . . . . . . . . 166Gateway configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Firmware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Modem configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Telephony configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Trunk configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Adding a trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Modifying trunk parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 193


Modifying IP route configuration . . . . . . . . . . . . . . . . . . . . . . . 194Displaying trunk status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Removing a trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Configuring a trunk media module . . . . . . . . . . . . . . . . . . . . . . 197

Endpoint installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Alarm configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Password and final screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Appendix D: Running the Gateway Installation Wizard (GIW) . . . . . . 209Running the Gateway Installation Wizard (GIW). . . . . . . . . . . . . . . . . . . 209

Performing a basic configuration of the G450 . . . . . . . . . . . . . . . . . . 209Connect a modem, if necessary . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Connecting a serial modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Connecting a USB modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Test the modem connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Testing the modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Appendix E: Power supplies and adjunct systems . . . . . . . . . . . . 233Typical adjunct power connections . . . . . . . . . . . . . . . . . . . . . . . . . 234Typical adjunct power connections end-to-end . . . . . . . . . . . . . . . . . . . 235Auxiliary power for an attendant console . . . . . . . . . . . . . . . . . . . . . . 235

Local and Phantom Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236IA770 INTUITY AUDIX messaging application . . . . . . . . . . . . . . . . . . . 237

Shared resources of IA 770 coresidency. . . . . . . . . . . . . . . . . . . . . 237Where is the IA770 location and software . . . . . . . . . . . . . . . . . . . 238

Using an AUDIX trunk group as well as an AUDIX hunt group for new systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

IA770 INTUITY AUDIX installations and S8300upgrades for IA770 INTUITY AUDIX . . . . . . . . . . . . . . . . . . . . . . 238

INTUITY AUDIX LX messaging system . . . . . . . . . . . . . . . . . . . . . . . 239Call center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

About Avaya G450 announcement software . . . . . . . . . . . . . . . . . . 239Uninterruptible power supply (UPS) . . . . . . . . . . . . . . . . . . . . . . . . 242

UPS models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Terminal server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Equipment required for installing and administering the terminal server . . . 246What are the distance limits for the terminal server . . . . . . . . . . . . . . 247How is the terminal server cabling connected. . . . . . . . . . . . . . . . . . 247Connecting the IOLAN+ to the adjunct and the LAN . . . . . . . . . . . . . . 247Administering the IOLAN+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248


Connecting the IOLAN+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Setting up HyperTerminal on the computer . . . . . . . . . . . . . . . . . 249Administering the IOLAN+ the first time . . . . . . . . . . . . . . . . . . . 249Rebooting the IOLAN+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Navigating the IOLAN+ terminal server . . . . . . . . . . . . . . . . . . . . . 252Administering the gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Administering an IOLAN+ port . . . . . . . . . . . . . . . . . . . . . . . . . . 253Testing connectivity through the IOLAN+ . . . . . . . . . . . . . . . . . . . . 255Potential failure scenarios and repair actions . . . . . . . . . . . . . . . . . . 256Administering IP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Call Detail Recording (CDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Connecting CDR equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Administering CDR data collection. . . . . . . . . . . . . . . . . . . . . . . . 258Administering CDR parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 259Testing the switch-to-adjunct link . . . . . . . . . . . . . . . . . . . . . . . 260

Reliable Data Transport Tool (RDTT) package . . . . . . . . . . . . . . . . . . . . 261What does the RDTT package contain . . . . . . . . . . . . . . . . . . . . . . 261Downloading the RDTT package . . . . . . . . . . . . . . . . . . . . . . . . . 261Installing the RDTT package . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Administering the RDTT package . . . . . . . . . . . . . . . . . . . . . . . . 262Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262DS1/T1 CPE loopback jack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Installing a loopback jack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Selecting the loopback jack installation method . . . . . . . . . . . . . . 263Installing a loopback jack with a smart jack . . . . . . . . . . . . . . . . . 264Installing a loopback jack without a smart jack . . . . . . . . . . . . . . . 264

Administering a loopback jack . . . . . . . . . . . . . . . . . . . . . . . . . . 264Testing a loopback jack with a smart jack . . . . . . . . . . . . . . . . . . . . 265

Testing the DS1 span from the MM710 to the loopback jack . . . . . . . . 265Checking the integrity of local equipment . . . . . . . . . . . . . . . . . . 265Testing the integrity of data sent over the loop . . . . . . . . . . . . . . . 267Testing the DS1 span from the smart jack to the network interface termination or fiber multiplexer (MUX) . . . . . 270

Testing the DS1 span from the loopback jack to the smart jack . . . . . . 270Testing a loopback jack without a smart jack . . . . . . . . . . . . . . . . . . 274Configurations using fiber multiplexers . . . . . . . . . . . . . . . . . . . . . 276

Checking for the presence of DC . . . . . . . . . . . . . . . . . . . . . . . 277External modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Hardware required when configuring modems . . . . . . . . . . . . . . . . . 278


Multi-Tech MT5634ZBA-USB-V92 . . . . . . . . . . . . . . . . . . . . . . . . 278Configuring the MT5634ZBA-USB-V92 modem . . . . . . . . . . . . . . . 279

Multi-Tech MT5634ZBA-V92-GLOBAL . . . . . . . . . . . . . . . . . . . . . . 279Administering Multi-Tech modems . . . . . . . . . . . . . . . . . . . . . . . . 279

Busy tone disconnect equipment for non-U.S. installations . . . . . . . . . . . . 280Music-on-hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Installing a non-FCC-registered music source on a G450Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Connecting a non-FCC-registered music-on-hold source to a G450 using a KS-23395-L3 coupler . . . . . . . . . . . . . . . . . . . . . . . . 282

Connecting a non-FCC-registered music-on-hold source to a G450 using a KS-23395-L4 coupler . . . . . . . . . . . . . . . . . . . . . . . . 283

Installing an FCC-registered music source on a G450 MediaGateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Connecting an FCC-registered music-on-hold source to a G450 usinga KS-23395-L4 coupler . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Paging and announcement equipment . . . . . . . . . . . . . . . . . . . . . . . 285Hooking up loudspeaker paging from a G450 Media Gateway . . . . . . . . . 285

Adjunct Information Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Call Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286INTUITY AUDIX Messaging Systems . . . . . . . . . . . . . . . . . . . . . . . 287Avaya Modular Messaging System . . . . . . . . . . . . . . . . . . . . . . . . 287Avaya Interactive Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Avaya EC500 Extension to Cellular and Off-PBX Stations . . . . . . . . . . . 287Avaya SIP Enablement Services . . . . . . . . . . . . . . . . . . . . . . . . . 287Call Accounting Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Appendix F: Information Checklists . . . . . . . . . . . . . . . . . . . . 289Installer's Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Serial Number and Login Information . . . . . . . . . . . . . . . . . . . . . . . . 291

G450 Serial Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Quick Setup for G450 Media Gateway Processor (MGP) . . . . . . . . . . . . . . 292Installation Site Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Appendix G: Equipment List . . . . . . . . . . . . . . . . . . . . . . . . 295

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305


About this book

Downloading this book and updates from the WebYou can download the latest version of Installing and Upgrading the Avaya G450 Media Gateway from the Avaya Support website. You must have access to the Internet, and a copy of Acrobat Reader must be installed on your personal computer.

Avaya makes every effort to ensure that the information in this book is complete and accurate.However, information can change after we publish this book. Therefore, the Avaya Support website might also contain new product information and updates to the information in this book. You can also download these updates from the Avaya Support website.

Downloading this book1. Access the Avaya Support website at http://www.avaya.com/support/.

2. Click FIND DOCUMENTATION and TECHNICAL INFORMATION by PRODUCT NAME.

3. Type this book’s document number (03-602054) in the Search box.

4. Click GO.

The search results appear.

5. Locate the latest version of the book.

6. Click the book title. Your browser downloads the book.

Safety labels and security alert labelsObserve all caution, warning, and danger statements to help prevent loss of service, equipment damage, personal injury, and security problems. This book uses the following safety labels and security alert labels:

! CAUTION:CAUTION: A caution statement calls attention to a situation that can result in harm to

software, loss of data, or an interruption in service.

http://www.avaya.com/support/

About this book


! WARNING:WARNING: A warning statement calls attention to a situation that can result in harm to

hardware or equipment. A warning can also indicate the presence of a hazard that could cause personal injury if the hazard is not avoided by following the instructions provided.

! DANGER:DANGER: A danger statement indicates the presence of a hazard that can result in severe

personal injury or death if the hazard is not avoided by following the instructions provided.

ELECTROSTATIC ALERT:ELECTROSTATIC ALERT: An ESD warning calls attention to situations that can result in ESD damage to electronic

components.

! SECURITY ALERT:SECURITY ALERT: A security alert calls attention to a situation that can increase the potential for

unauthorized use of a telecommunications system.

Related resources


Related resourcesFor more information on the Avaya G450 Media Gateway and related features, see the following books:

Title Number

Overview for the Avaya G450 Media Gateway 03-602058

Quick Start for Hardware Installation for the Avaya G450 Media Gateway

03-602053

Administration for the Avaya G450 Media Gateway 03-602055

Avaya G450 CLI Reference 03-602056

Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers

03-300430

Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers

03-300431

Maintenance Procedures for Avaya Communication Manager, Media Gateways and Servers

03-300432

About this book


Technical assistance Avaya provides resources for technical assistance within the US and internationally.

Within the US● Call the Avaya Technical Consulting Support System at 1-800-225-7585 for help with

feature administration and system applications.

● Call the Avaya National Customer Care Support Line at 1-800-242-2121 for help with maintenance and repair.

● Call Avaya Toll Fraud Intervention at 1-800-643-2353 for help with toll fraud.

InternationalContact your local Avaya authorized dealer for all international resources.

TrademarksAll trademarks identified by ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.

Sending us comments


Sending us comments Avaya welcomes your comments about this book. To reach us by:

● Mail, send your comments to:

Avaya Inc.

Product Documentation Group

Room B3-H13

1300 W. 120th Ave.

Westminster, CO 80234 USA

● Email, send your comments to:

[email protected]

● Fax, send your comments to:

1-303-538-1741

Ensure that you mention the name and number of this book, Installing and Upgrading the Avaya G450 Media Gateway, 03-602054.

About this book



Chapter 1: Before you install

Read this chapter carefully before you begin the installation. If you are installing the G450 at a customer site, read this chapter before going to the customer site.

Before going to siteBefore going to the site, it is necessary to read the planning documentation and prepare equipment required for installation.

Preparing required equipmentMake sure you have the necessary equipment to assist you in the installation before you start working.

Equipment required for installation

● One loop start analog trunk for connecting a modem

● A separate telephone line, if needed, for verbal communication during remote configuration

Equipment required for mounting

● A crosspoint screwdriver if rack mounting or wall mounting the G450

● If you will mount the G450 on a flat wall: screws to fasten the G450 to the wall

● If you will mount the G450 on a non-flat wall:

- A plywood sheet at least ½ in (1.2 cm) thick and at least 2 x 2 ft (0.6 x 0.6 m) in size- Wood screws to fasten the G450 to the plywood- Screws to fasten the plywood board to the wall

Before you install


Equipment required for installing an S8300 Server

● One USB modem. The only supported USB modem is the Multitech MultiModemUSB MT5634ZBA-USB-V92.

● One USB CD-ROM drive

● A laptop computer with MS Internet Explorer

Equipment required if you are not installing an S8300 Server

● A PC on the local network, optionally with a USB flash drive

● A laptop computer running Windows XP or Windows 2000 with a serial port recognized by the operating system on the laptop. If the port is recognized, it is listed by the Device Manager.

● A modem to connect to the G450 to enable dial-in configuration. The G450 supports the Multitech MultiModemZBA MT5634ZBA-V-V92 serial modem and the Multitech MultiModemUSB MT5634ZBA-USB-V92 USB modem.

Obtaining the G450 serial numberLook for the serial number sticker on the back of the G450 chassis, to create the customer’s license file. If the unit is delivered directly to the customer and you will not have phone or LAN line access from the customer site to access the http://rfa.avaya.com website, this task will require a preliminary trip to the customer site.

Obtaining RFA accessYou need to obtain a personal Single Sign-On (SSO) for Remote Feature Activation (RFA) website authentication login before going to the site for installation. You must complete the authentication process before you can be assigned an SSO authentication login.

As a first-time user:

● Business Partners should point their browsers to the Business Partner portal option sales_market, services-voice, training tools and procedures to select RFA

● Associates should point their browsers to the Avaya Associate portal

● Contractors should point their browsers to Avaya.com

● Alternatively go directly to http://rfa.avaya.com.

From that point, log into SSO and complete the process to obtain your personal login.

https://sso.avaya.com/AvayaLogin.jsp?TYPE=100663297&REALMOID=06-3b840a0a-a97b-001d-0000-22d4000022d4&GUID=&SMAUTHREASON=0&TARGET=https://rfa.avaya.com/index.jsp


Before going to site


Checking license file and Avaya CommunicationManager versions for a Local Survivable Processor (LSP)

If you are installing an S8300 as a Local Survivable Processor (LSP), the license file for the S8300 must have a feature set that is equal to or greater than that of the server that acts as primary controller (an S8300, S8400, S87xx, or S85xx). This is necessary so that if control passes to the LSP, it can allow the same level of call processing as that of the primary controller.

Additionally, the LSP must have a version of Avaya Communication Manager (CM) that is identical to that of the primary controller.

The license file requirements of the LSP should be identified in your planning documentation.

Downloading a G450 license file to your laptopIf you are installing VPN, obtain a VPN license file from the Remote Feature Activation (RFA).

1. Use Windows File Explorer or another file management program to create a directory on your laptop for storing license files (for example, C:\licenses).

2. Access the Internet from your laptop and go to http://rfa.avaya.com.

3. Login using your SSO login and password. The AFS and RFA information home page appears.

4. Start the RFA application from the RFA information page. To create and download the license file, follow the instructions outlined in the Avaya Remote Feature Activation (RFA) User Guide, 03-300149.

Once the G450 license file is downloaded to your PC, you can use either the Avaya Installation Wizard or the Gateway Installation Wizard to install the license file in the G450. See Running the Avaya Installation Wizard (Avaya IW) and Running the Gateway Installation Wizard (GIW).

Downloading CM license and authentication files to your laptopIf you are installing a G450 with an S8300 Server as a primary controller, you need license and authentication files for the Communication Manager.

1. Use Windows File Explorer or another file management program to create a directory on your laptop for storing license and authentication files (for example, C:\licenses).

2. Access the Internet from your laptop and go to http://rfa.avaya.com.

3. Login using your SSO login and password. The AFS and RFA information home page appears.



Before you install


4. Start the RFA application from the RFA information page. To create and download the license file and authentication file, follow the instructions outlined in the Avaya Remote Feature Activation (RFA) User Guide, 03-300149.

5. Use the download or email capabilities of the RFA website to download the license and authentication files to your laptop.

Once the Communication Manager license and authentication files are downloaded to your PC, you can use the Avaya Installation Wizard to install them (see Running the Avaya Installation Wizard (Avaya IW). You can also use the Maintenance Web Interface to install the Communication Manager license and authentication files.

Running the Automatic Registration Tool (ART)for the RAS IP address

The ART tool is a software tool that generates a remote access (RAS) IP address and password, for accessing a product attached to a customer’s modem. This IP address is required for configuring remote access to a modem on the S8300 or G450. If you need to configure remote access to both the G450 and the S8300, follow this procedure twice, once for the G450 and once for the S8300. For each procedure, a script file is created and downloaded or emailed to you. You can use the installation script to automatically set up an IP address and other alarming parameters.

When you run GIW, you will have the opportunity to import the Electronic Planning Worksheet (EPW). The ART information will be imported along with all the other information in the EPW. Alternatively, if the G450 will be configured using the CLI, keep the installation script to run as a CLI command at the configuration stage.

If the G450 will be configured using Gateway Installation Wizard (GIW) or Avaya Installation Wizard (AIW), and you have an EPW, enter the ART information contained in the installation script into the EPW.

Note:Note: ART is available only to Avaya associates. Business Partners call 800-295-0099.

Note:Note: You must generate a license file, and for the S8300– also an authentication file,

before you use the ART tool. In addition, the ART process is available only to Avaya personnel. You need an ART user name and password, which you can set up at the ART website. Non-Avaya personnel must contact their service support or customer care center for INADS addresses, if required.

Obtaining the RAS IP address and password

1. Access the ART website on your laptop at http://art.dr.avaya.com.

http://art.dr.avaya.com

Before going to site


2. From the User menu, select Administer an S8xxx, G450, CCS, CVLAN, or ASGGuard II. The Enter Network Password dialog box appears.

3. Enter your ART user name and password.

4. Click OK.

The Start of Installation script & IP Addr Admin screen appears.

5. In the FL Number field, enter the customer’s FL number.

6. In the Session Type field, select Installation Script Administration.

7. In the Product Type field, select G450 MEDIA GATEWAY if you want to configure remote access for the G450, or S8300 SERVER if you want to configure remote access for the S8300.

8. In the INADS field, enter the number of the telephone line to which you will connect the modem.

9. Click Start Installation script & IP Addr Admin. ART validates your input and the Customer Validation screen appears.

10. Read the customer information displayed, to check that it is correct.

11. In the Customer Type field, select Other.12. Click Continue Installation Script Administration. A product list appears.

13. Click the number of the product for which you are configuring remote access. The G450 MEDIA GATEWAY Installation Script Administration Data screen appears.

14. In the Product Name field, enter the product name.

15. In the INADS Number field, make sure the correct customer provided dial-in number for the G450 Media Gateway appears.

16. Click Continue Installation Script Administration. ART generates the RAS IP address and password (CHAP secret key) and generates an installation script for the product. Keep the RAS IP address and password to configure your modem later.

17. Click Download Installation Script File to download the installation script to your laptop, or Email Installation Script File to have the script emailed to you.

A script file is created and downloaded or emailed to you.

Before you install


Downloading recent firmwareDownload any recently updated firmware for the G450 and media modules to your laptop. Visit the Avaya Support website to check the latest firmware image file versions against the factory installed versions in the hardware you are installing. Download any firmware image file upgrades you need from the Avaya Support website, and any Communication Manager service packs that may be required for the upgrade.

Obtaining the Electronic Preinstallation Worksheet (EPW)The EPW is an Excel spreadsheet from which Avaya configuration wizards automatically pull data to configure and install the S8300 Server and the G450 Media Gateway. The EPW is filled in by the customer and project manager, and should be completed before installation.

For greatest efficiency, obtain the Electronic Preinstallation Worksheet (EPW) from the Avaya Support website at http://support.avaya.com/avayaiw.

Site requirementsInspect the site before you begin the installation. Verify that the site requirements have been met for adequate environmental conditions, power and grounding availability, safety, and security conditions. If you find discrepancies between the specifications necessary for proper installation of equipment and the conditions on site, contact your project manager before proceeding with the installation.

The G450 may be installed in a 19” rack, mounted on a wall, or placed on a sturdy table. Installation instructions are provided in Chapter 2: Installing the Avaya G450 Media Gateway. The surrounding temperature should be in the range 0-40°C. The humidity should not be higher than 90%.

Environmental verificationVerify that temperatures and clearances are within the recommended technical parameters. Consult the table of Technical Specifications in Appendix B: Technical specifications.

Site requirements


! WARNING:WARNING: Verify that temperature and clearance ranges are within tolerable limits. The

thermal sensors may shut down equipment if it is subjected to conditions beyond the recommended limits. Equipment can be damaged if these restrictions are not respected.

Power verificationCheck that an adequate number of power outlets are available. Verify that the G450 Media Gateway and the other equipment in the rack do not present a possible overcurrent or overload to the customer's branch circuit and/or power distribution strip. Power requirements are listed in Power cord specifications on page 150.

! WARNING:WARNING: Do not overload the power circuit.

Grounding verificationEnsure that the installation site has access to approved grounds and that either a trained technician or a licensed electrician will be verifying all grounds and installing the Supplementary Ground Conductor (consult Step 4: Attaching ground conductors).

Before you install


! WARNING:WARNING: Installation in a Restricted Access Location and secure access are required in

Finland, Norway, and Sweden. The G450 Media Gateway relies on two ground connections: first, the mains plugs for the power supplies are required to be connected to AC outlets that have earth contacts; and second, the Supplementary Ground Conductor provided with the system provides a non-removable ground even when the AC cords are disconnected. However, because of unreliable earthing concerns in Finland, Norway, and Sweden, the G450 Media Gateway must be installed in a Restricted Access Location (RAL). An RAL is defined as an access that can be gained only by trained service personnel or customers who have been instructed about the reasons for the restricted access and any safety precautions that must be taken. In these cases, access to the G450 Media Gateway is gained by the use of a tool (such as a lock and key) or other means of security. If you have any questions about the safety conditions, contact your project manager. When you have verified that the site is ready for a safe installation, proceed with the installation.

Package contentsThe G450 chassis and accessories are shipped in a box. The package should contain the following items:

● One Avaya G450 Media Gateway chassis. The required media modules may be installed.

● One accessories box, containing:

- One power cord. If the power cord provided does not have the correct plug configuration needed in a particular country, see the power cord specifications in Appendix B: Technical specifications.

- Two standard mounting brackets- One mounting bracket with cable guides- One Supplementary Ground Conductor- Fifteen 3/8” flat head screws- One 5/16” crosspoint screw for grounding- One washer for grounding- Four rubber feet- One jumper for bridging NVRAM init pins

The Avaya Partner Contact Closure adjunct box, if ordered, is packaged separately.

Package contents


Removing power supply unitsFor ease of installation and to enable single-person installation, it is recommended to remove the power supply unit(s) before unpacking the G450.

1. Open the package. Note that the G450 is lying flat. Turn it so that the rear panel is facing up.

2. Remove the power supply unit (PSU). If you ordered two PSUs, remove them both.

a. Loosen the two PSU captive screws, one on each side of the PSU.

b. Grasp the two side handles and pull the PSU up and out.

c. Place the PSU carefully on the table.

Unpacking and checking package contents1. Unpack the G450 and accessories.

ELECTROSTATIC ALERT:ELECTROSTATIC ALERT: Wear an anti-static wrist ground strap whenever handling components of an

Avaya G450 Media Gateway. Connect the strap to an approved ground, such as an unpainted metal surface.

2. Check the contents of the packaging against the customer order.

3. Cross-check the customer order with the planning documentation you have been given. Media modules, telephones and other equipment are listed on your planning and shipping documentation. Placement for the media modules and other equipment are also indicated.

4. Verify that all necessary elements have been received and are in good condition. If there are missing or damaged elements, contact your project manager. The planning documentation will list contact information for key personnel.

If you have any questions about the equipment order, or if the equipment has been damaged, contact your project manager.

Before you install



Chapter 2: Installing the Avaya G450 Media Gateway

Installing the Avaya G450 Media Gateway consists of installing the chassis, power supply, and media modules, attaching ground conductors, and connecting the power.

Step 1: Mounting the G450 chassisYou can mount the G450 in a rack, on a wall, or on a table.

ELECTROSTATIC ALERT:ELECTROSTATIC ALERT: When handling any components of an S8300 Server or G450 Media Gateway,

wear an anti-static wrist ground strap. Connect the strap to an approved ground, such as an unpainted metal surface.

Note:Note: Avaya has developed special hardware platforms for customers with harsh

environmental conditions. These platforms have been tested to meet stringent physical and environmental requirements (i.e., shock, vibration, EMI, etc.) imposed by the United States Navy for use on their ships. The platforms make use of specialized racks and reinforcements. If you wish to obtain information about the design and implementation of such a ruggedized solution, contact the Avaya Navy Shipboard Services organization.

Mounting the G450 in a rackThe G450 mounts in a standard 19-inch rack.

You can fasten the G450 to the rack either at the front of the G450 or at the middle. In either case, mounting brackets must be attached to the G450.

There are two types of mounting brackets provided with the G450:

● Without cable guides. Two mounting brackets without cable guides are provided.

● With cable guides. One mounting bracket with cable guides is provided. This bracket provides guides for electrical cables and is useful for cable management.

Installing the Avaya G450 Media Gateway


Brackets without cable guides

Mounting brackets without cable guides can be attached in either of the following positions:

● To each side of the front of the G450 for fastening the unit to the rack at the front

● To the middle of each side panel of the G450 for fastening the chassis to the rack at the middle

Figure 1: Attaching a mounting bracket to the front of the G450

Figure 2: Attaching a mounting bracket to the middle of the G450

Brackets with cable guides

You can attach the mounting bracket with cable guides to the front of the G450 at one side, as shown in the following figure. If you are fastening the chassis to the rack at the front, use the mounting bracket with cable guides as one of the two front brackets. If you are fastening the chassis to the rack at the middle, use the mounting bracket with cable guides at the front of the chassis, in addition to the two regular mounting brackets on the sides of the chassis. In this case, the mounting bracket with cable guides serves for cable management only — you do not fasten it to the rack.

Step 1: Mounting the G450 chassis


Note:Note: It is recommended to attach the mounting bracket with cable guides to the left

side of the rack, so that the cables will not interfere in case you replace the fan tray. However, if you are installing an MM717 or MM716 media module, attach the mounting bracket with cable guides to the right side of the rack, to support the weight of the amphenol cable you will connect to the MM717 media module. See Connecting a DCP telephone to an MM712 or MM717 media module on page 52.

Figure 3: Attaching a mounting bracket with cable guides

Attaching each mounting bracket to the G450

The G450 is held in place by mounting screws through the two mounting ears. Fill racks from the bottom; that is, mount units in the lower positions first, to avoid balancing problems and cabling complications.

1. Position a bracket over the desired mounting position.

2. Affix the bracket to the chassis with five of the fifteen 6-32 x 3/8 screws provided.

3. Tighten with a screwdriver.

Before mounting the G450

● Ensure that the rack is bolted to the floor and is earthquake-protected, if required. If the rack is not securely fixed in place, do not proceed with the installation.

● If the G450 is being mounted in a rack with other equipment already installed, the G450 must be positioned to avoid imbalance.

Note:Note: The G450 weighs 21 pounds (9.5 kg) empty and between 37.5 and 39.5 pounds

(between 17 and 18 kg) when equipped with media modules, an S8300 Server, and two Power Supply Units.



Mounting the G450 in the rack

The G450 is designed for single-person mounting. This assumes that the power supplies were removed (see Removing power supply units on page 27).

1. Insert two mounting screws, one on either side of the rack. These will be the bottom screws of the mounting brackets. Turn the screws only 3-4 times, so that a part of them is protruding.

2. Position the G450 in the rack so that the bottoms of the brackets are resting on the protruding screws.

3. Position the G450 in the rack. Ensure that there is adequate ventilation.

4. Insert four rack mounting screws, two on each side.

5. Tighten the rack mounting screws. Avoid overtightening.

6. Either tighten the two bottom-most screws inserted in step 1, or remove them completely.

7. Verify that ventilation vents are not obstructed.

At this point, you have mounted the G450 chassis in the rack and are ready to insert media modules as required in the planning documentation.

Mounting the G450 on a wallTo mount the G450 on a wall, use the two mounting brackets without cable guides. You can also add a mounting bracket with cable guides if desired, as explained in Brackets with cable guides on page 30.

! WARNING:WARNING: Only service-trained personnel are to wall-mount the G450.

! CAUTION:CAUTION: A fully loaded G450 weighs 40 pounds (18 kg). It weighs 30 pounds (13.4 kg) if

both power supply units were removed. Use lifting precautions. A minimum of two installers is required to wall-mount a G450.

Attaching brackets to the G450 for wall mounting

Attach a bracket to each side of the G450, as shown in the figure below.

Step 2: Installing the Power Supply Units


Figure 4: Attaching a bracket to each side of the G450

Fastening the G450 to the wall

The plywood and the hardware to mount the plywood are installer-provided.

1. If the wall does not have a portion of plywood available, mount a plywood sheet at least ½ in (1.2 cm) thick and at least 2 x 2 ft (0.6 x 0.6 m) in size, horizontally onto the wall. Make sure the plywood screws are sufficiently anchored in the wall. Use a minimum of four wood screws and ensure the screws are driven into wall studs, or use four wall anchors rated not less than 50 pounds (22.5 kg) shear strength each.

2. Mark the plywood with the location of the G450 bracket screw holes before fastening the plywood to the wall.

3. Position the G450 so that its front panel is facing up, and secure it to the plywood using a minimum of four screws (pan head at least ½ in, # 10-12 screw).

Placing the G450 on a tableIf you will be installing the G450 as a tabletop unit, you need to affix the provided rubber feet to the underside of the G450.

1. Remove the four feet from their packaging.

2. Turn the G450 upside down.

3. Position each foot into one of the mounting sites, near each corner of the chassis.

Step 2: Installing the Power Supply UnitsWhen the G450 chassis is installed, first insert the power supply unit(s) if you removed them before installation (refer to Removing power supply units on page 27).



1. Position the power supply unit before the opening at the rear of the G450 and engage both sides of the PSU in the interior guides.

2. Slide the PSU slowly into the chassis, maintaining an even pressure to assure that the PSU does not become twisted or disengaged from the guides.

3. Close and tighten the two PSU captive screws, one on each side of the PSU.

Figure 5: Inserting the power supply unit

Step 3: Installing the media modulesWhen the G450 chassis is installed and the power supply unit(s) have been inserted, you can insert the media modules. Each module is shipped with two thumb screws for securing the position of the module in the G450 chassis.

Note:Note: The required media modules are sometimes pre-installed in the G450 chassis. If

this is the case, skip this step. Read this section only if the media modules are not pre-installed, or if you want to replace modules or add new media modules.

Before inserting media modules into the G450 chassis● Do not install an unsupported combination of media modules. See Combination

limitations on page 35.

● Allocate a permissible slot to each media module. See Allocating slots on page 35.

Step 3: Installing the media modules


! WARNING:WARNING: The Avaya G450 Media Gateway must not be operated with any open slots.

Failure to cover empty slots with the supplied blank plates can cause overheating due to inadequate air distribution.

Combination limitationsThe following limitations apply to combining media modules in the G450:

● 3 MM340/MM342 WAN modules

● The MM760 is not supported

Allocating slotsYou insert media modules into the slots marked V1, V2, V3, V4, V5, V6, V7, and V8 on the G450 front panel, shown in Figure 6 below.

Allocate a slot for the media module. Make sure your slot allocations allow a permissible slot for every media module.



Figure 6: The G450 front panel ports and slots

Figure notes:

1. System LEDs2. USB ports3. Console port4. Services port5. ETR (Emergency Transfer Relay) port6. CCA (Contact Closure) port7. ETH WAN ports8. ETH LAN ports9. RST button

10. ASB button

11. V1 — slot for standard media module or S8300 Server

12. V2 — slot for standard media module13. V3 — slot for standard media module14. V4 — slot for standard media module15. V5 — slot for standard media module16. V6 — slot for standard media module17. V7 — slot for standard media module18. V8 — slot for standard media module

Table 1: Permitted slots for media modules

Media module Permitted slots Description

MM340 V3, V4, V8 Provides one E1/T1 WAN port for connecting to a WAN endpoint device.

MM342 V3, V4, V8 Provides one USP WAN port for connecting to a WAN endpoint device.

MM710 V1 – V8 Provides one E1/T1 trunk port for connecting an E1/T1 telephone trunk.

MM711 V1 – V8 Provides eight universal analog ports for connecting analog telephones or trunks.

MM712 V1 – V8 Provides eight ports for connecting DCP telephones.

MM714 V1 – V8 Provides four analog ports for analog telephones and four analog ports for analog trunks.

1 of 2

1 2 3 4 5 6 7 8

109

11

12

13

14

15

16

17

18



Inserting the S8300 Server moduleThe S8300 can only be inserted in slot V1 on the left side of the G450 Media Gateway.

ELECTROSTATIC ALERT:ELECTROSTATIC ALERT: Hold media modules only by the edges to avoid damage from static electricity. Do

not touch the top or bottom of the circuit board. If possible, wear an anti-static wrist-strap and use an anti-static bag.

! CAUTION:CAUTION: The connector pins can be bent or damaged if the module is handled roughly, or if

misaligned and then forced into position.

! CAUTION:CAUTION: Separate ESD paths to the chassis ground connect to the media modules at the

spring-loaded captive screws. Use a screwdriver to ensure the captive screws are securely tightened to prevent damage to the equipment.

1. If you are inserting an S8300/B module, remove the plate above slot V1, labelled “Remove before removing or inserting S8300 module”.

2. Remove the blank plate from slot V1.

3. Position the media module before the V1 bay opening and engage both sides of the module in the interior guides.

4. Slide the S8300 module slowly into the chassis, maintaining an even pressure to assure that the module does not become twisted or disengaged from the guides.

MM716 V1 – V8 Provides one amphenol connector that connects to a punch down block to provide 24 analog line ports.

MM717 V1 – V8 Provides one amphenol connector that connects to a punch down block to provide 24 ports for connecting DCP telephones.

MM720 V1 – V8 Provides eight ports for connecting up to eight ISDN trunks or 16 ISDN BRI stations.

MM722 V1 – V8 Provides two ports for connecting ISDN trunks.

S8300B/S8300C V1 Server

Table 1: Permitted slots for media modules (continued)

Media module Permitted slots Description

2 of 2



Figure 7: Inserting the S8300 Server module.

5. Apply firm pressure to engage the connectors.

The connector has different length pins. The long pins will engage first to provide grounding. Medium length and short pins will provide power and signal.

6. Lock the S8300 Server module into the chassis by tightening the spring-loaded captive screws on the front of the module.

7. If you are inserting an S8300/B module, replace the plate labelled “Remove before removing or inserting S8300 module” above slot V1 and tighten the screws on the front of the plate.

After you have inserted the S8300 Server module, if applicable, insert the rest of the media modules. Make sure to insert each module in a permissible slot.

! DANGER:DANGER: To prevent access to electrical hazards by unauthorized personnel and to ensure

continued compliance to radiated emissions requirements, all captive screws must be securely tightened such that they cannot be loosened without the use of a tool.



Inserting media modules

After you have inserted the S8300 Server module, if applicable, insert the rest of the media modules. Make sure to insert each module in a permissible slot. Remove the blank plate from the empty bay.

ELECTROSTATIC ALERT:ELECTROSTATIC ALERT: Hold media modules only by the edges to avoid damage from static electricity. Do

not touch the top or bottom of the circuit board. If possible, wear a wrist-strap and use an anti-static bag.



! CAUTION:CAUTION: Separate ESD paths to the chassis ground connect to the media modules at the

spring-loaded captive screws. Use a screwdriver to ensure the captive screws are securely tightened to prevent damage to the equipment.

1. Position the media module before the selected bay on the front of the G450 chassis and engage both sides of the module in the interior guides.

2. Slide the module slowly into the chassis, maintaining an even pressure to assure that the module does not become twisted or disengaged from the guides.

Figure 8: Inserting a media module

3. Apply firm pressure to engage the connectors. The media module connector has different length pins. The long pins will engage first to provide grounding. Medium length and short pins will provide power and signal.



4. Lock the media module into the chassis by tightening the spring-loaded captive screws on the front of the module.

! DANGER:DANGER: To prevent access to electrical hazards by unauthorized personnel and to ensure

continued compliance to international radiated emissions requirements, all captive screws must be securely tightened such that they cannot be loosened without the use of a tool.

! WARNING:WARNING: After you have connected telephones to the various media modules, be sure to

add circuit protection to the lines.

Step 4: Attaching ground conductorsTo assure safe installation and operation, carefully read all requirements, recommendations, and instructions. Pay special attention to all CAUTION, WARNING, and DANGER statements.

! WARNING:WARNING: System grounding must comply with the general rules for grounding provided in

Article 250 of the National Electrical Code (NEC), National Fire Protection Agency (NFPA) 70, or the applicable electrical code in the country of installation.

General grounding requirementsTwo safety grounds are required to ensure safe operation of the G450 Media Gateway: the ground conductor that is part of the AC power cord and the field-installed green/yellow conductor referred to as the Supplementary Ground Conductor. Both safety grounds must be connected to an approved ground. If a power cord accompanies the G450, use that cord whenever possible.

Installation location

The customer must select a location for the G450 Media Gateway installation that is no more than 50 ft (15 m) from an approved ground. If this location requirement is not met, the customer must contact a licensed electrician to install a Supplementary Ground Conductor per Article 250

Step 4: Attaching ground conductors


of the National Electrical Code (NEC).

! WARNING:WARNING: If the installation location is greater than 50 ft (15 m) from an approved ground, do

not install the Avaya G450 Media Gateway until a licensed electrician is present to install a Supplementary Ground Conductor.

Ground conductor

A Supplementary Ground Conductor is provided with the equipment, and is constructed of 10 AWG (4.0 mm2) wire, with an insulated ring terminal crimped to one end that is suitable for the #8 (M4) stud/screw on the rear of the G450 chassis.

The customer will need to provide a means of connecting this Supplementary Ground Conductor to an approved ground according to Article 250 of the National Electrical Code (NEC).

Ground block

A ground block is available for use when multiple G450 Media Gateways are being installed. The ground block, intended for rack mounting, has ten terminals available for terminating Supplementary Ground Conductors. Up to ten G450 Media Gateways can be grounded at the block installed close to the equipment (on a rack) and then a single ground conductor can be routed from the same block to an approved ground. If the ground block is to be used, it must be ordered separately.

! DANGER:DANGER: Failure to install both grounds will void the Product Safety certifications (UL and

the CE Mark) on the product, as well as allow a hazard to be present that could result in death or severe personal injury.

Restricted Access Location

In Finland, Norway, and Sweden, the G450 Media Gateway must be installed in a Restricted Access Location, due to unreliable earthing concerns. A Restricted Access Location is defined as access that can be gained by only Service Personnel or Customers who have been instructed about the reasons for the restricted access and any safety precautions that must be taken. In these cases, access to the G450 is gained by the use of a tool (such as a lock and key) or other means of security.



! WARNING:WARNING: For installations in Finland, Norway, and Sweden, the Avaya G450 Media

Gateway relies on two ground connections (mains plug with an earth contact and a Supplementary Ground Conductor).

Approved groundsAn approved ground is the closest acceptable medium for grounding the building entrance protector, entrance cable shield, or a single-point ground of electronic telephony equipment. If more than one type of approved ground is available on the premises, the grounds must be bonded together as required in Section 250-81 of the NEC for the US or per the local electrical code regulations in the country of installation.

● Grounded Building Steel. The metal frame of the building where it is effectively grounded by one of the following grounds: acceptable metallic water pipe, concrete encased ground, or a ground ring.

● Acceptable Water Pipe. A metal underground water pipe, at least 1/2 in (1.3 cm) in diameter, in direct contact with the earth for at least 10 ft (3m). The pipe must be electrically continuous (or made electrically continuous by bonding around insulated joints, plastic pipe, or plastic water meters) to the point where the protector ground wire connects. A metallic underground water pipe must be supplemented by the metal frame of the building, a concrete-encased ground, or a ground ring. If these grounds are not available, the water pipe ground can be supplemented by one of the following types of grounds:

- Other local metal underground systems or structures, such as tanks and piping systems.

- Rod and pipe electrodes. A 5/8 in (1.6 cm) solid rod or 3/4 in (2 cm) conduit or pipe electrode driven to a minimum depth of 8 ft (2.4 m).

- Plate electrodes. Must have a minimum of 2 sq. ft (0.185 sq. m) of metallic surface exposed to the exterior soil.

● Concrete Encased Ground. An electrode encased by at least 2 in (5.1 cm) of concrete and located within and near the bottom of a concrete foundation or footing in direct contact with the earth. The electrode must be at least 20 ft (6.1 m) of one or more steel reinforcing bars or rods, 1/2 in (1.3 cm) in diameter, or at least 20 ft (6.1 m) of bare solid copper, 4 AWG (26 mm2) wire.

● Ground Ring. A buried ground that encircles a building or structure at a depth of at least 2.5 ft (0.76 m) below the earth’s surface. The ground ring must be at least 20 ft (6.1 m) of 2 AWG (35 mm2), bare copper wire.

● Approved Floor Grounds. Floor grounds are those grounds on each floor of a high-rise building that are suitable for connection to the ground terminal in the riser closet and to the cabinet single-point ground terminal. Approved floor grounds may include the following:

- Building steel.

Step 4: Attaching ground conductors


- The grounding conductor for the secondary side of the power transformer feeding the floor.

- Metallic water pipes.- Power-feed metallic conduit supplying panel boards on the floor.- A grounding point specifically provided in the building for that purpose.

! WARNING:WARNING: If the approved ground or approved floor ground can only be accessed inside a

dedicated power equipment room, then connections to this ground must be made by a licensed electrician.

Connecting the safety groundProper grounding of the G450 Media Gateway installation safeguards the system, users, and service personnel by providing protection from lightning, power surges, AC mains faults, power crosses on central office trunks, and electrostatic discharge (ESD).

Local electrical installation codes must be followed when installing the G450.

! DANGER:DANGER: Connection of both grounds (through the AC Power Cord and the Supplementary

Ground Conductor) is required for safe operation of the G450 Media Gateway.

! WARNING:WARNING: An improper ground can cause electrical shock as well as equipment failures and

service outages.

Attaching the ground wires

1. Place the ring terminal of the 10 AWG (4.0 mm2) Supplementary Ground Conductor on the ground screw that was provided in the accessories box.

2. Insert the ground screw on the rear of the chassis adjacent to the ground symbol and securely tighten the screw such that it cannot be loosened without the use of a tool.

If the ground block has been purchased1. Cut the Supplementary Ground Conductor (which has one end attached to the grounding

screw on the chassis) to the length needed to terminate it into one of the terminals of the ground block. Do not coil the Supplementary Ground Conductor.

2. Attach one end of the remaining 10 AWG (4 mm2) ground wire to one of the terminals in the ground block and the other end to an approved ground.



3. Cut this ground wire to the length needed to reach the approved ground. Do not coil this wire.

Note:Note: The ground block is provided for use with more than one G450 in the rack. It is

usually mounted by the customer electrician.

If the ground block is not being used1. Attach the Supplementary Ground Conductor to an approved ground.

2. Connect the AC power cable to the inlet receptacle on the rear of the chassis.

Step 5: Connecting power to the G450After you have mounted the G450, installed the PSU(s), installed the media modules, and attached grounding conductors, you can connect power to the G450. The G450 can be ordered with either one or two power supply units.

1. Connect the power cable to the power connector on the G450 back panel.

2. Plug the power cable into a mains socket. The G450 is now powered.

The PWR LED on the front panel lights. The CPU LED lights up if the firmware is running. At least one LED on each media module, except the S8300, lights up initially and then goes off after about 20 seconds.

3. If you have a second power supply unit, you can connect it to power by repeating steps 1 and 2.

Note:Note: If two PSUs are installed in the G450, the PWR LED blinks if only one PSU is

connected to power, and stays on if both PSUs are connected to power.

Step 5: Connecting power to the G450


PWR LED indicationsThe PWR LED on the power supply unit indicates the operational status of the power supply unit.

Table 2: Power Supply Unit PWR LED

LED Name State Color Indication

PWR Power On Green Power is OK

On Red A power fault

Off The PSU unit is broken or not powered


Chapter 3: Connecting devices

External endpoint devices can be connected to the ports on the front panels of the installed media modules and to the fixed front panel ports. Before you connect endpoint devices, the G450 should be mounted and all media modules should be inserted.

! WARNING:WARNING: To reduce the risk of fire, use only 26 AWG or larger telecommunication line cords

when installing telephones or adjuncts, or connecting to any media module telecommunication ports.

! WARNING:WARNING: Attention: Pour réduire les risques d’incendie, utiliser uniquement des conductors

de télécommmunications 26 AWG ou de section supérieure. Pour réduire les risques d'incendie, veuillez n'utiliser que des fils de lignes télécommmunications de 26 AWG ou de section supérieure, lorsque vous connectez des téléphones, des équipements complémentaires, ou pour toute connexion aux ports télécommunications d'une quelconque carte d'équipement.

Step 1: Connecting data and voice devicesThere are various possible ways of connecting different devices. See your planning documentation for any topology requirements to connect specific devices to specific ports. As you connect devices, keep a record of the slots and ports into which specific devices are connected. You will need this information when configuring the G450.

Connecting a switch or a network data portThe G450 can provide network switching and also supports the connection of switches. You can connect the following to either of the ETH LAN ports on the G450 front panel:

● One or more LAN switches

● The network data ports in the office

Connecting devices


Connecting a computer to the Services port

A laptop connected directly to the Services port of the G450 or S8300 Server requires a specific configuration of its network settings.

Note:Note: Make a record of any IP addresses, DNS servers, or WINS entries that you

change when you configure your services laptop. Unless you use the NetSwitcher program or an equivalent, you will need to restore these entries to connect to other networks.

● Configure TCP/IP properties. Set the laptop's TCP/IP properties as follows:

- IP address: 192.11.13.5- Subnet mask: 255.255.255.252- Disable DNS service- Disable WINS Resolution

● Configure browser settings. Configure the laptop’s browser for a direct connection to the Internet. Either disable/bypass proxy servers, or enter 192.11.13.6 in the Exceptions box.

● Server address. Access the G450 or S8300 Server using the URL http://192.11.13.6.

Note:Note: The names of the dialog boxes and buttons vary on different operating systems

and browser releases. Use your computer's help system if needed to locate the correct place to enter the configuration information.

Connecting an IP telephone

Note:Note: For a full list of supported phones, see Appendix B, Supported Avaya telephones

in Overview for the Avaya G450 Media Gateway, 03-602058.

Connect the IP telephone to an external Ethernet switch. This switch must be connected to a LAN port on the Avaya G450 Media Gateway. This port is labeled 10/5 or 10/6.

If the telephone is not an Avaya IP telephone, you can connect it to any port on the network switch. Note the slot and port number on the Avaya G450 Media Gateway to which you connect the telephone.

Step 1: Connecting data and voice devices


Connecting the telephone to the G450

1. Wire a telephone port to a port on the switch connected to the G450 LAN port.If the switch is a PoE switch, you do not need to plug the IP telephone into a power supply.

2. Plug the telephone into the telephone port.

3. If the IP telephone will be powered independently, plug the IP telephone into a power supply and check that the IP telephone is powered up.

Connecting an ISDN BRI stationEach ISDN port on the MM720 Media Module supports up to two ISDN BRI stations.

Note:Note: The MM720 BRI Media Module cannot be administered to support both BRI

trunks and BRI stations at the same time. Also, the MM720 BRI Media Module does not support combining both B-channels together to form a 128-kbps channel. Finally, if the MM720 BRI Media Module is administered to support BRI stations, it cannot be used as a clock synchronization source.

Connecting one ISDN BRI station to one ISDN port

Connect the station via a standard 8-pin BRI cable to one of the ISDN ports on an MM720 Media Module.

Connecting two ISDN BRI stations to one ISDN port

1. Connect each station to an RJ-45 splitter that provides two RJ-45 4-pair jacks, and one RJ-45 male connector. See Figure 9 for the correct wiring for the splitter.

2. Connect the male connector of the splitter to one of the ISDN ports on an MM720 Media Module.

Connecting devices


Figure 9: RJ-45 splitter wiring for connecting two ISDN BRI stations to one ISDN port

Figure 10: The MM720 media module

Connecting an analog telephone



1. Wire a telephone port to one of the following analog ports:

- A universal analog port on an MM711 media module- Any analog line port on a punch down block connected to an MM716 media module.

To connect the MM716 media module to a punch down block to enable telephone connection, see Connecting devices to the MM717 and MM716 media modules on page 55.

- A LINE port on an MM714 media module

2. Plug the analog telephone into the telephone port.






Note:Note: Analog line ports support the following maximum distances:

- For phone equipment with a ringer load above 3 REN (old mechanical ringers): - Up to 10,000 ft for 26 AWG wire- Up to 16,000 ft for 24 AWG wire- Up to 20,000 ft for 22 AWG wire

- For modern phone equipment with a ringer load below 0.1 REN (electronic ringers):- Up to 20,000 ft for 26 AWG, 24 AWG, and 22 AWG wire

Connecting devices


Connecting a DCP telephone to anMM712 or MM717 media module



1. Wire a telephone port to a DCP port on the G450.

The following media modules provide DCP telephone ports:

- MM712. 8 DCP ports- MM717. 24 DCP ports, provided via a single 25-pair amphenol socket on the front

panel. To connect the MM717 media module to a punch down block to enable telephone connection, see Connecting devices to the MM717 and MM716 media modules on page 55.



2. Plug the DCP telephone into the telephone port.



! WARNING:WARNING: With the exception of the MM712, all DCP media modules are intended for

in-building use only. Phone lines connected to these ports are not to be routed out-of-building. Failure to comply with this could cause harm to personnel and equipment.

Note:Note: The MM712 and MM717 and media modules support the following maximum loop

lengths:- Up to 5500 ft for 22 AWG wire- Up to 3500 ft for 24 AWG wire- Up to 2200 ft for 26 AWG wire

Connecting an analog trunk1. Connect the trunk to one of the following ports:

- Any universal analog port on an MM711 media module- Any analog line port on a punch down block connected to an MM716 media module.

To connect the MM716 media module to a punch down block to enable trunk connection, see Connecting devices to the MM717 and MM716 media modules on page 55.

Note:Note: The MM716 media module does not support analog CO or CAMA trunks.

- One of the ports marked TRUNK on an MM714 media module

Note:Note: For an analog DID trunk, you cannot use a TRUNK port on an MM714 media

module. Instead, you must connect the trunk to one of the ports marked LINE on an MM711, MM714, or MM716 media module.

Connecting devices


Connecting an E1/T1 trunkConnect the trunk cable to the E1/T1 port on an MM710 media module. The SIG LED lights.


Connecting an ISDN BRI trunkConnect the trunk to any ISDN port on an MM720 or MM722 media module.

Note:Note: In the US, you need to connect a separately purchased NT1 device to each ISDN

port you use to connect an ISDN BRI trunk.





Connecting devices to the MM717 and MM716 media modulesThe MM716 and MM717 media modules do not support direct connection of telephones or other endpoint devices. The MM716 and MM717 media modules each have a single 25-pair amphenol socket on the front panel, intended for use with a punch down block. Connect the front panel connector to a punch down block. You can terminate up to 24 endpoint devices on the connected punch down block.

Connecting the MM716 or MM717 front panel connectorto a punch down block

1. Connect one end of a CAT5 cable with a 25-pair amphenol connector at each end to the 25-pair socket on the MM716 or MM717 front panel, so that the cable extends to the right of the G450. (The cable you use must be such that the connector you plug into the media module is 90° to the cable.)

2. Tighten the end screw of the amphenol connector to securely fasten the connector to the left side of the front panel socket.

3. Thread a tie wrap through the small bracket to the right of the front panel socket.

4. Fasten the tie wrap around the cable to secure the cable to the right side of the front panel socket.

Figure 19: Attaching and securing the amphenol cable to the MM716 or MM717 25-pair socket

5. Connect the other end of the amphenol cable to a punch down block that converts the single amphenol connector to 24 RJ-45 or RJ-11 jacks, as needed. You can now connect endpoint devices to the RJ-45 or RJ-11 jacks. For the pin-out of the 25-pair connector, see Table 18.

Connecting devices


Step 2: Installing circuit protectionOut-of-building installations of telephones or other standard (tip/ring) devices/terminals that connect to the Avaya G450 Media Gateway Media Modules require over-voltage and sneak current protection in both buildings. Field installed sneak current protectors must have a maximum current rating of 350 mA and a minimum voltage rating of 600V. The following devices have been evaluated or tested and approved to protect the media modules from over-voltages and sneak current protection:

● For the Avaya MM710 or MM340 T1/E1. Over-voltage and sneak current protection for the Avaya MM710 and MM340 are provided on the media modules themselves.

● For the Avaya MM711, MM714, and MM716 Analog. Over-voltage and sneak current protection for these interfaces is provided on the media modules/interfaces. Incoming trunks normally have over-voltage protection provided by the local telephone company. Analog voice terminals use one of the following types of combined over-voltage and sneak current protection at both building entry points:

- Gas tube with heat coil. 4B1E-W- Solid state with heat coil. 4C1S- IROB. 146C (4-lines) or 146F (25-lines)

● For the Avaya MM712 DCP: either 146E IROB (In-Range Out-of-Building) or 4C3S-75 solid state protectors for over-voltage and sneak current.

● For the Avaya MM722 ISDN-BRI: over-voltage and sneak current protection are provided on the media modules themselves.

● For the Avaya MM720 ISDN-BRI: network-side applications require an NT-1 device. Tie trunk applications require either the 146E IROB (In-Range Out-of-Building) or 4C3S-75 solid state protectors for over-voltage and sneak current.

Step 3: Connecting to the Wide Area Network (WAN)


! WARNING:WARNING: Only service-trained personnel are to install these circuit protection devices.

! WARNING:WARNING: With the exception of the MM712, all DCP media modules are intended for

in-building use only. Phone lines connected to these ports are not to be routed out-of-building. Failure to comply with this could cause harm to personnel and equipment.

Step 3: Connecting to the Wide Area Network (WAN)Since the G450 contains an internal router, you can connect the G450 directly to a WAN endpoint device. You can also connect a WAN endpoint device to the G450 via an external router.

Connecting a WAN to the G450There are some differences in how to connect the WAN, depending on the type of WAN link you are connecting.

Connecting a WAN link to the MM342 media module

You must connect the WAN link to a device connected to the Avaya MM342 media module.

To connect the WAN link, plug the WAN line into the USP port on the MM342 media module. This port is marked USP. To connect the WAN line to the port, use one of the following cable types, depending on the service provider’s equipment:

● Avaya Serial Cable DTE V.35

● Avaya Serial Cable DTE X.21


Connecting devices


Connecting an E1/T1 WAN link to the MM340 media module

To connect the WAN link, plug the WAN line into the E1/T1 port on the MM340 media module. This port is marked E1/T1. Use an unshielded twisted pair cable, straight or crossover, depending on the WAN equipment.


Connecting an Ethernet WAN link

You must connect the Ethernet WAN line (DSL, firewall, etc.) to the Ethernet WAN port on the front panel of the Avaya G450 Media Gateway chassis. This port is marked ETH WAN. See Figure 6. Use a CAT5 Ethernet cable to connect the WAN line to the port.

Connecting an external router to the G450You can connect a router to any of the following ports on the G450:

● The ETH WAN ports on the G450 front panel

● The ETH LAN ports on the G450 front panel

Step 4: Installing the Coupled Bonding ConductorThe Coupled Bonding Conductor (CBC) provides mutual inductance coupling between the CBC and the telephone cables that are exposed to lightning. The conductor can be a 10 AWG (4 mm2) wire tie wrapped to the exposed cables, a metal cable shield around the exposed cables, or six spare pairs from the exposed cable. In a high-rise building, connect the CBC to an approved building ground on each floor.

Step 5: Installing the Avaya Partner Contact Closure Adjunct


Installing the CBCBefore you begin, be sure the telephone lines are cross-connected to the appropriate media module(s).

1. Connect one end of the conductor to a telephone cable building entrance protector ground that is connected to an approved ground.

2. Route the rest of the conductor next to the exposed telephone cables being protected until they reach the cross-connect nearest to the telephone system.

3. Terminate the other end to the single-point ground block provided for the telephone system.

Note:Note: Position the non-exposed telephone cables at least 12 in (30.5 cm) away from

exposed telephone cables whenever possible.

Step 5: Installing the Avaya Partner Contact Closure Adjunct

The Contact Closure feature is a controllable relay providing dry contacts for various applications. To implement the contact closure feature, you connect an Avaya Partner Contact Closure Adjunct box to the CCA port on the G450 chassis. The adjunct box provides two contact closures that can be operated in either a “normally closed” or “normally open” state. The contact closures can control auxiliary devices such as devices that automatically lock or unlock doors or voice recording units. The CCA port can be configured so that the connected devices can be controlled by an end device, such as a telephone. For example, a user can unlock a door by keying a sequence into a telephone keypad.

Installing the contact closure1. Follow the installation instructions in the Avaya Partner Contact Closure Adjunct

Installation Instructions leaflet to install the Contact Closure and connect the auxiliary devices that will be activated and deactivated by the Contact Closure relays.

2. Note which device is connected to each relay. You will need this information for configuration.

3. Connect the Avaya Partner Contact Closure adjunct box to the CC port on the G450 front panel. Use a 24 gauge minimum telephone wire, no longer than 200 ft, with a standard four wire RJ-11 connector.

Connecting devices


Step 6: Installing an 808A Emergency Transfer Panel and associated telephones

The ETR feature provides basic telephone services in the event of system failure, such as a power outage or a failed connection to the MGC. The ETR feature can be used in conjunction with an analog media module (MM711, MM714, or MM716). The ETR panel provides up to five incoming Central Office (CO) trunk loops to 5 selected G450 analog lines. Thus, one ETR panel supports up to five emergency lines. You can cascade a second ETR panel, providing support for up to 10 emergency analog phones. ETR is activated automatically upon system failure by closing the tip/ring contacts between the analog lines and the analog trunks. When ETR is activated, all calls are directed by the analog relays between the outside lines and the analog telephones. A current-loop detection circuit prevents ongoing calls from being disconnected when normal functioning resumes. If a call is in progress on an outside line when the problem ends, the call continues. The trunk port and analog line port passing through the ETR panel do not start to operate until the active call ends.

For information on installing the 808A Emergency Transfer Panel, see 808A Emergency Transfer Panel Installation Instructions, 03-602518, which ships with the Emergency Transfer Panel.

Step 6: Installing an 808A Emergency Transfer Panel and associated telephones


Figure 22: 808A Emergency Transfer Panel

cycmfig1 LAO 082107

25-PAIRMALECONNECTOR

CABLERETAINER

TRUNK TYPESELECTIONSWITCHES

LED

TESTSWITCH

EmergencyTransferPanel

POWER

TRUNK / TEST SWITCHES

CIRCUIT

12345

12345678910

12

1

LOOPSTART

GROUNDSTART

TRUNK OPTION:

BOTH SWITCHES MUST BETHROWN TO ACTIVATETRUNK OPTION

ACTIVATED NORMALOPERATION

TRANSFER TEST SWITCH

TRUNK IDENTIFICATION

TRUNKLINE EXT LOC

TRUNKIDENTIFICATIONLABEL

808A

RATING-48V DC

0.08A

2

Connecting devices



Chapter 4: Connecting and enabling a modem for remote access

You can connect a modem to the G450 to enable configuration from a remote location. A serial modem connected to the G450 can also be used for the modem dial backup feature, which provides a redundant connectivity with a remote primary Media Gateway Controller (MGC). Modem dial backup allows for more superior survivability than switching to a secondary MGC, since more features are preserved.

If an S8300 is installed in the G450, leave a modem connected permanently to enable reporting of alarms to remote locations.

Note:Note: If you choose to configure the G450 by running an installation wizard, you can

enable a modem with the wizard as part of the configuration. Instructions for connecting the modem are included in Appendix C: Running the Avaya Installation Wizard (Avaya IW) on page 151 and in Appendix D: Running the Gateway Installation Wizard (GIW) on page 209. You do not need to read this chapter.

Connecting and enabling a modem (G450 without S8300)You can either connect a serial modem to the CON port on the G450 front panel or you can connect a USB modem to either of the two USB ports on the G450 front panel.

Connecting and enabling a serial modem1. Prepare a PC with a CD-ROM drive and a TFTP server on the network. This may be

needed for installing software and firmware upgrades.

Note:Note: When uploading firmware from the S8300 using TFTP, you may need to enable

TFTP service in the Set LAN Security parameters of your web server.

Note:Note: Firmware upgrades for the G450 and media modules can either be installed from

CD or downloaded from the Web.

Connecting and enabling a modem for remote access


2. Download Gateway Installation Wizard (GIW) from the Avaya Support website (support.avaya.com/avaygiw) to the laptop computer. The laptop should be running Windows 2000 or Windows XP to support GIW.

3. Plug one end of the provided flat RJ-45 to RJ-45 cable into the provided DB-9 adapter.

4. Plug the RJ-45 connector at the other end of the cable into the CON port of the G450.

5. Plug the DB-9 end of the flat cable into the COM port of the laptop computer.

6. From your laptop computer, double-click the GIW icon to run GIW. The Overview screen appears.

7. Click Continue. The COM Port Selection screen appears.

Figure 23: COM Port Selection screen

8. Select the COM port on the laptop that you are using to connect to the G450.

9. Click Continue. The G450 Wizard Usage Options screen appears.

Connecting and enabling a modem (G450 without S8300)


Figure 24: G450 Wizard Usage Options screen

10. Select Enable the modem for remote installation.

11. Click Continue. The G450 Modem Type Selection screen appears.



Figure 25: G450 Modem Type Selection screen

12. Select Serial Modem.

13. Click Continue. The G450 Serial Modem Configuration screen appears.



Figure 26: G450 Serial Modem Configuration screen

14. In the IP Address field, enter the RAS IP address of the modem obtained using the ART tool. See Running the Automatic Registration Tool (ART) for the RAS IP address on page 22.

15. Fill in the remaining modem information fields.

16. Select the authentication method:

● If you have an Avaya Service contract, check Enable ASG Authentication to enable remote access to the device.

● If you do not have an Avaya Service contract:

- Check Enable CHAP Authentication.

- In the CHAP Secret field, enter the CHAP secret key obtained using the ART tool. See Running the Automatic Registration Tool (ART) for the RAS IP address on page 22.

- In the Confirm CHAP Secret field, re-enter the CHAP secret key.

17. Click Continue. The Connect Modem screen appears.



Figure 27: Connect Modem screen

18. Click Finish.

19. Connect the serial modem to a working telephone line.

20. Connect the provided DB-25 adapter to the modem.

21. Disconnect the flat cable from the COM port of the laptop computer.

22. Connect the flat cable to the DB-25 connector on the modem.

Connecting and enabling a USB modem (G450 without S8300)You can enable a MultiTech MT5634ZBA-USB USB modem on a USB port on the G450 front panel.

Note:Note: The MultiTech model MT5634ZBA-USB USB modem is the only USB modem

supported by the G450.

1. Prepare a PC with a CD-ROM drive and a TFTP server on the network. This may be needed for installing software and firmware upgrades.






CD or downloaded from the Web.

2. Download GIW (Gateway Installation Wizard) from the Avaya Support website (support.avaya.com/avaygiw) to the laptop computer. The laptop should be running Windows 2000 or Windows XP to support GIW.












10. Select Enable the modem for remote installation.

11. Click Continue. The G450 Modem Type Selection screen appears.



Figure 30: G450 Modem Type Selection screen

12. Select USB Modem.

13. Click Continue. The G450 USB Modem Configuration screen appears.



Figure 31: G450 USB Modem Configuration screen

14. In the PPP IP Address field, enter the RAS IP address of the modem obtained using the ART tool. See Running the Automatic Registration Tool (ART) for the RAS IP address on page 22.

15. Enter the PPP Subnet Mask.







17. Click Continue. The Connect Modem screen appears.



Figure 32: Connect Modem screen

18. Click Finish.

19. Connect a USB modem to a working telephone line.

20. Connect one end of a USB cable to the modem.

21. Connect the other end of the USB cable to a USB port on the G450 front panel.



Testing the modem connection (G450 without S8300)Dial into the modem to verify that you can authenticate to the modem.



Connecting and enabling a USB modem (G450 with S8300)You can connect a USB modem to either of the two USB ports on the G450 front panel.

Maintenance web pagesMost of the preparations you are making require you to access the Maintenance web pages part of Avaya Integrated Management (AIM) from your laptop. After accessing the Maintenance web pages, leave the Maintenance web pages open until you have completed all the preparations.

Accessing the Maintenance web pages

1. Connect the laptop you prepared to the Services port on the S8300. Use a standard Ethernet crossover cable.

2. Configure the network settings on the laptop, according to the following tables:

3. Open Internet Explorer, and browse to 192.11.13.6. The welcome screen for Avaya Integrated Management appears.

4. Click Continue. The Logon screen for Avaya Integrated Management appears.

Table 3: TCP/IP settings

Setting Value

IP Address 192.11.13.5

Subnet Mask 255.255.255.252

DNS disable

WINS Servers do not use (clear out any values)

Table 4: Internet Browser Settings

Setting Value

Proxy Server disable

Connecting and enabling a USB modem (G450 with S8300)


Figure 33: Integrated Management Logon screen

5. Enter your S8300 initial entry username in the Logon ID box.

6. Click Logon. The password field appears.

7. Enter your password in the password field, and click Logon. The main menu for Avaya Integrated Management appears.



Figure 34: Integrated Management Main Menu

8. From the Integrated Management main menu, select Launch Maintenance Web Interface. The Maintenance Web Pages Notice page appears, with a navigation menu at the left.



Figure 35: Maintenance Web Pages Notice page

9. Leave the Maintenance Web Pages open to perform the tasks described in the coming sections.

Changing the modem settings on the Configure Server MaintenanceWeb Page

1. Select Configure Server from the left-hand menu on the Maintenance web page. The Back Up Data page appears.

2. Follow the on-screen instructions to back up the current data.

3. Click Continue.

4. Select Configure individual services.

5. Click Continue.

6. From the left navigation menu, click Set Modem Interface. The Set Modem Interface page appears.

7. Enter the RAS IP address you obtained using the ART tool. See Running the Automatic Registration Tool (ART) for the RAS IP address on page 22.



8. Click Change modem settings.

9. Click Continue.

10. Click Close Window.

Note:Note: You can only change the modem settings on the Configure Server Maintenance

Web Pages if you have an Avaya Maintenance contract.

Connecting and enabling a USB modem (G450 with S8300)If your installation includes an S8300 Server module, you must connect the USB modem to the S8300. After the G450 is configured, you can leave the modem permanently connected to enable the S8300 to report alarms to remote locations.

Note:Note: If you require a USB CD-ROM drive to download software upgrades, connect the

USB CD-ROM drive to the remaining available USB port on the S8300 module.

Connecting and enabling the modem

1. Connect the USB modem to a working telephone line.

2. Connect the modem to one of the USB ports on the S8300 module.

3. From the navigation menu of the Maintenance Web Pages, select Security > Modem. The Modem page appears.

Figure 36: Modem page

4. Select Enable modem for unlimited incoming calls.

5. Click Submit.



Testing the modem connection (G450 with S8300)1. Setup a dialup connection on a remote PC with the following settings:

● Automatically detect settings.

● No Username, Password, or Domain.

● Security > Show Terminal Window.

2. Dial in to the modem from the remote PC.

3. When prompted, provide the rasaccess login and password in the Terminal Window.

4. Close the Terminal Window to complete the connection.

If a USB CD-ROM drive is required to download software upgrades

Connect the USB CD-ROM drive to the remaining available USB port on the S8300 module.


Chapter 5: Configuring the G450

The G450 requires software configuration. The G450 can be configured using:

● The Avaya Installation Wizard (Avaya IW). Avaya IW is a wizard that prompts you for all configurations required to complete the installation of the G450. Avaya IW is used only to configure a G450 with an S8300. Refer to Appendix C: Running the Avaya Installation Wizard (Avaya IW) on page 151.

● The Gateway Installation Wizard (GIW). The GIW is a wizard that prompts you for all configurations required to complete the installation of the G450. You can run GIW to configure a G450 without an S8300. Refer to Appendix D: Running the Gateway Installation Wizard (GIW) on page 209.

● The Avaya G450 Command Line Interface (CLI). The CLI is a comprehensive tool for configuring the gateway and includes all supported configuration tasks. For information about configuration using the CLI, see Administration for the Avaya G450 Media Gateway, 03-602055. For detailed information on CLI commands, refer to the Avaya G450 CLI Reference, 03-602056.

The G450 can be configured at the customer site via a laptop connected to the CON port or Services port of the G450, or from a remote location via a modem. For information about connecting a laptop to the Services port, refer to Connecting a computer to the Services port on page 48. For information about connecting and enabling a modem, refer to Chapter 4: Connecting and enabling a modem for remote access on page 63.

Configuring the G450



Chapter 6: After installation

After initial configuration, it is necessary to test the installation, and remove the installation equipment.

Step 1: Testing the installationWhen the installation is complete, simple tests must be performed to test telephone and data connectivity.

Testing data connectivityTest data connectivity by pinging the IP address of each device to test the device’s connectivity within the network and outside the network.

Test local data connectivity on-site by checking that you can send an email between two PCs that are connected to the G450.

Testing telephones1. Make outgoing calls from the telephone. Make sure you hear a dial tone when you pick up

the receiver. Make sure you can make both an internal (within the local network) and an external (outside the local network) call.

2. Make a call to the telephone from both within the network and outside of the network.

Testing trunksUse the facility test call feature to verify that each trunk is functioning properly.

For information about how to use the facility test call feature, see Maintenance Procedures for Avaya Communication Manager, Media Gateways and Servers, 03-300432.

After installation


LSP failover testingIf you have an S8300 Server module installed in the G450 and configured as an LSP, you need to perform a test to make sure that the LSP takes over control of the G450 if the G450 becomes disconnected from the primary MGC.

1. Verify that valid translations are file synchronized to the LSP by logging into Avaya Communication Manager from the LSP and listing either stations or trunks (refer to Administrator’s Guide for Avaya Communication Manager, 555-233-506). Verify that the list of stations or trunks is valid. If the files are not synchronized, verify that you have correctly configured the required IP address(es) for the primary controller (MGC). If you are using Avaya IW to configure the G450, the following are key actions that must be done in the wizard to ensure correct IP address configuration:

a. In the Usage options screen, select Install this media server as an LSP. The Primary Controller IP Address screen appears later in the wizard, and calls for the required primary controller IP addresses for your primary controller type. Refer to Table 5 for the IP addresses and controller information.

b. In the Primary Controller IP address screen, enter all the required IP addresses for the primary controller type.

There may be a delay after running AIW until the LSP is registered with the primary MGC and the translations are file synchronized.

2. If valid translations are not file synchronized to the LSP, do the following:

a. From a SAT session run from the primary controller, verify that the LSP node-name and IP address are correctly entered.

b. Use the save translation lsp command to start the file synchronization process.

c. Log in again to Avaya Communication Manager from the LSP and list either stations or trunks.

d. Verify that the list of stations or trunks is valid.

3. Disconnect the G450 from the primary controller, ensuring that all telephones are still connected to the G450.

4. Verify that calls can be made between local telephones and to outside telephones.

Step 2: Removing the installation equipment


Table 5: IP addresses and controllers

Step 2: Removing the installation equipmentRemove all equipment that you used to assist you in the installation process. This may include the CD-ROM drive, the software upgrade CDs, the laptop computer, and the modem (for installations without an S8300 module only).

Note:Note: If you have an S8300 Server module installed in the G450, leave the modem

connected to enable reporting of alarms to remote locations.

Primary media gateway controller

IP addresses to configure

S8300 The IP address of the primary S8300

S8400 The IP address of the S8400’s C-LAN or the IP address of an Ethernet port on the S8400 configured for processor Ethernet connections

S8500 The IP address of the S8500’s C-LAN or the IP address of an Ethernet port on the S8500 configured for processor Ethernet connections

S8710 The IP address of the S8710’s C-LAN and the IP address of alternate C-LAN boards connected to the S8710



After installation



Chapter 7: Adding media modules and devices

When adding new devices to the G450, consult your project manager for topology requirements for specific ports to be connected to specific devices.

Adding a media moduleVarious media modules including voice modules or WAN modules can be added to the Avaya G450 Media Gateway.

Adding voice modulesYou can hot-swap voice modules. This means you can add or remove a voice module in the Avaya G450 Media Gateway while the system is running, without any disruption to your network. Configuration of the G450 is not necessary when you add or remove a voice module. Configuration is only necessary when you add telephones, fax machines, and trunks to the new module. See Adding a telephone on page 89 and Adding a trunk on page 90.

Some configuration of the Avaya Communication Manager is necessary when you install an MM710, MM720, or MM722 media module. See Administrator’s Guide for Avaya Communication Manager, 555-233-506. Also, for an MM710 or MM722, it is usually advisable to set the media module as the synchronization source of the G450. For information about setting the synchronization source of the G450, see Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers, 03-300431.

Adding WAN modulesYou can hot-swap WAN modules. This means you can add or remove a WAN module in the Avaya G450 Media Gateway while the system is running, but the G450 resets when you add or remove the module. However, hot insertion and removal is not recommended in most cases. Because hot insertion or removal resets the G450, any translation and other data that is in the running configuration but has not been saved to the startup configuration will be lost.

Adding media modules and devices


There is no configuration necessary when you add or remove a WAN module. Configuration is only necessary when you add WAN lines to the new module. See Adding a WAN line on page 91.

Adding a LAN deviceYou must connect, configure and test the LAN device before adding the device to the Avaya G450 Media Gateway.

For instructions on connecting a new LAN device, see Connecting a switch or a network data port on page 47.

Configuring the LAN device on the G450Configuration may be performed on site by connecting a laptop computer to the CON port or Services port of the G450, or remotely via a modem connected to the G450 or S8300.

For information about connecting a laptop to the Services port, refer to Connecting a computer to the Services port on page 48. For information about preparing a modem, refer to Chapter 4: Connecting and enabling a modem for remote access on page 63. For information about configuration, refer to Chapter 5: Configuring the G450 on page 81.

Recording LAN information for software configuration

Before software configuration for the new LAN device takes place, gather the following information:

● The name and location of the owner of or person responsible for the LAN device

● The slot and port number on the Avaya G450 Media Gateway to which the LAN device connects. If the LAN device is connected to an IP telephone, note the extension of the telephone to which the LAN device connects, and the slot and port number on the G450 to which the telephone connects.

Testing the LAN deviceAfter installation and configuration of the LAN device is complete, ping the IP address of the device to test the device’s connectivity within the network and outside the network.

Adding a telephone


Adding a telephoneYou must connect, configure and test the telephone before adding the telephone to the Avaya G450 Media Gateway.

Connecting the telephoneTo connect a new telephone, refer to of the following sections:

● Connecting an IP telephone on page 48

● Connecting an analog telephone on page 50

● Connecting a DCP telephone to an MM712 or MM717 media module on page 52

Configuring the telephone on the G450Configuration may be performed on site by connecting a laptop computer to the CON port or Services port of the G450, or remotely via a modem connected to the G450 or S8300.

For information about connecting a laptop to the Services port, refer to Connecting a computer to the Services port on page 48. For information about preparing a modem, see Chapter 4: Connecting and enabling a modem for remote access on page 63. For information about configuration, see Chapter 5: Configuring the G450 on page 81.

Recording telephone information for software configuration

When you add a new telephone, note the following information for software configuration:

● Name and location of the owner of the telephone

● Model number of the telephone

● Extension of the telephone

● Slot and port number on the Avaya G450 Media Gateway to which the telephone connects

Testing the telephone1. Make outgoing calls from the telephone. Make sure you hear a dial tone when you pick up

the receiver. Make sure you can make both an internal (within the local network) and an external (outside of the local network) call.

2. Make a call to the telephone from both within the network and outside of the network.



Adding a trunkYou must order, connect, configure, and test the trunk before adding the trunk to the Avaya G450 Media Gateway.

Ordering the trunk● Make sure to install the trunk near the physical location of the Avaya G450 Media Gateway

● Make sure that the telephone service provider installs the trunk and verifies that the trunk is working properly before you contact the technician that is performing or supervising the configuration

● Note the telephone number of the trunk

Special considerations when ordering an analog trunkWhen you order an analog trunk, there are several recommendations depending on your system’s particular needs:

● For optimal functioning of the Emergency Transfer Relay feature, it is recommended to use a loop-start trunk

● For voice mail systems in the United States, it is recommended to use a ground start trunk to ensure that calls are properly disconnected when the outside caller disconnects

● For access to voice mail systems in the United States, it is recommended to use a ground start trunk to ensure that calls are properly disconnected when the outside caller disconnects. Ground start trunks may be provided via the MM711 media module.

● Request conditioned lines to ensure satisfactory voice quality and trunking interactions

Connecting the trunkTo connect a new trunk, see one of the following sections:

● Connecting an analog trunk on page 53

● Connecting an E1/T1 trunk on page 54

● Connecting an ISDN BRI trunk on page 54

Adding a WAN line


Configuring the trunk on the G450Configuration may be performed on site by connecting a laptop computer to the CON port or Services port of the G450, or remotely via a modem connected to the G450 or S8300.


Recording trunk information for software configuration

When you add a new trunk, note the following information for software configuration:

● Slot and port number on the Avaya G450 Media Gateway to which the trunk connects

● Telephone number of the trunk

Testing the trunk1. Make outgoing calls from the trunk. Ask the technician that is performing or supervising the

configuration for instructions how to access the trunk. Make sure you can make both an internal (within the local network) and an external (outside of the local network) call.

2. Make a call into the G450 trunk.

Adding a WAN lineYou must order, connect, configure and test the WAN line before adding the line to the Avaya G450 Media Gateway.

Ordering the WAN lineIf you need to order the WAN line, make sure that the service provider installs the line near the physical location of the G450 and verifies that the line is working before you configure the WAN on the G450.



Connecting the WAN lineTo connect a WAN line, see Step 3: Connecting to the Wide Area Network (WAN) on page 57.

Configuring the WAN line on the G450Configuration may be performed on site by connecting a laptop computer to the CON port or Services port of the G450, or remotely via a modem connected to the G450 or S8300.


Recording WAN information for software configuration

When you add a new WAN line, note the following information for software configuration:

● Slot and port number on the Avaya G450 Media Gateway to which the WAN line connects

Testing the WAN linkAfter installation of the WAN line is complete, test the link by verifying that the SIG LED for the port to which the link connects is lit. It is also recommended that you ping the IP address of a device using the WAN line and perform a trace route test in order to test connectivity with the network and outside the network.

Adding an Avaya Partner Contact Closure AdjunctTo install an Avaya Partner Contact Closure Adjunct, follow the instructions in Step 5: Installing the Avaya Partner Contact Closure Adjunct on page 59.


Chapter 8: Upgrading and replacing Field Replaceable Units

You can add or remove VoIP modules, the fan tray, or a power supply unit. Refer to Equipment List on page 295 for ordering information.

Adding or removing G450 main board modulesYou can add or remove VoIP modules in the G450 main board. To do so, you must pull out the G450 main board. The G450 supports hot insertion and removal of the main board without power drop. However, all services are suspended while the G450 main board is out, and all calls are disconnected. Any translation and other data that is in the running configuration but has not been saved to the startup configuration is lost.

ELECTROSTATIC ALERT:ELECTROSTATIC ALERT: Hold the module only by the edges to avoid damage from static electricity. Do not

touch the top or bottom of the circuit board. If possible, wear a wrist-strap and use an anti-static bag.



Note:Note: Consult your project manager before adding or removing VoIP modules in the

G450.

Removing and inserting the G450 main board1. To remove the G450 main board:

a. Unscrew the two captive screws, one at each side of the G450 main board front panel.

b. Open the latches on both sides of the main board.

c. Grasp the latches and pull out the main board from its slot.

d. Place the main board carefully on a table.

Upgrading and replacing Field Replaceable Units


2. To insert the G450 main board:

a. Open the latches on both sides of the slot.

b. Insert the G450 main board vertically into the slot.

c. Push the main board in until the latches begin to close.

d. Close and tighten the two captive screws on the front panel and then tighten the latches.

e. Use the show platform mainboard CLI command to make sure everything is OK.

Figure 37: Removing and inserting the G450 main board

Adding or removing VoIP modules: MP20 and MP80The G450 main board has four slots for VoIP engines. Each slot can accommodate either an MP20 (Media Processor 20) module or an MP80 (Media Processor 80) module. An MP20 provides 20 channels, and an MP80 provides 80 channels. However, the G450 supports a maximum of 240 active channels. Therefore, the following number of active channels can be supported: 20, 40, 60, 80, 100, 120, 140, 160, 180, 200, or 240. Note that 220 channels cannot be supported.

ELECTROSTATIC ALERT:ELECTROSTATIC ALERT: Hold modules only by the edges to avoid damage from static electricity. Do not

touch the top or bottom of the circuit board. If possible, wear a wrist-strap and use an anti-static bag.



There is no configuration necessary when you install an MP20 or MP80 module.

1. To insert an MP20 or MP80 module:

a. Locate the MP20 or MP80 module slot (see Figure 38).

Adding or removing G450 main board modules


Figure 38: Location of MP20 and MP80 modules

b. Position the MP20 or MP80 module at a 45 degree angle to the main board, and start inserting it into an MP20 or MP80 slot (see Figure 39).

Figure notes:

1. MP20 or MP80 module slot2. MP20 or MP80 module slot

3. MP20 or MP80 module slot4. MP20 or MP80 module slot



Figure 39: Adding or removing an MP20 or MP80 module

c. Push the module in all the way. Do not use too much force.

d. Flatten the module so it is flush with the main board. The latches at both sides click shut.

e. After powering up, use the show platform mainboard CLI command to make sure everything is OK.

2. To remove an MP20 or MP80 module:

a. Open the latches on both sides of the module slot. The module lifts up.

b. Pull out the module. Touch the module only at the edges.

Replacing the fan trayThe fan system is field replaceable. It is mounted on a fan tray that can be replaced as one unit.

The G450 supports hot swap of the fan tray. There is no need to power down or reset the G450 when replacing a faulty fan tray unit.

Prepare the new fan tray for insertion before removing the current the fan tray: take the new fan tray out of its package and place it nearby.

Replacing a power supply unit


! Important:Important: Replace the fan tray within one minute, to avoid overheating the G450. If the

G450 exceeds its allowed heat level, it shuts down.

Figure 40: Replacing the fan tray

1. To remove the fan tray:

a. Unscrew the two captive screws on the front panel of the fan tray.

b. Grasp the screws and pull the fan tray out of its slot.

2. To insert the fan tray:

a. Insert the fan tray all the way into the slot.

b. Close and tighten the two captive screws on the front panel.

The fans start operating immediately.

c. Wait one minute and then use the show platform fans CLI command to make sure everything is OK.

Replacing a power supply unitThe G450 provides full redundant, load sharing power supply units (1 + 1). A single power supply unit provides sufficient power for any G450 configuration. If you choose to install two power supply units, they operate in a load sharing mode.

The G450 supports hot swap of the power supply unit. Even if you have only one PSU unit installed, there is no need to power down or reset the G450 when replacing a faulty power unit. You can install the replacement PSU in the second PWR slot, and it will become the active PSU once you remove the faulty PSU.



Figure 41: Replacing a power supply unit

1. To remove a power supply unit:

a. Disconnect the G450 power cable from the mains socket.

b. Disconnect the G450 power cable from the power connector, located on the front panel of the power supply unit, at the rear of the G450.

c. Loosen the two captive screws, one on each side of the power supply unit.

d. Grasp the two side handles and pull the power supply unit out of its slot.

2. To insert a power supply unit:

a. Position the power supply unit before the opening and engage both sides of the unit in the interior guides.

b. Slide the power supply unit slowly into the chassis, maintaining an even pressure to assure that the unit does not become twisted or disengaged from the guides.

c. Close and tighten the two captive screws on the front panel.

d. Connect the power cable to the power connector on the power supply unit.

e. Plug the power cable into a mains socket.

f. After powering up, use the show platform power CLI command to make sure everything is OK. The upper PSU is referred to as PSU #1 in the CLI, and the lower PSU is PSU #2.


Chapter 9: Upgrading the AvayaCommunication Manager software

If your Avaya G450 Media Gateway includes an Avaya S8300 Server, it might be necessary to upgrade the Avaya Communication Manager software. Upgrading the software can be performed in one of the following ways:

● Remote configuration via Telnet — upgrade the software remotely via Telnet. In this scenario, a modem is required at the local site. See Chapter 4: Connecting and enabling a modem for remote access on page 63.

● Local configuration with S8300 Media Gateway — upgrade the software at the site, using a laptop computer and a CD-ROM drive connected to the S8300 Media Gateway

● Remote configuration via network — upgrade the software remotely via a network connection

Upgrading the software using a CD-ROM driveThe upgrade software is usually installed from a CD-ROM drive connected to the S8300. If the upgrade is performed locally, you might need to provide a laptop and a USB CD-ROM drive. If the upgrade is performed from a remote location, you must connect a USB CD-ROM drive to the S8300 and insert the upgrade CD-ROM in the CD-ROM drive. You also might need to connect a modem. This depends on the method used to perform the upgrade.

For a software upgrade on an Avaya G450 Media Gateway with an S8300 Server, use a USB modem. The only supported USB modem is the Multitech MultiModem USB, MT5634ZBA-USB-V92.

Local configuration with S8300 Media GatewayUpgrade the software at the site, using a laptop computer and a CD-ROM drive connected to the S8300 Media Gateway.

1. Connect the modem to a working telephone line. Note the telephone number of the line to which you connect the modem, so that you can provide the number to the technician who is performing or supervising the configuration.

Upgrading the Avaya Communication Manager software


2. Connect the USB modem to either of the two USB ports in the Avaya S8300 Server.

Note:Note: You may be required to enable the modem and port. For instructions on enabling

the modem, see Chapter 4: Connecting and enabling a modem for remote access on page 63.

3. Connect a USB CD-ROM drive to the free USB port on the Avaya S8300 Server. Then, insert the CD-ROM provided by Avaya into the CD-ROM drive.

Upgrading the software without a CD-ROM driveYou can upgrade the Avaya Communication Manager software without a CD-ROM drive by downloading the upgrade software or installing it from a laptop computer.

Remote configuration● Remote configuration via Telnet — upgrade the software remotely via Telnet. In this

scenario, a modem is required at the local site. See Chapter 4: Connecting and enabling a modem for remote access on page 63.

● Remote configuration via network — upgrade the software remotely via a network connection

Performing the upgradeYou can upgrade the S8300 using Avaya IW or the Upgrade tool. To upgrade S8300 software using Avaya IW, see Appendix C: Running the Avaya Installation Wizard (Avaya IW) on page 151. For information about upgrading S8300 firmware using the Upgrade tool, see Appendix D: Running the Gateway Installation Wizard (GIW) on page 209.


Chapter 10: Upgrading the G450 firmware

Software used to control the Avaya G450 Media Gateway itself and media modules installed on the G450 is called firmware. You can upgrade the firmware on the Avaya G450 Media Gateway and media modules using various different tools, each suitable for specific types of installation.

Note:Note: The G450 firmware also includes the firmware for the MM340 and MM342 media

modules.

Upgrading G450 firmware using Avaya Software Update Manager

You can use Avaya Software Update Manager to view your network inventory and the firmware vintages of devices on your network. Avaya Software Update Manager can also check the software versions currently in use against the latest versions available from Avaya and recommend updates when a newer version is available. Based on this information, you can download new firmware to multiple network devices simultaneously from a single management station, ensuring all devices are updated.

You can use Avaya Software Update Manager to take a new release from Avaya's website and store it on your hard disk for subsequent downloading to the appropriate devices.

Avaya Software Update Manager is a server application hosted on the Avaya Network Management server. The server stores all the software retrieved from the Web and can download the software to appropriate devices. You may also copy files containing embedded software to the server. You can reach the server locally or via remote access, so you can update the software on your devices from anywhere in the world.

Avaya Software Update Manager is part of the Integrated Management Enterprise Package which is an entitlement for all Avaya Communication Manager non-introductory offers.

For information about using Avaya Software Update Manager, see the Avaya Software Update Manager 3.6 User Guide, 14-300168.

Upgrading the G450 firmware


Upgrading G450 firmware from the primary controllerFor a G450 without an S8300 or for a G450 with an S8300 installed as an LSP, you can upgrade G450 firmware from the remotely located primary controller using the Upgrade Tool. The primary controller may be an S8300, S8500, or S8700-series server. If the G450 includes an LSP, you can also use the Upgrade Tool to upgrade the S8300 software on the LSP. For information about using the Upgrade Tool, see Job Aid: Upgrade Tool and Worksheets, 555-245-757.

You can also refer to the guide for the primary controller for information about upgrading firmware from the primary controller. See Upgrading, Migrating, and Converting Avaya Servers and Gateways, 03-300412.

Upgrading G450 firmware using Gateway Installation Wizard (GIW)

1. Prepare installation worksheets. See Preparing installation worksheets on page 105.

2. Download GIW from the Avaya Support website (support.avaya.com/avayagiw) to the laptop computer. The laptop should be running Windows 2000 or Windows XP to support GIW.

3. Set up a TFTP server on the G450 network. See Setting up a TFTP server on page 107. The GIW runs the CLI commands on the G450 so the G450 can obtain the files from the TFTP server.

4. Download the G450 firmware files to the TFTP server. See Downloading G450 firmware files to a local TFTP server on page 108.

5. Run GIW to perform the upgrade. For instructions on performing the upgrade, see Appendix D: Running the Gateway Installation Wizard (GIW) on page 209.

Note:Note: This upgrade must be done locally.

Note:Note: You can only use GIW to upgrade firmware on a G450 that does not contain an

S8300.

Upgrading G450 firmware and Avaya Communication Manager software using Avaya Installation Wizard


Upgrading G450 firmware and Avaya CommunicationManager software using Avaya Installation Wizard (IW)

For a G450 with an S8300B installed, you can use Avaya IW to upgrade G450 firmware and Avaya CM software. You can run Avaya IW from a remote location if the software is loaded locally. You can point your browser to the ip address of the S8300B if you are in the customer network or via the modem connection.


2. Place the upgrade software and firmware files on a laptop. These files are on the Avaya Communication Manager CD-ROM. To upgrade the S8300 Server software and G450 firmware, insert the Communication Manager CD-ROM into a CD-ROM drive connected to a laptop. Alternatively, you can upload the individual files to the hard drive of the laptop. For more details, see Job Aid: Avaya Installation Wizard, 555-245-754.

3. Upgrade the S8300 Server using the Avaya Installation Wizard. For more details, see Job Aid: Avaya Installation Wizard, 555-245-754. This procedure also copies the G450 firmware as an RPM (Red Hat Package Manager) file from the Communication Manager CD-ROM into the /tftproot directory on the S8300.

Note:Note: The CD-ROM may not contain the latest firmware. Therefore, you should check

the Avaya Support website for the latest firmware versions and match these against the versions in the directory. If the CD-ROM does not contain the latest versions, you should download the latest versions from the Avaya Support website to the laptop.

4. Connect the laptop to the services port of the S8300 Server.

5. Access Avaya IW. See Accessing Avaya IW on page 151.

6. Run Avaya IW to perform the required upgrades:

● See Upgrading an existing MGC on page 160 for instructions for upgrading Avaya CM software

● See Firmware configuration on page 177 for instructions for upgrading G450 firmware



Upgrading G450 firmware using the CLI via FTP/TFTPYou can upgrade firmware via FTP/TFTP using the CLI. You can perform the upgrade remotely via a modem connection, but the upgrade files must first be downloaded to an FTP or TFTP server on the LAN connected to the G450.


2. Set up an FTP or TFTP server on the LAN connected to the G450. For information about setting up a TFTP server, see Setting up a TFTP server on page 107.

Note:Note: If you use an FTP server, the G450 prompts you for a username and password

when you enter a command to transfer a file. Also, when opening an FTP connection to the S8300, all anonymous FTP file transfers are restricted to the /var/home/ftp/pub directory. Permission for anonymous FTP users to create files in other directories is denied.

3. Download the firmware files to the FTP or TFTP server. See Downloading G450 firmware files to a local TFTP server on page 108 or Installing firmware from the TFTP server on the S8300 Server on page 109.

4. Connect to the G450 via modem or via the CON port on the front panel. For information about connecting and enabling a modem for remote access, see Chapter 4: Connecting and enabling a modem for remote access on page 63.

5. Run CLI commands. See CLI commands for upgrading G450 firmware via FTP/TFTP on page 104.

CLI commands for upgrading G450 firmware via FTP/TFTPYou can use CLI commands to upload an upgrade file to the G450. For each of these commands, include the full path of the file and the IP address of the FTP or TFTP host as parameters. You must use the specific path to the file on the FTP or TFTP server according to the home directory of the service (FTP or TFTP) that you are using. When you enter the command, the CLI prompts you for a username and password.

● Use the copy ftp EW_archive command to upgrade the Java applet for Avaya G450 Manager software from an FTP server

● Use the copy ftp module command, followed by the module number of the module you want to upgrade, to upgrade the firmware on a media module from an FTP server

● Use the copy ftp SW_imageA command to upgrade the G450 firmware into Bank A from an FTP server

● Use the copy ftp SW_imageB command to upgrade the G450 firmware into Bank B from an FTP server

Upgrading G450 firmware using the CLI via FTP/TFTP


● Use the copy tftp EW_archive command to upgrade the Java applet for Avaya G450 Manager software from a TFTP server

● Use the copy tftp module command, followed by the module number of the module you want to upgrade, to upgrade the firmware on a media module from a TFTP server

● Use the copy tftp SW_imageA command to upgrade the G450 firmware into Bank A from a TFTP server

● Use the copy tftp SW_imageB command to upgrade the G450 firmware into Bank B from a TFTP server

Example upgrade via FTP/TFTP using the CLITo upgrade the firmware of an MM712 media module in slot 3 from a TFTP server with the IP address 192.1.1.10, where the home directory is c:\home\ftp\ and the upgrade file is located in the directory c:\home\ftp\version, use the following command:

copy tftp module \version\mm712v51.fdl 192.1.1.10 3

Note:Note: When uploading firmware from the S8300, use only the file name, without the

directory path, in the command line. Otherwise, the procedure will fail. For instance, in the example above, you must use the following command:copy tftp module mm712v51.fdl 192.1.1.10 3



The following example uploads a firmware version with the path and file name C:\g450.net from an FTP server with the IP address 149.49.134.153 to Bank A of the G450:

copy ftp SW_imageA C:\g450.net 149.49.134.153

Preparing installation worksheetsBefore you perform the upgrade, you must enter the names of the target software and firmware versions that you need to install in the software and firmware upgrade worksheet. If you will need to set up a TFTP server, you also need to plan the TFTP server IP address, login, and password.



Entering values in Server Values worksheet

Enter software and firmware upgrade file names in the following table:

Enter the TFTP server information in the following table:

Table 6: Software and firmware upgrade file names

Items for Upgrading New file name for target

File for LSP and primary controller (not used with Gateway Installation Wizard or for individual files)

G450 Processor

G450 Device Manager

MM710 E1/T1 Media Module

MM711 Analog Port/Trunk Media Module

MM712 DCP Media Module



MM717 24-port DCP Media Module

MM720 BRI Media Module

MM722 BRI Trunk Media Module

Table 7: Global Settings for TFTP Server

TFTP Server IP Address

TFTP Server Directory



Setting up a TFTP serverTo load individual firmware files on an Avaya G450 Media Gateway, you must place the files on a PC connected to the customer’s LAN or on an S8300 Server in the customer’s network. Later, you will log onto the G450 and use its TFTP capability to download the new firmware. If you can use an S8300 Server to stage the firmware, see Installing firmware from the TFTP server on the S8300 Server on page 109. If not, a TFTP server must be set up on the LAN.

Note:Note: A Linux or Unix TFTP server should be used only if a Linux or Unix TFTP server

already exists on the local network. In this case, download the appropriate files to your laptop and give it to the customer for proper placement and execution.

Setting up a TFTP on the LAN1. On the hard drive of the local PC, create a directory into which you will load the G450

firmware. It is recommended that you call the directory C:\tftp.

2. Connect to the LAN using Microsoft Internet Explorer on the local PC and access http://www.avaya.com/support on the Internet.

3. Search for software downloads for 4600 series IP telephones.

4. Double-click one of the links listed with TFTP Server. The TFTP Server is on the Communication Manager CD-ROM. For example:4630 IP Telephone R 1.73 and TFTP Server.

5. Scroll to the bottom of the page to find the TFTP Server Application file, iptel_avaya_tftp.exe.

6. Double-click the file and download it to the local PC that will serve as the TFTP server. Record the directory location of the file.

Note:Note: You may also wish to download and view or print the file iptel.pdf, which provides

instructions on installing iptel_avaya_tftp.exe for Windows servers.

7. After downloading the iptel_avaya_tftp.exe file to the PC, double-click the file and follow instructions to install it. By default, the installation program creates the directoryC:\Program Files\Walusoft\TFTPSuite containing the application files.

8. When the file has been installed, go to the directory where the software was installed and double-click the file tftpserver32.exe to open the program. The TFTP Server window appears and displays the IP address of the PC in the upper border, plus port 69.

9. Enable the TFTP server as follows:

a. From the System menu, select Setup. The server option window appears.





b. Select the Outbound tab, and enter the directory location of the TFTP server for the outbound file path.

c. Select the Options tab, and enter 69 in the Use Port field (default).

d. Select No Incoming (default). However, if you wish to copy files as a backup prior to performing a software upgrade, leave this field unselected.

e. Select the Inbound tab, and enter the directory path of the TFTP server for the inbound file path.

f. Click OK.

Downloading G450 firmware files to a local TFTP server1. Access the www.avaya.com/support website.

2. Navigate to G450 Media Gateway downloads.

3. Locate the file names that match the files listed in your installation worksheet. See Table 8 for sample firmware file names.

4. Double-click the file name of the file you want to download. A File Download window appears.

5. Select Save this file to disk.

6. Save the file to directory on the TFTP server on the local LAN that was created for this purpose. See Setting up a TFTP server on page 107.

Note:Note: If you are performing the upgrade using the G450’s Command Line Interface

(CLI) or the Upgrade Tool, you can place the upgrade files on an FTP server. However, the GIW requires that the files be placed on a TFTP server.

Note:Note: Use WinZip or another zip file tool to unzip the file, if necessary, before you copy

the file to the TFTP server.

Table 8: Sample Software and Firmware File names

Component File name Example

G450 Processors

G450 Processor g450_sw_21_11_0.bin

G450 Device Manager g450_emweb_1_0_7.bin

1 of 2




Installing firmware from the TFTP server on the S8300 ServerInstead of using a separately configured TFTP server on the LAN, you can use the TFTP server capability of an S8300 Server to stage the firmware for upgrading the G450. To do this, you must copy the individual firmware files to the /var/home/ftp/pub directory on the S8300 Server using the Download Files web page on the S8300 Server. You must then copy the files to the /tftpboot directory of the S8300 Server.

After copying the files to the /tftpboot directory, you can use the GIW or the Upgrade Tool to install the files to the G450 or its media modules by specifying the S8300 Server’s IP address as the TFTP server containing the new firmware files.

Note:Note: You only have to do this if you have not upgraded the S8300 first or if you did

upgrade it first and found that the gateway files on the communication manager CD were out of date. Otherwise, when you upgrade the S8300, the files appear in the /tftpboot directory automatically.

Media Modules

MM710 E1/T1 Media Module mm710v3.fdl

MM711 Analog Port/Trunk Media Module (version 6 or earlier)

mm711v16.fdl

MM711 Analog Port/Trunk Media Module (version 7)

mm711h7v21.fdl

MM711 Analog Port/Trunk Media Module (version 20 or later)

mm711h20v54.fdl

MM712 DCP Media Module mm712v14.fdl

MM714 Analog Port/Trunk Media Module mm714v5.fdl

MM716 Analog Port/Trunk Media Module mm716v80.fdl

MM717 DCP Media Module Mm717v3.fdl

MM720 BRI Media Module mm720v1.fdl

MM722 BRI Media Module mm722v3.fdl

Table 8: Sample Software and Firmware File names (continued)

Component File name Example

2 of 2



Copying firmware files to the /tftpboot directory of an S8300 Server

1. Use Telnet, Avaya Site Administration, or another tool to access the S8300 Server command line.

2. Log in as craft.

3. At the Linux prompt, type cd /var/home/ftp/pub and press <Enter>. The Linux prompt reappears. The current directory has changed to /var/home/ftp/pub.

4. At the Linux prompt, type mv <firmware_filename> /tftpboot, and press <Enter> to move the firmware file to the /tftpboot directory. To move multiple firmware files (most firmware files have an .fdl suffix), use the command mv *.fdl /tftpboot. The Linux prompt reappears. The firmware file has been moved to the /tftpboot directory. If you copy the firmware using the cp command, remove the files from the /var/home/ftp/pub directory after you have copied them.

5. Repeat step 4, if necessary, for each firmware file you want to install.

6. At the Linux prompt, type cd /tftpboot. The Linux prompt reappears. The current directory has changed to /tftpboot.

7. At the Linux prompt, type ls, and press <Enter>. A list of files in the directory appears.

8. Check the directory to make sure the firmware files you want to install are listed.

Upgrading G450 firmware using the CLI via a USB device


Upgrading G450 firmware using the CLI via a USB deviceYou can upgrade firmware via a USB mass storage device using the CLI. The upgrade files must first be downloaded to a local PC.


2. Download the firmware files to a PC. See Downloading G450 firmware files to a local PC on page 112.

3. Insert a USB mass storage device into the PC’s USB port, and copy the firmware files to the USB mass storage device.

4. Remove the USB mass storage device from the PC, and insert it into a G450 USB port.

5. Run CLI commands to copy the firmware files from the USB mass storage device to the G450. See CLI Commands for upgrading G450 firmware via a USB device on page 111.

CLI Commands for upgrading G450 firmware via a USB deviceYou can use CLI commands to upload an upgrade file from a USB mass storage device to the G450. You must use the specific path to the file on the USB mass storage device.

● Use the copy usb EW_archive command to upgrade the Java applet for Avaya G450 Manager software from a USB mass storage device

● Use the copy usb module command, followed by the slot number of the module you want to upgrade, to upgrade the firmware on a media module from a USB mass storage device

● Use the copy usb SW_imageA command to upgrade the G450 firmware into Bank A from a USB mass storage device

● Use the copy usb SW_imageB command to upgrade the G450 firmware into Bank B from a USB mass storage device

Example upgrade using the CLI via a USB deviceTo upgrade the firmware of an MM712 media module in slot 3 from a USB mass storage device where the upgrade file is located in the directory \temp\, use the following command:

copy usb module usb-device0 \temp\mm712v51.fdl 3



Downloading G450 firmware files to a local PC1. Access the www.avaya.com/support website.

2. Navigate to G450 Media Gateway downloads.

3. Locate the file names that match the files listed in your installation worksheet. See Table 8 for sample firmware file names.

4. Double-click the file name of the file you want to download. A File Download window appears.

5. Select Save this file to disk.

6. Save the file to a directory on the local PC.

Note:Note: Use WinZip or another zip file tool to unzip the file, if necessary, before you copy

the file to the PC.



Chapter 11: Upgrading IP phone configuration and firmware files

The Avaya G450 Media Gateway supports Trivial File Transfer Protocol (TFTP) downloading of configuration files and firmware files for IP phones. TFTP can be used to download image files, upgrade scripts, and settings files to IP phones. The local TFTP server stores the files and supports requests to read files from the its outgoing directory for phone images and scripts.You can use CLI procedures for downloading the files for IP phone upgrade from the G450 TFTP server.

Note:Note: You can also upgrade IP phones using the S8300. For more details refer to

http://support.avaya.com/elmodocs2/white_papers/TFTP_HTTP_Download_External_060504.pdf

IP telephones supported by the local TFTP Server feature● 4601

● 4602

● 4602SW

● 4606

● 4610SW

● 4612/24

● 4620

● 4620SW

● 4690

● SIP phone: 4602 SIP

IP telephones not supported by the local TFTP Server feature● 4630

● 4630SW

Note:Note: If you have an S8300 installed in the G450, you can alternatively upgrade IP

phones using the CM web pages.

Upgrading IP phone configuration and firmware files


Note:Note: You can also upgrade IP phones using Avaya IW or GIW, as described in

Appendix C: Running the Avaya Installation Wizard (Avaya IW) on page 151 and Appendix D: Running the Gateway Installation Wizard (GIW) on page 209.

Note:Note: An alternative tool, the Avaya Software Update Manager (4.0 or higher), is a GUI

application that greatly simplifies the IP phone upgrade process, avoiding the need to know the file names of the necessary upgrade files for each IP phone type. For further information, see Avaya Software Update Manager User Guide, 14-300168.

Note:Note: The IP address of the TFTP server is the PMI.

Administering the upgradeWhen using supported IP phones with the G450, the IP phones require the downloading of the settings file and the upgrade scripts. These files are stored in the script banks in NVRAM and are preserved in the event of a reset or power failure. There are two script banks.In addition, each phone can have a booter application and a phone application. There are four banks that can store up to two phone images (booter and phone application files) at any given time. Since the image files are stored in RAM, a reset or power failure erases these files. The image files are used only for upgrading the IP phone, so there is no need to store them permanently. However, the scripts are used by the IP phones when they are reset, and are therefore stored in NVRAM. You can upgrade up to two types of phones and then release the banks for use with another IP phone type.There are cases where the image files are the same for different IP phone types. In these cases, you can download the image files once for the IP phones that use the same image. The scripts are global to all the supported IP phone images.You can download and then upload setting script files in order to update their content. It is not recommended to change the upgrade script.By default, the RAM allocation for TFTP server is 10 MB. You can increase the RAM allocation for TFTP server to up to 11.264 MB at the expense of the Sniffer cache application. The maximum RAM for both applications is 12 MB. There are four image banks, supporting two IP phone images in RAM, provided the combined file sizes do not exceed the RAM allocation for TFTP server. The maximum size for a booter application or phone application file is 4.5 MB. Thus, it is possible that in some cases, the allocation may only suffice for one complete IP phone image and not two.

Administering the upgrade


! CAUTION:CAUTION: To activate a change in RAM allocation to the TFTP server, reset is required.

Upon reset, any phone image files stored in RAM are erased.

Note:Note: Previous releases of TFTP server required the configuration of the DHCP server

option 43/176 with the named value pair TFTPDIR=/phonedir/ in order to allow the IP phone to access the files in this directory. This configuration is still supported but is no longer required.

Upgrading the IP telephoneIP phone upgrade files include script files, boot images files, and phone application image files. You can download these files to a remote FTP/TFTP/SCP server, or you can download them to a laptop and copy them to a USB device. You can then copy the upgrade files to the G450.

Note:Note: An SCP server can be used for copying the script files, which do not exceed

128 KB, but cannot be used for copying image files.

Note:Note: The G450 uses the SSH protocol to support the use of SCP for secure file

transfer. When using SCP, the G450 is the SCP client, and an SCP server must be configured on the management station. For more information about establishing an SCP session, see Administration for the Avaya G450 Media Gateway, 03-602055.

1. Check the available memory size for the image files using the show application-memory command. If the memory size needs to be changed, proceed to step 2, otherwise proceed to step 6.

2. Set the memory size for the image files using the ip tftp-server file-system size command.

3. Copy the running configuration to the start-up configuration using the copy running-config startup-config command.

4. Reset the G450 using the reset command.

5. From the Avaya Support website, obtain the desired phone upgrade files (script files, boot image files, phone application image files), using either of the following methods:

- Download the phone upgrade files to a remote FTP/TFTP/SCP server. Note that SCP can be used to download script files but not image files.

- Download the upgrade files to a laptop and copy them to a USB mass storage device.



6. Copy the script files for the IP phone family.

- To copy from the remote FTP/SCP/TFTP server, use one of the following commands:

● copy scp phone-script

● copy ftp phone-script

● copy tftp phone-script

- To copy from the USB device, insert the USB device into a G450 USB port and copy the files to the resident TFTP server using the copy usb phone-script command.

7. Copy the boot image files for up to two IP phone types.

- To copy from the remote FTP/TFTP server, use either the copy ftp phone-image command or the copy tftp phone-image command for each IP phone type.

- To copy from the USB device, insert the USB device into a G450 USB port and copy the files to the resident TFTP server using the copy usb phone-image command.

8. Copy the phone application image files for up to two IP phone types.

- To copy from the remote FTP/TFTP server, use either the copy ftp phone-image command or the copy tftp phone-image command for each IP phone type.

- To copy from the USB device, insert the USB device into a G450 USB port and copy the files to the resident TFTP server using the copy usb phone-image command.

9. Reset the phones and wait for the installation to be completed.

Note:Note: Once the upgrade procedure is complete, you can delete the files using the

erase phone-image command.

TFTP IP telephone upgrade examplesIn the following example, 4602SW and 4602D phones, which use the same image files, are upgraded first. Later, 4620 phones are upgraded. The script files are not copied for the second upgrade, since they are already stored in NVRAM.

TFTP IP telephone upgrade examples


Upgrading the 4602SW and 4602D phones1. Check the available memory size for the image files using the show

application-memory command. If the memory size is smaller than the combined sizes of the image files for the phones, proceed to step 2, otherwise proceed to step 5.

2. Set the memory size for the image files using the ip tftp-server file-system size command. For example:

3. Copy the running configuration to the start-up configuration using the copy running-config startup-config command. For example:

4. Reset the G450 using the reset command. For example:

5. From the Avaya Support website, download the desired phone upgrade files (script files, boot image files, phone application image files) to a remote FTP server at IP address 192.168.49.10.

G450-001(super)# ip tftp-server file-system-size 18128To change ip tftp-server file system size, copy the running configuration to the start-up configuration file, and reset the deviceG450-001(super)

G450-001(super)# copy running-config startup-configBeginning copy operation ................... Done!

G450-001(super)# resetThis command will reset the device*** Reset the device *** - do you want to continue (Y/N)? y

Resetting the device...



6. Copy the script files for the 46xx IP phone family using the copy ftp phone-script command. For example:

7. Copy the boot image files for the Avaya 4602 IP telephone using the copy ftp phone-image command. For example:

G450-001(super)# copy ftp phone-scriptA 46xxupgrade.txt 192.168.49.10Confirmation - do you want to continue (Y/N)? y

Username: rootPassword:Beginning download operation ...

This operation may take up to 20 seconds.Please refrain from any other operation during this time.For more information , use 'show download phone-script-file status' commandG450-001(super)#G450-001(super)# copy ftp phone-scriptB 46xxupgrade.txt 192.168.49.10Confirmation - do you want to continue (Y/N)? y

Username: rootPassword:Beginning download operation ...

This operation may take up to 20 seconds.Please refrain from any other operation during this time.For more information , use 'show download phone-script-file status' commandG450-001(super)#

G450-001(super)# copy ftp phone-imageA pub\4602dbte1_8.bin 192.168.49.10

Username: rootPassword:Beginning download operation ...This operation may take up to 20 seconds.Please refrain from any other operation during this time.For more information , use 'show download phone-image-file status' commandG450-001(super)# copy ftp phone-imageB pub\4602sbte1_8.bin 192.168.49.10

Username: rootPassword:Beginning download operation ...This operation may take up to 20 seconds.Please refrain from any other operation during this time.For more information , use 'show download phone-image-file status' command

TFTP IP telephone upgrade examples


8. Copy the phone application image files for the 4602 IP phone type DEF4602D using the copy ftp phone-image command. For example:

9. Reset the phones and wait for the installation to be completed.

Upgrading 4620 IP phones after the script files are already stored in NVRAM

1. Copy the boot image files for the 4620 IP phone using the copy ftp phone-image command. For example:

G450-001(super)# copy ftp phone-imageC pub\4602dape_8.bin 192.168.49.10

Username: rootPassword:Beginning download operation ...This operation may take up to 20 seconds.Please refrain from any other operation during this time.For more information , use 'show download phone-image-file status' commandG450-001(super)# copy ftp phone-imageD pub\4602sape_8.bin 192.168.49.10


G450-001(super)# copy ftp phone-imageA pub\bbla20_1817.bin 192.168.49.10




2. Copy the phone application image files for the 4620 IP phone using the copy ftp phone-image command. For example:

Note:Note: Once the upgrade procedure is complete, you can delete the files using the

erase phone-image command.

Failure scenarios and repair actionsThere are various configuration related problems which will cause the upgrade to fail. The scenarios can be repaired by readjusting the downloading or configuration settings.

G450-001(super)# copy ftp phone-imageB pub\def20r1_8_1.bin 192.168.49.10


Table 9: Failure scenarios and repair actions

Problem Possible cause Action

“Free Application Memory is xxx MB. Use show application-memory for more details”

You tried to configure more memory than is available in the main bank.

Re-adjust the allocation of memory between the Sniffer cache application and the TFTP server. Be sure the Sniffer allocation is not needed for trouble shooting.

“Application Memory reached its limits. Sniffer and TFTP server application memory sizes restore to defaults”

You tried to download configuration files after configuring the total memory allocations for applications and Sniffer to more than 12 Mb in the startup configuration and performing a reset.

None. The memory allocations are set to the default values.

Cannot download file to Gateway

Refer to the specific error message you receive.

1 of 2

Upgrading considerations


Upgrading considerations● Configuration files, such as upgrade script and setting files, are copied to the phone

configuration banks in NVRAM, while phone images are stored in RAM

Note:Note: Image files are cleared if you reset the gateway.

● Phone image banks are stored in the same TFTP directory. Therefore, you cannot copy the same file name to more then one bank. Copying a file to a bank containing a file with the same file name causes the old file to be overwritten by the new one.

● File names for IP phone image files and script files are limited to 32 characters

"Not enough memory in RAM"

The remote file is larger than the available RAM.

Free more space in the RAM using the erase phone-script or erase phone-image command.

"Not enough memory in NVRAM"

The remote file is larger than the available NVRAM.

Free space in the NVRAM using the erase phone-script command.

"File already Exists in other Bank"

You tried to download the same file to more than one bank.

None. You cannot load two files with the same file name to more than one bank.

“TFTP - General failure” File name or path incorrect Check the file name and path.

“Can't start upload operation.Wrong operation parameters or other operation already in progress, please try again”

You are trying to upload a file from an empty bank.

Upload from a different bank.Download a file to the bank.

Table 9: Failure scenarios and repair actions (continued)

Problem Possible cause Action

2 of 2


Chapter 12: Backing up and restoring the G450

You can backup and restore the G450 to/from a USB mass storage device using a single CLI command for backup and a single CLI command for restore. This is especially helpful for efficient restoring or replicating of a G450 media gateway.

If the G450 is located remotely, you can backup and restore the G450 files one by one, using TFTP/FTP/SCP servers.

For information about G450 backup and restore, see chapter 5 in Administration for the Avaya G450 Media Gateway, 03-602055.

Backing up and restoring the G450



Chapter 13: Troubleshooting

You can have problems with phones, a trunk, the power, or the WAN line. It is necessary to identify the specific problem to figure out how it can be resolved. In addition, you may have to perform an NVRAM initialization if you are unable to access the CLI.

One telephone stops workingIf one telephone in the network stops working, but the other telephones and data devices continue to work normally, the problem is probably with the telephone itself. There could also be a problem with the telephone’s connection to the Avaya G450 Media Gateway, or a power management event, in which the power budget is exceeded and low priority ports are disconnected.

Identifying the problem when one phone stops working1. Replace the telephone. If the new telephone works, the problem is with the telephone

itself. If the new telephone does not work, go on to the next step.

2. Connect the telephone to a different power supply. If the telephone works, the problem is with the original power supply. If the telephone still does not work, go on to the next step.

3. Connect the telephone to a different network port. If the telephone works, the problem is with the original network port. If the telephone still does not work, go on to the next step.

4. Check the module on the Avaya G450 Media Gateway to which the telephone is connected. Check whether the physical connection is loose, and tighten the connection if necessary. If the telephone still does not work, go on to the next step.

5. Check the LEDs on the module to which the telephone connects. Make sure the LED for the port to which the telephone is connected is lit. If it is not lit, the problem may be with the port or the module. If the ALM LED is lit, this is also an indication that there is a problem with the port or the module. Note the port and module and contact your project manager. For information on the various modules and their LEDs, see Appendix A: Front panel description on page 131.

Troubleshooting


Several telephones stop workingIf some telephones in the network stop working, but others continue to work, the problem could be with a trunk or with one of the modules in the G450.

Identifying the problem when several phones stop working1. Determine whether all the telephones that are affected connect to the same switch or port.

If they do, the problem is probably with that switch or port. If they do not, go on to the next step.

2. Determine whether all the telephones that are affected connect to the same module. If they do, check the LEDs on that module. If the ALM LED is lit, there may be a problem with the module. Contact your project manager. If not, go on to the next step. For information on the various modules and their LEDs, see Appendix A: Front panel description on page 131.

3. Check the ALM LED on the Avaya G450 Media Gateway chassis. If it is lit, there may be a system-wide problem. Contact your project manager. For information on the chassis, see Appendix A: Front panel description on page 131.

No power on the G4501. Check the AC power source with a voltmeter.

2. Connect the Avaya G450 Media Gateway to a different AC power source. If the G450 has power, the problem is with the original power source. If the G450 still does not work, go on to the next step.

3. Check the ALM LED on the Avaya G450 Media Gateway chassis. If it is lit, there may be a system-wide problem. Contact your project manager. See Appendix A: Front panel description on page 131.

A trunk stops working1. Check the connection between the trunk and the Avaya G450 Media Gateway. If the

physical connection is loose, tighten the connection. If the trunk still does not work, go on to the next step.

A WAN line stops working


2. Check the ALM LED on the module to which the trunk connects. If it is lit, see Maintenance Alarms for Communication Manager 2.1, Media Gateways and Servers, 03-300190 for testing procedures.

A WAN line stops working1. Check the connection between the WAN line and the Avaya G450 Media Gateway. If the

physical connection is loose, tighten the connection. If the line still does not work, go on to the next step.

2. Check the ALM LED on the module to which the WAN line connects. If the ALM LED is lit, the problem may be the configuration of the module or a lack of T1 signal. You can try the following:

- For E1/T1 interfaces, use the show controllers command to view the status of the interface’s controller. Make sure the controller is up, and that all error counters do not increase.

- For all serial interfaces (E1/T1 and USB), use the show interfaces Serial command to verify that the interface and line protocol are both up.

- For USB interfaces only, use the show interfaces Serial command to verify that all line signals are up.

- Swap the module with another one. - Check the CON LED on the module. The CON LED indicates if you have a signal. If

the CON LED is lit, check with your provider that you are receiving a signal.

For information on the various modules and their LEDs, see Appendix A: Front panel description on page 131.

! CAUTION:CAUTION: Hot insertion of a WAN module resets the G450. Therefore, any translation and

other data that is in the running configuration but has not been saved to the startup configuration will be lost.

3. Check the ALM LED on the Avaya G450 Media Gateway chassis. If it is lit, there may be a system-wide problem.

CLI is not accessibleYou can perform an NVRAM initialization using a jumper on the G450 main board. You should only use this procedure if you are unable to access the CLI, for example if the G450 resets continuously.

Troubleshooting


VOLTAGE ALERT:VOLTAGE ALERT: Disconnect the G450 from the external power source before proceeding.

ELECTROSTATIC ALERT:ELECTROSTATIC ALERT: Do not touch any components on the printed circuit board except when installing

or removing the bridge for the jumper pins.

1. Remove the G450 main board as described in Removing and inserting the G450 main board on page 93.

2. Locate the NVRAM init jumper (jumper J5) on the front of the G450 main board. Refer to Figure 42.

Figure 42: G450 NVRAM INIT Jumper Location

3. Bridge jumper P5 (refer to Figure 42) using the bridge provided in the accessory kit.

4. Insert the G450 main board as described in Removing and inserting the G450 main board on page 93.

CLI is not accessible


5. Let the G450 operate for about 5 minutes so that it will boot and erase the current configuration.

6. Remove the G450 main board as described in Removing and inserting the G450 main board on page 93.

7. Remove the bridge.

! Important:Important: If you do not remove the bridge, the G450 will continue to initialize the NVRAM

when it resets or is powered up.

8. Insert the G450 main board as described in Removing and inserting the G450 main board on page 93.

Troubleshooting



Appendix A: Front panel description

You can use the front panel of the Avaya G450 Media Gateway to:

● Connect devices

● Add media modules

● View LEDs

● Reset the device

● Reset and recover from the alternate bank

The front panel of the Avaya G450 Media Gateway chassis without media modules

Figure 43: The G450 front panel ports and slots

Media module slotsThe G450 has eight standard media module slots (V1 through V8).

For information about the different media modules that can be housed in the media module slots, see Combination limitations on page 35 and Allocating slots on page 35.

Front panel description


System LEDs

USB portsUSB are standard USB ports, USB 1.1 and 2.0 compatible. The USB ports support the connection of:

● USB flash drive

● The Multitech MultiModemUSB MT5634ZBA-USB-V92 USB modem

Console port (CON)The Console port is a standard RJ-45 network port. Use the Console port to connect a console device or modem to the G450.

Services port (SERVICES)The Services port is a standard RJ-45 network port. Use the Services port to connect a laptop through a 10/100 Mbps Ethernet port to the G450 for configuration purposes.

Table 10: System LEDs

LED Name Color Indication

MDM Modem Detected Green A modem is connected to the CONSOLE or USB port

ALM Alarm Red An alarm is present in the system

CPU CPU Green OFF — A test is in progressON — Normal operation

PWR Power Green OFF — No powerBLINKING — Problem with powerON — Normal operation

The front panel of the Avaya G450 Media Gateway chassis without media modules


Emergency Transfer Relay port (ETR)The ETR port is a standard RJ-45 network port. Use the ETR port to connect to up to two 808A Emergency Transfer Panels. These panels provide basic telephone services in the event of system failure.

For more information on Emergency Transfer Relay, see Step 6: Installing an 808A Emergency Transfer Panel and associated telephones on page 60.

For information on installing the 808A Emergency Transfer Panel, see 808A Emergency Transfer Panel Installation Instructions, which ships with the Emergency Transfer Panel.

Contact Closure port (CCA)The Contact Closure port (CCA) is wired as an RJ-14 port, but uses an RJ-45 network jack. This port is used to support the G450’s Contact Closure feature. The Contact Closure feature is a controllable relay providing dry contacts for various applications.

The adjunct box provides two contact closures that can be operated in either a normally closed or normally open state. The contact closures can control devices such as devices that automatically lock or unlock doors or voice recording units. The CCA port can be configured so that the connected devices can be controlled by an end device, such as a telephone. For example, a user can unlock a door by keying a sequence into a telephone keypad. For more information on Contact Closure, see Step 5: Installing the Avaya Partner Contact Closure Adjunct on page 59.

Implement the Contact Closure feature

Connect an Avaya Partner System Contact Closure Adjunct™ box to the CCA port.

Router ports (ETH WAN)Each ETH WAN port is a standard RJ-45 network port. Use ETH WAN to connect a data device to the internal router through a 10/100 Mbps Ethernet port. The G450 serves as a router for the WAN.

Switch ports (ETH LAN)Each ETH LAN port is a standard RJ-45 network port. Use ETH LAN to connect a data device to the switch through a 10/100 Mbps Ethernet port. You can connect an external LAN to ETH LAN.



Reset (RST) and Alternate Software Bank (ASB) buttonsRST is the reset button. ASB is the Alternate Software Bank button.

The Avaya G450 Media Gateway has two firmware banks:

● Bank A

● Bank B

Each firmware bank contains a version of the G450 firmware. These may be different versions. The purpose of this feature is to provide software redundancy. If one of the versions becomes corrupted, you can reset the G450 using the other version. This is particularly important when uploading new versions.

By default, when you turn on or reset the G450, the G450 loads firmware from Bank B. This default setting can be changed by the system administrator.

For example, if the G450 is configured to load firmware from Bank B, you can reset the G450 to load the firmware from Bank A instead.

Load firmware from a bank other than the default bank during startup

1. Press and hold the reset button.

2. Press and hold the ASB button.

3. Release the reset button.

4. Release the ASB button.

The front panel of the Avaya S8300 ServerThe S8300 Server is a Pentium-based processor that runs on a Linux operating system. The S8300 runs Avaya Communication Manager (ACM) to provide call control services to the G450 and other Avaya gateway devices.

The front panel of the S8300 includes:

● 10/100BaseT Fast Ethernet port (SERVICES)

● Two USB ports for modem connections or the USB CD-ROM drive (USB 1 and USB 2)

The front panel of the Avaya S8300 Server


Figure 44: The S8300 Server

S8300 Server portsThe S8300’s 10/100BaseT Fast Ethernet port is labeled SERVICES, and is located in the center of the front panel. The S8300’s two USB ports are labeled USB 1 and USB 2. They are located towards the right of the front panel.

S8300 Server port LEDs

In addition, the front panel of the S8300 has a LED labeled OK TO REMOVE, which is connected to a button labeled SHUT DOWN. This LED indicates that the S8300 has been shut down, and can be removed from the G450 chassis. Do not attempt to remove the S8300 without instructions from a specially trained technician.

Table 11: S8300 LEDs


ALM Alarm Red An alarm is present

TST Test Green Avaya Communication Manager is running. When an S8300B is installed as an LSP, the green light shows that the server is up and waiting to provide service.

ACT Activity Yellow This LED is lit whenever a G450, a G700, an IP telephone, or an IP console is registered with the S8300. It is off when none of these IP endpoints are registered with the S8300.



The front panel of the Avaya MM340 media moduleThe MM340 media module provides one WAN access port for the connection of an E1 or T1 WAN line.

Figure 45: The MM340 media module front panel

MM340 portsThe MM340’s E1/T1 WAN access port is marked E1/T1. This port is located in the center of the front panel.

MM340 LEDs

Table 12: MM340 LEDs


ALM Alarm Red The module type is not the type configured in the MSG for the slot

TST Test Green A port is being initialized or a loopback is present

ACT Activity Yellow At least one PPP/Frame Relay session is active

SIG Signal Green The physical connection is up.

The front panel of the Avaya MM342 media module


The front panel of the Avaya MM342 media moduleThe MM342 media module provides one USP WAN access port and supports the following WAN interface types:

● V.35/ RS449

● X.21


MM342 portsThe MM342 contains one WAN SCSI access port.

MM342 LEDs




TST Test Green A port is being initialized or a loopback is present

ACT Activity Yellow At least one PPP/Frame Relay session is active

CON Connection Green The physical connection is up



The front panel of the Avaya MM710 media moduleThe MM710 T1/E1 media module terminates a T1 or E1 trunk. The MM710 has a built-in Channel Service Unit (CSU), so an external CSU is not necessary. The CSU is only used for the T1 circuit.

Note:Note: For drop and insert, an external CSU is required.


Note:Note: The six ports in the middle of the front panel are used for testing.

MM710 portsThe MM710 contains an E1/T1 port.

MM710 LEDs




TST Test Green Either a test is being performed on the module via the server, or the module is performing a self-test upon initial insertion

1 of 2



The front panel of the Avaya MM711 media moduleThe MM711 media module provides analog line, trunk and telephone features and functionality. The MM711 front panel includes eight universal analog ports. These ports can be used for analog telephone or fax machines, or for analog trunks.


MM711 portsThe MM711’s eight universal analog ports are labeled 1 through 8.

ACT Activity Yellow An E1/T1 trunk device connected to the module is in use.The light is always on if the trunk is an ISDN E1 or T1 PRI trunk, and the MM710 is not configured as the synchronization source of the G450.The light flashes at a rate of 2.8 seconds on and 0.2 seconds off if the MM710 synchronization source is configured to synchronize the G450 and the module is receiving a T1 source signal.The light flashes at a rate of 0.2 seconds on and 2.8 seconds off if the MM710 synchronization source is configured to synchronize the G450 and the T1 source is lost.

SIG Signal Green The physical connection is up.

Table 14: MM710 LEDs (continued)


2 of 2



MM711 LEDs

The front panel of the Avaya MM712 media moduleThe MM712 DCP media module includes eight DCP telephone ports. The ports support two-wire DCP telephones.


MM712 portsThe MM712’s eight DCP telephone ports are labeled 1 through 8.





ACT Activity Yellow A device connected to the module is in use. This can include a telephone that is off the hook.



MM712 LEDs

The front panel of the Avaya MM714 media moduleThe MM714 analog media module includes four analog telephone ports and four analog trunk ports.

Note:Note: The four analog trunk ports can not be used for analog DID trunks. Instead, the

four analog line ports must be used.


MM714 portsThe MM714’s four analog telephone ports are labeled 1 through 4. These ports can also be used for DID trunks.

The MM714’s four analog trunk ports are labeled 5 through 8.








MM714 LEDs

The front panel of the Avaya MM716 media moduleThe MM716 media module front panel has a 25-pair amphenol connector supporting 24 analog line ports. These ports can be configured as DID trunks with either wink start or immediate start.

The MM716 is compatible with Avaya CM version 2.0 and higher, and G450 firmware version 25.0.0 and higher.









MM716 portsThe MM716 contains a single 25-pair amphenol connector, which can be connected by an amphenol cable to a breakout box or punch down block containing RJ-45 or RJ-11 jacks, as needed. You can attach up to 24 devices (analog telephones, trunks, modems, or fax machines) to these jacks.

Table 18: 25-pair amphenol connector pinout

Station port Cable pair

1 White Blue

2 White Orange

3 White Green

4 White Brown

5 White Slate

6 Red Blue

7 Red Orange

8 Red Green

9 Red Brown

10 Red Slate

11 Black Blue

12 Black Orange

13 Black Green

14 Black Brown

15 Black Slate

16 Yellow Blue

17 Yellow Orange

18 Yellow Green

19 Yellow Brown

20 Yellow Slate

1 of 2



MM716 LEDs

The front panel of the Avaya MM717 media moduleThe MM717 high density DCP media module front panel has a 25-pair amphenol connector supporting 24 Digital Communications Protocol (DCP) ports. To use the MM717 media module, connect an amphenol cable to the port and to either a breakout box or a punch down block containing RJ-45 or RJ-11 jacks, as needed. You can attach up to 24 two-wire DCP telephones to these jacks. The MM717 does not support four-wire DCP telephones.

21 Violet Blue

22 Violet Orange

23 Violet Green

24 Violet Brown

OPEN Violet Slate

Table 18: 25-pair amphenol connector pinout (continued)


2 of 2









MM717 portsThe MM717 contains a single 25-pair amphenol connector, which can be connected by an amphenol cable to a breakout box or punch down block containing RJ-45 or RJ-11 jacks, as needed.

Table 20: 25-pair amphenol connector pinout


1 White Blue

2 White Orange

3 White Green

4 White Brown

5 White Slate

6 Red Blue

7 Red Orange

8 Red Green

9 Red Brown

10 Red Slate

11 Black Blue

12 Black Orange

13 Black Green

14 Black Brown

15 Black Slate

16 Yellow Blue

1 of 2



MM717 LEDs

17 Yellow Orange

18 Yellow Green

19 Yellow Brown

20 Yellow Slate

21 Violet Blue

22 Violet Orange

23 Violet Green

24 Violet Brown

OPEN Violet Slate

Table 20: 25-pair amphenol connector pinout (continued)


2 of 2





ACT Activity Yellow A device connected to the module is in use



The front panel of the Avaya MM720 media moduleThe MM720 ISDN BRI media module contains eight 4-wire S/T ISDN BRI ports. These ports interface to the central office at the ISDN T reference point.


MM720 portsThe MM720’s eight ISDN BRI ports are labeled 1 through 8.

MM720 LEDs





ACT Activity Yellow A trunk connected to the module is in use. In CM 3.0 or higher, the LED could alternatively indicate that a telephone connected to the module is in use.



The front panel of the Avaya MM722 media moduleThe MM722 ISDN BRI media module provides two 4-wire S/T ISDN BRI (Basic Rate Interface) 2B+D access ports with RJ-45 jacks.


MM722 portsThe MM722 contains two ISDN BRI ports.

MM722 LEDs





ACT Activity Yellow A trunk connected to the module is in use. In CM 3.0 or higher, the LED could alternatively indicate that a telephone connected to the module is in use.


Appendix B: Technical specifications

This appendix provides technical specifications for the G450 and for compatible power cords.

G450 Media Gateway specificationsTable 24 provides detailed information on the physical dimensions and tolerances of the G450 Media Gateway.

Table 24: G450 Media Gateway specifications

Description Value

Height 5.25 in (133.3 mm)

Width 19 in (482.6 mm)

Depth 18 in (456 mm)

Weight of empty chassis 7.4 kg (16.5 pounds)with blank plates - 9.5 kg (21 pounds)

Weight of chassis with basic configuration, including main board, power supply unit, fan tray, one DSP, and blank panels on the media module slots

14 Kg (31 pounds)

Ambient working temperature 0-40°C

Operation altitude up to 10000 ft (3048 m)

Front clearance 12 in (30 cm)

Rear clearance 18 in (45 cm)

Relative humidity 10-90%, non-condensing

BTU 1,780 BTU/h

Max current 6 A

Technical specifications


Power cord specificationsFollowing are specifications for power cords suitable for use with the G450.

For North America: The cordset must be UL Listed/CSA Certified, 16 AWG, 3-conductor (3rd wire ground), type SJT. One end is to be terminated to an IEC 60320, sheet C13 type connector rated 10A, 250V. The other end is to be terminated to either a NEMA 5-15P attachment plug for nominal 125V applications or a NEMA 6-15P attachment plug for nominal 250V applications.

For Outside North America: The cord must be VDE Certified or Harmonized (HAR), rated 250V, 3-conductor (3rd wire ground), 1.0 mm2 minimum conductor size. The cord is to be terminated at one end to a VDE Certified/CE Marked IEC 60320, sheet C13 type connector rated 10A, 250V and the other end to a 3-conductor grounding type attachment plug rated at a minimum of 10A, 250V and a configuration specific for the region/country in which it will be used. The attachment plug must bear the safety agency certifications mark(s) for the region/country of installation.


Appendix C: Running the Avaya Installation Wizard (Avaya IW)

The Avaya IW is a web-based installation wizard that is used with the Avaya G450 Media Gateway to perform initial configuration tasks and to upgrade software and firmware. The Avaya IW is designed for use with systems that contain an S8300 Server, operating in either ICC or LSP mode. You can use Avaya IW to configure the Avaya G450 Media Gateway or to upgrade an installed S8300 with new Avaya Communication Manager (CM) software and/or G450 firmware. If you have an EPW (see Obtaining the Electronic Preinstallation Worksheet (EPW) on page 24), you will be able to upload configuration parameters from the EPW to AIW as part of your AIW session.

Accessing Avaya IW1. Connect a laptop computer to the Services port of the S8300, using a crossover cable.

2. Make sure the laptop is configured as follows:

● IP Address: 192.11.13.5

● NetMask: 255.255.255.252

● Disable DNS

● Clear the primary WINS and secondary WINS IP Addresses

● Disable the Proxy Server in the Internet Explorer

3. Launch Internet Explorer on the laptop and type the following URL to access the S8300 Server Home Page: http://192.11.13.6.

The welcome screen for Avaya Integrated Management appears.

4. Click Continue. The Logon screen for Integrated Management appears.

5. Enter the appropriate login name and password.

6. Ask a customer representative for a login name and password that the customer would like for the superuser login. If you are a business partner, you can also repeat this procedure to add the dadmin login.

Note:Note: Make sure the customer can change this login, its password, or its permissions

later.

Running the Avaya Installation Wizard (Avaya IW)


7. From the Integrated Management main menu, select Launch Maintenance Web Interface.

8. From the navigation menu of the Maintenance Web Pages, select Security > Administrator Accounts.

The Administrator Accounts screen appears.

9. Select Add Login.

10. Select Privileged Administrator and click Submit. The Administrator Logins -- Add Login: Privileged Administrator screen appears.

11. Type a login name for the account in the Login name field.

12. Verify the following:

● susers appears in the Primary group field.

● prof18 appears in the Additional groups (profile) field. prof18 is the code for the customer superuser.

● /bin/bash appears in the Linux shell field.

● /var/home/login name appears in the Home directory field, where login name is the name you entered in step 11.

13. Skip the fields Lock this account and Date on which account is disabled-blank to ignore.

14. For the Select type of authentication option, select password.

Note:Note: Do not lock the account or set the password to be disabled.

15. Enter the password in the Enter password or key field and the Re-enter password or key field.

16. In the section Force password/key change on next login select no.

17. Click Submit.The system informs you the login is added successfully.

18. Select the Launch Installation Wizard link from the home page.

The Overview screen appears:

Preliminary screens


Figure 55: The Overview screen

Preliminary screens1. Access the Avaya IW. The first screen that appears is the Overview screen.



Figure 56: The Overview screen

2. Click Continue. The Avaya IW performs system auto-discovery and displays the results on the following screen:

Preliminary screens


Figure 57: The Auto Discovery Results screen

3. Click Continue. The Electronic Preinstallation Worksheet screen appears. This screen allows you to import system data from the Electronic Preinstallation Worksheet (EPW). If you import an EPW, some of the fields on the subsequent screens will be filled automatically. For information about obtaining the EPW, see Obtaining the Electronic Preinstallation Worksheet (EPW) on page 24.



Figure 58: The Electronic Preinstallation Worksheet screen

MGC configuration and upgrade options● Install this media server as a Main Server. This option configures the installed S8300

Server as the primary Media Gateway Controller (MGC). The primary MGC is the MGC that the G450 searches for first to provide call processing services to the G450.

● Install this media server as an LSP. This option configures the installed S8300 Server as a backup MGC (LSP) and to configure an external server as the primary MGC. In this case, the installed S8300 will provide backup call processing services to the G450 in case of connection failure to the primary MGC.

● Upgrade a previously installed media server with new software and/or media gateway firmware. This option upgrades an installed server with new Avaya Communication Manager software and/or Media Gateway firmware.

Configuring and upgrading the server1. Click Continue from the Electronic Preinstallation Worksheet screen. The Usage Options

screen appears.

MGC configuration and upgrade options


Figure 59: The Usage Options screen

2. Specify which configuration processes you would like to initiate:

● Install this media server as a Main Server● Install this media server as an LSP

● Upgrade a previously installed media server with new software and/or media gateway firmware

3. Click Continue. If you are configuring a new MGC, the Confirm New Installation screen appears, as shown below. If you are upgrading an existing MGC, the Avaya Communication Manager Software screen appears. See Upgrading an existing MGC on page 160.



Figure 60: The Confirm New Installation screen

4. Click Continue. The Checklist screen appears displaying a list of required and optional items you need to configure the G450. For details, see Chapter 1: Before you install on page 19.

Figure 61: The Checklist screen

MGC configuration and upgrade options


5. Click Continue. The NVRAM INIT screen appears. Restore all factory default settings if necessary by clicking NVRAM INIT and selecting OK in the confirmation box.

Figure 62: The NVRAM INIT screen

6. Click Continue. The Date/Time screen appears. Reset the G450’s date and time if necessary.

Figure 63: The Date/Time screen



7. Click Continue. The Product ID screen appears. If you are configuring a new G450, enter the product ID in the ID field and select Assign a new Product ID.

Figure 64: The Product ID screen

Upgrading an existing MGC1. Click Continue from the Product ID screen. The Avaya Communication Manager Software

Upgrade screen appears.

This screen enables you to upgrade the Communication Manager software on the S8300 installed in the G450.

Upgrading an existing MGC


Figure 65: The Avaya Communication Manager Software Upgrade screen

2. If you want to enable/disable the SES Co-Res server, move on to step 4. If you want to upload a new release of Avaya Communication Manager software, click Upload New Release.



Figure 66: The Avaya Communication Manager Upload Source screen

3. Select the source from which the Avaya Communication Manager release will be uploaded.

4. Click Continue. The SES Co-Res screen appears.

This screen allows you to enable or disable a SES Co-Res server.



Figure 67: The SES Co-Res screen

5. Click Continue. The Software Update screen appears.

This screen allows you to unpack Avaya Communication Manager updates.



Figure 68: The Software Update screen

6. If you want to unpack an Avaya Communication Manager update, check Unpack Update and browse to locate the update file on the laptop.

7. Click Continue. The Phone Message Files screen appears. Use this screen to install standard and custom phone message files that provide messages for display sets that are in the desired language format.



Figure 69: The Phone Message Files screen

8. Click Continue. The Media Server - IP Addresses screen appears. If your S8300 Server is already configured, the Avaya IW should detect and display its address information in this screen. If not, you must enter the required information.



Figure 70: The Media Server - IP Addresses screen

Configuring the primary controller IP addresses1. Click Continue from the Media Server - IP Addresses screen. If you selected the Install

this media server as an LSP option in the Usage Options screen, the LSP Controller screen appears. The IP addresses required vary depending on the type of primary controller. Enter the required IP address(es) for the primary controller.

Configuring the primary controller IP addresses


Figure 71: The LSP Controller screen

2. Click Continue. From the Optional Services screen, select the services you want.

Figure 72: The Optional Services screen



3. Click Continue. If you selected Uninterruptible Power Supply (UPS) in the Optional Services screen, the Uninterruptible Power Supply (UPS) screen appears. Enter the required information.

Figure 73: The Uninterruptible Power Supply (UPS) screen

4. Click Continue. If you selected Domain Name Service (DNS) in the Optional Services screen, the Domain Name Server (DNS) screen appears. Enter the required information.



Figure 74: The Domain Name Server (DNS) screen

5. Click Continue. If you selected Network Time Protocol (NTP) in the Optional Services screen, the Network Time Protocol (NTP) screen appears. Select an NTP option.

Figure 75: The Network Time Protocol (NTP) screen



6. Click Continue. If you selected Remote Access/INADS Support in the Optional Services screen, the INADS screen appears. Enter a dialup IP address for Installation and Administration System (INADS) remote support. For instructions on how to obtain the INADS IP address, see Running the Automatic Registration Tool (ART) for the RAS IP address on page 22.

Figure 76: The INADS screen

7. Click Continue. The Translation Source screen appears. Use the screen to generate Avaya Communication Manager translation information, including translations for administration of extension ranges, trunk types, routes, class of service, feature access codes, trunk access codes, station button assignment, and several other parameters.



Figure 77: The Translation Source screen

8. Click Continue. The Security Files screen appears if there is a resident server on the gateway. This screen displays the installed status of the license file and enables you to install or replace the file from the laptop or LAN source. Without a valid license file, you cannot access the Avaya Communication Manager. For information on this file, see Downloading CM license and authentication files to your laptop on page 21.

Note:Note: If you selected Use this wizard to create basic translations in the Translation

Source screen (Figure 77), the Security Files screen displays also the installed status of the CM’s authentication file and enables you to install or replace the authentication file from the laptop or LAN source.



Figure 78: The Security Files screen

Gateway configuration


Gateway configuration1. Click Continue from the Security Files screen. The IP Addresses screen appears.

This screen displays the G450’s ID, as well as the type of media module residing in each slot of the G450’s chassis.

Figure 79: The IP Addresses screen

2. Click the wrench icon corresponding to the G450 in the Action column.

The PMI configuration screen appears. The IP address and subnet mask of the PMI should appear in this screen. Change this IP address and subnet mask in accordance with your system specifications.

The Primary Management Interface (PMI) address is the interface used for the following management functions:

- Registration of the G450 to an MGC- Sending SNMP traps- Opening telnet sessions from the G450- Sending messages from the G450 using FTP and TFTP protocol

Note:Note: You can assign any IP interface that the MGC recognizes to be the PMI.



Figure 80: PMI Configuration screen

3. Click Continue. The SNMP V1 Community Strings screen appears. In the Read Only Community String field, specify a name for the SNMP read community access name to assign to the G450. In the Read Write Community String field, specify a name for the SNMP write community access name to assign to the G450. Re-enter the strings in the Re-enter Community String fields for confirmation. For information about SNMP, see Administration for the Avaya G450 Media Gateway, 03-602055.

Gateway configuration


Figure 81: The SNMP V1 Community Strings screen

4. Click Continue. The SNMP V3 screen appears.

Figure 82: The SNMP V3 screen



5. Complete all fields if you want to configure an SNMP V3 user. Otherwise, leave all fields blank.

6. Click Continue. The Media Gateway Controller Information screen appears.

Configure the list of Media Gateway Controllers (MGCs) that will provide call processing services for the G450. You must specify a primary MGC in the first IP address box. You can specify up to three backup MGCs in the optional IP address boxes, in priority order. Specify your primary MGC in accordance with the usage option you chose (see step 1). If you do not configure the S8300 installed in the G450 as the primary MGC, configure the S8300 as a backup MGC.

Note:Note: The G450 searches for the primary MGC first. If it cannot connect to the primary

MGC, it searches for a backup MGC. An MGC may be the Avaya S8300 Server installed in the G450 or an external Avaya S8500 Server or Avaya S8700-series Server, or an Avaya S8300 Server installed in an external media gateway.

Note:Note: To register an S8500 or S8700-series Server as the MGC, use the IP address of

the server’s Control-LAN card (CLAN) rather than the IP address of the server itself.

Figure 83: The Media Gateway Controller Information screen

Firmware configuration


Firmware configuration1. To upgrade the G450 firmware, click Continue from the Media Gateway Controller

Information screen.

The Firmware screen appears. This screen displays the currently installed firmware versions on the G450 and its media modules, as well as the most recent available versions.

● To upgrade firmware, select the modules you want to upgrade and click Continue● To upload a new firmware version from a laptop, click Upload New Firmware. The

Firmware File Upload screen appears.

● To proceed without upgrading any firmware, clear all the boxes in the Select column and click Continue

Figure 84: The Firmware screen

2. The Firmware File Upload screen allows you to upload a new firmware file from a laptop. Enter the file path of the file you want to upload, or use the Browse button to locate the file.



Figure 85: The Firmware File Upload screen

3. Click Continue. The file is uploaded and the Firmware screen returns. Clear all the checkboxes in the Select column.

4. Click Continue. The Change Master Key - Optional screen appears. The master key is used to encrypt gateway secrets (passwords, etc.) in the gateway configuration file.



Figure 86: The Change Master Key - Optional screen

5. If you want to change the master key, enter the new master key passphrase and then confirm by entering it again. A new master key is generated from the passphrase.

6. Click Continue. The Gateway License screen appears.



Figure 87: The Gateway License screen

7. If you will need to use the VPN feature on the G450, check Install Gateway License file and fill in the remaining fields to install the gateway license file. For information on the Gateway license file, see Downloading a G450 license file to your laptop on page 21.

8. Click Continue. The Gateway Authentication screen appears.



Figure 88: The Gateway Authentication screen

9. If you have a service contract, the G450 is shipped with an authentication file. This authentication file is required for Avaya services personnel to allow them secure remote access to the gateway. Click Continue. The Field Replaceable Unit (FRU) Status screen appears. View the status of the Field Replaceable Units detected in the G450.



Figure 89: The FRU Status screen

10. Click Continue. The TFTP Server screen appears.

Figure 90: The TFTP Server screen



11. If you want to upload configuration and firmware files for IP phones to the G450 TFTP Server, do the following:

a. In the Server IP Address field, enter the IP address of the machine hosting the files that are to be uploaded.

b. Select the file transfer protocol (TFTP, FTP, or SCP) you want to use to upload the files from the host machine. TFTP is selected by default.

c. The use of the SCP protocol is limited to copying files of 1 MB or less. Therefore, an SCP server can be used for copying the script files, which do not exceed 128 KB, but cannot be used for copying image files.

d. If you selected FTP or SCP, enter the username and password in the Username and Password fields, and re-enter the password for confirmation in the Re-enter Password field.

12. In the Select column, check any files you wish to upload. If you selected SCP as your upload protocol, the checkboxes for the phone images are disabled. If a green circled checkmark is displayed in the Uploaded column, the file has already been uploaded.

Modem configuration1. To configure the G450 for modem use, click Continue on the TFTP Server screen.

The G450 Modem Type Selection screen appears. Select the modem type you want to use. For more information on using a modem with the G450, see Chapter 4: Connecting and enabling a modem for remote access on page 63.



Figure 91: The G450 Modem Type Selection screen

2. Click Continue. If you selected Serial Modem, the G450 Serial Modem Configuration screen appears. If you selected USB Modem, the G450 USB Modem Configuration screen appears. If you selected None, the Country screen appears. See Telephony configuration on page 186.

3. If you selected Serial Modem, enter the required information in the G450 Serial Modem Configuration screen, then click Continue.



Figure 92: The G450 Serial Modem Configuration screen

4. If you selected USB Modem, enter the required information in the G450 USB Modem Configuration screen, then click Continue.



Figure 93: The G450 USB Modem Configuration screen

Telephony configurationIf you selected the option to use this wizard to create basic translations in the Translation Source screen (see step 7), the Telephony, Trunking, and Endpoints sections appear in the wizard. If you did not select the option to use this wizard to create basic translations in the Translation Source screen, skip to Alarm configuration on page 198.

1. To configure the G450’s telephony parameters, click Continue in the applicable modem configuration screen. The Country screen appears. Select the country in which the installation is taking place.



Figure 94: The Country screen

2. Click Continue. The Import Custom Template screen appears. This screen allows you to configure telephony translation defaults for the Avaya IW.

Figure 95: The Import Custom Template screen



3. Click Continue. The Call Routing screen appears. Enter the required call routing information.

Figure 96: The Call Routing screen



4. Click Continue. The Extension Ranges screen appears. To add a range, click Add Extension Range and enter the starting and ending extensions for the range. If you want this range to be used to route calls over an IP trunk, select Private Networking. To add additional extension ranges, repeat these steps. When you are finished, click Continue.

Figure 97: The Extension Ranges screen



5. Click Continue. The Import Name/Number List screen appears. This screen allows you to import an Excel file that contains user names, extension numbers, and other information. To import this file:

a. Select Import the following name and number list.b. Enter the file path of the file you want to import, or use the Browse button to locate the

file.

c. Click Continue.

Figure 98: The Import Name/Number List screen

Trunk configurationThe Trunking section appears in the wizard only if you selected the option to use this wizard to create basic translations in the Translation Source screen (see step 7). If you did not select the option to use this wizard to create basic translations in the Translation Source screen, skip to Alarm configuration on page 198.

1. To configure the G450’s trunk parameters, click Continue from the Import Name/Number List screen. The Cross-Connects screen appears. If your trunk cross-connects have been completed, click Continue to proceed with trunk configuration. If your trunk cross-connects have not been completed, it is strongly recommended to exit the Avaya IW and complete all cross-connects before proceeding with trunk configuration.



Figure 99: The Cross-Connects screen

2. Click Continue. The IP Trunk List screen appears. This screen displays all IP trunks configured on the G450. To refresh this list, click Refresh.

Figure 100: The IP Trunk List screen



3. From the IP Trunk List screen you can perform actions including: adding a trunk, modifying trunk parameters, modifying IP route configuration, displaying trunk status, and removing a trunk.

To proceed to the CO Trunk List screen for configuring a trunk media module, click Continue.

Adding a trunk

1. To add a new trunk click Add IP Trunk from the IP Trunk List screen. The IP Trunk Configuration (new) screen appears.

Figure 101: The IP Trunk Configuration (new) screen

2. Enter the required information in the IP Trunk Configuration (new) screen and click Continue. The IP Trunk List appears, with the new trunk included in the list of trunks. To add an additional trunk, click Add IP Trunk and repeat this step. When you are finished adding trunks, click Continue or select an action from the Actions column to modify an existing trunk.



Modifying trunk parameters

1. To modify the trunk’s parameters, click the configuration icon in the Actions column of the IP Trunk List screen.

Figure 102: The configuration icon in the Actions column

The IP Trunk Configuration (<trunk name>) screen appears, with the trunk’s current parameters displayed.

Figure 103: The IP Trunk Configuration screen (with current parameters)

2. Modify the trunk parameters and click Continue. The IP Trunk List appears. Select an additional action from the Actions column, or click Continue to proceed to the CO Trunk List screen. See The CO Trunk List screen on page 197.



Modifying IP route configuration

1. To modify the trunk’s IP route configuration, click the IP route icon in the Actions column of the IP Trunk List screen.

Figure 104: The IP route icon in the Actions column

The IP Route Configuration screen appears.

Figure 105: The IP Route Configuration screen (with extension ranges)

2. The IP Route Configuration screen displays the extension ranges available for private-network routing. Modify these ranges, if any, and click Continue. The IP Trunk List appears. Select an additional action from the Actions column, or click Continue to proceed to the CO Trunk List screen. See The CO Trunk List screen on page 197.



Displaying trunk status

1. To display the trunk’s operational status, click the trunk status icon in the Actions column of the IP Trunk List screen.

Figure 106: The trunk status icon in the Actions column

The IP Trunk Status screen appears.

Figure 107: The IP Trunk Status screen (with the operational status)

2. The IP Trunk Status screen displays the operational status of the trunk. To refresh the information, click Refresh. Otherwise, click Continue. The IP Trunk List appears. Select an additional action from the Actions column, or click Continue to proceed to the CO Trunk List screen. See The CO Trunk List screen on page 197.



Removing a trunk

1. To remove a trunk, click the trunk’s remove icon in the Actions column of the IP Trunk List screen.

Figure 108: The remove trunk icon in the Action column

A message appears asking if you want to remove the trunk.

Figure 109: Message to remove trunk

2. Click OK to remove the trunk. Select an additional action from the Actions column, or click Continue to proceed to the CO Trunk List screen.



Configuring a trunk media module

1. To configure a trunk media module, click Continue from the IP Trunk List screen. The CO Trunk List screen appears. Use this screen which lists trunk media modules detected in the G450 to configure a media module and run diagnostics. To configure or run diagnostics on a trunk media module, click the Actions icon for the module.

Figure 110: The CO Trunk List screen

2. Select an additional action from the Actions column, or click Continue to proceed to the CO Trunk List screen.

Endpoint installation The Endpoint section appears in the wizard only if you selected the option to use this wizard to create basic translations in the Translation Source screen (see step 7). If you did not select the option to use this wizard to create basic translations in the Translation Source screen, skip to Alarm configuration on page 198.

For instructions on endpoint installation, click Continue from the CO Trunk List screen. The Endpoint Installation screen appears. You can access endpoint installation information from this screen.



Figure 111: The Endpoint Installation screen

Alarm configuration1. To display modem status and configure alarms, click Continue from the Endpoint

Installation screen if you selected the option to create basic translations in the Translation Source screen, or the USB modem screen otherwise. The Modem Status & Configuration screen appears. Perform the following actions from this screen:

● Click Reset to reset the modem

● Click Refresh to re-detect and test the modem

● Select the appropriate modem access policy in the Modem Access area and click Continue



Figure 112: The Modem Status & Configuration screen



2. Click Continue. The OSS Configuration screen appears. Enter the required information from the ART tool. For information on using the ART tool, see Running the Automatic Registration Tool (ART) for the RAS IP address on page 22.

Figure 113: The OSS Configuration screen



3. Click Continue. The SNMP Configuration screen appears. Check Enable SNMP Alarming if you want to enable the sending of SNMP traps to the INADS. Check the Alarm Abbreviation checkbox if you want to enable SNMP alarm abbreviation. Click Add Trap Destination to add an SNMP trap destination IP address. You can add multiple destinations. For each destination, enter the INADS IP address in the Destination IP Address field. In the Community Name field, enter an SNMP community access string. Check the Enable checkbox to enable each trap destination.

Figure 114: The SNMP Configuration screen



Password and final screens1. To change your password (optional) and complete the installation, click Continue from the

SNMP Configuration screen.

The Change Root Password screen appears. This screen allows you to change the root password on the G450.

Figure 115: The Change Root Password screen

2. Click Continue. The Authentication File screen appears if there is a resident server on the gateway and if you selected Translations will be added after the installation has been completed using the SAT, ProVision, ASA or another Integrated Management tool in the Translation Source screen (Figure 77).

The Authentication File screen displays the installed status of the authentication file and enables you to install or replace the file from the laptop or LAN source. Without a valid authentication file, you cannot access the Avaya Communication Manager. If the screen displays Not Installed, you must install the file now. To install a new authentication file:

a. Check Install New Authentication file.

b. Enter the full path of the authentication file in the File Path field.



Figure 116: The Authentication File screen



3. Click Continue. The Finish Up screen appears. This screen allows you to save the installation log file to your laptop. To save the installation log file:

a. Click Save Log File. A dialog box appears.

b. Click Save.

! WARNING:WARNING: Do not click Open. Clicking Open will damage the log file and may cause other

problems to the Avaya IW.

c. Press <F5> to restore the Back and Continue buttons to the Finish Up screen.

Figure 117: The Finish Up Screen

4. Click Continue. If you have not installed an allocation license file, a warning appears reminding you to install this file.



5. Click Continue. The Verify Gateway Installation screen appears. This screen displays a list of CLI commands that you can use to verify the G450 configuration. The following figure shows a portion of the Verify Gateway Installation screen.

Figure 118: Verify Gateway Installation screen



6. Click Continue. The Launch Device Manager screen appears. This screen allows you to launch the Gateway Device Manager, an application that allows you to configure the WAN Router and perform other advanced configuration tasks.

Figure 119: The Launch Device Manager screen



7. Click Continue. The Congratulations! screen appears to inform you that the installation is complete. To exit the Avaya IW, click Finish.

Figure 120: The Congratulations! screen

The Exit AIW screen appears.

Figure 121: The Exit AIW screen


Appendix D: Running the Gateway Installation Wizard (GIW)

If you did not install an S8300 in the G450, you can use the Gateway Installation Wizard (GIW) to perform the configurations required to complete the installation. GIW prompts you for all the configurations required to complete the installation. If you have an EPW (see Obtaining the Electronic Preinstallation Worksheet (EPW) on page 24), you will be able to upload configuration parameters from the EPW to GIW as part of your GIW session.

GIW includes the option to enable a modem connected to the S8300. This appendix describes how to run GIW, and how to connect and test a modem if you choose to enable the modem.

Running the Gateway Installation Wizard (GIW)Running the GIW performs a basic configuration of the G450. The configuration can include:

● Configuring the Primary Management Interface (PMI)

● Setting SNMP communities and trap destinations

● Upgrading firmware

● Enabling a modem on the G450

Performing a basic configuration of the G4501. Prepare a PC with a CD-ROM drive and a TFTP server on the network. This may be

needed for installing software and firmware upgrades.




CD or downloaded from the Web. For information about downloading firmware upgrades from the Web to the TFTP server, see Downloading G450 firmware files to a local TFTP server on page 108.

Running the Gateway Installation Wizard (GIW)


2. Download GIW (Gateway Installation Wizard) from the Avaya Support website (support.avaya.com/avayaiw) to the laptop computer. The laptop should be running Windows 2000 or Windows XP to support GIW.












10. Select Continue the installation using this wizard.

11. Click Continue. The Initializing the Components screen appears.



Figure 124: Initializing the Components screen

12. Check Initialize the Gateway Installation Session.

13. Click Continue. The Import Electronic Preinstallation Worksheet screen appears.



Figure 125: The Import Electronic Preinstallation Worksheet screen

14. If you have an EPW on your laptop (see Obtaining the Electronic Preinstallation Worksheet (EPW) on page 24), check Import EPW. If you are using GIW to only upgrade files, verify that Import EPW is unchecked.

15. Browse to the EPW file on your laptop. Any values that are included in the EPW will appear as default values from now on as you move through this wizard.

16. Click Continue. The IP Addresses screen appears.



Figure 126: The IP Addresses screen

The IP Addresses screen displays information about the G450 automatically detected, such as what media modules are installed in the media modules slots.

17. If you are using GIW only to upgrade firmware, continue with step 30.

18. Click in the Action column. The PMI screen appears.



Figure 127: The PMI screen

19. In the PMI screen, specify the details of the Primary Management Interface (PMI) for the G450. The PMI is used as the IP address of the G450 for specific management functions. If you do not know which interface to designate as the PMI, check with your project manager.





21. In the SNMP V1 screen, specify SNMP V1 community strings for Read Only and Read Write access.





23. If you want to configure an SNMP V3 user on the G450:

a. In the User Name field, enter a string of up to 32 characters representing the SNMP V3 user.

b. In the Authentication Protocol field, select the authentication protocol by which the SNMP V3 user should be authenticated (SHA1 or MD5).

c. In the Authentication Password field, enter a string of between 8 and 64 characters specifying the user’s authentication password. The authentication password is transformed using the authentication protocol and the SNMP engine ID to create an authentication key.

d. In the Re-enter Authentication Password field, enter the authentication password again for verification.

e. In the Privacy Password field, enter a string of between 8 and 64 characters specifying the SNMP V3 user’s privacy password.

f. In the Re-enter Privacy Password field, enter the privacy password again for verification.

24. Click Continue. The IP Addresses - Media Gateway Controller List screen appears.



Figure 130: The IP Addresses - Media Gateway Controller List screen

25. In the Media Gateway Controller List screen, specify the IP address of the primary Media Gateway Controller (MGC) in the first IP address box.

26. Specify the IP addresses of up to three additional MGCs, optionally, in the subsequent boxes.

27. Specify Transition Point information.

28. Click Ping Test to test the accessibility of each MGC.

29. Click Continue. You return to the IP addresses screen.

30. Click Continue. The Firmware screen appears.



Figure 131: The Firmware screen

31. Upload any firmware upgrades you need to install to your TFTP server.

32. In the TFTP Address field, enter the address of your TFTP server.

33. In the TFTP Directory field, enter the name of the directory on the TFTP server in which the upgrade files are located.

34. In the table, check the Select box for all firmware components you want to upgrade. The current version of each component is listed to help you confirm the need for upgrade.

35. Enter the file name of each firmware upgrade file you want to install in each line of the table where you checked the Select box.

36. Click Continue. The firmware is upgraded and the Change Master Key - Optional screen appears. The master key is used to encrypt gateway secrets (passwords, etc.) in the gateway configuration file.



Figure 132: The Change Master Key - Optional screen

37. If you want to change the master key, enter the new master key passphrase and then confirm by entering it again. A new master key is generated from the passphrase.

38. Click Continue. The Gateway License screen appears.



Figure 133: The Gateway License screen

39. If you will need to use the VPN feature on the G450, check Install Gateway License File and fill in the remaining fields to install the gateway license file. For information on the Gateway license file, see Downloading a G450 license file to your laptop on page 21.

40. Click Continue. The Gateway Authentication screen appears.



Figure 134: The Gateway Authentication screen

41. If you have a service contract, the G450 is shipped with an authentication file. This authentication file is required for Avaya services personnel to allow them secure remote access to the gateway. Click Continue. The Field Replaceable Unit (FRU) Status screen appears. View the status of the Field Replaceable Units detected in the G450.



Figure 135: The Field Replaceable Unit (FRU) Status screen

42. Click Continue. The TFTP Server screen appears. The TFTP Server screen enables you to upload firmware and configuration files for IP phone upgrades to the G450 TFTP server.



Figure 136: The TFTP Server screen - part 1

43. If you want to upload configuration and firmware files for IP phones to the G450 TFTP Server, do the following:

a. In the Server IP Address field, enter the IP address of the machine hosting the files that are to be uploaded.

b. Select the file transfer protocol (TFTP, FTP, or SCP) you want to use to upload the files from the host machine. TFTP is selected by default.

The use of the SCP protocol is limited to copying files of 1 MB or less. Therefore, an SCP server can be used for copying the script files, which do not exceed 128 KB, but cannot be used for copying image files.

c. If you selected FTP or SCP, enter the username and password in the Username and Password fields, and re-enter the password for confirmation in the Re-enter Password field.

44. Click Continue.



Figure 137: The TFTP Server screen - part 2

45. In the Select column, check any files you wish to upload.

Note:Note: If you selected SCP as your upload protocol, the checkboxes for the phone

images are disabled. If a green circled checkmark is displayed in the Uploaded column, the file has already been uploaded.

46. Click Continue. The files are uploaded and the G450 Modem Type Selection screen appears. If you are using GIW only to upgrade firmware, click Continue until you reach the Finish Up screen. Go to step 55.



Figure 138: The G450 Modem Type Selection screen

47. If you do not need to connect a modem to the G450, select None.

48. If you do need to connect a modem to the G450, select the type of modem you want to connect.

49. Click Continue. The appropriate modem configuration screen appears.



Figure 139: The G450 Serial Modem Configuration screen



Figure 140: G450 USB Modem Configuration screen

50. In the PPP IP Address field, enter the RAS IP address of the modem obtained using the ART tool. See Running the Automatic Registration Tool (ART) for the RAS IP address on page 22.

51. Enter the PPP Subnet Mask.







53. Click Continue. The Change Root Password screen appears.



Figure 141: The Change Root Password screen

54. If you would like to change the password on the G450 Media Gateway, enter the current password in the Current Password field, enter a new password in the New Password field, and re-enter the new password in the Confirm New Password field.

55. Click Continue. The Finish Up screen appears.



Figure 142: The Finish Up screen

Follow the on-screen instructions if you want to save the installation log file. Further configurations, as described in this screen, can now be performed either remotely, via a modem that you enabled with GIW, or locally.

Connect a modem, if necessaryIf you enabled a serial or USB modem on the G450 during your GIW session, you can now connect the modem.

Connecting a serial modem1. Connect the serial modem to a working telephone line.

2. Connect the provided DB-25 adapter to the modem.

3. Disconnect the flat cable from the COM port of the laptop computer.

4. Connect the flat cable to the DB-25 connector on the modem.

Test the modem connection


Connecting a USB modem1. Connect a USB modem to a working telephone line.



2. Connect one end of a USB cable to the modem.

3. Connect the other end of the USB cable to a USB port on the G450 front panel.

Test the modem connectionIf the modem is successfully initialized, the MDM LED on the G450 front panel lights.

Testing the modemIf you connected a modem, verify that the MDM LED is lit, and then dial into the modem to check that you can authenticate to the modem.


Appendix E: Power supplies and adjunct systems

This appendix provides information and wiring examples of installation procedures for various telephone and console power supplies.In addition, you may need to install one or more adjunct systems or devices. Follow the instructions in:

● IA770 INTUITY AUDIX messaging application on page 237

● INTUITY AUDIX LX messaging system on page 239

● Call center on page 239

● Uninterruptible power supply (UPS) on page 242

● Terminal server installation on page 245

● Call Detail Recording (CDR) on page 258

● Reliable Data Transport Tool (RDTT) package on page 261

● Printers on page 262

● DS1/T1 CPE loopback jack on page 263

● External modems on page 278

● Busy tone disconnect equipment for non-U.S. installations on page 280

● Music-on-hold on page 281

● Paging and announcement equipment on page 285

● Adjunct Information Sources on page 286

For these adjunct systems, consult the documentation specific to the system for complete installation instructions. Your planning documentation specifies the equipment you will be installing.

! WARNING:WARNING: To reduce the risk of fire, use only 26 AWG or larger telecommunication line cords

when installing telephones or adjuncts.

Power supplies and adjunct systems


Typical adjunct power connectionsThe 400B2 adapter is convenient for connecting local -48 VDC power to a modular plug. See Figure 143.Each port network can provide power for up to three attendant consoles. This source of power is preferred for the attendant consoles because it has the same battery backup as the G450 Media Gateway. Refer to Documentation for Avaya Communication Manager, Media Gateways and Servers CD, 03-300151, for detailed power supply information and installation procedures.

Figure 143: 400B2 Adapter Connecting to a Modular Plug

Figure notes:

1. Flush-Mounted Information Outlet2. Surface-Mounted Information

Outlet3. To Individual Power Unit

4. 400B2 Adapter5. To Telephone6. Destination Service Access Point

(DSAP) Power Cord

r749428KLC060396

Typical adjunct power connections end-to-end


Typical adjunct power connections end-to-endFigure 144 shows typical connection locations for adjunct power.

Figure 144: Example Adjunct Power Connections

Auxiliary power for an attendant consoleThe nonessential functions of an attendant console and its optional 26A1 or 24A1 selector console derive power from an auxiliary power source. Provide auxiliary power for an attendant console through this cable so the console remains fully operational during short power outages.

Note:Note: Only 1 console can derive auxiliary power from the system and through the

auxiliary cable located in the trunk/auxiliary field.

A console’s maximum distance from its auxiliary power source is:

● 800 ft (244 m) for a 302A1

Figure notes:

1. Typical display telephone2. Individual power supply (Such as 1151B/

C) (Not used if item 14 is used)3. 400B2 adapter4. Information outlet (modular jack)5. 4-pair D-Inside Wire (DIW) cable6. Satellite site or adapter location7. 25-pair D-Inside Wire (DIW) cable8. Station side of MDF

9. 100P6A patch cord or jumpers10. System side of MDF11. 25-pair cable to digital line

modular jack12. Equipment room13. Satellite location14. Bulk power supply. Install at

satellite location or equipment room (not both).

cydmapwr EWS 052898

1

2

3

4

5

6

7

8

9

10

11

1213

14 14



● 350 ft (107 m) for a 301B1 and 302D

An attendant console can also derive auxiliary power from:

● Individual 1151B/C or 1151B2/C2 power supply

● MSP-1 power supply

● 258A-type adapters

● Bulk power supplies

Local and Phantom PowerAn attendant console’s maximum distance from the system is limited. See Table 25.

Table 25: Attendant Console Cabling Distances

Enhanced Attendant Console (302D)

24 AWG Wire (0.26 mm2) 26 AWG Wire (0.14 mm2)

Feet Meters Feet Meters

With Selector Console

Phantom powered 800 244 500 152

Locally powered 5000 1524 3400 1037

Without Selector Console

Phantom powered 1400 427 900 274

Locally powered 5000 1524 3400 1037

IA770 INTUITY AUDIX messaging application


IA770 INTUITY AUDIX messaging applicationThe IA770 INTUITY AUDIX Messaging Application runs on a G450 Media Gateway controlled by an S8300 Server. Without the need for additional hardware, IA770 INTUITY AUDIX software processes touchtones, converts messages to the G.711 format, and converts text to speech.

Note:Note: For complete information on IA770 INTUITY AUDIX Installations, see Avaya

IA770 INTUITY AUDIX Messaging, Release 3.0, Installation, Upgrades, and Troubleshooting, 11-300532.

! CAUTION:CAUTION: IA770 INTUITY AUDIX Messaging processes messages using the G.711 codec

only. Therefore, ensure that a codec set exists that uses only the G.711 codec. Then, assign that codec set to a network region. And, finally, assign that network region to the AUDIX signaling group that is linked to the IA770 INTUITY AUDIX Messaging trunk group.

Shared resources of IA 770 coresidencyAn IA770 uses many resources of the S8300 Server and the media gateway where it resides. The following list outlines the S8300’s shared resources used by the IA770 INTUITY AUDIX system:

● Hardware for data storage and retrieval

● TFTP server for:

- Downloading and updating the license file for feature activation- Backing up and restoring data over a LAN or a WAN, including translations and

messages- Updating and upgrading software

● IP address for administration access

● General Alarm Manager for alarm display

● Web interface to start and stop the system

The IA770 system also shares the same switch-tone parameters established for the S8300 Server. With the software-only version of the IA770 system that is currently sold, the S8300 Server handles switch tones on behalf of the IA770 system and passes on the control information to the IA770 system using QSIG signaling. With the IA770 system that uses a CWY1 board, the installer or administrator must set IA770 parameters to match those of the S8300 Server.



Where is the IA770 location and softwareIA770 INTUITY AUDIX messaging is a software-only version of INTUITY AUDIX messaging that uses a QSIG-MWI H.323 virtual trunk for communication between the Communication Manager and IA770 software. The INTUITY AUDIX system software is loaded directly onto the S8300 hard drive.

Note:Note: For upgrades only, a G450 Media Gateway that previously used a CWY1 board

can continue to use the CWY1 board with IA770 INTUITY AUDIX software. However, the CWY1 board is no longer available for new systems.

Using an AUDIX trunk group as well as an AUDIX hunt group for new systems

For new systems, an H.323 virtual trunk integration must be established. The virtual trunk group, and signaling group, setup is handled automatically when you install IA770 INTUITY AUDIX Messaging with the Avaya Installation Wizard. Otherwise, you must administer the trunk group, its signaling group, and the assigned network region and IP codec set with Communication Manager once the software is installed. The number of trunks assigned to the trunk group can be either 3, 6, or 12.The use of trunks replaces the need for voice ports in the hunt group. However, an INTUITY AUDIX hunt group must still be defined. The hunt group setup is also handled automatically when you install IA770 INTUITY AUDIX Messaging with the Avaya Installation Wizard. Otherwise, you must administer the hunt group using Communication Manager. Other switch administration tasks that are associated with proper hunt group functions, such as creating COR, COS, and coverage paths, are also required.

IA770 INTUITY AUDIX installations and S8300upgrades for IA770 INTUITY AUDIX

The INTUITY AUDIX software must be installed or upgraded at the same time as the S8300 Communication Manager software load (the .rpm files). The IA770 software is delivered on the Communication Manager software distribution CD. The Communication Manager installation tools install IA770 INTUITY AUDIX automatically.For complete information on IA770 INTUITY AUDIX Installations Avaya IA770 INTUITY AUDIX Messaging, Release 3.0, Installation, Upgrades, and Troubleshooting, 11-300532.

INTUITY AUDIX LX messaging system


INTUITY AUDIX LX messaging system The process of integrating an INTUITY AUDIX LX system with an Avaya S8300 Server involves a series of tasks to prepare the switch to work with the INTUITY AUDIX LX system.The procedures for this process are fully documented in INTUITY AUDIX LX Release 1.0 Documentation, 585-313-818. The information is contained in a document with the title INTUITY AUDIX LX Release 1.0 LAN Integration with S8300 and DEFINITY® Systems.

Call centerThe S8300 Server provides an excellent solution for a small call center. The S8300 Server with the G450 Media Gateway supports the following call center capabilities:

● All three Avaya call center packages:

- Avaya Call Center Basic - Avaya Call Center Deluxe- Avaya Call Center Elite

● Up to 450 agents

● A maximum of 16 ASAI links

● Avaya G450 announcement software

About Avaya G450 announcement softwareVoice announcements are used in a call center environment to announce delays, direct customers to different departments, and entertain and inform calling parties. The announcement capability is standard and comes co-resident on the G450. The G450 announcement software has many of the functions of the TN2501AP VAL circuit pack. See Table 26 for differences between the Avaya G450 Announcement software and the VAL circuit pack. For more information on Avaya G450 Announcement software, see the



Administrator Guide for Avaya Communication Manager, 03-300509, Chapter 13, "Managing Announcements".

Table 26: Comparison between the G450 Announcement software and the VAL circuit pack

Area description

TN2501AP (VAL) circuit pack

Avaya G450 announcement software

Requires hardware

Yes No

Maximum storage time

Up to 60 minutes at 64Kbps sample rate

Up to 45 minutes at 64Kbps uncompressed speech

Concurrent calls per announcement

50 when using a DEFINITY Server SI or DEFINITY Server CSI1,000 when using the DEFINITY Server R, S8500, or S8700-series Server

1,000

Backup and restore over LAN

Yes Yes

Recording method

Use PC or telephone Use PC or telephone

File portability to multiple DEFINITY or Avaya G450 Media Gateways

Yes Yes

Playback quality Toll quality Toll quality

Backup speed 2.6 seconds for each 60 seconds of announcement time

2.6 seconds for each 60 seconds of announcement time

Reliability High High

Firmware downloadable

Yes Yes

1 of 2

Call center


Number of boards per system

5 on the DEFINITY CSI and DEFINITY SI10 on the DEFINITY R and S8500 or S8700-series Server

10 per configuration

Number of announcement ports

32 64

Announcements per board

1024 256

Maximum number of announcements in a configuration

128 DEFINITY Server CSI or DEFINITY Server Si1,000 DEFINITY Server R3,000 S8500, or S8700-series Server

3,000 over multiple G450 Media Gateways

Format CCITT A-law or u-law CCITT A-law or u-law

Sample bits 8 8

Sample rate 8,000 KHz 8,000 KHz

Channels Mono Mono

Table 26: Comparison between the G450 Announcement software and the VAL circuit pack (continued)

Area description

TN2501AP (VAL) circuit pack

Avaya G450 announcement software

2 of 2



Uninterruptible power supply (UPS)The Avaya 1000-2000 VA online Uninterruptible power systems (UPSs) provide power protection for telecommunications systems and equipment. Avaya UPSs are a cost-effective measure to avoid costly downtime. The Avaya UPS provides complete isolation from power disturbances to protect customer’s data and equipment. It can keep the phones up and ensure network reliability, but it also provides customizable alarm and monitoring capabilities.Avaya online UPSs feature:

● Isolation of connected equipment from all incoming power problems● Doubled battery service life and advanced warning of the end of useful battery life with

Advanced Battery Management (ABM) technology● Prolonged backup time with Extended Battery Modules (EBMs)● Conditioned incoming power without depleting the battery to preserve battery power for

complete power outages● Adapted to rack-mount and standalone tower applications with two-in-one form factor● Standard RS-232 communications port● Standard DEFINITY alarm contacts● Six foot communications cable included● Web/SNMP card to add direct control and monitoring capabilities in SNMP-based

networks and via Web browsers (Optional for all models except select 1000 VA UPS)

UPS models

Avaya Equipment to protect (total load of 750VA | 523 Watts)

Holdover Time (mins)

UPS UPS Capacity used

SAP

6 750 VA Line-interactive Rackmount UPS, RoHS

100.0% 700427073


75.0% 700427081


52.1% 700427099

8 1000 VA Online UPS with Web/SNMP Card

75.0% 700290273

1 of 2

Uninterruptible power supply (UPS)


24 1500 VA Online UPS w/Web card + Rail Kit

50.0% 194384

68 1000 VA Online UPS with Web/SNMP Card and 1 EBM

75.0% (1) 700290273(1) 700404411

89 1500 VA Online UPS w/1 EBM, Web card, 4-post Rail

50.0% (1) 194384(1) 700404429

143 1000 VA Online UPS with Web/SNMP Card and 2 EBM

75.0% (1) 700290273(2) 700404411

167 1500 VA Online UPS w/2 EBM, Web card, 4-post Rail

50.0% (1) 194384(2) 700404429

253 1500VA Online UPS w/3 EBM, Web card, 4-post Rail

50.0% (1) 194384(3) 700404429

344 1500VA Online UPS w/4 EBM, Web card, 4-post Rail

50.0% (1) 194384(4) 700404429

360 3000 VA Online UPS with 4 EBM

25.0% (1) 181588(4) 700404577

720 1500 VA Online UPS w/1 XBU48 and Web/SNMP Card

50.0% (1) 194384(1) 700404486

Avaya Equipment to protect (total load of 750VA | 523 Watts)

Holdover Time (mins)

UPS UPS Capacity used

SAP

2 of 2

Battery runtimes (in minutes)1

1000 VA Model

Load Std Internal Batteries (1) 24V EBM (2) 24V EBMs

200 VA / 140 W 37 271 546

400 VA / 280 W 19 142 278

700 VA / 490 W 9 72 156

1 of 2



1. This table provides typical information. Runtimes are approximate and may vary with equipment, configuration, battery age, temperature, etc.

Full Details on these units can be found in Hardware Description and Reference for Avaya Communication Manager, 555-245-207. You can also go online to find out the latest details about UPS technology at http://www.avayaups.com/avaya/default.asp.

850 VA / 595 W 6 59 124

1000 VA / 700 W 5 48 104

Battery runtimes (in minutes)1

1000 VA Model

Load Std Internal Batteries (1) 24V EBM (2) 24V EBMs

2 of 2

http://www.avayaups.com/avaya/default.asp

Terminal server installation


Terminal server installationThis section provides information on connecting adjunct equipment to a G450 Media Gateway with an S8300 Server using a terminal server (see Figure 145). Avaya supports the IOLAN+ 104 terminal server.Any device that does not support a direct TCP/IP connection, but that does support an RS-232 interface, can connect through a terminal server. System printers and some CDR devices use RS-232 connections and can connect through a terminal server.You can connect up to four adjuncts through one terminal server.

Figure 145: Switch-to-adjunct LAN connectivity through a terminal server

Figure notes:

1. switch2. IP connection on an S8300/G450 configuration3. 10/100Base-T Hub (optional)

4. terminal server5. serial port6. CDR adjunct

LAN

cydfadj KLC 091302

1

2 5

6

3DATA CONNECTIONS ONLY - NOT FOR TELECOM USE

1 2 3 4 10BASE-T 5VDC

4



Equipment required for installing and administering the terminal server

Make sure you have all the equipment on site before the installation. You must have the hardware listed in Table 27.

You also need a computer (laptop) with the HyperTerminal software program for the initial administration of the IOLAN+ and to set up the ports.

Table 27: Required equipment

Comcode Description Qty Supplier

700015084 700409519 CUST SOL TERM SRVR 4PT RHS

1 Avaya

NA RJ45-to-DB25 connector for IOLAN+ (supplied with 700015084)

4 Avaya

NA DB25-to-DB9 connector for PC COM port

1 Avaya

NA RS-232 Null modem (if needed for PC or printer connectivity)

1 or more

Avaya

405369042 Male/female adapter (if necessary) 1 or more

Avaya

846943306or 104154414NA

6-inch RJ45 crossover cord, or

10/100Base-T auto-sensing LAN hub or router

1

1

Avaya

Customer

102631413NA

259A adapter, orCAT5 cross connect hardware and connecting blocks

1 AvayaCustomer

NA RJ45 UTP Category 5 modular cords 1–2 Customer

NA 451A in-line RJ45 adapters, as needed to connect modular cords together



What are the distance limits for the terminal serverThe distance limit from the switch to the LAN hub is 328 ft (100 meters). The distance limit from the LAN hub to the terminal server is 328 ft (100 meters). If installed, the limit from the terminal server to the adjunct is 50 ft (15 meters).However, to achieve greater distance limits, the switch’s LAN hub/router may be connected to a WAN and the hub/router for the terminal server also connected to the same WAN.

How is the terminal server cabling connectedFigure 146 shows the connection between the terminal server port and a call accounting system.

Figure 146: Stand-alone call accounting system link using a terminal server

Connecting the IOLAN+ to the adjunct and the LANConnect the adjunct to the IOLAN+, using the RJ45-to-DB25 cable and the null modem. You can use a male/female adapter (see Figure 147).

clan2gca.cdr 50 Ft. Maximum

StandaloneCall Accounting

CallAccounting

Port

DemarcationPoint

M25A or M25BRS232 Cable

«C-LAN

Switch

Hub orRouter

328 ft max(100 m)

328 ft max(100 m)

AC Power

Terminal Server

RJ45 Cat 5Modular Cord

RJ45 Cat 5Modular Cord

259A Adapter,356A Adapter (Jack #1), or

258B Adapter (Jack #1)



Figure 147: Connecting an adjunct to the IOLAN+

Follow these typical steps:

Note:Note: Depending on the adjunct’s connections, you may not need all of these pieces.

1. Connect the null modem adapter to COM1 port on the adjunct.

Note:Note: The null modem is an important element in this setup. Without it, data may not

transfer correctly.

2. Connect the other end of the null modem adapter to the DB25 to RJ-45 cable.

3. Connect the RJ-45 end to any port on the IOLAN+.

Administering the IOLAN+To administer the IOLAN+ the first time, you must connect a PC or laptop to the RS-232 Port 1 on the IOLAN+ terminal server. Follow these typical steps:

1. Connecting the IOLAN+ on page 249

2. Setting up HyperTerminal on the computer on page 249

3. Administering the IOLAN+ the first time on page 249

Figure notes:

1. IP connection on an S8300/G450 2. Local area network (LAN)3. IOLAN+ 104 terminal server4. Adjunct (system management terminal or

a system printer, for example)

5. Null modem6. PC or laptop (for initial

administration)7. DB25-to-RJ45 cable8. DB25-to-DB9 cable

cydf

rcon

KLC

021

201

1

2

4

DATA CONNECTIONS ONLY - NOT FOR TELECOM USE

1 2 3 4 10BASE-T 5VDC

3

7

7

8

5

5

6



4. Rebooting the IOLAN+ on page 252

Note:Note: Depending on the computer’s COM port, you may not need all of these pieces.

Connecting the IOLAN+

1. Connect the DB9 end of the DB9-to-DB25 cable to the COM port on the PC or laptop.

2. Connect the DB25 end to the null modem adapter.

3. Connect the other end of the null modem adapter to the DB25 to RJ-45 cable.

4. Connect the RJ-45 end to Port 1 of the IOLAN+.

5. Before beginning the initial administration, make sure you have the following information:

● New IP address and subnet mask for IOLAN+

● Host name for IOLAN+

● IP address of S8300 Server Ethernet interface

● Port number of S8300 Server Ethernet interface where adjunct connects

Use the HyperTerminal software program that comes with Windows 95/98/NT/2000 to administer the IOLAN+.

Setting up HyperTerminal on the computer

1. Open HyperTerminal.

2. Click the File > Properties > Connect tab.

a. In the Connect using: field, select COM n,

where n is the communication port your computer is using.

3. Click CONFIGUREa. Set the bits per second field to 9600.

b. Set the Flow control field to Hardware.

4. Click OK.

5. Press ENTER to get the login prompt.

Administering the IOLAN+ the first time

1. At the login prompt type any text and press ENTER.



2. At the second prompt type set term ansi and press ENTER to view the Connections Menu.

3. Under Connection select Port 1 (the port to which the adjunct is connected) and press ENTER to access the Commands menu.

4. Select Admin mode > Password and press ENTER.

5. Type iolan, the default password, and press ENTER.

The Administration Menu changes, offering more options.

Name: port 2 CONNECTIONS MENU Terminal: 2

Connection Host

1 *** FREE ** === Commands === 2 *** FREE ** | Telnet ^T| 3 *** FREE ** | Rlogin ^R| 4 *** FREE ** | Port ^P| | Admin mode ^A| | CLI | | Lock | | Logout ^D| ================

___________________________________________________________________________

IOLAN PLUS v4.02.00 a CDi iolan

Name: port 2 ADMINISTRATION MENU Terminal: 2

gateway Examine/modify gateway table. host Examine/modify host table. line Terminal configuration organised by line. password Specify password to allow modification of menu items. port Terminal configuration organised by port. quit Return to connections menu. server Examine/modify Server parameters. stats Examine Server statistics.

Password [ ]

___________________________________________________________________________

IOLAN PLUS v4.02.00 a CDi iolan-st



6. Select server and press ENTER to view the Server Configuration menu.

7. Fill in the following fields with information appropriate to your network.

Leave the default settings for the other fields.

● Name: ● IP address: (for IOLAN+)

● Subnet mask:8. Press ENTER and select Save & Exit to effect the changes.

You must reboot the server any time you change an IP address or Local Port value.

** Administrator ** SERVER CONFIGURATION Terminal: 2

Name [iolan ] Debug mode [0 ] IP address [123.45.67.89 ] Subnet mask [222.222.0.0 ] Ethernet address [00:80:d4:03:11:cd] Ethernet interface [AUTO] Language [English ] Identification [ ] Lock [Disabled] Password limit [5 ] CR to initiate [No ] SNAP encoding [Disabled] Boot host [ ] Boot diagnostics [Enabled ] Boot file [ ] Init file [ ] MOTD file [ ] Domain name [ ] Name server [ ] NS Port [53 ] WINS server [ ]___________________________________________________________________________

Name used for prompts and message on bottom right of screen.




Rebooting the IOLAN+

1. Press ENTER to view the Administration Menu.

Note:Note: The following steps re-initialize the IOLAN+ so it knows it's connected to the LAN

through its IP address.

2. Select reboot and press ENTER.

3. Press the space bar to restart the IOLAN+.

Navigating the IOLAN+ terminal serverRefer to the IOLAN+ user guide for details. In general, you must:

● Use the arrow keys to move to a menu item

● Use the TAB key to move from field to field horizontally

● Use the ENTER key to choose an item

** Administrator ** ADMINISTRATION MENU Terminal: 2

access Remote System Access (PPP). change Change login and/or admin password. gateway Examine/modify gateway table. host Examine/modify host table. kill Kill TCP connections on serial line. line Terminal configuration organised by line. port Terminal configuration organised by port. quit Return to connections menu. reboot Reboot Server. server Examine/modify Server parameters. stats Examine Server statistics. trap Examine/modify SNMP Trap parameters.

Port [2 ]

____________________________________________________________________________




Administering the gatewayYou need to administer the gateway only if the S8300 Server and IOLAN+ are not in the same subnet.

Note:Note: If the S8300 Server and IOLAN+ are in the same subnet, skip this procedure.


2. Type iolan and press ENTER.

3. Select gateway to access the Gateway menu.

4. Fill in the following fields for Entry 1:

● Destination: S8300 Server IP address

● Gateway: Gateway address

● Netmask: Subnet mask

Note:Note: The following steps re-initialize the IOLAN+ so it knows it's connected to the LAN

through your gateway.

5. Select reboot and press ENTER.

6. Press the space bar to restart the IOLAN+.

Administering an IOLAN+ portUse this procedure when connecting an adjunct or serial COM port on a PC directly (locally) to the IOLAN+ (see Figure 147: Connecting an adjunct to the IOLAN+ on page 248).


2. Type iolan and press ENTER.

3. Select port and press ENTER.



4. Type port number and press ENTER to view the Port Setup Menuwhere port number is the port that the adjunct connects to.

5. Fill in the following fields.

Leave the default settings for the other fields.

● Speed: 9600● Monitor DSR: Yes● Monitor DCD: No● Name: port number or other descriptive name

● Terminal type: undef● CLI/Menu: CLI● Reset Term: No● Flow ctrl: xon/xoff ● IP addresses: leave blank

● Mask: leave blank

● Access: Remote● Authentication: None● Mode: Raw● Connection: None

** Administrator ** PORT SETUP MENU Terminal: 2Hardware Flow ctrl Keys Speed [9600 ] Flow ctrl [xon/xoff] Hot [^]] Intr [^C] Parity [None] Input Flow [Enabled ] Quit [^@] Kill [^U] Bit [8] Output Flow [Enabled ] Del [^@] Sess [^@] Stop [1 ] Echo [^@] Break [Disabled] IP Addresses Monitor DSR [Yes ] Src [ ] Mask [ ] Monitor DCD [No ] Dst [ ]

User Options Access Name [port 2 ] Keepalive [No ] Access [Remote ] Terminal type [undef ] Rlogin/Telnet [Telnet] Authentication [None ] TERM [ ] Debug options [No ] Mode [Raw ] Video pages [0] Map CR to CR LF [No ] Connection [None ] CLI/Menu [CLI] Hex data [No ] Host [ ] Reset Term [No ] Secure [No ] Remote Port [0 ] MOTD [No ] Local Port [5101]

________________________________________________________________________________




● Host: leave blank or enter S8300 Server IP Address

● Remote Port: 0● Local Port: must match the value of Remote Port on the IP Services screen of the

Communication Manager software

6. Press ENTER and select Save & Exit to effect the changes.

7. Press ENTER again to view the Administration Menu.

8. Select kill to disable the port connection.

9. Repeat the steps for each additional port you want to administer.

10. When administration is complete, from the Connections Menu, select logout (or press Ctrl D).

11. Close HyperTerminal.

At this point, you have established a connection path from the adjunct through the IOLAN+ to the S8300 Server.

Testing connectivity through the IOLAN+1. On the system management terminal, press ENTER to get the login prompt to the

Communication Manager switch.

Note:Note: If you get garbled text, check the baud rate setting on the Port Setup Menu. You

can adjust it up or down.

2. If no login prompt appears, log back into the IOLAN+ through HyperTerminal.

3. Select Admin mode > stats and press ENTER twice.

4. Select users and press ENTER.



5. Look at the port that the adjunct is connected to and see if there is any traffic.

If not, check all your connections and administration fields.

After you have successfully administered and validated the connection between the adjunct and the S8300 Server through the IOLAN+, you can disconnect the laptop or other PC from the IOLAN+. No further IOLAN+ administration is required.

Potential failure scenarios and repair actionsIf a link goes down between the terminal server and the switch, you must reboot the terminal server for the link come back up. If you are performing a software upgrade or if a system reset occurs, you must reboot the terminal server to restore the link. See Rebooting the IOLAN+ on page 252 for instructions.

Administering IP servicesFor each adjunct that you connect using TCP/IP, you need to administer IP services to establish the IP address/TCP port pairing. The IP address is associated with the node name that you just administered. In this example, we are administering the primary call detail recording (CDR) connection as end-to-end TCP/IP.

1. Type change ip-services and press ENTER to assign the CDR endpoint.

** Administrator ** SERVER STATISTICS Terminal: 2 1. port1 Talking to host 172.22.22.67.5111<DSR+CTS+DCD >DTR+RTS 2. port 2 SERVER STATISTICS <DSR+DCD >DTR+RTS 3. port 3 waiting for DSR or DCD >DTR+RTS 4. port 4 modem waiting for DSR or DCD >DTR+RTSREM <unknown> logged outLOG logger not enabled

___________________________________________________________________________

Press <RETURN> to see list of options.IOLAN PLUS v4.02.00 a CDi iolan-st



2. In the Service Type field, enter CDR1 for the call accounting link.

3. In the Local Node field, enter the node name for the switch.

In this example, enter procr.4. The Local Port field defaults to 0 for all client applications.

You cannot make an entry in this field.

5. In the Remote Node field, enter the node name for the adjunct, as administered on the Node Names screen.

For the call accounting application, type callacctg.

6. In the Remote Port field, enter the TCP listen port assigned to the adjunct.

The recommended value for CDR1 is 5101.

Note:Note: This number must match the port administered on the end device. If you are

using the Downloadable Reliable Session-Layer Protocol tool, this must match the port administered in the Server application. If you are using a terminal server, this number must match the Local Port number on the Port Setup menu. Consult the documentation for your Call Accounting system to determine the appropriate port for the CDR device.

7. Go to Page 3 and type n in the Reliable Protocol field for the CDR Service Type.

You do not use RSP with a terminal server.

8. Press ENTER to save your changes.

change ip-services Page 1 of 3

IP SERVICESService Enabled Local Local Remote RemoteType Node Port Node PortCDR1 procr 0 callacctg 5101

change ip-services Page 3 of 3

SESSION LAYER TIMERSService Reliable Packet Resp Session Connect SPDU ConnectivityType Protocol Timer Message Cntr Cntr Timer

CDR1 n 3 1 1 1



Call Detail Recording (CDR) This section provides information on connecting Call Detail Recording (CDR) equipment.

Connecting CDR equipmentThe interface between an Avaya server and CDR equipment is a Processor Ethernet Connection. As with C-LAN connections, the CDR adjunct may be a terminal server or a CDR application using RSP.

Note:Note: A printer or customer premises equipment (CPE) can also be used as the output

receiving device.

Administering CDR data collection

Note:Note: To send CDR data using a processor Ethernet interface to a device on the LAN/

WAN, you have the option to enable/disable RSP.

1. Setup the CDR adjunct to be ready to collect CDR data.

Record the IP address and the port number of the CDR adjunct, which could be a terminal server or a CDR application that uses RSP.

If the CDR adjunct is an application that uses RSP, start the application to listen for a client connection at the port.

2. Access the IP Services screen in Communication Manager (see Administering IP services on page 256), and do the following:

a. In the Service Type field, enter CDR1 or CDR2.

b. In the Local Node field, enter procr.c. The Local Port field defaults to 0 for all client applications.

d. You cannot make an entry in this field.

e. In the Remote Node field, enter the node name you assigned to the CDR adjunct in step 2.

f. In the Remote Port field, enter the port number used by the CDR adjunct determined in step 1.

Call Detail Recording (CDR)


3. Go to Page 3 and do the following:

a. Enter y in the Reliable Protocol field if you have a CDR application using RSP.

b. Enter n if the CDR adjunct is connected through a terminal server.

c. If RSP is being used, complete the Packet Resp Timer and Connectivity Timer fields with a reasonable value that matches the network condition (recommended values are 30 and 60 seconds, respectively).

d. Accept the defaults in the other fields.

4. Administer CDR parameters as described in Administering CDR parameters on page 259.

Administering CDR parametersYou must administer CDR parameters to let the system know that the adjunct is connected through TCP/IP. For details on all fields on the CDR System Parameters screen, see Administrator Guide for Avaya Communication Manager, 03-300509.

1. Type change system-parameters cdr and press ENTER.

The CDR System Parameters screen appears.

2. In the Primary Output Format field, enter a format specific to the call accounting system, if necessary.

In the example, unformatted is used. If you were sending data directly to a printer, you would use printer.

change system-parameters cdr Page 1 of 1 CDR SYSTEM PARAMETERS

Node Number (Local PBX ID): CDR Date Format: month/day Primary Output Format: unformatted Primary Output Endpoint: CDR1 Secondary Output Format: unformatted Secondary Output Endpoint: CDR2 Use ISDN Layouts? n EIA Device Bit Rate: 9600 Use Enhanced Formats? n Condition Code ‘T’ for Redirected Calls? nModified Circuit ID Display? n Remove # From Called Number? n Record Outgoing Calls Only? y Intra-switch CDR? n Suppress CDR for Ineffective Call Attempts? y CDR Call Splitting? y Disconnect Information in Place of FRL? n Outg Attd Call Record? y

Interworking Feat-flag? n Force Entry of Acct Code for Calls Marked on Toll Analysis Form? n Calls to Hunt Group - Record: member-extRecord Called Vector Directory Number Instead of Group or Member? n

Record Called Agent Login ID Instead of Group or Member? nInc Trk Call Splitting? n

Record Non-Call-Assoc TSC? n Call Record Handling Option: warningRecord Call-Assoc TSC? n Digits to Record for Outgoing Calls: dialed

Privacy - Digits to Hide: 0 CDR Account Code Length: 4



3. In the Primary Output Endpoint field, type CDR1.

4. If you use a secondary output device, and that device is also connected through TCP/IP, complete the Secondary Output Format field.

Also, type CDR2 in the Secondary Output Endpoint field.

5. Press ENTER to save your changes.

Testing the switch-to-adjunct linkYou can use the test, status, busyout and release commands to find and correct problems with CDR links. For more information about these commands, see Maintenance Commands for Avaya Communication Manager, Media Gateways and Servers, 03-300431.

Work with the vendor to test the link from the call accounting adjunct.If a link does not come up immediately, use the busyout cdr-link and release cdr-link commands to bring up the link. Additional administration procedures for CDR equipment are provided in the Administrator Guide for Avaya Communication Manager, 03-300509.

status cdr-linkCDR LINK STATUS

Primary Secondary

Link State: up extension not administered

Maintenance Busy? no

Reliable Data Transport Tool (RDTT) package


Reliable Data Transport Tool (RDTT) packageAvaya provides this free software application to help vendors and customers develop CDR applications that use the reliable session protocol to collect CDR data from an Avaya Server. The Reliable Data Transport Tool (RDTT) is a testing tool and thus is not supported by Avaya.

What does the RDTT package containThe RDTT package consists of the following:

● Specifications for the Reliable Session Protocol

● The Client application (Client.exe)

This application is designed to help you test the reliable session protocol without use of an Avaya Server.

● The Server application (Server.exe)

This application is designed to help you understand the reliable session protocol and to start building your products to work with the Avaya Server.

● User Guide

This document contains information about the client and server applications.

Downloading the RDTT packageThe RDTT package is available from the Avaya Support website as a self-extracting executable.

1. Go to the Avaya Support website at http://avaya.com/support.

2. In the Search For text box, type reliable and click Go.

3. Select Reliable Data Transport Client/Server Tool from the list of links that are found.

4. When asked, save the RDTT.exe file to a temporary folder on your computer.

It is approximately 1.6 to 2.0 MB in size.

Installing the RDTT package1. Double-click the RDTT.exe file.

The Install Shield Wizard steps you through the installation.

http://avaya.com/support



2. When prompted to select Client or Server, select both programs.

3. Continue with the installation.

Use the default destination folder and program folder.

Administering the RDTT packageSee the instructions in the user_guide.doc file to administer the RDTT tool on a PC.

Related topicsSee the following topics related to CDR:

● Chapter 16, “Collecting Billing Information,” in Administrator Guide for Avaya Communication Manager, 03-300509.

● “Call Detail Recording” in Chapter 21, “Features and Technical Reference” in Administrator Guide for Avaya Communication Manager, 03-300509.

PrintersFor connecting a printer to a G450 Media Gateway, see Terminal server installation on page 245 for more information.

DS1/T1 CPE loopback jack


DS1/T1 CPE loopback jackThis section provides information on how to install and use a DS1 loopback jack to test the DS1 span between the Avaya Server or Gateway and the network interface point. The loopback jack is required when DC power is at the interface to the MM710 media module.

Note:Note: Do not remove the loopback jack after installation. It should always be available

for remote tests of the DS1 span.

Note:Note: For G450 Media Gateway systems, the channel service unit (CSU) is integrated

within the MM710 Media Module. This means that there is no need for a separate external device. The loopback jack isolates the MM710 internal CSU from the DC power and properly loops the DC span power.

This section covers:

● Installing a loopback jack on page 263

● Administering a loopback jack on page 264

● Testing a loopback jack with a smart jack on page 265

● Testing a loopback jack without a smart jack on page 274

● Configurations using fiber multiplexers on page 276

Installing a loopback jackYou can use one of two installation options:

● Installing a loopback jack with a smart jack on page 264

● Installing a loopback jack without a smart jack on page 264

Selecting the loopback jack installation method

Select the installation method as follows:

● Install the loopback jack at the interface to the smart jack, if possible.

This position provides maximum coverage of CPE wiring when remote loopback tests are run.

● If the smart jack is not accessible, install the loopback jack at the extended demarcation point.



● If there is no extended demarcation point, install the loopback jack directly at the network interface point as shown in Figure 148.

● If there is an extended demarcation point and the smart jack is not accessible, install the loopback jack as shown in Figure 149.

● If there is an extended demarcation point, but the smart jack is accessible, install the loopback jack as shown in Figure 150.

Installing a loopback jack with a smart jack

1. Disconnect the RJ-48 (8-wide) connector at the appropriate interface point, and connect the loopback jack in series with the DS1 span.

See Figure 148 through Figure 150.

2. Plug the H600-383 cable from the MM710 into the female connector on the loopback jack.

3. Plug the male connector on the loopback jack cable into the network interface point.

Note:Note: Do not remove the loopback jack after installation. This is not a test tool and

should always be available to remotely test a DS1 span.

Installing a loopback jack without a smart jack

Install the loopback jack at the point where the cabling from the MM710 plugs into the dumb block. However, if there is more than one dumb block, choose the one that is closest to the Interface Termination feed or the fiber MUX, to provide maximum coverage for loopback jack tests. Refer to Figure 151 and Figure 152.

1. Disconnect the RJ-48 (8-wide) connector at the appropriate interface point, and connect the loopback jack in series with the DS1 span.

See Figure 151 through Figure 152.

2. Plug the H600-383 cable from the MM710 into the female connector on the loopback jack.

3. Plug the male connector on the loopback jack cable into the network interface point.

Note:Note: Do not remove the loopback jack after installation. This is not a test tool and

should always be available to remotely test a DS1 span.

Administering a loopback jack1. At the management terminal, type change ds1 location

where location is the DS1 interface circuit pack corresponding to the loopback jack.



2. Verify that the near-end CSU type is set to integrated.

3. On page 2 of the form, change the supply CPE loopback jack power field to y.

Setting this field to y informs the technician that a loopback jack is present on the facility and allows the technician to determine that the facility is available for remote testing.

4. Enter save translation to save the new information.

Testing a loopback jack with a smart jackThe loopback jack and smart jack isolate faults by dividing the DS1 span into three sections (see Figure 148 through Figure 150). These three sections are:

● From the MM710 to the loopback jack

● From the loopback jack to the smart jack (network interface point)

● From the smart jack to the CO

The first two sections are your responsibility. The last is the responsibility of the DS1 service provider.

Testing the DS1 span from the MM710 to the loopback jack

The DS1 span test has 2 parts:

● Checking for circuit connectivity between the DS1 circuit pack and the loopback jack.

The first part of the test powers-up the loopback jack and sends a signal from the DS1 circuit pack, through the wiring, to the loopback jack. The test allows about 10 seconds for the signal to loop around the loopback jack and return to the DS1 circuit pack. Then it sends the results to the management terminal and proceeds to the second part of the test.

● The second part of the test sends the standard, 3-in-24 DS1 stress-testing pattern from the DS1 board, through the loopback jack, and back to a bit error detector and counter on the DS1 board. A bit-error rate counter displays the results on the management terminal until you terminate the test.

Always perform both parts of the test. Proceed as follows.

Checking the integrity of local equipment

Before you go any further, make sure that the problem is actually on the DS1 span by testing the equipment that connects to the span at the near end. Test the DS1 circuit pack, and perform any needed maintenance or repairs.



1. On the SAT, type busyout board XXXVSwhere XXX is the administered number of the G450 (for example, 002), and VS is the slot number on the G450 of the Media Module (for example, V3).

2. Type change ds1 XXXVS to open the DS1 administration form.

3. Make sure that the near-end csu type field is set to integrated.

4. Go to page 2 of the DS1 administration form, and verify that the value of the TX LBO field is 0dB.

5. If the value of the TX LBO field is not 0dB, record the current value.

Then set the TX LBO field to 0dB for testing.

6. Press ENTER to make the changes.

7. Type test ds1-loop XXXVS cpe-loopback-jack.

where XXX is the administered number of the G450 (for example, 002), and VS is the slot number on the G450 of the Media Module (for example, V3).

The loopback jack powers up. Active, DS1 facility alarms (if any) clear. After about 20 seconds, the first set of results appears on the terminal.

8. If FAIL appears on the terminal display, there may be a fault in the wiring between the MM710 and the loopback jack or the loopback jack may itself be faulty.

Isolate the problem by replacing the loopback jack and repeating step 8.

9. If FAIL still appears after the loopback jack has been replaced, suspect a wiring problem.

Replace the cable between the MM710 and the loopback jack. Then repeat step 8.

10. When PASS appears on the terminal, proceed with the second part of the test, checking the integrity of transmitted data.



Testing the integrity of data sent over the loop

Now perform the second part of the test, checking for data errors.

Note:Note: The loss of signal (LOS) alarm (demand test #138) is not processed during this

test while the 3-in-24 pattern is active.

1. At the SAT, type clear meas ds1 loop XXXVS to zero out the bit-error counter


2. Type clear meas ds1 log XXXVS to zero out the performance measurement counter.

3. Type clear meas ds1 esf XXXVS to zero out the ESF error count.

4. Type list meas ds1 sum XXXVS to display the bit error count.



5. Step through Table 28 to troubleshoot.

Once you are fairly certain that the test is reporting no errors (after at least 1 error-free minute), confirm that the 3-in-24 pattern error detector is operating.

6. Type test ds1-loop XXXVS inject-single-bit-error.


7. Type list meas ds1 sum XXXVS to display the bit error count again.

Table 28: DS1 Troubleshooting

Condition Solution

The value of the Test: cpe-loopback-jack field is Pattern 3-in-24

The loopback jack test is active.

The value of the Synchronized field is N Retry the test 5 times.

The value of the Synchronized field remains N after 5 tries

Excessive bit errors are likely. Check for intermittent connections or broken wires in an SPE receive or transmit pair, and repair as necessary. Then repeat step 1.

The value of the Bit-error count field is non-zero

Repeat step 1 several times.

The value of the Synchronized field is Y The DS1 circuit pack has synchronized to the looped 3-in-24 pattern and is counting bit errors in the pattern.

The value of the Bit-error count field pegs at 65535 or increments by 100s or 1000s each time you repeat step 1

Suspect loose or corroded connections, severe crosstalk, or impedance imbalances between the two conductors of the receive or transmit pair. Wiring may need replacement.

The value of the Bit-error count fieldis 0

There are no obvious wiring problems. Verify this by repeating step 1 at 1-minute to 10-minute intervals until you are certain.If the test reports no errors for 1 minute, the error rate is less than 1 in 108. If the test reports no errors for 10 minutes, the error rate is less than 1 in 109.



8. Step through Table 29 to troubleshoot.

9. Type test ds1-loop location end-loopback/span-test to end the test.

Wait about 30 seconds for the DS1 to reframe on the incoming signal and clear DS1 facility alarms. Use Table 30 to evaluate the test results and to determine the solution.

Table 29: DS1 Bit-error count troubleshooting

Condition Solution

The value of the Bit-error count field is greater than 1

Replace the DS1 circuit pack, and retest.

The value of the Bit-error count field is 1 The test passed.

Table 30: Evaluation of DS1 CPE loopback and service provider test results

Condition Solution

Loopback termination fails with an error code of 1313

The span is still looped somewhere, possibly at the loopback jack, at the MM710, or somewhere in the network.

Loopback termination still fails

Replace the DS1 circuit pack, and repeat the test.

The DS1 cannot frame on the incoming span’s signal after the loopback jack power down

Either there is something wrong with the receive signal into the loopback jack from the dumb block or the smart jack, or there is something wrong with the MM710 media module itself. To rule out the MM710 media module, insert a transmit to receive loop around and verify that the MM710 can frame to its own signal.

The span failed the service provider’s loopback test

The problem is in the service provider’s network.

The service provider successfully loop tested the span, up to the smart jack

If the MM710 media module successfully passes the CPE Loopback Jack test, then the wiring between the loopback jack and the smart jack is suspect. Test and make repairs as needed.

You cannot locate and repair the problem in the time available and must terminate the test

The test will not terminate normally in the absence of a good framing signal. You have to reset the circuit pack. Enter reset board XXXVS.

The test terminated normally Proceed with step 10.



10. To restore DS1 administration:

a. At the SAT, type change ds1 XXXVS to open the DS1 administration form.

b. Go to page 2 of the DS1 administration form.

c. Change the value of the TX LBO field to the original value that you wrote down when you were administering the DS1 for the test.

d. Press ENTER to save the changes.

11. To release the DS1 circuit pack:

a. At the SAT, type release board XXXVS.

b. Leave the loopback jack in place.

Testing the DS1 span from the smart jack to the network interface termination or fiber multiplexer (MUX)

1. Have the service provider run a smart-jack loopback test against the network interface wiring that links the smart jack to the CO (section 3 in Figure 148 through Figure 150).

2. If the tests fails, there is a problem on the network side.

Have the service provider correct it.

Testing the DS1 span from the loopback jack to the smart jack

Note:Note: This test cannot isolate the problem if there are problems in the wiring between

the far-end CO and the far-end MM710. You must coordinate this test with the DS1 service provider.

Test the short length of customer premises wiring between the loopback jack and the smart jack (Section 2 in the following 3 figures) using a loopback that overlaps this section of the span.

1. Have the DS1 service provider at the CO end run a local MM710 line loopback test.

2. Have the DS1 service provider at the CO end run a local DS1 payload loopback test.

3. Run a far-end MM710 line loopback, using the following procedure:

a. From the SAT, type test ds1-loop XXXVS far-csu-loopback-test-beginwhere XXX is the administered number of the G450 (for example, 002), and VS is the slot number on the G450 of the Media Module (for example, V3).

b. Examine the bit-error counts, as in Testing the integrity of data sent over the loop on page 267.

c. Type test ds1-loop location end-loopback/span-test to terminate the test.



If the tests fails and there were no problems Testing the DS1 span from the MM710 to the loopback jack or Testing the DS1 span from the smart jack to the network interface termination or fiber multiplexer (MUX), there is a problem between the loopback jack to the smart jack. Work with the service provider to isolate the fault.

Figure 148: Network interface at smart jack for an MM710 multi-media module

Figure notes:

1. Span section 12. Span section 23. Span section 34. G450 Media Gateway5. E1/T1 port on an MM710

multi-media module

6. RJ-48 to network interface (up to 1000 ft [305 m])

7. Loopback jack8. Network interface smart jack9. Interface termination or fiber multiplexer (MUX)

10. Central office

2

CCA ETH WAN ETH LAN

RST ASB

2 3 4 5 61

V6

V5V1

V10

V3 V7

V4 V8

PWR

CPU

ALM

MDM

SY

ST

EM G450

V2

1

ETR

COMPACT FLASH

SERVICESCONSOLEUSB

CARD IN USE



Figure 149: Network interface at extended demarcation point (smart jack inaccessible) for an MM710 multi-media module

Figure notes:


multi-media module

6. RJ-48 to network interface (up to 1000 ft [305 m])7. Loopback jack8. Dumb block (extended demarcation)9. Network interface smart jack

10. Interface termination or fiber multiplexer (MUX)11. Central office

2

CCA ETH WAN ETH LAN

RST ASB

2 3 4 5 61

V6

V5V1

V10

V3 V7

V4 V8

PWR

CPU

ALM

MDM

SY

ST

EM G450

V2

1

ETR

COMPACT FLASH

SERVICESCONSOLEUSB

CARD IN USE



Figure 150: Network interface at extended demarcation point (smart jack accessible) for an MM710 multi-media module

Figure notes:


multi-media module

6. RJ-48 to network interface (up to 1000 ft [305 m])7. Dumb block (extended demarcation)8. Loopback jack9. Network interface smart jack

10. Interface termination or fiber multiplexer (MUX)11. Central office12. Dumb block to smart jack RJ-48

2

CCA ETH WAN ETH LAN

RST ASB

2 3 4 5 61

V6

V5V1

V10

V3 V7

V4 V8

PWR

CPU

ALM

MDM

SY

ST

EM G450

V2

1

ETR

COMPACT FLASH

SERVICESCONSOLEUSB

CARD IN USE



Testing a loopback jack without a smart jackWhen the loopback jack is added to a span that does not contain a smart jack, the span is divided into two sections: from the MM710 to the loopback jack and from the loopback jack to the central office (CO). Section 2 includes the short cable from the loopback jack to the dumb block demarcation point (part of the loopback jack). This cable is the only part of Section 2 that is part of customer premises wiring. It is not covered in the loopback jack’s loopback path. See Figure 151 and Figure 152.

Figure 151: Network interface at “dumb” block for an MM710 multi-media module

Figure notes:

1. Span section 12. Span section 23. G450 Media Gateway4. E1/T1 port on an MM710

multi-media module

5. RJ-48 to network interface (up to 1000 ft [305 m])6. Loopback jack7. Dumb block (demarcation point)8. Interface termination or fiber multiplexer (MUX)9. Central office

2

CCA ETH WAN ETH LAN

RST ASB

2 3 4 5 61

V6

V5V1

V10

V3 V7

V4 V8

PWR

CPU

ALM

MDM

SY

ST

EM G450

V2

1

ETR

COMPACT FLASH

SERVICESCONSOLEUSB

CARD IN USE



Figure 152: Network interface at “dumb” block with repeater line to fiber MUX for an MM710 multi-media module

You are responsible for finding and correcting problems in the customer wiring (section 1 and the loopback cable portion of section 2). The DS1 service provider is responsible for finding and correcting problems in the majority of section 2.

1. Test customer premises wiring from the MM710 to the loopback jack, as described in Testing the DS1 span from the loopback jack to the smart jack on page 270.

2. Test the loopback jack-to-dumb block and dumb block-to-CO wiring (section 2 in Figure 151 and Figure 152).

This can be done using a loopback that “overlaps” the section of the span. Any of the following loopbacks can do this:

● The local MM710’s line loopback, which the DS1 service provider at the CO end typically activates, tests, and then deactivates.

Figure notes:

1. Span section 12. Span section 23. G450 Media Gateway4. E1/T1 port on an MM710

multi-media module

5. RJ-48 to network interface (up to 1000 ft [305 m])6. Loopback jack7. Dumb block (demarcation point)8. Repeater9. Fiber multiplexer (MUX)

10. Central office

2

CCA ETH WAN ETH LAN

RST ASB

2 3 4 5 61

V6

V5V1

V10

V3 V7

V4 V8

PWR

CPU

ALM

MDM

SY

ST

EM G450

V2

1

ETR

COMPACT FLASH

SERVICESCONSOLEUSB

CARD IN USE



● The local DS1 interface’s payload loopback, which the DS1 service provider at the CO end activates and tests.

● The far-end MM710’s line loopback:

a. At the SAT type test ds1-loop location far-csu-loopback-test-begin to activate this test,


b. Type test ds1-loop location end-loopback/span-test to terminate this test,


Bit error counts are examined as described in Testing the DS1 span from the MM710 to the loopback jack on page 265. This test only isolates problems to Section 2 wiring if there are no problems in the wiring between the far-end CO and the far-end MM710. Coordinate this test with the DS1 service provider.

Failure of any of these tests indicate a problem in Section 2. This could mean bad loopback jack -to-”dumb” block cabling, but is more likely to indicate a problem somewhere between the “dumb” block and the CO. This is the responsibility of the DS1 service provider.

If the DS1 Span Test confirms that there are no problems in Section 1, the technician should proceed as follows to avoid unnecessary dispatch:

a. Identify and contact the DS1 service provider.

b. Inform the DS1 provider that loopback tests of the CPE wiring to the “dumb” block (section 1) showed no problems.

c. If the far-end MM710 line loopback test failed, inform the DS1 provider.

d. Request that the DS1 provider perform a loopback test of their portion of the Section 2 wiring by sending someone out to loop Section 2 back to the CO at the “dumb” block.

If this test fails, the problem is in the service provider’s wiring.

If the test passes, the problem is in the cable between the loopback jack and the “dumb” block. Replace the loopback jack.

Configurations using fiber multiplexersUse the loopback jack when customer premises DS1 wiring connects to an on-site fiber multiplexer (MUX) and allows wiring to the network interface point on the MUX to be remotely tested. This requires that the MM710 CSU be set so it can be used on DS1 wiring to the MUX.Fiber MUXs can take the place of Interface termination feeds as shown in Figure 148 through Figure 151. Test these spans using the same procedures as metallic spans.



Note:Note: Fiber MUXs may have loopback capabilities that the service provider can activate

from the CO end. These may loop the signal back to the CO or back to the DS1 MM710. If the MUX provides the equivalent of a line loopback on the “problem” DS1 facility, activate it after a successful loopback jack test, and use it to isolate problems to the wiring between the loopback jack and the MUX.

! Important:Important: Be aware that there are installations that use repeater-augmented metallic lines

between the MUX and the “dumb” block. These lines require DC power for the repeaters and this DC power is present at the “dumb” block interface to the CPE equipment. A loopback jack is required in this configuration to properly isolate and terminate the DC power.

Checking for the presence of DC

1. Make the following four measurements at the network interface jack:

● From transmit tip (T, Pin 5) to receive tip (T1, Pin 2)

● From transmit ring (R, Pin 4) to receive ring (R1, Pin 1)

● From transmit tip (T, Pin 5) to transmit ring (R, Pin 4)

● From receive tip (T1, Pin 2) to receive ring (R1, Pin 1)

All measurements should read 0 (zero) volts DC.



External modemsThe following section assumes that you are using one of the recommended external modems. However, any locally obtained, type-approved external modem should work. Contact your Avaya representative for more information.Recommended modems include:

● Multi-Tech MT5634ZBA-USB-V92

This section covers:

● Hardware required when configuring modems on page 278

● Multi-Tech MT5634ZBA-USB-V92 on page 278

● Multi-Tech MT5634ZBA-V92-GLOBAL on page 279

● Administering Multi-Tech modems on page 279

Hardware required when configuring modemsTo configure many modems, you use the Hayes-compatible AT command set.

Note:Note: If your modem uses a USB connection, use the USB ports instead of the serial

port. Also, AT commands are not required, so you can skip this section. Use the factory defaults.

Before you can enter AT configuration commands, you must first connect a terminal or a PC with a keyboard, monitor, and terminal-emulation software to the modem, as follows:

1. Connect one end of an RS-232 cable to an RS-232, serial-communications port (often called a COM port) on the terminal or PC.

2. Connect the other end of the RS-232 cable to the modem.

3. If you are using a PC, start your terminal emulation software.

Multi-Tech MT5634ZBA-USB-V92 Avaya recommends using a Multi-Tech USB modem, model MT5634ZBA-USB-V92, with an S8300/700, S8500, or S8700-series configuration. This modem is used for sending alarms, as well as for remote dial up to the server for maintenance and administration.

External modems


Configuring the MT5634ZBA-USB-V92 modem

In the United States, the Multi-Tech MT5634ZBA-US-V92 modem gets configured automatically through the USB port with the factory defaults. No special configuration is necessary. In a non-US country, the modem may require settings specific to the country in which the modem will be used.

Multi-Tech MT5634ZBA-V92-GLOBALAvaya recommends using a Multi-Tech serial modem, model MT5634ZBA-V92-GLOBAL, with a G450 media gateway.The Multi-Tech serial modem connects the G450 media gateway to an external trunk. This connection enables remote dial in capability for administration and troubleshooting.

Administering Multi-Tech modemsThe Multi-Tech modems do not require administration if used in the United States. In non-US countries, these modems may require administration.

For the full range of modem options, see the Administrator Guide for Avaya Communication Manager, 03-300509.



Busy tone disconnect equipment for non-U.S. installationsThe customer-provided busy tone disconnect adjunct detects busy tone disconnects of incoming calls on loop-start, 2-wire, analog trunks. In some non-U.S. countries where a G450 Media Gateway is used, the PSTN sends busy tone as the disconnect signal. Therefore, the S8300 Server, G450 Media Gateway requires a busy tone disconnect adjunct. Figure 153 shows typical connections.

Figure 153: Typical cabling for busy tone disconnect

Figure notes:

1. Public switched telephone network2. Main distribution frame3. Busy tone disconnect device

4. Tip and ring wires5. To loop-start, central-office, trunk

MM711 analog media module

cydf057 RPY 123097

1

2 234 4 4

5

Music-on-hold


Music-on-holdThe music-on-hold (MOH) feature allows a caller to hear music when that caller is placed on hold. This section covers:

● Installing a non-FCC-registered music source on a G450 Media Gateway on page 281

● Installing an FCC-registered music source on a G450 Media Gateway on page 284

Music-on-hold can be provided:

● Through a port on an MM711 Analog Media Module to a customer-supplied music source on a G450 Media Gateway

● Through a port on an MM711 Analog Media Module or MM714 Analog Media Module to a customer-supplied music source on a G450 Media Gateway

On a G450 Media Gateway, the music-on-hold feature is connected through a port on an MM711 Analog Media Module or an MM714 Analog Media Module.The G450 Media Gateway does not support an auxiliary trunk circuit pack. Therefore, for S8300 Server users, the music-on-hold feature through an auxiliary trunk is not supported. However, G450 Media Gateway users with an S8500 or S8700-series Server as primary controller can access the music-on-hold feature, if their equipment is physically connected to a TN763 auxiliary trunk circuit pack in an EPN carrier of an S8500 or S8700-series system.

Installing a non-FCC-registered music source on a G450Media Gateway

Figure 154 and Figure 155 show the connections for the music-on-hold feature on a G450 Media Gateway for a non-FCC-registered source.

Note:Note: The G350 Media Gateway’s physical connection with the MM711 Analog Media

Module or MM714 Analog Media Module is the same as the G450 Media Gateway’s connection with the MM711 Analog Media Module.

Note:Note: If you want multiple music sources, you must use multiple ports on the MM711

Analog Media Module.



Connecting a non-FCC-registered music-on-hold source to a G450 using a KS-23395-L3 coupler

Figure 154: Non-FCC-registered music-on-hold equipment connecting to KS-23395-L3 for a G450 Media Gateway

1. Connect one end of an RJ-45 cable to a port in the MM711 Media Module, or to a port or trunk port in the MM714 Media Module.

2. Connect the other end of the RJ-45 cable to a KS-23395-L3 coupler.

3. Connect the KS-23395-L3 coupler to the customer-supplied music source.

Follow the manufacturer’s instructions to properly connect the music source to the KS-23395-L3 coupler. Normally, you simply use an RCA cord.

4. Administer the switch for the new equipment.

Figure notes:

1. G450 Media Gateway2. MM711 Analog Media Module3. RJ-45 connection

4. KS-23395-L3 coupler5. RCA cord6. Music source

2

CCA ETH WAN ETH LAN

RST ASB

2 3 4 5 61

V6

V5V1

V10

V3 V7

V4 V8

PWR

CPU

ALM

MDM

SY

ST

EM G450

V2

1

ETR

COMPACT FLASH

SERVICESCONSOLEUSB

CARD IN USE

Music-on-hold


Connecting a non-FCC-registered music-on-hold source to a G450 using a KS-23395-L4 coupler

Figure 155: Non-FCC-registered music-on-hold equipment connecting to KS-23395-L4 for a G450 Media Gateway

1. Connect one end of an RJ-45 cable to a port in the MM711 Analog Media Module.

2. Connect the other end of the RJ-45 cable to a KS-23395-L4 coupler.

3. Connect the KS-23395-L4 coupler to the 909A/B universal coupler using a 8-pair modular cord.

4. Connect the 909A/B universal coupler to the music source using a 8-pair modular cord.


Note:Note: For additional installation information, refer to 909A/909B Universal Coupler

Installation Instructions, which is normally shipped with the 909A/909B Universal Coupler.

Figure notes:

1. G450 Media Gateway2. MM711 Analog Media Module3. RJ-45 connection4. KS-23395-L4 coupler

5. 8-pair modular cord6. 909A/B universal coupler7. 8-pair modular cord8. Music source

2

CCA ETH WAN ETH LAN

RST ASB

2 3 4 5 61

V6

V5V1

V10

V3 V7

V4 V8

PWR

CPU

ALM

MDM

SY

ST

EM G450

V2

1

ETR

COMPACT FLASH

SERVICESCONSOLEUSB

CARD IN USE



Installing an FCC-registered music source on a G450 MediaGateway

Figure 156 show the connections for the music-on-hold feature on a G450 Media Gateway for an FCC-registered source.

Note:Note: If you want multiple music sources, you must use multiple ports on the MM711

Analog Media Module.

Connecting an FCC-registered music-on-hold source to a G450 usinga KS-23395-L4 coupler

Figure 156: FCC-registered music-on-hold equipment connecting to KS-23395-L4 for a G450 Media Gateway


2. Connect the KS-23395-L4 coupler to the customer-supplied music source.

Normally, you simply use a 8-pair modular cord.


Figure notes:

1. G450 Media Gateway2. MM711 Analog Media Module3. RJ-45 connection

4. KS-23395-L4 coupler5. 8-pair modular cord6. Music source

2

CCA ETH WAN ETH LAN

RST ASB

2 3 4 5 61

V6

V5V1

V10

V3 V7

V4 V8

PWR

CPU

ALM

MDM

SY

ST

EM G450

V2

1

ETR

COMPACT FLASH

SERVICESCONSOLEUSB

CARD IN USE

Paging and announcement equipment


Paging and announcement equipment This section provides information on loudspeaker paging.

On a G450 Media Gateway, the loudspeaker paging feature is connected through a port on an MM711 Analog Media Module. The port is administered on the SAT Station screen, not the Loudspeaker Paging screen. The G450 Media Gateway does not support an auxiliary trunk circuit pack. Therefore, the loudspeaker feature through an auxiliary trunk is not supported on a G450 Media Gateway. Users on a G450 Media Gateway controlled by an S8700-series or S8500 can also access the loudspeaker paging feature if equipment is physically connected to a TN763 auxiliary trunk circuit pack in an PN carrier of an the S8700-series or S8500 system.Figure 157 shows the connections for loudspeaker paging, dial dictation, or recorded announcement features on a G450 Media Gateway.

Hooking up loudspeaker paging from a G450 Media Gateway

Figure 157: Typical loudspeaker equipment connections for a G450 Media Gateway


2. Connect the other end of the RJ-45 cable to a customer-supplied telephone hybrid device.

3. Follow the manufacturer’s instructions to properly connect the telephone hybrid device to your loudspeaker paging system.

4. Administer the M711 port on the SAT Station screen as an analog station.

Figure notes:

1. G450 Media Gateway2. Universal Paging access module3. RJ-45 connection

4. Telephone hybrid (third party) device

5. Loudspeaker paging system

2

CCA ETH WAN ETH LAN

RST ASB

2 3 4 5 61

V6

V5V1

V10

V3 V7

V4 V8

PWR

CPU

ALM

MDM

SY

ST

EM G450

V2

1

ETR

COMPACT FLASH

SERVICESCONSOLEUSB

CARD IN USE



Note:Note: Do not administer the MM711 port on the SAT Loudspeaker Paging screen.

Adjunct Information SourcesThis section lists documents you can use for installation of some of the key adjunct systems that you can connect. This section covers:

● Call Management System

● INTUITY AUDIX Messaging Systems

● Avaya Modular Messaging System

● Avaya Interactive Response

● Avaya EC500 Extension to Cellular and Off-PBX Stations

● Avaya SIP Enablement Services

● Call Accounting Systems

Call Management SystemFor information on installing Call Management System R3V12, see the following:

● Avaya Call Management System (CMS) R12 Software Installation, Maintenance, and Troubleshooting Guide (585-215-117)

● Avaya Call Management System (CMS) Sun Enterprise 3500 Computer Hardware Installation, Maintenance, and Troubleshooting (585-215-873)

● Avaya CMS R12 Sun Blade 100/150 Workstation Hardware Installation, Maintenance, and Troubleshooting (585-215-783)

● Avaya CMS Sun Fire V880 Computer Hardware Installation, Maintenance, and Troubleshooting (585-215-116)

Adjunct Information Sources


INTUITY AUDIX Messaging SystemsFor information on installing INTUITY AUDIX Messaging systems, see one of the following:

● For INTUITY AUDIX Release 5.1 Messaging, see INTUITY Messaging Solutions Release 5 Installation for New Systems on the INTUITY Messaging Solutions Release 5 Documentation CD-ROM, 585-313-803.

● For INTUITY AUDIX LX Messaging, see INTUITY AUDIX LX Installation Checklist on the INTUITY AUDIX LX Release 1 Documentation CD-ROM, 585-313-818.

● Avaya IA770 INTUITY AUDIX Messaging, Release 3.0, Installation, Upgrades, and Troubleshooting, 11-300532.

● For IA770 INTUITY AUDIX Messaging R1.3 (when available), go tohttp://support.avaya.com.

Avaya Modular Messaging SystemFor information on installing Avaya Modular Messaging systems, see Modular Messaging Release 2.0 Documentation CD-ROM, 11-300121.

Avaya Interactive ResponseFor information on installing Avaya Interactive Response systems, see Avaya Interactive Response R1.3 Installation, Migration, and Troubleshooting Guide (07-300180) on the Avaya Interactive Response R1.3 Documentation CD (07-300181).

Avaya EC500 Extension to Cellular and Off-PBX StationsFor information on installing Avaya EC500 Extension to Cellular and Off-PBX Station systems, see the Avaya EC500 Extension to Cellular and Off-PBX Station (OPS) Installation and Administration Guide, 210-100-500.

Avaya SIP Enablement ServicesFor information on installing Avaya SIP Enablement Services (SES), see the SIP Enablement Services Implementation Guide, 16-300140, and SIP Support in Avaya Communication Manager 4.0, 555-245-206.

http://support.avaya.com



Call Accounting SystemsFor information on installing Call Accounting Systems, see the online help or documentation included with the eCAS software CD-ROM.


Appendix F: Information Checklists

This appendix can be used as an aid for collecting necessary information for the installation of an Avaya G450 Media Gateway Media Gateway.The following lists are provided:

● Installer's Checklist: Tools, software, laptop settings, customer network information

● Serial Number and Login Information: Serial number of the G450 and login/passwords for various access methods

● Quick Setup for G450 Media Gateway Processor (MGP): IP addresses and setup commands for the MGP

● Installation Site Information: Customer and site contact information

Information Checklists


Installer's Checklist

Tools laptop with 32 MB RAM40 MB available disk spaceRS-232 port connector or Ethernet interfacecross-over Ethernet cables direct Ethernet cableserial cable and adapterUSB flash drive (optional)screwdriverSoftware Windows 95/98/ME/XP/NT/2000/Vista operating systemFTP server program. TFTP server program and SCP server program are recommendedTelnet programterminal emulation program: HyperTerminal or otherTCP/IP networking software: bundled with Windows OSweb browser: Netscape 4.7x or Internet Explorer 5.0Ethernet connections laptop default address and mask: 192.11.13.5, 255.255.255.252browser: no proxiescommunications properties: 9600 baud rate; no parity; 8 data bits, 1 stop bit; no flow SSO login Obtaining this login will require that you complete the authentication process. You will not be able to obtain the license file or to perform remote feature activation without the SSO login authentication process. You will not be able to obtain the license file or to perform remote feature activation without the SSO login.

Dial plan IP addressing plan List of customer-provided IP services

Serial Number and Login Information


Serial Number and Login Information

G450 Serial Number

Logins

Name & PasswordS8300 Server

G450 Media Gateway

SSO Authentication Login

ftp anonymousemail address

Communication Manager



Quick Setup for G450 Media Gateway Processor (MGP)

Task CLI Command Requested Fields Information to enter

Define a Primary Management Interface (PMI)

Enter the context of the interface which you want to set as the Primary Management Interface (PMI). For example:interface vlan

vlan id

In the context of the interface, assign an IP address and subnet mask to the interface:ip address

IP address

netmask

In the context of the interface, define this interface as the PMIpmi

Configure the ICC-VLANNote: By default, the ICC-VLAN is 1. Therefore configure the ICC-VLAN only if you wish to configure it for a VLAN other than 1.

Create a vlan and enter its configuration context:interface vlan

vlan id

In the context of the vlan interface, set the current vlan as the icc-vlan:icc-vlan

Set the VLAN ID of a LAN port (10/5 or 10/6) to the VLAN number of the ICC-VLAN:set port vlan

vlan id

module number

port number

Define the CLI prompt hostname hostname

Define a default gateway

ip default-gateway gateway IP address

Create a list of valid Media Gateway Controller(s)

set mgc list IP address1

IP address2

IP address3

IP address4

Display device information

show system

Installation Site Information


Installation Site Information

Site Name Main Phone

Installation Address

Shipping Address

Customer Contact NameTitlePhone:FAX:Mobile:Pager:email:Off-hours contact:

Salesperson/ Account Exec Sales/AE phone:Other Contact Info:

Notes to installer: access procedures, safety/security procedures

Access Contact NameTitlePhone:FAX:Mobile:Pager:email:Off-hours contact:

Installer NameDate of Installation


Appendix G: Equipment List

The following lists contain information necessary for ordering Avaya G450 Media Gateway and Avaya S8300 Server equipment.

Note:Note: If ordering parts, use the 9-digit "Comcode" numbers, not the 6-digit numbers.

Table 31: Equipment List: Avaya G450 Media Gateway

Avaya G450 Media Gateway

The Avaya G450 Media Gateway is a 19-inch 3u rack-mountable device. The G450 Media Gateway contains VoIP resources, a layer 2 switch, modular interface connectivity for traditional trunk and station access, and performs the function of a gateway/gatekeeper. It also houses eight Media Module Bays. The Avaya G450 Media Gateway is designed to offer options and scalability. You can mix and match Media Modules, as well as add additional Avaya G450 Media Gateways as they grow in size.

Avaya G450 Media Gateway Comcodes (for Services Ordering Only)

Comcode Number of Items Description

700407802 1 G450 chassis/Main board/80 channel DSP daughterboard/ 1 PSU

700432487 1 G450 chassis/Main board/20 channel DSP daughterboard/ 1 PSU

700017932 1 Rack Mount screw set for attaching the ears to the rack

700438997 2 Rack Mount Ears

700439003 1 Cable Management Ear

700305535 15 Rack Mount screw set for attaching the ears to the chassis

700318421 4 Feet

700318397 1 Tech Laptop Cable

700336597 8 Media Module Blanks

1 of 2

Equipment List


700336621 2 Low-Profile blanks (S8300)

700439011 1 G450 PSU Blank Panel

700236680 1 Grounding Kit for multiple G450s in a 19 inch rack

700439029 1 Cable grounding terminal-ring to open end 10AWG, 8M

Avaya G450 Media Gateway Comcodes for Customer and Services ordering

Comcode Description

700407802 G450 chassis/Main board/80 channel DSP daughterboard/ 1 PSU

700432487 G450 chassis/Main board/20 channel DSP daughterboard/ 1 PSU

700432495 G450 main board

700432503 80 channels DSP daughterboard

700432511 20 channels DSP daughterboard

700432529 G450 Power Supply Unit 400W AC

700432537 G450 Chassis

700438278 G450 Fan tray

700394992 808A Emergency Transfer Panel

Table 31: Equipment List: Avaya G450 Media Gateway (continued)

Avaya G450 Media Gateway

2 of 2


Table 32: Equipment List: G450 Media Gateway Power Cords

G450 Media Gateway Power Cords

Supplies Power to the G450 Media Gateway. One cord per gateway is required, and there are various cords depending on the power required for the country in which the unit will be installed.

When you order this material code, a descriptive attribute will be required; the attributes are:

Attribute Option Comcode: Description

CRD 30 405362641: PWR CORD 9X10IN USA 17505

CRD 31 407786623: PWR CORD 98IN EUROPE 12013S

CRD 32 407786599: PWR CORD 98IN UNITED KINGDOM 14012

CRD 33 407786631: PWR CORD 98IN AUSTRALIA 15012

CRD 34 407790591: PWR CORD INDIA P250CIM

CRD 42 408161453: PWR CORD 96IN ARGENTINA

Equipment List


Table 33: Equipment List: Avaya S8300B Server

Server

S8300B Server

The Avaya S8300B Server is an Intel™-based server complex that carries: ● administration and maintenance provisioning software

● Hard drive (Field-replaceable. Comcode: 700307028)

● 512 MB RAM

● Web serve

● Linux OS

● H.248 Media Gateway Signaling Protocol

● CCMS messages tunneled over H.248 Signaling Protocol

● TFTP server

The S8300B Server can act as the primary server of the G450 Media Gateway, or it can serve as a local survivable processor for remote/branch customer locations.

Comcode (for Services Ordering Only): 700335144


Table 34: Equipment List: Avaya S8300C Server

Server

S8300C Server

The Avaya S8300C Server is an Intel™-based server complex that carries: ● administration and maintenance provisioning software

● Hard drive (Field-replaceable. Comcode: 700307028)

● One GB RAM

● Web serve

● Linux OS

● H.248 Media Gateway Signaling Protocol

● CCMS messages tunneled over H.248 Signaling Protocol

● TFTP server

The S8300C Server can act as the primary server of the G450 Media Gateway, or it can serve as a local survivable processor for remote/branch customer locations.


Equipment List


Table 35: Equipment List: Media Modules

Media Modules

MM710 T1/E1 Media Module


The MM710 T1/E1 Media Module offers the combined features of a DEFINITY DS1 circuit pack and includes the following:

● A built-in CSU

● AMI-BASIC

● Both A-law for E1 and μ -law for T1

● Line Coding: AMI, ZCS, B8ZS for T1 and HDB3 or AMI for E1

● Stratum 3 Clock compatibility

● Trunk signaling for supporting US and International CO trunks and tie trunks as currently in existence

The MM710 T1/E1 Media Module supports the universal DS1 conforming to 1.544 Mbps T1 standard and 2.048 Mbps E1 standardISDN PRI is also supported for T1 or E1 revenue-associated option. The MM710 is RoHS compliant.

DEF DS1 LOOPBACK JACK 700A

Provides the ability to remotely troubleshoot the MM 710 T1/E1 Media Module. It is required for any customer with a maintenance contract and highly recommended for any other customer.

Material Code: 700406101

Apparatus Code: None Required for any customer with a maintenance contract and an MM710 T1/E1 Media Module. Highly recommended for other customers to avoid expensive technician visits.

1 of 4


MM711 Analog Media Module


The MM711 Analog Media Module supports eight analog interfaces allowing the connectivity of Loop Start, Ground Start, Analog DID trunks, and 2-wire analog Outgoing CAMA E911 trunks. The MM711 Analog Media Module also allows connectivity of analog, tip/ring devices such as single line telephones, modems or group 3 fax machines. Each port may be configured as either a trunk interface or a station interface.Also included is support for caller ID signaling, ring voltage generation for a variety of international frequencies and cadences, and administrable line termination styles. The MM711 is RoHS compliant.

MM714 Analog Media Module


The MM714 Analog Media Module supports four analog stations and four CO trunks. Analog DID trunk connections are to be associated with the ports labeled "Line" and not "Trunk". The MM714 is RoHS compliant.

MM712 DCP Media Module


The MM712 DCP Media Module allows connectivity of up to eight 2-wire DCP voice terminals. MM712 does not support 4-wire DCP telephones.Signal timing specifications for the MM712 support TDM Bus Timing in receive and transmit modes. The G450 Media Gateway supplies only +5 VDC and –48 VDC to the MM712 Media Module. Any other required voltages must be derived on the module.Loop range secondary protection is provided on the MM712. The MM712 is also self-protecting from an over current condition on a tip and ring interface. The MM712 is RoHS compliant.

MM716 24 port Analog Media Module


The MM716 provides 24 analog ports supporting telephones, modem, and fax. These ports can also be configured as DID trunks with either wink-start or immediate-start. The 24 ports are provided via a 25-pair RJ21X amphenol connector, which can be connected by an amphenol cable to a breakout box or punch down block. The MM716 is RoHS compliant.

Table 35: Equipment List: Media Modules (continued)

Media Modules

2 of 4

Equipment List


MM717 24 port DCP Media Module


The MM717 DCP Medial Module supports 24 DCP stations. The MM717 uses a 25-pair amphenol connector on the media module’s faceplate. The 24 DCP ports are intended for in-building use only. Phone lines connected to those ports are not to be routed out-of-building. Failure to comply with this restriction could cause harm to personnel or equipment. The MM717 is RoHS compliant.

MM720 BRI Media Module


The MM720 BRI Media Module contains eight ports that can be administered either as BRI trunk connections or BRI endpoint (telephone and data module) connections. Information is communicated in two ways:● Over two 64 Kbps channels called B1 and B2 that can be circuit-switched

simultaneously● Over a 16 Kbps channel called the D channel that is used for signaling. The

D channel occupies one time slot for all eight D channelsThe circuit switched connections have a u-law or A-law option for voice operation. The circuit switched connections operate as 64 Kbps clear channels when in the data mode.The MM720 BRI Media Module does not support combining both B channels together to form a 128 Kbps channel.

Note:Note: The MM720 BRI Media Module cannot be administered to

support both BRI trunks and BRI endpoints at the same time.

For BRI trunking, the MM720 BRI Media Module supports up to eight BRI interfaces, or up to 16 trunk ports, to the central office at the ISDN S/T reference point.

For BRI endpoints, each of the eight ports on the MM720 BRI Media Module can support one integrated voice/data endpoint or up to two BRI stations and/or data modules. Supported endpoints must conform to AT&T BRI, World Class BRI, or National ISDN NI1/NI2 BRI standards. The MM720 BRI Media Module provides -40 volt phantom power to the BRI endpoints.

The MM720 is RoHS compliant.


Media Modules

3 of 4


MM722 2-port BRI Media Module


The MM722 BRI Media Module supports two BRI ports. The MM722 is RoHS compliant.

MM340 Media Module Comcode (for Services Ordering Only): 700397128

The MM340 Media Module supports one E1/T1 WAN port for connecting to a WAN endpoint device. The MM340 is RoHS compliant.

MM342 Media Module Comcode (for Services Ordering Only): 700397136

The MM342 Media Module supports one USP WAN port for connecting to a WAN endpoint device. The MM342 is RoHS compliant.


Media Modules

4 of 4

Equipment List



Index

Index

Numerical400B2 Adapter . . . . . . . . . . . . . . . . . . 234808A Emergency Transfer Panel, installing . . . . . 60888B converter

for multi-carrier cabinets. . . . . . . . . . . . . 279for single-carrier cabinets . . . . . . . . . . . . 279

909A universal coupler, DC version . . . . . . . . . 280909A/B universal coupler . . . . . . . . . . . . . . 280

connection to loudspeaker paging system . . . . 285DIP switch settings . . . . . . . . . . . . . . . 280

909B universal coupler AC versionKS-22911L2 power supply . . . . . . . . . . . 280

AAccess, RFA . . . . . . . . . . . . . . . . . . . 20Accessing

Avaya Installation Wizard (IW) . . . . . . . . . . 151Maintenance web pages . . . . . . . . . . . . 74

Accessories box, contents . . . . . . . . . . . . . 26Adjunct

IOLAN+, connecting to . . . . . . . . . . . . . 247parameters, administering . . . . . . . . . . . . 262power connections . . . . . . . . . . . . . . . 234

end-to-end . . . . . . . . . . . . . . . . . 235sources of information . . . . . . . . . . . . . 286

Avaya Interactive Response systems . . . . . 287Avaya Modular Messaging systems. . . . . . 287Avaya SIP Enablement Services (SES) . . . . 287Call Accounting Systems. . . . . . . . . . . 288Call Management System . . . . . . . . . . 286DEFINITY

Wireless Business System . . . . . . . . 288EC500 Extension to Cellular systems . . . . . 287Intuity AUDIX Messaging systems . . . . . . 287Off-PBX Station systems . . . . . . . . . . . 287

Administrator loginsadding in IW . . . . . . . . . . . . . . . . . . 152configuring in IW . . . . . . . . . . . . . . . . 152

After installationoverview . . . . . . . . . . . . . . . . . . . . 83testing

connectivity . . . . . . . . . . . . . . . . . 83LSP failover . . . . . . . . . . . . . . . . . 84overview . . . . . . . . . . . . . . . . . . 83telephones . . . . . . . . . . . . . . . . . 83trunks. . . . . . . . . . . . . . . . . . . . 83

Alarmconfiguring in IW . . . . . . . . . . . . . . . 198OSS, configuring in IW. . . . . . . . . . . . . 200SNMP, configuring in IW . . . . . . . . . . . . 201

Allocating media module slots . . . . . . . . . . . . 35Alternate Software Bank button . . . . . . . . . . 134Amphenol cable, attaching to MM716 or MM717 . . . 55Analog

line circuit pack, TN2183. . . . . . . . . . . . 285port, connecting analog telephone to . . . . . . . 50telephone

port LEDs . . . . . . . . . . . . . . . . . 132telephone, connecting to analog port . . . . . . . 50trunk

connecting . . . . . . . . . . . . . . . . . . 53ordering . . . . . . . . . . . . . . . . . . . 90

Announcements, gateway. . . . . . . . . . . . . 239Approved grounds . . . . . . . . . . . . . . . . . 42ART (Automatic Registration Tool), running for RAS IP

address . . . . . . . . . . . . . . . . . . . . . 22ASB button. . . . . . . . . . . . . . . . . . . . 134ASG authentication

enabling in GIW . . . . . . . . . . . . . 67, 72, 228installing authentication file

in GIW. . . . . . . . . . . . . . . . . . . 222in IW . . . . . . . . . . . . . . . . . . . 181

Asynchronous TCP/IP links . . . . . . . . . . . . 262Attaching

amphenol cable to MM716 or MM717. . . . . . . 55analog telephone to analog port . . . . . . . . . 50analog trunk . . . . . . . . . . . . . . . . . . 53and enabling a modem

gateway without S8300 . . . . . . . . . . . . 63general description . . . . . . . . . . . . . . 63

and enabling a USB modemgateway with S8300 . . . . . . . . . . . . . 78

Avaya Partner Contact Closure Adjunct . . . . . . 59BRI stations to ISDN port . . . . . . . . . . . . 49chassis to wall or rack . . . . . . . . . . . . . . 29circuit protection devices . . . . . . . . . . . . . 56computer . . . . . . . . . . . . . . . . . . . . 47Coupled Bonding Conductor (CBC). . . . . . . . 58data and voice devices . . . . . . . . . . . . . 47DCP telephones. . . . . . . . . . . . . . . . . 52E1/T1

trunk . . . . . . . . . . . . . . . . . . . . 54WAN link . . . . . . . . . . . . . . . . . . 58

endpoint devices . . . . . . . . . . . . . . . . 47Ethernet WAN link . . . . . . . . . . . . . . . . 58


Index

external router . . . . . . . . . . . . . . . . . 58ground conductors . . . . . . . . . . . . . . . 40IP telephone to gateway. . . . . . . . . . . . . 49ISDN trunk . . . . . . . . . . . . . . . . . . . 54modem to gateway without S8300 . . . . . . . . 63safety ground. . . . . . . . . . . . . . . . . . 43server . . . . . . . . . . . . . . . . . . . . . 48switch or network data port . . . . . . . . . . . 47USB modem to gateway with S8300 . . . . . . . 78USP WAN link . . . . . . . . . . . . . . . . . 57WAN link . . . . . . . . . . . . . . . . . . . . 57

Attendant consoleauxiliary power . . . . . . . . . . . . . . . . . 235distance limitations . . . . . . . . . . . . . . . 236

AUDIXIA770 . . . . . . . . . . . . . . . . . . . . . 237

coresidency, shared resources of . . . . . . . 237installations . . . . . . . . . . . . . . . . . 238location . . . . . . . . . . . . . . . . . . . 238S8300 upgrades. . . . . . . . . . . . . . . 238software . . . . . . . . . . . . . . . . . . 238

LX . . . . . . . . . . . . . . . . . . . . . . . 239Authentication

CHAP, enabling in GIW . . . . . . . . . . . . . 228file

for CMinstalling in IW . . . . . . . . . . . . . . 171obtaining. . . . . . . . . . . . . . . . . 21

for gatewayinstalling in GIW . . . . . . . . . . . . . 222installing in IW . . . . . . . . . . . . . . 181

obtaining gateway . . . . . . . . . . . . . . 21Automatic Registration Tool

see ARTAuxiliary power for attendant console . . . . . . . . 235Avaya Communication Manager (CM)

softwareunpacking in IW . . . . . . . . . . . . . . . 164upgrading

in IW . . . . . . . . . . . . . . . 103, 161overview . . . . . . . . . . . . . . . . . 99via S8300 . . . . . . . . . . . . . . . . 99with CD-ROM drive . . . . . . . . . . . . 99without CD-ROM drive . . . . . . . . . . 100

upload source, selecting . . . . . . . . . . . 162version requirements for LSP . . . . . . . . . . 21

Avaya EC500 Extension to Cellular systems, sources of information . . . . . . . . . . . . . . . . . . . . 287

Avaya Ethernet switch, external. . . . . . . . . . . 48Avaya Gateway Manager, upgrading Java applet via FTP/

TFTP . . . . . . . . . . . . . . . . . . . . . . 104Avaya Installation Wizard (IW)

accessing . . . . . . . . . . . . . . . . . . . 151accessing, configuring laptop for . . . . . . . . . 151administrator logins

adding . . . . . . . . . . . . . . . . . . . 152

configuring. . . . . . . . . . . . . . . . . 152alarms, configuring . . . . . . . . . . . . . . 198authentication file, installing . . . . . . . . . . 181call routing, configuring . . . . . . . . . . . . 188CM

authentication file, installing . . . . . . . . . 202license file, installing . . . . . . . . . . . . 171software

unpacking . . . . . . . . . . . . . . . 164upgrading . . . . . . . . . . . . . 103, 161upload source, selecting . . . . . . . . . 162

configuration, initial . . . . . . . . . . . . . . 151country, selecting . . . . . . . . . . . . . . . 187date/time information, configuring . . . . . . . 159description . . . . . . . . . . . . . . . . . . . 81Domain Name Server (DNS), configuring . . . . 168Electronic Preinstallation Worksheet, importing . 155endpoints, installing . . . . . . . . . . . . . . 197extension ranges, adding . . . . . . . . . . . 189firmware

upgrading . . . . . . . . . . . . . . . . . 177uploading . . . . . . . . . . . . . . . . . 178

gatewayconfiguring. . . . . . . . . . . . . . . . . 173firmware, upgrading . . . . . . . . . . . . 103installation, verifying . . . . . . . . . . . . 205

Gateway Device Manager, launching . . . . . . 206INADS, configuring . . . . . . . . . . . . . . 170installation

log file, saving . . . . . . . . . . . . . . . 204new, confirming . . . . . . . . . . . . . . 158

IP addresses, configuring . . . . . . . . . . . 173IP phone upgrade files, uploading . . . . . . . 182laptop, configuring to access . . . . . . . . . . 151license file, installing. . . . . . . . . . . . . . 180master key, changing . . . . . . . . . . . . . 179Media Gateway Controller (MGC)

configuring. . . . . . . . . . . . . . . . . 176and upgrading . . . . . . . . . . . . . 156

upgrading existing . . . . . . . . . . . . . 160modem

configuring. . . . . . . . . . . . . . . . . 183enabling . . . . . . . . . . . . . . . . . . 184status, displaying. . . . . . . . . . . . . . 198

name and number list, importing . . . . . . . . 190Network Time Protocol (NTP), configuring . . . 169new installation, confirming . . . . . . . . . . 158NVRAM factory defaults, restoring . . . . . . . 159optional item checklist . . . . . . . . . . . . . 158optional services, configuring. . . . . . . . . . 167OSS alarm, configuring . . . . . . . . . . . . 200overview . . . . . . . . . . . . . . . . . . . 151phone message files, installing . . . . . . . . . 165primary controller IP addresses, configuring . . . 166Primary Management Interface (PMI), configuring 174


Index

product ID, changing . . . . . . . . . . . . . . 160required item checklist . . . . . . . . . . . . . 158root password, changing . . . . . . . . . . . . 202running. . . . . . . . . . . . . . . . . . . . . 153S8300 Server IP addresses, configuring . . . . . 166Server IP addresses, configuring . . . . . . . . 166SNMP

alarm, configuring . . . . . . . . . . . . . . 201V1 community strings, configuring . . . . . . 175V3 user, configuring . . . . . . . . . . . . . 175

system data, viewing . . . . . . . . . . . . . . 155telephony

parameters, configuring . . . . . . . . . . . 186translation defaults, configuring. . . . . . . . 187

translation information, generating . . . . . . . . 170trunk

adding . . . . . . . . . . . . . . . . . . . 192configuring . . . . . . . . . . . . . . . . . 190list of, viewing . . . . . . . . . . . . . . . . 191media module, configuring . . . . . . . . . . 197modifying

IP route configuration . . . . . . . . . . . 194parameters . . . . . . . . . . . . . . . 193

removing . . . . . . . . . . . . . . . . . . 196status, displaying . . . . . . . . . . . . . . 195

UPS, configuring . . . . . . . . . . . . . . . . 168usage options, selecting. . . . . . . . . . . . . 157

Avaya Interactive Response systems, information on. 287Avaya Modular Messaging systems, information on . 287Avaya Navy Shipboard Services . . . . . . . . . . 29Avaya Off-PBX Station systems, information on

. . . . . . . . . . . . . . . . . . . . . . . . 287Avaya Partner Contact Closure Adjunct . . . . . . . 59Avaya SIP Enablement Services (SES), sources of

information . . . . . . . . . . . . . . . . . . . . 287Avaya Software Update Manager . . . . . . . . . . 101

BBacking up the gateway to USB mass storage device 123Before installation

environmental verification . . . . . . . . . . . . 24grounding verification . . . . . . . . . . . . . . 25power verification . . . . . . . . . . . . . . . . 25read planning documentation . . . . . . . . . . 19required equipment . . . . . . . . . . . . . . . 19site requirements . . . . . . . . . . . . . . . . 24unpacking . . . . . . . . . . . . . . . . . . . 27

Boot banks . . . . . . . . . . . . . . . . . . . . 134Box inventory . . . . . . . . . . . . . . . . . . . 26Brackets, mounting

for rackattaching . . . . . . . . . . . . . . . . . . 31checks before . . . . . . . . . . . . . . . . 31types of . . . . . . . . . . . . . . . . . . . 29

with cable guides. . . . . . . . . . . . . . . 30without cable guides . . . . . . . . . . . . . 30

for wall . . . . . . . . . . . . . . . . . . . . . 32attaching to gateway . . . . . . . . . . . . . 32

BRI stations, connecting to ISDN port . . . . . . . . 49Busy tone disconnect equipment . . . . . . . . . 280Buttons

ASB . . . . . . . . . . . . . . . . . . . . . 134RST . . . . . . . . . . . . . . . . . . . . . 134

CCabinets

multi-carrier, converter forCCSC-1 PRI-to-DASS . . . . . . . . . . . 279CCSC-2 PRI-to-DPNSS . . . . . . . . . . 279PRI-to-BRI . . . . . . . . . . . . . . . . . 279

single-carrier, converter forCCSC-1 PRI-to-DASS . . . . . . . . . . . 279CCSC-2 PRI-to-DPNSS . . . . . . . . . . 279PRI-to-BRI . . . . . . . . . . . . . . . . . 279

Cable guides on mounting bracket . . . . . . . . 29, 30Call Accounting Systems, sources of information . . 288Call center . . . . . . . . . . . . . . . . . . . . 239

gateway announcements . . . . . . . . . . . 239Call Detail Recording (CDR)

data collection, administering. . . . . . . . . . 258equipment, connecting. . . . . . . . . . . . . 258parameters, administering . . . . . . . . . . . 259switch-to-adjunct link, testing . . . . . . . . . . 260

Call Management System, sources of information . 286Call routing, configuring in IW . . . . . . . . . . . 188Calling queue . . . . . . . . . . . . . . . . . . 285CBC (Coupled Bonding Conductor) . . . . . . . . . 58

installing . . . . . . . . . . . . . . . . . . . . 59CCA port. . . . . . . . . . . . . . . . . . . . . 133CCSC-1 PRI-to-DASS converter

for multi-carrier cabinets . . . . . . . . . . . . 279for single-carrier cabinets . . . . . . . . . . . 279

CCSC-2 PRI-to-DPNSS converterfor multi-carrier cabinets . . . . . . . . . . . . 279for single-carrier cabinets . . . . . . . . . . . 279

CDRsee Call Detail Recording (CDR)

CD-ROM drive, upgrading software . . . . . . . 79, 99CHAP authentication

enabling . . . . . . . . . . . . . . . . . . 67, 72enabling in GIW . . . . . . . . . . . . . . . . 228

Chassisdimensions and weight . . . . . . . . . . . . 149front panel description . . . . . . . . . . . . . 131installation

see Gateway chassis installationChecking

available number of power outlets . . . . . . . . 25


Index

environment before installing . . . . . . . . . . 24for DC in loopback jack . . . . . . . . . . . . . 277grounding . . . . . . . . . . . . . . . . . . . 25integrity of local equipment on DS1 span . . . . . 265list of optional and required items in IW. . . . . . 158

Circuit packsTN2183 analog line . . . . . . . . . . . . . . . 285TNPRI/BRI converter

for multi-carrier cabinets . . . . . . . . . . . 279for single-carrier cabinets . . . . . . . . . . 279

Circuit protection, installing . . . . . . . . . . . . . 56C-LAN board, administering IP addresses of. . . . . 256Clearance, front and rear . . . . . . . . . . . . . . 149CLI

commands for upgrading firmwarevia a USB device . . . . . . . . . . . . . . 111via FTP/TFTP . . . . . . . . . . . . . . . . 104

description . . . . . . . . . . . . . . . . . . . 81troubleshooting . . . . . . . . . . . . . . . . . 127upgrading gateway firmware

via FTP/TFTP . . . . . . . . . . . . . . . . 104via USB device . . . . . . . . . . . . . . . 111

CMauthentication file

downloading to laptop . . . . . . . . . . . . 21installing in IW. . . . . . . . . . . . . . . . 202

license filedownloading to laptop . . . . . . . . . . . . 21installing in IW. . . . . . . . . . . . . . . . 171

softwareunpacking in IW . . . . . . . . . . . . . . . 164upgrading

overview . . . . . . . . . . . . . . . . . 99via S8300 . . . . . . . . . . . . . . . . 99with CD-ROM drive . . . . . . . . . . . . 99without CD-ROM drive . . . . . . . . . . 100

upgrading in IW . . . . . . . . . . . . . . . 161upload source, selecting . . . . . . . . . . . 162

software, upgrading in IW . . . . . . . . . . . . 103Coaxial converter, 888B


COM port, selecting in GIW. . . . . . . . . . . . . 210Combination limitations for media modules . . . . . 35Command Line Interface

see CLICommands

copy ftp EW_archive . . . . . . . . . . . . . . 104copy ftp module . . . . . . . . . . . . . . . . 104copy ftp phone-image . . . . . . . . . . . . . . 116copy ftp phone-script . . . . . . . . . . . . . . 116copy ftp SW_imageA . . . . . . . . . . . . . . 104copy ftp SW_imageB . . . . . . . . . . . . . . 104copy running-config startup-config . . . . . . . . 115copy scp phone-script . . . . . . . . . . . . . . 116

copy tftp EW_archive . . . . . . . . . . . . . 105copy tftp module. . . . . . . . . . . . . . . . 105copy tftp phone-image . . . . . . . . . . . . . .116copy tftp phone-script . . . . . . . . . . . . . .116copy tftp SW_imageA . . . . . . . . . . . . . 105copy tftp SW_imageB . . . . . . . . . . . . . 105copy usb EW_archive . . . . . . . . . . . . . . 111copy usb module . . . . . . . . . . . . . . . .111copy usb phone-image. . . . . . . . . . . . . .116copy usb phone-script . . . . . . . . . . . . . .116copy usb SW_imageA . . . . . . . . . . . . . . 111copy usb SW_imageB . . . . . . . . . . . . . . 111erase phone-image . . . . . . . . . . . . . . .116ip tftp-server file-system size . . . . . . . . . . .115reset . . . . . . . . . . . . . . . . . . . . . .115save translation lsp . . . . . . . . . . . . . . . 84show application-memory . . . . . . . . . . . .115show controllers . . . . . . . . . . . . . . . . 127show interfaces serial . . . . . . . . . . . . . 127

Computerconnecting to the gateway . . . . . . . . . . . . 47downloading gateway firmware to local . . . . . .112HyperTerminal, setting up on. . . . . . . . . . 249laptop, configuring for IW access . . . . . . . . 151testing . . . . . . . . . . . . . . . . . . . . . 88

Conditions good for installation . . . . . . . . . . . 24Configuration

Avaya Communication Manager software via S8300 Server. . . . . . . . . . . . . . . . . . . . . 99

DS1 loopback jackchecking for DC . . . . . . . . . . . . . . 277using fiber multiplexers . . . . . . . . . . . 276

filesupgrading IP phone, overview. . . . . . . . .113

gateway . . . . . . . . . . . . . . . . . . . . 81basic . . . . . . . . . . . . . . . . . . . 209initial in GIW . . . . . . . . . . . . . . . . 209initial in IW. . . . . . . . . . . . . . . . . 151

LANdevice on gateway . . . . . . . . . . . . . . 88software, recording information for . . . . . . 88

laptop, for accessing IW . . . . . . . . . . . . 151limitations of media modules . . . . . . . . . . . 35modem

in IW . . . . . . . . . . . . . . . . . . . 183Multi-Tech

hardware required for . . . . . . . . . . 278MT5634ZBA-USB-V92 . . . . . . . . . 279

NTP in IW. . . . . . . . . . . . . . . . . . . 169remote, via Telnet . . . . . . . . . . . . . . . 100telephone . . . . . . . . . . . . . . . . . . . . 89telephone software, recording information for . . . 89trunk . . . . . . . . . . . . . . . . . . . . . . 91trunk software, recording information for . . . . . 91WAN

line . . . . . . . . . . . . . . . . . . . . . 92


Index

software, recording information for . . . . . . 92Connecting

analog telephone to analog port . . . . . . . . . 50analog trunk . . . . . . . . . . . . . . . . . . 53and enabling a modem

gateway without S8300 . . . . . . . . . . . 63general description . . . . . . . . . . . . . 63serial . . . . . . . . . . . . . . . . . . . . 63USB

gateway with S8300 . . . . . . . . . . . 78gateway without S8300 . . . . . . . . . . 68

Avaya Partner Contact Closure Adjunct . . . . . 59BRI stations to ISDN port . . . . . . . . . . . . 49Call Detail Recording (CDR) equipment . . . . . 258circuit protection devices . . . . . . . . . . . . 56computer . . . . . . . . . . . . . . . . . . . . 47computer to Services port . . . . . . . . . . . . 48Coupled Bonding Conductor (CBC) . . . . . . . 58data and voice devices . . . . . . . . . . . . . 47DCP telephones . . . . . . . . . . . . . . . . 52E1/T1 trunk. . . . . . . . . . . . . . . . . . . 54E1/T1 WAN link . . . . . . . . . . . . . . . . 58endpoint devices . . . . . . . . . . . . . . . . 47Ethernet WAN link . . . . . . . . . . . . . . . 58external router . . . . . . . . . . . . . . . . . 58IOLAN+ 104 terminal server . . . . . . . . . . . 249IOLAN+ 104 to adjunct and LAN . . . . . . . . . 247IP telephone to gateway. . . . . . . . . . . . . 49ISDN trunk . . . . . . . . . . . . . . . . . . . 54modem after running GIW . . . . . . . . . . . . 230music source

registeredto gateway via KS-23395-L4 . . . . . . . 284

unregisteredto gateway via KS-23395-L3 . . . . . . . 282to gateway via KS-23395-L4 . . . . . . . 283

over-voltage protection devices . . . . . . . . . 56power to the gateway . . . . . . . . . . . . . . 44printer to gateway via TCP/IP . . . . . . . . . . 262safety ground. . . . . . . . . . . . . . . . . . 43serial modem in GIW . . . . . . . . . . . . . . 230server . . . . . . . . . . . . . . . . . . . . . 48Services port to computer . . . . . . . . . . . . 48sneak-current protection devices. . . . . . . . . 56switch or network data port . . . . . . . . . . . 47telephone . . . . . . . . . . . . . . . . . . . 89trunk . . . . . . . . . . . . . . . . . . . . . . 90USB modem

gateway with S8300 . . . . . . . . . . . . . 78in GIW . . . . . . . . . . . . . . . . . . . 231

USP WAN link . . . . . . . . . . . . . . . . . 57WAN. . . . . . . . . . . . . . . . . . . . . . 57

Connectionsadjunct power . . . . . . . . . . . . . . . . . 234

end-to-end . . . . . . . . . . . . . . . . . 235IOLAN+ 104 terminal server cabling . . . . . . . 247

music-on-holdFCC-registered equipment . . . . . . . . . 281non-FCC-registered equipment . . . . . . . 281

ConnectivityIOLAN+ 104, testing . . . . . . . . . . . . . . 255LAN device, testing . . . . . . . . . . . . . . . 88testing after installation . . . . . . . . . . . . . 83

Console (CON) port . . . . . . . . . . . . . . . 132Contact closure

implementing . . . . . . . . . . . . . . . . . 133installing . . . . . . . . . . . . . . . . . . . . 59port description . . . . . . . . . . . . . . . . 133

Contents of gateway package . . . . . . . . . . . . 26Converter

for multi-carrier cabinetsCCSC-1 PRI-to-DASS . . . . . . . . . . . 279CCSC-2 PRI-to-DPNSS . . . . . . . . . . 279

for single-carrier cabinets . . . . . . . . . . . 279CCSC-1 PRI-to-DASS . . . . . . . . . . . 279CCSC-2 PRI-to-DPNSS . . . . . . . . . . 279

TNPRI/BRIfor multi-carrier cabinets . . . . . . . . . . 279for single-carrier cabinets . . . . . . . . . . 279

copy ftp EW_archive CLI command . . . . . . . . 104copy ftp module CLI command . . . . . . . . . . 104copy ftp phone-image CLI command. . . . . . . . .116copy ftp phone-script CLI command . . . . . . . . .116copy ftp SW_imageA CLI command . . . . . . . . 104copy ftp SW_imageB CLI command . . . . . . . . 104copy running-config startup-config CLI command . . .115copy scp phone-script CLI command. . . . . . . . .116copy tftp EW_archive CLI command . . . . . . . . 105copy tftp module CLI command . . . . . . . . . . 105copy tftp phone-image CLI command . . . . . . . .116copy tftp phone-script CLI command . . . . . . . . .116copy tftp SW_imageA CLI command. . . . . . . . 105copy tftp SW_imageB CLI command. . . . . . . . 105copy usb EW_archive CLI command. . . . . . . . .111copy usb module CLI command . . . . . . . . . . . 111copy usb phone-image CLI command . . . . . . . .116copy usb phone-script CLI command . . . . . . . .116copy usb SW_imageA CLI command . . . . . . . . 111copy usb SW_imageB CLI command . . . . . . . . 111Country, selecting in IW. . . . . . . . . . . . . . 187Coupled Bonding Conductor

see CBCCoupler

KS-23395-L3connecting

unregistered music source to gateway . . 282KS-23395-L4

connectingregistered music source to gateway via . . 284unregistered music source to gateway via 283

universal909A, DC version . . . . . . . . . . . . . 280


Index

909A/B . . . . . . . . . . . . . . . . . . . 280DIP switch settings . . . . . . . . . . . . 280jumper pinouts . . . . . . . . . . . . . . 280

909BAC version . . . . . . . . . . . . . . . . 280AC version, KS-22911L2 power supply . . 280

loudspeaker paging with . . . . . . . . . . . 285CWY1 board. . . . . . . . . . . . . . . . . . . . 238

DDate/time information, configuring in IW . . . . . . . 159DCP

media modules, ports for in-building use only . . . 57telephone, connecting. . . . . . . . . . . . . . 52

DEFINITYWireless Business System

sources of information . . . . . . . . . . . . 288Device Manager, upgrading Java applet via a USB device

111Devices

connecting endpoint . . . . . . . . . . . . . . 47data and voice, connecting . . . . . . . . . . . 47new, replacing and adding. . . . . . . . . . . . 87

Dimensions of plywood board for mounting gateway . 19DIP switch settings for 909A/B universal coupler . . . 280DNS, configuring in IW . . . . . . . . . . . . . . . 168Documentation, planning . . . . . . . . . . . . . . 19Domain Name Server

see DNSDownloading

CMauthentication file . . . . . . . . . . . . . . 21license file . . . . . . . . . . . . . . . . . 21

gatewayauthentication file . . . . . . . . . . . . . . 21firmware to local PC . . . . . . . . . . . . . 112firmware to local TFTP sever . . . . . . . . . 108license file . . . . . . . . . . . . . . . . . 21

IP telephoneconfiguration files . . . . . . . . . . . . . . 114

latest version of guide from website . . . . . . . 13recent firmware updates. . . . . . . . . . . . . 24upgrade software from CD-ROM. . . . . . . .79, 99

DS1loopback jack. . . . . . . . . . . . . . . . . . 263

administration . . . . . . . . . . . . . . . . 264checking local equipment integrity . . . . . . 265configuration

checking for DC . . . . . . . . . . . . . 277using fiber multiplexers . . . . . . . . . . 276

installing . . . . . . . . . . . . . . . . . . 263selecting method . . . . . . . . . . . . . 263with smart jack . . . . . . . . . . . . . . 264without smart jack . . . . . . . . . . . . 264

testingdata integrity . . . . . . . . . . . . . . 267from ISCU . . . . . . . . . . . . . . . 265from smart jack . . . . . . . . . . . . . 270to smart jack . . . . . . . . . . . . . . 270with smart jack . . . . . . . . . . . . . 265without smart jack . . . . . . . . . . . . 274

span . . . . . . . . . . . . . . . . . . . . . 264checking integrity of local equipment on . . . 265T1. . . . . . . . . . . . . . . . . . . . . 263

DTEV.35 serial cable . . . . . . . . . . . . . . . . 57X.21 serial cable . . . . . . . . . . . . . . . . 57

EE1 trunk, connecting . . . . . . . . . . . . . . . . 54E1/T1

port, on MM340 media module . . . . . . . . . . 58WAN link, connecting . . . . . . . . . . . . . . 58

ECCsee External Communications Controller

Electronic Preinstallation Worksheet (EPW)importing in GIW . . . . . . . . . . . . . . . 212importing in IW . . . . . . . . . . . . . . . . 155obtaining . . . . . . . . . . . . . . . . . . . . 24

EnablingASG authentication in GIW. . . . . . . . 67, 72, 228CHAP authentication . . . . . . . . . . 67, 72, 228modem

gateway without S8300 . . . . . . . . . . . . 63general description . . . . . . . . . . . . . . 63in GIW. . . . . . . . . . . . . . . . . . . 226in IW . . . . . . . . . . . . . . . . . . . 184serial . . . . . . . . . . . . . . . . . . . . 63USB

gateway with S8300. . . . . . . . . . . . 78gateway without S8300 . . . . . . . . . . 68

Endpoint devicesconnecting . . . . . . . . . . . . . . . . . . . 47new, replacing and adding . . . . . . . . . . . . 87

Endpointsinstalling in IW . . . . . . . . . . . . . . . . 197Multimedia Call Handling (MMCH) . . . . . . . 262

administering . . . . . . . . . . . . . . . 262one-number complex . . . . . . . . . . 262

connecting . . . . . . . . . . . . . . . . . 262testing . . . . . . . . . . . . . . . . . . . 262troubleshooting . . . . . . . . . . . . . . 262

widebandnon-signaling . . . . . . . . . . . . . . . 262overview. . . . . . . . . . . . . . . . . . 262remote port module. . . . . . . . . . . . . 262signaling. . . . . . . . . . . . . . . . . . 262

Environmental conditions


Index

mounting solution for harsh . . . . . . . . . . . 29verifying for installation . . . . . . . . . . . . . 24

EPWsee Electronic Preinstallation Worksheet (EPW)

Equipmentbusy tone disconnect . . . . . . . . . . . . . . 280Call Detail Recording (CDR), connecting . . . . . 258music-on-hold

FCC-registered connections . . . . . . . . . 281non-FCC-registered connections . . . . . . . 281

paging . . . . . . . . . . . . . . . . . . . . . 285loudspeaker

for MCC1, SCC1, CMC1, G600, or G650 media gateways . . . . . . . . . . . . . . . . 285

hooking up from gateway . . . . . . . . . 285with universal coupler. . . . . . . . . . . 285without paging adapter . . . . . . . . . . 285without universal coupler . . . . . . . . . 285

required for installationgathering . . . . . . . . . . . . . . . . . . 19IOLAN+ 104 terminal server . . . . . . . . . 246removing . . . . . . . . . . . . . . . . . . 85

unpacking . . . . . . . . . . . . . . . . . . . 27erase phone-image CLI command . . . . . . . . . 116ETH LAN port

connectingcomputer to . . . . . . . . . . . . . . . . . 47external router to . . . . . . . . . . . . . . 58server to . . . . . . . . . . . . . . . . . . 48

description . . . . . . . . . . . . . . . . . . . 133for network switching . . . . . . . . . . . . . . 47

ETH WAN portconnecting

computer to . . . . . . . . . . . . . . . . . 47Ethernet WAN link to. . . . . . . . . . . . . 58external router to . . . . . . . . . . . . . . 58server to . . . . . . . . . . . . . . . . . . 48

description . . . . . . . . . . . . . . . . . . . 133Ethernet

switch, external Avaya . . . . . . . . . . . . . 48WAN link, connecting . . . . . . . . . . . . . . 58

ETR port . . . . . . . . . . . . . . . . . . . . . 133European Standard Paging Access (ESPA) radio paging

equipment . . . . . . . . . . . . . . . . . . . . 285Expansion Services Module (ESM) . . . . . . . . . 262

administration . . . . . . . . . . . . . . . . . 262installing . . . . . . . . . . . . . . . . . . . . 262testing . . . . . . . . . . . . . . . . . . . . . 262troubleshooting . . . . . . . . . . . . . . . . . 262

Extension ranges, adding in IW . . . . . . . . . . . 189External

Avaya Ethernet switch . . . . . . . . . . . . . 48Communications Controller (ECC) . . . . . . . . 281endpoint devices, connecting . . . . . . . . . . 47Multi-Tech modem . . . . . . . . . . . . . . . 278

administering . . . . . . . . . . . . . . . . 279

hardware to configure . . . . . . . . . . . 278MT5634ZBA-USB-V92 . . . . . . . . . . . 278MT5634ZBA-USB-V92, configuring . . . . . 279MT5634ZBA-V92-GLOBAL . . . . . . . . . 279

ringing . . . . . . . . . . . . . . . . . . . . 285router, connecting to gateway . . . . . . . . . . 58

FFan tray, replacing . . . . . . . . . . . . . . . . . 96Fastening chassis to wall or rack . . . . . . . . . . 29Feet, affixing to stand gateway on table . . . . . . . 33Fiber multiplexers

configuring DS1 loopback . . . . . . . . . . . 276Field replaceable units

adding and removing . . . . . . . . . . . . . . 93fan tray . . . . . . . . . . . . . . . . . . . . . 96gateway main board . . . . . . . . . . . . . . . 93memory modules . . . . . . . . . . . . . . . . 94MP20 modules . . . . . . . . . . . . . . . . . 94MP80 modules . . . . . . . . . . . . . . . . . 94power supply . . . . . . . . . . . . . . . . . . 97VoIP modules . . . . . . . . . . . . . . . . . . 94

Firmwarebanks. . . . . . . . . . . . . . . . . . . . . 134copying files to S8300 Server . . . . . . . . . .110default bank. . . . . . . . . . . . . . . . . . 134downloading recent updates . . . . . . . . . . . 24files

upgrading IP phone . . . . . . . . . . . . .113installing from TFTP server on the S8300 Server 109loading . . . . . . . . . . . . . . . . . . . . 134upgrading

example using FTP/TFTP. . . . . . . . . . 105gateway

CLI commands for, via FTP/TFTP . . . . 104downloading to local PC . . . . . . . . . .112downloading to local TFTP server . . . . 108from primary controller . . . . . . . . . 102in GIW . . . . . . . . . . . . . . . . . 102in IW . . . . . . . . . . . . . . . . . . 103overview . . . . . . . . . . . . . . . . 101using CLI via FTP/TFTP . . . . . . . . . 104using CLI via USB device . . . . . . . . . 111

in GIW. . . . . . . . . . . . . . . . . . . 219in IW . . . . . . . . . . . . . . . . . . . 177installation worksheets, preparing . . . . . . 105Server Values worksheets, preparing . . . . 106with Avaya Software Update Manager . . . . 101

uploading in IW . . . . . . . . . . . . . . . . 178Front panel

gatewaybuttons

ASB . . . . . . . . . . . . . . . . . . 134RST . . . . . . . . . . . . . . . . . . 134


Index

description . . . . . . . . . . . . . . . . . 131media module slots . . . . . . . . . . . . . 131overview . . . . . . . . . . . . . . . . . . 131ports

analog telephone . . . . . . . . . . . . . 132CCA . . . . . . . . . . . . . . . . . . . 133Console (CON). . . . . . . . . . . . . . 132ETH WAN . . . . . . . . . . . . . . . . 133ETR . . . . . . . . . . . . . . . . . . . 133line . . . . . . . . . . . . . . . . . . . 132router . . . . . . . . . . . . . . . . . . 133Services . . . . . . . . . . . . . . . . . 132trunk. . . . . . . . . . . . . . . . . . . 132USB . . . . . . . . . . . . . . . . . . . 132

system LEDs . . . . . . . . . . . . . . . . 132media modules

MM312LEDs . . . . . . . . . . . . . . . . . . 135overview . . . . . . . . . . . . . . . . . 135ports. . . . . . . . . . . . . . . . . . . 135









MM716LEDs . . . . . . . . . . . . . . . . . . 144overview . . . . . . . . . . . . . . . . . 142

ports . . . . . . . . . . . . . . . . . . 143MM717

LEDs. . . . . . . . . . . . . . . . . . 146overview . . . . . . . . . . . . . . . . 144ports . . . . . . . . . . . . . . . . . . 145

MM720LEDs. . . . . . . . . . . . . . . . . . 147overview . . . . . . . . . . . . . . . . 147ports . . . . . . . . . . . . . . . . . . 147

MM722LEDs. . . . . . . . . . . . . . . . . . 148overview . . . . . . . . . . . . . . . . 148ports . . . . . . . . . . . . . . . . . . 148

S8300 Serveroverview. . . . . . . . . . . . . . . . . . 134ports . . . . . . . . . . . . . . . . . . . 135

LEDs. . . . . . . . . . . . . . . . . . 135

GGateway

authentication file, downloading to laptop . . . . . 21backing up to USB mass storage device . . . . 123call center. . . . . . . . . . . . . . . . . . . 239

announcements . . . . . . . . . . . . . . 239channels, number of supported. . . . . . . . . . 94components, initializing in GIW . . . . . . . . . 212configuration . . . . . . . . . . . . . . . . . . 81

initial gateway in GIW . . . . . . . . . . . 209initial in IW. . . . . . . . . . . . . . . . . 151

configuring in IW . . . . . . . . . . . . . . . 173connecting

computer to . . . . . . . . . . . . . . . . . 47power to . . . . . . . . . . . . . . . . . . . 44printers via TCP/IP . . . . . . . . . . . . . 262

firmwarebanks . . . . . . . . . . . . . . . . . . . 134downloading files

to local PC . . . . . . . . . . . . . . . .112to local TFTP server. . . . . . . . . . . 108

installing from TFTP server on S8300 Server. 109upgrading

CLI commands for, via FTP/TFTP . . . . 104CLI commands for, via USB device. . . . . 111from primary controller . . . . . . . . . 102in GIW . . . . . . . . . . . . . . . . . 102in IW . . . . . . . . . . . . . . . . . . 103overview . . . . . . . . . . . . . . . . 101using CLI via FTP/TFTP . . . . . . . . . 104using CLI via USB device . . . . . . . . . 111with Avaya Software Update Manager . . 101

front panelbuttons

ASB . . . . . . . . . . . . . . . . . . 134RST . . . . . . . . . . . . . . . . . . 134


Index

description . . . . . . . . . . . . . . . . . 131media module slots . . . . . . . . . . . . . 131ports

analog telephone . . . . . . . . . . . . . 132CCA . . . . . . . . . . . . . . . . . . . 133Console (CON). . . . . . . . . . . . . . 132ETH WAN . . . . . . . . . . . . . . . . 133ETR . . . . . . . . . . . . . . . . . . . 133line . . . . . . . . . . . . . . . . . . . 132router . . . . . . . . . . . . . . . . . . 133Services . . . . . . . . . . . . . . . . . 132trunk. . . . . . . . . . . . . . . . . . . 132USB . . . . . . . . . . . . . . . . . . . 132

system LEDs . . . . . . . . . . . . . . . . 132ground block for multiple . . . . . . . . . . . . 41installation

chassismedia modules, before inserting. . . . . . 34mounting options . . . . . . . . . . . . . 29overview . . . . . . . . . . . . . . . . . 29rack mounting . . . . . . . . . . . . . . 29tabletop installation . . . . . . . . . . . . 33wall mounting . . . . . . . . . . . . .32, 33

equipment required . . . . . . . . . . . . . 19non-S8300, prerequisites for . . . . . . . . . 20S8300 Server, prerequisites for. . . . . . . . 20session, initializing in GIW . . . . . . . . . . 212verifying in IW . . . . . . . . . . . . . . . . 205

IOLAN+ 104 terminal server, administering . . . . 253LAN

deviceadding to. . . . . . . . . . . . . . . . . 88configuring on . . . . . . . . . . . . . . 88

modules, adding to . . . . . . . . . . . . . 87license file

downloading to laptop . . . . . . . . . . . . 21required for VPN . . . . . . . . . . . . . . 21

loudspeaker paging, hooking up from . . . . . . 285main board

inserting . . . . . . . . . . . . . . . . . . 93on-board modules

adding . . . . . . . . . . . . . . . . . . 93removing. . . . . . . . . . . . . . . . . 93replacing. . . . . . . . . . . . . . . . . 93

removing . . . . . . . . . . . . . . . . . . 93mounting hardware required. . . . . . . . . . . 19music source

registeredconnecting to via KS-23395-L4 . . . . . . 284installing . . . . . . . . . . . . . . . . . 284

unregisteredconnecting to via KS-23395-L3 . . . . . . 282connecting to via KS-23395-L4 . . . . . . 283installing . . . . . . . . . . . . . . . . . 281

package, contents of . . . . . . . . . . . . . . 26

prerequisites for installing S8300 Server in . . . . 20replicating to USB mass storage device. . . . . 123restoring from USB mass storage device . . . . 123serial number . . . . . . . . . . . . . . . . . . 20specifications, technical . . . . . . . . . . . . 149

chassis . . . . . . . . . . . . . . . . . . 149clearance . . . . . . . . . . . . . . . . . 149

supported modems . . . . . . . . . . . . . . . 20telephone

adding to . . . . . . . . . . . . . . . . . . 89configuring on . . . . . . . . . . . . . . . . 89

troubleshooting . . . . . . . . . . . . . . . . 126trunk

adding to . . . . . . . . . . . . . . . . . . 90configuring on . . . . . . . . . . . . . . . . 91

USB mass storage devicebacking up to . . . . . . . . . . . . . . . 123replicating to . . . . . . . . . . . . . . . . 123restoring from . . . . . . . . . . . . . . . 123

voice modules, adding to. . . . . . . . . . . . . 87WAN

line, configuring on . . . . . . . . . . . . . . 92modules, adding to . . . . . . . . . . . . . . 87

Gateway Device Manager, launching in IW. . . . . 206Gateway Installation Wizard (GIW)

ASG authentication, enabling . . . . . . 67, 72, 228authentication file, installing . . . . . . . . . . 222basic configuration . . . . . . . . . . . . . . 209CHAP authentication, enabling . . . . . . . . . 228COM port, selecting . . . . . . . . . . . . . . 210configuration, initial gateway . . . . . . . . . . 209description . . . . . . . . . . . . . . . . . . . 81Electronic PreInstallation Worksheet, importing . 212firmware, upgrading . . . . . . . . . . . . . . 219gateway

components, initializing . . . . . . . . . . . 212firmware, upgrading . . . . . . . . . . . . 102installation session, initializing. . . . . . . . 212

installation log file, saving . . . . . . . . . . . 230IP addresses, configuring . . . . . . . . . . . 214IP phone upgrade files, uploading . . . . . . . 224license file, installing. . . . . . . . . . . . . . 221master key, changing . . . . . . . . . . . . . 220Media Gateway Controller (MGC), configuring. . 218modem

connecting after running GIW . . . . . . . . 230enabling . . . . . . . . . . . . . . . . . . 226serial

connecting . . . . . . . . . . . . . . . 230enabling . . . . . . . . . . . . . . . . . 63

testing after running GIW . . . . . . . . . . 231USB

connecting . . . . . . . . . . . . . . . 231enabling (gateway with S8300). . . . . . . 78enabling (gateway without S8300) . . . . . 68


Index

Primary Management Interface (PMI), configuring 215RAS IP address, entering . . . . . . . . . . . . 67root password, changing . . . . . . . . . . . . 229running. . . . . . . . . . . . . . . . . . . . . 209SNMP

V1 community strings, configuring . . . . . . 216V3 user, configuring . . . . . . . . . . . . . 217

usage options, selecting. . . . . . . . . . . . . 211Gigabit Ethernet port, for network switching . . . . . 47Ground block for multiple gateways . . . . . . . . . 41Ground conductors, attaching. . . . . . . . . . . . 43

general requirements . . . . . . . . . . . . . . 40location . . . . . . . . . . . . . . . . . . . . 40overview . . . . . . . . . . . . . . . . . . . . 40safety ground. . . . . . . . . . . . . . . . . . 43

Groundingapproved. . . . . . . . . . . . . . . . . . . . 42requirements . . . . . . . . . . . . . . . . . . 40Supplementary Ground Conductor . . . . . . . . 41verifying . . . . . . . . . . . . . . . . . . . . 25wires, attaching. . . . . . . . . . . . . . . . . 43

Guidedownloading latest version from website . . . . . 13related resources . . . . . . . . . . . . . . . . 15safety labels . . . . . . . . . . . . . . . . . . 13security alert labels . . . . . . . . . . . . . . . 13sending comments about . . . . . . . . . . . . 17trademarks . . . . . . . . . . . . . . . . . . . 16typographical conventions . . . . . . . . . . . . 13

Guides for cables . . . . . . . . . . . . . . . .29, 30

HHelp

resources for technical assistance . . . . . . . . 16technical assistance

international . . . . . . . . . . . . . . . . . 16within the US . . . . . . . . . . . . . . . . 16

Hot-inserting WAN and LAN modules . . . . . . . . 87Hot-swapping media modules . . . . . . . . . . . 87HyperTerminal, setting up . . . . . . . . . . . . . 249

IICC

see Internal Communications ControllerICC- VLAN

configuring using CLI . . . . . . . . . . . . . . 292ICSU

see Integrated Channel Service UnitImport name and number list in IW . . . . . . . . . 190INADS

address . . . . . . . . . . . . . . . . . . . . 22configuring in IW . . . . . . . . . . . . . . . . 170

Inserting

media modules . . . . . . . . . . . . . . . . . 39S8300 Server module . . . . . . . . . . . . . . 37

Installation808A Emergency Transfer Panel . . . . . . . . . 60after . . . . . . . . . . . . . . . . . . . . . . 83AUDIX IA770 . . . . . . . . . . . . . . . . . 238Avaya Partner Contact Closure Adjunct . . . . . . 59before you start . . . . . . . . . . . . . . . . . 19CBC . . . . . . . . . . . . . . . . . . . . . . 59conditions good for . . . . . . . . . . . . . . . 24contact closure . . . . . . . . . . . . . . . . . 59DS1 loopback jack. . . . . . . . . . . . . . . 263

selecting method . . . . . . . . . . . . . . 263with smart jack . . . . . . . . . . . . . . . 264without smart jack . . . . . . . . . . . . . 264

equipment, removing . . . . . . . . . . . . . . 85Expansion Services Module (ESM) . . . . . . . 262firmware from TFTP server on the S8300 Server 109gateway, verifying in IW . . . . . . . . . . . . 205IOLAN+ 104 terminal server, equipment required 246log file

saving in GIW . . . . . . . . . . . . . . . 230saving in IW . . . . . . . . . . . . . . . . 204

music sourcenon-registered . . . . . . . . . . . . . . . 281registered . . . . . . . . . . . . . . . . . 281

on gateway . . . . . . . . . . . . . . . 284unregistered on gateway . . . . . . . . . . 281

new, confirming in IW . . . . . . . . . . . . . 158required equipment . . . . . . . . . . . . . . . 19testing

connectivity . . . . . . . . . . . . . . . . . 83LSP failover . . . . . . . . . . . . . . . . . 84telephones. . . . . . . . . . . . . . . . . . 83trunks . . . . . . . . . . . . . . . . . . . . 83

worksheets, preparing . . . . . . . . . . . . . 105Installing the gateway chassis

see Gateway chassis installationIntegrated Channel Service Unit (ICSU) . . . . 263, 281

testing DS1 span . . . . . . . . . . . . . . . 265Internal Communications Controller (ICC) . . . . . 281Intuity AUDIX

hunt group . . . . . . . . . . . . . . . . . . 238IA770. . . . . . . . . . . . . . . . . . . . . 237LX . . . . . . . . . . . . . . . . . . . . . . 239messaging system, sources of informations . . . 287trunk group . . . . . . . . . . . . . . . . . . 238

Inventory of packed items . . . . . . . . . . . . . . 26IOLAN+ 104 terminal server . . . . . . . . . . . . 245

administering . . . . . . . . . . . . . . . . . 248first time . . . . . . . . . . . . . . . . . . 249gateway . . . . . . . . . . . . . . . . . . 253port . . . . . . . . . . . . . . . . . . . . 253

cabling connection. . . . . . . . . . . . . . . 247connecting . . . . . . . . . . . . . . . . . . 249


Index

to adjunct and LAN . . . . . . . . . . . . . 247connectivity, testing . . . . . . . . . . . . . . . 255distance from switch to LAN hub . . . . . . . . . 247HyperTerminal, setting up . . . . . . . . . . . . 249installation and administration . . . . . . . . . . 246navigating . . . . . . . . . . . . . . . . . . . 252rebooting. . . . . . . . . . . . . . . . . . . . 252troubleshooting . . . . . . . . . . . . . . . . . 256

IP addressconfiguring

in GIW . . . . . . . . . . . . . . . . . . . 214in IW . . . . . . . . . . . . . . . . . . . . 173

of C-LAN board, administering. . . . . . . . . . 256RAS, obtaining . . . . . . . . . . . . . . . . . 22

IP node names, administering . . . . . . . . . . . 256IP services, administering . . . . . . . . . . . . . 256IP telephones

connecting to gateway . . . . . . . . . . . . . 49not supported by local TFTP server . . . . . . . 113supported by local TFTP server . . . . . . . . . 113TFTP server upgrade example . . . . . . . . . 116upgrade files

downloading . . . . . . . . . . . . . . . . 114uploading in GIW . . . . . . . . . . . . . . 224uploading in IW . . . . . . . . . . . . . . . 182

upgrading . . . . . . . . . . . . . . . . . . . 115configuration files, overview . . . . . . . . . 113considerations. . . . . . . . . . . . . . . . 121examples of

4602 after file stored in NVRAM . . . . . . 1194602SW and 4602D . . . . . . . . . . . 117

firmware files, overview . . . . . . . . . . . 113troubleshooting . . . . . . . . . . . . . . . 120

ip tftp-server file-system size CLI command . . . . . 115ISDN

adapters . . . . . . . . . . . . . . . . . . . . 279BRI stations, connecting . . . . . . . . . . . . 49converters . . . . . . . . . . . . . . . . . . . 279

for multi-carrier cabinets . . . . . . . . . . . 279PRI-to-DASS. . . . . . . . . . . . . . . 279PRI-to-DPNSS . . . . . . . . . . . . . . 279

for single-carrier cabinets . . . . . . . . . . 279PRI-to-DASS. . . . . . . . . . . . . . . 279PRI-to-DPNSS . . . . . . . . . . . . . . 279

PRI-to-BRIfor multi-carrier cabinets . . . . . . . . . 279for single-carrier cabinets . . . . . . . . . 279

trunk, connecting . . . . . . . . . . . . . . . . 54

JJumper pinouts for 909A/B universal coupler . . . . 280

KKS-22911L2 power supply . . . . . . . . . . . . 280KS-23395-L3 coupler

connecting unregistered music source to gateway 282KS-23395-L4 coupler

connectingregistered music source to gateway via . . . 284unregistered music source to gateway via . . 283

LLabels

safety. . . . . . . . . . . . . . . . . . . . . . 13security alert . . . . . . . . . . . . . . . . . . 13

LANdevices

adding and connecting . . . . . . . . . . . . 88configuring. . . . . . . . . . . . . . . . . . 88testing . . . . . . . . . . . . . . . . . . . . 88

IOLAN+, connecting to. . . . . . . . . . . . . 247port

connecting computer to . . . . . . . . . . . . 47connecting IP phone to . . . . . . . . . . . . 49connecting switch to . . . . . . . . . . . . . 47

software configuration, recording information for. . 88switch, connecting to the gateway . . . . . . . . 47TFTP server, setting up on . . . . . . . . . . . 107

Laptop, configuring for IW access . . . . . . . . . 151LEDs

analog telephone port . . . . . . . . . . . . . 132media modules

MM312 . . . . . . . . . . . . . . . . . . 135MM314

alarm. . . . . . . . . . . . . . . . . . 135port . . . . . . . . . . . . . . . . . . 135

MM316alarm. . . . . . . . . . . . . . . . . . 135port . . . . . . . . . . . . . . . . . . 135

MM340 . . . . . . . . . . . . . . . . . . 136MM342 . . . . . . . . . . . . . . . . . . 137MM710 . . . . . . . . . . . . . . . . . . 138MM711 . . . . . . . . . . . . . . . . . . 140MM712 . . . . . . . . . . . . . . . . . . 141MM714 . . . . . . . . . . . . . . . . . . 142MM716 . . . . . . . . . . . . . . . . . . 144MM717 . . . . . . . . . . . . . . . . . . 146MM720 . . . . . . . . . . . . . . . . . . 147MM722 . . . . . . . . . . . . . . . . . . 148

power supply indicator . . . . . . . . . . . . . . 45S8300 Server . . . . . . . . . . . . . . . . . 135system . . . . . . . . . . . . . . . . . . . . 132

License filefor CM


Index

installing in IW. . . . . . . . . . . . . . . . 171obtaining . . . . . . . . . . . . . . . . . . 21

for gatewayinstalling in GIW . . . . . . . . . . . . . . . 221installing in IW. . . . . . . . . . . . . . . . 180obtaining . . . . . . . . . . . . . . . . . . 21

required for LSP . . . . . . . . . . . . . . . . 21Lightning exposure. . . . . . . . . . . . . . . . . 58Limitations

attendant console distance . . . . . . . . . . . 236IOLAN+ 104, distance from switch to LAN hub . . 247media module combinations . . . . . . . . . . . 35

LINE port, connecting analog telephone to. . . . . . 50Logins, administrator

adding in IW . . . . . . . . . . . . . . . . . . 152configuring in IW . . . . . . . . . . . . . . . . 152

Loopback jack . . . . . . . . . . . . . . . . . . . 263administration . . . . . . . . . . . . . . . . . 264checking local equipment integrity . . . . . . . . 265configuration

checking for DC . . . . . . . . . . . . . . . 277using fiber multiplexers . . . . . . . . . . . 276

installation . . . . . . . . . . . . . . . . . . . 263selecting method . . . . . . . . . . . . . . 263with smart jack . . . . . . . . . . . . . . . 264without smart jack . . . . . . . . . . . . . . 264

testingdata integrity . . . . . . . . . . . . . . . . 267DS1 span . . . . . . . . . . . . . . . . . . 265

from smart jack. . . . . . . . . . . . . . 270to smart jack . . . . . . . . . . . . . . . 270

with smart jack . . . . . . . . . . . . . . . 265without smart jack . . . . . . . . . . . . . . 274

Loudspeaker paging equipmentfor MCC1, SCC1, CMC1, G600, or G650 media

gateways . . . . . . . . . . . . . . . . . . . 285hooking up from gateway . . . . . . . . . . . . 285with universal coupler . . . . . . . . . . . . . . 285without paging adapter . . . . . . . . . . . . . 285without universal coupler . . . . . . . . . . . . 285

LSPAvaya Communication Manager version requirements21failover testing . . . . . . . . . . . . . . . . . 84license file requirements . . . . . . . . . . . . 21

MMain board, gateway

inserting . . . . . . . . . . . . . . . . . . . . 93on-board modules

adding . . . . . . . . . . . . . . . . . . . 93removing . . . . . . . . . . . . . . . . . . 93replacing . . . . . . . . . . . . . . . . . . 93

removing . . . . . . . . . . . . . . . . . . . . 93Main distribution frame (MDF) . . . . . . . . . . . 285

Maintenance web pages, accessing . . . . . . . . . 74Malicious call trace (MCT). . . . . . . . . . . . . 280Master key

changing in GIW . . . . . . . . . . . . . . . 220changing in IW . . . . . . . . . . . . . . . . 179

Media Gateway Controller (MGC)configuring

and upgrading in IW . . . . . . . . . . . . 156in GIW. . . . . . . . . . . . . . . . . . . 218in IW . . . . . . . . . . . . . . . . . . . 176

existing, upgrading in IW. . . . . . . . . . . . 160Media Gateway installation

before inserting media modules . . . . . . . . . 34connecting

endpoint devices . . . . . . . . . . . . . . . 47power to . . . . . . . . . . . . . . . . . . . 44

ground conductorsattaching . . . . . . . . . . . . . . . . . . 40location . . . . . . . . . . . . . . . . . . . 40

installingchassis . . . . . . . . . . . . . . . . . . . 29media modules. . . . . . . . . . . . . . . . 34power supply unit . . . . . . . . . . . . . . 33

order of installation . . . . . . . . . . . . . . . 29power supply unit, removing . . . . . . . . . . . 27Restricted Access Location . . . . . . . . . . . 41S8300 server module, inserting. . . . . . . . . . 37safety ground, connecting . . . . . . . . . . . . 43

Media module slots . . . . . . . . . . . . . . . . 131Media modules

before installing . . . . . . . . . . . . . . . . . 34combination limitations of . . . . . . . . . . . . 35firmware

upgrading via FTP/TFTP . . . . . . . . . . 104upgrading via USB device . . . . . . . . . . 111

for indoor use only. . . . . . . . . . . . . . . . 53gateway chassis, inserting into . . . . . . . . . . 39hot-swapping . . . . . . . . . . . . . . . . . . 87installing . . . . . . . . . . . . . . . . . . . . 34LAN modules, adding . . . . . . . . . . . . . . 87MM312 . . . . . . . . . . . . . . . . . . . . 135MM314 . . . . . . . . . . . . . . . . . . .47, 135MM316 . . . . . . . . . . . . . . . . . . .47, 135MM340 . . . . . . . . . . . . . . . . . . . . 136MM342 . . . . . . . . . . . . . . . . . . . . 137MM710 . . . . . . . . . . . . . . . . . . . . 138MM711 . . . . . . . . . . . . . . . . . . . . 139MM712 . . . . . . . . . . . . . . . . . . . . 140MM714 . . . . . . . . . . . . . . . . . . . . 141MM716 . . . . . . . . . . . . . . . . . . . . 142MM717 . . . . . . . . . . . . . . . . . . . . 144MM720 . . . . . . . . . . . . . . . . . . . . 147MM722 . . . . . . . . . . . . . . . . . . . . 148new, replacing and adding . . . . . . . . . . . . 87S8300 . . . . . . . . . . . . . . . . . . . . 134


Index

slot allocation. . . . . . . . . . . . . . . . . . 35slots, permitted . . . . . . . . . . . . . . . . . 35voice modules, adding . . . . . . . . . . . . . 87WAN modules, adding . . . . . . . . . . . . . 87

Memory modulesadding . . . . . . . . . . . . . . . . . . . . . 94removing . . . . . . . . . . . . . . . . . . . . 94replacing . . . . . . . . . . . . . . . . . . . . 94

MessagingIA770 . . . . . . . . . . . . . . . . . . . . . 237LX . . . . . . . . . . . . . . . . . . . . . . . 239

MGCsee Media Gateway Controller (MGC)

MM312DCP ports, connecting DCP phones to . . . . . . 52media module

description . . . . . . . . . . . . . . . . . 135LEDs . . . . . . . . . . . . . . . . . . . . 135ports . . . . . . . . . . . . . . . . . . . . 135

MM31410/100 Ethernet port, connecting external router to 58Gigabit Ethernet port

connecting computer to . . . . . . . . . . . 47connecting external router to . . . . . . . . . 58connecting server to . . . . . . . . . . . . . 48

media module . . . . . . . . . . . . . . . . . 47description . . . . . . . . . . . . . . . . . 135LEDs

alarm . . . . . . . . . . . . . . . . . . 135port . . . . . . . . . . . . . . . . . . . 135

ports . . . . . . . . . . . . . . . . . . . . 135PoE ports

connecting computers to . . . . . . . . . . . 47connecting IP phones to . . . . . . . . . . . 48connecting servers to . . . . . . . . . . . . 48for network switching . . . . . . . . . . . . 47

MM31610/100 Ethernet port, connecting external router to 58Gigabit Ethernet port

connecting computer to . . . . . . . . . . . 47connecting external router to . . . . . . . . . 58connecting server to . . . . . . . . . . . . . 48

media module . . . . . . . . . . . . . . . . . 47description . . . . . . . . . . . . . . . . . 135LEDs

alarm . . . . . . . . . . . . . . . . . . 135port . . . . . . . . . . . . . . . . . . . 135

ports . . . . . . . . . . . . . . . . . . . . 135PoE ports

connecting computers to . . . . . . . . . . . 47connecting IP phones to . . . . . . . . . . . 48connecting servers to . . . . . . . . . . . . 48for network switching . . . . . . . . . . . . 47

MM340 media moduleconnecting to WAN . . . . . . . . . . . . . . . 58

description . . . . . . . . . . . . . . . . . . 136LEDs . . . . . . . . . . . . . . . . . . . . . 136ports . . . . . . . . . . . . . . . . . . . . . 136

MM342 media moduleconnecting to WAN . . . . . . . . . . . . . . . 57description . . . . . . . . . . . . . . . . . . 137LEDs . . . . . . . . . . . . . . . . . . . . . 137ports . . . . . . . . . . . . . . . . . . . . . 137

MM710E1/T1 port, connecting E1/T1 trunk to. . . . . . . 54media module

circuit protection devices for outdoor endpoints. 56description . . . . . . . . . . . . . . . . . 138LEDs . . . . . . . . . . . . . . . . . . . 138ports . . . . . . . . . . . . . . . . . . . 138

MM711analog port

connecting analog telephone to . . . . . . . . 50connecting analog trunk to . . . . . . . . . . 53

media modulecircuit protection devices for outdoor endpoints. 56description . . . . . . . . . . . . . . . . . 139LEDs . . . . . . . . . . . . . . . . . . . 140ports . . . . . . . . . . . . . . . . . . . 139

MM712DCP ports

connecting DCP phones to . . . . . . . . . . 52for in-building use only . . . . . . . . . . . . 57

media moduledescription . . . . . . . . . . . . . . . . . 140LEDs . . . . . . . . . . . . . . . . . . . 141ports . . . . . . . . . . . . . . . . . . . 140

MM714analog trunk ports, connecting analog trunks to . . 53LINE port, connecting analog telephone to . . . . 50media module

description . . . . . . . . . . . . . . . . . 141LEDs . . . . . . . . . . . . . . . . . . . 142ports . . . . . . . . . . . . . . . . . . . 141

MM716analog port

connecting analog telephone to . . . . . . . . 50connecting analog trunk to . . . . . . . . . . 53

attaching amphenol cable to . . . . . . . . . . . 55media module

connecting to punch down block for RJ-45 or RJ-11 jacks . . . . . . . . . . . . . . . . . . . . 55

description . . . . . . . . . . . . . . . . . 142LEDs . . . . . . . . . . . . . . . . . . . 144ports . . . . . . . . . . . . . . . . . . . 143

MM717attaching amphenol cable to . . . . . . . . . . . 55DCP ports

connecting DCP phones to . . . . . . . . . . 52for in-building use only . . . . . . . . . . . . 57

media module


Index

connecting to punch down block for RJ-45 or RJ-11 jacks . . . . . . . . . . . . . . . . . . . 55


MM720ISDN ports, connecting ISDN BRI trunks to. . . . 54media module

connecting ISDN BRI stations to . . . . . . . 49description . . . . . . . . . . . . . . . . . 147LEDs . . . . . . . . . . . . . . . . . . . . 147ports . . . . . . . . . . . . . . . . . . . . 147

MM722ISDN ports, connecting ISDN BRI trunks to. . . . 54media module


Modemconfiguring in IW . . . . . . . . . . . . . . . . 183connecting

after running GIW . . . . . . . . . . . . . . 230for remote access . . . . . . . . . . . . . . 63gateway without S8300 . . . . . . . . . . . 63serial . . . . . . . . . . . . . . . . . . . . 63serial in GIW . . . . . . . . . . . . . . . . 230USB


USB in GIW . . . . . . . . . . . . . . . . . 231dial backup . . . . . . . . . . . . . . . . . . . 63enabling

for remote access . . . . . . . . . . . . . . 63gateway without S8300 . . . . . . . . . . . 63in GIW . . . . . . . . . . . . . . . . . . . 226in IW . . . . . . . . . . . . . . . . . . . . 184serial in GIW . . . . . . . . . . . . . . . . 63USB in GIW


Multi-Tech . . . . . . . . . . . . . . . . . . . 278administering . . . . . . . . . . . . . . . . 279hardware to configure . . . . . . . . . . . . 278MT5634ZBA-USB-V92. . . . . . . . . . . . 278

configuring . . . . . . . . . . . . . . . . 279MT5634ZBA-V92-GLOBAL. . . . . . . . . . 279

permanent connection for reporting alarms . . . . 63settings, Configure Server Maintenance Web page 77status, displaying in IW . . . . . . . . . . . . . 198supported by gateway. . . . . . . . . . . . . . 20testing connection

after running GIW . . . . . . . . . . . . . . 231gateway with S8300 . . . . . . . . . . . . . 79gateway without S8300 . . . . . . . . . . . 73

Mountingbrackets

for wall . . . . . . . . . . . . . . . . . . . 32attaching to gateway . . . . . . . . . . . 32

gatewayin 19-inch rack . . . . . . . . . . . . . . . . 29in rack . . . . . . . . . . . . . . . . . . . . 32on tabletop. . . . . . . . . . . . . . . . . . 33on wall . . . . . . . . . . . . . . . . . 32, 33

hardware required . . . . . . . . . . . . . . . . 19options for chassis. . . . . . . . . . . . . . . . 29

mounting brackets for rackattaching . . . . . . . . . . . . . . . . . . . . 31checks before . . . . . . . . . . . . . . . . . . 31types of . . . . . . . . . . . . . . . . . . . . . 29with cable guides . . . . . . . . . . . . . . . . 30without cable guides . . . . . . . . . . . . . . . 30

MP20 modulesadding . . . . . . . . . . . . . . . . . . . . . 94channels, number of . . . . . . . . . . . . . . . 94removing . . . . . . . . . . . . . . . . . . . . 94replacing . . . . . . . . . . . . . . . . . . . . 94

MP80 modulesadding . . . . . . . . . . . . . . . . . . . . . 94channels, number of . . . . . . . . . . . . . . . 94removing . . . . . . . . . . . . . . . . . . . . 94replacing . . . . . . . . . . . . . . . . . . . . 94

Multi-carrier cabinets, converter for . . . . . . . . 279CCSC-1 PRI-to-DASS . . . . . . . . . . . . . 279CCSC-2 PRI-to-DPNSS . . . . . . . . . . . . 279PRI-to-BRI . . . . . . . . . . . . . . . . . . 279

Multimediaendpoints . . . . . . . . . . . . . . . . . . . 262

administering . . . . . . . . . . . . . . . 262one-number complex . . . . . . . . . . 262

connecting . . . . . . . . . . . . . . . . . 262system

administering . . . . . . . . . . . . . . . 262Multimedia Call Handling (MMCH) . . . . . . . . . 262

administeringendpoints . . . . . . . . . . . . . . . . . 262one-number complex . . . . . . . . . . . . 262system . . . . . . . . . . . . . . . . . . 262

connecting endpoints . . . . . . . . . . . . . 262Expansion Services Module (ESM) . . . . . . . 262

Multiplexers, fiberconfiguring DS1 loopback

using . . . . . . . . . . . . . . . . . . . 276Multi-Tech modem

administering . . . . . . . . . . . . . . . . . 279MT5634ZBA-USB . . . . . . . . . . . . . . . . 68MT5634ZBA-USB-V92. . . . . . . . . . . 278, 279MT5634ZBA-V92-GLOBAL . . . . . . . . . . 279

Music sourcenon-registered, installing . . . . . . . . . . . . 281registered

connecting to gateway via KS-23395-L4 . . . 284


Index

installing . . . . . . . . . . . . . . . . . . 281on gateway . . . . . . . . . . . . . . . 284

unregisteredconnecting to gateway via

KS-23395-L3. . . . . . . . . . . . . . . 282KS-23395-L4. . . . . . . . . . . . . . . 283

installing on gateway. . . . . . . . . . . . . 281Music-on-hold (MOH) . . . . . . . . . . . . . . . 281

connecting FCC-registered equipment . . . . . . 281connecting non-FCC-registered equipment . . . . 281source

non-registered. . . . . . . . . . . . . . . . 281registered . . . . . . . . . . . . . . . . . . 281

connecting to gateway via KS-23395-L4 . . 284installing on gateway . . . . . . . . . . . 284

unregisteredconnecting to gateway via KS-23395-L3 . . 282connecting to gateway via KS-23395-L4 . . 283installing on gateway . . . . . . . . . . . 281

Mutual inductance coupling. . . . . . . . . . . . . 58

NName and number list, importing in IW . . . . . . . 190Network

data port, connecting to gateway. . . . . . . . . 47interface . . . . . . . . . . . . . . . . . . . . 265LAN device, testing within and without . . . . . . 88

Network Time Protocol (NTP), configuring in IW . . . 169Node names. . . . . . . . . . . . . . . . . . . . 256NVRAM

initializing with a jumper . . . . . . . . . . . . . 127restoring factory defaults in IW. . . . . . . . . . 159

OOptional

items in IW . . . . . . . . . . . . . . . . . . . 158services, configuring in IW. . . . . . . . . . . . 167

Orderinganalog trunk . . . . . . . . . . . . . . . . . . 90trunk . . . . . . . . . . . . . . . . . . . . . . 90WAN line. . . . . . . . . . . . . . . . . . . . 91

OSS alarm, configuring in IW . . . . . . . . . . . . 200Outdoor installation . . . . . . . . . . . . . . . . 56Out-of-building installation . . . . . . . . . . . . . 56Over-voltage protection . . . . . . . . . . . . . . 56

PPackage inventory . . . . . . . . . . . . . . . . . 26Paging equipment . . . . . . . . . . . . . . . . . 285

ESPA radio. . . . . . . . . . . . . . . . . . . 285external ringing . . . . . . . . . . . . . . . . . 285

loudspeakerfor MCC1, SCC1, CMC1, G600, or G650 media

gateways. . . . . . . . . . . . . . . . . 285hooking up from gateway . . . . . . . . . . 285with universal coupler . . . . . . . . . . . 285without paging adapter . . . . . . . . . . . 285

queue warning indicator . . . . . . . . . . . . 285Parameters, administering adjunct . . . . . . . . . 262Password

RAS, obtaining . . . . . . . . . . . . . . . . . 22root

changing in GIW . . . . . . . . . . . . . . 229changing in IW . . . . . . . . . . . . . . . 202

PCconnecting to the gateway . . . . . . . . . . . . 47downloading gateway firmware to local . . . . . .112

Phone message files, installing in IW . . . . . . . 165Physical description of gateway front panel. . . . . 131Planning

documentation . . . . . . . . . . . . . . . . . 19installation . . . . . . . . . . . . . . . . . . . 19

Platform, hardware, for harsh environment . . . . . . 29Plugging in

endpoint devices . . . . . . . . . . . . . . . . 47the gateway. . . . . . . . . . . . . . . . . . . 44

Plywood boarddimensions . . . . . . . . . . . . . . . . . . . 19using to wall-mount gateway . . . . . . . . . . . 33

PoE portsconnecting

computers to. . . . . . . . . . . . . . . . . 47IP phones to . . . . . . . . . . . . . . . . . 48servers to . . . . . . . . . . . . . . . . . . 48

for network switching . . . . . . . . . . . . . . 47Ports

analog telephone . . . . . . . . . . . . . . . 132CCA . . . . . . . . . . . . . . . . . . . . . 133COM, selecting in GIW . . . . . . . . . . . . 210CON . . . . . . . . . . . . . . . . . . . . . 132connecting

data and voice devices to . . . . . . . . . . . 47endpoint devices to. . . . . . . . . . . . . . 47

contact closure . . . . . . . . . . . . . . . . 133ETH LAN . . . . . . . . . . . . . . . . . . . 133ETH WAN . . . . . . . . . . . . . . . . . . 133ETR . . . . . . . . . . . . . . . . . . . . . 133IOLAN+ 104 terminal server

administering . . . . . . . . . . . . . . . 253connectivity testing . . . . . . . . . . . . . 255

line . . . . . . . . . . . . . . . . . . . . . . 132MM312 . . . . . . . . . . . . . . . . . . . . 135MM314 . . . . . . . . . . . . . . . . . . . . 135MM316 . . . . . . . . . . . . . . . . . . . . 135MM340 . . . . . . . . . . . . . . . . . . . . 136MM342 . . . . . . . . . . . . . . . . . . . . 137MM710 . . . . . . . . . . . . . . . . . . . . 138


Index

MM711. . . . . . . . . . . . . . . . . . . . . 139MM712. . . . . . . . . . . . . . . . . . . . . 140MM714. . . . . . . . . . . . . . . . . . . . . 141MM716. . . . . . . . . . . . . . . . . . . . . 143MM717. . . . . . . . . . . . . . . . . . . . . 145MM720. . . . . . . . . . . . . . . . . . . . . 147MM722. . . . . . . . . . . . . . . . . . . . . 148router . . . . . . . . . . . . . . . . . . . . . 133S8300 Server. . . . . . . . . . . . . . . . . . 135

LEDs . . . . . . . . . . . . . . . . . . . . 135Services . . . . . . . . . . . . . . . . . . . . 132switch . . . . . . . . . . . . . . . . . . . . . 133switch or network data, connecting. . . . . . . . 47trunk . . . . . . . . . . . . . . . . . . . . . . 132USB . . . . . . . . . . . . . . . . . . . . . . 132

Positioninggateway in rack. . . . . . . . . . . . . . . . . 32S8300 media module . . . . . . . . . . . . . . 37

Powerattendant console

auxiliary. . . . . . . . . . . . . . . . . . . 235connection

adjunct . . . . . . . . . . . . . . . . . . . 234end-to-end . . . . . . . . . . . . . . . . 235

to gateway . . . . . . . . . . . . . . . . . 44cords

obtaining . . . . . . . . . . . . . . . . . . 150specifications . . . . . . . . . . . . . . . . 150

local and phantom . . . . . . . . . . . . . . . 236outlets, checking available number of . . . . . . 25verification . . . . . . . . . . . . . . . . . . . 25

Power supplyKS-22911L2 . . . . . . . . . . . . . . . . . . 280unit

installing . . . . . . . . . . . . . . . . . . 33LED indication. . . . . . . . . . . . . . . . 45removing . . . . . . . . . . . . . . . . . . 27replacing . . . . . . . . . . . . . . . . . . 97

Pre-installation activities . . . . . . . . . . . . . . 19Preinstallation worksheet

see Electronic Preinstallation Worksheet (EPW)Preparation

installation worksheets . . . . . . . . . . . . . 105Server Values worksheets. . . . . . . . . . . . 106telephone configuration . . . . . . . . . . . . . 89trunk configuration . . . . . . . . . . . . . . . 91WAN line configuration . . . . . . . . . . . . . 92

Primary controllerconfiguring IP addresses in IW . . . . . . . . . 166upgrading gateway firmware from . . . . . . . . 102

Primary Management Interface (PMI)configuring in GIW . . . . . . . . . . . . . . . 215configuring in IW . . . . . . . . . . . . . . . . 174configuring using CLI . . . . . . . . . . . . . . 292management functions . . . . . . . . . . . . . 173

Printersadjunct parameters, administering . . . . . . . 262connecting to gateway via TCP/IP . . . . . . . 262PMS journal and PMS log . . . . . . . . . . . 262system . . . . . . . . . . . . . . . . . . . . 262

switch-to-adjunct link, testing . . . . . . . . 262Product ID, changing in IW . . . . . . . . . . . . 160

QQueue warning indicator . . . . . . . . . . . . . 285

RRack mounting

brackets . . . . . . . . . . . . . . . . . . . . 29the gateway chassis . . . . . . . . . . . . . . . 29

RASIP address

entering in GIW . . . . . . . . . . . . . 67, 72obtaining . . . . . . . . . . . . . . . . . . 22

password, obtaining . . . . . . . . . . . . . . . 22RDTT

see Reliable Data Transport Tool (RDTT)Reliable Data Transport Tool (RDTT)

administering . . . . . . . . . . . . . . . . . 262downloading . . . . . . . . . . . . . . . . . 261installing . . . . . . . . . . . . . . . . . . . 261overview . . . . . . . . . . . . . . . . . . . 261package contents . . . . . . . . . . . . . . . 261

Reliable Session-Layer Protocol (RSP) tool . . . . 262Remote

access, enabling . . . . . . . . . . . . . . . . 63configuration via Telnet . . . . . . . . . . . . 100

Removing installation equipment . . . . . . . . . . 85Replacing

endpoint devices . . . . . . . . . . . . . . . . 87fan tray . . . . . . . . . . . . . . . . . . . . . 96main board on-board module, gateway . . . . . . 93main board, gateway . . . . . . . . . . . . . . 93memory module . . . . . . . . . . . . . . . . . 94power supply unit . . . . . . . . . . . . . . . . 97VoIP modules, MP20 and MP80 . . . . . . . . . 94

Replicating the gateway to USB mass storage device 123Required

equipment . . . . . . . . . . . . . . . . . . . 19for installing IOLAN+ 104 terminal server . . 246

hardware for Multi-Tech modem . . . . . . . . 278items in IW . . . . . . . . . . . . . . . . . . 158

Reset button . . . . . . . . . . . . . . . . . . . 134reset CLI command. . . . . . . . . . . . . . . . .115Restoring the gateway from USB mass storage device123Restricted Access Location . . . . . . . . . . . . . 41RFA access . . . . . . . . . . . . . . . . . . . . 20RJ-45 splitter for connecting two BRI stations. . . . . 49


Index

Root passwordchanging in GIW . . . . . . . . . . . . . . . . 229changing in IW . . . . . . . . . . . . . . . . . 202

Routerconnecting external to gateway . . . . . . . . . 58ports . . . . . . . . . . . . . . . . . . . . . . 133

RST button . . . . . . . . . . . . . . . . . . . . 134Rubber feet, affixing to stand gateway on table . . . 33Ruggedized mounting solution for harsh environment 29Running

Avaya Installation Wizard (IW) . . . . . . . . . . 153Running Gateway Installation Wizard (GIW) . . . . . 209

SS8300

ServerAvaya Communication Manager software, upgrading

via . . . . . . . . . . . . . . . . . . . . 99call center solution. . . . . . . . . . . . . . 239connecting to

gateway . . . . . . . . . . . . . . . . . 48connecting to USB modem . . . . . . . . . . 78copying firmware to . . . . . . . . . . . . . 110gateway chassis, inserting into . . . . . . . . 37installing firmware from the TFTP server on . . 109IP addresses, configuring in IW. . . . . . . . 166overview . . . . . . . . . . . . . . . . . . 134ports

description . . . . . . . . . . . . . . . . 135LEDs . . . . . . . . . . . . . . . . . . 135

prerequisites for installing in gateway . . . . . 20testing . . . . . . . . . . . . . . . . . . . 88

softwareupgrading using IW or the Upgrade tool . . . . 100

upgrades for IA770 Intuity AUDIX . . . . . . . . 238Safety

ground, connecting . . . . . . . . . . . . . . . 43labels . . . . . . . . . . . . . . . . . . . . . 13

save translation lsp CLI command . . . . . . . . . 84Screws required for mounting gateway . . . . . . . 19Securing amphenol cable to MM716 or MM717 . . . 55Security alert labels . . . . . . . . . . . . . . . . 13Serial

cableDTE V.35 . . . . . . . . . . . . . . . . . . 57DTE X.21 . . . . . . . . . . . . . . . . . . 57

modemconnecting and enabling . . . . . . . . . . . 63connecting in GIW . . . . . . . . . . . . . . 230

Serial number of gateway . . . . . . . . . . . . . 20viewing in IW . . . . . . . . . . . . . . . . . . 155

Server see S8300 Server

Server IP addresses, configuring in IW . . . . . . . 166

Server Values worksheets, preparing . . . . . . . 106Services

optional, configuring in IW . . . . . . . . . . . 167port. . . . . . . . . . . . . . . . . . . . . . 132

connecting a computer to . . . . . . . . . . . 48show application-memory CLI command . . . . . . .115show controllers CLI command . . . . . . . . . . 127show interfaces serial CLI command. . . . . . . . 127Single Sign-On (SSO) . . . . . . . . . . . . . . . 20Single-carrier cabinets, converter for

CCSC-1 PRI-to-DASS . . . . . . . . . . . . . 279CCSC-2 PRI-to-DPNSS . . . . . . . . . . . . 279PRI-to-BRI . . . . . . . . . . . . . . . . . . 279

Siteconditions, checking before installation . . . . . . 24requirements . . . . . . . . . . . . . . . . . . 24

Smart jackinstalling DS1 loopback jack with . . . . . . . . 264testing DS1 loopback jack with . . . . . . . . . 265

Sneak-current protection . . . . . . . . . . . . . . 56SNMP

alarm, configuring in IW . . . . . . . . . . . . 201V1 community strings, configuring in GIW. . . . 216V1 community strings, configuring in IW . . . . 175V3 user, configuring in GIW . . . . . . . . . . 217V3 user, configuring in IW . . . . . . . . . . . 175

Softwareconfiguration . . . . . . . . . . . . . . . . . . 81

recording LAN information for . . . . . . . . . 88recording telephone information for . . . . . . 89recording trunk information for . . . . . . . . 91recording WAN information for . . . . . . . . 92

Reliable Data Transport Tool (RDTT)administering . . . . . . . . . . . . . . . 262downloading . . . . . . . . . . . . . . . . 261installing . . . . . . . . . . . . . . . . . . 261overview. . . . . . . . . . . . . . . . . . 261package contents . . . . . . . . . . . . . 261

upgradingAvaya CM via S8300 Server . . . . . . . . . 99overview. . . . . . . . . . . . . . . . . . . 99with CD-ROM drive. . . . . . . . . . . . . . 99without CD-ROM drive . . . . . . . . . . . 100

version, viewing in IW . . . . . . . . . . . . . 155Software Update Manager . . . . . . . . . . . . 101Specifications, technical. . . . . . . . . . . . . . 149

chassis . . . . . . . . . . . . . . . . . . . . 149clearance . . . . . . . . . . . . . . . . . . . 149power cord . . . . . . . . . . . . . . . . . . 150

Supplementary Ground Conductor. . . . . . . . . . 41if ground block is used . . . . . . . . . . . . . . 43if ground block not used . . . . . . . . . . . . . 44

Survivability by modem dial backup . . . . . . . . . 63Switch

connecting to computer . . . . . . . . . . . . . 47


Index

connecting to gateway . . . . . . . . . . . . . 47connecting to server . . . . . . . . . . . . . . 48external Avaya Ethernet. . . . . . . . . . . . . 48P130. . . . . . . . . . . . . . . . . . . . . . 48P130PWR . . . . . . . . . . . . . . . . . . . 48P333PWR . . . . . . . . . . . . . . . . . . . 48P333T . . . . . . . . . . . . . . . . . . . . . 48port . . . . . . . . . . . . . . . . . . . . . . 133testing . . . . . . . . . . . . . . . . . . . . . 88

Switch-to-adjunct link, testingCDR . . . . . . . . . . . . . . . . . . . . . . 260printer . . . . . . . . . . . . . . . . . . . . . 262

System data, viewing in IW . . . . . . . . . . . . . 155

TT1

DS1 span . . . . . . . . . . . . . . . . . . . 263trunk, connecting . . . . . . . . . . . . . . . . 54

Tabletop installation of the gateway chassis . . . . . 33Task list . . . . . . . . . . . . . . . . . . . . . . 262TCP/IP

connections . . . . . . . . . . . . . . . . . . 262printers

connecting to gateway via . . . . . . . . . . 262settings for Maintenance web pages . . . . . . . 74task list. . . . . . . . . . . . . . . . . . . . . 262

Technical assistanceinternational . . . . . . . . . . . . . . . . . . 16resources . . . . . . . . . . . . . . . . . . . 16within the US . . . . . . . . . . . . . . . . . . 16

Technical specifications . . . . . . . . . . . . . . 149chassis. . . . . . . . . . . . . . . . . . . . . 149clearance . . . . . . . . . . . . . . . . . . . 149power cord . . . . . . . . . . . . . . . . . . . 150

Telephoneadding to gateway . . . . . . . . . . . . . . . 89configuring . . . . . . . . . . . . . . . . . . . 89connecting . . . . . . . . . . . . . . . . . . . 89IP, connecting to gateway . . . . . . . . . . . . 49software configuration, recording information for . 89testing . . . . . . . . . . . . . . . . . . . . . 89

after installation . . . . . . . . . . . . . . . 83troubleshooting

one . . . . . . . . . . . . . . . . . . . . . 125several . . . . . . . . . . . . . . . . . . . 126

Telephonyparameters, configuring in IW . . . . . . . . . . 186translation defaults, configuring in IW . . . . . . 187

Telnet, remote configuration via. . . . . . . . . . . 100Terminal server

administeringIP node names . . . . . . . . . . . . . . . 256IP services . . . . . . . . . . . . . . . . . 256

IOLAN+ 104 . . . . . . . . . . . . . . . . . . 245

administering . . . . . . . . . . . . . . . 248first time . . . . . . . . . . . . . . . . 249gateway . . . . . . . . . . . . . . . . 253port . . . . . . . . . . . . . . . . . . 253

cabling connection . . . . . . . . . . . . . 247connecting . . . . . . . . . . . . . . . . . 249

to adjunct and LAN . . . . . . . . . . . 247connectivity, testing . . . . . . . . . . . . 255distance from switch to LAN hub . . . . . . 247HyperTerminal, setting up. . . . . . . . . . 249installation and administration . . . . . . . . 246navigating . . . . . . . . . . . . . . . . . 252rebooting . . . . . . . . . . . . . . . . . 252troubleshooting . . . . . . . . . . . . . . 256

overview . . . . . . . . . . . . . . . . . . . 245Terminating telephones on the MM717 and MM716. . 55Testing

computer type data device . . . . . . . . . . . . 88DS1

loopback jack with smart jack . . . . . . . . 265loopback jack without smart jack . . . . . . 274span

from ISCU . . . . . . . . . . . . . . . 265from smart jack . . . . . . . . . . . . . 270to smart jack . . . . . . . . . . . . . . 270

Expansion Services Module (ESM) . . . . . . . 262installation

connectivity . . . . . . . . . . . . . . . . . 83LSP failover . . . . . . . . . . . . . . . . . 84overview. . . . . . . . . . . . . . . . . . . 83telephones. . . . . . . . . . . . . . . . . . 83trunks . . . . . . . . . . . . . . . . . . . . 83

integrity of data sent over loop . . . . . . . . . 267IOLAN+ 104 connectivity. . . . . . . . . . . . 255LAN device . . . . . . . . . . . . . . . . . . . 88modem connection

gateway with S8300 . . . . . . . . . . . . . 79gateway without S8300 . . . . . . . . . . . . 73

server type data device . . . . . . . . . . . . . 88switch type data device . . . . . . . . . . . . . 88switch-to-adjunct link

CDR. . . . . . . . . . . . . . . . . . . . 260printer . . . . . . . . . . . . . . . . . . . 262

telephone . . . . . . . . . . . . . . . . . . . . 89trunk . . . . . . . . . . . . . . . . . . . . . . 91WAN link . . . . . . . . . . . . . . . . . . . . 92

TFTP serverdownloading gateway firmware to local . . . . . 108for upgrading IP phones . . . . . . . . . . . . .113installing firmware from, on the S8300 Server . . 109IP telephones

not supported by local . . . . . . . . . . . .113supported by local . . . . . . . . . . . . . .113upgrade example. . . . . . . . . . . . . . .116

setting up


Index

on the LAN . . . . . . . . . . . . . . . . . 107overview . . . . . . . . . . . . . . . . . . 107

uploading IP phone upgrade filesin GIW . . . . . . . . . . . . . . . . . . . 224in IW . . . . . . . . . . . . . . . . . . . . 182

TN2183 analog line circuit pack . . . . . . . . . . . 285TNPRI/BRI converter


Trademarks . . . . . . . . . . . . . . . . . . . . 16Translations, generating information in IW . . . . . . 170Troubleshooting

CLI not accessible . . . . . . . . . . . . . . . 127Expansion Services Module (ESM) . . . . . . . 262gateway has no power . . . . . . . . . . . . . 126IOLAN+ 104 terminal server . . . . . . . . . . . 256IP telephone upgrades . . . . . . . . . . . . . 120overview . . . . . . . . . . . . . . . . . . . . 125telephone

one stops working . . . . . . . . . . . . . . 125several stop working . . . . . . . . . . . . . 126

trunk stops working . . . . . . . . . . . . . . . 126WAN line stops working . . . . . . . . . . . . . 127

Trunkadding

in IW . . . . . . . . . . . . . . . . . . . . 192to gateway . . . . . . . . . . . . . . . . . 90

analogconnecting to TRUNK port . . . . . . . . . . 53ordering. . . . . . . . . . . . . . . . . . . 90

configuringin IW . . . . . . . . . . . . . . . . . . . . 190on gateway . . . . . . . . . . . . . . . . . 91

connecting . . . . . . . . . . . . . . . . . . . 90list of, viewing in IW. . . . . . . . . . . . . . . 191media module, configuring in IW . . . . . . . . . 197modifying in IW

IP route configuration . . . . . . . . . . . . 194parameters . . . . . . . . . . . . . . . . . 193

ordering . . . . . . . . . . . . . . . . . . . . 90removing in IW . . . . . . . . . . . . . . . . . 196software configuration, recording information for . 91status, displaying in IW . . . . . . . . . . . . . 195testing . . . . . . . . . . . . . . . . . . . . . 91

after installation . . . . . . . . . . . . . . . 83troubleshooting . . . . . . . . . . . . . . . . . 126

TRUNK port, connecting analog trunk to. . . . . . . 53

UUniform Call Distribution/Direct Departmental Calling (UCD/

DDC) queue . . . . . . . . . . . . . . . . . . . 285Uninterruptable Power Supply

see UPSUniversal coupler

909A/B . . . . . . . . . . . . . . . . . . . . 280Unpacking . . . . . . . . . . . . . . . . . . . . . 27Upgrading

Avaya Communication Manager softwarein IW . . . . . . . . . . . . . . . . . . . 103overview. . . . . . . . . . . . . . . . . . . 99

firmwareexample

using a USB device . . . . . . . . . . . . 111using FTP/TFTP . . . . . . . . . . . . 105

in GIW. . . . . . . . . . . . . . . . . . . 219in IW . . . . . . . . . . . . . . . . . . . 177installation worksheets, preparing . . . . . . 105Server Values worksheets, preparing . . . . 106

gateway firmwareCLI commands for, via FTP/TFTP . . . . . . 104downloading

to local PC . . . . . . . . . . . . . . . .112to local TFTP server. . . . . . . . . . . 108

from primary controller . . . . . . . . . . . 102in GIW. . . . . . . . . . . . . . . . . . . 102in IW . . . . . . . . . . . . . . . . . . . 103overview. . . . . . . . . . . . . . . . . . 101using CLI

via USB device . . . . . . . . . . . . . . 111using CLI via FTP/TFTP . . . . . . . . . . 104with Avaya Software Update Manager . . . . 101

IP telephones . . . . . . . . . . . . . . . . . .115configuration files

downloading . . . . . . . . . . . . . . .114overview . . . . . . . . . . . . . . . . .113

considerations . . . . . . . . . . . . . . . 121examples of

4602 after file stored in NVRAM . . . . . .1194602SW and 4602D. . . . . . . . . . . .117

firmware files, overview . . . . . . . . . . . .113troubleshooting . . . . . . . . . . . . . . 120

media modules and devices . . . . . . . . . . . 87software

S8300, using IW or the Upgrade tool . . . . 100with CD-ROM drive. . . . . . . . . . . . . . 99without CD-ROM drive . . . . . . . . . . . 100

Uploading firmware in IW . . . . . . . . . . . . . 178UPS

configuring in IW . . . . . . . . . . . . . . . 168models . . . . . . . . . . . . . . . . . . . . 242overview . . . . . . . . . . . . . . . . . . . 242specifications . . . . . . . . . . . . . . . . . 242

Usage optionsselecting in GIW. . . . . . . . . . . . . . . . .211selecting in IW . . . . . . . . . . . . . . . . 157

USBmass storage device

backing up the gateway. . . . . . . . . . . 123CLI commands for upgrading firmware. . . . . 111


Index

example of upgrading firmware . . . . . . . . 111replicating the gateway . . . . . . . . . . . 123restoring the gateway . . . . . . . . . . . . 123upgrading gateway firmware using CLI . . . . 111

modemconnecting in GIW . . . . . . . . . . . . . . 231


enabling in GIWgateway with S8300 . . . . . . . . . . . 78gateway without S8300 . . . . . . . . . . 68

supported by gateway . . . . . . . . . . . . 68port . . . . . . . . . . . . . . . . . . . . . . 132

USP port, on MM342 media module. . . . . . . . . 57

VVerifying

environmental conditions before installation . . . 24grounding . . . . . . . . . . . . . . . . . . . 25power . . . . . . . . . . . . . . . . . . . . . 25

VoIP modulesadding . . . . . . . . . . . . . . . . . . . . . 94removing . . . . . . . . . . . . . . . . . . . . 94replacing . . . . . . . . . . . . . . . . . . . . 94

VPN license file . . . . . . . . . . . . . . . . . . 21

WWall mounting

brackets . . . . . . . . . . . . . . . . . . . . 32the gateway chassis . . . . . . . . . . . . .32, 33

WANconfiguring on gateway . . . . . . . . . . . . . 92connecting . . . . . . . . . . . . . . . . . . . 57E1/T1 port . . . . . . . . . . . . . . . . . . . 58link

connecting . . . . . . . . . . . . . . . . . 57connecting to E1/T1 port . . . . . . . . . . . 58connecting to USP port . . . . . . . . . . . 57ordering. . . . . . . . . . . . . . . . . . . 91preparing for configuration . . . . . . . . . . 92testing . . . . . . . . . . . . . . . . . . . 92

modulesadding . . . . . . . . . . . . . . . . . . . 87hot-inserting. . . . . . . . . . . . . . . . . 87

software configuration, recording information for . 92troubleshooting . . . . . . . . . . . . . . . . . 127

Wideband endpointsnon-signaling . . . . . . . . . . . . . . . . . . 262overview . . . . . . . . . . . . . . . . . . . . 262remote port module . . . . . . . . . . . . . . . 262signaling . . . . . . . . . . . . . . . . . . . . 262

Worksheetsinstallation, preparing . . . . . . . . . . . . . . 105

Server Values, preparing. . . . . . . . . . . . 106

g450 Upgrade

Documents

Transcript of g450 Upgrade