NEC Neax 2400 Imx System Operations And Maintenance Manual

							CHAPTER 6 NDA-24238
Page 424
Revision 3.0
SYSTEM OPERATIONS
(2) Identifier 2: Sending Data Text
A text for sending billing data in response to “(1) Data Request Text” from the client.
Text sending direction: Client   Server
The number of billing data records is 64 or less.
(3) Identifier 3: Server Response Text
A text to be sent to the client when there is no billing data to send in response to “(1) Data Request Text”
or as a response to a “(5) Status Monitoring Text.”
Text sending direction: Client   Server
(4) Identifier 4: Client Response Text
A response text to be sent to the server by the client which has received the data by a “(2) Sending Data
Te x t . ”
Text sending direction: Client   Server
Data length
(XXXXX) Text 
identifier 
(2) S
Y
NSequence
No. Device
No.Billing data 
(IMX Format)Parity
Note
Note:Text format of billing data is IMX format only. (Refer to Section 7.2.9, Text Format
of Centralized Billing - Fusion.)
Data length
(00003) Text 
identifier 
(3) S
Y
NParity Device
No.Response
No.
Data length
(00002) Text 
identifier 
(4) S
Y
NParity Device
No.Se-
quence
No.ACK/
NAK 
						

							NDA-24238 CHAPTER 6
Page 425
Revision 3.0
SYSTEM OPERATIONS
(5) Identifier 5: Status Monitoring Text
A text for use in monitoring the server status from the client’s viewpoint or the client from the server’s
viewpoint. At the same time, the text is used to notify the server of the client status.
Text sending direction: Client   Server
(6) Identifier 6: Connection Disconnect Text
A text to be sent from the client to the server to disconnect the connection. In response to this text, the
server promptly performs processing to disconnect the connection.
Text sending direction: Client   Server
8. TRAFFIC MANAGEMENT
To obtain the value of common equipment usage, the system provides traffic measurement feature. It can im-
prove the system efficiency.
8.1 Kind of Traffic Measurement
Table 6-5 shows the kinds of traffic measurements.
Table 6-5  Traffic Measurement Types 
TYPEKIND OF
MEASUREMENTDESCRIPTION
1* Terminal Traffic 
MeasurementMeasurement of traffic on a per LENS basis, and measurement of the total traffic on 
a PIM basis. 
2* Route Traffic 
MeasurementMeasurement of traffic on a per route basis. 
3* Station Peg Count Measurement of the number of outgoing connections, intra-office calls, outgoing 
C.O. line calls, Tie Line calls, etc. originated by each station.
Data length
(00005) Text 
identifier 
(5) S
Y
NParity Device
No.Client
device
informationACK/
NAK
Data length
(00003) Text 
identifier 
(6) S
Y
NParity Device
No.ACK/
NAK 
						

							CHAPTER 6 NDA-24238
Page 426
Revision 3.0
SYSTEM OPERATIONS
Note:
Asterisk (*) identifies the traffic measurements that can be saved on the HD of the MAT.
4* ATTCON Peg Count Measurement of the number of each type of call handled at the ATTCON/
DESKCON.
5* Route  Peg  Count Measurement of the number of various types of call connections on a per route basis. 
6 Service Peg Count Measurement of the number of times the following services are operated:
Call Hold
Call Back
Executive Right of Way
Call Waiting
Call Pickup - Group
Call Pickup - Direct
Call Forwarding - All Calls
Call Forwarding - Busy Line
Call Forwarding - Don’t Answer
Speed Calling - System
Speed Calling - Station
Off-Hook Outgoing Trunk Queuing
Outgoing Trunk Queuing
Consultation Hold - All Call
Call Transfer - All Calls
Three-Way Calling
8 UCD Route Peg Count Measurement of the number of incoming calls, answered calls, and abandoned calls 
handled at UCD Groups on a per route basis.
9 UCD Group Peg Count Measurement of the number of incoming calls, answered calls and abandoned calls 
on a UCD Group basis.
10 UCD Station Peg Count Measurement of the number of incoming calls, answered calls and abandoned calls 
for each station on a UCD Group basis.
15 ATT Answer Peg Count Measurement of the number of answered calls handled by each attendant.
18 Connection Route Peg 
CountMeasurement of the number of various type of call connection on a connection route 
basis.
19 Connection Route Traffic Measurement of traffic on a connection route basis.Table 6-5  Traffic Measurement Types (Continued)
TYPEKIND OF
MEASUREMENTDESCRIPTION 
						

							NDA-24238 CHAPTER 6
Page 427
Revision 3.0
SYSTEM OPERATIONS
8.2 Operating Procedure 
1. Procedure for Set-up and Start
The procedure to set up and start the traffic measurement is as follows:
STEP 1
By using the ASYD/ASYDN command, assign the necessary system data as follows:
When performing traffic measurement on a node basis:
 SYS1, INDEX8 (Number of Tenants)
 SYS1, INDEX9 (Number of Attendant Consoles)
 SYS1, INDEX47, bit 0 (Unit of Traffic Measurement):  0/1 = CCS/Erlang
 SYS1, INDEX47, bit 7 (Traffic Measurement Service):  0/1 = Out/In Service      Assign “1.”
When performing traffic measurement on a network basis (via TCP/IP):
 SYS1, INDEX8 (Number of Tenants)
 SYS1, INDEX9 (Number of Attendant Consoles)
 SYS1, INDEX47, bit 0 (Unit of Traffic Measurement):  0/1 = CCS/Erlang
 SYS1, INDEX47, bit 7 (Traffic Measurement Service):  0/1 = Out/In Service      Assign “1.”
STEP 2
By using the ATRF/ATRFN command, assign the traffic measurement programs as follows:
When performing traffic measurement on a node basis:
Assign traffic measurement “TYPE” (
Note), “PORT” number to be used, and the output 
“INTERVAL” and “Time (HOUR/MINUTE),” etc. For more details, see the AT R F command in 
CHAPTER 8.
When performing traffic measurement on a network basis (via TCP/IP):
Assign traffic measurement “TYPE” (
Note), “PORT” number to be used, and the output “INTER-
VAL” and “Time (HOUR/MINUTE),” etc. For more details, see the AT R F command in CHAP-
TER 8.
Note:You can select one measurement “TYPE” at a time. If you need two or more measurement
“TYPE,” repeat the same steps, following the entry of this command.
STEP 3: Terminate all the MAT commands.
An image of IMX “MAT Menu” is shown in Figure 6-21. Terminate all MAT commands, and
make sure no commands are currently running via the “Processes” button.
STEP 4: Set the programmed Traffic Measurement in routine operation.
Click the “Scan New Alarms/Traffic” and “Collect New Alarms” buttons on the IMX “MAT
Menu” (confirm the clicked buttons remain in the pressed state). Then, the Traffic Measurement is
activated as programmed.
END
ASYD
ASYDN
AT R F NAT R F 
						

							CHAPTER 6 NDA-24238
Page 428
Revision 3.0
SYSTEM OPERATIONS
Figure 6-21   IMX “MAT Menu” Display Image (Example)
Figure 6-21 shows the IMX “MAT Menu” display image. The display should look similar to the following:
Scan New Alarms/Traffic
Office Name (assigned by ASYD/AOFC command
Collect New Alarms
Collect New Traffic
Abor t Data Collections
View Scanning Log
Major Alarm Indicator
Minor Alarm Indicator
Supervisory Message Indicator
Traffic Data Indicator
About
Log Manager
Log out
Configure
Log in
Processes
Command Name Input Text Box 
						

							NDA-24238 CHAPTER 6
Page 429
Revision 3.0
SYSTEM OPERATIONS
(2) Data Output - Details on DTFD/DTFDN Command
To obtain the collected Traffic data, you can use the “DTFxxx” or “DTFxxxN” command as shown below.
The commands can be activated by your direct log-in operation onto the MAT, but in normal cases, the com-
mands are to be activated automatically at predetermined intervals assigned by the ATRF/ATRFN command.
Also, each command below corresponds to the Traffic Measurement “TYPE” assigned by the ATRF/ATR-
FN command.
When performing traffic measurement on a node basis:
When performing traffic measurement on a network basis (via TCP/IP):
Note:For information on the command display images, see Figure 6-22, Figure 6-23, and Figure 6-24.
Measurement “TYPE”
(by ATRF Command)Command
NameFull Command Name
1Terminal TrafficDTF101Display of Terminal Traffic Data
2Route TrafficDTF102Display of Route Traffic Data
3Station Peg CountDTF103Display of Station Peg Count Data
4ATTCON Peg CountDTF104Display of Attendant Peg Count Data
5Route Peg CountDTF105Display of Route Peg Count Data
6Service Peg CountDTF201Display of Service Peg Count Data
8UCD Route Peg CountDTF301Display of UCD Route Peg Count Data
9UCD Group Peg CountDTF302Display of UCD Group Peg Count Data
10UCD Station Peg CountDTF303Display of UCD Station Peg Count Data
15ATT Answer Peg CountDTF501Display of Attendant Answering Peg Count Data
18Connection Route Peg CountDTF601Display of Connection Route Peg Count Data
19Connection Route TrafficDTF602Display of Connection Route Traffic Data
Measurement “TYPE”
(by ATRFN Command)
Command 
NameFull Command Name
1Terminal TrafficDTF101NDisplay of Terminal Traffic Data for Fusion Network
2Route TrafficDTF102NDisplay of Route Traffic Data for Fusion Network
3Station Peg CountDTF103NDisplay of Station Peg Count Data for Fusion Network
4ATTCON Peg CountDTF104NDisplay of Attendant Peg Count Data for Fusion Network
5Route Peg CountDTF105NDisplay of Route Peg Count Data for Fusion Network
6Service Peg CountDTF201NDisplay of Service Peg Count Data for Fusion Network
8UCD Route Peg CountDTF301NDisplay of UCD Route Peg Count Data for Fusion Network
9UCD Group Peg CountDTF302NDisplay of UCD Group Peg Count Data for Fusion Network
10UCD Station Peg CountDTF303NDisplay of UCD Station Peg Count Data for Fusion Network
15ATT Answer Peg CountDTF501NDisplay of Attendant Answering Peg Count Data for Fusion Network
18Connection Route Peg CountDTF601NDisplay of Connection Route Peg Count Data for Fusion Network
19Connection Route TrafficDTF602NDisplay of Connection Route Traffic Data for Fusion Network 
						

							CHAPTER 6 NDA-24238
Page 430
Revision 3.0
SYSTEM OPERATIONS
Figure 6-22   DTFD Command Display Image (Example)
Figure 6-22 shows the DTFD command display image (example). The DTFD/DTFDN command should look
similiar to this.
Traffic Data
Check box to specify the “Traffic Data” 
TYPE.
Data collecting Log
This area displays the current Traffic 
Measurement data, based on the selected 
“Traffic Data” TYPE.
Tool Buttons
 Collect Data
Used to collect the Traffic report with regard to the selected “Traffic Data” TYPE. The result test is shown in
the “Data Collection Log” display area.
Stop
Used to quit the currently performed Traffic Data collection.
Print Log
Used to print out the text data now displayed in the “Data Collection Log” area
 View Database
Used to view the whole data (based on the selected “Traffic Data” TYPE), so far stored in the database. More
details are shown in figure 6-11-3.
 Clear Database
Used to delete (clear) the whole data (based on the selected “Traffic Data” TYPE), so far stored in the data-
base.
 Log Colors
Used to designate/change the text font color of the “Data Collection Log” display area.
Exit
Used exit this command. (Note that the database contents are not cleared by pressing this button.) 
						

							NDA-24238 CHAPTER 6
Page 431
Revision 3.0
SYSTEM OPERATIONS
Figure 6-23   “Listup Report” Window when “View Database” is Selected (Example)
Figure 6-24   “Export” Dialog for Traffic Report Text File Saving
Form at:Destination:
OKCancel
Disk fileCharacter separated values
Export
The dialog box, as shown below, appears, if the “Save Text File” button is selected on the “Listup Report” window 
(see Figure 6-23 above). If the file is to be saved:
1.  Select “Character-separated values” on the “Format”
 list box.
2.  Select “Disk file” on the “Destination” list box.
3.  Click OK.
After these steps, a new dialog, asking the saved file name and directory, also appears. Then, complete the data saving by
filling out these necessary items.
 
 
  
CloseCancel
[ TROUBLE :: DTFA ]
Start Tim e:     12/25  12:00  
End Time:      12/25  13:00  
M odule  Group  Unit        G roup        Type            Level 0            Level 1            Level 2           Level 3            L e ve l 4              L e ve l 5            L e v e l 6             L e v e l 70                       0              0               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0              1               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0              2               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0              3               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0              4               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0              5               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0              6               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0              7               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0              8               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012 
0                       0              9               CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0             10              CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0             11              CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0             12              CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0             13              CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
0                       0             14              CCS            09252.000       09215.859      09179.718       09143.576       09107.435       09071.294      09035.153       08999.012
 
 *  Term inal Traffic Data (DTF101) *
ABCDE 
L istu p   R eport
1  /  269 of 69T otal: 69100%
 
 
 
 
Figure 6-23 shows a sample image of the “Listup Report” window for the DTFD/DTFDN command. This window appears by taking
the following operations, and is used to obtain a sequence of Traffic data, so far collected and stored in the database. The window is
also used to save the Traffic data text (now displayed in the window) onto your desired PC directory.
- To activate this window:
1. Designate a specific “Traffic Data” TYPE out of the DTFD/DTFDN command check boxes. (see Figure 6-22).
2. Press the “View Database” button on the left-bottom part of the DTFD/DTFDN command (see Figure 6-22).
Display Area
This area displays the details
on the Traffic report, specified
by the “Page (UP)/Page
(DOWN)” buttons.
Shown here is an example of a 
certain first page of “Terminal
Traffic Data (DTF101).”  
Save Text File
When saving the currently displayed text page, press this button. 
Then, a dialog box, as shown in Figure 6-24, appears.
Page (UP)
Page (DOWN)
Any Traffic data, now in the database, can easily be found via these buttons. Select “UP” or
“DOWN,” according to the text display pattern: “the newest the first, the oldest the last.”
Note
Note:
When this window is activated, the initial text to appear is the newest file data, out of a sequence of Traffic reports. Like
this, the newest text (in the database) appears on the first page, and the next new, the next page. 
						

							CHAPTER 6 NDA-24238
Page 432
Revision 3.0
SYSTEM OPERATIONS
(3) Service Conditions (when performing Traffic Measurement via TCP/IP)
(a) The NDM (network-level) data for the traffic measurement order is replaced/updated, at each time
the system is initialized or data change is requested from the ATRFN command.
(b) When the network-level data is once assigned via the ATRFN command, the node-level data for
ATRF command cannot be changed or modified.
(c) When the network-level data is once assigned via the ATRFN command, the already assigned data
by the ATRF command is not cleared, but becomes ineffective.
(d) When a data transfer error occurs, the following are performed in order:
Traffic measurement is suspended momentarily and system message is displayed (notification
of fault)
Traffic measurement, concerning all the remaining data except for the fault-involved one, is re-
sumed
Retry is made repeatedly for the transfer of fault-involved data, until the fault has been eradicat-
ed
If the fault hasn’t been eradicated still until the time of next measurement routine, the data is
finally discarded, and next traffic measurement routine starts
(e) When the same Individual ATT Numbers exist on the network, the traffic measurement concerning
the ATTCON/DESKCON cannot be performed correctly. 
						

							NDA-24238 CHAPTER 6
Page 433
Revision 3.0
SYSTEM OPERATIONS
9. OFFICE DATA MANAGEMENT
This section explains how to manage various kinds of data such as Call Forwarding Data, Individual Speed
Calling Data, and Office Data, etc.
9.1 Office Data Stored Locations
The office data is stored in the memory (MEM) and on the Hard Disk (HD). While the system is in service,
it operates by the office data stored in the memory. Should the contents of the office data be destroyed due
to trouble, the system restarts its operations by loading the office data from the hard disk into the memory.
The office data of the system in operation is being backed up by the hard disk.
9.2 Office Data Preservation
Since the PBX keeps operating by the assigned office data, be sure to preserve the latest office data. If the
office data is not preserved, all office data must be reassigned if the contents of the data memory have been
destroyed, because of trouble occurrence, etc. The system will remain in a system down state until reas-
signment of the office data is complete.
Practice to verify and confirm the valid office data by routine maintenance is considered an effective
means to prevent loss of the office data and occurrence of trouble due to the office data. For this reason,
be sure to keep the following items near the system at all times so that they may be available when needed.
(1) Office Data Programming Sheets
As the most up-to-date data must be recorded in the sheets, be sure to make entries by pencil.
(2) Floppy Disks for Data Saving
To back up the office data stored on the HD, use floppy disks. The necessary number of Floppy Disks (FD)
is determined by the following factors:
 Mounting capacity of office data depends upon the system data (SYS1, Index30).
 Each floppy disk can save 1MB of data. After a large-scale office data change, in particular which
includes system data, unpredictable failures might occur. To deal with such failures, prepare an FD
for saving the office data before the changing. In addition, prepare an FD for saving the latest office
data.