NEC Neax 2400 Imx Feature Programming Manual

							NEAX2400 IMX Feature Programming Manual
ND-70184 (E), Issue 3
Page 477
Multiple Call Forwarding - Don’t Answer M-25
FCCS Programming 
This data setting describes only the additional or replacement commands used to activate FCCS
services. When used as an FCCS feature, these commands replace the non-network commands (for
example, AAED is replaced by AAEDN). Note that the data setting for FCCS service varies depending
on the node. 
(Note)
STEP 1:ASYDN - These data must be set to the NCN.
System Data 1 Index69, b7. Enable Multiple Call Forwarding-Busy Line/Don’t Answer/All Calls. 0/
1=Out of Service/In Service
Note:
When using ASYDL or ASYDN to program an FCCS feature, the basic programming of ASYD is required in addition
to ASYDL or ASYDN. 
						

							NEAX2400 IMX Feature Programming Manual
Page 478ND-70184 (E), Issue 3
M-26 Message Center Interface
M-26 Message Center Interface
General Description
This feature provides an interface to an external CPU for Message Center information when a specific UCD [U-1]
group or ATTENDANT CONSOLE [A-3] is called. This interface allows external control of Call Indicator Lamp
(Note) indications on equipped NEAX2400 IMX stations. This feature also provides a socket interface (LAN
interface) for connection to an external LAN.
Note:
Call Indicator Lamp on Dterm Series E is used as the Message Waiting Lamp.
This feature also provides a socket interface (LAN interface) for connection to an external LAN.
Operating Procedure
The MESSAGE CENTER INTERFACE (MCI) can provide one of two modes of operation. These modes are
described as Feature 1 and Feature 2. The functions of each feature are as follows:
Feature 1:
1. Incoming call information is sent to the MCI when an Attendant answers.
2. Control of Call Indicator Lamp based on data from the external CPU.
Feature 2:
1. Incoming call information is sent to the MCI when a UCD station is called.
2. Dual Call Forwarding service is possible.
3. Control of Call Indicator Lamp based on data from the external CPU.
Note:
Feature 2 is not available when a hot line call terminates to a UCD station.
Feature 1
1. When the Attendant answers a call, the NEAX2400 IMX transmits a call handling record to the MCI. The
external CPU, based on the received data, will display a profile of the station/trunk being handled by the
Attendant on the CRT.
2. Call Indicator Lamp control is based on data from the external CPU. Through the external CPU terminal,
when information is registered, the Host/CPU system forwards Call Indicator Lamp control data according
to the Call Indicator Lamp On/Off control information sent.
3. The NEAX2400 IMX, upon receiving this control data from the MCI, will extinguish or illuminate the
Call Indicator Lamp, depending on the subscriber displayed on the Attendants monitor/display.
4. The called station will be able to receive a message from the Attendant by dialing “0”, or a computer
terminal by entering an identification number.
5. The external CPU, upon receiving retrieved message information, will transmit a data record requesting
the NEAX2400 IMX to extinguish the Call Indicator Lamp of the corresponding station.
Feature 2
1. This provides an interface to a Voice Mail System, or a Message Center Computer that is capable of
sending Call Indicator Lamp control data to the NEAX2400 IMX.
2. To perform the data transfer to the external CPU, a station/trunk is connected to a designated UCD [U-1]
group. The stations of the UCD [U-1] group are connected to the Voice Mail System/Message Center
System in order to collect call connection status of Call Indicator Lamp control information. The block
diagram of this concept follows on the next page.
3. The NEAX2400 IMX, upon receiving this control data from the MCI, extinguishes or illuminates the Call
Indicator Lamp depending upon the information displayed on the Attendants monitor/display.
4. The called station will be able to receive a message by dialing “0”, or by a computer terminal by entering
his/her identification number. 
						

							NEAX2400 IMX Feature Programming Manual
ND-70184 (E), Issue 3
Page 479
Message Center Interface M-26
Operating Procedure (cont’d)
5. The external CPU, upon receiving retrieved message information, will transmit a data record requesting
the NEAX2400 IMX to extinguish the Call Indicator Lamp of the corresponding station.
Service Conditions
1. The call type is sent to the external CPU via the MCI interface, this call record will pertain to the following
services:
ATTENDANT CAMP-ON [A-1]
AUTOMATIC RECALL [A-8]
CALL FORWARDING - DONT ANSWER [C-3]
CALL FORWARDING - BUSY LINE [C-2] 
CALL FORWARDING - ALL CALLS [C-5]
Call returned from Hold
CALL TRANSFER - ALL CALLS 
(Note)[C-11] 
CENTRALIZED ATTENDANT SERVICE (CAS) [C-20] 
DIAL ACCESS TO ATTENDANT [D-2] 
DID to the Specific UCD Group
DIT to the Specific UCD Group 
Intercept Call to the Attendant 
INTER-POSITION TRANSFER [I-5]
LDN call
OFF-HOOK ALARM [O-6]
Recall
Recall from a Series Call
Series Call Re-Entry
Tandem Transferring/Hold Entry
Note:
Available for interoffice station transfer calls only.
2. The NEAX2400 IMX MESSAGE CENTER INTERFACE [M-26] can control the display of a Dterm for
Message Indication; MW in a Message Center application.
3. If an ATTENDANT CONSOLE [A-3] calls a UCD [U-1] group directly, for Feature 2, the NEAX2400
IMX will not generate a call record to the MCI.
VOICE MAIL 
SYSTEM ANALOG 
STATION 
LINE MESSAGE CENTER
MESSAGE 
CENTER 
COMPUTER
UCD
MESSAGE 
CENTER 
INTERFACE NEAX2400 IMX
UCD
MESSAGE 
CENTER 
INTERFACE NEAX2400 IMX 
						

							NEAX2400 IMX Feature Programming Manual
Page 480ND-70184 (E), Issue 3
M-26 Message Center Interface
Service Conditions (cont’d)
4. If the Host/CPU malfunctions and stops collecting call records, the NEAX2400 IMX can store up to 16
call records. If the maximum of 16 call records is stored and a 17th is generated, the system will write over
the oldest stored record, thus giving the stack the most recently generated call records.
5. MCI data will not be output when a hotline station is terminated to a station that is forwarded to a Voice
Mail System.
6. It can be determined on a UCD group basis whether to send the incoming call information of the call
terminating to a station in the UCD group to the message center CPU. When OVERFLOW - UCD [O-7]
is activated, the MCI operation of the overflow UCD group is followed.
7. When the calling party number is received via the C.O. line/ISDN line/CCIS line, the number is sent to
the MCI. The calling number is output to the additional MCI text format.
8. When activating this feature via the FCCS network, the station number type (Physical Station Number or
telephone number) to be output for MCI IMX format may be designated in system data.
9. When activating this feature via the FCCS network, a maximum of 2 Messages Centers per node are
available.
SOCKET Interface (LAN interface) Conditions:
1. LAN interface and IOC interface cannot be used concurrently for MCI.
2. The socket interface will be used for transfer data to and from the Message Center connected to the LAN.
3. After the link has been released, it will always be the client which presents a link establishment request.
4. The MCI messages which are transferred via the LAN interface is IMX format messages only.
5. Multiple nodes within an FCCS network can accommodate the Message Center (MC).
6. When activating this feature via the FCCS network, a maximum of 32 nodes can be assigned as the remote
node. Stations accommodated in remote node are controlled by the Message Waiting Lamp (MWL) by the
MC.
FCCS Link
Group AGroup B
Node C
Node A
Node B Node D
MC #1
MC 
#2
MC #1
MC 
#2 
						

							NEAX2400 IMX Feature Programming Manual
ND-70184 (E), Issue 3
Page 481
Message Center Interface M-26
Interactions
1. In case a Message Center exists on each side of the FCCS network and CCIS network:
a.) Message data will be transmitted to the MC on the side of the CCIS network (in the figure below,
MC#1), provided that a call from any of the FCCS network nodes (in the figure, node A/B/C)
terminates to an ATTCON/UCD station of the non-FCCS node (in the figure, node D).
b.) Message data will be transmitted to the MC on the side of the FCCS network (in the figure below,
MC#2), provided that a call from the non-FCCS node (in the figure, node D) terminates to the
ATTCON/UCD station of any of the FCCS network nodes (in the figure, node A, B, C).
2. In case a Message Center is shared by both CCIS and FCCS networks:
a.) Message data will be transmitted to the shared MC (in the figure below, assumed to be connected
to the FCCS node A), given that a call from the CCIS node (in the figure, node D) terminates to
the ATTCON/UCD station of any of the FCCS network nodes (in the figure, node A, B, C).
Node B
Node DNode A Node C
CCISFCCS FCCSFCCS
MC #2
MC #1
MC: Message Center 
						

							NEAX2400 IMX Feature Programming Manual
Page 482ND-70184 (E), Issue 3
M-26 Message Center Interface
Interactions (cont’d)
b.) The shared Message Center also can let the Message Waiting Lamps for both FCCS and non-
FCCS (CCIS) network stations go ON and OFF to inform the telephone user of the message
arrival.
3. In case the Message Center exists only on the side of CCIS network:
a.) Message data will be transmitted to the offered MC (in the figure below, assumed to be connected
to node D), given that a call from any of the FCCS network nodes (in the figure, node A/B/C)
terminates to an ATTCON/UCD station of the CCIS node (in the figure, node D).
b.) The MC, though provided outside the FCCS network, can also control the Message Waiting
Lamp for each station on the FCCS service link, as well as ON/OFF indication of the lamps for
stations on the CCIS link.
Node B
Node DNode A Node C
CCIS FCCS FCCS
FCCS
MC
MC: Message Center
Node B
Node DNode A Node C
CCISFCCS FCCSFCCS
MC
MC: Message Center 
						

							NEAX2400 IMX Feature Programming Manual
ND-70184 (E), Issue 3
Page 483
Message Center Interface M-26
Interactions (cont’d)
4. In case the Message Center exists only on the side of FCCS network:
a.) Message data will be transmitted to the offered MC (in the figure below, assumed to be connected
to node A), given that a call from the CCIS node (in the figure, node D) terminates to the
ATTCON/UCD station of any of the FCCS network nodes (in the figure, node A, B, C).
b.) The MC, though provided only inside the FCCS network, can also control the Message Waiting
Lamp for each station on the CCIS link, as well as ON/OFF indication of the lamps for stations
within the FCCS link.
Programming
STEP 1:ASYD - System Data 1, Index 28, Bits 0-4. Assign a Miscellaneous Timer Counter (MTC) used to
calculate the message-sending Guard Timer for Message Center. 
Timer = MTC x 128ms. Normally a Guard Timer is not required. If not required, assign data “0” to
these bits.
System Data 1, Index 28, Bit 5. Is Message Waiting Lamp setting from the Message Center to be used?
0/1: No/Yes.
System Data 1, Index 29, Bits 0-4. Assign which I/O port will act as the MESSAGE CENTER
INTERFACE. Bit 0 as Port 0 is always used as a Maintenance Administration Terminal (MAT). Bit 1 =
Port 1, Bit 2 = Port 2; Bit 3 = Port 3; Bit 4 = Port 4; Bit 5 = Port 5, for a maximum of 2 ports. 
System Data 1, Index 34, Bit 0 &1. 
b2, b1 = “00”; no parity and output data Bit 7 is “0”.
System Data 1, Index 70, Bit 0. Called Number Display on the console for DID and TIE Line calls
must be enabled. Assign Bit 0 as data “1” when System Data 2, Index 6, Bit 7 is also enabled. 
System Data 1, Index 78, Bit 0. CALLING NUMBER DISPLAY-D
term [C-24D] must be enabled.
Assign Bit 0 as data “1”. 
System Data 1, Index 78, Bit 1. CALLING STATION STATUS DISPLAY-D
term [C-22D] must be
enabled. Assign Bit 1 as data “1”. 
Note:
Index 116, Port 0 is assigned as data 02H, MAT. 
Node B
Node DNode A Node C
CCISFCCS FCCS
FCCS
MC
MC: Message Center 
						

							NEAX2400 IMX Feature Programming Manual
Page 484ND-70184 (E), Issue 3
M-26 Message Center Interface
Programming (cont’d)
System Data 2, Index 6, Bit 0. Is MCI service with UCD groups to be enabled? 0/1: No/Yes. 
System Data 2, Index 7, Bit 1. Is MCI service for calls via the Attendant Console to be enabled? 0/1:
No/Yes. 
STEP 2:AIOC - Assign the function and attribute data of the IOC ports.
FCCS Programming 
This data setting describes only the additional or replacement commands used to activate FCCS
services. When used as an FCCS feature, these commands replace the non-network commands (for
example, AAED is replaced by AAEDN). Note that the data setting for FCCS service varies depending
on the node.
 (Note 1)
STEP 1:ASYDL - System Data 1, Index 641 Bit 1. Designate output numbers for MCI IMX format. (Note 2)
0/1 = Physical (station) number/telephone number
System Data 1, Index 832. Assign the Fusion Point Code (FPC) of the node providing the MC 
(Note 3) 
System Data 1, Index 641 Bit 1. Designate output numbers for MCI IMX format.
0/1 = Physical (station) number/telephone number 
(Note 2)
System data 1, Index 833, Bit 0. Interface type for MCI. 0/1 = IOC/LAN interface (Note 3)
System data 1, Index 833, Bit 1. Text format for MCI. 0/1 = ICS/IMX format (Note 2)
Note:
When more than a 5 digit telephone number is assigned, designate 1 = IMX format.
STEP 2:This data is required for the LAN interface.
ASYDL - System Data 1, Index 529, Bits 0 and 1. Parity check method of SMDR/MCI with LAN
interface.
b1, b0: 00 = No parity
01 = Odd parity
10 = Even parity
System Data 1, Index 834, Bit 0. 0/1 = MC0 for LAN is not mounted/mounted. 
(Note 2)
System Data 1, Index 834, Bit 1. 0/1 = MC1 for LAN is not mounted/mounted. (Note 2)
STEP 3:AMWF - Assign Fusion Point Code (FPC) of the node for being controlled the MWL on the Dterm by
the MC. 
(Note 2)
Note 1:
When using ASYDL or ASYDN to program an FCCS feature, the basic programming of ASYD is required in addition
to ASYDL or ASYDN.
Note 2:
Assign this data to the node accommodating the MC.
Note 3:
Assign this data to all the nodes to be provided MCI service. 
						

							NEAX2400 IMX Feature Programming Manual
ND-70184 (E), Issue 3
Page 485
Message Waiting Lamp Setting - Station M-30
M-30  Message Waiting Lamp Setting - Station
General Description
This feature allows a station to set/cancel a Message Waiting indication or lamp. Any single line telephone or Dterm
can set/cancel Message Waiting indication to any single line telephone equipped with a 90v neon lamp, or a Dterm.
Note:
Call Indicator Lamp on Dterm Series E is used as the Message Waiting Lamp.
Operating Procedure
For example:
Station 200: Users station
Station 201: Message Agent*
Note:
A Message Agent is a preassigned station allowed to set/cancel a Message Waiting indication. 
1. Station 200 sets Call Forwarding to Station 201.
2. An incoming call to Station 200 is call forwarded to Station 201.
3. Station 201 receives a message from the calling party.
4. Station 201 hangs up.
5. Station 201 sets the Message Waiting indication for Station 200. (Procedure 1)
6. Station 200 sees the Message Waiting indication.
7. Station 200 calls Station 201.
8. Station 200 receives the message from Station 201.
9. The call is terminated.
10. Station 201 cancels the Message Waiting indication for Station 200. (Procedure 2)
Procedure 1:
To set a Message Waiting Indication from a single line telephone:
1. Lift the handset; receive dial tone.
2. Dial the Message Waiting Set access code (up to 3 digits); receive special dial tone. 
3. Dial the desired telephone number; receive service set tone. 
4. Message Waiting indication is set.
To set a Message Waiting Indication from a Dterm or MY Line:
1. Lift the handset or press the SPEAKER key; receive dial tone.
2. Press the Message Waiting Set line/feature key; receive special dial tone.
3. Dial the desired telephone number; the LCD displays:
Service set tone is heard.
4. Message Waiting indication is set.
Procedure 2:
To cancel a Message Waiting Indication from a single line telephone: 
1. Lift the handset; receive dial tone.
2. Dial the Message Waiting Cancel access code (up to 3 digits); receive special dial tone.
3. Dial the desired telephone number; receive service set tone. 
4. Message Waiting indication is cancelled.MW SET 
						

							NEAX2400 IMX Feature Programming Manual
Page 486ND-70184 (E), Issue 3
M-30 Message Waiting Lamp Setting - Station
Operating Procedure (cont’d)
To cancel a Message Waiting Indication from a Dterm or MY Line:
1. Lift the handset or press the SPEAKER key; receive dial tone.
2. Press the Message Waiting Cancel line/feature key, receive special dial tone. 
3. Dial the desired telephone number; the LCD displays, and service set tone is heard.:
4. Message Waiting indication is cancelled.
Service Conditions
1. Any number of Dterm stations within the system can be assigned to activate this feature.
2. Any attempt to set Message Waiting to a station that already has a Message Waiting indication will receive
busy tone.
3. Each station can cancel the Message Waiting indication.
4. This feature can be restricted by CLASS OF SERVICE - INDIVIDUAL [C-15].
5. Message Waiting for one station of the network can be controlled from the ATTENDANT CONSOLE [A-
3] and any other station at the same time.
6. The Message Waiting indication on a station appears as follows:
Type of Station SetCondition
Single line telephone with MWL Dterm Series 
without displayMessage Waiting Lamp is ON
D
term Series with displayDisplay shows:
MW CANCEL
(Time Display) 
MW
(Time Display)