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.
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
Cisco Media Gateway Controller Documentation Suitexv
Cisco Media Gateway Controller Documentation Mapxvi
Obtaining Documentation, Obtaining Support, and Security Guidelinesxvii
Summary History of Document Changesxvii
CHAPTER
1Billing Interfaces1-1
Billing Capabilities Overview1-1
System Interfaces1-1
Physical Interface1-1
RADIUS Interface1-2
Message Interface1-2
CDB Message Format1-2
Tag Values1-3
Formats and Codes1-4
CDB Record Types1-4
Call Data Block Descriptions1-6
Enabling Call Screening1-7
Configuring Call Detail Record File Output1-7
Configuring Call Detail Record Message Types1-8
Enabling Call Screening1-8
Configuring Call Detail Record File Output1-8
Call Data Element Descriptions1-9
Cisco MGC Billing Interfaces1-19
FTP Interface1-20
Generic Interface1-20
OL-1089-11
Redundant Cisco MGC Configuration1-20
Cisco MGC Clock Synchronization1-21
Detailed CDB Description1-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 Description1-48
CDEs Encoded in ANSI1-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 Recommendation1-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) Retired1-70
Calling Number Nature of Address (Tag: 3003/ITU)1-70
Charged Number Nature of Address (Tag: 3004/ITU) Retired1-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 CDEs1-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)—Retired1-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) Retired1-112
Ingress Packet Info (Tag: 4046) Restored1-113
Egress Packet Info (Tag: 4047) Restored1-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 Use1-116
Terminating Gateway Primary Select (Tag: 4053) Defined for Future Use1-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
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
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Unique Call Correlator ID (Tag: 5000)1-162
Miscellaneous Fields1-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 CDEs1-165
NTT1-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
2MGC Info Field Reference2-1
MGC Info Subfields2-1
ACDE Listings by ReleaseA-1
CDE Baseline—Release 9.1(5) and HigherA-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.7A-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.
NoteThis 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 1Document Organization
ChapterTitleDescription
1Billing InterfacesDescribes the Cisco MGC billing interface
2Info Field ReferenceProvides additional information about the MGC
Appendix ACDE 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 .
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 2Conventions (continued)
ConventionMeaningDescription/Comments
Braces and vertical bars
within square brackets
([ { | } ])
Caret character (^)Control keyThe key combinations ^D and Ctrl-D
A nonquoted set of
characters
System prompts
Screen fontTerminal 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 stringFor 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 lineComments are sometimes displayed by
the Cisco IOS software.
CautionMeans reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
TimesaverMeans reader may be able to save some time. Taking the action described could achieve a result in less
time than might be achieved otherwise.
NoteMeans 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 3Data Type Conventions
Data TypeDefinitionExample
IntegerA 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).
TextA 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.
StringA 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
NoteHexadecimal 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 4Cisco Media Gateway Controller Documentation Set
Functional AreaDocument TitleDocument Description
HardwareCisco Media Gateway Controller
Hardware Installation Guide
HardwareRegulatory 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 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 1Documentation 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:
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 5Summary History of Document Changes
Document Number and Change
Subject
Tag revisionsOL-1089-09, May 17, 2004 • Modified the description of the
Tag revisionsOL-1089-08, January 9, 2004
Tag revisionsOL-1089-08, December 3, 2003
Tag revisionsOL-1089-08, August 18, 2003
DateChange 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 revisionsOL-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 5Summary History of Document Changes
Document Number and Change
Subject
Tag revisionsOL-1089-07, June 27, 2003 • Modified CDB information for tag
Tag revisionsOL-1089-07, March 14, 2003
DateChange 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 revisionsOL-1089-07, January 20, 2003
Tag revisionsOL-1089-07, December 9, 2002
Tag revisionsOL-1089-06, October 9, 2002
Tag revisionsOL-1089-06, September 19, 2002
Tag revisionOL-1089-06, September 5, 2002
Tag revisionsOL-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 5Summary History of Document Changes
Document Number and Change
Subject
Tag revisionsOL-1089-06, August 16, 2002 • Added data value information to
Tag revisionsOL-1089-06, July 10, 2002
New templateOL-1089-06, July 1, 2002
Tag revisionsOL-1089-06, July 1, 2002
DateChange 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 revisionsOL-1089-06, May 15, 2002
Revised Table 1-2OL-1089-05, April 3, 2002
Tag revisionsOL-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 5Summary History of Document Changes
Document Number and Change
Subject
Tag revisionsOL-1089-03, November 27, 2001 • Revised text for last bullet on
ASCII output OL-1089-02, November 16, 2001
—OL-1089-01, October 18, 2001Initial release
DateChange 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 theRADIUS
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.
NoteIt 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).
NoteThese 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-1CDB TLV Record Format
Billing Capabilities Overview
Ta gLength
Ta gLength
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.
NoteThe 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-2CDB 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
NoteThe 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- 1CD B Typ e s
CDB Tag
Point in Call EventDescription
Answer call eventCall went through and was answered.1010Set CDB record
Deselected outgoing
Circuit cannot be used, passed to another.1020Deselected outgoing circuit
circuit event
Aborted attempt call event Call did not get to setup status.1030Aborted attempt CDB record
Release call eventReleased call.1040Release CDB record
Interrupted call eventCall terminating without release message.1050Interrupted CDB record
On-going call eventLong call.1060On-going call CDB record
Maintenance CDB recordCircuit maintenance.1070Maintenance CDB record
N/ASent as a result of a Cisco MGC audit or a change in
circuit counts via the sta-aud-cic MML command.
External access CDBCall sent a query to a Service Control Point (SCP) (or
to another external device or database).
File header CDBCDR dumper creates the file header CDB at the
beginning of each CDR file.
File footer CDBCDR dumper creates the file footer CDB at the end of
each CDR file.
End of a call CDBThis 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).
NoteIf 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.
ValueCDB Message/Record
CDB record
1071SS7 CIC Audit CDB record
1080External access CDB record
1090File header CDB record
1100File footer CDB record
1110End of a Call CDB
1210Slave End of a Call CDB
1260Slave 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-2CDB Call Data Element Fields for Current Release
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.
NoteMaking 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.
NoteIf you use 1110 in the engine.CDRmessageTypes parameter (for TCAP), you must specify milliseconds
for the CDRtimeStamp value.
NoteThe 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-3Call Screening Parameters
ParameterModification
engine.SysConnectDataAccessTo 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
Chapter 1 Billing Interfaces
Table 1-4Call Detail Record File Output Parameters
ParameterModification
engine.CDRencodingFormatTo specify the call detail record (CDR) file encoding format,
engine.CDRmessageTypesTo specify which call detail blocks (CDBs, statistics taken at
engine.CDRtimeStampTo specify the CDR file time-stamp unit, enter one of the
Call Data Element Descriptions
enter one of the following values:
• AnsiCDB—North American (default)
• ItuCDB—European
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):
this set of values if your CDR files are to be read by a
measurement server or other CDR reader.
• 1060, 1110—Use this set of values if the end-of-call
record is desired.
• 1071—Use this set of values for BAMS measurements.
following values:
cdrDmpr.openCDRTo indicate whether the standard data dumper writes out CDR
cdrDmpr.seqFileIndicate the location of the file for storing or retrieving the
Call Data Element Descriptions
This section describes the current CDB CDEs. The CDEs are divided into three tables (ANSI, ITU, and
generic format).
The ANSI formatted fields are used for customers requesting ANSI-formatted fields (as is the case for
North American customers) and is based on ANSI T1.113.1995.
• S—Seconds (default).
• M—Milliseconds; use this parameter if your
configuration uses TCAP or BAMS.
NoteIf you use are using BAMS or 1110 in the
engine.CDRmessageTypes parameter (for TCAP),
you must specify milliseconds (M) for the
CDRtimeStamp value.
files, enter one of the following values:
• true—Standard data dumper opens a CDR file and logs
call detail blocks (CDBs).
• false—Standard data dumper does not open a CDR file
and does not log CDBs.
CDR sequence number (range is 1 to 999999).
Default: ../var/.cdr.seq
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-9
Call Data Element Descriptions
The ITU formatted fields are used for customers requesting ITU-formatted-fields (as is the case for
European customers) and is based on ITU-Q.763.
The generic format provides common CDEs with one encoding scheme. The generic format is used to
handle different protocol variants.
Table 1-5 defines all the fields that can exist in any given CDB along with the associated tag and type
for each one.
Table 1-5CDE Detail Description for the Current Release
Chapter 1 Billing Interfaces
Field Name
Tag
Value
Answered
(1010)
Deselected
(1020)
Aborted
(1030)
Release
(1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External
DB
(1080)
End of
Call
(1110)
ANSI Based Formatted Fields
Calling Party
2000YNYNNNNNYN
Category
User Service
2001YNYNNNNNYN
Information
Originating Line
2002YNYNNNNNNN
Information
Calling Number
2003YNYNNNNNYN
Nature of Address
Charged Number
2004YNYNNNNNYN
Nature of Address
Dialed Number
2005YNYNNNNNYN
Nature of Address
LRN Nature of
2006YNYNNNNNNN
Address
Called Number
2007YNYNNNNNYN
Nature of Address
Reason Code2008NYYYNNNNYN
Forward Call
2009YYYNNNNNNN
Indicators
Received
Forward Call
2010YYNNNNNNNN
Indicators Sent
Nature of
2011YYYNNNNNNN
Connection
Indicators
Received
Nature of
2012YYYNNNNNNN
Connection
Indicators Sent
Transit Network
2013YNYNNNNNYN
Selection
1071
1210
1260
1-10
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-5CDE Detail Description for the Current Release (continued)
Call Data Element Descriptions
Tag
Field Name
Carrier
Value
2014YNYNNNNNNN
Identification
Parameter
Carrier Selection
2015YNYNNNNNYN
Parameter
Jurisdiction
2016YNYNNNNNNN
Information
Parameter
Redirecting
2017YNYNNNNNYN
Number NOA
Egress Calling
2018YNYNNYNNYN
Number NOA
Egress Redirecting
2019YNYNNYNNYN
Number NOA
Egress Original
2020YNYNNYNNYN
Called Number
NOA
ITU Based Formatted Fields
Answered
(1010)
Deselected
(1020)
Aborted
(1030)
Release
(1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External
DB
(1080)
End of
Call
(1110)
1071
1210
1260
Calling Party
3000YNYNNNNNYN
Category
User Service
3001YNYNNNNNYN
Information
Calling Number
3003YNYNNNNNYN
Nature of Address
Dialed Number
3005YNYNNNNNYN
Nature of Address
LRN Nature of
3006YNYNNNNNNN
Address
Called Number
3007YNYNNNNNYN
Nature of Address
Reason Code3008NYYYNNNNYN
Forward Call
3009YYYNNNNNNN
Indicators
Received
Forward Call
3010YYNNNNNNNN
Indicators Sent
Nature of
3011YYYNNNNNNN
Connection
Indicators
Received
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-11
Call Data Element Descriptions
Table 1-5CDE Detail Description for the Current Release (continued)
Member
Calling Number4010YNYNNYNNY
Charged Number4011YNYNNNNNY
Dialed Number4012YNYNNYNNY
LRN Number4013YNYNNNNNN
Called Number4014YNYNNYNNY
Terminating Trunk
4015YYYNNYNNY
Group
Terminating
4016YYYNNYNNY
Member
N
N
1210
N
1210
1260
1210
1260
N
N
N
N
N
1210
1260
1210
1260
1-12
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-5CDE Detail Description for the Current Release (continued)
Call Data Element Descriptions
Field Name
Tag
Value
Answered
(1010)
Deselected
(1020)
Aborted
(1030)
Release
(1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External
DB
(1080)
End of
Call
(1110)
1071
1210
1260
Maint Trunk Group 4017NNNNNNYNN1071
Maint Circuit
4018NNNNNNYNNN
Member
Glare Encountered 4019NYYYNNNNNN
RLC Release
4020NYYYNNNNNN
Timepoint
First Release
4028NYYYNNNNYN
Source
LNP Dip4029YNYNNNNNNN
Total Meter Pulses 4030NNNYNNNNNN
Maint Type4032NNNNNNYNNN
Maint Reason
4033NNNNNNYNNN
(Retired in Release
9.4(1))
Ingress
Originating Point
Code
Ingress
Destination Point
Code
Egress
Originating Point
Code
Egress
Destination Point
Code
Ingress Media
4034YYYNNNNNY (9.3
and
up)
4035YYYNNNNNY (9.3
and
up)
4036YYYNNNNNY (9.3
and
up)
4037YYYNNNNNY (9.3
and
up)
4038YYYNNNNNNN
N
N
N
N
Gateway ID
Egress Media
4039YYYNNNNNNN
Gateway ID
TCAP
4040YNNNNNNYNN
Transaction
Identification
Transaction Start
4041YNNNNNNYNN
Time
Transaction End
4042YNNNNNNYNN
Time
TCAP Database
4043YNNNNNNYN N
Identification
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-13
Call Data Element Descriptions
Table 1-5CDE Detail Description for the Current Release (continued)
Chapter 1 Billing Interfaces
Field Name
Announcement
AnsTag
Value
wered
(1010)
4044NNNYNNNNNN
Deselected
(1020)
Aborted
(1030)
Release
(1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External
DB
(1080)
End of
Call
(1110)
Identification
Ingress Gateway
4046NNYYNNNNYN
Packet Info
Egress Gateway
4047NNYYNNNNYN
Packet Info
Directional Flag4048YNYNNNNNNN
Service Logic ID4049NNNNNNNYN N
AMA Line
4050NNNNNNNYNN
Number
Originating
4052NNNNNNNNNN
Gateway
Primary Select
Terminating
4053NNNNNNNNNN
Gateway
Primary Select
Redirecting
4060YNYNNNNNYN
Number
Tariff Rate4061NNYYNNNNYN
Scale Factor4062NNYYNNNNYN
Test Line Indicator 4063YNYNNNNNYN
Redirection
4065NNYNNNNNYN
Number
Ingress SigPath ID 4066YNYNNYNNNN
Ingress Span ID4067YNYNNYNNNN
Ingress BearChan ID4068YNYNNYNNY (9.3
and
up)
Ingress Protocol ID4069YNYNNYNNNN
1071
1210
1260
N
Egress SigPath ID4070YNYNNYNNNN
Egress Span ID4071YNYNNYNNNN
Egress BearChan ID4072YNYNNYNNY (9.3
and
up)
Egress Protocol ID 4073YNYNNYNNNN
Maintenance
4074NNNNNNYNN1071
SigPath ID
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-14
OL-1089-11
N
Chapter 1 Billing Interfaces
Table 1-5CDE Detail Description for the Current Release (continued)
Call Data Element Descriptions
Field Name
Tag
Value
Answered
(1010)
Deselected
(1020)
Aborted
(1030)
Release
(1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External
DB
(1080)
End of
Call
(1110)
Maintenance Span ID4075NNNNNNYNNN
Maintenance
4076NNNNNNYNNN
BearChan ID
Maintenance
4077NNNNNNYNNN
Circuits Count
Charge Band
4078NNYYNNNNYN
Number
Furnish Charging
4079NNYYNNNNYN
Information
Original Called
4080YNYNNYNNYN
Number
T.38 Fax Call4081YYNNYYYYNN
Charge Unit
4082NNYYNNNNYN
Number
Charge Indicator4083YNYYNNNNYN
Outgoing Calling
4084YNYYNNNNYN
Party Number
MCID Request
4085YNYYNNNNYN
Indicator
MCID Response
4086YNYYNNNNYN
Indicator
Ingress MGCP
4087NNYYNNNNYN
DLCX Return
Code
Egress MGCP
4088NNYYNNNNYN
DLCX Return
Code
Network
4089YNYYNNNNYN
Translated
Address Indicator
Reservation
4090YNYYNNNNYN
Request Accepted
Reservation
4091NNYYNNNNYN
Request Error
Count
ATM Ingress
4092YNYNNNNNYN
Configured Profile
ATM Egress
4093YNYNNNNNYN
Configured Profile
1071
1210
1260
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-15
Call Data Element Descriptions
Table 1-5CDE Detail Description for the Current Release (continued)
Chapter 1 Billing Interfaces
Field Name
ATM Negotiated
AnsTag
Value
wered
(1010)
4094YNYNNNNNYN
Deselected
(1020)
Aborted
(1030)
Release
(1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External
DB
(1080)
End of
Call
(1110)
Profiler
Route List Name4095YNYYNNNNYN
Route Name4096YNYYNNNNYN
MGCP Script
4097NNNYNNNNYN
Response String
Originating Leg
4098NNYYNNNNYN
DSP statistics (9.4
and up)
Terminating Leg
4099NNYYNNNNYN
DSP statistics (9.4
and up)
Originating
4201YNYNNNNNYN
Remote SIP Host
Originating Local
4202YNYNNNNNYN
SIP Host
SIP Call ID4203YNYNNNNNYN
Source IP Address 4204YNYNNNNNYN
Ingress Media
4205YNYYNNNNYN
Device Address
Egress Media
4206YNYYNNNNYN
Device Address
Initial Codec4207YNYYNNNNYN
Final Codec4208NNYYNNNNYN
Ingress Media
4209YNYYNNNNYN
Device Port
Egress Media
4210YNYYNNNNYN
Device Port
Originating VPN ID4211YNYNNNNNYN
1071
1210
1260
Terminating VPN ID4212YNYNNNNNYN
Meter Pulses
4213NNNYNYNNYN
Received
Meter Pulses Sent4214NNNYNYNNYN
Charge Tariff Info 4215NNNYNNNNYN
Advice of Charge
4216NNNYNNNNYN
Indicator
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-16
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-5CDE Detail Description for the Current Release (continued)
Call Data Element Descriptions
Field Name
Short Call
AnsTag
Value
wered
(1010)
4217NNNYNNNNYN
Deselected
(1020)
Aborted
(1030)
Release
(1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External
DB
(1080)
End of
Call
(1110)
Indicator
Charge Limit
4218NNNYNNNNYN
Exceeded
Call Recovered
4219NNNYNNNNYN
Indication
Partial Calling
4220YNYNNYNNYN
Line Identity
Service Activation 4221NNNYNNNNYN
PRI AOC Invoke
4222NNYYNNNNYN
Type
PRI AOC – S
4223NNYYNNNNYN
Charge
Information
PRI AOC – D
4224NNYYNNNNYN
Charge
Information
PRI AOC – E
4225NNYYNNNNYN
Charge
Information
PRI AOC Invoke
4226NNYYNNNNYN
Failure
RO/PR Executed
4227NNNYNNNNY1210
(added in 9.6)
RO/PR Other Call
4228NNNYNNNNY1210
Ref (added 9.6)
RO/PR Trunk
4229NNNYNNNNYN
Group Info
(added in 9.6)
RO/PR
4230NNNYNNNNYN
Replacement Chan
ID
(added in 9.6)
RO Switchover
4231NNNYNNNNYN
Timestamp
(added in 9.6)
Rejecting Location
4232NYYNNNNNYN
Label
(added in 9.6(1))
1071
1210
1260
1260
1260
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-17
Call Data Element Descriptions
Table 1-5CDE Detail Description for the Current Release (continued)
Chapter 1 Billing Interfaces
Field Name
Rejecting Location
AnsTag
Value
wered
(1010)
4233NYYNNNNNYN
Deselected
(1020)
Aborted
(1030)
Release
(1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External
DB
(1080)
End of
Call
(1110)
Label Direction
(added in 9.6(1))
PRI AOC – E
4234NNNYNNNNN1071
Charge
Information
PRI AOC Invoke
4235NNNYNNNNN1071
Failure
H323 Destination4236YNYNNNNNY
Ingress
4237YNYNNYNNYN
Redirecting
Number
Service Usage
4239NNYYNNNNYN
Data
CNAM DIP4240YNYYNNNNYN
Calling Name4241YNYYNNNNYN
Terminating
4242YNYNNNNNYN
Remote SIP Host
Terminating Local
4243YNYNNNNNYN
SIP Host
License Rejecting
4244NNYNNNNNYN
Reason
License Rejecting
4245NNYNNNNNYN
Direction
SIP Transport4246YNYNNNNNYN
SIP Routing URI
4247YNYNNNNNYN
Source
SIP Routing URI4248YNYNNNNNYN
Millisecond Granularity Timepoint Fields
1071
1210
1260
IAM Timepoint
Received_ms
IAM Timepoint
Sent_ms
ACM Timepoint
Received_ms
ACM Timepoint
Sent_ms
ANM Timepoint
Received_ms
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-18
4100YYYNNYNNYN
4101YYYNNYNNYN
4102YNYNNYNNYN
4103YNYNNYNNYN
4104YNNNNYNNYN
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-5CDE Detail Description for the Current Release (continued)
Cisco MGC Billing Interfaces
Ans-
Tag
Field Name
ANM Timepoint
Sent_ms
First REL
Timepoint_ms
Second REL
Timepoint_ms
RLC Timepoint
Received_ms
RLC Timepoint
Sent_ms
Cisco Reserved Tags
Unique Call Correlator ID (Release 9
and later)
Miscellaneous FieldsThis field is used only in the File Header CDB and File Footer CDB. These CDBs are not
MGC ID6000
File Start Time6001
File End Time6002
Total Number of
CDB records
MGC Version6004
Interim CDB6005NNNYNNNNYN
Protocol Specific Fields
Value
4105YNNNNYNNYN
4106NYYYNNNNYN
4107NNYYNNNNYN
4108NYYYNNNNYN
4109NYYYNNNNYN
5000YY
6003
wered
(1010)
optional and are generated by the CDR dumper for each CDR file.
Deselected
(1020)
Aborted
(1030)
Y
InterRelease
(1040)
YYYYYY1071
rupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External
DB
(1080)
End of
Call
(1110)
1071
1210
1260
1210
1260
TTC Contract #6100YYYNNNNNNN
TTC Contract #
NOA
TTC Charge Info6102YYYNNNNNNN
TTC Charge Info
Type
TTC Charge Area
Info
6101YYYNNNNNNN
6103YYYNNNNNNN
6104YYYNNNNNNN
Cisco MGC Billing Interfaces
There are two billing interfaces provided by the Cisco MGC. They are:
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
1-19
Redundant Cisco MGC Configuration
• File Transfer Protocol (FTP) interface
• Generic interface
FTP Interface
The FTP interface allows the user to FTP the CDR files from the spool directory. This interface supports
users who own a mediation system or data collocation system. Users can process the CDR files on a
separate system.
The Cisco MGC runs on Solaris UNIX that provides the standard file transfer capability (FTP). The
Cisco MGC can be configured so other systems can download the CDR files from the spool directory.
The FTP download can be restricted by establishing user privileges.
The data collector and mediation systems can use this interface by periodically downloading the files.
The CDR files provide a sequence number and the timestamp of the file creation. The data collection
system or the mediation system can use this information to determine the desired file to download.
The Cisco MGC has several configuration parameters to write the CDR file. The following are the
configuration parameters:
• The prefix in the file name (CDR_YYYYMMDDHHMMSS_SeqNo) where SeqNo is in the format
Chapter 1 Billing Interfaces
(000001 to 999999)
• Spool directory
• Frequent creation of the file
The sequence number provides an audit capability to the data collection system or mediation software.
The sequence number is unique and ranges from 1 to 999999. If the system fails or restarts, it uses the
next sequence number (last sequence number + 1). When the sequence number reaches 999999, it then
restarts at 1.
Generic Interface
The Cisco MGC defines a generic or flexible billing interface. This is an internal interface between the
call processing module and the CDR dumper in Cisco MGC. Users cannot modify this interface.
This interface provides a CDB data stream for the CDR dumper. The generic interface is based on the
flexible CDB record layout. The record layout uses a tag, length, and value (TLV) encoding mechanism.
The detail messages (that is, CDBs) are explained later in this document.
Redundant Cisco MGC Configuration
In a redundant Cisco MGC configuration, the active Cisco MGC creates checkpoint records to
synchronize it with the standby Cisco MGC. The standby Cisco MGC creates call objects with
appropriate states to allow continued call processing after switchover occurs. When the standby Cisco
MGC becomes active, it starts synchronizing with End Offices (circuit audit). Another aspect of the
architecture is that the Cisco 2600s buffer messages while failover occurs.
Billing under a redundant configuration is basically limited to the following: The active Cisco MGC
generates the CDBs and the standby Cisco MGC does not. When failover occurs, the now active
Cisco MGC generates the CDBs.
1-20
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
If a call was stable during the failover, then the newly active Cisco MGC eventually generates an end of
a call CDB (Release CDB or possibly an Interrupted CDB) for each call. The CDBs generated by the
previous standby MGC include the same unique Call IDs. The mediation software requires correlating
the CDB records from both systems. For both systems to be properly correlated, both Cisco MGC clocks
must be synchronized with each other.
Cisco MGC Clock Synchronization
The Cisco MGC uses Network Time Protocol (NTP) to synchronize its time to another server or
reference time source, such as a radio or satellite receiver or modem. For example, the NTP provides
client accuracy that is typically within 1 millisecond on LANs and up to a few tenths of a second on
WANs relative to a primary server synchronized to Coordinated Universal Time (UTC) by a Global
Positioning Service (GPS) receiver. To achieve high accuracy and reliability, typical NTP configurations
use multiple redundant servers and diverse network paths. Some configurations include cryptographic
authentication to prevent accidents or malicious protocol attacks.
NoteRFC-1305 provides information on the NTP architecture, protocol, and algorithm.
Cisco MGC Clock Synchronization
Detailed CDB Description
This section contains the distinct record layouts for the CDB. Since each type of CDB is for a different
part of a call, the Cisco MGC provides the related CDEs that are needed.
NoteThe CDE includes only fields that have values. The layout varies based on the Cisco MGC configuration.
For example, if the Cisco MGC is configured with a protocol that does not support a specific CDE, then
the CDB record does not include that particular CDE.
Answered CDB Record (Tag: 1010/Release 5 or Later)
Table 1-6 lists data about the answered message. This CDB is generated when a call went through and
was answered (when the Cisco MGC receives ANM/Answered message).
Table 1-6Answered CDB Record
Tag
Field Name
ANSI Based Formatted Fields
Calling Party Category2000
User Service Information2001
Originating Line Information2002
Calling Number Nature of Address2003
Charged Number Nature of Address2004
ValueComments
When configured for ANSI-based formatted
fields (Release 7 or later option)
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-21
Detailed CDB Description
Chapter 1 Billing Interfaces
Table 1-6Answered CDB Record (continued)
Tag
Field Name
Dialed Number Nature of Address2005
LRN Nature of Address2006
Called Number Nature of Address2007
Forward Call Indicators Received2009
Forward Call Indicators Sent2010
Nature of Connection Indicators
Received
Nature of Connection Indicators Sent2012
Transit Network Selection2013
Carrier Identification Parameter2014
Carrier Selection Parameter2015
Jurisdiction Information Parameter2016
Redirecting Number NOA2017
Egress Calling Number NOA2018Added in a Release 9.5(2) patch
Egress Redirecting Number NOA2019Added in a Release 9.5(2) patch
Egress Original Called Number NOA2020Added in a Release 9.5(2) patch
ITU Based Formatted Fields
Calling Party Category3000
User Service Information3001
Originating Line Information3002
Calling Number Nature of Address3003
Dialed Number Nature of Address3005
LRN Nature of Address3006
Called Number Nature of Address3007
Forward Call Indicators Received3009
Forward Call Indicators Sent3010
Nature of Connection Indicators
Received
Nature of Connection Indicators Sent3012
Transit Network Selection3013
Redirecting Number NOA3017
Egress Calling Number NOA3018Added in a Release 9.5(2) patch
Egress Redirecting Number NOA3019Added in a Release 9.5(2) patch
Egress Original Called Number NOA3020Added in a Release 9.5(2) patch
ValueComments
2011
When configured for ITU-based formatted
fields (Release 7 or later option)
3011
1-22
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-6Answered CDB Record (continued)
Field Name
MGC Generic Tags
CDB Versionb4000
CDB Timepoint4001
Call Reference ID4002
IAM Timepoint4003When configured for seconds timepoint
ACM Timepoint4004When configured for seconds timepoint
ANM Timepoint4005When configured for seconds timepoint
Originating Trunk Group4008
Originating Member4009
Calling Number4010
Charged Number4011
Dialed Number4012
LRN Number4013
Called Number4014
Terminating Trunk Group4015
Terminating Member4016
LNP Dip4029
MGC Info Field4031Disabled as of Release 7.3.x, 7.4.x
Ingress Originating Point Code 4034
Ingress Destination Point Code4035
Egress Originating Point Code4036
Egress Destination Point Code4037
Ingress Media Gateway (CU)4038Ingress Media Gateway ID
Egress Media Gateway (CU)4039Egress Media Gateway ID
TCAP Transaction Identification4040
Transaction Start Time4041
Transaction End Time4042
TCAP Database Identification4043
Route Selection Info4045
Directional Flag4048
Redirecting Number4060Number or address from which forwarded
Test Line Indicator4063
Detailed CDB Description
Tag
ValueComments
(Release 7 or later option)
(Release 7 or later option)
(Release 7 or later option)
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-23
Detailed CDB Description
Chapter 1 Billing Interfaces
Table 1-6Answered CDB Record (continued)
Tag
Field Name
Ingress SigPath ID4066
Ingress Span ID4067
Ingress BearChan ID4068
Ingress ProtocolId4069
Egress SigPath ID4070
Egress Span ID4071
Egress BearChan ID4072
Egress ProtocolId4073
Original Called Number4080Release 9.3(1) and later
Charge Indicator4083Release 9.5(2) and later
Outgoing Calling Party Number4084Release 9.5(2) and later
MCID Request Indicator4085Release 9.5(2) and later
MCID Response Indicator4086Release 9.5(2) and later
Network Translated Address Indicator4089Release 9.5(2) and later
Reservation Request Accepted4090Release 9.5(2) and later
Reservation Request Error Count4091Release 9.5(2) and later
ATM Ingress Configured Profile4092Release 9.5(2) and later
ATM Egress Configured Profile4093Release 9.5(2) and later
ATM Negotiated Profile4094Release 9.5(2) and later
Route List Name4095Release 9.5(2) and later
Route Name4096Release 9.5(2) and later
MGCP Script Response String4097Release 9.5(2) and later
Originating Remote SIP Host4201Release 9 and later (Named as Ingress SIP URL
Originating Local SIP Host4202Release 9 and later (Named as Egress SIP URL
SIP Call ID4203Release 9 and later
Source IP Address4204Release 9.4(1) and later
Ingress Media Device Address4205Release 9.4(1) and later
Egress Media Device Address4206Release 9.4(1) and later
Initial Codec4207Release 9.4(1) and later
Ingress Media Device Port4209Release 9.4(1) and later
Egress Media Device Port4210Release 9.4(1) and later
Originating VPN ID4211Release 9.4(1) and later
Terminating VPN ID4212Release 9.4(1) and later
Partial Calling Line Identity4220Release 9.5(2) and later
ValueComments
in versions prior to the Release 9.7(3))
in versions prior to the Release 9.7(3))
1-24
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-6Answered CDB Record (continued)
Field Name
H323 Destination4236Release 9.7 and later
Ingress Redirecting Number4237Added in a Release 9.5(2) patch
CNAM DIP4240Release 9.7 and later
Calling Name4241Release 9.7 and later
Terminating Remote SIP Host4242Release 9.7 and later
Terminating Local SIP Host4243Release 9.7 and later
SIP Transport4246Release 9.7 and later
SIP Routing URI Source4247Release 9.7 and later
SIP Routing URI4248Release 9.7 and later
Millisecond Granularity Timepoint Fields
IAM Timepoint Received_ms4100
IAM Timepoint Sent_ms4101
ACM Timepoint Received_ms4102
ACM Timepoint Sent_ms4103
ANM Timepoint Received_ms4104
ANM Timepoint Sent_ms4105
Cisco Reserved Tags
Unique Call ID (Release 9 and later)5000
Detailed CDB Description
Tag
ValueComments
Deselected Outgoing Circuit CDB Record (Tag: 1020/Release 5 or Later)
Table 1-7 lists data about the deselected outgoing circuit. CDB Tag 1020 is generated when a circuit is
attempted to be used and for some reason the circuit can not be used. The call is then passed to another
circuit to complete the call.
Table 1-7Deselected Outgoing Circuit CDB Record
Tag
Field Name
ANSI Based Formatted Fields
Reason Code2008
Forward Call Indicators Received2009
Forward Call Indicators Sent2010
Nature of Connection Indicators
Received
Nature of Connection Indicators Sent 2012
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
ValueComments
When configured for ANSI encoding (Release 7
or later)
2011
1-25
Detailed CDB Description
Chapter 1 Billing Interfaces
Table 1-7Deselected Outgoing Circuit CDB Record (continued)
Tag
Field Name
ITU Based Formatted Fields
Reason Code3008
Forward Call Indicators Received3009
Forward Call Indicators Sent3010
Nature of Connection Indicators
Received
Nature of Connection Indicators Sent 3012
MGC Generic Tags
CDB Version4000
CDB Timepoint4001
Call Reference ID4002
IAM Timepoint4003When timepoint in seconds is selected
REL Timepoint4006When timepoint in seconds is selected
Originating Trunk Group4008
Originating Member4009
Terminating Trunk Group4015
Terminating Member4016
Glare Encountered4019
RLC Timepoint4020
First Release Source4028
Ingress Originating Point Code 4034
Ingress Destination Point Code4035
Egress Originating Point Code4036
Egress Destination Point Code4037
Ingress Media Gateway (CU)4038
Egress Media Gateway (CU)4039
Rejecting Location Label 4232Release 9.6(1) and later
Rejecting Location Label Direction4233Release 9.6(1) and later
Millisecond Granularity Timepoint Fields
IAM Timepoint Received_ms4100
IAM Timepoint Sent_ms4101
First REL Timepoint_ms4106
RLC Timepoint Received_ms4108
ValueComments
When configured for ITU encoding (Release 7 or
later)
3011
When configured for milliseconds (Release 7 or
later)
1-26
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-7Deselected Outgoing Circuit CDB Record (continued)
Tag
Field Name
ValueComments
RLC Timepoint Sent_ms4109
Cisco Reserved Tags
Unique Call ID (Release 9 and later) 5000
Aborted Attempt CDB Record (Tag: 1030/Release 5 or Later)
Table 1-8 lists data about the aborted attempt. CDB Tag 1030 is generated for an attempted call that did
not get to Setup status. That is a call that did not get answered.
Table 1-8Aborted Attempt CDB Record
Tag
Field Name
ANSI Based Formatted Fields
Calling Party Category2000
User Service Information2001
Originating Line Information2002
Calling Number Nature of Address2003
Charged Number Nature of Address2004
Dialed Number Nature of Address2005
LRN Nature of Address2006
Called Number Nature of Address2007
Reason Code2008
Forward Call Indicators Received2009
Nature of Connection Indicators
Received
Nature of Connection Indicators Sent 2012
Transit Network Selection2013
Carrier Identification Parameter2014
Carrier Selection Parameter2015
Jurisdiction Information Parameter2016
Redirecting Number NOA 2017
Egress Calling Number NOA2018Added in a Release 9.5(2) patch
Egress Redirecting Number NOA2019Added in a Release 9.5(2) patch
Egress Original Called Number NOA 2020Added in a Release 9.5(2) patch
ValueComments
When configured for ANSI based encoding
(Release 7 or later)
2011
Detailed CDB Description
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-27
Detailed CDB Description
Chapter 1 Billing Interfaces
Table 1-8Aborted Attempt CDB Record (continued)
Tag
Field Name
ITU Based Formatted Fields
Calling Party Category3000
User Service Information3001
Originating Line Information3002
Calling Number Nature of Address3003
Dialed Number Nature of Address3005
LRN Nature of Address3006
Called Number Nature of Address3007
Reason Code3008
Forward Call Indicators Received3009
Nature of Connection Indicators
Received
Transit Network Selection3013
Redirecting Number NOA3017
Egress Calling Number NOA3018Added in a Release 9.5(2) patch
Egress Redirecting Number NOA3019Added in a Release 9.5(2) patch
Egress Original Called Number NOA 3020Added in a Release 9.5(2) patch
MGC Generic Tags
CDB Version4000
CDB Timepoint4001
Call Reference ID4002
IAM Timepoint4003When configured for seconds timepoint
ACM Timepoint4004When configured for seconds timepoint
REL Timepoint4006When configured for seconds timepoint
Originating Trunk Group4008
Originating Member4009
Calling Number4010
Charged Number4011
Dialed Number4012
LRN Number4013
Called Number4014
Terminating Trunk Group4015
Terminating Member4016
Glare Encountered4019
ValueComments
When configured for ITU encoding (Release 7 or
later)
3011
1-28
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-8Aborted Attempt CDB Record (continued)
Field Name
RLC Timepoint4020When timepoint in seconds is selected
First Release Source4028
LNP Dip4029
MGC Info Field4031Disabled as of Release 7.3.x and 7.4.x
Ingress Originating Point Code 4034
Ingress Destination Point Code4035
Egress Originating Point Code4036
Egress Destination Point Code4037
Ingress Media Gateway (CU)4038
Egress Media Gateway (CU)4039
Ingress Gateway Packet Info4046Restored as of Release 9.4(1)
Egress Gateway Packet Info4047Restored as of Release 9.4(1)
Directional Flag4048
Redirecting Number4060
Tariff Rate4061
Scale Factor4062
Test Line Indicator4063
Redirection Number4065Release 9.7(3) and later
Ingress SigPath ID4066
Ingress Span ID4067
Ingress BearChan ID4068
Ingress ProtocolId4069
Egress SigPath ID4070
Egress Span ID4071
Egress BearChan ID4072
Egress ProtocolId4073
Charge Band Number4078Release 9.3(1) and later
Furnish Charging Information4079Release 9.3(1) and later
Original Called Number4080Release 9.3(1) and later
T.38 Fax Call4081Release 9.3(2) and later
Charge Unit Number4082Release 9.3(2) and later
Charge Indicator4083Release 9.5(2) and later
Outgoing Calling Party Number4084Release 9.5(2) and later
MCID Request Indicator4085Release 9.5(2) and later
MCID Response Indicator4086Release 9.5(2) and later
Detailed CDB Description
Tag
ValueComments
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-29
Detailed CDB Description
Chapter 1 Billing Interfaces
Table 1-8Aborted Attempt CDB Record (continued)
Tag
Field Name
Ingress MGCP DLCX Return Code4087Release 9.5(2) and later
Egress MGCP DLCX Return Code4088Release 9.5(2) and later
Network Translated Address
Indicator
Reservation Request Accepted4090Release 9.5(2) and later
Reservation Request Error Count4091Release 9.5(2) and later
ATM Ingress Configured Profile4092Release 9.5(2) and later
ATM Egress Configured Profile4093Release 9.5(2) and later
ATM Negotiated Profile4094Release 9.5(2) and later
Route List Name4095Release 9.5(2) and later
Route Name4096Release 9.5(2) and later
Originating Leg DSP Statistics4098Release 9.4(1) and later
Terminating Leg DSP Statistics4099Release 9.4(1) and later
Originating Remote SIP Host4201Release 9 and later (Named as Ingress SIP URL
Originating Local SIP Host4202Release 9 and later (Named as Egress SIP URL
SIP Call ID4203Release 9 and later
Source IP Address4204Release 9.4(1) and later
Ingress Media Device Address4205Release 9.4(1) and later
Egress Media Device Address4206Release 9.4(1) and later
Initial Codec4207Release 9.4(1) and later
Final Codec4208Release 9.4(1) and later
Ingress Media Device Port4209Release 9.4(1) and later
Egress Media Device Port4210Release 9.4(1) and later
Originating VPN ID4211Release 9.4(1) and later
Terminating VPN ID4212Release 9.4(1) and later
Partial Calling Line Identity4220Release 9.5(2) and later
Service Activation4221Added in Release 9.5(2), modified in 9.6(1)
PRI AOC Invoke Type4222Release 9.5(2) and later
PRI AOC – S Charge Information4223Release 9.5(2) and later
PRI AOC – D Charge Information4224Release 9.5(2) and later
PRI AOC – E Charge Information4225Release 9.5(2) and later
PRI AOC Invoke Failure4226Release 9.5(2) and later
Rejecting Location Label 4232Release 9.6(1) and later
Rejecting Location Label Direction4233Release 9.6(1) and later
ValueComments
4089Release 9.5(2) and later
in versions prior to the Release 9.7(3))
in versions prior to the Release 9.7(3))
1-30
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-8Aborted Attempt CDB Record (continued)
Field Name
H323 Destination4236Release 9.7 and later
Ingress Redirecting Number4237Added in a Release 9.5(2) patch
Service Usage Data4239Release 9.7 and later
CNAM DIP4240Release 9.7 and later
Calling Name4241Release 9.7 and later
Terminating Remote SIP Host4242Release 9.7 and later
Terminating Local SIP Host4243Release 9.7 and later
License Rejecting Reason4244Release 9.7 and later
License Rejecting Direction4245Release 9.7 and later
SIP Transport4246Release 9.7 and later
SIP Routing URI Source4247Release 9.7 and later
SIP Routing URI4248Release 9.7 and later
Millisecond Granularity Timepoint Fields
IAM Timepoint Received_ms4100
IAM Timepoint Sent_ms4101
ACM Timepoint Received_ms4102
ACM Timepoint Sent_ms4103
First REL Timepoint_ms4106
Second REL Timepoint_ms4107
RLC Timepoint Received_ms4108
RLC Timepoint Sent_ms4109
Cisco Reserved Tags
Unique Call ID (Release 9 and later) 5000
Detailed CDB Description
Tag
ValueComments
When configured for milliseconds granularity
for timepoints fields
Release CDB Record (Tag: 1040/Release 5 or Later)
Table 1-9 lists data about the release CDB. CDB Tag 1040 is generated when the terminating CDB on a
call that went through and was answered and then released.
Table 1-9Release CDB Record
Tag
Field Name
ANSI Based Formatted Fields
Reason Code2008
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
ValueComments
When configured for ITU encoding (Release 7 or
later)
1-31
Detailed CDB Description
Chapter 1 Billing Interfaces
Table 1-9Release CDB Record (continued)
Tag
Field Name
ITU Based Formatted Fields
Reason Code3008
MGC Generic Tags
CDB Version4000
CDB Timepoint4001
Call Reference ID4002
REL Timepoint4006When configured for seconds granularity
Glare Encountered4019
RLC Timepoint4020When configured for seconds granularity
First Release Source4028
Total Meter Pulses4030
Announcement Identification4044
Ingress Gateway Packet Info4046Restored as of Release 9.4(1)
Egress Gateway Packet Info4047Restored as of Release 9.4(1)
Tariff Rate4061
Scale Factor4062
Charge Band Number4078Release 9.3(1) and later
Furnish Charging Information4079Release 9.3(1) and later
T.38 Fax Call4081Release 9.3(2) and later
Charge Unit Number4082Release 9.3(2) and later
Charge Indicator4083Release 9.5(2) and later
Outgoing Calling Party Number4084Release 9.5(2) and later
MCID Request Indicator4085Release 9.5(2) and later
MCID Response Indicator4086Release 9.5(2) and later
Ingress MGCP DLCX Return Code4087Release 9.5(2) and later
Egress MGCP DLCX Return Code4088Release 9.5(2) and later
Network Translated Address
Indicator
Reservation Request Accepted4090Release 9.5(2) and later
Reservation Request Error Count4091Release 9.5(2) and later
Route List Name4095Release 9.5(2) and later
Route Name4096Release 9.5(2) and later
MGCP Script Response String4097Release 9.5(2) and later
ValueComments
When configured for ITU encoding (Release 7 or
later)
timepoints
timepoints
4089Release 9.5(2) and later
1-32
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-9Release CDB Record (continued)
Field Name
Originating Leg DSP Statistics4098Release 9.4(1) and later
Terminating Leg DSP Statistics4099Release 9.4(1) and later
Ingress Media Device Address4205Release 9.4(1) and later
Egress Media Device Address4206Release 9.4(1) and later
Initial Codec4207Release 9.4(1) and later
Final Codec4208Release 9.4(1) and later
Ingress Media Device Port4209Release 9.4(1) and later
Egress Media Device Port4210Release 9.4(1) and later
Meter Pulses Received4213Release 9.5(2) and later
Meter Pulses Sent4214Release 9.5(2) and later
Charge Tariff Info4215Release 9.5(2) and later
Advice of Charge Indicator4216Release 9.5(2) and later
Short Call Indicator4217Release 9.5(2) and later
Charge Limit Exceeded4218Release 9.5(2) and later
Call Recovered Indication4219Release 9.5(2) and later
Service Activation4221Added in Release 9.5(2), modified in 9.6(1)
PRI AOC Invoke Type4222Release 9.5(2) and later
PRI AOC – S Charge Information4223Release 9.5(2) and later
PRI AOC – D Charge Information4224Release 9.5(2) and later
PRI AOC – E Charge Information4225Release 9.5(2) and later
PRI AOC Invoke Failure4226Release 9.5(2) and later
RO/PR Executed4227Release 9.6(1) and later
RO/PR Other Call Ref4228Release 9.6(1) and later
RO/PR Replacement Trunk Group4229Release 9.6(1) and later
RO/PR Replacement Chan ID4230Release 9.6(1) and later
RO/PR Switchover Timestamp4231Release 9.6(1) and later
Service Usage Data4239Release 9.7 and later
CNAM DIP4240Release 9.7 and later
Calling Name4241Release 9.7 and later
Millisecond Granularity Timepoint Fields
First REL Timepoint_ms4106
Second REL Timepoint_ms4107
RLC Timepoint Received_ms4108
RLC Timepoint Sent_ms4109
Detailed CDB Description
Tag
ValueComments
When configured for ITU encoding (Release 7 or
later)
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-33
Detailed CDB Description
Table 1-9Release CDB Record (continued)
Tag
Field Name
Cisco Reserved Tags
Unique Call ID (Release 9 and later) 5000
ValueComments
Interrupted CDB Record (Tag: 1050/Release 5 or Later)
Table 1-10 lists data about the interrupted CDB. CDB Tag 1050 is created when a call is terminated
without a Release message. This happens for example, in hot standby configuration when dual Cisco
MGCs are used, and when failover occurs and the now active Cisco MGC discovers that a call is no
longer active (the release message probably arrived and was lost during the failover window).
Table 1-10Interrupt CDB Record
Tag
Field Name
MGC Generic Tags
CDB Version4000
CDB Timepoint4001
Call Reference ID4002
Crash Timepoint4007
Cisco Reserved Tags
Unique Call ID (Release 9 and later) 5000
ValueComments
Chapter 1 Billing Interfaces
On-Going (Call) CDB Record (Tag: 1060/Release 5 or Later)
The On-going Call CDB (or Long-Call CDB) indicates that a call is still active after the expiration of
the time span defined in the XECfgParm.dat parameter *.LongCallTime. This CDB is generated again
each time the period defined in *.LongCallTime elapses while the call is active. For example, if *.LongCallTime is set to its default value, 21600000 ms, which is equal to 6 hours, a 1060 CDB is
generated every 6 hours until the call is terminated.
NoteWhen the MGC is configured to create only the 1110 CDB (End-of-Call Summary) and this CDB, all of
the relevant 1060 tags are present and populated. This is because the 1060 CDB may be the first CDB
that is written for a call, if it has been active for the long-call period. In this case, the 1060 CDB contains
the full set of populated tags. However, when the MGC is configured to generate event-based CDBs
(such as 1010, 1020, 1030, 1040, 1050, 1060, 1070, and 1080) the 1060 CDB can contain only a subset
of tags: 5000, 4000–4002, 4213, and 4214. This occurs because the other event-based CDBs contain the
tag information, as they are associated with specific events. Therefore, in this instance the 1060 CDB
does not contain this redunant data, as it would be outside the primary purpose of this CDB.
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-34
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-11 lists data about the on-going (Call) CDB.
NoteIn Release 7 and later, the long duration includes more fields than it does in Release 5. The extra fields
are marked Release 7 and later.
Table 1-11On-going CDB Record
Field Name
ANSI-Specific Tags
Egress Calling Number NOA2018Added in a Release 9.5(2) patch. Present only when
Egress Redirecting Number NOA2019Added in a Release 9.5(2) patch. Present only when
Egress Original Called Number NOA 2020Added in a Release 9.5(2) patch. Present only when
ITU-Specific Tags
Egress Calling Number NOA3018Added in a Release 9.5(2) patch. Present only when
Egress Redirecting Number NOA3019Added in a Release 9.5(2) patch. Present only when
Egress Original Called Number NOA 3020Added in a Release 9.5(2) patch. Present only when
MGC Generic Tags
CDB Version4000Always present and populated in 1060.
CDB Timepoint4001Always present and populated in 1060.
Call Reference ID4002Always present and populated in 1060.
IAM Timepoint4003Optional. Present only when 1110 is configured and if
ACM Timepoint4004Optional. Present only when 1110 is configured and if
ANM/Answer Timepoint4005Optional. Present only when 1110 is configured and if
Originating Trunk Group4008Optional. Present only when 1110 is configured.
Originating Member4009Optional. Present only when 1110 is configured.
Detailed CDB Description
Tag
ValueComments
1110 is configured. Not recorded for point-in-call
mode.
1110 is configured. Not recorded for point-in-call
mode.
1110 is configured. Not recorded for point-in-call
mode.
1110 is configured. Not recorded for point-in-call
mode.
1110 is configured. Not recorded for point-in-call
mode.
1110 is configured. Not recorded for point-in-call
mode.
system is configured for seconds timepoint.
system is configured for seconds timepoint.
system is configured for seconds timepoint.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-35
Detailed CDB Description
Chapter 1 Billing Interfaces
Table 1-11On-going CDB Record (continued)
Tag
Field Name
Calling Number4010Optional. Present only when 1110 is configured.
Dialed Number4012Optional. Present only when 1110 is configured.
Called Number4014Optional. Present only when 1110 is configured.
Terminating Trunk Group4015Optional. Present only when 1110 is configured.
Terminating Member4016Optional. Present only when 1110 is configured.
Ingress SigPath ID4066Optional. Present only when 1110 is configured.
Ingress Span ID4067Optional. Present only when 1110 is configured.
Ingress BearChan ID4068Optional. Present only when 1110 is configured.
Ingress ProtocolId4069Optional. Present only when 1110 is configured.
Egress SigPath ID4070Optional. Present only when 1110 is configured.
Egress Span ID4071Optional. Present only when 1110 is configured.
Egress BearChan ID4072Optional. Present only when 1110 is configured.
Egress ProtocolId4073Optional. Present only when 1110 is configured.
Original Called Number4080Release 9.3(1) and later. Optional. Present only when
Meter Pulses Received4213Release 9.5(2) and later. Always present and
Meter Pulses Sent4214Release 9.5(2) and later. Always present and
Partial Calling Line Identity4220Release 9.5(2) and later. Optional. Present only when
Ingress Redirecting Number 4237Added in a Release 9.5(2) patch. Present only when
Millisecond Granularity Timepoint Fields
IAM Timepoint Received _ms4100Optional. Present only when 1110 is configured.
IAM Timepoint Sent_ms4101Optional. Present only when 1110 is configured.
ACM Timepoint Received_ms4102Optional. Present only when 1110 is configured.
ACM Timepoint Sent_ms4103Optional. Present only when 1110 is configured.
ANM Timepoint Received_ms4104Optional. Present only when 1110 is configured.
ANM Timepoint Sent_ms4105Optional. Present only when 1110 is configured.
Cisco Reserved Tags
Unique Call ID (Release 9 and later) 5000Always present and populated in 1060.
ValueComments
1110 is configured.
populated in 1060.
populated in 1060.
1110 is configured.
1110 is configured. Not recorded for point-in-call
mode.
1-36
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Maintenance CDB Record (Tag: 1070/Release 5 or Later)
Table 1-12 lists data about the maintenance record CDB type. CDB Tag 1070 is created for maintenance
activity (such as block or unblock) on a circuit.
Table 1-12Maintenance CDB Record
Tag
Field Name
MGC Generic Tags
CDB Version4000
CDB Timepoint4001
Call Reference ID4002
Maint Trunk Group4017
Maint Circuit Member4018
Maint Type4032
Maint Reason (Retired in Release
9.4(1))
Maintenance SigPath ID 4074
Maintenance Span ID4075
Maintenance BearChan ID4076
Maintenance Circuits Count4077
Cisco Reserved Tags
Unique Call ID (Release 9 and later) 5000
Value
4033
Detailed CDB Description
SS7 CIC Audit CDB Record (Tag: 1071/Release 9 or Later)
Table 1-13 lists data about the SS7 CIC audit record CDB type. This CDB is used to record changes to:
• the number of circuits defined for a trunk group when the MGC is configured in Call Control mode
• the number of circuits defined in a signaling service when the MGC is configured in Signaling mode.
This CDB is modeled after the 1070 CDB but does not contain independent CIC statuses, just total
counts of CICs defined and unavailable. It is triggered by provisioning changes to the number of circuits
in a trunk group (Call Control) or signaling service (Signaling).
Table 1-13SS7 CIC Audio CDB Record
Tag
Field Name
MGC Generic Tags
CDB Version4000
CDB Timepoint4001
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
ValueComments
1-37
Detailed CDB Description
NoteCDB 1071 is configurable in XECfgParm.dat by adding it in engine.CDRmessageType; but if CDB 1110
Table 1-13SS7 CIC Audio CDB Record (continued)
Tag
Field Name
Maint Trunk Group4017Appears when the MGC is
Maintenance SigPath ID 4074Appears when the MGC is
Total Circuit Count4234added in 9.4(1) patch
Total Circuit Unavailable Count4235added in 9.4(1) patch
Cisco Reserved Tags
Unique Call ID5000
is configured, CDB 1071 is suppressed.
ValueComments
configured for call control.
configured for signaling.
Chapter 1 Billing Interfaces
Once configured in XECfgParm.dat, CDB 1071 is generated for the following conditions.
• When the MML command sta-aud-cic is used to generate the current CIC availability information
on each configured ISUP trunk group or signaling service.
• A provisioning change (add or delete) is made in the number of circuits.
• A CIC service state or block state change occurs. A circuit that is unavailable is either blocked, OOS,
or both. A circuit that is blocked and also OOS is not double counted as unavailable circuits. The
following tables show the action taken when there is a service state or block state change.
Table 1-14Service State Change
Service State ChangeBlockedUnblocked
OOSDo nothingIncrement total unavailable counters
ISDo nothingDecrement total unavailable counters
Table 1-15Service Block Change
Service Block ChangeOOSIS
BlockDo nothingIncrement total unavailable counters
UnblockDo nothingDecrement total unavailable counters
1-38
A blocked state is one or a combination of the following states:
• Manual local block
• Manual remote block
• Auto remote block (hardware failure)
• Auto local block
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
• Propagation block (gateway initiated blocking)
CDB Tag 1071 generation rules:
• If CDB Tag 1071 is generated as the result of the sta-aud-cic MML command, it includes the CIC
• CDB Tag 1071 is generated only on the active side.
• To generate the CDB Tag 1071 on a trunk group or signaling service level rather than individual CIC
• The sta-aud-cic MML command is rejected for the following conditions:
• A circuit that has COT failure and has COT retest in progress is not counted as unavailable.
Detailed CDB Description
unavailability information per trunk group for switched configuration, or per signaling service for
nailed up. For other two scenarios, it only generates the information for the trunk groups that are
impacted.
level to minimize CPS impact, an internal 10-second timer is used. 1071 CDB is generated 10
seconds after the initial CIC state change and/or the initial CIC provision change. This delay
prevents the flooding of 1071 CDBs if a large number of CICs have blocks or service state changes
almost simultaneously.
–
The MML command is attempted to be run on the standby side
–
CDB Tag 1071 is not configured in the XECfgParm.dat file
• If the CDB Tag 1071 is configured to be generated for Cisco MGC software Release 9.5(2), that pre
BAMS 3.20 would require a skip-CDE for the CDB Tag 1071 record to be added to BAMS.
External Access CDB (Tag: 1080/Release 7 or Later)
Table 1-16 lists data about the external access CDB type. CDB Tag 1080 is generated whenever a query
is sent to an SCP (or other external device or database).
Table 1-16External Access CDB Record
Tag
Field Name
MGC Generic Tags
CDB Version4000
CDB Timepoint4001Time written
Universal Call Reference ID4002
TCAP Transaction Identification4040TCAP Transaction ID
Transaction Start Time4041Time that TCAP query was sent
Transaction End Time4042Time that TCAP response was received
TCAP Database Identification4043SCP Selection Number
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-39
Detailed CDB Description
File Header CDB (Tag: 1090/Release 7 or Later)
The CDR dumper generates the File Header CDB at the beginning of each new CDR file. It is generated
according to the CDB creation guidelines, where the first three fields are mandatory and are located in
their specified positions (refer to Table 1-17).
NoteThis CDB is not configurable. Users cannot enable or disable the CDB nor can they select which fields
are to be included. This CDB always contains the fields shown in Table 1-17.
Chapter 1 Billing Interfaces
.
Table 1-17File Header CDB Record
Tag
Field Name
MGC Generic Tags
CDB Version4000
CDB Timepoint4001Time written
Universal Call Reference ID4002Always 0 for compatibility with all other CDB
Miscellaneous Fields
File Start Time6001
Host MGC ID6000
MGC Software Version6004
ValueInformation Source
layouts
File Footer CDB (Tag: 1100/Release 7 or Later)
The CDR dumper generates the File Footer CDB at the end of each new CDR file. It is generated
according to the CDB creation guidelines, where the first three fields are mandatory and are located in
their specified positions (refer to Table 1-18).
1-40
NoteThis CDB is not configurable. Users cannot enable or disable the File Footer CDB nor can they select
which fields are to be included. This CDB always contains the fields shown in Table 1-18.
Table 1-18File Footer CDB Record
Tag
Field Name
MGC Generic Tags
CDB Version4000
CDB Timepoint4001
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
ValueInformation Source
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-18File Footer CDB Record (continued)
Tag
Field Name
Call Reference ID4002This will always be 0, for compatibility with all
Miscellaneous Fields
File End Time6002
Total Number of CDB Records6003
Host ID6000
MGC Software Version6004
ValueInformation Source
other CDB layouts.
End of the Call CDB (Tag: 1110/Release 7 or Later)
When the Cisco MGC software is configured to generate one CDB per call, a CDB is generated that
includes basic billing information. It is generated at the end of the call, as is the Release CDB, or an
attempted call that did not get to Setup status. That is, a call that did not get answered, as in an Aborted
Attempted CDB.
Detailed CDB Description
This End of Call CDB consists of the values listed in Table 1-19.
Table 1-19End of Call CDB Record
ANSI
Tag
ValueDescription
2000Calling Party Category3000Calling Party Category
2001User Service Information3001User Service Information
2003Calling number NOA3003Calling Number NOA
2004Charged number NOA Does not exist for ITU
2005Dialed number NOA3005Dialed Number NOA
2007Called Number NOA3007Called Number NOA
2008Reason Code3008Reason Code
2013Transit Network Selection
2015Carrier Selection Parameter
2017Redirecting Number NOA3017Redirecting Number NOA
2018Egress Calling Number NOA (Release
2019Egress Redirecting Number NOA
2020Egress Original Called Number NOA
4000CDB Version4000CDB Version
9.5(2) and later)
(Release 9.5(2) and later)
(Release 9.5(2)) and later)
ITU
Tag
ValueDescription
3018Egress Calling Number NOA (Release
3019Egress Redirecting Number NOA
3020Egress Original Called Number NOA
9.5(2) and later)
(Release 9.5(2) and later)
(Release 9.5(2) and later)
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-41
Detailed CDB Description
Chapter 1 Billing Interfaces
Table 1-19End of Call CDB Record (continued)
ANSI
Tag
ValueDescription
ITU
Tag
ValueDescription
4001CDB Timepoint4001CDB Timepoint
4002Call Reference ID4002Call Reference ID
4008Originating Trunk Group4008Originating Trunk Group
4009Originating Member4009Originating Member
4010Calling Number4010Calling Number
4011Charged Number4011Charged Number
4012Dialed Number4012Dialed Number
4014Called Number4014Called Number
4015Terminating Trunk Group4015Terminating Trunk Group
4016Terminating Member4016Terminating Member
4028First Release Source4028First Release Source
4031MGC Info Field (disabled as of
Release 7.3.x and 7.4.x)
4034Ingress Originating Point Code
(Release 9.3(2) and up)
4035Ingress Destination Point Code
(Release 9.3(2) and up)
4036Egress Originating Point Code (Release
9.3(2) and up)
4037Egress Destination Point Code (Release
9.3(2) and up)
4046Ingress Gateway Packet Info (Restored
as of Release 9.4(1))
4047Egress Gateway Packet Info (Restored
as of Release 9.4(1))
4031MGC Info Field (disabled as of
Release 7.3.x and 7.4.x)
4034Ingress Originating Point Code
(Release 9.3(2) and up)
4035Ingress Destination Point Code
(Release 9.3(2) and up)
4036Egress Originating Point Code (Release
9.3(2) and up)
4037Egress Destination Point Code (Release
9.3(2) and up)
4046Ingress Gateway Packet Info (Restored
as of Release 9.4(1))
4047Egress Gateway Packet Info (Restored
as of Release 9.4(1))
4060Redirecting Number4060Redirecting Number
4061Tariff Rate4061Tariff Rate
4062Scale Factor4062Scale Factor
4063Test Line Indicator4063Test Line Indicator
4065Redirection Number4065Redirection Number (Release 9.7(3)
and later)
4068Ingress BearChan ID (Release 9.3(2)
and up)
4072Egress BearChan ID (Release 9.3(2)
and up)
4068Ingress BearChan ID (Release 9.3(2)
and up)
4072Egress BearChan ID (Release 9.3(2)
and up)
4078Charge Band Number 4078Charge Band Number (
4079Furnish Charging Information4079Furnish Charging Information
1-42
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-19End of Call CDB Record (continued)
Detailed CDB Description
ANSI
Tag
ValueDescription
ITU
Tag
ValueDescription
4080Original Called Number4080Original Called Number
4082Charge Unit Number4082Charge Unit Number
4083Charge Indicator (Release 9.5(2) and
up)
4084Outgoing Calling Party Number
(Release 9.5(2) and up)
4085MCID Request Indicator (Release
9.5(2) and up)
4086MCID Response Indicator (Release
9.5(2) and up)
4087Ingress MGCP DLCX Return Code
(Release 9.5(2) and up)
4088Egress MGCP DLCX Return Code
(Release 9.5(2) and up)
4089Network Translated Address Indicator
(Release 9.5(2) and up)
4090Reservation Request Accepted (Release
9.5(2) and up)
4091Reservation Request Error Count
(Release 9.5(2) and up)
4092ATM Ingress Configured Profile
(Release 9.5(2) and up)
4093ATM Egress Configured Profile
(Release 9.5(2) and up)
4094ATM Negotiated Profiler (Release
9.5(2) and up)
4095Route List Name (Release 9.5(2) and
up)
4083Charge Indicator(Release 9.5(2) and
up)
4084Outgoing Calling Party Number
(Release 9.5(2) and up)
4085MCID Request Indicator (Release
9.5(2) and up)
4086MCID Response Indicator (Release
9.5(2) and up)
4087Ingress MGCP DLCX Return Code
(Release 9.5(2) and up)
4088Egress MGCP DLCX Return Code
(Release 9.5(2) and up)
4089Network Translated Address Indicator
(Release 9.5(2) and up)
4090Reservation Request Accepted (Release
9.5(2) and up)
4091Reservation Request Error Count
(Release 9.5(2) and up)
4092ATM Ingress Configured Profile
(Release 9.5(2) and up)
4093ATM Egress Configured Profile
(Release 9.5(2) and up)
4094ATM Negotiated Profile (Release 9.5(2)
and up)
4095Route List Name (Release 9.5(2) and
up)
4096Route Name (Release 9.5(2) and up)4096Route Name (Release 9.5(2) and up)
4203SIP Call ID (Release 9 and later)4203SIP Call ID (Release 9 and later)
4204Source IP Address (Release 9.4(1) and
later)
4205Ingress Media Device Address (Release
9.4(1) and later)
4206Egress Media Device Address (Release
9.4(1) and later)
4204Source IP Address (Release 9.4(1) and
later)
4205Ingress Media Device Address (Release
9.4(1) and later)
4206Egress Media Device Address (Release
9.4(1) and later)
4207Initial Codec (Release 9.4(1) and later) 4207Initial Codec (Release 9.4(1) and later)
4208Final Codec (Release 9.4(1) and later)4208Final Codec (Release 9.4(1) and later)
4209Ingress Media Device Port (Release
9.4(1) and later)
4210Egress Media Device Port (Release
9.4(1) and later)
4211Originating VPN ID (Release 9.4(1)
and later)
4212Terminating VPN ID (Release 9.4(1)
and later)
4213Meter Pulses Received (Release 9.5(2)
and later)
4214Meter Pulses Sent (Release 9.5(2) and
later)
4215Charge Tariff Info (Release 9.5(2) and
later)
4216Advice of Charge Indicator (Release
9.5(2) and later)
4217Short Call Indicator (Release 9.5(2) and
later)
4209Ingress Media Device Port (Release
9.4(1) and later)
4210Egress Media Device Port (Release
9.4(1) and later)
4211Originating VPN ID (Release 9.4(1)
and later)
4212Terminating VPN ID (Release 9.4(1)
and later)
4213Meter Pulses Received (Release 9.5(2)
and later)
4214Meter Pulses Sent (Release 9.5(2) and
later)
4215Charge Tariff Info (Release 9.5(2) and
later)
4216Advice of Charge Indicator (Release
9.5(2) and later)
4217Short Call Indicator (Release 9.5(2) and
later)
1-44
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-19End of Call CDB Record (continued)
Detailed CDB Description
ANSI
Tag
ValueDescription
4218Charge Limit Exceeded (Release 9.5(2)
and later)
4219Call Recovered Indication (Release
9.5(2) and later)
4220Partial Calling Line Identity (Release
9.5(2) and later)
4221Service Activation (Added in Release
9.5(2), modified in Release 9.6(1))
4222PRI AOC Invoke Type (Release 9.5(2)
and later)
4223PRI AOC – S Charge Information
(Release 9.5(2) and later)
4224PRI AOC – D Charge Information
(Release 9.5(2) and later)
4225PRI AOC – E Charge Information
(Release 9.5(2) and later)
4226PRI AOC Invoke Failure (Release
9.5(2) and later)
4227Route Optimization/Path Replacement
Action (Release 9.6(1) and later)
4228Route Optimization / Path Replacement
Call Reference of Associated Call
Instance (Release 9.6(1) and later)
4229Route Optimization / Path Replacement
Trunk Group Info (Release 9.6(1) and
later)
4230Route Optimization / Path Replacement
Channel Info (Release 9.6(1) and later)
4231Route Optimization Switchover
Timestamp (Release 9.6(1) and later)
4232Rejecting Location Label (Release
9.6(1) and later)
4233Rejecting Location Label Direction
(Release 9.6(1) and later)
4236H323 Destination (Release 9.7 and
later)
4237Ingress Redirecting Number (Release
9.5(2) and later)
4239Service Usage Data (Release 9.7 and
later)
ITU
Tag
ValueDescription
4218Charge Limit Exceeded (Release 9.5(2)
and later)
4219Call Recovered Indication (Release
9.5(2) and later)
4220Partial Calling Line Identity (Release
9.5(2) and later)
4221Service Activation (Added in Release
9.5(2), modified in Release 9.6(1))
4222PRI AOC Invoke Type (Release 9.5(2)
and later)
4223PRI AOC – S Charge Information
(Release 9.5(2) and later)
4224PRI AOC – D Charge Information
(Release 9.5(2) and later)
4225PRI AOC – E Charge Information
(Release 9.5(2) and later)
4226PRI AOC Invoke Failure (Release
9.5(2) and later)
4227Route Optimization/Path Replacement
Action (Release 9.6(1) and later)
4228Route Optimization / Path Replacement
Call Reference of Associated Call
Instance (Release 9.6(1) and later)
4229Route Optimization / Path Replacement
Trunk Group Info (Release 9.6(1) and
later)
4230Route Optimization / Path Replacement
Channel Info (Release 9.6(1) and later)
4231Route Optimization Switchover
Timestamp (Release 9.6(1) and later)
4232Rejecting Location Label (Release
9.6(1) and later)
4233Rejecting Location Label Direction
(Release 9.6(1) and later)
4236H323 Destination (Release 9.7 and
later)
4237Ingress Redirecting Number (Release
9.5(2) and later)
4239Service Usage Data (Release 9.7 and
later)
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-45
Detailed CDB Description
Chapter 1 Billing Interfaces
Table 1-19End of Call CDB Record (continued)
ANSI
Tag
ValueDescription
4240CNAM DIP (Release 9.7 and later)4240CNAM DIP (Release 9.7 and later)
4241Calling Name (Release 9.7 and later)4241Calling Name (Release 9.7 and later)
4242Terminating Remote SIP Host (Release
4243Terminating Local SIP Host (Release
4244License Rejecting Reason (Release 9.7
4245License Rejecting Direction (Release
4246SIP Transport4246SIP Transport (Release 9.7 and later)
4247SIP Routing URI Source4247SIP Routing URI Source (Release 9.7
4248SIP Routing URI4248SIP Routing URI (Release 9.7 and later)
5000Unique Call ID (Release 9 and later)5000Unique Call ID (Release 9 and later)
6005Interim CDB (Release 9.5(2) and later) 6005Interim CDB (Release 9.5(2) and later)
9.7 and later)
9.7 and later)
and later)
9.7 and later)
ITU
Tag
ValueDescription
4242Terminating Remote SIP Host (Release
4243Terminating Local SIP Host (Release
4244License Rejecting Reason (Release 9.7
4245License Rejecting Direction (Release
9.7 and later)
9.7 and later)
and later)
9.7 and later)
and later)
Slave End-of-Call CDB Record (Tag: 1210/Release 9.6 or Later)
Table 1-20 lists data about the Slave End-of-Call CDB type. This CDB is defined to be used at the
end-of-call for a non-controlling half-call instance. Only end-of -call summary style CDBs are issued
for slave half-call instances and the appropriate information is check-pointed to ensure the data is
successfully written in the event of a switchover occurring. This CDB is disabled by default on your
Cisco PGW 2200.
NoteIf you do enable this CDB and your network includes a Cisco BAMS, you must provision the Cisco
BAMS to ignore this CDB.
Table 1-20Slave End-of-Call CDB Record
Tag
Field Name
MGC Generic Tags
Call Reference ID4002
IAM Timepoint4003
REL Timepoint4006
Originating Trunk Group 4008
ValueComments
1-46
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Detailed CDB Description
Table 1-20Slave End-of-Call CDB Record (continued)
Tag
Field Name
ValueComments
Originating Member4009
Terminating Trunk Group4015
Terminating Member4016
RO/PR Executed4227Added in Release 9.6(1)
RO/PR Other Call Ref4228Added in Release 9.6(1)
Cisco Reserved Tags
Unique Call ID (Release 9 and later) 5000
Slave Long Duration Call CDB Record (Tag: 1260/Release 9.6 or Later)
Table 1-21 lists data about the Slave Long Duration Call CDB type. This CDB is used when the call
instance remains active beyond a pre-configured time. The long call duration timer of the slave call is
the same as that of “master” call which is configured in XECfgParm.dat.
Table 1-21Slave Long Duration Call CDB Record
Tag
Field Name
ValueComments
MGC Generic Tags
Call Reference ID4002
IAM Timepoint4003
Originating Trunk Group 4008
Originating Member4009
Terminating Trunk Group4015
Terminating Member4016
RO/PR Executed4227Added in Release 9.6(1)
RO/PR Other Call Ref4228Added in Release 9.6(1)
Cisco Reserved Tags
Unique Call ID (Release 9 and later) 5000
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-47
Chapter 1 Billing Interfaces
CDE Detail Description
CDE Detail Description
A call data element (CDE) is a field within the CDB that contains basic information about a billing
record. Examples of CDEs are the calling number and the called number.
The CDEs are described in the CDE description form template as shown in Table 1-22. CDE description
forms for each of the CDBs listed near the bottom in Table 1-22 are included in Table 1-23 through
Table 1-213.
Table 1-22CDE Description Form Template
Name: Name of the call data elementTa g: Its tag valueSource: MGC
subsystem that
generates the CDE
value
Description/Purpose: Brief description of the CDE
Format: The format of the CDE valueLength: CDE value length
Data Value: Range of CDE values, or valid values
Extended Data Value: This section includes CDE values that are extended (from the ANSI/ITU standard) by the Cisco MGC.
General Information: General information about the CDE and comments.
MGC Release: The Cisco MGC release(s)
supporting this CDE
1-48
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
CDEs Encoded in ANSI
Calling Party Category (Tag: 2000/ANSI)
Table 1-23Calling Party Category Description Form
Name: Calling Party CategoryTa g: 2000Source: MDL
Description/Purpose: Indicates what type of calling party is placing the call.
Format: ANSI T1.113Length in Octets: 1
Data Value:
The following codes are used in the calling party category (CPC) parameter field:
00000000 Calling party's category unknown (default)
00000001Operator, language French
00000010Operator, language English
00000011Operator, language German
00000100Operator, language Russian
00000101Operator, language Spanish
00000110|
00000111|-> Available to admin. For selecting a particular language.
00001000|
00001001Reserved
00001010Ordinary calling subscriber
00001011Ordinary calling subscriber with priority
00001100Data call
00000001Operator, language French
00001101Test call
00001110Spare
00001111Pay phone
00010000
toCCITT spare
11011111
11100000Emergency service call
11100001High priority emergency service call
11100010National security and emergency
11100011
toANSI spare
11110111
11110000
toNetwork-specific use
11111110
11111111Reserved
Extended Data Value: No extended value.
General Information:
MGC Release: Release 5.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-49
Chapter 1 Billing Interfaces
CDE Detail Description
User Service Information (Tag: 2001/ANSI)
Table 1-24User Service Information Description Form
Name: User Service InformationTag : 2001Source: MDL
Description/Purpose: This parameter is used to send the data transmission parameters to the distant exchange. The field
format is the same as the format for the bearer capability information element from ANSI standard T1.607.
Format: ANSI T1.113Length in Octets: 2 to 13
Data Value: For more detail, please refer to ANSI T1.113.
Extension: octet continues through the next octet, 1 last octet
Coding standard: the setting should be 00 for CCITT standard, 10 for national
Information Transfer Capability. For POTS calling, this field is set at one of the following:
00000 Speech
01000 Unrestricted digital information
01001 Restricted digital information
10000 3.1 kHz audio
10001 Unrestricted digital information with tone and announcements
Transfer Mode (octet 2)
00 Circuit mode
10 Packet mode
7.3 Information Transfer Rate
00000 Packet mode only
10000 64 kb
00011 384 kb
10100 1472 kb
10101 1536 kb
10111 1920 kb
11000 Multi-rate
Structure, Configuration, Establishment, and so on: please refer to T1.113
Extended Data Value: No extended value.
General Information:
1-50
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
Originating Line Information (Tag: 2002/ANSI)
Table 1-25Originating Line Information Description Form
Name: Originating Line InformationTa g: 2002Source: MDL
Description/Purpose: This information is captured from the originating line information parameter.
Format: ANSI T1.113Length in Octets: 1
Data Value:
00000000
to Binary equivalent of the digits
01100011
01100100
to Reserved
11111111
Extended Data Value: No extended value.
General Information:
MGC Release: Release 5.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-51
Chapter 1 Billing Interfaces
CDE Detail Description
Calling Number Nature of Address (Tag: 2003/ANSI)
Table 1-26Calling Number Nature of Address Description Form
Name: Calling Number Nature of AddressTa g: 2003Source: MDL
Description/Purpose: Indicates to the Cisco MGC how the number was delivered. It indicates the calling party type of
address. In POTS calling, two values are usually used: unique national number and nonunique national number.
Format: ANSI T1.113Length in Octets: 1
Data Value:
0000000 Spare
0000001 Unique subscriber number
0000010 Spare (national use)
0000011 Unique national number
0000100 Unique international number
0000101
to Spare
1110000
1110001 Nonunique subscriber number
1110010 Spare
1110011 Nonunique national number
111010 0 Nonunique international number
1110101 Spare
1110110 Spare
1110111 Test line
1111000
to Reserved
1111000
1111111 Spare
Extended Data Value: No extended value.
General Information:
MGC Release: Release 5.0 and later.
1-52
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
Charged Number Nature of Address (Tag: 2004/ANSI)
Table 1-27Charged Number Nature of Address Description Form
Name: Charged Number Nature of Address Ta g: 2004Source: MDL
Description/Purpose: Indicates to the Cisco MGC how the number was delivered.
Format: ANSI T1.113Length in Octets: 1
Data Value:
0000000 Spare
0000001Unique subscriber number
0000010 Spare (national use)
0000011 Unique national number
0000100 Unique international number
0000101
to Spare
1110000
1110001 Nonunique subscriber number
1110010 Spare
1110011 Nonunique national number
111010 0 Nonunique international number
1110101 Spare
1110110 Spare
1110111 Test line
1111000
to Reserved
1111000
1111111 Spare
Extended Data Value: No extended value.
General Information:
MGC Release: Release 5.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-53
Chapter 1 Billing Interfaces
CDE Detail Description
Dialed Number Nature of Address (Tag: 2005/ANSI)
Table 1-28Dialed Number Nature of Address Description Form
Name: Dialed Number Nature of AddressTag : 2005Source: MDL
Description/Purpose: Allows the Call Process to route a call differently based on the Nature of Address (NOA) value
provided in the IAM called number parameter. This tag represents the external (for example, line) value of NOA for the
called part number.
Format: ANSI T1.113Length in Octets: 1
Data Value:
0000000Spare - If the LEC doesn't know what type of line the calling party is, it will send this value to the Cisco MGC.
The Cisco MGC does not alter this value and does not do anything as far as billing with this field.
0000001Unique subscriber number
0000010 Spare (national use)
0000011 Unique national number
0000100 Unique international number
0000101
to Spare
1110000
1110001Nonunique subscriber number
1110010Spare
1110011Nonunique national number
111010 0Nonunique international number
1110101 Spare
1110110 Spare
1110111 Test line
1111000
to Reserved
1111000
1111111 Spare
Extended Data Value: No extended value.
General Information:
MGC Release: Release 5.0 and later.
1-54
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
LRN Nature of Address (Tag: 2006/ANSI)
Table 1-29LRN Nature of Address Description Form
Name: LRN Nature of AddressTag : 2006Source: MDL
Description/Purpose: Stores the NOA of LRN from an INAP query.
Format: ANSI T1.113Length in Octets: 1
Data Value:
0000000Spare
0000001Unique subscriber number
0000010 Spare (national use)
0000011 Unique national number
0000100 Unique international number
0000101
to Spare
1110000
1110001Nonunique subscriber number
1110010Spare
1110011Nonunique national number
111010 0Nonunique international number
1110101 Spare
1110110 Spare
1110111 Test line
1111000
to Reserved
1111000
1111111 Spare
Extended Data Value: No extended value.
General Information:
MGC Release: Release 5.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-55
Chapter 1 Billing Interfaces
CDE Detail Description
Called Number Nature of Address (Tag: 2007/ANSI)
Table 1-30Called Number Nature of Address Description Form
Name: Called Number Nature of AddressTag: 2007Source: MDL
Description/Purpose: The tag contains the Nature of Address (NOA) value from the egress protocol message used in the
outbound IAM. The NOA value in this tag is from the ingress protocol message. If no B number NOA is available
(redirected to an unknown number) but an original called number Information Element (IE) is available in the protocol
message, then the NOA from the IE is logged, and this can be modified for number normalization.
Format: ANSI T1.113Length in Octets: 1
Data Value:
0000000Spare - If the LEC doesn't know what type of line the calling party is, it will send this value to the Cisco MGC.
The Cisco MGC does not alter this value and does not do anything as far as billing with this field.
0000001Unique subscriber number
0000010 Spare (national use)
0000011 Unique national number
0000100 Unique international number
0000101
to Spare
1110000
1110001Nonunique subscriber number
1110010Spare
1110011Nonunique national number
111010 0Nonunique international number
1110101 Spare
1110110 Spare
1110111 Test line
1111000
to Reserved
1111000
1111111 Spare
Extended Data Value: No extended value.
General Information:
MGC Release: Release 5.0 and later.
1-56
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
Reason Code (Tag: 2008/ANSI)
Table 1-31Reason Code Description Form
Name: Reason CodeTag : 2008Source: MDL
Description/Purpose: Incorporates SS7 release with cause values and any additional reasons that the basic call model
determines.
Format: ANSI T1.113Length in Octets: 2
Data Value: The value of this field includes the first two octets of the cause indicators. Please refer to the ANSI T1.113
specification. (No diagnostic information included.)
Extended Data Value:
NoteTag 2008 extends ANSI definition by adding COT failure indicators according to ANSI rules, with slight
modification as follows:
Octet 1:
Extension 0
Coding Standard 11
Spare 0
Location 0011
Octet 2:
Extension 1
Cause 1111110
General Information:
MGC Release: Release 5.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-57
Chapter 1 Billing Interfaces
CDE Detail Description
Forward Call Indicators Received (Tag: 2009/ANSI)
Table 1-32Forward Call Indicators Received Description Form
Description/Purpose: This is for the received Forward Call Indicator parameter in ISUP message. It includes the following
fields: International Call Ind.; End To End Method Ind.; Interworking Ind.; IAM Segmentation Ind.; ISDN User Part Ind.;
ISDN User Part Preference Ind.; ISDN Access Ind.; and SCCP Method Ind.
Format: ANSI T1.113Length in Octets: 2
Data Value:
National/International call indicator Bit A—For POTS calling, Bit A should be coded as a 0, signifying that this is an
incoming national call. A coding of 1 signifies that the call is an incoming international call.
End-to-end method indicator Bits CB:
00 No end-to-end method available.
01 Pass along method available.
10 SCCP method available.
11 Both Pass along and SCCP methods available.
Interworking indicator Bit D—This field indicates to the Cisco MGC if any interworking has been encountered in the type
of signaling for this call. No pertinent information needs to be acted upon by the Cisco MGC; it should pass the information
to the destination. “0” means no interworking was encountered (SS7 all the way). “1” means interworking was encountered.
IAM Segmentation indicator Bit E—In POTS calling, this segmentation indicator is marked with a 0.
ISDN User Part indicator Bit F, HG, I: This is a more granular field for use by the ISUP. In the United States, the ISUP is
used exclusively. For POTS national numbers, this field is marked 1 for ISUP used all the way. That is, if the Interworking
indicator is set at 0 there was no interworking. If the incoming call has a 0 in this field, there was interworking or the
incoming international call could have used TUP for signaling before reaching the national network. The Cisco MGC
should not have to deal with this bit; it should pass it on to the destination. For more details, please refer to the ANSI T1.113
specification.
Extended Data Value:
General Information:
MGC Release: Release 5.0 and later.
1-58
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
Forward Call Indicators Sent (Tag: 2010/ANSI)
Table 1-33Forward Call Indicators Sent Description Form
Description/Purpose: This is for the sent Forward Call Indicator parameter in ISUP message. It includes the following
fields: International Call Ind.; End To End Method Ind.; Interworking Ind.; IAM Segmentation Ind.; ISDN User Part
Ind.; ISDN User Part Preference Ind.; ISDN Access Ind.; and SCCP Method Ind.
Format: ANSI T1.113Length in Octets: 2
Data Value: National/International call indicator Bit A—For POTS calling, Bit A should be coded as a 0, signifying
that this is an incoming national call. A coding of 1 signifies that the call is an incoming international call.
End-to-end method indicator Bits CB
00 No end to end method available.
01 Pass along method available.
10 SCCP method available.
11Both Pass along and SCCP methods available.
Interworking indicator Bit D—This field indicates to the Cisco MGC if any interworking has been encountered in the
type of signaling for this call. No pertinent information needs to be acted upon by the Cisco MGC; it should just pass
the information to the destination. “0” means no interworking encountered (SS7 all the way). “1” means interworking
was encountered.
IAM Segmentation indicator Bit E—In POTS calling, this segmentation indicator is marked with a 0.
ISDN User Part indicator Bit F, HG, I—This is a more granular field for use by the ISUP. In the United States, the ISUP
is used exclusively. For POTS national numbers, this field is marked 1 for ISUP used all the way. That is, if the
Interworking indicator is set at 0, there was no interworking. If the incoming call has a 0 in this field, there was
interworking or the incoming international call could have used TUP for signaling before reaching the national
network. The Cisco MGC should not have to deal with this bit; it passes it on to the destination. For more details, please
refer to the ANSI T1.113 specification.
Extended Data Value:
General Information:
MGC Release: Release 5.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-59
CDE Detail Description
Nature of Connection Indicators Received (Tag: 2011/ANSI)
Table 1-34Nature of Connection Indicators Received Description Form
Chapter 1 Billing Interfaces
Name: Nature of Connection Indicators
Tag : 2011Source: MDL
Received
Description/Purpose: Used to record the Nature of Connection received from the IAM. Three possible indicators can be
received: the satellite indicator, the continuity check indicator, and the echo suppressor indicator.
Format: ANSI T1.113Length in Octets: 1
Data Value:
Assume bit order HGFEDCBA
Satellite Indicator (Bits BA)—This field provides the Cisco MGC with information on how many satellites have been used
on this circuit. If the field is set to 00 and the Cisco MGC sends the circuit out on a circuit going over a satellite, the field
is incremented by one. The same goes for the other incoming settings (for example, 01 goes to 10 and 10 goes to 11). If
the outgoing circuit doesn't go over a satellite, the field is not incremented.
Continuity check indicator (Bits DC)—The Cisco MGC acts upon this field based on what is received. Also depending on
mutual agreements with the LECs, each outgoing trunk group sends Continuity tones to the terminating LECs with a
frequency between 0% to 100% of the time. This is configurable on a per trunk group basis. In addition, the Cisco MGC
interprets the incoming continuity field and passes the appropriate action to the Coding Unit.
Echo suppressor indicator (Bit E)—If this field is filled, the outgoing half echo control is already set on previous circuits,
there is no need for the terminating Cisco MGC to engage the EC. for this call. If the Cisco MGC activates the echo
canceller, this field needs to be set for the outgoing IAM message to subsequent switches.
Bits F-G: spare
Extended Data Value:
General Information:
MGC Release: Release 5.0 and later.
1-60
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Nature of Connection Indicators Sent (Tag: 2012/ANSI)
Table 1-35Nature of Connection Indicators Sent Description Form
CDE Detail Description
Name: Nature of Connection Indicators
Tag : 2012Source: MDL
Sent
Description/Purpose: Used to record the Nature of Connection sent. Three possible indicators can be sent: the satellite
indicator, the continuity check indicator, and the echo suppressor indicator.
Format: ANSI T1.113Length in Octets: 1
Data Value:
Assume bit order HGFEDCBA
Satellite Indicator (Bits BA)—This field provides the Cisco MGC with information on how many satellites have been used
on this circuit. If the field is set to 00 and the Cisco MGC sends the circuit out on a circuit going over a satellite, the field
is incremented by one. The same goes for the other incoming settings (for example, 01 goes to 10 and 10 goes to 11). If
the outgoing circuit doesn't go over a satellite, the field is not incremented.
Continuity check indicator (Bits DC)—The Cisco MGC acts upon this field based on what is received. Also depending on
mutual agreements with the LECs, each outgoing trunk group sends Continuity tones to the terminating LECs with a
frequency between 0% to 100% of the time. This is configurable on a per trunk group basis. In addition, the Cisco MGC
interprets the incoming continuity field and passes the appropriate action to the Coding Unit.
Echo suppressor indicator (Bit E)—If this field is filled, the outgoing half echo control is already set on previous circuits,
there is no need for the terminating Cisco MGC to engage the EC. for this call. If the Cisco MGC activates the echo
canceller, this field needs to be set for the outgoing IAM message to subsequent switches.
Bits F-G: spare
Extended Data Value:
General Information:
MGC Release: Release 5.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-61
Chapter 1 Billing Interfaces
CDE Detail Description
Transit Network Selection (Tag: 2013/ANSI)
Table 1-36Transit Network Selection Description Form
Description/Purpose: Includes Type of Network, Network Identification Plan, Digits, and Circuit Code.
Format: ANSI T1.113Length in Octets: 4
Data Value:
Network Identification Plan—The Network ID plan field indicates to the Cisco MGC what type of ID the parameter has.
Since POTS calling uses the National Network Plan, there are two values that pertain to the Cisco MGC: 3-digit CIC and
4-digit CAC.
National Network ID:
0000 Unknown
00104 Digit Carrier Identification Code—If this value is used, the layout of the parameter is the second figure.
0011
to Spare
0111
1000
to Reserved for network specific use
1111
Type of Network Identification—This field holds the type of network identification for the transit network parameter.
000 CCITT
010 National Network ID
Spare bit
Digits 1, 2, 3 or Digits 1, 2, 3, 4—These fields hold the Carrier Identification Code of the international transit carrier that
is required.
Circuit Code—The circuit code field indicates to the carrier how the call was dialed. The following values are found in this
field:
0000 Unknown
0001 International call, no operator
0010 International call, operator requested
Extended Data Value:
General Information:
MGC Release: Release 5.0 and later.
1-62
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
Carrier Identification Parameter (Tag: 2014/ANSI)
Table 1-37Carrier Identification Parameter Description Form
Description/Purpose: This is for the Carrier Identification Parameter in ISUP message. It includes the following fields:
Network Identification Plan; Type of Network Identification; Spare; Digit 1; Digit 2; Digit 3; Digit 4 or Null.
Format: ANSI T1.113Length in Octets: 3 or 4
Data Value:
Network Identification Plan (1st Octet, Bits 4321)—Indicates what type of Carrier Identification the caller is requesting.
The Cisco MGC looks at this field to determine whether the requested CIC is a 3 digit or 4 digit code and how many digits
to expect in the Digits field.
Type of Network Identification(1st Octet, Bits 765)—Gives the identification of the network numbering plan. For POTS
calls from the LECs, the value of this field is 010 (National Network ID).
Spare(1st Octet, Bits 8)—Not applicable
Digit 1-3 or 1-4 (remaining two octets, Bits 8765 are all zeros if only 3 digits present)—Requested CIC
Extended Data Value:
General Information:
MGC Release: Release 5.0 and later.
Carrier Selection Parameter (Tag: 2015/ANSI)
Table 1-38Carrier Selection Parameter Description Form
Description/Purpose: Indicates to the Cisco MGC how the caller dialed. This parameter can be used to determine how the
call will be routed. The parameter indicates to the Cisco MGC how the Carrier Access Code was dialed. With this
information and the Carrier Identification parameter, the Cisco MGC can route the call in a more granular fashion.
Format: ANSI T1.113Length in Octets: 1
Data Value:
00000000 No indication
00000001 Selected Carrier Identification Code presubscribed and not input by calling party
00000010 Selected Carrier Identification Code presubscribed and input by calling party
00000011 Selected Carrier Identification Code presubscribed; but no indication of whether input by calling party
00000100 Selected Carrier Identification Code not presubscribed and input by calling party
00000101
to Spare
11111110
11111111 Reserved
Extended Data Value:
General Information:
MGC Release: Release 5.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-63
Chapter 1 Billing Interfaces
CDE Detail Description
Jurisdiction Information Parameter (Tag: 2016/ANSI)
Table 1-39Jurisdiction Information Parameter Description Form
Name: Jurisdiction Information ParameterTag: 2016Source: MDL
Description/Purpose: This parameter provides numerical data indicating the geographic origination of the call.
Format: IA5Length in Octets: 6
Data Value: Digits from Jurisdiction Information Parameter.
Extended Data Value:
General Information:
MGC Release: Release 5.0 and later.
Redirecting Number Nature of Address (Tag 2017/ANSI)
Table 1-40Redirecting Number Nature of Address Description Form
Name: Called Number Nature of AddressTag : 2017Source: MDL
Description/Purpose: NOA of Redirecting Number.
Format: ANSI T1.113Length in Octet: 1
Data Value:
0000000 Spare
0000001 Unique subscriber number
0000010 Spare (national use)
0000011 Unique national number
0000100 Unique international number
0000101
to Spare
1110000
1110001 Nonunique subscriber number
1110010 Spare
1110011 Nonunique national number
111010 0 Nonunique international number
1110101 Spare
1110110 Spare
1110111 Test line
1111000
to Reserved
1111000
1111111 Spare
Extended Data Value: No extended value.
General Information:
MGC Release: Release 7.4.
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-64
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
Egress Calling Number Nature of Address (Tag 2018/ANSI)
Table 1-41Egress Calling Number Nature of Address Description Form
Name: Egress Calling Number NOATag : 2018Source: MDL
Description/Purpose: This CDE records the calling party NOA sent in the outgoing message by the MGC. This field
indicates the address type of the calling party. In POTS calling, there are usually two values that are used. They are Unique
National Number and Non-unique National Number.
Format: ANSI T1.113Length in Octet: 1
Data Value:
0000000 Spare
0000001 Unique subscriber number
0000010 Spare (national use)
0000011 Unique national number
0000100 Unique international number
0000101
to Spare
1110000
1110001 Nonunique subscriber number
1110010 Spare
1110011 Nonunique national number
1110100 Nonunique international number
1110101 Spare
1110110 Spare
1110111 Test line
1111000
to Reserved
1111000
1111111 Spare
Extended Data Value: No extended value.
General Information:
NoteThis CDE is present in the 1060 CDB if the End-of-Call CDB (1110) is configured. For point-in-call mode, the 1060
CDB is usually a short one and does not contain this CDB.
MGC Release: Release 9.5(2) patch xx.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-65
Chapter 1 Billing Interfaces
CDE Detail Description
Egress Redirecting Number Nature of Address (Tag 2019/ANSI)
Table 1-42Egress Redirecting Number Nature of Address Description Form
Name: Egress Redirecting Number NOATag : 2019Source: MDL
Description/Purpose: This CDE records the redirecting calling number NOA sent in the outgoing message by the MGC.
Format: ANSI T1.113Length in Octet: 1
Data Value:
0000000 Spare
0000001 Unique subscriber number
0000010 Spare (national use)
0000011 Unique national number
0000100 Unique international number
0000101
to Spare
1110000
1110001 Nonunique subscriber number
1110010 Spare
1110011 Nonunique national number
1110100 Nonunique international number
1110101 Spare
1110110 Spare
1110111 Test line
1111000
to Reserved
1111000
1111111 Spare
Extended Data Value: No extended value.
General Information:
NoteThis CDE is present in the 1060 CDB if the End-of-Call CDB (1110) is configured. For point-in-call mode, the 1060
CDB is usually a short one and does not contain this CDB.
MGC Release: Release 9.5(2) patch xx.
1-66
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Egress Original Called Number Nature of Address (Tag 2020/ANSI)
Table 1-43Egress Calling Number Nature of Address Description Form
CDE Detail Description
Name: Egress Original Called Number
Tag : 2020Source: MDL
NOA
Description/Purpose: This CDE records the original called party NOA sent in the outgoing message by the MGC.
Format: ANSI T1.113Length in Octet: 1
Data Value:
0000000 Spare
0000001 Unique subscriber number
0000010 Spare (national use)
0000011 Unique national number
0000100 Unique international number
0000101
to Spare
1110000
1110001 Nonunique subscriber number
1110010 Spare
1110011 Nonunique national number
1110100 Nonunique international number
1110101 Spare
1110110 Spare
1110111 Test line
1111000
to Reserved
1111000
1111111 Spare
Extended Data Value: No extended value.
General Information:
NoteThis CDE is present in the 1060 CDB if the End-of-Call CDB (1110) is configured. For point-in-call mode, the 1060
CDB is usually a short one and does not contain this CDB.
MGC Release: Release 9.5(2) patch xx.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-67
Chapter 1 Billing Interfaces
CDE Detail Description
CDE Encoded as ITU Recommendation
Calling Party Category (Tag: 3000/ITU)
Table 1-44Calling Party Category Description Form
Name: Calling Party CategoryTa g: 3000Source: MDL
Description/Purpose: Indicates what type of calling party is placing the call.
Format: ITU-T Q.763Length in Octets: 1
Data Value:
00000000 Calling party’s category is unknown (national use).
00000001 Operator, language French
00000010Operator, language English
00000011Operator, language German
00000100Operator, language Russian
00000101Operator, language Spanish
00000110
toAvailable to Administrations for selecting a particular language by mutual agreement
00001000
00001001 Reserved (Refer to Recommendation Q.104) Can be used in national networks to indicate that the calling party
is a national operator
00001010Ordinary calling subscriber
00001011Calling subscriber with priority
00001100Data call (voice band data)
00001101Test call
00001110Spare
00001111Payphone
00010000
toSpare
11011111
11100000
to Reserved for national use
11111110
11111111Spare
Note: The above values are for standard ITU SS7. Variants of ITU SS7 may have different values. Verify the values for
your variant with the appropriate specification, if necessary.
Extended Data Value: No extended value.
General Information:
MGC Release: Release 5.0 and later.
1-68
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
User Service Information (Tag: 3001/ITU)
Table 1-45User Service Information Description Form
Name: User Service InformationTag : 3001Source: MDL
Description/Purpose: Captures the User Service Information parameter of ITU-T ISUP.
Format: ITU-T Q.763Length in Octets: 2 to 13
Data Value:
876 5 4 32 1
1Ext.Coding StandardInformation Transfer Capability
2Ext.Transfer ModeInformation Transfer Rate
2aRate multiplier
3Ext.Layer identityUser information Layer 1 protocol
4Ext.Layer identityUser information Layer 2 protocol
5Ext.Layer identityUser information Layer 3 protocol
Notes:
1 Octet 2a is required if octet 2 indicates multirate (64 kbps base rate); otherwise it shall not be present.
2 Octets 3, 4, 5 or any combination of these octets may be omitted. Octet 3 may be extended as described in Table 4-6/Q.931
Note: The above values are for standard ITU SS7. Variants of ITU SS7 may have different values. Verify the values for
your variant with the appropriate specification, if necessary.
For French TUP, the following values apply:
876 5 4 32 1
1Ext.Coding Standard (00)Information Transfer Capability (Mapped from OptaddRoutingInf)
Supported Values:
01 Speech
10 3.1 kHz
11 64 kbps
2Ext.Transfer Mode (00)Information Transfer Rate (10000)
Extended Data Value: No extended value.
General Information:
MGC Release: Release 7.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-69
Chapter 1 Billing Interfaces
CDE Detail Description
Originating Line Information (Tag: 3002/ITU) Retired
Table 1-46Originating Line Information Description Form
Name: Originating Line InformationTa g: 3002Source: MDL
Description/Purpose: Indicates to the Cisco MGC what II digits are being sent from the LEC. This differentiates calls based
on the II digits.
Format: ITU-T Q.763Length in Octets: 1
Data Value:
Extended Data Value: No extended value.
General Information: For more information on II digits, refer to the Telecordia Local Exchange Routing Guide.
MGC Release: Release 7.0 and later.
Note: This tag was retired in Release 7.4. It is no longer associated with any CDBs.
Calling Number Nature of Address (Tag: 3003/ITU)
Table 1-47Calling Number Nature of Address Description Form
Name: Calling Number Nature of AddressTag : 3003Source: MDL
Description/Purpose: Indicates to the Cisco MGC how the number was delivered. This field indicates the address type of
the calling party. In POTS calling, there are usually two values that are used: Unique national number and Nonunique
national number.
Format: ITU-T Q.763Length in Octets: 1
Data Value:
0000000 Spare
0000001 Subscriber number (national)
0000010 Unknown (national)
0000011 National (significant) number
0000100 International number
0000101
to Spare
1101111
1110000
to Reserved for national use
1111110
1111111 Spare
Note: The above values are for standard ITU SS7. Variants of ITU SS7 may have different values. Verify the values for your
variant with the appropriate specification, if necessary.
Extended Data Value: No extended value.
General Information:
MGC Release: Release 7.0 and later.
1-70
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
Charged Number Nature of Address (Tag: 3004/ITU) Retired
Table 1-48Charged Number Nature of Address Description Form
Name: Charged Number Nature of Address Ta g: 3004Source: MDL
Description/Purpose: Indicates the address type of the calling party. In POTS calling, the value is typically Unique National
Number or Non-Unique National Number
Format: ITU-T Q.763Length in Octets: 1
Data Value:
0000000 Spare
0000001 Subscriber number (national)
0000010 Unknown (national)
0000011 National (significant) number
0000100 International number
0000101
to Spare
1101111
1110000
to Reserved for national use
1111110
1111111 Spare
Note: The above values are for standard ITU SS7. Variants of ITU SS7 may have different values. Verify the values for
your variant with the appropriate specification, if necessary.
Extended Data Value: No extended value.
General Information:
MGC Release: Release 7.0 and later. Retired in Release 9.1(2).
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-71
Chapter 1 Billing Interfaces
CDE Detail Description
Dialed Number Nature of Address (Tag: 3005)
Table 1-49Dialed Number Nature of Address Description Form
Name: Dialed Number Nature of AddressTag : 3005Source: MDL
Description/Purpose: This value allows the Call Process to route a call differently based on the Nature of Address value
provided in the IAM Called Number parameter.
Format: ANSI T1.113Length in Octets: 1
Data Value:
0000000 Spare
0000001 Subscriber number (national)
0000010 Unknown (national)
0000011 National (significant) number
0000100 International number
0000101
to Spare
1101111
1110000
to Reserved for national use
1111110
1111111 Spare
Note: The above values are for standard ITU SS7. Variants of ITU SS7 may have different values. Verify the values for
your variant with the appropriate specification, if necessary.
Extended Data Value: No extended value.
General Information:
MGC Release: Release 7.0 and later.
1-72
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
LRN Nature of Address (Tag: 3006/ITU)
Table 1-50LRN Nature of Address Description Form
Name: LRN Nature of AddressTag : 3006Source: MDL
Description/Purpose: Stores the NOA of LRN from an INAP query.
Format: ITU-T Q.763Length in Octets: 1
Data Value:
0000000 Spare
0000001 Subscriber number (national)
0000010 Unknown (national)
0000011 National (significant) number
0000100 International number
0000101
to Spare
1101111
1110000
to Reserved for national use
1111110
1111111 Spare
Note: The above values are for standard ITU SS7. Variants of ITU SS7 may have different values. Verify the values for
your variant with the appropriate specification, if necessary.
Extended Data Value: No extended value.
General Information:
MGC Release: Release 7.0 and later.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-73
Chapter 1 Billing Interfaces
CDE Detail Description
Called Number Nature of Address (Tag: 3007/ITU)
Table 1-51Called Number Nature of Address Description Form
Name: Called Number Nature of AddressTag : 3007Source: MDL
Description/Purpose: The tag contains the Nature of Address (NOA) value from the egress protocol message used in the
outbound IAM.The NOA value in this tag is from the ingress protocol message. If no B number NOA is available
(redirected to an unknown number) but an original called number Information Element (IE) is available in the protocol
message, then the NOA from the IE is logged, and this can be modified for number normalization.
Format: ITU-T Q.763Length in Octets: 1
Data Value:
0000000 Spare
0000001 Subscriber number (national)
0000010 Unknown (national)
0000011 National (significant) number
0000100 International number
0000101
to Spare
1101111
1110000
to Reserved for national use
1111110
1111111 Spare
Note: The above values are for standard ITU SS7. Variants of ITU SS7 may have different values. Verify the values for your
variant with the appropriate specification, if necessary.
Extended Data Value: No extended value.
General Information: The value may be modified during the call because of IN actions (for example, LNP).
MGC Release: Release 7.0 and later.
1-74
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
CDE Detail Description
Reason Code (Tag: 3008/ITU)
Table 1-52Reason Code Description Form
Name: Reason CodeTag : 3008Source: MDL
Description/Purpose: Incorporates C7 release with cause values and any additional reasons that the basic call model
determines.
Format: based on ITU-T Q.850Length in Octets: 2
Data Value:
Format:
876 5 4 321
1Ext.Coding StandardSpareLocation
2Ext.Cause value
Note: This CDE does not include the Diagnostic and Recommendation octets defined in Q.850. The format of this CDR is
the same for both Q.763 and Q.931 signaling.
Extension:
0 Octet continues through the next octet (for example, octet 1 to 1a)
1 Last octet
Coding Standard
00 ITU-T standardized coding
01 ISO/IEC standard
10 National standard
11 Standard specific to identified location
Note: The coding standards other than ITU-T should only be used when the desired cause value cannot be represented with
the ITU-T standardized codeing.
Location:
0000 User (U)
0001 Private network serving the local user (LPN)
0010 Public network serving the local user (LN)
0011 Transit network (TN)
0100 Public network serving the remote user (RLN)
0101 Private network serving the remote user (RPN)
0111 International network (INTL)
1010 Network beyond interworking point (BI)
1100
to Reserved for National use
1111
All other values are spare.
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-75
Chapter 1 Billing Interfaces
CDE Detail Description
Table 1-52Reason Code Description Form (continued)
Cause value: (only applicable in the context of Recommendations Q.763 and Q.931)
The cause value is divided into two fields, a class (bits 5 through 7) and a value within the class (bits 1 through 4).
The class indicates the general nature of the event. The valid values are as follows:
000 Normal event
001 Normal event
010 Resource unavailable
011 Service or option not available
100 Service or option not implemented
101 Invalid message (for example, parameter out of range)
110 Protocol error (for example, unknown message)
111 Interworking
The valid class values are listed in Table 1-53.
Extended Data Value:
NoteTag 3008 extends ANSI definition by adding COT failure indicators according to ANSI rules, with slight
modification as follows:
Octet 1:
Extension 0
Coding Standard 11
Spare 0
Location 0011
Octet 2:
Extension 1
Cause 1111110
General Information:
MGC Release: Release 7.0 and later.
The following table lists the Cause information element or parameter definitions for this tag.
Table 1-53Cause Information Element/Parameter Definitions
DSS 1, ISUP Q.931U, RPN,
that the called party cannot be reached
because, although the called party number is
in a valid format, it is not currently allocated
(assigned)
Reference
(Note 2)
Location
(Note 3)Remarks
LN
RLN, TN,
INTL
No route by
digit analysis
1-76
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
OL-1089-11
Chapter 1 Billing Interfaces
Table 1-53Cause Information Element/Parameter Definitions (continued)
CDE Detail Description
Cause
Class/Value/No. Definition
000/0010/2No route to specified transit network (national
use)—indicates that the equipment sending
this cause has received a request to route the
call through a particular transit network which
it does not recognize. The equipment sending
this cause does not recognize the transit
network either because the transit network
does not exist or because that particular transit
network, while it does exist, does not serve the
equipment which is sending this cause.
This cause is supported on a
network-dependent basis.
000/0010/3No route to destination—indicates that the
called party cannot be reached because the
network through which the call has been
routed does not serve the destination desired.
This cause is supported on a networkdependent basis.
000/0100/4Send special information tone— indicates that
the called party cannot be reached for reasons
that are of a long term nature and that the
special information tone should be returned to
the calling party.
000/0101/5Misdialled trunk prefix (national
use)—indicates the erroneous inclusion of a
trunk prefix in the called party number.
000/0110/6Channel unacceptable—indicates that the
channel most recently identified is not
acceptable to the sending entity for use in this
call.
000/0111/7Call awarded and being delivered in an
established channel—indicates that the user
has been awarded the incoming call, and that
the incoming call is being connected to a
channel already established to that user for
similar calls (for example, packet-mode X.25
virtual calls).
000/1000/8Preemption—indicates that the call is being
pre-empted.
000/1001/9Preemption – circuit reserved for
reuse—indicates that the call is being
pre-empted and the circuit is reserved for
reuse by the pre-empting exchange.
Application
(Note 1)
DSS 1,
Reference
(Note 2)
Location
(Note 3)Remarks
Q.931LN, TN
ISUP(NU)
DSS 1, ISUP Q.931U, RPN,
LN
ISUPClause 7/Q.35
ISUP(NU)
DSS 1Q.931LN
DSS 1Q.931LN
DSS 1, ISUP Q.735.3
MLPP
Q.955.3
ISUPQ.735.3MLPP
OL-1089-11
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-77
CDE Detail Description
Table 1-53Cause Information Element/Parameter Definitions (continued)
Chapter 1 Billing Interfaces
Cause
Class/Value/No. Definition
000/1110/14QoR:ported number—indicates that an
exchange detected that the called number was
ported out (see Annex C/Q.769.1)
001/0000/16Normal call clearing—indicates that the call
is being cleared because one of the users
involved in the call has requested that the call
be cleared.
Under normal situations, the source of this
cause is not the network.
001/0001/17User busy— indicates that the called party is
unable to accept another call because the user
busy condition has been encountered. This
cause value may be generated by the called
user or by the network. In the case of user
determine user busy, it is noted that the user
equipment is compatible with the call.
001/0010/18No user responding—used when a called
party does not respond to a call establishment
message with either an alerting or connect
indication within the prescribed period of
time allocated.
001/0011/19No answer from user (user alerted)—used
when the called party has been alerted but
does not respond with a connect indication
within a prescribed period of time.
NoteThis cause is not necessarily
generated by Q.931 procedures but
may be generated by internalnetwork
timers.
Application
(Note 1)
Reference
(Note 2)
Location
(Note 3)Remarks
ISUPQ.769.1LN
DSS 1, ISUP Q.931,
U, RPN
2.3/Q.764
DSS 1, ISUP Q.931,
Q.732,
U, RPN,
RLN
Q.733.3
DSS 1, ISUP Q.931,
RLNCall diversion
Q.732
DSS 1, ISUP Q.931RLN
2.1.4/Q.764,
2.9.8.3/
RLN, TN,
INTL
Q.764
Q.732RLNCall diversion
Basic call and
call diversion
services
services
Expiry of
waiting ANM
timer (T9)
services
001/0100/20Subscriber absent—used when a mobile
station has logged off, radio contact is not
obtained with a mobile station or if a personal
telecommunication user is temporarily not
addressable at any user-network interface.
001/0101/21Call rejected—indicates that the equipment
sending this cause does not wish to accept this
call, although it could have accepted the call
because the equipment sending this cause is
neither busy nor incompatible. This cause
may also be generated by the network,
indicating that the call was cleared due to a
supplementary service constraint..
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
1-78
DSS 1, ISUPMobile
application
DSS 1, ISUP Q.931U, RPN
Q.732RLNCall diversion
services
OL-1089-11
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.