Configuring Dynamic Prompts, Customizing Accounting Templates, and Directing AAA Requests for Voice Gateways
Overview

Table of Contents

An Overview of Dynamic Prompts, Accounting Templates, and Directing AAA Requests

An Overview of Dynamic Prompts, Accounting Templates, and Directing AAA Requests

Feature History
Release Modification

12.2(11)T

Customizing accounting templates, directing AAA requests, and enhancements to dynamic prompts are introduced on the Cisco 3660, Cisco AS5300, Cisco AS5350, Cisco AS5400, Cisco AS5800, and Cisco AS5850.

This chapter consists of the following:

Dynamic Prompts

The functionality of dynamic prompts, an existing Cisco IOS feature, has been expanded in Cisco IOS Release 12.2(11)T to playout ISO formatted time and date, and visible noncontrol ASCII characters. Dynamic prompts allow a TCL application to play the date and time information on a Cisco voice gateway. The information is first retrieved by using the clock command in the TCL library, and then played through dynamic prompts using the multi-language script.

The media play command in the TCL library plays the specified dynamic prompt on the specified call leg. The English version of the multi-language TCL script must be enabled before you use the media play command; it allows a dynamic prompt to play string, and visible noncontrol ASCII characters.

AAA Enhancements to Voice Gateways

Cisco IOS Release 12.2(11)T introduces the capability of splitting AAA requests to RADIUS servers based on account number, called party number, and incoming trunk groups.

Consider the topology shown in Figure 1 below.


Figure 1: RADIUS/Billing Selection Based on DNIS and Card Number


In Figure 1 above, the gateway identifies the TCL IVR application to be invoked based on:

  • The access number dialed by the caller, or

  • The account number or card number

Calling party A has a different access number compared to calling parties B and C. Because calling parties B and C use the same access number, the service provider can use the TCL IVR script to manipulate the call and direct the AAA information to the appropriate billing/RADIUS server based on the individual card numbers entered by callers B and C. If a caller is using an account number instead of a prepaid calling card, the service provider can use the caller's account number to direct the AAA information to the appropriate RADIUS/billing server that is used to authorize calls based on account numbers.

Figure 2 below shows RADIUS/Billing server selections based on T1/E1 trunk groups. For example, if caller A is using a pre-paid application, the service provider directs AAA information to the appropriate RADIUS/Billing server based on the T1/E1 trunk group that is assigned to receive prepaid application calls.


Figure 2: RADIUS/Billing Server Selection Based on T1/E1 Trunk Groups


Customizing Accounting Records

You can create an accounting template to customize your accounting records based on your billing needs. An accounting template is a text-based interface that allows you to customize and define the content of that template and helps reduce billing traffic from the gateway to the accounting servers.

A sample accounting template applicable to POTS and VoIP dial-peers is shown below.

Vendor specific attributes (VSAs) used in session applications such as h323-ivr-out, h323-credit-amount, h323-credit-time, h323-billing-model, are only controlled in the TCL script and not in the accounting template. If you specify these VSAs in the accounting template, they are ignored and no error messages are reported. You cannot control h323-conf-id and h323-incoming-conf-id; they are mandatory VSAs required for co-relating accounting messages on the incoming and outgoing legs.

Session applications also use some VSAs for authentication and authorization which are not controlled by the accounting template. For example, h323-ivr-out, h323-credit-amount, h323-credit-time, and h323-billing-model are only controlled by the TCL script. The VSAs listed in this template are voice-specific only. Non-voice specific attributes cannot be controlled through this template. To add new attributes not defined in this template, contact your Cisco marketing representative.

To delete an attribute, add the # sign in front of the attribute name.

Accounting Template

You can create a custom accounting template by selecting only those VSAs that are applicable to your billing needs. The list below shows some existing VSAs introduced in previous Cisco IOS releases (also known as default VSAs in this document) and new VSAs introduced in Cisco IOS Release 12.2(11) T that can be used to create custom accounting templates. For the latest list of VSAs, refer to the RADIUS Vendor-Specific Attributes Voice Implementation Guide.

Attribute Name Usage and Restrictions

h323-gw-id

h323-call-origin

h323-call-type

h323-setup-time

h323-connect-time

h323-disconnect-time

h323-disconnect-cause

h323-remote-address

h323-voice-quality-subscriber

ICPIF

Detail CallHistory

acom-level

#POTS leg only

noise-level

#POTS leg only

img-pages-count

#POTS leg only

voice-tx-duration

#POTS leg only

tx-duration

#POTS leg only

charged-units

#

disconnect-text

#

peer-if-index

#

logical-if-index

#

codec-type-rate

#

codec-bytes

#IP leg only

session-protocol

#IP leg only

vad-enable

#IP leg only

remote-udp-port

#IP leg only

hiwater-playout-display

#IP leg only

lowater-playout-display

#IP leg only

receive-delay

#IP leg only

round-trip-delay

#IP leg only

ontime-rv-playout

#IP leg only

gapfill-with-silence

#IP leg only

gapfill-with-prediction

#IP leg only

gapfill-with-interpolation

#IP leg only

gapfill-with-redundancy

#IP leg only

lost-packets

#IP leg only

early-packets

#IP leg only

late-packets

#IP leg only





Each accounting template attribute is unique. For example, the attribute disconnect-time is applied to a stop message because you can only get that information at the end of a call and not at the start of that call.

If you want to generate individual accounting templates for different incoming trunk calls on an accounting server, you can define multiple templates and associate them with different sets of incoming dial-peers. You can customize the template by deleting attributes that are not required for your specific template.

Related Features and Technologies

  • Service Provider feature set for VoIP uses the IVR for interaction with the caller; collects digits for accounting and billing purposes.

  • Authentication, Authorization, and Accounting (AAA) feature is used in conjunction with IVR.

  • Settlement for Packet Telephony on Cisco Access Platforms uses the TCL IVR scripts for the billing process.

  • Debit Card for Packet Telephony on Cisco Access Platforms uses TCL IVR extensively for interoperability.

  • Enhanced Multi-Language Support for Cisco IOS Interactive Voice Response allows you to implement and add support for new languages and text-to-speech (TTS) notations to the core IVR infrastructure on Cisco voice gateways.

Related Documents

For related information on the features described in this document, refer to the following documents:


Tip see the "Obtaining Documentation" section.

Supported Platforms

This feature is supported on the following platforms:

  • Cisco 3660 router

  • Cisco AS5300 universal access server

  • Cisco AS5350 universal gateway

  • Cisco AS5400 universal gateway

  • Cisco AS5800 universal gateway

  • Cisco AS5850 universal gateway

Determining Platform Support Through Cisco Feature Navigator

Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.

Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.

To access Cisco  Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:

http://www.cisco.com/register

Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:

http://www.cisco.com/go/fn

Availability of Cisco IOS Software Images

Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.

Supported Standards, MIBs and RFCs

MIBs

There are no MIBs. To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB web site on Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://tools.cisco.com/ITDIT/MIBS/servlet/index

If Cisco  MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco  MIBs page at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:

http://www.cisco.com/register

RFCs
  • Remote Authentication Dial In User Service (RADIUS), RFC 2138

  • RADIUS Accounting, RFC 2139

Prerequisites

The following tasks are a prerequisite to configuring the Cisco IOS features in this document:

  • Establish a working IP network. For more information about configuring IP, refer to the "IP Overview," "Configuring IP Addressing," and "Configuring IP Services" chapters in the Cisco IOS Release 12.0 Network Protocols Configuration Guide, Part 1.

  • Configure Voice over IP. For more information about configuring Voice over IP, refer to the "Voice over IP Software Configuration Guide."

  • Configure a TFTP sever to perform storage and retrieval of the audio files, which are required by the Debit Card gateway or other features requiring TCL IVR scripts and audio files.

  • Program and configure the interface between the RADIUS server and the Cisco voice gateway to operate with vendor specific attributes (VSAs).

  • Download the TCL scripts that are not embedded in Cisco IOS from the Cisco CCO software support URL:
    http://www.cisco.com/public/sw-center/

  • Define and apply IVR applications on the dial peer to direct AAA requests to a RADIUS server.


Tip See the "Related Documents" section.

Hardware Requirements

One of the following hardware platforms is required:

  • Cisco AS5300 universal access server with a voice feature card (VFC)

  • Cisco AS5350 or Cisco AS5400 universal gateway with a dial feature card (DFC)

Memory Requirements

  • DRAM

    • Cisco 2650 and Cisco 3640: at least 96 MB of DRAM

    • Cisco AS5300 and Cisco AS5350: minimum 128 MB of DRAM

    • Cisco 3660 and Cisco Cisco AS5400: minimum 256 MB of DRAM

  • Flash memory

    • Cisco 2650, 3640, 3660 and Cisco AS5300: minimum 16 MB of Flash memory

    • Cisco AS5350 and Cisco AS5400: minimum 32 MB of Flash memory