6.2.4.2. Message "CDR information block on demand" or "CDR
information block with immediate output" 
Direction
OpenScape 4000 → DPA
Format:
Only the record identifier (Record ID) and, for the first record,
the reference (REF) have a fixed definition. You can put the rest together
in any way from the data elements defined in Section 59.5.2,
"Configurable Elements". Furthermore, you can configure
the length, justification, fill character, and, if needed, decimal separation
character (decimal point or comma) of these elements. Examples of possible
formats are given in the following.
Setup of the first data record in a block (Example)
Table 26. Setup of the First Data Record in a Block (Example), Direction: OpenScape 4000 -> DVA
|
RID
|
REF
|
BLENBYT
|
Output-Time
|
BLENREC
|
|
2
|
2
|
4
|
10
|
3
|
Description:
Table 27. Description of Data Elements for "CDR information block on demand or for immediate output", Direction: OpenScape 4000 → DPA
|
Position (byte)
|
Name
|
Value
|
Description
|
|
1 – 2
|
RID
|
"AA" "AH"
|
Record identifier (see Section 59.5.1,
"Elements with a Fixed Specification") on demand For
immediate output
|
|
3 – 4
|
REF
|
"00" "01" "02"
|
Source of the data to be transmitted for immediate
output CDR1 file CDR2 file
|
|
5 – 8
|
BLENBYT
|
Length of the entire block in bytes right justified,
with leading zeros *)
|
|
|
9 –10
|
OUTYEAR
|
Date of the output: year (right justified, with
leading zeros*))
|
|
|
11 – 12
|
OUTMONN
|
Date of the output: month (right justified,
with leading zeros*))
|
|
|
13 – 14
|
OUTDAYN
|
Date of the output: day (right justified, with
leading zeros*))
|
|
|
15 – 16
|
OUTHOUR
|
Date of the output: hour (right justified, with
leading zeros*))
|
|
|
17 – 18
|
OUTMIN
|
Date of the output: minute (right justified,
with leading zeros*))
|
|
|
19 – 21
|
BLENREC
|
Number of the data records following in the
block; (right justified, with leading zeros *)
|
|
*)
|
The coding information (length, justification,
and fill character) applies to the present example.
|
Setup of the data records following in the block (example):
Format
Table 28. Setup of the following data records in the block (example)
|
RID
|
L
|
SWP
|
STNID
|
CHRGEE
|
PIN
|
TKNOLIST
|
|
2
|
4
|
2
|
1
|
6
|
12
|
6
|
Table 29. Setup of the following data records in the block (example)
|
ROUTCN
|
DESTPTY
|
NETTYPE
|
SERVICE
|
SPEED
|
CHRGUNIT
|
|
2
|
22
|
1
|
1
|
1
|
4
|
Table 30. Setup of the following data records in the block (example)
|
End-of-connection
|
Call duration
|
MSGNO
|
SIGDATA
|
|
13
|
7
|
5
|
1
|
Description
Table 31. Description of the Data Elements for "CDR information block on demand or for immediate output", Direction: OpenScape 4000 → DPA
|
Position (byte)
|
Name
|
Value
|
Description
|
|
1 – 2
|
RID
|
Record identifier (see Section 59.5.1,
"Elements with a Fixed Specification")
|
|
|
"AB"
|
On demand
|
||
|
"AI"
|
For immediate output
|
||
|
3 – 6
|
L
|
"0084"
|
Length of the following data in bytes ***)
|
|
7 – 8
|
SWP
|
" 1"... "11"
|
Partial switching procedure **)
|
|
9
|
STNID
|
"1"... "5"
|
User ID **)
|
|
10 – 15
|
CHRGEE
|
Party charged for the connection left justified,
filled with blanks *)
|
|
|
16 – 27
|
PIN
|
Personal id left justified, filled with blanks
*)
|
|
|
28 – 33
|
TKNOLIST
|
Fictitious circuit number (trunk no. list) right
justified, with leading blanks *)
|
|
|
34 – 35
|
ROUTCN
|
Trunk group code right justified, with leading
blanks *)
|
|
|
36 – 57
|
DESTPTY
|
Newly selected or through connected destination
for a connection. left justified, filled with blanks *)
|
|
|
58
|
NETTYPE
|
"1"... "3"
|
Output of the network description **)
|
|
59
|
SERVICE
|
"1"... "6"
|
Output of the service **)
|
|
60
|
SPEED
|
"1"... "6"
|
Output of the transmission speed **)
|
|
61 – 64
|
CHRGUNIT
|
Call charge units right justified, with leading
zeros *)
|
|
|
65 – 66
|
ENDYEAR
|
End-of-connection: year (right justified, with
leading zeros*))
|
|
|
67 – 68
|
ENDMONTH
|
End-of-connection: month (right justified, with
leading zeros*))
|
|
|
69 – 70
|
ENDDAY
|
End-of-connection: day (right justified, with
leading zeros*))
|
|
|
71 – 72
|
ENDHOUR
|
End-of-connection: hour (right justified, with
leading zeros*))
|
|
|
73 – 74
|
ENDMIN
|
End-of-connection: minute (right justified,
with leading zeros*))
|
|
|
75 – 76
|
ENDSEC
|
End-of-connection: seconds (right justified,
with leading zeros*))
|
|
|
77
|
END10
|
End-of-connection: 1/10 seconds (right justified,
with leading zeros*))
|
|
|
78 – 79
|
CONHOUR
|
Call duration: hours (right justified, with
leading zeros*))
|
|
|
80 – 81
|
CONMIN
|
Call duration: minutes (right justified, with
leading zeros*))
|
|
|
82 – 83
|
CONSEC
|
Call duration: seconds (right justified, with
leading zeros*))
|
|
|
84
|
CON10
|
Call duration: 1/10 seconds (right justified,
with leading zeros*))
|
|
|
85 – 89
|
MSGNO
|
Message's consecutive number right justified,
with leading zeros *)
|
|
|
90
|
SIGDATA
|
"1"... "2"
|
Identification whether the data record is correct,
incorrect, or duplicate **)
|
|
*)
|
The coding information (length, justification,
and fill character) applies to the present example.
|
|
**)
|
The coding given for the values applies to the
present example.
The appropriate code for the possible values of
the element must be set with AMO TEXT.
|
|
***)
|
This length is not one of the configurable data
elements. It is set up as field with constant contents.
|