Nortel M1 -- Set Emulation

Transcription

1 Avaya Modular Messaging Configuration Note Version O (7/09) Nortel M1 -- Set Emulation Linear Hunt Meridian One Message Application Server TRUNK Integrated Services Digital Line (ISDL) Port Card Automated Attendant Return to Operator Call ID Message Waiting Voice Boards CPU Minimum Software rel Mi nimum Software (see section 2.0) The Dialogic card passes call information to the Avaya Message Application Server, which then answers with the proper greeting 1.0 METHOD OF INTEGRATION The Dialogic D/82JCT-U is an eight-port voice processing board that emulates the 2616 digital display telephones. When a call is presented to a hunt group consisting of D/82JCT-U ports, the display information is read and the PBX provides the call information to the Avaya Message Application Server (MAS), which then answers with the proper greeting. The D/82JCT-U then sends MWI on or off information to the PBX via a digital port from the PBX, which in turn sets the message lamps on the phones on or off. MAS Requirements 2.0 AVAYA MESSAGE APPLICATION SERVER REQUIREMENTS Dialogic D/82JCT-U Board (8 port card) Software Releases: 1.1, 2.0, 3.0, 3.1, 4.0, 5.x CT-Bus cable PBX hardware requirements 3.0 PBX HARDWARE REQUIREMENTS NT8D02 Integrated Services Digital Line (ISDL) ports: - Revision AB or higher - One channel per Dialogic port 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 M-1 Set Emulation 2 Cables: - RJ11 telephone cord, one per Message Application Server (MAS) port - D/82JCT-U cable connected to 50 way telco female, 12 4-wire RJ11 cluster box/panel where voice server is greater than 3 feet from the PBX or directly connect to the PBX card using the D/82JCT-U cable where the voice server co-resides with the PBX. This is required for each 8-port D/82JCT-U card installed in the voice server. - If more than 1 D/82JCT-U card is installed then a CT-Bus drop down cable must be used to connect the D82U cards together e.g. a 4-drop CT- Bus cable if 4 or less cards are installed. PBX software requirements 3.1 PBX SOFTWARE REQUIREMENTS Generic X.11, Release , or Succession 3/4/5 with the following: MSB, Make Set Busy, Option 17 MWC, Message Waiting Center, Option 46 EES, Enhanced End-to-End Signaling, Option 10 DDSP, Digit Display, Option DIALOGIC REQUIREMENTS Dialogic D/82JCT-U Board (8 port card) D/82 JCT-U cable Supported integration features 4.0 SUPPORTED INTEGRATION FEATURES Items are supported System Forward to Personal Greeting All Calls [ ] Ring/no answer Busy Busy/No Answer Station Forward to Personal Greeting All Calls Ring/no answer Busy Busy/No Answer [ ]

3 M-1 Set Emulation 3 Auto Attendant Call Me Direct Call External Call ID (ANI) Find Me Internal Call ID Message Waiting Multiple Return to Operator Multiple Call Forward N+1 Outcalling NOTICE: The programming entries in this Config Note are only for illustration purposes. It is recommended that a qualified technician review the customer s programming for accuracy. 5.0 CONFIGURING THE M-1 PBX SPECIAL NOTE: The following represents changes to the M-1 PBX that will affect the MAS integration. Items not addressed here do not require modification for integration with the MAS and should remain as-is on the PBX. NOTE: All entries must be NEW, do not reuse existing extensions, ACD groups, Terminal Blocks, etc. Reusing existing items will cause the integration to fail. To reuse existing items (i.e. extension numbers), these must be completely deleted and then recreated. It is recommended that a hard copy of the Customer Data Block be printed in overlay 21 to verify the existing programming. If necessary, change the following parameters in overlay 15 to the underlined values. Default values are listed in parentheses. The following PBX programming is intended for certified Nortel M1 technicians/engineers. REQ CHG TYPE CDB Customer Data Block CUST 0-31 Customer Number OPT MCI, (MCX) Message Center is Included (excluded) MDID YES, (NO) No-answer DID calls are (are not) routed to the Message Center NDID YES, (NO) No-answer non-did calls are (are not) routed to the Message Center

4 M-1 Set Emulation 4 MWFB YES, (NO) DID calls encountering busy are (are not) routed to Message Center EEST NO Enhanced end-to-end signaling (OFF) 5.1 CONFIGURING THE 2616 TERMINAL NUMBER(S) IN A HUNT GROUP One 2616 TN is configured for each Dialogic with Linear Hunt Configuration. The DN assigned to key 0 is the primary directory number (PDN) used as part of the hunt group Set REQ NEW TYPE 2616 Digital set data block TN lll S CC U Terminal number: loop (0-159) shelf (0-1) card (1-10) unit (0-7) CDEN SD, (DD), 4D Density of this card is single, (double), quad and is dependent on the type of PBX card is being used CUST 0-31 Customer number DES MMA1 Designation for telephone CLS FBD Forward Busy Denied HTA Hunting Allowed MWD Message Waiting Denied CNDA Calling Name Display Allowed DNDA Dialed Number Display Allowed CPTD Forced Camp-on to another set Denied FDN HUNT EHT EFD XXXX XXXX XXXX XXXX Where XXXX is the DN of the pilot number of the hunt group.

5 M-1 Set Emulation 5 KEY 00 SCR XXXX PDN (Primary Directory Number Port 1) 02 MSB Make Set Busy 03 TRN Transfer Key 04 MCK Message Cancellation Key 05 MIK Message Indication Key Program one 2616 station for each MAS port. NOTE: Keys not mentioned should be configured as Blank keys. 5.3 CONFIGURE GROUP HUNT Prompt Response Comment.ld 18 REQ chg or add TYPE GHT LSNO List Number CUST xx Customer Number PLDN xxxx Pilot DN (this is configured in ld 57) SIZE Size of list STOR xxx yyy...y * *Entry number (0-999) and the digits stored with it i.e, CONFIGURING THE 2616 TERMINAL NUMBER(S) IN A LINEAR CHAIN Instead of using a linear hunt group a chain of DN s can be used where each DN in the chain forwards on busy and ring no answer to the next DN One 2616 TN is configured for each Dialogic port in the linear chain. The DN assigned to key 0 is the primary directory number (PDN) used as part of the chain Set REQ NEW TYPE 2616 Digital set data block TN lll S CC U Terminal number: loop (0-159) shelf (0-1) card (1-10) unit (0-7) CDEN SD, (DD), 4D Density of this card is single, (double), quad and is dependent on the type of PBX card is being used CUST 0-31 Customer number DES MMA1 Designation for telephone

6 M-1 Set Emulation 6 CLS FBD Forward Busy Denied HTA Hunting Allowed MWD Message Waiting Denied CNDA Calling Name Display Allowed DNDA Dialed Number Display Allowed CPTD Forced Camp-on to another set Denied FDN HUNT EHT EFD FNA HFA CFTA XXXX XXXX XXXX XXXX Where XXXX is the DN of the next terminal in the chain. The last terminal in the chain uses the DN of the first terminal in the chain. KEY 00 SCR XXXX PDN (Primary Directory Number Port 1) 02 MSB Make Set Busy 03 TRN Transfer Key 04 MCK Message Cancellation Key 05 MIK Message Indication Key Program one 2616 station for each MAS port. NOTE: Keys not mentioned should be configured as Blank keys. 5.3 CONFIGURING THE SUBSCRIBERS TELEPHONE 2616 Set REQ CHG TYPE 2616 Digital set data block TN lll S CC U Terminal number: loop (0-159) shelf (0-1) card (1-10) unit (0-7) CDEN SD, (DD), 4D Density of this card is D8 single, (double), quad CUST 0-31 Customer number

7 M-1 Set Emulation 7 DES XXXXX Designation for telephone FDN XXXX Forward Directory Number (Enter the Pilot number of the MAS) CLS FBA Forward Busy Allowed FNA Forward Ring-No-Answer Allowed HTA Hunting Allowed MWA Message Waiting Allowed CNDA Calling Name Display Allowed DNDA Dialed Number Display Allowed HUNT XXXX Hunt DN of next station (Enter the Pilot number of the MAS) KEY 00 SCR XXXX PDN (Primary xx SCN XXXX This number must be unique for each 2616 set xx MWK XXXX Message Waiting Key can be programmed on any other available key. NOTE: If the voice server ports are part of a hunt group, the hunt group pilot number should not be entered here. Instead the 1 st voice server port should be used. The following programming is required on the PBX to support the multiple personal greetings 5.4 PBX PROGRAMMING FOR MULTIPLE PERSONAL GREETINGS The following programming is required on the PBX to support the multiple personal greetings feature. feature In Overlay 95, Calling Party Name Display, set RESN to YES. Then assign the following values to the specified parameters: REQ CHG TYPE CPND CUST CNFG MXLN 27 STAL YES DFLN 27 DES NO RESN YES CFWD CFWD CFNA RNA HUNT BUSY PKUP PKUP

8 M-1 Set Emulation 8 XFER XFER AAA AAA NITC NITC NOTE: Items left blank do not require changes. Verifying that M-1 TNS are active 5.5 VERIFYING THAT M-1 TNS ARE ACTIVE To ensure the M-1 TNs are active, go to overlay 32. (Indicates ready to accept command) STAT XXXX Where XXXX is the TN of the M-1 programmed as an MAS port The status displayed will IDLE or DSBL IDLE status is required. If DSBL is displayed, enable them with the following using overlay 32: ENLU XXXX Where XXXX is the TN of the disabled TN Please refer to the Consideration section at the end of this document for special PBX programming considerations. - continued on next page Configuring the MAS

9 M-1 Set Emulation CONFIGURING THE MESSAGE APPLICATION SERVER Configuring the MAS platform for proper PBX integration requires configuring several menus accessed within the Voice Mail System Configuration application, and a certified MM engineer. Access the Voice Mail System Configuration application from the MAS program group. Access the Voice Mail Domain, and then select PBXs NT M-1 (Set Emulation). Access the General tab and set the following values: DTMF Inter-Digit Delay during Dialing = 80 DTMF Length during Dialing = 80 DTMF Length during Detection = 50 Port Disable Key = C Access the Transfer/Outcall tab and set the following values: Transfer Mode = Blind Start Delay for Call Progress = 6000 Initiate Transfer = ^KD,L%s, Initiate Blind Transfer = %s Complete Transfer = ^KD Retrieve Call = ^KA, Drop Call = ^KR Make Call Prefix = Leave Blank Access the Tone Detection tab and set the following values: Maximum Silence before Hanging Up (ms) = 6000 Maximum Tone before Hanging Up (ms) = continued on next page -

10 M-1 Set Emulation 10 Next access the Message Waiting Indicator (MWI) Support NOTE for MM 1.1 & 2.0 only: Limit Requests should be checked. The Max Req per Minute depends on how many MWI Ports are configured. Each MWI request takes 10 secs. So that s 6 requests per minute per port. (i.e. 4 MWI Ports = 24 MWI Req per Min) 1. Enable Message Waiting Indicator (MWI) = Enable by checking the box 2. MAS MWI Server = Enter the name of the MWI server created during the installation procedure. 3. Scheduled MWI updates: Active or Inactive = Configure as per customer requirements.* 4. Limit requests = Leave Unchecked 5. Maximum Requests per Minute = <grayed out> 6. Message Application Servers that Support MWI = This box should contain a list of MAS servers capable of placing MWI requests. 7. Select OK to save changes *Note: The Scheduled MWI updates parameter is only available on MM 3.x NOTE 2: We recommend at least 2 ports dedicated for Message Waiting by removing the highest 2 ports from the default port group and placing them in a port group of their own called e.g. MWI port group.

11 M-1 Set Emulation 11 Return to the Voice Mail System Configuration window and access the Message Application Servers, then select the General tab under the Telephony Interface (Set Emulation) and set the following values: Playback Volume = 2 Concurrent Calls = Enter the number of ports connected to the PBX Note: The MAS service must be restarted to allow port enabling Port = Enable ports by checking the checkbox next to the ports Extension = Enter the extension number associated with the MAS port NOTE: We recommend at least 2 ports dedicated for Message Waiting by removing the highest 2 ports from the default port group and placing them in a port group of their own called e.g. MWI port group. Return to the Voice Mail System Configuration window and access the General tab within the PBX Integration property page and set the following value: IMPORTANT: Be sure to DISABLE the option Indicator ON/Off signals must use the same port by ensuring the box next to is UNCHECKED (blank). Not doing so may result in delaying MWI operation. Set Emulation = Enable by checking the box Access the QSIG/SE tab and set the following values: Port Group Name = Enter the Group defined for your system Max MWI Session = 2 Indicator On/Off signals must use the same port = <Leave Blank> MWI On = ^O,%s,^O MWI Off = ^F,%s,^F After making these changes, return to Configuring the voic system within the Message Application Server Installation Guide. Ensure you are prompted to restart the Message Application Server services to apply these changes. - continued on next page -

12 M-1 Set Emulation CONNECTIVITY The Dialogic D/82JCT-U emulates 2-wire Nortel sets. The shielded PBX station interface cable is used to connect the D/82JCT-U board to a Nortel PBX. The shielded cable has a 36-pin connector at one end and a 50-pin telco/amphenol connector on the other. The 36-pin connector mates to to connector located on the rear of the Dialogic D/82JCT-U board. The 50 pin connector is used to connect to connect to a punch down block or other device that provides the necessary connectivity to the PBX ports for integration. See pinout-tochannel configuration in figure below Pin 1 26 Channel 1 Transmit/receive (pins 2 / 27) Channel 2 Transmit/receive (pins 4 / 29) 50-pin Telco/amphenol plug connector pinout-to-channel relationship Important notes regarding this integration 8.0 CONSIDERATIONS/ALTERNATIVES 8.1 The Meridian Option 11 does not support supervised transfers below Release 18. This is because the option 11 does not currently support reconnecting with a transferred call. Unsupervised transfers must be used. 8.2 Determine if ACD option is required. Set Emulation integration installations that use hunting does not require ACD, unless the number of ports exceeds the number of hunting steps available on your PBX model. Eighteen steps are supported on the Options 11, 21, 51, or 61. Thirty steps are available on the Options 71 and 81. If

13 M-1 Set Emulation 13 the number of ports exceeds the number of hunting steps, ACD is required to expand the hunting capability. 8.3 Verified versions of PBX software include through 22..xx. 8.4 Secretarial filtering allows a set (phone A, for example) to forward calls to a second set (phone B). If a user at phone B transfers such forwarded calls back to phone A, phone A will ring instead of re-forwarding the call. 8.5 No more than 8 voice mail ports on the NT PBX cards are recommended. AVAYA highly recommends that the MAS voice ports be distributed among different port cards/shelves/loops on the M1 PBX. This reduces the possibility that a single card/shelve failure will affect a large number of MAS ports. Depending on the PBX architecture, performance could also be an issue on some PBXs during high traffic, if a large number of calls are being processed on the same card. In addition, heavy traffic could cause the PBX to reboot and or initialize. 8.6 The 2616 station configured for message waiting should be assigned on an NT card with low traffic. Otherwise customers can experience excessive 7A (message waiting bad extension) errors, on valid extensions. 8.7 AVAYA recommends a ratio of one dedicated message waiting port for every 24 integrated ports. However some customer environments may require a higher ratio due to MWI traffic. 8.8 Automated Attendant/ECP applications transferring calls between NMS nodes may experience loss of integration. When Trunk Route Optimization is enabled on NMS trunks, calls transferred to stations on remote switches that forward without first ringing the station do not pass called party ID to the FLT-N port. The workaround is to have customers use Trunk Tromboning, which allows call ID to be passed throughout the entire call process. 8.9 AVAYA recommends the Background Task 30 be disabled in the configuration data block (LD 17) of the M1. Otherwise, problems with integration and message waiting can occur. This background task 30 can be performed during the midnight routine, however is not recommended as a background routine Customers may experience a problem with Nortel Release 25.10, where the PBX does not provide the correct display information needed to integrate properly. Customers must request that Nortel install patch MPLR in order to resolve this problem.

14 M-1 Set Emulation The following Registry Entry must be entered to support integration to remote sites: Registry Key: HKLM/Software/Octel/Geneva/VCM_telephonyServiceMgr/D82U_NTM1 Add Value: OverrideCallerID Data Type: REG_DWORD Value: Station Coverage To enable stations to cover to the pilot number in a Nortel PBX, starting at load 15 the following features allow call coverage treatment for multiple stations. You may consider this in lieu of administering each individual station s coverage. CXOD - No Override of Call Forward External CXOA - Overrides Call Forward External Denied CFXD - Allows call forward to a CDP Distant Steering Code (DSC)

15 M-1 Set Emulation ADDENDUM A - NORTEL NETWORK MESSAGE SERVICES The Nortel Network Message Services - Message Center feature is designed to allow a centralized message center to serve multiple Nortel PBXs. With this feature a MAS system, acting as a message center, can provide integration for multiple Meridian SL-1 or Meridian M-1 PBXs connected with an ISDN or T- 1/D-channel network. Meridian SL-1 or Meridian M-1 REMOTE PBX Meridian SL-1 or Meridian M-1 VOICE PATH Modular Messaging LOCAL PBX Meridian SL-1 or Meridian M-1 REMOTE PBX The Nortel Network Message Services feature requires one of the following Nortel networking capabilities: ISDN Primary Rate Access (PRA) or ISDN Signaling Link (ISL). Both require a signaling path, called the D-channel. PRA networks utilize the D channel of the PRA to carry signaling information. ISL networks utilize a dedicated data line as a D channel, usually requiring modems. To support an ISL network for integration, the D-channel must operate at 9600 bps or faster. Slower speeds can cause message waiting notification to become unreliable. There is no restriction for PRA networks, which support a D- channel operating at 56 kbps. Below is a summary list of the PBX requirements. This list is not intended to be all inclusive; it is meant as a guideline only. Some options listed have hardware and software prerequisites that are not listed. It remains the responsibility of the customer and PBX vendor to identify all necessary hardware and software components and to correctly configure the Nortel Network Message Services - Message Center.

16 M-1 Set Emulation 16 NORTEL PBX REQUIREMENTS: Integration Requirements for Local PBX - refer to appropriate Configuration Note X11 Release 16 Software Network Message Services (option 175) Advanced ISDN Network Features (option 148) ISDN Signaling (option 145) ISDN Primary Rate Access (PRA) (option 146) or ISDN Signaling Link1 (ISL) (option 147) Message Center (option 46) End-to-End Signaling (option 10) Coordinated Dial Plan (CDP) (option 59) or Network Automatic Route Select (NARS)(option 58) ¹ With ISL networking, the D-channel must operate at a minimum of 9600 bps. CHANGE HISTORY Revision Issue Date Reason for Change DRAFT /19/02 Initial release for review/validation DRAFT /10/03 Brand name change Version A 03/28/03 GA Version B 09/02/03 Changed Initiate Transfer and Complete Transfer: by adding a comma (delay) at the end of the sequence. Version C 12/16/03 Updates to meet MM R1.1 Version D 03/03/04 Added Consideration 8.11

17 M-1 Set Emulation 17 Version E 07/21/04 Removed comma (delay) from Complete Transfer and added comma (delay) to Retrieve Call as per development s input. Version F 09/16/04 Updated to Meet MM R2.0 Version G 10/20/04 Updated to support Nortel Succession 3.0 Changed PBX programming for LD95 Version H 04/22/05 Updated 8.12 Version I 04/11/06 Added: MM 3.0 to support release section 2.0 New bullet for Scheduled MWI updates parameter added in Section 6.0, noted for MM3.0 Version J 01/24/07 Corrected statement in section 6.0 so Indicator On/Off signals must use the same port is disabled (unchecked). Added text sidebar with related information. Added Section 7.0 Connectivity for Dialogic Board for Nortel DSE integration. Version K 01/18/2008 Updated diagram page 1 and removed Consideration 8.12 regarding N+1 and QSIG as it did not apply to this integration. Replaced with 8.12 detailing features for coverage. Version L 05/05/08 Updated to support MM 4.0 Version M 05/16/08 Removed Dialogic Driver release from Section 3.2 Version N 2/02/09 Updated to support MM 5.0; Changed Limit Requests for MWI in Section 6.0 Version O 07/09 Updated to support MM 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)