Product Support Notice

Transcription

1 Product Support Notice 2007 Avaya Inc. All Rights Reserved. PSN# PSN001471u Original publication date: 10-Aug This is Issue #2, published 14- Severity/risk level High Urgency Optional Nov Name of problem Proactive Contact PG230 and Predictive Dialing System Switch Database Conversion Tool Issues. Products affected Proactive Contact 3.0 Problem description An issue was discovered in the conversion utility supplied with generic 16.1 Rev 1 (16.1.1). The increased number of port addresses introduced in this release caused an increase in the number of port entries in the database port table. Each card table entry contains an index into port table to associate the port configurations with a given card. This index was correctly modified to reflect the port table changes. There were other indexes buried in the card entry sub-structures that were not modified. These indexes are used exclusively for writing port configurations to disk. The result is that modifications of port configurations, for ports above the 0x3FF timeslot, will get written to the wrong entries of the port table. The result might not be seen until the switch is rebooted. One noticeable symptom is that the ports listed in a resource group may be inconsistent with the port count for that group and port configuration screens. The conversion utility has been corrected in generic 16.1 Rev2 (16.1.2). In addition, the install utility will block upgrade to Rev-2 unless the Rev-1 database has been cleaned manually. This is done by deleting card.tbl, port.tbl, resgroup.tbl and nfascnfg.tbl files in the c:/dbase directory and then rebooting the switch. This causes empty and uncorrupted versions of these files to be created. Symptoms from the Database Conversion tool (16.1.1) issue vary from site to site. The problem becomes worse when more database related changes are made after the Database Conversion step. Symptoms include: Loss of COS (Class of Service) causing ports to fail Unable to delete cards from a Resource Group Ports which are in the Resource Group do not display in the Resource Group One-way audio on QT1PRI ports Resolution Switch generic has been released with a corrected Database Conversion tool. Any system which is upgraded from a version prior to directly to will not have the above problem. NOTE 1: A switch may NOT be upgraded to or later WITHOUT the switch being reconfigured following the procedures below. NOTE 2: If a switch has been recently upgraded to and an old backup is available made PRIOR to the upgrade to , you can avoid the above problem by performing a full Installation of , and restore the database from the old database backup disk that was made PRIOR to the upgrade to Then use the Database Conversion tool included with the generic (labeled 16.1 Rev. 2 on the disks). WARNING: Old Avaya service cards (ECPA, ECC, EDRC, EMFCR2, DDC) are NOT COMPATIBLE with new port addresses made available in 16.1 or later. The new port addresses (in hex) are: and 7B0-7F7. If you configure an old card on 16.1.x or later, do NOT use the above port addresses. Specifically, when you add a card the switch will attempt to use port address 400 as the first port address for the card. If you have any of the above cards starting at port address 400, the card will not clear alarms (LEDs will be lit on the card). The Card Maintenance screen may show the card in service (state=a), but there will be LEDs lit on the front panel. Workaround: Use port address 400 on a QT1 or QE1 card or on a DSP2 card, not on an old ECPA, ECC, DDC, EDRC or EMFCR2 card.

2 Prior to beginning the configuration: 1. Verify that the dialer Digital Switch has not been previously configured: a. Log into the Digital Switch, go to Maintenance Menu, then select B, Disk Utilities, then A, Show Directory. Type: c: b. If the Digital Switch has been previously cleaned and reconfigured, a manual file called clean161.txt should exist in the root directory of the hard drive, such as shown here: Directory C:/ SUMMA4 <LABEL> BOOT <DIR> :42:18 DBASE <DIR> :39:32 LOG <DIR> :39:32 TRACE <DIR> :22:20 BLANK :25:32 GREETING :25:34 ZIP :25:34 ZIP :25:34 CLEAN161 TXT :05:48 If this file exists, the Digital Switch should be already clean; the reconfiguration has already been completed. Do not proceed. 2. Contact the customer and explain the need for their switch reconfiguration. 3. Open a Maestro case. 4. Schedule downtime for the reconfiguration to take place. Tell the customer that this will involve a reboot of the dialer switch, and cpu1 will also need to be restarted. Expected down time depends on the size of the system, the amount and thoroughness of preparation done beforehand, and whether the system will be reconfigured on a lab system or on the customer s live Digital Switch. For systems larger than about 200x400, it is recommended that a lab system be used for the reconfiguration to minimize down time and to allow more time to compare the lab configuration with the customer s configuration. Then the lab system configuration for the Digital Switch will be ftp d to the live system for installation. Because the reconfiguration will be done on a lab system, actual down time would be expected to be 90 minutes or less. For systems less than 200x400, the reconfiguration can be done on the customer s live system, and there should be at least 4 hours downtime allowed. 5. Determine from the customer whether their circuits consistently come into service after a switch reboot, or whether some might stay in alarm. This is especially true for circuits connected to a Meridian PBX. The customer should warn their phone line vendor and/or PBX technician that the dialer will be rebooted and circuits will be reset. 6. Warn the customer that once you have started your review of the Digital Switch for obtaining the current configuration, no changes are to be made to the Digital Switch until the reconfiguration is completed Avaya Inc. All Rights Reserved. Page 2

3 Preparation steps: Before the schedule configuration: Preparation Steps 1-2 below should be done ahead of the actual scheduled down time, and can be done while the system is dialing. Step 1: Back up the current switch database onto cpu1 in case the reconfiguration has to be aborted. a. On cpu1, type: go switch b. Make a new directory. Type: mkdir badswitchbackup c. Log into switch, go to Maintenance Menu, then select B, Disk Utilities. d. Backup the current switch database onto cpu1. From the Disk Utilities menu, select B, Copy Files. Copy from? c:/dbase/*.tbl Copy to? f:badswitchbackup The screen should show 16 files being copied. e. Press ctrl-x to return to main Disk Utilities menu. Step 2: Capture the current configuration details so that you can reconfigure the switch with the same configuration. f. On cpu1, obtain a screen capture of dgswitch.cfg. g. Use the swit utility and type: show tx ok err init switch1:2050 eportmap h. Obtain a screen shot of the eportmap results. Then type: ecards i. Obtain a screen shot of the ecards results. j. On the switch, go to Maintenance Menu, then Card Maintenance. Obtain a screen shot of the entire Card Maintenance screen. Press ctrl-x to return to Maintenance menu. k. Select G, Card Alarms IMPORTANT! Note any existing alarms on the switch. This will prevent you from unnecessary troubleshooting of these alarms after your reconfiguration files are loaded. l. Press ctrl-g to go to the main menu, then press A, Database administration, and select A, Card Summary. Display each card. Note the following: i. For each slot and span, note the Card Type ii. Note the current state, i.e. Active, Out of Service, Maintenance, Unused iii. For non-isdn (CAS) circuits, note the following: Span Type: SF or ESF Code Type: AMI or B8ZS Length: Usually Law: A or Mu CRC: On or off, if applicable Signaling type Inpulse Rule COS Note: The COS on active ports may show additional internal characters, such as T, U, C or P. You can ignore those. Only note whether the COS=2 or A2. iv. For QE1-CAS cards, display the TIMING screen. (Move the cursor under the TIMING column, type any character, then press Enter.) The baseline will show: QUAD E1 TRUNK TIMING CONFIGURATION SPAN LOCATION: R,L,S CARD TYPE: 4-Span Quad E1 CAS STATUS: Out of Service SEIZE FLASH-DET PULSE GUARD PORT NAME TIMEOUT MIN MAX SEND TIMEOUT (100ms) Avaya Inc. All Rights Reserved. Page 3

4 If the timing screen shows anything other than the above settings, obtain a screen shot. v. For QT1 cards, display the TIMING screen. (Move the cursor under the TIMING column, type any character, and then press Enter.) The baseline will show: TRUNK TIMING CONFIGURATION SPAN LOCATION: R,L,S CARD TYPE: 96-Port Quad T1 STATUS: Out of Service WINK-DET. WINK FLASH-DET. FLASH OFFHK ONHK GUARD AUTODROP PORT NAME MIN MAX SEND MIN MAX SEND MIN MIN -- (100 MS) If your system shows anything other than the above values, get a screen capture. vi. For ISDN circuits (QT1PRI, QE1PRI, PRI/N, E1-PRI, etc.), note the following: Access Type CA IP Rule Switch Type Span Length (for QT1PRI or PRIN only) Span Type: ESF, ECR4 or DCR4 A/Mu Law COS Note: The COS on active ports may show additional internal characters, such as T, U, C or P. You can ignore those. Only note whether the COS=2 or A2. Note: EVERY phone line (outbound, inbound, transfer or headset port) used by the dialer MUST have a COS. Any ports missing the COS should be corrected Avaya Inc. All Rights Reserved. Page 4

5 h. From menu A, Database Administration, select B, Resource Group Summary. Obtain a screen shot of the current Resource Group Summary. Warning: The Resource Group Summary screen may be corrupted and show the wrong number of ports in the group. You will need to verify from dgswitch.cfg which ports SHOULD be in each Resource Group. Display each Resource Group. Note the following: Number of Resource Group Name of Resource Group Hunt Type: Usually CYCLIC Ports in the Resource Group Order of ports in the Resource Group Note: For headsets, it is best to match the order shown in dgswitch.cfg. For outbound and inbound lines, it is best to match the order in dgswitch.cfg. i. From menu A, Database Administration, select L, NFAS Group configuration. 1. If no configuration exists, note this and go to the next step. 2. For systems with NFAS groups configured, note the following for each group: NFAS group number NFAS group name Display the group and obtain a screen shot of each NFAS group. j. Go to menu C, Maintenance, select F, Master Timing Link Selection. Obtain a screen shot of this configuration. Reconfiguration Steps while the system is not dialing, or on a lab system Note for configuring on a lab system: Steps 3-10 below can be done on an Avaya lab dialer with a Digital Switch rather than the customer s Digital Switch. When the reconfiguration on the lab switch is complete, go to Step 11 below. [ ] Step 3: Remove the problem database files from the Digital Switch. 3A. From the Disk Utilities menu on the switch, select C, Delete Files. 3B. Delete the following files one at a time: c:/dbase/card.tbl c:/dbase/port.tbl c:/dbase/resgroup.tbl c:/dbase/nfascnfg.tbl Do this even if system is NOT using NFAS groups. Press ctrl-x to return to main Disk Utilities menu. 3C. Select A, Show Directory. Type: c:/dbase The following example shows the 14 files which should display. Directory C:/DBASE. <DIR> :53:34.. <DIR> :00:00 DBVERS TBL :51:00 EXROUTE TBL :07:48 HOSTCNFG TBL :07:40 IPRULE TBL :07:40 ISDNMSG TBL :07:42 ISDNSUPV TBL :07:42 OPRULE TBL :07:42 PROMPTLB TBL :57:48 ROUTESUM TBL :07: Avaya Inc. All Rights Reserved. Page 5

6 ROUTETBL TBL :07:46 SUPVTMPL TBL :07:40 SYSCNFG TBL :51:00 If the card.tbl, port.tbl, resgroup.tbl or nfascnfg.tbl files are listed, you made an error in your delete command. Correct this and repeat step C. 3D. Reboot the Digital Switch. Press ctrl-x to return to the Disk Utilities menu, and then press ctrl-x again to return to the Maintenance Menu. Then select I, Shutdown System, and press Enter to confirm, then R to reboot. Once the switch comes up, go to Maintenance Menu, then select A, Card Maintenance. The following should be displayed: C A R D M A I N T E N A N C E R L S CARD TYPE V.RV S R L S CARD TYPE V.RV S Enhanced Network Bus A Enhanced DTG O A)DD, D)ELETE, C)HANGE, P)ORT: PORTS: 1-64: : : : [ ] Step 4: Reconfigure the appropriate Tone Generator hardware to match the customer s system. The blank database included in the switch generic assumes that there is an old EDTG card in slot 2. When the switch is rebooted, wait a few minutes. If the card in slot 2 becomes active (state=a), then skip to Step 5. 4A. From the old Card Maintenance screen shot obtained in Step 2 above, determine the slot for the Tone Generator, usually in slot 2. What type of hardware is used? If a DSP2 card is used, the Card Maintenance screen will show something like the following: 2007 Avaya Inc. All Rights Reserved. Page 6

7 C A R D M A I N T E N A N C E R L S CARD TYPE V.RV S R L S CARD TYPE V.RV S Enhanced Network Bus A Tone Generator DSP S Tone Generator DSP A Port Quad T A Call Progress DSP A Port Quad T A Call Progress DSP A Port Quad T A Conference DSP A Port Quad T A Large Port Voice Card 2.00 A Port Quad T A Large Port Voice Card 2.03 A Port Quad T A Call Progress DSP A Port Quad T A Call Progress DSP A Port Quad T A Call Progress DSP A Port Quad T A If an old Summa Four DTG card is in use, the Card Maintenance screen will show something like this for slot 2: C A R D M A I N T E N A N C E R L S CARD TYPE V.RV S R L S CARD TYPE V.RV S Enhanced Network Bus A Port Quad T A Tone Generator (DTG) 1.15 A Port Quad T A Large Port Voice Card 2.03 A Port Quad T A Conference Card 1.02 A Port Quad T A Enhanced Call Progress 1.00 A Enhanced Call Progress 1.00 A Enhanced Call Progress 1.00 A Note: If there are more than one Tone Generator configured in the Digital Switch, use the one in slot 2 as the Active one (A) and configure it first. 4B. Delete the old EDTG from slot 2. Using the Maintenance Menu, select A, Card Maintenance. Then enter: D and press Enter. Press Enter again to confirm. This should delete the card in slot 2. 4C. Now add the appropriate slot, processor, and Card Type to match the Card Maintenance screen as determined in A above. For example: For DSP2 hardware, enter: A Tone Generator DSP2 and press Enter. Then activate the card, enter: C A and press Enter. For old DTG hardware, enter: A Tone Generator (DTG) and press Enter. Then activate the card, enter: C A and press Enter. 4D. If there are more than one Tone Generators in the customer s switch, add the Tone Generators as shown in the Card Maintenance screen shot from the customer s system. Note: The active Tone Generator card is always assigned port addresses 480-4BF hex. Any additional Tone Generators are assigned the same port addresses Avaya Inc. All Rights Reserved. Page 7

8 [ ] Step 5: Using the eportmap and ecards results obtained from the customer s system in Step 2 above, use swit to reconfigure all the cards, using the SAME port address as shown in the eportmap. This will ensure that the dgswitch.cfg file will match the reconfigured system. Sample ecards output: swit> = NBC = EDTG = ECC = ECPA = ECPA = LPVC = QT1X = QT1X96 Sample eportmap output (remember these port addresses are in hex): swit> 17:56:52 *** HOST <= NMA Request Enhanced Port Mapping = OK Ports => not used Ports => Ports => Ports 108-1C7 => not used Ports 1C8-1DF => Ports 1E0-1F7 => Ports 1F8-20F => Ports => Ports F => Ports => Ports F => Ports => Ports F => not used Ports 480-4FF => Ports 500-7AF => not used swit> 17:56:53 *** HOST <= NMA Request Enhanced Port Mapping = OK Ports 800-8BF => Ports 8C0-97F => Ports 980-BFF => not used 2007 Avaya Inc. All Rights Reserved. Page 8

9 To configure the example above onto the empty switch using swit, you would enter the cards starting from the lowest port address in the eportmap and working to the higher addresses. For this example, type the following commands in swit: init switch1:2050 add lpvc 8 (Note: Type lpvc for either LPVC or LPVC2 cards) add ecc2 88 add qt1x96 1c8 add qt1x add ecpa2 add ecpa2 Use the card type shown in the ecards results. [ ] Step 6: On the Digital Switch, go to menu A, then select A, Card Summary. Using the screen shots for each card which you obtained in Step 2 above, reconfigure each card exactly to match the screen shot and data you obtained. [ ] Step 7: Once all cards are configured, exit Card Summary, then select B, Resource Group Summary. 7A. Configure LPVC port in Resource Group 1. 7B. Configure ECPA ports in Resource Group 2. 7C. Configure DCC/ECC (conference) ports in Group 3. 7D. If applicable, configure EDRC ports in Group 4. 7E. Using dgswitch.cfg screen shot and Resource Group information, configure the following using the order listed in dgswitch.cfg: outbound lines inbound lines transfer trunks agent headsets 7F. Exit the Resource Group screen once all Resource Groups are configured. [ ] Step 8: If applicable, configure the NFAS group configuration. Select L, ISDN NFAS Group Summary. Configure NFAS group names and groups. [ ] Step 9: Configure the Master Timing Link Selection. Go to menu C, Maintenance, then select F, Master Timing Link Selection. Configure the information to match the screen shot taken previously. [ ] Step 10: Make a database backup on cpu1. 10A. On cpu1, type: go switch 10B. Make a directory for the new backup. Type: mkdir cleanswitch161 10C. From the Digital Switch menus, go to Menu C, then select B, Disk Utilities. Then select B, Copy Files. Copy from? c:/dbase/*.tbl Copy to? f:cleanswitch161 Press Enter and 16 files should be copied Avaya Inc. All Rights Reserved. Page 9

10 [ ] Step 11: For systems reconfigured on a lab system ONLY Reconfigurations done directly on a customer s system should skip to Step A. On cpu1 of the lab system, type: cd cleanswitch161.you should see 16 files, such as the following: $ ll total 496 -rw-rw-r-- 1 admin pds_system Apr 23 15:06 card.tbl -rw-rw-r-- 1 admin pds_system 270 Apr 23 15:06 dbvers.tbl -rw-rw-r-- 1 admin pds_system 1600 Apr 23 15:06 exroute.tbl -rw-rw-r-- 1 admin pds_system 792 Apr 23 15:06 hostcnfg.tbl -rw-rw-r-- 1 admin pds_system 1440 Apr 23 15:06 iprule.tbl -rw-rw-r-- 1 admin pds_system Apr 23 15:06 isdnmsg.tbl -rw-rw-r-- 1 admin pds_system 312 Apr 23 15:06 isdnsupv.tbl -rw-rw-r-- 1 admin pds_system 2886 Apr 23 15:06 nfascnfg.tbl -rw-rw-r-- 1 admin pds_system 1440 Apr 23 15:06 oprule.tbl -rw-rw-r-- 1 admin pds_system Apr 23 15:06 port.tbl -rw-rw-r-- 1 admin pds_system 1120 Apr 23 15:06 promptlb.tbl -rw-rw-r-- 1 admin pds_system 1024 Apr 23 15:06 resgroup.tbl -rw-rw-r-- 1 admin pds_system 300 Apr 23 15:06 routesum.tbl -rw-rw-r-- 1 admin pds_system Apr 23 15:06 routetbl.tbl -rw-rw-r-- 1 admin pds_system 480 Apr 23 15:06 supvtmpl.tbl -rw-rw-r-- 1 admin pds_system 2184 Apr 23 15:06 syscnfg.tbl 11B. On cpu1 of the customer s system, type: go switch. Then make a new directory. Type: mkdir cleanswitch161 11C. Using binary mode, ftp ONLY the following 4 files to /opt/avaya/pds/switch/cleanswitch161 on cpu1 of the customer s system: card.tbl port.tbl resgroup.tbl nfascnfg.tbl ftp this one even if not using NFAS groups 11D. Verify the checksum of each of these 4 files matches the checksum for these 4 files on the lab system cpu1. 11E. Log into the customer s Digital Switch. 11F. Select C, Maintenance, then B, Disk Utilities, then B, Copy Files. Copy the following files one at a time: Copy from: f:cleanswitch161/card.tbl Copy to: c:/dbase Do the same for: c:/dbase/port.tbl c:/dbase/resgroup.tbl c:/dbase/nfascnfg.tbl Do this even if NFAS not being used on this system. Press ctrl-x twice to return to the Maintenance menu Avaya Inc. All Rights Reserved. Page 10

11 [ ] Step 12: Reboot the customer s Digital Switch by pressing I, then Enter. Press Enter to confirm, then press R for Reboot. [ ] Step 13: Verify that all alarms clear, except for any pre-existing alarms determined from Step 2 above. [ ] Step 14: Restart cpu1 using stop/start_pds. [ ] Step 15: Make a marker file to indicate the switch has been cleaned. 15A. On cpu1, type: go switch 15B. Make a new file with vi called clean161.txt. In this file, simply state that the database that has been cleaned. For example: Switch version cleaned 07/19/2007, <name>. Save this file. Then from the switch menu C, then B (Disk Utilities), select B for Copy files. Copy from? f:clean161.txt Copy to? c: This will place the clean161.txt file on the root directory of the switch hard drive. Upgrades from to will REQUIRE the presence of this file to indicate the database has been cleaned. [ ] Step 16: TEST! Have an agent log in, place test calls on each outbound circuit, run a small job, etc. It is CRITICAL to verify that all T1 or E1 circuits function normally. Some C.O.s or PBXs may need to have circuits reset on the far-end after the reconfiguration. Coordinate this with the customer. [ ] Step 17: Monitor dialing during the next day or so. If the customer agrees that everything is normal, make a new backup disk of the customer s switch. Discard any OLD switch backup disks. [ ] Step 18: Close case. Upgrade to new switch generic version Once the database has been cleaned, then you may upgrade to new switch generic version as follows: 1. Insert SRK ENBC Generic 16.1 ( ) Rev 2 diskette #1 into the floppy drive. 2. Power-up the subrack. The switch displays: ENBC Main Boot Firmware v Reading boot file from disk device A:/boot/boot.sds Loading file A:/boot/genkern.exe Loading file A:/boot/install.exe Boot File System is [not] configured Ethernet option is [not] installed... NFS option is [not] installed... ISDN/PRI option is [not] installed... NFAS option is [not] installed... Installing disks Avaya Inc. All Rights Reserved. Page 11

12 Setting default device to C:... Installing NFS driver D I G I T A L S W I T C H I N S T A L L A T I O N U T I L I T I E S Version 16.1.X Tues Aug 7, :00:00 Copyright , Avaya Inc. All Rights Reserved. 1) Install/Configure Switch Generic Software 2) Incremental Install of Switch Generic Software 3) Disk Utilities 4) Install Another Software Option 5) Install/Configure Ethernet Option 6) Database Conversion 7) Set System Clock 8) Set Non-Volatile Memory 9) Terminate Installation Enter Selection: _ 3. If this version of the generic is installed on an ENBC loaded with EPROMs of versions earlier than 16.1 (pn ), you may receive the following message. If so, when prompted to save existing NVRAM settings, press y <ENTER>. This will initialize the checksum for the new gateway routing table added to NVRAM. *** NVRAM is corrupted and/or has a bad checksum! : 43 3A : 2F 62 6F 6F 74 2F C: /boot/ : : Use existing NVRAM settings? [y/n] y <ENTER> Workaround or alternative remediation Remarks Patch Notes The information in this section concerns the patch, if any, recommended in the Resolution above. Backup before applying the patch Download Patch install instructions Verification Service-interrupting? No 2007 Avaya Inc. All Rights Reserved. Page 12

13 Failure Patch uninstall instructions Security Notes The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks Avaya Security Vulnerability Classification Not Susceptible Mitigation For additional support, contact your Authorized Service Provider. Depending on your coverage entitlements, additional support may incur charges. Support is provided per your warranty or service contract terms unless otherwise specified. Avaya Support Contact Telephone U.S. Remote Technical Services Enterprise U.S. Remote Technical Services Small Medium Enterprise U.S. Remote Technical Services BusinessPartners for Enterprise Product BusinessPartners for Small Medium Product Please contact your distributor. Canada Caribbean and Latin America Europe, Middle East, and Africa Asia Pacific Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED AS IS. AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS AVAYA ), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA. All trademarks identified by or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners Avaya Inc. All Rights Reserved. Page 13