9. 6079ch1.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 1-1
Important Notices
About this Book
1 Important Notices
1.1 About this Book
This guide defines the format of call detail recording (CDR) records that are generated for
specific call types. It shows the formats and output used in the HiPath 4000 CDR feature. Also
included is summary information about CDR record generation, generation options, forms, and
output.
CDR refers to both voice and data CDR. Voice CDR is also known as station call detail
recording or station message detail recording (SMDR). Data CDR is also known as data call
detail recording or data message detail recording (DMDR).
1.2 Audience
This publication is a guide for Siemens service personnel and third party customer vendors who
maintain and support the CDR feature for Siemens customers.
1.3 How to Use this Book
This guide contains the following chapters:
● Chapter 1, “Important Notices”, provides an overview of this book.
● Chapter 2, “CDR Overview”, defines CDR and provides information about CDR features
including recorded call type and trunk type references.
● Chapter 3, “CDR Output Formats”, contains information about CDR default output formats,
default output fields, and custom output fields.
● Chapter 4, “An Overview of the Configuration Process”, contains configuration
components.
● Chapter 5, “Configuring the HiPath 4000 System to Output CDR Records” describes the
procedures necessary to put Standard CDR into operation.
● Chapter 6, “Setting Up Collecting Agent” to retrieve the existing CDR records for use with
Performance Management (PM).
● Appendix A, “CDR AMOS”, describes the CDR related AMOs and their uses.
● Appendix B, “CDR Restrictions”, lists the restrictions and limitations associated with
various uses of the CDR feature.
This guide also contains a glossary and an index.
10. Important Notices
A31003-H3140-S109-1-7620, October 2007
1-2 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch1.fm
Related Publications
1.4 Related Publications
Related publications are as follows:
● Hicom 300 H, V1.0 Call Detail Recording Reference Guide, G281-0250
● Hicom 300 H, V1.0 Configuration Guide, G281-0702
● Hicom 300 H, V1.0 AMO Reference, G281-0703
● HiPath 4000 V4.0, Section 1 - AMO Descriptions, Service Documentation,
P31003H3140S104017620
● HiPath 4000 V4, Feature Usage Examples, Service Manual, A31003-H3140-S106-1-7620
● HiPath 4000 V4.0, Section 2 - System Components (Hardware, Software), Service
Documentation, Issue 1, P31003H3140S105017620
● HiPath 4000 V4.0, Section 3 - Feature Usage Examples, Service Documentation,
Issue 2 P31003H3140S106017620
1.4.1 Special Notices
Potentially dangerous situations are noted throughout this guide. The three alert methods are
defined below:
The symbol that appears with the alert indicates the type of dangerous situation to which the
alert calls attention. The symbols are defined below:
DANGER A danger notice calls attention to conditions that, if not avoided, will result in
death or serious injury.
WARNING A warning notice calls attention to conditions that, if not avoided, could result
in death or serious injury.
Caution A caution notice calls attention to conditions that, if not avoided, may damage
or destroy hardware or software.
> 1 0 6 7 7 4
Information/
Note
Electrical Fire Chemical General Weight Electrostatic
11. 6079ch1.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 1-3
Important Notices
Documentation Feedback
1.5 Documentation Feedback
In an effort to continuously improve our documentation, Siemens provides a documentation
feedback line. You can use this line to report documentation errors or make suggestions on how
we can improve our documents.
To use the Documentation Feedback Line:
1. Call toll free 1-800-835-7656
2. Provide the following information:
● The document name: HiPath 4000, Call Detail Recording Reference Guide
● The document order number: A31003-H3140-S109-1-7620
● The page number or section number you are referencing
● Your name, address, e-mail address, and telephone number
● A brief description of your suggestion
13. 6079ch2.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 2-1
CDR Overview
What is CDR?
2 CDR Overview
This chapter provides an overview of CDR, its function and its features.
2.1 What is CDR?
The HiPath CDR feature collects information on calls placed to and from the HiPath 4000. This
information is collected in order to:
● Track bill-back accounting (for extension, department, division, or company)
● Track and identify special common carrier services (track telephone numbers and call
duration to specific locations)
● Track client or user identification (track account numbers or personal identification numbers
[PINs])
● Track system traffic for analysis (call patterns, trunk usage, and other least-cost routing
[LCR] information) to enable effective performance management.
● Track and identify call abuse (unauthorized calls).
2.1.1 Recorded Call Types
CDR supports three types of call records:
● Voice
● Fax
● Data
Data and fax calls placed over an analog acoustic-coupling device are considered voice calls.
2.1.2 CDR Trunk Types
CDR uses the following trunk types:
● CO trunks
A central office (CO) trunk refers to any public-switched analog trunk using conventional
signaling. This type of trunk also includes digital trunks that emulate analog trunks and
their associated conventional signaling.
● ISDN trunk
An integrated services digital network (ISDN) trunk refers to any public-switched primary
rate ISDN trunk. It does not include private network CorNet trunks that are ISDN-based.
14. CDR Overview
A31003-H3140-S109-1-7620, October 2007
2-2 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch2.fm
CDR Features
● CorNet trunk
A CorNet trunk refers only to private network trunks using the CorNet-N, CorNet-NQ, and
CorNet-VN signaling protocol.
● Tie trunk
A tie trunk refers to private network trunks using non-CorNet-N, trunk-to-trunk signaling.
2.1.3 Calls Recorded by CDR
The CDR feature collects information on the following types of calls:
● Outgoing voice and data trunk calls
– CorNet trunk calls
– Analog and digital trunk calls to a CO
– Primary rate interface (PRI) calls
– Tie trunk calls
● Incoming voice and data trunk calls
– CorNet trunk calls
– Tie trunk calls
– PRI calls
– Analog and digital trunk calls from the CO (for example and dedicated incoming trunk
[DIT])
● Intra-switch station-to-station data calls
● Intra-switch voice calls
2.2 CDR Features
This section describes the CDR features for HiPath 4000 V1.0, V2.0 and later.
2.2.1 CDR Record Generation
CDR records can be generated for the following types of calls:
● Internal voice
● External voice calls
● Internal data
15. 6079ch2.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 2-3
CDR Overview
CDR Features
● External data calls
A CDR record is opened when a call reaches a connected state. The record is usually closed
when the call disconnects or is transferred. Multiple call detail records can be generated under
more complex call scenarios involving transfers, conferences, networking, and other HiPath
4000 features.
2.2.2 CDR Generation Options
Refer to the HiPath 4000, AMO Descriptions, P31003-H3130-A104-01-7620, for information
about configuring CDR output types using the AMO FEACG.
2.2.3 CDR Forms
CDR output formats are flexible and configurable. Options include field selection and position,
page headers and footers, multi-line CDR record blocks, and configurable text strings. The
output record width of a CDR form is limited to 255 field elements.
● Most HiPath 4000 systems ship with five or more predefined forms. A maximum of 16 forms
can be defined. Form number 2 is used in the US only and contains most of the elements
required by US customers. This eases work by CDR post-processing devices, if used. The
CDR examples in this document use form number 2. Refer to the HiPath 4000 AMO
Descriptions, P31003-H3130-A104-01-7620, for information about configuring and
selecting forms using the AMO FTBL.
Table 3-2 on page 3-14 lists the fields and their characteristics for default form number 2.
● When a custom-designed form is used, the text string output for the following fields can
also be changed: SERVICE, TRANSFER, PARTYID. More fields are possible, refer to the
AMO TEXT in the HiPath 4000 AMO Descriptions, P31003-H3130-A104-01-7620, for
more information about custom text strings.
2.2.4 CDR Output
When a record is closed, the result is output for collection and processing. Voice and data CDR
records can be output to a common device (for example, voice and data records can be output
to a printer) or to separate devices (for example, voice records can be output to a printer and
the data records can be output to a hard disk). Voice and data records can also use different
output forms. When voice and data CDR records are output to a common device, the records
are combined. CDR records can be output using one of the following methods:
● Continuous output
● Periodically scheduled output
● Predefined time output
16. CDR Overview
A31003-H3140-S109-1-7620, October 2007
2-4 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch2.fm
CDR Record Processing
● Output when reaching a record threshold
● Output when requested
Refer to the AMOs FEACG, GEZU, GEZAB, SELG, DAGR, and SELS in the HiPath 4000 V4.0,
Section 1 - AMO Descriptions, Service Documentation, P31003H3140S104017620, for
information about configuring CDR output devices.
If an error occurs on a CDR output device, the CDR records can be buffered to the HiPath 4000
ADP or HiPath 4000 hard disk to prevent CDR record loss. The usage of the HiPath 4000 ADP
buffer is controlled by the configuration of the parameter RESOP in the AMO SELG. When the
HiPath 4000 ADP buffer is full or configured to not be used, two files that are available on the
hard disk (CDRC1 and CDRC2) that are configurable to buffer the data. The sum of the records
in these two files cannot exceed a total of 65,535 records. When buffered, the records are
stored in an internal system data format known as HDFORM.
Another file is available on the hard disk (FT) that stores CDR records in ASCII format, allowing
for quick retrieval of files.
CDR records are output in the order they are closed, not in the order they are opened.
2.3 CDR Record Processing
Call records for active calls are kept in a buffer area in the switching unit (SWU). When a call is
completed, the call record is placed in a SWU storage area that holds up to 3800 records
(ECX), 2200 for all other systems.
If this buffer is filled to 75%, no Internal records will be buffered.
The buffer area for the records of active calls and the storage area for the records of completed
calls are duplicated in the standby processor. The call records in the storage area are sent to
the administration and data processor (ADP) one at a time.
The ADP processes the call records by sending the records to one of two devices (or disk
areas): a tape device or a serial interface. When the call records have been processed by the
appropriate device, the call records are deleted from the switching unit, if configured to do so.
The administration and maintenance order (AMO) SELG defines up to four selection groups,
each containing eight selection tables. These selection groups determine which device collects
the CDR data records. The selection groups determine whether a reserve collection point is to
be established. The selection tables also contain individual customer selection criteria of
certain data records. The selection criteria is configured on a form. The default form (2) is
established. If the customer desires different criteria than what is specified by the form, the
technician has to amend the form to accommodate the customer.
When a call record is received by the ADP, CDR compares the records to criteria defined for
the first selection group. When a table is found that matches the call record, the record is sent
to the appropriate device and the remaining selection tables of the group are ignored. Search
17. 6079ch2.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 2-5
CDR Overview
CDR Record Processing
is continued, however, on any other active selection groups. The same record can be sent to
multiple devices. If none of the tables of the selection groups requires the output of the current
record, the record is deleted.
If reserve operation is specified, and the primary or base device is inoperative or is not
connected, the CDR records can be configured to overflow to the hard drive. If reserve
operation is not specified, the call detail records in the temporary buffer are immediately output.
Call detail records that overflowed to the hard disk must be retrieved using an AMO command.
CDR records stored on the hard disk will utilize a special hard disk format.
Selection Group 1 Selection Group 2
Selection Group 3 Selection Group 4
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
1-16 forms in
Table 1
Table 2
each table
19. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-1 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
3 CDR Output Formats
This chapter contains information about CDR default output formats, default output fields, and
custom output fields. These are the fields that when selected show up in the customer’s report.
3.1 Available Output Fields
Table 3-1 lists all available fields used to configure custom CDR output. The following describes
each field:
● AMO FTBL Field Name—Lists the field name of the AMO.
● Field Description—Contains a summary of the function of each field.
● Maximum Length—Lists the maximum number of available character positions for the
field.
● Default Field—Shows the logical position of the field as it appears in the default form 2
CDR output.
Subscripts indicate multiple AMO FTBL fields that are used together in the default form 2, such
as the duration of call fields E1, E2, and E3. If the field is not contained in the default output, a
dash appears.
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
ACCTCODE P Account code associated with a call. The account code is
entered by the user either before or during the call. In AMO
FEASU, the system feature “CDRACC” must be activated for
this to work.
12 6
ACDAGTID —— ACD Agent ID. The ID of the ACD agent involved in an incoming
or outgoing, answered call.
6 ——
ADPLOAD —— Processor load of the ADP in parts per thousand. It is an
average load over 10 seconds. The time stamp, when the load
was taken, is available in the end_of_connection field: ENDDAY
(2 digits), ENDMONTH (2 digits), ENDHOUR (2 digits),
ENDMIN (2 digits), ENDSEC (2 digits), END10 (1 digits).
END10 is tenth of a second.
4 ——
AOCTYPE —— Advice of charge (Administered through AMO-TEXT). Not used
in the US.
10 ——
ATNDGRNO —— Attendant group, range 0 – 15. Identity of the attendant console
group.
2 ——
ATTCALLP —— Attendant call priority – This field contains a number
representing the priority of a call to the attendant.
——
Table 3-1 AMO-FTBL Parameters (Sheet 1 of 13)
20. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-2 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
ATTCALLR —— Attendant intercept reason – when a call is intercepted to the
attendant console, the field will contain a number representing
the intercept reason.
2 ——
ATTCALLT —— Attendant call type – contains a number representing the type
of a call to the attendant.
attendant call type
0: EMERGENCY_CALL
1: HOTLINE_CALL
2: LOCAL_FIRST_CALL
3: LOCAL_RECALL
4: LOCAL_PRIO_CALL
5: CO_RECALL
6: CO_SERIAL_CALL
7: CO_IN_CONSULTATION
8: CO_ON_HOOK_IN_CONS
9: TIE_RECALL
10: TIE_SERIAL_CALL
11: TIE_IN_CONSULTATION
12: TIE_ON_HOOK_IN_CONS
13: OVFL_LOC_FIRST_CALL
14: OVFL_LOC_PRIO_CALL
15: OVFL_CO_FIRST_CALL
16: OVFL_TIE_FIRST_CALL
17: PERSONAL_CALL
18: ATND_LOOP_TRANSFER
19: CO_FIRST_CALL
20: MLPP_FLASH_OV
21: MLPP_FLASH
22: MLPP_IMMED
23: MLPP_PRTY
2 ——
ATTQUEID —— Attendant Queue ID – for calls to an AC Win MQ this field will
hold the Queue ID assigned to the call.
2 ——
BAUD
(SPEED)
—— Output of the transmission speed as a text string (administered
through AMOTEXT), if the speed is not defined in the text-table
of AMO-TEXT, the speed will be output as number with 3 digits.
10 ——
BCHLCNT —— The number of B-channels 2 ——
BLENBYT —— The length of blocks in bytes 5 ——
BLENREC —— The number of records per block 5 ——
CALCTYPE —— Type of billing applied (administered through AMO-TEXT). Not
used in the US.
10 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 2 of 13)
21. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-3 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
CALLEPTY —— Called party – number which was dialed by the calling party.
Common for all parties:
If the party is an attendant console, AMO-TLZO can be used to
create a virtual subscriber number; an entry in AMO-TLZO must
be created for a main PBX tie trunk set (HAS).
If the length of the output field is shorter than the length of the
party number to output, the party number is cut off. For this
reason the parameter FLDALIGN (more details see AMO-
FTBL) will be used.
Example right justified:
Party: 96252125 Data record: 2125
Example left justified:
Party: 96252125 Data record: 9625
If the length of the party to output is shorter than the field size in
the data record, the field will be filled with the specified filler (left
or right).
Example right justified with longer field:
A-Paypart: 2125 Data record: ____2125
Example left justified with longer field:
A-Paypart: 2125 Data record: 2125____
22 ——
CALLIID —— Represents the ID of calling party. The ID output is the same as
the AMO TEXT field STNID.
10 ——
CALLILV0 —— The node number of calling party 3 ——
CALLILV1 —— The subdomain number of calling party 3 ——
CALLILV2 —— The domain number of calling party 2 ——
CALLIONI —— The originating Network ID of the calling party 2 ——
CALLIPTY J The calling party number: The party that initiated the current
connection/section. Contains information about the right/left
justified output field.
22 15
Carrier —— Output of the Identifier of the communication network, such as
AT & T, or MCI, as a text string (administered through AMO-
TEXT)
10 ——
Cause —— A code used to indicate the reason for clearing a call
(connection interrupt), consult AMO-FTBL for a complete listing.
Not used when CONNTYPE = INTERNAL
3 ——
CHOFCON —— Type of connection – output as a text string, (administered
through AMO-TEXT)
1 = Local
2 = Long distance
3 = Local with limit value exceeded
4 = Long distance with limit value exceeded
5 = No entry
6 = Route optimization
10 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 3 of 13)
22. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-4 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
CHRGEE
(PAYPART)
—— The party charged or the Paying party; chargee of a connection.
For information about the right/left justified output field, see
description of CALLEPTY.
22 ——
CHRGUNIT —— The units of charge for a call. Not used in the US. 5 ——
CONCHRG —— The output of the costs (including value-added tax)—Not used
in the US.
8 ——
CONCHRN —— The output of the net costs (without value-added tax)—Not
used in the US.
8 ——
CONHOUR E1 The duration of the connection in hours 2 2
CONMIN E2 The duration of the connection in minutes 2 2
CONSEC E3 The duration of the connection in seconds 2 2
CON10 —— The duration of the connection in tenths of a second 1 ——
CONSECT
(CONTSEC)
—— The total duration of the connection in tenths of a second. 6 ——
CONNSTEP —— All CDR records with same CONNTYPE and same Call_Id will
be numbered sequentially (starts with content 1).
3 ——
CONNTYPE —— Output of the connection type as a text string (administered
through AMOTEXT)
Connection type:
INTERN = internal connection
INCO = incoming connection
OUTGO = outgoing connection
ACACT = activity of attendant
LOAD = load of processors
10 ——
COPIN F The output of the class of pin as a text string (administered
through AMO-TEXT)
0 = No valid class of PIN
1 = Manual PIN for mobile user
2 = Business PIN for long service
3 = Business PIN used for the call
4 = Private PIN used for the call
5 = Project code used for the call
6 = ID card for mobile user
7 = Switchover code
8 = PIN for service ID
9 = CDR account code
10 = PIN for dialing pattern check
10 1
CTRDIFF —— call charge sum for station difference, only GET-functionality
(charge data recording per station)
5 ——
CTRTOT —— call charge sum for station total, only GET-functionality (charge
data recording per station)
5 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 4 of 13)
23. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-5 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
DESTLV0 —— This is the node number of new destination connected party 3 ——
DESTLV1 —— This is the subdomain number of the new destination connected
party
3 ——
DESTLV2 —— This is the domain number of the new destination connected
party
2 ——
DESTPID G Identification of the destination party. For dialed numbers it is
not always possible to determine the ID of the destination party.
In these cases “unknown” is output. For connected parties (and
new destination parties that might occur) the ID is the same as
that STNID in AMO TEXT listed here:
1 = VF =Operator console
2 = HAS= PBX set
3 = NST= Night server
4 = TLN = Subscriber
5 = SM= Service module (for field paying party ID only)
6 = SPC= Special charging (for field paying party ID only)
7 = MEQ= Maintenance equipment (for field paying party ID
only)
8 = PUP= Public phone via SLMAR to HiPath (for field paying
party ID only)
9 = MOB = Mobile user
10 = KEY = Number of the other line (keyset)
10 1
DESTPTY K The new destination connected party; new selected destination
for a connection. For information about the right or left justified
output field, see description of CALLEPTY.
22 15
DISPCHRG —— The output of the connection charge that is seen on display
(including value-added tax)—Not used in the US.
8 ——
DISPCHRN —— Represents the output of the net connection charge as seen on
a display (without value-added tax)—Not used in the US.
8 ——
DNIS —— Represents the output of the dialed number identification
service number. The DNIS number is provided by the PSTN and
is related to the called party.
11 ——
ENDDAY —— Represents the day that the connection ended. 2 ——
ENDHOUR —— Represents the hour that the connection ended. 2 ——
ENDMIN —— Represents the minute that the connection ended. 2 ——
ENDSEC —— Represents the second that the connection ended. 2 ——
ENDMONTH —— Represents the month in which the connection ended. 2 ——
ENDYEAR —— Represents the year in which the connection ended. 4 ——
ENDYDAY —— Represents the day of the year that the connection ended. 3 ——
END10 —— Represents the value to the nearest 1/10 of a second of the
connection ending.
1 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 5 of 13)
24. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-6 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
EXPENS H The output of the degree of expense of the connections as a text
string (administered through AMO-TEXT)
Values:
0 = BILLIG = Inexpensive connections
1 = TEUER= Expensive connections
2 = GRATIS_A = Free of charge A-party
3 = GRATIS_B = Free of charge B-party
10 1
FACA —— The facility parameter for a FX or TTA trunk access at the
BREAKIN (PSTN) trunk (this parameter is provided as part of
NI2 PRI support).
5 ——
FACB —— The facility parameter for a FX or TTA trunk access at the
BREAKOUT trunk (this parameter is provided as part of NI2 PRI
support).
5 ——
FLAG1 —— The generation of flag byte one, only if using a data processing
system behind PBX.
2 ——
FLAG2 —— The generation of flag byte two, only if using a data processing
system behind PBX.
2 ——
GLOBLLV0 —— The node number of global leg ID, identical with LEGLV0 3 ——
GLOBLLV1 —— The subdomain number of global leg ID, identical with LEGLV1 3 ——
GLOBLLV2 —— The domain number of global call leg ID, identical with LEGLV2 2 ——
GLOBLSEQ —— The sequence number of global leg ID, identical with LEGSEQ 8 ——
GLOBLV0 —— The node number of global call ID. 3 ——
GLOBLV1 —— The subdomain number of global call ID. 3 ——
GLOBLV2 —— The domain number of global call ID. 2 ——
GLOBSEQ —— The global call ID; A new global call ID may be produced only,
in case of a new connection.
8 ——
HOLDDUR —— The total hold duration (how long the call was on hold) in format
1/10 seconds.
5 ——
IDPP —— The output of the station ID as a text string (administered
through AMO-TEXT), only GET-functionality (charge data
recording per station)
10 ——
INFOTYPE —— The type of information; if charging information from carrier,
then units or amounts. Not used in the US.
10 ——
INTNLIST —— The imaginary trunk number converted from INTNREAL
(administered through AMO-FBTN)
6 ——
INTNBCHA —— The B-channel of real trunk number of non-recording point. 2 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 6 of 13)
25. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-7 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
INTNREAL O The real trunk number of non-recording point (see also
TKNOREAL).
This field represents the “real” trunk number of the non-
recording point. But again, forget the word “trunk”, as this field
actually means “line” number. This field is taken from the
internal “line” number of a channel. For analog trunks, each
analog trunk channel has its own unique “line” number. For
digital trunks, each of the channels on a digital trunk span share
a common “line” number, so you cannot tell which “B-channel”
is being used. If a station-to-station (internal) call produces a
CDR record, INTNREAL will display the “line” number of the
called station.
Example #1: If station 2001 dials 9-972-355-4321, then the
CDR record will show “2001” in Field 15 (CALLIPTY), “9” in field
18 (ROUTCN), “9723554321” in field 16 (DESTPTY), the trunk
line number in field 19 (TKNOREAL), and the station (2001) line
number in field 20 (INTNREAL). So for station calls, the data in
this field is not needed, as we already know the station number.
We really do not need the “line” number in this example.
Example #2: If a trunk call enters the HiPath 4000, then exits
the HiPath 4000 on another trunk (tandem call), the CDR fields
TKNOREAL and INTNREAL show the “line” numbers for both
trunks that were used. This example is the only practical use for
the field INTNREAL.
5 4
INTNTRGR —— The trunk group of trunk at non-recording point. When the non-
recording point is a line (station) instead of a trunk, zero (000) is
output here.
3 ——
KEYLV0 —— The node number of the party of the key line used. 3 ——
KEYLV1 —— The subdomain number of the party of the key line used. 3 ——
KEYLV2 —— The domain number of the party of the key line used. 2 ——
KEYPTY —— The party of the key line used; the selected line (number) on a
key phone providing multiple lines. For information about the
right or left justified output field, see CALLEPTY description of
item
22 ——
LCALLENO
(LCALLENR)
—— The length of the called party number (CALLEPTY). 2 ——
LDESTNO
(LDESTNR)
—— The length of the destination number (DESTPTY). 2 ——
LEGLV0 —— The node number of leg ID. 3 ——
LEGLV1 —— The subdomain number of leg ID. 3 ——
LEGLV2 —— The domain number of leg ID. 2 ——
LEGSEQ —— The sequence number of leg ID. 8 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 7 of 13)
26. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-8 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
LISTTYPE —— The output of the type of station, CDR list type as a text string
(administered through AMO-TEXT), only GET-functionality
(charge data recording per station)
Values:
IND = Individual call charge calculation
SUM = Sum call charge calculation (partial calculation.)
TOTAL = Total call charge calculation
16 ——
MOBUCLV0 —— The node number of mobile user calling party. 3 ——
MOBUCLV1 —— The subdomain number of mobile user calling party. 3 ——
MOBUCLV2 —— The domain number of mobile user calling party. 2 ——
MOBUCPTY —— The mobile user calling party; user identifies at calling station
with PIN. For information about the right or left justified output
field, see CALLEPTY description.
22 ——
MSGNO
(MSGNR)
—— The consecutive number of message by Store & Forward
connection. Not used in the US.
5 ——
NCT —— A flag, indicating that a network call transfer (NCT) was
successfully performed.
In a network call transfer, the transfer is performed in the public
network and all connections via the HiPath 4000 are released.
CDR of HiPath 4000 is not able to monitor charging of the
remaining call any more (1 char)
1 ——
NETCARA —— The access code of the network carrier providing the BREAKIN
(PSTN) trunk.
4 ——
NETCARB —— The access code of the network carrier providing the
BREAKOUT (PSTN) trunk.
4 ——
NETPULS —— Pulses representing charge information from the network. Not
used in the US.
5 ——
NETSVCA —— Network service type representing the type of service for the
long distance carrier that delivered the PRI-rate call (for
incoming calls).
2 ——
NETSVCB —— Network service type representing the type of service for the
long distance carrier that was used or requested when making
an outgoing PRI-rate call.
2 ——
NETTYPE —— The output of the network description as a text string
(administered through AMO-TEXT)
Values are:
ANA = Analog network
IDN = Integrated Data Network
ISDN = Integrated Services Digital Network
10 ——
OSAA —— Operator system access for incoming trunk connections. OSAA
is currently not in use because OSA encoding cannot be
received from CO or private network.
1 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 8 of 13)
27. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-9 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
OSAB —— operator system access for outgoing trunk connections. 1 ——
OUTDAYC —— current output date, name of the day (administered through
AMO-TEXT)
Values are:
1 = Monday
2 = Tuesday
3 = Wednesday
4 = Thursday
5 = Friday
6 = Saturday
7 = Sunday
10 ——
OUTDAYN —— Represents the current output date that data is sent to the
collection device defined in AMO-SELG, date of the month.
2 ——
OUTHOUR —— Represents the current output date, hour. 2 ——
OUTMIN —— Represents the current output minute. 2 ——
OUTMONN —— Represents the current output month. 2 ——
OUTMONC —— Represents the current output month, name of the month
(administered through AMO-TEXT)
Values are:
1 = January
2 = February
3 = March
4 = April
5 = May
6 = June
7 = July
8 = August
9 = September
10 = October
11 = November
12 = December
10 ——
OUTSEC —— Represents the current output second. 2 ——
OUTDAY —— Represents the current output day of the year. 3 ——
OUTYEAR —— Represents the current output year. 4 ——
PIN (VIDCARD) Q Represents the caller’s personal ID. 12 9
PINLEN
(LIDCARD)
—— Represents the length of the caller’s personal ID. 2 ——
PPLV0 —— Represents the node number of paying party (CHRGEE). 3 ——
PPLV1 —— Represents the subdomain number of paying party (CHRGEE). 3 ——
PPLV2 —— Represents the domain number of paying party (CHRGEE). 2 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 9 of 13)
28. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-10 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
QUEUEDUR —— Represents the total queuing duration (call queue of attendant)
in 1/10 seconds.
5 ——
RECNO
(RECNR)
—— The consecutive number of the record to be output for each
selection group.
4 ——
RECPT —— Record point
0 = Transit between systems
1 = Breakout to central office
2 = Recording direct at origin
3 = Recording direct at origin and breakout to central office
4 = Incoming
1 ——
RECTYPE —— An indicator specifying which application areas (CDR-e or
Performance Management [PM]) the record is relevant. A
record may be either relevant for charging purposes, or may be
relevant for performance measurements.
A record may be relevant for both areas at the same time, too.
Values are:
1 = empty
2 = CDR-e only
3 = PM only
4 = CDR-e and PM
1 ——
RING10 —— Ring duration (at the destination party in 1/10 second
increments within format—minute:second:1/10 second.
1 ——
RINGDUR —— Total ring duration in format 1/10 seconds. 5 ——
RINGMIN —— Ring duration: minute part within format minute:second:1/
10second.
2 ——
RINGSEC —— Ring duration, second part within format minute:second:1/
10second.
2 ——
ROUTCC —— output of the route code as a text string (administered through
AMO-TEXT)
Values are:
ATND = Attendant console
MTLC = PBX tie-line circuit
STN = Station
TC = CDR per trunk
10 ——
ROUTCN M Route code 6 5
RTINGLV0 —— Represents the node number of redirecting party. 3 ——
RTINGLV1 —— Represents the subdomain number of redirecting party. 3 ——
RTINGLV2 —— Represents the domain number of redirecting party. 2 ——
RTINGPTY —— Represents the redirecting party’s number; A redirecting party
is the one that redirects a call. For information about the right or
left justified output field, see CALLEPTY description.
22 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 10 of 13)
29. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-11 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
RTIONLV0 —— Represents the node number of the party receiving the
redirection.
3 ——
RTIONLV1 —— Represents the subdomain number of the party receiving the
redirection.
3 ——
RTIONLV2 —— Represents the domain number of the party receiving the
redirection.
2 ——
RTIONPTY L The redirection party’s number; The redirection party is the
number to which a call is redirected. For information about the
right or left justified output field, see CALLEPTY description.
22 15
RURAL —— A flag that indicates a call with pulse metering and sending
(rural). Not used in US
Values are:
flag if rural call (1 digit)
value 0 = rural
value 1 = other terminal device
1 ——
SELGRUNO
(SELGRUNU)
—— The output represents one of four (4) selection group numbers. 1 ——
SERVICE A The output represents the type of service as a text string: voice,
data, or fax (administered through AMO-TEXT)
Values are:
DTE = Data terminal equipment
FAX = Facsimile
VOICE = Voice connection
10 1
SIDANI —— A text string related to the calling station or calling number. The
SIDANI number is provided at the BREAKIN (PSTN) incoming
trunk and is related to the calling party.
24 ——
SIGDATA —— This field indicates whether the output data record is correct,
incorrect or double (administered through AMO-TEXT)
Values are:
0 = incorrect or double data set
1 = correct data set
10 ——
STDAY C2 This field indicates the day when the connection started. 2 2
STHOUR D1 This field indicates the hour when the connection started. 2 2
STMIN D2 This field indicates the minute when the connection started. 2 2
STMONTH C1 This field indicates the month when the connection started. 2 2
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 11 of 13)
30. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-12 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
STNID (SUBSID) B The output of the type of station ID (of CHRGEE) as a text string
(administered through AMO-TEXT)
Values are:
1 = Operator console
2 = PBX set
3 = Night server
4 = Subscriber
5 = Service module (for field paying party ID only)
6 = Special charging (for field paying party ID only)
7 = Maintenance equipment (for field paying party ID only)
8 = Public phone via SLMAR to HiPath (for field paying party ID
only)
9 = Mobile user
10 = Number of the other line (keyset)
10 1
STYDAY —— This field indicates the day of the year when the connection
started.
3 ——
STYEAR C3 This field indicates the year when the connection started. 4 4
STSEC —— This field indicates the second when the connection started. 2 ——
ST10 —— This field indicates the 1/10 second when the connection
started.
1 ——
SUPLSERV I This output indicates the type of supplementary service that
was utilized. It is represented as a text string, (administered
through AMO-TEXT)
10 2
SWP —— This field indicates the subprocesses of Call processing
(administered through AMO-TEXT)
Values are:
ENDL = End of call after limit value
ENDS = End of call after seizure
ENDSEC = End of call after section
LAL = Limit value after limit value
LAS = Limit value after seizure
LASEC = Limit value after section
NEXTSEC = Section after section
SECACC = Section after account code
SECL = Section after limit value
SECS = Section after seizure
SPACE = No call processing process
10 ——
SWULOAD —— Represents the processor load of the SWU in parts per
thousand. It is an average load over 10 seconds. The time
stamp, when the load was taken, is available in fields
“start_of_connection” -> STDAY (2 digits), STMONTH (2 digits),
STHOUR (2 digits), STMIN (2 digits), STSEC (2 digits),
ST10 (1 digit)
4 ——
THRELV0 —— The node number of global thread ID, identical with GLOBLV0 3 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 12 of 13)
31. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-13 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Available Output Fields
THRELV1 —— The subdomain number of global thread ID, identical with
GLOBLV1
3 ——
THRELV2 —— The domain number of global thread ID, identical with
GLOBLV2
2 ——
THRESEQ —— The sequence number of global thread ID; a new global thread
ID may be produced only in case of a new connection, identical
with GLOBSEQ
8 ——
TKNOBCHA —— The B-channel of real trunk number of recording point. 2 ——
TKNOLIST
(TNLIST)
—— The imaginary trunk number converted from TKNOREAL
(administered through AMO-FBTN)
6 ——
TKNOREAL
(TNREAL)
N The real trunk number of recording point. 5 4
TKNOTRGR —— The trunk group of trunk at recording point. When the recording
point is a line (to a station) instead of a trunk, zero (000) is
output here.
3 ——
TRNSFLV0 —— The node number of transferring party. 3 ——
TRNSFLV1 —— The subdomain number of transferring party. 3 ——
TRNSFLV2 —— The domain number of transferring party. 2 ——
TRNSFPTY —— The transferring party’s number; it is the number of the party
that transferred the call. For information about the right or left
justified output field, see CALLEPTY description.
22 ——
TRANSCNT —— The number of transit nodes through which the call passed. 2 ——
UNANS —— Through-connect / no through-connect (administered through
AMO-TEXT)
Values are:
NTHRCONN = No through-connect
THRCONN = Through-connect
10 ——
UNITERAS —— Flag, if counter – of the charge data recording per station – is
deleted after output (22 digits, administered through AMO-
TEXT), only GET-functionality (charge data recording
per station)
22 ——
ZONE —— Output of the distance zone as a text string (administered
through AMO-TEXT)
10 ——
AMO FTBL
Field Name
Default
Field
Field Description Max
Length
Actual
Length
Table 3-1 AMO-FTBL Parameters (Sheet 13 of 13)
32. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-14 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Default Output Fields for Form 2
3.2 Default Output Fields for Form 2
There are 16 forms using the parameters found in Table 3-1 that can be configured for the
customer use. When a new HiPath 4000 V2.0, or later, switch or new software is shipped from
the factory, certain fields in Table 3-1 are preconfigured and set as the default form. Then only
standard form for use in the US is form 2. The fields used in this form are the subject of the
discussion that follows.
The default format for form number 2 contains 22 fields. Table 3-2 lists those fields along with
their descriptions. The following provides an explanation for each of the fields in Table 3-2:
● Field—Corresponds to a logical position in the output and is designated alphabetically.
● Field Length—Shows the number of characters in the field.
● L/R—Indicates whether the data contained in the field is left or right aligned in the default
form. Multiple entries in this column are used to indicate the alignment of multiple field
components, if applicable.
● Field Description—Provides a brief explanation of the field.
● Values—Provides the values of the field.
The CDR default output forms are configurable by using the AMO FTBL. Figure 3-1 on page
3-16 shows a sample of a CDR call using this format with headers added to indicate the various
fields.
3.2.1 Form 2 Descriptions
Table 3-2 lists the CDR output fields of Default Form 2 and Figure 3-1 on page 3-16 shows the
form layout.
Field Actual
Field
Length*
L/R Field Description Values
A 1 L SERVICE—Output of the service as a text string, (up
to 10 digits, set to 1 digit).
0 = Speech
1 = Data
2 = Fax
B 1 L STNID—Output of the station ID as a text string, (up
to 10 digits, set to 1 digit).
1 = VF =Operator
console
2 = HAS= PBX set
3 = NST= Night server
4 = TLN = Subscriber
C1 2 R STMONTH—The month in which the connection
started.
mm
C2 2 STDAY—The day in which the connection started. dd
Table 3-2 Default CDR Output Field of Form 1 (Sheet 1 of 2)
33. CDR Output Formats
A31003-H3140-S109-1-7620, October 2007
3-15 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch3.fm
Default Output Fields for Form 2
C3 2 STYEAR—The year in which the connection started. yyyy
D1 2 R STHOUR—The hour in which the connection started. hh
D2 2 STMIN—The minute in which the connection started. mm
E1 2 R CONHOUR —Connection duration in hours. hh
E2 2 CONMIN—Connection duration in minutes. mm
E3 2 CONSEC—Connection duration in seconds. ss
F 1 L COPIN—The class of pin used. See COPIN in Table 3-1
on page 3-1 for values.
G 1 L DESTPID—The type of identity of new/connected
party.
See DESTPID in Table 3-
1 on page 3-1 for values.
H 1 L EXPENS—Identifies the expense of the call. See EXPENS in Table 3-
1 on page 3-1 for values.
I 1 L SUPLSERV—Indicates which supplementary service
was used in the call.
See Table 3-4 on page
3-19 for values.
J 15 L CALLIPTY—Calling party; identifies the party that
initiated the current connection
The number of the calling
party.
K 15 L DESTPTY—The identity of the new or connected
party; new selected destination for a connection
The number of the
destination party.
L 15 L RTIONPTY—redirection party; party where a call is
redirected to, the target.
The number of the
redirection party.
M 5 L ROUTCN—Route code or access code. The number of the route
code.
N 4 L TKNOREAL—Real trunk number of recording point xxxx
O 4 L INTNREAL—real trunk number of the non-recording
point
xxxx
P 6 L ACCTCODE—is a code that is typically used in a
project and is inputted by the caller before or during
the call.
xxxxxx
Q 12 L PIN—is a personal identification code that is entered
prior to the call to identify the caller to the system for
the purpose of authorization.
xxxxxxxxxxxx
* The length of the field transmitted in the CDR output.
Field Actual
Field
Length*
L/R Field Description Values
Table 3-2 Default CDR Output Field of Form 1 (Sheet 2 of 2)
34. CDR
Output
Formats
A31003-H3140-S109-1-7620,
October
2007
3-16
HiPath
4000
V4,
Call
Detail
Recording
Reference
Guide
6079ch3.fm
Default
Output
Format
3.3 Default Output Format
The CDR default output format used in this document is form number 2, however it can easily be modified. This is the
most commonly used output format and is configurable by using the AMO FTBL. Figure 3-1 shows a sample of a CDR
call using this format with headers added to indicate the various fields.
The actual fields are represent in the top line. Each field has a length that is specified in Table 3-2 on page 3-14. If the
field length is greater than one digit, the remaining positions are occupied by a filler. The fields begin with a # sign and
the @ signs are used as fillers.
Below the field designators are two rows of numbers indicating the field positions which correlate to the Fields in Table
3-2 on page 3-14
In the example of Figure 3-1, using Table 3-2 on page 3-14 to correlate the data, the results can be interpreted as shown
in Table 3-3. The fourth row in Figure 3-1 indicate the values of each of the fields. The fifth or last row in Figure 3-1 are
the field labels: A, B, C, etc.
Column Value Interpretation
A S This column represents the type of SERVICE. The value of S, meaning speech, indicates that
this was a voice call.
B T In column B, the value T for STNID indicates that the calling party is a subscriber. The values
are obtained from SUBSID in AMO-TEXT. The full German abbreviation is TLN. However,
only one digit is used to represent STNID.
C 11/11/04 Column C, is made up of three fields: month (STMONTH), day (STDAY), and year (STYEAR)
representing the calendar start of the connection.
D 15:48 Column D is made up of two fields: hour (STHOUR) and minutes (STMIN) representing the
time that the connection started. In this case 3:48 p.m.
Table 3-3 CDR Record Interpreted (Sheet 1 of 3)
Figure 3-1 Example of a CDR Record in HiPath 4000
## #@/#@/#@ #@:#@ #@:#@:#@ ####@ #@@@@@@@@@@@@@@ #@@@@@@@@@@@@@@@@@@@@@ #@@@@@@@@@@@@@@ #@@@@ #@@@ #@@@ #@@@@@ #@@@@@@@@@@@
AB C C C D D E E E FGHI J K L M N O P Q
1 2 3 1 2 1 2 3
ST 11/11/04 15:48 00:00:15 0TBNO 32007 4927009 9 1834 1534
35. 6079ch3.fm
A31003-H3140-S109-1-7620,
October
2007
HiPath
4000
V4,
Call
Detail
Recording
Reference
Guide
3-17
CDR
Output
Formats
Default
Output
Format
E 0:00:15 Column E is made up of three fields representing the duration of the call in hours
(CONHOUR), minutes (CONMIN), and second (CONSEC). In this case, the duration was15
seconds.
F 0 A number representing the Class of PIN (COPIN) that the caller is using. The (0) value
indicates that a COPIN was not used.
0 = No valid class of PIN
1 = Manual PIN for mobile user
2 = Business PIN for long service
3 = Business PIN used for the call
4 = Private PIN used for the call
5 = Project code used for the call
6 = ID card for mobile user
7 = Switchover code
8 = PIN for service ID
9 = CDR account code
10 = PIN for dialing pattern check
G T The column G identifies the type of the destination party (DESTPID). The value T is obtained
from SUBSID in AMO-TEXT, with the full abbreviation being TLN, indicating subscriber.
DESTPID is represented by a single digit.
1 = VF =Operator console
2 = HAS= PBX set
3 = NST= Night server
4 = TLN = Subscriber
5 = SM= Service module (for field paying party ID only)
6 = SPC= Special charging (for field paying party ID only)
7 = MEQ= Maintenance equipment (for field paying party ID only)
8 = PUP= Public phone via SLMAR to HiPath (for field paying party ID only)
9 = MOB = Mobile user
10 = KEY = Number of the other line (keyset)
Column Value Interpretation
Table 3-3 CDR Record Interpreted (Sheet 2 of 3)
36. CDR
Output
Formats
A31003-H3140-S109-1-7620,
October
2007
3-18
HiPath
4000
V4,
Call
Detail
Recording
Reference
Guide
6079ch3.fm
Default
Output
Format
Table 3-4 on page 3-19 provide the details for the SUPLSERV parameter. In the example output, the field length is two
digits.
H B The B in column H represents the relative expensiveness of the route chosen. In this case,
the B stands for the German word “BILLIG” indicating that this is an inexpensive connection.
0 = BILLIG = Inexpensive connections
1 = TEUER= Expensive connections
2 = GRATIS_A = Free of charge A-party
3 = GRATIS_B = Free of charge B-party
I NO Field I (SUPLSERV) has a value of “NO” indicating that this is a normal connection. Refer to
Table 3-4 on page 3-19 for legend.
J 32007 Field J represents the calling party (CALLIPTY). When CALLIPTY was defined in AMO-
FTBL, its value was defined to be 15 digits in length and left shifted.
K 4927009 Field K represents the number of destination party (DESTPTY). Field G indicates the type of
destination party, in this case a subscriber; whereas field K indicates the number of the
destination party—9999.
L blank Field L (RTIONPTY) is intended to indicate the number to which the calling party was
redirected. In this case, the calling party was not redirected, therefore, field L is blank.
M 9 Column M indicates the access code or route code that the caller dialed. The access code
that the calling party dialed was 9.
N 1834 Field N (TKNOREAL) is a line number representing the real trunk number of recording point
and is four digits in length. It can be viewed using AMO-SDSU.
O 1534 Field O (INTNREAL) is a line number representing the real trunk number of the non-recording
point and is four digits in length. It can be viewed using AMO-SDSU.
P blank Account code —Intended to capture the account code that the caller inputted before or during
the call. On this call it was not used.
Q blank PIN—Intended to capture the personal identification code that the caller inputted before the
call. On this call it was not used.
Column Value Interpretation
Table 3-3 CDR Record Interpreted (Sheet 3 of 3)
37. 6079ch3.fm
A31003-H3140-S109-1-7620,
October
2007
HiPath
4000
V4,
Call
Detail
Recording
Reference
Guide
3-19
CDR
Output
Formats
Default
Output
Format
For CDR, the output form lies at the center of its ability to provide data for the reports.
0 = Not defined
1 = Normal call
2 = Consultation call
3 = Call transfer
4 = Call back
5 = Call fwd busy
6 = Call fwd unconditional
7 = Call fwd no reply
8 = Call pickup
9 = Conference
10 = Override
11 = Hunting group
12 = Mail box
13 = Paging
14 = Dictation
15 = Credit card charge
16 = Reverse charging
17 = Call defection
18 = Door opening
19 = Ring back
20 = Hang up on hold
21 = Hang up on queuing
22 = End of queuing
23 = Begin of queuing
24 = Master transfer
25 = Recall
26 = Intercept
27 = ZVF
28 = Not output !!!
29 = Busy
30 = Not output !!!
31 = Attendant activated night service
32 = Attendant deactivated night service
33 = Attendant pulled jack
34 = Attendant reconnected jack
35 = Attendant console out of order
36 = Attendant console restarted
37 = hang up while queued at hunt groups
38 = Hunt group busy
39 = Record with SWU and ADP load
40 = Call transits a node
41 = Call rerouting
42 = Incoming call barred
43 = Destination party out of
service
44 = Resource unavailable
45 = Call rejected
46 = Unassigned number
47 = Account code
48 = the paying convener is
active in conference
49 = the paying convener has
already left the conference
50 = A party put on hold
51 = B party put on hold
52 = A party back from hold
53 = B party back from hold
54 = A party hang up while hold
55 = B party hang up while hold
56 = Ringing after connect
Table 3-4 SUPLSERV Legend
39. 6079ch4.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 4-1
An Overview of the Configuration Process
Outputting CDR Records: An Overview
4 An Overview of the Configuration Process
Now that the output format has been explained, one has to select the default form or amend it
to comply with the customer’s wishes. This chapter explains how to select or amend the default
form. In addition, this chapter explains how to select which transactions the users make for the
report.
The call details have to be directed to an output device. The paths to the devices have to be
activated. If a failure occurs in in output device, the call details may have to be redirected to
another device, such as the hard drive located in the switch itself.
In general, this chapter explains the process used in setting up CDR. The use of this process
entails:
1. Configuring a selection group or groups (AMO-SELG)
2. Activating the selection group (AMO-SELS)
3. Configuring the CDR devices (AMO-GEZU)
4. Activating CDR in the switch (AMO-FEACG)
5. Defining the CDR record retrieval requirements (AMO-GEZAB)
6. Activating the CDR features (AMO-FEASU)
4.1 Outputting CDR Records: An Overview
This section provides an overview of the steps necessary to configure the system to output
CDR to a collection device. The actual procedures to perform this configuration are located in
Chapter 5, “Configuring the HiPath 4000 System to Output CDR Records”.
4.1.1 Define Selection Group
Use AMO-SELG to define Selection Groups.
To output CDR records, several steps must be performed:
1. Choose a Selection Group to define.
2. Selecting a base (primary) output device as well as a reserve (secondary) output device.
3. Set the HiPath 4000 block sizes to 1.
4. Indicate whether the reserve operation should be set to Yes or No.
● If you wish the call detail records to be sent to the reserve device immediately upon
failure of the base device, set the reserve operation to Yes.
40. An Overview of the Configuration Process
A31003-H3140-S109-1-7620, October 2007
4-2 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch4.fm
Outputting CDR Records: An Overview
● If you want the call detail records to be buffered initially upon failure of the base device,
set the reserve operation to No.
Selection Table
Each Selection Group has 8 selection tables. Each of 8 tables will use the base and reserve
devices as well as the block sizes. If reserve operation is enabled, it will apply to all of the
selection tables within the chosen Selection Group.
At this point, one needs to define the selection table. A selection table must use a form
containing the fields (elements) that the customer wishes to have included in the report. If a
reserve or secondary device is used, a form for this device must also be specified.
Other details must be specified, such as domain, subdomain, and node of the switch; which
attendant console groups are to be included, and so on. The type of service to be recorded:
voice, fax, or data must be indicated. Other questions need to be answered, such as: Have
limits been set so that if a caller exceeds those limits, these excesses can be reported?
Even the carriers (AT&T, MCI, etc.) can be specified or we can include all carriers in the report.
Selection Features 1
Specific sources of call details can be included in the report:
Connection Type: Internal, Incoming, Outgoing, etc.; calls that are through-connected; local
and toll calls, along with many other distinctions.
Selection Features 2
We can place paying parties in station tables or destination tables and track the stations or
numbers. Other distinctions may also be included to refine the source of data for the report.
Station and Destination Lists
Sometimes it may be necessary to monitor station numbers and destination numbers. These
numbers are entered in a station table or a destination table. In the system, there are two of
each type table: Station Table 1 (STATAB1) and 2 (STATAB2) and Destination Table 1
(DNOTBL1) and 2 (DNOTBL2). When numbers are entered in these tables and are selected
on a selection table, the transactions related to those numbers are output in the report.
>
One selection table can handle everything required in a report. Multiple tables are
only necessary if the customer wants different formats for voice, data, or fax calls. If
the customer requires separate reports for voice, data, and fax, then three tables are
required, each using different formats.
41. 6079ch4.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 4-3
An Overview of the Configuration Process
Outputting CDR Records: An Overview
4.1.2 Activating Selection Groups
Use AMO-SELS to switch on and off the Selection Groups defined in AMO-SELG.
The selection groups must be controlled. That is, they must be switched on or off. The selection
group may be turned on conditionally.,that is, conditionally with regard to the data being output.
When the switch outputs call data, the data is placed in a queue and from the queue, the data
is released. Four possible conditions exists:
1. The selection group is switched on (CDR “on”). When the switch outputs the call
record, it is inserted into a queue, and is released from the queue to the device.
2. The selection group is conditionally switched on (CDR “on” with queue). When the
switch outputs the call record, it is inserted into a queue, however, the queue is blocked
until the selection group is switched back on or the selection group is switched off.
All call records that are already inserted into the output queue for output at this time remain
secured for output as long as the memory capacity of the overflow memory or of the group-
specific memory has been reached. When the memory capacity is reached, the output to
the reserve device is started.
3. The selection group is conditionally switched off (CDR “off.” Buffered records are
not lost). With this setting no call record is processed in the Selection Tables of this
selection group, and thus no output is made.
However, all call charge data records that are already inserted into the output queue at the
time of the removal from service are still output. In the block output mode, this can result
in the formation of a partial block.
4. The selection group is switched off (CDR “off.” Buffered records are lost). In this
operating state, call records are not processed in the selection tables of this selection
group.
All call charge data records inserted into the queue at the time of the removal from service
are deleted.
4.1.3 Define CDR Devices
Use AMO-GEZU to allocate the CDR devices.
The CDR devices must also be configured. The system must know the type device to which it
is outputting. When the Selection Group were configured, symbolic device names were used
to identify the devices to which the output was being sent. The symbolic device names (such
as DEV1) must be given a physical name (such as TTY) and whether it is a printer, terminal,
some other device.
These devices are defined in AMO-GEZU.
42. An Overview of the Configuration Process
A31003-H3140-S109-1-7620, October 2007
4-4 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch4.fm
Outputting CDR Records: An Overview
4.1.4 Define CDR Record Retrieval Requirements
Use AMO-GEZAB to define the requirements for CDR record retrieval.
For whatever reason, call records are sometimes stored on the hard disk. If this is the case,
then these records must be retrieved by configuring the system ahead of time. The system must
know:
● Where the records are stored on the hard drive?
● The name of the file in which the records are stored.
● Whether to retrieve the entire file or a portion of it?
● Where to send the output, for example, DEV1?
● Should the record be deleted after it is retrieved?
● What form should be used, for example, Form 1 to 16?
● Should the output be done immediately?
● When should the retrieval be done? Immediately or at a specified time?
● Whether this is a single output or a part of a multiple output. If a multiple output is required,
the period must be specified.
– If multiple output is required, up to three different periods can be specified.
4.1.5 Activate/Deactivate CDR
Use AMO-FEACG to activate and deactivate CDR devices.
For CDR to be active in the switch, at least one output device type must be activated. To
deactivate CDR in the switch, deactivate all of the output device types.
4.1.6 Activate CDR Features
Use AMO-FEASU to activate and deactivate the CDR features.
Several features pertain to CDR which must be activated before they are functional:
● CDRACC – Call detail recording of account codes
● CDRE – Extended charge detail recording (not required for standard CDR)
● CDRINH – Call detail recording for in-house calls
● CDRIC – call detail recording for incoming network and trunk calls
● CDROGNW – call detail recording for outgoing network calls
43. 6079ch4.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 4-5
An Overview of the Configuration Process
Outputting CDR Records: An Overview
● CDROGTR – call detail recording for outgoing trunk calls
● DISCHINH – Display charges for in-house calls (not supported in US). Do not activate.
● DISCHNW – Display charges for network calls (not supported in US). Do not activate.
● DISCHTR – Display charges for trunk (not supported in US). Do not activate.
44. An Overview of the Configuration Process
A31003-H3140-S109-1-7620, October 2007
4-6 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch4.fm
Outputting CDR Records: An Overview
45. 6079ch5.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 5-1
Configuring the HiPath 4000 System to Output CDR Records
CDR Configuration Steps
5 Configuring the HiPath 4000 System to Output
CDR Records
5.1 CDR Configuration Steps
Although Table 5-1 lists the various steps required to output CDR records, the section
containing the steps refer in sequential order to the next step and it is not necessary to return
to Table 5-1 after each section.
Action Reference
Configure the format table to be used for the call detail
report.
Perform the procedure in Section
5.1.1, “Configuring the Report
Elements”, on page 5-2.
Configure the Selection Group Perform the procedure in Section
5.1.2, “Configuring the Selection
Group”, on page 5-7.
Configure the Selection Table Perform the procedure in Section
5.1.3.1, “Selection Table”, on
page 5-9.
Activate selection group Use the procedure found in
Section 5.1.4, “Activating
Selection Group”, on page 5-13.
Configure the CDR devices Perform the procedure in Section
5.1.5, “Configuring the CDR
Devices”, on page 5-15
Make provisions for retrieving records from hard drive Complete the steps in Section
5.1.7, “Retrieving Records Stored
on Hard Drive”, on page 5-17.
Activating CDR Perform the procedure in Section
5.1.6, “Activating CDR”, on page
5-16.
Activate Appropriate CDR Features Complete the procedure in
Section 5.1.8, “Activating CDR
Features”, on page 5-21.
Testing CDR output Perform the procedure in Section
5.2, “Testing System for CDR
Output”, on page 5-24.
You have successfully set up Standard CDR
Table 5-1 Outputting CDR Records (Sheet 1 of 2)
46. Configuring the HiPath 4000 System to Output CDR Records
A31003-H3140-S109-1-7620, October 2007
5-2 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch5.fm
CDR Configuration Steps
5.1.1 Configuring the Report Elements
Using AMO-FTBL, configure the report elements. To do so you must:
1. Identify the report elements that the customer wants on the CDR report.
2. Compare these report elements with those on the BLS website:
http://tac.fld.rolm.com/pub/9006/HiPath%204000/HP4000cdr_default.htm
3. Display AMO-FTBL to determined which forms between 1-16 that match the one identified
on the BLS website.
4. Display AMO-FTBL to determined which forms between 1-16 that are not used.
5. If there is a difference in steps 1 and 2, determine whether you will be adding fields or
deleting fields or both. Proceed to step 7.
6. If there is not a difference in the items in steps 1 and 2, proceed to step 9.
7. Regenerate (REGEN) AMO-FTBL representing the BLS form number found in step 3, and
copy the results to Microsoft Notepad.
8. Edit the items in Notepad from step 5 in the order in which the fields should appear in the
report, making additions and deletions as necessary. If you will be adding or making
deletions in the BLS form, refer to Section 5.1.1.1, “Making Changes to the BLS Default
Form” for detailed instruction.
9. You have completed configuring report elements.
10. Proceed to Section 5.1.2, “Configuring the Selection Group”.
5.1.1.1 Making Changes to the BLS Default Form
Figure 5-1 shows the default form as seen on the BLS website. The first three line show the
individual field lengths. The first field which represents the type SERVICE has only one
character, the # symbol. Each field begins with the # symbol. If a field is more than one digit in
length, it is filled out with the @ symbol or an actual character such as a colon (:) or slash (/).
For example, field three, STMONTH, is three digits long. Two of those digits represents the
number of the month with the third digit (/) being a separator. Field eight, CONHOUR, uses a
colon (:) separator.
Proceed to set up system for Performance Management. Go to Section 5.1, “CDR
Configuration Steps”, on page
5-1
Action Reference
Table 5-1 Outputting CDR Records (Sheet 2 of 2)
47. 6079ch5.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 5-3
Configuring the HiPath 4000 System to Output CDR Records
CDR Configuration Steps
Field 16 has its beginning character, a # symbol, on line one, but this field flows into the next
command on line two. To verify its length, count the # symbol and the @ that flowed into the
next line: In this case, 22 characters, including the # symbol.
To modify this form:
1. Locate this form in the switch on which you are working. It may be a different form number.
2. So perform a “DIS-FTBL;” and compare the contents: Field 1 to Field 22. When you see
a matching form, note the form number. Also note which form numbers between Form 1
and 16 are not used. Identify one of the unused form numbers to be used to assigned to
the modified form you are creating.
3. Regenerate the form that matched the one on the BLS website and copy the results into a
text editor, for example, Notepad. If are removing an FTBL element, proceed to Step 4 on
page 5-3.
4. Deleting an FTBL Element
ADD-FTBL:2,B,FORM,1,N,"## #@/#@/#@ #@:#@ #@:#@:#@ ####@ #@@@@@@@@@@@@@@ #";
ADD-FTBL:2,B,FORM,2,N,"@@@@@@@@@@@@@@@@@@@@@ #@@@@@@@@@@@@@@ #@@@@ #@@@ #";
ADD-FTBL:2,B,FORM,3,N,"@@@ #@@@@@ #@@@@@@@@@@@";
ADD-FTBL:2,B,CTRL,4,N,CR;
ADD-FTBL:2,B,CTRL,5,Y,LF;
ADD-FTBL:2,B,FIELD,1,SERVICE,CHAR,"0",L;
ADD-FTBL:2,B,FIELD,2,STNID,CHAR,"0",L;
ADD-FTBL:2,B,FIELD,3,STMONTH,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,4,STDAY,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,5,STYEAR,CHAR," ",R;
ADD-FTBL:2,B,FIELD,6,STHOUR,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,7,STMIN,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,8,CONHOUR,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,9,CONMIN,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,10,CONSEC,CHAR,"0",R;
ADD-FTBL:2,B,FIELD,11,COPIN,CHAR," ",L;
ADD-FTBL:2,B,FIELD,12,DESTPID,CHAR," ",L;
ADD-FTBL:2,B,FIELD,13,EXPENS,CHAR," ",L;
ADD-FTBL:2,B,FIELD,14,SUPLSERV,CHAR,"0",L;
ADD-FTBL:2,B,FIELD,15,CALLIPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,16,DESTPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,17,RTIONPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,18,ROUTCN,CHAR," ",L;
ADD-FTBL:2,B,FIELD,19,TKNOREAL,CHAR," ",L;
ADD-FTBL:2,B,FIELD,20,INTNREAL,CHAR," ",L;
ADD-FTBL:2,B,FIELD,21,ACCTCODE,CHAR," ",L;
ADD-FTBL:2,B,FIELD,22,PIN,CHAR," ",L;
Field Lngth = 1
Field Lngth = 1
Field Lngth = 3
Field Lngth = 3
Field Lngth = 2
Field Lngth = 3
Field Lngth = 3
Field Lngth = 3
Field Lngth = 3
Field Lngth = 2
Field Lngth = 1
Field Lngth = 1
Field Lngth = 1
Field Lngth = 2
Field Lngth = 15
Field Lngth = 22
Field Lngth = 15
Field Lngth = 5
Field Lngth = 4
Field Lngth = 4
Field Lngth = 6
Field Lngth = 12
Figure 5-1 Display of Form as Seen on BLS Website
Field
16
48. Configuring the HiPath 4000 System to Output CDR Records
A31003-H3140-S109-1-7620, October 2007
5-4 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch5.fm
CDR Configuration Steps
Let’s say you wish to delete DESTPTY found at position 16 (the bolded #) of the first line:
The DESTPTY field has 22 digits and overflows from line 1 into line 2 containing the second
command.
To delete an FTBL element, perform the following:
a) Note its field number and delete the entire line (bolded in the example) containing that
field.
b) Close the space left after the deletion.
c) Re-number all fields after the one you just deleted:
d) Proceed to step 6 on page 5-6
5. Adding an FTBL Element
Let’s say you wish to add the following:
At position 16, TRNSFPTY, length is 22 digits
>
In Notepad, use the Find command. In the Find What field enter the # character and
click Find Next, count each time you click until you reach the desired # characters.
ADD-FTBL:2,B,FORM,1,N,"## #@/#@/#@ #@:#@ #@:#@:#@ ####@ #@@@@@@@@@@@@@@ #";
ADD-FTBL:2,B,FORM,2,N,"@@@@@@@@@@@@@@@@@@@@@ #@@@@@@@@@@@@@@ #@@@@ #@@@ #";
ADD-FTBL:2,B,FIELD,15,CALLIPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,16,DESTPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,17,RTIONPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,15,CALLIPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,17,RTIONPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,16,RTIONPTY,CHAR," ",L;
ADD-FTBL:2,B,FIELD,17,ROUTCN,CHAR," ",L;
ADD-FTBL:2,B,FIELD,18,TKNOREAL,CHAR," ",L;
ADD-FTBL:2,B,FIELD,19,INTNREAL,CHAR," ",L;
ADD-FTBL:2,B,FIELD,20,ACCTCODE,CHAR," ",L;
ADD-FTBL:2,B,FIELD,21,PIN,CHAR," ",L;
49. 6079ch5.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 5-5
Configuring the HiPath 4000 System to Output CDR Records
CDR Configuration Steps
a) In Notepad, locate the current position 16 by counting the # symbols. You arrive at the
field in the first command (one with box around it). You will insert TRANSPTY field just
prior to this field.
This inserts the new field at the correct position.
Do not be concerned if the line is extended, the system will correct this.
b) In Notepad, for our example, find the line that reads:
ADD-FTBL:2,B,FIELD,16,DESTPTY,CHAR," ",L;
c) Copy this line (use Ctrl-C to copy), and at the beginning of this line, press the Enter
key.
d) In the space created above this line, Paste (use Ctrl-V to paste), the contents that you
just copied.
e) Edit the line just pasted by highlighting DESTPTY and type TRNSFPTY.
f) In the example, the Filltype will be CHAR, the Filler is null (no character), and the
justification should be left (L). The resulting line will look like:
ADD-FTBL:2,B,FIELD,16,TRNSFPTY,CHAR," ",L;
g) Re-number each of the fields after FIELD,16. The field containing DESTPTY will be
FIELD,17.
h) Proceed to step 6.
>
In Notepad, use the Find command. In the Find What field enter the # character
and click Find Next, count each time you click until you reach the desired #
characters. Stop at this point and enter the # character to insert the beginning
of the field to be inserted. Add @ symbols until you reach the field length, then
add a space.
ADD-FTBL:2,B,FORM,1,N,"## #@/#@/#@ #@:#@ #@:#@:#@ ####@ #@@@@@@@@@@@@@@
#@@@@@@@@@@@@@@@@@@@@@ #";
ADD-FTBL:2,B,FORM,2,N,"@@@@@@@@@@@@@@@@@@@@@ #@@@@@@@@@@@@@@ #@@@@ #@@@ #";
ADD-FTBL:2,B,FORM,3,N,"@@@ #@@@@@ #@@@@@@@@@@@";
ADD-FTBL:8,B,FIELD,16,TRNSFPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,17,DESTPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,18,RTIONPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,19,ROUTCN,CHAR," ",L;
ADD-FTBL:8,B,FIELD,20,TKNOREAL,CHAR," ",L;
ADD-FTBL:8,B,FIELD,21,INTNREAL,CHAR," ",L;
ADD-FTBL:8,B,FIELD,22,ACCTCODE,CHAR," ",L;
ADD-FTBL:8,B,FIELD,23,PIN,CHAR," ",L;
50. Configuring the HiPath 4000 System to Output CDR Records
A31003-H3140-S109-1-7620, October 2007
5-6 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch5.fm
CDR Configuration Steps
6. Change the form number to an unused one found in step 4 on page 5-2: Replace ADD-
FTBL:2 with ADD-FTBL:X, where X is an unused Form number found earlier between 1
and 16. In our example, Format 8 is used.
See the results of the changes made in this example by referring to Figure 5-2 on page 5-6.
Notice that the new field was inserted ahead of the previous field 16, DESTPTY. Even
though line 1 was extended further, the system will accommodate this. In our example, the
extended line 1 wrapped to a second line.
7. Use the resulting Notepad edits, run a script executing AMO-FTBL with the changes made.
8. After the script runs, you want to see:
AMO-FTBL -111 SMDR/DMDR TABLE FORMATS
ADD COMPLETED;
ADD-FTBL:8,B,FORM,1,N,"## #@/#@/#@ #@:#@ #@:#@:#@ ####@ #@@@@@@@@@@@@@@
#@@@@@@@@@@@@@@@@@@@@@ #";
ADD-FTBL:8,B,FORM,2,N,"@@@@@@@@@@@@@@@@@@@@@ #@@@@@@@@@@@@@@ #@@@@ #@@@ #";
ADD-FTBL:8,B,FORM,3,N,"@@@ #@@@@@ #@@@@@@@@@@@";
ADD-FTBL:8,B,CTRL,4,N,CR;
ADD-FTBL:8,B,CTRL,5,Y,LF;
ADD-FTBL:8,B,FIELD,1,SERVICE,CHAR,"0",L;
ADD-FTBL:8,B,FIELD,2,STNID,CHAR,"0",L;
ADD-FTBL:8,B,FIELD,3,STMONTH,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,4,STDAY,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,5,STYEAR,CHAR," ",R;
ADD-FTBL:8,B,FIELD,6,STHOUR,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,7,STMIN,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,8,CONHOUR,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,9,CONMIN,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,10,CONSEC,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,11,COPIN,CHAR," ",L;
ADD-FTBL:8,B,FIELD,12,DESTPID,CHAR," ",L;
ADD-FTBL:8,B,FIELD,13,EXPENS,CHAR," ",L;
ADD-FTBL:8,B,FIELD,14,SUPLSERV,CHAR,"0",L;
ADD-FTBL:8,B,FIELD,15,CALLIPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,16,TRNSFPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,17,DESTPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,18,RTIONPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,19,ROUTCN,CHAR," ",L;
ADD-FTBL:8,B,FIELD,20,TKNOREAL,CHAR," ",L;
ADD-FTBL:8,B,FIELD,21,INTNREAL,CHAR," ",L;
ADD-FTBL:8,B,FIELD,22,ACCTCODE,CHAR," ",L;
ADD-FTBL:8,B,FIELD,23,PIN,CHAR," ",L;
Figure 5-2 Display of BLS Website Form Edited
51. 6079ch5.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 5-7
Configuring the HiPath 4000 System to Output CDR Records
CDR Configuration Steps
9. After the script completes, perform: REG-FTBL:X, where X is the format number you used
in the script. In our example, this was REG-FTBL:8. See Figure 5-3 on page 5-7 for the
results.
10. Proceed to step 9 on page 5-2.
5.1.2 Configuring the Selection Group
Using AMO-SELG, perform the following:
1. Configure a selection group, typically Selection Group 1
2. Identify the primary (base) device used to collect CDR: AMO-SELG
REG-FTBL:8;
H500: AMO FTBL STARTED
ADD-FTBL:8,B,FORM,1,N,"## #@/#@/#@ #@:#@ #@:#@:#@ ####@ #@@@@@@@@@@@@@@ #";
ADD-FTBL:8,B,FORM,2,N,"@@@@@@@@@@@@@@@@@@@@@ #@@@@@@@@@@@@@@@@@@@@@ #@@@@";
ADD-FTBL:8,B,FORM,3,N,"@@@@@@@@@@ #@@@@ #@@@ #@@@ #@@@@@ #@@@@@@@@@@@";
ADD-FTBL:8,B,CTRL,4,N,CR;
ADD-FTBL:8,B,CTRL,5,Y,LF;
ADD-FTBL:8,B,FIELD,1,SERVICE,CHAR,"0",L;
ADD-FTBL:8,B,FIELD,2,STNID,CHAR,"0",L;
ADD-FTBL:8,B,FIELD,3,STMONTH,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,4,STDAY,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,5,STYEAR,CHAR," ",R;
ADD-FTBL:8,B,FIELD,6,STHOUR,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,7,STMIN,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,8,CONHOUR,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,9,CONMIN,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,10,CONSEC,CHAR,"0",R;
ADD-FTBL:8,B,FIELD,11,COPIN,CHAR," ",L;
ADD-FTBL:8,B,FIELD,12,DESTPID,CHAR," ",L;
ADD-FTBL:8,B,FIELD,13,EXPENS,CHAR," ",L;
ADD-FTBL:8,B,FIELD,14,SUPLSERV,CHAR,"0",L;
ADD-FTBL:8,B,FIELD,15,CALLIPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,16,TRNSFPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,17,DESTPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,18,RTIONPTY,CHAR," ",L;
ADD-FTBL:8,B,FIELD,19,ROUTCN,CHAR," ",L;
ADD-FTBL:8,B,FIELD,20,TKNOREAL,CHAR," ",L;
ADD-FTBL:8,B,FIELD,21,INTNREAL,CHAR," ",L;
ADD-FTBL:8,B,FIELD,22,ACCTCODE,CHAR," ",L;
ADD-FTBL:8,B,FIELD,23,PIN,CHAR," ",L;
AMO-FTBL -111 SMDR/DMDR TABLE FORMATS
REGENERATE COMPLETED;
Figure 5-3 FTBL Regeneration Results After Script Runs
52. Configuring the HiPath 4000 System to Output CDR Records
A31003-H3140-S109-1-7620, October 2007
5-8 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch5.fm
CDR Configuration Steps
3. Identify the reserve (backup or secondary) device used to collect CDR: AMO-SELG.
Use Table 5-2 to select your devices.
4. Define whether reserve operation is to be permitted.
5. Set the block size for base operations to 1.
6. Set the block size for reserve operations to 1.
A typical example of this configuration is shown in Figure 5-4 on page 5-8.
This AMO SELG example indicates that when CDR records are generated by the
Switching Unit, the records will be output immediately to DEV1 (RMX Maintenance port).
Since the parameter RESOP=Yes, if the RMX port is not connected (DTR not HIGH), the
records will be sent to the HiPath 4000 hard disk (CDRC1), and must be retrieved manually
by using the AMO GEZAB.
If RESOP=No, and the RMX port is not connected, the next 2200 call detail records are
stored in a temporary memory buffer on the ADP. Subsequent records will be stored on
the HiPath 4000 hard disk. When the RMX port is re-connected, the call detail records in
the temporary buffer are immediately output. Call detail records that overflowed to the hard
disk must be retrieved using the AMO GEZAB.
Device Comment
CDRC1 Call detail recording – central, file 1
CDRC2 Call detail recording – central, file 2
DEV1, DEV2, DEV3, or DEV4 Output the data on device (DEV1, 2, 3, or 4)
FT Output the data to a file-transfer (FT) file, typically
used with Collecting Agent (COL).
Table 5-2 Devices used in US
Figure 5-4 Display of Selection Group 1
+==============================================================================+
| SELECTION GROUP : 1 |
+------------------------------------------------------------------------------+
| |
| OPERATING STATE : ON
| |
| RESOP : Y |
| BASDEV : DEV1 BLBAS : 1 |
| RESDEV : CDRC1 BLRES : 1 |
| |
+==============================================================================+
53. 6079ch5.fm
A31003-H3140-S109-1-7620, October 2007
HiPath 4000 V4, Call Detail Recording Reference Guide 5-9
Configuring the HiPath 4000 System to Output CDR Records
CDR Configuration Steps
7. Proceed to Section 5.1.3, “Defining the Type of Records to Be Outputted”
5.1.3 Defining the Type of Records to Be Outputted
In this section, you will configure the Selection Table for the selection group configured above
along with the selection features. Proceed to Section 5.1.3.1, “Selection Table”
5.1.3.1 Selection Table
Using AMO-SELG, configure the following within a specified selection group:
1. Configure a selection table (1 of 8)
2. Identify the output format to be used by the base device. Valid entries in the US are:
FORM01, FORM02...FORM16, HDFORM, and NOFORM
3. Define the output format to be used by the reserve device. The choice of devices are the
same as in step 2.
4. Specify the node, subdomain, and domain number of this switch. Unless, information is
available to the contrary, chain the values: LEVEL0 = 0&&999; LEVEL1 = 0&&254;
LEVEL2 = 0&&30
5. Indicate the CDR route codes (CDRCD) to be used by callers, for example 8 for private
calls (RNET) and 9 for public calls. The values can be chained. Unless, information is
available to the contrary, chain the values: 0&&999999
6. Indicate the Attendant Console groups from which data will be collected. Unless,
information is available to the contrary, chain the values: 0&&15.
7. Indicate the type of service from which data will be collected: Voice, Data, and Fax. These
values can be chained: VOICE&DTE&FAX
8. Call charge unit limit value (CDRULT) should be 0, since call charging in the US in not
utilized.
9. If the customer is interested in seeing calls that exceed a certain time limit, enter the
customer’s time limit in the hh:mm:ss format in the CONNTL field.
10. Identify the number of carriers (CARRIER) associated with various routes used in the
system. Five numbers can be chained. The actual names can be associated with the
numbers entered here are defined in AMO-TEXT.
a) For each carrier name defined here, enter a name in AMO-TEXT under the entry for
CARRIER, for example, 0 = AT & T, 1 = MCI, etc.
11. If the customer wishes to see the Class of PIN (COPIN), identify which classes that the
customer desires to see. The COPIN values can be chained.
54. Configuring the HiPath 4000 System to Output CDR Records
A31003-H3140-S109-1-7620, October 2007
5-10 HiPath 4000 V4, Call Detail Recording Reference Guide
6079ch5.fm
CDR Configuration Steps
12. In the US, TARIFF should be set to NOCALC.
13. The destination count (DESTCNT) should be specified indicated the extent to which the
called party or the connected party’s output should be reduced (Ax or Lx). The Ax indicates
the numbers of digits included starting with the first position whereas the Lx indicates the
number of digits included starting with the last position.
14. Now proceed to Section 5.1.3.2, “Selection Features 1”.
5.1.3.2 Selection Features 1
Continue to use AMO-SELG to define the features listed below:
1. Complete the CTYPE parameter to specify whether the record to be outputted is to be for
local or toll calls or whether they are to be for all calls.
2. Indicate whether the system, using the CDRAC parameter, should output records that are:
● associated with Attendant call setup using the CDRAC key (Enter ATND)
● marked with CDRACS code for station setup (Enter STN)
● for all calls (Enter N)
3. If the customer wants to see only faulty records, indicate this using the CDBAD parameter
by entering Y, otherwise enter N and all records (good ones as well as faulty ones) will be
output.
4. If the customer only wants station records with central CDR authorization to be output,
enter Y for the CDRC parameter. If all records are to be output, enter N.
5. If the customer only wants to see station records with station authorization to be output,
enter Y for the CDRSTA parameter. By entering N, this criteria does not apply.
6. Indicate the type connections (CONNTYP) that CDR data is to be outputted for:
Values can be chained together.
Type Connection Details
INT output only internal connections
INCO output only incoming connections
OUTG output only outgoing connections
LOAD output of processor load
ACACT output of events of attendant console
ALL Output all connections (this is the default)
Table 5-3 Connection Types
