Base template; changes from time to time (see …



[pic]

Avaya Communication Manager

(Release 1.3.1)

with an Avaya DEFINITY® Server R

Load R011r.03.1.531.0

Change Notice 1364B

Attachment Package 700241888:

Field technician/engineer general information 2

Update notes 6

Update procedures 9

“Standard (simplex) reliability” update procedures 9

“High/critical (duplicated) reliability” update procedures 11

Label formats 13

Reference documents 14

Change description 14

Hardware/firmware minimum vintage table 14

Adjunct minimum vintage table 14

Related documentation 14

Field technician/engineer general information

Overview

The purpose of this Change Notice is to provide new features, enhancements, and modifications for customers running Avaya Communication Manager Release 1.1 or 1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3 (all Communication Manager loads prior to R011r.03.1.531.0), with an Avaya DEFINITY( Server R. For more detail, see the Change Description referenced on page 14 of this document.

This Change Notice is to be reactively applied to Avaya Communication Manager Release 1.1 or 1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3 (all Communication Manager loads prior to R011r.03.1.531.0), with an Avaya DEFINITY Server R requiring this load to correct a problem, per Customer, Avaya Sales/Service, or Authorized BusinessPartner request and approved (verifying that the customer has a valid target configuration) by Tier III or the Center of Excellence (CoE).

This change is technician installable and is service interrupting.

Coordination with other Change Notices is not required.

Material Requirements

Contact 800-422-6560, prompt 4, prompt 1 for all Avaya U.S. Direct material concerns.

U.S. Authorized BusinessPartners receive material shipped from the National Distribution Center. The service center at 800-222-7278 is the contact for all Avaya U.S. Indirect material concerns.

The ITAC/GSO (International Technical Assistance Center/Global Services Organization) Change Notice Administration Group in Denver is the contact for all non-U.S. material concerns and coordinates the ordering of material per the actual customer requirements shown on the ticket created in the implementation process.

The following material is required to implement this Change Notice and should be ordered from the Denver factory via this Change Notice:

|System |Comcode |Quantity |Description |

|Unduplicated |700236847 |2 |Magneto Optical Disk |

|Duplicated |700236847 |4 |Magneto Optical Disk |

|Simplex 2 |700276413 |1 |DEF SFTW SERVER R COMMUNICATION MANGER 1.3.1 MO |

|Duplex 4 | | | |

|All |700261704 |1 |ASA 1.3 Software CD |

The following material is also required to implement this Change Notice and should be downloaded. Please DO NOT order this material via this Change Notice. To download the necessary material:

1. Go to and click Product Documentation.

2. In the list on the left, click Communications Systems.

3. Find Communication Manager. Under that, click 1.3.1.

4. Under 1.3.1, click Installation & Maintenance, and then click

Communication Manager 1.3.1 Attachment Package for Server R.

|System |Qty |Code/Comcode |Description |

|All |1 |700241888 |Attachment Package (See Note Below) |

Note: Attachment Package 700241888 (this document) provides the following:

- Technician General Information - Hardware/Firmware Minimum Vintage Table

- Update Notes - Adjunct Minimum Vintage Table

- Update Procedures - Change Description

- Label Formats - Document Reference List

Notify the customer of how the Change Description accompanying this upgrade can be found on the Avaya support Web site:

1. Go to and click Product Documentation.

2. In the list on the left, click Communication Systems.

3. Find Communication Manager. Under that, click 1.3.1.

4. Under User Information, click DEFINITY Servers: Release Notes (Release 1.3.1 of the

Avaya Communication Manager).

5. On the bottom of the page under Files, click the link View HTML.

6. In the left hand pane, click the link titled Resolutions and Patches. This will present a list of .pdf documents

describing the changes from Release 1.3.

See the tables below for the billing breakdown of services based on contract terms.

U.S. Billing Information

|Warranty/Maintenance Contract/Self Maintenance Customers |

|Material |No charge - for all customers |

|Helpline Assistance |No charge - for all customers |

|Technician Labor | 8AM-5PM |5PM-8AM |

| |M-F No Charge |M-F Applicable Overtime Rate |

| |S-S Applicable Overtime Rate |S-S Applicable Overtime Rate |

|Time and Material (T&M) Customers |

|Material |No charge - for all customers |

|Helpline Assistance |Standard Charges Apply |

|Technician Labor | 8AM-5PM |5PM-8AM |

| |M-F Standard Rate |M-F Applicable Overtime Rate |

| |S-S Applicable Overtime Rate |S-S Applicable Overtime Rate |

Non-U.S. Billing Information

Warranty/Maintenance Contract/Self Maintenance Offer Customers -

Helpline assistance is available at the CoEs at no charge. No customer charges for material. Customer charges for labor apply for work performed outside of normal business hours.

T&M Customers –

Helpline assistance is available at the CoEs at the predetermined in-country labor rate.

No customer charges for material. Labor charges for technician time apply at the predetermined in-country labor rate.

Upgrade Instructions

In addition to travel time, it should take a technician an estimated 1.5 hours, maximum, for a simplex system software update or 2 hours, maximum, for a duplicated system software update per the instructions provided in the Update procedures section starting on page 9. Service is interrupted for approximately 10-15 minutes for an upgrade to a simplex system. Service is interrupted for less than one minute for a duplicated system software update on a DEFINITY Server R, except as indicated in the Update Procedures that begin on page 9.

The update instructions in this document are applicable only when updating the load on a configuration already running Avaya Communication Manager Release 1.1 or 1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3, with a valid license file installed. Adding features or changing processor hardware requires the creation and installation of a license file using the Remote Feature Activation (RFA) process. See the RFA web site at for further information. See the RFA Users Guide, chapter 5, on the aforementioned web site.

Avaya Site Administration version 1.11.05 is the minimum network administration solution required for Avaya Communication Manager Release 1.1 or 1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3, with an Avaya DEFINITY Server R (hereafter Communication Manager R 1.1 or 1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3).

Material Disposition

U.S. Direct, U.S. Indirect, Non-U.S. Direct, and Non-U.S. Indirect: There are no returns required per this Change Notice.

U.S. Indirect: The optical disks with software earlier than R011r.03.1.531.0 should be destroyed and disposed of locally in accordance with environmental guidelines. These optical disks are not reusable with any other software load and should not be left in a useable condition. Compliance with this measure prevents old software from being mistakenly re-installed, causing system problems.

The optical disks with R011r.03.1.531.0 software are to remain with the system. One optical disk should remain in each optical disk drive (TN2211). Additional optical disks should be given to the customer.

U.S. Indirect: The National Distribution Service Center will close the ticket immediately, since there are no returns required per this Change Notice.

Technical Escalation

The formal Technical Escalation Process to be used for technical questions pertaining to the application of this Change Notice is:

U.S. Direct: Contact the Technician “Help-Me” line at 1-800-248-1234 for assistance.

U.S. Indirect: Contact the Technician “Help-Me” line at 1-877-295-0099 for assistance.

NON-U.S.: Customers and dealers contact their Regional CoE.

Normal escalation procedures apply to this Change Notice.

Technician Time Reporting

Field Technicians implementing this change for U.S. customers are to report all activity for this Change Notice using the Activity Code “S”.

All arrangements for reimbursement/credit to BusinessPartner Accounts for implementation of this Change Notice follow standard processes. Contact local CoE Change Notice Coordinators for details on this process.

Technicians report their time to the appropriate Regional Workgroup Service Manager in order to log their expenses to the appropriate International Change Notice Monthly Activity Report.

Reimbursement is limited as per the following:

|Class S3 (Software) Time and Expense Authorization |

|U.S. |Avaya Warranty and Maintenance |Time and Material |

|Travel Time to Site |0.75 hour |0.75 hour |

|Implementation Time (per site) Simplex System |1.5 hours |1.5 hours |

|Duplicated System |2 hours |2 hours |

|Travel Expense |N/A |No reimbursement |

|Shipping Expense |N/A |No reimbursement |

|NON-U.S. |Avaya Warranty and Maintenance |Time and Material |

|Travel Time to Site |0.75 hours |0.75 hour |

|Implementation Time (per site) Simplex System |1.5 hours |1.5 hours |

|Duplicated System |2 hours |2 hours |

|Travel Expense |N/A |No reimbursement |

|Shipping Expense |N/A |No reimbursement |

Update notes

WARNING

READ THE FOLLOWING NOTES BEFORE PROCEEDING WITH THE UPDATE!

This information is intended to aid in the software update process.

WARNING!! WARNING!! WARNING!! WARNING!! WARNING!! WARNING!!

The update instructions in this document are applicable only when updating the load on configurations already running Communication Manager 1.1 or 1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3 with a valid license file installed. Upgrading from a previous release, adding features, or changing processor/MSS-NET (Mass Storage System Network Control) hardware requires the creation and installation of a license file using the RFA process. You must take training and pass a certification test before registering to use the RFA process. See the DEFINITY RFA URL:



The most recent Communication Manager 1.1 init password change was made in load 01.0.059.0. Please contact the TSC (Technical Service Center) Data Base Administration group at 1-800-422-6560 for the new init password.

The default secret keys for Access Security Gateway (ASG) were also changed in load 01.0.059.0 for the craft, inads, and init logins. The new default secret keys are invoked for new software installs only. For updates and upgrades, the secret keys saved in translations remain in effect. For security reasons, most hand-held ASG challenge/response devices are no longer supported.

The default Product Identifier (PID) was changed in load 01.0.059.0 to indicate default ASG secret key selection to services and provisioning tools. Like the default ASG secret keys, the default PID is invoked only for new software installs. The existing PID is preserved during software updates or upgrades.

Before beginning the update, review the following for customer impact:

1. Multimedia Call Handling:

Multimedia-to-voice station calls are not preserved during an update. In order to properly release multimedia conversion resources and restore them to service after the update, the following steps must be executed prior to updating a Communication Manager 1.1 or 1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3 switch that has the Multimedia Call Handling (MMCH) customer option turned on. These steps apply only to High/Critical (duplicated) reliability configurations.

● Locate all MULTIMEDIA INTERFACE circuit cards (TN787) in the system using the “list configuration all” command.

● Locate all VOICE CONDITIONER circuit cards (TN788) in the system using the “list configuration all” command.

● Busy-out all MULTIMEDIA INTERFACE and VOICE CONDITIONER circuit cards using the “busyout board” command. This prevents any further multimedia-to-voice connections and drops any active connections.

Failure to busy-out the circuit cards before doing the update may result in unusable Multimedia Interface (TN787) and Voice Conditioner (TN788) ports.

2. Daylight Savings Rule:

Check to make sure that the system defaults to a rule value of “0”. Or, if the customer wants the switch to change time automatically for daylight savings, make sure that whatever number is selected for the Daylight Savings Rule on the SAT (System Access Terminal) screen “set time” is also entered as the “daylight savings rule” on the SAT screen “change locations”.

3. Basic System Features:

● The “upgrade software” command preserves only calls in which two or more parties are connected and talking. Held calls, dialing calls, calls in queue, and calls connected to announcements, speech synthesis, or tones are not preserved. The only supported operation on a preserved call is to drop it. Other feature activation attempts are ignored.

● For a call-preserving update, the length of time during which calls cannot be originated is very short (estimated at less than 5 seconds for most cases). In the worst case, it is estimated that there can be up to 1 minute of service outage. The length of the service outage is dependent on the number of calls active when the SPE (Switch Processing Element) interchange occurs.

● Status information is lost on a “reset system 3” and therefore on an update. This impacts user-controlled restrictions and group-controlled restrictions which are kept as status information in the switch.

● ISDN trunk facilities may go out-of-service during an update. Verify that the facilities are in-service after completion of the update process. If the trunks are not in-service, busy/release the trunk group. If the trunks are still out-of-service, contact the network service provider in order to restart the trunk group.

● Wireless facilities may go out-of-service during an update. Verify that the facilities are in-service after completion of the update process. If the wireless stations are not in-service, busy/release the station. A “reset system 3” also brings the wireless facilities back into service; however, this may result in other service outages.

● Calls over wireless facilities are not preserved during an update.

● IP telephony calls are not preserved during an update.

● Attendant features are lost. Some features have to be reactivated following the update, including night service; trunk/hunt group control; and manual/clock-manual override status on time-of-day routing.

● Administered connections are dropped. They are automatically re-established after the interchange.

● SPE-based “Leave Word Calling” messages are not preserved. All SPE-based “Leave Word Calling” messages are lost.

● After the update, lamps may be inconsistent for up to an hour (until background maintenance completes one cycle).

● Use the “change system-parameters features” command to disable TTI (Terminal Translation Initialization) changes during the update.

● Find all Maintenance Objects (MOs) that are demand-busied-out. Enter the “display errors print” command and select “Error Type 18”. All demand-busied-out MOs are lost during all forms of update and must be re-entered afterward.

● Disable scheduled maintenance to prevent any conflicts during the update. Note that it must be rescheduled after the update has been successfully completed.

● Reports that are currently printing or queued to print are lost (“list report-scheduler” command). The technician may delay the update until they have finished printing. The “status sp-link” command indicates if reports are printing; the link state is “up” if the system printer is available.

● If a user dials a TAC (Trunk Access Code) for a trunk and then dials less than the minimum number of digits needed to make it a valid number dialed, the trunk is not disconnected from the TDM bus. This results in noise on some talkpaths.

4. ACD (Automatic Call Distribution) Update Information:

● ACD queues are lost after an update. There is no mechanism in mips-processor switches to drain the queues. CMS (Call Management System) or BCMS (Basic CMS) can be used to monitor queue lengths. If it is important to empty all queues before the update, the technician must coordinate with the customer to redirect traffic away from ACD splits before the update, for example, by changing vectors to temporarily route calls to a disconnect announcement.

● All ACD agents are logged out after an update and must re-login to receive calls.

● Status lamps associated with ACD are incorrect after the update. The lamp inconsistencies are corrected by background maintenance within 1 hour.

● The CMS link is dropped and restarted. This causes CMS data to be lost after the update. The amount of CMS data lost can be minimized if the update is done just after the last CMS measurement interval.

● All measurement data is lost after a software update (including BCMS). If needed, the reports may be printed prior to the update.

5. Property Management System (PMS) Features:

● Client Room Names are temporarily lost on an update and need to be restored by the PMS. This happens automatically since the PMS link drops and is re-established, triggering a database swap.

● “list wakeup print” shows scheduled wakeup calls. The technician should consider rescheduling to avoid conflicting with large numbers of scheduled wakeup calls, or printing the report and rescheduling them after the update.

● “list do-not-disturb print” shows stations with do-not-disturb activated. This status is lost during an update and must be re-entered after an update is completed.

6. Validating System Health Before Upgrading:

Use the following commands to verify the overall health of the switch before starting the upgrade:

● status spe – Shows the overall state of the system. Any alarms shown could preclude the update and should be investigated before proceeding. The “Health” of both the active and standby SPEs should be “Functional”.

● status logins – Shows active logins to the system. Only the technician should be logged into the system during an update.

● display alarms – Shows active alarms, which may preclude the update.

● display errors – Shows active system errors, which may preclude the update.

● status health – Shows the current system load. It is recommended to postpone the update if call-processing occupancy is greater than 50%. Nothing prevents the technician from updating under heavy call load, but customer impact is more noticeable.

7. Translation Sanity Check

Validate the sanity of the existing translations before upgrading to the new load, using the following steps:

● Execute “list station type 7303s” (or some other infrequently administered station type) and “list trunk-group” commands. Note that on larger systems (greater than 500 stations), this check may take several minutes.

● If the response “Error encountered, can’t complete request” appears, discontinue the update and proceed with the Technical Escalation process.

Update procedures

“Standard (simplex) reliability” update procedures

WARNING

These procedures are applicable only when updating a switch already running Communication Manager 1.1 or 1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3 software. To upgrade an R from a previous release to Communication Manager 1.1, see the instructions in the “Upgrades and Additions” manual (555-233-115), available online under Product Documentation at .

No administration changes should be entered during the following software update procedure. There can be substantial time gaps between steps and, since the system cannot prevent administration changes, it is up to the system technician to see that none are attempted before the update completes. Use the “status login” command to see that no one, including the customer, is logged into the switch during the update.

|Step |Action |Minutes (Optical|Purpose |Service |

| | |Disk) | |Affecting? |

|1 |Login as craft and verify that Communication Manager 1.1 or |2 |Determine that a valid license is installed. |No |

| |1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3 software is installed and | |Changing processor hardware, increasing | |

| |there are no “License Error” or “No License” warning messages. | |capacities, or adding features requires | |

| | | |creating a new license file through the RFA | |

| | | |process. | |

|2 |Validate system sanity, as described in “Validating System |5 |Verify that the system is operating properly. |No |

| |Health Before Upgrading” on page 8 of this document. | | | |

|3 |Disable TTI using the change system-parameters features command.|2 |Prevent background activity from interfering |No |

| | | |with the update. TTI must be re-activated after| |

| | | |the update. | |

|4 |Disable scheduled maintenance using the change system-parameters|2 |Prevent background activity from interfering |No |

| |maintenance command. Set the “start time” field to a value after| |with the update. Scheduled maintenance must be | |

| |the update will complete. If scheduled maintenance is active, | |re-activated after the update. | |

| |set the “stop time” field to 1 minute from now. | | | |

|5 |If a TN750/B announcement circuit card is present, and the |40 |Save volatile announcements. |No |

| |customer has not backed up the annaouncements on it, execute | | | |

| |save announcements | | | |

|6 |If MMCH is active, use list config all to find all TN787 and |variable |Remove TN787 and TN788 boards from service. |Yes |

| |TN788 boards, and then use the busyout board command to remove | | | |

| |them from service. | | | |

|7 |Execute save translation |2 |Preserve existing translations. |No |

|8 |Execute backup disk |9 |Back up the current software load to the |No |

| | | |removable media. Do not press the return key | |

| | | |once execution begins. Doing so clears the | |

| | | |screen immediately after the backup completes, | |

| | | |thus losing any messages. | |

|9 |Remove the backup removable media. |1 |Keep the backup in a safe place. |No |

|10 |Insert the new removable media. |1 |Check that the optical disk, if any, is NOT |No |

| | | |write-protected. | |

|11 |Execute list config soft |3 |Verify that the removable media contains the |No |

| | | |expected new load. | |

|12 |Execute restore disk install |3 |Copy the new software version on the removable |No |

| | | |media to disk. | |

|13 |Execute upgrade software R011r.03.1.531.0 |15 |Reboot the new load, causing a service outage. |Yes |

| |Follow the instructions on the screen. | | | |

| |Install the license file, if necessary. | | | |

|14 |Login as craft and check that no “translation corruption” |1 |Verify that the upgraded translations are sane.|No |

| |messages are displayed | | | |

|15 |Enable scheduled maintenance using change system-parameters |2 |Re-enable scheduled maintenance. |No |

| |maintenance and set the “Start” and “Stop” time fields to their | | | |

| |original values. | | | |

|16 |If TTI was originally enabled, re-enable TTI using change |2 |Re-enable TTI. |No |

| |system-parameters features | | | |

|17 |Use the release busyout command to release any TN787 and TN788 |2 |Re-enable TN787 and 788 boards as needed. |No |

| |boards busied in step 12. | | | |

|18 |Validate system sanity, as described in “Validating System |5 |Verify that the system is operating properly. |No |

| |Health Before Upgrading” on page 8 of this document. | | | |

|19 |When the system is confirmed to be running normally, execute |10 |Save the upgraded translations. Investigate any|No |

| |save translation | |errors, and do not override any warnings. Doing| |

| | | |so could cause total loss of translations. | |

| | | |Follow the Technical Escalation Procedure if | |

| | | |any problems are encountered. | |

|20 |Execute backup disk |9 |Back up the current software load to the |No |

| | | |removable media. Do not press the return key | |

| | | |once execution begins. Doing so clears the | |

| | | |screen immediately after the backup completes, | |

| | | |thus losing any messages. | |

|21 |Execute list config soft |3 |Conduct final verification of installed files. |No |

|22 |Inform the appropriate organization that the update is complete.|5 |Inform INADS (Initialization and Administration|No |

| | | |System) administration by calling | |

| | | |1-800-248-1234 (US/Canada only). | |

| | | |For non-US sites, notify the appropriate CoE in| |

| | | |the International CoE Contact Table on page 12.| |

Back Out Procedure

If, after escalating problems through the Technical Escalation procedure, it is necessary to revert to the original software load, insert the backup removable media and execute the restore disk full command followed by the reset system 4 command. Use the list configuration software-version command to verify software release information in memory, disk, and removable media.

“High/critical (duplicated) reliability” update procedures

WARNING

These procedures are applicable only when updating a switch already running Communication Manager 1.1 or 1.1.1 software. To upgrade an R from a previous release to Communication Manager 1.1, see the instructions in the “Upgrades and Additions” manual (555-233-115), available online under Product Documentation at .

No administration changes should be entered during the following software update procedure. There can be substantial time gaps between steps and, since the system cannot prevent administration changes, it is up to the system technician to see that none are attempted before the update completes. Use the “status login” command to see that no one, including the customer, is logged into the switch during the update.

|Step |Action |Minutes (Optical |Purpose |Service |

| | |Disk) | |Affecting? |

|1 |Login as craft and verify that Communication Manager 1.1 or |2 |Determine that a valid license is installed. |No |

| |1.1.1 or 1.1.2 or 1.1.3 or 1.2 or 1.3 software is installed and | |Changing processor hardware, increasing | |

| |there are no “License Error” or “No License” warning messages. | |capacities, or adding features requires | |

| | | |creating a new license file through the RFA | |

| | | |process. | |

|2 |Validate system sanity, as described in “Validating System |5 |Verify that the system is operating properly. |No |

| |Health Before Upgrading” on page 8 of this document. | | | |

|3 |Disable TTI using the change system-parameters features command.|2 |Prevent background activity from interfering |No |

| | | |with the update. TTI must be re-activated after| |

| | | |the update. | |

|4 |Disable scheduled maintenance using the change system-parameters|2 |Prevent background activity from interfering |No |

| |maintenance command. Set the “start time” field to a value after| |with the update. Scheduled maintenance must be | |

| |the update will complete. If scheduled maintenance is active, | |re-activated after the update. | |

| |set the “stop time” field to 1 minute from now. | | | |

|5 |If a TN750/B announcement circuit card is present, and the |40 |Save volatile announcements. |No |

| |customer has not backed up the annaouncements on it, execute | | | |

| |save announcements | | | |

|6 |Execute save translation |2 |Preserve existing translations. |No |

|7 |Execute backup disk |9 |Back up the current software load to the |No |

| | | |removable media. Do not press the return key | |

| | | |once execution begins. Doing so clears the | |

| | | |screen immediately after the backup completes, | |

| | | |thus losing any messages. | |

|8 |Remove the backup removable media. |1 |Keep the backup in a safe place. |No |

|9 |Insert the new removable media. |1 |Check that the optical disk, if any, is NOT |No |

| | | |write-protected. | |

|10 |Execute list config soft long |3 |Verify that the removable media contains the |No |

| | | |expected new load. | |

|11 |Execute restore disk install both |3 |Copy the new software version on the removable |No |

| | | |media to disk. | |

|12 |If MMCH is active, use list config all to find all TN787 and |variable |Remove TN787 and TN788 boards from service. |Yes |

| |TN788 boards, and then use the busyout board command to remove | | | |

| |them from service. | | | |

|13 |Execute upgrade software R011r.03.1.531.0 |15 |Reboot the new load, causing a service outage. |Yes |

|14 |Login as craft and check that no “translation corruption” |1 |Verify that the upgraded translations are sane.|No |

| |messages are displayed | | | |

|15 |Execute status spe |5 |Repeat this command until standby handshake = |No |

| | | |yes | |

|16 |Execute reset spe-standby 4 |1 |Install new software load on the standby SPE. |No |

|17 |Execute status spe |5 |Repeat this command until both SPEs’ “state of |No |

| | | |health” is “functional”. | |

|18 |Enable scheduled maintenance using change system-parameters |2 |Re-enable scheduled maintenance. |No |

| |maintenance and set the “Start” and “Stop” time fields to their | | | |

| |original values. | | | |

|19 |If TTI was originally enabled, re-enable TTI using change |2 |Re-enable TTI. |No |

| |system-parameters features | | | |

|20 |Use the release busyout command to release any TN787 and TN788 |2 |Re-enable TN787 and 788 boards as needed. |No |

| |boards busied in step 12. | | | |

|21 |Validate system sanity, as described in “Validating System |5 |Verify that the system is operating properly. |No |

| |Health Before Upgrading” on page 8 of this document. | | | |

|22 |When the system is confirmed to be running normally, execute |10 |Save the upgraded translations. Investigate any|No |

| |save translation | |errors, and do not override any warnings. Doing| |

| | | |so could cause total loss of translations. | |

| | | |Follow the Technical Escalation Procedure if | |

| | | |any problems are encountered. | |

|23 |Execute backup disk |9 |Back up the current software load to the |No |

| | | |removable media. Do not press the return key | |

| | | |once execution begins. Doing so clears the | |

| | | |screen immediately after the backup completes, | |

| | | |thus losing any messages. | |

|24 |Execute test stored-data long |9 |Verify all MSS files are consistent. |No |

|25 |Execute list config soft long |3 |Conduct final verification of installed files. |No |

|26 |Inform the appropriate organization that the update is complete.|5 |Inform INADS (Initialization and Administration|No |

| | | |System) administration by calling | |

| | | |1-800-248-1234 (US/Canada only). | |

| | | |For non-US sites, notify the appropriate CoE in| |

| | | |the International CoE Contact Table below. | |

International CoE Contact Table

|Location |Number |

|AVAYA USA/Canada TSO (Technical Services Organization) |800-422-6560, prompt 4 |

|AVAYA RSC Hungary |361-345-4334 |

|AVAYA Caribbean and Latin America Headquarters |786-331-0860 |

|AVAYA Western Europe CoE (Guildford) |44-8702-410-518 |

|AVAYA Asia/Pacific Regional Support Center |65-872-8686 |

Back Out Procedure

If, after escalating problems through the Technical Escalation procedure, it is necessary to revert to the original software load, insert the backup removable media and execute the restore disk full command followed by the reset system 4 command. Follow that with the reset spe-standby 4 command. Use the list configuration software-version command to verify software release information for memory, disk, and removable-media.

Label formats

The following information shall be imprinted on the MV 1.3.1 G3r MO label:

Reference documents

If the screen asks you to log in as you retrieve these documents, log in as anonymous, without a password.

Change description

For the change description for Communication Manager 1.3.1:

1. Go to and click Product Documentation.

2. In the list on the left, click Communication Systems.

3. Find Communication Manager. Under that, click 1.3.1.

4. Under User Information, click DEFINITY Servers: Release Notes (Release 1.3.1 of the

Avaya Communication Manager).

5. On the bottom of the page under Files, click the link View HTML.

6. In the left hand pane, click the link titled Resolutions and Patches. This will present a list of .pdf documents

describing the changes from Release 1.3.

.

Hardware/firmware minimum vintage table

The hardware and firmware minimum vintage table can be found at .

Adjunct minimum vintage table

The adjunct minimum vintage table can be found at .

Related documentation

For documentation on Communication Manager with a Server R:

1. Go to and click Product Documentation.

2. In the list that appears at the left, click Communications Systems.

3. Click Avaya Communication Manager.

S8700: go to . A further, extended list of documentation appears, for both S8700 IP Connect and S8700 Multi-Connect, under MultiVantage and Resources.

S8300: go to . A further, extended list of documentation appears in this document under Supporting Library.

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

-----------------------

Avaya DEFINITY( Server R

Avaya MultiVantageTM Software 1.2

11r.01.2.110.4.

Comcode # 700236847

Avaya Proprietary – Restricted

Limited Use Software

Registration Enclosed

Copyright( 2002 Avaya Inc.

All Rights Reserved

[pic]

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download