Upgrading the System. AT&T MERLIN LEGEND Release 3.1, MERLIN LEGEND Release 4.0

Upgrading the System

Upgrading the System

!

WARNING:

The following procedures are to be used by qualified technicians or service personnel only. Installation or maintenance of this product by anyone other than qualified personnel may damage or impair the product; your limited warranty does not cover such damage. For details, see your limited warranty in the Customer Support Information in the back of this book. Hazardous electrical voltages are present inside this product.

This section describes upgrading your communications system to Release 4.0.

You can use this procedure to perform the following upgrades:

■ From Release 1.0 to Release 4.0






NOTE:

You must have a version later than SPM 4.15 to upgrade from Release 3.1 to

Release 4.0.

MERLIN

â

II Communications System programming cannot be upgraded to this communications system. The new communications system must be completely reprogrammed.

2–48 Programming with SPM


Before You Begin

Before you begin the upgrade to Release 4.0, you will need the items listed below.

■ SPM Version 4.15 or later to back up and convert system programming information and to restore system programming information after the

Release 4.0 processor module has been installed.

■ One or both of the following:

–

Release 4.0 processor module (when converting from Release 2.1

or earlier.)

–

A forced installation PCMCIA memory card with Release 4.0

system software (when converting from any release).

■ DOS-formatted diskette

NOTE:

If SPM is already installed, the Welcome to SPM screen that appears when you start SPM identifies the version on both the last line of the console simulation window and in the upper left corner of the screen. If you are working with Version

4.15, V4 appears in the upper left-hand corner of the screen and Version 4.15

appears on the last line of the console simulation window.

Inter-Release Compatibility

It is important to understand compatibility between files created on each of the different versions of SPM, not only for upgrading but also for programming.

Table 2-6 summarizes programming compatibility. (It is assumed that the

majority of the programming is done in surrogate mode and backed up on disk).

Programming with SPM 2–49


Table 2–6. Programming Compatibility

2.09

2.16

3.18

4.15

2.16

3.18

4.15

3.18

4.15

4.15

1.16

2.09

2.16

3.18

4.15

SPM

Version

1.13

1.16

2.09

2.16

3.18

4.15

1.1

1.1

1.1

1.1

1.1

Program

Backup on 1.0

1.0

1.0

1.0

1.0

1.0

1.0

yes yes yes yes yes yes

2.0

2.0

2.0

2.0

2.1

2.1

2.1

3.0

3.0

4.0

no no no no no no no no no no no no no no no no no no no no no no no no no yes yes yes yes yes

1.1

no yes yes yes yes yes no no yes* yes* no yes* yes* yes yes no no no no yes* yes*

3.0

no no no no yes* yes* yes yes yes yes no no no no no no

Restore on

2.0/2.1

no no yes* yes* yes* yes* no yes* yes* yes* yes* no no no yes* no no yes* no yes* yes no no no no yes*

4.0

no no no no no yes*

* The backup file must be converted before it is restored.

NOTE:

The default barrier code and any programmed barrier codes from Release 2.1

and earlier will be carried over to Release 3.0 and later with no change and the barrier code length will be four (4). It is the responsibility of the system manager to change the barrier code length and the barrier codes if so desired.



Upgrade Procedure

1

2

3

4

Install SPM.

To upgrade the system to Release 4.0, you will need to install (or upgrade to)

Version 4.15 of SPM. See “Installing the SPM Software.”

Back up your system programming.

This step creates a file containing system programming information. See

“Backup.”

Turn off AC power switches on the control unit in the following order:

(1) Basic carrier

(2) Expansion carrier 1, if present

(3) Expansion carrier 2, if present.

Replace the processor module (when upgrading from Release 2.1 and earlier).

5 a. Unplug the interface cords from the SPM and SMDR printer ports on the processor module.

b. Remove the processor module from Slot 0.

c. Install the Release 4.0 processor module in Slot 0.

d. Plug the interface cords into the SPM and SMDR printer ports on the processor module.

Insert the forced installation memory card into the PCMCIA interface slot on the processor module.

6 Turn on the AC power switches on the control unit in the following order:



(3) Basic carrier.

7

8

IMPORTANT:

The system upgrade procedure must follow the order of the steps shown below.

Convert your backup file to Release 4.0 format.

This procedure converts the backup file created in Step 2. See “Convert.”

Restore your system programming.

The system is forced idle and cannot be used during this procedure. See

“Restore.”



9 Program new features.

If you wish to use the factory defaults for the new features available with Release

4.0, skip this step.

NOTE:

After upgrading to Release 3.0 or 4.0 from Release 1.0, 1.1, 2.0, or 2.1 some programming will be lost. You must reprogram the following:

■

■

■

Authorization Codes

Extensions ®

More

® AuthCode

SMDR Account Code Format

Options ® SMDR ® AuthCode

Inter-digit Timers

Options ®

More

® Interdigit

See Tables 2–7, 2–8, 2–9, 2–10, and 2–11 which follow this procedure.

■

Table 2–7.

Lists the features added with Release 1.1 of the

communications system.

■

Table 2–8.

Lists the features added with Release 2.0 or 2.1 of the


■

Table 2–9.



When you upgrade from Release 2.0 or 2.1 to Release 3.0, you must program these features as the last step of the upgrade procedure.

When you upgrade from Release 1.1 to Release 3.0, you must

program the features listed in Table 2–8, then the features listed in

Table 2–9.

When you upgrade from Release 1.0 to Release 3.0, you must first


Table 2–8, then the features listed in Table 2–9.

■

Table 2–10.



When you upgrade from Release 3.0 to Release 3.1

, you must program these features as the last step of the upgrade procedure.

When you upgrade from Release 2.0 or 2.1 to Release 3.1

, you must


Table 2–10.




, you must




, you must first


Table 2–8, then the features listed in Table 2–9, then the features listed in Table 2–10.

■

Table 2–11.



When you upgrade from Release 3.1 to Release 4.0, you must program these features as the last step of the upgrade procedure.



Table 2–11.

When you upgrade from Release 2.0 or 2.1 to Release 4.0, you must





Table 2–9, then the features listed in Table 2–10, then the features listed in Table 2–11.

When you upgrade from Release 1.0 to Release 4.0, you must first program the features listed in Table 2–7, then the features listed in

Table 2–8, then the features listed in Table 2–9, then the features listed in Table 2–10, then the features listed in Table 2–11.

Table 2–7. Programming Needed after Upgrade to Release 1.1

Feature Sequence

System language SysProgram

Extension language SysProgram

SMDR language

Printer language

SysProgram

SysProgram

®

More

® Language ® SystemLang

®

More

® Language ® Extensions

®

More

®

Language

®

SMDR

®

More

® Language ® Printer




Feature

Primary Rate

Interface (PRI)

DID Emulation on T1

Night Service

Sequence

SysProgram ® LinesTrunks ® LS/GS/DS1 ® Type ® PRI

SysProgram

®

LinesTrunks

®

LS /GS/DS1

®

FrameFormat

SysProgram ® LinesTrunks ® LS/GS/DS1 ® Suppression

SysProgram

®

LinesTrunks

®

PRI

®

PhoneNumber

SysProgram ® LinesTrunks ® PRI ® B-ChannlGrp

SysProgram ® LinesTrunks ® PRI ® NumbrToSend

SysProgram ® LinesTrunks ® PRI ® Test TelNum

SysProgram ® LinesTrunks ® PRI ® Protocol

SysProgram

®

LinesTrunks

®

PRI

®

DialPlanRtg

SysProgram ® LinesTrunks ® PRI ® OutgoingTbl

SysProgram

®

Tables

®

ARS

SysProgram ® LinesTrunks ® LS/GS/DS1 ® Type ®

More

®

DID/All DID

SysProgram ® NightSrvce ® GroupAssign ® Calling Group

Calling Group

Coverage VMS Off SysProgram ®

More

® Cntr-Prg ® Program Ext

Data Status

Extension Copy

Posted Message

SysProgram

®

More

®

Cntr-Prg

®

Program Ext

SysProgram ®

More

® Cntr-Prg ® Copy Ext

SysProgram

®

More

®

Cntr-Prg

®

Program Ext button on analog multiline and MLX-10 non-display telephones (for use with Do Not Disturb)




Feature

Automatic Backup

Incoming Call Line

Identification Delay

Remote Access

Barrier Codes

Authorization Codes

Sequence

SysProgram ® System ® Back/Restore ® Auto Backup

LinesTrunks

®

More

®

LS-ID Delay

®

Drop

®

Dial trunk no.

® Enter

LinesTrunks

®

RemoteAccss

®

BarrierCode

®

Code Info

® Code Length

LinesTrunks

®

RemoteAccss

®

BarrierCode

®

Code Info

® Code Entry

Extensions

®

More

®

Auth Code


Feature Sequence

Trunk-to-Trunk Transfer Extensions ®

More

®

More

® TrkTransfer ®

Toggle LED

On/Off or Dial ext. no.

® Enter ® Exit ® Exit

Second Dial Tone Timer Options ®

More

® SecDT ® dial second dial tone timer value

® Enter


Feature

Delayed Call

Forwarding

Group Calling Overflow and Thresholds

Voice Announce on a

QCC

2B Data

Sequence

Extensions

®

More

®

Delay Frwd

®

Dial ext. no.

®

Enter

®

Dial no. of delay rings

® Enter

Extensions

®

More

®

Grp Calling

®

Overflow

®

Dial calling group ext. no.

® Enter ®

Dial ext. no.

® Enter ®

Number Based Overflow

®

Drop

®

Dial no. of calls

®

Enter ® Time Based Overflow ®

Drop

®

Dial no. of seconds

® Enter

Operator ® Queued Call ®

More

® Voice Annc ® Enabled or Disabled ® Enter

Data ® 2B Data ®

Dial adjunct ext. no.

® Enter

Continued on next page



Table 2–11, Continued

Basic Rate Interface

(BRI)

LinesTrunks ®

More

® BRI ® SPID/DN .

®

Dial line/trunk no.

® Enter ®

Drop

®

Dial SPID

® Enter ®

Drop

®

Dial DN

®

Enter

LinesTrunks

®

More

®

BRI

®

Timers

®

Select timer

®

Drop

®

Dial no. of seconds or ms

® Enter

Clock Synchronization LinesTrunks

®

More

®

ClockSync

®

Primary

®

Drop

®

Dial slot no.

® Enter ®

Dial port no. OR Select source of synchronization

® Enter ® Secondary ®

Dial slot no.

®

Ringing Frequency

(016 module)

Board Renumber

Enter ®

Dial port no. OR Select source of synchronization

® Enter ® Tertiary ® dial slot no.

® Enter ®

Dial port no.

OR Select source of synchronization

® Enter

Options ®

More

® Ringing Freq ® dial slot no.

®

Select

20Hz or 25Hz

System

®

Enter

® Board Renum ® Yes

(When an 012 module is replaced by an 016 module)

Switched 56 Data To select T1- All Tie, Switched 56 Data:

LinesTrunks

®

LS/GS/DS1

®

Dial slot no.

®

Enter

®

Type

®

T1 ® Enter ® All TIE ® Enter ® S56 ® Enter ®

Dial channel no.

® Enter ® Exit ® Exit ® Exit ® Exit

LinesTrunks ® LS/GS/DS1 ®

Dial slot no.

® Enter ® Type ®

T1

®

Enter

®

TIE

®

Enter

®

S56

®

Enter

®

Dial channel no.

® Enter ® Exit ® Exit ® Exit ® Exit

To select T1: All Switched 56 Data:

LinesTrunks

®

LS/GS/DS1

®

Dial slot no.

®

Enter

®

Type

®

T1 ® Enter ®

More

® ALL S56 Data ® Enter ®

Select

Direction , Intype , Outtype , AnsSupv , Disconnect , Inmode , or Outmode ®

Program options

® Enter ® Exit ® Exit ®

Exit ® Exit

To select T1: Switched 56 Data:

LinesTrunks

®

LS/GS/DS1

®

Dial slot no.

®

Enter

®

Type

®

T1 ® Enter ®

More

® S56 Data ® Enter ®

Dial channel no.

® Enter ®

Select Direction , Intype , Outtype , AnsSupv ,

Disconnect , Inmode , or Outmode ®

Program options

®

Enter ® Exit ® Exit ® Exit ® Exit

Continued on next page



Table 2–11, Continued

Switched 56 Data

Network Dial Plan

Routing

To specify Expected Digits:

LinesTrunks ®

MORE

®

T1 Data NW

® S56 Dial Plan

Routing

®

Expected Digits

®

Drop

®

Dial expected digits

® Enter ® Exit ® Exit ® Exit

To specify Delete Digits:

LinesTrunks

®

MORE

®

T1 Data NW

®

S56 Dial Plan

Routing ® Delete Digits ®

Drop

®

Dial delete digits

®

Enter ® Exit ® Exit ® Exit

To specify Add Digits:

LinesTrunks

®

MORE

®

T1 Data NW

®

S56 Dial Plan

Routing ® Add Digits ®

Drop

®

Dial add digits

® Enter ®

Exit

®

Exit

®

Exit


Upgrading the System. AT&T MERLIN LEGEND Release 3.1, MERLIN LEGEND Release 4.0

Upgrading the System

–

–

Related manuals

Table of contents

Upgrading the System. AT&T MERLIN LEGEND Release 3.1, MERLIN LEGEND Release 4.0