um4730 integration guide

Liability Disclaimer

NEC Unified Solutions, Inc. reserves the right to change the specifications, functions, or features at any time without notice.

NEC Infrontia Inc. has prepared this document for the exclusive use of its employees and customers. The information contained herein is the property of NEC Infrontia Inc. and shall not be reproduced without prior written approval from NEC Infrontia Inc.

NEC Unified Solutions, Inc. has prepared this document for use by its employees and customers. The information contained herein is the property of NEC Unified Solutions, Inc. and shall not be reproduced without prior written approval of NEC Unified Solutions, Inc. Dterm, NEAX and UNIVERGE are registered trademarks of NEC Corporation and Electra Elite is a registered trademark of NEC America, Inc. Windows is a registered trademark of Microsoft Corporation. AT&T is a registered trademark of AT&T Wireless Services, Inc. Pentium is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. AutoTalk is a trademark of Uniden America Corporation. ViewCall and ViewMail are registered trademarks of Active Voice, LLC.

© 2009 NEC Infrontia Inc.

MS-DOS, Microsoft, and Windows are trademarks of Microsoft Corporation.All other brand or product names are or may be trademarks or registered trademarks

of, and are used to identify products or services of, their respective owners.

NEC Infrontia, Inc. 6535 N. State Highway 161

Irving, TX 75039-2402

Technology Development

■ CONTENTS

Introducing UNIVERGE UM4730 Integrations 1Overview ......................................................................................... 2

Using this Document ..................................................................... 2Document Conventions .................................................................. 2

General Integration Steps .................................................................. 3General Integration Requirements ................................................... 3Integration Features...................................................................... 3

Programming the Phone System ......................................................... 4Selecting an Extension Numbering Plan............................................ 4Configuring Hunt Groups................................................................ 4Programming Subscriber Call Forwarding Settings ............................. 5

Configuring the Messaging System ...................................................... 6

Avaya with D42JCTU or D82JCTU Voice Boards Integration 7Overview ......................................................................................... 8

Integration Steps .......................................................................... 8Integration Requirements............................................................... 8

Connecting the Systems..................................................................... 9System Connections ...................................................................... 9

Programming the Phone System ....................................................... 11Programming the Avaya Definity G3 or System 75........................... 11Programming the Avaya System 85 Phone System .......................... 15

Configuring the Messaging System .................................................... 17

Centrex SMDI Integration 19Overview ....................................................................................... 20

Integration Steps ........................................................................ 20Integration Requirements............................................................. 20

Connecting the Systems................................................................... 21How a CO Centrex SMDI Integration Works .................................... 21System Connections .................................................................... 21

Configuring the Messaging System .................................................... 22Programming the Phone System ....................................................... 23

Select an Extension Numbering Plan .............................................. 23

Ericsson MD-110 Integration 25Overview ....................................................................................... 26


Connecting the Systems................................................................... 27System Connections .................................................................... 27

Programming the Phone System ....................................................... 28Configuring the Messaging System .................................................... 29

CONTENTS iii

Fujitsu 9600/SMDI Integration 31Overview ....................................................................................... 32




Hitachi HCX5000 Integration 37Overview ....................................................................................... 38

Integration Steps ........................................................................ 38Requirements ............................................................................. 38



ITT 3100 Integration 43Overview ....................................................................................... 44




Mitel with D42JCTU or D82JCTU Voice Boards Integration 49Overview ....................................................................................... 50


Connecting the Systems................................................................... 51Programming the Phone System ....................................................... 52

Mitel SX-200 ML.......................................................................... 52Mitel SX-2000 or 3300 ................................................................. 53


Mitel SX-50 with D42JCTU or D82JCTU Voice Boards Integration 57

Overview ....................................................................................... 58Integration Steps ........................................................................ 58Requirements ............................................................................. 58


Programming the Phone System ....................................................... 61Setting Mitel SX-50 Message Waiting System Options ...................... 61Configuring Call Forwarding on Subscriber Lines .............................. 61Programming Superset 420 Digital Stations .................................... 62


UNIVERGE UM4730 INTEGRATION GUIDEiv

NEC NEAX 2000 IPS with Serial MCI Integration 67Overview ........................................................................................ 68

Integration Steps......................................................................... 68Requirements.............................................................................. 68

Connecting the Systems ................................................................... 69Programming the Phone System ........................................................ 70Configuring the Messaging System..................................................... 73

NEC NEAX 2000 IPS without Serial MCI Integration 75Overview ........................................................................................ 76

Integration Steps......................................................................... 76Integration Requirements ............................................................. 76


NEC NEAX 2400 with IP Protims Integration 83Overview ........................................................................................ 84


Programming the Phone System ........................................................ 85Configuring the Messaging System..................................................... 86

NEC NEAX 2400 IPX with LAN MCI Integration 87Overview ........................................................................................ 88



NEC NEAX 2400 IPX/UNIVERGE SV7000 without MCI Integration 95

Overview ........................................................................................ 96Integration Steps......................................................................... 96Integration Requirements ............................................................. 96

Connecting the Systems ................................................................... 97Programming the Phone System ........................................................ 98Configuring the Messaging System................................................... 101

NEC NEAX 2400 with Serial MCI Integration 103Overview ...................................................................................... 104

Integration Steps....................................................................... 104Integration Requirements ........................................................... 104

Connecting the Systems ................................................................. 105System Connections................................................................... 105

Configuring the Trunk Boards .......................................................... 106Programming the Phone System ...................................................... 107Configuring the Messaging System................................................... 109

CONTENTS v

UNIVERGE SV7000 with LAN MCI Integration 111Overview ..................................................................................... 112

Integration Steps ...................................................................... 112Integration Requirements........................................................... 112Integration Features for SV7000 ................................................. 113

Programming the Phone System ..................................................... 114Configuring the Messaging System .................................................. 117

Selecting Optional Conversations................................................. 117Changing Integration Options ..................................................... 117Redirecting Extension Numbers ................................................... 117

NEC UNIVERGE SV8300 with IP Protims Integration 121Overview ..................................................................................... 122

Integration Steps ...................................................................... 122Integration Requirements........................................................... 122


NEC UNIVERGE SV8500 with Direct Digital Integration 127Overview ..................................................................................... 128


Integration Description .................................................................. 129Configuring the Messaging System .................................................. 130Programming the Phone System ..................................................... 131

NEC UNIVERGE SV8500 with IP Protims Integration 133Overview ..................................................................................... 134



Nortel Meridian-1 with D42JCTU or D82JCTU Voice Boards Integration 137

Overview ..................................................................................... 138Integration Steps ...................................................................... 138Integration Requirements........................................................... 138

Connecting the Systems................................................................. 139System Connections .................................................................. 139


Nortel Meridian Norstar with D42JCTU or D82JCTU Voice Boards Integration 147

Overview ..................................................................................... 148Integration Steps ...................................................................... 148Integration Requirements........................................................... 148

Connecting the Systems................................................................. 149System Connections .................................................................. 149

Programming the Phone System ..................................................... 151Selecting an Extension Numbering Plan ........................................ 151

Configuring the Messaging System .................................................. 152

UNIVERGE UM4730 INTEGRATION GUIDEvi

Siemens 9751 CBX with D42JCTU or D82JCTU Voice Boards Integration 153

Overview ...................................................................................... 154Integration Steps....................................................................... 154Integration Requirements ........................................................... 154

Connecting the Systems ................................................................. 155System Connections................................................................... 155

Programming the Phone System ...................................................... 157Rolm 8000 CBX systems ............................................................. 157Rolm 9000CBX, Rolm 9751CBX, or Siemens 9751 CBX Systems....... 162

Configuring the Messaging System................................................... 167

Toshiba CIX 100/200/670, CTX 100/670, and Strata DK Series Integration 169

Overview ...................................................................................... 170Integration Steps....................................................................... 170Integration Requirements ........................................................... 170

Connecting the Systems ................................................................. 171Requirements............................................................................ 171

Programming the Phone System ...................................................... 172Configuring the Messaging System................................................... 173

Appendix A Testing an Integration 175Testing Extensions ......................................................................... 176

Test Requirements ..................................................................... 176Test Steps ................................................................................ 176

Appendix B Learning the Phone System Tones 179Using GTDetect ............................................................................. 180

Appendix C Call Transfer Settings, Integration Options, and Troubleshooting 183Selecting a Call Transfer Type.......................................................... 184

How to Select Call Transfer Types ................................................ 184Configuring Release Transfers...................................................... 184Configuring Await Answer Transfers.............................................. 185Configuring Wait for Ringback Transfers........................................ 186

Optional Integration Settings........................................................... 187Setting Port Extensions................................................................... 188Testing the Serial Link .................................................................... 189Changing the Keypad Map............................................................... 190Troubleshooting............................................................................. 192

CONTENTS vii

UNIVERGE UM4730 INTEGRATION GUIDEviii

■ Introducing UNIVERGE UM4730 Integrations

1

In this integration...

Overview..........................................................................................................................................2Using this Document .....................................................................................................................2Document Conventions ..................................................................................................................2

General Integration Steps...................................................................................................................3General Integration Requirements ...................................................................................................3Integration Features ......................................................................................................................3

Programming the Phone System..........................................................................................................4Selecting an Extension Numbering Plan............................................................................................4

Determining the Number of Unique IDs for an ID Numbering Plan ...................................................4Configuring Hunt Groups................................................................................................................4Programming Subscriber Call Forwarding Settings .............................................................................5

Configuring the Messaging System.......................................................................................................6

INTRODUCING UNIVERGE UM4730 INTEGRATIONS

Overview Using this DocumentThe Integration Guide is arranged to provide specific integration information based upon the phone system installed.

Print the section for the specific phone system along with this chapter and all of the appendices. These pages should be used with the Installation Guide to complete the installation and configure the integrated messaging system.

This chapter also has a general overview for phone system integrations.

Document ConventionsThis document uses the following conventions:

● Key Names. Names of keys on the keyboard are shown in capital letters. For example, ESC, ALT, SHIFT and so on.

When two keys must be pressed simultaneously they are joined by a + sign; for example, ALT+TAB.

● Icon and Button Names. Names of icons and buttons on the application are shown in bold font. The capitalization matches the user interface. For example, OK, Ok, DELETE, or Delete are acceptable.

● Menu Selections. Menu selections are shown in a distinctive font. For example: File > Save and Actions > New Voice Message.

● User Input. Information you are required to type is shown in a distinctive font. For example, type msgorder.

Caution is required when typing a zero (0) or capital-O (O); a one (1) or a lowercase l.

● Placeholder Text. Variable text that is replaced by specific text is shown in italics between angle brackets. For example;

vm_ctl <service> <action>

where <action> = the command and

<service> = the name of the service.

● Hypertext Links. When viewing the Adobe® Acrobat® PDF document, links to other locations within the document and external Internet links appear in blue. Click a link to go to the referenced topic, page, or URL.

● Notes, Cautions, and Warnings. Text for notes, cautions, and warnings appear as shown below:

NOTE

On the command line prompt, always press ENTER after typing a command.

NOTE

A note provides additional information to supplement the main text. A note provides helpful information, but is not essential to understanding the current topic.

CAUTION!

A caution advises you that failure to avoid or to take a specific action might lead to unwanted or undesirable results.

WARNING!

A warning advises you that failure to avoid or to take a specific action might result in physical harm to the user, damage to the hardware or loss of data.

GRATIONS
UNIVERGE UM4730 INTEGRATION GUIDE INTRODUCING UNIVERGE UM4730 INTE2

General Integration StepsThe following information outlines the general steps required to successfully integrate the phone and the messaging systems, not all steps are applicable to all integrations:

1 Review the system and equipment requirements. See “General Integration Requirements” on page 3.

2 Configure the phone system.See “Programming the Phone System” on page 4.

3 Configure the messaging system.See “Configuring the Messaging System” on page 6.

4 Learn the phone system tones.See “Learning the Phone System Tones” on page 179.

5 Configure messaging system options.See “Call Transfer Settings, Integration Options, and Troubleshooting” on page 183.

6 Test the integration.See “Testing an Integration” on page 175.

General Integration RequirementsMake sure that you have the following to set up the phone and messaging system integration.

Phone System● Phone system installed.

● The phone system is programmed and ready for the integration.

Messaging System Server● Cable to connect phone system to the messaging system.

● Voice boards installed and configured.

● A system key that licensing the integration and the appropriate number and type of messaging system ports.

● The messaging system software installed and ready for the integration.

Integration FeaturesDepending upon the type of phone system and licensing purchased the integration provides the some or all of the following features.

● Call forward to personal greeting. An incoming call is routed to an unanswered or busy extension, the call is forwarded to the voice mail. The caller then hears a personal greeting and leaves a message.

● Caller ID. The messaging system receives caller ID information from the phone system (if available).

● Easy message access. A subscriber can retrieve messages without entering an ID. The messaging system identifies a subscriber based on the extension from which the call originated. To prevent unauthorized access to messages, a subscriber can set a security code.

● Identified subscriber messaging (ISM). If the phone system forwards calling party and called-party information, The messaging system automatically identifies a subscriber who leaves a message during a forwarded internal call, based on the extension from which the call originated.

● Message waiting indication (MWI). When a message is waiting for a subscriber, The messaging system notifies the phone system to activate the message waiting indicator on the subscriber’s extension (if it is equipped with one) or to activate a stutter dial tone.

3

Programming the Phone System

After connecting the systems, use the following procedures to set up the phone system for the integration. Refer to the phone system specific integration information in this document and the manufacturer documentation for more details.

Selecting an Extension Numbering PlanBefore setting up the messaging system extensions, decide on an extension numbering plan that meets the organization’s needs. Extensions are generally referred to as system IDs. The messaging system requires a unique system ID for each subscriber, guest, transaction box, voice detect box, or interview box.

System IDs are numbers that callers dial to access subscriber extensions and mailboxes and are used to link boxes for advanced call routing and audio text.

Before assigning system IDs:

● Estimate what kind and how many system IDs are needed.

● Design a simple, easy to use, system ID numbering plan and use it consistently. All system IDs should contain the same number of digits.

● Assign system IDs using numbers rather than letters. When system IDs are assigned by letters, duplication can occur, both SANDY and RANDY, have the same ID number, 72639.

Determining the Number of Unique IDs for an ID Numbering PlanThe number of system IDs required in a system determines the number of digits used in the ID. The following table shows how many unique IDs are available for a particular numbering plan. When creating system IDs to allow for a range of unused system IDs; this enables future system expansion, for new subscribers, transaction boxes, interview boxes, and subscriber guests.

Configuring Hunt GroupsUse the following procedure to set up a hunt group for the messaging system extensions.

To set up the messaging system extensions to use a hunt group

1 On the phone system find the extensions assigned to the messaging system.

2 Set the phone system to hunt to the next extension when the first messaging system extension is busy or unanswered.

3 Set the last port to hunt back to the first extension in the group.

For each messaging system port, go to the Capabilities section and set the Abilities field to CFB (call forward busy) and CFNA (call forward no answer). For example, for extension 200, set the field to CFB/NA 200 to 201.

NOTE

Duplicate system IDs are not permitted in the messaging system.

Number of digits in each ID

Number of unique IDs (assumes system operator box ID is 0)

1 9

2 90

3 900

4 9,000

5 90,000

6 900,000

7 9,000,000

8 90,000,000

9 900,000,000

10 9,000,000,000

GRATIONS

When the hunt group is set up, all of the subscriber extensions are forwarded to the first messaging system extension. If the first extension is busy, the system hunts for the next available extension. The system hunts in sequence up to the last extension, then starts over until a messaging system extension becomes available.

Programming Subscriber Call Forwarding SettingsUse the following procedure to set up forwarding calls to the messaging system for each subscriber,

To program call forwarding for individual subscriber stations

❚ In the Capabilities section set the Abilities field to CFB (call forward busy) and CFNA (call forward no answer).

Next step…

◆ Configure the messaging system. See “Configuring the Messaging System” on page 6.

5

Configuring the Messaging System

After setting up the phone system, you will set up the messaging system.

The message system is configured on the Switch Information page of the Administration Console.

Refer to the Installation Guide and System Administrator Help for detailed information about additional features.

GRATIONS

■ Avaya with D42JCTU or D82JCTU Voice Boards Integration

AVAYA WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION 7


Overview..........................................................................................................................................8Integration Steps ..........................................................................................................................8Integration Requirements...............................................................................................................8

Connecting the Systems .....................................................................................................................9System Connections ......................................................................................................................9

Programming the Phone System........................................................................................................11Programming the Avaya Definity G3 or System 75 ...........................................................................11Programming the Avaya System 85 Phone System...........................................................................15

Configuring the Messaging System.....................................................................................................17

Overview Use this section of the Integration Guide with the Installation Guide to configure the messaging and phone systems for the integration. Refer to the phone system manufacturer documentation for additional details.

Integration StepsFollow these steps to set up this integration.

1 Review the system and equipment requirements.See “Integration Requirements” on page 8.

2 Connect the systems.See “Connecting the Systems” on page 9.

3 Configure the phone system for the integration.See “Programming the Phone System” on page 11

4 Configure the messaging system for the integration.See “Configuring the Messaging System” on page 17.

5 Test the phone extensions.See “Testing an Integration” on page 175


7 Select a transfer type.See “Call Transfer Settings, Integration Options, and Troubleshooting” on page 183.

Integration RequirementsMake sure that you have the following to set up the Avaya withD42JCTU or D82JCTU integration.

Phone System● Avaya Definity G3, System 75, or System 85 G2 phone system.

● For each messaging system port, one Digital Network Interface Circuit (DNIC) port that emulates a 7434D or 8434D digital phone, installed and set up as a messaging system port.

● The phone system is configured and ready for the integration.

● A type 66 interconnect block for each PBX station interface cable.

Messaging System Server● A system key that licenses the integration and the appropriate number and type of

messaging system ports.

● D42JCTU or D82JCTU voice boards configured and installed.

The Avaya with D42JCTU or D82JCTU integration uses digital lines to connect the phone system and the messaging system server. The D82JCTU voice board emulates up to eight digital phones and the D42JCTU voice board emulates up to four digital phones.

● An 18-pair PBX station interface cable for each voice board.


IMPORTANT

If you are setting up an integration from an Avaya System 85 phone, you must configure the phone system before connecting the system.

UNIVERGE UM4730 INTEGRATION GUIDE AVAYA WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION8

Connecting the Systems

After installing all of the required hardware on the messaging system server, use the following procedure to connect the messaging and phone systems.

Refer to the Installation Guide, to install any required messaging system hardware such as voice boards.

System Connections

To connect the phone system and the messaging system

1 Connect the phone system digital lines 1-8, or 1-4 on a 4-port system, to a type 66 interconnect block.

Refer to the “Two-wire pinouts” and “Four-wire pinouts” tables for cabling requirements.

IMPORTANT

If you are setting up an integration from an Avaya System 85 phone, you must configure the phone system before connecting the system.

Two-wire Pinouts

Phone Line Port Number

Type 66 Block Pair

Pin Number

Pair Color Lead Designation

1 2 272

white-orange orange-white

Tip 1 Ring 1

2 4 29 4

white-brown brown-white

Tip 2 Ring 2

3 6 31 6

red-blue blue-red

Tip 3 Ring 3

4 8 33 8

red-green green-red

Tip 4 Ring 4

5 10 35 10

red-slate slate-red

Tip 5 Ring 5

6 12 37 12

black-orange orange-black

Tip 6 Ring 6

7 14 39 14

black-brown brown-black

Tip 7 Ring 7

8 16 41 16

yellow-blue blue-yellow

Tip 8 Ring 8


2 Connect the messaging system server to the interconnect block:

■ If the PBX cable cannot be directly connected to the interconnect block, use a telco cable:

◆ Connect one end of the telco cable to the interconnect block.

◆ Connect the other end of the telco cable to a PBX station interface cable.

■ Otherwise, connect the PBX cable directly to the interconnect block and the other end to a voice board installed in the messaging system server.

Repeat step 2 for each additional voice board installed.

Next Step...

◆ Configure the Phone System.See “Programming the Phone System” on page 11

Four-wire Pinouts

Phone Line Number

Pin Number


1 26 1

27 2

white-blue blue-white white-orange orange-white

TXR1 TXT1 PXR1 PXT1

2 28 3

29 4

white-green green-white white-brown brown-white

TXR2 TXT2 PXR2 PXT2

3 30 5

31 6

white-slate slate-white red-blue blue-red

TXR3 TXT3 PXR3 PXT3

4 32 7

33 8

red-orange orange-red red-green green-red

TXR4 TXT4 PXR4 PXT4

5 34 9

35 10

red-brown brown-red red-slate slate-red

TXR5 TXT5 PXR5 PXT5

6 36 11 37 12

black-blue blue-black black-orange orange-black

TXR6 TXT6 PXR6 PXT6

7 38 13 39 14

black-green green-black black-brown brown-black

TXR7 TXT7 PXR7 PXT7

8 40 15 41 16

black-slate slate-black yellow-blue blue-yellow

TXR8 TXT8 PXR8 PXT8



Use the procedures in this section to program the phone systems for integration:

● Avaya Definity G3 or System 75. See “Programming the Avaya Definity G3 or System 75” on page 11.

● Avaya System 85. See “Programming the Avaya System 85 Phone System” on page 15.

Programming the Avaya Definity G3 or System 75 Use the following procedure to program the Avaya Definity G3 or System 75 phone systems.

1 Set up the voice messaging extensions.The Definity G3 voice board emulates the Avaya 8434D digital phone and the System 75 the voice board emulates the Avaya 7434D phone. See “To set up the messaging system extensions as digital phones” on page 11.

2 Set up the hunt group.Set up the hunt group to include all the messaging ports. See “To set up a hunt group” on page 12.

3 Set up message waiting indication.Dedicate one of the messaging system ports to control the phone system message waiting indication. See “To set up message waiting indication for a port” on page 13.

4 Set up a coverage path.The phone system uses a coverage path to forward unanswered or busy calls. See “To set up a coverage path” on page 13.

5 Set up subscribers.Use the following procedure to assign the messaging system coverage path to all subscribers. See “To set up subscribers” on page 14.

To set up the messaging system extensions as digital phones

1 On the phone system programming terminal, type:

add station <nnn>

where <nnn> is a three-or-four digit messaging system extension, then press ENTER.

2 In the Name field on page 1 of the Station screen, type a name that includes the messaging system extension number (maximum of 16 characters). For example, VoiceMail 501.

3 Set the emulation Type field as follows:

If the Type field is set to 8434D, the messaging system will not integrate with the phone system.

On the programming screen type the following:

change system-parameter features

4 On page 5, set 7405ND Numeric Terminal Display to Y.

Emulation type Type field setting

7434D 7434D

8434D 7405ND

NOTE

7405ND is not a phone type, it enables numeric display. To use 7405ND, enable it in the System-parameter Features screen when programming the phone system using the following steps.

NOTE

To use G3 phones with 7405ND the switch must be V5 or higher.


5 In the Feature Options section, type the field settings shown below. Use the phone system documentation to configure the other fields on the first page.

6 Go to page 2 of the Station screen.

7 In the Button Assignments section, fields 1 and 2, type the following:

call-appr

8 Go to page 4.

9 In the Display Button Assignments section, confirm that the value for field 1 is Normal.

10 Press ENTER to save the setup.

11 Repeat steps 1 through 10 for each port extension.

To set up a hunt group


add hunt next

Then press ENTER.

2 On page 1 of the Hunt Group screen, set up a hunt group number, extension, and name.

For example, use Group Number 1, Group Extension 500, and Group Name Voice Mail.

3 In Group Type, type ucd (Uniform Call Distributor) or circ (circular).

4 Set Queue? to N. Refer to the phone system documentation for setting up the remaining fields.

NOTE

The ACD (automatic call distributor) field should be set to No. The messaging system does not support ACD ports.

f Feature Options LWC Activation = Y

a Extension b Type c Name

8434D Digital Phone Emulation Example:


5 Go to page 3. In the Group Member Assignments section, add all of the messaging system extensions that answer calls to hunt groups.


To set up message waiting indication for a port


change station <extension>

Where <extension> is the extension that you want to control message waiting indication, then press ENTER. For example, extension 501 is used in the example screen.

2 On page 1 of the Station screen, set up the Port field according to the phone system requirements.

3 In the Feature Options section, type the field settings as shown in the image below. Refer to the phone system documentation for setting up the remaining fields on the page.

4 On page 2, in the Button Assignments section, in fields 1 and 2 type:

call-Apr

5 On page 3, in the Feature Button Assignments section, type the following field settings:

6 On page 4, in the Display Button Assignments section, confirm that the value for field 1 is Normal.


To set up a coverage path


add coverage path <pathNumber>

where <pathNumber> is a path number such as 1 (one), then press ENTER.

2 In the Coverage Criteria section of the Coverage Path screen, set the field settings based on the transfer options selected in “Selecting a Call Transfer Type” on page 184.

The following table describes how the system uses the setting when it is set to Yes.

NOTE

Do not add ports that are set up on the messaging system with the Dial, Lamp, or Msg port status codes.

Field Setting

33 lwc-store

34 lwc-cancel

Field Description

Active If any call appearance is in use, the call forwards.

This example shows completed fields for the 8434D digital phone emulation.


Refer to the phone system documentation for more details on setting up the coverage path fields.

3 Press ENTER to exit this screen.

To set up subscribers


change station <extension>

where <extension> is the subscriber’s extension number, then press ENTER.

2 In the Name field:

3 In the Coverage path field, type the coverage path number created in step 1 of “To set up a coverage path” on page 13.

4 Press ENTER.

5 Repeat steps 1 through 4 for each subscriber extension.

Next Step...

◆ Configure the Messaging System.See “Configuring the Messaging System” on page 17.

Busy If all call appearances are in use, the call forwards

Don’t Answer If the call is unanswered, the call forwards after the specified number of rings.

All All calls immediately forward.

Emulation Type Action…

7434D emulation confirm that the name includes the subscriber’s extension number (maximum 15 characters).

8434D (7405ND) emulation

no restrictions on the name field and no other numbers, as they will be added to the subscriber’s extension and the integration will fail.

NOTE

The Name field must be set up correctly or the integration might fail. Refer to the phone system documentation for additional details about setting up these fields.

Field Description

Extension is required for 7434D emulations only.


Programming the Avaya System 85 Phone System Use the following steps to set up the Avaya System 85 for the integration. Refer to the phone system documentation for additional details.

1 Set up the messaging system ports.The voice board emulates the Avaya 7434D phone. See “To set up messaging system ports” on page 15.

2 Set up the message waiting indication.Refer to the manufacturer documentation for more detailed instructions setting up one of the messaging system extensions to control the phone system message waiting indication.

3 Set up a coverage path.Set up a basic coverage path to the first messaging system extension number and assign the messaging system coverage path to each subscriber. See “To set up a coverage path” on page 15.

4 Set up subscribers for the integration.Set up subscriber extensions for the integration. See “To set up subscriber extensions” on page 16.

To set up messaging system ports

1 Set up the system to detect hardware.

The phone system must detect the boards and other special phone system hardware that you have added or enabled.

2 Assign the extension numbers the phone system uses to access the messaging system.

Program extensions as digital 7434D phones. To set up the messaging system extensions as 7434D digital phones, see “To set up subscriber extensions” on page 16.

3 Set up a hunt group to include all of the messaging system ports.

If the phone system supports hunt group access codes, assign a hunt group access code for the messaging system. This code is the number that subscribers dial internally to connect to the messaging system.

Some phone systems do not have hunt groups. You can simulate a hunt group by forwarding each messaging system extension to the next extension when the extension is busy.

To set up a coverage path

1 Go to Proc 011 and set up a coverage path to the extension number of the first messaging system port.

2 In the Word 1 section, complete fields 1 through 9. An example of field settings is shown in the following table.

NOTE

Before connecting the messaging system server to the phone system, use the following steps to set up the phone system for the integration.

Field Setting Call coverage paths

1 xxxx Coverage path group number

2 3 Cover on active - all types of calls

3 3 Cover on busy - all types of calls

4 0 Do not cover on all calls

5 3 Cover on did not answer - all types of calls

6 3 Cover on third ring

7 8 Coverage point is an extension

8 1 Coverage point number (1-3)


There are no restrictions on coverage paths. You might create several coverage paths to address specific situations. Refer to the phone system documentation for the field setting options and descriptions.

To set up subscriber extensions

1 Go to the Word 1 section of Proc 012.

2 In the Name field, type a subscriber’s name and extension number.

The full extension number must appear in the first 16 characters of the subscriber name.

3 Go to the Word 2 section of Proc 000.

4 In field 6, type the coverage path group number.

5 Go to Proc 063 and set up the automatic message waiting lamp.

6 Repeat steps 1 throughstep 5 for each subscriber.

Next Step...


9 xxxx 7405 D extension

Field Setting Call coverage paths



After setting up the phone system, use the following procedures to set up the messaging system. For more information on messaging system features, see Administrator Help.

To configure the messaging system

1 Sign in to the Administration Console.

2 In the Navigation pane, click System > Switch > Switch Information.

3 Select the phone system manufacturer and model from the Switch list.

The switch parameters are displayed in the Integration options field.

4 In the Integration Options field, confirm that the integration string includes the following data:

INT=DIGITAL

5 Click Save.

6 In the Navigation pane, click System > Switch > Switch Extensions.

Assign an Extension for each port displayed in the table.

7 Click Save.

8 Stop and restart the messaging system to implement the changes as follows:

a In the Navigation pane, click Server Control.

b Click Stop to stop the messaging system.

Wait a few seconds for the messaging system to stop. The Start button is activated when the messaging system has stopped.

c Click Start to restart the messaging system.

Next Steps…The following procedures are located in the Integration Guide appendices.

◆ Test the extensions.See “Testing an Integration” on page 175.

◆ Learn the phone system tonesSee “Learning the Phone System Tones” on page 179.

◆ Select a call transfer typeSee “Call Transfer Settings, Integration Options, and Troubleshooting” on page 183.

◆ Change optional integration settingsSee “Optional Integration Settings” on page 187.

◆ Set port extensionsSee “Setting Port Extensions” on page 188.

◆ Test the serial linkSee “Testing the Serial Link” on page 189.

◆ Changing the keypad mapSee “Changing the Keypad Map” on page 190.

◆ TroubleshootingSee “Troubleshooting” on page 192.

NOTE

Integration options cannot be changed while the messaging system is stopped.


■ Centrex SMDI Integration

CENTREX SMDI INTEGRATION 19


Overview........................................................................................................................................20Integration Steps ........................................................................................................................20Integration Requirements.............................................................................................................20

Connecting the Systems ...................................................................................................................21How a CO Centrex SMDI Integration Works.....................................................................................21System Connections ....................................................................................................................21

Configuring the Messaging System.....................................................................................................22Programming the Phone System........................................................................................................23

Select an Extension Numbering Plan ..............................................................................................23

Overview Use this section of the Integration Guide with the Installation Guide to integrate the Centrex with SMDI (Simplified Messaging Desk Interface) phone system with the messaging system. The Central Office (CO) Centrex with SMDI integration requires the optional SMDI package, see the Intergration Requirements below. An RS-232 data link with a serial modem is used to connect the messaging system to the CO system. SMDI is a protocol that allows the messaging system to recognize the incoming call information based on the packet sent by PBX. The packet contains information about the call origin, call type, etc.

Integration StepsFollow these steps to set up the integration.

1 Review the system and equipment requirements. See “Integration Requirements” on page 20.


3 Configure the messaging system for the integration. See “Configuring the Messaging System” on page 22.

4 Set up the phone system for the integration. See “Programming the Phone System” on page 23.

5 Test the phone extensions that are set up for the integration.See “Testing an Integration” on page 175



Integration RequirementsThe steps to set up the Centrex SMDI integration require the following:

Phone System● A Centrex phone system or a CO Centrex system. If using a CO Centrex system:

■ The SMDI package is available on some Centrex systems served by 1AESS, 5ESS, DMS-100, 5RSM, and NEAX 5200 central offices.

■ An external modem for connecting the CO and the messaging system.

■ An SMDI four-wire private data link.

■ An SMDI call ID for each Centrex extension.

● One serial port available for the serial link.

● One RS-232 serial cable for connecting the phone system serial link to the messaging system.

● One 2500 station port set up for each messaging system port.

● The appropriate phone lines for connecting the phone system messaging system ports to the messaging system voice boards.

● A type 66 interconnect block.

● The phone system ready for the integration as described in the phone system manufacturer documentation.

Messaging System Server● The messaging system software installed and ready for the integration.

● A serial port is available on the messaging system server.

● A system key that licenses the integration and the appropriate number and type of messaging system ports is connected to the messaging system.

UNIVERGE UM4730 INTEGRATION GUIDE CENTREX SMDI INTEGRATION20


After installing all of the required hardware on the messaging system server, use the following procedures to connect the phone and messaging systems.

How a CO Centrex SMDI Integration WorksThe CO Centrex SMDI integration requires the optional SMDI package. A serial RS-232 data link connects the messaging system to the CO system emulates SMDI.

Refer the Installation Guide for information about installing the required messaging system hardware (such as voice boards).

System Connections

To connect the phone and the messaging systems

1 Connect the phone system station lines to the phone system or CO.

2 Connect the other end of the phone system station lines to the voice boards in the messaging system server.

3 Connect the serial cable to COM1 on the messaging system server.

Next Step...

◆ Configure the Messaging System. See “Configuring the Messaging System” on page 22.

Type of phone system

Centrex phone system

Connect the other end of the serial cable to the phone system.

CO Centrex system Connect the serial cable from the messaging system to the external serial modem then connect the modem to the CO.



After setting up the phone system, use the following procedures to configure the messaging system. For more information about the messaging system features, refer to the System Administrator Help.

To configure the messaging systemSelecting a phone system is generally done during the installation of the messaging system. Should you need to change the phone system, use this procedure to modify the phone system and switch information.


2 Stop the messaging system as follows:


b Click Stop to stop the messaging system software.



4 Select the phone system manufacturer name and model from the Switch list.

The switch parameters appear in the Integration options field.

5 Click Save.



7 Click Save.

8 Rrestart the messaging system to save the changes as follows:


b Click Start to restart the messaging system.

Next Step...

◆ Program the Phone System. See “Programming the Phone System” on page 23.

NOTE

If data is removed or changed in the Integration Options field, the messaging system software must be restarted to activate the changes.



Use the following procedures to program the phone system for the integration. Refer to the phone manufacturer documentation for more details.

Select an Extension Numbering PlanBefore setting up the messaging system extensions, decide on an extension numbering plan that meets the needs of the organization. For detailed information see “Selecting an Extension Numbering Plan” on page 4.

To set up the phone system for the integration

❚ Confirm that the SMDI package is installed on the phone system.


1 Confirm the Centrex SMDI package has been ordered from the Central Office and make sure the phone company has set the information below.

2 On the phone system, find the phone system station lines assigned to the messaging system.

3 Set up the lines as part of a multi-line hunt group and for a switch hook flash transfer to another number.

4 Set up the lines with the following call forward options:

■ Call forward - unrestricted source

■ Call forward - ring-no-answer

■ Call forward - busy

See “Selecting a Call Transfer Type” on page 184.











■ Ericsson MD-110 Integration

ERICSSON MD-110 INTEGRATION 25



System Connections.........................................................................................................................27Connecting the Systems...............................................................................................................27

Programming the Phone System........................................................................................................28Configuring the Messaging System.....................................................................................................29

Overview Use this section of the Integration Guide with the Installation Guide to integrate the Ericsson MD-110 with the messaging system. The integration uses an RS-232 serial cable to send call information from the phone system to the messaging system.




3 Configure the phone system for the integration.See “Programming the Phone System” on page 28.


5 Test the phone extensions that are set up for the integration.See “Testing an Integration” on page 175.



Integration RequirementsThe Ericsson MD-110 integration requires the following:

Phone System● Software level BC4, 5, or 6.

● One Data I/O port available for the integration link.

● Ericsson ICU ROF 103 4421/2 connected to the messaging system serial port (part number might vary from country to country).

● Ericsson analog ELU boards (one analog port for each messaging system port).

● Phone lines for connecting the station ports to the messaging system voice boards.

● One station port (analog) set up for each messaging system port.

Messaging System Server● The messaging system is installed and ready for the integration.

● An available serial port.

● A system key that licenses the integration and the appropriate number and type of messaging system ports.

UNIVERGE UM4730 INTEGRATION GUIDE ERICSSON MD-110 INTEGRATION26


After installing all of the required hardware in the messaging system server, use the following procedure to connect the phone and messaging systems.

To install required messaging system hardware (such as voice boards), see the Installation Guide.

System Connections

To connect the phone and the messaging systems

1 Connect one end of an RS-232 serial cable to the phone system Data I/O port.

2 Connect the other end of the RS-232 serial cable to the messaging system computer COM1 serial port.

3 Connect the analog line from the type 66 interconnect block to the appropriate connectors on each analog voice board in the messaging system computer.

Repeat this step for each additional analog line.

Next Step ...

◆ Configure the Phone System. See “Programming the Phone System” on page 28.



After connecting the systems, use the following procedures to configure the Ericsson MD-110 phone system. Programming the phone system or extension options using difference procedures than those supplied in this document might adversely affect the integration performance.

To set up the phone system

1 Use the EXTEI command to program the ELU extensions to connect to the messaging system ports. Program each extension with the following:

■ No Call Waiting

■ No Diversion

■ No Conferencing

■ No Intrusion

2 Use the VMPOI command to create a logical affiliation between the extensions and their port numbers in the messaging system.

Each messaging system port must match the Ericsson port it is connected to. For example, the messaging system port 01, must match the Ericsson port 01, extension 3500; the messaging system port 02 must match Ericsson port 02, extension 3501, and so on for all the messaging system ports.

3 Use the GH command to create a hunt group for the extensions going to the messaging system.

4 Use the VMPOI command to associate the hunt group with the messaging system.

5 Use the CD (Call Diversion) command if you are using the Release call transfer type, or want to provide for internal call diversion.

This provides extensions with call diversion to the pilot number of the messaging system hunt group. Set up call diversion for both the busy and ring-no-answer conditions.

If you are using the Await Answer call transfer type, set the call diversion timer on the phone system to at least two rings higher than the number of rings set for the messaging system. For example, set the messaging system to three rings, and the phone system to five rings.

6 Use the KS command to provide message waiting indication on DTS phones.

Next Step ...


NOTE

ELU1 does not support message waiting indication for analog phones. ELU24 provides stutter dial tone for message waiting indication.



After setting up the phone system, use the following procedures to set up the messaging system. For more information on messaging system features, see System Administrator Help.




3 Select Ericsson MD 110 from the Switch list.

The switch parameters appear in the Integration options field.

4 Click Save.



6 Click Save.

7 Stop and restart the messaging system to save the changes as follows:














NOTE

If data is removed or changed in the Integration Options field, the messaging system software must be restarted to activate the changes.


■ Fujitsu 9600/SMDI Integration

FUJITSU 9600/SMDI INTEGRATION 31


Overview....................................................................................................................................... 60Integration Steps ........................................................................................................................32Integration Requirements.............................................................................................................32

Connecting the Systems ...................................................................................................................33System Connections ....................................................................................................................33


Overview Use this section of the Integration Guide with the Installation Guide to integrate the Fujitsu 9600/SMDI with the messaging system. A SMDI (Simplified Messaging Desk Interface) port is required for the Fujitsu 9600 integration. The integration uses an RS-232 serial cable to send call information from the phone system to the messaging system.


1 Review the system and equipment requirements. See “Integration Requirements” on page 32.


3 Program the phone system for the integration.See “Programming the Phone System” on page 34.





Integration RequirementsThe Fujitsu 9600/SMDI integration requires the following:

Phone System● One SMDI port available for the integration link.



● One RS-232 serial cable (included with the integration package) for connecting the phone system SMDI port to the messaging system serial port.

Messaging System Server● Messaging system is installed and ready for the integration.



UNIVERGE UM4730 INTEGRATION GUIDE FUJITSU 9600/SMDI INTEGRATION32


After installing all of the required hardware in the messaging system server, use the following procedure to connect the systems.

To install required messaging system hardware, see Installation overview in Chapter 1 of the Installation Guide.

System Connections

To connect the phone system and messaging system

1 Connect one end of an RS-232 serial cable to the SMDI port on the phone system.




Next Step ...

◆ Program the Phone System.See “Programming the Phone System” on page 34.



After connecting the systems, use the following procedures to set up the Fujitsu 9600 system. Programming the phone system or extension options using difference procedures than those supplied in this document might adversely affect integration performance.


1 Select specific messaging system ports to be used for the integration, and identify any automated attendant ports, if applicable.

2 Enable the VMS Integration option on the phone system for the stations assigned to the messaging system ports only.

3 Assign a DCC port for integration with the messaging system.

4 In the Assign single line phone section, set Type to 1 for the Fujitsu 9600 sets used as messaging system ports.

5 In the Change service parameter, set Type to 2.

6 Set ID:01 to 01 for the Fujitsu 9600 phone sets used as messaging system ports.

The Change service parameter Type and ID:01 settings disable the immediate ring feature.

Next Step…


CAUTION

Always use an antistatic wrist strap or grounding device when you handle boards or other components. Static electricity can damage the components in phone system equipment.

NOTE

Do not enable the VMS integration for stations connected to automated attendant ports.



After setting up the phone system, use the following procedures to set up the messaging system. For more information on messaging system features, see the System Administrator Help.



2 In the Navigation pane click System > Switch > Switch Information.



4 Click Save.



6 Click Save.















NOTE

When data in the Integration Options field is changed you must restart the messaging system software to activate the changes.


■ Hitachi HCX5000 Integration

HITACHI HCX5000 INTEGRATION 37


Overview........................................................................................................................................38Integration Steps ........................................................................................................................38Requirements .............................................................................................................................38



Overview Use this section of the Integration Guide with the Installation Guide to integrate the Hitachi HCX5000 phone system with the messaging system.


1 Review the system and equipment requirements.See “Requirements” on page 38.


3 Configure the phone system for the integration.See “Programming the Phone System” on page 40.





RequirementsThe Hitachi HCX5000 integration require the following:

Phone System● Software level 5.1 or higher.

● One Data I/O port available for the integration link.



● One RS-232 serial cable for connecting the phone system Data

● I/O port to the messaging system serial port.

Messaging System Server● Messaging system installed and ready for the integration.



UNIVERGE UM4730 INTEGRATION GUIDE HITACHI HCX5000 INTEGRATION38


After installing all of the required hardware in the messaging system computer use the following procedure to connect the systems.

System Connections


1 Connect one end of an RS-232 serial cable to the Data I/O port on the phone system.




Next Step ...


CAUTION




After connecting the systems, use the following procedures to set up the Hitachi HCX5000 system. Programming the phone system or extension options using instructions than those supplied in the following procedures might adversely affect the integration performance.


1 Select specific messaging system ports to be used for the integration, and identify any automated attendant ports, if applicable.

2 Enable the VMS Integration option on the Hitachi system for the stations assigned to the messaging system ports only.

3 Program each Hitachi HCX5000 station for call coverage (call forwarding) to the messaging system, based on the selections made about automated attendant features and message delivery.

4 Program the Hitachi phone system to forward the correct prefix digits to the messaging system for forwarded calls and Easy Message Access calls:

■ For calls with call coverage, program a single-digit, 0 (zero), as a prefix digit.

■ For Easy Message Access calls, program a single-digit, 1 (one), as a prefix digit.

Next Step ...


NOTE

Do not enable the VMS integration for stations connected to automated attendant ports.

NOTE

Do not use the Immediate Coverage option. Immediate Coverage prevents the messaging system from forwarding back to itself when it attempts to transfer a call or deliver a message.

NOTE

Do not create any system IDs on the messaging system that match either of these prefix/extension number codes. You can still use 0 (zero) for the operator.



After setting up the phone system, use the following procedures to set up the messaging system. For more information about the messaging system features, see System Administrator Help.




3 From the Switch list, select Hitachi HCX5000.


4 Click Save.



6 Click Save.















NOTE



■ ITT 3100 Integration

ITT 3100 INTEGRATION 43





Overview Use this section of the Integration Guide with the Installation Guide to integrate the ITT 3100 phone system with the messaging system. An SMDI (simplified messaging desk interface) port is required on the ITT 3100 for the integration.




3 Program the phone system.See “Programming the Phone System” on page 46.


5 Test the phone extensions.See “Testing an Integration” on page 175.


7 Select a call transfer type.See “Call Transfer Settings, Integration Options, and Troubleshooting” on page 183.

Integration RequirementsThe steps to set up the ITT 3100 integration require the following:

Phone System● For the ITT 3100 phone system, a VMAD option kit that includes:

■ RS Quad Idea 2A RS-422 card (Part # 676-120-000-011). This card connects directly into the data card and gives the phone system data capabilities.

■ RS Quad Idea 2A RS-232 card (Part # 676-120-000-001). This card connects to the voice mail system.

■ Data register card (Part # 676-089-000-002). This might have been previously installed on the ITT 3100.

■ One 4-circuit Modem Control Card (MCC) for each voice board in the voice mail system (Part # 188405-106-PAK). These Modem Control Cards are connected to the voice mail system ports.

● If using message delivery to external phones, you need one single-line port on the ITT 3100.

● Voice mail ports can dial internal extensions on the ITT 3100, but are not able to access a trunk for an external call.

● One SMDI port available for the integration link.







UNIVERGE UM4730 INTEGRATION GUIDE ITT 3100 INTEGRATION44


After installing all of the required hardware in the messaging system server, use the following procedure to connect the systems. To install required messaging system hardware, see the Installation Guide.

System Connections


1 Install the cards from the VMAD option kit on the ITT 3100 system. Install one modem control card (MCC) for each 4-port voice board.

2 Connect one end of an RS-232 serial cable to the RS-232 port on the phone system. If the number of pins does not match, use an adapter provided in the integration kit. If you need to wire the connection, use the following table as reference.

3 Connect the other end of the RS-232 serial cable to the messaging system server COM1 serial port.


Repeat step 4 for each additional analog line.

Next Step ...


CAUTION


Messaging system Idea2A card

Function Pin Function Pin

TD 2 RD 3

RD 3 TD 2

DSR 4 DTR 20

DTR 6 DSR 6

NOTE

Do not use the normal signal ground wire when connecting to the RS-232 card. Use the digital ground to prevent damage to the power supply. Refer to the phone system documentation for digital ground connection instructions.



After connecting the systems, use the following procedures to set up the ITT 3100 system. Programming the phone system or extension options using difference procedures than those supplied in this document might adversely affect the integration performance.


1 Program each ITT 3100 station to call forward on busy and ring-no-answer to the pilot number for the voice mail system ports.

2 Program the first port of the IDEA RS232 card as follows:

LX TYPE = VMDATA QUAD

PROFILE = VMDATA

3 Program the Vmdata Profile as follows:

PROFILE

VMDATA = NPEN,BITS8,STP1,1200,NTMOUT,SEND_ENQ

4 Program the RS-422 IDEA2 Card as follows:

LX TYPE = DREG QUAD

DREGNUM = DREG1

5 Program the first modem controller port as follows:

port 1 lx type = vmvoice quad ndisconnect

vm port = 0a

6 Program the remaining modem controller ports that will be used as messaging system ports in the same manner. Use the following table for the Vmport numbering pattern.

7 If a port is set to Dial or AnswerDial to dial out for external message delivery, program the port as follows.

This programming allows the messaging system to dial an external number. The example assumes that port 4 is being programmed.

Skip this step if message delivery is made to internal extensions only or if you are programming a port to light lamps. Lamps are lit over the data link.

NOTE

Dregnum should be set to the data register that has been cross-connected to the RS-232 card. The example uses dreg1, but it can be set to any available data register port on the data register card.

Port VMport

1 0a

2 0b

3 1a

4 1b

5 2a

6 2b

port4 lx type = slp quad ndisconnect

profile = slp1

cos = station1

profile slp1 = nrcp (0-63) nsr msg vmbox nexecpt ncamppr ncfpr rcfpr ndrppr ndcppr aring moh nexclh

cos station1 = ntra (0-15)rep npage ndcp ndrp conf ntacamp nexec ntrktfr rcfcf cfos lcr vm ntrktfr ncalltfr_dialt ntalktfr_dialt


To set up the automated attendant (optional)

1 Program a port on the system as a 10-button phone.

2 Attach a phone to the port.

3 Forward calls to the messaging system, depending on how you use it:

● Primary automated attendant. Forward all calls to the messaging system. Incoming calls ring the operator console only if the data link to the messaging system is out of service.

● Backup automated attendant. Forward calls to the messaging system on ring-no-answer. All trunks ring the operator console. If a call is not answered in the number of rings specified, it is forwarded to the messaging system.

4 Program the phone system to assign each trunk group to appear on one of the secondary button locations on the phone.

5 If you do not want an extension on the port programmed in step 2, disconnect the phone.

To set up the phones

❚ Program the call-forward, message-send, and message-retrieve buttons on each phone. For the call-forward and message-send buttons, include the TDL1 parameter to indicate that a trailing digit is dialed.

When the phones, phone system, and messaging system are set up properly, subscribers can press the keys as described in the following table.

Next Step ...


Action Key Presses

Use easy message access MSGS

Call the messaging system and hear the opening greeting

MSGS, 0

Access a voice mailbox to retrieve messages MSGS, 2

Forward all calls CF, 1, MSGS, 0

Forward all calls that are not answered CF, 2, MSGS, 0

Forward calls that are not answered and calls that encounter a busy signal

CF, 3, MSGS, 0

NOTE

When setting call forwarding, subscribers should press MSGS, 0, not MSGS, 2 in the CF setting. Using MSGS, 0 in the setting forwards callers to a greeting. Using MSGS, 2 forwards callers to the mailbox to hear messages.



After programming the phone system, use the following procedure to set up the messaging system. For more information on messaging system features, see System Administrator Help.





The Integration option field is filled with switch options.

4 Click Save.



6 Click Save.







◆ Test the Extensions.See “Testing an Integration” on page 175.

◆ Learn the Phone System TonesSee “Learning the Phone System Tones” on page 179.

◆ Select a Call Transfer TypeSee “Call Transfer Settings, Integration Options, and Troubleshooting” on page 183.

◆ Change Optional Integration SettingsSee “Optional Integration Settings” on page 187.

◆ Set Port ExtensionsSee “Setting Port Extensions” on page 188.

◆ Test the Serial LinkSee “Testing the Serial Link” on page 189.

◆ Changing the Keypad MapSee “Changing the Keypad Map” on page 190.


NOTE



■ Mitel with D42JCTU or D82JCTU Voice Boards Integration

MITEL WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION 49



Connecting the Systems ...................................................................................................................51Programming the Phone System........................................................................................................52

Mitel SX-200 ML..........................................................................................................................52Mitel SX-2000 or 3300 .................................................................................................................53


Overview Use this section of the Integration Guide with the Installation Guide to integrate the phone system with the messaging system. The Mitel with the Dialogic® D42JCTU or D82JCTU voice boards integration uses digital lines to connect the phone system and the messaging system server. Each voice board in the messaging system connects to the phone system through a PBX station interface cable.

● A D82JCTU voice board emulates up to eight Mitel Superset digital phones.

● A D42JCTU voice board emulates up to four Mitel Superset digital phones.



2 Connect the systems. See “Connecting the Systems” on page 51.

3 Set up the phone system. See “Programming the Phone System” on page 52.

4 Configure the messaging system. See “Configuring the Messaging System” on page 55.




Integration RequirementsTo set up the Mitel with D42JCTU or D82JCTU integration:

Phone System● One of the following Mitel phone systems:

● One Digital Network Interface Circuit (DNIC) port, that emulates a Superset 430 digital phone, installed and set up as a messaging system port.

● The phone system is ready for the integration.


● The phone system messaging system ports connected to the voice boards installed in the messaging system server with a PBX station interface cable for each group of eight messaging system ports.

Messaging System Server● The Dialogic D42JCTU or D82JCTU voice boards are installed.

● A PBX station interface cable for each voice board.

● Messaging system installed and ready for the integration.


Phone System Software Version

SX-200 ML Superset 420, 430

SX-2000 Superset 430

3300 Superset 430

UNIVERGE UM4730 INTEGRATION GUIDE MITEL WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION50


After installing all of the required hardware on the messaging system server, use the following procedure to connect the phone and messaging systems.


1 Connect the phone system digital lines 1-8 (or 1-4 on a 4-port system) to a type 66 interconnect block.

2 Refer to the following Two-wire pinouts table for cabling requirements.

3 Connect a telco cable to an amphenol connection on the type 66 interconnect block.

4 Connect the other end of the telco cable to a PBX station interface cable.

5 Connect the other end of the PBX cable to a voice board installed in the messaging system server.

6 Repeat steps 1 through 5 for each voice board installed.

Next Step ...

◆ Program the Phone System. See “Programming the Phone System” on page 52.


Type 66 Block Pair

Pin Number


1 2 27 2


Tip 1 Ring 1

2 4 29 4


Tip 2 Ring 2

3 6 31 6

red-blue blue-red

Tip 3 Ring 3

4 8 33 8

red-green green-red

Tip 4 Ring 4

5 10 35 10

red-slate slate-red

Tip 5 Ring 5

6 12 37 12


Tip 6 Ring 6

7 14 39 14


Tip 7 Ring 7

8 16 41 16


Tip 8 Ring 8



After confirming that the integration is enabled, use the following procedures to program your phone system model.

● For the Mitel SX-200ML, see the procedures below.

● For the Mitel SX-2000 or 3300, see the procedures on page 53.

Mitel SX-200 MLUse the following procedures to set up the messaging system extensions and the hunt group.

To set up the messaging system extensions on the Mitel SX-200 ML

1 On the phone system Main Menu, select option 9, Station/Supersets.

2 Type 430 in each messaging system extension TYP field.

3 Select a messaging system extension field, then press ESC+3 to expand the extension settings.

4 Set the first key (01) Type to Prime, then set the remaining key types to Speed Dial.

5 Repeat steps 3 through 4 for each messaging system extension.

To set up the hunt group on the Mitel SX-200 ML

1 On the phone system Main Menu, select Option 17, Hunt Groups.

2 Create a circular hunt group with a pilot number. This is the published messaging system number for all direct and forwarded calls. Include all of the messaging system extensions in the hunt group.


To enable the Last Party Clear Dial Tone

❚ On the phone system, enable the Last Party Clear Dial Tone.

If the Last Party Clear Dial Tone is not enabled, the messaging system detection is delayed when internal calls are disconnected.

Next Step ...


Mitel SX-2000 or 3300Use the following procedure to configure the messaging system extensions, to assign key numbers, and to configure the hunt group for the Mitel SX-2000 or Mitel 3300 integration.

To set up the messaging system extensions on the Mitel SX-2000 or 3300

1 On the phone system console Main Menu, select System Forms.

2 On the System Forms screen, select DNI Circuit Assignment.

3 On the DNI Circuit Assignment screen, set the Device Type Channel #1 field to Superset 430 for each messaging system extension.

To assign key numbers on the Mitel SX-2000 or 3300

1 On the phone system console Main Menu, select Multiline Set Forms.

2 On the Multiline Set Forms screen, select Multiline set key assignment.

3 On the Multiline Set Key Assignment screen, type a messaging system extension in the Prime directory number field.

4 Set the Line Type field for the extension to Not assigned.

5 Repeat steps 3 through 4 for each messaging system port extension number.

To set up the hunt group on the Mitel SX-2000 or 3300

1 On the phone system console Main Menu, select Group Forms.

2 On the Group Forms screen, select Hunt Group Assignment.

c

d


The Hunt Group Assignment screen appears.

3 In the Pilot number field, type the <published messaging system number> for all direct and forwarded calls, then press ESC+1.

4 In the Name field type a <group name>. For example, D82JCTU hunt.

5 In the Hunt Mode field, type circular.

6 In a Directory Number field, type a messaging system extension.

7 In the Directory Name field, type a name for the messaging system extension.

8 Repeat steps 6 through 7 for each messaging system extension that must be set up for the integration.

Next Step ...


ef

g



After setting up the phone system, use the following procedures to set up the messaging system. For more information about messaging system features, see the System Administrator Help.





The Integration options field displays the switch options.

4 Click Save.



6 Click Save.















NOTE

If data in the Integration options field is changed, restart the messaging system software to activate the changes.


■ Mitel SX-50 with D42JCTU or D82JCTU Voice Boards Integration

MITEL SX-50 WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION 57




Programming the Phone System........................................................................................................61Setting Mitel SX-50 Message Waiting System Options.......................................................................61Configuring Call Forwarding on Subscriber Lines ..............................................................................61Programming Superset 420 Digital Stations ....................................................................................62


Overview Use this section of the Integration Guide with the Installation Guide to integrate the phone system with the messaging system. The Mitel SX-50 integration uses digital lines to connect the phone system and the messaging system server. Each voice board in the messaging system connects to the phone system through a PBX station interface cable.

● The D42JCTU voice board emulates up to four Mitel Superset digital phones.

● The D82JCTU voice board emulates up to eight Mitel Superset digital phones.





4 Set up the messaging system for the integration. See “Configuring the Messaging System” on page 65.



7 Select a transfer type. See “Call Transfer Settings, Integration Options, and Troubleshooting” on page 183.

RequirementsTo set up the Mitel SX-50 integration, confirm that you have the following:

Phone System● Mitel SX-50 DPABX, MS-54 or later.



● The phone system messaging system ports connected to the voice boards installed in the messaging system server with a PBX station interface cable for each group of eight messaging system ports.

Messaging System Server● The Dialogic D42JCTU or D82JCTU voice boards installed as described in the Installation

Guide.

● PBX station interface cable for each voice board.

● The messaging system installed and ready for the integration.

● A system key that enables the integration and the appropriate number of messaging system ports.

UNIVERGE UM4730 INTEGRATION GUIDE MITEL SX-50 WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION58


After installing all of the required hardware in the messaging system server, use the following procedure to connect the phone system and messaging system.

To install the required messaging system hardware, such as voice boards, refer to the Installation Guide. For wiring pinout information, see the “Two-wire pinouts” and “Four-wire pinouts” below.

System Connections



2 Connect a telco cable to an amphenol connection on the type 66 interconnect block.

3 Connect the other end of the telco cable to a PBX station interface cable.

4 Connect the other end of the PBX cable to a voice board installed in the messaging system server.

5 Repeat steps 1 through 4 for each additional voice board installed.


1 Connect the phone system digital lines 1-8, or 1-4 on a 4-port system, to a type 66 interconnect block.

Refer to the “Two-wire Pinouts” and “Four-wire Pinouts” tables for cabling requirements.

Two-wire Pinouts


Type 66 Block Pair

Pin Number


1 2 272


Tip 1 Ring 1

2 4 29 4


Tip 2 Ring 2

3 6 31 6

red-blue blue-red

Tip 3 Ring 3

4 8 33 8

red-green green-red

Tip 4 Ring 4


Next Step ...


5 10 35 10

red-slate slate-red

Tip 5 Ring 5

6 12 37 12


Tip 6 Ring 6

7 14 39 14


Tip 7 Ring 7

8 16 41 16


Tip 8 Ring 8

Four-wire Pinouts


Pin Number


1 26 1

27 2


TXR1 TXT1 PXR1 PXT1

2 28 3

29 4


TXR2 TXT2 PXR2 PXT2

3 30 5

31 6


TXR3 TXT3 PXR3 PXT3

4 32 7

33 8


TXR4 TXT4 PXR4 PXT4

5 34 9

35 10


TXR5 TXT5 PXR5 PXT5

6 36 11 37 12


TXR6 TXT6 PXR6 PXT6

7 38 13 39 14


TXR7 TXT7 PXR7 PXT7

8 40 15 41 16


TXR8 TXT8 PXR8 PXT8

Two-wire Pinouts


Type 66 Block Pair

Pin Number




Use the procedures in this section to program the phone system:

● Set the phone system message waiting options for the integration.

● Program the call forwarding options for subscriber lines.

● Set up the digital stations assigned to messaging system.

Setting Mitel SX-50 Message Waiting System OptionsTo set the message waiting system options, use the following procedure.

To set the Mitel SX-50 message waiting system options

1 Type the following command on the operator console to access system options programming:

command 100

2 Locate register 12 to access message waiting options.

3 In the Function fields c, d, and f program the values shown in the following diagram.

Configuring Call Forwarding on Subscriber LinesUse the following procedure to access class of service (COS) and set up call forwarding on Mitel SX-50 subscriber lines.

To set up call forwarding on subscriber lines

1 Type the correct command, range 121–129, on the operator console to access new or existing class of service programming for subscriber lines.

2 Locate register 4 to access call forwarding options.

3 Program the call forwarding values necessary for subscriber lines to work with the messaging system transfer type selected. Refer to the diagram for available functions and values.

NOTE

The call forwarding options programmed depend on the messaging system transfer type selected and if call transfer to an extension is used.

Register

Message waiting system enable with

lampsMessage waiting

indication always used

Message waiting automatic cancel disabled

Function fields

Program values to be entered

Register

Call forward, busyCall forward, ring-no-answer

Call forward, busy and ring-no-answer

Function fields

Program values to be selected:0 = disable1 = internal only2 = internal and external, extension only3 = internal and external, extensions and

external lines


Programming Superset 420 Digital Stations Mitel SX-50 Superset 420 digital stations assigned to the messaging system are programmed to configure the following features:

● Class of service

● Hunt group

● Prime line key

● Message waiting key

A specific key assignment configuration for digital stations programmed at the Mitel SX-50 console is required by the messaging system software.

Class of Service for Superset 420 Digital StationsThe class of service (COS) available on the Mitel SX-50 is COS 1–9, represented by Commands 121–129. The messaging system and subscriber extensions must be set to different COS numbers. For example, in the following procedure and diagram, the messaging system extensions are assigned to COS 1.

To program class of service for Mitel SX-50 Superset 420 digital stations as voice mail ports

1 On the operator console, type the following command to access COS 1 for the messaging system extensions.

command 121

2 Locate register 7 to access options for auxiliary attendant position and Superset 420 message programming.

Type the values in Function fields b and d, for the auxiliary attendant position and Superset 420 message programming.

Messaging System Hunt GroupHunt group locations 1–6 are available on the Mitel SX-50, represented by commands 361-366. In the following procedure, the hunt type is programmed and the Mitel SX-50 messaging system extensions are assigned to hunt group 1 using command 361.

To set up the hunt type and Mitel SX-50 extension assignments for the hunt group

1 To access the extension hunt group programming, type the following command on the operator console:

command 361

2 Locate register 1 to access the extension hunt group 1 options.

NOTE

The messaging system ports require auxiliary attendant capability to turn message waiting indicator on or off. The messaging system ports emulate the Mitel 420 superset phones.

Register

Superset 420 message programming enabled

Auxiliary attendant position enabled

Function fields

Program values to be typed.


3 To program a terminal hunt type, type one, the value shown in Function field b.

4 Type the messaging system extension numbers in Register 2 through Register 9, where fields b through e are the hunt group member extension numbers, shown below.

Assigning Prime Line and Message Waiting Keys on Superset 420 Digital StationsYou must identify the Superset 420 equipment numbers to assign the prime line and message waiting keys on Mitel SX-50 Superset 420 digital stations. These numbers determine the DNIC slot location and digital station circuits on the DNIC used for voice messaging.

The following procedure shows an example where the DNIC is in slot location 1 and the digital station circuits in use are: 01, 02, 03, and 04.

Command 401 locates the equipment number that determines the correct slot location and circuit for the first digital station. Key assignments are programmed on the Superset 420 digital station circuit.

To assign prime line and message waiting keys

1 On the operator console, type the following command to access digital station circuit 01 on the DNIC card in slot 1:

command 401

RegisterTerminal hunt type enabled

Function fields

Program values to be typed.

Hunt group member number

(Register)

Hunt group member extension number

Function fields

Voice mail extension numbers to be typed.

For system expansion

63
MITEL SX-50 WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION

2 Type the values shown in function fields c, d, and e for keys 01 and 03 to program the prime line and message waiting key configurations for the first Superset 420 digital station assigned as a messaging system extension.

3 Type the first messaging system extension number in fields f, g, h, and i for keys 01 and 03.

4 Repeat steps 1 through 3 for each messaging system extension being used.

Command 402 is used to locate DNIC digital station circuit number 02 for the next messaging system extension, and so on.

For the attendant function line appearance, fields d and e are used to indicate attendant function number 10 for message waiting.

Next Step ...


Key number

Line appearance type: 1= prime line; 8= attendant function

Immediate ring type enabled

Call direction both ways enabled

Function fields

Program values to be typed. Extension number data replaces x characters.

TEGRATION
UNIVERGE UM4730 INTEGRATION GUIDE MITEL SX-50 WITH D42JCTU OR D82JCTU VOICE BOARDS IN64


After setting up the phone system, use the following procedures to set up the messaging system. For more information on messaging system features refer to System Administrator Help.






4 Click Save.



6 In the Navigation pane, click System > Switch > MWI.

Verify that that Reset MWI after each new message is not selected, since the on and off codes use the same key press.

7 Click Save.

8 Stop and restart the messaging system software:













NOTE

If data in the Integration options field is changed, restart the messaging system software to activate the changes.

65
MITEL SX-50 WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION

■ NEC NEAX 2000 IPS with Serial MCI Integration

NEC NEAX 2000 IPS WITH SERIAL MCI INTEGRATION 67



Connecting the Systems ...................................................................................................................69Programming the Phone System........................................................................................................70Configuring the Messaging System.....................................................................................................73

Overview Use this section of the Integration Guide with the Installation Guide to integrate the messaging system with the NEAX 2000 IPS phone system using a network connection. Both calls and call information are transmitted using Internet protocols.









RequirementsThe NEAX 2000 IPS phone system integration requires the following:

Phone System● CP24 card.

● Licenses for the total number of IP phones and messaging system ports.

● IP PAD card with/without VCTI for connections to TDM stations/trunks. Every simultaneous connection between IP Phones and TDM stations/trunks requires one IP PAD channel. Three party conference and all features based on it, such as executive override used for Live Record, require an IP PAD channel for every IP party involved.

● Dterm IP Phone.


● A system USB flash drive.

● A Security Key File disc that licenses the integration and the appropriate number of messaging system ports.

NOTES

If firewalls are used in the network, they must be configured to allow peer-to-peer connections.Only the G.711 and G.729 codecs with 20ms or 40ms packets (payload) are supported.If route names are used in ADRTL or ADRTN, adjust the DispParse.ini file. Although the syntax of DispParse.ini is self explanatory, you might prefer to avoid using the ADRTL and ADRTN commands.

UNIVERGE UM4730 INTEGRATION GUIDE NEC NEAX 2000 IPS WITH SERIAL MCI INTEGRATION68


Use the following procedure to connect the phone system to the messaging system.

To connect the phone system to the messaging system

1 Connect the phone system voice mail network card to the IP network.

IP connectivity needs to be provided to the MP card, IP PAD and IP stations.

2 Connect one end of the RS-232 serial cable to the Cable 1 CA RS-232 cable on the phone system.

3 Connect the other end of the RS-232 serial cable to the COM1 serial port on the messaging system computer.

Next Step ...


NOTE

Only the G.711 and G.729 codecs are supported.If firewalls are used in the network, they must be configured to allow peer-to-peer connections.



After connecting the systems, use the following procedures to program the phone system. Programming phone system or extension options using different procedures than those defined in this document might adversely affect integration performance.

Use a Customer Administration Terminal (CAT) to program the phone system in the following procedures.


1 Program the PIMs (real/virtual) following the PBX setup guide.

2 Program the MP address. This is used as the Device Registration Server (DRS) and needs to be programmed before the messaging system is installed.

The ipreconfig utility can be used to reprogram this address and extensions in the messaging system.

3 Program the phone system voice mail ports in the PBX as normal IP stations (CM 14). Program user extensions following the phone system manual (IP extensions are programmed in CM 14 while TDM extensions are programmed using CM 10).

4 Program the IP PAD card following the phone system manual. If compression is used, make sure all calls to the messaging system use G.711. Select a separate Location Group for the messaging system.

Example IP Pad programming:

NOTE

Phone system programming must be done by a NEC PBX-certified technician.

CM 050 > 00-63 >

CM 054 > 00-63 >

CM 056 > 00-63 >

CM 058 > 00-63 >

CM 0B00 > 00 > IP address

CM 0B00 > 01 > Netmask

CM 0B00 > 02 > Gateway

CM 14 > LEN > <extension number>

Set up IP voice mail extensions

CM 10 > Unequipped_LEN > <voice mail pilot number>

Set up pilot extension

NOTES

The pilot of the UCD group must be a Phantom S/L station assigned with command code 10 to a LEN with no card in the slot.In command 14, the LEN number is 5 digits. In command 10, the LEN number is 3.

CM 0A09 All IP PAD trunks.

CM 1239 and CM 1250 All IP Phones and messaging system extensions.

CM 8Axxx > 173 > All CCIS over IP routes.

CM 6700 Bidirectional for the Location Group of the voice mail.

CM 42 to 01 Corresponding values in to mandate the use of the G.711 codec.

CM 0A00 > 00 > 000

CM 0A01 > 00 > IP Address

CM 0A02 > 00 > Netmask

CM 0A03 > 00 > Gateway


Example G.711 programming:

5 Set up and test access code executive override.

6 Use the CM command to program the general configuration options.

7 Set up communication parameters for the PBX serial port.

CM 0A22 > 00 > 0 Enable Non Linear processor

CM 0A50 > 00 > XX XX = IP PAD number

CM 0A71 > 00 > 1 Allow G.711 without VCTI

CM 0A09 > 00 > 00 Location group

CM 10 > LEN > DDXXZZ XX = IP PAD number, ZZ = Pad channel number

CM 1239 > Ext > LG1 Extensions in LG1 (local)

CM 1250 > Ext > LG1 Extensions in LG1 (remote)

CM 1239 > VMP > LG2 VM ports in LG2 (local)

CM 1250 > VMP > LG2 VM ports in LG2 (remote)

CM 0A09 > IPPADCh > LG1 IP PAD trunks in LG1

CM 8Axxx > 173 > LG1 CCIS over IP routes in LG1

CM 6700 > LG1LG2 > 00 LG1 calling LG2; program all LGs

CM 6700 > LG2LG1 > 00 LG2 calling LG1; program all LGs

CM 42 > 100 > 01 G.711

CM 200 > *4 > A006 Executive override

CM 08 > 515 > 0 Disable encoded password

CM 08 > 234 > 1 Disable auto lamp out when calling voice mail

CM 08 > 147 > 1 Disable SLT camp-on

CM 410 > 01 > 06 First call forward no answer timer (minimum 06)

CM 08 > 702 > 0 Enable ringing signal or live record start signal including caller id information

CM 08 > 703 > 0 Enable calling or forwarding party information for CCIS terminated call

CM 08 > 379 > 0 Enable caller name display for the called station using CCIS

CM 08 > 706 > 0 Enable MWI across CCIS

CM 08 > 713 > 1 Enable MWI across CCIS

CM 0401 > 01 > 1 0=port 0; 1=port 1; 7=AP00

CM 4000 > 1 > 10 10=MCI; 11=MCI+SMDR

CM 4001 > 1 > 1/0 8 bit/7 bit

CM 4002 > 1 > 1 Parity None

CM 4003 > 1 > 1 No Parity

CM 4004 > 1 > 1 Stop bits 1

CM 4005 > 1 > 1 DTR signal set hi

CM 4006 > 1 > 1 RTS signal set hi

CM 4008 > 1 > NONE/5 Speed (None=4=9600bps; 5=19200)


8 Set function keys and ringer activation for each messaging system port:

9 Build UCD group for messaging system extensions:

10 Designate messaging system ports and user extensions.

11 Set voice mail pilot station to connect to the messaging system per tenant number (Quick TRF to VM feature).

12 If the messaging system is used as an automated attendant, program the Direct Input Termination (DIT):

13 Set stations to call forward to the Pilot number of the messaging system hunt group. The phone system provides the follow along ID and adds the digit 2 for transfer override.

14 Save all changes.

CM EC6 > 0 > 0

15 Log an IP phone in to one of the phone system voice messaging extensions and verify calling patterns to different locations. A network analyzer or sniffer may be used to confirm that the G.711 codec is used to and from all location groups.

16 Log the IP phone out of the phone system when testing is complete.

CM 1290

Next Step ...


CM 9000 > Ext,16 > Ext Set line appearance on key 16

CM 9000 > Ext,Key > CCC Delete keys 01-15, 17-20, 22, and 24

CM 9001 > Ext, 16 > 1 Set ringer activation to key 16

CM 93 > Ext > Ext Set prime line to its own extension

CM 170 > ExtA > Ext B

CM 171 > <voice mail pilot number> > 1

Set UCD pilot

CM 172 > Ext > <UCD Group Number> Assign UCD Group number

NOTES

VMP = program each voice mail port including pilot number.In command 170, you need to link the pilot number to the first station. Link every extension to the next one. Link the last extension back to the pilot number.

CM 1310 > VMP > 0 Enable MCI VMX port (0=VMS; 1=ordinary station)

CM 1322 > VMP > 0 momentary open

CM 1324 > VMP > 0 0=VMS; 1=ordinary station

NOTE

Program every user extension in the phone system.

CM 5115 > TN > VM Pilot TN = 00-63 tenant number

CM 3004 > Trunk > VM Pilot Day Mode

CM 3005 > Trunk > VM Pilot Night Mode



After setting up the phone system, use the following procedures to configure the messaging system. For more information on messaging system features, refer to System Administrator Help.


1 Sign in to the Administration Console:


3 Select the phone system from the Switch list.

The phone system parameters appear in the Integration options field. Depending on the phone system select additional data might appear on the Switch Information page.

4 Click Save.


Assign an Extension, Password, and Authorization name for each port displayed in the table.

6 Click Save.















NOTE



■ NEC NEAX 2000 IPS without Serial MCI Integration

NEC NEAX 2000 IPS WITHOUT SERIAL MCI INTEGRATION 75



Connecting the Systems ...................................................................................................................77Programming the Phone System........................................................................................................78

Overview Use this section of the Integration Guide with the Installation Guide to integrate the messaging system with the NEAX 2000 IPS phone system using a network connection. Both calls and call information are transmitted using Internet protocols.









Integration RequirementsThe NEAX 2000 IPS phone system integration requires the following:

Phone System● CP24 card.

● Licenses for the total number of IP phones and messaging system ports.

● IP PAD card with/without VCTI for connections to TDM stations/trunks. Every simultaneous connection between IP Phones and TDM stations/trunks requires one IP PAD channel. Three party conference and all features based on it, such as executive override used for Live Record, require an IP PAD channel for every IP party involved.

● Dterm IP Phone.


● A system USB key.

● A Security Key File disc that enables the integration and the appropriate number of messaging system ports.

NOTES

If firewalls are used in the network, they must be configured to allow peer-to-peer connections.Only the G.711 and G.729 codecs with 20ms or 40ms packets (payload) are supported.If route names are used in ADRTL or ADRTN, adjust the DispParse.ini file. Although the syntax of DispParse.ini is self explanatory, you might prefer to avoid using the ADRTL and ADRTN commands.

UNIVERGE UM4730 INTEGRATION GUIDE NEC NEAX 2000 IPS WITHOUT SERIAL MCI INTEGRATION76


To connect the messaging system to the phone system

❚ Connect the messaging system network card to the IP network. IP connectivity needs to be provided to the MP card, IP PAD and IP stations.

Next Step ...


NOTE

Only the G.711 and G.729 codecs are supported.If firewalls are used in the network, they must be configured to allow peer-to-peer connections.



After connecting the systems, use the following procedures to program the phone system. Programming phone system or extension options using different procedures than those described in this document might adversely affect integration performance.

The following procedures use a Customer Administration Terminal (CAT) to program the phone system data.



2 Program the MP address. This is used as the Device Registration Server (DRS) and needs to be programmed before the messaging system is installed.

The ipreconfig utility can be used to reprogram this address and extensions in the messaging system.

3 Use CM 14 to program the phone system voice mail ports in the PBX as normal IP stations.

4 Program user extensions following the phone system manual. IP extensions are programmed in CM 14 while TDM extensions are programmed in CM 10.

5 Program the IP PAD card following the phone system manual. If compression is used, make sure all calls to the messaging system use the G.711 codec. Select a separate Location Group for the messaging system.

NOTE


CM 050 > 00-63 >

CM 054 > 00-63 >

CM 056 > 00-63 >

CM 058 > 00-63 >

CM 0B00 > 00 > IP address

CM 0B00 > 01 > Netmask

CM 0B00 > 02 > Gateway

CM 14 > LEN > <ext num-ber>

Set up IP messaging system extensions.

CM 10 > Unequipped_LEN > <pilot ext>

Set up pilot extension.

NOTES

The pilot of the UCD group must be a Phantom S/L station assigned with command code 10 to a LEN with no card in the slot.In command 14, the LEN number is 5 digits. In command 10, the LEN number is 3.

CM 0A09 All IP PAD trunks.

CM 1239 and CM 1250 All IP Phones and messaging system extensions.

CM 8Axxx > 173 > All CCIS over IP routes.

CM 6700 Bidirectional for the messaging system Location Group.

CM 42 to 01 Mandate the use of G.711 codec.


Example IP Pad programming:

Example G.711 programming:

6 Set up and test access codes for MWI and executive override.

7 Use the CM command to program the general configuration options.

8 Set functions keys and ringer activation for each messaging system port:

9 Build UCD group for messaging system extensions:

CM 0A00 > 00 > 000

CM 0A01 > 00 > IP Address

CM 0A02 > 00 > Netmask

CM 0A03 > 00 > Gateway

CM 0A22 > 00 > 0 Enable Non Linear processor.

CM 0A50 > 00 > XX XX = IP PAD number.

CM 0A71 > 00 > 1 Allow G.711 codec without VCTI.

CM 0A09 > 00 > 00 Location group.

CM 10 > LEN > DDXXZZ XX = IP PAD number and ZZ = Pad channel number

CM 1239 > Ext > LG1 Extensions in LG1 (local).

CM 1250 > Ext > LG1 Extensions in LG1 (remote).

CM 1239 > VMP > LG2 VM ports in LG2 (local).

CM 1250 > VMP > LG2 VM ports in LG2 (remote).

CM 0A09 > IPPADCh > LG1 IP PAD trunks in LG1.

CM 8Axxx > 173 > LG1 All CCIS over IP routes in LG1.

CM 6700 > LG1LG2 > 00 LG1 calling LG2; program all LGs.

CM 6700 > LG2LG1 > 00 LG2 calling LG1; program all LGs.

CM 42 > 100 > 01 G.711

CM 200 > *9 > A040 Message waiting lamp set.

CM 200 > #9 > A041 Message waiting lamp reset.

CM 200 > *4 > A006 Executive override.

CM 08 > 234 > 1 Disable auto lamp out when calling voice mail.

CM 08 > 147 > 1 Disable SLT camp-on.

CM 410 > 01 > 06 First call forward no answer timer (minimum 06).

CM 08 > 702 > 0 Enable ringing signal or live record start signal including caller id information.

CM 08 > 703 > 0 Enable calling or forwarding party information for CCIS terminated call.

CM 08 > 379 > 0 Enable caller name display for the called station using CCIS.

CM 08 > 706 > 0 Enable MWI across CCIS.

CM 08 > 713 > 1 Enable MWI across CCIS.

CM 9000 > Ext,16 > Ext Set line appearance on key 16.

CM 9000 > Ext,Key > CCC

Selected keys 01-15, 17-20, 22, and 24.

CM 9001 > Ext, 16 > 1 Set ringer activation to key 16.

CM 93 > Ext > Ext Set prime line to its own extension.

CM 170 > ExtA > Ext B

CM 171 > <voice mail pilot number> > 1 Set UCD pilot.

CM 172 > Ext > <UCD Group Number> Assign UCD Group number.


10 Designate messaging system ports and user extensions.

11 Set the voice mail pilot station to connect to the voice mail per tenant number (Quick TRF to VM feature).

12 If the messaging system is used as an automated attendant, program Direct Input Termination (DIT):

13 Set stations to call forward to the Pilot number of the messaging system hunt group. The phone system provides the follow along ID and adds the digit 2 for transfer override.

14 Save all changes.

CM EC6 > 0 > 0

15 Log an IP phone in to one of the phone system voice messaging extensions and verify calling patterns to different locations. A network analyzer or sniffer can be used to confirm that G.711 codec is used to and from all location groups.

16 Log the IP phone out of the phone system when testing is complete.

CM 1290

Next Step ...


NOTES

VMP = program each phone system voice mail port including pilot number.In command 170, link the pilot number to the first extension, link all extensions in sequence, then link the last extension back to the pilot number.

CM 1324 > VMP > 0 0=VMS; 1=ordinary station.

CM 1303 > EXT > 0 Allow setting of the MWI Lamp.

NOTE

Program every user extension in the phone system.

CM 5115 > TN > VM Pilot TN = 00-63 tenant number

CM 3004 > Trunk > VM Pilot Day Mode

CM 3005 > Trunk > VM Pilot Night Mode



After setting up the phone system, use the following procedures to configure the messaging system. For more information on messaging system features, refer to System Administrator Help.





The phone system parameters appear in the Integration options field. Depending on the phone system select additional data might appear on the Switch Information page.

4 Click Save.



6 Click Save.















NOTE



NEC NEAX 2400 WITH IP PROTIMS INTEGRATION 83




■ NEC NEAX 2400 with IP Protims Integration

Overview Use this section of the Integration Guide with the Installation Guide to integrate the phone system and messaging system. NEAX 2400 IP Protims integration uses a network connection to connect messaging system server with the phone system. Each voice messaging port emulates an IP VPS extension. The communication between the parties is facilitated by a series of Voice over IP (VOIP) protocols, such as DRS, Protims, RTP, H245, Voice control, used for call signaling and voice streaming, some of them being NEC proprietary protocols.


1 Review the system and equipment requirements. See “Integration Requirements,” below.

2 Program the phone system and extensions.See “Programming the Phone System” on page 85.


Integration RequirementsThe steps to set up the NEC NEAX 2400 IP Protims integration require the following:

Equipment

● All Dterm® IP phones that will be used with UNIVERGE UM4730 must have software version 1.2 or newer.

Phone System● A NEAX 2400 IMX software version 16 or newer or SV7000, model T10 or T20, installed and

ready for the integration as described in the phone system documentation.

● Password encryption type for IP extensions is MD5, see command ASYDL, index 848, b7=0.

● Fully functional IP PAD cards with VCTI sub-boards.

Messaging System Server● If the G729 codec is used, the Sipro Lab G729 codec driver must be installed in the voice

mail server.

● The installation file for this driver is named sl_g729a_setup.exe and can be found in the Voice Mail\Utilities folder on the Installation disc.

● A system key that licenses the integration and the appropriate number of voice messaging ports.

NOTE

IP PAD cards provide interface function between IP telephony, terminals or other devices on LAN, and non-IP telephony, conventional networks such as PSTN, ISDN, and private networks. If the telephony network is 100% IP, the IP PAD cards are not mandatory.

UNIVERGE UM4730 INTEGRATION GUIDE NEC NEAX 2400 WITH IP PROTIMS INTEGRATION84


If programming options other than those described in the following procedures are used, the integration performance might be adversely affected. Refer to the phone system documentation for detailed information about the commends.

To program the IP voice messaging ports in the phone system

1 Use the DPTR command to make sure that the NEAX 2400 phone system has licenses for using IP extensions.

2 Use the AISTL command to configure the voice messaging ports as IP VPS extensions. Set KIND = IP VPS and TEC = 26.

3 Assign the ports successive VPS channels, starting with IP VPS CH = 0.

4 Write down the VPS ID value of the voice messaging ports, for use during the UM4730 installation. Enter the value when the UNIVERGE UM4730 installation wizard asks for this value.

5 Write down the MWI analog codes that the NEAX 2400 phone system uses for turning the phones lamps on and off. These codes are needed when configuring UM4730 to work with the integration.

6 Use the ASFC command to specify a Service Feature Restriction Class (SFC) for the voice messaging ports.

All of the voice messaging ports should be placed in their own SFC. The following Service Feature Indexes (SFIs) are needed in the SFC:

7 Use the ASHU command to assign all of the voice messaging ports to a Uniform Call Distribution (UCD) group.

8 Use the ALOCL and AIVCL commands to set the same location ID for all voice messaging ports and set the codecs G711, U-Law or A-Law, and G729A with payload size equal to 40 milliseconds for that location ID.

Next Step ...


NOTE

The following procedures are written with the assumption that a Maintenance Administration Terminal (MAT) or similar tool is used to program the phone system.

CAUTION

All voice messaging ports must have the same value assigned for VPS ID.

NOTE

The NEAX 2400 phone system may not have any settings made to use codes for MWI analog operations. If this is the case, use the ANPD and ASPA commands to set “SRV=SSCA” and “SIDA=54 / 55.”

SFI Service feature

10 Call hold

103 Assignment of no answer timer for blind transfer to station or blind transfer to attendant

104 Blind transfer

NOTE

To associate the voice messaging ports with a specific location, add the IP address of the messaging system server to that location.

NEC NEAX 2400 WITH IP PROTIMS INTEGRATION 85


After ensuring that the messaging system server is ready for the integration by completing all appropriate tasks in the Installation Guide, use the following procedure to confirm that the integration is enabled.



2 In the Navigation pane, click System > Switch > Switch Information. Confirm that the switch settings match those in the following table.

If the settings are incorrect the integration features might not be enabled.

3 Type the IP address of the phone system in the Primary IP registrar field.

4 Click Save.

5 In the Navigation pane, click System > Switch > MWI. Enter the MWI analog codes that the NEAX 2400 phone system uses for turning the phones lamps on and off.

6 Click Save.



If the port information is incorrect, verify the phone system settings made for the voice messaging ports, see “To program the IP voice messaging ports in the phone system” on page 85 to make the necessary adjustments.

8 Click Save.






NOTE

The software version used depends on the phone system settings. Check the ASYDL 672 parameter. If bit b1=1, the software version must be “Software Release 16 or newer with IP ports and display like DTERM_E”. Otherwise, the software version must be “Software Release 16 or newer with IP ports and display like DTERM_III”.

UNIVERGE UM4730 INTEGRATION GUIDE NEC NEAX 2400 WITH IP PROTIMS INTEGRATION86

■ NEC NEAX 2400 IPX with LAN MCI Integration

NEC NEAX 2400 IPX WITH LAN MCI INTEGRATION 87



Connecting the Systems ...................................................................................................................89Programming the Phone System........................................................................................................90Configuring the Messaging System.....................................................................................................93

Overview Use this section of the Integration Guide with the Installation Guide to integrate the messaging system with the NEAX 2400 IPX phone systems through a network connection. Both calls and call information are transmitted using Internet Protocols.









Integration RequirementsThe steps to set up the NEAX 2400 IPX phone system integration requires the following:

Phone System● Licenses for the total number of IP phones and messaging system ports.

● IP PAD card with VCTI for connections to TDM stations/trunks

● Dterm IP phone.



● A Security Key File disc that enables the integration and the appropriate number of messaging system ports.

NOTE

Every connection between an IP Phone and TDM stations/trunks requires one IP PAD channel. Phone system features which rely upon three-party conferencing, such as executive override used for Live Record, require an IP PAD channel for every IP party involved.

NOTE

Softkeys are not available with this integration.

UNIVERGE UM4730 INTEGRATION GUIDE NEC NEAX 2400 IPX WITH LAN MCI INTEGRATION88


Use the following procedure to connect the phone system to the messaging system computer.


1 Connect the messaging system network card to the IP network.

IP connectivity should be provided to the MP, the PHD card, if it exists, IP PAD, and IP stations.

2 If a firewall exists, configure the firewall to allow peer-to-peer connections.

3 Only the G.711 and G.729 codecs with 20ms or 40ms packets (payload) are supported.

4 If route names are used in ADRTL or ADRTN commands, you must adjust your DispParse.ini file.

Although the syntax of DispParse.ini is self explanatory, you might prefer to avoid using the ADRTL or ADRTN commands.

5 Connect one end of an RS-232 serial cable to the Cable 1 CA RS-232 cable on the phone system.

6 Connect the other end of the RS-232 serial cable to the COM1 serial port on the messaging system computer.

Next Step ...




After connecting the systems, use the following procedures to program the phone system. Programming the phone system or extension using procedures other than those supplied in the in this document might adversely affect integration performance.

The following procedures use a Maintenance Administration Terminal (MAT) to program the phone system.



ASYDL SYS 1 INDEX 556




2 Program the MP address, netmask, and Default gateway. This is used as the Device Registration Server (DRS) and needs to be programmed when the messaging system is installed.

ADTM

3 Program the physical card or internal emulation (PHD).

ALIDL

4 Program the messaging system ports in the PBX as normal IP stations.

AISTL (DtermIP, TEC 12, RSC, SFC)

5 Program user extensions following the phone system installation manual. IP extensions are programmed in AISTL while TDM extensions are programmed in ASDT.

6 Setup and test access codes for executive override (E-1).

Use ASFC to:

■ Program SFI 3 and SFI 11 for the SFC of the messaging system ports (E-1).

■ Program SFI 4 and SFI 11 for the other SF classes (E-1).

ASFC

7 Use ANPD and ASPA to program Feature Access Code for Executive Override (SSC 4) (E-1).

8 Check ANPDL, ASPAL, ANPDN, and ASPAL.

NOTE


NOTES

Assign a different service feature class (SFC) for the messaging system ports as you need to set the MWI from the messaging system ports only.You do not need to program AMAC.Delete AKYD in case it is programmed or make sure you have default programming for the required keys. For example, line appearance, ring, or executive override on line key 4.

NOTES

The Local Memory and Network Memory commands override the Data Memory commands. Check ANPDL, ASPAL, ANPDN, and ASPAN to confirm they do not conflict with the access code settings for executive override.For the Executive Override feature to work on the PBX, you need to have three-party conferences enabled and working. Do not forget to program three-party conferences on route 909. Confirm that the CFT light on the SW10 card is on.


9 Build UCD group for messaging system stations.

ASHUN

10 Program IP PAD card following the manual.

ACRD: TF=3, TCL=4, RLP=2, SMDR=0, LSG=12, PAD=?, TRKS=0/1, TC/EC=?, IP-PAD=19

ACTK (ACTKC) assign all IP PAD trunks to the route set above.

MBCTC make idle.

AFPC: FPC=0 FCCH=0 P_ROUTE=0 FCHN/FPCN=0

ALIDL

11 Make sure the G.711 codec with 40ms packets is used from any location group to the messaging system and from the messaging system to any location group.

■ Program ALOCL for all IP Phones, messaging system extensions and IP PADs. Use a different location group for the messaging system. In order to assign a separate location group for the messaging system IP address, you need to break down the subnet.

■ Program AIVCL for all combinations of location groups.

12 Enable Automatic Idle Return for the messaging system service feature class.

ASFC - SFI 136

ASYD 401 bits 0, 1, 2 and 3 (timer)

13 If the system is configured as an automated attendant, program Direct Input Termination (DIT) to the messaging system.

ACSI

14 Use ASYD and the following table to program the System Data.

NOTE

If the G.711 codec is used systemwide, skip this step.

NOTE

Make sure AMNO is not enabled for the route in which the trunk is located.

Sys Index Bit Value Description

1 28 b5 1 Enable MWI activation.

63 b0 1 Enable blind transfer for stations in service.

69 b0 1 No recall, execute call forwarding on no answer.

70 b0 1 Enable called number display when forwarding to attendant console.

77 b2 0 Disable MWI refresh

78 b0 1 Enable calling number display.

78 b1 1 Enable calling station status.

240 b4 ANPR Route 0 information sent to MCI.

246 b3 0

1

Set MCI to normal.

Set MCI to expanded.

370 b1 Delete ANPR Route 0 for MCI.

400 b2 1 Send calling number information (ANI) to MCI

2 6 b0 1 Enable MCI when terminating to a UCD group.

6 b7 1 Enable MCI service with UCD group.


15 Use ASYDL and the following table to program the System Data Local Data Memory.”

16 Set stations to call forward to the Pilot number of the messaging system hunt group. Do not forget the Forward Logout feature.

17 Save all changes with MEM_HDD.

LAN Interface and IOC Interface cannot be used concurrently for MCI.

The Socket Interface is used to transfer data to and from the message center connected to the LAN. After the link has been released, the client sends a link establishment request. The MCI messages that are transferred using the LAN Interface are in IPX format messages only.

When two MCs are connected to LAN Interface, the MC information is transmitted to both MCs. When transmitting the MC information to lower number port only, assign:

ASYDL System Data 1 Index 833 Bit 2 = 1 (single output).

18 Log an IP Phone in to one of the messaging system extensions and verify calling patterns to different locations.

A network analyzer can be used to confirm that G.711 codec is used to and from all location groups.

19 To log the test IP phone out of the phone system reinitialize the PHD card. Alternatively, use ADPM to reinitialize the internal PHD.

Next Step ...


7 b1 0 Disable MCI when terminating to attendant console.

Enable MCI when terminating to attendant console.


1 529 b0-1 00

01

10

Set parity check method to “Odd parity”

Set parity check method to “No parity”

Set parity check method to “Even parity”

641 b1 0

1

MCI IMX telephone number

MCI IMX station number

832 b0-7 0

1

Disable FPC

Enable FPC

833 b0 1 Enable LAN MCI

833 b1 1 Enable IPX format

833 b2 0

1

Enable dual output

Enable single output

834 b0 0

1

MC 0 for LAN is not mounted

MC 0 for LAN is mounted

834 b1 0

1

MC 1 for LAN is not mounted

MC 1 for LAN is mounted

848 b7 0 Enable MD5 password encryption

NOTE

Resetting the PHD (physical card or internal emulation) disconnects all extensions connected to that card.









The phone system parameters appear in the Integration Options field. Depending on the phone system select additional data might appear on the Switch Information page.

4 Click Save.



6 Click Save.















NOTE



■ NEC NEAX 2400 IPX/UNIVERGE SV7000 without MCI Integration

NEC NEAX 2400 IPX/UNIVERGE SV7000 WITHOUT MCI INTEGRATION 95


Overview........................................................................................................................................96Integration Requirements.............................................................................................................96

Connecting the Systems ...................................................................................................................97Programming the Phone System........................................................................................................98Configuring the Messaging System................................................................................................... 101

Overview Use this section of the Integration Guide with the Installation Guide to integrate the messaging system with the NEAX 2400 IPX or UNIVERGE SV7000 phone systems through a network connection. Both calls and call information are transmitted using the Internet protocol.









Integration RequirementsThe steps to set up the NEAX 2400 IPX or UNIVERGE SV7000 phone system integration require the following:

Phone System● Licenses for the total number of IP phones and messaging system ports.

● IP PAD card with VCTI for connections to TDM stations/trunks.

● Dterm IP phone.

Messaging System Server● The messaging system software is installed and ready for the integration.


● A Security Key File disc that licenses the integration and the appropriate number of messaging system ports.

NOTE

Every connection between an IP Phone and TDM stations/trunks requires one IP PAD channel.Phone system features that rely upon three-party conferencing such as executive override used for Live Record require an IP PAD channel for every IP party involved.

NOTE

Softkeys are not available with this integration.

UNIVERGE UM4730 INTEGRATION GUIDE NEC NEAX 2400 IPX/UNIVERGE SV7000 WITHOUT MCI INTEGRATION96


Use the following procedure to connect the phone system to the messaging system computer.


1 Connect the messaging system network card to the IP network. IP connectivity should be provided to the MP, the PHD card, if it exists, IP PAD, and IP stations.

If a firewall exists, configure the firewall to allow peer-to-peer connections.

2 Only the G.711 and G.729 codecs with 20ms or 40ms packets (payload) are supported.

3 If route names are used in ADRTL or ADRTN commands, you must adjust your DispParse.ini file.

Although the syntax of DispParse.ini is self explanatory, you might prefer to avoid using the ADRTL or ADRTN commands.

Next Step ...

◆ Program the phone system.See “Programming the Phone System” on page 98.



After connecting the systems, use the following procedures to set up the phone system. Programming phone system or extension options other than those supplied in the following procedures might adversely affect integration performance.

Use a Maintenance Administration Terminal (MAT) or similar tool to program the phone system as described in the following procedures.



ASYDL SYS 1 INDEX 556ASYDL SYS 1 INDEX 557ASYDL SYS 1 INDEX 558ASYDL SYS 1 INDEX 559

2 Program the MP address, netmask, and Default gateway.

ADTM

This is used as the DRS (Device Registration Server) and needs to be programmed when the messaging system is installed.

3 Program the PHD (physical card or internal emulation).

ALIDL

4 Program the messaging system ports in the PBX as normal IP stations.

AISTL (DtermIP, TEC 12, RSC, SFC)

5 Program user extensions following the phone system manual. IP extensions are programmed in AISTL while TDM extensions are programmed in ASDT

a Set up and test access codes for MWI (M-30) and executive override (E-1).

Use ASFC to:

◆ Program SFI 74 and SFI 82 for the SFC of the messaging system ports (M-30).

◆ Program SFI 3 and SFI 11 for the SFC of the messaging system ports (E-1).

◆ Program SFI 4 and SFI 11 for the other SF classes (E-1).

Use ANPD and ASPA to:

◆ Program Feature Access Codes to set (SIDA 54) and cancel (SIDA 55) the MWI (M-30).

WARNING


NOTES

Assign a different service feature class (SFC) for the messaging system ports as you need to set the MWI from the messaging system ports only.You do not need to program AMAC.Delete AKYD in case it is programmed or make sure you have default programming for the required keys. For example: line appearance, ring, or executive override on line key 4.


◆ Program Feature Access Code for Executive Override (SSC 4) (E-1).

6 Build UCD group for messaging system stations.

ASHU

7 Program IP PAD card following the phone system manual.

ACRD: TF=3, TCL=4, RLP=2, SMDR=0, LSG=12, PAD=?, TRKS=0/1, TC/EC=?, IP-PAD=19

ACTK (ACTKC) assign all IP PAD trunks to the route set above.

MBCTC make idle.

AFPC: FPC=0 FCCH=0 P_ROUTE=0 FCHN/FPCN=0

ALIDL

8 Make sure the G.711 codec with 40millisecond packets is used from any location group to the messaging system and from the messaging system to any location group.

■ Program ALOCL for all IP Phones, messaging system extensions and IP PADs.

Use a different location group for the messaging system. To assign a separate location group for the messaging system IP address, you need to break down the subnet.

■ Program AIVCL for all combinations of location groups

9 Use ASYDL and the following table to program general configuration options

10 Set Automatic Idle Return on for the messaging system service feature class.

ASFC - SFI 136

ASYD 401 bits 0, 1, 2 and 3 (timer)

NOTES

The Local Memory and Network Memory commands override the Data Memory commands. Check ANPDL, ASPAL, ANPDN, and ASPAN to confirm they do not conflict with the access code settings for MWI.

For the Executive Override feature to work on the PBX, you need to have three-party conferences enabled and working. Do not forget to program three-party conferences on route 909.

Default access codes are: *9 for MWI set, #9 for MWI reset, and *4 for Executive Override.

NOTE

If the G711 codec is used systemwide, skip this step.


1 819 b0 00 Enable G.711 codec systemwide.

672 b0-1 00

01

Disable 24 character display.

Enable 24 character display.

390 b1-3 004 Enable 2 lines for Caller ID and ANI display.

241 b1-6 2E Enable 16 character name display.

214 b5 01 Disable office codes display.

79 b5 01 Enable calling party name display.

78 b1 23 Enable service conditions display.

b3 23 Enable service conditions display.

b5 23 Enable service conditions display.

848 b7 0 Enable MD5 password encryption


11 If the messaging system is used as an automated attendant, program Direct Inward Termination (DIT).

ACSI

12 Set stations to call forward to the Pilot number of the messaging system hunt group. Do not forget the Forward Logout feature.

13 Save all changes using the MEM_HDD command.

14 Log an IP Phone in to one of the messaging system extensions and verify calling patterns to different locations.

A network analyzer may be used to confirm that G.711 is used to and from all location groups.

15 To log the test IP phone out of the phone system reinitialize the PHD card. Alternatively, use ADPM to reinitialize the internal PHD.

Next Step ...

◆ Configure the messaging system.See “Configuring the Messaging System” on page 101.

NOTE

Make sure AMNO is not set for the route where the trunk is located.

NOTE

Resetting the PHD (physical card or internal emulation) disconnects all extensions connected to that card.








The phone system parameters appear in the Integration Options field. Depending on the phone system select additional data might appear on the Switch Information page.

4 Click Save.



6 Click Save.















NOTE



■ NEC NEAX 2400 with Serial MCI Integration

NEC NEAX 2400 WITH SERIAL MCI INTEGRATION 103


Overview...................................................................................................................................... 104Integration Steps ...................................................................................................................... 104Integration Requirements........................................................................................................... 104

Connecting the Systems ................................................................................................................. 105System Connections .................................................................................................................. 105

Configuring the Trunk Boards .......................................................................................................... 106Programming the Phone System...................................................................................................... 107Configuring the Messaging System................................................................................................... 109

Overview Use this section of the Integration Guide with the Installation Guide to integrate the messaging

system with the NEC® NEAX® 2400 phone system using a Message Center Interface (MCI) link. The phone system messaging system ports connect to voice boards in the messaging system.


1 Review the system and equipment requirements.“Integration Requirements,” below.


3 Configure the trunk boards.See “Configuring the Trunk Boards” on page 106

4 Set up the phone system for the integration.See “Programming the Phone System” on page 107.





Integration RequirementsThe NEC NEAX 2400 phone system integration through a Message Center Interface (MCI) link requires the following:

Phone System● One of the following NEC phone systems:

● MCI feature II installed on the phone system as described in the NEC document ETI No. 121A (October 1998).

● One IOC serial port available for the MCI serial link with a PH-68 two-port cable and a RS-232C CA-1 cable installed.

● One or more 2500 station ports (analog) set up for each messaging system port.

● The appropriate phone lines for connecting the phone system messaging system ports to the messaging system voice boards.

● One RS-232 serial cable (included with the integration package) for connecting the phone system MCI serial link to the messaging system.




Phone System Software Version

IMX All software versions

SIM/IMG 5200 or later

MMG/UMG 4200 or later

UNIVERGE UM4730 INTEGRATION GUIDE NEC NEAX 2400 WITH SERIAL MCI INTEGRATION104


After installing all of the required hardware on the messaging system, use the following procedure to connect the systems.

System Connections


1 Connect one end of the RS-232 serial cable to the Cable 1 CA RS-232 cable on the phone system.


3 Connect the analog line from the punchdown block to the appropriate connectors on each analog voice board in the messaging system computer.

Repeat step 3 for each additional analog line.

Next step…

◆ Configure the trunk boards.See “Configuring the Trunk Boards” on page 106.


Configuring the Trunk Boards

After connecting the systems, use the following procedure to confirm the trunk board firmware version and to set the trunk board DIP switches.

To confirm the trunk board firmware

1 Remove the 24DTR/DLI trunk board from the phone system.

2 Locate a removable, integrated circuit (PROM) with a white label.

This PROM contains the trunk board program, or firmware. The relative position of the PROM might vary, but there is only one PROM with a white label on the trunk board.

3 Confirm that the firmware version printed on the label is SP-3298 3A 001 or later.

If the version is incorrect, update the firmware by replacing the PROM or the trunk board.

Repeat this procedure for each trunk board.

To set the trunk board switches

❚ Set the DIP switches for the 24DTR/DLI trunk board as shown below:

Next step…


CAUTION




Use the following procedure to program the phone system.

To program the phone system

Assign all of the messaging system ports to a UCD hunt group.

If the number of messaging system ports exceeds the number of supported ports for a UCD hunt group, specify additional UCD hunt groups, then link them together using the AUOG command.

1 Use the AIOC command and the following table to program the IOC serial port for the serial MCI integration.

2 Use the AUCD command to program the phone system to send UCD call information to the MCI.

3 Assign a value of 0 to the MCI Data Transfer field for the appropriate tenant and UCD pilot station numbers.

4 If you use a remote maintenance modem, program the modem line for data security. Otherwise, skip this step.

5 Use the ASYD command and the following programming table to program the System Data.

Each bit is part of a hexadecimal number displayed in the ASYD Data field. Convert the hexadecimal number to binary to determine the individual settings.

NOTE

Software versions 7200 or later support up to 100 ports in a UCD hunt group while software versions earlier than 7200 support up to 20 ports in a UCD hunt group.

Field Value Description

Terminal 1 MCI

Speed 6 9600 baud

Parity bit 0 No parity

Stop bit 1 1 stop bit

Character bit 0 8 data bits


1 17 b4 1 Blind transfer to attendant console.

28 b0-4 0 Guard timer not required.

b5 1 MWI controlled by MCI.

29 b1-7 0/1 I/O port for MCI. Port 1=b1, Port 2=b2, and so on.

34 b1-4 0 Set output to no parity and 1 stop bit.

60 b3 0 UCD queuing required.

63 b0 1 Blind transfer for stations in service.

69 b0 1 No recall, execute call forwarding to attendant console.

70 b0 1 No recall, execute call forwarding on no answer.

77 b2 0 MWI refresh required.

78 b0 1 Calling number display enabled.

b1 1 Calling station status display enabled.

238 b0-7 00 Lamp flash rate.

246 b3 0 MCI expansion set to normal.

400 b3 1 Calling number information sent to MCI.


6 Use the ASYDL command and the following programming table to program the ASYDL settings.

Each bit is part of a hexadecimal number displayed in the ASYDL Data field. Convert the hexadecimal number to binary to determine the individual settings.

7 If the phone system is part of a CCIS network, assign the remote point code (RPC) for each remote node using the ARPC command.

Next step…


2 6 b0 1 MCI in service when terminating to a UCD group.

7 b1 0 MCI out of service when terminating to attendant console.


1 641b 1 0/1 0/1:MCI IMX station number/phone number.

832 b0-7 00-FD Assign the FPC of the node connected to MC.

833 b0 0 IOC serial interface enabled for MCI.

833 b1 0 0/1: ICS/IMX format.

848 b7 0 Enable MDS password encryption.




After setting up the phone system, use the following procedures to configure the messaging system. For more information on messaging system features refer to the System Administrator Help.





4 In the Integration Options field, confirm that the integration string includes the following data:

S=MCI CR,,, DT

The switch parameters are displayed in the Integration Options field. Any changes made on this page requires stopping and restarting the messaging system.

5 Click Save.



7 Click Save.
















■ UNIVERGE SV7000 with LAN MCI Integration

UNIVERGE SV7000 WITH LAN MCI INTEGRATION 111


Overview...................................................................................................................................... 112Integration Steps ...................................................................................................................... 112Integration Requirements........................................................................................................... 112Integration Features for SV7000 ................................................................................................. 113

Programming the Phone System...................................................................................................... 114Configuring the Messaging System................................................................................................... 117

Selecting Optional Conversations................................................................................................. 117Changing Integration Options ..................................................................................................... 117Redirecting Extension Numbers ................................................................................................... 117

Overview Use this section of the Integration Guide with the Installation Guide to integrate the messaging system with the UNIVERGE SV 7000.


1 Review the system and equipment requirements.See “Integration Requirements,” below.

2 Set up the phone system for the integration.See “Programming the Phone System” on page 114

3 Configure the messaging system for the integration.See “Configuring the Messaging System” on page 117

4 Test the phone extensions.See “Testing an Integration” on page 175.



Integration RequirementsThe steps to configure the UNIVERGE SV7000 Message Center Interface (MCI) integration with a LAN interface requires the following:

Phone System● UNIVERGE SV7000 (model T10 or T20) phone system with LAN MCI.

● A network connection between the messaging system server and the phone system.

● One or more of the following station ports, of the same type, set up as messaging system ports:


● A network connection between the messaging system server and the phone system.

● An available serial port and cable for progaming the switch.

● One or more of the following voice boards installed:


Port Type Description

Analog One analog station port for each messaging system port.

T1 One digital line interface card for each group of 24 messaging system ports.

Digital One digital station port for each messaging system port.

IP VPS One IP VPS port for each messaging system port.

IP Terminal One IP Terminal port for each messaging system port.

Line type Voice board

Analog Dialogic D4JCT, D4PCIUF, D41D, D120JCT, D41JCTLS (3.3v), D120JCTLSU (3.3v). These can be VFX as well as Voice.

T1 Dialogic D240PCIt1, D240JCT-T1R2

Digital Dialogic D42NE2, D82JCTU T1R2

NOTE

If IP VPS or IP Terminal ports are used no voice boards are required.

UNIVERGE UM4730 INTEGRATION GUIDE UNIVERGE SV7000 WITH LAN MCI INTEGRATION112

Integration Features for SV7000● Message waiting indication (MWI). When a message is waiting for a subscriber, the

messaging system notifies the phone system to activate the message waiting indicator on the subscriber’s extension (if it is equipped with one) or to activate a stutter dial tone.

NOTE

The MWI over CCIS through LAN/MCI integration only works if a closed numbering plan is used.



This section describes how to program the NEC UNIVERGE SV7000 using the Windows-MAT application. For additional information, please refer to the SV7000 documentation or online-help for Windows-MAT.

To program the phone system

1 Use the ASYD (System Data) command to program the SV7000 configuration. Set/Confirm is required.

SYS=3 INDEX=13 DATA=1B.

2 Use the AISTL (IP Extension Data (LDM)) command to set the extension data for SV7000.

Set Kind to SIP-VPS, and TEC = 26.

SIP-VPS is a unique number to identify each phone system. The allowable range is 0-255. This value must be associated with the IP driver setting tool.

SIP-VPS Ch is the channel number (range 0-23).

We recommend that you set sequential numbers for IPSTN and SIP-VPS Ch. For example,

3 Use the ASHC (Circular Data of Extension) command to create the circular group of extension numbers.

For example:

set SECRETARY STN to 4000, and enter EDIT STN to 4001, 4002, and 4003

When extension 4000 is busy, the call is transferred to 4001. If 4001 is also busy; the call is transferred to 4002, and so on.

4 Use the ASFC (Class of Service Restriction) command to set the permission (or Restriction) of various services.

SYS INDEX DATA Bit Description

1 238 01 0 Message Waiting Lamp Color 0:Red 1:Green

1 238 01 1 Message Waiting Type 0:Blink 1:Always On

1 435 00 5 Message Waiting Indication 0:Enable 1:Disable

3 13 1B 0 to 7 Enable IP-VMS/UMS

IPSTN=4000 SIP-VPS NO=0 CH=0 the 1st Line Channel (Gr.#1 Ch.#1)

IPSTN=4001 SIP-VPS NO=0 CH=1 the 2nd Line Channel (Gr.#1 Ch.#2)

IPSTN=4002 SIP-VPS NO=0 CH=2 the 3rd Line Channel (Gr.#1 Ch.#3)

IPSTN=4003 SIP-VPS NO=0 CH=3 the 4th Line Channel (Gr.#1 Ch.#4)

IPSTN=4004 SIP-VPS NO=0 CH=4 the 5th Line Channel (Gr.#2 Ch.#1)

IPSTN=4023 SIP-VPS NO=0 CH=23 the 24th Line Channel (Gr.#6 Ch#4)

Tenant No. (TN)

IP Extension (IPSTN)

Kind of Ext

Class (TEC)

Route Class (RSC)

Service Class (SFC)

LENS SIP-VPS NO

SIP-VPS CH

1 SIP-VPS 26

1 SIP-VPS 26

1 SIP-VPS 26

1 SIP-VPS 26

Tenant No. (TN)

Extension Number (STN)

SECRETARY STN

EDIT STN

EDIT STN

EDIT STN

1


DAY/NIGHT = D Tenant No.(TN) = 1

5 Use the AVPS (VPS Connection Data) command for SV7000 phone systems.

When a user accesses the phone system using soft keys or function keys, the phone extension is the phone system set using the VPS-STN setting.

6 Use the AKYD (Function-Key Data of Dterm, NEterm) command to set the function key data for the phone.

The following is an example. It is not necessary to set all of the following data. Select and customize the functions needed:

For example,

Kind of Service SFI

Restriction Class(SFC)

0 1 2

IP-UMS Service 118

Start live recording automatically. 119

Special dial tone for message waiting. 142

Tenant No. (TN)

Extension No. (STN)

Extension No. (VPS STN)

1

1

Tenant No. (TN)

Ext No (STN)

PRI PLTN PLSTN

S MWD LNPRE

SPK ANS ORG TP

1 3000 0 2 0 0 0 0

Key Num (KYN)

Kind of Service (KYI)

Func Key Num (FKY)

Kind of Line (KD)

Tenant No of Multi-LIne (TN)

Ext No of Multi-Line (STN)

Ringing Info of Multi-Line (RG)

Kind of intercom (ICM)

Group ID (G-ID)

1 1 66

2 1 67

3 1 68

4 1 69

5 1 70

6 1 71

7

8 1 73

:

15

16 2 0 1 3000 7

NOTE

You can use the some of above functions without the settings.

Function Method Pause L.R.

Finish L.R.

Re-Recording Cancel L.R.

Urgent Mail

5# 1# 2# 0# 9#


7 Use the AIVSL (to configure VS-32) command with VS-32.

If you want to use the SV7000 live-record feature, you must use this command to create 3-CONF channels of VS-32.

The following is an example of 2 set with 3-CONF channels:

8 use the MBTK (Trunk Make Busy) command after making the channel of VS-32, to enable it for use.

For example:

Next Step ...

◆ Configure the message system.See “Configuring the Messaging System” on page 117.

Channel No.of VS-32 (VS-CH)

Kind of Channel (KIND)

Route Number (RT)

Trunk Number (TK)

LENS Others

0 3-CONF 909 1 PAD value, etc.

3 3-CONF 909 2 PAD value, etc.

Route Number (RT)

Trunk Number (TK)

Make Busy (MB)

909 1 0

909 2 0



Use the procedures in this section to configure the messaging system for the integration.

Selecting Optional ConversationsUse the following procedure to select optional conversations.

To select an optional conversation


2 In the Navigation pane, click System > Configuration > System Settings.

3 Select the appropriate conversation for your messaging system. Default is the default conversation.

4 Click Save.

Changing Integration OptionsSeveral system options, such as Easy Message Access (EMA) and Identified Subscriber Messaging (ISM), are enabled by default, use the following procedure to disable these options or to enable ISM secured mode.

To enable or disable Integration Options



3 To disable easy message access:

Look in the Integrations Options field for the text: ema=. If you find it, set the value to 0 so that ema=0.

If you do not find it, at the end of the integration string add a blank space followed by the text: ema=0.

4 To disable identified subscriber messaging (ISM):

Look in the Integrations Options field for the text: ism=. If you find it, set the value to 0 so that ism=0.

If you do not find it, at the end of the integration string add a blank space followed by the text: ism=0.

5 To enable identified subscriber messaging (ISM) in the secured mode:

Look in the Integrations Options field for the text: ism=. If you find it, set the value to 2 so that ism=2.

If you do not find it, at the end of the integration string add a blank space followed by the text: ism=2.

6 Click Save.

Redirecting Extension NumbersThe messaging system can redirect calling and called numbers on a systemwide basis. Calling numbers are extension numbers that originate a call. Called numbers are extension numbers where a call is received.

When a live record conversation is initiated from a redirected extension, the system sends the recorded conversation to the mailbox of the called extension, rather than the redirected extension.

Optional Conversations

Default

Centigram TUI Emulation

Octel Aria TUI Emulation


By redirecting extensions users can:

● Retrieve mail messages from multiple extensions, such as work phones and cell phones.

● Forward calls to a mailbox when extensions are busy or unanswered.

● Send, forward, and respond to voice messages from any extension. For example, when using the Hospitality feature, a voice message can be forwarded from any extension in the hotel room, the person receiving the forwarded call hears the room number before they hear the message.

To redirect extension numbers


2 In the Navigation pane, click System > Extension Remapping.

Any existing extension remaps appear on the Extension Remapping page.

3 Click Add to add a new extension remap.

The Add Extension Map dialog box appears.

a Specify one of the following:

◆ Calling numbers only. Remapping applies to extensions that originate the call.

◆ Called numbers only. Remapping applies to extensions that receive the call.

◆ Both calling and called numbers. Remapping applies to both calling and called extensions.

b Type the From number and To number. The symbols in the following table are valid wild cards.

c Select + (plus) or - (minus) from the Offset for question mark (?) wildcard list.

The system adds (+) or subtracts (-) the offset from the designated digits in the extension number. For example: With an offset of +3 and the wildcard 6?00; extension 6100 maps to 6400.

d Type the wildcard offset value.

e Select one of the following to assign the mapping rule a priority:

◆ Top of the list. This puts the mapping rule at the top of the list.

◆ Specify. Select and specify the position of the mapping rule in the list.

f Specify the mapping rule status:

◆ Active. Saves and enables the mapping rule.

◆ Inactive. Saves the mapping rule and leaves it disabled.

g Click Add to add an additional extension remap or click Cancel to close the Add Extension Map dialog box without making any changes.

4 Repeat step 3 to add any other extension remapping rules.

5 Restart the messaging system.

Wild cards

Type in as Represents

? One-to-one correspondence on both sides of the equal sign. Specify offset

One digit wildcard

* One-to-one correspondence on both sides of the equal sign.

Wildcard of one or more digits

CAUTION

The number of wildcards (?) used and their placement must be the same in both the From number and the To number fields.

For example, 5?00 to 6??0; 5??0 to 6?00 are invalid uses of the wildcard. However, 5?00 to 6?00 or 5??0 to 6??0 are valid.


NEC UNIVERGE SV8300 WITH IP PROTIMS INTEGRATION 121




■ NEC UNIVERGE SV8300 with IP Protims Integration

Overview Use this section of the Integration Guide with the Installation Guide.


1 Review the system and equipment requirementsVerify that all equipment, phone system, and messaging system server requirements have been met. See “Integration Requirements,” below.

2 Program the phone system.See “Programming the Phone System” on page 123.


Integration RequirementsThe steps to set up the NEC SV8300 IP Protims integration require the following:

Equipment


Phone System ● UNIVERGE SV8300 with software release A1 or C1 and ready for the integration as

described in the phone system documentation.

● Password encryption type for IP extensions is MD5, see command CM08 YY=517 on 0.

Messaging System Server● If the phone system uses G729 codec, the Sipro Lab G729A codec driver must be installed

on the messaging system server. The installation file for this driver is named sl_g729a_setup.exe and can be found in the Voice Mail\Utilities folder on the Installation disc.

● A system key that enables the integration and the appropriate number of voice messaging ports.

NOTE

Encoding must be enabled (CM08 is set as 1).

UNIVERGE UM4730 INTEGRATION GUIDE NEC UNIVERGE SV8300 WITH IP PROTIMS INTEGRATION122


If programming options other than those supplied in the following procedures are used, the integration’s performance can be affected.


1 Make sure that the SV8300 phone system has licenses for using IP extensions using command F88 and the information in the following table:

The following example can be used as a guideline for setting up IP or passwords:

CM 08>516>x sets whether or not you want to use a password for IP station login (usually same as extension)

CM 0B1xx>00>ip address of VOIPDB (where xx is the unit number)

CM 0B1xx>01>voipdb subnet (where xx is the unit number)

CM 0B1xx>02>voipdb gateway (where xx is the unit number)

CM 0B2xx>00>IPLA addresses (where xx is the unit number)

CM1290>ip_ext>CCC clears the MAC address of phones so a different phone can log on to that extension.

2 Configure the voice messaging ports as IP Terminal extensions, the default IP extensions type.

The following example reflects programming eight ports, 3900-3907, and the VM pilot, 3999. Use this example as guide for programming the PBX:

a CM 10-01>F3900-F3907 Assigns station numbers (VM Ports)

b CM 11>0000>3999 Assigns the VM pilot as a virtual number

c CM E50>3999>0 Makes Busy the VM Pilot number

d CM 1324>Sta#(3900-3907)>0 DTMF passing SIP to IP DTerm

e CM 1359>Sta#(3900-3907)>0 DTMF passing SIP to IP DTerm

f CM 1303>(all stations - not the voicemail ports)>0 Allows MWI

g CM 08>517>0 MD5 encryption

h Build UCD Group:

CM 170>3999>3900 Create a loop pointing Pilot to first Port

CM 170>3900>3901 Point each port to the next.

CM 170>3901>3902CM 170>3902>3903

CM 170>3903>3904CM 170>3904>3905

CM 170>3905>3906CM 170>3906>3907

CM 170>3907>3999 Finally point last port back to pilot.

NOTE

The following procedures are written with the assumption that you will use the SV8300 PCPro Software to program the phone system.

For Use

VoIP Channels F88>010

IP Trunk F88>011

IP Ports F88>012

SIP TRK Channels (if used) F88>017

STD SIP Phone (if used) F88>024

SIP Trunk (if used) F87>173

NOTE

The following information is only an example of how to congifure a system. The settings for your system might be different.


i CM 171>3999>1 Assigns Pilot number as a UCD Pilot

j Assign Pilot and ports to a UCD group number:

CM 172>3999>00

CM 172>3900>00

CM 172>3901>00

CM 172>3902>00

CM 172>3903>00

CM 172>3904>00

CM 172>3905>00

CM 172>3906>00

CM 172>3907>00

k CM 5115>01>3999 Assigns transfer destination for quick transfer

l CM 5110>01>3999 Assigns transfer destination when station is set to DND

m CM 5118>01>3999

n CM 200>*9>A040 Allows MWI lamp ON (example of code)

o CM 200>#9>A041 Allows MWI lamp OFF (example of code)

p CM 200>*4>A006 Allows executive override for Live Record - If needed (example of code)

q CM 9000>xxxx,01>xxxx Sets the prime line on button 1, where xxxx is the IP extension numbers (3900-3907 in this example)

CM 9000>xxxx,94>F1016 Sets the speaker key mapped to button 94, where xxxx is the extension numbers (3900-3907 in this example)

CM 9000>xxxx,96>F1004 Sets the transfer key mapped to button 96, where xxxx is the extension numbers (3900-3907 in this example)

Clear all buttons except for the prime (1),speaker (94),and transfer (96) on the extensions

3 Make sure that the following service features are enabled in the phone system:

■ Call hold

■ Assignment of no answer timer for blind transfer to station or blind transfer attendant

■ Blind transfer

4 Set the same location ID for all voice messaging ports and set either or both of the codecs G711, U-Law or A-Law, and G729A with any payload your system may need (10, 20, 30, or 40). The codec list you use for IP phones or IP voice messaging ports is based on the location group assigned for the ports in CM 1239. There are 4 programmable codec lists for CM 6700.

For example: Station 3000 is set to location group 00 with CM 1239>3000>00 and IP phone 2500 is set to location group 01 with CM 1239>2500>01. CM 6700 sets the codec list used when calling from location 00 to 01, and vice versa. So CM 6700>0001>0 sets that calls from the voicemail to an IP phone, or from an IP phone to voicemail should use codec list 0. In codec list 0 the codec and payload size used are set by CM 42>100-103 and 110-113. So CM 42>100 is the first codec choice for group 0, CM 42>101 is the second codec choice for group 0, and so on. CM 42>110 is the first payload size choice for group 0, CM 42>111 is the second choice of payload size, and so on.

Use the following Priority Codec List example:

CM 42>100>priority codec 1 for codec list 0 (G.711u, G.711a, G.722 (wide band), G.723.1, G.729a)





CM 42>110>priority payload 1 for codec list 0 (10ms, 20ms, 30ms, 40ms)




Next Step ...




After ensuring that the messaging system server is ready for the integration by completing all appropriate tasks in the Installation Guide, perform the following procedure to confirm that the integration is enabled.



2 In the Navigation pane, click System > Switch > Switch Information. Select the phone system manufacturer and model from the Switch list.

3 The switch parameters appear in the Integration options field. Depending on the phone system select additional data might appear on the Switch Information page.


5 Click Save.

6 In the Navigation pane, click System > Switch > MWI. Enter the MWI analog codes that the SV8300 phone system uses for turning the phones lamps on and off.

7 Click Save.




9 Click Save.






NOTE



NEC UNIVERGE SV8500 WITH DIRECT DIGITAL INTEGRATION 127



Integration Description................................................................................................................... 129Configuring the Messaging System................................................................................................... 130Programming the Phone System...................................................................................................... 131

■ NEC UNIVERGE SV8500 with Direct Digital Integration

Overview Use this section of the Integration Guide with the Installation Guide to integrate the phone system with the messaging system.


1 Review the system and equipment requirements.Verify that all phone system and messaging system server requirements have been met. See “Integration Requirements,” below.



Integration RequirementsThe steps to set up the NEC UNIVERGE USV8500 direct digital integration require the following:

Phone System● NEC UNIVERGE SV8500, revision S01 or later, installed and ready for the integration as

described in the phone system documentation.

● One or more of the following digital line cards set up as voice messaging ports connected to the voice boards in the messaging system server:

Messaging System Server● The Dialogic digital voice boards installed; see the Installation Guide for installation

details.

● UM4730 installed and ready for the integration as described in the Installation Guide.


Card name Description

16ELCH (with SP-3125) Digital line card, 16 ports

16ELCJ Digital line card, 16 ports

16ELCJ-B Digital line card, 16 ports

16ELCJB-A Digital line card, 16 ports

16ELCNA Digital line card, 16 ports

NOTE

For the latest information on supported voice boards for UM4730, contact a sale representative.

UNIVERGE UM4730 INTEGRATION GUIDE NEC UNIVERGE SV8500 WITH DIRECT DIGITAL INTEGRATION128

Integration Description

The SV8500 direct digital integration uses digital lines to connect the phone system and messaging system server. The phone system digital voice messaging ports connect to the voice boards in the messaging system server. The following illustration shows the required connections.

The phone system parses the phone’s display for the following:

● The called party’s extension

● The reason for the forward (the extension is busy, does not answer, or is set to forward all calls)

● The calling party’s extension (for internal calls)

UM4730 uses this information to answer the call appropriately. For example, a call forwarded to UM4730 is answered with the subscriber’s personal greeting. If the phone system routes the call to UM4730 without this information, UM4730 answers with the opening greeting.

UNIVERGE UM4730 Server

SV8500Digital lines









5 Click Save.



7 Click Save.






NOTE




If programming options other than those described in the following procedures are used, the integration’s performance can be affected.

To program the digital voice messaging ports in the phone system

1 Specify a Service Feature Restriction Class (SFC) for the voice messaging ports by using the ASFC command. It is recommended that all of the voice messaging ports be placed in a single SFC not used for any other purpose. The following Service Feature Indexes (SFIs) are needed in the SFC:

2 Assign a value of 26 to the Telephone Equipment Class (TEC) for each voice messaging port by using the ASDT command. Use the SFC created for the voice messaging ports in step 1.

3 Assign all of the voice messaging ports to a Uniform Call Distribution (UCD) group.

If the number of voice messaging system ports exceeds the number of supported ports in a UCD group, specify additional UCD groups, then link them together using the AUOG command.

4 Program each phone to forward calls to the UCD pilot number assigned to the voice messaging ports, based on the UM4730 call transfer type:

Release to switch transfer. Program the phone to forward calls to the UCD pilot number when:

■ The extension is busy; or,

■ The call is not answered.

Supervised transfer. Program the phone to forward calls to the UCD pilot number only when the call is not answered. Confirm that call forwarding is disabled when the extension is busy.

NOTE

The following procedures are written on the assumption that you will use the SV8500 PCPro software to program the phone system.

SFI Service feature

10 Call hold


104 Blind transfer

CAUTION

Do not use a phantom single line extension for the UCD pilot number.


5 Use the programming system data table to program the ASYD settings. Each bit is part of a hexadecimal number displayed in the ASYD settings. Convert the hexadecimal number to binary to determine the individual settings. For more information, refer to the SV8500 Office Data Specification.

To program the Dterm phones that use Live Record

For each Dterm phone that uses the UNIVERGE UM4730 Live Record feature, perform the following steps:

1 Assign an SFI of 118 by using the ASFC command.

2 Assign the extension to the UCD pilot number of the voice messaging ports by using the AVPS command. Enter the UCD pilot number for the VPS STN.

3 Designate the following function key assignments by using the AKYD command:

Programming system data

System Index Bit Value Description

1 17 b4 1 Blind transfer to attendant console

28 b0–4 0 Guard timer not required

60 b3 0 UCD queuing required

63 b0 1 Blind transfer for stations in service

69 b0 1 No recall, execute call forwarding on no answer

70 b0 1 Called number display, when forwarding to attendant console

77 b2 0 MWI refresh required

78 b0 1 Calling number display enabled

b1 1 Calling station status display enabled

238 b0–7 0 Lamp flash rate

Function key number Function

66 Record

67 Re-record

68 Pause

69 End






■ NEC UNIVERGE SV8500 with IP Protims Integration

Overview Use this section of the Integration Guide with the Installation Guide to integrate the phone system and messaging system.

The SV8500 IP Protims integration uses a network connection to connect messaging system server with the phone system. Each voice messaging port emulates an IP-VPS extension. The communication between the parties is facilitated by a series of Voice over IP (VOIP) protocols, such as DRS, Protims, RTP, H245, Voice control, used for call signaling and voice streaming, some of them being NEC proprietary protocols.


1 Review the system and equipment requirements.Verify that all equipment, phone system and messaging system server requirements have been met. See “Integration Requirements,” below.


3 Configure the message system.See “Configuring the Messaging System” on page 136.

Integration RequirementsThe steps to set up the NEC SV8500 IP Protims integration require the following:

Equipment


Phone System● UNIVERGE SV8500 installed and ready for the integration as described in the phone

system documentation.

● Password encryption type for IP extensions is MD5, see command ASYDL, index 848, b7=0.

● Fully functional IP PAD cards with VCTI sub-boards.

Messaging System Server● If the G729 codec is used, the Sipro Lab G729 codec driver must be installed in the voice

mail server. The installation file for this driver is named sl_g729a_setup.exe and can be found in the Voice Mail\Utilities folder on the Installation disc.


NOTE

IP PAD cards provide interface function between IP telephony, terminals or other devices on LAN, and non-IP telephony, conventional networks such as PSTN, ISDN, and private networks. If the telephony network is 100% IP, the IP PAD cards are not mandatory.



If programming options other than those described in the following procedures are used, the integration’s performance might be affected.


1 Make sure that the SV8500 phone system has licenses for using IP extensions by using the DPTR command.

2 Configure the voice messaging ports as IP-VPS extensions by using the AISTL command to set KIND = IP VPS and TEC = 26.

Assign the ports successive VPS channels, starting with IP VPS CH = 0.

3 Write down the VPS ID value of the voice messaging ports, for use during the messaging system installation. Enter the value when the messaging system installation wizard asks for this value.

4 Write down the MWI analog codes that the SV8500 phone system uses for turning the phones lamps on and off. These codes are needed when configuring the messaging system to work with the integration.

5 Specify a Service Feature Restriction Class (SFC) for the voice messaging ports by using the ASFC command. It is recommended that all of the voice messaging ports be placed in their own SFC. The following Service Feature Indexes (SFIs) are needed in the SFC:

6 Assign all of the voice messaging ports to a Uniform Call Distribution (UCD) group using the ASHU command.

7 Set the same location ID for all voice messaging ports and set either or both of the codecs G711, U-Law or A-Law, and G729A with payload size equal to 40 milliseconds for that location ID using the commands ALOCL and AIVCL.

Next Step ...


NOTE

The following procedures are written on the assumption that you will use the SV8500 PCPro Software to program the phone system.

CAUTION

All voice messaging ports must have the same value assigned for VPS ID.

NOTE

The SV8500 phone system may not have any settings made to use codes for MWI analog operations. If this is the case, use the ANPD and ASPA commands to set “SRV=SSCA” and “SIDA=54 / 55.”

SFI Service feature

10 Call hold


104 Blind transfer

NOTE

To associate the voice messaging ports with a specific location, add the IP address of the messaging system server to that location.









5 Click Save.


7 Click Save.


Assign an Extension and Password for each port displayed in the table.


9 Click Save.






NOTE



■ Nortel Meridian-1 with D42JCTU or D82JCTU Voice Boards Integration

NORTEL MERIDIAN-1 WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION 137





Overview The Nortel Meridian-1 with a Dialogic® D42JCTU or D82JCTU voice board integration uses digital lines to connect the phone system and the messaging system server. The phone system digital messaging system ports connect to voice boards in the messaging system server. The D42JCTU voice board emulates up to four digital phones. The D82JCTU voice board emulates up to eight digital phones.


1 Review the system and equipment requirements. “Integration Requirements,” below.

2 Connect the systems. See “System Connections” on page 139.






Integration RequirementsThe Nortel Meridian-1 with D42JCTU or D82JCTU integration requires the following:

Phone System● A Nortel Meridian-1, generic release 15 or later phone system.

● Phone system packages required:

● Package 19. Digit Display software (DDSP)

● Package 46. Message Waiting Center (MWC)

● One Digital Network Interface Circuit (DNIC) for each messaging system port, that emulates a digital phone, installed and set up as a messaging system port.


● A telco connection cable for each voice board.

● A type 66 interconnect block for each 18-pair PBX station interface cable.




● The messaging system server software installed and ready for the integration.


UNIVERGE UM4730 INTEGRATION GUIDE NORTEL MERIDIAN-1 WITH D42JCTU OR D82JCTU VOICE BOARDS INTE-138


After installing all of the required hardware in the messaging system server, use the following procedure to connect the phone system and messaging system.

Refer to the Installation Guide to install required messaging system hardware such as voice boards.

System Connections



2 Connect the messaging system server to the interconnect block:

■ If the PBX cable cannot be directly connected to the interconnect block, use a telco cable:


Two-wire Pinouts


Type 66 Block Pair

Pin Number


1 2 272


Tip 1 Ring 1

2 4 29 4


Tip 2 Ring 2

3 6 31 6

red-blue blue-red

Tip 3 Ring 3

4 8 33 8

red-green green-red

Tip 4 Ring 4

5 10 35 10

red-slate slate-red

Tip 5 Ring 5

6 12 37 12


Tip 6 Ring 6

7 14 39 14


Tip 7 Ring 7

8 16 41 16


Tip 8 Ring 8





Next Step ...

◆ Program the phone system. See “Programming the Phone System” on page 141.



After connecting the systems, use the following procedures to set up the phone system for the integration. Integration includes configuring an extension numbering plan, confirming that the required software and utilities are installed, setting up hunt groups, identifying incoming calls, and configuring phones. Refer to the phone system documentation for details.

Programming other phone systems or extension options might create a conflict with the messaging system functions.

To set up an extension numbering plan

Before setting up the messaging system extensions, decide on an extension numbering plan that meets the organization’s requirements.

To confirm that the DDSP and MWC packages are installed

1 On the phone system, click the LD22 screen.

2 Set the REQ prompt to PRT.

3 Set the TYPE prompt to PKG.

4 Confirm that both of the following are displayed:

■ DDSP (for Package 19, Digit Display Software)

■ MWC (for Package 46, Message Waiting Center)


1 On the phone system, find the extensions assigned to the messaging system (circuit board types QPC578 or NT8D02).

Only the prompts needed for this integration appear on this screen. For details on other prompt settings, refer to the phone system documentation.

2 On the phone system console click a LD11 screen.

3 Set up a terminal number (the TN prompt) for the first messaging system extension. The following example uses TN 0 0 6 2.

4 Set Key 00 to SCR (ring call appearance key).

NOTE

On the LD16 screen for each extension, confirm that the CPDC prompt is set to No, which is the default setting. Otherwise, the dialing ports might be disabled.

NOTE

The phone system does not recognize extension numbers that start with zero.


5 Set Keys 3 - 5 as shown:

6 Set the HUNT prompt to the next extension the phone system should hunt when this messaging system extension is busy. The following example uses extension 501.


When the hunt group is set up as described, all of the subscriber extensions are forwarded to the first messaging system extension.

If the first extension is busy, the system hunts for the next available extension. The system hunts in sequence up to the last extension, then starts over until a messaging system extension becomes available.

Repeat this procedure for each messaging system extension.

To set the call party name display

1 On the phone system console click the LD95 screen.

2 Accept the default settings, except for the HUNT prompt. The HUNT prompt should be changed to CFNA.

3 Verify that the CFNA prompt is set to CFNA. The settings should be as follows:

NOTE

Some releases of the Meridian-1 phone system require setting the CLS prompt to DDS instead of ADD.

Prompt Setting Prompt Setting

REQ PRT DES NO

TYPE CPND RESN YES

CUST 0 CFWD FWD

TYPE CPND CFNA CFNA

CUST 0 HUNT CFNA

CNFG ALON PKUP PICK

MXLN 27 XFER T

STAL YES AAA A

DFLN 27 NITC NI


To program a 2008 phone

1 On the phone system, click the LD11 screen to set up the digital 2008 phone.

2 Set the REQ, TYPE and CLS prompts as shown in the screen sample.

3 Set the other prompts as applicable.

LD11 Settings for Digital 2008 Phones

To program SL-1 phones

1 On the phone system, click the LD11 screen to set up the SL-1 phones.

● Phones with audible message waiting (AMW). Set the CLS prompt to LPD to enable a stutter dial tone.

● Phones with LEDs or neon lamps. Set the CLS prompt to LPA to enable the activation of visual message waiting indicators.

2 Set the REG, TYPE, CLS, and KEY prompts as shown in the following image:

NOTE

If the system is equipped with audible message waiting (AMW), set the CLS prompt to LPD to enable a stutter dial tone. If the phones have LEDs or neon lamps, set the CLS prompt to LPA to allow the activation of visual message waiting indicators.

NOTE

Only the prompts necessary for the integration appear on this screen. Refer to the phone system documentation for other prompt settings.

NOTE

Only the prompts needed for this integration appear on this screen. Refer to the phone system documentation for additional prompt settings.



To program analog 2500 type phones

1 On the phone system, select the LD10 screen to set up the analog 2500 type phone.

2 Set the REQ, TYPE, CLS, and FTR prompts as shown in the following image:


The other prompts shown in the sample are examples. Different settings might be required, depending on the site. For details on the other prompt settings, refer to the phone system documentation

Next Step ...


NOTE

Analog phones require special interface boards for QPC789 and NT8D09AB neon lamps. Without these boards, the neon lamp is disabled.

NOTES

Depending on the call transfer type selected for individual subscribers, the CLS prompt setting for call forwarding (FNA) might be a different setting.

Only the prompts needed for this integration appear on this screen. Refer to the phone system documentation for additional prompt settings.



After setting up the phone system, use the following procedures to configure the messaging system. Refer to System Administrator Help for additional information about the messaging system features.





The switch parameters appear in the Default Parameters field.

4 Click Save.



6 Click Save.















■ Nortel Meridian Norstar with D42JCTU or D82JCTU Voice Boards Integration

NORTEL MERIDIAN NORSTAR WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION 147




Programming the Phone System...................................................................................................... 151Selecting an Extension Numbering Plan........................................................................................ 151

Configuring the Messaging System................................................................................................... 152

Overview The Nortel Meridian Norstar DR5 V5A or later system with Dialogic® D42JCTU or D82JCTU voice boards integration uses digital lines to connect the phone system and the messaging system. The phone system digital messaging system ports connect to voice boards in the messaging system server. A D42JCTU voice board emulates up to four digital phones. A D82JCTU voice board emulates up to eight digital phones.


1 Review the system and equipment requirements. “Integration Requirements,” below.







Integration RequirementsVerify the phone system and messaging system requirements.

Phone System● For each messaging system port: One digital port that emulates a M7324 digital phone

installed and set up as a messaging system port.

● The phone system ready for the integration.

● A type 66 interconnect block for each 18-pair PBX station interface cable.

● A telco connection cable for each voice board.






UNIVERGE UM4730 INTEGRATION GUIDE NORTEL MERIDIAN NORSTAR WITH D42JCTU OR D82JCTU VOICE BOARDS 148


After installing all of the required hardware on the messaging system server, use the following procedure to connect the phone system and messaging system.

System Connections



2 Connect the messaging system server to the type 66 interconnect block:

■ If the PBX cable cannot be connected to the interconnect block, use a telco cable:




Repeat step 2 for each additional voice board.

Two-wire Pinouts


Type 66 Block Pair

Pin Number


1 2 272


Tip 1 Ring 1

2 4 29 4


Tip 2 Ring 2

3 6 31 6

red-blue blue-red

Tip 3 Ring 3

4 8 33 8

red-green green-red

Tip 4 Ring 4

5 10 35 10

red-slate slate-red

Tip 5 Ring 5

6 12 37 12


Tip 6 Ring 6

7 14 39 14


Tip 7 Ring 7

8 16 41 16


Tip 8 Ring 8


Next Step ...




After connecting the systems, use the following procedures to program the phone system for the integration. Refer to the phone manufacturer documentation for more details.

Selecting an Extension Numbering PlanBefore setting up the messaging system extensions, select an extension numbering plan in accordance with the organization’s requirements.

To set up the phone system for the integration

1 On the phone system, click the Configuration menu.

2 For each outside line set the Dial mode field to Tone in the Trunk Data section.

3 For each outside line set the Prime set field to a messaging system port in the Line Data section.

4 For each messaging system port set the following fields to the specified values in the Line Access section:

5 For each messaging system port set the Applicable Line pool fields to Yes in the Line Pool Access section.

6 If the messaging system acts as the primary attendant, set outside lines that are not using messaging system ports to No ring in the Ringing field in the Line Access section.

7 If the messaging system is set up to answer overflow calls for the operator, set the operator’s phone to forward to a messaging system port on busy or unanswered calls.


1 On the phone system, find the extensions assigned to the messaging system.

2 Set the phone system to hunt to the next extension when the first messaging system extension is busy or unanswered.


For each messaging system port go to the Capabilities section and set the Abilities field to CFB (call forward busy) and CFNA (call forward no answer). For example, for extension 200, set the field to CFB/NA 200 to 201.

When the hunt group is set up, all of the subscriber extensions are forwarded to the first messaging system extension. If the first extension is busy, the system hunts for the next available extension. The system hunts in sequence up to the last extension, then starts over until a messaging system extension becomes available.

To program call forwarding for individual subscriber stations

On the phone system, set up forwarding calls to the messaging system for each subscriber,

❚ Select the Capabilities section and set the Abilities field to CFB (call forward busy) and CFNA (call forward no answer).

Next Step ...

◆ Configure the messaging system. See “Configuring the Messaging System” on page 152.

Field name Value

Line assignment No lines assigned

Intercom keys 1

Prime line I/C



After programming the phone system, use the following procedures to configure the messaging system. Refer to System Administrator Help for detailed information about additional features.





4 The switch parameters appear in the Default Parameters field. Edit the parameters if necessary.

5 Click Save.



7 Click Save.















■ Siemens 9751 CBX with D42JCTU or D82JCTU Voice Boards Integration

SIEMENS 9751 CBX WITH D42JCTU OR D82JCTU VOICE BOARDS INTEGRATION 153




Programming the Phone System...................................................................................................... 157Rolm 8000 CBX systems ............................................................................................................ 157Rolm 9000CBX, Rolm 9751CBX, or Siemens 9751 CBX Systems ...................................................... 162

Configuring the Messaging System................................................................................................... 167

Overview The Siemens 9751 CBX with Dialogic® D42JCTU or D82JCTU voice boards integration uses digital lines to connect the phone system and the messaging system server. The phone system digital messaging system ports connect to the voice boards in the messaging system server. A D42JCTU voice board emulates up to four digital phones. A D82JCTU voice board emulates up to eight digital phones.

Integration StepsFollow these steps to set up the integration.

1 Review the system and equipment requirements“Integration Requirements,” below.




5 Test the phone extensions that are set up for the integration. See “Testing an Integration” on page 175.



Integration RequirementsVerify the phone system and messaging system requirements.

Phone System● Rolm 8000 CBX, Rolm 9000/9751 CBX, or Siemens 9751 CBX.

● The phone system is set up and ready for the integration. Refer to the phone system documentation.







UNIVERGE UM4730 INTEGRATION GUIDE SIEMENS 9751 CBX WITH D42JCTU OR D82JCTU VOICE BOARDS INTE-154


After installing all of the required hardware in the messaging system server, use the following procedure to connect the phone system and voice messaging system.

System Connections



Two-wire Pinouts


Type 66 Block Pair

Pin Number


1 2 272


Tip 1 Ring 1

2 4 29 4


Tip 2 Ring 2

3 6 31 6

red-blue blue-red

Tip 3 Ring 3

4 8 33 8

red-green green-red

Tip 4 Ring 4

5 10 35 10

red-slate slate-red

Tip 5 Ring 5

6 12 37 12


Tip 6 Ring 6

7 14 39 14


Tip 7 Ring 7

8 16 41 16


Tip 8 Ring 8

Four-wire Pinouts

Phone Line Number

Pin Number


1 26 1

27 2


TXR1 TXT1 PXR1 PXT1


2 Connect the messaging system server to the type 66 interconnect block:

■ If the PBX cable cannot be connected to the interconnect block, use a telco cable:





Next Step ...


2 28 3

29 4


TXR2 TXT2 PXR2 PXT2

3 30 5

31 6


TXR3 TXT3 PXR3 PXT3

4 32 7

33 8


TXR4 TXT4 PXR4 PXT4

5 34 9

35 10


TXR5 TXT5 PXR5 PXT5

6 36 11 37 12


TXR6 TXT6 PXR6 PXT6

7 38 13 39 14


TXR7 TXT7 PXR7 PXT7

8 40 15 41 16


TXR8 TXT8 PXR8 PXT8

Four-wire Pinouts

Phone Line Number

Pin Number




After connecting the system, use the following procedures to set up the phone system for the integration. Refer to the phone system documentation for additional details.

Use the procedure for the appropriate phone system:

● For the Rolm 8000 CBX phone system, see the procedures below.

● For the Rolm 9000/9751 CBX or Siemens 9751 CBX phone system, see the procedure on page 162.

Rolm 8000 CBX systems

1 Program the ROLMphone 400 digital station sets.See “Programming ROLMphone 400 Digital Station Sets” on page 157.

2 Program the hunt group.See “To set up a hunt group” on page 160.

3 Program subscriber stations.Set subscriber stations to call forward to the hunt group. See “To program a subscriber station” on page 161.

Programming ROLMphone 400 Digital Station SetsCreate a feature configuration table, extensions, and assign line appearances to feature buttons. Each extension on the ROLM CBX is assigned a class of service (COS) that determines the features available for that extension. The default class of service is 00, this default COS might not have the necessary features for the voice mail ports or the ROLMphone 400 extensions. This section describes how to enable or disable features within a COS.

To set up the class of service

1 On the phone system programming terminal, display the features enabled for a given class of service.

Up to16 classes of service, numbered 00 through 15, can be defined on the ROLM CBX.

2 Change COS 15 to meet the integration requirements.

Disable feature 13 (NFL, no flash allowed) and enable feature 17 (NOH, no howler if disconnected).


3 Display the modified COS to check changes. The COS 15 setup shown below is compatible with the integration.

To program the stations

Before setting up the ROLMphone 400 extensions, you must locate an available ROLMphone Interface channel in the ROLM CBX. An RPI channel is the basic digital port used by ROLMphone 400 digital station sets. Any ROLM CBX with 8003 software or higher has built-in support for the ROLMphone 400. For details locating an RPI channel, see the phone system documentation.

In the examples shown in the following pages, the PAD # (port address) of the selected RPI channel is 010402. Once you locate an available channel, change its configuration to indicate that a ROLMphone 400 is to be attached to it. To implement the feature key layout of the ROLMphone 400s, use the following procedure.

1 Verify settings using the Feature Configuration table.

2 Program key 10 as Hold, key 30 as Connect, key 38 as Transfer, and key 37 as the Message Waiting Center.


3 Assign line appearance 1 to key 9.

4 Check the settings using the Feature Configuration table.

5 Assign the feature configuration table just created to the PAD address used for the integration.

6 Define the ROLMphone 400 as a display phone.

7 Create one extension for the integration line appearance. Assign the extension to key 1. For example, if the first extension in the voice mail hunt group is 501, type: NEX 501.

The first assignment is shown below. The first flag parameter is for ringing, the second for privacy, and the third for the intercom.


8 Forward each extension back to the same number. This prevents ringing calls from forwarding to an error tone.

9 List and verify the ROLMphone 400 programming.

10 Assign the line appearance on the ROLMphone 400 to an appropriate COS. The example below assigns a COS of 15.

Any COS can be used as long as the following settings are assigned:

11 Check the extension.

Repeat this procedure to program the other voice mail extensions.

To set up a hunt group

The integration uses only one hunt group for all of the voice mail ports. The pilot number for the group is the published voice mail number for all direct and forwarded calls. Select a number for this purpose that is easy to remember, for example, 500.

Do not program a name for the voice port hunt group. Programming a name increases the amount of information sent between the ROLM CBX and the messaging system during each call and slows down the overall process.

Feature # Description Setting

3 PRV, private call 1

9 DND, do not disturb 0

13 NFL, no flash allowed 0

17 NOH, no howler if disconnected 1

NOTE

Add only voice mail system ports that answer calls to hunt groups. Do not add ports programmed on the messaging system with the Dial, Lamp, or Msg port status codes.


1 Place the extensions assigned to voice mail ports in a hunt group. The following example uses extension 500 as the pilot number.

2 Check the hunt group.

To program a subscriber station

The remaining ROLM CBX programming involves individual subscriber extensions. Forwarding a subscriber to the integration pilot number provides integrated call answering. Some versions of the phone system software allow two forwarding paths. Program call forwarding for internal, external, busy, and ring-no-answer conditions to meet the subscriber’s needs.

Generally, subscribers using the ROLMphone 400 digital station sets have a message waiting button assigned on their phones. If the pilot number of the integration hunt group is assigned to the message waiting button, a subscriber retrieves messages by pressing the button whenever message waiting indicators are activated. A message waiting button can be programmed on the phones.

1 Assign a forwarding path for the subscriber. In the following examples, the subscriber extension is 201 and the hunt group pilot number is 500.

NOTE

If you program a forwarding path to a second extension and the second extension forwards to the voice mail system, program the second extension forwarding path through feature programming at the ROLMphone 400 digital station sets (press # 9 to enter feature programming).


2 Check the forwarding path.

3 Optionally, assign a message waiting retrieval button.

Next Step ...


Rolm 9000CBX, Rolm 9751CBX, or Siemens 9751 CBX SystemsUse the following steps to set up the Rolm 9000 CBX, Rolm 9751 CBX, or Siemens 9751 CBX for the integration. Refer to the phone manufacturer documentation for more details.

1 Program the ROLMphone 400 digital station sets.See “Program ROLMphone 400 Digital Station Sets” on page 162.

2 Program the hunt group.See “To set up the hunt group” on page 165.

3 Program subscriber stations.See “To program subscriber stations” on page 165.

Program ROLMphone 400 Digital Station SetsCreate a feature configuration table, extensions, and assign line appearances to feature buttons. Each extension on the ROLM CBX is assigned a class of service (COS) that determines features available for the extension. The default COS, 00, might not have the necessary features for the voice mail ports or the ROLMphone 400 extensions. This section describes how to enable or disable features within a COS.

To set the class of service

1 Assign COS 15 settings to meet ROLMphone 400 digital station set requirements.


2 Enable the NOH (no howler if disconnected) feature.

To program the ROLMphone 400 digital stations

Before setting up the ROLMphone 400 feature configuration table, locate an available ROLMphone Interface (RPI) channel in the ROLM CBX. An RPI channel is the basic digital port used by ROLMphone digital sets. Any ROLM 9000 or 9751 CBX should have built-in support for the ROLMphone 400s.

In the following example, the PAD # (port address) of the selected RPI channel is 010402. Once you locate an available channel, change its configuration to indicate ROLMphone 400s are attached. We recommend sequentially numbering these extensions. The extensions are placed in a hunt group later.

1 Locate an unused Feature Configuration Table and create it.

The programming for one line appearance for the station key is shown above. These are the minimum programming requirements for the integration.

2 Check settings by listing the Feature Configuration table.

3 Create one extension number to be used as ringing line appearances on each integration port. The following example uses extension 501 for this application.

NOTE

The ROLM 9000 CBX and 9751 CBX provide default button assignments.

Override default button assignments by keying the required value, shown in bold type, or cancel the assignment by pressing CTRL-N. Check that key 10 is programmed to Hold, key 30 as Connect, key 38 as Transfer, and key 37 as the MWCTR.


4 Assign the new Feature Configuration table to the integration PAD address and program the line appearance buttons.

5 Check the ROLMphone 400 programming.

Repeat this procedure to program the remaining extensions.

NOTE

The example uses the same subscriber dial plan information used in the example for the ROLM 8000 CBX. Extensions 501 integration digital ports.


To set up the hunt group

The integration uses only one hunt group. The pilot number for this group is the published voice mail number for all direct and forwarded calls. Select a number for this purpose that is easy to remember.

Do not program a name for the voice port hunt group because it increases the amount of information sent between the ROLM CBX and the messaging system during each call and slows down the overall process.

1 Place the extensions from all the ROLMphone400 digital station sets in a hunt group using extension 500 as the pilot number.

2 Check the hunt group.

To program subscriber stations

The remaining ROLM CBX programming involves individual subscriber extensions. By forwarding a subscriber to the integration pilot number, you provide integrated call answering.

Some phone system software versions allow two forwarding paths. Program call forwarding for internal, external, busy, and ring-no-answer conditions to suit subscriber needs.

Subscribers with ROLMphone 400 digital station sets generally have a message waiting button defined on the phones. If the pilot number of the integration hunt group is assigned to the message waiting button, a subscriber retrieves messages by pressing the button when message waiting indicators are activated.

1 Assign a forwarding path for the subscriber. In the following example, 500 is the hunt group pilot number.


2 Check the forwarding path.

3 Optionally, assign a message waiting retrieval button.

Next Step ...




After programming the phone system, use the following procedures to configure the messaging system. Refer to System Administrator Help for detailed information about additional features.





The switch parameters appear in the Default Parameters field.

4 Click Save.



6 Click Save.






Next Steps…









■ Toshiba CIX 100/200/670, CTX 100/670, and Strata DK Series Integration

TOSHIBA CIX 100/200/670, CTX 100/670, AND STRATA DK SERIES INTEGRATION 169



Connecting the Systems ................................................................................................................. 171Requirements ........................................................................................................................... 171


Overview An Simplified Messaging Desk Interface (SMDI) port is required on the Toshiba DK280/424 for this integration. The integration uses an RS-232 serial cable to send call information from the phone system to the messaging system.


1 Review the system and equipment requirementsSee “Integration Requirements,” below.




5 Test the phone extensions that are set up for the integration. See “Testing an Integration” on page 175



Integration RequirementsThe steps to set up the Toshiba DK280/424 SMDI integration require the following:

Phone System● Toshiba DK280 or DK424 with an SMDI port installed.

● One serial port available for the serial link.



● One PPTC-25 connector cable.


● An type 66 punchdown board.

Messaging System Server● Messaging system is installed and ready for the integration.



UNIVERGE UM4730 INTEGRATION GUIDE TOSHIBA CIX 100/200/670, CTX 100/670, AND STRATA DK SERIES 170


After installing all of the required hardware on the messaging system, use the following procedure to connect the systems.

RequirementsThe following cables are required to connect the phone system to the messaging system server

● One PPTC-25 connector cable.


● An type 66 punchdown board.


1 Connect one end of the RS-232 serial cable to the PPTC-25 connector cable.


3 Connect the other end of the PPTC-25 connector cable to the SMDI port on the phone system.

4 Connect the analog line from the punchdown block to the appropriate connectors on each analog voice board in the messaging system computer.

Repeat this step for each analog line.

Next Step ...




After connecting the systems, use the following procedures to set up the Toshiba DK280/424 system. Programming the phone system or extension options using difference procedures than those supplied in this document might adversely affect the integration performance.


1 Select specific messaging system ports to be used for the integration and the remaining ports to be used for the automated attendant (if appropriate).

2 On the Toshiba system, activate the SMDI port.

3 In System assignments, set the following:

a Program 10-2 = LED 4 should be turned on for the messaging system to turn off message waiting indication.

b Program 10-3 = LED 8, 9, 11, 13, 14, and 20 should be turned on for correct spacing and digit length. LED 8 allows the phone system to pass caller ID information to the messaging system.

Next Step ...


CAUTION


Modular to PPTC 25 Pin Out

1 to 7

2 to 8

3 to 20

4 to 6

5 to 2

6 to 3

Short pins 4 and 5 on the PPTC-25 connector

Modular to PPTC 9 Pin Out

1 to 5

2 to 1

3 to 4

4 to 6

5 to 3

6 to 2

Short pins 7 and 8 on the PPTC-25 connector







3 Select Toshiba DK280 SMDI in the Switch list.

The switch parameters appear in the Integration Options field.

4 Confirm that the integration string includes the following:

DT CR,,,&, HUT=D S=TOSH

Any changes made on this page requires stopping and restarting the messaging system.

5 Click Save.



7 Click Save.
















In this integration

AAPPENDIX

Testing ExtensionsTest RequiremeTest Steps ......

Testing an Integration

APPENDIX A: 175

...

......................................................................................................................... 176nts..................................................................................................................... 176.......................................................................................................................... 176

Testing Extensions

Use the following procedures to test each extension and confirm that the phone system is correctly programmed.

Test RequirementsThe following is required to properly test each extension:

● A test phone. A standard analog phone set with a ringer. If the phone system voice messaging uses feature phone sets, use a feature set for the tests.

● A line splitter. If the boards use RJ-14 connectors with two extensions per connector, use a line splitter to separate the two extensions.

Test Steps

1 Connect the test phone to the phone system.Use a line designated as a messaging system extension to connect the test phone to the phone system.

2 Confirm that the phone system identifies DTMF dialing through the test extension.Use the test phone to dial a station phone. The station phone should ring.

3 Confirm that the phone system transmits DTMF tones to the test extension.

a Use the test phone to dial a station phone.

b Have someone answer the station phone and enter a digit.

You should hear the tone on the test phone.

Repeat this test for each type of station connected to the phone system. For example, analog, feature set, or operator.

4 Confirm that the test phone can access outside lines.From a line outside the messaging system, dial the number designated for the messaging system.

a Answer the test phone, perform a hookflash (timed break recall), then dial a station phone.

b Listen for ringing, then hangup the test phone. The call should be transferred to the station that was dialed.

5 Confirm that the phone system generates rings on the test extension.From a line outside the messaging system, dial the number designated for the messaging system.

a Answer the test phone, perform a hookflash (timed break recall), then dial a station phone.

b Listen for ringing, then hangup the test phone. The call should be transferred to the station that was dialed.

6 Confirm that trunk routing is set up correctly for extensions that answer trunk calls.Use a station phone to dial the test phone extension. Answer the test phone and use a hookflash, then dial a station phone. Listen for ringing, then hang up the test phone. The call should be transferred to the station that was dialed.

Check that trunk routing is set up correctly for extensions that only answer calls from stations (for phone systems that support trunk routing).

a Dial the test phone extension from a station phone.

b Answer the test phone, perform a hookflash (timed break recall), then dial a station phone.

NOTE

If you are using digital phones, skip this step.

UNIVERGE UM4730 INTEGRATION GUIDE 176

c Listen for ringing, then hangup the test phone. The call should be transferred to the station that was dialed.

APPENDIX A: 177

In this integration

BAPPENDIX

Using GTDetect ...

Learning the Phone System Tones

APPENDIX B: 179

...

.......................................................................................................................... 180

Using GTDetect System tones vary from one phone system to another. Use the GTDetect utility to learn the phone system tones and configure the messaging system server to recognize these tones.

The GTDetect utility also detects voice boards and checks the status of each port on each board. GTDetect is automatically installed with the messaging system software. The messaging system must be stopped before using the utility. For GTDetect to function properly, at least two of the voice ports must be connected.

USING THE MAINTENANCE MENU

To run GTDetect

1 If the messaging system computer is shut down, restart it.

The messaging system VMail log on page appears.

a Log on as admin, then click OK.

b Type the admin password (voicemail), then click Login.

The Linux desktop appears.

2 On the taskbar click Maintenance Menu.

The Maintenance Menu appears.

3 Select Configuration, then press ENTER.

4 Select Global tone detection, then press ENTER.

A confirmation message appears:

5 Click YES.

If any calls are in progress, an alert message appears:

6 Press ENTER to close the calls and shut down the messaging system software.

Wait for the messaging system software to stop. When the messaging system software has stopped the Global Tone Detection options menu appears.

NOTE

To type a different user name, click Start Again.


7 Select an option:

● Manual. Manual tone detection requires one line connected to the voice board and extension.

Follow the step-by-step instructions.

● Automatic. Automatic tone detection requires two lines to be connected.

When global tone detection is completed, an additional menu appears:

8 Select Exit, then press ENTER.

9 The global tone detection returns to the Maintenance menu Configuration page.

10 Select Return to previous menu, then press ENTER.

11 Select Control, then press ENTER.

12 Select Start messaging system software, then press ENTER.

When the messaging system software has restarted, the System Control menu appears.


14 Select Log out, then press ENTER to log out and close the Maintenance menu.

NOTE

The manual procedure requires an extension within reach of the messaging system computer.

APPENDIX B: 181

In this integration

CAPPENDIX

Selecting a Call TrHow to Select CConfiguring RelConfiguring AwConfiguring Wa

Optional IntegratioSetting Port ExtenTesting the Serial Changing the KeypTroubleshooting...

Call Transfer Settings, Integration Options, and Troubleshooting

APPENDIX C: 183

...

ansfer Type.......................................................................................................... 184all Transfer Types ................................................................................................ 184ease Transfers ..................................................................................................... 184ait Answer Transfers ............................................................................................. 185it for Ringback Transfers ....................................................................................... 186n Settings .......................................................................................................... 187

sions .................................................................................................................. 188Link .................................................................................................................... 189ad Map .............................................................................................................. 190

.......................................................................................................................... 192

Selecting a Call Transfer Type

After setting up the messaging system, determine which call forwarding and call transfer settings you want and use the appropriate procedure to configure the call transfer settings.

How to Select Call Transfer TypesCall forwarding on the phone system and call transfer on the messaging system must be set up to work together to avoid overlapping features or conflicts.

The phone system and messaging system capabilities, and unsupported features for each call transfer type. Ensure that the associated unsupported features are not required by the subscribers. Use the appropriate procedure to set up call forwarding on the phone system and call transfer on the messaging system.

Configuring Release TransfersSet the transfer type on the messaging system default subscriber template to set the call transfer type for each new subscriber added to the system.

If subscribers are already enrolled and their settings conflict with the selected transfer type, change the call transfer setting for each existing subscriber.

The transfer type for System Operator boxes, Transaction boxes, Voice Detect boxes, and Public Fax boxes can be configured using the Administration Console. Refer to the System Administrator Help for additional details.

To configure the release transfer type

1 On the phone system, set subscriber extensions to forward all calls to the messaging system when the called extension is busy or is not answered.


3 In the Navigation pane, click Subscribers > Subscriber Template > Call Transfer.

4 Select Release from the Transfer Type list.

5 Click Save.

Call Transfer Settings

If you want to… …and do not need… …then use…

Enable the messaging system to handle calls quickly using the phone system call forwarding capabilities.

The messaging system:

● Call holding ● Call transfer or screening

options ● Message delivery to an

extension. Available if call forwarding-busy and call forwarding-all calls are disabled.

Release transfer.

See “To configure the release transfer type” on page 184.

Use one or more of the following messaging system options:

● Call holding ● Call transfer or screening

options ● Message delivery to an

extension

The phone system:

● Call forwarding-busy ● Call forwarding-all calls

Await answer.

See “To set up the Await Answer transfer type” on page 185.

Use one or both of the following messaging system options, or if your phone system does not support call forwarding-busy:

● Call holding ● Message delivery to an

extension

The messaging system call transfer or screening options and the phone system:

● Call forwarding-busy ● Call forwarding-all calls

Wait for ringback.

See “To set up the wait for ringback transfer type” on page 186.


To change existing subscriber call transfer settings


2 In the Navigation pane, click Subscribers > Subscribers > Call Transfer.


4 Click Save.

Repeat this procedure for each existing subscriber.

To set release call transfer for boxes




4 Click Save.

Repeat this procedure for each existing box.

Configuring Await Answer TransfersSet the transfer type on the subscriber template to set the call transfer type for each new subscriber added to the system.

If subscribers are already enrolled and their settings conflict with the selected transfer type, change the call transfer setting for each existing subscriber.

During an Await Answer transfer, if the call is answered, the transfer is completed. If the extension is busy or rings unanswered, the call is taken back and handled by the messaging system.

The transfer type for the operator box, any transaction box, or any voice detect box can be configured. Refer to the System Administrator Help for additional details.

To set up the Await Answer transfer type

1 On the phone system:

a Set subscriber extensions to forward unanswered calls to the messaging system.

b Set the number of rings the phone system to five (5).

c Confirm that the phone system call forward settings are disabled for all calls and busy calls.



4 Select Await Answer from the Transfer Type list.

5 In the Wait for…rings field, set the number of rings to two rings less than the number of rings programmed on the phone system for forwarding unanswered calls.

A minimum of three rings is recommended.

For example, if Wait for…rings is set to 3 (three), then the phone system must be set to at least 5 rings.

6 Click Save.

NOTE

Setting the “Rings” option as described in this step prevents the phone system from forwarding the call back to the messaging system.

APPENDIX C: 185

To change existing Subscriber Call Transfer settings



3 Select Await Answer from the Transfer Type list.

4 Click Save.

Repeat this procedure for each existing subscriber or box.

Configuring Wait for Ringback TransfersSet up the transfer type in the subscriber template to set the call transfer type for each new subscriber added to the system.

If subscribers are already enrolled in the messaging system and their settings conflict with the selected transfer type, change their settings.

During a Wait for Ringback transfer, if the call is answered then the transfer is completed. If the extension is busy, the call is taken back and handled by the messaging system. If the extension rings unanswered, the call is released to the phone system.

Wait for Ringback is incompatible with forward-busy and forward-all-calls. Wait for Ringback is compatible with forward-no-answer; however, the number of rings to wait in the phone system must be two rings greater than the number of rings to wait in the messaging system. For callers to be able to leave voice messages when the extension rings unanswered enable forward-no-answer.

To set up the wait for ringback transfer type

1 On the phone system:

a Set subscriber extensions to forward unanswered calls to the messaging system.

b Set the number of rings the phone system allows before forwarding calls to five (5).

c Confirm that the call forward settings are disabled for all calls and busy calls.



4 Select Wait for ringback from the Transfer Type list.

5 In the Wait for…rings field, set the number of rings to two rings less than the number of rings programmed on the phone system for forwarding unanswered calls.

A minimum of three rings is recommended.

For example, if Wait for…rings is set to 3, then the phone system must be set to at least 5 rings.

6 Click Save.

To change existing Subscriber Call Transfer settings



3 Select Wait for ringback from the Transfer Type list.

4 Click Save.

Repeat this procedure for each existing subscriber or box.

NOTE

Setting the “Rings” option as described in this step prevents the phone system from forwarding the call back to the messaging system.


Optional Integration Settings

Easy message access and identified subscriber messaging are optional integration settings that can be turned on or off. Use the following procedures to change optional integration settings.

To disable Easy Message Access

Easy message access is enabled by default, blank field or ema=1.



3 Add ema=0 to the end of the Integration Options field string. For example:

DTMFMute=1 ema=0

4 Click Save.






To disable Identified Subscriber Messaging

By default, identified subscriber messaging is enabled, blank field or ism=1.



3 Add a blank space and ism=0 to the end of the Integration Options field string. For example:

DTMFMute=1 ism=0

4 Click Save.






To enable Identified Subscriber Messaging in Secure Mode



3 Add a blank space and ism=2 to the end of the Integration Options field string. For example, adding the string to the end of the DTMNMute=1 string:

DTMFMute=1 ism=2

4 Click Save.






APPENDIX C: 187

Setting Port Extensions

To set port extensions


2 In the Navigation pane, click System > Configuration > Access Numbers.

3 In the Trunk pilot # field, type the trunk pilot number.

4 If applicable, in the Alternate trunk #s fields, type the alternate numbers.

5 In the Pilot # field, type the hunt group pilot number.

6 In the Station numbers field, type the extension numbers assigned to each port.

7 Click Save.

To assign port extensions



The Switch Extensions page appears.

The A/D, Ans, Dial, and Busy status options apply to voice and fax ports.

3 Click Edit All.

4 Type an Extension for each port.

Password. The Password field is automatically filled with the same value typed in the Extension field.

Authorization name. This field is not available in all integrations. In most integrations, this field automatically fills with the value typed in the Extension field.

5 Click Save.

6 Stop and restart the messaging system for the new configuration to take effect as follows:





Status Options Description

Options Key Description

A/D Answer and dial out FC Forwarded calls

DID Direct inward dial NL No LAN connects

Ans Answer only, no dial out

Dial Dial out only

Busy Busy

Lamp Light lamps

A/L Answer and light lamps

MD Message delivery

A/M Answer and message delivery


Testing the Serial Link

If problems occur and you suspect that the serial link might be incorrectly configured, use the following procedure to test the serial link.

To test the serial link

1 Confirm that the serial connection is connected to the correct COM port on the messaging system computer.

2 Confirm the other end of the serial connection is connected to the phone system integration port.

3 Stop the messaging system software.

4 At a command prompt type:

minicom -s

then press ENTER.

This launches the Minicom terminal software.

5 Configure the Minicom serial port to match the phone system configuration (9600bps, 8N1).

Serial packets should appear on the console screen. If information does not appear, the system is not receiving information from the phone system.

6 Press CTRL+A, then press X to exit Minicom.

7 Restart the messaging system software.

APPENDIX C: 189

Changing the Keypad Map

Callers use the keypad on their touchtone phones to interact with the messaging system. The keypad map determines how the numeric digits on the keypad are mapped to alphabetic letters in the messaging system.

Each digit on the keypad is mapped to letters in the messaging system. Each keypad map has an associated wild card digit. Callers can enter a wildcard digit in place of any letter when they are not sure of the letter.

For example, when using the Q=7, Z=9 keypad map, the digits 7-1-1 represent P, Q, R, or S, followed by any two letters.

The messaging system supports five different keypad maps:

The mapping of digits to letters should match the phone system and the phones of the outside callers. The default keypad map for the messaging system is Q=7, Z=9. Use the following procedure to select a different keypad map.

USING THE MAINTENANCE MENU

To change the keypad map

1 Shut down the messaging system.

2 Log on to the Maintenance Menu admin.

3 Shut down the messaging system software:

a Select Control, then press ENTER.

b Select Stop the messaging system software, then press ENTER.

c Select Return to previous menu, then press ENTER.

4 Select Maintenance then press ENTER.

5 Select Command prompt on the Main Menu, then press ENTER.

6 At the Linux command prompt, type:

remap

then press ENTER.

The Keypad Remapping Utility appears. The Current keypad map is shown:

7 Type a number for the new keypad map, then press ENTER.

Keypad map Wildcard

Q, Z on the 0 (zero) key 1

Q, Z on the 1 key 0

Q=7, Z=9 1

Numerals (numbers only) 1 (groups only)

Cosmos (Sweden) None

REMAP v10.0 - Keypad Remapping Utility c) 1983-2007 Active Voice, LLC. All rights reserved.

Type the number corresponding to the desired keypad mapping, or press Ctrl-C to abort:

1. Q-Z on the 0 key 2. Cosmos (Sweden) 3. Numerals 4. QZ on the 1 key Current keypad map -> 5. Q=7, Z=9 keys

New keypad map ->


8 Press CTRL + D, or Esc, to return to the main menu.


10 Select Control, then press ENTER.

11 Select Restart the messaging system software, then press ENTER.


13 Select Log out, then press ENTER.

APPENDIX C: 191

Troubleshooting If you encounter one of the following problems, try using the corresponding corrective actions to fix the problem. If these actions do not correct the problem, or if the problem is not described here, contact Technical Support.

Problem Corrective Action

Calls to the messaging system do not connect.

Calls to the messaging system connect, but no prompts play.

Callers entering an extension are always answered with the opening greeting instead of the personal greeting.

Calls are not integrating with the phone system.

Easy message access is not functioning: a subscriber logs on to the messaging system and hears the opening greeting instead of personal options.

Calls are forwarded to the opening greeting instead of a subscriber’s message box.

Try the following:

● Confirm that expansion boards are firmly seated in the computer expansion slots and that each board is properly configured.

● Confirm that easy message access is set up correctly. See “To disable Easy Message Access” on page 187.

● Confirm that the cables between the systems are connected and functioning correctly. You might try testing each cable or replacing each with a different cable.

● To check the phone system model setup on the messaging system, on the Administration Console, click System > Switch > Switch Information. The phone system manufacturer and model type should be displayed.

Callers are asked to hold (or complain that they are on hold for too long) when calling an extension that is using Do not disturb mode.

Typically this happens because the messaging system is set up to use the await-answer transfer type and call holding for that extension. Call holding must be turned off when using the Do not disturb mode on the phone.

The phone system cabinet that contains the messaging system station cards sporadically resets itself.

The phone system might be overloaded due to an increase in polling traffic between the voice boards and the system. Spread out the load by distributing the messaging system extensions among multiple station cards on the phone system.

For example, distribute three or fewer messaging system extensions per station card.

Subscribers’ phones are not forwarding calls on ring-no-answer or on busy.

Confirm that each subscriber’s phone is set up on the phone system to forward calls to the messaging system hunt group pilot number on ring-no-answer and on busy.

Subscribers are not being identified by the system (using identified subscriber messaging) when leaving messages for other subscribers.

Confirm that identified subscriber messaging is set up correctly on the messaging system.

See “Optional Integration Settings” on page 187.


Subscriber message waiting indication fails.

Message waiting indicators are not activated after messages are left.

Message waiting indicators are not terminated after messages are retrieved.

Perform one or more of the following for the problems listed:

● On the Administration Console, go to System > Port Status. Confirm that at least one of the messaging system ports is set to Light lamps, Dial out only, Answer/Light lamps, or Answer/Dial out to turn message waiting indication on or off.

● On the Administration Console, click Subscribers > Subscribers > Notification. Under Message Indication, confirm that the Enable MWI check box is selected.

● On the Administration Console, click Switch > Switch Settings > MWI. Confirm that the MWI codes for turning MWIs on and off are set correctly.

Await-answer calls release before the personal greeting is played.

Run GTDetect.

See “Using GTDetect” on page 180.

Problem Corrective Action

APPENDIX C: 193

um4730 integration guide

Documents

property of nec infrontia

integration features

general integration

phone system

programming subscriber

document conventions

messaging system

system connections