cn4006.doc - Avayasupport.avaya.com/elmodocs2/Octel/config/Cn4026.doc · Web viewEnter the name and...

Configuration Note 4026 - Ver C (3/01)

Avaya Definity G2 VoiceBridge II (Bridged Mode)

ANALOGPORTS

TRUNK

TDMBUS

CPU

ACP OR I/ODISTRIBUTION

BOARD

ATICs

DIGITALTN754B

Lucent Definity G2 Octel 350

Minimum Software Release 1.0

Minimum ReleaseGeneric 2

XXX

VOICE PATH

Multiple Return to OperatorOutcalling

Auto-Attendant

Call ID

VOICEBRIDGE

MWI On/Off

LINE

1.0 METHOD OF INTEGRATIONThe VoiceBridge emulates a 7434D digital display telephone. When a call

appears at the VoiceBridge, it simultaneously rings at a bridged analog appearance corresponding to an Octel voice port. The VoiceBridge creates and passes a standard Simplified Message Desk Interface (SMDI) packet containing the call information provided by the PBX, to the Octel system which then answers with the proper greeting.

2.0 OCTEL ORDERING INFORMATION§ Analog TICs (ATICs), 12 ports

per TIC

§ Disk Drives (SCSI drives require Release 5.0 or higher)

§ VoiceBridge II integration packageVersion 3.2

§ RS-232 Integration Software

§ In-Band Integration Software (only if using in-band MWI option)

§ Minimum Software: Aria 1.0

§ Asynchronous Communications Processor (ACP), optionalDisclaimer: Configuration Notes are designed to be a general guide reflecting AVAYA Inc.’s experience configuring its systems. These notes cannot anticipate every configuration possibility given the inherent variations in all hardware and software products. Please understand that you may experience a problem not detailed in a Configuration Note. If so, please notify the TAC/TSO at (408) 922-1822 and if appropriate we will include it in our next revision. AVAYA Inc. accepts no responsibility for errors or omissions contained herein.

O c t e l 3 5 0

M e s s a g e S e r v e r

The VoiceBridge emulates a digital 7434D set

Octel requirements

Avaya Definity G2 (VB2) C o n f i d e n t i a l

2

§ Integration cables, one per VoiceBridge (057-1174-000)

3.0 PBX HARDWARE REQUIREMENTS§ Digital 7434D ports, one per

VoiceBridge

§ Analog ports, one per Octel 350 voice port. For faster disconnect, Octel recommends using ports from circuit packs SN228 or SN229B. See section 8.10 for more details.

§ One analog port for remote service access (RDAC)

§ One analog port per VBII (optional)

§ 25 pair cables, with one right-angle, male-amphenol connector, one per ATIC

3.1 PBX SOFTWARE REQUIREMENTS§ Supported Software: Generic 2

4.0 SUPPORTED INTEGRATION FEATURES§ Call coverage to personal greeting

- busy- ring-no-answer

§ Station forward to personal greeting- all calls

§ Message-Waiting Indicator- lights- audible message waiting

§ Automated Attendant

§ Outcalling

§ Multiple return-to-operator

§ Direct Call

§ Multiple Greetings - busy- no answer

§ Call Sender

§ Personal greeting of original-called party using Call Coverage

§ Reply to message left by subscriber in internal telephone-answering mode

The information contained in this document is provided by AVAYA Inc. to serve as a guide. See the disclaimer on page 1

PBX hardware requirements

PBX software requirements

Supported integration features


3

4.1 ATTENDANT CONSOLE FUNCTIONALITY¨ The attendant console can

transfer callers into a subscribers mailbox by dialing the system access number directly, then entering a valid mailbox number and releasing.

o The Avaya PBX does not support attendant console overflow to a hunt group. Attendant calls cannot overflow to an Octel system. There are two possible alternatives:

1. Split the incoming trunks into two groups, directing half to the console and half to the voice module.

2. Configure the voice module pilot number as the Night Answer for the console. Then, when the console becomes busy, the attendant can switch to night service sending subsequent calls to the Octel system.

Note:

When the console is in night mode, features such as Recall to operator, are not available. Please consult your Avaya representative before changing trunk or attendant console programming.

5.0 CONFIGURING THE Avaya PBX TO INTEGRATE

Six tasks must be completed when programming the PBX to integrate. They are as follows:

§ Create Single Line Sets (analog voice ports)

§ Create ACD Group with Octel 350 system access number and then assign Single Line Sets

§ Configure each analog voice port as a bridged call appearance on the 7434D set.

§ Program a digital port as a 7434D station for each VoiceBridge on your system.

§ Create call coverage path(s) that include the Octel 350 system access number.

§ Change subscriber's station programming to include the proper name field information and call coverage path.

5.1 ANALOG 2500 SET ADMINISTRATIONo Define the integrated analog voice ports that will connect to the Octel

system. They must be configured as 'Single Line Sets'.

o Create an extension number without assigning an equipment location using Single Terminal Translation PROC 000, WORD 1:


Attendant console functionality

Define the analog voice ports that will connect to the Octel

system


4

Field 1 XXXXX Extension number Fields 2-6 XXXXXXXX ELL (do not assign) Field 7 XX Class of Service.Field 8 - Port Type - Extension administered in Procedure 052 Word 1

The remaining fields should not be changed.

o Assign each analog extension to an ELL using the Multiple Terminal and Data Module Translation Procedure, PROC 051, WORD 1:

Fields 1-5: XXXXXXX Terminal equipment location of the analog ports

Field 6: 10 Terminal Type (SLS)Field 7: 1 Option - Voice onlyFields 8-9: - Not assignedField 10: 2 Origination is Prime LineField 11: 0 Termination is None


5.2 AVAYA 7434D DIGITAL SET ADMINISTRATIONEstablish an ACD group pilot number which all subscribers dial to access the VPM and which contains the analog bridged call appearances as members. Figure 1 shows the button configuration for the 7434D set. This set is assigned 10 call appearances and a bridged call appearance for each integrated Octel voice port. Up to 24 bridged call appearances can be assigned.



5

Figure 1. 7434D Station Set-Up.

Conf

Drop

Trans

Hold

Call-AppCall-App

Call-App

Call-App

Call-App

Call-App

Call-App

Call-App

Call-App

Call-App

Br-Ap 1 Br-Ap 2

Br-Ap 3

Br-Ap 4

Br-Ap 5

Br-Ap 6

Br-Ap 7

Br-Ap 8

Br-Ap 9

Br-Ap 10

Br-Ap 11

Br-Ap 12

Br-Ap 16

Br-Ap 17

Br-Ap 18

Br-Ap 19

Br-Ap 20

Br-Ap 21

Br-Ap 22

Br-Ap 23

Br-Ap 24

Br-Ap 14

Br-Ap 15

Message

Mute Br-Ap 13

Select

Speaker

1 2 3

4 5 6

7 8 9

0 #*

o Configure the “Integrated 7434D” using the multiple appearance set procedure, PROC 051, WORD 1:

Fields 1-5: XXXXXXX Terminal equipment location of the digital port

Field 6: 40 Terminal type:7434DField 7: 5 Option: Terminal displayField 8: -- Not assignedField 9: 1 Display: 1 Display moduleField 10: 1 Idle LineField 11: 2 Ringing LineField 12: 0 NoField 13: -- N/AField 14: 0 NoField 15: - N/AField 16: - N/AField 17: 0 ISDN Advantage is Disabled

o Assign the “Integrated 7434D” extension created previously as 10 line appearances on buttons 3 - 12 of the 7434D set using the Multi appearance Terminal/Data Module - Line Appearance Procedure, PROC 052, WORD 1:

Fields 1-5: XXXXXXX Terminal equipment location of the 7434D port

Field 6: 0 Device type is Basic Set



6

Field 7: xx Member (buttons 3 - 12)Field 8 XXXXX Extension number assigned in

PROC 000 WORD 1Field 9: xx Line Appearance (1 - 10)Field 10: 0 Line type is No Prime LineField 11 1 RingingField 12: 1 Home terminal - YesField 13: 0 Originate only - No

Buttons 1 and 2 are default for Hold and Message Waiting.


Repeat the above steps for each line appearance.

o Assign each of the analog extensions as bridged call appearances on the “Integrated 7434D” set using the Multi Appearance Terminal/Data Module - Line Appearance Procedure, PROC 052, WORD 1:

Fields 1-5: XXXXXXX Terminal equipment location of the 7434D port

Field 6: 0 Device type is Basic SetField 7: xx Member (buttons 13 - 36)Field 8 XXXXX Extension number assigned in

PROC 000 WORD 1 (analog port)

Field 9: 1 Line Appearance Field 10: 0 Line type is No Prime LineField 11 1 Ringing type - RingingField 12: 0 Home terminal - NoField 13: 0 Originate only - NoField 14: 0 SAC group - NoField 15: 1 Button Type - Line appearance

(from PROC 052 WORD 1)

Repeat the above steps for each bridged call appearance.

o Assign the 'normal' mode feature to the first button of the digital display, using PROC 054 WORD 4:

Fields 1-5: xxxxxxx Terminal equipment location of 7434D digital port

Field 6: 3 Device type of display moduleField 7: 01 Point to first feature buttonField 8: 0 Normal Feature Button Code

o The analog appearances must now be placed in a ACD. ACD Programming varies by s/w version. Please refer to the Avaya Technician or the Avaya Admin. Manual for your PBX version.



7

¨ Define the dedicated analog MWI ports (OPTIONAL)

In-Band MWI is an option. On most new installations it is recommended that all MWI functions be performed by the VB(s) over the RS-232 integration link. If this is an upgrade of an existing system that already has in-band MWI ports defined, or needs to have more MWI ports added contact TAC for assistance.

VBII(s) used for dedicated MWI should be configured as per “Integrated 7434D” except that “bridged call appearances” are not required and “LWC Activation?” should be set to Yes.

The number of ports that will be dedicated to perform MWI tasks is dependent on call traffic and in particular MWI traffic. It is recommended that at least 1 port be dedicated for this function for every 24 integrated voice ports. If excessive delays are encountered in activating or deactivating subscribers message waiting indicator, more ports could be dedicated. See section 8.8 of this note.

§ The MWI ports would be identical to the voice ports. The only difference will be "LWC Activation?" should be set to Yes..

Notes:

Do not place the message-waiting ports in the above ACD group. Instead, all-calls forward these analog appearance(s) to the ACD pilot number.

All message-waiting ports must be configured within the first ten TIC cards, i.e., within the first 120 ports, ports 1A through 10L. If ports 11A - 12L are used for message waiting, message-waiting lights

may not extinguish.

o Assign to the ACD group of Octel ports the name “VOICEMAIL” using PROC 012, WORD 1. The entire name should be entered in capital letters with no spaces appearing within it.

o If Call Vectoring software is configured on the PBX, the following additional steps must be completed after the ACD programming

1. Create a vector directory number, or VDN, using PROC 000, WORD 1. This number will serve as the Octel system access number.

2. Create a vector using PROC 030, WORD 3. Configure it with the following step:

Vector Number: (assign a number)

Step Number: 1


Assign the bridged appearances as members of an ACD group

If Call Vectoring software is configured on the PBX, the

following additional steps must be completed after the ACD

programming


8

Step Type: 1 - Queue-to-main-split

Destination: (assign the ACD split of the Octel ports)

3. To provide callers with a busy signal instead of queuing when all Octel ports are busy, configure two additional steps with PROC 000, WORD 1:

Step Number: 2

Step Type: 5 - Delay

Step Number: 3

Step Type: 8 - Forced-busy

4. Using PROC 031, WORD 1, associate the VDN created for Octel System Access in step 1 with the vector just configured in step 2.

o The final step is to 'Auto-in' and 'Staff-in' the analog appearances. Breakout each analog port from the 25-pair cable to a 2500 telephone set and dial the access codes for the two features. Replace the cable at the 350 backplane. Later PBX software levels will perform this action automatically.

o Subscribers must have the ACD Group Number placed in their call coverage path to allow the 350 to automatically answer their phone.

o Any station that can be reached through unsupervised transfer applications (automated attendant, return-to-operator, or ECP) must have call coverage-busy programmed. Otherwise, callers will be disconnect when the Octel systems attempts an unsupervised transfer.

The pilot number of the ACD Group, or the VDN if the PBX has Call Vectoring software, is the 350 Access Number. Subscribers call this extension number to access their mailboxes.

5.1 VDN INTEGRATIONIntegration is provided for Vector Directory Numbers (VDNs) on Definity G2 PBXs. Typical

Applications that use VDNs are ACD and DNIS. When calls to VDNs are routed through Call Vectoring to the Octel system, the greeting of the mailbox corresponding to the VDN is heard.

For VDN integration applications, to retain a VDN as the original-called party throughout the call vectoring steps associated with it, do not program VDN Display Override. This is programmed in PROC 031, WORD 1, FIELD 9, and when assigned to a VDN, might cause the VDN call ID to change during call vectoring process.


Integration is provided for Vector Directory Numbers

(VDNs) on Definity G2 PBXs


9

5.3 CALL COVERAGE PATH ADMINISTRATIONA coverage path forwards calls to

another extension if the station is in use or not answered. Placing the Octel System Access Number in a coverage path will send busy and ring-no-answer calls to the Octel system to be answered.

o Use PROC 11, WORD 1, to create a coverage path:

Field 1: xxxx Coverage path group numberField 2: 3 Cover on Active - All types of callsField 3: 3 Cover on Busy - All type of callsField 4: 0 Do not cover on All CallsField 5: 3 Cover on Did Not Answer - All types of

callsField 6: 3 Cover on third ringField 7: 0 Coverage point is an extensionField 8: 1 Coverage point number (1-3)Field 9: xxxxx Octel System Access Number

5.4 SUBSCRIBER ADMINISTRATIONSubscriber administration has two parts: administering the name field, and assigning the call coverage path.

o For a station to integrate, the entire extension number must appear within the first 16 characters of the subscriber name field. Each site may have a different format for name placement in these fields; the only requirement for integration is that the extension number appear. Long names may need abbreviating. Here are some examples of valid name field entries:

Smith, John 210John 210 Smith210 John SmithJohn Smith 210Livingston, S 202

Numbers other than the extension number may be included if they have fewer digits than the extension number. For example, "Conf Rm 3, 230" is acceptable.

Note:

If the Avaya Integrated Directory Feature is implemented then the name must precede the extension number. Also a period between the name and mailbox will cause the Integrated Directory Feature on the G2 to not display that name, therefore always use a comma.

o Use PROC 12, WORD 1, to enter the extension number in the name field for each subscriber:


Configuring a call coverage path

Performing subscriber administration


10

Field 1: xxxxx Extension number of subscriberField 2: 1 Type of extensionField 3: 01 First Display CharacterField 4: -- UnassignedField 5: 0 Add nameField 6: -- Unassigned

o Enter the name and extension in word 2. Refer to the table in PROC 12 for the character codes.

Field 1 1 Segment number 1-3Fields 2-11 xx Character codes

o Use PROC 000, WORD 2, to assign a coverage path to a subscriber extension:

Field 1: xxxxx Extension number of subscriberField 6: xxxx Coverage Path group number

o Use PROC 63 to assign a Message Waiting lamp to a subscriber extension:

Field 1: xxxxx Extension number of subscriberField 2-6 xxxxxxx Terminal equipment location of

subscriberField 7: 0 Device Type is basic unitField 8: 2 Locate at feature button 2 (MWL)

Note:

Field 8 should be set to 0 for single line sets.

6.0 CONFIGURING 350 SERVER o Menu 0 - First Time Setup

§ Message Waiting Special: (Program to Y when using more the one in-band MW port) - OPTIONAL.

Note:If this is not a new installation contact Octel TAC for assistance in converting to multiple in-band MWI ports.

o Menu 1.1 - System Parameters

§ Type of PBX connected to: 3 - 1A ESS/SMDI, Full Duplex

§ Number of Digits in Extension used for MWI: 4 or 5


Configuring the 350 system management menus


11

§ Sender ID Used for Telephone Answering Messages: 2 - Calling Party, if Known

o Menu 4.1 - Port Assignments

§ Extension/Phone No.: It is important that this column

contain the nine-digit number associated with each link, LLGGGMMMM, defined as follows:

LL = physical link number (01-03)GGG = message desk number (001-063)MMMM = logical terminal number (LTN) of each analog port (0001-0024)

The physical link number corresponds with the connector on the I/O board of the Octel 350. See Table 1 below.

The message desk number must match the message desk number to be programmed into the VoiceBridge unit.

All nine digits must be entered. Each entry must be unique. The use of the physical link number, however, allows redundant message desk/terminal number coordinates to be used a long as they are spread across separate links.

See Table 1 below for an example of a 3 VB installation with 72 integrated ports. This field is optional for all other non-integrated ports.

Table 1. Menu 4.1 Assignments

VB #1

Port1A1B1C1D

2L3A3B3C3D

4L5A5B5C5D

6L

VB #2

VB #3

Extension / Phone No.010010001010010002010010003010010004

010010024020020001020020002020020003020020004

020020024030030001030030002030030003030030004

030030024

§ I column: Y (N for OPTIONAL dedicated MWI ports)


Define Menu 4 port assignments per customer requirements


12

§ O column: Y (the number of outcalling ports is customer traffic dependent)

§ T column: Y (N for any ports that will not do telephone answering)

§ M column: N (see note)

§ N,P,F columns: (Networking, Paging, and Fax ports are customer site dependent)

§ Line Type: 35 ( integrated ports )

3 (dedicated MWI ports )

6 (all other non-integrated ports)

§ D column: 4 (4, or 5 only for dedicated MWI ports, Line Type 3)

Note:

§ MWI functions can be handled by the VB . In-band MWI is also an option, contact TAC for specific information on setting up in-band MWI ports instead of VB MWI. It is recommended that new installs use VB MWI.

o Menu 6.1 - Transfer Dialing Sequences

§ "Flash" On-hook Time: 500 ms

§ "Pause" Time: 1000 ms

§ Dialing sequence to Transfer a Call: FPN

§ Dialing sequence to Reconnect with a Call -

Ring/No Answer: FFBusy: FF

Note:

Verify these dialing sequences for your PBX.

o Menu 6.2 - In-Band Integration

§ Dialing Sequence to Activate Message Waiting: *4N

§ Dialing Sequence to Deactivate Message Waiting: #4N

§ Reset Message Waiting on System Boot: Y

Note:


Define transfer and reconnect dial sequences


13

This menu applies only for installations that use in-band MWI. The Leave Word Calling feature codes are programmable (CH FEA) on the G2, verify these dialing sequences for your PBX.

¨ Menu 6.3 - Define CPU Serial Channels:

• For each configurable serial channel (channels 1, 2 and 3) to be used for direct integration, assign channel type 3 - Direct Integration.

When 'Direct Integration' is chosen for a serial channel configuration, you will need to program menu 6.5.1 for each link. (See bullet on Menu 6.5.)

• If ACP integration is being used, configure the integration links in Menu 6.5. ACP integration links do not use CPU serial channels, and therefore, do not require programming in Menu 6.3.

Notes:

Channel 4 is always used for the primary system management/local service and is not configurable.

The Octel 350 must be rebooted to apply any changes to serial channel parameters.

¨ Menu 6.5 - Integration Link Management

The following link information must be defined for each VB.

§ Link Number: (1-3)

§ Link Name:Type of Switch to which the System is Integrated: 3 - 1A ESS/SMDI, Full DuplexBaud Rate: 3 - 9600 BaudNumber of Data Bits: 0 - 7 Data BitsNumber of Stop Bits: 0 - 1 Stop BitsParity (None/Odd/Even): 2 - Even ParityXON/XOFF: 1 - Ignore XON/XOFFCarrier Detect: 0 - Carrier Detect UsedExtension to Check SMDI Message Waiting: 5551212Max. Msg. Waiting Operations per second: 1Switch Number to which this Link is Associated: 1 SMDI link down alarm threshold counter: 1

NOTE:

After any changes are made in Menu 6.5.2, reset the affected integration link(s) using Menu 6.5.5

¨ Menu 8/9.1 - Subscriber Mailbox Profile



14

• Subscriber’s Extension Number: If the subscriber is allowed to have message waiting, enter his or her phone number in this entry.

• Message Waiting Allowed: Y

• Intg. Link Number: (see section 8.10)

(Message Waiting should only be allowed for valid extensions on the PBX that are configured with a message waiting indicator.)

6.1 CONFIGURING THE DEFINITY G2 PBX TO INTEGRATE WITH MULTIPLE VOICEBRIDGE UNITS

One additional digital 7434D port is required for each additional VoiceBridge. Follow the programming instructions previously described when the additional VoiceBridges are installed. Care should be taken in the following areas:

§ Assign the additional analog voice port extensions as bridged call appearances on the 7434D buttons associated with each additional VoiceBridge. Each VoiceBridge will support a maximum of 24 integrated voice ports.

§ All integrated voice port extensions must be included as members of the hunt group. They should be defined in an alternating sequential order of button appearances from each VoiceBridge to distribute the load across each VoiceBridge evenly.

7.0 INSTALLING THE VOICEBRIDGE¨ Unpack the VB

unit.

§ The VoiceBridge package includes:VoiceBridge unit (s/w version 3.2 or higher)Power cord10 ft. Centrex cable (not used)RJ45 to DB-25 Adapter - 25ft. 8 wire RJ45 cable 057-1174-000 rev. A- 6-ft. AT&T Line cord

o Locate a cool, dry place to install the VoiceBridge. A grounded AC wall outlet of appropriate voltage is required.

o Remove the VoiceBridge from its packaging. Locate the power switch and verify that it is OFF. Attach the power cord to the appropriate connection on the back of the VoiceBridge, and plug the other end into the wall outlet.

o Locate the 6' telephone line cord that shipped with the unit. Insert it into the RJ-45 connector on the VoiceBridge, marked 'line A'. Connect the other end of the telephone cord to the jack for the 7434D


Installing the VoiceBridge


15

station set created for VoiceBridge. Connect the VB to the Overture 350 Distribution or ACP Board using cable 057-1174-000.

Notes:

Before installing the VoiceBridge, be sure to ground yourself to prevent damage to the device from static.

Never attach cables to the VoiceBridge while it is powered.

7.1 DIRECT INTEGRATIONS

The I/O distribution board has four serial channels: J44 (channel 1), J43

(channel 2), J46 (channel 3), and J50 (channel 4). Each of the first three serial channels are configurable as either direct RS232 integration links or system management channels. See Figure 2. Any of these three channels (J44, J43, J46) when used for system management terminals must connect to a null modem. Channel 4 (J50) is for a local, primary system management terminal only and does not require a null modem.

o Fasten the DB25 end of the RS232 cable 057-1174-000 to the appropriate connector (J43, J44, or J46) on the I/O distribution board of the 350. See Figure 2.

Figure 2. Octel 350 Main Distribution Board For Serial Channels Connections.

2 1 3 4

J43 J44 J45 J46 J47 J48 J49 J50

F E D C B A

SMDIor

SMT

SMDIor

SMT

SMDIor

SMT

Primary SMT/Local Service

Note:

A maximum of 2 VoiceBridges can be supported without the use of an ACP card. The Asynchronous Communications Processor (ACP) and associated hardware and software (MSA) will expand this capacity up to 16. Refer to Table 2 for allowable combinations of integration links and system management terminals without the ACP option.


Installing the VoiceBridge for direct integrations


16

Table 2. Combinations of Direct Integrations and SMT Terminals.

No. of Integration Links

1

2

No. of SystemManagement

Terminals

Up to 31

Up to 21

1 For more terminals, use ACP MTA.2 For more integration links, use ACP MSA.

Note:

One system-management-terminal channel shares CPU access with the Remote Diagnostic Analysis Center (RDAC) modem channel. For contention-free system management, one of the additional configurable serial channels must be used.

7.2 ACP INTEGRATIONS

The ACP supports up to 16 VoiceBridge links, as shown in

Figure 3.

o If an ACP is required for integration, the MSA (Multiple Switch Access) software option must be enabled. This is listed in Menu 13.7 as 'ACP Integration'. Verify that it is set to “Y”.

o Connect the RS-232 cable 057-1174-000 to the appropriate DB25 on the ACP distribution board. Use only ACP channels labeled "Link1” etc. See Figure 4. Connect the other end of the cable to the Voicebridge.

Voice Lines

Octel

ACP

PBX

VB 2

VB 1

VB 16

Octel

Figure 3. ACP MSA

7.3 POWERING THE VOICEBRIDGEThe VoiceBridge will go through a set of self diagnostics upon power-up.


Installing the VoiceBridge for ACP integrations


17

o Turn on the VoiceBridge unit. The power switch is located in the back. The unit should begin a self-test and boot sequence. If any of the self-tests fail, the screen will display 'No Module - Waiting for Remote Access'. If this occurs, refer to the VoiceBridge manual for resolution.

7.4 CONNECTING THE ANALOG CHANNELSEach Analog TIC supports 12 ports.

Each Analog TIC connects to the switch via a single 25 pair male amphenol cable. The first port uses the first pair of the cable ( pins 1,26), the second port uses the second pair (2,27), etc. Only the first 12 pairs are used.

o Physically connect the lines used for the voice path between the switch and the 350. The voice lines are connected to the switch using customer-supplied male-amphenol cables which terminate on the main backplane on the 350 frames. See Figures 5 and 6.

Ports6A-6L

Ports5A-5L

Ports4A-4L

Ports3A-3L

Ports2A-2L

Ports1A-1L

25-pair Male Amphenol Connectors

(Not Used)

Figure 5. Octel 350 Main Backplane (rearview)First Frame

Ports12A-12L

Ports11A-11L

Ports10A-10L

Ports9A-9L

Ports8A-8L

Ports7A-7L

25-pair Male Amphenol Connectors

(Not Used)

Figure 6. Octel 350 Main Backplane (rearview)Second Frame


Powering the VoiceBridge

Connecting the analog channels


18

7.5 CONFIGURING THE VOICEBRIDGE SOFTWAREBefore configuring the VoiceBridge, collect the following information:

§ Number of Voice Mail Ports. (Up to 24 per VoiceBridge)

§ Message Desk Number - this must match the message desk number assigned within the Octel system. The range of values is 001 to 063. This field indicates which Octel system is supported by the particular SMDI link.

§ Extension length on the PBX.

§ Extension numbers assigned to the Octel analog ports.

§ The LTN (logical terminal number 0001-0024) for each group of analog ports assigned to each VB.

§ Leave-Word-Calling enable and disable codes. Verify these with the PBX technician. These feature codes will be programmed in the VB if the VB is doing MWI. Menu 6.2 of the Octel System will be used only if in-band MWI ports are being used.

7.6 TESTING THE VOICEBRIDGE PRIOR TO PROGRAMMING¨ Test the VoiceBridge prior to programming.

§ Turn the unit on. After a few minutes, a SETUP menu appears.

§ Press the FUNC key on the unit to reach the Main Menu.

§ From the Main Menu, press 6 to reach the Diagnostic Menu.

§ At the Diagnostic Menu, press 1 for telephone emulation. Now the VoiceBridge will display the activity of the 7434D set.

Note:

If you have any difficulty, please refer to the VoiceBridge Installation Manual, which contains greater detail on testing and installing the VoiceBridge.

7.7 CONFIGURING THE VOICEBRIDGE FOR INTEGRATIONThe VoiceBridge Manual (Document

Number - VB201-0202) contains much more information on the functionality and programming of the VoiceBridge. Refer to it to set the date and time on the unit, to set security levels, and to learn more about the functionality of VoiceBridge.

¨ To begin entering configuration information, press the FUNC key to reach the Main Menu. Then follow these steps:

§ Press 4 to reach the Setup Menu.


Configuring the VoiceBridge


19

§ Press 1, for Params. This will allow you to edit the global parameters.

§ Fields will be presented, one at a time. Enter the appropriate information for each. The fields are as follows:

Number of Ports: Enter number of ports associated with this particular VoiceBridge.

Msg Desk Number: Enter message desk number.

Directory Numbers: Set to variable length.

Unidentified Reason: Disable

MWI Feature: Enabled (unless using in-band MWI ports)

MWI Interleave: 10 (used to force MWI command by the VB).

Msg Waiting On: Leave Word Calling activate code. ( used when VB is doing MWI functions)

Msg. Waiting Off: Leave Word Calling deactivate code. (used when VB is doing MWI functions)

Call sequence: Data/Call .

o From the Setup menu press 4 for Advanced options. Arrow down to Answer delay field. Answer Delay: 2500 ms

o Press the FUNC key. This will return you to the Setup Menu. Press the 2 key to edit the port configuration, as follows:

§ For each port, enter the LTN and the extension number. Use the UP and DOWN arrow keys to move from one port to another.

Note:

For a large number of Octel ports to enter, refer to the AUTOFILL command in the VoiceBridge documentation to make the process quicker.

o Press the FUNC key twice. this should bring you to the Main Menu. The system will ask the following questions. Answer as indicated.

§ SAVE EDITS? 1 - Yes

§ START SYSTEM? 1 - Yes

Within a few seconds, integration is active, utilizing the new configuration. You will be placed in the View Mode on VoiceBridge.



20

7.8 TESTING THE INSTALLATIONo Create two mailboxes associated

with two test extensions. Record a name and personal greeting for each mailbox.

o Assign a call coverage path to the test extensions that contain the Octel system's hunt group number as the first member.

o Using one test extension, call the other test extension. You should hear the personal greeting.

¨ With Octel Release 4 s/w, verify the Call Sender/Multiple Greetings feature works for both a busy and no answer condition.

o Leave a message. Verify that the message waiting indicator turns on.

o Review the message in the mailbox. Verify that the direct reply feature works by pressing 8 at the end of the message.

o Verify that return-to-operator works properly.

o Call the voice module from a test extension. You should immediately hear the recorded name and be asked to enter the password.

o Review the message. Verify that the message waiting indicator turns off.

8.0 CONSIDERATIONS8.1 Unsupervised transfers

require busy-call coverage. Calls that are blind transferred to stations that are busy and are not call covered will be lost.

8.2 The message return feature cannot be used to retrieve Octel messages. Use of the message return feature may cause ring-no-answer, caller disconnect, or VB lockup. We suggest creating a Class of Restriction (COR) to prevent access to the message waiting ports. For ease of use, create a speed call number to be used to retrieve messages. Assign this speed call number to a button on the feature phone.

8.3 To minimize the possibility of call collisions on ports used for outcalling, paging, fax, and networking applications, these ports should always be defined as the last members in a hunt group.

8.4 Leave Word Calling (LWC) provides message notification.

If the LWC feature is being used by the Octel system and other sources (that is message center and station users), then users without display terminals must contact their designated message retriever to determine the source of their message-waiting light.


Testing the installation

Important notes regarding this integration


21

CAUTION: Users with display terminals must not delete any Octel messages on their display. This allows the Octel system to turn off the message-waiting light when voice messages are reviewed.

8.5 Extensions on the Avaya Definity G2 can be a maximum of five digits.

8.6 The VB supports a maximum of 24 integrated ports per VB. An Octel 350 system with 3 VBs can support a maximum of 72 integrated voice ports. The number of ports per VB is based on traffic. Contact Sales Engineering for assistance in sizing the number of VBs required,

8.7 DCS is Avaya's PBX networking package. In a DCS environment, subscribers on the remote nodes may not have the same integration feature functionality as those on the hub node. In general, all integration features are supported. Call Coverage support on the remote nodes is dependent on the type of switch and software as follows:

- If they are on a G3 V2 or higher system, the Remote Call Coverage feature is standard and allows coverage to personal greeting for Busy and RNA conditions.

- If they are on a G2, they must call cover to a VDN that routes the call to the hub system. This allows coverage to personal greeting on Busy and RNA conditions. VDN software is an optional package on the G2. Without VDN S/W, they will be limited to station call forwarding All Calls only.

- If they are on a System 75 or G1 system, they are limited to station call forwarding All Calls only.

In all cases MWI is supported to the remote hubs over a DCS network.

Note:

G3i V1 7.0 with DCS is NOT SUPPORTED! The display field is shifted 2 characters on the G3i side. V1 also does not support call Coverage to a VDN.

8.8 If using VB to control MWI functions, Octel recommends that the MWI load is distributed over multiple VB’s. This can be done by using the “Intg. Link Number” field in the subscribers mailbox profile. This field is used by the VPM to direct MWI commands to the proper VB.

8.9 Octel highly recommends that VPM voice ports be distributed among different port cards/shelves on the PBX. This reduces the possibility that a single card/shelf failure will affect a large number of VPM ports. Depending on PBX architecture, performance could also



22

be an issue on some PBX's during high traffic if a large number of calls are being processed on the same card or shelf.

8.10 Octel recommends using ports from analog circuit packs SN228 or SN229B, as these circuit packs provide open-loop disconnect signals to Octel ports, thus allowing for faster port hang-up. Circuit packs SN229 do not provide the open-loop disconnect, causing Octel ports to have to rely on silence detection for disconnect.

©2001 AVAYA Inc. All rights reserved. All trademarks identified by the ®, SM and TM are registered trademarks, servicemarks or trademarks respectively. All other trademarks are properties of their respective owners. The above information is based on knowledge available at the time of publication and is subject to change without notice. Printed in U.S.A.

AVAYA Inc.1001 Murphy Ranch Road

Milpitas, CA 95035-7912

(408) 321-2000

http://www.avaya.com


cn4006.doc - Avayasupport.avaya.com/elmodocs2/Octel/config/Cn4026.doc · Web viewEnter the name and...

Documents

Transcript of cn4006.doc - Avayasupport.avaya.com/elmodocs2/Octel/config/Cn4026.doc · Web viewEnter the name and...