Nortel DMS-100, SL-100 & DMS-250, DMS-500

Transcription

1 Avaya Modular Messaging Configuration Note Version K (1/10) Nortel DMS-100, SL-100 & DMS-250, DMS-500 DMS-100/SL-100/DMS-250/DMS-500 Message Application Server TRUNK Analog Station Automated Attendant Return to Operator Voice Boards CPU I/O Port Minimum Software BCS 24 with SMDI Package MODEM MODEM RS-232 Circuit Call ID Message Waiting COM Port Releases Supported See section 2.0 Overview This Configuration Note is intended for Avaya certified Modular Messaging technicians/engineers who are familiar with Modular Messaging procedures and terminology. It also assumes that you are PBX certified or very familiar with the features and functionality of the PBXs supported in this Configuration Note and the SMDI protocol. Use this document in conjunction with Modular Messaging Installation Guide and your PBX Administration Guide. Please read the entire document before attempting any configuration. With RS232 integration, call information is transmitted over a digital RS232 link between the PBX and Avaya Message Application Server 1.0 METHOD OF INTEGRATION With RS232 integration, call information is transmitted over a digital RS232 link between the PBX and the Avaya Message Application Server (MAS). Voice communications are provided over separate analog lines on the PBX that connect to the MAS. When an incoming call is received, it is accompanied by a digital message from the PBX containing call information. The MAS then answers the call and plays the appropriate greeting. To set or cancel Message-Waiting Notification, the MAS sends a digital message over the RS-232 link to the PBX. Disclaimer: Configuration Notes are designed to be a general guide reflecting AVAYA Inc. 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 Technical Assistance Center at (800) , and if appropriate we will include it in our next revision. AVAYA Inc. accepts no responsibility for errors or omissions contained herein.

2 Nortel DMS (RS-232) 2 MAS Requirements 1 Release Note: Should features of the integration not function optimally when integrated to a PBX or MM that may be operating on an unsupported software release as defined Section 2.0 and 3.1, customers will need to upgrade their PBX and/or MM to a supported software release. PBX hardware requirements PBX software requirements Supported integration features 2.0 AVAYA S3400 MESSAGE SERVER REQUIREMENTS RS-232 Integration cable (PN & ) Dialogic D/41 or D/120 cards (4 and12 ports/cards) Software Releases 1 : 1.1, 2.0, 3.0, 3.1, 4.0, 5.x 3.0 PBX HARDWARE REQUIREMENTS Station appearances, one per MAS port DMS-100/SL-100/DMS-250 I/O channel One Series 3002 private line data channel One modem provided by the CO NOTE: If the MAS is not co-located with the DMS-100/SL-100/DMS-250, it will be necessary to use modems and a private data line for the RS-232 link. Co-located systems require a null modem instead. The customer must provide the necessary hardware. Cables: - RJ11 four-wire telephone cord, one per MAS port 3.1 PBX SOFTWARE REQUIREMENTS Minimum Software 1 : BCS 24 Simplified Message Desk Interface (SMDI) Feature Package NTX119AA 4.0 SUPPORTED INTEGRATION FEATURES Items are supported System Forward to Personal Greeting All Calls [ ] Busy Ring/no answer Station Forward to Personal Greeting All Calls Bus Ring/no answer [ ] Auto Attendant Call Me Direct Call External Call ID (ANI) Fax

3 Nortel DMS (RS-232) 3 Find Me [ ] Internal Call ID Message Waiting Multiple Call Forward Multiple Greetings N+1 [ ] Outcalling Return to Operator Configure the DMS PBX Create a UCD hunt group for the analog lines connected to the MAS Create the analog lines connected to the MAS 5.0 CONFIGURING THE DMS PBX TO INTEGRATE The I/O channel should be configured as follows: full duplex 1200 baud asynchronous 7 data bits, 1 stop bit even parity Create a UCD hunt group for the analog lines connected to the MAS. Configure the UCD hunt group as a group using the SMDI feature. Configure the Release Count # for 0. This count sets the maximum number of times a port can take abandoned calls before logging itself out. Setting it to 0 will guarantee that ports are not locked out. Create the analog lines connected to the MAS. Place the lines in the UCD hunt group. Verify that the line identification numbers (line ID for the data link messages) for each analog line are in the same sequential order as they are connected into the MAS (i.e., Line ID 0001 connects to MAS port 1, Line ID 0002 connects to MAS port 2, etc.). The Cut-off on Disconnect (COD) feature must be programmed. In the Table OFCVAR (Office Variables), program the COD mnemonic for greater than 600 ms. This programming causes the DMS-100/SL100 to disconnect the MAS ports immediately when callers hang up. If this is not programmed correctly, subscribers might receive messages with a recording of Please hang up and dial again at the end. Define the following feature codes: Call Request Activate (CRA) Call Requestor Deactivate (CRDS) Modify each subscriber s extension profile to allow message-waiting notification.

4 Nortel DMS (RS-232) 4 For subscriber phones with lights, assign one position on the phone set for message-waiting notification. Forward all subscriber phones to the pilot number of the UCD hunt group on busy and ring-no-answer. The pilot number is the MAS System Access Number. NOTES: The decibel level of the lines coming into the MAS should be -5.5 db or higher or else call volume programming is ignored. For exact DMS-100/SL-100 programming instructions, refer to Northern Telecom s SMDI interface document (NTP ). Please refer to section 8.0 at the end of this document for special PBX programming considerations. 6.0 CONFIGURING THE MESSAGE APPLICATION SERVER Configuring the MAS Configuring the MAS platform for proper PBX integration requires configuring several menus accessed within the Voice Mail System Configuration application. Access the Voice Mail System Configuration application from the MAS program group. Access the Voice Mail Domain, and then select PBXs Centrex Access the General tab and set the following values: Go Off Hook when Port Disabled = Enable by checking the box Pause before Digits = 500 Pause Interval for Comma in Dial String (ms) = 1000 DTMF Inter-Digit Delay during Dialing (ms) = 80 DTMF Length during Dialing = 80 DTMF Length during Detection (ms) = 50 DTMF Length during Play (ms) = 50 Access the Call Transfer tab and set the following values: Transfer Mode = Blind Transfer Prefix Code = &,XN Transfer Complete Code = Leave Blank Transfer Release Code when Busy = &,& Transfer Release Code when No Answer = &,& Transfer Release Code when Reject = &,&,,, Flash Time Interval (ms) = 500

5 Nortel DMS (RS-232) 5 Enable Call Progress = Enable by checking the box Start Delay for Call Progress (ms) = 1000 Access the Hangup Detection tab and set the following values: Maximum Continuous Tone before Hanging Up (ms) = 6000 Hang-up String = Leave Blank Hang-up String Timeout (ms) = 0 Minimum Duration For Drop in Loop Current (ms) = 300 Maximum Silence before Hanging Up (ms) = 6000 Return to the Voice Mail System Configuration window, and select Voice Servers and access Telephony Interface (Analog). Select the Analog tab to configure the selected port(s) on your Voice Server as follows: - Playback Volume = 2 (Default) - Number of Ports = Enter the number of ports in your system Note: The MAS service must be restarted to allow port enabling IMPORTANT SMDI protocol only allows use of a 7 or 10 digit extension length. - Set the Extension Field Length in Packet field to 7 or 10 digits to match the length used for extensions in the SMDI packet at your site. - Using VMSC, in TUI under VMD set MB # to x, where x is the # of digits in a MB (i.e., 4, 5, 6, 7, etc). - In MSS when adding users their MB length is set to x (as above) but their EXT # must be the 7 or 10 digit # to match the extension sent in the SMDI packet. (see FYI below). NOTE: If MS-Exchange you have 3 fields: NUM, EXT, MB# that need to be set. FYI: The 7 or 10 digit extension # you enter in user record in the MSS is used for MWI and call transfers. If the customer uses 4 or 5 digit dialing, the DMS COS for the ports connected to the MM must be set to 7 or 10 digits so AA transfers will work properly. - Enable the port(s) by checking the Box field next to the Port field - Extension = Enter the proper extension number assigned to each port - Incoming Ring Count = 1 - Primary ID = Enter Logical Terminal Number (LTN) for that port (normally, LTN start with 0001 for first port, 0002 for second port, 0003 for third port, etc.). - Secondary ID = Enter Message Desk (MD) number for all ports. NOTE: The Secondary ID is the Message Desk # and must be 3 digits in length (standard SMDI protocol). For example, MD could be 001, 999, 501, 698, etc. If you do not enter the correct MD # calls will not integrate. Return to the Voice Servers section and access PBX Integration. Access the General tab. Select Serial as the integration type. Maximum Time to Wait for Serial and Remote Integration Data = 4 Access the Serial General tab and set the following values: Packet Format = SMDI Extension Field Length in Packet = <enter 7 or 10> *see sidebar note Maximum Number of Remote Service Sessions = 0 (see side Note) Log Serial Packets = Enable by checking the box Access the Serial Settings button and set the following values: Line Speed (Bits per Second) = 1200 Data Bits = 7 Stop Bits = 1

6 Nortel DMS (RS-232) 6 For multiple MAS servers, refer to Consideration 8.6 Parity = Even Flow Control = None Connector = COM1 After making these changes, return to Configuring the voic system within the S3400 Message Server Installation guide. Ensure you are prompted to restart the Message Application Server services to apply these changes. 7.0 INSTALLING THE INTEGRATION LINK AVAYA provides a cable to connect from the 202-T modem port to the MAS. Connect the cable to the COM1 serial port on the MAS. If the MAS is going to be co-located with the DMS-100/SL-100 (and no modem s are going to be used), a null modem adapter must be used. Important notes regarding this integration 8.0 CONSIDERATIONS/ALTERNATIVES 8.1 At software levels BCS 26 and below, extensions on the DMS-100/SL- 100 are not allowed to transfer calls directly to a UCD group. A suggested workaround is to create a hardware-supported analog station that is ring-no-answer forwarded to the voice module. Use this station as a transfer target to the MAS. In this scenario, the person transferring the call must stay on the line until at least one burst of ringing is heard. If not, the DMS-100/SL-100 will re-ring the transferring party and the transfer will not be complete. BCS 27 or higher does allow calls to be directly transferred to the MAS. 8.2 Users might experience silence at the end of messages and ports might take up to 30 seconds to disconnect. Subscriber training is recommended to encourage callers to exit the MAS properly. 8.3 For proper disconnect, a PBX patch must be removed. The patch #RPG50A24 prevents the DMS-100 from providing the required cutoff for disconnect supervision. This patch if installed on the DMS-100 must be removed. 8.4 In order to use the 1X67FA card, you must enable Patch #DDK14A29 on the DMS-100. (Later software will incorporate the patch.). The 1X67FA card transmits data at multiple baud rates. 8.5 Loss of data link reverts the MAS to interface mode. Calls can still be forwarded to the MAS ports but will not have call ID. 8.6 Procedure for adding more than one Message Application Server (MAS) when using RS-232 integrations: The following steps are for MAS 1 only:

7 Nortel DMS (RS-232) 7 1) The first MAS is the only one that will have the RS-232 link from the PBX connected to COM1 2) MAS 1 will also have the appropriate Serial integration (i.e. Serial General, NEC/Ericsson) according to the Configuration Note or the PBX used. 3) Finally, within the Serial integration programming of MAS 1, configure the Maximum Number of Remote Service Sessions. For example, if there are 2 additional MAS servers, then the value should be 2. The following steps are for the additional MAS servers only: 1) The remaining MAS servers will not have any integration link or any other cabling from the PBX or external devices. 2) These MAS servers will have the PBX Integration programmed as Remote. 3) Next, access the Remote tab from the PBX Integration General page and configure the 2 fields (Primary Remote Server Name and Secondary Remote Server Name) with MAS #1 s info. You can not get integration data from any other MAS, so it must be MAS 1 only. After concluding these steps, save them, and continue with the remaining of the programming detailed on either the Configuration Note and/or the MM Installation Guide. 8.7 Should non-integrated calls arise during heavy MWI conditions it is advised that MWI be disabled (via COS setting) for those mailboxes not associated with valid extensions on the PBX. CHANGE HISTORY Revision Issue Date Reason for Change DRAFT /14/03 Initial release for review/validation DRAFT /07/03 Brand name change DRAFT /12/03 Included DMS-500 to the PBX list. DRAFT /02/04 Added Consideration 8.5 Version A 11/19/04 GA Version B 04/22/05 Updated to support MM R1.1, added Consideration 8.6 Version C 04/11/06 Updated to support MM R3.0 Version D Version E 05/14/07 03/02/2007 Rewrote Secondary ID is Message Desk with explanation in Section 6.0 Added sidebars to explain 5 digit extensions v. 7/10 digit length for SMDI at end of Section 6.0

8 Nortel DMS (RS-232) 8 Version F 05/17/07 Removed Consideration 8.5 as it incorrectly noted a Registry Key for 4-digit extensions. Added Consideration 8.2 about users experiencing silence at end of messages. Version G 09/3/2007 Added Consideration 8.7 regarding MWI and MBs with valid extensions. Version H 05/05/08 Updated to support MM 4.0 Version I 2/02/09 Updated to support MM 5.0 Version J 07/09 Updated to support MM 5.1 Version K 01/19/10 Added note indicator to titles of Section 2.0 and 3.1; added corresponding note in sidebar; removed word supported in same sections for MAS releases and PBX Software releases AVAYA Inc. All rights reserved. All trademarks identified by the, SM and TM are registered trademarks, servicemarks or trademarks respectively. All other trademarks are properties of their respective owners. The above information is based on knowledge available at the time of publication and is subject to change without notice. Printed in U.S.A. AVAYA Inc McCarthy Blvd. Milpitas, CA (408)