Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NEC 2400 to Octel 350 1
- Thread starter JustMack
- Start date
-
1
- #2
You would setup the T-1 in the NEC as analog ports (stations)
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
This is the T-1 config note for Octel 350 and NEC 2400.
Octel 350
Message Server
Configuration Note 4015 - Rev B (3/01)
NEC NEAX 2400 IMS with Series 4000, 4100, 4200 Software
1.0 METHOD OF INTEGRATION
With RS-232 integration, call information is transmitted over a digital RS-232 link between the PBX and the Octel system
With RS-232 integration, call information is transmitted over a digital RS-232 link between the PBX and the Octel system. Voice communications are provided by a separate path created by analog lines on the PBX that connect to the Octel system. When an incoming call is received, it is accompanied by a digital message from the PBX containing call information. The Octel system then answers the call and plays the appropriate greeting. To set or cancel message-waiting notification, the Octel system sends a digital message over the RS-232 link to the PBX.
2.0 OCTEL 350 ORDERING INFORMATION
Octel 350 ordering information
* 24-Port T1 TICs or 12-port Analog TICs
* Disk drives (SCSI drives require a minimum of Release 5)
* RS-232 integration software
* Asynchronous Communication Processor (ACP), optional
* Minimum Octel Software: Release 1.5
* Cables for RS-232 connections
NOTE: Determine whether direct integration or Asynchronous Communications Processor (ACP) integration will be used. To do so, count the number of SMDI 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
NOTE: One system-management-terminal channel shares CPU access with the Remote Diagnostic Analysis Center (RDAC) modem channel. For contention-free system management, one of the additional configurable serial channels must be used.
3.0 PBX HARDWARE REQUIREMENTS
PBX hardware requirements
* Standard, single-line extension appearances, one per Octel port, and one per system for remote service access - see Section 8.2
* One I/O-02 port for RS-232 data link with CA-1 cable
* 80 Vdc power supply (for message waiting on single lines)
* Male-amphenol cable with right-angle connector, one per TIC
3.1 PBX SOFTWARE REQUIREMENTS
PBX software requirements
* Software Series 4000:
level 4003 (MMG), level 4004 (UMG)
Software Series 4100:
level 4103 (MMG), level 4104 (UMG)
Software Series 4200:
level 4203 version 5 or 6 (MMG)
level 4204 version 5 or 6 (UMG) - see Section 8.4
* Feature 2 activated
4.0 SUPPORTED FEATURES
Supported features
* System forwarding to personal greeting
- ring-no-answer
* Station forwarding to personal greeting
- busy
- ring-no-answer
- all calls
* Message-waiting notification
- lights
- LCD display (if available)
* Multiple return-to-operator (to stations only, below 4200 software)
* Automated attendant
* Outcalling
* Direct call
* Multiple personal greetings (Release 4 and above)
* Call Sender (Release 4 and above)
* Personal greeting of original-called party on multiple-call forward (4200 software only)
* Multiple RS-232 links
4.1 SUPPORTING MULTIPLE PBXS WITH ONE OCTEL 350
Supporting multiple PBXs with one Octel 350
To support multiple IMGs, MMGs, and/or UMGs with one Octel system, the following software and hardware is required:
* Application Disk
* SIM - level 5201
* IMG - level 4202, version 5.2
* MMG - level 4203, version 5.2
* UMG - level 4202, version 5.2
* CCIS link to all PBXs
o With Series 4200 Software (level 4203/4204, version 5.2/5.5), an MMG or UMG must be used as the hub, i.e., must be directly connected to the Octel system. Integration with the IMG (level 4202, version 5.2) can be supported only if the IMG is a remote switch. With Series 5200 Software, an IMG or SIM can be used as the hub or a remote PBX. An NEC 1400 can be supported as a remote PBX only, at 550 software level or higher.
o In a networked environment, all of the remote PBXs receive full integration: forward to personal greeting, message-waiting, and multiple return-to-operator. Automated attendant can be used to transfer callers to extensions on the remote PBXs. The direct call feature and the automatic reply to internal telephone- answering message feature are not supported on the remote PBXs.
The optional NEC applications disk (series 4200 software only)
4.2 THE OPTIONAL NEC APPLICATIONS DISK (SERIES 4200 SOFTWARE ONLY)
o To support integration on external calls that are transferred to stations forwarded to the voice module, and to support unsupervised transfers to the attendant console, the applications disk must be loaded on the NEC PBX. The required software level is either 4203, version 5.32, or 4204, version 5.6. These features require one of the following application floppy disks to be loaded:
8" version; NEAX2400 4200 APPL FD-B Disk (C1.1)
Stock # 240773
5.25" version: NEAX2400 4200 APPL FD-C Disk 1 (D1.1) Stock #242773
NOTES:
§ Unsupervised transfers to the attendant console cannot be performed with level 4000, 4100, or 4200, version 6 software. As a possible alternative, use an extension that ring-no-answer forwards to the console as a zero-out target.
§ If the attendant does not answer an unsupervised transfer within the predetermined time set for Transfer Call Recall, the call will be sent back to the Octel voice module and the caller will hear the general system greeting.
§ Recorder tone will be sent to the extension attempting to transfer a call to an attendant in Night Mode, unless a station is programmed in the NEC as the Attendant Night Transfer Target.
5.0 CONFIGURING THE PBX DATA LINK
Configuring the PBX data link
o Each NEC PBX can support up to four IO02 cards. Each IO02 card supports two I/O ports. Locate an available IO02 port that will be used for the voice-mail data link. Assign it as a Feature 2 MCI port through the ASYD command.
o Verify that the guard timer is set to zero for the MCI port through the ASYD command.
o Locate the 6 sets of dip switches on the card. The switches are identified as SW0, SW01, SW02, SW11, SW12, and SW13.
o Switch SW0 tells the PBX which I/O card (of four) it is. Verify that the switches are set according to Figure 1 for the voice mail I/O port.
o Port 1 on a given IO02 card is controlled by switches SW01 and SW02. Port 2 is controlled by switches SW11 and SW12. All four switches have 8 settings each.
The settings for SW01 should be as follows: Settings 1,2, and 3 set to off, on, off for a baud rate of 9600 BPS. Setting 4 is set to on for Parity Bit valid. Setting 5 is set to on for odd parity. Setting 6 is set to on for 7 bits. Setting 7 is set to off for 2 stop bits. Setting 8 is set to on for Send Side FIFO is 1 byte. See Figure 2.
NOTE: If using Port 2 on the IO02 card, configure the settings on SW11 the same as above.
The settings for SW02 should be as follows: Setting 1 is set to on for PB signal not provided. Setting 2 is set to on for DRT. Setting 3 is set to off for DSR is provided. Setting 4 is set to off for CD is provided. Settings 5,6, and 7 are set to on for CS, CI, and PB not provided. Setting 8 is not used. See Figure 3.
o Verify that all four settings on SW12 are off. The card is now configured for RS-232 operation.
NOTE: If the PBX is taken out of service and restarted, the MCI port might not operate. If this is the case, unplug the RS-232 link from the Octel voice module, then have the PBX vendor reset the system processor.
5.2 CONFIGURING THE VOICE LINES IN THE NEC PBX
Configuring the voice lines in the NEC PBX
o Assign single-line ports for the Octel 350 system in the ASDT (Assign Station Data Table) with TEC=3.
o Assign a Service Feature Class (SFC) to those ports. The SFC should have Service Feature Index 48, Distinctive Ringing, set to 0. This will disable Distinctive Ringing. If this feature is enabled, problems with ringing detection will occur.
o Assign the Octel ports to a UCD group using the ASHU command.
The pilot number of the above UCD group is the Octel 350 Access Number. It is used by subscribers to call the Octel system to retrieve their messages. It is also used by subscribers to forward their phones to the Octel system.
o Create a single-line extension in the PBX. Set call forward all-calls to the pilot number of the UCD group. Do not create a voice mailbox for this extension. This extension is used as the Octel Transfer Target Number. Any call to be transferred to this number to the voice module should be transferred to this number so callers will hear the general system greeting instead of the direct call greeting.
5.3 CONFIGURING THE PBX TO SUPPORT MORE THAN 20 VOICE MAIL PORTS
The NEC 2400 software series 4200 MMG and UMG support one UCD group of 20 members which can overflow to a second UCD group of 20 members. Only one overflow group is allowed for a total of 40 ports. 4000 and 4100 software do not support UCD overflow.
Configuring the PBX to support more than 20 voice mail ports
o If more than 40 integrated ports are required on a PBX with 4200 software, or if more than 20 integrated ports are required with Series 4000 or 4100 software, create additional UCD groups with the required number of ports. Configuring additional UCD groups without overflow capability requires splitting subscribers between two different UCD groups and two different access numbers. Only one MCI link is required.
o To configure a UCD group to overflow, use the AUOG (Assign UCD Overflow Group) command.
Configuring Octel 350 system management
6.0 CONFIGURING THE OCTEL 350
¨ Menu 1.1: System Parameters
* Type of PBX: D-NEC 2400
* ACP Used for Integration: answer Y if using ACP Integration method. Answer N if using Direct Integration method.
¨ Menu 2:
§ The NEC PBX at 4000 and 4100 software does not support unsupervised transfers to the attendant console, or "0". Change all entries in these menu from "0" to a valid extension number.
¨ Menu 4.1:
Extension/Phone No.: It is important that this column contain the number associated with each link, defined as follows: LLMMMM
where,
LL = Physical link number (01-02)
MMMM = Extension number of the port
*If ACP Integration is being used, up to 16 data links are possible, numbered 01 to 16.
§ The physical link number corresponds with the actual connector on the distribution board used to make the connection. See Figure 9 and Table 2 for direct integrations.
For ACP Integrations, enter the link number assigned to each serial port. The assignments are labeled on the ACP board. See Figure 11 and
Table 3.
* Enter the extension number of each port assigned on the PBX.
* For example, an Octel 350 is being integrated with two PBXs. PBX #1 has a six-member multiline hunt group connecting to the Octel 350 ports 1A through 1F, and the MCI link connects to the main distribution board connector J44. PBX #2 has a six-member multiline hunt group connecting to the Octel 350 ports 1G through 1L, and the MCI link connects to the main distribution board connector J43. Both fractional T1 trunks were combined into a single T-span which was physically connected to the appropriate amphenol connector on the Octel 350 first frame main backplane. See Table 4 for Menu 4.1 entries for this example.
If the port configuration is ever changed (e.g., additional ports and/or MCI links are added), the appropriate fields in Menu 4 must be updated.
* Line type: for integrated ports utilizing T1 channels:
121 for integrated T1 ports
* Line type: for integrated ports utilizing analog lines:
39 for integrated ports
4 for non-integrated ports
* M column : Enter N for all ports. Entering Y for any port might cause message-waiting errors.
NOTE: 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.
¨ Menu 4.2:
* Special RS-232 Message-Waiting set to 'Y'
¨ Menu 6.1 - Dialing Parameters:
* Flash On-hook time: 500 milliseconds
* Pause Time: 1000 milliseconds
* Dialing Sequence to Transfer a Call: FPN
* Dialing Sequence to Reconnect a Call: FP
NOTE: Verify that these dialing sequences match for all PBXs/COs applicable to your installation.
¨ Menu 6.3 - Define CPU Serial Channels:
NOTES
§ Channel 4 is always used for service/RDAC and is not configurable.
§ When a system management terminal is connected to one of the configurable serial channels, a null modem adapter must be installed.
o 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.)
o If ACP integration is being used, configure the integration links in Menu 6.5. ACP integration links do not use CPU serial channels, and therefore, do not require programming in Menu 6.3
NOTE: The Octel 350 must be rebooted to apply any changes to serial channel parameters.
¨ Menu 6.5 - Integration Link Management:
* In menu 6.5, for integration link select "5 - NEC 2400, MMG/MCI." (Refer to Table 3 to verify link numbers when using ACP integration.) Use the following default parameters:
Baud Rate: 9600
Number of Data Bits: 7
Number of Stop Bits: 2
Parity: Odd
XON/XOFF: Not Used
Carrier Detect: Carrier Detect Not Used
Extension to Check SMDI Message-Waiting: blank
NOTE: After any changes are made in Menu 6.5.2, reset the affected integration link(s) using Menu 6.5.5.
¨ Menu 8/9:
* "Subscriber's Extension Number": If the subscriber is allowed to have message-waiting, enter his or her extension number in this entry.
* Link Number: Assign the appropriate integration link number for the subscriber.
7.0 CONNECTING T1 VOICE CHANNELS
Connecting T1 voice channels
This section applies only if your installation is using T1 TICs within the Octel 350 system.
o During installation of the Octel 350, the hardware configuration of the T1 TIC must be set. This is performed by correctly setting the 8 switches contained within the dip switch device (located at U2U) on each TIC. The dip switch device informs the T1 TIC of the distance between the Octel 350 and the Digital Cross-Connect (DSX) or the Customer Service Unit (CSU). Table 5 defines the valid switch settings.
o Each T1 TIC in the Octel 350 supports 24 T1 channels. Each TIC connects to the PBX via a single cable.
o Physically connect the T1 lines between the PBX and the Octel 350. The customer terminates its cabling directly to the Octel 350 main backplane. The T-span connections to the Octel 350 main backplanes are shown in Figures 4 and 5. The customer must provide a cable terminated with a male amphenol-type connector for each T1 TIC connection. The T1 pinout for the Octel 350 main backplane connector is represented in Figure 6. (Transmit/receive reference is the Octel 350 connector.)
NOTE: Amphenol pinout conforms to the RJ48H standard.
7.1 CONNECTING ANALOG VOICE CHANNELS
Connecting analog voice channels
If the Octel 350 is using the analog TIC for integration, follow these instructions:
o Each analog TIC supports 12 ports. Each analog TIC connects to the PBX via a single cable. The first port uses the first pair of conductors (1, 26), the second port uses the second pair (2, 27), etc.
o Physically connect the lines used for the voice path between the PBX and the Octel 350. The voice lines are connected to the PBX using customer-supplied cable which terminate on the main backplanes within the Octel 350 frames. See Figures 7 and 8. The cables should have male amphenol-type connectors.
7.2 CONNECTING THE RS-232 LINK USING DIRECT INTEGRATION
Connecting the RS-232 link using direct integration
The I/O distribution board has four serial channels: J44 (channel 1), J43 (channel 2), J46 (channel 3), and J50 (channel 4). Each of the first two serial channels are configurable as either direct RS-232 integration links or system management channels. See Figure 9. Either of these two channels (J44, J43,) when used for system management terminals must connect to a null modem. Channel 4 (J50) is for a local, primary system management terminal only and does not require a null modem. Channel 3 (J46) is for secondary system management.
o Physically connect the data link to the Octel 350 platform using the DB-25 data cables shipped with the Octel system. Connect each cable to the I/O 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 9.
7.3 CONNECTING THE RS-232 LINK USING ACP INTEGRATION
The ACP provides up to 16 RS-232 data link connections, as shown in Figure 10.
o If an ACP is required for integration, 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 For ACP integrations, the DB-25 connectors should be fastened to the ACP board. Use only the ACP channels labeled 'integration'. See Figure 11. The integration adapter board should be connected to the ACP board with the modular jacks facing up. Lock the DB-25 connections in place by moving the slide latch down.
7.3 TESTING THE INSTALLATION
Testing the installation
o Create two mailboxes associated with two test extensions.
Record a name and a 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. 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 that the direct reply feature works by pressing 8 at the end of the message.
o Delete the message. Verify that the message-waiting indicator turns off.
8.0 CONSIDERATIONS/ALTERNATIVES
Important notes regarding this integration
8.1 NEC uses the last digit of the software level to designate the PBX type. The first descriptor for an NEC PBX is the family name, the second is a software series. It is important to identify the family name and the software series; PBX/Octel functionality is affected based on the software series; not all integration features are available at all software levels. Where exceptions exist, they are noted in sections 4.0 and 8.0 of the configuration note.
The NEC uses the last digit of the software level to designate the PBX type. The designations are as follows: 1 = SIM, 2 = IMG, 3 = MMG, and 4 = UMG. For example, software level 4202 is the 4200 series of software for an IMG.
8.2 Series 4000, 4100 and 4200 software are not available on the SIM.
4200 Software is available on the IMG, but it does not support MCI software, required for integration. 5200 software is required to support a direct integration on either the SIM or IMG. Refer to the 5200 software configuration note for details.
8.3 An IMG at a minimum of 4200 level software, version 5.2, in a CCIS network will receive integration as a remote PBX only.
The Octel voice module cannot be directly connected to the IMG at 4200 software. The remote IMG subscribers will receive personal greeting, message-waiting indication, and multiple return-to- operator. The optional application disk is required for remote integration support.
8.4 To support message-waiting display on digital sets, the following is required:
§ 4DLC (Digital Line Circuit) cards must be Issue A9 or higher.
§ 8ELC - (Electronic Line Circuit) card must be Issue A8 or higher.
8.5 To provide the voice paths from the PBX to the Octel 350 on T1 trunks, channel-bank equipment may be required.
Check with the PBX manufacturer. The T1 trunks must be configured with D4 format and the Octel 350 platform will act as the T1 timing slave.
If an Octel 350 is connected to multiple PBXs, a single T1 TIC can support channels from more than one PBX (for example, 20 channels from PBX #1 and 4 channels from PBX#2). Such a configuration requires that multiple fractional T1 trunks be combined into a single trunk that can be connected to the single T1 TIC. Equipment to combine multiple T1 must be provided by the customer.
8.6 When a system management terminal is connected to one of the configurable serial channels, a null-modem adapter must be installed and supplied by the customer. The non-configurable channel, J50, does not require a null modem.
8.7 4000 and 4100 software have the following restrictions:
§ External callers transferred to extensions that are forwarded to the voice module hear system greeting instead of personal greeting. MCI software does not support integration for transferred external callers until Series 4200 software, and requires the optional NEC applications disk.
§ 4000 and 4100 software do not support multiple-call forwarding to personal greeting of the original-called party. At 4000 software, multiple-call forwarding is not permitted. At 4100 software, multiple-call forwarding is allowed, however, last called party ID is retained. At 4200 software, this issue is resolved.
§ Series 4000 and 4100 software support a maximum of 20 members in a single UCD group. No UCD overflow is available until 4200 software.
§ At 4000 and 4100 software, unsupervised transfers to the console are not supported. Calls will re-ring the transferring station. A possible solution is to transfer calls to an extension that ring-no-answer forwards to the console. Unsupervised transfers to the attendant are supported with 4200 software and requires the optional NEC applications disk.
§ At 4000 and 4100 software, the attendant cannot be programmed to overflow.
§ Series 4200 software requires the optional NEC applications disk to support the following features:
- Integrations on external calls that are transferred to stations the forward to the Octel voice module.
- Unsupervised transfers to the attendant console.
Refer to section 4.2 of the note for details.
8.8 Supported NEC line cards are the 16LC-G, the 16LC-GB, the 16LC-GG, and the 16LC-Q. The 16LC-Q card provides a 128-194 millisecond open on disconnect which is not sufficient for the USL TIC to detect. However, the PBX will send a fast-busy signal for disconnect which the Octel system does recognize. The 16LC-AD card is a ?24 Vdc line card which is incompatible with the USL TIC and, therefore, is not supported.
8.9 NEC's open architecture requires software series 4200, version 6. This software will not support unsupervised transfers. In addition, if the customer has more than six digits in an extension number, contact Sales Engineering for additional programming details.
8.10 "Expanded MCI" is not currently supported on the Octel 350. "Expanded MCI" is MCI that has been increased from six (6) to eight (8) digits. "Expanded MCI" should only be necessary for centralized voice mail systems that are operating within a CCIS 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
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Octel 350
Message Server
Configuration Note 4015 - Rev B (3/01)
NEC NEAX 2400 IMS with Series 4000, 4100, 4200 Software
1.0 METHOD OF INTEGRATION
With RS-232 integration, call information is transmitted over a digital RS-232 link between the PBX and the Octel system
With RS-232 integration, call information is transmitted over a digital RS-232 link between the PBX and the Octel system. Voice communications are provided by a separate path created by analog lines on the PBX that connect to the Octel system. When an incoming call is received, it is accompanied by a digital message from the PBX containing call information. The Octel system then answers the call and plays the appropriate greeting. To set or cancel message-waiting notification, the Octel system sends a digital message over the RS-232 link to the PBX.
2.0 OCTEL 350 ORDERING INFORMATION
Octel 350 ordering information
* 24-Port T1 TICs or 12-port Analog TICs
* Disk drives (SCSI drives require a minimum of Release 5)
* RS-232 integration software
* Asynchronous Communication Processor (ACP), optional
* Minimum Octel Software: Release 1.5
* Cables for RS-232 connections
NOTE: Determine whether direct integration or Asynchronous Communications Processor (ACP) integration will be used. To do so, count the number of SMDI 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
NOTE: One system-management-terminal channel shares CPU access with the Remote Diagnostic Analysis Center (RDAC) modem channel. For contention-free system management, one of the additional configurable serial channels must be used.
3.0 PBX HARDWARE REQUIREMENTS
PBX hardware requirements
* Standard, single-line extension appearances, one per Octel port, and one per system for remote service access - see Section 8.2
* One I/O-02 port for RS-232 data link with CA-1 cable
* 80 Vdc power supply (for message waiting on single lines)
* Male-amphenol cable with right-angle connector, one per TIC
3.1 PBX SOFTWARE REQUIREMENTS
PBX software requirements
* Software Series 4000:
level 4003 (MMG), level 4004 (UMG)
Software Series 4100:
level 4103 (MMG), level 4104 (UMG)
Software Series 4200:
level 4203 version 5 or 6 (MMG)
level 4204 version 5 or 6 (UMG) - see Section 8.4
* Feature 2 activated
4.0 SUPPORTED FEATURES
Supported features
* System forwarding to personal greeting
- ring-no-answer
* Station forwarding to personal greeting
- busy
- ring-no-answer
- all calls
* Message-waiting notification
- lights
- LCD display (if available)
* Multiple return-to-operator (to stations only, below 4200 software)
* Automated attendant
* Outcalling
* Direct call
* Multiple personal greetings (Release 4 and above)
* Call Sender (Release 4 and above)
* Personal greeting of original-called party on multiple-call forward (4200 software only)
* Multiple RS-232 links
4.1 SUPPORTING MULTIPLE PBXS WITH ONE OCTEL 350
Supporting multiple PBXs with one Octel 350
To support multiple IMGs, MMGs, and/or UMGs with one Octel system, the following software and hardware is required:
* Application Disk
* SIM - level 5201
* IMG - level 4202, version 5.2
* MMG - level 4203, version 5.2
* UMG - level 4202, version 5.2
* CCIS link to all PBXs
o With Series 4200 Software (level 4203/4204, version 5.2/5.5), an MMG or UMG must be used as the hub, i.e., must be directly connected to the Octel system. Integration with the IMG (level 4202, version 5.2) can be supported only if the IMG is a remote switch. With Series 5200 Software, an IMG or SIM can be used as the hub or a remote PBX. An NEC 1400 can be supported as a remote PBX only, at 550 software level or higher.
o In a networked environment, all of the remote PBXs receive full integration: forward to personal greeting, message-waiting, and multiple return-to-operator. Automated attendant can be used to transfer callers to extensions on the remote PBXs. The direct call feature and the automatic reply to internal telephone- answering message feature are not supported on the remote PBXs.
The optional NEC applications disk (series 4200 software only)
4.2 THE OPTIONAL NEC APPLICATIONS DISK (SERIES 4200 SOFTWARE ONLY)
o To support integration on external calls that are transferred to stations forwarded to the voice module, and to support unsupervised transfers to the attendant console, the applications disk must be loaded on the NEC PBX. The required software level is either 4203, version 5.32, or 4204, version 5.6. These features require one of the following application floppy disks to be loaded:
8" version; NEAX2400 4200 APPL FD-B Disk (C1.1)
Stock # 240773
5.25" version: NEAX2400 4200 APPL FD-C Disk 1 (D1.1) Stock #242773
NOTES:
§ Unsupervised transfers to the attendant console cannot be performed with level 4000, 4100, or 4200, version 6 software. As a possible alternative, use an extension that ring-no-answer forwards to the console as a zero-out target.
§ If the attendant does not answer an unsupervised transfer within the predetermined time set for Transfer Call Recall, the call will be sent back to the Octel voice module and the caller will hear the general system greeting.
§ Recorder tone will be sent to the extension attempting to transfer a call to an attendant in Night Mode, unless a station is programmed in the NEC as the Attendant Night Transfer Target.
5.0 CONFIGURING THE PBX DATA LINK
Configuring the PBX data link
o Each NEC PBX can support up to four IO02 cards. Each IO02 card supports two I/O ports. Locate an available IO02 port that will be used for the voice-mail data link. Assign it as a Feature 2 MCI port through the ASYD command.
o Verify that the guard timer is set to zero for the MCI port through the ASYD command.
o Locate the 6 sets of dip switches on the card. The switches are identified as SW0, SW01, SW02, SW11, SW12, and SW13.
o Switch SW0 tells the PBX which I/O card (of four) it is. Verify that the switches are set according to Figure 1 for the voice mail I/O port.
o Port 1 on a given IO02 card is controlled by switches SW01 and SW02. Port 2 is controlled by switches SW11 and SW12. All four switches have 8 settings each.
The settings for SW01 should be as follows: Settings 1,2, and 3 set to off, on, off for a baud rate of 9600 BPS. Setting 4 is set to on for Parity Bit valid. Setting 5 is set to on for odd parity. Setting 6 is set to on for 7 bits. Setting 7 is set to off for 2 stop bits. Setting 8 is set to on for Send Side FIFO is 1 byte. See Figure 2.
NOTE: If using Port 2 on the IO02 card, configure the settings on SW11 the same as above.
The settings for SW02 should be as follows: Setting 1 is set to on for PB signal not provided. Setting 2 is set to on for DRT. Setting 3 is set to off for DSR is provided. Setting 4 is set to off for CD is provided. Settings 5,6, and 7 are set to on for CS, CI, and PB not provided. Setting 8 is not used. See Figure 3.
o Verify that all four settings on SW12 are off. The card is now configured for RS-232 operation.
NOTE: If the PBX is taken out of service and restarted, the MCI port might not operate. If this is the case, unplug the RS-232 link from the Octel voice module, then have the PBX vendor reset the system processor.
5.2 CONFIGURING THE VOICE LINES IN THE NEC PBX
Configuring the voice lines in the NEC PBX
o Assign single-line ports for the Octel 350 system in the ASDT (Assign Station Data Table) with TEC=3.
o Assign a Service Feature Class (SFC) to those ports. The SFC should have Service Feature Index 48, Distinctive Ringing, set to 0. This will disable Distinctive Ringing. If this feature is enabled, problems with ringing detection will occur.
o Assign the Octel ports to a UCD group using the ASHU command.
The pilot number of the above UCD group is the Octel 350 Access Number. It is used by subscribers to call the Octel system to retrieve their messages. It is also used by subscribers to forward their phones to the Octel system.
o Create a single-line extension in the PBX. Set call forward all-calls to the pilot number of the UCD group. Do not create a voice mailbox for this extension. This extension is used as the Octel Transfer Target Number. Any call to be transferred to this number to the voice module should be transferred to this number so callers will hear the general system greeting instead of the direct call greeting.
5.3 CONFIGURING THE PBX TO SUPPORT MORE THAN 20 VOICE MAIL PORTS
The NEC 2400 software series 4200 MMG and UMG support one UCD group of 20 members which can overflow to a second UCD group of 20 members. Only one overflow group is allowed for a total of 40 ports. 4000 and 4100 software do not support UCD overflow.
Configuring the PBX to support more than 20 voice mail ports
o If more than 40 integrated ports are required on a PBX with 4200 software, or if more than 20 integrated ports are required with Series 4000 or 4100 software, create additional UCD groups with the required number of ports. Configuring additional UCD groups without overflow capability requires splitting subscribers between two different UCD groups and two different access numbers. Only one MCI link is required.
o To configure a UCD group to overflow, use the AUOG (Assign UCD Overflow Group) command.
Configuring Octel 350 system management
6.0 CONFIGURING THE OCTEL 350
¨ Menu 1.1: System Parameters
* Type of PBX: D-NEC 2400
* ACP Used for Integration: answer Y if using ACP Integration method. Answer N if using Direct Integration method.
¨ Menu 2:
§ The NEC PBX at 4000 and 4100 software does not support unsupervised transfers to the attendant console, or "0". Change all entries in these menu from "0" to a valid extension number.
¨ Menu 4.1:
Extension/Phone No.: It is important that this column contain the number associated with each link, defined as follows: LLMMMM
where,
LL = Physical link number (01-02)
MMMM = Extension number of the port
*If ACP Integration is being used, up to 16 data links are possible, numbered 01 to 16.
§ The physical link number corresponds with the actual connector on the distribution board used to make the connection. See Figure 9 and Table 2 for direct integrations.
For ACP Integrations, enter the link number assigned to each serial port. The assignments are labeled on the ACP board. See Figure 11 and
Table 3.
* Enter the extension number of each port assigned on the PBX.
* For example, an Octel 350 is being integrated with two PBXs. PBX #1 has a six-member multiline hunt group connecting to the Octel 350 ports 1A through 1F, and the MCI link connects to the main distribution board connector J44. PBX #2 has a six-member multiline hunt group connecting to the Octel 350 ports 1G through 1L, and the MCI link connects to the main distribution board connector J43. Both fractional T1 trunks were combined into a single T-span which was physically connected to the appropriate amphenol connector on the Octel 350 first frame main backplane. See Table 4 for Menu 4.1 entries for this example.
If the port configuration is ever changed (e.g., additional ports and/or MCI links are added), the appropriate fields in Menu 4 must be updated.
* Line type: for integrated ports utilizing T1 channels:
121 for integrated T1 ports
* Line type: for integrated ports utilizing analog lines:
39 for integrated ports
4 for non-integrated ports
* M column : Enter N for all ports. Entering Y for any port might cause message-waiting errors.
NOTE: 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.
¨ Menu 4.2:
* Special RS-232 Message-Waiting set to 'Y'
¨ Menu 6.1 - Dialing Parameters:
* Flash On-hook time: 500 milliseconds
* Pause Time: 1000 milliseconds
* Dialing Sequence to Transfer a Call: FPN
* Dialing Sequence to Reconnect a Call: FP
NOTE: Verify that these dialing sequences match for all PBXs/COs applicable to your installation.
¨ Menu 6.3 - Define CPU Serial Channels:
NOTES
§ Channel 4 is always used for service/RDAC and is not configurable.
§ When a system management terminal is connected to one of the configurable serial channels, a null modem adapter must be installed.
o 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.)
o If ACP integration is being used, configure the integration links in Menu 6.5. ACP integration links do not use CPU serial channels, and therefore, do not require programming in Menu 6.3
NOTE: The Octel 350 must be rebooted to apply any changes to serial channel parameters.
¨ Menu 6.5 - Integration Link Management:
* In menu 6.5, for integration link select "5 - NEC 2400, MMG/MCI." (Refer to Table 3 to verify link numbers when using ACP integration.) Use the following default parameters:
Baud Rate: 9600
Number of Data Bits: 7
Number of Stop Bits: 2
Parity: Odd
XON/XOFF: Not Used
Carrier Detect: Carrier Detect Not Used
Extension to Check SMDI Message-Waiting: blank
NOTE: After any changes are made in Menu 6.5.2, reset the affected integration link(s) using Menu 6.5.5.
¨ Menu 8/9:
* "Subscriber's Extension Number": If the subscriber is allowed to have message-waiting, enter his or her extension number in this entry.
* Link Number: Assign the appropriate integration link number for the subscriber.
7.0 CONNECTING T1 VOICE CHANNELS
Connecting T1 voice channels
This section applies only if your installation is using T1 TICs within the Octel 350 system.
o During installation of the Octel 350, the hardware configuration of the T1 TIC must be set. This is performed by correctly setting the 8 switches contained within the dip switch device (located at U2U) on each TIC. The dip switch device informs the T1 TIC of the distance between the Octel 350 and the Digital Cross-Connect (DSX) or the Customer Service Unit (CSU). Table 5 defines the valid switch settings.
o Each T1 TIC in the Octel 350 supports 24 T1 channels. Each TIC connects to the PBX via a single cable.
o Physically connect the T1 lines between the PBX and the Octel 350. The customer terminates its cabling directly to the Octel 350 main backplane. The T-span connections to the Octel 350 main backplanes are shown in Figures 4 and 5. The customer must provide a cable terminated with a male amphenol-type connector for each T1 TIC connection. The T1 pinout for the Octel 350 main backplane connector is represented in Figure 6. (Transmit/receive reference is the Octel 350 connector.)
NOTE: Amphenol pinout conforms to the RJ48H standard.
7.1 CONNECTING ANALOG VOICE CHANNELS
Connecting analog voice channels
If the Octel 350 is using the analog TIC for integration, follow these instructions:
o Each analog TIC supports 12 ports. Each analog TIC connects to the PBX via a single cable. The first port uses the first pair of conductors (1, 26), the second port uses the second pair (2, 27), etc.
o Physically connect the lines used for the voice path between the PBX and the Octel 350. The voice lines are connected to the PBX using customer-supplied cable which terminate on the main backplanes within the Octel 350 frames. See Figures 7 and 8. The cables should have male amphenol-type connectors.
7.2 CONNECTING THE RS-232 LINK USING DIRECT INTEGRATION
Connecting the RS-232 link using direct integration
The I/O distribution board has four serial channels: J44 (channel 1), J43 (channel 2), J46 (channel 3), and J50 (channel 4). Each of the first two serial channels are configurable as either direct RS-232 integration links or system management channels. See Figure 9. Either of these two channels (J44, J43,) when used for system management terminals must connect to a null modem. Channel 4 (J50) is for a local, primary system management terminal only and does not require a null modem. Channel 3 (J46) is for secondary system management.
o Physically connect the data link to the Octel 350 platform using the DB-25 data cables shipped with the Octel system. Connect each cable to the I/O 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 9.
7.3 CONNECTING THE RS-232 LINK USING ACP INTEGRATION
The ACP provides up to 16 RS-232 data link connections, as shown in Figure 10.
o If an ACP is required for integration, 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 For ACP integrations, the DB-25 connectors should be fastened to the ACP board. Use only the ACP channels labeled 'integration'. See Figure 11. The integration adapter board should be connected to the ACP board with the modular jacks facing up. Lock the DB-25 connections in place by moving the slide latch down.
7.3 TESTING THE INSTALLATION
Testing the installation
o Create two mailboxes associated with two test extensions.
Record a name and a 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. 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 that the direct reply feature works by pressing 8 at the end of the message.
o Delete the message. Verify that the message-waiting indicator turns off.
8.0 CONSIDERATIONS/ALTERNATIVES
Important notes regarding this integration
8.1 NEC uses the last digit of the software level to designate the PBX type. The first descriptor for an NEC PBX is the family name, the second is a software series. It is important to identify the family name and the software series; PBX/Octel functionality is affected based on the software series; not all integration features are available at all software levels. Where exceptions exist, they are noted in sections 4.0 and 8.0 of the configuration note.
The NEC uses the last digit of the software level to designate the PBX type. The designations are as follows: 1 = SIM, 2 = IMG, 3 = MMG, and 4 = UMG. For example, software level 4202 is the 4200 series of software for an IMG.
8.2 Series 4000, 4100 and 4200 software are not available on the SIM.
4200 Software is available on the IMG, but it does not support MCI software, required for integration. 5200 software is required to support a direct integration on either the SIM or IMG. Refer to the 5200 software configuration note for details.
8.3 An IMG at a minimum of 4200 level software, version 5.2, in a CCIS network will receive integration as a remote PBX only.
The Octel voice module cannot be directly connected to the IMG at 4200 software. The remote IMG subscribers will receive personal greeting, message-waiting indication, and multiple return-to- operator. The optional application disk is required for remote integration support.
8.4 To support message-waiting display on digital sets, the following is required:
§ 4DLC (Digital Line Circuit) cards must be Issue A9 or higher.
§ 8ELC - (Electronic Line Circuit) card must be Issue A8 or higher.
8.5 To provide the voice paths from the PBX to the Octel 350 on T1 trunks, channel-bank equipment may be required.
Check with the PBX manufacturer. The T1 trunks must be configured with D4 format and the Octel 350 platform will act as the T1 timing slave.
If an Octel 350 is connected to multiple PBXs, a single T1 TIC can support channels from more than one PBX (for example, 20 channels from PBX #1 and 4 channels from PBX#2). Such a configuration requires that multiple fractional T1 trunks be combined into a single trunk that can be connected to the single T1 TIC. Equipment to combine multiple T1 must be provided by the customer.
8.6 When a system management terminal is connected to one of the configurable serial channels, a null-modem adapter must be installed and supplied by the customer. The non-configurable channel, J50, does not require a null modem.
8.7 4000 and 4100 software have the following restrictions:
§ External callers transferred to extensions that are forwarded to the voice module hear system greeting instead of personal greeting. MCI software does not support integration for transferred external callers until Series 4200 software, and requires the optional NEC applications disk.
§ 4000 and 4100 software do not support multiple-call forwarding to personal greeting of the original-called party. At 4000 software, multiple-call forwarding is not permitted. At 4100 software, multiple-call forwarding is allowed, however, last called party ID is retained. At 4200 software, this issue is resolved.
§ Series 4000 and 4100 software support a maximum of 20 members in a single UCD group. No UCD overflow is available until 4200 software.
§ At 4000 and 4100 software, unsupervised transfers to the console are not supported. Calls will re-ring the transferring station. A possible solution is to transfer calls to an extension that ring-no-answer forwards to the console. Unsupervised transfers to the attendant are supported with 4200 software and requires the optional NEC applications disk.
§ At 4000 and 4100 software, the attendant cannot be programmed to overflow.
§ Series 4200 software requires the optional NEC applications disk to support the following features:
- Integrations on external calls that are transferred to stations the forward to the Octel voice module.
- Unsupervised transfers to the attendant console.
Refer to section 4.2 of the note for details.
8.8 Supported NEC line cards are the 16LC-G, the 16LC-GB, the 16LC-GG, and the 16LC-Q. The 16LC-Q card provides a 128-194 millisecond open on disconnect which is not sufficient for the USL TIC to detect. However, the PBX will send a fast-busy signal for disconnect which the Octel system does recognize. The 16LC-AD card is a ?24 Vdc line card which is incompatible with the USL TIC and, therefore, is not supported.
8.9 NEC's open architecture requires software series 4200, version 6. This software will not support unsupervised transfers. In addition, if the customer has more than six digits in an extension number, contact Sales Engineering for additional programming details.
8.10 "Expanded MCI" is not currently supported on the Octel 350. "Expanded MCI" is MCI that has been increased from six (6) to eight (8) digits. "Expanded MCI" should only be necessary for centralized voice mail systems that are operating within a CCIS 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
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #4
Thanks KenMeans,
I really appreciate your help!
I had read over CN 4015 a couple of times. What I am wondering is this:
1)what card to use in the NEC, and
2)what the settings on the card would be.
I work with Avaya switches mostly, but am starting to support a site that has an NEC 2400.
Thanks again,
I really appreciate your help!
I had read over CN 4015 a couple of times. What I am wondering is this:
1)what card to use in the NEC, and
2)what the settings on the card would be.
I work with Avaya switches mostly, but am starting to support a site that has an NEC 2400.
Thanks again,
a PA- 24DTG for the t-1 in the PBX and set it up like it is clocking from the master in the pbx.
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
Ken Means
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
- Thread starter
- #6
- Status
Similar threads
- Locked
- Question