NEC Neax 2400 Ipx System Operations And Maintenance Manual
Have a look at the manual NEC Neax 2400 Ipx System Operations And Maintenance Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1168 NEC manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![Page 275
NDA-24307 CHAPTER 3
Page 247
Issue 1
SYSTEM MESSAGES
This massage is issued when a call, originated via a station/trunk, is judged as malicious, and then, the details
on the call is traced with the called party pressing an access code or the “Call Trace” key.
[When a call is originated from a station]
Information on Called Party (Informer)
Fusion Point Code (FPC) (Hex.)
Note
Tenant No. (Hex.) Note
Physical Station No. (Hex.) Note
User Group No. (UGN) (Hex.) Note
Telephone No. (Hex.) Note 1: XXXX XXXX...](http://img.usermanuals.tech/thumb/54/84234/w64_nec-ipx-system-op-and-maint-ipx-u-type_d-274.png "Page 275
NDA-24307 CHAPTER 3
Page 247
Issue 1
SYSTEM MESSAGES
This massage is issued when a call, originated via a station/trunk, is judged as malicious, and then, the details
on the call is traced with the called party pressing an access code or the “Call Trace” key.
[When a call is originated from a station]
Information on Called Party (Informer)
Fusion Point Code (FPC) (Hex.)
Note
Tenant No. (Hex.) Note
Physical Station No. (Hex.) Note
User Group No. (UGN) (Hex.) Note
Telephone No. (Hex.) Note 1: XXXX XXXX...")
NDA-24307 CHAPTER 3 Page 243 Issue 1 SYSTEM MESSAGES ➃ Detailed information on changing Dch ➄ Status of the Primary/Back-up Dch ➅ EVENT No.b3 b2 b1 b0 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b0, b1: 00 = Change from Primary Dch to Dch for Back-up 01 = Change from the Dch for Back-up to Primary Dch 10 = Primary Dch Changeover to ACT status 11 = Back-up Dch Changeover to ACT status b2, b3: The way of changing 00 = Changed by the MAT 01 = Changed by the MB switch of the circuit card 02 = Changed by placing Dch to Make-Busy 03 = Unknown b0-b2: Status of Primary Dch 0 = In service (ACT status) 1 = STBY 2 = Out of Service 3 = Make Busy 4 = Changing the status from STBY to In Service 5 = Manual Changeover out of service b3-b5: Status of Back-up Dch 0 = In service (ACT status) 1 = STBY 2 = Out of Service 3 = Make Busy 4 = Changing the status from STBY to In Service 5 = Manual Changeover out of service b0-b7: EVENT No.
CHAPTER 3 NDA-24307 Page 244 Issue 1 SYSTEM MESSAGES This message displays when the MUX (PH-PC36) card has a clock failure in one of the dual systems. ➀ MUX Card Location and System Status ➁ Scan Data See Chapter 5 for repair procedure. 1: XXXX 0000 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000 ➀ ➁ 4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000 7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000 b4 b3 b2 b1 b0 b3 b2 b1 Default Alarm: MN23-YMUX Clock FailureDefault Grade: 3Grade Modified: Lamp Modified: b0-b1: Unit number b2: MG number b3: 0/1 = MUX No. 0 system/MUX No. 1 system b4: 0/1 = ACT/STBY Scan Data:Clock alarm information on the faulty MUX card b1: 0/1 = -/FH failure for 2M PCM Highway b2: 0/1 = -/CLK failure for 2M PCM Highway b3: 0/1 = -/4M CLK failure for PM
NDA-24307 CHAPTER 3 Page 245 Issue 1 SYSTEM MESSAGES This message displays when the MUX (PH-PC36) card has a clock failure in both of the dual systems. ➀ MUX Card Location ➁ Scan Data 1 ➂ Scan Data 2 See Chapter 4 for the Circuit Card Replacement Procedure. 1: XXXX XX00 0000 0000 2: 0000 0000 0000 0000 3: 0000 0000 0000 0000 ➀ ➁ ➂ 4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000 7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000 b2 b1 b0 b3 b2 b1 b3 b2 b1 Default Alarm: MN23-ZBoth MUX Clock FailureDefault Grade: 3Grade Modified: Lamp Modified: b0-b1: Unit No. b2: MG No. Scan Data 1:Details on clock alarm information (ACT side) b1: 0/1 = -/FH failure for 2M PCM Highway b2: 0/1 = -/CLK failure for 2M PCM Highway b3: 0/1 = -/4M CLK failure for PM Scan Data 2:Details on clock alarm information (STBY side) b1: 0/1 = -/FH failure for 2M PCM Highway b2: 0/1 = -/CLK failure for 2M PCM Highway b3: 0/1 = -/4M CLK failure for PM
CHAPTER 3 NDA-24307 Page 246 Issue 1 SYSTEM MESSAGES This message displays when the MAT is log-in or log-out. ➀ I/O Port No. and MAT Status ➁ Command Name ➂ User Name 1: XX00 XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX ➀ ➁ ➁ ➁ ➁ ➁ ➁ ➂ ➂ ➂ ➂ ➂ ➂ ➂ ➂ ➂ ➂ ➂ ➂ ➂ ➂ ➂ ➂ 4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000 7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000 b7 b6 b5 b4 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 Default Alarm: NON26-NMAT LogDefault Grade: 0Grade Modified: Lamp Modified: b0-b2: I/O Port No. 000 = Port 0 001 = Port 1 010 = Port 2 011 = Port 3 100 = Port 4 101 = Port 5 110 = Port 6 111 = Port 7 b4-b7: 0000 = Login 0001 = Logout 0010 = Command is startup 0011 = Command exit b0-b7: Command name b0-b7: MAT user name
NDA-24307 CHAPTER 3 Page 247 Issue 1 SYSTEM MESSAGES This massage is issued when a call, originated via a station/trunk, is judged as malicious, and then, the details on the call is traced with the called party pressing an access code or the “Call Trace” key. [When a call is originated from a station] Information on Called Party (Informer) Fusion Point Code (FPC) (Hex.) Note Tenant No. (Hex.) Note Physical Station No. (Hex.) Note User Group No. (UGN) (Hex.) Note Telephone No. (Hex.) Note 1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX ➀➁➂ ➃➄➅➆➇➈ 4: XXXX XXXX XXXX XXXX 5: XXXX XX00 0000 0000 6: 0000 0000 0000 0000 ➉ 7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 Default Alarm: NON26-RCall TraceDefault Grade: 2Grade Modified: Lamp Modified: 11 b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 1 1 2b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 2 3b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 dc4 dc5 3 4b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 4 5b4 - b7 b0 - b3 b4 - b7 b0 - b3 dc0 dc1 dc8 dc9 dc2 dc3 dc10 dc11 dc4 dc5 dc12 dc13 dc6 dc7 dc14 dc15 5
CHAPTER 3 NDA-24307 Page 248 Issue 1 SYSTEM MESSAGES Information on Malicious call Kind of Call (Hex.) Note10H=Call from a station Fusion Point Code (FPC) (Hex.) Note Tenant No. (Hex.) Note Physical Station No. (Hex.) Note User Group No. (UGN) (Hex.) Note Telephone No. (Hex.) Note Note: Each No./code is output in hexadecimal. Detailed meanings are as follows: Output Data (Hex.) Actual Meaning 1~9→1~9 A→0 B→* C→# 0→blank b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 6 7b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 7 8b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 8 9b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 dc4 dc5 9 10b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 10 11b4 - b7 b0 - b3 b4 - b7 b0 - b3 dc0 dc1 dc8 dc9 dc2 dc3 dc10 dc11 dc4 dc5 dc12 dc13 dc6 dc7 dc14 dc15 11
NDA-24307 CHAPTER 3 Page 249 Issue 1 SYSTEM MESSAGES When a call is originated from a trunk Information on Called Party (Informer) Fusion Point Code (FPC) (Hex.) Note Tenant No. (Hex.) Note Physical Station No. (Hex.) Note User Group No. (UGN) (Hex.) Note Telephone No. (Hex.) Note 1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX ➀➁➂ ➃➄➅ 4: XXXX XXXX XXXX XXXX 5: XXXX 0000 0000 0000 6: 0000 0000 0000 0000 ➆ 7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 1b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 1 2b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 2 3b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 dc4 dc5 3 4b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 4 5b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 dc4 dc5 dc6 dc7 dc8 dc9 dc10 dc11 dc12 dc13 dc14 dc15 5
CHAPTER 3 NDA-24307 Page 250 Issue 1 SYSTEM MESSAGES Information on Malicious Call Kind of Call (Hex.) Note20H=Call from a trunk Calling No. of Trunk Call (Caller ID) (Hex.) Note, Note 1 Note: Each No./code is output in hexadecimal. Detailed meanings are as follows: Output Data (Hex.) Actual Meaning 1~9→1~9 A→0 B→* C→# 0→blank Note 1:If the number of the trunk call (Caller-ID) cannot be identified, the data here is output as “0”. b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 6 7b4 - b7 b0 - b3 dc0 dc1 dc2 dc3 dc4 dc5 dc6 dc7 dc8 dc9 dc10 dc11 dc12 dc13 dc14 dc15 dc16 dc17 dc18 dc19 dc20 dc21 dc22 dc23 dc24 dc25 dc26 dc27 dc28 dc29 dc30 dc31 7
NDA-24307 CHAPTER 3 Page 251 Issue 1 SYSTEM MESSAGES This message is issued when the connection error related to external LAN Interface equipment occurs in the system. ~ IP Address for external equipment in which error has been detected. (Hex.) , Port No. (Client Port No.) (Hex.) Socket No. (Used Socket No.) (Hex.) Error Code (TCP/IP Error Code) (Hex.) See Table 3-2. TCP/IP Part Application Part 1: XXXX XXXX XXXX XXXX 2: XXXX XXXX XXXX XXXX 3: XXXX XXXX XXXX XXXX ➀ ➁ ➂ ➃ ➄ ➅ ➆ ➇ ➈ ➉ 4: 0000 0000 0000 0000 5: 0000 0000 0000 0000 6: 0000 0000 0000 0000 7: 0000 0000 0000 0000 8: 0000 0000 0000 0000 9: 0000 0000 0000 0000 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 Default Alarm: SUP26-VLAN Interface Error ReportDefault Grade: Grade Modified: Lamp Modified: 1112131415161718192021222324 14 56 7 8
CHAPTER 3 NDA-24307 Page 252 Issue 1 SYSTEM MESSAGES Table 3-2 Error Code Output Data (Hex.)DefinitionOutput Data (Hex.)Definition BSD SOCKET ERROR 58 Address family not supported 10 User parameter error PROTOCOL FAMILY 11 Host not reachable 59 Address already in use 12 Timeout 60 Can’t assign requested address 14 Protocol error 61 Network is down 15 No buffer space 62 Network is unreachable 16 Connection block invalid 63 Network dropped connection 17 Invalid pointer argument RESET 18 Operation would block 65 Connection reset by peer 19 Message too long 67 Socket is already connected 20 Protocol not available 68 Socket is not connected 50 Destination address required 69 Can’t send after socket shutdown 52 Protocol wrong type for socket 72 Connection refused 54 Protocol not supported 73 Host is down 55 Socket type not supported 76 Operation already in progress 56 Operation not supported on socket 77 Operation now in progress 57 Protocol family not supported