Octel 350
Message Server
Configuration Note 4032 - Ver C (3/01)
Nortel SL-100*
1.0 METHOD OF INTEGRATION
With RS232 integration, call information is transmitted over a digital RS232 link between the SL100 and the Octel system
With RS232 integration, call information is transmitted over a digital RS232 link between the SL100 switch and the Octel system. Voice communications are provided over a separate path created by analog lines on the switch that connect to the Octel system. When an incoming call is received, it is accompanied by a digital message from the SL100 switch containing call information. The Octel system then answers the call and plays the appropriate greeting. To set or cancel message-waiting indicators, the Octel system sends a digital message over the RS232 link to the SL100.
2.0 OCTEL 350 ORDERING INFORMATION
Octel 350 requirements
• SMDI Integration kit - includes RS232 Integration software
• ATICs Analog TICs (12 ports/card)
§ Disk Drives
• Asynchronous Communications Processor (ACP), to support three or more RS232 links
• 25-pair, right-angle, male-amphenol cables, one per ATIC
• Null modem, one per local PBX, and per local terminal
NOTE: Determine whether direct integration or Asynchronous Communications Processor (ACP) integration will be used. To do so, count the number of RS232 links and system management terminals that will be supported. The allowable combinations of integration links and system management terminals without an ACP are shown in Table 1.
3.0 SL100 HARDWARE REQUIREMENTS
SL100 hardware requirements
• Ground-start line appearances, one per Octel 350 port
• One single-line channel for remote service access (RDAC)
• Nortel Cable - NTNX36AQ
• One Series “3002” private line data channel
• I/O channel for RS232 link
3.1 SL100 SOFTWARE REQUIREMENTS
SL100 software requirements
• Minimum Software Stream: MSL003 and above
• Simplified Message Desk Interface (SMDI)
• Feature Packages: NTX119AA - Message Waiting NTXE47AA - Meridian Display Communication NTX732AA - SMDI Interface
• Octel ports must be in a UCD group
• Message-waiting feature for each subscriber extension as required
• User programmable DFB/RNA software package for Call forward on busy/ring-no-answer to the appropriate multiline hunt-group pilot number for each subscriber extension
3.2 CUSTOMER PROVIDED EQUIPMENT
• One modem provided by the CO - see section 8.8
NOTE: One 202-T data set (modem) provided by CO/Customer premise, the 202T or 212A-type modems are not required, however, the RS232 data link is still required.
4.0 SUPPORTED INTEGRATION FEATURES
Supported integration features
• Station forward to personal greeting
- All Calls
• System forward to personal greeting
- Busy
- Ring-No-Answer
• Message Waiting Indicator
- stutter dial tone
• Outcalling
• Multiple Return-to-Operator
• Direct Call
• Reply to message left by subscriber in internal telephone-answering mode
• Personal greeting of original-called party on multiple-call forward
• Multiple SMDI Links
• Call Sender
• Centralized voice mail - See section 8.8
• Multiple greetings
5.0 CONFIGURING THE SL100 TO INTEGRATE
Configuring the SL100 to integrate
* The decibel level of the lines coming into the Octel system should be -5.5 db or higher or else call volume might be insufficient.
* For exact SL100 programming instructions, refer to Nortel’s SMDI interface document (NTP 555-4151-100).
Configure the I/O channel
o The I/O channel should be configured as follows: TABLE: TERMDEV TERMDES: OCTEL IOCNO: CKTNO: TERM TYPE: SMDI BAUDRT: B1200 (see note) INTYP: EIA EQPEC: 1X67FA PRTY: EVEN GUAR: N MODEM: NONE COMCLASS: ALL
The I/O port must be full duplex, asynchronous, and have computer-to-computer communications.
Configure the I/O channel
NOTE: The baud rate must match the baud rate defined in menu 6.5.
o Create a UCD hunt group for the analog lines connected to the Octel 350. Configure the UCD hunt group as a group using the SMDI feature. The following table is used to configure the UCD group.
TABLE UCDGRP:
UCDNAME: Voice mail ACD: N CUSTGRP: (enter a name to define this customer) UCDRNGTH: 30 THROUTE: OFRT NSROUTE: 75 PRIOPRO: OFRT MAXPOS: 75 DBG: 12 DEFPRIO: 144 RLSCNT: N MAXWAIT: 1 0 MAXCQSIZ: 1880 OPTIONS: 144
(AUDIO 10 Y AUDIO2) (UCD_SMDI OCTEL 1 $) $
o Define the SL100 link using the following table:
TABLE: SLLNKDEV DEVNAME: OCTEL DEVTYPE: HS1X67 XLATION: NONE PROTOCOL: NONE DRECTION: INOUTLK ZFERS:
(SMDIDATA $) $
o Define the Directory Number Route using the following table:
TABLE: DNROUTE DNNM: ( Define the number to reach the Octel system) DNRESULT: FEAT UCD VOICE_MAIL PRIM 0
Create the analog lines connected to the Octel system
o If you are using loop-start station appearances, 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 SL100 to disconnect the Octel 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.
o Modify each subscriber’s extension profile to allow message-waiting notification.
o For subscriber phones with lights, assign one position on the phone set for message-waiting notification.
o Forward all subscriber phones to the pilot number of the UCD hunt group on busy and ring-no-answer. The pilot number is the Octel System Access Number.
6.0 CONFIGURING OCTEL 350 SYSTEM MANAGEMENT
Configuring the Octel system management menus
o Menu 1.1 - System Parameters
• Type of PBX/CO: 3 - #1AESS/SMDI, Full Duplex
• ACP Used for Integration: answer Y if using ACP Integration method. Answer N if using Direct SMDI Integration method.
o Menu 4.1 - Port Assignments
• Extension/Phone No.: It is important that this column contain the nine-digit number associated with each link, defined as LLGGGMMMM:
LL = physical link number (01-02*)
GGG = message desk number (001-063)
MMMM = terminal number (0001-2047)
* If ACP Integration is being used, up to 16 SMDI links are possible, numbered 01 to 16.
For direct integrations, the physical link number corresponds with the actual connector on the distribution board used to make the connection. See Figure 7 and Table 2.
For ACP Integrations, enter the link number assigned to each serial port. The assignments are labeled on the ACP board. See Figure 6 and Table 3.
• Enter the message desk number assigned by the PBX. For the LTNs associated with each link, number them 0001, 0002, 0003, etc. Begin again at 0001 for each link.
All nine digits must be entered. Each entry must be unique. The use of the physical link number, however, allows redundant message desk/terminal number coordinates to be used as long as they are spread across separate links.
For example, an Octel 350 is being integrated with two SL100 switches. Switch #1 has a six-member multiline hunt group connecting to the Octel 350 ports 1A through 1F, and the SMDI link connects to the main distribution board connector J44. Switch #2 has a six-member multiline hunt group connecting to the Octel 350 ports 1G through 1L, and the SMDI link connects to the main distribution board connector J43. Both groups use the same message desk number (001). See Table 4 for Menu 4.1 entries for this example.
NOTE: If the port configuration is ever changed, i.e., additional ports and/or SMDI links are added, the appropriate fields in Menu 4 must be updated. Any time the Extension/Phone No. field in Menu 4.1 is changed, the affected integration link must be reset in Menu 6.5.5.
• Line Type: 35 loop start or
52 ground start
• M column: Enter N for all ports. Entering Y for any port might cause message-waiting errors.
o Menu 4.3 - RS232 Message Waiting:
• Special RS232 Message Waiting: set to Y
o Menu 6.1 - Dialing Parameters
• Flash On-hook time: 500 milliseconds
• Pause Time: 1000 milliseconds
• Dialing Sequence to Transfer a Call: FPPN
• Dialing Sequence to Reconnect a Call:
Ring no answer: FF Busy: FF
NOTE: Verify that these dialing sequences match for all PBXs applicable to your installation.
o Menu 6.3 - Define CPU Serial Channels
• For each configurable serial channel (channels 1 and 2) to be used for direct integration, assign channel type 3 - Direct Integration.
When “Direct Integration” is chosen for a serial channel configuration, you will need to program menu 6.5.2 for each link. (See bullet on Menu 6.5.)
• If ACP integration is being used, configure the integration links in Menu 6.5. ACP integration links do not use CPU serial channels and so do not require programming in Menu 6.3.
NOTE: The Octel 350 must be rebooted to apply any changes to serial channel parameters in Menu 6.3.
¨ Menu 6.5 - Integration Link Management
Link Number: (1-3 or 1-16 with ACP)
Link Name: (up to 20 characters)
Type of Switch to which the System is Integrated: 3 - 1A ESS/SMDI, Full Duplex
Baud Rate: 0 - 1200 Baud (see note 2)
Bits: 0 - 7 Data Bits
Number of Stop Bits: 0 - 1 Stop Bits
Parity (None/Odd/Even): 2 - Even Parity
XON/XOFF: 1 - Ignore XON/XOFF
Carrier Detect: 1 - Carrier Detect Not Used
Extension to Check SMDI Message Waiting: 0000
Max. Msg. Waiting Operations per second: 1
Switch Number to which this Link is Associated:
SMDI link down alarm threshold counter: 1
NOTE: After any changes are made in Menu 6.5.2, reset the affected integration link using Menu 6.5.5.
NOTE 2: Octel can support the link at 9600 Baud, however the Central Office must match the baud rate of the Octel.
o Menu 8/9.1 - Mailbox Profile
• Subscriber’s Extension : If the subscriber is allowed to have message waiting, enter all seven digits of his or her phone number in this entry.
• Message Waiting : Enter Yes only for valid extensions on the switch configured for MWI
• SMDI Link Number : Enter the physical link number of the SMDI link, which is associated with the subscriber.
7.0 CONNECTING THE ANALOG VOICE CHANNELS
Connecting analog voice channels
o Each Analog TIC (ATIC) supports 12 ports and connects to the PBX via a single cable. The first port uses the first pairs of conductors (1,26), the second port uses the second pair (2,27), etc. For a detailed description of the pinout of the ATIC, refer to the Octel 350 Service Manual.
o Physically connect the lines used for the voice path between the SL100 and the Octel 350. The voice lines are connected to the switch using customer-supplied cables, which terminate on the main backplanes of the Octel 350. See Figures 1 and 2.
7.1 CABLING NOTES
• When a system management terminal is connected to one of the configurable serial channels (J44 & J43) or to the secondary SMT channel (J46), a null modem adapter must be installed and supplied by the customer.
• If modems are not used in the installation, a null modem must be installed on the end of the cable connected to the PBX. See Figure 3 for proper wiring of the null modem connector.
7.2 CONNECTING THE SMDI LINKS USING DIRECT INTEGRATION METHOD
Connecting the serial channel using direct integration
The main distribution board has four serial channels: J44 (channel 1), J43 (channel 2), J46 (channel 3), and J50 (channel 4). Channels 1 and 2 are configurable as either SMDI links or system management (SMT) channels. See Figure 4. A maximum of two SMDI links can be directly connected to the main distribution board.
Channels 3 and 4 are not configurable; channel 4 is for the primary SMT/local service and channel 3 is for a secondary SMT. Channels 1, 2, and 3 require a null modem to support an SMT. Channel 4 does not require a null modem.
o The arrangement chosen for the serial ports must be configured within the Octel 350 platform using menu 6.3 - Serial Channel Parameters.
o Physically connect the SMDI links to the Octel 350 platform using the DB-25 data cables. Connect each cable to the distribution board located on the back of the Octel 350. The end of the cable with the right-angle DB-25 connector is connected to the main distribution board. See Figure 4.
7.3 CONNECTING THE SERIAL CHANNELS USING ACP INTEGRATION (ACP MSA) METHOD
Connecting the serial channels using ACP integration
The ACP provides up to 16 SMDI link connections, as shown below in Figure 5.
o For ACP, the MSA (Multiple Switch Access) software option must be enabled. This option is listed in Menu 13.7 as “ACP Integration.” Verify that it is set.
o Physically connect the SMDI links to the ACP I/O distribution board installed on the Octel 350 platform using the DB-25 data cables. Connect each cable to the appropriate channel on the ACP I/O distribution board located on the back of the Octel 350. See Figure 6. Use the channels labeled ‘Integration’. The end of the cable with the right-angle DB-25 connector is connected to the ACP I/O distribution board. Software configuration information is included in section 6.0.
7.4 TESTING THE INSTALLATION
Testing the installation when completed
o Create two Octel 350 mailboxes associated with two test extensions. Record a name and personal greeting for each mailbox.
o System forward one test extension to the Octel 350 System Access Number.
o Using one test extension, call the other test extension. You should hear the personal greeting.
o Leave a message. Verify that message-waiting indication turns on.
o Verify that return-to-operator works properly.
o Call the Octel 350 from a test extension. You should immediately hear the recorded name and be asked to enter your password.
o Review the message in the mailbox. Verify the direct reply feature works by pressing 8 at the end of the message.
o Delete the message. Verify that message-waiting indication turns off.
8.0 CONSIDERATIONS
Important notes regarding this integration
8.1 At software levels BCS 26 and below, extensions on the SL100 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 Octel system. 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 SL100 will re-ring the transferring party and the transfer will not be completed. MSL03 or higher does allow calls to be directly transferred to the Octel 350 Server.
8.2 If you are using loop-start station appearances, the Cut-off on Disconnect (COD) feature must be programmed for proper disconnect signaling. The programming is covered in section 5.0 of this note. If this feature is not available on your PBX, ground-start lines are recommended for immediate disconnect. If loop-start lines are used, users might hear silence or “Please hang up and dial again” recorded at the end of messages.
8.3 For proper disconnect, a PBX patch must be removed. The patch #RPG50A24 prevents the SL100 from providing the required cutoff for disconnect supervision. This patch if installed on the SL100 must be removed.
8.4 In order to use the 1X67FA card, you must enable Patch #DDK14A29 on the SL100. (Later software might incorporate the patch. Check with your Nortel representative.) The 1X67FA card transmits data at multiple baud rates. The voice module’s RS-232 link accepts SMDI messages at 1200 baud only.
8.5 The decibel level of the analog lines that connect to the Octel 350 should be a minimum of -5.5 db or else call volume might be insufficient.
8.6 The reply to internal telephone-answering message feature may require greater mailbox length. The PBX sends a seven-digit calling party ID over the RS-232 link to the Octel system when the caller is located on the same switch, whether or not she/he is a subscriber. The Octel voice module interprets this as a call from another subscriber, attempts to match a mailbox number. If successful, the recipient is allowed to mistakenly reply to the message. To prevent subscribers from inadvertently replying to messages not sent by another subscriber, system managers have two choices. Menu 1, part 1, option “Sender ID used for Telephone Answering” should be set to “1 - Outside Caller,” which will disable the automatic reply feature for telephone-answering messages. Otherwise, the mailbox length defined in the system must be expanded to guarantee uniqueness.
8.7 If the SMDI I/O port on the SL100 is located more than 50 feet from the Octel 350 system, data sets are required.
8.8 Nortel announced the support of NMS (Network Message Service Software), however Octel must validate which features are supported in this environment.
©2001 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.
1001 Murphy Ranch Road
Milpitas, CA 95035-7912
(408) 321-2000
Ken Means
MESSAGE WAITING SET/CLEAR)