Mitel SX-2000/SX-2000 LIGHT

Transcription

1 Octel 250 Message Server Configuration Note Rev. E (6/05) Mitel SX-2000/SX-2000 LIGHT Mitel SX-2000/SX-2000 LIGHT Octel 250 XXX LINE TRUNK TDM BUS DNI Line Card VOICE PATH Multiple Return to Operator Outcalling Auto-Attendant Call ID M WI On/Off FLT-D CPU Minimum Release M Stream (MS2006) Minimum Software Release 2.04 With set emulation integration, FLT-D (FLT-DNIC) Cards emulate Mitel Superset 430 digital display sets 1.0 METHOD OF INTEGRATION With set emulation integration, FLT-D (FLT-DNIC) Cards within the Octel 250 emulate Mitel Superset 430 digital display sets. When a call is sent to the hunt group of Octel ports, the display is read and provides the call information to the Octel 250. The call is then answered with the appropriate greeting. Message-waiting indicator is set and canceled by the Octel 250, using the message send feature of the PBX. Octel 250 requirements 2.0 OCTEL 250 ORDERING INFORMATION FLT-D ( 8 ports/board), including those for dedicated message waiting Set Emulation Software feature (Feature Bit 33) Inband Integration Software feature (Feature Bit 35) PBX hardware requirements PBX software requirements 3.0 PBX HARDWARE REQUIREMENTS Digital Network Interface (DNI) Line card channels, one per FLT-D port 25-pair, male-amphenol cables, one per FLT-D One single-line channel for remote service access 3.1 PBX SOFTWARE REQUIREMENTS Message-waiting feature Disclaimer: Configuration Notes are designed to be a general guide reflecting AVAYA Inc. s experience configuring its systems. These notes cannot anticipate every configuration possibility given the inherent variations in all hardware and software products. Please understand that you may experience a problem not detailed in a Configuration Note. If so, please notify the the TAC/TSO at (408) and if appropriate we will include it in our next revision. AVAYA Inc. accepts no responsibility for errors or omissions contained herein

2 Mitel SX-2000/SX-2000 LIGHT (FLT-D) Confidential 2 Digital Sets Feature Package ARS Minimum Software: M Stream (MS2006) Supported integration features 4.0 SUPPORTED FEATURES Station forward to personal greeting - don t answer - busy - busy/don t answer - follow me Multiple Greetings Message-Waiting Indicator - lights - rings Automated Attendant Outcalling/Paging Networking Multiple return-to-operator Direct Call Reply to message left by subscriber in internal telephone-answering mode Personal greeting of original-called party on double-call forward Configuring the Mitel SX- 2000/SX-2000 LIGHT for integration 5.0 CONFIGURING THE MITEL SX-2000/SX-2000 LIGHT TO INTEGRATE Configure DNIC channels that will be connected to the FLT-D ports in the Octel 250. Those channels, configured using the DNI Circuit Assignment form, must be configured as Device Type = SUPERSET 430. Using the Class of Service Options Assignment form, configure a Class of Service for the FLT-D ports designated as the Call Answering ports that have only the following options enabled: Option Call Forwarding - Accept COV/ONS/E&M Voice Mail Port Multiline Set Onhook Dialing Select

3 Mitel SX-2000/SX-2000 LIGHT (FLT-D) Confidential 3 Using the Hunt Group Assignment form, place the Octel 250 ports into a hunt group. The pilot number of the hunt group is the Octel System Access Number. It is used by subscribers to retrieve their messages. It is also used by subscribers to forward their phones to the Octel Overture 250. This hunt group should be configured as Hunt Mode: Circular, Group Type: VOIC . Using the Feature Access Code Assignment form, configure the Feature Access Code for Message Waiting - Activate making sure that the first digit of the Feature Access Code is a *. Using the Feature Access Code Assignment form, configure the Feature Access Code for Message Waiting - Deactivate making sure that the first digit of the Feature Access Code is a #. In Mitel MS2006, M stream software, the Call-Me-Back Message Cancel Timer can be set up to 255 hours. Leaving the option blank will stop the audit from canceling any Call-Me-Back messages. Below MS2006 software, the Timer can be set from 1 to 24 hours only. Three alternatives are available for message waiting on the SX CONFIGURING THE MESSAGE WAITING PORT(S) Three alternatives are available for message waiting on the Octel 250. The first scenario is recommended for the following reasons: It provides dedicated ports for message waiting, avoiding potential call collisions and delays in message waiting caused by the use of non-dedicated ports. It prevents the loss of integration on 'Call Me Backs' to the Octel message-waiting ports. The loss of integration is caused by forwarding the message-waiting port(s) to the hunt group. This solution avoids the potential issue of delays in message waiting caused by an inadequate number of total Call-Me-Back messages available on the PBX. (The total number of Call-Me-Back messages allowed is configurable. Check with the PBX technician.) RECOMMENDED MESSAGE-WAITING CONFIGURATION (Prior to N Stream software): The following is the recommended configuration for message waiting ports on Mitel SX2000 PBX s using software prior to N Stream: The recommended configuration for message-waiting ports 1. Dedicate port(s) to message waiting to ensure that there are ports available to set message waiting. 2. Do not include the message-waiting port(s) in the Octel hunt group. 3. The class of service for the message-waiting ports should be set as follows:

4 Mitel SX-2000/SX-2000 LIGHT (FLT-D) Confidential 4 A second configuration which uses non-dedicated messagewaiting ports Option Call Forwarding - Accept Select COV/ONS/E&M Voice Mail Port Message Waiting Multiline Set Onhook Dialing No 4. Do not forward the message-waiting ports to the Octel hunt group. 5. When the Octel 250 sets message-waiting notification, there will be no extension in the display and the subscribers will not be able to use the Call Me Back feature. Instead, subscribers should be trained to recognize a message-waiting notification that is not accompanied by an extension number in the display as a signal to dial the Octel pilot number and retrieve messages. A SECONDARY MESSAGE-WAITING CONFIGURATION: The following configuration can be used for systems not using dedicated message waiting ports: Important Note: Delays in message waiting and call collisions may occur when non-dedicated message-waiting ports are configured. 1. If the customer chooses to not have the recommended dedicated message-waiting ports, create one hunt group for all Octel ports and create a Class of Service for all Octel ports as follows: Option Call Forwarding - Accept COV/ONS/E&M Voice Mail Port Message Waiting Multiline Set Onhook Dialing Select MESSAGE WAITING CONFIGURATION FOR N STREAM: The following configuration is recommended on systems using MS2007 N Stream software: 1. Include the Message-Waiting ports in the Octel Hunt Group. 2. Create a unique Class of Service for the Message-Waiting port(s) with the following features: Option Do Not Disturb Permanent Select

5 Mitel SX-2000/SX-2000 LIGHT (FLT-D) Confidential 5 COV/ONS/E&M Voic Port Message Waiting Multiline Set Onhook Dialing Note: The feature Do Not Disturb Permanent will route all calls made to the Message-Waiting ports to the Octel Hunt Group. Displays on digital telephone sets will show MSG WAITING, and if the READ MSG is used, the display will indicate the Octel Hunt Group number as the source of the message, instead of the extension number of the Message- Waiting extension that sent the message-waiting command. Configuring the Octel CONFIGURING THE OCTEL 250 Menu System Parameters Type of PBX: M - Mitel SX2000 Menu Port Assignments Extension/Phone No.: Extension number of DNIC channel Line type: 153 M column: Y only for the message-waiting port(s) I and T columns: Y for all ports except the message-waiting port(s) O, P, N, F columns: Define based on your site specific need Menu Transfer Dialing Sequences Flash time: 500 ms Pause time: 1000 ms Transfer sequence: Not Used Reconnect sequence: Not Used Menu In-band Integration Dialing Sequences Dialing Sequence to Activate Message Waiting: <Code>N Dialing Sequence to Deactivate Message Waiting: <Code>N NOTE: <Code> is the Message Waiting - Activate and Message Waiting - Deactivate feature access codes as programmed in the PBX. Menu 8/9.1 - Subscriber Mailbox Profile Subscriber Extension: Enter subscriber s extension number Message Waiting Allowed: Enter Y only for those mailboxes associated with extensions allowing for message waiting notification

6 Mitel SX-2000/SX-2000 LIGHT (FLT-D) Confidential 6 Connecting the DNIC channels 7.0 CONNECTING DNIC CHANNELS Each FLT-D supports eight DNIC ports. Each FLT-D connects to the PBX via a single male-amphenol connector cable. The first port uses the first pair of the cable, every other pair is used by the remaining ports. Physically connect the lines used for the voice path between the switch and the Octel 250. Each FLT-D provides the Amphenol connector on the front edge of the board. See Figure 1. Off-hook/Ringing LED s 25-pair Female Amphenol Connector 26 TA 1 RA TB 3 RB TC 5 RC TD 7 RD TE 9 RE TF 11 RF TG 13 RG TH 15 RH 25 and 50 Telecom Grnd FLT-D Cable Pin-Out Figure - 1

7 Mitel SX-2000/SX-2000 LIGHT (FLT-D) Confidential 7 Testing the integration when installation is complete 7.1 TESTING THE INSTALLATION Create two mailboxes associated with two test extensions. Record a name and personal greeting for each mailbox. System forward one test extension to the Octel System Access Number. Using one test extension, call the other test extension. You should hear the personal greeting. Leave a message. Verify that message waiting indication turns on. Verify that return-to-operator works properly. Call the Octel 250 from a test extension. You should immediately hear the recorded name and be asked to enter your password. Review the message in the mailbox. Verify the direct reply feature works by pressing 8 at the end of the message. Delete the message. Verify that message waiting indication turns off. Set up all ports busy situation. Place a forwarded call and a direct call into the Octel system. Verify the Octel 250 correctly handles the call. Important notes regarding this integration 8.0 CONSIDERATIONS 8.1 Octel recommends dedicating port(s) for message-waiting feature. 8.2 Calls released too quickly by the attendant console to a station that is busy or all calls forwarded to the Octel 250 pass the trunk ID instead of the extension ID. Callers hear system greeting instead of personal greeting. To avoid this problem, the console operator should be instructed to wait approximately one second before releasing the call. 8.3 If your application requires outcalling or networking, the Automatic Route Select (ARS) feature must be enabled. ARS provides a DTMF generator for dialing the necessary DTMF tones to complete the call. If the PBX does not have the ARS feature, analog FLTs are required for outcalling and networking. 8.4 Class of Service feature Message Waiting - Deactivate on Offhook must be set to No in subscribers telephones Class of Service. If left on, the PBX will extinguish message waiting indicators from subscriber s telephones any time the telephone is taken off-hook. This feature defaults to. 8.5 If the O250 is used to support subscribers on remote Mitel SX- 2000/SX-2000 LIGHT switches networked without MSDN networking software, message waiting notification must be

8 Mitel SX-2000/SX-2000 LIGHT (FLT-D) Confidential 8 performed using dedicated FLT-D port(s). This is because the remote switch must provide dial tone as confirmation that the message waiting command was accepted. If the device on the local PBX that sends the message waiting command goes back on-hook before dial tone is provided by the remote PBX, the message waiting command is ignored. When using FLT-D ports for message waiting notification, a pause can be configured in menu 6.2 parameters Dialing Sequence to Activate Message Waiting and Dialing Sequence to Deactivate Message Waiting that will keep the port offhook even after the message waiting feature access code and extension number have been dialed. 8.6 If the Mitel is in a DPNSS environment, Public Network Access via DPNSS must be changed to yes to allow Outcalling. 8.7 If the customers application requires the use of routing via DNIS, Display ANI/DNIS/ISDN Calling Number must be changed to yes CHANGE HISTORY Revision Issue Date Reason for Change D 05/02 GA Release E 06/05 Updated consideration AVAYA Inc. All rights reserved. All trademarks identified by the, SM and TM are registered trademarks, servicemarks or trademarks respectively. All other trademarks are properties of their respective owners. The above information is based on knowledge available at the time of publication and is subject to change without notice. Printed in U.S.A. AVAYA 911 Murphy Ranch Road Milpitas, CA (408)