Page 1 Maintenance for the Avaya G250 and Avaya G350 Media Gateways 03-300438 Issue 1.1 June 2005...
Page 2 • System administration documents Warranty • Security documents Avaya Inc. provides a limited warranty on this product. Refer to your • Hardware-/software-based security tools sales agreement to establish the terms of the limited warranty. In • Shared information between you and your peers addition, Avaya’s standard warranty language as well as information...
Page 3 A reorder tone is received. operations or procedures that could affect the operation of the Avaya attests that this registered equipment is capable of providing users equipment. If this happens, the telephone company will provide advance access to interstate providers of operator services through the use of notice in order for you to make necessary modifications to maintain access codes.
Page 4 Declarations of Conformity United States FCC Part 68 Supplier’s Declaration of Conformity (SDoC) Avaya Inc. in the United States of America hereby certifies that the equipment described in this document and bearing a TIA TSB-168 label identification number complies with the FCC’s Rules and Regulations 47 CFR Part 68, and the Administrative Council on Terminal Attachments (ACTA) adopted technical criteria.
Page 5: Table Of Contents
Media module replacement ......Permitted Slots in the G250 ......
Page 6 Dynamic Call Admission Control (CAC) ..... . . Enabling Dynamic CAC on the G250/G350....
Page 7 Maintenance Objects ....... . . Avaya G250/G350 Media Gateway MOs .....
Page 8 Port Audit Update Test (#36) ......8 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 9 Contents ISDN-LNK (ISDN-PRI Signaling Link Port) ..... . Hardware Error Log Entries and Test to Clear Values ... . . System Technician-Demanded Tests: Descriptions and Error Codes .
Page 10 Connect laptop to Services port of S8300 ....Connect laptop to the G250/G350 Console port ....
Page 11 Device Manager (G350 only) ......Avaya Site Administration ......
Page 12 Alarm format ........G250/G350 traps and resolutions......
Page 13: About This Book
You can download the latest version of the Maintenance for the Avaya G250 and Avaya G350 Media Gateways from the Avaya web site. You must have access to the Internet, and a copy of Acrobat Reader must be installed on your personal computer.
Page 14: Downloading This Book
- PDF Format to download the book in regular PDF format - ZIP Format to download the book as a zipped PDF file Related resources For more information on the Avaya G250 and G350 Media Gateways and related features, see the following books: Title...
Page 15: Technical Assistance
Toll fraud, call Avaya Toll Fraud Intervention at 1-800-643-2353 ● International For all international resources, contact your local Avaya authorized dealer for additional help. Trademarks All trademarks identified by the ® or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.
Page 16: Sending Us Comments
Fax, send your comments to: ● 1-303-538-1741 Ensure that you mention the name and number of this book, Maintenance for the Avaya G250 and Avaya G350 Media Gateways, 03-300438. 16 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 17: Chapter 1: Maintenance Overview
Media Gateways, Media Servers, and Software. The Media Server functions as a Media Gateway Controller (MGC). Integration with your network system The G250/G350 with a Media Server incorporates the following features that help it fit easily into your system: It is built around open IP standards (H.248 and H.323).
Page 18: Maintenance Strategy
Upgrade Tool and Worksheets, 555-245-747. Maintenance of the G250/G350 begins with regular monitoring of the hardware components and software systems of the media gateway. The G250/G350 and its media modules can be monitored in several ways, including: Inspecting the G250/G350 and media module LEDs ●...
Page 19: Media Module Maintenance
DEFINITY server circuit pack counterpart. Field replacement of media modules can be performed in many cases without removing power to the G250/G350 (hot swapping). Note: The G250 only supports the S8300 Media Server and the WAN media modules Note: (MM340 and MM342). However, the G250 also includes built-in functionality that provides the equivalent of a virtual analog media module.
Page 20: Hot Swapping
The S8300 Media Server can be a primary MGC for a network of IP endpoints Note: and Avaya G250 and G350 Media Gateways, or it can be configured as a Local Survivable Processor (LSP), to become active only if connectivity to the primary MGC is lost.
Page 21: Leds
Troubleshooting and diagnostic tasks can be supported by software accessed by laptops in the field or remotely from an administrator’s computer. The S8300 Media Server and Avaya G250 and G350 Media Gateways employ LEDs in the following areas: G250/G350 LEDs ●...
Page 22: Maintenance Web Interface
Avaya G250/G350 Media Gateway on the corporate local area network (LAN). This administration interface via the web is an efficient way to configure the Avaya G250 and G350 Media Gateways, the Media Server, and media modules. In addition to initial...
Page 23: Avaya G250/G350 Media Gateway Cli
03-300394. Plugging in and unplugging the G250/G350 The Avaya G250 and G350 Media Gateways contain a detachable power cord. You can power the device by plugging the power cord into the G250/G350 receptacle, then plugging the cord into the wall outlet.
Page 24: Useful Terms
Avaya Communication Manager MultiVantage, Avaya Call Processing S8300 Media Server ICC, Internal Call Controller S8500 or S8700/S8710 Media Server ECC, External Call Controller (Could also be a non-co-resident S8300 Media Server) 24 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 25: Chapter 2: G250/G350 Component Maintenance
Communication Manager 3.0, Media Gateways and Servers, 03-300430. Power cords Each Avaya G250/G350 Media Gateway ships with one power cord, suitable for the local region. If the power cord provided with the equipment does not have the correct plug configuration needed in a particular country, please refer to the cord set specifications below:...
Page 26: Replacing The Avaya G250/G350 Media Gateway
Server, various media modules) may be reused in the replacement G250/G350. To replace the G250/G350: 1. If the original G250/G350 is still in operation, backup the configuration files to an FTP or TFTP server on the customer LAN. To backup the configuration files, use one of the following commands: copy startup-config ftp <filename>...
Page 27: Replacing The S8300 Media Server
Avaya S8300 Media Server with the G700 Media Gateway, 03-300538. Media modules supported in the G250 The G250 supports the S8300 Media Server and the MM340 and MM342 WAN media modules only. For information on these media modules, as well as the media modules supported by the...
Page 28 G250/G350 component maintenance Note: The MM760 media module is currently not supported by either the G250 or the Note: G350. Table 4: G350 supported media modules Media Module Description S8300 Media server Telephony media modules MM711 8 universal analog ports...
Page 29 G250/G350 component maintenance Note: Material Codes change frequently. To obtain the most up-to-date Material Codes, Note: refer to the Avaya web site. Table 5: Equipment List: Media Modules Media Modules E1/T1 Media Module Material Code: Apparatus Code: Optional 700315567 MM710 DEF DS1 LOOPBACK JACK 700A Provides the ability to remotely troubleshoot the E1/T1 media module.
Page 30 Apparatus Code: Optional 700281728 MM314 E1/T1 WAN Media Module Material Code: Apparatus Code: Optional 700281702 MM340 USP WAN Media Module Material Code: Apparatus Code: Optional 700281710 MM342 2 of 2 30 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 31: Media Module Replacement
Avaya Communication Manager is necessary when you install an MM710, MM720, and MM722 media module. You can hot-insert data modules. This means you can add a data module to the Avaya G250/ G350 Media Gateway while the system is running. However, the G250/G350 resets when you add the module.
Page 32: Permitted Slots In The G250
G250/G350 component maintenance Permitted Slots in the G250 The G250 chassis has two media module slots, marked V1 and V2. Slot V1 is for an S8300 Media Server. Slot V2 is for a WAN media module (MM340 or MM342). Permitted Slots in the G350 The G350 chassis has six media module slots, marked V1, V2, V3, V4, V5, V6.
Page 33: Combination Limitations In The G350
Maximum of one of the following modules: MM712 and MM717 (you can combine this ● module with an MM312) The G250 supports a maximum of one S8300 Media Server (slot V1) and one WAN media module (slot V2). For detailed descriptions of the media modules see Hardware Guide for Avaya Communication Manager, 555-233-200.
Page 34 Figure 1: Inserting Media Modules into the G350 34 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 35: Facility Test Call
Facility test call Figure 2: Inserting Media Modules into the G250 Facility test call The facility test call feature allows you to use a voice terminal to make test calls to specific trunks within the system. The test call verifies that the accessed component is functioning properly.
Page 36 - X = Slot number (1 - 5, if no S8300/LSP in Slot 1) - yy = Circuit number Circuit range depends upon the media module on which the trunk is set up. For the Avaya Analog media module (MM711), the range is 1-8; for the Avaya E1/T1 media module (MM710), the range could be 1-23, 1-24, 1-31, or 1-32, depending upon the type of translation and signaling.
Page 37 Facility test call 4. Listen for one of the following tones: Tone Description / Steps Dial tone or silence The trunk is connected. Go to Step 5. Busy tone The trunk is either busy processing a call or is out of service.
Page 38: Setting G350 Synchronization
G250/G350 component maintenance Setting G350 synchronization If the Avaya G350 Media Gateway contains an MM710 E1/T1 media module, it is usually advisable to set the MM710 up as the primary synchronization source for the G350. In so doing, clock sync signals from the Central Office (CO) are used by the MM710 to synchronize all operations of the G350.
Page 39: Viewing G350 Sync Sources
Setting G350 synchronization If the Avaya G350 Media Gateway contains a second MM710 media module, type set sync interface secondary. If, for any reason, the primary MM710 media module cannot function as the clock synchronization source, the system defaults to the secondary MM710 media module for that function.
Page 40 The results from the above command are shown in Table 10: TEST RESULTS on page 40: Table 10: TEST RESULTS Port Maintenance Alt. Name Test No. Error Code Name Result 001V4 MG-DS1 PASS Command successfully completed 40 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 41 Setting G350 synchronization If a secondary sync source is similarly provisioned: Table 11: G350-001# set sync interface secondary v3 G350-001# show sync timing SOURCE STATUS FAILURE Primary Active None Secondary Standby None Local Standby None To activate the secondary sync source: Table 12: G350-001# set sync source secondary G350-001# show sync timing SOURCE...
Page 42 Table 15: G350-001# show sync timing SOURCE STATUS FAILURE Primary Standby Out of Lock Secondary Active None Local Standby None Note that primary and local are standby because they are provisioned as fail overs. 42 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 43: Ip Telephones
IP telephones IP telephones The Avaya 4600-Series IP Telephones are relatively trouble-free. Table 16: IP Phone Problems and Solutions on page 43 provides the most common problems an end user might encounter. For other IP Telephone questions or problems, contact your Telephone System Administrator.
Page 44 Reset or power cycle the phone. See your Telephone System Administrator if the above steps do not produce the desired result. Check the status of the VoIP board. 2 of 3 44 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 45 If the connection is secure, verify that you works properly are using an approved headset, base unit and/or adapter, as described in the list of approved Avaya Communication compatible Headsets. Phone does not ring If you have a 4612 or 4624 IP Telephone, use the Menu to access the RngOf (Ringer Off) feature;...
Page 46: Reset And Power Cycle
4. Press # to restart the phone or * to terminate the restart and restore the phone to its previous state. Note: Any reset/restart of your phone may take a few minutes. Note: 46 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 47: Power Cycle The Phone
IP telephones Power cycle the phone Use the power cycle only if the basic or programmed reset procedure cannot be performed or does not correct the problem. To power cycle the phone 1. Unplug the phone and plug it back in. The phone connection is re-established.
Page 48 G250/G350 component maintenance 48 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 49: Chapter 3: Avaya Communication Manager Controlled Maintenance
Avaya Communication Manager SAT gives you Note: complete information, including whether or not stations have been administered on a port. show mg list_config on the G250/G350 CLI gives you information for the installed equipment in that G250/G350. Maintenance commands DEFINITY server-experienced users will find that G250/G350 components and media modules function, and are maintained, in a similar way as their DEFINITY server counterparts.
Page 50: Sat Commands Specific To The Avaya G250 And G350 Media Gateways
Therefore, a new convention was developed that meets the needs of the Avaya G250 and G350 Media Gateways (as well as the G700 Media Gateway), yet for portability to traditional administration maintains the 7-character field. Also, in traditional MGC administration there are many commands that either require port fields as an argument to the command or require a port field value be entered on the form.
Page 51: Add/Change/Display/Status Media Gateway [X, Next]
The V, for virtual, is a required character that is part of the media module slot Note: number (H.248 terminology). The following subsections describe the commands unique to the Avaya G250 and G350 Media Gateways: add/change/display/status media gateway [x, next] ●...
Page 52 ANN VMM Max Survivable IP Ext: The Primary Server administers the Avaya G250 and G350 Media Gateways by the command add media-gateway x or add media-gateway next, where x is valid between the range of 1 to the capacity for a given primary server, and next is the next available number to be administered.
Page 53 For the G350, general slots for G350/G700 form factor media modules ● For the G250, V2 is a slot for a WAN media module (MM340 or MM342). V3 is the virtual ● slot from which the analog ports on the motherboard are administered. Slots V4 - V8 do not appear.
Page 54: List Media-Gateway
Max Survivable IP Ext – limits the number of simultaneous IP endpoint registrations for ● the G250 in SLS mode (1 - 60). The limited VoIP resources in SLS can only handle a limited number of simultaneous endpoint registrations. Adjusting this field above the default value (8) can result in system performance problems.
Page 55: List Configuration Media-Gateway
Maintenance commands RecRule – the number of Auto Fallback registrations that will be accepted ● Registered? – indicates whether the media gateway is currently registered ● Figure 5: List Media-Gateway Screen list media-gateway Page 1 of 1 MEDIA GATEWAY REPORT Name Serial No/ IP Address/...
Page 56: Status Media-Gateway
MG Mj Mn Wn Lk MG Mj Mn Wn Lk MG Mj Mn Wn Lk MG Mj Mn Wn Lk 1| 0| 0|dn 1| 0| 0|dn 1| 0| 0|pd 56 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 57: Change System-Parameters Mg-Recovery-Rule
Maintenance commands Table 18: The status media-gateway Command Display on page 57 describes the display associated with each section of the status media-gateway screen. Table 18: The status media-gateway Command Display Section Display ALARM Current number of alarms (Major/Minor/Warning) SUMMARY for the total number of media gateways administered BUSY-OUT...
Page 58 The user must hang up in order to regain access to all features. Note: set ’Migrate H.248 MG to primary’ to Blank to disable rule. 58 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 59 Maintenance commands Figure 9: System-Parameters MG-Recovery-Rule Screen – 0-Active-Calls change system-parameters mg-recovery-rule <n> SYSTEM PARAMETERS MEDIA GATEWAY AUTOMATIC RECOVERY RULE Recovery Rule Number: n Rule Name: Migrate H.248 MG to primary: 0-active-calls Minimum time of network stability: 3 WARNING: The MG shall only be migrated when there are no active calls. Note: set ’Migrate H.248 MG to primary’...
Page 60: Hidden Avaya Communication Manager Sat Commands
Hidden Avaya Communication Manager SAT commands Certain Avaya Communication Manager SAT commands have no practical use or are not supported on an Avaya G250/G350 Media Gateway. These commands are removed from the S8300 Media Server/LSP software to prevent any misunderstanding or confusion as to what functions are supported.
Page 61 Maintenance commands Table 19: Disabled SAT Commands (1) change display remove list cabinet cabinet cabinet cabinet cabinet data-module circuit-packs circuit-packs data-module configuration (atm) fiber-link data-module data-module fiber-link configuration (carrier) ipserver-interface fiber-link fiber-link ipserver-interface configuration (port-network) modem-pool ipserver-interface ipserver-interface modem-pool configuration (control) pgate modem-pool modem-pool...
Page 62 S8300 configured as an LSP. For an LSP, translations are received from the primary MGC, and there is no need to save them. 62 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 63: Dynamic Call Admission Control (Cac)
Dynamic Call Admission Control (CAC) Dynamic Call Admission Control (CAC) In order to manage the flow of calls and voice data on the G250/G350 most efficiently, the Media Gateway Controller must have real-time information about the network topology and currently available bandwidth. Without this, changes to the network structure, such as switching over to a backup line, can cause the network to become overloaded with voice data.
Page 64: System Resets
G250 itself to provide partial backup MGC functionality in the event that the connection with the primary MGC is lost. If the G250 tries and fails to find another Media Server, it turns to the SLS module as an alternative. For a full description of SLS, see...
Page 65: Results Evaluation
System resets You can also execute a traceroute operation from the Diagnostics area of the Maintenance Web Interface. See Figure Figure 12: Traceroute from Maintenance Web Interface In order to keep from overloading platform processes, a traceroute cannot be executed in less than 10 seconds from the last command.
Page 66: Link Recovery, Connection Preservation, And Auto Fallback
MGC or LSP. Link Recovery does not diagnose or repair the network failure that caused the link outage. In a G250 in which SLS is enabled, if no backup MGC is found and there is no LSP, the SLS module will take over limited call control functionality until the link to the primary MGC is restored.
Page 67: Applicable Hardware And Adjuncts
● and Avaya media modules and all applicable endpoints Note: The software and firmware versions on the MGC and the G250/G350 must Note: match. If they do not match, the intent of Link Recovery is circumvented because the gateway resets (drops calls) as soon as the link loss is detected.
Page 68 74 for instructions on administering this list. Administering the gateway timers and Transition Point on page 74 for instructions on administering the Primary and Total Search Timers. 1 of 2 68 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 69 1. S8300: 1-3 S8300s configured as Local Spare Processors (LSPs) 2. S8700/S8710: 1-3 C-LAN circuit packs within the primary server’s configuration 3. SLS: A built-in module providing limited call control functionality (G250 only) The Total Search Timer continues running. Administering the MGC list on page 74 for instructions on administering this list and setting the Transition Point.
Page 70 Applications running on the Avaya Communication Manager API server connect with ● Avaya Communication Manager through an IP softphone-like interface. Thus, an individual instance of an application might end up in Connection Preservation mode, where no Avaya Communication Manager features other than disconnects are allowed. Feature interactions and compatibility on page 78 section describes other performance impacts associated with Link Recovery.
Page 71: Link Recovery Unsuccessful
System resets Link recovery unsuccessful If link recovery was unsuccessful, both Avaya Communication Manager and the media gateway generate events and alarms. Server alarms Expiration of the Link Loss Delay Timer triggers Avaya Communication Manager alarm notification. These events and their associated alarm levels are in...
Page 72: Link Recovery Administration
Administering the MGC list Administering the server timer The Link Loss Delay Timer determines how long Avaya Communication Manager retains the gateway’s call state information before activating Connection Preservation or SLS (if enabled). To administer the Link Loss Delay Timer: 1.
Page 73 Total Search Timer, and the MGC list Transition Point. You also administer an MGC list of up to four alternate controllers for the gateway. Note: SLS (G250 only) adds a fifth element to the MGC list. See Standard Local Note: Survivability (SLS) on page 87.
Page 74 The MGC list consists of the IP addresses to contact and the order in which to re-establish the H.248 link. In the G250, the MGC list includes an additional entry for Standard Local Survivability (SLS). This entry indicates whether or not SLS is enabled on the G250.
Page 75: Connection Preservation
The next three elements are the IP addresses of 1-3 MGCs, which can include an LSP. ● There are a total of four elements in this list. On a G250 in which SLS is enabled, there is a fifth element in the list called survivable-call-engine.
Page 76 MGC fully preserves the calls that it is already aware of and reconstructs only those calls that the new MGC started. If the G250/G350 re-registers with the primary MGC after the Link Loss Delay Timer expires, then the G250/G350 reconstructs calls, since the primary MGC has no knowledge of the calls.
Page 77 Communication Manager software on the MGC, the firmware on the G250/G350, and the firmware on the VoIP media module be compatible. Note: On the G250, there is no VoIP media module, and the gateway firmware handles Note: VoIP functionality. The following software and firmware versions are required for proper functioning of Connection Preservation: Avaya Communication Manager, Release 3.0...
Page 78: Feature Interactions And Compatibility
NVRAM or directed to a syslog server for later processing. Call Management System Measurements collected during the recovery (CMS) period might be inaccurate in those reports that rely upon time-related data. 1 of 6 78 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 79 System resets Table 26: H.248 Link Recovery feature/adjunct interactions (continued) Feature or adjunct Description Property Management System Automatic Wake-up, Daily Wake-up, and (PMS) Housekeeping Status features might not operate as expected if the link fails and the time to search for alternate resources exceeds the PMS application’s time-out parameters.
Page 80 Hold Calls on hold are not preserved by Connection Preservation. In addition, calls on hold are not monitored to see if there is active VoIP traffic. 3 of 6 80 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 81 System resets Table 26: H.248 Link Recovery feature/adjunct interactions (continued) Feature or adjunct Description H.323 stations An IP phone that is on a call tries to return to the primary MGC if it loses its signalling link (when TCP keepalive fails) to the MGC. If the MGC is aware of the call it allows the IP phone to register.
Page 82 Routing (IGAR) two additional calls involving each trunk. When the call is reconstructed, the new MGC constructs each of the IGAR connection is a separate call. 5 of 6 82 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 83: Network Fragmentation And Auto Fallback
System resets Table 26: H.248 Link Recovery feature/adjunct interactions (continued) Feature or adjunct Description IP phone shared control The MGC does not allow an IP Softphone that is feature sharing control of an IP phone to re-register until the IP phone has re-registered. The MGC allows an IP Softphone that is sharing control of a DCP phone to re-register only after the DCP phone is in service.
Page 84 Avaya Communication Manager 3.0 or vice versa. However, the Auto Fallback feature would not be available. For this feature to work, the MGC is required to have Avaya Communication Manager 3.0, while the media gateway is required to have the gateway firmware available at the time of the Avaya Communication Manager 3.0 release.
Page 85 There is no need for the LSP to have any of these translations. 4. When associated with a primary MGC running Avaya Communication Manager 3.0, the media gateway attempts to register with the primary MGC whenever it is connected to an LSP or a backup MGC.
Page 86 9. Once the registration message is accepted by the primary MGC, then the H.248 link to the LSP or backup MGC is dropped. Note: Auto Fallback in a G250 operating in SLS mode operates the same way as Auto Note: Fallback in a G250/G350 obtaining service from an LSP.
Page 87: Standard Local Survivability (Sls)
IP station registration ● As one of the most affordable offers in Avaya’s recovery strategy, SLS is not a replacement for ESS or LSP survivability which offer full call-feature functionality and full translations in the survivable mode. Instead, SLS is a cost-effective survivability alternative offering limited call processing in survivable mode and no special station features.
Page 88: Call Processing In Sls Mode
Avaya Communication Manager controlled maintenance PIM, the data set can be configured manually from individual media gateways using CLI commands. For instructions on configuring SLS, see Administration for the G250 and 350 Media Gateways, 03-300436. Call processing in SLS mode...
Page 89: Provisioning Data
Communication Manager, see Administrator's Guide for Avaya Communication Manager, 555-233-506. SLS also requires PIM configuration data, some of which the G250 extracts from the Avaya Communication Manager translations. PIM aggregates the required data and copies the provisioning data over a secure communication path to non-volatile RAM (NVRAM) on the media gateway.
Page 90: Entering Sls Mode
When the Link Recovery search settles on the survivable-call-engine entry in the MGC list, then the G250 registers with SLS (resident on the media gateway) for its call control. This section discusses each of the four possible SLS states and the transitions from one state to another.
Page 91: Emergency Transfer Relay (Etr) In Sls Mode
After Teardown has completed, SLS transitions to the Unregistered state. Emergency Transfer Relay (ETR) in SLS mode Emergency Transfer Relay (ETR) on the G250 connects or “latches” a CO trunk port (V304) to an analog station port (V305), allowing the user to access the PSTN for emergency calls in...
Page 92: Sls Logging Activities
Emergency Transfer mode, the system returns Abort Code 1426, “cannot release ports, MG has control.” There is no means to disable the ETR feature when the G250 gateway models are powered-down. Therefore, on the G250 models, certain ports should not be used as DID ports to avoid having the ETR “loop-start”...
Page 93: Maintenance Objects
Maintenance Objects Figure 14: CDR log example G250-SLS(super)# show logging cdr file content 02/18/2005,10:46:35:CDR-Informational: 10:46 00:00 A 700 50029555 52001 v301 02/18/2005,10:45:46:CDR-Informational: 10:45 00:00 A 700 50029 52001 v301 02/18/2005,10:45:14:CDR-Informational: 10:45 00:00 A 700 52 52001 v301 02/18/2005,10:44:35:CDR-Informational: 10:44 00:00 A 700 445200 52001 v301...
Page 94: Avaya G250/G350 Media Gateway Mos
1412 Avaya G250/G350 Media Gateway MOs The following list shows new, G250/G350-specific maintenance objects. Other maintenance objects have been modified slightly for the G350 and (where applicable) the G250. MED-GTWY (MEDIA GATEWAY) (G250 and G350) ● MG-ANA (ANALOG MM711, MM714) (G250 and G350) ●...
Page 95: Mo Groupings By Mm Type
MO groupings by MM type MO groupings by MM type Table 27: Media Module Tests on page 95 shows MO groupings by Avaya media module type. Table 27: Media Module Tests Media Module Maintenance Object E1/T1 Media Module Board (MG-DS1)
Page 96: Mo Test Commands
Media Gateways, where GGG is the G250/G350 Number, the character V indicates that this system is a G250 or G350, S is the slot number, and PP is the port number. Full test commands can be either short or long as indicated, and can be repeated several times.
Page 97: Abort Code 1412
Abort Code 1412 Abort Code 1412 Tests that do not run on the G250 or G350 will abort with Abort Code 1412. Tests that abort are listed under each MO, but are not described. ALARM-PT (ALARM PORT) Table 28: ALARM-PT (ALARM PORT)
Page 98: System Technician-Demanded Tests: Descriptions And Error Codes
Order of Investigation Short Test Long Test D/ND* Sequence Sequence Battery Feed Test (#35) Station Status and Translation Audits and Updates Test (#36) *D = Destructive; ND = Nondestructive 98 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 99: Battery Feed Test (Also Called Port Diagnostic Test) (#35)
ALARM-PT (ALARM PORT) Battery Feed Test (also called Port Diagnostic Test) (#35) The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing, transmission, and balance. This test checks the signaling and switchhook capabilities of the battery feed chip by terminating the port, applying battery, and trying to detect a current. Table 31: TEST #35 Battery Feed Test Error Test...
Page 100: Station Status And Translation Audits And Updates Test (#36)
The translation update failed. This does not indicate a hardware problem but may be an internal software error. PASS The software and the port processor have the same status. 100 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 101: An-Ln-Pt (Analog Line Port)
Analog Line Port Note: You must consult local records for the location and designation of the equipment rack where the G250/G350 is mounted. The MM711 Analog Trunk and Line media module provides 8 ports, each of which may be administered in any of several ways, as described in maintenance object MG-ANA.
Page 102 Test #48. (b) Error Type 15 - a software audit error that does not indicate any hardware malfunction ● - Run the Short Test Sequence and investigate any associated errors. 102 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 103: System Technician-Demanded Tests: Descriptions And Error Codes
AN-LN-PT (Analog Line Port) (c) Error Type 130 - indicates that the media module has been removed or has been ● insane for more than 11 minutes - To clear the error, reset or replace the media module. (d) Error Type 257 - an in-line error that can only be resolved over time. This error ●...
Page 104: Battery Feed Test (Also Called Port Diagnostic Test) (#35)
To enable the test for a particular station being tested, enter change station extension. Change the Test? field on the station form to y. 1 of 3 104 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 105 AN-LN-PT (Analog Line Port) Table 36: TEST #35 Battery Feed Test (continued) Error Test Description/Recommendation Code Result 1392 ABORT This port is currently a TTI port and the test does not execute on it. Verify that the port is a TTI port: Enter the display port GGGVSpp command (the display shows that the port is a TTI port).
Page 106 Use the test board GGGVS long command. This re-establishes the link between the internal ID and the port. If this is not the case, check to make sure that a valid board is inserted. 3 of 3 106 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 107: Station Status And Translation Audits And Updates Test (#36)
AN-LN-PT (Analog Line Port) Station Status and Translation Audits and Updates Test (#36) This test updates the analog port’s message lamp state (if it has one) and translations with information in the software. Table 37: TEST #36 Station Status and Translation Audits and Updates Error Test Description/ Recommendation...
Page 108 Use the test board GGGVS long command. This re-establishes the link between the internal ID and the port. If this is not the case, check to make sure that a valid board is inserted. 2 of 2 108 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 109: Station Present Test (Also Called Ringing Application Test) (#48)
AN-LN-PT (Analog Line Port) Station Present Test (also called Ringing Application Test) (#48) This test applies momentary ringing voltage to the terminal equipment and monitors resulting current flow to determine whether terminal equipment is connected to the port. This test may cause some terminal equipment to ring briefly during daily maintenance.
Page 110 (enter n into the Test field). Note that this action also disables Test #35 on this port. If the test still fails, the terminal equipment may be defective. Check and replace it, if necessary. 2 of 3 110 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 111: Co-Ds1 (Ds1 Co Trunk)
DS1 CO Trunk Note: For Avaya G250/G350 systems you must consult local records for the location and designation of the equipment rack where the G250/G350 is mounted. A Major alarm on a trunk indicates that alarms on these trunks are not downgraded by the set options command and that at least 75 percent of the trunks in this trunk group are alarmed.
Page 112: Error Log Entries And Test To Clear Values
Settings must be compatible with the local environment and with parameter settings on the far-end. Refer to “Chapter 12, Managing Trunks” in the Administrator's Guide for Avaya Communication Manager, 555-233-506 for information on how to administer trunks. For the correct settings for administrable timers and other parameters on a country-by-country basis, see your local Avaya representative.
Page 113 CO-DS1 (DS1 CO Trunk) Table 41: CO-DS1 Trunk Error Log Entries (continued) Error Associated Test Alarm On/Off Test to Clear Value Type Data Level Board 1(a) 57487 15(b) Port Audit and Update Test (#36) 18(c) busyout trunk WARNING release trunk <grp>/ <grp>/<mbr>...
Page 114: System Technician-Demanded Tests: Descriptions And Error Codes
Conference Circuit Test (#7) Note: This Test ABORTS DS1 CO Trunk Seizure Test (#314) Note: This Test ABORTS Port Audit and Update Test (#36) *D = Destructive; ND = Nondestructive 114 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 115: Port Audit And Update Test (#36)
CO-DS1 (DS1 CO Trunk) Port Audit and Update Test (#36) This test sends port level translation data from switch processor to the DS1 Interface media module to assure that the trunk’s translation is correct. Translation updates include the following data: trunk type (in/out), dial type, timing parameters, and signaling bits enabled. The port audit operation verifies the consistency of the current state of trunk.
Page 116 (even though the reset board command does work). The software puts the hyperactive board back in service after the hyperactivity clears. 2 of 2 116 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 117: Co-Trk (Analog Co Trunk)
WARNING test port GGGVSpp l Analog CO Trunk Note: For Avaya G250/G350 systems, you must consult local records for the location and designation of the equipment rack where the G250/G350 is mounted. **A MAJOR alarm on a trunk indicates that alarms on these trunks are not downgraded by the set options command and that at least 75% of the trunks in this trunk group are alarmed.
Page 118: Ground Start Operation
2. CO Ringing: CO applies ringing voltage. a. PBX Response: Detect ringing, ring destination. 3. PBX Off-Hook (Answer Message): Close loop. a. CO Response: Trip ringing, provide loop current. 118 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 119: Error Log Entries And Test To Clear Values
CO-TRK (Analog CO Trunk) 4. PBX On-Hook first (Drop Message): Open the Tip-Ring Loop, no loop current. a. CO Response: Open circuit on Tip. 5. CO On-Hook first (Disconnect): Open circuit on Tip, no loop current. Error Log Entries and Test to Clear Values Table 45: CO Trunk Error Log Entries Error Aux Data...
Page 120 Call Seizure Tests have passed. Problems at the CO may cause this condition rather than problems with the PBX. 120 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 121 CO-TRK (Analog CO Trunk) If test fails after two repetitions, replace media module. ● Check for the use of MFT/Range extenders. If there are extenders present, and there are no other complaints or maintenance errors against this trunk, then there is a good chance that Test #3 failed due to excessive loop current and may be ignored.
Page 122 If this is a hard fault, the dial tone test and all outgoing calls should also fail. Check for other errors. 2 of 3 122 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 123 CO-TRK (Analog CO Trunk) Table 46: CO Trunk Errors with No Tests (continued) Error Error Description and Repair Action Type Data 3329 57408 Trunk error. No Tip ground detected on outgoing call. This error occurs when an attempt is made to seize a ground-start CO trunk for an outgoing call and Tip ground is not detected or the caller hangs up before Tip ground is detected.
Page 124: System Technician-Demanded Tests: Descriptions And Error Codes
MFT/Range Extenders are being used. If extenders are present, then there is a good chance that there is excessive loop current, which will cause Test #3 to log errors. However, all else being normal, these errors should not affect the customer. 124 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 125: Dial Tone Test (#0)
CO-TRK (Analog CO Trunk) Dial Tone Test (#0) This test attempts to seize a port and checks for the return of a dial tone. Table 48: Test #0 Dial Tone Test Error Test Description/ Recommendation Code Result ABORT Could not allocate system resources to run this test. 1.
Page 126 ABORT Response to the test was not received within the allowable time period. 1. Retry the command at 1-minute intervals for a maximum of 5 times. 2 of 4 126 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 127 CO-TRK (Analog CO Trunk) Table 48: Test #0 Dial Tone Test (continued) Error Test Description/ Recommendation Code Result FAIL Trunk was seized, but dial tone could not be detected. 1. Test all administered outgoing ports on the board. Failure of 1 indicates a problem toward the CO.
Page 128 3. Use the reset board command. 4. Use the release busy board command. 5. Use the test board command. This should re-establish the linkage between the internal ID and the port. 4 of 4 128 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 129: Co Demand Diagnostic Test (#3)
CO-TRK (Analog CO Trunk) CO Demand Diagnostic Test (#3) For ground start trunks, port media module relays are operated and checks are made to see if the port can detect and apply ground on the Tip lead. This test also verifies that there is no external ground on the Ring lead.
Page 130 Use the reset board command. Use the release busy board command. Use the test board command. This should re-establish the linkage between the internal ID and the port. 2 of 2 130 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 131: Port Audit Update Test (#36)
CO-TRK (Analog CO Trunk) Port Audit Update Test (#36) This test will send updates of the CO port translation for all ports on the media module which have been translated. The update is non-disruptive and guards against possible corruption of translation data contained on the media module.
Page 132: Did-Ds1 (Direct Inward Dial Trunk)
The MM710 series media modules support wink-start and immediate-start trunks and call processing signaling. See MG-DS1 for more information. Throughout this section, the term DS1 applies to MM710 media modules. 132 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 133: Error Log Entries And Test To Clear Values
DID-DS1 (Direct Inward Dial Trunk) Information included in this section covers the in-line errors log, initialization tests, periodic tests, scheduled tests, system technician demand tests, and alarms escalation and elimination. Two trunk service states are specified in the DID-DS1 trunk maintenance: out-of-service –...
Page 134 DID trunk. Aux Data 57393 indicates belated external release on PBX disconnect. (h) Error Type 1793—DS1 Interface media module is out-of-service. Look for MG-DS1 ● errors in Hardware Error Log. Refer to the appropriate “MG-DS1” information for details. 134 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 135: System Technician-Demanded Tests: Descriptions And Error Codes
DID-DS1 (Direct Inward Dial Trunk) (i) Error Type 2305—This error indicates that a signaling change was detected by the PBX ● trunk media module which is inconsistent with the present state of the trunk. (j) Error Type 3840—Port Audit and Update Test (#36) failed due to an internal system ●...
Page 136: Port Audit And Update Test (#36)
Retry the command at 1-minute intervals a maximum of 5 times. FAIL Test failed due to internal system error. Retry the command at 1-minute intervals a maximum of 5 times. 1 of 2 136 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 137 DID-DS1 (Direct Inward Dial Trunk) Table 54: TEST #36 Port Audit and Update Test (continued) Error Test Description/ Recommendation Code Result PASS Trunk translation has been updated successfully. The current trunk states kept in the DS1 Interface media module and switch software are consistent.
Page 138: Did-Trk (Direct Inward Dial Trunk)
Refer to Administrator’s Guide for Avaya Communication Manager, 555-233-506, for information on how to administer trunks. For the correct settings for administrable timers and other parameters on a country-by-country basis, see your local Avaya representative. Direct Inward Dial trunks connect the switch to the CO, and allow outside parties to call directly to an extension in the system.
Page 139: Did Trunk Testing
DID-TRK (Direct Inward Dial Trunk) DID Trunk Testing The system uses technician-invoked tests to diagnose the health of the trunk. These tests are described in the following sections. Additionally, in-line testing, which can generate errors, is performed while a call is in progress. See the Error Log Table 56: DID Trunk Error Log Entries on page 139 for a description of these errors.
Page 140 (a) This condition occurs when the tone detector times out waiting for digits. Change wink/ ● immediate-start parameter to wink/immediate-start and rotary/tone-dial parameters. 1. Verify trunk administered wink/immediate-start parameter. 2. Test trunk using BUTT set. 3. Refer problem to CO. 140 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 141 DID-TRK (Direct Inward Dial Trunk) (b) Rotary dial before wink — This condition occurs when the CO starts dialing before the ● PBX sends wink on a wink-start trunk. 1. Verify trunk administered wink/immediate-start parameter. 2. Refer problem to CO. (c) Rotary dial too early —...
Page 142: System Technician-Demanded Tests: Descriptions And Error Codes
Port Diagnostic Test (#35) Looparound and Conference Circuit Test (#33) Note: This test will abort with Error Code 1412 Port Audit Update Test (#36) *D = Destructive; ND = Nondestructive 142 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 143: Port Diagnostic Test (#35)
DID-TRK (Direct Inward Dial Trunk) Port Diagnostic Test (#35) This test checks a port’s battery feed circuitry for on-/off-hook detection, battery shutdown, and battery reversal (wink) capabilities. Table 58: TEST #35 Port Diagnostic Test Error Test Description/ Recommendation Code Result ABORT System resources required to run this test were not available.
Page 144 Use the release busy board command. Use the test board command. This should re-establish the linkage between the internal ID and the port. If the problem persists, replace the circuit pack. 2 of 2 144 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 145: Port Audit Update Test (#36)
DID-TRK (Direct Inward Dial Trunk) Port Audit Update Test (#36) This test sends updates of the DID port translation for all ports on the media module that have been translated. The update is non-disruptive and guards against possible corruption of translation data contained on the media module.
Page 146: Dig-Line (Digital Line)
Media Gateway-level maintenance is covered by “MG-DCP” whose strategy is described in the “XXX-BD (Common Port Media Module)” section. 146 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 147: Programmable Terminals
DIG-LINE (Digital Line) Digital line maintenance interacts with digital line media module (MG-DCP) maintenance, and results of DIG-LINE testing can be affected by the health of the digital line media module. Keep this in mind when investigating digital line problems. There are instances where the service state of a station is mentioned.
Page 148: Downloadable Terminal Parameters
The mu-law companding mode is assigned as a default setting at the factory. For Note: the United States, a programmable terminal can place calls even though it has not been downloaded from the system. 148 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 149: Download Actions
DIG-LINE (Digital Line) Download Actions There are several different scenarios that cause a terminal to be downloaded. These can occur as part of background maintenance activity or on demand from the System Access Terminal or from a station. For the background actions described below, the terminal downloads automatically if a download retry flag for the terminal is set in software.
Page 150: Port Insertion
Demand Download Actions Busyout/Release Command A maintenance demand busyout/release request for a station will cause the terminal to be downloaded regardless of its previous download status. 150 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 151: Feature Access Code
DIG-LINE (Digital Line) Feature Access Code A Refresh Terminal Parameters Feature Access Code can be used to request a terminal download action. When this code is followed by a “#”, the programmable parameters for the current terminal are downloaded when the terminal goes on hook. When this code is followed by an extension, the programmable parameters for the specified station are downloaded.
Page 152: Error Log Entries And Test To Clear Values
GGGVSpp sh r 4 Audits Test (#17) 1537 (h) 40968 None WARNING 2304 (n) None 2305 (i) 32770 None 2305 (h) 40967 None 2817(j) None 3840 (k) 40965 None 1 of 2 152 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 153 DIG-LINE (Digital Line) Table 63: Digital Line Error Log Entries (continued) Error Associated Test Alarm Level On/Off Test to Clear Value Type Data Board 3840 (l) 40989 None 3841 (m) 41029 None *Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures.
Page 154 (n) Internal system error. No action is necessary. ● (o) There is a problem with the voice terminal EEPROM. When the voice terminal is ● repaired the alarm will be resolved with the passing of time. 154 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 155: System Technician-Demanded Tests: Descriptions And Error Codes
DIG-LINE (Digital Line) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below. By clearing error codes associated with the Voice and Control Channel Local Looparound Test, for example, you may also clear errors generated from other tests in the testing sequence. Table 64: Order of Investigation Order of Investigation Short Test...
Page 156 Use the release busy board command. Use the test board command. This should re-establish the linkage between the internal ID and the port. If the problem persists, replace the circuit pack. 2 of 2 156 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 157: Dig-Line Station Lamp Updates Test (#16)
DIG-LINE (Digital Line) DIG-LINE Station Lamp Updates Test (#16) This test lights all lamps on the terminal as specified. The lamp updates will run only if the station is in-service. The status of the station is checked and the lamp updates are blocked from taking place if the station is not in the in-service state.
Page 158: Digital Station Audits Test (#17)
This value is set initially when the station is put in-service and every time the station’s state changes from other states to in-service. 158 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 159 DIG-LINE (Digital Line) Table 67: TEST#17 Station (Digital) Audits Test Error Test Description/ Recommendation Code Result ABORT Switchhook audit timed out. ABORT ID request fails, health bit returned from voice terminal is bad. Make sure voice terminal is connected and repeat test. If test fails, replace voice terminal and repeat test.
Page 160: Diod-Trk (Diod Trunk)
Refer to the Administration Manual for information on how to administer trunks. For the correct settings for administrable timers and other parameters on a country-by-country basis, see your local Avaya representative. 160 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 161: Services Supported By Diod Trunks
DIOD-TRK (DIOD Trunk) Services Supported by DIOD Trunks Direct inward and outward dial (DIOD) trunks are 2-wire analog lines to the CO which support the following services: Both incoming and outgoing CO calls ● DID trunk ● DID trunk and 1-way outgoing DIOD ●...
Page 162: Error Log Entries And Test To Clear Values
Run the Dial Tone Test (#0) and follow its procedures. Aux data 57376—No loop current on incoming call Aux data 57424—No loop current on outgoing call 162 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 163 DIOD-TRK (DIOD Trunk) (d) Single polarity ringing current—This error results from abnormal ringing current, but ● does not prevent the incoming call from being accepted. This error code is logged for information purposes only and does not cause additional testing to occur. (e) Late CO Trunk release—This indicates that the CO releases the trunk at least four ●...
Page 164: System Technician-Demanded Tests: Descriptions And Error Codes
The port translation data includes: ground or loop start trunk, tone or rotary dialing trunk, rotary dialing inter-digit timing, network balance R/ RC, and disconnect timing. 164 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 165: Isdn-Lnk (Isdn-Pri Signaling Link Port)
*pp is 24 for 24-channel interfaces and 16 for 32-channel interfaces. Note: You must consult local records for the location and designation of the equipment rack where the G250/G350 is mounted. **For additional related information, see USD1-BD and MG-DS1 MOs.
Page 166: Hardware Error Log Entries And Test To Clear Values
WARNING release port GGGVSpp** GGGVSpp** 130 (b) None WARNING test port GGGVSpp** 1537 (c) 46210 WARNING 1793 (d) test board GGGVS l 3841 (f) 46211 1 of 2 166 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 167 ISDN-LNK (ISDN-PRI Signaling Link Port) Table 74: ISDN-PRI Signaling Link Port Error Log Entries (continued) Error Associated Test Alarm On/Off Test to Clear Value Type Data Level Board 3842 (g) 46223 *Run the Short Test Sequence first. If all tests pass, run the Long Test Sequence. Refer to the appropriate test description and follow the recommended procedures.
Page 168: System Technician-Demanded Tests: Descriptions And Error Codes
Re-attach the disconnected PRI terminal adapter Disable the rollabout video feature on this board by entering change ds1 GGGVSpp and set the field labeled “Alarm when PRI Endpoint Detached?” to “y.” 1 of 2 168 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 169: Isdn-Sgr (Isdn-Pri Signaling Group)
ISDN-SGR (ISDN-PRI Signaling Group) Table 76: Test #643 Signaling Link Board Check (continued) Error Test Description/ Recommendation Code Result FAIL The MM710 is not in-service. Check the Hardware Error Log for entries logged against DS1 MM and consult the DS1 Interface media module Maintenance documentation for repair procedures.
Page 170 D-channels reside and the system link that is carried over the packet bus to the processor. When there are problems with the ISDN-PRI signaling group, also investigate ISDN-LNK, MG-DS1, and SYS-LINK. 170 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 171: Error Log Entries And Test To Clear Values
ISDN-SGR (ISDN-PRI Signaling Group) Error Log Entries and Test to Clear Values Table 78: ISDN-PRI Signaling Group Error Log Entries Error Associated Test Alarm On/Off Test to Clear Type Data Level Board Value test sig-group grp# 1 (a) None 257 (b) None test sig-group grp#...
Page 172 (although incoming calls will still be accepted). When Test #637 succeeds and the Far-end switch starts responding properly, the DS1 ISDN Trunk (B-channels) will be placed back into normal operation and their alarms will be retired. 172 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 173 ISDN-SGR (ISDN-PRI Signaling Group) (g) A SERV or SERV ACK ISDN D-channel message has been received by a non-US-type ● interface (country option other than 1 on the DS1 administration form). However, these messages are used only for duplex NFAS signaling which is supported only by country protocol 1.
Page 174 Consider modifying all routing patterns containing this the call may not be trunk group, to route calls around the network which is successful). out of service. 2 of 4 174 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 175 ISDN-SGR (ISDN-PRI Signaling Group) Table 79: Descriptions and Recommendations for Error Types 3842-3942 (continued) Error Description Recommendation Code 3890 A request to use a network This could be a local administration problem only, or a service (e.g., ISDN) has mismatch between the local administration and that of been denied.
Page 176 (for example, some ISDN switches may not allow a voice station to call a data extension). 3942 Timer expiry: T310 time-out, no answer to CALL PROCEEDING. 4 of 4 176 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 177: System Technician-Demanded Tests: Descriptions And Error Codes
ISDN-SGR (ISDN-PRI Signaling Group) System Technician-Demanded Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. By clearing error codes associated with the Primary Signaling Link Hardware Check, for example, you may also clear errors generated from other tests in the testing sequence.
Page 178: Remote Layer 3 Query (#637)
Note: The service state can be displayed by using the status trunk <trunk group/ Note: trunk member> or status pri-endpoint command. 178 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 179 ISDN-SGR (ISDN-PRI Signaling Group) As is the case with Test #256 for an ISDN trunk, a PASS only indicates that a message was composed and sent to the far-end switch or terminal adapter. The ISDN PRI Specification allows up to 2 minutes for a response. Check the Error Log for ISDN-SGR (ISDN-PRI Signaling Group) errors of type 2305 for evidence of a Remote Layer 3 Query failure.
Page 180: Secondary Signaling Link Hardware Check (#639)
MM-DS1 media module. This test will abort if a Secondary D-channel is not administered for the signaling group. If there are problems with the ISDN-PRI Secondary Signaling Channel port (ISDN-LNK), also investigate the MM710. 180 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 181 ISDN-SGR (ISDN-PRI Signaling Group) Table 83: TEST #639 Secondary Signaling Link Hardware Check Error Test Result Description/ Recommendation Code ABORT Internal system error Retry the command at 1-minute intervals a maximum of 5 times. 1132 ABORT The Secondary D-Channel is not administered for this Signaling Group.
Page 182: Layer 2 Status Test (#647)
Channel (D-channel) at the far end has been administered correctly. Verify that the DS1 port used for the Primary D-channel has not been busied out at the far end. 1 of 2 182 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 183 ISDN-SGR (ISDN-PRI Signaling Group) Table 84: TEST #647 Layer 2 Status Query Test (continued) Error Test Description/ Recommendation Code Result FAIL Layer 2 of the secondary signaling channel is down. Examine the results of Secondary Signaling Link Hardware Test (#639) and follow recommendations provided there.
Page 184: Isdn-Trk (Ds1 Isdn Trunk)
DS1 ISDN Trunk Note: For Avaya G250/G350 Media Gateway systems, you must consult local records for the location and designation of the equipment rack where the G250/ G350 is mounted. For additional repair information, see also DS1-BD for TN767 ports and MM710.
Page 185: Alarming Based On Service States
ISDN-TRK (DS1 ISDN Trunk) On 24-channel interfaces, any of the first 23 ports on the DS1 media modules can be a B-channel. On the MM710, the 24th port may be used as a B-channel or as a D-channel depending on the type of ISDN-PRI signaling group (FAS or NFAS) implemented on the media module.
Page 186: Ds1 Isdn Trunk Service States
Note that transitions into MTC/NE do not drop stable calls. In this state, the B-Channel is not usable for new incoming or outgoing calls. 186 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 187 ISDN-TRK (DS1 ISDN Trunk) Pending States ● In addition to one of the above components, the service state may have a pending component, indicating that the switch is waiting for a reply from the far-end. These service states remain in effect until either a response is received or the allotted waiting time expires. - Pending-in-Service The near-end is waiting for a response from the far-end to a B-channel maintenance message requesting that the B-channel be transitioned to in-service.
Page 188: Error Log Entries And Test To Clear Values
Associated Test Alarm Level On/Off Test to Clear Value Type Data Board test port GGGVSpp 1(a) None test port GGGVSpp 15(b) Audit and Update Test (#36) 1 of 2 188 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 189 ISDN-TRK (DS1 ISDN Trunk) Table 87: DS1 ISDN Trunk Error Log Entries (continued) Error Associated Test Alarm Level On/Off Test to Clear Value Type Data Board busyout trunk grp/ release trunk grp/mbr 19(c) None 129(d) None WARNING test port GGGVSpp 130(e) None WARNING...
Page 190 ● - Translations conflict - Protocol differences - ESS may be using NI3 protocol, which is not currently implemented in Avaya Communication Manager - B-channel negotiation problem (glare) (i) This error indicates a failure of the DS1/MM-DS1 Interface media module. When ●...
Page 191 ISDN-TRK (DS1 ISDN Trunk) (k) Error Type 3585 appears when the switch receives an ISDN RESTART message for an ● ISDN trunk. Calls are cleared with the RESTART message. Therefore, this Error Type may be associated with a dropped call report from a user. The following Aux Data values for Error Type 3585 represent the trunk’s ISDN call state at the time the unexpected request to restart the channel was received from the remote switch.
Page 192: System Technician-Demanded Tests: Descriptions And Error Codes
Call State Audit Test (#257) ISDN Test Call Test (#258) Note: This Test ABORTS when run on a Avaya G250/G350 Media Gateway system. D = Destructive, ND = Non-destructive 192 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 193: Audit And Update Test (#36)
ISDN-TRK (DS1 ISDN Trunk) Audit and Update Test (#36) This test sends port level translation data from switch processor to the DS1 interface media module to assure that the trunk’s translation is correct. The port audit operation verifies the consistency of the current state of trunk kept in the DS1 interface media module and in the switch software.
Page 194: Signaling Link State Check Test (#255)
Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. 194 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 195: Service State Audit (#256)
ISDN-TRK (DS1 ISDN Trunk) Service State Audit (#256) As noted in the general description for DS1 ISDN Trunk, these trunks may be in one of several service states. This test performs a Service State Audit with the far-end switch. For interfaces using country protocol 1 (including the US) the Service State Audit executes in all trunk service states.
Page 196 Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. 2 of 2 196 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 197: Call State Audit Test (#257)
ISDN-TRK (DS1 ISDN Trunk) Call State Audit Test (#257) If a call is active on the trunk, the switches on both sides of the connection should agree on the ISDN state of the call, as defined in the ISDN Protocol Specification. This test audits internal call state data by querying the far-end switch as to the ISDN state of the call.
Page 198: Plat-Alm (Platform Alarms)
2 of 2 PLAT-ALM (Platform Alarms) The PLAT_ALM is a virtual MO used by Avaya Communication Manager to keep track of Media Server alarms. A MAJOR, MINOR, or WARNING alarm can be logged against this MO to indicate the presence of one or more Media Server alarms.
Page 199: System Technician-Demanded Tests: Descriptions And Error Codes
Refer to “Administrator’s Guide for Avaya Communication Manager, 555-233-506” for information on how to administer trunks. For the correct settings for administrable timers and other parameters on a country-by-country basis, see your local Avaya representative. The DS1 tie trunk provides both voice and data communications between two PBX switches.
Page 200: Hardware Error Log Entries And Test To Clear Values
WARNING release trunk grp/ mbr* 19(d) None 130(e) None WARNING test trunk grp/mbr 257(f) 57473 57474 513(g) 57392 DS1 Tie Trunk MIN/MAJ Seizure Test (#136) 1 of 2 200 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 201 This error can be caused by incompatible translations. Make sure the parameters administered on the DS1 media module form match those administered on the far-end switch. See Administrator’s Guide for Avaya Communication Manager, 555-233-506, for details. The Aux Data field indicates the following hardware error types:...
Page 202 Error Type 1025 also appears). In this case, the trunk may be put in “Ready-for-Service” state (shown as “disconnected” by the status command), which allows only incoming calls. Run the Trunk Seizure Test (#136) and follow its procedures. 202 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 203: System Technician-Demanded Tests: Descriptions And Error Codes
TIE-DS1 (DS1 Tie Trunk) (k) Error Type 2562—Retry Failure error. This error is logged only. It is not a hardware ● failure and hence does not start any testing or generate any alarms. This error comes from call processing and is generated when a second attempt (retry) to seize an outgoing trunk fails.
Page 204: Port Audit And Update Test (#36)
Retry the command at 1-minute intervals a maximum of 5 times. FAIL Internal system error. Retry the command at 1-minute intervals a maximum of 5 times. 1 of 2 204 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 205: Ds1 Tie Trunk Seizure Test (#136)
TIE-DS1 (DS1 Tie Trunk) Table 97: TEST #36 Audit and Update Test (continued) Error Test Description/ Recommendation Code Result PASS Trunk translation has been updated successfully. The current trunk states kept in the DS1 Interface media module and switch software are consistent.
Page 206 If the port is in use, wait until the port is idle before testing. If the port status is idle, retry the command at 1-minute intervals for a maximum of 5 times. 1 of 3 206 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 207 TIE-DS1 (DS1 Tie Trunk) Table 98: TEST #136 DS1 Tie Trunk Seizure Test (continued) Error Test Description/ Recommendation Code Result 1005 ABORT Test failed due to incompatible configuration administered in trunk group form. Verify the following fields on the trunk group administration screen: Is trunk direction incoming only? Is trunk outgoing type either automatic or immediate-start? Is trunk the 24th port of the DS1 Interface media module while...
Page 208 ID and the port. If this is not the case, check to see that there is a valid board inserted. *Earlier G1 Software Versions reported Error Code 2053 as a FAIL. 3 of 3 208 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 209: Wae-Port (Wideband Access Endpoint Port)
For additional repair information, see also DS1-BD (DS1 Interface media module). Wideband Switching supports end-to-end connectivity between customer endpoints at data rates from 128 to 1536 kbps over T1 facilities and to 1984 kbps over E1 facilities. Avaya Communication Manager switching capabilities are extended to support wideband calls comprised of multiple DS0s that are switched end-to-end as a single entity.
Page 210: Error Log Entries And Test To Clear Values
If the wideband access endpoint port is out of service, enter release access-endpoint extension to put it back into service. Retry the test command. 210 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 211: Technician-Demand Tests: Descriptions And Error Codes
Sequence Sequence NPE Crosstalk Test (#6) Note: This Test ABORTS with code 1412 when run on a Avaya G250/ G350 Media Gateway system. Conference Circuit Test (#7) Note: This Test ABORTS with code 1412 when run on a Avaya G250/ G350 Media Gateway system.
Page 212 Use the reset board command. Use the release busy board command. Use the test board long command. This should re-establish the linkage between the internal ID and the port. 2 of 2 212 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 213: Xxx-Bd (Common Port Media Module)
Maintenance Note: You must consult local records for the location and designation of the equipment rack where the G250/G350 is mounted. Refer to the appropriate media module documentation for the correct MO name displayed in this field. It usually ends with BD.
Page 214: Xxx-Bd Common Media Modules
MINOR 65535 Control Channel MINOR test board GGGVS sh Test (#52) r 20 257 (g) None None WARNING 513 (h) None MINOR test board GGGVS sh 1 of 2 214 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 215 XXX-BD (Common Port Media Module) Table 105: Common Port Media Module Maintenance Error Log Entries (continued) Error Associated Test Alarm On/Off Test to Clear Value Type Data Level Board 769 (i) 4358 None 1281 (k) Ringing Application MINOR test board GGGVS r 2 Test (#51) 1538 (l) None...
Page 216 However, if this error type is logged when the media module is being lightly used, it may indicate a problem with the media module or the equipment attached to it. 216 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 217: Technician-Demand Tests: Descriptions And Error Codes
XXX-BD (Common Port Media Module) Technician-Demand Tests: Descriptions and Error Codes Always investigate tests in the order presented in the table below when inspecting errors in the system. By clearing error codes associated with the NPE Audit, for example, you may also clear errors generated from other tests in the testing sequence.
Page 218: Control Channel Looparound Test (#52)
Verify that the board is physically in the system. Verify that the system is not in a stage of booting up. Retry the command at 1-minute intervals for a maximum of 5 times. 218 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 219: Saki Sanity Test (#53)
1005 ABORT If the media module needs to be reset, and if this is an Avaya G250/ G350 Media Gateway system, and the DS1 interface media module under test is providing timing for the platform, it cannot be reset without major platform disruptions.
Page 220 Avaya Communication Manager controlled maintenance 220 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 221: Chapter 4: License And Authentication Files
A new license file and the Avaya authentication file may be installed independently of each other or any other server upgrades. In addition, to enable IPSec VPN, you must obtain and install a VPN license on the G250/G350. For instructions on obtaining a VPN license, see...
Page 222: Rfa Information Requirements For New Installations
(ASG). The ASG challenge/response protocol confirms the validity of each user, reducing the opportunity for unauthorized access. Before starting the installation or, ideally, before coming on site, the license and Avaya authentication files may be downloaded to the services laptop. The license and Avaya authentication files are routinely installed during the installation process.
Page 223: Installing License And Authentication Files
1. Access the Maintenance Web Interface part of Avaya Integrated Management (AIM) from your laptop, using IP address 192.11.13.5. 2. Logon at the Avaya Integrated Management Logon screen. The main menu for Avaya Integrated Management appears. Figure 16: Integrated Management Main Menu 3.
Page 224 6. Browse to the customer’s license file (.lic), which you downloaded from the RFA web site. 7. Click Submit. A message appears telling you your installation was successful. 8. From the navigation menu, select Security > Authentication File. The Authentication File web page appears. 224 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 225 11. Click Install. A message appears telling you your installation was successful. Installing the Avaya authentication file removes all default passwords and establishes new ones. After the installation, services logins specific to the media server are protected through Access Security Gateway (ASG), which means a craft login will be challenged.
Page 226: License Files For Different Configurations
Local Survivable Processor (LSP). The LSP is present on the G250/G350, but Avaya Communication Manager is not active, and runs in a special survivable mode. The LSP provides service to a subset of endpoints in the event that the G250/G350 cannot be served by its primary Media Server.
Page 227: License File Modes
This is caused when: A survivable processor begins to provide service, which causes a major alarm ● The serial number in the license file does not match the serial number of the G250/G350 ● into which the S8300 is physically inserted...
Page 228: No-License Mode
Variables are always locked either On of Off by the License File. Four combinations are possible with meanings as shown in Table 109: Type I Feature License Behavior on page 229. 228 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 229: Type Ii Entries
License and Options Forms interactions Table 109: Type I Feature License Behavior License Content Consequence Value Lock Feature Status Options* Screen Unlocked Set by translation via login. If init and dadmin may administer no translation, feature is this feature. enabled. Locked Translation is always ignored.
Page 230: Type Iii Entries
III entry has two values associated with it, a lower limit value (V1), and an upper limit value (V2). V1 is never greater than V2. See Table 110: Type II and Type III Feature License Behavior on page 230. 230 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 231: Chapter 5: Access And Login Procedures
Chapter 5: Access and login procedures This chapter describes the various ways of connecting to, and logging into, the S8300 Media Server and the Avaya G250/G350 Media Gateway. Use this chapter as a reference for the other chapters in this book.
Page 232: System Admin Computer Or Technician Laptop Administration Via Corporate Lan
The G250 does not support USB modem connection. Note: Alternatively, connect to the G250 or G350 remotely using a serial modem connected to the Console port of the G250 or G350. 232 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 233 Connection overview Tasks 1. Diagnosis of media gateway 2. Remote administration of media gateway Figure 19: Summary of S8300 and G350 Access Methods and Tasks Issue 1.1 June 2005...
Page 234: Initial Configuration And Maintenance Of Media Gateway (No S8300)
Access and login procedures Figure 20: Summary of S8300 and G250 Access Methods and Tasks Initial configuration and maintenance of Media Gateway (no S8300) Connect to the Avaya G250/G350 Media Gateway directly using a laptop connected to the Console port. Onsite Tasks 1.
Page 235: Connecting The G250/G350 To The Customer Lan
Connecting a laptop to the S8300 Services port Connecting the G250/G350 to the customer LAN If you are providing maintenance for a G250/G350 that does not have an internal S8300, you may need to connect the G250/G350 to the customer’s LAN. There are various ways that the G250/G350 is connected to the customer’s LAN, depending on the G250/G350’s configuration.
Page 236: Setting Tcp/Ip Properties In Windows
Use your computer's help system if needed to locate the correct place to enter this information. The S8300 Media Server uses the same access configuration as an Avaya S8100 Media Server with a CMC1 or G600 Media Gateway. If you already have a NetSwitcher profile for the S8100 Media Server (formerly called DEFINITY One), try using that profile first before configuring a new one.
Page 237 Connecting a laptop to the S8300 Services port 7. On the General tab, select the radio button Use the following IP address. Enter the following: - IP address: 192.11.13.5 - Subnet mask: 255.255.255.252 Note: Record any IP addresses, DNS settings, or WINS entries that you change. You Note: may need to restore them later to connect to another network.
Page 238 Clear the check box for Enable DNS for WINS Resolution. ● 9. Click OK twice to accept the address information and close the Network dialog box. 10. Reboot the system if directed to do so. 238 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 239 Connecting a laptop to the S8300 Services port To disable/bypass proxy servers in browser: If you are connecting a laptop directly to the Services Ethernet interface on the S8300 faceplate, you must either disable or bypass proxy servers as described below. Note: The Microsoft Internet Explorer (IE) browser is recommended, version 5.5 or Note:...
Page 240: Connection Methods
Internet browser or start a Telnet session and log in. When accessing the server from a directly connected laptop, always type the following IP address in the browser's Address or Location field to access the server: 192.11.13.6. 240 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 241: Connect Laptop To The G250/G350 Console Port
Connection methods Connect laptop to the G250/G350 Console port To configure a G250/G350 that does not have an S8300, you may need to set up a direct connection from your laptop’s serial port to the G250/G350 Console (serial) port. To connect a laptop directly to the Console port on the Avaya G250/G350 Media Gateway: 1.
Page 242: Use Windows For Modem Connection To The Media Server (Windows 2000 Or Xp)
(Windows 2000 or XP) To use Windows for a modem connection: Note: The remote dial-up PC must be configured for PPP access. Also, Avaya Terminal Note: Emulator does not support Windows XP. 1. Right-click My Network Places and click Properties.
Page 243: Configure The Remote Pc For Ppp Modem Connection (Windows 2000 Or Xp, Terminal Emulator, Or Asa)
Connection methods 3. Select Dial-up to private network on the Network Connection Type screen. Note: If your system has more than one modem, you may be requested to select the Note: device. If so, select the modem you are using to dial out. 4.
Page 244: Use Windows For Ppp Modem Connection (Windows 2000 Or Xp)
Use Avaya Terminal Emulator for LAN connection to Avaya Communication Manager You can download the Avaya Terminal Emulator from the main menu for the VisAbility™ Management Suite. Simply click Download next to the Administration menu item and follow the instructions.
Page 245 10. In the IP address field, type the IP address of the Media Server. 11. In the TCP/IP port number field, leave 23 if you want to log in at the Linux command line. Type 5023 if you want to log in directly to the Avaya Communication Manager SAT command line.
Page 246: Use Avaya Terminal Emulator For Modem Connection To Avaya Communication Manager
Step 8 of the above procedure. 11. In the TCP/IP port number field, leave 23 if you want to log in at the Linux command line. Type 5023 if you want to log in directly to the Avaya Communication Manager SAT command line.
Page 247: Log In Methods
249. Log in methods This section describes how to log on to the Avaya G250/G350 Media Gateway or the S8300 Media Server using Telnet or the built-in Web Interface and how to start a SAT session. These procedures assume: You have a crossover cable directly connected from your laptop to the Services port on the ●...
Page 248: Log In To The S8300 Web Interface From Your Laptop
7. Check the top of the right panel. - The Avaya Media Server you are logged into is identified by name and server number. - The S8300 Media Server number is always 1. 248 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 249: Open The Avaya Communication Manager Sat Screens
Log in to the G250/G350 Media Gateway interface with a direct connection to the S8300 Services port Use this procedure to log in to the G250/G350 Media Gateway interface when you have a direct connection with your laptop to the S8300 Services port.
Page 250: Log In To The G250/G350 Interface With A Lan Connection
For a complete list of command line interface commands, type help or refer to the Avaya G250 and Avaya G350 CLI Reference, 03-300437 (available at http://www.avaya.com/support).
Page 251: Log In To The G250/G350 Interface With A Direct Serial Connection
Log in to the G250/G350 interface with a direct Serial connection Use this procedure to access the G250/G350 interfaces when your laptop is directly connected to the G250/G350 Console port via a serial cable. To access the G250/G350 via the Console (serial) port: ®...
Page 252: Avaya Site Administration
Configure Avaya Site Administration When Avaya Site Administration is initially installed on a client machine, it must be configured to communicate with Avaya Communication Manager on the S8300 Media Server. When initially running Avaya Site Administration, after downloading, you must create a new entry for the switch connection.
Page 253: Logging In To The S8300 With Avaya Site Administration
GEDI and Data Import. For more information, refer to Online Help, Guided Tour, and Show Me, accessed from the Avaya Site Administration Help menu. To use Avaya Site Administration, open the application and select the switch (media server) you want to access. When prompted, log in.
Page 254: Terminal Emulation Function Keys For Avaya Communication Manager
<command> 2 of 2 The command-line prompts in a G250/G350 CLI session use the media gateway’s name that is assigned when it is configured. You can Telnet to another interface from a current Telnet session. Terminal emulation function keys for...
Page 255 Terminal emulation function keys for Avaya Communication Manager Table 114: w2ktt terminal emulation function keys on page 255 lists key presses for w2ktt terminal emulation. Table 114: w2ktt terminal emulation function keys Key Sequence Function Function Cancel Execute Help Next Page Previous Page Issue 1.1 June 2005...
Page 256 Access and login procedures 256 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 257: Chapter 6: G250/G350 And Media Module Leds
257 indicates the meanings associated with standard DEFINITY server LEDs. Although in some cases these LEDs have been augmented or modified for the S8300 Media Server and Avaya G250/G350 Media Gateway, it is important to be aware of their standard meanings when viewing the system.
Page 258: Front Panel Leds
The following figure shows the G250 chassis: Figure 21: G250 chassis The following figure shows the G250-BRI chassis: Figure 22: G250-BRI chassis The following figure shows the G350 chassis: Figure 23: G350 chassis 258 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 259: System Leds
Front panel LEDs System LEDs The system LEDs show the status of the Avaya G250/G350 Media Gateway. The following table shows the meaning of the system LEDs when they are lit: Table 116: System LEDs Name Color Meaning Modem Detected...
Page 260: Analog Telephone Ports And Leds
Media Gateway Controller (MGC). Alarm An alarm is present on the board Test Green A test is in progress Activity Yellow A call is in progress 260 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 261: Media Module Leds
The physical LEDs provide board level status information, while the SAT provides Note: port level status information. Note: The G250 only supports the S8300 Media Server and the WAN media modules Note: (MM340 and MM342). LED locations on the media modules...
Page 262: S8300 Media Server Leds
LEDs during shutdown differs depending on the version of Avaya Communication Manager running: - For Avaya Communication Manager versions 1.2 and earlier, the fourth GREEN LED flashes at a constant rate until it finally glows steadily. - For Avaya Communication Manager version 1.3 and later, the fourth GREEN “Ok-to-Remove”...
Page 263: S8300 Led Differences From Media Modules
RED LED turns off. Note: For an S8300 configured as an LSP, the converse is true. If an Avaya G250/G350 Note: Media Gateway registers with an LSP, a major alarm is generated, and the RED LED turns on.
Page 264 Color Power On Reset BIOS Boot On-SW OS and SW Boot Off - SW System Up Off - SW H.248 Registered Off - SW Shutdown in Progress Shutdown Complete 264 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 265 Media module LEDs Table 120: Active – In Use Active – In Use Yellow Color Power On Reset BIOS Boot OS and SW Boot System Up On-SW H.248 Registered Off-SW Shutdown in Progress Shutdown Complete Table 121: OK to Remove OK to Remove Green Color...
Page 266: S8300 Led Lighting Sequence
Right LED in Services port - GREEN (10 MB link speed) – lights up then turns off At this point, you can connect to the S8300. When Avaya Communication Manager starts, the green TST LED turns on and stays on.
Page 267 Media module LEDs Table 122: E1/T1 LEDs (continued) Name Color Location Description YELLOW Third This LED indicates that the clock is synchronized with a source (usually the Central Office). The LED is blinking 2700 ms ON and 300 ms OFF. This is the most common condition.
Page 268: Synchronization
Operational control After successful initialization, the E1/T1 media module’s LEDs are controlled as follows: The Angel lights the YELLOW ACT LED when there is at least one non-idle trunk. If Avaya ● Communication Manager sends a message to drive the clock sync signals, the YELLOW ACT LED indicates this instead of the port busy/idle status.
Page 269: Avaya Mm314 Media Module Leds
The MM314’s alarm (ALM) LED is located on the lower left corner of the front panel. The ALM LED indicates that an alarm is present in the module, or that Avaya Communication Manager (CM) has the slot administered for a Voice media module.
Page 270 If the LED is lit, the port belongs to a LAG. Power over Ethernet If the LED is lit, the port is operating in PoE mode. 2 of 2 270 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 271: Chapter 7: Alarms
MO. If a hardware component incurs too many errors, an alarm is raised. Alarms on the S8300 Media Server with Avaya G250/G350 Media Gateways can occur in several areas: Media modules, Media Servers, and the Media Gateway are all capable of detecting ●...
Page 272: Alarm Classifications
Simple Network Management Protocol, the industry standard protocol governing network management and the monitoring of network devices and their functions. RTCP Real Time Control Protocol, contained in IETF RFC 1889. 1 of 2 272 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 273: Alarm-Related Leds
2 of 2 Alarm-related LEDs The following alarm-related LEDs appear on the faceplate of the G250/G350 or attendant console, and show how certain LEDs reflect specific alarm situations. Table 125: Alarm-Related LEDs Location...
Page 274: Alarm Content
Alarms Alarm content Alarms logged by Avaya Communication Manager are stored in an alarm log. All alarms include a date and time stamp that reflects the date and time of the sending device. The alarm contains: Device type ● Component type ●...
Page 275: Alarm Management
Avaya P333T User’s Guide. The Dynamic Trap Manager feature of the G250/G350 insures that SNMP traps and alarms are always sent to the currently active Media Gateway Controller. By default, the Dynamic Trap Manager sends all SNMP messages to the currently active MGC.
Page 276: Snmp Alarming On The G250/G350
2. Via this modem, a client PC uses the Point-to-Point Protocol (PPP) to access the Media Server and connect via telnet to a Linux shell. 3. Once logged into the Media Server, you can telnet out to G250/G350s and other devices on the network.
Page 277 The following procedure using the primary server’s Linux shell commands administers the dial-out modem to send alarms in the OSS method. In this example, the primary server is an S8300, and the services support agency is Avaya’s Initialization and Administration System (INADS).
Page 278: Configuring The G250/G350 To Send Snmpv3 Alarms
The Avaya G250/G350 Media Gateway uses SNMPv3 for traps and alarms. In order to configure the Avaya G250/G350 Media Gateway to send SNMP traps to the primary server you must enable the SNMP agent, specify the SNMP host, and setup SNMP authentication. You...
Page 279 Alarm management Refer to Table 126: SNMPv3 Notification Types on page 279 for a full list of notification types that can be configured. Table 126: SNMPv3 Notification Types Notification Type Description All notifications generic Generic traps hardware Hardware faults rmon RMON rising/falling alarm dhcp server DHCP server error, such as a DHCP IP conflict...
Page 280 Alarms Configure SNMPv3 authentication In order to use SNMPv3 authentication, you must create users, groups, and views for the G250/ G350. The G250/G350 provides several pre-configured views and groups for setting up SNMP authentication. Refer to Table 127: G250/G350 pre-configured views...
Page 281: Chapter 8: G250/G350 Traps
Chapter 8: G250/G350 traps A trap indicates a special condition that exists or an event that occurs within the Avaya G250/ G350 Media Gateway system. Some traps indicate configuration changes or component modifications and are merely informative. Other traps indicate warning or error conditions that may compromise the performance of the media gateway.
Page 282: G250/G350 Traps And Resolutions
Resolutions on page 282). “07/17/2002:13:45” is the event’s date and time stamp. ● “121.1.1.2” is the IP address for Telnet access to the alarmed Avaya G350 Media Gateway ● Processor (MGP). “cmgMultipleFanFault” is the trap name (3rd column of Table 129: G250/G350 Traps and ●...
Page 283 G250/G350 traps and resolutions Table 129: G250/G350 Traps and Resolutions (continued) Enterprise Trap Name Severity Description / Resolution Facility avayaG350 deleteSWRedundancyTrap Switch Info A redundancy link has been deleted. Fabric avayaG350 createSWRedundancyTrap Switch Info A redundancy link has been created for Fabric the specified ports.
Page 284 Replace the entire G250/G350. Fans and the PSU are not field replaceable. avEntTraps avEntFanOk Temp Notification A faulty fan has returned to normal functioning. 3 of 16 284 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 285 G250/G350 traps and resolutions Table 129: G250/G350 Traps and Resolutions (continued) Enterprise Trap Name Severity Description / Resolution Facility avEntTraps avEnt48vPwrFlt Supply There is a problem with the 48V power supply. 1. Check voltages. Use the CLI command show voltages to...
Page 286 If one is found, replace the media module. If no media module is found to be bad, the power supply is suspect. Replace the G250/G350. 5 of 16 286 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 287 G250/G350 traps and resolutions Table 129: G250/G350 Traps and Resolutions (continued) Enterprise Trap Name Severity Description / Resolution Facility avEntTraps avEntAmbientHiThresholdTempOk Temp The ambient temperature in the device has returned to the acceptable range. avEntTraps avEntAmbientLoThresholdTempFlt Temp The ambient temperature in the device is below the acceptable temperature range.
Page 288 The synchronization signal has been regained. 7 of 16 288 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 289 G250/G350 traps and resolutions Table 129: G250/G350 Traps and Resolutions (continued) Enterprise Trap Name Severity Description / Resolution Facility cmgTrapTypes cmgVoipHardwareFault Major A DSP complex serving the VoIP engines has failed. cmgTrapTypes cmgVoipHardwareClear The DSP complex serving the VoIP engines has returned to normal functioning.
Page 290 The low memory condition has been cleared. This occurs when the available memory rises above 5 MB. 9 of 16 290 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 291 G250/G350 traps and resolutions Table 129: G250/G350 Traps and Resolutions (continued) Enterprise Trap Name Severity Description / Resolution Facility cmgTrapTypes cmgFirmwareDownloadFault Major An attempt to download a software module has failed. 1. Check the event log to find the specific error.
Page 292 3. If the IP address in the mgc list matches the Media Server CLAN or the Media Server IP addresses, there may be a network problem. 4. Verify that the primary controller is 11 of 16 292 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 293 G250/G350 traps and resolutions Table 129: G250/G350 Traps and Resolutions (continued) Enterprise Trap Name Severity Description / Resolution Facility cmgTrapTypes cmgH248LinkDown Minor An H.248 link between the Media Gateway and its controller is down. 1. Check the S8300, S8500, or S8700/S8710.
Page 294 If service is impaired, reset the Media Gateway manually. Escalate and have Tier 3 personnel capture the trap information and the event logs for analysis. 13 of 16 294 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 295 G250/G350 traps and resolutions Table 129: G250/G350 Traps and Resolutions (continued) Enterprise Trap Name Severity Description / Resolution Facility cmgTrapTypes cmgModuleAutoReste Warning cmgModuleAutoReset — A media module in the Media Gateway automatically reset (rebooted). To resolve the problem, take the following steps: 1.
Page 296 4. If the problem persists, reboot the G250/G350. cmgTrapTypes cmgVoipOccFault cmgTrapTypes cmgVoipOccClear cmgTrapTypes cmgVoipAvgOccFault cmgTrapTypes cmgVoipAvgOccClear 15 of 16 296 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 297 G250/G350 traps and resolutions Table 129: G250/G350 Traps and Resolutions (continued) Enterprise Trap Name Severity Description / Resolution Facility cmgTrapTypes cmgVoipAutoReset Warning The VoIP module in the Media Gateway automatically reset.To resolve the problem, take the following steps: 1. Check if a maintenance test that resets the VoIP module was run.
Page 298 G250/G350 traps 298 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 299: Chapter 9: Media Server Alarms
Chapter 9: Media Server alarms In the Avaya S8300 Media Server with an Avaya G250/G350 Media Gateway system, some maintenance processes take place on the G250/G350 while others are controlled by Avaya Communication Manager and pertain to the S8300. Note:...
Page 300: Viewing The Alarm
S8300 alarms can be tested and corrected using SAT commands or the Web interface. If you run the Avaya Communication Manager application either from a Telnet session (SAT window) or Avaya Site Administration, you can use the following SAT commands to obtain more information.
Page 301: Alarming On An External Media Server
The S8300 functioning as a Local Survivable Processor (LSP) logs an alarm when it becomes active. It also logs an alarm for every Avaya G250/G350 Media Gateway that registers with it. It does NOT log alarms when IP phones register with it; rather, it logs a warning.
Page 302 Media Server alarms 302 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 303: Index
... . downloading using RFA ..via Avaya Site Administration Auto Fallback via external modem ....
Page 304 ..software and firmware requirements ....VoIP monitoring 304 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 305 ........G250/350 ....
Page 306 ....viewing alarms ..... . trap 306 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 307 Port diagnostic test ....supported by G250 ....8-port analog .
Page 308 ....DS1 CO trunk ....Subsystem listing 308 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...
Page 309 Index Tests, (continued) error codes ....8-port analog ....Updates test analog line port .
Page 310 Index 310 Maintenance for the Avaya G250 and Avaya G350 Media Gateways...

This manual is also suitable for:

G350

Avaya G250 Maintenance Manual

About this Book

Overview

Audience

Downloading this Book and Updates from the Web

Related Resources

Technical Assistance

Trademarks

Sending Us Comments

Chapter 1: Maintenance Overview

The G250/G350 with a Media Server System

Maintenance Strategy

Media Module Maintenance

Leds

Maintenance Access to the G250 and G350 and to the Media Servers

Upgrading Software

Plugging in and Unplugging the G250/G350

Useful Terms

Chapter 2: G250/G350 Component Maintenance

G250/G350 Component Maintenance

Facility Test Call

Setting G350 Synchronization

IP Telephones

Chapter 3: Avaya Communication Manager Controlled Maintenance

G250/G350 Subsystems Maintained by Avaya Communication Manager

Maintenance Commands

Dynamic Call Admission Control (CAC)

System Resets

Maintenance Objects

MO Groupings by MM Type

MO Test Commands

Abort Code 1412

Alarm-Pt (Alarm Port)

AN-LN-PT (Analog Line Port)

CO-DS1 (DS1 CO Trunk)

CO-TRK (Analog CO Trunk)

DID-DS1 (Direct Inward Dial Trunk)

DID-TRK (Direct Inward Dial Trunk)

DIG-LINE (Digital Line)

DIOD-TRK (DIOD Trunk)

ISDN-LNK (ISDN-PRI Signaling Link Port)

ISDN-SGR (ISDN-PRI Signaling Group)

ISDN-TRK (DS1 ISDN Trunk)

PLAT-ALM (Platform Alarms)

TIE-DS1 (DS1 Tie Trunk)

WAE-PORT (Wideband Access Endpoint Port)

XXX-BD (Common Port Media Module)

Chapter 4: License and Authentication Files

License and Authentication File Installation

License Files for Different Configurations

License File Modes

License and Options Forms Interactions

Chapter 5: Access and Login Procedures

Connection Overview

Connecting a Laptop to the S8300 Services Port

Connection Methods

Log in Methods

Avaya Site Administration

Navigational Aid for CLI Commands

Terminal Emulation Function Keys for Avaya Communication Manager

Chapter 6: G250/G350 and Media Module Leds

Front Panel Leds

Media Module Leds

Chapter 7: Alarms

Introduction

Background Terms

Alarm-Related Leds

Alarm Content

Qos Alarms

Alarm Management

Chapter 8: G250/G350 Traps

Alarm Format

G250/G350 Traps and Resolutions

Chapter 9: Media Server Alarms

Media Server Alarms

Avaya Communication Manager Alarms

Index

Quick Links

Related Manuals for Avaya G250

Summary of Contents for Avaya G250