12.8 |
Call Detail Recording Central (CDRC) |
| |
| The HiPath 3000/5000 can transmit consecutive call detail recording central (CDRC) information for each call segment completed or for each incoming call to a connected device. The device is normally a PC for analyzing the received data or a printer.
|
| Call data records can be recorded for external calls that were not completed. For example, this gives the party calling proof that the destination station did not accept the attempted call (marked in the output log with the call time "00:00:00"). The "CDRC outgoing without connection" feature applies to digital external traffic using ISDN and CorNet/Q-SIG and to all stations. With analog external traffic (loop start), a call data record is always recorded, no matter whether "CDRC outgoing without connection" has been configured or not.
|
Additional station number field in the call detail record
|
| With HiPath 3000/5000 from V7 R3 or later, the output line for the call detail record has been extended by an additional station number field. This feature is implemented when the flag LCR station number outgoing or dialed station number incoming is activated in Manager E. The station number field contains:
|
|
•
|
for an outgoing call: the LCR phone number that was actually sent to the exchange following conversion by LCR or
|
|
•
|
for an incoming call: the internal phone number of the station required, that is, the first station dialed.
|
Output of the data to an external output device
|
| The following options are available for exporting the data to an external output device:
|
|
•
|
application programming interface (V.24)
CDRC data is exported to call detail recording applications such as Teledata.
|
|
•
|
PC attendant console port
Users can also forward the CDRC data to a optiClient Attendant (PC attendant console port). This transfers the call data to the Charge.dat file, which is created or updated whenever a new record is entered. You can use software to evaluate this data. A UP0/E card is used for the PC attendant console.
|
|
•
|
LAN interface (Ethernet)
CDRC data can be output to external applications via the LAN interface (Ethernet) using TFTP (client or server) or using a direct TCP/IP connection. The LAN interface only supports the compressed output format (see below).
|
| The CDRC output can be in two different formats:
|
|
•
|
Compressed format (via V.24 / via LAN) for PC or call charge computer
The system outputs all data (including ACCT) without separating spaces, without headers, and without form feed. Call charge pulses, call charge amounts or arithmetic units are output.
|
|
•
|
Long format for printer
The system outputs all data (except ACCT) separated by spaces, with header (in the language selected for the system) and form feed. The call charge amount is output.
|
| The following rules apply to the line format:
|
|
•
|
The carriage return (CR) and line feed (LF) control characters are transmitted at the end of each record.
|
|
•
|
Data not supplied and unused fields are filled with spaces.
|
|
•
|
In compressed format, the data output is consecutive. No form feed (FF) is transmitted.
|
|
•
|
In long format, each page contains a one-line header followed by a blank line. After 62 characters are printed, a form feed automatically executes.
|
| The output contains the following information:
|
|
•
|
Date (at end of call), 8 characters
|
|
•
|
Time (at end of call), 8 characters
|
|
•
|
Number of seized trunk, 3 characters
|
|
•
|
Internal station number (max. 6 digits)
|
|
•
|
Ring duration, 5 characters
|
|
•
|
Call duration, 8 characters
|
|
•
|
External station number (up to 25 digits if available)
|
|
•
|
Call charge pulse/amount, 11 characters (blank in U.S.)
|
|
•
|
Additional information (such as incoming call, outgoing call, transferred call, conference, DISA, call setup charges), 2 characters
|
| The following data is always compressed prior to output:
|
|
•
|
MSN used (up to 11 digits for multi-device connections)
|
|
•
|
LCR access code (trunk access code, 5 digits)
|
|
•
|
LCR route used (path table, 2 digits)
|
|
•
|
Additional data in U.S.:
|
| |
- |
PRI Carrier Identification Code
|
|
|
| All fields are predefined and cannot be changed except for the options mentioned in this section.
|
|
|
|
•
|
The last four digits of the destination number can be suppressed in the call record. If selected, the last four spaces are filled with the symbol "?".
|
|
•
|
The Call Duration field can be suppressed from the record. If selected, this field is blank.
|
|
•
|
Incoming calls can be recorded. The default value is No (only outgoing calls are recorded).
|
|
•
|
A call record is started as soon as an incoming call starts ringing into the system.
|
|
•
|
The individual elements of a call detail record can be separated by a ";" or a pipe "|". Empty fields are not filled with spaces, and therefore, the content of a call detail record is not position-oriented. The sequence and the range of values of the individual elements remain unchanged
Note: A space can also be selected as the separator to ensure downward compatibility. In this case, the output format is position-oriented.
|
|
•
|
Other configurable parameters: which RS-232 port is to be used for the CDRC output and the baud rate (2400, 9600, or 19200).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Printer, call charge computer
|
|
|
|
|
|
|
| 20000 (only in TFTP format)
|
|
|
Dependencies/Restrictions
|
|
|
|
| "Active" call charge output
|
|
| The records are forwarded directly to a printer or other application. If the output device is out of service (e.g. the printer is switched off), a memory with capacity for 300 (150, 50) entries is available, in which the records are buffered.
|
| When the maximum is reached, all subsequent call detail records are lost.
|
|
| "Passive" call charge output
|
|
| With passive call charge output (TFTP servers only), the files are saved in the file "gez.txt". The file may be read out from the system using the TFTP command GET, and has a maximum size of 20 000 records.
|
| When the maximum is reached, all subsequent call detail records are lost.
|
|
|
|
| A system pseudo-answer timer (Artificial End-of-Dial) is used when the call is placed over analog trunks without answer supervision to determine the beginning of the call record
|
|
| CDRC outgoing without connection
|
|
|
•
|
for call attempts that are not allowed (LCR, denied lists).
|
|
•
|
for premature termination of the call attempt.
|
|
|
|
| If call charges arise even before connection setup, they are recorded. regardless of whether or not "CDRC outgoing without connection" has been selected.
|
|
|
|
•
|
Compressed Output Format for Call Details - Output via Application Programming Interface (V.24)
|
| ---------------------------------------------------------------------------------------------------------------------------
|
1 1
0 1 2 3 4 5 6 7 8 9 0 1
12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
--------------------------------------------------------------------------------------------------------------
1 Date (8 digits)
| 2 Time (8)
| | 3 Trunk (3)
| | | 4 internal station number (6 digits)
| | | | 5 Ring duration (5)
| | | | | 6 Call duration (8)
| | | | | | 7 Station number (25)
| | | | | | | 8 Call charges (11) (blank in U.S.)
| | | | | | | | 9 Information element (2)
| | | | | | | | | 10 ACCT (11)
| | | | | | | | | | 11 MSN (11)
| | | | | | | | | | | 12 Seizure
| | | | | | | | | | | code (5)
| | | | | | | | | | | | 13 LCR
| | | | | | | | | | | | route (2)
| | | | | | | | | | | | | ...
| | | | | | | | | | | | | Extension
V V V V V V V V V V V V V V
11.12.0008:23:23 4 16 00:05:2302317324856 12 2 902725 841 (1)
11.12.0009:12:45 3 18 00:01:23834756 34 212345678901 2 (2)
11.12.0009:25:34 2 1100:34 1 (3)
11.12.0010:01:46 1 12 00:12:5383726639046287127384 5 2
11.12.0010:03:42 2 14 05:42:4338449434444495598376 245 2
11.12.0010:23:24 2 15 00:02:221234567890123412???? 83 2 (4)
11.12.0011:12:45 3 18 00:01:23834756 34 2
12.12.0012:23:34 3 1200:1500:03:12 1 (5)
12.12.0012:23:50 4 11 00:03:583844733399 7 2
12.12.0013:23:54 3 17 00:02:233844733399 8 5 (6)
12.12.0014:05:24 3 18 00:01:23834756 31 2
12.12.0014:38:43 2 12 00:03:242374844 63 2 (7a)
12.12.0014:43:33 3 12 00:00:255345545556 5 2 (7b)
12.12.0014:44:12 2 12 00:12:122374844 12 8 (7c)
12.12.0014:44:12 3 12 00:12:125345545556 10 8 (7d)
12.12.0014:56:24 2 12 00:23:462374844 84 2 (7e)
13.12.0009:43:52 1 5 00:01:0539398989983 76 4 (8)
14.12.0012:23:34 1 600:1400:02:3427348596872347569036 3 (9)
** 100 calls lost ** (10)
15.12.0009:44:34 4 15 00:02:12189???? 23 2
15.12.0009:56:33 3 14 00:05:451283394495 28 2
15.12.0012:20:26 1 12 0230298007766 0 (11a)
15.12.0012:23:34 1 1200:3400:02:340230298007766 1 (11b)
15.12.0013:43:25 3 15 00:05:2408972212345 1 (12a)
15.12.0013:43:25 4 15 00:05:240231471154321 74 9 (12b)
15.12.0013:45:28 4 18 0230298007252 0 (13a)
15.12.0013:45:28 4 32 0230298007252 0 (13a)
15.12.0013:45:28 4 16 0230298007252 0 (13a)
15.12.0013:46:18 4 1600:5000:00:000230298007252 1 (13b)
01.01.0000:00:00 8 16 00:00:000 23 2 (14)
01.06.0113:55:35 3 1201:1300:00:000897221234567 2 (15)
12.06.0709:40:54 1 1004 00:00:106675031 0,06 2 0 2
6675031 (16)
12.06.0709:59:07 1 100200:0800:00:076675031 1 1002
(17)
| ---------------------------------------------------------------------------------------------------------------------------
|
| Explanation of the sample entries shown on Seite 12-19:
|
|
|
| Outgoing connection from stn 16 on trunk 4 using the MSN "902725". End of call at 8:23:23 on 12/11/00. Duration of the call: 5 minutes, 23 seconds: Number called: 02317324856. Accrued call charge pulses: 12. The seizure code "841" was used for call setup.
|
|
|
|
| Outgoing connection with 11-digit account code (ACCT) "12345678901". Route "2" was used for LCR.
|
|
|
|
| Unanswered incoming call without station number (missing origin address, active station number suppression CLIR at calling station).
|
|
|
|
| Outgoing connection with suppression of the last 4 digits.
|
|
|
|
| Incoming connection with ringing and call duration.
|
|
|
|
|
|
|
| (7a) Stn 12 sets up a first external call on trunk 2 ("2374844"),
|
| (7b) Stn 12 sets up a second external call on trunk 3 ("5345545556"),
|
| (7c) Stn 12 is involved in a conference with trunk 2 and
|
| (7e) Trunk 3 drops out of the conference. The call on trunk 2 is treated like a normal outgoing call.
|
|
|
|
| Outgoing connection (other services).
|
|
|
|
| Incoming connection (other services).
|
|
|
|
| Loss message: 100 records were lost.
|
| Problems that may result in call data not being output by the system via the V.24 interface include:
|
|
•
|
Connected device is turned off or suffers a power failure
|
|
•
|
Printer is out of paper
|
|
•
|
Printer has a paper jam
|
|
•
|
CDRC output is interrupted by CDB output
|
|
•
|
Interface cable is defective or incorrect
|
In these or similar cases, the call records accumulated during this time are buffered in the system. It is possible to buffer the first 150 (HiPath 3550/HiPath 3500) or 50 (HiPath 3350,
HiPath 3250, HiPath 3300) records.
|
| Additional records are only counted by the system and then discarded. If the connection can be restored to the connected device, a loss message indicating the number of lost records (that is, 100 calls lost) is issued after the buffered records are output.
|
|
|
|
| Incoming call with transmitted caller station number:
|
| (11a) Caller list: When the call arrives, an information line is immediately output indicating the date, time, trunk, station number, incoming external station number (if available), and information element "0" (used, for example, with a PC: start database search -> message appears on station's monitor).
|
| (11b) Station 12 accepted the call after a ringing duration of 34 seconds. This line is output at the end of the call.
|
|
|
|
| Call forwarding with an external destination:
|
| (12a) Incoming call for station 15 on trunk 3 with transmitted station number, no ringing duration due to call forwarding (see 12b),
|
| (12b) Call forwarded (12a) to trunk 4 for station number 0231471154321, 74 call charge pulses (not for U.S.) have accrued for the forwarded call.
|
|
|
|
| Incoming call to subscriber group (stations 18, 32, and 16):
|
| (13a) The three entered stations are called simultaneously; they are listed in the order in which they were entered in the group (the second station is listed first).
|
| (13b) The call was not accepted by any group member. After the call has ended, a line is output indicating the ringing duration for the last called or entered station.
|
|
|
|
| Output after a power failure or reset: 23 call detail units on trunk 8 were present before the power failure.
|
| When a power failure or reset occurs, the call charges accrued for each trunk are stored in nonvolatile system memory (CDRT).
|
| The system checks for consistency between the output and internally stored data following a power failure or system restart. The system also checks to determine whether call charges are still stored that have not yet been output via the V.24 (RS-232) interface. If this is the case, the system outputs a data line using the format illustrated in the example (15) for each affected trunk: (output does not include station number).
|
|
|
|
| Output CDCR ticket without connect (call attempt), indicated by call duration "00:00:00". If the ring duration is "00:00", the station was busy. Connection setup charges are also recorded.
|
|
|
|
| Outgoing connection with extension: transmitted digits in appendix
|
|
|
|
| Incoming connection with extension: required stations in appendix
|
|
|
|
•
|
Compressed Output Format for Call Details - Output via LAN Interface
|
| ---------------------------------------------------------------------------------------------------------------------------
|
1 1
0 1 2 3 4 5 6 7 8 9 0 1
12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
--------------------------------------------------------------------------------------------------------------
1 Date (8 digits)
| 2 Time (8)
| | 3 Trunk (3)
| | | 4 Internal station number (6 digits)
| | | | 5 Ring duration (5)
| | | | | 6 Call duration (8)
| | | | | | 7 Station number (25)
| | | | | | | 8 Call charge pulses (11)
| | | | | | | | 9 Information element (2)
| | | | | | | | | 10 ACCT (11)
| | | | | | | | | | 11 MSN (11)
| | | | | | | | | | | 12 Seizure code (5)
| | | | | | | | | | | | 13 LCR route (2)
| | | | | | | | | | | | | ...
| | | | | | | | | | | | | ...
V V V V V V V V V V V V V
13.12.00;08:23:23;4;16;;00:05:23;02317324856;12;2;12345678901;902725;841;;
| ---------------------------------------------------------------------------------------------------------------------------
|
|
|
| Call detail records can be output via a LAN interface using two different settings:
|
|
•
|
DOS mode (carriage return (CR), line feed (LF)) = default or UNIX mode (line feed (LF)) at the end of a call data record.
|
|
•
|
Separators (";" = default or "|") between the logical elements of a call data record; the record is no longer position-oriented.
|
|
|
|
Table 12-1
|
Compressed Output Format-Explanation of Output Fields (Seite 1 von 8)
|
|
|
|
|
|
|
|
|
|
| Date at end of call: DD.MM.YY
|
| (DD = day: Value range 01 ... 31, MM = Month: Value range 01 ... 12, YY = Year: Value range 00 ... 99)
|
|
|
|
|
|
|
| Time at end of call segment or an unanswered incoming call: hh:mm:ss
|
| (hh = hours: value range 00 - 23, mm = minutes: value range 00 - 59, ss = seconds: value range 00 - 59)
|
|
|
|
|
|
|
| value range 1 ... 250 (as of HiPath 3000 V4.0)
|
|
|
|
|
|
|
| Station: internal station number, value range 0000000 ... 9999999. Missing digits are replaced by blanks.
|
| In the case of unanswered calls, this is the last station called (as in a hunt group, call forwarding, call forwarding--no answer). With group call, this is the last station entered. In the case of answered calls, it is the station that accepted the call. A programmed SNO prefix (with networking only) is not output.
|
| If the internal numbering was converted to a maximum 7-digit numbering plan, the converted station number is output.
|
| A node number with max. seven digits can be placed in front of the station number. If the total resulting from the node number and the station number is greater than seven, only the last seven digits of the number are output.
|
|
|
|
|
|
|
| Ringing duration of an incoming external call: mm:ss
|
(mm = minutes: value range 00,
ss = seconds: value range 00 - 59)
|
| The system displays all incoming calls as long as the output of ringing duration has been configured in the system. If a counter overflow occurs (duration > 59:59), "59:59" is output. A change in date or time during system operation can result in this situation.
|
| In the case of an incoming call to a busy station, the ring duration is "00:00".
|
|
|
|
|
|
|
| Duration of the call or call segment: hh:mm:ss
|
| (hh = hours: value range 00 - 23, mm = minutes: value range 00 - 59, ss = seconds: value range 00 - 59)
|
| If a connection has not been established for an incoming call, 8 spaces are output here. If a counter overflow occurs (duration > 23:59:59), "23:59:59" is output.
|
|
|
|
|
|
|
| Dialed or received external station number (if available): nnnnnnnnnnnnnnnnnnnnnnnnn
|
| (n = dialed or received character: value range 0, *, #, ?)
|
| Output occurs for incoming and outgoing calls (if available). With outgoing calls, the dialed station number or, if available, the station number transmitted via COLP is displayed. In the case of an active data protection function, the last four digits dialed are replaced by the symbols ???? If no station number information is available, 25 spaces are output.
|
|
|
|
|
|
|
| Call charge pulses for a call segment: zzzzzzzzzzz (blank spaces in U.S.)
|
| (z = digit: value range 0 - 9)
|
| You can select either call charge pulses or call charge amounts.
|
| Setting the call charge factor:
|
|
•
|
With calculation detail: call charge factor = 100% + mandatory surcharge
|
|
•
|
Without calculation detail: call charge factor = amount/unit + mandatory surcharge
|
| The system outputs data whenever call charges accrue for the call segment (even with transferred calls). If no call detail information is available, these 11 characters are filled with spaces.
|
|
|
|
|
|
|
| Information element: additional information
|
|
•
|
1 = Incoming connection (voice/3.1 kHz audio call)
|
|
•
|
2 = Outgoing connection (voice/3.1 kHz audio call)
|
|
•
|
3 = Incoming connection (other services)
|
|
•
|
4 = Outgoing connection (other services)
|
|
•
|
5 = Incoming connection forwarded
|
|
•
|
6 = Outgoing connection forwarded
|
|
•
|
7 = Int/ext/ext conference with incoming connection/transit through external transfer
|
|
•
|
8 = Conference with outgoing connection/transit through external transfer
|
|
•
|
9 = Outgoing connection via call forwarding to an external destination
|
|
•
|
0 = Call information (caller list) is output immediately when an incoming call is received (output can be suppressed). This can be used, for instance, for a database search by a PC. When multiple stations are called, a line is output for each individual station (without ring duration, call duration, call detail information).
|
|
|
|
|
|
|
|
•
|
+20 = Offset as a code for call setup charges (connection setup without call duration)
|
|
•
|
+30 (HiPath 3000/5000 V1.0 and later) = offset as an ID for a follow-up data record in the case of
|
| |
- |
contiguous call segments with the same line/station number (for example, after transferring a call, after clearing a conference).
|
| Can occur in combination with offset +40.
|
|
•
|
+40 = Offset for a data record with transit code (by an extension in the subsystem). Can occur in combination with offset +30.
|
|
•
|
+50 = Offset as a code for DISA calls
|
|
•
|
+70 = combination of offsets +30 and +40
|
|
|
|
|
|
|
| Account code (ACCT) entered by the user for this call: ppppppppppp
|
| p = ACCT digit: value range 0 - 9)
|
| If an ACCT has not been entered, 11 spaces are output. If the ACCT is shorter than 11 digits, the remaining characters are filled with spaces.
|
|
|
|
|
|
|
| (m = MSN digit: value range 0 - 9)
|
| Information is displayed if the user has programmed an MSN key. Non-existent characters are replaced by spaces. If MSN information is not available (as in a point-to-point connection), 11 spaces are output instead of these characters.
|
| In the case of outgoing calls from a MULAP station, the station number of the busy MULAP is output.
|
|
|
|
|
|
|
| Seizure code used, access code: bbbbb
|
| (b = digit of the seizure code: value range 0 - 9)
|
| Non-existent characters are replaced by spaces.
|
|
|
|
|
|
|
| (r = digit of the dialed route: value range 0 - 9)
|
| Non-existent characters are replaced by spaces.
|
|
|
|
|
|
|
| (n = digit: value range 0 - 9)
|
| Non-existent characters are replaced by spaces.
|
|
|
|
|
|
|
| (w = digit: value range 0 - 9)
|
| If no information is available, a space is output.
|
|
|
|
|
|
|
| PRI Carrier Identification Code (CIC): cccc
|
| (c = CIC digit: value range 0 - 9)
|
| Non-existent characters are replaced by spaces.
|
|
|
|
|
|
|
| U.S.-specific fields are filled with blanks in other countries.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Only with non-activated extended dataset (on HiPath 3000/5000 from V7 R3 or later):
|
| End of line control character
|
| (carriage return [CR], line feed [LF])
|
|
|
|
|
|
|
| In the case of an activated extended dataset (on HiPath 3000/5000 from V7 R3 or later):
|
| Dialed or received station number (if available): nnnnnnnnnnnnnnnnnnnnnnnnn
|
| (n = dialed or received character: value range 0 - 9)
|
| The data is output for incoming and outgoing calls as long as the LCR number outgoing or dialed number incoming flag is activated in Manager E.
|
| In the case of outgoing calls, the station number that may in fact have been routed to the exchange following LCR conversion is displayed.
|
| In the case of incoming calls, the internal station number for the required station, i.e. the first station dialed, is displayed. If no station number information is available, 25 spaces are output.
|
|
|
|
|
|
|
| End of line control character
|
| (carriage return [CR], line feed [LF])
|
|
|
|
|
|
•
|
Long Output Format for Call Data
|
|
|
| The header in the long output format is output in the language used across the system.
|
| After 62 lines have printed (including header), a form feed (FF) is carried out and the next page begins with a header.
|
|
|
| ---------------------------------------------------------------------------------------------------------------------------
|
Date Time Trk Stn Call Duration Station number Amount I
11.12.00 08:23:23 4 16 00:05:23 02317324856 20,23 2
11.12.00 09:12:45 3 18 00:01:23 834756 0,69 2
11.12.00 09:25:34 2 11 00:34 1
11.12.00 10:01:46 1 12 00:12:53 83726639046287127384 413,69 2
| ---------------------------------------------------------------------------------------------------------------------------
|
|
Table 12-2
|
Long output format - explanation of output fields
|
|
|
|
|
|
|
|
|
|
| See Table 12-1, field position 1
|
|
|
|
|
|
|
| See Table 12-1, field position 2
|
|
|
|
|
|
|
| See Table 12-1, field position 3
|
|
|
|
|
|
|
| See Table 12-1, field position 4
|
|
|
|
|
|
|
| See Table 12-1, field position 5
|
|
|
|
|
|
|
| See Table 12-1, field position 6
|
|
|
|
|
|
|
| Dialed or received external station number (if available): nnnnnnnnnnnnnnnnnnnn
|
| (n = dialed or received character: value range 0 ... 9, *, #, ?)
|
| See Table 12-1, field position 7
|
|
|
|
|
|
|
| Call charge amount for a call segment: zzzzzzzzzzz (blank spaces in U.S.)
|
| (z = digit: value range 0 - 9)
|
| The system outputs data whenever call charges accrue for the call segment (even with transferred calls). If no call detail information is available, these 11 characters are filled with spaces. A comma (,) separates the amount from the decimal places.
|
|
|
|
|
|
|
| See Table 12-1, field position 9
|
|
|
|
|
|
|
| End of line control character
|
| (carriage return [CR], line feed [LF])
|
|
|
|
|
 |
