NEC Neax 2400 Imx Oai System Manual

							ND-70895 (E) CHAPTER 5
 Page 81
Revision 1.0
OFFICE DATA DESIGN
Procedure for Setting Office Data for OAI Services
3.7.2 Multiple IPs
3.7.2.1 Functional Outline
In this configuration (Multiple IPs), IP can be accommodated to multiple nodes in a Fusion Network.
Since Series 7400 (Release 8) software, establishing the CCIS line is not necessary to use OAI system
through the network. (“Facility” which can be used through the Fusion Network varies in “the OAI
application”.)
This feature is available with Series 7400 (Release 8) software.
3.7.2.2 Using Conditions
(a) Telephone Number (max. 5 digits) is used for the station number type to activated OAI system
through Fusion network.
(b) Logical Route is used for the route type to activate OAI system through Fusion network.
(c) Only one IP to be used for “OAI Terminal Anywhere” can be contained in a Fusion Network
(Multiple IPs).
(d) IP can be accommodated to multiple nodes in a Fusion Network. However, maximum number
of Status Monitoring Requests to a terminal is decided by the system data (max. 8 ports
available including UAP). Note that the normal operation is not guaranteed if Status
Monitoring is requested to a terminal from more than the number of ports. 
UAPIP
FACILITY
Node B
OAI Term inalsFACILITY
Node A
UAPIP
FACILITY
FCCS
FCCSFCCS
OAI Term inals
OAI Terminals
Node C 
						

							CHAPTER 5 ND-70895 (E)
Page 82
Revision 1.0
OFFICE DATA DESIGN
Procedure for Setting Office Data for OAI Services
(e) OAI terminals to be controlled from different IPs can not be accommodated in a node.
(f) When the IMG-U system is included in a Fusion Network (Multiple IPs), take the following
conditions into consideration when programming data.
3.7.2.3 Data Programming
[Notice for Data Programming]
This section shows data programming divided into the types of OAI system (Figure 5-1).
Figure 5-1   Network Configuration of OAI systems
........................................................................
........................................................................
........................................................................
........................................................................
Node B
OAI Terminals OAI Terminals
FCCS FCCS
FCCS
Node A
IP
IP
Node C
(a)  IMG-U system where the OAI terminals are accommodated in multiple Local Nodes.
       In the IMG-U system, data programming for “OAI terminal Anywhere” must be programmed at
       the node that has IP (“IP1” in the figure below). In the network, another IP can not be used for
       “OAI terminal Anywhere” any more.
IMG-U
IP1IP2LN
LN
LN LNLN
LN
LN
LEGEND
: Local Node that
  has OAI terminals
PBX1 PBX2IIP
IPII
PBX3 PBX4III
Fusion Network
LEGEND
Type I :  PBX1 - Non - OAI system
Type II : PBX2 - OAI Stand-alone system (OAI system provides OAI
                         function in the self-node only)
Type III : OAI Terminal Anywhere
               PBX3 - System providing the OAI terminals (Non-IP Node)
               PBX4 - System providing the OAI terminals (IP-Node)       The following are the network configuration of OAI system in a Fusion Network. 
						

							ND-70895 (E) CHAPTER 5
 Page 83
Revision 1.0
OFFICE DATA DESIGN
Procedure for Setting Office Data for OAI Services
1. The following are the quick reference table of optional software and system data programming for
each OAI system configuration. (See Figure 5-1 “Network Configuration of OAI systems” for
network configuration of OAI systems.)
:
The software is installed to be linked with the standard service software using MSVIP command.
Note 1:When CM is used for another function, this setting may be changed.
(Ex. Assign “6” Hex. when FLF Fusion service is used.)
Note 2:When the CPU in system 1 is used, assign “1”.
Note 3:Assign “1” at the all nodes using “OAI Terminal Anywhere” in the Fusion network that “MULTIPLE IPs” is provided.
Note 4:When the all fusion nodes in the network are used for “MULTIPLE IPs”, this data may be assigned using ASYDN. 
Note 5:This data is required for UAP connection.
Note 6:(This data is not necessary for the example above.) Assign this data so that the proper number of ports can be used when
more than three ports of Status Monitoring for terminal (SMFN). The identical data should be assigned at all nodes. 
ASYDL SYS1 INDEX864  b4~5:
 b5 
 b4 
00=2 ports
01=8 ports
Note 7:When the node using “OAI Terminal Anywhere” is included in the Fusion network that “Multiple IPs” is provided, assign
the FPC no. of IP node using “OAI Terminal Anywhere”. 
Table 5-1 OAI Software and System Data
Type and Node
OA II II III
PBX1 PBX2 PBX3 PBX4
OA I Software
1OAI Option Service software (basic)
[Series 7400 (Release 8)]
2 ACD Option Service Software for “Agent Anywhere”
System Data
3CM UsageNote 1
(ASYD:SYS1, INDEX31, b0~b3)0444
4OAI in service/out of service
(ASYD:SYS1, INDEX79, b6)1000
5No.0  CPU Mounted Status of IP00/1: Not mounted/Mounted
(ASYD:SYS1, INDEX207, b0)0101
6No.1  CPU Mounted Status of IP00/1: Not mounted/Mounted
(ASYD:SYS1, INDEX207, b1)0Note 20Note 2
7OAI Call Processing Event Notification
(ASYD:SYS1, INDEX241, b2)0111
8SCF Return Error Detail Notification
(ASYD:SYS1, INDEX241, b3)0111
9Built-in IP:Not used/Used
(ASYDL:SYS1, INDEX864, b0)0101
10OAI Terminal Anywhere:Out of service/In serviceNote 3
(ASYDL:SYS1, INDEX864, b2)0011
11MULTIPLE IPs:Out of service/In serviceNote 4 
(ASYDL:SYS1, INDEX864, b3)0011
12FPC Number of the node providing IP
(ASYDL:SYS1, INDEX865)00Note 5 Note 5
13Number of ports for SMFN (terminal)
(ASYDL:SYS1, INDEX864, b4~5)0Note 6 Note 6 Note 6
14FPC Number of Center Node providing VNDM (ASYDN:SYS1, 
INDEX533)Note 7 Note 7 Note 7 Note 7 
						

							CHAPTER 5 ND-70895 (E)
Page 84
Revision 1.0
OFFICE DATA DESIGN
Procedure for Setting Office Data for OAI Services
2. Some notices for PBX commands data programming are described below. (See Figure 5-1
“Network Configuration of OAI systems” for network configuration of OAI systems.)
: Assign data by the corresponding commands written in DM.
N : Assign data by the corresponding commands written in NDM.
L : Assign data by the corresponding commands written in LDM when the call is not terminated from other nodes.
Type and Node
PBX Command DataI II III
PBX1 PBX2 PBX3 PBX4
Monitor Number Data (AMNO) N/L N
Conversion Number Data (ACNO) N/L N
Announcement/Dictation Data (AADT) N N
OAI Key Code Data (AOKC)
Key Data for D
term (AKYD) 
						

							ND-70895 (E) CHAPTER 5
 Page 85
Revision 1.0
OFFICE DATA DESIGN
Procedure for Setting Office Data for OAI Services
3.7.3 Example of Use of Facility on Fusion Network
As a example of use of facilities through Fusion Network, the explanations will give in the following
about Free Location Facility (FLF).
By using Free Location Facility (FLF) through Fusion Network, OAI Logical Number services can be
used at any nodes in the Fusion network. This feature is available with the Series 7400 (Release 8)
software.
This service enables the Free Location Facility (FLF) beyond the nodes via the Fusion link. For
example, if OAI Logical Number 5000 is converted from Station Number 200 at Node A to Station
Number 300 at Node B. (Station Number 200 = OAI Logical Number 5000 → Station Number 300 =
OAI Logical Number 5000)
Information on OAI Logical Number Development is broadcast to all (Fusion network) nodes.
Note:For this service, assign the system data as follows;
ASYD-SYS1 INDEX 31:06 (Mounting Capacity of Common Memory (CM) 6 Mbytes)
ASYDN-SYS1 INDEX 870, b0=1(FLF Fusion service is available)
ASYDL-SYS1 INDEX 864, b6=1 (FLF Error detailed Information is provided)
....................................................................................................................................
............................................................................................................................................................
Node B
Node B
Station Number : 200
Station Number : 200Station Number : 300
Station Number : 300
OAI Logical Number : 5000
OAI Logical Number : 5000OAI Logical Number 5000 is
converted from Station Number 200
to Station Number 300
Node A
IP
Node A
IP 
						

							CHAPTER 5 ND-70895 (E)
Page 86
Revision 1.0
This page is for your notes. 
						

							ND-70895 (E) CHAPTER 6
Page 87
Revision 1.0
CHAPTER 6 MAINTENANCE
This chapter explains maintenance, fault diagnosis out of system messages, fault repair procedure of the NEAX2400
IMX OAI System.
1. General
When a fault has been discovered in the course of maintenance works, the fault is to be diagnosed out of system
messages and is to be repaired by the following fault repair procedure (Refer to Figure 6-1).
Figure 6-1   Flow of Maintenance Works
System messages
indicating OAI fault
3. SYSTEM MESSAGES
 Message Detail Data 2. MAINTENANCE
 Routine Maintenance
4. FAULT DIAGNOSIS
 Diagnosis out of System Messages 
						

							CHAPTER 6 ND-70895 (E)
Page 88
Revision 1.0
MAINTENANCE
Maintenance
2. Maintenance
2.1 Routine Maintenance
By the routine maintenance on the NEAX2400 IMX OAI System, the following are performed.
1. System messages pertaining to OAI faults
A check is made to see if any system message pertaining to OAI faults is printed out. (Refer to
Chapter 6, Section 3.1)
2.1.1 System Messages and Lamp Indications on TOPU
In the OAI system, an alarm lamp on TOPU corresponding to the faulty equipment lights up. The alarm
lamps on TOPU corresponding to system messages are shown in Table 6-1.
Table 6-1 Relationship between System Messages and Alarm Lamps on TOPU
SYSTEM MESSAGE FRAME-TOP LAMP
REMARKS
No. NAME MJ MN SUP
4-R I/O Card Fault of IP
×
26-V LAN Interface Error Report× 
						

							ND-70895 (E) CHAPTER 6
 Page 89
Revision 1.0
MAINTENANCE
System Messages
3. System Messages
3.1 Outline
If any of the NEAX2400 IMX OAI functions becomes faulty, the corresponding system message shown in
Table 6-2 is displayed. This section explains the meaning of each system message and message detail data.
Table 6-2 System Messages of OAI System
SYSTEM 
MESSAGE No.FAULT CONTENTS OF FAULT
4-R TCP/IP Link Failure A fault has occurred to the UAP or to the line connected with the 
external computer.
26-V LAN Interface Error Report A fault, related to the TCP/IP connection between the PBX and 
Host, occurred. 
						

							CHAPTER 6 ND-70895 (E)
Page 90
Revision 1.0
MAINTENANCE
System Messages
3.2 Message Detail Data
This paragraph describes the detailed information on the faults indicated by system messages (message
detail data).
3.2.1 Message Detail Data of System Message “4-R”
System Message 4-R: TCP/IP Link Failure
1. Print-out Format
2. Print-out information (typical)
Fault port number: 0-5
Communication Protocol: 03 = ETHER + TCP/IP
Error Code (ERRK): Refer to the table below (6-3 ERROR CODE)
Fault logical channel number (LCID) : 01~10H (00 means the data is invalid)
~ IP address
Note 1:This error code shows that the Host (UAP) is down manually. You can program not to output this detail
message at some offices using SYS1, INDEX864, b1 in ASYDL (Other messages than ERRK = 01 is output
when TCP connection disconnected is not output).
Note 2:This data is output for Series 7300 Release 6 or earlier. If your system is Series 7300 Release 7 or later, the
message is output by 26-V” instead. (Refer to Section 3.2.2)
Relation between LCID and PBX TCP port number
LCID TCP port number of the PBX
01 60030
Table 6-3 Error Code
PROTOCOL ERROR CODE CONTENT OF FAULT
03
(ETHER + TCP/IP)01 TCP Connection disconnected (Normal)  Note 1
02 Reception of a text that cannot be analyzed  Note 2
03~09 Not used
10 (0A) TCP Connection disconnected (On the way)  Note 2
11 (0B) Transmission to PZ-PC19 (LANI) is disabled (Permanent)  Note 2
12 (0C) Abnormal UAP is detected by Heart Beat function
13 (0D) Not used
14 (0E)  TCP/IP Connection Error (B-level Infinite Loop, etc.)  Note 2
15 (0F) Not used
SYSTEM MESSAGE 4-R                                                                           TCP/IP Link Failure
       NEC - ESD                                                                                            DEC 22    21:32
1:  xx    xx     xx   xx     xx   xx    xx    xx             2:  00   00     00    00     00    00     00    00
                                                      
                12345678910111213141516
1
2
3
4
58
23