Mitel OnePoint Messenger SX-200 Users Guide

OnePoint Messenger/SX-200 Guide

NOTICE

The information contained in this document is believed to be accurate in all respects but is not warranted by Mitel Corporation (MITEL). The information is subject to change without notice and should not be construed in any way as a co mmit ment by MI TEL or any of it s af fi liates or subsidiaries. MITEL and its affiliates and subsidiaries assume no responsibility for any error or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate any such changes.

Nothing in this document may be reproduced in any manner, either wholly or in part for any use whatsoever, without written permission from Mitel Corporation.

Host Command Interface, HCI, MITEL, MiTAI, NuPoint Messenger, NuPoint Voice, NuPoint Fax, NuPoint Agent, OnePoint Messenger, SUPERSET, SX-200 and SX-2000 are trademarks of Mitel Corporation. Windows 95 and Windows NT are trademarks of Microsoft Corporation. INTEL and Pentium are trademarks of Intel Corporation. All other product names specified in this document are trademarks of their corresponding owners.

OnePoint Messenger/SX-200 Guide

OnePoint Messenger Release 2.0

Part number: 9164-120-115-NA, Rev. A

August 9, 2000

â, ä

, Trademark of MITEL Corporation.

OnePoint Messenger/SX-200 Integration Guide

About This Guide ............................................................................9

How to Use This G u id e ............... ............. .. .. .............. .. ............. .. .. .............. .. 9

Book Organization ................................................................................................ 10

Chapter Organization.................... ....... ...... ....... ...... ....... ...... ...... ....... ...... ....... ...... . 10

Using Electronic and Printed Versions............................................................... 10

Conventions U s e d in Th is G u id e ............ ............. .. ... ............. .. ............. ... .. 10

Keys, Commands, and Buttons........................................................................... 11

Images and Tables................................................................................................ 11

Type in Commands and Screen Output.............................................................. 12

Lists........................................................................................................................ 12

Notes and Cautions .............................................................................................. 12

Other Text Styles................................................................................................... 12

Other Documentation.................................................................................. 12

Contacting Technical Publications ..................................................................... 14

1. OnePoint Messenger/SX-200 Integration Overview...............15

What Is OnePoint Messenger and Unified Messaging? .......................... 15

Telephony Server.................................................................................................. 16

Telephony Server Peripherals................................................................................................17

Benefits of the Integration.......................................................................... 18

Call Flow Overview...................................................................................... 18

Task Overvie w .. ............. ... ............. .. ............. ... .. ............. .. ............. ... ........... 20

Integration Strategy .................................................................................... 20

2. Configuring the SX-200 PBX....................... ...... ....... ...... ....... ...2 3

Overview of OnePoint Messenger Requirements.................................... 24

Required Forms and Settings .................................................................... 25

Form 1, System Configuration............................................................................. 26

OnePoint Messenger/SX-200 Integration Guide, Rev. A, 8/9/00 iii

Form 2, Feature Access Codes ........................................................................... 26

Form 3, COS Definitions....................................................................................... 26

Form 4, System Options....................................................................................... 29

Form 9, Desktop Device Assignments................................................................ 30

Form 11, Data Circuit Descriptors....................................................................... 30

Form 12, Data Assignment................................................................................... 31

Form 17, Hunt Group............................................................................................ 31

Form 31, System Abbreviated Dial Entry............................................................ 31

Form 34, Direct I/O................................................................................................ 33

Check MAI Installation and Programming.................................................33

Show Status Command........................................................................................ 33

Examples of the Customer Data Entry (CDE) Forms................................34

3. Installing the TalkTo Card..................................... ...... ....... ..... 39

About the TalkTo CX Card.............................. .. ...........................................39

SX-200 Support for Peripherals........................................................................... 40

Installing the TalkTo Card ...........................................................................40

TalkTo CX Card Configuration............................................................................. 43

TalkTo CX Card Settings.......................................................................................................43

Troubleshooting the TalkTo Card Installation...........................................43

Changing the IRQ.................................................................................................. 44

Changing the I/O Base Address .......................................................................... 45

4. Installing Mitel Telephony Application Interface (MiTAI)... 47

What You Need to Complete this Chapter.................................................47

Installing MiTAI on the Telephony Server..................................................47

Installing MiTAI on the Telephony Server........................................................... 47

Checking the Operation of the MiTAI Link to the PBX .............................51

Editing the Ser v e r H o s ts Fi le ............ .. ... ............. .. ............. ... ............. .. .......53

5. Configuring OnePoint Messenger PBX Integration Software55

Introduction..................................................................................................56

Integrating the Telephony Server with the SX-200 ...................... .............56

Show N Tel Telephony Applications Overview .................................................. 56

Notification Server Configuring and Testing Overview..................................... 57

Configuring Show N Tel with the SX-200 PBX..........................................59

Assigning Pro g r a m s to Li n e s .... ............. .. ............. ... .. ............. .. .............. .. 61

Modifying the Phone System Definition.................................................... 63

Setting Show N Tel Paramete rs ............ .. ............. .. .............. .. .. ............. ... .. 66

Setting OneP o in t S y s tem Parameters........... .. .. ............. .. .............. .. .. ....... 67

Editing Configuration Files for a Mitel PBX Integration .................................... 68

Editing the Server Hosts File.................................................................................................68

Editing the Telsrvr.ini file for a Mitel PBX Integration........................................................69

Starting and Stopping Telephony Server.................................................. 70

Configuring OnePoint Messenger to Auto-start ................................................ 71

Running the Telephony Applications.................................................................. 71

Reassigning Lines to Other Applications........................................................... 71

Index...............................................................................................75

OnePoint Messenger/SX-200 Integration Guide, Rev. A, 8/9/00 v

List of Figures

Figure 1-1 Network Diagram ................................................................................................. 16

Figure 2-1 Show Status Command Display ........................................................................... 33

Figure 2-2 Form 1, System Configuration .............................................................................34

Figure 2-3 Form 2, Feature Access Codes ............................................................................. 35

Figure 2-4 Form 3, Class Of Service ......................................................................................35

Figure 2-5 Form 4, System Options/System Timers .............................................................. 36

Figure 2-6 Form 11, Data Circuit Descriptors .......................................................................36

Figure 2-7 Form 12, Data Assignment ...................................................................................37

Figure 2-8 Form 17, Hunt Groups ..........................................................................................37

Figure 2-9 Form 31, System Abbreviated Dial Entry ............................................................ 38

Figure 2-10 Form 34, Direct I/O ..............................................................................................38

Figure 3-1 Windows NT Diagnostics, Resources Tab, IRQ List ..........................................41

Figure 3-2 Windows NT Diagnostics, I/O Port List .............................................................. 42

Figure 3-3 TalkTo Card Diagram ...........................................................................................45

Figure 4-1 MiTAI Settings Dialog, Hardware Tab ................................................................ 49

Figure 4-2 MiTAI Settings Dialog, Software Tab ................................................................. 50

Figure 4-3 MiTAI Settings Dialog, Versions Tab .................................................................. 51

Figure 4-4 MiTAIX Program Window 1 ...............................................................................52

Figure 4-5 MiTAIX Program Window 2 ...............................................................................52

Figure 4-6 MiTAIX Program Window 3 ...............................................................................53

Figure 5-1 SNT Manager, Configure CTI, Device Map Tab ................................................. 60

Figure 5-2 Show N Tel Runtime Tab, Assign Phone System ................................................63

Figure 5-3 Show N Tel Setup, Phone System Tab .................................................................64

Figure 5-4 SNT Setup, Phone Sys Definition, Configure CTI Tab ....................................... 65

Figure 5-5 Show N Tel, Feature Definitions Tab ................................................................... 66

Figure 5-6 Show N Tel Manager, Parameters Tab ................................................................ 67

Figure 5-7 Telsrvr.ini ............................................................................................................. 70

Figure 5-8 SNT Manager, Operate and Monitor Window ..................................................... 72

vi Table of Contents

List of Tables

Table 2-1 Form 2, Required Feature Access Codes .............................................. 26

Table 2-3 Form 3, Additional ONS COS Features ................................................ 27

Table 2-2 Form 3, COS Features Common to the Four COS Groups ................... 27

Table 2-4 Form 3, Additional User Set COS Features .......................................... 28

Table 2-5 Form 3, Additional MiTAI link/DNIC 2103 COS Features ................ 28

Table 2-6 Form 3, Additional MWI/Pager Notification COS Features ................. 28

Table 2-7 Form 4, System Options ........................................................................ 29

Table 2-8 Form 11, Data Circuit Descriptor, Select Option .................................. 30

Table 2-9 Form 31, System Abbreviated Dial Entry ............................................. 32

Table 2-10 Form 34, MAI Programming: Direct I/O .............................................. 3 3

Table 3-1 Base Address Locations on the TalkTo Card ........................................ 46

Table 5-1 Telephony Applications ........................................................................ 61

OnePoint Messenger/SX-200 Integration Guide, Rev. A, 8/9/00 vii

OnePoint Messenger/SX-200 Integration Guide, Rev. A, 8/9/00 viii

About This Guide

Use this guide to integrate a OnePoint Messenger Telephony Server with a Mitel SX-200 PBX. I f y ou a re i nst al li ng a turnkey TS800 Telephony Server, use this guide with the OnePoint Messenger Getting Started Guide. If you are installing OnePoint Messenger on a bare system, use this guide with the OnePoint Messenger Installation Guide. This integration guide replaces Chapter 4 in that guide.

This chapter contains these sections:

Section Page

How to Use This Guide 9 Conventions Used in This Guide 10 Other Documentation 12

How to Use This Guide

“Task Overview” on page 20 in Chapter 1 lists the sequence of tasks

in the installation and integration process, noting the chapter associated with the task.

OnePoint Messenger is designe d to be r elati vely s imple to impl emen t and use. However, integrating the OnePoint Messenger Telephony Server with a Mitel PBX requires the skills of a technic ian with certification in the programming of an SX-200 and the installation of OnePoint Messenger. While this manual lists the critical PBX features that must be enabled and contains instructions on the use of the PBX user interface, the instructions are for LIGHTWARE 17 and may not be current for your system. See the manufacturer’s programming guide that accompanies your PBX software. In addition, this manual does not discuss the array of monitoring, programming, and troubleshooting options available to the Mitel SX-200 installer and administrator.

OnePoint Messenger/SX-200 Integration Guide, Rev. A, 8/9/00 9

Book Organization

This guide provides an overview in Chapter 1, followed by chapters organized by the most appropriate sequence of activities.

• Chapter 1 (page 15): Overview of the components, tasks, and

benefits of the integration

• Chapters 2 (page 23): Configuring the SX-200 PBX

•Chapter 3 (page 39): Installing the TalkTo card on the Tele-

phony Server

• Chapter 4 (page 47): Installing MiTAI on the Telephony Server

• Chapter 5 (page 55): Configuring the Telephony Server, with an

overview of startup and shutdown procedures

• Index: In the electronic form of this guide, the index items are

hyperlinked to the associated contents.

Chapter Organization

Each chapter in this b ook u ses th e same or gani zatio n. Under t he chap ter title is a brief introduction to the chapter content, followed by a list of the major topic headings, as exemplified above.

Using Electronic and Printed Versions

This guide uses a format that accommodates both on-screen viewing and printing. The text is aligned to 7" by 9" borders, so that, when printed on normal letter stock, there is a lot of room for you to make notes. Use Acrobat Reader version 3.0 or better to view and print PDF versions of the document.

Links: Blue text indicat es hyperl inks. The Acrobat bookmark li st and thumbnails also provide hyperlinks. The Table of Contents (page iii) is hyperlinked to the chapters and sections in chapters. Each chapter contains its own hyperli nked tabl e of cont ents i n its intro ducti on. References to sections, figures, and tables are hyperlinks.

Conventions Used in This Guide

This section describes the formatting conventions used in this guide to give you extra cues about the action that you are to take.

10 About This Guide

Keys, Commands, and Buttons

The commands “select”, “cl ear”, “click”, and “choose ” al l me an basically the same thing—to make a choice—but the terms are used in specific situations:

• “Choose” is used in menus, such as the Windows Start menu and program menus, to indicate menu items.

• “Click” is used for obvious buttons, up and down arrows, in edit boxes, spin controls, and for the Windows Start button.

• “Double-click” is us ed in any si tuat ion where pr essi ng the mou se button twice is the most appropriate action, although other options may be available.

• “Press” is used when indicating a computer keyboard or telephone keypad key. There are brackets around the keyboard key, as in “Press [Tab].”

• “Select” is used on property pages (tabs) and dialogs, such as to indicate items in a field or group of options. “Clear” is used to deselect a check in a check box or an entry in a field.

This guide generally does not include the keyboard shortcuts for menus and commands. To use the keyboard shortcuts, you should:

• Display menus by pressing [Alt] a nd the underlined charact er d is played on the screen (for example, press [Alt+F] for the File menu).

• Choose commands by typing the underlined character displayed on the screen (for example, type S for the Save command).

An instruction that involves making a choice from a menu is structured: “From the XXX menu, choose YYY.” This style is also used for dialog boxes. As you become familiar with the style, you can focus on the words in bold as the critical operative phrases.

Images and Tables

Tables and inline graphics in this guide contain captions with numbers based on the chapter number. References to a figure or table from another page are linked and highlighted in blue to indicate the link. You can also find and access them from the Acrobat bookmark list.

When presenting information about buttons, such as “Click the XXX button to open the YYY dialog box,” this guide may present the but-

Conventions Used in This Guide 11

ton to the left of the instruction, as shown here. In that case, the graphic is not labelled.

Type in Commands and Screen Output

For statements in command syntax format,

bold type like this

Brackets like these < > designate the variables that you are to replace with other information. For exampl e, in the followi ng command, you type the word the names of the drive and directory you are using:

<drive>\<directory>\INSTALL

The same font in reg ular we ight ( not bo ldfac e) pre sen ts scr een out put.

Lists

Numbered lists present the steps of procedures that you must follow in the order given.

Bulleted lists present options for which the order is not important.

Notes and Cautions

A “NOTE:” presents information that is of special importance or is relevant only to some users or in some situations.

A “CAUTION!” alerts you to choices with potentially problematic results.

small mono-spaced

indicates the characters you should type.

INSTALL but replace “drive” and “directory” with

“WARNING!” is more serious than a caution, alerting you to a choice that could cause a failure of the system.

Other Text Styles

Italic type is used to introduce terms and for the titles of publications. In this guide, boldface type is used to emphasize tasks and key

words, such as buttons, tab, and menu items, to make them easier for you to spot. For example, a task is presented with the purpose in a separate bold line, followed by the steps, with key words in bold.

1. OnePoint Messenger/SX-200 Integration Overview

This chapter is an overview of the in tegration between the O nePoint Messenger™ Telephony Server and the SX-200 PBX to create a unified messaging environment. This chapter includes details on installing the line cards in the Telephony Server and setting up telephony applications on the Telephony Server. This chapter contains the following sect ions:

Section Page

What Is OnePoint Messenger and Unified Messaging?

Telephony Server

Benefits of the Integration 18 Call Flow Overview 18 Task Overview 20 Integration Strategy 20

What Is OnePoint Messenger and Unified Messaging?

OnePoint Messenger is a software suite that, when combined with other hardware and software products, provides a unified messaging environment. “Unified messaging” is the storage of telephone voice messages, faxes, and e- mail in one ce ntral re pository so that use rs can use a PC or a telephone to retrieve both e-mail and messages sent from a telephone.

OnePoint Messenger also provides a single point of user administration on the Exchange Server connected to the Telephony Server through a LAN. The Telephony Server provides a messaging conduit between the PBX and the Exchange Server, caching users’ Exchange profile information, such as telephone passwords and greetings for faster message access through a telephone.

OnePoint Messenger/SX-200 Integration Guide, Rev. A, 8/9/00 15

The network diagram in Figure 1-1 shows the major components that provide the unified messaging service, examples of the clients, and the relationship between the components.

Figure 1-1 Network Diagram

Telephony Server

In these guides,“Telephony Server” is used to refer to the collection of OnePoint Messenger telephony applications that reside on “the Telephony Server” (the computer running the Windows NT Server

4.0 operating system). The OnePoint Messenger software on the Telephony Server is com-

prised of a group of Windows NT Server applications that, among other tasks, provide the link between the SX-200 and Microsoft Exchange.

Those telephone call routing and messaging services include:

• Controlling what happens to calls that are not answered and providing the caller the ability to leave and retrieve voice messages

• Providing digitization, transcoding, and compression of telephone messages for stora ge on Exc hange or forwarding to VPIM

16 OnePoint Messenger/SX-200 Integration

accounts, and also reverse transcoding of messages saved on Exchange back to callers and VPIM accounts

• Enabling OnePoint Messenger subscribers (“users”) to retrieve and reply to e-mail messages that are read to them using the textto-speech (TTS) capabilities of Telephony Server

• Providing advanced fax handling features, including routing email to fax machines and a Fax on De mand servi ce; see Chapter 4 of the OnePoint Messen ger Admini st rator Guide for a dis cus si on of OnePoint Messenger fax features.

For more on the RAS (support) programs, see the OnePoint Messen- ger Administrator Guide, Chapter 1 and Chapters 5 through 9. See Chapter 5 in that guide for operational details.

Telephony Server Peripherals

The backplane of the Telephony Server contains an Ethernet LAN card for communication with Exchange and the telephony “line cards” cards that provide the connection to the switch.

When integrating with an SX-200 switch, the Telephony Server contains a TalkTo CX card and one or more Natural MicroSystems (NMS) line cards in the ISA bus (also, optionally, a Brooktrout fax card). The connection to the SX-200 PBX is through both the TalkTo and NMS cards. A digital line connects the Line port on the TalkTo card to the DNIC card on the PBX. Analog lines connect the ONS card on the PBX to four duplexed RJ-61 ports on each NMS AG-8 card.

For details on installing the TalkTo card in the TS80 0 turnkey Telephony Server, see Chapter 3 (page 39). See Appendix A of the OneP- oint Messenger Getting Started Guide for recommendations on card arrangement in ISA slots (“slot map”), and IRQ and I/O base address assignment.

For an overview of installing other line cards, see Appendix B in the OnePoint Messenger Installation Guide, then see the manufacturer documentation.

Modem: To provide remote technical support, connect a modem to a Telephony Server serial port and to an outside telephone line, then configure the program pcAnywhere, which is included with the turnkey TS-800 system, to communicate over that modem and allow offsite support to control the Telephony Server.

What Is OnePoint Messenger and Unified Messaging? 17

Benefits of the Integration

The integration between the PBX and the Telephony Server provides these benefits:

• Forward to Personal Greeting: Provides the ability to play a

user’s personal greeting to a caller who has been forwarded to voice mail.

• Auto Logon: The Te lephony Server can recognize a caller as a

OnePoint Messenger subscriber ( “user”), r ather tha n as an out side caller, when calling directly from the user’s phone. The Telephony Server greets users by name and asks for their passcodes.

• Multiple Use Ports: Allows use of the same port for dynamic

allocation of ports for the Automated Attendant, the Message Center, including Text-to-Speech e-mail access, or fax services.

• Direct Answer to In ternal Message: Allows a messa ge recipient

to record an answer to a message from another user without having to first dial the user’s extension.

• Message Notification: Allows the Telephony Server to send a

message waiting notifi cation to a use r through the PBX. The PBX then activates the message waiting indicator, such as a light or a stutter dial tone, on the user’s extension.

Call Flow Overview

This is a basic overview of the processing sequence of calls routed from the SX-200 PBX to the Telephony Server:

1. The PBX receives a call intended for an extension managed by the PBX.

2. If the call is to a OnePoint Messenger user whose phone is busy or is not answered, the PBX redirects the call to the Telephony Server. The PBX also directs calls to the Telephony Server that are forwarded by users to voice mail, or users who make a direct call to the Message Center (the mailbox access pilot number) on the Telephony Server.

Other T ele phony Server s ervices can be associat ed with parti cular phone numbers, such as t he Auto ma te d Att end ant and the Fax on Demand service. For details, see Chapter 3 in the OnePoint Mes- senger Administrator Guide.

18 OnePoint Messenger/SX-200 Integration

3. The call arrives at the Telephony Server in two streams of data:

• The call itself goes to a port on the NMS card. The card has four physical ports, each of which handles two loop start phone lines.

• The calling data goes to the TalkTo card. This includes the caller’s phone number, called party’s phone number, and the reason code why the call was sent to the Telephony Server; this is also known as CLI, or calling line identification.

4. The NMS card detects th e call and al erts Telephony Server. At the same time, the TalkTo card passes the CLI data to Te lephony Server software that uses the ca lled n umber to det ermine whether to play a system greeting or a user’s greeting. The TalkTo card’s role is complete for this call.

5. Telephony Server maintains a cache of user profile information, including digitize d greetings. The appropr iate greeting loads from the Telephony Server onto the NMS card, which converts it to analog speech and plays it to the caller.

6. The Telephone User Interface (TUI) on the Telephony Server sends the appropriate digitized prompts to the NMS card for conversion and playing to the caller. For example, if the call is for a user, the TUI pr ompts t he calle r with t he messa ging op tions avail able, such as to record or re-record a voice message, or to l ea v e a fax.

7. The caller responds with a voice message or keypad input.

8. The NMS card converts the analog input from the caller (the voice message and keyed responses to prompts) into digital strings for Telephony Server. The NMS card routes fax messages through the Brooktrout card.

9. T el epho ny Server package s the ca ller’s message into a digit al fil e and routes it to the recipient’s mailbox on the Exchange Server.

Reciprocally, when users retrieve voice messages from a telephone, the NMS card converts the stored digitized voice messages back into analog voice for delivery to the user.

Call Flow Overview 19

Task Overview

1. Install ONS and DNIC digital line cards on the SX-200 PBX,

2. Install and configure the TalkTo card on the Telephony Server.

3. Install and configure the NMS AG-8 cards and Brooktrout card

4. Install the MiTAI 7.5.3 software on the Telephony Server, then

5. Install the OnePoint Messenger software on the Telephony

6. Configure Show N Tel and the other Telephony Server software

Integration Strategy

then configure the PBX to communicate with the Telephony Server. See Chapter 2 (page 23).

See Chapter 3 (page 39).

on the Telephony Server. See the manufacturers’ documentation and Appendix B in the OnePoint Messenger Installation Guide.

configure MiTAI for the TalkTo card and the SX-200. See Chapter 4 (page 47).

Server. See Chapter 6 in the OnePoint Messenger Installation Guide.

to communicate with the PBX. See Chapter 5 (page 55).

OnePoint Messenger provides three services that you can set up so that callers can access any one of them by dialing unique pilot numbers. They are Automated Attendant (automated receptionist), Message Center (access to mailboxes), and Fax on Demand (faxback). Typically, to be able to provide optimum access to each service, you would create a hunt group for each, the total lines of which would match the number of lines attached to the Telephony Server assigned to incoming calls. For the SX-200 integration, however, you must route calls to the Auto mated Attendant and Fa x on Demand through the Message Center pilot. Chapter 2 (page 23) here describes creating subscriber extensions for Automated Attendant and Fax on Demand (often called phantom extensions), set up to forward all calls to the Message Center pilot.

On the Telephony Server side, you would normally be able to assign applications to certain ports that would be dedicated to providing either the Automated Attendant or Fax on Demand service. For the SX-200 integration, you must assign the Telephony Server telephony application to all inbound ports. The Telephony Server telephony application is a general purpose application that provides all three

20 OnePoint Messenger/SX-200 Integration

dialed services (Automated Attendant, Message Center, and Fax on Demand). The correct se rvi ce ans w er s b ase d on the pilot number t hat the caller d ials.

Notifications and Se ndFax ar e outbound applications t hat require outdial ports on the PBX.

Integration Strategy 21

22 OnePoint Messenger/SX-200 Integration

2. Configuring the SX-200 PBX

This chapter contains required PBX settings to enable OnePoint Messenger unified messaging. This chapter contains these sections:

Section

Required Forms and Settings 25

Form 1, System Configuration 26 Form 2, Feature Access Codes 26 Form 3, COS Definitions 26 Form 4, System Options 29 Form 9, Desktop Device Assignments 30 Form 11, Data Circuit Descriptors 30 Form 12, Data Assignment 31 Form 17, Hunt Group 31 Form 31, System Abbreviated Dial Entry 31 Form 34, Direct I/O 33

Check MAI Installation and Programming 33 Examples of the Customer Data Entry (CDE) Forms 34

Page

For details on SX-200 programming proce dures, se e your Mitel documentation:

• For details on data entry, refer to the Mitel Practice, SX-200 PBX Customer D ata Entry (CDE) (91xx-yyy-210, where xx is the product designator and yyy is the software release).

• For specific information on ONS voice mail setup, see the document SX-200 EL-ML Technical Documentation–Release 3.1

OnePoint Messenger/SX-200 Integration Guide, Rev. A, 8/9/00 23

• On the Mitel SX-200 EL/ML LIGHTWARE 17 CD-ROM (P/N 9109-953-081-NA), refer to the section “Voice Mail on ONS Ports”.

CAUTION! Only a Mitel-certified SX-200 PBX technician should program the SX-200.

Information exchan ge b etween the Telephony Ser ver and the SX-200 PBX is achieved through the Mitel Application Interface (MAI), of which MiTAI is a component. To accommodate the MAI link, the PBX should contain the following hardware:

• DNIC digital line circuit for the TalkTo card connection

• ONS card for analog voice mail ports on the NMS cards

Program the PBX for MAI oper ation. You can program only one MAI port for the PBX system.

NOTE: You can program the MAI link without removing the PBX from service.

Overview of OnePoint Messenger Requirements

From the viewpoint of programming the PBX, the OnePoint Messenger unified messaging system provides two general categories of features:

• Message Center, Automated Attendant, and Fax on Demand

• Message Waiting notifications and fax forwarding

Message Center, Automated Attendant, and Fax on Demand are grouped together, because they can use the same incoming lines and trunks. Each needs its own pilot number. Note that the SX-200 can have its own Automated Attendant; it is as an optional feature. There are several ways t hat y ou can se t up support for Automat ed Att endant and Fax on Demand on the SX-200. The simplest way is to program dedicated extensions that are permanently rerouted to the voice mail access code.

Message waiting notifications by paging and fax forwarding each need one or more dedicated lines that can sup port lon g distan ce outdi aling. They do not need pilot numbers.

24 Chapter 2, Configuring the SX-200 PBX

+ 53 hidden pages