Account Guide

Net-Net 4000
Accounting Guide
Release Version C6.0.0
Acme Packet, Inc.

71 Third Avenue
Burlington, MA 01803
t 781-328-4400
f 781-425-5077
www.acmepacket.com
Last updated: August 1, 2008

Document Number: 400-0015-60 Rev. 1.10
Notices
20022008 Acme Packet, Inc., Burlington, Massachusetts. All rights reserved. Acme Packet, Session Aware
Networking, Net-Net, and related marks are trademarks of Acme Packet, Inc. All other brand names are
trademarks, registered trademarks, or service marks of their respective companies or organizations.
Patents Pending, Acme Packet, Inc.
The Acme Packet Documentation Set and the Net-Net systems described therein are the property of Acme
Packet, Inc. This documentation is provided for informational use only, and the information contained within
the documentation is subject to change without notice.
Acme Packet, Inc. shall not be liable for any loss of profits, loss of use, loss of data, interruption of business, nor
for indirect, special, incidental, consequential, or exemplary damages of any kind, arising in any way in
connection with the Acme Packet software or hardware, third party software or hardware, or the
documentation. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential
damages, so the above exclusions may not apply. These limitations are independent from all other provisions
and shall apply notwithstanding the failure of any remedy provided herein.
Copying or reproducing the information contained within this documentation without the express written
permission of Acme Packet, Inc., 71 Third Avenue, Burlington, MA 01803, USA is prohibited. No part may be
reproduced or retransmitted.
Acme Packet Net-Net products are protected by one or more of the following patents: United States: 7072303,
7028092, 7002973, 7133923, 7031311, 7142532, 7151781. France: 1342348, 1289225, 1280297, 1341345, 1347621.
Germany: 1342348, 1289225, 1280297, 1341345, 1347621. United Kingdom: 1342348, 1289225, 1280297,
1341345, 1347621. Other patents are pending.
About this Guide
Overview
The Net-Net 4000 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.
About Net-Net Release version C6.0.0 is supported on the Net-Net 4000 series platforms. This series
4000 Software contains two systems, the Net-Net 4250 and the Net-Net 4500. When C6.0.0 is
Releases compiled to run on the Net-Net 4250 system, Acme Packet calls the image C6.0.0.
When C6.0.0 is compiled to run on the Net-Net 4500 system, Acme Packet calls the
image CX6.0.0.
Who is Acme Packet?

Acme Packet enables service providers to deliver trusted, first class interactive
communicationsvoice, video and multimedia sessionsacross IP network
borders. Our Net-Net family of session border controllers satisfy critical security,
service assurance and regulatory requirements in wireline, cable and wireless
networks. Our deployments support multiple applicationsfrom VoIP trunking to
hosted enterprise and residential services; multiple protocolsSIP, H.323,
MGCP/NCS and H.248; and multiple border pointsinterconnect, access network
and data center.
Established in August 2000 by networking industry veterans, Acme Packet is a public
company trading on the NASDAQ and headquartered in Burlington, Massachusetts.
Version C6.0.0 Acme Packet, Inc. Technical Publications iii

ABOUT THIS GUIDE
Related Documentation
The following table lists related documents.
Document Name Document Description
Net-Net 4250 Hardware Contains information about the components and

Installation Guide installation of the Net-Net SBC.
(400-0003-00)
Net-Net 4500 Hardware Contains information about the components and

Installation Guide installation of the Net-Net 4500 SBC.
(400-0101-00)
Net-Net 4000 Configuration Contains information about the administration and

Guide (400-0061-00) software configuration of the Net-Net SBC.
Net-Net 4000 ACLI Reference Contains explanations of how to use the ACLI, as
Guide an alphabetical listings and descriptions of all ACLI
(400-0062-00) commands and configuration parameters.
Net-Net 4000 Maintenance and Contains information about Net-Net SBC logs,
Troubleshooting Guide performance announcements, system
(400-0063-00) management, inventory management, upgrades,
working with configurations, and managing
backups and archives.
Net-Net 4000 MIB Reference Contains information about Management

Guide Information Base (MIBs), Acme Packets enterprise
(400-0010-00) 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.
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
Technical Assistance
If you need technical assistance with Acme Packet products, you can obtain it on-
line by going to https://support.acmepacket.com. With your customer identification
number and password, you can access Acme Packets on-line resources 24 hours a
day. If you do not have the information required to access the site, send an email to
[email protected] requesting a login.
In the event that you are experiencing a critical service outage and require live
assistance, you can contact the Acme Packet Technical Assistance Center emergency
hotline:
iv Net-Net 4000 Accounting Guide Version C6.0.0

ABOUT THIS GUIDE
From the United States, Canada, and Mexico call: 1 866 226 3758
From all other locations, call: +1 781 756 6920
Please note that a valid support/service contract with Acme Packet is required to
obtain technical assistance.
Customer Questions, Comments, or Suggestions

Acme Packet is committed to providing our customers with reliable documentation.
If you have any questions, comments, or suggestions regarding our documentation,
please contact your Acme Packet customer support representative directly or email
[email protected].
Contact Us
Acme Packet
71 Third Avenue
Burlington, MA 01803 USA
t 781 328 4400
f 781 425 5077
www.acmepacket.com
Version C6.0.0 Acme Packet, Inc. Technical Publications v

ABOUT THIS GUIDE
vi Net-Net 4000 Accounting Guide Version C6.0.0

Contents
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
About Net-Net 4000 Software Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Who is Acme Packet? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
Customer Questions, Comments, or Suggestions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Contact Us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Using RADIUS with the Net-Net SBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Standard RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Standard RADIUS Attributes Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
RADIUS Accounting Termination Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
VSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Acme Packet RADIUS VSAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
New in Release C6.0.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Notes on Media Flow Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Acme Packet VSA Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Cisco Systems RADIUS Decodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Mappings and Disconnect Cause Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SIP, H.323, and Q.850 Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SIP Status to H.323 Disconnect Reason Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SIP Status to H.323 RAS Error Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
SIP Status to H.323 Release Complete Reason Error Mapping. . . . . . . . . . . . . . . . . . . . . . 31
Q.850 Cause to H.323 Release Complete Reason Mapping . . . . . . . . . . . . . . . . . . . . . . . . 31
Version C6.0.0 Acme Packet, Inc. Technical Publications vii

CONTENTS
SIP-SIP Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

SIP-H.323 Calls with Interworking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
SIP Events and Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
H.323 Events and Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
H.225 RAS Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Configuring Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Accounting for SIP and H.323. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Call Detail Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
RAS Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
RADIUS Accounting Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Session Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
RADIUS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Session Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
ACLI Instructions and Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Accessing the Accounting and Accounting Servers Configuration . . . . . . . . . . . . . . . . . . .41
Setting Up the Account Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Setting Up Accounting Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Local CDR Storage and FTP Push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
About the Record Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
CDR File Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Local Storage Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
File Size and Rotation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
More About File Rotation Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
CDR Local File Format Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Recommended Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Accessing the Accounting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Enabling Local CDR Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Setting the CSV File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Enabling FTP Push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Per Realm Accounting Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Configurable Intermediate Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
RADIUS CDR Content Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Preventing Duplicate RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
RADIUS Attribute Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
RADIUS CDR Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
viii Net-Net 4000 Accounting Guide Version C6.0.0

CONTENTS
Caveats for H.323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Potential OOS Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
ACLI Instructions and Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
RADIUS CDR Content Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
ACLI Instructions and Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Accessing the Accounting Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Preventing Duplicate RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
RADIUS Attribute Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Accounting Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
RADIUS Accounting Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Alarm Generation and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
RADIUS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Status and Statistics Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
ACLI Show RADIUS Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
RADIUS CDR Samples for SIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Basic Successful SIP Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Unsuccessful SIP Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
SIP Call On Hold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Appendix B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Net-Net 4000 C6.0.0 RADIUS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Appendix C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Local File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Start Record CSV Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Interim Record CSV Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Stop Record CSV Placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Version C6.0.0 Acme Packet, Inc. Technical Publications ix

CONTENTS
x Net-Net 4000 Accounting Guide Version C6.0.0

1 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 (37) 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 Net-
Net 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 C6.0.0 Acme Packet, Inc. Technical Publications 11

USING RADIUS WITH THE NET-NET SBC
The Standard RADIUS Attributes Dictionary (12) 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):
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)
Standard RADIUS The table below lists and describes standard RADIUS attributes.
Attributes
Dictionary
Attribute
Attribute
Attribute Name Attribute Description Value Messages
Value
Type
NAS-IP-Address IP address of the SIP proxy or the 4 IP Start

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

call signaling RAS port. Interim-Update
Stop
On
Off
12 Net-Net 4000 Accounting Guide Version C6.0.0

Attribute
Attribute
Value
Type
Called-Station-Id To field value of the SIP INVITE 30 string Start

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

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

NAS-ID field for the accounting Interim-Update
server that you configure as part of Stop
the accounting configuration. This On
identifier sets the value that the Off
remote server (the accounting
server) uses to identify the Net-Net
SBC so that RADIUS messages can
be transmitted.
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-Status-Type Whether this Accounting Request 40 integer Start (1)

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

the SIP INVITE message, the Interim-Update
callIdentifier of the H.323 Stop
message, or RADIUS client On
information. Off
Acct-Session- How much time in seconds the 46 integer Interim-Update

Time user has received service. Stop
Off
Acct-Terminate- How or why the session ended. 49 integer Stop

Cause Off

RADIUS The table below describes the possible session termination causes for the Acct-
Accounting Terminate-Cause RADIUS attribute.
Termination
Causes
Related
RADIUS
Integer Value
Termination Termination Event Message
(per RFC
Cause
2059)
User Request 1 A SIP BYE message. Stop
User Error 17 Input from user is erroneous; for example, SIP Stop
signaling failed to establish the session. Used
in combination with the Cisco Systems
Disconnect Cause.
(This termination cause is not used for H.323.)
Lost Service 3 Service cannot be sustained for reasons such Stop

as a lost connection.
Admin Reset 6 Net-Net SBC hard reset occurred: A hard reset Off
occurs when you use the front panels orange
Reset button; it reboots the Net-Net SBC.
Admin Reboot 7 Net-Net SBC gracefully rebooted. Off
NAS Request 10 RADIUS server is disabled; session terminated Off

for non-error reason.
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 Acme Packets vendor identification number is 9148. This number refers to the 4-
RADIUS VSAs octet 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

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 (61) 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 C6.0.0 The following changes appear in Release C6.0.0; they include a changes made in
Release C5.1.1 (p3).
A new VSA appears for SIP REFER call method transfer support. It is:
Acme-Refer-Call-Transfer-ID (number 141)
Notes on Media Flow The Net-Net SBC records media flow attributes in RADIUS CDRs, and there can be
Attributes 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
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 Attribute
Attribute Name Attribute Description Messages
Value Value Type
General Attributes
Acme-CDR-Sequence- Sequence number (that increases by 1) 59 integer Start

Number the Net-Net SBC generates; recorded in Interim-Update
each CDR. Stop
Acme-Intermediate- Time interval at which periodic interim 63 string Interim-Update

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

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

Version Net-Net SBC. Interim-Update
Stop
Acme-User-Class Identifies the type user on the Net-Net 254 string Start
SBC; used for RADIUS authentication Stop
only and does not apply to accounting.
General Flow Attributes
Acme-FlowID_FS1_F Unique identifier for every media flow 1 string Start

processed by the Net-Net SBC, flow-set 1 Interim-Update
forward direction. Stop
On
This VSA always prefaces other flow Off
information.
Acme-FlowID_FS1_R Unique identifier for every media flow 78 string Start

reverse direction. Stop
On
information.
Acme-FlowID_FS2_F Unique identifier for every media flow 90 string Start

forward direction. Stop
On
information.
Acme-FlowID_FS2_R Unique identifier for every media flow 112 string Start
reverse direction. Stop
On
information.
Acme-FlowType_FS1_F Codec that describes the flow, flow-set 1 2 string Start

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

Attribute Attribute
Value Value Type
Acme-FlowType_FS1_R Codec that describes the flow, flow-set 1 79 string Start

reverse direction: PCMU, PCMA, G726, Interim-Update
G723, G728, G729, H261, H263, T38. Stop
On
Off
Acme-FlowType_FS2_F Codec that describes the flow, flow-set 2 91 string Start

forward direction: PCMU, PCMA, G726, Interim-Update
G723, G728, G729, H261, H263, T38. Stop
On
Off
Acme-FlowType_FS2_R Codec that describes the flow, flow-set 2 113 string Start
reverse direction: PCMU, PCMA, G726, Interim-Update
G723, G728, G729, H261, H263, T38. Stop
On
Off
Inbound Flow Attributes
Acme-Flow-In- Inbound realm identifier for flow-set 1, 10 string Start

Realm_FS1_F forward direction. Interim-Update
Stop

Realm_FS1_R reverse direction. Interim-Update
Stop

Stop

Stop
Acme-Flow-In-Src- Inbound source address (remote) 11 IP address Start

Addr_FS1_F information for flow-set 1, forward Interim-Update
direction. Stop

Addr_FS1_R information for flow-set 1, reverse Interim-Update
direction. Stop

direction. Stop

direction. Stop
Acme-Flow-In-Src- Inbound source (remote) port information 12 integer Start

Port_FS1_F for flow-set 1, forward direction. Interim-Update
Stop

Port_FS1_R for flow-set 1, reverse direction. Interim-Update
Stop

Attribute Attribute
Value Value Type

Port_FS2_F for flow-set 2, forward direction. Interim-Update
Stop

Port_FS2_R for flow-set 2, reverse direction. Interim-Update
Stop
Acme-Flow-In-Dst- Inbound destination (local) address 13 IP address Start

Addr_FS1_F information (the IPv4 address field value Interim-Update
of the steering pool configuration) for Stop
flow-set 1, forward direction.

Addr_FS1_R information (the IPv4 address field value Interim-Update
flow-set 1, reverse direction.


Acme-Flow-In-Dst- Inbound destination (local) port 14 integer Start

Port_FS1_F information (a port in the range between Interim-Update
the start port and end port field values of Stop
the steering pool configuration) for flow-
set 1, forward direction.

Port_FS1_R information (a port in the range between Interim-Update
set 1, reverse direction.

Port_FS2_F information (a port in the range between Interim-Update
set 2, forward direction.

Port_FS2_R information (a port in the range between Interim-Update
set 2, reverse direction.
Outbound Flow Attributes
Acme-Flow-Out- Outbound realm identifier for flow-set 1, 20 string Start

Stop

Stop

Attribute Attribute
Value Value Type

Stop

Stop
Acme-Flow-Out-Src- Outbound source (local) address 21 IP address Start

of the steering port configuration) for Stop



Acme-Flow-Out-Src- Outbound source (local) port information 22 integer Start

Port_FS1_F for flow-set 1, forward direction (a port in Interim-Update
the range between the start port and end Stop
port field values of the steering port
configuration).

Port_FS1_R for flow-set 1, reverse direction (a port in Interim-Update
configuration).

Port_FS2_F for flow-set 2, forward direction (a port in Interim-Update
configuration).

Port_FS2_R for flow-set 2, reverse direction (a port in Interim-Update
configuration).
Acme-Flow-Out-Dst- Outbound destination (remote) address 23 IP address Start

direction. Stop

direction. Stop

Attribute Attribute
Value Value Type

direction. Stop

direction. Stop
Acme-Flow-Out-Dst- Outbound destination (remote) port 24 integer Start

Port_FS1_F information for flow-set 1, forward Interim-Update
direction. Stop

Port_FS1_R information for flow-set 1, reverse Interim-Update
direction. Stop

Port_FS2_F information for flow-set 2, forward Interim-Update
direction. Stop

Port_FS2_R information for flow-set 2, reverse Interim-Update
direction. Stop
Session Attributes
Acme-Session-Generic- Common ID shared by H.323 and SIP call 40 string Start

Id legs of a session. This attribute is a Interim-Update
combination of a time stamp (measured Stop
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.
This VSA is not configurable; all CDRs

contain this attribute.
Acme-Session-Ingress- Call ID generated by the originating 3 string Start

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

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

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


Attribute Attribute
Value Value Type
Acme-Session-Egress- Explicitly identifies the egress realm, and 42 string Start

Realm contains the name of the egress realm Interim-Update
for the session. All CDRs contain this Stop
attribute.
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-Protocol- Signaling protocol used for a particular 43 string Start

Type leg of a session (in the case of IWF, there Interim-Update
may be two legs). This attribute contains Stop
the signaling protocol type; for example,
SIP or H323.

Acme-Session- Appears when the Net-Net SBC inserts, 54 string Start

Charging-Vector passes, or deletes the P-Charging-Vector Interim-Update
header (SIP). Stop
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-Session- Appears when the Net-Net SBC inserts, 55 string Start

Charging- passes, or deletes the P-Charging- Interim-Update
Function_Address Function-Address. Stop
This attribute is only populated for SIP

CDRs, and is not populated if the Net-Net
SBC does not have P-Charging-Function-
Address information.
Acme-Session- Status of the call attempt as it 60 integer Start

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

initiation and an alerting event. Interim-Update
Stop
Acme-P-Asserted-ID P-Asserted ID as described in RFC 3325. 69 integer Start

Interim-Update
Stop
Acme-SIP-Diversion SIP Diversion header; communicates to 70 integer Start

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

Number context (or ingress SIP Request-URI). Interim-Update
Stop

Attribute Attribute
Value Value Type
Acme-Egress-Final- Final routing number and phone context 134 integer Stop
Routing-Number (or egress SIP Request-URI).
Acme-Disconnect- Initiator of a call disconnect. 61 integer Stop

Initiator
Acme-Disconnect- Q.850 cause code value. 62 integer Stop

Cause
Acme-SIP-Status SIP status code for RFC 3326 support. 71 integer Stop
Acme-Originating- Originating trunk group. 65 string Start

Trunk-Group Interim-Update
Stop
Acme-Originating- Originating trunk group context. 67 string Start

Trunk-Context Interim-Update
Stop
Acme-Terminating- Terminating trunk group. 66 string Start

Trunk-Group Interim-Update
Stop
Acme-Terminating- Terminating trunk group context. 68 string Start

Trunk-Context Interim-Update
Stop
Acme-Ingress-Local- Signaling IP address and port of the 74 string Start

Addr ingress Net-Net SBC signaling interface. Interim-Update
Stop
Acme-Ingress-Remote- Signaling IP address and port of the 75 string Start

Addr ingress remote signaling element. Interim-Update
Stop
Acme-Egress-Local- Signaling IP address and port of the 76 string Start

Addr egress Net-Net SBC signaling interface. Interim-Update
Stop
Acme-Egress-Remote- Signaling IP address and port of the 77 string Start

Addr destination signaling element. Interim-Update
Stop
Acme-Session-Ingress- RPH value received in the incoming call 135 string Start
RPH (e.g., ets.1). Interim-Update
Stop
Only populated for NSEP calls.
Acme-Session-Egress- RPH value sent in the outgoing call (e.g., 136 string Start
RPH ets.3). Interim-Update
Stop
Only populated for NSEP calls.
Acme-Ingress-Network- To differentiate overlapping IP address 137 string Start

Interface-Id spaces (with the Acme-Ingress-Vlan-Tag- Interim-Update
Value), gives the ID of the ingress Stop
network interface.
Acme-Ingress-Vlan-Tag- To differentiate overlapping IP address 138 integer Start

Value spaces (with the Acme-Ingress-Network- Interim-Update
Interface-Id), gives the VLAN tag. Stop

Attribute Attribute
Value Value Type
Acme-Egress-Network- To differentiate overlapping IP address 139 string Start

Interface-Id spaces (with the Acme-Egress-Vlan-Tag- Interim-Update
Value), gives the ID of the ingress Stop
network interface.
Acme-Egress-Vlan-Tag- To differentiate overlapping IP address 140 integer Start

Value spaces (with the Acme-Egress-Network- Interim-Update
Interface-Id), gives the VLAN tag. Stop
Acme-Refer-Call- For SIP REFER call method transfer, 141 string Stop
Transfer-Id communicates a call has been tranferred
from the referer to the referree
New to Release C6.0.0
QoS Attributes
Acme-Calling-RTCP- Total lost packets reported via Real-time 32 integer Stop

Packets-Lost_FS1 Transport Protocol Control Protocol
(RTCP), flow-set 1.
Populated only if QoS is enabled.
Acme-Calling-RTCP- Total lost packets measured on RTP 102 integer Stop

Packets-Lost_FS2 packets in milliseconds, flow-set 2.
Acme-Calling-RTCP- Average jitter reported via RTCP 33 integer Stop

Avg-Jitter_FS1 measured in milliseconds, flow-set 1.
Acme-Calling-RTCP- Average jitter reported via RTCP 105 integer Stop

Avg-Jitter_FS2 measured in milliseconds, flow-set 2.
Acme-Calling-RTCP-Avg Average latency reported by comparing 34 integer Stop

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

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

MaxJitter_FS1 via RTCP measured in milliseconds, flow-
set 1.
Acme-Calling-RTCP- Maximum amount of jitter value reported 107 integer Stop

MaxJitter_FS2 via RTCP measured in milliseconds, flow-
set 3.

Attribute Attribute
Value Value Type
Acme-Calling-RTCP- Maximum latency value measured in 36 integer Stop

MaxLatency_FS1 milliseconds as observed through RTCP,
flow-set 1.
Acme-Calling-RTCP- Maximum latency value measured in 108 integer Stop

MaxLatency_FS2 milliseconds as observed through RTCP,
flow-set 2.
Acme-Calling- Bytes of RTP traffic for this call, flow-set 28 integer Stop
Octets_FS1 1.
Acme-Calling- Bytes of RTP traffic for this call, flow-set 102 integer Stop
Octets_FS2 2.
Acme-Calling- RTP packets for this call, flow-set 1. 29 integer Stop

Packets_FS1
Acme-Calling- RTP packets for this call, flow-set 2. 103 integer Stop
Packets_FS2
Acme-Calling-RTP- Total lost packets measured on RTP 37 integer Stop

Acme-Calling-RTP- Total lost packets measured on RTP 109 integer Stop

Acme-Calling-RTP-Avg- Total jitter measured on RTP packets in 38 integer Stop

Jitter_FS1 milliseconds, flow-set 1.
Acme-Calling-RTP-Avg- Total jitter measured on RTP packets in 110 integer Stop

Jitter_FS2 milliseconds, flow-set 2.
Acme-Calling-RTP- Maximum jitter measured on RTP 39 integer Stop

MaxJitter_FS1 packets in milliseconds, flow-set 1.
Acme-Calling-RTP-Avg- Maximum jitter measured on RTP 111 integer Stop

MaxJitter_FS2 packets in milliseconds, flow-set 2.

Attribute Attribute
Value Value Type
Acme-Called- Bytes of RTP traffic for the ingress side of 44 integer Stop
Octets_FS1 the call, flow-set 1.
Acme-Called- Bytes of RTP traffic for the ingress side of 124 integer Stop
Octets_FS2 the call, flow-set 2.
Acme-Called- RTP packets for the ingress side of the 45 integer Stop
Packets_FS1 call, flow-set 1.
Acme-Called- RTP packets for the ingress side of the 125 integer Stop
Packets_FS2 call, flow-set 2.
Acme-Called-RTCP- Total lost packets measured on RTCP 46 integer Stop

Packets-Lost_FS1 packets in milliseconds for the ingress
side of the call, flow-set 1.
Acme-Called-RTCP- Total lost packets measured on RTCP 126 integer Stop

Acme-Called-RTCP-Avg- Average jitter reported via RTCP 47 integer Stop

Jitter_FS1 measured in milliseconds for the ingress
Acme-Called-RTCP-Avg- Average jitter reported via RTCP 127 integer Stop

Jitter_FS2 measured in milliseconds for the ingress
Acme-Called-Avg- Average latency reported via RTCP 48 integer Stop

Latency_FS1 measured in milliseconds for the ingress
Acme-Called-Avg- Average latency reported via RTCP 128 integer Stop

Latency_FS2 measured in milliseconds for the ingress
Acme-Called-RTCP- Maximum amount of jitter reported via 49 integer Stop

MaxJitter_FS1 RTCP measured in milliseconds for the
ingress side of the call, flow-set 1.

Attribute Attribute
Value Value Type
Acme-Called-RTCP- Maximum amount of jitter reported via 129 integer Stop

MaxJitter_FS2 RTCP measured in milliseconds for the
Acme-Called-RTCP- Maximum amount of latency reported via 50 integer Stop

MaxLatency_FS1 RTCP measured in milliseconds for the
Acme-Called-RTCP- Maximum amount of latency reported via 130 integer Stop

MaxLatency_FS2 RTCP measured in milliseconds for the
Acme-Called-RTP- Total lost packets measured on RTP 51 integer Stop

Acme-Called-RTP- Total lost packets measured on RTP 131 integer Stop

Acme-Called-RTP-Avg- Average jitter reported via RTP measured 52 integer Stop

Jitter_FS1 in milliseconds for the ingress side of the
realm, flow-set 1.
Acme-Called-RTP-Avg- Average jitter reported via RTP measured 132 integer Stop
Jitter_FS2 in milliseconds for the ingress side of the
realm, flow-set 2.
Acme-Called-RTP- Maximum amount of jitter reported via 53 integer Stop

MaxJitter_FS1 RTP measured in milliseconds for the
ingress side of the call, flow-set1.
Acme-Called-RTP- Maximum amount of jitter reported via 133 integer Stop

MaxJitter_FS2 RTP measured in milliseconds for the
Acme Packet VSA The table below defines the possible values for several Acme Packet VSAs.
Values

Acme Packet VSA

Attribute Value Possible Values
Name
Acme-PostDial- 58 Unit value in milliseconds

Delay
Acme-Session- 60 0=unknown
Disposition 1=call_attempt
2=ringing
3=answered
Acme-Disconnet- 61 0=UNKNOWN_DISCONNECT_INITIATOR
Initiator 1=CALLING_PARTY_DISCONNECT
2=CALLED_PARTY_DISCONNECT
3=INTERNAL_DISCONNECT
Acme-Disconnect- 62 34=No circuit/channel available

Cause 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

Acme Packet VSA

Attribute Value Possible Values
Name
Acme-SIP- 70 SIP Diversion header based on this RFC draft: draft-

Diversion levy-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:
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
Cisco Systems The following table is a dictionary of the Cisco Systems (vendor identification
RADIUS Decodes 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
Attribute
Value
Type
Setup Time Time that a SIP INVITE or H.323 SETUP 25 string Start
message was received. The SETUP Stop
message is used to request a connection
(and therefore corresponds with the SIP
INVITE).
Connect Time Time that a SIP or H.323 session was 28 string Start
accepted. This is the time a 200 OK SIP Interim-
response to the SIP INVITE message was Update
received or the time that a call Stop
ANSWERED/CONNECTED response to the
H.323 SETUP message was received.
Disconnect Time that a SIP BYE or H.323 Release 29 string Stop

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

Cause 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.).
For more information, refer to this guides

Mappings and Disconnect Cause Values (29)
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 This section provides tables that show the mappings between SIP Status and: H.323
Q.850 Mappings 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

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
480 Temporarily Unavailable 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 to H.323

RAS Error Mapping
SIP Status H.323 RAS Error
404 Not Found Gatekeeper Resource
401 Unauthorized Invalid Permission
503 Service Unavailable Request Denied
500 Internal Server Error Undefined
401 Unauthorized Caller Not Registered
305 User Proxy Route Call to Gatekeeper
500 Internal Server Error Invalid Endpoint ID
503 Service Unavailable 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

Release Complete
Reason Error 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 Unreachable Destination
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 Unreachable Destination
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
480 Temporarily Unavailable Adaptive Busy
481 Call/Transaction Does Not Exist Undefined Reason
482 Loop Detected Undefined Reason
483 Too Many Hops Undefined Reason
484 Address Incomplete Bad Format Address
Q.850 Cause to H.323 The table below describes how the Q.850 Causes and the H.323 release complete
Release Complete reasons are mapped internally on the Net-Net SBC.
Reason Mapping
Q.850 Cause Numeric Code H.323 Release Complete Reason
Not Route To Destination 3 Unreachable 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 Unreachable Gatekeeper

Q.850 Cause Numeric Code H.323 Release Complete Reason
Temporary Failure 41 Adaptive Busy
Switching Equipment Congestion 42 Gateway Resource
Resource Unavailable 47 Gatekeeper Resource
Incompatible Destination 88 Invalid Revision
Interworking Unspecified 111 No Permission
SIP-SIP Calls 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 0 Undetermined reason
BYE 1 Normal clearing
3xx: Redirection 2 Redirection
4xx: Client Error 3 Client error
5xx: Server Error 4 Server error
6xx: Global Failure 5 Global error
SIP-H.323 Calls For calls that require SIP-H.323 interworking, the Net-Net SBC generates two sets
with Interworking 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 (31).
SIP CDR Disconnect

SIP Status Category/Event H.323 Disconnect Cause Value (Q.850)
Cause
BYE 16Normal call clearing 16Normal call clearing
3xx 23Redirection to new 16Normal call clearing

destination
404 Not Found 21Call rejected 3No route to destination
410 Gone 21Call rejected 3No route to destination

SIP CDR Disconnect

SIP Status Category/Event H.323 Disconnect Cause Value (Q.850)
Cause
403 Forbidden 21Call rejected 111Interworking unspecified
413 Request Entity Too Big 21Call rejected 28Invalid number format
414 Request URI Too Large 21Call rejected 28Invalid number format
420 Bad Extension 21Call rejected 28Invalid number format
484 Address Incomplete 21Call rejected 28Invalid number format
408 Request Timeout 21Call rejected 41Temporary failure
480 Temporarily 21Call rejected 41Temporary failure

unavailable
486 Busy Here 21Call rejected 17User Busy
401 Unauthorized 21Call rejected 32Normal unspecified
407 Proxy Authentication 21Call rejected 32Normal unspecified

Required
All other 4xx 21Call rejected 16Normal unspecified
502 Bad Gateway 38Network out of 28Invalid number format

order
505 Bad Version 38Network out of 88Incompatible destination

order
All other 5xx 38Network out of 16Normal unspecified

order
600 Busy Everywhere 31Normal unspecified 41Temporary failure
603 Decline 31Normal unspecified 31Normal unspecified
604 Does Not Exist 31Normal unspecified 3No route to destination

Anywhere
All other 6xx 31Normal unspecified 31Normal unspecified
H.323 Events and The Q.850 cause code value is recorded for the disconnect cause in the CDR for the
Errors 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.

The entries in this table are determined by the SIP Status to H.323 Disconnect
Reason Mapping (29).
H.323 H.323 CDR SIP CDR Disconnect

SIP Status
ReleaseCompleteReason Disconnect Cause Cause
No Bandwidth 34No 480 Temporarily 21Call rejected

channel/circuit Unavailable
available
Gatekeeper Resource 47Resource 404 Not Found 21Call rejected

unavailable
Unreachable Destination 3No route to 404 Not Found 21Call rejected

destination
Destination Rejected 31Normal 603 Decline 31Normal

unspecified unspecified
Invalid Revision 88Incompatible 505 Version Not 38Network out of

destination Supported order
No Permission 111Interworking 401 Unauthorized 21Call rejected

unspecified
Unreachable Gatekeeper 38Network out of 503 Service 38Network out of

order Unavailable order
Gateway Resource 42Switching 480 Temporarily 21Call rejected

equipment unavailable
congestion
Bad Format Request 28Invalid number 400 Bad request 21Call rejected
format
Adaptive Busy 41Temporary failure 486 Busy Here 21Call rejected
In Conference 17User busy 486 Busy Here 21Call rejected
Undefined Reason 16Normal 500 Internal Server 38Network out of

unspecified Error order
Called Party Not 20Subscriber 404 Not Found 21Call rejected

Registered absent
Caller Not Registered 31Normal call

clearing
New Connection Needed 47Resource 401 Unauthorized 21Call rejected

Unavailable
H.225 RAS Errors 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 (30).
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 503 Service Unavailable 38Network out of order
Undefined 500 Internal Server Error 38Network out of order
Caller Not Registered 401 Unauthorized 21Call Rejected
Route Call to Gatekeeper 305 Use Proxy 23Redirection to new destination
Invalid Endpoint ID 500 Internal Server Error 38Network out of order
Resource Unavailable 503 Service Unavailable 38Network out of order
Security Denial 401 Unauthorized 21Call Rejected
QoS Control Not Supported 501 Not Implemented 38Network out of order
Incomplete Address 484 Address Incomplete 21Call Rejected
Route Call to SCN 302 Moved Temporarily 2Redirection
Aliases Inconsistent 485 Ambiguous 21Call Rejected
Not Currently Registered 401 Unauthorized 21Call Rejected


2 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,

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 The RADIUS accounting client process has a local socket at which it accepts RADIUS
Client 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

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 The RAS client can record SIP, H.323, and IWF session activity based on
Accounting 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.

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 Start, Interim-
stacks call signal address. Update, Stop, On,
Off
NAS Port SIP proxy port or the H.323 stacks call Start, Interim-
signaling RAS port. Update, Stop, On,
Off
NAS Identifier Value, if any, set in the optional NAS-ID field Start, Interim-
for the accounting server that you configure as Update, Stop, On,
part of the accounting configuration. This Off
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.
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 Start, Interim-
message, the callIdentifier of the Update, Stop, On,
H.323 message, or RADIUS client information. Off
Called Station ID To field value of the SIP INVITE message (a Start, Interim-
type of message used to initiate a session) or Update, Stop
the calledPartyNumber of the H.323
message.
Calling Station ID From field value of the SIP INVITE message Start, Interim-
or the callingPartyNumber of the H.323 Update, Stop
message.
Acct-Terminate-Cause Reason for session ending (refer to Session Stop, Off

Termination session).
Acct-Session-Time Length of session (time in seconds). Interim-Update,

Stop, Off

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
Event Message
Cause
User request SIP BYE message or H.323 Stop
User error SIP signaling failed to establish session Stop

(accompanied by disconnect cause)
NAS request RADIUS server disabled Off
ACLI Instructions This section tells you how to access and set parameters for RADIUS accounting
and Examples 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 To configure the account configuration and account servers:

Accounting and
Accounting Servers 1. In Superuser mode, type configure terminal and press <Enter>.
Configuration
ACMEPACKET# configure terminal
2. Type session-router and press <Enter> to access the system-level configuration
elements.
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 You set the account configuration parameters to indicate where you want accounting
Account Configuration messages sent, when accounting messages you want them sent, and the strategy you
want used to select account servers.
To configure the account configuration:
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.
Minimum: zero (0)
Maximum: 232-1
6. 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.
Minimum: one (1) message
Maximum: 4096 messages
7. 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

(Stop). The transmitted accounting information for a single session might

span a period of hours and be spread out among different storage files.
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.
8. 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:
StartRADIUS Start message should not be generated.
InviteRADIUS Start message should be generated once the Net-Net SBC
receives a SIP session INVITE.
9. 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) RADIUS Interim message is generated when the Net-Net
SBC receives a SIP session reINVITE and responds to it
(for example, session connection or failure).
reinvite cancel RADIUS Interim message is generated when the Net-Net

SBC receives a SIP session reINVITE, and the Reinvite is
cancelled before the Net-Net SBC responds to it.
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 You must establish the list of servers to which the Net-Net SBC can send accounting
Servers 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. 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
7. 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.
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.
Local CDR Storage and FTP Push
The local CDR storage allows you to save RADIUS CDR data locally on the Net-Net
SBC. Storing these records locally gives you the option of either:
Sending them to an FTP server
Developing and implementing your own script for retrieving them as necessary
Previously, the Net-Net SBC sent CDRs to RADIUS servers for every call. The local
CDR storage and FTP push feature can either replace that functionality or be
configured in addition to it.
You configure the Net-Net SBC for:
The Net-Net SBC directory path where you want to save files
File size, number of files, and how often the Net-Net SBC should send files to
the FTP server
FTP server (IP address, port, user name and password, and the path on the FTP
server where you want the file transferred)
According to the settings you configure, the Net-Net SBC writes CDRs as comma-
delimited ASCII records and stores them locally. In addition, the Net-Net SBC will
attempt to send (push) any non-active CDR file to an FTP server you specify when
you enable FTP push.
About the Record The CDRs are written as comma-delimited ASCII records to files on the Net-Net
Format 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 and STOP records, which are defined in the tables below. Using
the accounting configuration, you can configure the Net-Net SBC to record STOP
records only.
The record types do not have consistent field positioning, so any server parsing them
would need to read the first field to determine the type and learn how to parse the
remaining fields.
CDR File Naming Filenames are derived from the date and time that the CDR file is opened for writing.
Convention 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 Storage The Net-Net SBC only allows local storage of ASCII CDRs to the /ramdrv and
Directories /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.
File Size and You can configure maximum file size, maximum number of files to store on the Net-
Rotation Net SBC, and the interval at which the files rotate.
The Net-Net SBC saves up to the file size limit and the number of files that you set.
When the Net-Net SBC has reached the maximum number of files it is configured
to store, it starts to rotate the files. This means that the oldest file will be overwritten
so that the newest one can be stored.
At the configured time interval, the Net-Net SBC sends out the files that are
complete; the file that is being written will not be sent.
If a file exceeds the configured maximum file size, the Net-Net SBC rotates that file,
but it does not initiate an FTP push. The file continues to rotate until it becomes the
oldest file and, as a result, is discarded.
More About File When you enable the Net-Net SBCs CDR storage and FTP push feature, the Net-
Rotation Time Net SBC saves CDRs to comma-delimited files which are then pushed to FTP servers
you designate. You can also use the CDR local storage feature on its own. The Net-
Net SBC uses a period of time that you set to periodically rotate the files, but in prior
releases this rotation is only used when the FTP push feature is enabled. However,
the behavior of the accounting configurations file-rotate-time parameter has
changed so that file rotation can be enabled regardless of whether you use the push
feature.
You can configure maximum file size, maximum number of files to store on the Net-
Net 4000, and the interval at which the files rotate. The Net-Net SBC saves up to the
file size limit and the number of files that you set. When the Net-Net SBC has
reached the maximum number of files it is configured to store, it starts to rotate the
files at the configured time interval. This means that the oldest file will be
overwritten so that the newest one can be stored.
CDR Local File Using the Net-Net SBCs local CDR storage feature, you can enable the Net-Net
Format SBC to write CDRs as comma-delimited ASCII records to files on the Net-Net SBC.
Enhancements 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. This feature is mainly used with the Net-Net SBCs
FTP push capability, so that the files stored locally are periodically sent to a an FTP
server you designate.

In prior releases, unpopulated or unused fields in the RADIUS CDR are omitted
from the locally-stored CSV file. This means that in prior releases, 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.
The enhancements to this feature offer you a way to guarantee the placement of
attributes in locally-stored CSV files. 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 C (83) of this document for details about where in locally-
generated CSV file VSAs appear for Start, Interim, and Stop records.
Requirements If you want to use this feature and 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 (which
replaces the max-vsa-id parameter for some Net-Net 4.1.1 images) 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.
Recommended Acme Packet recommends that you do not leave the vsa-id-range parameter
Configuration unconfigured, but set it to the attributes used in the Net-Net OS release loaded on
your system. As of this version of Release 4.1.4, your entry would look like the
following:
ACMEPACKET(account-config)# vsa-id-range 1-4,10-14,20-24,28,29,32-
71,74-136
This entry is the same one shown in the configuration sample below.
ACLI Instructions This section shows you how to configure Local CDR storage and FTP push on your
and Examples Net-Net SBC.
Accessing the To configure parameter for these features, you must access the accounting
Accounting configuration.
Configuration
To access the accounting configuration:
1. In Superuser mode, type configure terminal and press <Enter>.


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

3. Type account-config and press <Enter>.
From here, you can enable local CDR storage and FTP push.
Enabling Local CDR To enable local CDR storage:

Storage
4. file-outputEnable the output of comma-delimited CDRs (generated from
RADIUS records) for this Net-Net SBC. By default, this parameter is disabled.
To use FTP push, this parameter must be enabled.
5. 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.
6. 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.
7. 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.
8. 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
/ramdrv/logs
To use FTP push, you must configure a usable path.
Setting the CSV File This section shows you how to configure the CDR file enhancement to use fixed
Format value placement in locally-stored CSV files.
To enable fixed value placement in CSV files for RADIUS CDRs:

ACMEPACKET(configure)#
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 Net-
Net 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,32-

71,74-136
5. cdr-output-inclusiveIf you want to enable the CDR file format feature,
change this parameter from disabled (default) to enabled.
Enabling FTP Push To enable FTP push:
1. ftp-pushSet the state of FTP push feature. It is disabled by default.

2. ftp-addressSet the IP address for the FTP server to which the Net-Net SBC
will send files. There is no default value.
3. ftp-portSet the TCP port on the FTP server to which the Net-Net SBC will
send files; the minimum is 1025 and the maximum is 65535. The default is 21.
4. ftp-userSet the username for the FTP server to which the Net-Net SBC will
send files. There is no default value.
5. ftp-passwordSet the password corresponding to the FTP username. There is
no default value.
6. ftp-remote-pathSet the file path on the FTP server to which the Net-Net will
send files. There is no default value.
7. Confirm that you have configure the file-output and file-path appropriately.
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 To configure per realm accounting:

and Examples
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:

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.
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 now 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.
Note that if you use a Net-Net OS release with the max-vsa-id parameter, the vsa-
id-range parameter supercedes it. On upgrade, the change will automatically be
made from the configured max-vsa-id to the corresponding vsa-id-range.
ACLI Instructions This section shows you how to configure the two parameters used for CDR content
and Examples control.
Preventing Duplicate To enable duplicate RADIUS attribute prevention:

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

ACMEPACKET(account-config)# prevent-duplicate-attrs enabled

RADIUS Attribute You enter the list of VSAs that you want included as a comma-delimited list. There
Selection are special entry types you can use in the comma-delimited list to set ranges and
make entries easier:
X- Where X is a VSA identifier, the Net-Net SBC will include all attributes
with an identifier equal to or greater than 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.
RADIUS CDR Redundancy
When you are using the RADIUS CDR storage and FTP push feature, the Net-Net
SBC provides redundancy support for the comma-delimited CDRs that it stores. The
records stored on the active Net-Net SBC are duplicated to 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.
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.
Upgrading If you are upgrading to a version of the Net-Net OS that contains this feature, you
must pay attention to the status of the cdr-output-redundancy parameter. Note
the following scenarios:
Upgrade with pre-existing accounting configurationWhen you upgrade to a
release that contains this feature and you have a pre-existing accounting
configuration, the cdr-output-redundancy parameter defaults to disabled.
This is the Net-Net SBCs pre-existing default behavior.
Upgrade with no pre-existing accounting configurationWhen you are
upgrading to a release that contains this feature and there is no pre-existing

accounting configuration, the cdr-output-redundancy parameter defaults to

enabled.
Potential OOS Because it is possible to create a situation in which this parameter is saved to a
Scenario configuration as enabled on a system running an older version of software, you can
send a standby out of service when you try to upgrade it. You can check the status of
the parameter for running the ACLI show running-config account-config
command and confirming the value for cdr-output-redundancy:
ACMEPACKET# show running-config account-config
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 5
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 0
prevent-duplicate-attrs disabled
vsa-id-range
account-server
hostname 192.168.200.70
port 5050
state enabled
min-round-trip 250
max-inactivity 60
restart-delay 30
bundle-vsa enabled
secret
NAS-ID
If you check the configuration and find that the parameter is enabled for the active
peer in the HA node, perform the workaround procedure in this section to put the
standby system back in service.
To summarize, the standby peer can go OOS in the course of the following sequence
of events:

1. Two Net-Net SBCs are set up as an HA node, both running an older version
of software (released prior to the introduction of this feature). Both systems
share the same configuration, which does not have an accounting
configuration set up.
2. The standby system is upgraded to a version of the software that supports

CDR redundancy (and contains the cdr-output-redundancy parameter).
3. The HA node is then downgraded to the previous, older version that was
used. No changes were made to the configuration.
4. The standby is upgraded to a new version (containing the CDR redundancy

feature), and the accounting configuration shows that the cdr-output-
redundancy parameter is enabled. The standby will go OOS.
To put the standby peer in an HA node back in service after upgrade:

2. Type session-router and press <Enter> to access the signaling-related
configurations.
4. Use the ACLI select command to edit the accounting configuration.
ACMEPACKET(account-config)# select
5. Use the ACLI done command to save the accounting configuration.
ACMEPACKET(account-config)# done
6. Exit out to the main Superuser section of the ACLI.
ACMEPACKET(account-config)# exit
ACMEPACKET(session-router)# exit
ACMEPACKET(configure)# exit
ACLI Instructions To enable CDR redundancy:

and Examples
2. Type session-router and press <Enter> to access the signaling-related
configurations.
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. cdr-output-redundancyChange this parameter to enabled or disabled as
your configuration or upgrade needs require.

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 You enable these enhancements using two parameters in the accounting
and Examples configuration.
Accessing the To access the accounting configuration:

Accounting
Configuration 1. In Superuser mode, type configure terminal and press <Enter>.
From this point, you can reach the individual parameters for duplicate RADIUS
attribute prevention and for RADIUS attribute selection.
Preventing Duplicate To enable duplicate RADIUS attribute prevention:

RADIUS Attributes
1. prevent-duplicate-attrsChange this parameter from disabled (default) to
enabled.
ACMEPACKET(account-config)# prevent-duplicate-attrs enabled

RADIUS Attribute You enter the list of VSAs that you want included as a comma-delimited list. There
Selection are special entry types you can use in the comma-delimited list to set ranges and
make entries easier:
X- Where X is a VSA identifier, the Net-Net SBC will include all attributes
with an identifier equal to or greater than 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.
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 5
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 0
prevent-duplicate-attrs disabled
vsa-id-range
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
account-server
hostname 192.168.200.70
port 5050
state enabled
min-round-trip 250
max-inactivity 60
restart-delay 30
bundle-vsa enabled
secret packet
NAS-ID

3 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) (ap-
syslog.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 The table below describes the Net-Net SBCs alarms for RADIUS.
Alarm
Alarm Alarm Severity Cause Log Message Actions
ID
RADIUS 327681 CRITICAL if all enabled The enabled CRITICAL: All apSyslogMess
ACCOUNTING and configured RADIUS connections to enabled ageGenerate
CONNECTION accounting server RADIUS accounting d trap
DOWN connections have servers have connections have generated
timed-out without a timed-out been lost. Check critical, major
response from the without a accounting status dry contact
RADIUS server. response from for more details. syslog
the RADIUS
MAJOR if some, but not server. MAJOR: One or
all configured RADIUS more enabled
accounting server accounting
connections have connections have
timed-out without a been lost. Check
response from the accounting status
RADIUS server. 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 The show radius command can take one of the three available arguments:
RADIUS Display 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"

RoundTripTime :0
MalformedAccessResponse:0
AccessRequests :2
BadAuthenticators :0
AccessRetransmissions :5
AccessAccepts :0
Timeouts :6
AccessRejects :0
UnknownPDUTypes :0
AccessChallenges :0
Server:"172.30.0.8:1812"
RoundTripTime :0
AccessRequests :2
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
----------------- 192.168.200.70:5050 ------------------
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
================================================

----------------- 10.0.0.189:1813 ------------------

conn state=READY, RTT=250 ms
Restart delay=30 s
----------------- 192.168.200.70:5050 ------------------
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
AccessAccepts :0
Timeouts :6
AccessRejects :0
UnknownPDUTypes :0
AccessChallenges :0
Server:"172.30.0.8:1812"
RoundTripTime :0
AccessRequests :2
AccessAccepts :0
Timeouts :10
AccessRejects :0
UnknownPDUTypes :0
AccessChallenges :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 The following sample CDRs are for a successful SIP call.
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"

APPENDIX A
Acme-FlowID_FS1_F = "localhost:65594"
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 = ""

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"

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

APPENDIX A
Acme-Session-Disposition = 3
Acme-Disconnect-Initiator = 1
Acme-Disconnect-Cause = 0

APPENDIX A
Acme-SIP-Status = 0
Acct-Unique-Session-Id = "5af95b6a3259b428"
Unsuccessful SIP The following sample CDRs are for an unsuccessful SIP call.
Call Acct-Status-Type = Stop
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"

APPENDIX A
Acme-Flow-Out-Realm_FS1_R = "Core"

APPENDIX A
Acme-SIP-Status = 487
Acct-Unique-Session-Id = "f1c5761c4d973242"

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"

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

APPENDIX A


APPENDIX A

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

APPENDIX A

APPENDIX A
Acme-Intermediate_Time = "16:47:47.186 EST JUL 02 2008"

APPENDIX A
Wed Jul 2 17:25:09 2008

Acct-Status-Type = Stop
NAS-IP-Address = 192.168.12.100
NAS-Port = 5060
Acct-Terminate-Cause = User-Request

APPENDIX A

APPENDIX A
Acme-SIP-Status = 0

Appendix B
Net-Net 4000 C6.0.0 RADIUS Dictionary
#
# dictionary.acme
#
#
#
VENDOR Acme 9148
#
# Voice over IP attributes.
#
ATTRIBUTE Acme-FlowID_FS1_F 1 string Acme
ATTRIBUTE Acme-FlowType_FS1_F 2 string Acme
ATTRIBUTE Acme-Session-Ingress-CallId 3 string Acme
ATTRIBUTE Acme-Session-Egress-CallId 4 string Acme
ATTRIBUTE Acme-Flow-In-Realm_FS1_F 10 string Acme

ATTRIBUTE Acme-Flow-In-Src-Addr_FS1_F 11 ipaddr Acme
ATTRIBUTE Acme-Flow-In-Src-Port_FS1_F 12 integer Acme
ATTRIBUTE Acme-Flow-In-Dst-Addr_FS1_F 13 ipaddr Acme
ATTRIBUTE Acme-Flow-In-Dst-Port_FS1_F 14 integer Acme
ATTRIBUTE Acme-Flow-Out-Realm_FS1_F 20 string Acme

ATTRIBUTE Acme-Flow-Out-Src-Addr_FS1_F 21 ipaddr Acme
ATTRIBUTE Acme-Flow-Out-Src-Port_FS1_F 22 integer Acme
ATTRIBUTE Acme-Flow-Out-Dst-Addr_FS1_F 23 ipaddr Acme
ATTRIBUTE Acme-Flow-Out-Dst-Port_FS1_F 24 integer Acme
ATTRIBUTE Acme-Calling-Octets_FS1 28 integer Acme
ATTRIBUTE Acme-Calling-Packets_FS1 29 integer Acme
ATTRIBUTE Acme-Calling-RTCP-Packets-Lost_FS1 32 integer Acme
ATTRIBUTE Acme-Calling-RTCP-Avg-Jitter_FS1 33 integer Acme
ATTRIBUTE Acme-Calling-RTCP-Avg-Latency_FS1 34 integer Acme
ATTRIBUTE Acme-Calling-RTCP-MaxJitter_FS1 35 integer Acme
ATTRIBUTE Acme-Calling-RTCP-MaxLatency_FS1 36 integer Acme
ATTRIBUTE Acme-Calling-RTP-Packets-Lost_FS1 37 integer Acme
ATTRIBUTE Acme-Calling-RTP-Avg-Jitter_FS1 38 integer Acme
ATTRIBUTE Acme-Calling-RTP-MaxJitter_FS1 39 integer Acme
ATTRIBUTE Acme-Session-Generic-Id 40 string Acme

ATTRIBUTE Acme-Session-Ingress-Realm 41 string Acme
ATTRIBUTE Acme-Session-Egress-Realm 42 string Acme
ATTRIBUTE Acme-Session-Protocol-Type 43 string Acme
ATTRIBUTE Acme-Called-Octets_FS1 44 integer Acme

ATTRIBUTE Acme-Called-Packets_FS1 45 integer Acme
ATTRIBUTE Acme-Called-RTCP-Packets-Lost_FS1 46 integer Acme
ATTRIBUTE Acme-Called-RTCP-Avg-Jitter_FS1 47 integer Acme
ATTRIBUTE Acme-Called-RTCP-Avg-Latency_FS1 48 integer Acme
ATTRIBUTE Acme-Called-RTCP-MaxJitter_FS1 49 integer Acme
ATTRIBUTE Acme-Called-RTCP-MaxLatency_FS1 50 integer Acme
ATTRIBUTE Acme-Called-RTP-Packets-Lost_FS1 51 integer Acme
ATTRIBUTE Acme-Called-RTP-Avg-Jitter_FS1 52 integer Acme

APPENDIX B
ATTRIBUTE Acme-Called-RTP-MaxJitter_FS1 53 integer Acme
ATTRIBUTE Acme-Session-Charging-Vector 54 string Acme

ATTRIBUTE Acme-Session-Charging-Function_Address 55 string Acme
ATTRIBUTE Acme-Firmware-Version 56 string Acme
ATTRIBUTE Acme-Local-Time-Zone 57 string Acme
ATTRIBUTE Acme-Post-Dial-Delay 58 integer Acme
ATTRIBUTE Acme-CDR-Sequence-Number 59 integer Acme
ATTRIBUTE Acme-Session-Disposition 60 integer Acme
ATTRIBUTE Acme-Disconnect-Initiator 61 integer Acme
ATTRIBUTE Acme-Disconnect-Cause 62 integer Acme
ATTRIBUTE Acme-Intermediate_Time 63 string Acme
ATTRIBUTE Acme-Primary-Routing-Number 64 string Acme
ATTRIBUTE Acme-Originating-Trunk-Group 65 string Acme
ATTRIBUTE Acme-Terminating-Trunk-Group 66 string Acme
ATTRIBUTE Acme-Originating-Trunk-Context 67 string Acme
ATTRIBUTE Acme-Terminating-Trunk-Context 68 string Acme
ATTRIBUTE Acme-P-Asserted-ID 69 string Acme
ATTRIBUTE Acme-SIP-Diversion 70 string Acme
ATTRIBUTE Acme-SIP-Status 71 integer Acme
# 72 unused
# 73 unused
ATTRIBUTE Acme-Ingress-Local-Addr 74 string Acme
ATTRIBUTE Acme-Ingress-Remote-Addr 75 string Acme
ATTRIBUTE Acme-Egress-Local-Addr 76 string Acme
ATTRIBUTE Acme-Egress-Remote-Addr 77 string Acme
ATTRIBUTE Acme-FlowID_FS1_R 78 string Acme
ATTRIBUTE Acme-FlowType_FS1_R 79 string Acme
ATTRIBUTE Acme-Flow-In-Realm_FS1_R 80 string Acme
ATTRIBUTE Acme-Flow-In-Src-Addr_FS1_R 81 ipaddr Acme
ATTRIBUTE Acme-Flow-In-Src-Port_FS1_R 82 integer Acme
ATTRIBUTE Acme-Flow-In-Dst-Addr_FS1_R 83 ipaddr Acme
ATTRIBUTE Acme-Flow-In-Dst-Port_FS1_R 84 integer Acme
ATTRIBUTE Acme-Flow-Out-Realm_FS1_R 85 string Acme
ATTRIBUTE Acme-Flow-Out-Src-Addr_FS1_R 86 ipaddr Acme
ATTRIBUTE Acme-Flow-Out-Src-Port_FS1_R 87 integer Acme
ATTRIBUTE Acme-Flow-Out-Dst-Addr_FS1_R 88 ipaddr Acme
ATTRIBUTE Acme-Flow-Out-Dst-Port_FS1_R 89 integer Acme
ATTRIBUTE Acme-FlowID_FS2_F 90 string Acme
ATTRIBUTE Acme-FlowType_FS2_F 91 string Acme
ATTRIBUTE Acme-Flow-In-Realm_FS2_F 92 string Acme
ATTRIBUTE Acme-Flow-In-Src-Addr_FS2_F 93 ipaddr Acme
ATTRIBUTE Acme-Flow-In-Src-Port_FS2_F 94 integer Acme
ATTRIBUTE Acme-Flow-In-Dst-Addr_FS2_F 95 ipaddr Acme
ATTRIBUTE Acme-Flow-In-Dst-Port_FS2_F 96 integer Acme
ATTRIBUTE Acme-Flow-Out-Realm_FS2_F 97 string Acme
ATTRIBUTE Acme-Flow-Out-Src-Addr_FS2_F 98 ipaddr Acme
ATTRIBUTE Acme-Flow-Out-Src-Port_FS2_F 99 integer Acme
ATTRIBUTE Acme-Flow-Out-Dst-Addr_FS2_F 100 ipaddr Acme
ATTRIBUTE Acme-Flow-Out-Dst-Port_FS2_F 101 integer Acme
ATTRIBUTE Acme-Calling-Octets_FS2 102 integer Acme
ATTRIBUTE Acme-Calling-Packets_FS2 103 integer Acme
ATTRIBUTE Acme-Calling-RTCP-Packets-Lost_FS2 104 integer Acme
ATTRIBUTE Acme-Calling-RTCP-Avg-Jitter_FS2 105 integer Acme
ATTRIBUTE Acme-Calling-RTCP-Avg-Latency_FS2 106 integer Acme
ATTRIBUTE Acme-Calling-RTCP-MaxJitter_FS2 107 integer Acme
ATTRIBUTE Acme-Calling-RTCP-MaxLatency_FS2 108 integer Acme
ATTRIBUTE Acme-Calling-RTP-Packets-Lost_FS2 109 integer Acme
ATTRIBUTE Acme-Calling-RTP-Avg-Jitter_FS2 110 integer Acme
ATTRIBUTE Acme-Calling-RTP-MaxJitter_FS2 111 integer Acme
ATTRIBUTE Acme-FlowID_FS2_R 112 string Acme

ATTRIBUTE Acme-FlowType_FS2_R 113 string Acme
ATTRIBUTE Acme-Flow-In-Realm_FS2_R 114 string Acme

APPENDIX B
ATTRIBUTE Acme-Flow-In-Src-Addr_FS2_R 115 ipaddr Acme

ATTRIBUTE Acme-Flow-In-Src-Port_FS2_R 116 integer Acme
ATTRIBUTE Acme-Flow-In-Dst-Addr_FS2_R 117 ipaddr Acme
ATTRIBUTE Acme-Flow-In-Dst-Port_FS2_R 118 integer Acme
ATTRIBUTE Acme-Flow-Out-Realm_FS2_R 119 string Acme
ATTRIBUTE Acme-Flow-Out-Src-Addr_FS2_R 120 ipaddr Acme
ATTRIBUTE Acme-Flow-Out-Src-Port_FS2_R 121 integer Acme
ATTRIBUTE Acme-Flow-Out-Dst-Addr_FS2_R 122 ipaddr Acme
ATTRIBUTE Acme-Flow-Out-Dst-Port_FS2_R 123 integer Acme
ATTRIBUTE Acme-Called-Octets_FS2 124 integer Acme
ATTRIBUTE Acme-Called-Packets_FS2 125 integer Acme
ATTRIBUTE Acme-Called-RTCP-Packets-Lost_FS2 126 integer Acme
ATTRIBUTE Acme-Called-RTCP-Avg-Jitter_FS2 127 integer Acme
ATTRIBUTE Acme-Called-RTCP-Avg-Latency_FS2 128 integer Acme
ATTRIBUTE Acme-Called-RTCP-MaxJitter_FS2 129 integer Acme
ATTRIBUTE Acme-Called-RTCP-MaxLatency_FS2 130 integer Acme
ATTRIBUTE Acme-Called-RTP-Packets-Lost_FS2 131 integer Acme
ATTRIBUTE Acme-Called-RTP-Avg-Jitter_FS2 132 integer Acme
ATTRIBUTE Acme-Called-RTP-MaxJitter_FS2 133 integer Acme
ATTRIBUTE Acme-Egress-Final-Routing-Number 134 string Acme
ATTRIBUTE Acme-Session-Ingress-RPH 135 string Acme
ATTRIBUTE Acme-Session-Egress-RPH 136 string Acme
ATTRIBUTE Acme-Ingress-Network-Interface-Id 137 string Acme
ATTRIBUTE Acme-Ingress-Vlan-Tag-Value 138 integer Acme
ATTRIBUTE Acme-Egress-Network-Interface-Id 139 string Acme
ATTRIBUTE Acme-Egress-Vlan-Tag-Value 140 integer Acme
ATTRIBUTE Acme-Refer-Call-Transfer-Id 141 string Acme
ATTRIBUTE Acme-User-Class 254 string Acme

APPENDIX B

Appendix C
Comma-Delimited Entries for Local Files
Local File Format

Appendix C contains three tables that show where, in locally-generated CVV 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 (45) section in this guides Configuring Accounting (37)
chapter.
Start Record CSV

Placement
CSV Placement Attribute Name VSA ID Number
1 Acct-Status-Type
2 NAS-IP-Address
3 NAS-Port
4 Acct-Session-Id
5 Acme-Session-Ingress-CallId 3
6 Acme-Session--Egress-CallId 4
7 Acme-Session-Protocol-Type 43
8 Acme-Session--Generic-Id 40
9 Calling-Station-Id 31
10 Called-Station-Id 30
11 h323-setup-time
12 h323-connect-time
13 Acme-Ingress-Network-Interface-Id 137
14 Acme-Ingress-Vlan-Tag-Value 138
15 Acme-Egress-Network-Interface-Id 139
16 Acme-Egress-Vlan-Tag-Value 140
17 Acme-Session-Egress-Realm 42
18 Acme-Session-Ingress-Realm 41
19 Acme-FlowId_FS1_F 1
20 Acme-FlowType_FS1_F 2
21 Acme-Flow-In-Realm_FS1_F 10
22 Acme-Flow-In-Src-Addr_FS1_F 11
23 Acme-Flow-In-Src-Port_FS1_F 12

APPENDIX C
24 Acme-Flow-In-Dst-Addr_FS1_F 13
25 Acme-Flow-In-Dst-Port_FS1_F 14
26 Acme-Flow-Out-Realm_FS1_F 20
27 Acme-Flow-Out-Src-Addr_FS1_F 21
28 Acme-Flow-Out-Src-Port_FS1_F 22
29 Acme-Flow-Out-Dst-Addr_FS1_F 23
30 Acme-Flow-Out-Dst-Port_FS1_F 24
31 Acme-FlowID_FS1_R 78
32 Acme-FlowType_FS1_R 79
33 Acme-Flow-In-Realm_FS1_R 80
34 Acme-Flow-In-Src-Addr_FS1_R 81
35 Acme-Flow-In-Src-Port_FS1_R 82
36 Acme-Flow-In-Dst-Addr_FS1_R 83
37 Acme-Flow-In-Dst-Port_FS1_R 84
38 Acme-Flow-Out-Realm_FS1_R 85
39 Acme-Flow-Out-Src-Addr_FS1_R 86
40 Acme-Flow-Out-Src-Port_FS1_R 87
41 Acme-Flow-Out-Dst-Addr_FS1_R 88
42 Acme-Flow-Out-Dst-Port_FS1_R 89
43 Acme-FlowID_FS2_F 90

APPENDIX C
67 Acme-Session-Charging-Vector 54
68 Acme-Session-Charging-Function_Address 55
69 Acme-Firmware-Version 56
70 Acme-Local-Time-Zone 57
71 Acme-Post-Dial-Delay 58
72 Acme-Primary-Routing-Number 64
73 Acme-Originating-Trunk-Group 65
74 Acme-Terminating-Trunk-Group 66
75 Acme-Originating-Trunk-Context 67
76 Acme-Terminating-Trunk-Context 68
77 Acme-P-Asserted-ID 69
78 Acme-Ingress-Local-Addr 74
79 Acme-Ingress-Remote-Addr 75
80 Acme-Egress-Local-Addr 76
81 Acme-Egress-Remote-Addr 77
82 Acme-SIP-Diversion 70
83 Acme-Egress-Final-Routing-Number 134
84 Acme-Session-Ingress-RPH 135
85 Acme-Session-Egress-RPH 136

APPENDIX C
Interim Record CSV

Placement
1 Acct-Status-Type
2 NAS-IP-Address
3 NAS-Port
4 Acct-Session-Id
11 h323-setup-time
31 Acme-Calling-RTCP-Packets-Lost_FS1 32
32 Acme-Calling-RTCP-Avg-Jitter_FS1 33
33 Acme-Calling-RTCP-Avg-Latency_FS1 34

APPENDIX C
34 Acme-Calling-RTCP-MaxJitter_FS1 35
35 Acme-Calling-RTCP-MaxLatency_FS1 36
36 Acme-Calling-RTP-Packets-Lost_FS1 37
37 Acme-Calling-RTP-Avg-Jitter_FS1 38
38 Acme-Calling-RTP-MaxJitter_FS1 39
39 Acme-Calling-Octets_FS1 28
40 Acme-Calling-Packets_FS1 29
53 Acme-Called-RTCP-Packets-Lost_FS1 46
54 Acme-Called-RTCP-Avg-Jitter_FS1 47
55 Acme-Called-RTCP-Avg-Latency_FS1 48
56 Acme-Called-RTCP-MaxJitter_FS1 49
57 Acme-Called-RTCP-MaxLatency_FS1 50
58 Acme-Called-RTP-Packets-Lost_FS1 51
59 Acme-Called-RTP-Avg-Jitter_FS1 52
60 Acme-Called-RTP-MaxJitter_FS1 53
61 Acme-Called-Octets_FS1 44
62 Acme-Called-Packets_FS1 45

APPENDIX C
98 Acme-Called--RTCP-Avg-Jitter_FS2 127
99 Acme-Called--RTCP-Avg-Latency_FS2 128

APPENDIX C
100 Acme-Called--RTCP-MaxJitter_FS2 129
108 Acme-Session-Charging-Function_Address 55
123 Acme-Intermediate_Time 63

APPENDIX C
Stop Record CSV

Placement
1 Acct-Status-Type
2 NAS-IP-Address
3 NAS-Port
4 Acct-Session-Id
11 Acct-Terminate-Cause
12 Acct-Session-Time
13 h323-setup-time
15 h323-disconnect-time
16 h323-disconnect-cause

APPENDIX C
58 Acme-Called-RTCP-Avg-Jitter_FS1 47
59 Acme-Called-RTCP-Avg-Latency_FS1 48
60 Acme-Called-RTCP-MaxJitter_FS1 49

APPENDIX C

APPENDIX C
102 Acme-Called--RTCP-Avg-Jitter_FS2 127
103 Acme-Called--RTCP-Avg-Latency_FS2 128
104 Acme-Called--RTCP-MaxJitter_FS2 129
112 Acme-Session-Charging-Function-Address 55
127 Acme-Session-Disposition 60
128 Acme-Disconnect-Initiator 61
129 Acme-Disconnect-Cause 62
130 Acme-SIP-Status 71

APPENDIX C
134 Acme-Refer-Call-Transfer-Id 141

Account Guide

Uploaded by

Copyright:

Available Formats

Account Guide

Uploaded by

Document Information

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

Account Guide

Uploaded by

Copyright:

Available Formats

Net-Net 4000

Release Version C6.0.0

Acme Packet, Inc.

Last updated: August 1, 2008

Who is Acme Packet?

Version C6.0.0 Acme Packet, Inc. Technical Publications iii

Document Name Document Description

Net-Net 4250 Hardware Contains information about the components and

Net-Net 4500 Hardware Contains information about the components and

Net-Net 4000 Configuration Contains information about the administration and

Net-Net 4000 MIB Reference Contains information about Management

Date Revision Number Description

iv Net-Net 4000 Accounting Guide Version C6.0.0

Customer Questions, Comments, or Suggestions

Version C6.0.0 Acme Packet, Inc. Technical Publications v

vi Net-Net 4000 Accounting Guide Version C6.0.0

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

Using RADIUS with the Net-Net SBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Version C6.0.0 Acme Packet, Inc. Technical Publications vii

SIP-SIP Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Configuring Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

viii Net-Net 4000 Accounting Guide Version C6.0.0

Caveats for H.323 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

RADIUS Accounting Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Net-Net 4000 C6.0.0 RADIUS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Local File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Version C6.0.0 Acme Packet, Inc. Technical Publications ix

x Net-Net 4000 Accounting Guide Version C6.0.0

Version C6.0.0 Acme Packet, Inc. Technical Publications 11

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

NAS-IP-Address IP address of the SIP proxy or the 4 IP Start

NAS-Port SIP proxy port or the H.323 stacks 5 integer Start

12 Net-Net 4000 Accounting Guide Version C6.0.0

Called-Station-Id To field value of the SIP INVITE 30 string Start

Calling-Station-Id From field value of the SIP INVITE 31 string Start

NAS-Identifier Value, if any, set in the optional 32 string Start

The remote server to which the

This attribute only appears if a

Acct-Status-Type Whether this Accounting Request 40 integer Start (1)

Acct-Session-Id Either the Call-ID field value of 44 string Start

Acct-Session- How much time in seconds the 46 integer Interim-Update

Acct-Terminate- How or why the session ended. 49 integer Stop

Version C6.0.0 Acme Packet, Inc. Technical Publications 13

User Request 1 A SIP BYE message. Stop

Lost Service 3 Service cannot be sustained for reasons such Stop

Admin Reboot 7 Net-Net SBC gracefully rebooted. Off

NAS Request 10 RADIUS server is disabled; session terminated Off

14 Net-Net 4000 Accounting Guide Version C6.0.0

Inbound Flow AttributesDetailed traits of the inbound media flow (including

Version C6.0.0 Acme Packet, Inc. Technical Publications 15

Acme-CDR-Sequence- Sequence number (that increases by 1) 59 integer Start

Acme-Intermediate- Time interval at which periodic interim 63 string Interim-Update

Acme-Local-Time-Zone Local GMT/UTC time zone that is 57 string Start

Acme-Firmware- Current software version running on the 56 string Start

General Flow Attributes

Acme-FlowID_FS1_F Unique identifier for every media flow 1 string Start

Acme-FlowID_FS1_R Unique identifier for every media flow 78 string Start

Acme-FlowID_FS2_F Unique identifier for every media flow 90 string Start

Acme-FlowType_FS1_F Codec that describes the flow, flow-set 1 2 string Start

16 Net-Net 4000 Accounting Guide Version C6.0.0