NEC Neax 2400 Ipx System Operations And Maintenance Manual

							NDA-24307 CHAPTER 6
Page 483
Issue 1
SYSTEM OPERATIONS
7.4.5 Route Advance Information
When a call has been originated by route advancing, the following data is transmitted.
7.4.6 Condition B Information
The 51st through 53rd bytes are Condition B Information. The Condition B Information indicates the
following data:
BYTE
54
55
56
57
58THE CALL ORIGINATES EXAMPLE
0
0
3
0
3
0
59
ROUTE
NUMBER 1
ROUTE
NUMBER 2VIA NO. 3 ROUTE BECAUSE
NO. 30 ROUTE IS BUSY.
DATA
1st DIGIT
2nd DIGIT
3rd DIGIT
1st DIGIT
2nd DIGIT
3rd DIGIT
ROUTE NUMBER 1: The route which was actually used.
ROUTE NUMBER 2: The route which should have been selected first.
OUTPUT NUMBERDATA
C2
C1
C0 BYTE
51
52
53
0, 1 or SPACE
0–3 or SPACE
0–5 or SPACE
C2: 0 = Call is not transferred
1 = Call is transferred
C1: 0 = Normal Call
1 = Call originated by OG trunk queuing
2 = Call originated by dialing with Account Code
3 = Call originated by OG trunk queuing and dialing with Account Code
C0: 0 = Regular Call (Direct Dialing from a station)
1 = Regular Call (Call is made through an ATTCON/DESKCON)
2 = Call through route advance (Direct Dialing from a station)
3 = Call through route advance (Call is made through an ATTCON/DESKCON)
4 = Call through Least Cost Routing (Direct Dialing from a station)
5 = Call through Least Cost Routing (Call is made through a n   A T T C O N / D E S K C O N ) 
						

							CHAPTER 6 NDA-24307
Page 484
Issue 1
SYSTEM OPERATIONS
7.4.7 Call Metering Information
The value of call metering from the Central Office is transmitted via the data from the 92nd byte to
95th byte.
7.4.8 Office Code of Calling (Called) Party and Billing Process Office
The 96th byte through 99th byte indicates the Office Code of Calling (Called) Party terminated via
CCIS Line.
The 100th byte through 103rd byte indicates the Office Code of the office processing centralized
Billing for CCIS Network.
Note:Office Code includes the CCIS line access code.
BYTE
92
93
94
95WHEN 5200 METERING PULSES EXAMPLE
5
2
0
0
ARE RECEIVED FROM C.O. DATA
1000
100
10
1
OFFICE CODE = 812 BYTE
96
97
98
99
100
101
102
103DATA
1st DIGIT
2nd DIGIT
3rd DIGIT
4th DIGIT
1st DIGIT
2nd DIGIT
3rd DIGIT
4th DIGITEXAMPLE
8
1
2
SPACE
8
1
3
SPACEOFFICE CODE = 813OFFICE CODE OF
BILLING PROCESS
OFFICE OFFICE CODE OF
CALLING (CALLED)
PA R T Y 
						

							NDA-24307 CHAPTER 6
Page 485
Issue 1
SYSTEM OPERATIONS
7.4.9 Text Format of SMDR - TCP/IP Interface
When using SMDR - TCP/IP interface, billing information is output to the billing output devices
connected by an external LAN in the form of socket interface as shown in Figure 6-20. 
Figure 6-20   SMDR—TCP/IP Interface Billing Output Devices
Details on the text format for SMDR - TCP/IP Interface are explained below.
(1) Identifier 1: Data Request Text
A text to be sent by the client when it requests the server to send billing data.
Text sending direction: Client   Server
SMDR(A)
(Client)SMDR(B)
(Client)SMDR(C)
(Client)SMDR(D)
(Client)
PBX(Server)
LANBilling Information
Note:A maximum of 4 clients can be designated as SMDR equipment for each LN.
Data length
(00002) Text 
identifier 
(1) S
Y
NParity Device
No. 
						

							CHAPTER 6 NDA-24307
Page 486
Issue 1
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 
(IPX Format)Parity
Note
Note:Text format of billing data is IPX format only. (Refer to Section 7.2.)
Data length
(00003) Text 
identifier 
(3) S
Y
NParity Device
No.Response
No.
Data length
(00002) Text 
identifier 
(4) S
Y
NParity Device
No.Response
No.ACK/
NAK 
						

							NDA-24307 CHAPTER 6
Page 487
Issue 1
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
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-24307
Page 488
Issue 1
SYSTEM OPERATIONS
8. TRAFFIC MANAGEMENT
To obtain the value of common equipment usage, the system provides traffic measurement feature. It can
improve the system efficiency.
8.1 The Kind of Traffic Measurement
Table 6-5 shows the kinds of traffic measurements.
Table 6-5  Traffic Measurement Type s
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.
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. 
						

							NDA-24307 CHAPTER 6
Page 489
Issue 1
SYSTEM OPERATIONS
Note:
Asterisk(*) identifies the traffic measurements that can be saved on the HD of the MAT.
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 
						

							CHAPTER 6 NDA-24307
Page 490
Issue 1
SYSTEM OPERATIONS
8.2 Operating Procedure
8.2.1 Procedure for Set-up and Start
The procedure to set up and start the traffic measurement is as follows:
(1) By using the ASYD/ASYDN command, assign the necessary system data as follows:
START
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.”
 END
(2) By using the ATRF/ATRFN command, assign the traffic measurement programs as follows:
START
When performing traffic measurement on a node basis:
Assign traffic measurement “TYPE” (
Note 1), “PORT” number to be used, and the output
“INTERVAL” and “Time (HOUR/MINUTE),” etc. For more details, see the ATRF command in
CHAPTER 8.
When performing traffic measurement on a network basis (via TCP/IP):
Assign traffic measurement “TYPE” (
Note 1), “PORT” number to be used, and the output
“INTERVAL” and “Time (HOUR/MINUTE),” etc. For more details, see the ATRFN command
in CHAPTER 8.
END
Note 1: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.
(3) Terminate all the MAT commands.
An image of IPX “MAT Menu” is shown in Figure 6-21. Terminate all MAT commands, and make sure
no commands are currently running via the “Processes” button.
(4) Set the programmed Traffic Measurement in routine operation.
Click the “Scan New Alarms/Traffic” and “Collect New Alarms” buttons on the IPX “MAT Menu”
(confirm the clicked buttons remain in the pressed state). Then, the Traffic Measurement is activated as
programmed.
ASYD
AT R F NAT R F ASYDN 
						

							NDA-24307 CHAPTER 6
Page 491
Issue 1
SYSTEM OPERATIONS
Figure  6-21   IPX “MA T  M e n u” Display Image (Example)
Office Name (assigned by ASYD/AOFC command) Scan New Alarms/Traffic
Collect New Alarms
Collect New Traffic
Abort Data Collection
View Scanning Log
About
Log Manager
Log out
Configure
Log in
Processes Major Alarm  Indicator
Minor Alarm  Indicator
Supervisory Message Indicator
Traffic Data Indicator
Command Name Input Text Box
This Figure shows the IPX “MAT Menu” display image. The display should look similar to the following: 
						

							CHAPTER 6 NDA-24307
Page 492
Issue 1
SYSTEM OPERATIONS
8.2.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 commands
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/ATRFN
command.
When performing traffic measurement on a node basis:
When performing traffic measurement on a node network basis :
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
1 Terminal TrafficDTF101Display of Terminal Traffic Data
2 Route TrafficDTF102Display of Route Traffic Data
3 Station Peg CountDTF103Display of Station Peg Count Data
4 ATTCON Peg CountDTF104Display of Attendant Peg Count Data
5 Route Peg CountDTF105Display of Route Peg Count Data
6 Service Peg CountDTF201Display of Service Peg Count Data
8 UCD Route Peg CountDTF301Display of UCD Route Peg Count Data
9 UCD Group Peg CountDTF302Display of UCD Group Peg Count Data
10 UCD Station Peg CountDTF303Display of UCD Station Peg Count Data
15 ATT Answer Peg CountDTF501Display of Attendant Answering Peg Count Data
18 Connection Route Peg CountDTF601Display of Connection Route Peg Count Data
19 Connection Route TrafficDTF602Display of Connection Route Traffic Data
Measurement “TYPE”
(by ATRFN Command)Command
NameFull Command Name
1 Terminal TrafficDTF101NDisplay of Terminal Traffic Data for Fusion Network
2 Route TrafficDTF102NDisplay of Route Traffic Data for Fusion Network
3 Station Peg CountDTF103NDisplay of Station Peg Count Data for Fusion Network
4 ATTCON Peg CountDTF104NDisplay of Attendant Peg Count Data for Fusion Network
5 Route Peg CountDTF105NDisplay of Route Peg Count Data for Fusion Network
6 Service Peg CountDTF201NDisplay of Service Peg Count Data for Fusion Network
8 UCD Route Peg CountDTF301NDisplay of UCD Route Peg Count Data for Fusion Network
9 UCD Group Peg CountDTF302NDisplay of UCD Group Peg Count Data for Fusion Network
10 UCD Station Peg CountDTF303NDisplay of UCD Station Peg Count Data for Fusion Network
15 ATT Answer Peg CountDTF501NDisplay of Attendant Answering Peg Count Data for Fusion Network
18 Connection Route Peg CountDTF601NDisplay of Connection Route Peg Count Data for Fusion Network
19 Connection Route TrafficDTF602NDisplay of Connection Route Traffic Data for Fusion Network