3 Call data 
The Call Information Logging function generates records for storage of call data. Each record contains data for one call. All types of calls can be registered, e.g. internal calls, outgoing external calls and abandoned calls and also failed calls (calls to busy party and calls to vacant numbers). 
The following call data can be included in a record: 
•	Date 
•	End time 
•	Start time 
•	Call duration 
•	Calling party's number 
•	First and second access code 
•	Time in queue to a busy external line or route 
•	Queuing time for incoming call to PABX operator 
•	Ring time duration 
•	Queue time duration 
•	Dialled number 
•	Number of metering pulses 
•	Authorization Code 
•	Account Code 
•	Outgoing/Incoming External line identification 
•	Condition code 
Note 	Note: The record data for each party may include some of the following fields: 	
•	Codec type 
•	Cumulative number of packets lost 
•	Estimated throughput 
•	Fraction lost rate 
•	Mean estimated end to end delay 
•	Mean jitter 
•	Packet lost rate 
•	Simple R-value 
•	Extension TCP/IP address 
These output fields belong to the QoS mechanism that is Not relevant for MX-ONE, and should therefore be ignored. 
3.1 Condition data for call data 
The condition data is the key element in the call record. It designates the type of call that was made. 
Condition code field used may have either one, two or three characters or a user defined string, The one, two or three character codes are shown below. The condition fields with two or three characters width allow a more detailed description of the call case. 
The user defined condition code string can provide a printout in plain text to enhance readability. The default for the custom string is to use the tree character codes. 
Condition data are divided into segments and positions. Depending on the segments, condition codes for one, two and three character width will differ. Segments indicates the type of call. For further clarifications see parameter description for CALL INFORMATION LOGGING . 
3.1.1 One character condition code (type of call that consists of one characters): 
Example of some of the condition codes used for Segment 0 (zero). 
•	( ) Outgoing call 
•	(A) Call handled by a PABX operator 
•	(B) Calls to a busy party 
•	(C) Abandoned calls 
•	(D) Extremely long call duration 
•	(E) Group call pickup calls 
•	(F) Group Hunting calls 
•	(G) Call has been connected with alternative route selection 
•	(H) Recall to route 
•	(I) Incoming call or tandem call 
•	(J) Internal call 
•	(K) Calls to vacant numbers 
•	(L) Conference call 
•	(M) Least cost routing 
•	(N) Dialled party not equal to answering party 
•	(Q) Malicious Call Tracing 
•	(R) Intrusion 
•	(T) Transferred call 
•	(W) Call terminated due to route optimization 
•	(X) External follow me 
•	(Y) Call established due to route optimization 
All these condition codes are the same across all the Segments, but some will differ. i.e., single character condition codes falling under Segment 1 for Long duration calls will always displays D (for all types of traffic cases). 
Single character condition codes for the traffic cases, Operator Extended (A), ECF (X), Transfer (T), Route optimization (Y), LCR(M), MCT(Q), Call terminated due to Route optimization (W) will be same across all the Segments 2, 3, 5, 6 and 7. Single character condition code for the remaining cases will change depending on the type of call. 
Single character condition codes for the traffic case, Group Hunt Calls displays only F for the Segment 3. Similarly Group Call Pickup calls displays only E for the Segment 5. Similarly Direct Diversion calls and Diversion on Busy or Diversion on No Reply displays only D for Segment 6 and Segment 7, for the remaining cases displays N for all the Segments. 
3.1.2 Two character condition code (type of call that consists of two characters): 
•	(DO) Long outgoing call /Direct Divert /Diversion on Busy /Diversion on No Answer outgoing call 
•	(DA) Long PABX operator extended call /Direct Diverted /Diversion on Busy /Diversion on No Reply calls Extended by operator 
•	(DI) Long incoming call /Direct Diverted /Diversion on Busy /Diversion on No Reply incoming calls 
•	(DJ) Long internal call /Direct Diverted /Diversion on Busy /Diversion on No Answer internal calls 
•	(DX) Long external follow me call 
•	(NJ) Dialled party is not the answering party on an internal call 
•	(NI) Incoming DID call when the answering party was not the dialled party 
•	(NT) Dialled party is not the answering party on a transferred call 
•	(CI) Abandoned non-DISA call for Segment 0 
•	(CJ) Abandoned internal call for Segment 0 
•	(CO) Abandoned outgoing call in a private network for Segment 0 
•	(FC) Abandoned Group Hunting outgoing /Incoming /Internal calls for Segment 3 and Segment 7 
•	(DC) Abandoned outgoing /Incoming /Internal call due to Direct Diversion /Diversion on Busy /Diversion on No Reply in a private network for Segment 6 and Segment 7 
All these condition codes are the same across all the Segments, but some will differ. i.e., double character condition codes falling under Segment 1 for Long duration calls will always displays D and followed by the traffic case (for all types of traffic cases), similarly double character condition codes falling under Segment 4 for Data call will always displays V and followed by the traffic case (for all traffic cases). 
Double character condition codes for the traffic cases, Operator Extended (A), ECF (X), Transfer (T), Route optimization (Y), LCR(M), MCT(Q), Call terminated due to Route optimization (W) will be same across all the Segments 2, 3, 5, 6, and 7 followed by a blank SPACE. Double character condition code for the remaining cases will change depending on the type of call. 
Double character condition codes for the traffic case, Group Hunt Calls displays only F for the Segment 3 and follows the traffic case. Similarly Group Call Pickup calls displays only E for the Segment 5 and follows the traffic case. Similarly Direct Diversion calls and Diversion on Busy or Diversion on No Reply displays D and follows the traffic case, for Segment 6 and Segment 7. Double character condition code for the remaining cases displays N and follows the traffic case, for the remaining Segments. 
3.1.3 Three character condition code (type of call that consists of three characters): 
•	(NCI) Abandoned non-DISA call, dialled party is not the answering party. 
•	(NCJ) Abandoned internal call, dialled party is not the answering party. 
•	(NCO) Abandoned outgoing private network call, dialled party is not the answering party. 
•	(NCZ) Abandoned DISA call, dialled party is not the answering party. (Not relevant in MX-ONE). 
•	(FCI) Abandoned non-DISA incoming Group Hunting Call. 
•	(FCJ) Abandoned internal Group Hunting Call. 
•	(FCZ) Abandoned DISA call. (Not relevant in MX-ONE) 
•	(FCO) Abandoned outgoing Group Hunting Call. 
•	(DCI) Abandoned incoming Direct Diversion Call. 
•	(DCJ) Abandoned internal Direct Diversion Call. 
•	(DCO) Abandoned outgoing Direct Divert Call. 
•	(DRI) Incoming call Diverted on No Answer. 
•	(DRJ) Internal call Diverted on No Answer. 
•	(DRO) Outgoing call Diverted on No Answer. 
•	(DRT) Transferred call Diverted on No Answer. 
•	(DA) Operator Extended call after Direct Diversion to the operator. 
•	(DRA) Operator Extended call after Diverted on No Answer to operator 
All these condition codes are the same across all the Segments, but some will differ. i.e., triple character condition codes falling under Segment 1 for Long duration calls will always displays D and followed by the traffic case and a space (for all types of traffic cases). 
Triple character condition codes for the traffic cases, Operator Extended (A), ECF (X), Transfer (T), Route optimization (Y), LCR(M), MCT(Q), Call terminated due to Route optimization (W) will be same across all the Segments 2, 3, 5, 6, and 7 and followed by two blank SPACEs. Triple character condition codes for the remaining cases will change depending on the type of call. 
Triple character condition codes for the traffic case, Group Hunt Calls display only F for the Segment 3 and follows either the traffic case or a combinational condition code or a space. Similarly Group Call Pickup calls display only E for the Segment 5 and follows either the traffic case or a combinational condition code or a space. Similarly Direct Diversion calls and Diversion on Busy or Diversion on No Reply displays D and follows either the traffic case or a combinational condition code or a space, for Segment 6 and Segment 7. Triple character condition code for the remaining cases displays N and follows either the traffic case or a combinational condition code or a space Segments. 
Triple character condition codes falling under Segment 1 for all the traffic cases will display only the appropriate condition code and followed by two spaces. 
3.1.4 User defined condition string 
User defined condition code strings can be set with I/O command and will provide a readable string associated with any segment and position. The default is to use the three character format when no custom specification exists. This data field is available in the general subtype. 
4 Output types and subtypes 
Commands can be entered to select output type and subtype. The output type is generally describing the transport mechanism and the target where the data is written. The subtype is describing the formatting rules that apply. The format string is used to actually order the formatter to produce the output in the desired way. 
Each output can be used independently from any other output regarding type, subtype and formatting rules. 

Table 4-1 Output types and subtypes 
Type 	Subtype 	Description 	
sql. 	postgresql 
none 	Stores all. (no selection possible) 
Stores nothing 	
file. 	none 
commaSeparated 
xml 
general 
fp15 
mdfp15 
asb501 
asbumdfp15 
demo1 
demo2 	Stores nothing 
Stores all. (no selection possible) 
Stores all. (no selection possible) 
Scripting for formatting and selection 
Scripting for selection 
Scripting for selection 
Scripting for selection 
Scripting for selection 	
tcp. 	commaSeparated 
xml 
general 
fp15 
mdfp15 
asb501 
asbumdfp15 
demo1 
demo2 	Stores all. (no selection possible) 
Stores all. (no selection possible) 
Scripting for formatting and selection 
Scripting for selection 
Scripting for selection 
Scripting for selection 
Scripting for selection 
	
v24. 	commaSeparated 
xml 
general 
fp15 
mdfp15 
asb501 
asbumdfp15 
demo1 
demo2 	Stores all. (no selection possible) 
Stores all. (no selection possible) 
Scripting for formatting and selection 
Scripting for selection 
Scripting for selection 
Scripting for selection 
Scripting for selection 	
4.1 Output types 
Each output can be assigned to an external device, file or TCP/IP device by I/O command. 
All outputs are working independently and can be active all at the same time, writing the same information on several outputs or using different script filters to output selected information on different outputs as desired. 
SQL type is used when commutating with an SQL data base. It can be an internal or external data base. 
The type "file" is stored in the file system, locally or over NFS. The data will be stored as daily files during a week on the hard disk before over written. Each file should have a distinctive file name. In addition to the given file name the system will add a "day number" to the name which reflects the day it was produced (example: callData.1.xml callData.2.xml 1= monday,2= tuesday...). 
The type "tcp" can be used to connect to an external computer with an application that will accept a TCP/IP stream of data in the format written. 
The type "V24" can be used writing to a serial port, a parallel printer port, or any type of streaming device in the local computer. 
4.2 Output subtypes 
PostgreSQL format is always writing all valid data to the data base, and it assumed that the post processing will take care of all filtering and deleting of not wanted data. 
Comma separated and XML format is also writing all data but in a readable form. 
The fixed subtypes fp15, mdfp15, asb501 and asbumdfp15 each have a predefined format with fixed fields and preassigned widths defined. If the width of the field is defined larger than the actual width, the unused position is padded with spaces. On the other hand, if the width of the field is defined smaller than the actual width, a truncation will occur. 
The subtype "general" will allow the customer to tailor a script to output virtually any printout format. In fact subtypes fp15, mdfp15, asb501, asbumdfp15, demo1 and demo2 are made this way internally. 
The demo1 and demo2 formats are just sample format that can be used, but is made available to demonstrate the potential of the script language, and the user friendliness that can be achieved by using a verbose printout. 
For more details, refer to the command description for CALL INFORMATION LOGGING , CL and the parameter description for CALL INFORMATION LOGGING . 
5 Output formatting 
I/O command is used to set the time zone to use for the time information in printouts for the fixed output formats (fp15, mdfp15, asb501 and asbumdfp15). Thus keeping compatibility with md110 but allowing use of UTC to prevent problems with normal/summer time. 
Commands can be entered to determine what calls should be output to external equipment. This is done by defining a formatting string per output by I/O command. 
The format string is defined in a script language and can filter the output based on all data available in the call logging data. 
Any field in the output can be tested and used to filter the output of data. 
For subtype "general" the format string is also used to format the data output. 
6 CIL Heartbeat 
This facility is used to monitor the overall status of an ASP 113 01. It is activated by command and the record is generated periodically with the time interval of 15 minutes. The Heartbeat record will be output to the ordinary CL output file. 
Heartbeat is only possible to initiate for the types v24 and tcp. 
The following data are included in the Heartbeat record: 
•	Year 
•	Month 
•	Day 
•	Hour 
•	Minutes 
•	Text HEARTBEAT FROM 
•	Exchange ID 
7 Capacity 
How to set up a system is dependent on the size of the system, what output devices and facilities are to be used. 
Calculations must be made, when using hardware devices (e.g. V24) on communication speed and the number of characters to print per call. Consider to use more than one device if the device is to slow, then more outputs can be used with different filters. With this method a simple load sharing is created. 
7.1 Maximum capacity independent of output devices 
Below follow the maximum capacities independent of the output devices. 
Further on in the document information for each output device will follow. 
•	Maximum number of outputs per LIM is 10. 
•	Maximum number of active outputs per LIM is 10. 
•	Maximum number of data forwarding positions per LIM is 3. 
•	Maximum number of simultaneous calls to be recorded per LIM is 500. 
•	Considerations have to be taken if the SQL data base should reside in the same computer as the telephone application or on a separate (external) computer. In a situation with less than 7 calls/second less than 70 000 call records in the data base and low query rate, the data base can coexist on the same computer. If more than 20 calls/second and more than 200 000 call records in the data base and high query rate a high, an external data base server is needed. 
7.2 System reliability