NEC NEAX2400 IMX Specification
ND-70428 (E)
ISSUE 1
STOCK # 200892
®
Message Center Interface (MCI)
Specifications
JANUARY, 1999
NEC America, Inc.
LIABILI TY D ISC LAIMER
NEC America, Inc. reserves the right t o change t he specifications,
functions, or features, at any time, without notice.
NEC America, Inc. has prepared this docum ent for use by its employees and customers. The information contained herein is the
property of NEC America, Inc. and shall not be reproduced without
prior written approval from NEC America, Inc.
NEAX and D
term
are registered trademarks of NEC Corporation.
Copyright 1999
NEC America, Inc.
Printed in U S A
ND-70 428 (E)
ISSUE 1
JANUARY, 1999
NEAX2400 IMX
Message Center Interface (MCI) Specifications
TABLE OF CONTENTS
Page
LIST OF FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
LIST OF TABLES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
CHAPTER 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
CHAPTER 2 MCI FOR IOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1. SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Text Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. PROTOCOL AND MESSAGE RESPONSES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 PBX → MC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 MC → PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
CHAPTER 3 MCI FOR LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1. SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Basic Configuration of Text. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Text Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2. PROTOCOL AND MESSAGE RESPONSES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Link Establishment Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 Transmission and Reception of Call Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.3 MWL Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.4 Monitoring Status Between Client and Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.5 Link Release Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.6 Connection Sequence for System Changeov er . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CHAPTER 4 MESSAGE FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1. ICS FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2. IMX FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
CHAPTER 5 SERVICE CONDITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
CHAPTER 6 DATA ASSIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
ND-70428 (E) TABLE OF CONTENTS
Page i
Revision 1.0
LIST OF FIGURES
Figure Title
Figure 1-1 MCI for UCD Incoming Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Figure 1-2 MC I for Attendant Incoming Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Figure 2-1 Word Framing Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 2-2 Typical Text Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 3-1 PBX and MCI for LAN Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 3-2 Text Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 3-3 Lamp Control Text Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 3-4 Call Information Text Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 3-5 Server Response Text Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Figure 3-6 Client Response Text Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 3-7 Status Monitoring Text Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 3-8 Link Release Text Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 3-9 Link E stablis hme nt Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 3-10 Transmission and Reception of Call Information Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 3-11 Transmission and Reception of Call Information Error Processing Sequence (1) . . . . . . . . . . . 15
Figure 3-12 Transmission and Reception of Call Information Error Processing Sequence (2) . . . . . . . . . . . 16
Figure 3-13 Transmission and Reception of Call Information Error Processing Sequence (3) . . . . . . . . . . . 17
Figure 3-14 Transmission and Reception of Call Information Error Processing Sequence (4) . . . . . . . . . . . 18
Figure 3-15 MWL Control Processing Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Figure 3-16 MWL Control Error Processing Sequence (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 3-17 MWL Control Error Processing Sequence (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 3-18 MWL Control Error Processing Sequence (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 3-19 Monitoring Status Between Client and Server Processing Sequence . . . . . . . . . . . . . . . . . . . . 23
Figure 3-20 Link Release Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 3-21 System Changeover Connection Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Page
LIST OF FIGURES
Page ii
Revision 1.0
ND-70428 (E)
LIST OF T ABLE S
T able Title
Table 4-1 Call Type Codes for Attendant Incoming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 4-2 Call Type Codes for UCD Incoming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 4-3 Message Text Station Number Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 4-4 PBX → MC Data Type Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 4-5 Call Type Codes for Attendant Incoming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 4-6 Call Type Codes for UCD Incoming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 4-7 MC → PBX Data Type Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Table 4-8 MC → PBX Data Type Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Page
ND-70428 (E)
LIST OF T ABLE S
Page iii
Revision 1.0
This page is for your notes.
LIST OF TABLES
Page iv
Revision 1.0
ND-70428 (E)
CHAPTER 1 INTRODUCTION
This manual provides the Message Center Interface (MCI) specifications for the NEAX2400 IMX system.
When a call terminates to the attendant or a Uniform Call Distribution (UCD) station, the call information is
sent via the MCI to the Messa ge Center (MC). Base d on the call informa tion fr om the Privat e Branch Exchange
(PBX), the MC achieves ON/OFF control of the Message Waiting Lamp (MWL) and Message Waiting (MW)
indication of the station. Figure 1-1 and Figure 1-2 show the MCI for a UCD incoming call and an attendant
incoming call.
PBX
UCD
MC
ex. Voice
Message S y stem
IOC/
LANI
Message Center Interface (RS-232C/LAN)
Note:
Figure 1-1 MCI for UCD Incoming Call
PBX
IOC/
LANI
Message C enter Interfac e (RS-23 2C/LAN)
ATT
CRT
MC
For detailed information on an external device used as MC, refer to the manual included
with the external de v ice.
Figure 1-2 MCI for Attendant Incoming Call
ND-70428 (E) CHAPTER 1
Page 1
Revision 1.0
This page is for your notes.
CHAPTER 1 ND-70428 (E)
Page 2
Revision 1.0
CHAPTER 2 MCI FOR IOC
1. SPECIFICATIONS
1.1 Interface
This section has information on the signal interface requirements for the MCI for Input/Output Controller
(IOC).
Operating mode : Full duplex
Electrical interface characteristic : RS-232C electrical interface standard
Frame code : US ASCII
Parity : Non/Odd/Even
Word framing example : See Figure 2-1.
Data rate : Up to 9600 bps
Priority sequence
• Primary sta tion : PBX
• Secondary station : MC
Parity BitStart Bit
b1 b2 b3 b4 b5 b6 b7 b8
Figure 2-1 W or d Framing Example
1.2 Text Format
MCI for IOC uses the following text format.
S
S
T
X
STX : Start of Text
SA : System Addr ess
UA : Unit Address
EI : Entry Index
ETX : End of Text
U
A
A
Data Bits
E
I
Message text
(Refer to CHAPTER 4.)
Stop Bits
E
T
X
Figure 2-2 Typical Text Format
ND-70428 (E) CHAPTER 2
Page 3
Revision 1.0
MCI FOR IOC
2. PROTOCOL AND ME SSAGE RESPONSES
This section has inf ormation on protocol and m es sage responses of MCI for IOC. For detailed information on
each message, refer to CHAPTER 4.
2.1 PBX
→
PBX
Note:
MC
MC
S
SAU
T
X
receive receive
send send
S
E
Data Data
A
T
X
t
Note
SAU
T
X
A
E
T
X
The interval between communications is the Guard Timing (GT) value programmed in
ASYD (SYS1, Index 28, Bits 0-4).
2.2 MC
→
PBX
(1) W h en receiving messages con tr olling one station, the follo wing text format applies.
MC
PBX
S
SAU
T
X
A
send
STA1
E
T
X
receive
350 ms or longer
S
SAU
T
X
A
send
STA1
E
T
X
receive
(2) When receiving queue is full, the PBX sends Call Type 39. This requests MC to stop transmission. Whe n
the PBX has processed all MWL requests in full queue, the PBX sends Call Type 66. This requests MC
to start sending MWL data.
message messag e message
MC
PBX
MC
PBX
send
receive receive receive
wait
receive
send
Call Type 66
(Start Sending MW Control Data)
send
(Stop Sending MW Control Data)
receive
CHAPTER 2 ND-70428 (E)
Page 4
Revision 1.0
receivesend send
send
Call Type 39
wait
CHAPTER 3 MCI FOR LAN
1. SPECIFICATIONS
1.1 Timing
Timing to Esta blish a Link : A link is connected when an MC connect request is received.
Timing to Output Call Information : When a call terminates to the att endant or a UCD group station,
Timing to Rec eive MWL Information : When Message Waiting Lamp (MWL) information is received,
Timing to Release the Link : The MC for Local Area Network (LAN), which is a client of
the call information is sent via the MCI to the MC.
the MWL of the st ation served by the PBX is cause d to be ON/
OFF.
the PBX, discards the socket and performs processing to release the link when it does not receive a “Call Information
Text” or “Server Response Text” in a given time interval from
the server. When the PBX or the server does not receive a
“Lamp Control Text”, “Client Response Te xt”, or “Status Monitoring Text” in a gi ven tim e interv al from the c lient, it p erforms
NG processing + sends a “Connection Disconnect Text” and
then discards the socket and performs processing to release the
link.
1.2 Interface
This section has information on the interface requirements for the PBX and the external device (MC for
LAN). Figure 3-1 shows the PBX and the MCI for LAN interface.
Protocol : Stream type socket (TCP) protocol
Physical conditi on : Ethernet
Software condit ions
• PBX : Socket interface (capability provided to deal with WinSock)
• External device : Shall use the WinSock, UNIX socket and other libraries.
Port No. : 60020 (defined at PBX side)
Codes to be used
• Transmis sion code : ASCII 8 bits without parity
• Control codes
SYN : 16H indicates the beginning of a text.
STX : 02H indicate s the beginning of an MCI record.
ETX : 03H indicates the end of an MCI record.
ND-70428 (E) CHAPTER 3
Page 5
Revision 1.0
MCI FOR LAN
PBX
Application
Call information/MWL
informa tio n tr a ns fer
protocol
Socket
TCP/IP
Ethernet
Call informat ion/MWL
info rmation protocol
External Device (MC for LAN)
Applic ation
Call information /M WL
information transfer
protocol
Socket
TCP/IP
Ethernet
Figure 3-1 PBX and MCI for LAN Interface
1.3 Basic Configuration of Text
Data is transferred between the se rver and cl i ent in the unit of a text.
A text, as shown in Figure 3-2, consists of SYN (16H), used as the beginning of a text, a text identifier,
data length, device No., sequence No., message and parity (horiz ontal parity check system).
The result of the exclusive logical sum of the parity r ange is set as the parity.
(If the resu lt of t h e exclus ive logical sum of the range from the text identifier to the parity is even parity,
the check bit is set to “0”. If it is odd parity, the check bit is set to “1”.)
S
(X)
Y
N
Text
identifier
(X)
Data length
(XXX)
Device
Sequence
No.
(XX)
Parity Range
No.
(XX)
Figure 3-2 Text Basic Configuration
(1) SYN: Text Data Start Position Information
The SYN defines the posit ion where the text data to be sent or recei ved is to start.
Data type : Hexadecimal
Data size : 1 byte
Data : SYN 16H
CHAPTER 3 ND-70428 (E)
Page 6
Revision 1.0
Call information or
lamp control
informa tio n or
response No., et c.
Parity
(X)
(2) Text Identifier
The text identifier identifies the data to be sent or received.
Data type : Decimal (ASCII code)
Data size : 1 digit
Data range: 0 to 9
0 : Not used
1 : Lamp Control Text (MC for LAN PBX)
The PBX that recei ve d the da ta sends the result of t he received data ch eck as a “Serv er
Response Text (t ext identif ier (3))” to the MC for LAN in a predetermined time inte rval.
2 : Call Information Text (PBX MC for LAN)
The MC for LAN that received the data sends the result of the received data check as
a “Client Response Text (text identifier (4))” to the PBX in a predetermined time interval.
3 : Server Response Text (PBX MC for LAN)
MCI FOR LAN
When the PBX receives identifiers (1) or (5), it sends the result of the received data
check to the MC for LAN.
4 : Client Response Text (MC for LAN PBX)
When the MC for LAN receives ident ifier (2), it se nds the re sult of the received data
check to the PBX.
5 : Status Monitoring Text (MC for LAN PBX)
When both the MC for LAN and PBX do not send any of the v ar ious types of processing requests, a status monitoring text is sent by the MC for LANs in a predetermined
time interval.
When the PBX receives the text, it monitors the status of the client.
6 : L ink Re le ase Text (MC for LAN PBX)
A link release request text sent from the client to the server and from the server to the
client.
(3) D at a Len g th
The data length indicates the leng th of data to be sent and received betwee n the server and client.
The number of bytes ranging from the character following the data length to the character preceding to
the parity is set in terms of 3 digits.
Data type : Decimal (ASCII code)
Data size : 3 digits
Data range: 0 to 999
ND-70428 (E) CHAPTER 3
Page 7
Revision 1.0
MCI FOR LAN
(4) D evice N o.
The device No. indicates the device No. for the MC for LAN connected to the server.
The MC for LAN sends its own device No. to the server, and the PBX sends the device No. for the MC
for LAN, which is the destination of the text.
The device No. to be used is defined at the PBX side.
(5) Sequence No.
The sequence No. is a serial number for the data to be sent.
It is a number assigned to assure that the transferred data is cleared.
The PBX and server manage independent numbers respectively.
Data type : Decimal (ASCII code)
Data size : 2 digits
Data range: 0 to 99
Data type : Decimal (ASCII code)
Data size : 2 digits
Data range: 0 to 99
(6) Parity
The horizontal parity chec k method is a dopted. The c alculation range is f rom the te xt ide ntifie r to the c haracter preceding to the parity . By default, odd parity is used.
The parity check method can be changed in system data.
Data type : Hexadecimal
Data size : 1 byte
Data range: 00H to FFH
CHAPTER 3 ND-70428 (E)
Page 8
Revision 1.0
MCI FOR LAN
1.4Text Format
(1)Lamp Control Text (MC for LAN PBX)
Figure 3-3 shows text to be sent when a request for control from the MC for LAN is presented. The format
in a record is the IMX format of MCI message. It complies with the format of MC PBX message in
CHAPTER 4, Section 2, IMX FORMAT.
∫ ∫
S
(X)
Y
N
Text
identifier
(1)
Data length
(XXX)
Device
No.
(XX)
Sequence
No.
(XX)
New control
Parity
(X)
∫ ∫
Field of a record
Figure 3-3 Lamp Control Text Configuration
(2)Call Information Text (MC for LAN PBX)
Figure 3-4 shows the call information text to be sent from the PBX to the MC for LAN. The format in a
record is the IMX format of MCI message. It complies with the format of PBX MC message in CHAP-
TER 4, Section 2, IMX FORMAT.
As for text identifier (2), a piece of call information is created when a call terminates to the attendant or a
UCD station and when text is sent to the MC for LAN. Therefore, each text contains one record.
∫ ∫
S
(X)
Y
N
Text
identifier
(2)
Data length
(XXX)
Device
No.
(XX)
Sequence
No.
(XX)
Call information
∫ ∫
Field of a record
Figure 3-4 Call Information Text Configuration
ND-70428 (E) CHAPTER 3
Parity
(X)
Page 9
Revision 1.0
Loading...