SBC Sc610 Accounting

Oracle Communications Session
Border Controller
Accounting Guide
Release S-CX6.1.0
Formerly Net-Net Session Director
October 2013
Copyright 2013, year, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,
perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find
any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of
the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any
programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial
computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any
operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject
to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a risk of
personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its
affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used
under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo,
and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services
from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of
any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be
responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or
services.
About this Guide
Overview
The Oracle Communications Session Border Controller Accounting Guide describes:
The Net-Net SBCs accounting-based on Remote Authentication Dial-in

User Service (RADIUS)
How to configure RADIUS accounting support, and the features related to it
Local CDR storage and FTP file push
It includes the Acme Packet accounting Vendor-Specific Attributes (VSAs), and the
Cisco Systems, Inc. VSAs supported by the Net-Net SBC. This reference guide
indicates the Cisco Systems VSAs supported by Acme Packets Net-Net products.
This guide also includes RADIUS-related statistics and alarm information and
associated Acme Packet Command Line Interface (ACLI) configuration element
examples. Appendix A of this guide contains a selection of examples of RADIUS logs
for purposes of reference.
Supported
Platforms
Release Version S-CX6.3.0 is supported on the Net-Net 4500 and Net-Net 4250
platforms.
Related Documentation
The following table lists the members that comprise the documentation set for this
release:
Version S-C6.1.0
Document Name
Document Description
Acme Packet 4500 System

Hardware Installation Guide
Contains information about the components and

installation of the Acme Packet 4500 system.
ACLI Configuration Guide
Contains information about the administration and

software configuration SBC.
ACLI Reference Guide
Contains explanations of how to use the ACLI, as an

alphabetical listings and descriptions of all ACLI
commands and configuration parameters.
Maintenance and
Troubleshooting Guide
Contains information about Net-Net SBC logs,

performance announcements, system management,
inventory management, upgrades, working with
configurations, and managing backups and archives.
Oracle Communications Session Border Controller Accounting Guide iii
ABOUT THIS GUIDE
Document Name
Document Description
MIB Reference Guide
Contains information about Management

Information Base (MIBs), Enterprise MIBs, general
trap information, including specific details about
standard traps and enterprise traps, Simple Network
Management Protocol (SNMP) GET query
information (including standard and enterprise
SNMP GET query names, object identifier names and
numbers, and descriptions), examples of scalar and
table objects.
Accounting Guide
Contains information about the SBCs accounting

support, including details about RADIUS accounting.
Revision History
This section contains a revision history for this document.
Date
Revision Number
Description
August 1, 2008
Revision 1.10
Adds information about the Net-Net 4500

platform to About this Guide
August 21, 2010
Revision 2.00
Updates Local CDR Storage and FTP Push

section with detailed sftp configuration and
adds general clarifications
Integrates RADIUS CDR Redundancy seciton
into Local CDR Storage and FTP Push
Removes outdated information from Local
CDR Storage and FTP Push section
Notes deprecated parameters for FTP Push
feature
Updates Appendix C
Adds notes about VSAs 151-154
Corrects VSA 104 typo
August 26, 2010
Revision 2.01
Removes redundant Radius CDR Content

Control section
Updates VSAs 69 and 70 in description table to
correct data type
January 7, 2011
Revision 2.50
Creates new Appendix B to document CDR

output of specific application scenarios
iv Oracle Communications Session Border Controller Accounting Guide
Version S-C6.1.0
Contents
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iii
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Using RADIUS with the Net-Net SBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Standard RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Standard RADIUS Attributes Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
RADIUS Accounting Termination Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
VSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Acme Packet RADIUS VSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
New in Release S-C6.0.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Notes on Media Flow Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Acme Packet VSA Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Cisco Systems RADIUS Decodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Mappings and Disconnect Cause Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
SIP, H.323, and Q.850 Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
SIP Status to H.323 Disconnect Reason Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
SIP Status to H.323 RAS Error Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SIP Status to H.323 Release Complete Reason Error Mapping. . . . . . . . . . . . . . . . . . . . . . 30
Q.850 Cause to H.323 Release Complete Reason Mapping . . . . . . . . . . . . . . . . . . . . . . . . 30
SIP-SIP Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
SIP-H.323 Calls with Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
SIP Events and Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
H.323 Events and Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
H.225 RAS Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Version S-C6.1.0
Oracle Communications Session Border Controller Accounting Guide v
Configuring Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Accounting for SIP and H.323. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Call Detail Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
RAS Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
RADIUS Accounting Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Session Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
RADIUS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Session Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
ACLI Instructions and Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Accessing the Accounting and Accounting Servers Configuration . . . . . . . . . . . . . . . . . . .39
Setting Up the Account Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Setting Up Accounting Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Per Realm Accounting Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Configurable Intermediate Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
RADIUS CDR Content Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Accessing the Accounting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Preventing Duplicate RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
RADIUS Attribute Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Custom RADIUS CDR VSAs for SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
About User-Defined VSAs for SIP Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
HMR Adaptations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
HMR String Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
ACLI Instructions and Examples: User-Defined VSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
ACLI Instructions and Examples: String Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Trunk-Group VSA Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
ACLI Instructions and Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
RADIUS Account Server Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
How You Might User Server Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Accounting Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Local CDR Storage and FTP Push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Local CDR File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Local CDR File Format Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Local CDR File Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Local CDR File Storage Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Local CDR File Size and Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
vi Oracle Communications Session Border Controller Accounting Guide
Version S-C6.1.0
More About File Rotation Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

RADIUS CDR Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Caveats for H.323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
FTP Push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Deprecated ACLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Multiple Push Receivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Push Recievers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Secure FTP Push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
ACLI Instructions and Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Accessing the Accounting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Enabling Local CDR Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Setting the CSV File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Enabling FTP Push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
RADIUS Accounting Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Alarm Generation and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
RADIUS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Status and Statistics Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
ACLI Show RADIUS Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
CDR File Transfer Failure Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
RADIUS CDR Samples for SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Basic Successful SIP Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Unsuccessful SIP Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
SIP Call On Hold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Appendix B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
SIP: Call Tear Down Due to Media Guard Timer Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
CDR Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Appendix C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Net-Net 4000 S-C6.1.0 RADIUS Dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Appendix D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Local File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Start Record CSV Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Version S-C6.1.0
Oracle Communications Session Border Controller Accounting Guide vii
Interim Record CSV Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Stop Record CSV Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
viii Oracle Communications Session Border Controller Accounting Guide
Version S-C6.1.0
Using RADIUS with the Net-Net SBC
Introduction
RADIUS is an accounting, authentication, and authorization (AAA) system. In
general, RADIUS servers are responsible for receiving user connection requests,
authenticating users, and returning all configuration information necessary for the
client to deliver service to the user.
You can configure your Net-Net SBC to send call accounting information to one or
more RADIUS servers. This information can help you to see usage and QoS metrics,
monitor traffic, and even troubleshoot your system. For more information about
QoS, refer to the Admission Control and QoS chapter of the Net-Net 4000 ACLI
Configuration Guide.
For information about how to configure the Net-Net SBC for RADIUS accounting
use, refer to this guides Configuring Accounting (35) chapter.
Licensing
In order to use RADIUS with your Net-Net SBC, you must have the accounting
license installed and activated on your system. For more information about licensing,
see the Software Licensing section of the Net-Net 4000 ACLI Configuration Guides
Getting Started chapter. This chapter provides details about Acme Packet software
licensing, including instructions for how to obtain and install licenses.
Overview
For H.323, SIP, and calls being interworked between H.323 and SIP (IWF), you can
obtain sets of records that contain information to help you with accounting and that
provide a quantitative and qualitative measurement of the call. For H.323 and SIP
calls, the Net-Net SBC generates one set of records; for calls requiring IWF, the NetNet SBC generates two sets of records.
You can use the RADIUS records generated by your Net-Net SBC to assist you with:
Usage accountingSee the calling and called parties for a call, the protocol
used, the realm the call traversed (as well as local and remote IP address and
port information), and the codec used
Traffic monitoringYou can see information about the setup, connect, and
disconnect times, as well as the SIP or H.323 disconnect cause
SLA monitoringThe Net-Net SBC supports RADIUS attributes that provide

information about jitter, latency, and loss for H.323, SIP, and calls that require
interworking between H.323 and SIP
TroubleshootingObtain information about calls that can help you to identify

and address issues with quality and how calls are setup and torn down.
Standard RADIUS Attributes

This section describes the standard RADIUS attributes that the Net-Net SBC
supports. These attributes appear along with VSAs (Vendor-Specific Attributes) in
the CDRs that the Net-Net SBC generates.
Version S-C6.1.0
Oracle Communications Session Border Controller Accounting Guide 9
USING RADIUS WITH THE NET-NET SBC
The Standard RADIUS Attributes Dictionary (10) is a dictionary of the standard

RADIUS attributes included in Accounting Request messages sent by the Net-Net
SBC to the RADIUS server. The CDR event information determines which messages
are generated and which RADIUS attributes are included in the messages. Standard
RADIUS messages and attributes are used whenever possible; however, RADIUS
does not have attributes to record all important session information.
Possible messages are:
StartMarks the start of service delivery and describes the type of service being
delivered and the user to whom it is being delivered
Interim-UpdateIndicates to the accounting server that the session parameters

have changed
Stop
Marks the end of service delivery
Describes the type of service that was delivered
Sometimes describes statistics such as elapsed time, input and output
octets, or input and output packets
OnMarks the start of accounting
OffMarks the end of accounting
VSAs are used to record the necessary session information missing from this list of
standard RADIUS attributes.
For more information about RADIUS, see to the following Internet Engineering Task
Force Request for Comments (IETF RFCs):
Standard RADIUS
Attributes
Dictionary
RFC 2865, Remote Authentication Dial In User Service (RADIUS), Rigney, et

al., June 2000 (http://www.ietf.org/rfc/rfc2865.txt)
RFC 2866, RADIUS Accounting, C. Rigney, June 2000

(http://www.ietf.org/rfc/rfc2866.txt)
The table below lists and describes standard RADIUS attributes.
Attribute
Value
Attribute
Value
Type
Attribute Name
Attribute Description
NAS-IP-Address
IP address of the SIP proxy or the

H.323 stacks call signaling
address.
IP
address
Start
Interim-Update
Stop
On
Off
NAS-Port
SIP proxy port or the H.323 stacks

call signaling RAS port.
integer
Start
Interim-Update
Stop
On
Off
10 Oracle Communications Session Border Controller Accounting Guide
Messages
Version S-C6.1.0
Attribute
Value
Attribute
Value
Type
To field value of the SIP INVITE

message (a type of message used
to initiate a session) or the
calledPartyNumber of the H.323
message.
30
string
Start
Interim-Update
Stop
Calling-Station-Id
From field value of the SIP INVITE

message or the
callingPartyNumber of the
H.323 message.
31
string
Start
Interim-Update
Stop
NAS-Identifier
Value, if any, set in the optional

NAS-ID field for the accounting
server that you configure as part of
the accounting configuration. This
identifier sets the value that the
remote server (the accounting
server) uses to identify the Net-Net
SBC so that RADIUS messages can
be transmitted.
32
string
Start
Interim-Update
Stop
On
Off
Attribute Name
Called-Station-Id
Messages
The remote server to which the

accounting configuration will send
messages uses at least one of two
pieces of information for
identification:
NAS IP address: always
included in the accounting
message
NAS identifier: configured in the
NAS-ID parameter of the
accounting server; if configured,
the NAS identifier is sent to the
remote server
This attribute only appears if a
value is configured in the NAS-ID
field.
Version S-C6.1.0
Acct-Status-Type
Whether this Accounting Request

marks the beginning of the
RADIUS message (Start), the
middle (Interim-Update), or the end
(Stop), and whether the accounting
function is on or off (Accounting-On
or Accounting-Off).
40
integer
Start (1)
Interim-Update
Stop (2)
On
Off
Acct-Session-Id
Either the Call-ID field value of

the SIP INVITE message, the
callIdentifier of the H.323
message, or RADIUS client
information.
44
string
Start
Interim-Update
Stop
On
Off
Acct-SessionTime
How much time in seconds the

user has received service.
46
integer
Interim-Update
Stop
Off
Acct-TerminateCause
How or why the session ended.
49
integer
Stop
Off
RADIUS
Accounting
Termination
Causes
The table below describes the possible session termination causes for the AcctTerminate-Cause RADIUS attribute.
RADIUS
Termination
Cause
Related
Integer Value
(per RFC
2059)
Termination Event
Message
User Request
A SIP BYE message.
Stop
User Error
17
Input from user is erroneous; for example, SIP

signaling failed to establish the session. Used
in combination with the Cisco Systems
Disconnect Cause.
(This termination cause is not used for H.323.)
Stop
Lost Service
Service cannot be sustained for reasons such

as a lost connection.
Stop
Admin Reset
Net-Net SBC hard reset occurred: A hard reset

occurs when you use the front panels orange
Reset button; it reboots the Net-Net SBC.
Off
Admin Reboot
Net-Net SBC gracefully rebooted.
Off
NAS Request
10
RADIUS server is disabled; session terminated

for non-error reason.
Off
VSAs
This section describes the VSAs that the Net-Net SBC supports. These attributes
appear along with standard RADIUS attributes in the CDRs that the Net-Net SBC
generates.
VSAs are defined by vendors of remote access servers in order to customize how
RADIUS works on their servers. This section describes the accounting VSAs for
Acme Packet and for Cisco Systems.
Acme Packet
RADIUS VSAs
Acme Packets vendor identification number is 9148. This number refers to the 4octet VSA Vendor-ID field. The high-order octet is 0 and the low-order 3 octets are
the SMI Network Management Private Enterprise Code of the Vendor in network
byte order, defined in the Assigned Numbers RFC
(http://www.faqs.org/rfcs/rfc1700.html; Reynolds, J. and J. Postel, Assigned
Numbers, STD 2, RFC 1700, October 1994).
The table in this section is a dictionary of Acme Packets accounting VSAs. You can
use this information to translate the Acme Packet VSAs in Net-Net SBC RADIUS
messages into human-readable form. Acme Packet maintains VSA dictionary
definition files for the most popular RADIUS distributions; ask your Acme Packet
account representative for details.
Grouped according to attribute function, this table contains the following sections:
General Flow AttributesOverall traits of the media flow, these attributes

appear in all CDRs regardless of the sessions protocol; these attribute fields are
only populated if there are media flows
Version S-C6.1.0
Inbound Flow AttributesDetailed traits of the inbound media flow (including

realm, remote IP address and port, and local IP address and port); these attribute
fields are only populated if there are media flows
Outbound Flow AttributesDetailed traits of the outbound media flow

(including realm, remote IP address and port, and local IP address and port);
these attribute field are only populated if there are media flows
Session AttributesInformation about the protocol type, ingress and egress

realms used, and an identifier that links the H.323 and SIP legs of a call requiring
IWF
QoS AttributesRADIUS call records are instantiated by individual signaling

applications on the Net-Net SBC. The Net-Net SBC writes the following
additional parameters to the call record for QoS (Quality of Service):
RTP Lost packets
RTP Jitter
RTP Maximum Jitter
RTCP Lost packets
RTCP Jitter
RTCP Latency
RTCP Maximum Latency
RTP Total Packets
RTP Total Octets
Only RADIUS Stop records contain QoS information. For non-QoS calls, the
attributes appear in the record, but their values are always be zero (0). When you
review the list of QoS VSAs, please note that calling in the attribute name
means the information is sent by the calling party and called in the attribute
name means the information is sent by the called party.
Examples of how this information appears in CDRs appears in Appendix A (65) of
this guide. Please note that the contents of Interim-Update messages do not depend
on what events cause a Start message to be generated.
New in Release SC6.0.0
The Net-Net SBC reports R-Factor and MOS data for the calling and called
segments at the end of a session. This information appears in RADIUS CDRs, and in
the Acme Packet VSA dictionary:
Acme-Calling-R-Factor (151)
Acme-Calling-MOS (152)
Acme-Called-R-Factor (153)
Acme-Called-MOS (154)
Note: These values are reported as * 100 in order to appear as integers.
Notes on Media Flow

Attributes
The Net-Net SBC records media flow attributes in RADIUS CDRs, and there can be
multiple flows per session. In order to distinguish between the two flows that appear
for a basic session (forward and reverse), the Net-Net SBC supports unique media
flow attribute names.
The term flow-set represents a pair of media flows, where one is the forward flow
and one is the reverse. The flow attributes described in the table below have the
Version S-C6.1.0
designation FS1 or FS2, which identifies it as either the first or the second flow-set.
In addition, all non-QoS attributes have a direction indicator: F for forward, and R
for reverse.
Attribute Name
Attribute
Value
Attribute
Value Type
Messages
General Attributes
Acme-CDR-SequenceNumber
Sequence number (that increases by 1)

the Net-Net SBC generates; recorded in
each CDR.
59
integer
Start
Interim-Update
Stop
Acme-IntermediateTime
Time interval at which periodic interim

records are generated during a call.
63
string
Interim-Update
Acme-Local-Time-Zone
Local GMT/UTC time zone that is

provisioned on the Net-Net SBC.
57
string
Start
Interim-Update
Stop
Acme-FirmwareVersion
Current software version running on the

Net-Net SBC.
56
string
Start
Interim-Update
Stop
Acme-User-Class
Identifies the type user on the Net-Net

SBC; used for RADIUS authentication
only and does not apply to accounting.
254
string
Start
Stop
Unique identifier for every media flow

processed by the Net-Net SBC, flow-set 1
forward direction.
string
Start
Interim-Update
Stop
On
Off
78
string
Start
Interim-Update
Stop
On
Off
90
string
Start
Interim-Update
Stop
On
Off
112
string
Start
Interim-Update
Stop
On
Off
string
Start
Interim-Update
Stop
On
Off
General Flow Attributes

Acme-FlowID_FS1_F
This VSA always prefaces other flow

information.
Acme-FlowID_FS1_R

reverse direction.
information.
Acme-FlowID_FS2_F

forward direction.
information.
Acme-FlowID_FS2_R

reverse direction.
information.
Acme-FlowType_FS1_F
Codec that describes the flow, flow-set 1

forward direction: PCMU, PCMA, G726,
G723, G728, G729, H261, H263, T38.
Version S-C6.1.0
Attribute
Value
Attribute
Value Type

reverse direction: PCMU, PCMA, G726,
G723, G728, G729, H261, H263, T38.
79
string
Start
Interim-Update
Stop
On
Off
Acme-FlowType_FS2_F

forward direction: PCMU, PCMA, G726,
G723, G728, G729, H261, H263, T38.
91
string
Start
Interim-Update
Stop
On
Off
Acme-FlowType_FS2_R

reverse direction: PCMU, PCMA, G726,
G723, G728, G729, H261, H263, T38.
113
string
Start
Interim-Update
Stop
On
Off
Acme-Flow-InRealm_FS1_F
Inbound realm identifier for flow-set 1,

forward direction.
10
string
Start
Interim-Update
Stop
Acme-Flow-InRealm_FS1_R

reverse direction.
80
string
Start
Interim-Update
Stop
Acme-Flow-InRealm_FS2_F

forward direction.
92
string
Start
Interim-Update
Stop
Acme-Flow-InRealm_FS2_R

reverse direction.
114
string
Start
Interim-Update
Stop
Acme-Flow-In-SrcAddr_FS1_F
Inbound source address (remote)

information for flow-set 1, forward
direction.
11
IP address
Start
Interim-Update
Stop
Acme-Flow-In-SrcAddr_FS1_R

information for flow-set 1, reverse
direction.
81
IP address
Start
Interim-Update
Stop
Acme-Flow-In-SrcAddr_FS2_F

direction.
93
IP address
Start
Interim-Update
Stop
Acme-Flow-In-SrcAddr_FS2_R

direction.
115
IP address
Start
Interim-Update
Stop
Acme-Flow-In-SrcPort_FS1_F
Inbound source (remote) port information

for flow-set 1, forward direction.
12
integer
Start
Interim-Update
Stop
Acme-Flow-In-SrcPort_FS1_R

for flow-set 1, reverse direction.
82
integer
Start
Interim-Update
Stop
Attribute Name
Acme-FlowType_FS1_R
Messages
Inbound Flow Attributes
Version S-C6.1.0
Attribute
Value
Attribute
Value Type

for flow-set 2, forward direction.
94
integer
Start
Interim-Update
Stop
Acme-Flow-In-SrcPort_FS2_R

for flow-set 2, reverse direction.
116
integer
Start
Interim-Update
Stop
Acme-Flow-In-DstAddr_FS1_F
Inbound destination (local) address

information (the IPv4 address field value
of the steering pool configuration) for
flow-set 1, forward direction.
13
IP address
Start
Interim-Update
Stop
Acme-Flow-In-DstAddr_FS1_R

flow-set 1, reverse direction.
83
IP address
Start
Interim-Update
Stop
Acme-Flow-In-DstAddr_FS2_F

95
IP address
Start
Interim-Update
Stop
Acme-Flow-In-DstAddr_FS2_R

117
IP address
Start
Interim-Update
Stop
Acme-Flow-In-DstPort_FS1_F
Inbound destination (local) port

information (a port in the range between
the start port and end port field values of
the steering pool configuration) for flowset 1, forward direction.
14
integer
Start
Interim-Update
Stop
Acme-Flow-In-DstPort_FS1_R

the steering pool configuration) for flowset 1, reverse direction.
84
integer
Start
Interim-Update
Stop
Acme-Flow-In-DstPort_FS2_F

the steering pool configuration) for flowset 2, forward direction.
96
integer
Start
Interim-Update
Stop
Acme-Flow-In-DstPort_FS2_R

the steering pool configuration) for flowset 2, reverse direction.
118
integer
Start
Interim-Update
Stop
Acme-Flow-OutRealm_FS1_F
Outbound realm identifier for flow-set 1,

forward direction.
20
string
Start
Interim-Update
Stop
Acme-Flow-OutRealm_FS1_R

reverse direction.
85
string
Start
Interim-Update
Stop
Attribute Name
Acme-Flow-In-SrcPort_FS2_F
Messages
Outbound Flow Attributes
Version S-C6.1.0
Version S-C6.1.0
Attribute
Value
Attribute
Value Type

forward direction.
97
string
Start
Interim-Update
Stop
Acme-Flow-OutRealm_FS2_R

reverse direction.
119
string
Start
Interim-Update
Stop
Acme-Flow-Out-SrcAddr_FS1_F
Outbound source (local) address

of the steering port configuration) for
21
IP address
Start
Interim-Update
Stop
Acme-Flow-Out-SrcAddr_FS1_R

86
IP address
Start
Interim-Update
Stop
Acme-Flow-Out-SrcAddr_FS2_F

98
IP address
Start
Interim-Update
Stop
Acme-Flow-Out-SrcAddr_FS2_R

120
IP address
Start
Interim-Update
Stop
Acme-Flow-Out-SrcPort_FS1_F
Outbound source (local) port information

for flow-set 1, forward direction (a port in
the range between the start port and end
port field values of the steering port
configuration).
22
integer
Start
Interim-Update
Stop
Acme-Flow-Out-SrcPort_FS1_R

for flow-set 1, reverse direction (a port in
configuration).
87
integer
Start
Interim-Update
Stop
Acme-Flow-Out-SrcPort_FS2_F

for flow-set 2, forward direction (a port in
configuration).
99
integer
Start
Interim-Update
Stop
Acme-Flow-Out-SrcPort_FS2_R

for flow-set 2, reverse direction (a port in
configuration).
121
integer
Start
Interim-Update
Stop
Acme-Flow-Out-DstAddr_FS1_F
Outbound destination (remote) address

direction.
23
IP address
Start
Interim-Update
Stop
Acme-Flow-Out-DstAddr_FS1_R

direction.
88
IP address
Start
Interim-Update
Stop
Attribute Name
Acme-Flow-OutRealm_FS2_F
Messages
Attribute
Value
Attribute
Value Type

direction.
100
IP address
Start
Interim-Update
Stop
Acme-Flow-Out-DstAddr_FS2_R

direction.
122
IP address
Start
Interim-Update
Stop
Acme-Flow-Out-DstPort_FS1_F
Outbound destination (remote) port

direction.
24
integer
Start
Interim-Update
Stop
Acme-Flow-Out-DstPort_FS1_R

direction.
89
integer
Start
Interim-Update
Stop
Acme-Flow-Out-DstPort_FS2_F

direction.
101
integer
Start
Interim-Update
Stop
Acme-Flow-Out-DstPort_FS2_R

direction.
123
integer
Start
Interim-Update
Stop
Common ID shared by H.323 and SIP call

legs of a session. This attribute is a
combination of a time stamp (measured
in seconds) and a monotonically
increasing 16-bit integer, followed by an
at-sign (@) and the MAC address of the
rear interface (wancom).
This attribute is only used to correlate the
H.323 and SIP legs of an interworking
call/session.
40
string
Start
Interim-Update
Stop
Attribute Name
Acme-Flow-Out-DstAddr_FS2_F
Messages
Session Attributes
Acme-Session-GenericId
This VSA is not configurable; all CDRs

contain this attribute.
Acme-Session-IngressCallId
Call ID generated by the originating

device.
string
Start
Interim-Update
Stop
Acme-Session-EgressCallId
Call ID generated by the Net-Net SBC to

represent a two-way transaction.
string
Start
Interim-Update
Stop
Acme-Session-IngressRealm
Explicitly identifies the ingress realm, and

contains the name of the ingress realm
for the session. All CDRs contain this
attribute.
41
string
Start
Interim-Update
Stop

Version S-C6.1.0
Attribute Name
Acme-Session-EgressRealm
Explicitly identifies the egress realm, and

contains the name of the egress realm
for the session. All CDRs contain this
attribute.
Attribute
Value
Attribute
Value Type
42
string
Start
Interim-Update
Stop
43
string
Start
Interim-Update
Stop
54
string
Start
Interim-Update
Stop
55
string
Start
Interim-Update
Stop
Messages
This VSA is not configurable. All CDRs

contain this attribute, but it is only
populated if an egress realm is found; a
call without a route does not have an
egress realm.
Acme-Session-ProtocolType
Signaling protocol used for a particular

leg of a session (in the case of IWF, there
may be two legs). This attribute contains
the signaling protocol type; for example,
SIP or H323.
Acme-SessionCharging-Vector
Appears when the Net-Net SBC inserts,

passes, or deletes the P-Charging-Vector
header (SIP).
This attribute is only populated for SIP
CDRs, and is not populated if the Net-Net
SBC does not have P-Charging-Vector
information.
Acme-SessionChargingFunction_Address
Appears when the Net-Net SBC inserts,

passes, or deletes the P-ChargingFunction-Address.
This attribute is only populated for SIP
CDRs, and is not populated if the Net-Net
SBC does not have P-Charging-FunctionAddress information.
Version S-C6.1.0
Acme-SessionDisposition
Status of the call attempt as it

progresses from being initiated (using a
SIP INVITE or H.323 Setup message) to
being either answered or failing to be
answered.
60
integer
Start
Interim-Update
Stop
Acme-Post-Dial-Delay
Amount of time between session

initiation and an alerting event.
58
integer
Start
Interim-Update
Stop
Acme-P-Asserted-ID
P-Asserted ID as described in RFC 3325.
69
string
Start
Interim-Update
Stop
Acme-SIP-Diversion
SIP Diversion header; communicates to

the called party from whom and why a
call diverted.
70
string
Start
Interim-Update
Stop
Acme-Primary-RoutingNumber
Primary routing number and phone

context (or ingress SIP Request-URI).
64
string
Start
Interim-Update
Stop
Attribute
Value
Attribute
Value Type
Messages
Final routing number and phone context

(or egress SIP Request-URI).
134
integer
Stop
Acme-DisconnectInitiator
Initiator of a call disconnect.
61
integer
Stop
Acme-DisconnectCause
Q.850 cause code value.
62
integer
Stop
Acme-SIP-Status
SIP status code for RFC 3326 support.
71
integer
Stop
Acme-OriginatingTrunk-Group
Originating trunk group.
65
string
Start
Interim-Update
Stop
Acme-OriginatingTrunk-Context
Originating trunk group context.
67
string
Start
Interim-Update
Stop
Acme-TerminatingTrunk-Group
Terminating trunk group.
66
string
Start
Interim-Update
Stop
Acme-TerminatingTrunk-Context
Terminating trunk group context.
68
string
Start
Interim-Update
Stop
Acme-Ingress-LocalAddr
Signaling IP address and port of the

ingress Net-Net SBC signaling interface.
74
string
Start
Interim-Update
Stop
Acme-Ingress-RemoteAddr

ingress remote signaling element.
75
string
Start
Interim-Update
Stop
Acme-Egress-LocalAddr

egress Net-Net SBC signaling interface.
76
string
Start
Interim-Update
Stop
Acme-Egress-RemoteAddr

destination signaling element.
77
string
Start
Interim-Update
Stop
Acme-Session-IngressRPH
RPH value received in the incoming call

(e.g., ets.1).
135
string
Start
Interim-Update
Stop
136
string
Start
Interim-Update
Stop
Attribute Name
Acme-Egress-FinalRouting-Number
Only populated for NSEP calls.

Acme-Session-EgressRPH
RPH value sent in the outgoing call (e.g.,

ets.3).
Only populated for NSEP calls.
Acme-Ingress-NetworkInterface-Id
To differentiate overlapping IP address

spaces (with the Acme-Ingress-Vlan-TagValue), gives the ID of the ingress
network interface.
137
string
Start
Interim-Update
Stop
Acme-Ingress-Vlan-TagValue

spaces (with the Acme-Ingress-NetworkInterface-Id), gives the VLAN tag.
138
integer
Start
Interim-Update
Stop
Version S-C6.1.0
Attribute
Value
Attribute
Value Type

spaces (with the Acme-Egress-Vlan-TagValue), gives the ID of the ingress
network interface.
139
string
Start
Interim-Update
Stop
Acme-Egress-Vlan-TagValue

spaces (with the Acme-Egress-NetworkInterface-Id), gives the VLAN tag.
140
integer
Start
Interim-Update
Stop
Acme-Refer-CallTransfer-Id
For SIP REFER call method transfer,

communicates a call has been
transferred from the referer to the
referree
141
string
Stop
Total lost packets reported via Real-time

Transport Protocol Control Protocol
(RTCP), flow-set 1.
32
integer
Stop
104
integer
Stop
33
integer
Stop
105
integer
Stop
34
integer
Stop
106
integer
Stop
35
integer
Stop
107
integer
Stop
Attribute Name
Acme-Egress-NetworkInterface-Id
Messages
QoS Attributes
Acme-Calling-RTCPPackets-Lost_FS1
Populated only if QoS is enabled.

Acme-Calling-RTCPPackets-Lost_FS2
Total lost packets measured on RTP

packets in milliseconds, flow-set 2.
Acme-Calling-RTCPAvg-Jitter_FS1
Average jitter reported via RTCP

measured in milliseconds, flow-set 1.
Acme-Calling-RTCPAvg-Jitter_FS2

measured in milliseconds, flow-set 2.
Acme-Calling-RTCP-Avg
Latency_FS1
Average latency reported by comparing

the timestamps in RTCP packets for each
direction of a call, flow-set 1.
Acme-Calling-RTCP-Avg
Latency_FS2
Average latency reported by comparing

the timestamps in RTCP packets for each
direction of a call, flow-set 2.
Acme-Calling-RTCPMaxJitter_FS1
Maximum amount of jitter value reported

via RTCP measured in milliseconds, flowset 1.
Acme-Calling-RTCPMaxJitter_FS2
Maximum amount of jitter value reported

via RTCP measured in milliseconds, flowset 3.
Version S-C6.1.0
Attribute Name
Acme-Calling-RTCPMaxLatency_FS1
Maximum latency value measured in

milliseconds as observed through RTCP,
flow-set 1.
Attribute
Value
Attribute
Value Type
Messages
36
integer
Stop
108
integer
Stop
28
integer
Stop
102
integer
Stop
29
integer
Stop
103
integer
Stop
37
integer
Stop
109
integer
Stop
38
integer
Stop
110
integer
Stop
39
integer
Stop
111
integer
Stop

Acme-Calling-RTCPMaxLatency_FS2
Maximum latency value measured in

milliseconds as observed through RTCP,
flow-set 2.
Acme-CallingOctets_FS1
Bytes of RTP traffic for this call, flow-set

1.
Acme-CallingOctets_FS2
Bytes of RTP traffic for this call, flow-set

2.
Acme-CallingPackets_FS1
RTP packets for this call, flow-set 1.

Acme-CallingPackets_FS2
RTP packets for this call, flow-set 2.

Acme-Calling-RTPPackets-Lost_FS1

Acme-Calling-RTPPackets-Lost_FS2

Acme-Calling-RTP-AvgJitter_FS1
Total jitter measured on RTP packets in

milliseconds, flow-set 1.
Acme-Calling-RTP-AvgJitter_FS2
Total jitter measured on RTP packets in

milliseconds, flow-set 2.
Acme-Calling-RTPMaxJitter_FS1
Maximum jitter measured on RTP

Acme-Calling-RTP-AvgMaxJitter_FS2
Maximum jitter measured on RTP

Version S-C6.1.0
Attribute Name
Acme-CalledOctets_FS1
Bytes of RTP traffic for the ingress side of

the call, flow-set 1.
Attribute
Value
Attribute
Value Type
Messages
44
integer
Stop
124
integer
Stop
45
integer
Stop
125
integer
Stop
46
integer
Stop
126
integer
Stop
47
integer
Stop
127
integer
Stop
48
integer
Stop
128
integer
Stop
49
integer
Stop

Acme-CalledOctets_FS2
Bytes of RTP traffic for the ingress side of

the call, flow-set 2.
Acme-CalledPackets_FS1
RTP packets for the ingress side of the

call, flow-set 1.
Acme-CalledPackets_FS2
RTP packets for the ingress side of the

call, flow-set 2.
Acme-Called-RTCPPackets-Lost_FS1
Total lost packets measured on RTCP

packets in milliseconds for the ingress
side of the call, flow-set 1.
Acme-Called-RTCPPackets-Lost_FS2
Total lost packets measured on RTCP

Acme-Called-RTCP-AvgJitter_FS1

measured in milliseconds for the ingress
Acme-Called-RTCP-AvgJitter_FS2

Acme-Called-AvgLatency_FS1
Average latency reported via RTCP

Acme-Called-AvgLatency_FS2
Average latency reported via RTCP

Acme-Called-RTCPMaxJitter_FS1
Maximum amount of jitter reported via

RTCP measured in milliseconds for the
ingress side of the call, flow-set 1.
Version S-C6.1.0
Attribute Name
Acme-Called-RTCPMaxJitter_FS2

Attribute
Value
Attribute
Value Type
Messages
129
integer
Stop
50
integer
Stop
130
integer
Stop
51
integer
Stop
131
integer
Stop
52
integer
Stop
132
integer
Stop
53
integer
Stop
133
integer
Stop
151
integer
Stop

Acme-Called-RTCPMaxLatency_FS1
Maximum amount of latency reported via

Acme-Called-RTCPMaxLatency_FS2
Maximum amount of latency reported via

Acme-Called-RTPPackets-Lost_FS1

Acme-Called-RTPPackets-Lost_FS2

Acme-Called-RTP-AvgJitter_FS1
Average jitter reported via RTP measured

in milliseconds for the ingress side of the
realm, flow-set 1.
Acme-Called-RTP-AvgJitter_FS2
Average jitter reported via RTP measured

in milliseconds for the ingress side of the
realm, flow-set 2.
Acme-Called-RTPMaxJitter_FS1

RTP measured in milliseconds for the
ingress side of the call, flow-set1.
Acme-Called-RTPMaxJitter_FS2

RTP measured in milliseconds for the
Acme-Calling-R-Factor
QoS R-Factor calculation for the calling

side of a session.
This value is reported as * 100 in order to
appear as an integer.
Version S-C6.1.0
Attribute Name
Acme-Calling-MOS
QoS MOS calculation for the calling side

of a session.
Attribute
Value
Attribute
Value Type
Messages
152
integer
Stop
153
integer
Stop
154
integer
Stop

Acme-Called-R-Factor
QoS R-Factor calculation for the called

side of a session.
Acme-Called-MOS
QoS MOS calculation for the called side

of a session.
Acme Packet VSA

Values
The table below defines the possible values for several Acme Packet VSAs.
Acme Packet VSA

Name
Version S-C6.1.0
Attribute Value
Possible Values
Acme-PostDialDelay
58
Unit value in milliseconds
Acme-SessionDisposition
60
0=unknown
1=call_attempt
2=ringing
3=answered
Acme-DisconnectInitiator
61
0=UNKNOWN_DISCONNECT_INITIATOR
1=CALLING_PARTY_DISCONNECT
2=CALLED_PARTY_DISCONNECT
3=INTERNAL_DISCONNECT
Acme Packet VSA

Name
Acme-DisconnectCause
Attribute Value
Possible Values
62
34=No circuit/channel available

47=Resource unavailable
3=No route destination
31=Normal, unspecified
88=Incompatible destination
111=Interworking, unspecified
38=Network out of order
42=Switching equip congestion
28=Invalid number format
41=Temporary failure
17=User busy
16=Normal call clearing
20=Subscriber absent
31=Normal call clearing
Version S-C6.1.0
Acme Packet VSA

Name
Attribute Value
Possible Values
Acme-SIPDiversion
70
SIP Diversion header based on this RFC draft: draftlevy-sip-diversion-05.txt
Acme-SIP-Status
71
This is a complete list of support status codes; only a

subset would be reported in a Stop record:
Cisco Systems
RADIUS Decodes
Version S-C6.1.0
RESP_STATUS_TRYING 100
RESP_STATUS_RINGING 180
RESP_STATUS_FORWARD
181
RESP_STATUS_QUEUED 182
RESP_STATUS_PROGRESS
183
RESP_STATUS_OK
200
RESP_STATUS_CREATED 201
RESP_STATUS_ACCEPTED
202
RESP_STATUS_PART
206
RESP_STATUS_MAX_OK
299
RESP_STATUS_MULTIPLE
300
RESP_STATUS_MOVED 301
RESP_STATUS_MOVED_TMP
302
RESP_STATUS_USE_PROXY
305
RESP_STATUS_ALTERNATE
380
RESP_STATUS_BAD
400
RESP_STATUS_UNAUTH 401
RESP_STATUS_PAY_REQ 402
RESP_STATUS_FORBIDDEN
403
RESP_STATUS_NOT_FOUND
404
RESP_STATUS_NOT_ALLOW
405
RESP_STATUS_NOT_ACCEPT 406
RESP_STATUS_AUTH_REQ
407
RESP_STATUS_REQ_TMO
408
RESP_STATUS_CONFLICT
409
RESP_STATUS_GONE
410
RESP_STATUS_LEN_REQ 411
RESP_STATUS_TOO_BIG 413
RESP_STATUS_URI_TOO_BIG 414
RESP_STATUS_MEDIA
415
RESP_STATUS_URI_SCHEME
416
RESP_STATUS_BAD_EXT 420
RESP_STATUS_EXT_REQ 421
RESP_STATUS_TOO_SMALL
422
RESP_STATUS_TOO_BRIEF
423
RESP_STATUS_TMP_UNAVAIL 480
RESP_STATUS_NO_EXIST
481
RESP_STATUS_LOOP
482
RESP_STATUS_TOOMNY_HOPS 483
RESP_STATUS_ADDR_INCMPL 484
RESP_STATUS_AMBIGUOUS
485
RESP_STATUS_BUSY_HERE
486
RESP_STATUS_CANCELLED
487
RESP_STATUS_NOT_HERE
488
RESP_STATUS_BAD_EVENT
489
RESP_STATUS_PENDING 491
RESP_STATUS_UNDECIPH
493
RESP_STATUS_INT_ERR 500
RESP_STATUS_NOT_IMPL
501
RESP_STATUS_BAD_GTWY
502
RESP_STATUS_SVC_UNAVAIL 503
RESP_STATUS_GTWY_TMO
504
RESP_STATUS_BAD_VER 505
RESP_STATUS_MSG_TOO_BIG 513
RESP_STATUS_PRE_FAIL 580
RESP_STATUS_BUSY
600
RESP_STATUS_DECLINE 603
RESP_STATUS_DONT_EXIST
604
RESP_STATUS_NOTACCEPT
606
The following table is a dictionary of the Cisco Systems (vendor identification

number is 9) accounting VSAs. These attribute names are vendor-specific and
subject to change without notice.
You can use the information in this table to translate the Cisco Systems VSAs that
sometimes appear in Net-Net SBC RADIUS messages into a more human-readable
form.
Attribute
Value
Attribute
Value
Type
Time that a SIP INVITE or H.323 SETUP

message was received. The SETUP
message is used to request a connection
(and therefore corresponds with the SIP
INVITE).
25
string
Start
Stop
Connect Time
Time that a SIP or H.323 session was

accepted. This is the time a 200 OK SIP
response to the SIP INVITE message was
received or the time that a call
ANSWERED/CONNECTED response to the
H.323 SETUP message was received.
28
string
Start
InterimUpdate
Stop
Disconnect
Time
Time that a SIP BYE or H.323 Release

Complete message was received or the
session terminated. This is the time a SIP
INVITE or H.323 SETUP transaction
terminates for any reason.
29
string
Stop
Disconnect
Cause
SIP Reasons for Disconnection (normal,

redirection, client error, network error,
global error, time-out, or user abandon) or
the H.323 Release Complete Reason code
(bad format address, unavailable,
destination rejection, adaptive busy, etc.).
30
string
Stop
Attribute Name
Setup Time
Messages
For more information, refer to this guides

Mappings and Disconnect Cause Values (28)
section.
Mappings and Disconnect Cause Values

This section provides information about H.323 and SIP disconnect cause values for
RADIUS CDRs generated by the Net-Net SBC.
SIP, H.323, and

Q.850 Mappings
This section provides tables that show the mappings between SIP Status and: H.323
Disconnect Reason, H.323 Release Complete Reason, and RAS error. It also shows
the mapping for Q.850 cause to H.323 Release Complete Reason.
SIP Status to H.323

Disconnect Reason
Mapping
SIP Status
H.323 Disconnect Reason
480 Temporarily Unavailable
No Bandwidth
404 Not Found
Gatekeeper Resource
404 Not Found
Unreachable Destination
Version S-C6.1.0
SIP Status
H.323 Disconnect Reason
603 Decline
Destination Rejection
505 Version Not Supported
Invalid Revision
401 Unauthorized
No Permission
503 Service Unavailable
Unreachable Gatekeeper
Gateway Resource
400 Bad Request
Bad Format Request
486 Busy Here
Adaptive Busy
486 Busy Here
In Conference
500 Internal Server Error
Undefined Reason
486 Busy Here
Facility Call Deflection
401 Unauthorized
Security Denied
SIP Status
H.323 RAS Error
404 Not Found
Gatekeeper Resource
401 Unauthorized
Invalid Permission
Request Denied
Undefined
401 Unauthorized
Caller Not Registered
305 User Proxy
Route Call to Gatekeeper
Invalid Endpoint ID
Resource Unavailable
401 Unauthorized
Security Denial
501 Not Implemented
QoS Control Not Supported
484 Address Incomplete
Incomplete Address
302 Moved Temporarily
Route Call to SCN
485 Ambiguous
Aliases Inconsistent
401 Unauthorized
Not Currently Registered
SIP Status to H.323

RAS Error Mapping
Version S-C6.1.0
SIP Status to H.323

Release Complete
Reason Error Mapping
Q.850 Cause to H.323

Release Complete
Reason Mapping
SIP Status
H.323 RAS Error
300 Multiple Choices
Undefined Reason
401 Unauthorized
Security Denied
402 Payment Required
Undefined Reason
403 Forbidden
No Permission
404 Not Found
405 Method Not Allowed
Undefined Reason
606 Not Acceptable
Undefined Reason
407 Proxy Authentication Required
Security Denied
408 Request Timeout
Adaptive Busy
409 Conflict
Undefined Reason
410 Gone
411 Length Required
Undefined Reason
414 Request-URI Too Large
Bad Format Address
415 Unsupported Media Type
Undefined Reason
420 Bad Extension
Bad Format Address
Adaptive Busy
481 Call/Transaction Does Not Exist
Undefined Reason
482 Loop Detected
Undefined Reason
483 Too Many Hops
Undefined Reason
Bad Format Address
The table below describes how the Q.850 Causes and the H.323 release complete
reasons are mapped internally on the Net-Net SBC.
Q.850 Cause
Numeric Code
H.323 Release Complete Reason
Not Route To Destination
Normal Call Clearing
16
Destination Rejection
User Busy
17
In Conference
Subscriber Absent
20
Called Party Not Registered
Invalid Number Format
28
Bad Format Address
Normal Unspecified
16
Undefined Reason
No Circuit/Channel Available
34
No Bandwidth
Network Out of Order
38
Version S-C6.1.0
SIP-SIP Calls
Q.850 Cause
Numeric Code
H.323 Release Complete Reason
Temporary Failure
41
Adaptive Busy
Switching Equipment Congestion
42
Gateway Resource
47
Gatekeeper Resource
Incompatible Destination
88
Invalid Revision
Interworking Unspecified
111
No Permission
The Net-Net SBC maps SIP status codes and events to disconnect cause attribute
values used by Cisco Systems Proxy Server (CSPS) accounting services.
SIP Status Category/Event
CDR Disconnect Cause
Description
Undetermined reason
Undetermined reason
BYE
Normal clearing
3xx: Redirection
Redirection
4xx: Client Error
Client error
5xx: Server Error
Server error
6xx: Global Failure
Global error
SIP-H.323 Calls
with Interworking
For calls that require SIP-H.323 interworking, the Net-Net SBC generates two sets
of RADIUS CDRs: one for the SIP call-leg and one for the H.323 call leg. The values
recorded in RADIUS Stop records for the disconnect cause depend on the nature
and source of the call disconnect or rejection.
SIP Events and Errors
For calls rejected or disconnected because of SIP events and errors, the Net-Net SBC
records Q.850 cause values mapped from the SIP event/status code in the SIP CDR.
For the H.323 CDR, the SIP status categories and events are mapped to Q.850 cause
codes.
The entries in this table are determined by the SIP Status to H.323 Release Complete
Reason Error Mapping (30).
Version S-C6.1.0
SIP CDR Disconnect

Cause
H.323 Disconnect Cause Value (Q.850)
BYE
16Normal call clearing
3xx
23Redirection to new
destination
404 Not Found
21Call rejected
3No route to destination
410 Gone
21Call rejected
H.323 Events and

Errors
SIP CDR Disconnect

Cause
H.323 Disconnect Cause Value (Q.850)
403 Forbidden
21Call rejected
111Interworking unspecified
413 Request Entity Too Big
21Call rejected
28Invalid number format
414 Request URI Too Large
21Call rejected
420 Bad Extension
21Call rejected
21Call rejected
408 Request Timeout
21Call rejected
41Temporary failure
480 Temporarily
unavailable
21Call rejected
41Temporary failure
486 Busy Here
21Call rejected
17User Busy
401 Unauthorized
21Call rejected
32Normal unspecified
407 Proxy Authentication

Required
21Call rejected
All other 4xx
21Call rejected
502 Bad Gateway
38Network out of
order
505 Bad Version
38Network out of
order
88Incompatible destination
All other 5xx
38Network out of
order
600 Busy Everywhere
41Temporary failure
603 Decline
604 Does Not Exist

Anywhere
All other 6xx
The Q.850 cause code value is recorded for the disconnect cause in the CDR for the
H.323 call leg if the Q.850 cause is received. H.323 recommendations state that
either Q.850 Cause of RelCompReason is mandatory for the RELEASE COMPLETE;
the Cause information element (IE) is optional everywhere. The Cause IE and the
ReleaseCompleteReason (part of the release complete message) are mutually
exclusive.
If a Q.850 cause code is not received, the Net-Net SBC records a Q.850 cause value
mapped from the received ReleaseCompleteReason as defined in the table below.
Version S-C6.1.0
The entries in this table are determined by the SIP Status to H.323 Disconnect
Reason Mapping (28).
H.225 RAS Errors
Version S-C6.1.0
H.323
ReleaseCompleteReason
H.323 CDR
Disconnect Cause
No Bandwidth
34No
channel/circuit
available
480 Temporarily
Unavailable
21Call rejected
Gatekeeper Resource
47Resource
unavailable
404 Not Found
21Call rejected
3No route to
destination
404 Not Found
21Call rejected
Destination Rejected
31Normal
unspecified
603 Decline
31Normal
unspecified
Invalid Revision
88Incompatible
destination
505 Version Not

Supported
38Network out of
order
No Permission
111Interworking
unspecified
401 Unauthorized
21Call rejected
38Network out of
order
503 Service
Unavailable
38Network out of
order
Gateway Resource
42Switching
equipment
congestion
480 Temporarily
unavailable
21Call rejected
Bad Format Request
28Invalid number
format
400 Bad request
21Call rejected
Adaptive Busy
41Temporary failure
486 Busy Here
21Call rejected
In Conference
17User busy
486 Busy Here
21Call rejected
Undefined Reason
16Normal
unspecified
500 Internal Server

Error
38Network out of
order
Called Party Not

Registered
20Subscriber
absent
404 Not Found
21Call rejected
31Normal call
clearing
New Connection Needed
47Resource
Unavailable
401 Unauthorized
21Call rejected
SIP Status
SIP CDR Disconnect

Cause
For calls that are rejected because of H.225 RAS, there is no CDR generated for the
H.323 call leg as no Setup message is generated. The Net-Net SBC maps RAS errors
to SIP Status as specified in the table below.The SIP CDR disconnect cause values
are the same as the CSPS disconnect cause values already mentioned and defined.
The entries in this table are determined by the SIP Status to H.323 RAS Error
Mapping (29).
H.225 RAS Error
SIP Status
SIP CDR Disconnect Cause
Called Party Not Registered
404 Not Found
21Call Rejected
Invalid Permission
401 Unauthorized
21Call Rejected
Request Denied
38Network out of order
Undefined
401 Unauthorized
21Call Rejected
Route Call to Gatekeeper
305 Use Proxy
23Redirection to new destination
Invalid Endpoint ID
Security Denial
401 Unauthorized
21Call Rejected
QoS Control Not Supported
501 Not Implemented
Incomplete Address
21Call Rejected
Route Call to SCN
302 Moved Temporarily
2Redirection
Aliases Inconsistent
485 Ambiguous
21Call Rejected
Not Currently Registered
401 Unauthorized
21Call Rejected
Version S-C6.1.0
Configuring Accounting
Overview
This chapter provides you with information about configuring RADIUS accounting
on your Net-Net SBC.
The Net-Net products support Net-Net SBC RADIUS accounting, including these
essential configurations and specialized features:
Accounting for SIP and H.323
Local CDR storage on the Net-Net SBC, including CSV file format settings-
The ability to send CDRs via FTP to a RADIUS sever
Per-realm accounting control
Configurable intermediate period
RADIUS CDR redundancy
RADIUS CDR content control
Accounting for SIP and H.323

This section explains SIP and H.323 accounting using the RADIUS Accounting
System (RAS).
For accounting purposes, the Net-Net SBC uses RADIUS to send accounting
messages. These messages are transmitted to one of a predefined list of accounting
servers using a predefined forwarding strategy. RAS provides a mechanism for
temporarily storing session initiation and completion statistics and for delivering
these statistics to accounting servers located elsewhere in the network.
Call Detail Records
The Net-Net SBC supports CDRs through RADIUS reporting with additional VSAs
to include information that is not available with the standard RADIUS session
information. CDRs provide billing information on sessions traversed through a
system, as well as troubleshooting information, fraud detection, fault diagnostics,
and service monitoring.
CDRs can contain information about recent system usage such as the identities of
sources (points of origin), the identities of destinations (endpoints), the duration of
each call, the amount billed for each call, the total usage time in the billing period,
the total free time remaining in the billing period, and the running total charged
during the billing period.VSAs are defined by vendors of remote access servers in
order to customize how RADIUS works on their servers.
RAS Overview
The RAS acts as a RADIUS client. It provides a mechanism for generating accounting
information in CDRs. The CDRs are transmitted to a RADIUS server in UDP
datagrams, using RADIUS Accounting Request messages.
The RAS receives RADIUS accounting messages when different events occur. The
event and CDR event trigger list information determines which RADIUS messages,
Version S-C6.1.0
CONFIGURING ACCOUNTING
if any, are included, as well as which RADIUS attributes are included. The library
adds RADIUS messages to the waiting queue only when the message is ready to be
sent. The SIP proxy needs to populate the CDR as session information becomes
available so, by the time the session ends, it contains the information necessary to
generate all of the messages.
The RADIUS accounting client process manages its queue and a list of servers. The
servers each have a UDP connection and manage their own pending message
queues. Changes in the state of the server connection might cause interaction with
the client process waiting queue.
When RADIUS messages are added to the RAS waiting queue, the RAS sends them
to a server based on strategy. If the RAS is configured to transmit all the messages
when the session ends, all the messages are sent to the same server. Each session
continues logging messages according to the event logging scheme in effect when
the session began (for example, when the CDR was created).
The RAS notifies the RADIUS server with Accounting-On/Off messages when the
RASs entry for that server is enabled/disabled. The response to the Accounting-On
message is the RASs first determination of RTT, and serves as notification that the
server is reachable. Until the Accounting-On response is received, the server cannot
send other messages.
RADIUS Accounting
Client
The RADIUS accounting client process has a local socket at which it accepts RADIUS
messages. RADIUS messages received on the local socket are added to the waiting
queue for transmission to a RADIUS server. The waiting queue is a first-in, first-out
(FIFO) queue.
The RADIUS accounting client process sends messages to a server queue based on
the configuration (servers configured/enable/connected, as well as the strategy).
Messages that return from a server (due to server failure/disabling) are first in the
FIFO queue.
The RADIUS accounting client process interfaces with the RADIUS accounting
servers using the RADIUS protocol with the VSAs outlined above.
The RADIUS server collects a variety of information that can be used for accounting
and for reporting on network activity. The RADIUS client sends information to
designated RADIUS servers when the user logs on and logs off. The RADIUS client
might send additional usage information on a periodic basis while the session is in
progress. The requests sent by the client to the server to record logon/logoff and
usage information are generally called accounting requests.
RADIUS accounting permits a RADIUS server to track when users commence and
terminate their connections. Typical accounting information includes the following:
Full user name
RAS identification name or IP address
RAS port number
Time connection started
When a client is configured to use RADIUS accounting, it generates an Accounting

Start packet describing the type of service being delivered and the user it is being
delivered to at the start of service delivery. It sends that packet to the RADIUS
Accounting server, which sends back an acknowledgement that the packet has been
received. At the end of service delivery, the client generates an Accounting Stop
Version S-C6.1.0
packet describing the type of service that was delivered and, optionally, statistics
such as elapsed time, input and output octets, or input and output packets. It sends
that packet to the RADIUS Accounting server, which sends back an
acknowledgement that the packet has been received. The Accounting-Request
(whether for Start or Stop) is submitted to the RADIUS accounting server through
the network.
Transactions between the client and RADIUS accounting server are authenticated
through the use of a shared secret, which is never sent over the network.
Session
Accounting
The RAS client can record SIP, H.323, and IWF session activity based on
configuration and a CDR. The CDR determines which messages are generated and
determines the RADIUS attributes included in the messages. The RAS client must
be capable of sending CDRs to any number of RADIUS accounting servers, using the
defined hunt, failover, round robin, fewest pending, or fastest server strategies.
The establishment, failed establishment, change, or removal of a session can trigger
RADIUS Accounting Request messages. The RAS might also send notification of its
status (enabled/disabled). RADIUS Accounting Request messages include the
following:
StartSession has started.
Interim-UpdateSession parameters have changed.
StopSession has ended.
Accounting-OnCreation of a new RADIUS client.
Accounting-OffRADIUS client has shut down.
Each session might generate Start, Interim-Update, and Stop messages based on the
local configuration when the session is initiated. Each Start message tells the
RADIUS server that a session has started. Each Interim-Update message changes
the session parameters, and may report the session characteristics for the session to
that point. Each Stop message informs the RADIUS server that a session has ended
and reports session characteristics.
The RAS has the ability to transmit all RADIUS messages related to a session at the
end of the session, regardless of which messages are generated and when they are
generated. Some customers might choose this option to reduce the likelihood of the
RADIUS messages being logged to different servers, or in different log files on the
same server.
The RAS always generates a RADIUS Stop message when the session ends,
regardless of the session termination cause. The termination cause and the session
characteristics are reported.
Version S-C6.1.0
RADIUS Messages
The following table identifies the relationship between the signaling elements and
the RADIUS attributes included in Accounting Request messages to the RADIUS
server.
RADIUS Attribute
Data Element
Message
NAS IP-Address
IP address of the SIP proxy or the H.323

stacks call signal address.
Start, InterimUpdate, Stop, On,

Off
NAS Port
SIP proxy port or the H.323 stacks call

signaling RAS port.

Off
NAS Identifier
Value, if any, set in the optional NAS-ID field

for the accounting server that you configure as
part of the accounting configuration. This
identifier sets the value that the remote server
(the accounting server) uses to identify the
Net-Net SBC so that RADIUS messages can be
transmitted.

Off
The remote server to which the accounting

configuration will send messages uses at least
one of two pieces of information for
identification:
NAS IP address: always included in the
accounting message
NAS identifier: configured in the NAS-ID
parameter of the accounting server; if
configured, the NAS identifier is sent to the
remote server
This attribute only appears if a value is
configured in the NAS-ID field.
Acct-Session-ID
Either the Call-ID field value of the SIP INVITE

message, the callIdentifier of the
H.323 message, or RADIUS client information.

Off
Called Station ID
To field value of the SIP INVITE message (a

type of message used to initiate a session) or
the calledPartyNumber of the H.323
message.
Start, InterimUpdate, Stop
Calling Station ID
From field value of the SIP INVITE message

or the callingPartyNumber of the H.323
message.
Start, InterimUpdate, Stop
Acct-Terminate-Cause
Reason for session ending (refer to Session

Termination session).
Stop, Off
Acct-Session-Time
Length of session (time in seconds).
Interim-Update,
Stop, Off
Version S-C6.1.0
Session Termination
Sessions are terminated for reasons that include normal termination, signaling
failure, timeout, or network problems. The following table maps RADIUS
accounting termination cause codes to network events.
RADIUS Termination
Cause
Event
Message
User request
SIP BYE message or H.323
Stop
User error
SIP signaling failed to establish session

(accompanied by disconnect cause)
Stop
NAS request
RADIUS server disabled
Off
ACLI Instructions
and Examples
This section tells you how to access and set parameters for RADIUS accounting
support. To use the Net-Net SBC with external RADIUS (accounting) servers to
generate CDRs and provide billing services requires, you need to configure account
configuration and account server list.
Accessing the
Accounting and
Accounting Servers
Configuration
To configure the account configuration and account servers:

1.
In Superuser mode, type configure terminal and press <Enter>.
2.
Type session-router and press <Enter> to access the system-level configuration

elements.
ACMEPACKET# configure terminal
ACMEPACKET(configure)# session-router
3.
Type account-config and press <Enter>. The system prompt changes to let you
know that you can begin configuring individual parameters.
ACMEPACKET(session-router)# account-config
ACMEPACKET(account-config)#
4.
To configure account server parameters (a subset of the account configuration

parameters, type account-servers and press <Enter>. The system prompt
changes to let you know that you can begin configuring individual parameters.
ACMEPACKET(account-config)# account-servers
ACMEPACKET(account-server)#
Setting Up the
Account Configuration
You set the account configuration parameters to indicate where you want accounting
messages sent, when accounting messages you want them sent, and the strategy you
want used to select account servers.
To configure the account configuration:
Version S-C6.1.0
1.
hostnameDefaults to and must remain localhost.
2.
portRetain the default value of 1813 or enter the number of the UDP port
associated with the Net-Net SBC from which RADIUS messages are sent.
minimum: 1025
maximum: 65535
3.
strategyIndicate the strategy you want used to select the accounting servers
to which the Net-Net SBC will send its accounting messages. The following
table lists the available strategies:
Strategy
Description
hunt
Selects accounting servers in the order in which they are

listed.
If the first accounting server is online, working, and has
not exceeded any of the defined constraints, all traffic is
sent to it. Otherwise the second accounting server is
selected. If the first and second accounting servers are
offline or exceed any defined constraints, the third
accounting server is selected. And so on through the
entire list of configured servers
failover
Uses the first server in the list of predefined accounting

servers until a failure is received from that server. Once a
failure is received, it moves to the second accounting
server in the list until a failure is received. And so on
through the entire list of configured servers.
round robin
Selects each accounting server in order, distributing the

selection of each accounting server evenly over time.
fastest round trip time
Selects the accounting server that has the fastest round

trip time (RTT) observed during transactions with the
servers (sending a record and receiving an ACK).
fewest pending
Selects the accounting server that has the fewest

number of unacknowledged accounting messages (that
are in transit to the Net-Net SBC).
4.
stateRetain the default value enabled if you want the account configuration
active on the system. Enter disabled if you do not want the account
configuration active on the system.
5.
max-msg-delayRetain the default value of 60 seconds or indicate the length

of time in seconds that you want the Net-Net SBC to continue trying to send
each accounting message. During this delay, the Net-Net SBC can hold a
generic queue of 4096 messages.
6.
Minimum: zero (0)
Maximum: 232-1
max-wait-failoverRetain the default value of 100 messages or indicate the

maximum number of accounting messages the Net-Net SBC can store its
message waiting queue for a specific accounting server, before it is considered a
failover situation.
Once this value is exceeded, the Net-Net SBC attempts to send it accounting
messages, including its pending messages, to the next accounting server in its
configured list.
7.
Minimum: one (1) message
Maximum: 4096 messages
trans-at-closeRetain the default value of disabled if you do not want to defer

the transmission of message information to the close of a session. Enter enabled
if you want to defer message transmission.
disabledThe Net-Net SBC transmits accounting information at the start

of a session (Start), during the session (Interim), and at the close of a session
Version S-C6.1.0
(Stop). The transmitted accounting information for a single session might

span a period of hours and be spread out among different storage files.
8.
enabledLimits the number of files on the Net-Net SBC used to store the
accounting message information for one session. It is easiest to store the
accounting information from a single session in a single storage file.
generate-startRetain the default value ok if you want the RADIUS Start

message to be generated once the Net-Net SBC receives an OK message in
response to an INVITE. (A RADIUS Start message informs the accounting server
that a SIP session has started.)
Other options include:
9.
StartRADIUS Start message should not be generated.
InviteRADIUS Start message should be generated once the Net-Net SBC

receives a SIP session INVITE.
generate-interimRetain the default value reinvite response to cause the

Net-Net SBC to transmit a RADIUS Interim message. (A RADIUS Interim
message indicates to the accounting server that the SIP session parameters have
changed.)
You can select none, one, or more than one of the following values:
Option
Description
ok
RADIUS Start message is generated when the Net-Net

SBC receives an OK message in response to an INVITE.
reinvite
RADIUS Interim message is generated when the Net-Net

SBC receives a SIP session reINVITE message.
reinvite response (default)

SBC receives a SIP session reINVITE and responds to it
(for example, session connection or failure).
reinvite cancel

SBC receives a SIP session reINVITE, and the Reinvite is
cancelled before the Net-Net SBC responds to it.
unsuccessful-attempt
RADIUS Interim message is generated when a SIP

session set-up attempt from a preference-ordered list of
next-hop destinations is unsuccessful. This can happen
when a local policy lookup, LRT lookup, ENUM query
response, or SIP redirect returns a preference-ordered
list of next-hop destinations. The interim message
contains: the destination IP address, the disconnect
reason, a timestamp for the failure, and the number that
was called.
10. account-serverCreate the account server list to store accounting server

information for the account configuration. Each account server can hold 100
accounting messages. See the next section for step-by-step instructions.
Account server entries are specific to the account configuration. They cannot be
viewed or accessed for editing outside of the account configuration.
Note: RADIUS will not work if you do not enter one or more servers in
a list.
Setting Up Accounting
Servers
Version S-C6.1.0
You must establish the list of servers to which the Net-Net SBC can send accounting
messages.
1.
hostnameName of the host associated with the account server in hostname

format (FQDN) or as an IP address.
2.
portRetain the default 1813 or enter the number of the UDP port associated
with the account server to which RADIUS messages are sent.
minimum: 1025
maximum: 65535
3.
stateRetain the default enabled to enable the account servers on the system
or enter disabled to disable them.
4.
min-round-tripRetain the default 250 milliseconds or indicate the minimum

round trip time of an accounting message.
minimum: 1025 milliseconds
maximum: 65535 milliseconds
A round trip consists of the following:

The Net-Net SBC sends an accounting message to the account server.
The account server processes this message and responds back to the Net-Net
SBC.
If the fastest RTT is the strategy for the account configuration, the value you
enter here can be used to determine an order of preference (if all the configured
account servers are responding in less than their minimum RTT).
5.
max-inactivityRetain the default 60 seconds or indicate the length of time in

seconds that you want the Net-Net SBC with pending accounting messages to
wait when it has not received a valid response from the target account server.
minimum: 1 second
maximum: 300 seconds
Once this timer value is exceeded, the Net-Net SBC marks the unresponsive
account server as disabled in its failover scheme. When a server connection is
marked as inactive, the Net-Net SBC attempts to restart the connection and
transfers pending messages to another queue for transmission. RADIUS
messages might be moved between different account servers as servers become
inactive or disabled.
6.
7.
restart-delayRetain the default 30 seconds or indicate the length of time in

seconds you want the Net-Net SBC to wait before resending messages to a
disabled account server.
minimum: 1 second
maximum: 300 seconds
bundle-vsaRetain the default enabled if you want the account server to

bundle the VSAs within RADIUS accounting messages. Enter disabled if you do
not want the VSAs to be bundled. (Bundling means including multiple VSAs
within the vendor value portion of the message.)
In a bundled accounting message, the RADIUS message type is vendor-specific,
the length is determined for each individual message, and the vendor portion
begins with a 4-byte identifier, and includes multiple vendor type, vendor
length, and vendor value attributes.
8.
secretEnter the secret passed from the account server to the client in text
format. Transactions between the client and the RADIUS server are
authenticated by the shared secret; which is determined by the source IPv4
address of the received packet.
Version S-C6.1.0
9.
NAS-IDOptional. Enter the NAS ID in text format (FQDN allowed). The

account server uses this value to identify the Net-Net SBC for the transmittal of
accounting messages.
The remote server to which the account configuration sends messages uses at
least one of two potential pieces of information for purposes of identification.
The Net-Net SBC accounting messages always includes in the first of these:
Network Access Server (NAS) IP address (the IP address of the Net-Net

SBCs SIP proxy)
NAS ID (the second piece of information) provided by this value. If you enter
a value here, the NAS ID is sent to the remote server.
If you have more than one Net-Net SBC pointing to the same account server,
the NAS ID can be used to identify which Net-Net SBC generated the
record.
Per Realm Accounting Control

You can enable or disable accounting control for specific realms by setting one
parameter. This feature is enabled by default.
The Net-Net SBCs SIP and H.323 tasks check whether this parameter is set to
enabled or disabled, and sends record on that basis.
ACLI Instructions
and Examples
To configure per realm accounting:

1.

2.
Type session-router and press <Enter>.

ACMEPACKET(configure)# media-router
3.
Type realm-config and press <Enter>.

ACMEPACKET(media-router)# realm-config
4.
accounting-enableEither leave this parameter set to enabled (default) to

generate CDRs for this realm, or change it to disabled.
5.
Save and activate your configuration.
Configurable Intermediate Period

You can set how often the Net-Net SBC generates periodic interim records for H.323
and for SIP.
H.323The periodic timer (set to the value you specify in the accounting
configuration) is dynamically created when the Net-Net SBC receives a Connect
message and an H.323 call answer method is invoked. The Net-Net SBC deletes
the timer when the H.323 session is terminated.
SIPThe periodic timer (set to the value you specify in the accounting
configuration) is dynamically created when the Net-Net SBC receives a a 200
OK response to an INVITE message. The Net-Net SBC deletes the timer when
the session is terminated.
To set the timer for periodic interim records:

1.

Version S-C6.1.0
2.

3.
Type account-config and press <Enter>.

4.
intermediate-periodEnter amount of time in seconds between generating

periodic interim records during a SIP or H.323 call. This parameter defaults to
zero, which is not a valid value.
5.
RADIUS CDR Content Control

The Net-Net SBCs RADIUS support has been enhanced so that you can limit the
size of RADIUS CDRs. The Net-Net SBCs RADIUS accounting provides a detailed
set of records that can contain, for example, multiple media flow descriptions for
forked calls that can contain multiple sets of media and QoS attributes. While the
level of detail might be required for some networks, in others the large CDRs
generated to reflect that level of granularity can cause issues for the application
receiving the records.
You can use the following enhancements to control the size of the RADIUS CDRs
your Net-Net SBC produces:
Duplicate RADIUS attribute preventionUsing this feature, you can configure

the Net-Net SBC to send only one set of RADIUS attributes in CDR for a forked
call. (When a forked SIP INVITE contains media information, media and QoS
attributes can potentially be duplicated.)
RADIUS attribute selectionYou can set a list of the Acme Packet VSAs you
want included in a RADIUS CDR, and the Net-Net SBC will exclude the others
from the record; standard attributes are always included. You specify attributes
using their unique identifier in a comma-delimited list, and you can list them in
any order. However, entering an invalid range disables this feature.
The Net-Net SBC excludes attributes from the records in which they are already
defined. If an attributes only appears in a Stop record, then it will be deleted
from Stop records.
The configuration provides a mechanism to make entries flexible and easy.
ACLI Instructions
and Examples
You enable these enhancements using two parameters in the accounting

configuration.
Accessing the
Accounting
Configuration
To access the accounting configuration:

1.

2.

3.

From this point, you can reach the individual parameters for duplicate RADIUS
attribute prevention and for RADIUS attribute selection.
Version S-C6.1.0
Preventing Duplicate
RADIUS Attributes
To enable duplicate RADIUS attribute prevention:

1.
prevent-duplicate-attrsChange this parameter from disabled (default) to

enabled.
ACMEPACKET(account-config)# prevent-duplicate-attrs enabled
2.
RADIUS Attribute
Selection
You enter the list of VSAs that you want included as a comma-delimited list. There
are special entry types you can use in the comma-delimited list to set ranges and
make entries easier:
Where X is a VSA identifier, the Net-Net SBC will include all attributes
with an identifier equal to or greater than X.
X-
-X Where X is a VSA identifier, the Net-Net SBC will include all attributes
with an identifier equal to or less than X.
- Use the minus sign (-) alone when you want to turn off attribute selection,
including all VSAs in the CDR.
To enter a list of RADIUS attributes to include in a CDR:

1.
vsa-id-rangeEnter a comma-delimited list that represents the VSA you want

to appear in the RADIUS CDR. There is no default for this parameter.
Do not use <Spaces> when typing in your comma-delimited list.
ACMEPACKET(account-config)# vsa-id-range -5,7,10-
This entry specifies that CDRs contain VSA with identifiers equal to and less
than 5, VSA 7, and VSAs with identifiers equal to and greater than 10.
2.
Custom RADIUS CDR VSAs for SIP

This section describes these additions to the Net-Net SBCs RADIUS accounting
capabilities for customizing your call detail records (CDRs):
Generating CDRs with call detail information from a SIP messageThe NetNet SBC reserves a set of vender-specific attributes (VSAs) and then populates
them according to your header manipulation (HMR) configuration
Generating CDRs with trunk group informationYou can enable your Net-Net
SBC to provide terminating trunk-group and trunk-context data even when the
Net-Net SBC is not performing trunk-group routing.
Both support using the CSV file for RADIUS records, which you can either save
locally or push to a defined FTP server.
About UserDefined VSAs for

SIP Calls
The Net-Net SBC reserves VSAs 200-229 for you to define for use with SIP calls.
These VSAs should never be used for other purposes, and their use should never
conflict with the need to add new VSAs in the future. Because this leaves a significant
number of VSAs unused, there is still ample space for any new VSAs that might be
required.
Since RADIUS START records are created on session initiation, their content cannot
be updated. However, the content for INTERIM and STOP records can be.
To configure user-defined VSAs for a SIP call, you use HMR. For example, when you
set up HMR correctly, the Net-Net SBC reports originating or terminating country
Version S-C6.1.0
codes in CDRs in whatever format they appear in the SIP username field. The HMR
rules you configure uses the SIP header name P-Acme-VSA, adding it to the SIP
header from any part of the SIP message. Then the Net-Net SBC searches for the PAcme-VSA header, generates a VSA for it, and then includes that VSA in the CDR
for the call.
You can include multiple custom VSAs per CDR by adding the corresponding
number of rules; in essence, you add in the header as many times as required.
HMR Adaptations
The following HMR element rule types support user-defined VSA for SIP calls:
uri-user-onlyThe uri-user-only element rule type represents the URI

username without the URI user parameters. You can perform these actions for
the uri-user-only type: store, replaces, delete, and add. This means, for
example, that you can add a username string to SIP or TEL URI without having
any impact on other parameters.
uri-phone-number-onlyThe uri-phone-number-only applies when all

rules are met. It refers to the user part of the SIP/TEL URI without the user
parameters when the user qualifies for the BNF shown here:
uri-phone-number-only
phone-digit
DIGIT
[+]1*(phone-digit / dtmf-digit / pause-character)

DIGIT / visual-separator
"0" / "1" / "2" / "3" / "4" / "5" / "6" / "7" / "8" / "9"
visual-separator
"-" / "." / "(" / ")"
dtnf-digit
"*" / "#" / "A" / "B" / "C" / "D"
pause-character
"p" / "w"
Once the URI user part qualifies as a uri-phone-number-only based on this

BNF, the Net-Net SBC ignores the visual separators when comparing it against
a match value. Furthermore, the Net-Net SBC performs on or using the uriphone-number-only after the excluding the visual separators.
But anew value being added as a uri-phone-number-only or replacing a uriphone-number-only does not have to match the BNF noted above. That is, you
can use the uri-phone-number-only type knowing that:
HMR String Variable
The action only occurs if the URI username matches the BNF defined here.
Even so, you can also replace the uri-phone-number-only with one that does
not matchusing the same rule.
HMR supports the use of a string variable that you can use to populate headers and
elements. You set this value in the hmr-string parameter for a realm, SIP session
agent, or SIP interface. Then, you reference it as the $HMR_STRING variable.
When a message arrives, the Net-Net SBC matches the string you provision to the
closest session agent, realm, or SIP interface. The precedence for matching is in this
order: session agent, realm, and then SIP interface. For example, the Net-Net SBC
populates messages matching a session agent using the $HMR_STRING variable,
but it leaves the value empty for session agents that do not match.
You can use the string variable, for instance, for values specific to realms and session
agents such as country code values when the regular expression pattern used to
match a country code fails to do so.
ACLI Instructions and

Examples: UserDefined VSAs
This section shows you how to configure user-defined VSAs for SIP calls. It also
contains subsections with configuration examples so you can see how this feature is
put to use.
Version S-C6.1.0
This section also shows you two configuration examples for this feature.
To create a header manipulation rule that generates user-defined VSAs for SIP
calls:
1.

ACMEPACKET(configure)#
2.

ACMEPACKET(session-router)#
3.
Type sip-manipulation and press <Enter>.

ACMEPACKET(session-router)# sip-manipulation
ACMEPACKET(sip-manipulation)#
4.
Type header-rules and press <Enter>.

ACMEPACKET(session-router)# header-rules
ACMEPACKET(sip-header-rules)#
5.
nameEnter a meaningful name for the header rule you are creating. For
example, if you want to add VSA 200 to your CDRs for SIP calls, you might name
your rule generateVSA200. There is no default for this parameter, and it is
required.
6.
header-nameSet this parameter to P-Acme-VSA so the Net-Net SBC will

add this accounting information to CDRs for the call.
7.
actionSet this parameter to add.
8.
new-valueEnter the regular expression value for the new value you want to
add. For example, to add VSA 200 that contains the value from the SIP From
header, you would enter 200:+$storeFrom.$0.
9.
The first example shows you how to generate custom VSA for the To and From
headers in SIP messages.
VSA 200 contains the header value from the SIP From header.
VSA 220 contains the header value from the SIP To header.
sip-manipulation
namecustom
VSA1
description
header-rule
name
storeFrom
header-name
from
action
store
comparison-type
pattern-rule
match-value
.*
msg-type
request
new-value
methods
INVITE
header-rule
Version S-C6.1.0
name
storeTo
header-name
to
action
store
comparison-type
pattern-rule
match-value
.*
msg-type
request
new-value
methods
INVITE
header-rule
name
generateVSA200
header-name
P-Acme-VSA
action
add
comparison-type
case-sensitive
match-value
msg-type
any
new-value
200:+$storeFrom.$0
methods
INVITE
header-rule
name
generateVSA220
header-name
P-Acme-VSA
action
add
comparison-type
case-sensitive
match-value
msg-type
any
new-value
220:+$storeTo.$0
methods
INVITE
The second example shows you how to configure HMR to generate VSA 225, which
contains the customer P_From header when it is present. When that header is not
present, the rule instructs the Net-Net SBC to include the header value from the SIP
From header for VSA 225.
sip-manipulation
name
customVSA1
description
header-rule
name
storePfrom
header-name
P_From
action
store
comparison-type
pattern-rule
match-value
.*
msg-type
request
new-value
methods
INVITE
header-rule
name
storeFrom
header-name
from
action
store
comparison-type
pattern-rule
match-value
.*
msg-type
request
new-value
methods
INVITE
header-rule
name
generateVSA225_1
header-name
P-Acme-VSA
action
add
comparison-type
case-sensitive
match-value
Version S-C6.1.0
msg-type
request
new-value
225:+$storeFrom.$0
methods
INVITE
header-rule
name
generateVSA225_2
header-name
P-Acme-VSA
action
manipulate
comparison-type
pattern-rule
match-value
$storePfrom
msg-type
request
new-value
methods
INVITE
element-rule
name
one
parameter-name
type
action
header-value
delete-element
match-val-type
any
comparison-type
pattern-rule
match-value
^225.*
new-value
element-rule
name
two
parameter-name
type
header-value
action
add
match-val-type
comparison-type
any
case-sensitive
match-value
new-value

Examples: String
Variable
225:+$storePfrom.$0
To use the HMR string variable, you set the hmr-string value in the SIP session
agent, realm, or SIP interface where you want the feature applied. The following
sample shows you how to configure the hmr-string parameter for SIP session agent.
1.

2.

3.
Type session-agent and press <Enter>.

ACMEPACKET(session-router)# session-agent
ACMEPACKET(session-agent)#
If you are adding this feature to an existing configuration, you need to select the
configuration (using the ACLI select command) before making your changes.
Version S-C6.1.0
4.
manipulation-stringEnter a value that references the $HMR_STRING

variable that will be used to populate SIP headers and elements using HMR.
There is no default value for this parameter.
5.
Trunk-Group VSA
Generation
You can force the Net-Net SBC to generate VSAs related to trunk groups even when
you are not using the trunk group feature. With the force-report-trunk-info
parameter turned on in the session router configuration:
The Net-Net SBC reports terminating trunk group and trunk-context

information even though it has not perform trunk-group routing.
The appropriate VSAs report the terminating trunk-group (VSA 65) and trunk
context (VSA 67) with the information of the matching ingress session agent and
realm of the originator.
The Net-Net SBC reports the terminating trunk-group (VSA 66) and trunk
context (VSA 68) as the received trunk group and context from the calls SIP
REQUEST message. If the SIP message has none, then the Net-Net SBC uses
the information from the matching egress session agent (or egress realm, when
available) and next-hop realm.
Note that information is reported after HMR processingmeaning that header
manipulation has been performed on the message information reported.

Examples
You enable trunk-group VSA generation on a system-wide basis in the sessionrouter configuration.
To enable forced trunk-group VSA generation:
1.

2.

3.
Type session-agent and press <Enter>.

ACMEPACKET(session-router)# session-router
4.
forced-report-trunk-infoChange this parameter to enabled if you want to

turn on the Net-Net SBCs ability to generate VSAs for trunk group information
even when you are not using trunk-group routing. The Net-Net SBC uses VSAs
65-68 to report originating and terminating trunk group information as
described in the Trunk-Group VSA Generation (50) section above. By default,
this parameter is disabled.
5.
RADIUS Account Server Prioritization

Especially useful for customers with multiple Net-Net SBCs, the RADIUS account
server prioritization feature allows you to assign a priority to each of the account
servers you configure. Setting the priority for RADIUS accounting servers allows you
to load balance traffic across the servers.
Without this feature, the Net-Net SBC sorts RADIUS accounting servers by their IP
addresses and ports. For example, if you have a pre-existing accounting server with
the IP address and port combination of 10.1.31.2:1813 and then configure a new
server at 10.0.3.12:2145, the new server will take priority over the pre-existing one.
Of course, you always have the option of allowing the system to set the priority or
your accounting servers in this way.
Version S-C6.1.0
The prioritization feature works with all of the strategy types you set in the
accounting configuration. However, it is most applicable to the hunt or failover
strategies. You can assign a number to each server to mark its priority, or you can
leave the priority parameter set to 0 (default) so the Net-Net SBC prioritizes them by
IP address and port.
How You Might

User Server
Prioritization
This example shows you how you can might benefit from using the prioritization
feature if you have multiple Net-Net SBCs sending RADIUS CDRs to multiple
RADIUS servers. Consider the following Net-Net SBCs and accounting servers.
Net-Net SBC
Account Server1
Priority
Account Server2
Priority
Account Server3
Priority
Net-Net SBC1
10
Net-Net SBC2
10
Net-Net SBC3
10
Net-Net SBC4
10
Net-Net SBC5
10
Net-Net SBC6
10
If the strategy for this example is set to hunt or failover and assuming no timeouts
are pending, you can see that Net-Net SBC1 sends its accounting traffic to Account
Server3 over the other two. Net-Net SBC2 sends its traffic to Account Server2 over
the others, and likewise for the remainder of Net-Net SBCs and servers. The traffic,
then, is load balanced across the servers, less likely to overburden any of them.
ACLI Instructions
and Examples
This section shows you how set the priority for an account server.
1.

2.

3.

4.
Type account-server and press <Enter>.

ACMEPACKET(session-router)# account-server
ACMEPACKET(account-server)#
5.
Version S-C6.1.0
priorityEnter the number corresponding to the priority you want this account
server to have in relation to the other account servers to which you send traffic.
The default for this parameter is 0, meaning the prioritization feature is turned
offand that the Net-Net SBC will therefore prioritize accounting servers by IP
address and port. Otherwise, you can use any numbering scheme that suits your
needs and ease of use.
6.
Accounting Configuration Example

Using the Net-Net SBC with external RADIUS accounting servers to generate CDRs
and provide billing services requires you to configure accounting configuration and
any associated accounting servers you might need.
The following example shows how you can set accounting configuration and
accounting server parameters to support multiple RADIUS accounting servers.
ACMEPACKET(account-config)# show
account-config
hostname
localhost
port
1813
strategy
Hunt
state
enabled
max-msg-delay
60
max-wait-failover
100
trans-at-close
disabled
file-output
enabled
max-file-size
1000000
max-files
file-path
/ramdrv
file-rotate-time
60
ftp-push
enabled
ftp-address
154.0.12.4
ftp-port
21
ftp-user
Admin
ftp-password
A213HG
ftp-remote-path
/sdRADIUS
cdr-output-redundancy
enabled
generate-start
OK
generate-interim
Reinvite-Response
intermediate-period
prevent-duplicate-attrs
disabled
vsa-id-range
cdr-output-inclusive
account-server
hostname
10.0.0.189
port
1813
state
enabled
min-round-trip
250
max-inactivity
60
restart-delay
30
bundle-vsa
enabled
secret
acme
NAS-ID
priority
hostname
192.168.200.70
port
5050
state
enabled
min-round-trip
250
max-inactivity
60
account-server
Version S-C6.1.0
restart-delay
30
bundle-vsa
enabled
secret
packet
NAS-ID
priority
Local CDR Storage and FTP Push

The local CDR storage feature allows you to save RADIUS CDR data to a local CSV
text file on the Net-Net SBC. Local CDR file creation and storage can be used in
addition to or independently of sending CDRs to RADIUS servers for every call.
Once the Net-Net SBC creates and saves local CDR files, you can:
Send the files to an FTP server by configuring a push receiver
Develop and implement your own script for retrieving them as necessary from
the Net-Net SBC
You configure the Net-Net SBC to:
Set directory path where you want to save local CDR files
Set a maximum file size for the CSV file
Set a maximum number of local CDR files
Set an interval in which to close the existing local CDR file and begin writing a
new file.
Once local CDR file creation is enabled, you can configure push receivers to push
any non-active and closed CDR files to an FTP server using FTP or SFTP protocols.
You configure the Net-Net SBC with the push receivers:
server IP address and port information
login credentials
path to save the local CDR Files
The interval at which the Net-Net SBC should send files to a push reciever
For flexibility and security, the Net-Net SBC can log into a push reciever with either
FTP or SFTP. If you are creating a secure connection with SFTP, your Net-Net SBC
can authenticate to the server with either a public shared key or SSH-encrypted
username and password.
Local CDR File

Format
The CDRs are written as comma-delimited ASCII records to files on the Net-Net
SBC. The types of records are controlled by the same accounting configuration
parameters used for RADIUS. The fields of the comma-delimited entries correspond
to RADIUS START, INTERIM, and STOP records. Using the accounting
configuration, you can configure the Net-Net SBC to record STOP records only.
Because the record types do not have consistent field positioning, any server parsing
them would need to read the first field to determine the type and learn how to parse
the remaining fields.
Local CDR File Format

Consistency
Version S-C6.1.0
Unpopulated or unused fields in the RADIUS CDR are omitted from the locallystored CSV file. This means that there is no fixed position for a RADIUS attribute
across all CSV files. Instead, the missing values are skipped in the CSV file so that
the order and appearance for attribute values can differ from record to record.
You can optionally guarantee the placement of attributes in locally-stored CSV files
with the CDR output inclusive parameter. With this enhancement enabled,
RADIUS records sent to a RADIUS client contain even empty attributes with an
integer, date and time, or IP address format; the default value is zero. In other words,
when there is no value to report:
An IP address attribute will report as 0.0.0.0
A date and time attribute will report as 00:00:00.000 UTC JAN 01 1970
An integer attribute value will report as 0
To maintain RFC 2865 and 2866 compliance, the Net-Net SBC will not send empty
attributes that are string values to a RADIUS client. And when you enable this
feature, the Net-Net SBC adds all attributes to the locally-stored CSV file.
Refer to Appendix D (89) of this document for details about where in locallygenerated CSV file VSAs appear for Start, Interim, and Stop records.
Requirements
If you want to guarantee the CSV placement for RADIUS attribute values, you must
use the entire RADIUS dictionary. You cannot use the RADIUS CDR abbreviation
feature. Using an abbreviated form of the RADIUS dictionary results in adverse
effects for the CSV file.
In your configuration, then, you must set the vsa-id-range parameter to use the
entire range of attributes. Leaving this parameter blank disables abbreviation and all
attributes are included. Alternatively, you can specify all of the parameters (by
attribute number) that are used in the Net-Net OS release loaded on your system.
See the RADIUS CDR Content Control (44) section for more information.
Local CDR File

Naming
Convention
Filenames are derived from the date and time that the CDR file is opened for writing.
The format is cdrYYYYMMDDHHMM[a-j], where:
YYYY=the year
MM=the month
DD=the day
HH=the hour
MM=the minute
[a-j]=a suffix that provides additional discrimination in case of changing

system time, setting the rotation time for this feature to one minute, or in case
of another occurrence that might compromise the date and time
Your file name will resemble the following sample: cdr200511151200.
Local CDR File

Storage
Directories
The Net-Net SBC only allows local storage of ASCII CDRs to the /ramdrv and
/ramdrv/logs directories. If you try to save to another directory (such as /code or
/boot), you will receive an error message.
If you are using the ACLI and enter an inappropriate directory, the ACLI will issue
an error message.
Version S-C6.1.0
Local CDR File

Size and Rotation
You can configure maximum file size, maximum number of local CSV files to store,
and the interval at which the files rotate.
The Net-Net SBC saves up to the file size limit (max file size) and maintains only
number of files that you configure (max files). When the maximum file size is
reached, the Net-Net SBC closes that file and begins writing VSA attributes and
values to a new local CDR file. When it is time for the Net-Net SBC to write the max
files + 1 file, the oldest file is deleted so that the newest one can be stored.
More About File

Rotation Time
You can use the CDR local storage feature on its own, without enabling the ftp push
feature. The Net-Net SBC uses a period of time that you set to periodically rotate the
files. The file rotate time parameter rotates the local CSV files regardless of whether
you use the FTP push feature.
RADIUS CDR
Redundancy
When you are using the RADIUS CDR storage and FTP push feature, the Net-Net
SBC can create a redundant copy of the comma-delimited CDR files that it stores on
the standby system in the HA node.
This enhancement to the CDR storage feature ensures against data loss if, for
example, an active Net-Net SBC fails immediately before an FTP push. The standby
has a duplicate set of records that it sends. This feature is enabled with the CDR
output redundancy parameter found in the account config configuration element.
Caveats for H.323
H.323 calls proceed without interruption over an HA node in the event of a failover
from one Net-Net SBC to another, and RADIUS records are generated and
duplicated across the active and standby systems in an HA node. However if a
switchover occurs during an H.323 call (that has been initiated, but not completed),
the newly active (formerly standby) system will not generate RADIUS Stop records
when the call completes.
FTP Push
The FTP push feature is used to copy local CDR files to a remote FTP server on a
periodic basis. This feature is configured by defining push receivers which contain
standard login and FTP server credentials of the remote machine. At the configured
time interval (file rotate time), the Net-Net SBC closes the current file, and pushes
the files that are complete and have not yet been pushed; including the just-closedfile.
Deprecated ACLI
Configuration
The following parameters in the account-config configuration element are

deprecated:
ftp-address
ftp-port
ftp-user
ftp-password
ftp-remote-path
These parameters will only only be used if no account-config > push-receiver

configuration elements have been defined. All new push receivers must be defined
in the account-config > push-receiver configuration element.
Version S-C6.1.0
Multiple Push
Receivers
While you can configure multiple push receivers, the Net-Net SBC only uses the first
configured push reciever to log in to a remote FTP server.
Push Recievers
A push receiver configuration includes all the credentials that the Net-Net SBC
needs to log into an FTP server and upload any recent local CDR files. Push receiver
configurations must include:
Secure FTP Push
the servers IP address and port
remote path of where to upload the local CDR files
protocol used to connect to the server
account login credentials
The Net-Net SBC can securely log in to a push reciever using one of two methods
that create a secure connection.
You can use password-based SSH authentication for logging into an SFTP server by
setting the push receivers protocol parameter to sftp, configuring a username and
password and leaving the public-key parameter blank.
You can use SSH public key authentication for logging into an SFTP server by setting
the push receivers protocol parameter to sftp, setting the public-key parameter to
a configured public key record name (security > public key > name), and including
an account username.
ACLI Instructions
and Examples
This section shows you how to configure Local CDR storage and FTP push on your
Net-Net SBC.
Accessing the
Accounting
Configuration
To configure parameter for these features, you must access the accounting
configuration.
To access the accounting configuration:
1.

2.

3.

From here, you can enable local CDR storage and FTP push.
Enabling Local CDR
Storage
To enable local CDR storage:

4.
file-outputEnable this paramater for the Net-Net SBC to create commadelimited CDRs (generated from RADIUS records). By default, this parameter is
disabled.
5.
file-pathYou must configure this path or the CDR push feature will not work.
Set the path to use on the Net-Net SBC for file storage from these two options:
/ramdrv
Version S-C6.1.0
/ramdrv/logs
To use FTP push, you must configure a usable path.
Setting the CSV File

Format
6.
max-file-sizeSet the maximum file size in bytes permitted for each CDR file.
The default and minimum value is 1000000. The maximum value is 108.
7.
max-filesSet the maximum number of files to be stored on the Net-Net SBC

at one time. You can configure the Net-Net SBC to store as few as one file or as
many as 10. The default is 5.
8.
file-rotate-timeSet how often in minutes you want to rotate the stored files;
the Net-Net SBC will overwrite the oldest file first. The minimum rotation time
is 2 minutes; the default is 60 minutes. This parameter defaults to 0, and leaving
it set to the default means that the Net-Net SBC will not rotate the files.
9.
cdr-output-redundancySet this paramter to enabled for the Net-Net SBC to

store a redundant copy of the local CSV file to the standby HA node.
This section shows you how to to guarantee the CSV placement for RADIUS
attribute values by using the entire RADIUS dictionary.
To enable fixed value placement in CSV files for RADIUS CDRs:
1.

2.

3.

If you are adding support for this feature to a pre-existing accounting

configuration, then you must use the ACLI select command so that you can edit
it.
4.
vsa-id-rangeEither leave this parameter blank (default), or enter the

complete range of VSAs for the Net-Net OS release loaded on your system. The
following example shows what you would enter to use all of the VSAs for NetNet OS Release 4.1.4p4 for a system that is not running QoS.
ACMEPACKET(account-config)# vsa-id-range 1-4,10-14,20-24,28,29,3271,74-136
5.
Enabling FTP Push
cdr-output-inclusiveSet this parameter to enabled to fill in 0s in otherwise

empty fields in local CDR files. It is disabled by default.
To enable FTP push:

1.

2.

3.

Version S-C6.1.0
If you are adding support for this feature to a pre-existing accounting

configuration, then you must use the ACLI select command so that you can edit
it.
4.
ftp-pushSet the state of FTP push feature to enabled. It is disabled by default.
5.
Type push-receiver and press <Enter>.

ACMEPACKET(account-config)# push-receiver
6.
serverEnter the IP address of this push receiver FTP server.
7.
portEnter the port number of this push receiver FTP server.
8.
remote-pathEnter the remote pathname to which you want CDR files to be

sent on the push receiver. There is no default for this parameter.
9.
filename-prefixEnter the filename prefix (as a string) to prepend to the to the

CDR files the Net-Net SBC sends to the push receiver. The Net-Net SBC does
not rename local files. There is no default for this parameter.
10. protocolEnter SFTP if you want to change the transport protocol for this push
receiver from its default, FTP.
11. usernameEnter the username the Net-Net SBC uses when connecting to this
push receiver. There is no default for this parameter. This parameter must be
configured whether you are using unencrypted FTP, password or public key
authentication.
12. passwordEnter the password corresponding to the username the Net-Net
SBC uses when connecting to this push receiver. There is no default for this
parameter.
13. public-keyEnter the public key profile to use for authentication to this push
receiver if this is the preferred form of authentication. If you define this as an
SFTP push receiver but do not set the public-key value, the Net-Net SBC will
use password authentication. There is no default for this parameter.
14. Save and activate your configuration.
Version S-C6.1.0
RADIUS Accounting Management
Overview
This chapter provides information about management and monitoring of RADIUS
accounting functions on your Net-Net SBC.
Net-Net SBC alarm generation and monitoring
Status and statistics monitoring
Alarm Generation and Monitoring

The Net-Net products generate alarms when certain hardware and software events
occur. For more information about Net-Net SBC alarms for RADIUS, refer to the
Net-Net Maintenance and Troubleshooting Guide.
The RADIUS ACCOUNTING CONNECTION DOWN alarm, detailed in the table
below, is directly associated with the Net-Net SBCs RADIUS functionality. When
enabled connections to RADIUS servers have timed-out without a response from
the RADIUS server, the alarm is activated. The RADIUS ACCOUNTING
CONNECTION DOWN alarm triggers a Simple Network Management Protocol
(SNMP) trap that is sent via the syslog Management Information Base (MIB) (apsyslog.mib). For a list of all SNMP-related alarms and their associated traps, refer to
the table of SNMP trap correlation to Net-Net SBCs alarms in Acme Packets MIB
Reference Guide.
This alarm has no impact on a the health score of a Net-Net SBC that is part of an
HA Node.
RADIUS Alarms
Alarm
RADIUS
ACCOUNTING
CONNECTION
DOWN
The table below describes the Net-Net SBCs alarms for RADIUS.
Alarm
ID
327681
Alarm Severity
Cause
Log Message
Actions
CRITICAL if all enabled

and configured RADIUS
accounting server
connections have
timed-out without a
response from the
RADIUS server.
The enabled
connections to
RADIUS
servers have
timed-out
without a
response from
the RADIUS
server.
CRITICAL: All
enabled
accounting
connections have
been lost. Check
accounting status
for more details.
apSyslogMess
ageGenerate
d trap
generated
critical, major
dry contact
syslog
MAJOR if some, but not

all configured RADIUS
accounting server
connections have
timed-out without a
response from the
RADIUS server.
Version S-C6.1.0
MAJOR: One or
more enabled
accounting
connections have
been lost. Check
accounting status
for more details.
RADIUS ACCOUNTING MANAGEMENT
Status and Statistics Monitoring

The ACLI show radius command, used with the three arguments described below,
displays the status of any established RADIUS accounting connections and
authentications. A working RADIUS connection displays READY, and a disabled
connection displays DISABLED.
When an accounting server is disabled, the triggering and clearing of RADIUS
ACCOUNTING CONNECTION DOWN alarms is not affected.
For more information about Net-Net SBC about monitoring your Net-Net SBC,
refer to the Net-Net Maintenance and Troubleshooting Guide.
ACLI Show
RADIUS Display
The show radius command can take one of the three available arguments:
authenticationShows authentication statistics for primary and secondary

RADIUS servers, including: server IP address and port; round trip time;
information about failed and successful requests/authentications; number of
rejections; number of challenges; number of time-outs, number of
retransmissions
accountingShows the information described in this table:
Section
Description
Client Display
General accounting setup (as established in the accounting

configuration element), including:
Information about the state of the RADIUS client
Accounting strategy used (Hunt, Failover, RoundRobin,
FastestRTT, or FewestPending)
IP address and port on which the Net-Net server is listening
Maximum message delay in seconds
Number of configured accounting servers
Waiting Queue
Amount of accounting (RADIUS) messages waiting to be sent.

Waiting queue capacity is 4,096 messages.
<IP Address:Port>
Information about each configured accounting server (established in

the accounting servers configuration). The heading above each
accounting server section is the IPv4 address and port combination
of the accounting server described. This section also includes
information about the accounting servers state (e.g.,
Connect_Attempt, INIT).
allShows all of the information for both the authentication and accounting
displays
The following is an example of the ACLI show radius authentication command

output.
ACMEPACKET# show radius authentication
Active Primary Authentication Servers:
server ipAddr: 172.30.0.7
Active Secondary Authentication Servers:
Authentication Statistics:
Server:"172.30.0.7:1812"
Version S-C6.1.0
RoundTripTime
:0
MalformedAccessResponse:0
AccessRequests
:2
BadAuthenticators
:0
AccessRetransmissions
:5
AccessAccepts
:0
Timeouts
:6
AccessRejects
:0
UnknownPDUTypes
AccessChallenges
:0
:0
Server:"172.30.0.8:1812"
RoundTripTime
:0
AccessRequests
:2
BadAuthenticators
:0
:9
AccessAccepts
:0
Timeouts
:10
AccessRejects
:0
UnknownPDUTypes
:0
AccessChallenges
:0
The following is an example of the ACLI show radius accounting command

output.
ACMEPACKET# show radius accounting
*********Client Display Start************
Client State = READY, strategy=Hunt
listening on 127.0.0.1:1813
max message delay = 60 s, # of servers = 2
================= Waiting Queue ================
Waiting size = 89
================================================
----------------- 10.0.0.189:1813 -----------------Remote = 10.0.0.189:1813, Local = 0.0.0.0:1026, sock=45 (BOUND)
conn state=READY, RTT=250 ms
Min Rtt=250 ms, Max inactivity=60 s, expires at Nov 21 13:50:19.582,
Restart delay=30 s
conn state=DISABLED, RTT=0 ms
Restart delay=30 s
*********Client Display End************
The following is an example of the ACLI show radius all command output.
ACMEPACKET# show radius all
*********Client Display Start************
Client State = READY, strategy=Hunt
listening on 127.0.0.1:1813
max message delay = 60 s, # of servers = 2
================= Waiting Queue ================
Waiting size = 89
================================================
Version S-C6.1.0

conn state=READY, RTT=250 ms
Restart delay=30 s
conn state=DISABLED, RTT=0 ms
Restart delay=30 s
*********Client Display End************
Active Primary Authentication Servers:
Active Secondary Authentication Servers:
Authentication Statistics:
Server:"172.30.0.7:1812"
RoundTripTime
:0
AccessRequests
:2
BadAuthenticators
:0
:5
AccessAccepts
:0
Timeouts
:6
AccessRejects
:0
UnknownPDUTypes
AccessChallenges
:0
:0
Server:"172.30.0.8:1812"
RoundTripTime
:0
AccessRequests
:2
BadAuthenticators
:0
:9
AccessAccepts
:0
Timeouts
:10
AccessRejects
:0
UnknownPDUTypes
:0
AccessChallenges
:0
CDR File Transfer Failure Alarm

The Net-Net SBC sends out traps and triggers corresponding alarms when it
encounters failure when attempting to transfer locally stored CDR files via FTP or
SFTP. One set of traps is used for instances when one CDR push receiver fails;
another is used when all enabled CDR receivers fail. They are part of the
apSysMgmtCDRPushReceiverNotificationsGroup.
All of the traps contain information about the type of push receiver, the address of
the push receiver, and the failure reason code.
All of the traps contain information about the type of push receiver, the address of
the push receiver, and the failure reason code.
Version S-C6.1.0
The trap and corresponding clearing trap for single push receiver failure are:
apSysMgmtCDRPushReceiverFailureTrap
apSysMgmtCDRPushReceiverFailureClearTrap
The trap and corresponding clearing trap for global push receiver failure are:
Version S-C6.1.0
apSysMgmtCDRAllPushReceiversFailureTrap
apSysMgmtCDRAllPushReceiverFailuresClearTrap
Version S-C6.1.0
Appendix A
Net-Net RADIUS Log Examples
Overview
Several examples of RADIUS logs appear in this appendix. These logs were
processed and the output generated by a FreeRADIUS server; the labels for each
field come from the installed VSA dictionaries, including the Acme Packet RADIUS
dictionary.
As you review these examples, please note:
The Acct-Unique-Session-Id = and Timestamp = fields shown in the

following examples are generated by the RADIUS server and not by the Net-Net
SBC.
For non-QoS calls, the attributes appear in the record, but their values are
always zero (0).
RADIUS CDR Samples for SIP

This section provides an example CDRs for SIP calls.
Basic Successful
SIP Call
The following sample CDRs are for a successful SIP call.

Successfull SIP Call - Peer
=========================================
Acct-Status-Type = Start
NAS-IP-Address = 192.168.12.100
NAS-Port = 5060
Acct-Session-Id = "[email protected]"
Acme-Session-Ingress-CallId = "[email protected]"
Acme-Session-Egress-CallId = "[email protected]"
Acme-Session-Protocol-Type = "SIP"
Calling-Station-Id = ""7812223001"
<sip:[email protected]>;tag=40335A3-29FEF610"
Called-Station-Id = "<sip:[email protected];user=phone>"
h323-setup-time = "16:43:42.452 EST JUL 02 2008"
h323-connect-time = "16:43:53.517 EST JUL 02 2008"
Acme-Egress-Network-Interface-Id = "M10"
Acme-Egress-Vlan-Tag-Value = 0
Acme-Ingress-Network-Interface-Id = "M00"
Acme-Ingress-Vlan-Tag-Value = 0
Acme-Session-Egress-Realm = "Core"
Acme-Session-Ingress-Realm = "Peer"
Acme-FlowID_FS1_F = "localhost:65594"
Version S-C6.1.0
APPENDIX A
Acme-FlowType_FS1_F = "PCMU"
Acme-Flow-In-Realm_FS1_F = "Peer"
Acme-Flow-In-Src-Addr_FS1_F = 0.0.0.0
Acme-Flow-In-Src-Port_FS1_F = 0
Acme-Flow-In-Dst-Addr_FS1_F = 192.168.11.100
Acme-Flow-In-Dst-Port_FS1_F = 49188
Acme-Flow-Out-Realm_FS1_F = "Core"
Acme-Flow-Out-Src-Addr_FS1_F = 192.168.12.100
Acme-Flow-Out-Src-Port_FS1_F = 49152
Acme-Flow-Out-Dst-Addr_FS1_F = 192.168.12.200
Acme-Flow-Out-Dst-Port_FS1_F = 2222
Acme-FlowID_FS1_R = "localhost:65595"
Acme-FlowType_FS1_R = "PCMU"
Acme-Flow-In-Realm_FS1_R = "Core"
Acme-Flow-In-Src-Addr_FS1_R = 0.0.0.0
Acme-Flow-In-Src-Port_FS1_R = 0
Acme-Flow-In-Dst-Addr_FS1_R = 192.168.12.100
Acme-Flow-In-Dst-Port_FS1_R = 49152
Acme-Flow-Out-Realm_FS1_R = "Peer"
Acme-Flow-Out-Src-Addr_FS1_R = 192.168.11.100
Acme-Flow-Out-Src-Port_FS1_R = 49188
Acme-Flow-Out-Dst-Addr_FS1_R = 192.168.11.101
Acme-Flow-Out-Dst-Port_FS1_R = 2224
Acme-FlowID_FS2_F = ""
Acme-FlowType_FS2_F = ""
Acme-Flow-In-Realm_FS2_F = ""
Acme-Flow-Out-Realm_FS2_F = ""
Acme-FlowID_FS2_R = ""
Acme-FlowType_FS2_R = ""
Acme-Flow-In-Realm_FS2_R = ""
Acme-Flow-Out-Realm_FS2_R = ""
Version S-C6.1.0
APPENDIX A
Acme-Firmware-Version = "C6.0.0 GA (Build 13)"
Acme-Local-Time-Zone = "GMT-05:00"
Acme-Post-Dial-Delay = 223
Acme-Primary-Routing-Number = "sip:[email protected];user=phone"
Acme-Ingress-Local-Addr = "192.168.11.100:5060"
Acme-Ingress-Remote-Addr = "192.168.11.101:5060"
Acme-Egress-Local-Addr = "192.168.12.100:5060"
Acme-Egress-Remote-Addr = "192.168.12.200:5060"
Acme-Egress-Final-Routing-Number =
"sip:[email protected];user=phone"
Acme-CDR-Sequence-Number = 99
Client-IP-Address = 172.30.21.31
Acct-Unique-Session-Id = "5af95b6a3259b428"
Timestamp = 1215033670
Wed Jul
2 17:21:21 2008
Acct-Status-Type = Stop
NAS-IP-Address = 192.168.12.100
NAS-Port = 5060
<sip:[email protected]>;tag=40335A3-29FEF610"
Acct-Terminate-Cause = User-Request
Acct-Session-Time = 11
h323-disconnect-time = "16:44:04.356 EST JUL 02 2008"
h323-disconnect-cause = "1"
Version S-C6.1.0
APPENDIX A
Acme-Calling-RTCP-Packets-Lost_FS1 = 0
Acme-Calling-RTCP-Avg-Jitter_FS1 = 0
Acme-Calling-RTCP-Avg-Latency_FS1 = 0
Acme-Calling-RTCP-MaxJitter_FS1 = 0
Acme-Calling-RTCP-MaxLatency_FS1 = 0
Acme-Calling-RTP-Packets-Lost_FS1 = 0
Acme-Calling-RTP-Avg-Jitter_FS1 = 0
Acme-Calling-RTP-MaxJitter_FS1 = 0
Acme-Calling-Octets_FS1 = 0
Acme-Calling-Packets_FS1 = 0
Acme-Called-RTCP-Packets-Lost_FS1 = 0
Acme-Called-RTCP-Avg-Jitter_FS1 = 0
Acme-Called-RTCP-Avg-Latency_FS1 = 0
Acme-Called-RTCP-MaxJitter_FS1 = 0
Acme-Called-RTCP-MaxLatency_FS1 = 0
Acme-Called-RTP-Packets-Lost_FS1 = 0
Acme-Called-RTP-Avg-Jitter_FS1 = 0
Acme-Called-RTP-MaxJitter_FS1 = 0
Acme-Called-Octets_FS1 = 0
Acme-Called-Packets_FS1 = 0
Version S-C6.1.0
APPENDIX A
Acme-Session-Disposition = 3
Acme-Disconnect-Initiator = 1
Acme-Disconnect-Cause = 0
Acme-SIP-Status = 0
Version S-C6.1.0
APPENDIX A
Acct-Unique-Session-Id = "5af95b6a3259b428"
Unsuccessful SIP
Call
The following sample CDRs are for an unsuccessful SIP call.

NAS-IP-Address = 192.168.12.100
NAS-Port = 5060
<sip:[email protected]>;tag=591ADA30-B9864E09"
Acct-Terminate-Cause = User-Error
Acme-Session-Ingress-Realm = "Core"
Acme-Flow-In-Realm_FS1_F = "Core"
Version S-C6.1.0
APPENDIX A
Acme-Flow-Out-Realm_FS1_R = "Core"
Version S-C6.1.0
APPENDIX A
Acme-SIP-Status = 487
Acct-Unique-Session-Id = "f1c5761c4d973242"
Version S-C6.1.0
APPENDIX A
SIP Call On Hold
The following sample CDRs are for SIP call on hold.

Acct-Status-Type = Start
NAS-IP-Address = 192.168.12.100
NAS-Port = 5060
<sip:[email protected]>;tag=29749EE9-79CDC11E"
Version S-C6.1.0
APPENDIX A
Acct-Unique-Session-Id = "972a994cb16bcdc0"
Wed Jul
2 17:24:59 2008
Acct-Status-Type = Interim-Update
NAS-IP-Address = 192.168.12.100
NAS-Port = 5060
Version S-C6.1.0
APPENDIX A

Version S-C6.1.0
APPENDIX A
Version S-C6.1.0
APPENDIX A
Acme-Intermediate_Time = "16:47:42.877 EST JUL 02 2008"
Wed Jul
2 17:25:04 2008
Acct-Status-Type = Interim-Update
NAS-IP-Address = 192.168.12.100
NAS-Port = 5060
Version S-C6.1.0
APPENDIX A
Version S-C6.1.0
APPENDIX A
Acme-Intermediate_Time = "16:47:47.186 EST JUL 02 2008"
Version S-C6.1.0
APPENDIX A
Wed Jul
2 17:25:09 2008
NAS-IP-Address = 192.168.12.100
NAS-Port = 5060
Acct-Terminate-Cause = User-Request
Version S-C6.1.0
APPENDIX A
Version S-C6.1.0
APPENDIX A
Acme-SIP-Status = 0
Version S-C6.1.0
Appendix B
CDR Scenario Explanations
This section describes the expected CDR output for a given scenario.
SIP: Call Tear Down Due to Media Guard Timer Expiration

When a SIP call is torn down by the Net-Net SBC due to media timers expiring, the
following standard and VS attributes and their corresponding values will appear in
the CDR stop message:
CDR Output
The following five CDR AVPs must be observed in the same CDR.
Acct-Terminate-Cause = Idle-Timeout
Acme-SIP-Status = 0
Explanation
Acct-Terminate-Cause = Idle-Timeout: This standard RADIUS AVP indicates

the call was ended due to a timer expiring.
h323-disconnect-cause = "6": This VSA AVP indicates the call was ended due
to a timeout.
Acme-Disconnect-Initiator = 3: This VSA AVP indicates the call disconnect

was initiated internally from the Net-Net SBC, and not from an endpoint or due
to an unknown reason.
Acme-Disconnect-Cause = 0:
This VSA AVP indicates that a media timer
expired.
Version S-C6.1.0
Acme-SIP-Status = 0: This VSA AVP indicates the call disconnect was initiated
internally from the Net-Net SBC, and not from an endpoint or due to an
unknown reason for a SIP call.
APPENDIX B
Version S-C6.1.0
Appendix C
Net-Net 4000 S-C6.1.0 RADIUS Dictionary

#
#
#
#
#
#
#
#
#
#
#
#
dictionary.acme
Version:
For documentation on Acme Packet RADIUS attributes, see:

Net-Net Accounting Guide
VENDOR
Version S-C6.1.0
dictionary.acme,v 1.0 2001/11/19

Updated 2009/01/20
Acme
9148
#
# Voice over IP attributes.
#
ATTRIBUTE
Acme-FlowID_FS1_F
ATTRIBUTE
Acme-FlowType_FS1_F
ATTRIBUTE
Acme-Session-Ingress-CallId
ATTRIBUTE
Acme-Session-Egress-CallId
1
2
3
4
string
string
string
string
Acme
Acme
Acme
Acme
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
Acme-Flow-In-Realm_FS1_F
Acme-Flow-In-Src-Addr_FS1_F
Acme-Flow-In-Src-Port_FS1_F
Acme-Flow-In-Dst-Addr_FS1_F
Acme-Flow-In-Dst-Port_FS1_F
10
11
12
13
14
string
ipaddr
integer
ipaddr
integer
Acme
Acme
Acme
Acme
Acme
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
Acme-Flow-Out-Realm_FS1_F
Acme-Flow-Out-Src-Addr_FS1_F
Acme-Flow-Out-Src-Port_FS1_F
Acme-Flow-Out-Dst-Addr_FS1_F
Acme-Flow-Out-Dst-Port_FS1_F
Acme-Calling-Octets_FS1
Acme-Calling-Packets_FS1
Acme-Calling-RTCP-Packets-Lost_FS1
Acme-Calling-RTCP-Avg-Jitter_FS1
Acme-Calling-RTCP-Avg-Latency_FS1
Acme-Calling-RTCP-MaxJitter_FS1
Acme-Calling-RTCP-MaxLatency_FS1
Acme-Calling-RTP-Packets-Lost_FS1
Acme-Calling-RTP-Avg-Jitter_FS1
Acme-Calling-RTP-MaxJitter_FS1
20
21
22
23
24
28
29
32
33
34
35
36
37
38
39
string
ipaddr
integer
ipaddr
integer
integer
integer
integer
integer
integer
integer
integer
integer
integer
integer
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
Acme-Session-Generic-Id
Acme-Session-Ingress-Realm
Acme-Session-Egress-Realm
Acme-Session-Protocol-Type
40
41
42
43
string
string
string
string
Acme
Acme
Acme
Acme
ATTRIBUTE
ATTRIBUTE
Acme-Called-Octets_FS1
Acme-Called-Packets_FS1
44
45
integer
integer
Acme
Acme
APPENDIX C
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
Acme-Called-RTCP-Packets-Lost_FS1
Acme-Called-RTCP-Avg-Jitter_FS1
Acme-Called-RTCP-Avg-Latency_FS1
Acme-Called-RTCP-MaxJitter_FS1
Acme-Called-RTCP-MaxLatency_FS1
Acme-Called-RTP-Packets-Lost_FS1
Acme-Called-RTP-Avg-Jitter_FS1
Acme-Called-RTP-MaxJitter_FS1
46
47
48
49
50
51
52
53
integer
integer
integer
integer
integer
integer
integer
integer
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
# 72 unused
# 73 unused
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
Acme-Session-Charging-Vector
54
Acme-Session-Charging-Function_Address 55
Acme-Firmware-Version
56
57
58
Acme-CDR-Sequence-Number
59
Acme-Session-Disposition
60
Acme-Disconnect-Initiator
61
Acme-Disconnect-Cause
62
Acme-Intermediate_Time
63
Acme-Primary-Routing-Number
64
Acme-Originating-Trunk-Group
65
Acme-Terminating-Trunk-Group
66
Acme-Originating-Trunk-Context
67
Acme-Terminating-Trunk-Context
68
Acme-P-Asserted-ID
69
Acme-SIP-Diversion
70
Acme-SIP-Status
71
string
string
string
string
integer
integer
integer
integer
integer
string
string
string
string
string
string
string
string
integer
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
string
string
string
string
string
string
string
ipaddr
integer
ipaddr
integer
string
ipaddr
integer
ipaddr
integer
string
string
string
ipaddr
integer
ipaddr
integer
string
ipaddr
integer
ipaddr
integer
integer
integer
integer
integer
integer
integer
integer
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme-Ingress-Local-Addr
Acme-Ingress-Remote-Addr
Acme-Egress-Local-Addr
Acme-Egress-Remote-Addr
Acme-FlowID_FS1_R
Acme-FlowType_FS1_R
Acme-Flow-In-Realm_FS1_R
Acme-Flow-In-Src-Addr_FS1_R
Acme-Flow-In-Src-Port_FS1_R
Acme-Flow-In-Dst-Addr_FS1_R
Acme-Flow-In-Dst-Port_FS1_R
Acme-Flow-Out-Realm_FS1_R
Acme-Flow-Out-Src-Addr_FS1_R
Acme-Flow-Out-Src-Port_FS1_R
Acme-Flow-Out-Dst-Addr_FS1_R
Acme-Flow-Out-Dst-Port_FS1_R
Acme-FlowID_FS2_F
Acme-FlowType_FS2_F
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
Version S-C6.1.0
APPENDIX C
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
Version S-C6.1.0
109
110
111
integer
integer
integer
Acme
Acme
Acme
ATTRIBUTE
Acme-FlowID_FS2_R
112
string
ATTRIBUTE
Acme-FlowType_FS2_R
113
string
ATTRIBUTE
114
string
ATTRIBUTE
115
ipaddr
ATTRIBUTE
116
integer
ATTRIBUTE
117
ipaddr
ATTRIBUTE
118
integer
ATTRIBUTE
119
string
ATTRIBUTE
120
ipaddr
ATTRIBUTE
121
integer
ATTRIBUTE
122
ipaddr
ATTRIBUTE
123
integer
ATTRIBUTE
124
integer
ATTRIBUTE
125
integer
ATTRIBUTE
126
integer
ATTRIBUTE
127
integer
ATTRIBUTE
128
integer
ATTRIBUTE
129
integer
ATTRIBUTE
130
integer
ATTRIBUTE
131
integer
ATTRIBUTE
132
integer
ATTRIBUTE
133
integer
ATTRIBUTE
Acme-Egress-Final-Routing-Number
134
string
ATTRIBUTE
Acme-Session-Ingress-RPH
135
string
ATTRIBUTE
Acme-Session-Egress-RPH
136
string
ATTRIBUTE
Acme-Ingress-Network-Interface-Id
137
string
ATTRIBUTE
Acme-Ingress-Vlan-Tag-Value
138
integer
ATTRIBUTE
Acme-Egress-Network-Interface-Id
139
string
ATTRIBUTE
Acme-Egress-Vlan-Tag-Value
140
integer
ATTRIBUTE
Acme-Refer-Call-Transfer-Id
141
string
# Attributes 142-150 are reserved for future use.
ATTRIBUTE
151
integer
ATTRIBUTE
Acme-Calling-MOS
152
integer
ATTRIBUTE
153
integer
ATTRIBUTE
Acme-Called-MOS
154
integer
# Attributes 155-171 for IPV6 are reserved for future use.
ATTRIBUTE
Acme-Custom-VSA-200
200
string
ATTRIBUTE
Acme-Custom-VSA-201
201
string
ATTRIBUTE
Acme-Custom-VSA-202
202
string
ATTRIBUTE
Acme-Custom-VSA-203
203
string
ATTRIBUTE
Acme-Custom-VSA-204
204
string
ATTRIBUTE
Acme-Custom-VSA-205
205
string
ATTRIBUTE
Acme-Custom-VSA-206
206
string
ATTRIBUTE
Acme-Custom-VSA-207
207
string
ATTRIBUTE
Acme-Custom-VSA-208
208
string
ATTRIBUTE
Acme-Custom-VSA-209
209
string
ATTRIBUTE
Acme-Custom-VSA-210
210
string
ATTRIBUTE
Acme-Custom-VSA-211
211
string
ATTRIBUTE
Acme-Custom-VSA-212
212
string
ATTRIBUTE
Acme-Custom-VSA-213
213
string
ATTRIBUTE
Acme-Custom-VSA-214
214
string
ATTRIBUTE
Acme-Custom-VSA-215
215
string
ATTRIBUTE
Acme-Custom-VSA-216
216
string
ATTRIBUTE
Acme-Custom-VSA-217
217
string
ATTRIBUTE
Acme-Custom-VSA-218
218
string
ATTRIBUTE
Acme-Custom-VSA-219
219
string
ATTRIBUTE
Acme-Custom-VSA-220
220
string
ATTRIBUTE
Acme-Custom-VSA-221
221
string
ATTRIBUTE
Acme-Custom-VSA-222
222
string
ATTRIBUTE
Acme-Custom-VSA-223
223
string
ATTRIBUTE
Acme-Custom-VSA-224
224
string
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Acme
APPENDIX C
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
ATTRIBUTE
Acme-Custom-VSA-225
Acme-Custom-VSA-226
Acme-Custom-VSA-227
Acme-Custom-VSA-228
Acme-Custom-VSA-229
Acme-Custom-VSA-230
ATTRIBUTE
Acme-User-Class
225
226
227
228
229
230
string
string
string
string
string
string
254
string
Acme
Acme
Acme
Acme
Acme
Acme
Acme
Version S-C6.1.0
Appendix D
Comma-Delimited Entries for Local Files
Local File Format
Appendix C contains three tables that show where, in locally-generated CSV files,
specific VSAs appear. There is one table for each of the following type of record:
Start, Stop, Interim.
For more information about this feature and how to enable it, refer to the Local CDR
Storage and FTP Push (53) section in this guides Configuring Accounting (35)
chapter.
Start Record CSV
Placement
Version S-C6.1.0
CSV Placement
Attribute Name
VSA ID Number
Acct-Status-Type
NAS-IP-Address
NAS-Port
Acct-Session-Id
Acme-Session--Egress-CallId
43
Acme-Session--Generic-Id
40
Calling-Station-Id
31
10
Called-Station-Id
30
11
h323-setup-time
12
h323-connect-time
13
139
14
140
15
137
16
138
17
42
18
41
19
Acme-FlowId_FS1_F
20
Acme-FlowType_FS1_F
21
10
22
11
23
12
24
13
25
14
APPENDIX D
CSV Placement
Attribute Name
VSA ID Number
26
20
27
21
28
22
29
23
30
24
31
Acme-FlowID_FS1_R
78
32
Acme-FlowType_FS1_R
79
33
80
34
81
35
82
36
83
37
84
38
85
39
86
40
87
41
88
42
89
43
Acme-FlowID_FS2_F
90
44
Acme-FlowType_FS2_F
91
45
92
46
93
47
94
48
95
49
96
50
97
51
98
52
99
53
100
54
101
55
Acme-FlowID_FS2_R
112
56
Acme-FlowType_FS2_R
113
57
114
58
115
59
116
Version S-C6.1.0
APPENDIX D
Version S-C6.1.0
CSV Placement
Attribute Name
VSA ID Number
60
117
61
118
62
119
63
120
64
121
65
122
66
123
67
54
68
Acme-Session-Charging-Function_Address
55
69
56
70
57
71
58
72
64
73
65
74
66
75
67
76
68
77
Acme-P-Asserted-ID
69
78
74
79
75
80
76
81
77
82
Acme-SIP-Diversion
70
83
134
84
135
85
136
86
Acme-Custom-VSA-200
200
87
Acme-Custom-VSA-201
201
88
Acme-Custom-VSA-202
202
89
Acme-Custom-VSA-203
203
90
Acme-Custom-VSA-204
204
91
Acme-Custom-VSA-205
205
92
Acme-Custom-VSA-206
206
93
Acme-Custom-VSA-207
207
APPENDIX D
CSV Placement
Attribute Name
VSA ID Number
94
Acme-Custom-VSA-208
208
95
Acme-Custom-VSA-209
209
96
Acme-Custom-VSA-210
210
97
Acme-Custom-VSA-211
211
98
Acme-Custom-VSA-212
212
99
Acme-Custom-VSA-213
213
100
Acme-Custom-VSA-214
214
101
Acme-Custom-VSA-215
215
102
Acme-Custom-VSA-216
216
103
Acme-Custom-VSA-217
217
104
Acme-Custom-VSA-218
218
105
Acme-Custom-VSA-219
219
106
Acme-Custom-VSA-220
220
107
Acme-Custom-VSA-221
221
108
Acme-Custom-VSA-222
222
109
Acme-Custom-VSA-223
223
110
Acme-Custom-VSA-224
224
111
Acme-Custom-VSA-225
225
112
Acme-Custom-VSA-226
226
113
Acme-Custom-VSA-227
227
114
Acme-Custom-VSA-228
228
115
Acme-Custom-VSA-229
229
116
Acme-Custom-VSA-230
230
CSV Placement
Attribute Name
VSA ID Number
Acct-Status-Type
NAS-IP-Address
NAS-Port
Acct-Session-Id
43
Interim Record CSV

Placement
Version S-C6.1.0
APPENDIX D
Version S-C6.1.0
CSV Placement
Attribute Name
VSA ID Number
40
Calling-Station-Id
31
10
Called-Station-Id
30
11
h323-setup-time
12
h323-connect-time
13
139
14
140
15
137
16
138
17
42
18
41
19
Acme-FlowId_FS1_F
20
Acme-FlowType_FS1_F
21
10
22
11
23
12
24
13
25
14
26
20
27
21
28
22
29
23
30
24
31
32
32
33
33
34
34
35
35
36
36
37
37
38
38
39
39
28
40
29
41
151
APPENDIX D
CSV Placement
Attribute Name
VSA ID Number
42
Acme-Calling-MOS
152
43
Acme-FlowID_FS1_R
78
44
Acme-FlowType_FS1_R
79
45
80
46
81
47
82
48
83
49
84
50
85
51
86
52
87
53
88
54
89
55
46
56
47
57
48
58
49
59
50
60
51
61
52
62
53
63
44
64
153
65
Acme-Called-MOS
154
66
45
67
Acme-FlowID_FS2_F
90
68
Acme-FlowType_FS2_F
91
69
92
70
93
71
94
72
95
73
96
74
97
75
98
Version S-C6.1.0
APPENDIX D
Version S-C6.1.0
CSV Placement
Attribute Name
VSA ID Number
76
99
77
100
78
101
79
104
80
105
81
106
82
107
83
108
84
109
85
110
86
111
87
102
88
103
89
Acme-FlowID_FS2_R
112
90
Acme-FlowType_FS2_R
113
91
114
92
115
93
116
94
117
95
118
96
119
97
120
98
121
99
122
100
123
101
126
102
Acme-Called--RTCP-Avg-Jitter_FS2
127
103
Acme-Called--RTCP-Avg-Latency_FS2
128
104
Acme-Called--RTCP-MaxJitter_FS2
129
105
130
106
131
107
132
108
133
109
124
APPENDIX D
CSV Placement
Attribute Name
VSA ID Number
110
125
111
54
112
Acme-Session-Charging-Function_Address
55
113
56
114
57
115
58
116
64
117
65
118
66
119
67
120
68
121
Acme-P-Asserted-ID
69
122
74
123
75
124
76
125
77
126
Acme-SIP-Diversion
70
127
Acme-Intermediate_Time
63
128
134
129
135
130
136
131
Acme-Custom-VSA-200
200
132
Acme-Custom-VSA-201
201
133
Acme-Custom-VSA-202
202
134
Acme-Custom-VSA-203
203
135
Acme-Custom-VSA-204
204
136
Acme-Custom-VSA-205
205
137
Acme-Custom-VSA-206
206
138
Acme-Custom-VSA-207
207
139
Acme-Custom-VSA-208
208
140
Acme-Custom-VSA-209
209
141
Acme-Custom-VSA-210
210
142
Acme-Custom-VSA-211
211
143
Acme-Custom-VSA-212
212
Version S-C6.1.0
APPENDIX D
CSV Placement
Attribute Name
VSA ID Number
144
Acme-Custom-VSA-213
213
145
Acme-Custom-VSA-214
214
146
Acme-Custom-VSA-215
215
147
Acme-Custom-VSA-216
216
148
Acme-Custom-VSA-217
217
149
Acme-Custom-VSA-218
218
150
Acme-Custom-VSA-219
219
151
Acme-Custom-VSA-220
220
152
Acme-Custom-VSA-221
221
153
Acme-Custom-VSA-222
222
154
Acme-Custom-VSA-223
223
155
Acme-Custom-VSA-224
224
156
Acme-Custom-VSA-225
225
157
Acme-Custom-VSA-226
226
158
Acme-Custom-VSA-227
227
159
Acme-Custom-VSA-228
228
160
Acme-Custom-VSA-229
229
161
Acme-Custom-VSA-230
230
CSV Placement
Attribute Name
VSA ID Number
Acct-Status-Type
NAS-IP-Address
NAS-Port
Acct-Session-Id
43
40
Calling-Station-Id
31
10
Called-Station-Id
30
11
Acct-Terminate-Cause
12
Acct-Session-Time
Stop Record CSV

Placement
Version S-C6.1.0
APPENDIX D
CSV Placement
Attribute Name
13
h323-setup-time
14
h323-connect-time
15
h323-disconnect-time
16
h323-disconnect-cause
17
139
18
140
19
137
20
138
21
42
22
41
23
Acme-FlowId_FS1_F
24
Acme-FlowType_FS1_F
25
10
26
11
27
12
28
13
29
14
30
20
31
21
32
22
33
23
34
24
35
32
36
33
37
34
38
35
39
36
40
37
41
38
42
39
43
28
44
29
45
151
46
Acme-Calling-MOS
152
VSA ID Number
Version S-C6.1.0
APPENDIX D
Version S-C6.1.0
CSV Placement
Attribute Name
VSA ID Number
47
Acme-FlowID_FS1_R
78
48
Acme-FlowType_FS1_R
79
49
80
50
81
51
82
52
83
53
84
54
85
55
86
56
87
57
88
58
89
59
46
60
47
61
48
62
49
63
50
64
51
65
52
66
53
67
44
68
45
69
153
70
Acme-Called-MOS
154
71
Acme-FlowID_FS2_F
90
72
Acme-FlowType_FS2_F
91
73
92
74
93
75
94
76
95
77
96
78
97
79
98
80
99
APPENDIX D
CSV Placement
Attribute Name
VSA ID Number
81
100
82
101
83
104
84
105
85
106
86
107
87
108
88
109
89
110
90
111
91
102
92
103
93
Acme-FlowID_FS2_R
112
94
Acme-FlowType_FS2_R
113
95
114
96
115
97
116
98
117
99
118
100
119
101
120
102
121
103
122
104
123
105
126
106
Acme-Called--RTCP-Avg-Jitter_FS2
127
107
Acme-Called--RTCP-Avg-Latency_FS2
128
108
Acme-Called--RTCP-MaxJitter_FS2
129
109
130
110
131
111
132
112
133
113
124
114
125
Version S-C6.1.0
APPENDIX D
Version S-C6.1.0
CSV Placement
Attribute Name
VSA ID Number
115
54
116
Acme-Session-Charging-Function-Address
55
117
56
118
57
119
58
120
64
121
65
122
66
123
67
124
68
125
Acme-P-Asserted-ID
69
126
74
127
75
128
76
129
77
130
Acme-SIP-Diversion
70
131
Acme-Session-Disposition
60
132
Acme-Disconnect-Initiator
61
133
Acme-Disconnect-Cause
62
134
Acme-SIP-Status
71
135
134
136
135
137
136
138
Acme-Refer-Call-Transfer-Id
141
139
Acme-Custom-VSA-200
200
140
Acme-Custom-VSA-201
201
141
Acme-Custom-VSA-202
202
142
Acme-Custom-VSA-203
203
143
Acme-Custom-VSA-204
204
144
Acme-Custom-VSA-205
205
145
Acme-Custom-VSA-206
206
146
Acme-Custom-VSA-207
207
147
Acme-Custom-VSA-208
208
148
Acme-Custom-VSA-209
209
APPENDIX D
CSV Placement
Attribute Name
VSA ID Number
149
Acme-Custom-VSA-210
210
150
Acme-Custom-VSA-211
211
151
Acme-Custom-VSA-212
212
152
Acme-Custom-VSA-213
213
153
Acme-Custom-VSA-214
214
154
Acme-Custom-VSA-215
215
155
Acme-Custom-VSA-216
216
156
Acme-Custom-VSA-217
217
157
Acme-Custom-VSA-218
218
158
Acme-Custom-VSA-219
219
159
Acme-Custom-VSA-220
220
160
Acme-Custom-VSA-221
221
161
Acme-Custom-VSA-222
222
162
Acme-Custom-VSA-223
223
163
Acme-Custom-VSA-224
224
164
Acme-Custom-VSA-225
225
165
Acme-Custom-VSA-226
226
166
Acme-Custom-VSA-227
227
167
Acme-Custom-VSA-228
228
168
Acme-Custom-VSA-229
229
169
Acme-Custom-VSA-230
230
Version S-C6.1.0

SBC Sc610 Accounting

Uploaded by

Copyright:

Available Formats

SBC Sc610 Accounting

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SBC Sc610 Accounting

Uploaded by

Copyright:

Available Formats

What is the document about?

What is the document about?

What information is provided about accounting?

What information is provided about accounting?

Oracle Communications Session

About this Guide

The Net-Net SBCs accounting-based on Remote Authentication Dial-in

How to configure RADIUS accounting support, and the features related to it

Local CDR storage and FTP file push

Acme Packet 4500 System

Contains information about the components and

ACLI Configuration Guide

Contains information about the administration and

ACLI Reference Guide

Contains explanations of how to use the ACLI, as an

Contains information about Net-Net SBC logs,

Oracle Communications Session Border Controller Accounting Guide iii

ABOUT THIS GUIDE

MIB Reference Guide

Contains information about Management

Contains information about the SBCs accounting

Adds information about the Net-Net 4500

August 21, 2010

Updates Local CDR Storage and FTP Push

August 26, 2010

Removes redundant Radius CDR Content

Creates new Appendix B to document CDR

iv Oracle Communications Session Border Controller Accounting Guide

About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Oracle Communications Session Border Controller Accounting Guide v

Configuring Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

vi Oracle Communications Session Border Controller Accounting Guide

More About File Rotation Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Oracle Communications Session Border Controller Accounting Guide vii

Interim Record CSV Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

viii Oracle Communications Session Border Controller Accounting Guide

Using RADIUS with the Net-Net SBC

SLA monitoringThe Net-Net SBC supports RADIUS attributes that provide

TroubleshootingObtain information about calls that can help you to identify

Standard RADIUS Attributes

Oracle Communications Session Border Controller Accounting Guide 9

USING RADIUS WITH THE NET-NET SBC

The Standard RADIUS Attributes Dictionary (10) is a dictionary of the standard

Interim-UpdateIndicates to the accounting server that the session parameters

OnMarks the start of accounting

OffMarks the end of accounting

RFC 2865, Remote Authentication Dial In User Service (RADIUS), Rigney, et

RFC 2866, RADIUS Accounting, C. Rigney, June 2000

The table below lists and describes standard RADIUS attributes.

IP address of the SIP proxy or the

SIP proxy port or the H.323 stacks

10 Oracle Communications Session Border Controller Accounting Guide

USING RADIUS WITH THE NET-NET SBC

To field value of the SIP INVITE

From field value of the SIP INVITE

Value, if any, set in the optional

The remote server to which the

Whether this Accounting Request

Either the Call-ID field value of