Troubleshooting guide

1-23
Cisco Broadband Local Integrated Services Solution Troubleshooting Guide
OL-5169-01
Chapter 1 Solution Overview
Solution Components
In terms of billing for on-net versus off-net calls, different BAF structures are generated between on-net
calls, which are defined as calls completed within the service providers network, and off-net calls, which
are defined as calls completed outside the service providers network, such as PSTN calls.
RADIUS—is the protocol defined in Internet Engineering Task Force (IETF) Request for Comments
(RFC) 2138, Remote Authentication Dial In User Service (RADIUS). The use of the RADIUS protocol
for accounting purposes is defined in IETF RFC 2139, RADIUS Accounting, which defines the use of
two RADIUS packet types for accounting: Accounting-Request and Accounting-Response.
• Accounting-Request packets are mainly used to convey raw usage data. These packets are also used
to indicate when accounting has been turned on or off at the RADIUS Accounting Client, which is
the component that generates usage data and creates Accounting-Request packets.
• Accounting-Response packets are used by the RADIUS Accounting Server, which is the recipient
of Accounting-Request packets, to acknowledge the receipt of Accounting-Request packets.
In the defined BLISS for Cable architecture, the role of the RADIUS Accounting Client is played by the
Cisco BTS 10200, and the role of the RADIUS Accounting Server is played by the accounting gateway.
Announcement Servers
The Announcement Server (AS) receives MGCP signaling control messages from the Cisco BTS 10200
Call Agent and sends announcements to specified destinations, such as subscriber MTAs, using RTP.
The Announcement Server supports the following capabilities:
• Announcement servers store local copies of all audio announcements
• The Call Agent communicates with an announcement server to provide announcement services
using MGCP.
These communications include:
– A request from the Call Agent to create a connection context
– A request from the Call Agent to start sending a specified announcement file to a specific
address/port on the IP network.
The announcement server sends announcements as a series of RTP packets over the IP network.
The request also dictates whether an announcement is to be sent once, a specified number of
times, or in a continuous loop.
– A request from the Call Agent to terminate the connection context and end the play operation
– A message from the Announcement Server to the Call Agent indicating that the play operation
has been terminated.
The announcement server does not support the following:
• data dependent announcements
• Only G.711 encoding is supported in the first solution release
• Only single announcements are supported.
In addition, there are no indicators present in the Call Agent to allow user specified multilingual
announcements.
• Signaling tones, such as a busy signal, can be played by the MTA, but Special Information Tones
(SIT) can be included as part of an announcement file.