Cisco Systems OL-1089-11 User Manual
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
December, 2007
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-1089-11
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way
We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA,
CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo,
Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient,
IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX,
Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The
Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United
States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0805R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
© 2008 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface xi
Document Objective xi
Audience xi
Document Organization xii
Document Conventions xii
Cisco Media Gateway Controller Documentation Suite xv
Cisco Media Gateway Controller Documentation Map xvi
Obtaining Documentation, Obtaining Support, and Security Guidelines xvii
Summary History of Document Changes xvii
CHAPTER
1 Billing Interfaces 1-1
Billing Capabilities Overview 1-1
System Interfaces 1-1
Physical Interface 1-1
RADIUS Interface 1-2
Message Interface 1-2
CDB Message Format 1-2
Tag Values 1-3
Formats and Codes 1-4
CDB Record Types 1-4
Call Data Block Descriptions 1-6
Enabling Call Screening 1-7
Configuring Call Detail Record File Output 1-7
Configuring Call Detail Record Message Types 1-8
Enabling Call Screening 1-8
Configuring Call Detail Record File Output 1-8
Call Data Element Descriptions 1-9
Cisco MGC Billing Interfaces 1-19
FTP Interface 1-20
Generic Interface 1-20
OL-1089-11
Redundant Cisco MGC Configuration 1-20
Cisco MGC Clock Synchronization 1-21
Detailed CDB Description 1-21
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
iii
Contents
Answered CDB Record (Tag: 1010/Release 5 or Later) 1-21
Deselected Outgoing Circuit CDB Record (Tag: 1020/Release 5 or Later) 1-25
Aborted Attempt CDB Record (Tag: 1030/Release 5 or Later) 1-27
Release CDB Record (Tag: 1040/Release 5 or Later) 1-31
Interrupted CDB Record (Tag: 1050/Release 5 or Later) 1-34
On-Going (Call) CDB Record (Tag: 1060/Release 5 or Later) 1-34
Maintenance CDB Record (Tag: 1070/Release 5 or Later) 1-37
SS7 CIC Audit CDB Record (Tag: 1071/Release 9 or Later) 1-37
External Access CDB (Tag: 1080/Release 7 or Later) 1-39
File Header CDB (Tag: 1090/Release 7 or Later) 1-40
File Footer CDB (Tag: 1100/Release 7 or Later) 1-40
End of the Call CDB (Tag: 1110/Release 7 or Later) 1-41
Slave End-of-Call CDB Record (Tag: 1210/Release 9.6 or Later) 1-46
Slave Long Duration Call CDB Record (Tag: 1260/Release 9.6 or Later) 1-47
CDE Detail Description 1-48
CDEs Encoded in ANSI 1-49
Calling Party Category (Tag: 2000/ANSI) 1-49
User Service Information (Tag: 2001/ANSI) 1-50
Originating Line Information (Tag: 2002/ANSI) 1-51
Calling Number Nature of Address (Tag: 2003/ANSI) 1-52
Charged Number Nature of Address (Tag: 2004/ANSI) 1-53
Dialed Number Nature of Address (Tag: 2005/ANSI) 1-54
LRN Nature of Address (Tag: 2006/ANSI) 1-55
Called Number Nature of Address (Tag: 2007/ANSI) 1-56
Reason Code (Tag: 2008/ANSI) 1-57
Forward Call Indicators Received (Tag: 2009/ANSI) 1-58
Forward Call Indicators Sent (Tag: 2010/ANSI) 1-59
Nature of Connection Indicators Received (Tag: 2011/ANSI) 1-60
Nature of Connection Indicators Sent (Tag: 2012/ANSI) 1-61
Transit Network Selection (Tag: 2013/ANSI) 1-62
Carrier Identification Parameter (Tag: 2014/ANSI) 1-63
Carrier Selection Parameter (Tag: 2015/ANSI) 1-63
Jurisdiction Information Parameter (Tag: 2016/ANSI) 1-64
Redirecting Number Nature of Address (Tag 2017/ANSI) 1-64
Egress Calling Number Nature of Address (Tag 2018/ANSI) 1-65
Egress Redirecting Number Nature of Address (Tag 2019/ANSI) 1-66
Egress Original Called Number Nature of Address (Tag 2020/ANSI) 1-67
CDE Encoded as ITU Recommendation 1-68
Calling Party Category (Tag: 3000/ITU) 1-68
User Service Information (Tag: 3001/ITU) 1-69
iv
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Originating Line Information (Tag: 3002/ITU) Retired 1-70
Calling Number Nature of Address (Tag: 3003/ITU) 1-70
Charged Number Nature of Address (Tag: 3004/ITU) Retired 1-71
Dialed Number Nature of Address (Tag: 3005) 1-72
LRN Nature of Address (Tag: 3006/ITU) 1-73
Called Number Nature of Address (Tag: 3007/ITU) 1-74
Reason Code (Tag: 3008/ITU) 1-75
Forward Call Indicators Received (Tag: 3009/ITU) 1-88
Forward Call Indicators Sent (Tag: 3010/ITU) 1-89
Nature of Connection Indicators Received (Tag: 3011/ITU) 1-91
Nature of Connection Indicators Sent (Tag: 3012/ITU) 1-92
Transit Network Selection (Tag: 3013/ITU) 1-93
Redirecting Number Nature of Address (Tag 3017/ITU) 1-94
Egress Calling Number Nature of Address (Tag 3018/ITU) 1-95
Egress Redirecting Number Nature of Address (Tag 3019/ITU) 1-96
Egress Original Called Number Nature of Address (Tag 3020/ITU) 1-97
MGC Generic CDEs 1-98
CDB Version (Tag: 4000) 1-98
CDB Timepoint (Tag: 4001) 1-98
Call Reference ID (Tag: 4002) 1-98
IAM/Setup Timepoint (Tag: 4003) 1-99
ACM/Alert Timepoint (Tag: 4004) 1-99
ANM/Answer Timepoint (Tag: 4005) 1-99
REL/Release Timepoint (Tag: 4006) 1-100
Crash Timepoint (Tag: 4007) 1-100
Originating Trunk Group (Tag: 4008) 1-100
Originating Member (Tag: 4009) 1-101
Calling Number (Tag: 4010) 1-101
Charged Number (Tag: 4011) 1-101
Dialed Number (Tag: 4012) 1-102
LRN Number (Tag: 4013) 1-102
Called Number (Tag: 4014) 1-102
Terminating Trunk Group (Tag: 4015) 1-103
Terminating Member (Tag: 4016) 1-103
Maintenance Trunk Group (Tag: 4017) 1-103
Maintenance Circuit Member (Tag: 4018) 1-104
Glare Encountered (Tag: 4019) 1-104
RLC/RELEASE Complete Timepoint (Tag: 4020) 1-104
First Release Source (Tag: 4028) 1-105
LNP Dip (Tag: 4029) 1-105
Contents
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
v
Contents
Total Meter Pulses (Tag: 4030) 1-106
Maintenance Type (Tag: 4032) 1-106
Maintenance Reason (Tag: 4033)—Retired 1-107
Ingress Originating Point Code (Tag: 4034) 1-108
Ingress Destination Point Code (Tag: 4035) 1-108
Egress Originating Point Code (Tag: 4036) 1-109
Egress Destination Point Code (Tag: 4037) 1-109
Ingress Media Gateway ID (Tag: 4038) 1-110
Egress Media Gateway ID (Tag: 4039) 1-110
TCAP Transaction ID (Tag: 4040) 1-110
Transaction Start Time (Tag: 4041) 1-111
Transaction End Time (Tag: 4042) 1-111
TCAP Database ID (Tag: 4043) 1-111
Announcement ID (Tag: 4044) 1-112
Route Selection Info (Tag: 4045) Retired 1-112
Ingress Packet Info (Tag: 4046) Restored 1-113
Egress Packet Info (Tag: 4047) Restored 1-114
Directional Flag (Tag: 4048) 1-114
Service Logic ID (Tag: 4049) 1-115
AMA Line Number (Tag: 4050) 1-115
OOriginating Gateway Primary Select (Tag: 4052) Defined for Future Use 1-116
Terminating Gateway Primary Select (Tag: 4053) Defined for Future Use 1-116
Redirecting Number (Tag: 4060) 1-116
Scale Factor (Tag: 4062) 1-117
Test Line Indicator (Tag: 4063) 1-117
Redirection Number (Tag: 4065) 1-118
Ingress SigPath ID (Tag: 4066) 1-118
Ingress Span ID (Tag: 4067) 1-118
Ingress BearChan ID (Tag: 4068) 1-119
Ingress Protocol ID (Tag: 4069) 1-119
Egress SigPath ID (Tag: 4070) 1-120
Egress Span ID (Tag: 4071) 1-120
Egress BearChan ID (Tag: 4072) 1-120
Egress Protocol ID (Tag: 4073) 1-121
Maintenance SigPath ID (Tag: 4074) 1-121
Maintenance Span ID (Tag: 4075) 1-122
Maintenance BearChan ID (Tag: 4076) 1-122
Maintenance Circuits Count (Tag: 4077) 1-122
Charge Band Number (Tag: 4078) 1-123
Furnish Charging Information (Tag: 4079) 1-123
vi
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Original Called Number (Tag: 4080) 1-124
T.38 Fax Call (Tag: 4081) 1-124
Charge Unit Number (Tag: 4082) 1-125
Charge Indicator (Tag: 4083) 1-125
Outgoing Calling Party Number (Tag: 4084) 1-126
MCID Request Indicator (Tag: 4085) 1-126
MCID Response Indicator (Tag: 4086) 1-127
Ingress MGCP DLCX Return Code (Tag: 4087) 1-127
Egress MGCP DLCX Return Code (Tag: 4088) 1-127
Network Translated Address Indicator (Tag: 4089) 1-128
Reservation Request Accepted (Tag: 4090) 1-128
Reservation Request Error Count (Tag: 4091) 1-129
ATM Ingress Configured Profile (Tag: 4092) 1-129
ATM Egress Configured Profile (Tag: 4093) 1-130
ATM Negotiated Profile (Tag: 4094) 1-131
Route List Name (Tag: 4095) 1-131
Route Name (Tag: 4096) 1-132
MGCP Script Response String (Tag: 4097) 1-132
Originating Leg DSP Statistics (Tag: 4098) 1-133
Terminating Leg DSP Statistics (Tag: 4099) 1-135
Originating Remote SIP Host (Tag: 4201) 1-136
Originating Local SIP Host (Tag: 4202) 1-136
SIP Call ID (Tag: 4203) 1-136
Source IP Address (Tag: 4204) 1-137
Ingress Media Device Address (Tag: 4205) 1-137
Egress Media Device Address (Tag: 4206) 1-138
Initial Codec (Tag: 4207) 1-138
Final Codec (Tag: 4208) 1-139
Ingress Media Device Port (Tag: 4209) 1-139
Egress Media Device Port (Tag: 4210) 1-139
Originating VPN ID (Tag: 4211) 1-140
Terminating VPN ID (Tag: 4212) 1-140
Meter Pulses Received (Tag: 4213) 1-141
Meter Pulses Sent (Tag: 4214) 1-141
Charge Tariff Info (Tag: 4215) 1-142
Advice of Charge Indicator (Tag: 4216) 1-142
Short Call Indicator (Tag: 4217) 1-143
Charge Limit Exceeded (Tag: 4218) 1-143
Call Recovered Indication (Tag: 4219) 1-144
Partial Calling Line Identity (Tag: 4220) 1-144
Contents
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
vii
Contents
Service Activation (Tag: 4221) 1-145
PRI AOC Invoke Type (Tag: 4222) 1-145
PRI AOC – S Charge Information (Tag: 4223) 1-146
PRI AOC – D Charge Information (Tag: 4224) 1-146
PRI AOC – E Charge Information (Tag: 4225) 1-147
PRI AOC Invoke Failure (Tag: 4226) 1-147
Route Optimization/Path Replacement Action (Tag: 4227) 1-148
Route Optimization/Path Replacement Call Reference of Associated Call Instance (Tag:
4228) 1-148
Route Optimization/Path Replacement Trunk Group Info (Tag: 4229) 1-149
Route Optimization/Path Replacement Channel Info (Tag: 4230) 1-149
Route Optimization Switchover Timestamp (Tag: 4231) 1-149
Rejecting Location Label (Tag: 4232) 1-150
Rejecting Location Label Direction (Tag: 4233) 1-150
Total Circuit Count (Tag: 4234) 1-151
Total Circuits Unavailable Count (Tag: 4235) 1-151
H323 Destination (Tag 4236) 1-151
Ingress Redirecting Number (Tag 4237) 1-153
Service Usage Data (Tag 4239) 1-153
CNAM DIP (Tag 4240) 1-154
Calling Party Name (Tag 4241) 1-154
Terminating Remote SIP Host (Tag 4242) 1-155
Terminating Local SIP Host (Tag 4243) 1-155
License Rejecting Reason (Tag 4244) 1-155
License Rejecting Direction (Tag 4245) 1-156
SIP Transport (Tag 4246) 1-156
SIP Routing URI Source (Tag 4247) 1-157
SIP Routing URI (Tag 4248) 1-157
Millisecond Granularity CDEs 1-158
IAM Timepoint Received_ms (Tag: 4100) 1-158
IAM Timepoint Sent_ms (Tag: 4101) 1-158
ACM Timepoint Received_ms (Tag: 4102) 1-158
ACM Timepoint Sent_ms (Tag: 4103) 1-159
ANM Timepoint Received_ms (Tag: 4104) 1-159
ANM Timepoint Sent_ms (Tag: 4105) 1-159
First REL Timepoint_ms (Tag: 4106) 1-160
Second REL Timepoint _ms (Tag: 4107) 1-160
RLC Timepoint Received_ms (Tag: 4108) 1-160
RLC Timepoint Sent_ms (Tag: 4109) 1-161
Cisco Reserved CDEs 1-162
viii
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Unique Call Correlator ID (Tag: 5000) 1-162
Miscellaneous Fields 1-163
MGC ID (Tag: 6000) 1-163
File Start Time (Tag: 6001) 1-163
File End Time (Tag: 6002) 1-163
Total Number of CDB Records (Tag: 6003) 1-164
MGC Version (Tag: 6004) 1-164
Interim CDB (Tag: 6005) 1-164
Protocol Specific CDEs 1-165
NTT 1-165
TTC Contract Number (Tag: 6100) 1-165
TTC Contract Number NOA (Tag: 6101) 1-165
TTC Charge Info (Tag: 6102) 1-165
TTC Charge Info Type (Tag: 6103) 1-166
TTC Charge Area Info (Tag: 6104) 1-166
Contents
CHAPTER
APPENDIX
I
NDEX
2 MGC Info Field Reference 2-1
MGC Info Subfields 2-1
A CDE Listings by Release A-1
CDE Baseline—Release 9.1(5) and Higher A-1
CDE Changes in Release 9.2(2) A-4
CDE Changes in Release 9.3(1) A-5
CDE Changes in Release 9.3(2) A-5
CDE Changes in Release 9.4(1) A-5
CDE Changes in Release 9.5(2) A-6
CDE Changes in Release 9.6(1) A-7
CDE Changes in Release 9.7 A-8
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
ix
Contents
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
x
OL-1089-11
Preface
This preface includes the following sections:
• Document Objective, page xi
• Audience, page xi
• Document Organization, page xii
• Document Conventions, page xii
• Cisco Media Gateway Controller Documentation Suite, page xv
• Cisco Media Gateway Controller Documentation Map, page xvi
• Obtaining Documentation, Obtaining Support, and Security Guidelines, page xvii
• Summary History of Document Changes, page xvii
Document Objective
This guide provides reference information for the Cisco Media Gateway Controller (MGC) software
Release 9. You should read the system-level documentation supplied with your system before using this
guide. A complete list of these documents is included in the Cisco Media Gateway Controller Software
Release 9 Installation and Configuration Guide that ships with your system.
Note This guide uses the term Media Gateway Controller software or MGC application to mean the
Cisco MGC software that runs in the UNIX environment on a server. The term MGC refers to the
combination of this software and the server. The MGC communicates with the SS7 network to process
and route calls between a traditional time-division multiplexing (TDM) network and a packet data
network. This routing takes place through a variety of media gateways (MGWs), which are separate
devices that perform the conversion between the TDM and data network formats.
Audience
This guide is for network operators and administrators who have experience with telecommunications
networks, protocols, and equipment and who have familiarity with data communications networks,
protocols, and equipment.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
xi
Document Organization
The major sections of this guide are summarized in Tab l e 1.
Table 1 Document Organization
Chapter Title Description
1 Billing Interfaces Describes the Cisco MGC billing interface
2 Info Field Reference Provides additional information about the MGC
Appendix A CDE Listings by
Document Conventions
Release
Preface
capabilities and its call detail records (CDRs).
Info Field (Tag 4031).
Lists the call detail element (CDE) changes made
for each release.
Throughout this guide, $BASEDIR refers to the directory structure in which the Cisco MGC software is
installed. $BASEDIR is a UNIX environment variable that must be set during installation. Refer to the
Cisco MGC Software Release 9 Installation and Configuration Guide for a description of configuring
this environment variable.
Text conventions used in this guide are shown in Tab le 2 .
Table 2 Conventions
Convention Meaning Description/Comments
Boldface Commands and keywords
you enter as shown
Italics Variables for which you
supply values
Square brackets ([ ]) Optional elements command [abc]
Vertical bars ( | ) Separated alternative
elements
Braces ({ }) Required choices command {abc | def}
offset-list
command type interface
You replace the variable with the type
of interface.
In contexts that do not allow italics,
such as online help, arguments are
enclosed in angle brackets (< >).
abc is optional (not required), but you
can choose it.
command [abc | def]
You can choose either abc or def, or
neither, but not both.
xii
Yo u must choose either abc or def, but
not both.
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Preface
Table 2 Conventions (continued)
Convention Meaning Description/Comments
Braces and vertical bars
within square brackets
([ { | } ])
Caret character (^) Control key The key combinations ^D and Ctrl-D
A nonquoted set of
characters
System prompts
Screen font Terminal sessions and
Angle brackets (< >) Nonprinting characters such
Exclamation point (!) at the
beginning of a line
A required choice within an
optional element
command [abc {def | ghi}]
You have three options:
Nothing
abc def
abc ghi
are equivalent: Both mean “hold down
the Control key while you press the D
key.” Keys are indicated in capital
letters, but are not case sensitive.
A string For example, when setting an SNMP
community string to public, do not use
quotation marks around the string;
otherwise, the string will include the
quotation marks.
Denotes interactive
sessions, indicates that the
user enters commands at the
prompt
The system prompt indicates the
current command mode. For example,
the prompt
Router (config) #
indicates global configuration mode.
information the system
displays
as passwords
A comment line Comments are sometimes displayed by
the Cisco IOS software.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Timesaver Means reader may be able to save some time. Taking the action described could achieve a result in less
time than might be achieved otherwise.
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the
manual.
Conventions used in the Cisco MGC system (such as in MML commands) are shown in Tab l e 3.
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
xiii
Table 3 Data Type Conventions
Data Type Definition Example
Integer A series of decimal digits from the set of 0 through 9 that
represents a positive integer. An integer can have one or
more leading zero digits (0) added to the left side to align
the columns. Leading zeros are always valid as long as
the number of digits is less than or equal to ten. Values of
this type have a range of 0 through 4294967295.
Signed
integer
This data type has the same basic format as the integer
but can be either positive or negative. When negative, it
is preceded by the sign character (–). As with the integer
data type, this data type can be as many as ten digits in
length, not including the sign character. The value of this
type has a range of –2147483647 through 2147483647.
Hexadecimal A series of 16-based digits from the set of 0 through 9, a
through f, or A through F. The hexadecimal number can
have one or more leading zeros (0) added to the left side.
For all hexadecimal values, the maximum size is
0xffffffff (eight hexadecimal digits).
Text A series of alphanumeric characters from the ASCII
character set, where defined. Tab, space, and double
quote (“ ”) characters cannot be used. Text can be as many
as 255 characters; however, it is recommended that you
limit the text to no more than 32 characters for
readability.
String A series of alphanumeric characters and white-space
characters. A string is surrounded by double quotes (“ ”).
Strings can be as many as 255 characters; however, it is
recommended that you limit the strings to no more than
80 characters for readability.
123
000123
4200000000
123
–000123
–2100000000l
1f3
01f3000
EntityID
LineSES_Threshold999
“This is a descriptive
string.”
Preface
xiv
Note Hexadecimal and integer fields in files can have different widths (number of characters) for column
alignment.
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Preface
Cisco Media Gateway Controller Documentation Suite
The documents that make up the Cisco MGC documentation set are listed in Tabl e 4.
Table 4 Cisco Media Gateway Controller Documentation Set
Functional Area Document Title Document Description
Hardware Cisco Media Gateway Controller
Hardware Installation Guide
Hardware Regulatory Compliance and Safety
Information for the Cisco Media
Gateway Controller Hardware
Software installation
and configuration
Software installation
and configuration
Software installation
and configuration
Software installation
and configuration
Software installation
and configuration
Software installation
and configuration
Cisco Media Gateway Controller
Software Release 9 Installation and
Configuration Guide
Cisco Media Gateway Controller
Software Release 9 Provisioning
Guide
Cisco Media Gateway Controller
Software Release 9 Dial Plan Guide
Cisco Media Gateway Controller
Software Release 9 Billing Interface
Guide (this book)
Cisco Media Gateway Controller
Software Release 9 Operations,
Maintenance, and Troubleshooting
Guide
Release Notes for Cisco Media
Gateway Controller Software
Release 9
Provides information on how to
install the Cisco SC2200 and
Cisco VSC3000 MGCs
Provides regulatory compliance and
safety information
Provides installation and
configuration information for the
Cisco MGC software Release 9
Provides provisioning information
for the Cisco MGC software
Release 9
Provides dial plan information for the
Cisco MGC software Release 9
Provides reference information for
the Cisco MGC software Release 9
Provides operation, maintenance,
and troubleshooting information for
the Cisco MGC software Release 9
Provides release-specific
information for the Cisco MGC
software Release 9
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
xv
Cisco Media Gateway Controller Documentation Map
Refer to the map in Figure 1 to navigate through the media gateway controller documentation suite.
Figure 1 Documentation Map
Start
Solution Overview
Preface
Is
MGC host
set up?
No
Regulatory Compliance and Safety
Information for Cisco MGC
Cisco MGC Hardware
Installation Guide
Release Notes for
Cisco MGC Software Release 9
Cisco MGC Software Release 9
Installation and Configuration Guide
Cisco MGC Software Release 9
Provisioning Guide
Cisco MGC Software Release 9
Dial Plan Guide
Ye s
Is
gateway
set up?
No
Regulatory Compliance and Safety
Information for Cisco Media Gateway
Solution Gateway Hardware
Installation Guide
Solution Gateway Software
Installation and Configuration Guide
Solution Gateway
Provisioning Guide
End
Cisco MGC Software Release 9
Billing Interface Guide *
Cisco MGC Software Release 9 MML
Command Reference Guide *
Ye s
xvi
Cisco Voice Services Provisioning
Tool Version 2.x
Cisco MGC Software Release 9 Operations,
Maintenance, and Troubleshooting Guide
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
Cisco MGC Software Release 9
Messages Reference Guide *
Cisco MGC Software Release 9
Management Information Base Guide *
* This guide provides useful information
that is not required during installation.
57051
OL-1089-11
Preface
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback,
security guidelines, and also recommended aliases and general Cisco documents, see the monthly
What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical
documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Summary History of Document Changes
Table 5 describes the document changes made after the initial release of the Cisco Media Gateway
Controller Software Release 9 Billing Interface Guide.
Table 5 Summary History of Document Changes
Document Number and Change
Subject
Tag revisioins OL-1089-11, December, 2007
Tag revisions OL-1089-11, October, 2007
Tag revisions OL-1089-11, April 9, 2007
Tag revisions OL-1089-10, March 31, 2006
Tag revisions OL-1089-10, August 5, 2005
Tag revisions OL-1089-09, September 23, 2004
Date Change Summary
• Updated tags in Release 9.6, 9.7
• Added tags 4246, 4247, and 4248
• Modified information for tags 4201
and 4202.
• Added tags 4236, 4238, 4239,
4240, 4242, 4243, 4244, and 4245.
• Modified information for tags 4098
and 4099 for the Support for DSP
Voice Quality Statistics feature.
• Modified information for tags
4078, 4080, and 6000.
• Modified information for tags
4011, 4049, 4050, 4087, 4088,
4215, 4221, and 4223–4225.
• Added tags 2018-2020, 3018-3020,
4227-4233, and 4237.
• Modified definitions for CDBs
1070 and 1071.
• Added CDBs 1210 and 1260
• Added the 1071 CDB.
OL-1089-11
• Added tags 4234 and 4235.
• Removed CDB information from
individual tag tables.
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
xvii
Table 5 Summary History of Document Changes
Document Number and Change
Subject
Tag revisions OL-1089-09, May 17, 2004 • Modified the description of the
Tag revisions OL-1089-08, January 9, 2004
Tag revisions OL-1089-08, December 3, 2003
Tag revisions OL-1089-08, August 18, 2003
Date Change Summary
1060 CDB.
• Retired tag 4045.
• Modified information for tags 4044
and 4073.
• Added tags 4083–4097,
4213–4226, and 6005.
• Restored tags 4046 and 4047.
• Modified the description of the
1060 CDB.
• Reordered the tags, placing them in
numeric order.
• Modified the retirement
information for tag 3004.
• Modified release information for
tags 4052 and 4053. They are now
listed as “defined for future use.”
• Added tags 4098 and 4099, which
are part of a Release 9.4(1) patch.
• Added tags 4204–4212.
Preface
Tag revisions OL-1089-07, June 30, 2003
• Retired tag 4033.
• Added data value information for
tags 4030 and 4044.
• Modified the release in which the
3004 tag was retired.
xviii
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Preface
Table 5 Summary History of Document Changes
Document Number and Change
Subject
Tag revisions OL-1089-07, June 27, 2003 • Modified CDB information for tag
Tag revisions OL-1089-07, March 14, 2003
Date Change Summary
4081.
• Modified descriptions for the
following tags:
–
2006, 2009, 2010, and 2014
–
2017, 3001, 3002, and 3006
–
3009, 3010, 4048, and 4060
• Modified data values for the
following tags:
–
2011, 2012, 2014, and 2016
–
4013 and 4038—4040
–
4066—4068 and 4070—4072
–
4074—4077, 6000, and 6004
• Modified information and data
values for tags 6100—6104.
• Modified information for tags
2005, 2007, 3007, and 4014.
Tag revisions OL-1089-07, January 20, 2003
Tag revisions OL-1089-07, December 9, 2002
Tag revisions OL-1089-06, October 9, 2002
Tag revisions OL-1089-06, September 19, 2002
Tag revision OL-1089-06, September 5, 2002
Tag revisions OL-1089-06, August 20, 2002
• Added tags 4034–4037, 4068, and
4072 to the 1110 CBD.
• Corrected the octet length
information for tags 3011, 3012,
4032, and 4033.
• Added an appendix that identifies
the CDR changes by release.
• Updated the information for tag
3013.
• Changed the CDB information for
tag 4081.
• Added CDE and CDB information
for tag 4082.
• Expanded data value content of the
3008 tag to include detailed cause
code information.
• Corrected data value information
for tags 4032 and 4033.
• Corrected the data value
information for tag 4048.
• Corrected CDB information for
tags 3001, 4078, 4079, and 4080.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
xix
Preface
Table 5 Summary History of Document Changes
Document Number and Change
Subject
Tag revisions OL-1089-06, August 16, 2002 • Added data value information to
Tag revisions OL-1089-06, July 10, 2002
New template OL-1089-06, July 1, 2002
Tag revisions OL-1089-06, July 1, 2002
Date Change Summary
the 3000 series tags from Q.763.
• Identified tags 3002, 3004, 4046,
and 4047 as retired.
• Corrected the CBD information for
tags 4052 and 4053.
• Corrected descriptions for tags
4066–4068, 4070–4072, and
4074–4076.
• Modified the data value
information for the 4100 series tags
to indicate Cisco MGC time.
• Modified the data value
information for ANSI Nature of
Address tags to indicate that the
first value is spare.
• Modified tags to indicate that the
maximum ANSI number is 2
• Updated CDB values for tags 4078,
4079, and 4081.
• Updated CDB values for tags 4077
and 4080.
• Updated this document with the
current user documentation
template.
• Removed Tag 5000 from the
listings for CDBs 1090 and 1100.
14
.
xx
Tag revisions OL-1089-06, May 15, 2002
Revised Table 1-2 OL-1089-05, April 3, 2002
Tag revisions OL-1089-04, March 22, 2002
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
• Replaced Tag 6001 in CDB 1100
with Tag 6002.
• Added MGCP as a valid interface
in Tags 4069 and 4073.
• Added Tags 4078 through 4081.
• Removed references to Tags 4064
and 4065.
• Revised data value and general
information for Tags 4034 through
4037.
OL-1089-11
Preface
Table 5 Summary History of Document Changes
Document Number and Change
Subject
Tag revisions OL-1089-03, November 27, 2001 • Revised text for last bullet on
ASCII output OL-1089-02, November 16, 2001
— OL-1089-01, October 18, 2001 Initial release
Date Change Summary
page 1-7 and on page 1-8.
• Removed “(retired in Release
9.0(1))” for Tag 2017 and
Tag 3017.
• Added Tag 4203.
• Removed Tag 4064 and Tag 4065.
• Removed references to ASCII
output on page 1-2 to page 1-4.
• Removed Table 1-1 on page 1-11.
• Removed CdrDmpr.callDetail row
in Table 1-6 on page 1-11.
• Removed Trigger Interface section
on page 1-18.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
xxi
Preface
xxii
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Billing Interfaces
This chapter describes the Cisco Media Gateway Controller (MGC) billing interface capabilities and its
call detail records (CDRs). This chapter is primarily a reference that contains the following sections:
• Billing Capabilities Overview, page 1-1
• Cisco MGC Billing Interfaces, page 1-19
Billing Capabilities Overview
The generic interface to the CDR dumper interface carries all the billing information in the form of call
detail blocks (CDBs). When the CDR dumper receives the CDB, it writes the record in the CDR file.
CDB generation is based on a point in call (PIC). The MGC predefines several PICs that can trigger the
generation of CDBs. Examples of PICs include Answered, Long Duration, and Released. For example,
the MGC triggers the generation of the Answered CDB when an Answer message (ANM for SS7) is
received.
Each CDB has a type associated with it that distinguishes the PIC.
CDB required events that are triggered are passed to the CDR manager module. When an event is
received, the action the CDR manager module takes is determined by its configuration. The CDR
manager module either handles or ignores the event.
CHAPTER
1
System Interfaces
System interfaces vary according to the configuration. The configuration can be either dual MGC
(hot-standby) or standalone. The physical interface is described in the following section.
Physical Interface
The physical interface between the MGC and the mediation software (for example, Billing and
Measurements Server (BAMS)) relies on guaranteed delivery of the CDB information between both
MGCs. The interface consists of dual Ethernet links. Each link is physically isolated for redundancy.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-1
Billing Capabilities Overview
RADIUS Interface
Message Interface
Chapter 1 Billing Interfaces
The RADIUS Enhancement for Accounting feature provides RADIUS interface support on the PGW
2200 for CDR data. For more information about the feature, including new CDRs, refer to the RADIUS
Enhancement for Accounting feature guide.
The CDB message interface is a one-way interface to the CDR dumper. The following paragraphs
describe the CDR message format for messages sent to the CDR dumper. The CDR dumper saves the
CDB message into the CDR files without any conversion or data manipulation.
CDBs are written to disk in a binary, tag-length-value (TLV) format. Many mediation systems depend
on input data that is preformatted in an ASCII format. An optional BAMS converts the MGC CDR billing
output files to ASCII.
The accuracy selection for timepoints is configurable on the MGC as seconds or milliseconds. In order
for the ASCII representation of timepoints to be properly displayed, a place holder for each type has been
provided in the ASCII output layout. For each timepoint type, two entries are contained in the output
format, one entry for seconds granularity and another entry for milliseconds granularity.
A downstream mediation or billing system (for example, BAMS) can easily parse these ASCII records.
Each record is prefixed in the ASCII file with a record identifier field, for example a 1110 record would
begin as follows: 1110,1234,5678,2222,...
The ASCII files are named with the same prefix name specified (refer to page 1-20 for a prefix example),
and postfixed with “.csv” rather than “.bin”. Each file resides in the /opt/CiscoMGC/var/bam directory.
Note It is the system operator's responsibility to manage files created by the MGC billing process, including
archiving and deleting files from the system.
CDB Message Format
The format of CDB messages being sent to the CDR dumper is based on tag, length, and value (TLV).
Each field within the CDB message has a tag, length, and value.
Figure 1-1 shows how the CDB record itself is also in TLV format with the value part composed of
multiple sub-TLVs. For performance reasons the first few fields(tags) of the value portion of the CDB
exists in a fixed order for every message. These fields are the Unique Call ID (tag 5000), CDB Version
(tag 4000), and CDB Timepoint (tag 4001).
Note These three fields are fixed so that the CDR dumper can have direct access to these fields without having
to parse or search through all the CDB message TLV fields.
As shown in Figure 1-1, the first tag in the CDB record identifies the CDB message type. The length
indicates the length of the entire message, excluding 4 bytes (2 bytes for the message tag and 2 bytes for
the length).
1-2
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Figure 1-1 CDB TLV Record Format
Billing Capabilities Overview
Ta g Length
Ta g Length
Value
57859
Sub-TLV messages
The CDB message has both mandatory fields and optional fields. The following fields are mandatory in
each CDB message.
• Unique Call ID
• Ve rs i on
• CDB Timestamp
All other fields in the CDB message are considered optional. The optional fields do not appear in any
sort of predefined order. The TLV format allows the application to be insensitive to the order of the
message data. For example, in a 1010 Answer CDB message, the Call Reference ID tag (4002) could
appear as the first optional field, whereas in another CDB message, such as 1040 Release, the Call
Reference ID tag could appear as the last optional field.
Note The mandatory fields exist in each CDB message, with their associated values and locations. The
optional fields can have no value. Optional fields with no value are not included in the CDB message, to
improve performance.
Tag Values
As shown in Figure 1-2, the tags are divided into categories. The first tag category is assigned to the CDB
message ID(s), the second category is assigned to CDB format fields, and the third category is assigned
to miscellaneous usage.
Each category is divided into two or more sections. One section is the MGC range, and another section
is the customer-defined range. Customer-defined ranges (for each category) can be used to further
process the CDB records as required by the customer.
For example, in Figure 1-2, a Cisco MGC message ID range defined by a customer (1900 through 1999)
can be used for generating customer-specific CDB auditing records. The auditing records can be for
beginning and ending the CDR file. The field tag range can also use the customer-defined range for the
field category (5900 through 5999) to define new fields in the CDB auditing records.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-3
Billing Capabilities Overview
Figure 1-2 CDB Tag Categories
MGC message IDs
Chapter 1 Billing Interfaces
1000
Formats and Codes
Customer defined
MGC ANSI format
MGC ITU format
MGC generic format
Reserved
Customer defined
MGC miscellaneous
Reserved
Customer defined
1900
1999
2999
3999
4999
5900
5999
6999
7900
7999
CDB message ID tag category
CDB fields tag category
Miscellaneous tag category
57860
Note The length indicator value does not include the field tag octets (2 octets) or the length indicator octets
CDB Record Types
The CDB message tag and the length fields are binary encoded using big-endian (BE). The tag field
holds the value to identify the CDB field, and the length field holds the number of octets (length) of the
CDB field.
(2 octets).
The CDB field value is encoded as specified BE, International Alphabet No. 5 (IA5), ANSI T1.113, or
ITU Q.763).
This section describes different types of CDBs and their relation to PIC events. Creation of the CDB is
based on certain PIC events (refer to Tab le 1 - 1 ), and other call events.
1-4
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Billing Capabilities Overview
Ta b le 1- 1 CD B Typ e s
CDB Tag
Point in Call Event Description
Answer call event Call went through and was answered. 1010 Set CDB record
Deselected outgoing
Circuit cannot be used, passed to another. 1020 Deselected outgoing circuit
circuit event
Aborted attempt call event Call did not get to setup status. 1030 Aborted attempt CDB record
Release call event Released call. 1040 Release CDB record
Interrupted call event Call terminating without release message. 1050 Interrupted CDB record
On-going call event Long call. 1060 On-going call CDB record
Maintenance CDB record Circuit maintenance. 1070 Maintenance CDB record
N/A Sent as a result of a Cisco MGC audit or a change in
circuit counts via the sta-aud-cic MML command.
External access CDB Call sent a query to a Service Control Point (SCP) (or
to another external device or database).
File header CDB CDR dumper creates the file header CDB at the
beginning of each CDR file.
File footer CDB CDR dumper creates the file footer CDB at the end of
each CDR file.
End of a call CDB This CDB is generated when the MGC is configured
to have one CDB per call.
It is generated at the end of the call (as in Release
CDB) or when the call did not get to setup status (as
in Aborted attempt CDB).
Note If the Cisco MGC is configured for 1110
output, the 1010, 1030, and 1040 CDBs must
not be configured for inclusion in the output
billing files.
Half call slave release
event CDB
Half call slave ongoing
call event CDB
Refer to the 1110 CDB definition and apply to a
non-controlling slave half call instance.
Refer to th 1060 CDB definition and apply to a
non-controlling slave half call instance.
Value CDB Message/Record
CDB record
1071 SS7 CIC Audit CDB record
1080 External access CDB record
1090 File header CDB record
1100 File footer CDB record
1110 End of a Call CDB
1210 Slave End of a Call CDB
1260 Slave Long Duration Call
CDB
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-5
Chapter 1 Billing Interfaces
Call Data Block Descriptions
Call Data Block Descriptions
The CDB consists of several call data elements (CDEs) that are related to a certain point in call (PIC).
Each CDE has a tag, a length, and a value. Tab le 1 -2 defines the CDE fields in a CDB.
Table 1-2 CDB Call Data Element Fields for Current Release
CDE Tag Numbers
CDB Name CDB Tag
Common
Answered 1010 4000–4005, 4008–4016, 4029,
4034–4043, 4048, 4060, 4063,
4066–4073, 4080, 4081,
4083–4086, 4089, 4090,
4092–4096, 4201–4207,
4209–4212, 4236, 4237,
4240–4243, 5000
Deselected 1020 4000–4003, 4006, 4008, 4009,
4015, 4016, 4019, 4020, 4028,
4034–4037, 4081, 4232, 4233,
5000
Aborted 1030 4000–4004, 4006, 4008–4016,
4019, 4020, 4028, 4029,
4034–4039, 4046–4048,
4060–4062, 4065–4073,
4078–4080, 4082–4096, 4098,
4099, 4201–4212, 4232, 4233,
4236, 4237, 4239, 4240–4245,
4246, 5000
Release 1040 4000–4002, 4006, 4019, 4020,
4028, 4030, 4044, 4046, 4047,
4061, 4062, 4078, 4079,
4082–4091, 4095–4099,
4205–4210, 4213, 4214,
4227–4231, 4239, 4240, 4241,
5000
Interrupted 1050 4000–4002, 4007, 4081, 5000
Ongoing 1060 4000–4005, 4008–4010, 4012,
4014–4016, 4066–4073, 4080,
4081, 4213, 4214, 4237, 5000
Maintenance 1070 4000–4002, 4017, 4018, 4032,
4074–4077, 4081, 5000
SS7 CIC Audit 1071 4000–4002, 4017, 4074, 4081,
5000
External DB 1080 4000–4002, 4040– 4043, 4234,
4235, 5000
File Header
1090 4000–4002 6000, 6001,
CDB
Millisecond
Granularity
4100–4105 2000, 2001,
ANSI
2003–2007,
2009–2020
ITU
3000, 3001,
3003,
3005–3007,
3009–3013,
3017–3020
4100, 4101,
2008–2012 3008–3012 6100–6104
4106, 4108,
4109
4100–4103,
4106–4109,
2000, 2001,
2003–2009,
2011–2020
3000, 3001,
3003,
3005–3009,
3011, 3013,
3017–3020
4106–4109, 2008 3008
4100–4105, 2018–2020 3017–3020
Miscellaneous/
Protocol Specific
6100–6104
6100–6104
6004
1-6
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-2 CDB Call Data Element Fields for Current Release (continued)
CDE Tag Numbers
CDB Name CDB Tag
File Footer
1100 4000–4002 6000, 6002,
Common
CDB
End of Call 1110 4000–4002, 4008–4012,
4014–4016, 4028, 4034–4037,
4046, 4047, 4060–4063, 4065,
4068, 4072, 4078–4080,
4082–4099, 4201–4212, 4213,
4214, 4227–4231, 4232, 4233,
4236, 4237, 4239, 4240–4245,
4246, 5000
Slave End of
Call
Slave Long
Duration Call
1210 4002, 4003, 4006, 4008, 4009,
4015, 4016, 4227, 4228, 5000
1260 4002, 4003, 4006, 4008, 4009,
4015, 4016, 4227, 4228, 5000
Millisecond
Granularity
4100–4109, 2000–2005,
Call Data Block Descriptions
ANSI
ITU
Miscellaneous/
Protocol Specific
6003, 6004
2007, 2008,
2013, 2015,
2017–2020
3000, 3001,
3003, 3005,
3007, 3008,
3017–3020
Enabling Call Screening
To initialize the database that stores call screening information, modify the SysConnectDataAccess
parameter in the Engine section of the XECfgParm.dat file: For parameter modification, enter
SysConnectDataAccess.
Note Making changes to the XECfgParm.dat file requires the system software to be stopped, the parameter
value changed, and the software restarted. Contact Cisco TAC before stopping the system software.
To enable or disable the A-number and B-number analysis in the call screening database, enter one of
the following values:
• If you do not have the database environment set with all the required data populated, set this value
to false (default).
• If you have the database and want the system to access it, set this value to true.
Configuring Call Detail Record File Output
To configure the CDR file output, modify the following parameters in the Data Dumper and Engine
sections of the XECfgParm.dat file:
Parameter modification: engine.CDRencodingFormat
To specify the CDR file encoding format, enter one of the following values:
• AnsiCDB-North American (default)
OL-1089-11
• ItuCDB-European
Parameter modification: engine.CDRtimeStamp
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-7
Call Data Block Descriptions
To specify the CDR file timestamp unit, enter one of the following values:
• S-Seconds (default).
• M-Milliseconds; use this parameter if your configuration uses TCAP.
Note If you use 1110 in the engine.CDRmessageTypes parameter (for TCAP), you must specify milliseconds
for the CDRtimeStamp value.
Note The timestamp value is in Coordinated Universal Time (UTC). Previously the term used was Greenwich
Mean Time (GMT).
Configuring Call Detail Record Message Types
Parameter modification: engine.CDRmessageTypes
To specify which CDBs (statistics taken at various points in a call) are recorded during a call, enter one
of the two following sets of values (each number represents a point in a call):
• 1010, 1020, 1030, 1040, 1050, 1060, 1070, 1080—Use this set of values if your CDR files are used
by a measurement server or by another CDR reader.
Chapter 1 Billing Interfaces
• 1060, 1110—Use this set of values if the end-of-call record is desired.
• 1071—Use this set of values for BAMS measurements.
Enabling Call Screening
To initialize the database that stores call screening information, modify the parameters shown in
Table 1-3.
Table 1-3 Call Screening Parameters
Parameter Modification
engine.SysConnectDataAccess To enable or disable the A-number and B-number analysis in
the call screening database, enter one of the following values:
• If you do not have the database environment set with all
• If you have the database and want the system to access it,
Configuring Call Detail Record File Output
the required data populated, set this value to false
(default).
set this value to true.
1-8
To configure the CDR file output, modify the parameters shown in Table 1-4 in the Data Dumper and
Engine sections of the XECfgParm.dat file:
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Loading...