Guest

Cisco BTS 10200 Softswitch

PacketCable and Event Message Provisioning and Operations (Release 4.4.x)

  • Viewing Options

  • PDF (665.9 KB)
  • Feedback
PacketCable and Event Message Provisioning and Operations Guide (Cisco BTS 10200 Softswitch Release 4.4.x)

Table Of Contents

PacketCable and Event Message Provisioning and Operations Guide
(Cisco BTS 10200 Softswitch Release 4.4.x)

Overview

New PacketCable-Based Features and Functions for Release 4.4.x

CMS, MGC, and FEID Values and Billing Support Parameters

AUEP and ICMP Ping Options

Cisco BTS 10200 Softswitch In the PacketCable Network

PacketCable-Based Interfaces

Additional Network Interfaces

Gate Coordination Functions

Security Interface Features

Event Message Feature

Billing Data Options

Description of the Event Message Feature

Event Message Generation Details and Content

Timestamp Support for Event Messages

Event Message Transport

Event Message Storage on the CA

Planning

Installing

Configuring

Provisioning Basic PacketCable and DQoS Features

Provisioning CMS Parameters

Provisioning the CMS (Interfaces to the CMTS and eMTA)

Provisioning DQoS Parameters for Codec Negotiation Service

Provisioning TGCP Interfaces to TGW

Provisioning the Keepalive AUEP and ICMP Ping Options (Release 4.4.x and Later)

Provisioning Security Interfaces

Provisioning Parameters for Secured Media

Provisioning Security Interfaces to the MTA

Provisioning Security Interfaces to the CMTS

Provisioning Security Interfaces to the TGW

Provisioning Security Interfaces to the RKS

Provisioning IPsec Security Associations and Ciphersuite Algorithms

Provisioning Event Messages

Provisioning Support for EM Transmission and Storage

Provisioning the System to Generate EMs for Billing

Provisioning Media_Alive Verification for EMs

Operating

Status Command

Manual Recovery and Transfer of Stored EMs

Recovering the Billing Files

Sending Billing Files to the RKS via FTP

Comparing Checksums

Viewing Media_Alive Verification for EMs

EM Generation Details and Content

EM Generation Details

EM Content

Measurements

Creating Reports and Displays of Measurements

Measurements for the DQoS Feature on COPS Interface

Measurements for the EM Feature

Events and Alarms

Events and Alarms Specific to PacketCable-Based Network Elements

Events and Alarms for the EM Feature

Events and Alarms for the Security Interface Feature

Announcements

References

Related Documents

Industry Standards


PacketCable and Event Message Provisioning and Operations Guide
(Cisco BTS 10200 Softswitch Release 4.4.x)


This document describes how the Cisco BTS 10200 Softswitch implements PacketCable-based interfaces and functions. It also provides provisioning and operating information for PacketCable features and event messages (EMs). It is intended for use by service provider management, system administration, and engineering personnel who are responsible for designing, installing, configuring, and maintaining networks that use the Cisco BTS 10200 Softswitch system in a PacketCable-based network.


Note All of the features and functions described in this document are applicable to both Release 4.4.0 and Release 4.4.1, unless specifically noted. Release 4.4.x refers to both Release 4.4.0 and 4.4.1.


Feature History

Release
Modification

Release 4.4.x

Document #OL-6017-02: Notes were added referring to the BTS 10200 Softswitch Provisioning Guide and the Cisco BTS 10200 Softswitch Command Line Interface Guide. The document title and introduction were enhanced for clarity.

OL-6017-01:

This document was reorganized for enhanced usability.

References to PacketCable specifications were updated to a level consistent with CW27.

The CLI commands for CMS, MGC, CDB, and EM identification in the Call Agent profile (call-agent-profile) table were updated.

Commands related to AUEP and ICMP ping functionality were added

Provisioning examples were updated as needed.

Information was added in the Installation section on IPSEC_ENABLED parameter.

Clarified GATE-OPEN and GATE-CLOSE procedures.

Release 4.2

New rule was added in the IPsec Policy (ipsec-policy) table for source and destination identifiers.

Spelling of the token name MAX-DQOS-SESSIONS was corrected.

Release 4.1

TGCP and IP security support were added.

Provisioning commands, feature descriptions, and user interfaces were updated.

Compliance matrices were removed from the scope of this document—these are now provided by the Cisco account team.

Operational information about EMs was moved to Appendix B of this document.

Wording of BILLING_EM_RETRANS measurement was updated.

Caution was emphasized for storage of EMs on local CA disk when transmission to RKS is unsuccessful.

Descriptions of ciphersuite tokens was clarified.

Release 3.5

New alarms were added for Release 3.5.

Updates, corrections and clarifications were added to this document.

Release 3.3

The PacketCable feature was introduced, including COPS, NCS, DQoS and EM support.


Overview

This section provides technical information about the implementation of PacketCable features. It covers the following topics.

New PacketCable-Based Features and Functions for Release 4.4.x

Cisco BTS 10200 Softswitch In the PacketCable Network

Security Interface Features

Event Message Feature


Note In this document, embedded multimedia terminal adapter (eMTA) refers to eMTAs using PacketCable Network-Based Call Signaling (NCS) protocol.


New PacketCable-Based Features and Functions for Release 4.4.x

This section describes the PacketCable-based features that are new in Release 4.4.x of the Cisco BTS 10200 Softswitch.

CMS, MGC, and FEID Values and Billing Support Parameters

In Release 4.4.x, the CMS ID, MGC ID, and FEID default values are modified. The billing support token dependencies (CDB and EM) are also modified. These tokens belong to the Call Agent Profile (call-agent-profile) table.

AUEP and ICMP Ping Options

Release 4.4.x adds a provisionable option for controlling Internet Control Message Protocol (ICMP) pings from the Cisco BTS 10200 Softswitch to the eMTAs.


Note Each eMTA is provisioned in the Cisco BTS 10200 Softswitch database using the Media Gateway (mgw) table.


If an audit endpoint (AUEP) ping is sent from the Cisco BTS 10200 Softswitch and fails to get a response from the eMTA, the Cisco BTS 10200 Softswitch can then send out an ICMP ping to the eMTA to detect IP connectivity. The service provider can provision the system in any of the following ways:

Disable both AUEP and ICMP ping.

Enable AUEP ping but not ICMP ping.

Enable sending of an AUEP ping followed (if AUEP is unsuccessful) with an ICMP ping.

The following operational functions apply to the AUEP/ICMP feature:

The Cisco BTS 10200 Softswitch performs the pings to the first termination provisioned in the Media Gateway (mgw) table for the applicable MGW (eMTA).

If the AUEP attempt to the MGW fails and the ICMP also fails (or is disabled), the Cisco BTS 10200 Softswitch considers the link to the applicable MGW to be inactive.

Alarm: SIGNALING #68—If ICMP ping is enabled, the Cisco BTS 10200 Softswitch stores the ICMP ping result as a dynamic field in the mgw table. If the AUEP ping fails, the alarm is generated only after the ICMP ping completes, and the SIGNALING alarm #68 contains the message "ICMP ping <success/fail/in progress/not performed>."

Status MGW—If ICMP ping is enabled, and if the status command is issued for the mgw table, the system response contains the message "ICMP ping status <success/fail/in progress/not performed>."


Note If the ICMP ping is disabled, or if the ICMP ping status is not performed, the system responses to both the alarm and status queries show the ICMP ping status as "not performed."


The procedure for provisioning this option is provided later in this document ("Provisioning the Keepalive AUEP and ICMP Ping Options (Release 4.4.x and Later)" section).

Cisco BTS 10200 Softswitch In the PacketCable Network

The Cisco BTS 10200 Softswitch is a class-independent network-switching element. In a PacketCable-based network, it functions as both a call management server (CMS) and a media gateway controller (MGC). It provides call control, call routing, and signaling for several types of multimedia terminal adapters (MTAs) and embedded MTAs (eMTAs), cable modem termination systems (CMTSs), and trunking gateways (TGWs) in PacketCable-based networks. It provides interfaces to record keeping servers (RKSs) and key distribution centers (KDCs). The Cisco BTS 10200 Softswitch also communicates with announcement servers, SS7-based signaling gateways, MGCP-based media gateways (MGWs), and Session Initiation Protocol (SIP) networks.

Figure 1 shows a typical network with PacketCable-based network elements and the applicable external interfaces of the Cisco BTS 10200 Softswitch. In the PacketCable-based network, the Cisco BTS 10200 Softswitch performs the functions of both the CMS and MGC. The Cisco BTS 10200 Softswitch also provides provisionable options for customizing the external interfaces.

Figure 1 Example of PacketCable-Based Network Architecture

PacketCable-Based Interfaces

The Cisco BTS 10200 Softswitch supports signaling on specific PacketCable-based interfaces shown in Figure 1. The following list summarizes the supported protocols for each of the links:

CMS/MTA (NCS)—CMS to MTA interface for subscriber access

CMS/CMTS (COPS)—CMS to CMTS interface for gate management

CMS/RKS (EM over RADIUS)—CMS to Record Keeping Server (RKS) interface for EM-based billing functions

MGC/RKS (EM over RADIUS)—MGC to RKS interface for EM-based billing functions

CMS/CALEA (EM over RADIUS)—CMS to CALEA server (DF) interface (Note: DF = Delivery Function)

MGC/TGW (TGCP)—MGC to trunking gateway (TGW) interface for TGW management (which allows calls to be connected between the PacketCable network and the PSTN)


Note For a description of Cisco BTS 10200 Softswitch support for CALEA, see the Cisco BTS 10200 Softswitch System Description. For provisioning procedures related to CALEA support, see the Cisco BTS 10200 Softswitch Provisioning Guide.



Note For information on compliance to specific paragraphs of PacketCable standards and ECNs, contact your Cisco account team.


Additional Network Interfaces

The following additional interfaces are not part of the PacketCable feature set, but they provide other important functions useful in the service provider network.

Cisco BTS 10200 Softswitch/Signaling Gateway (SIGTRAN)—This interface allows calls to be made between the PacketCable network and the PSTN. The Call Agent (CA) of the Cisco BTS 10200 Softswitch interfaces to an Internet transfer point (ITP) signaling gateway (SG), for example, the Cisco 7500 series router. The ITP SG provides an SS7-based interface to the STP (PSTN).

MGCP Interface—The Cisco BTS 10200 Softswitch communicates with MGCP-based TGWs that provide bearer path to the PSTN.

SIP Interface—Session Initiation Protocol (SIP) signaling is used for the following two functions:

Communications with another CMS

Access to voice mail

Cisco BTS 10200 Softswitch /office applications (SNMPv3 and CORBA over TCP/IP)
This interface provides communication with Operations Support System (OSS) and office applications servers.

Gate Coordination Functions

The Cisco BTS 10200 Softswitch performs the gate coordination functions of a CMS, including the gate controller (GC), in the PacketCable environment. GC signaling is based on the COPS stack. Each CMTS informs the CMS when a gate is successfully opened or closed. Two gate coordination messages are used, GATE-OPEN and GATE-CLOSE. Gate coordination is required to avoid several theft-of-service scenarios, as described in Appendix K of the PacketCable Dynamic Quality-of-Service Specification, PKT-SP-DQOS-I07-030815, August 15, 2003.


Note For information on compliance to specific paragraphs of PacketCable standards and ECNs, contact your Cisco account team.


GATE-OPEN Process

The normal coordination process for GATE-OPEN signaling is illustrated in Figure 2:

1. During call setup, the Cisco BTS 10200 Softswitch requests the MTA to commit bearer-path resources.

2. The MTA sends a Commit message to the CMTS to request opening of the gate on the bearer path.

3. The CMTS opens the gate and sends a GATE-OPEN message to the Cisco BTS 10200 Softswitch.

4. The Cisco BTS 10200 Softswitch allows the call.

Figure 2 Gate Coordination Signaling Example (GATE-OPEN)


Note If the GATE-OPEN message arrives at the Cisco BTS 10200 Softswitch before it has sent a resource-commit request to the MTA, the Cisco BTS 10200 Softswitch tears down the call.


GATE-CLOSE Process

During a call, if the Cisco BTS 10200 Softswitch receives a GATE-CLOSE message from the CMTS, it allows the call to proceed on a best-efforts basis, without a guaranteed level of service. (It tears down the call only when one of the parties in the call goes on-hook.)

Security Interface Features


Note For information on compliance to specific paragraphs of PacketCable standards and ECNs, contact your Cisco account team.


The implementation of PKT-SP-SEC-I09-030728, PacketCable Security Specification, July 28, 2003, provides a security scheme for the voice-over-cable network based on a set of security protocols. These protocols, based on the documents listed below, provide authentication (to help prevent theft of bandwidth, denial-of-service attack, replay, and so forth) and enable message integrity, privacy, and confidentiality.

IETF documents covering IP security (IPsec) architecture:

RFC 2401, Security Architecture for the Internet Protocol, IETF (S. Kent, R. Atkinson), Internet Proposed Standard, November 1998.

RFC 2406, IP Encapsulating Security Payload (ESP), IETF (D. Piper), Internet Proposed Standard, November 1998.

IETF documents covering key management protocols—Internet Key Exchange (IKE) and Kerberos with extensions:

RFC 2409, The Internet Key Exchange (IKE), IETF (D. Harkins, D. Carrel), Internet Proposed Standard, November 1998.

RFC1510, The Kerberos Network Authentication Service (V5), IETF (J. Kohl, C. Neuman), September 1993, with updates presented in PKT-SP-SEC-I09-030728.

The Cisco BTS 10200 Softswitch performs the security functions of a call management server (CMS) and media gateway controller (MGC) in the PacketCable environment. It supports security in accordance with PKT-SP-SEC-I09-030728 for both signaling and media:

Signaling security—For signaling from CMS to eMTA, CMS to CMTS, and MGC to TGW

Media (bearer) security—For signaling between originating eMTA and terminating eMTA, which is facilitated by the CMS during call signaling setup.

The system supports IP security (IPsec) features for encryption and authentication on specific PacketCable-based interfaces (see Figure 1). There are two aspects to the security features, the security protocol itself (IPsec), and the key management (Kerberos or IKE). The following list summarizes the supported security type for each of the links:

CMS/MTA (NCS)—IPsec/Kerberos

CMS/CMTS (COPS)—IPsec/IKE

CMS/RKS (EM over RADIUS)—IPsec/IKE

MGC/RKS (EM over RADIUS)—IPsec/IKE

CMS/CALEA (EM over RADIUS)—IPsec/IKE

MGC/TGW (TGCP)—IPsec/IKE

As shown in Figure 1, there is no interface between the KDC and the Cisco BTS 10200 Softswitch. To ensure secure NCS signaling, the dynamic key exchange for IPsec security operation between the MTA and the Cisco BTS 10200 Softswitch is achieved as follows. (These procedures are described in the CableLabs document PacketCable Security Specification, PKT-SP-SEC-I09-030728, under "Kerberized IPsec" and other sections.)

Manual key provisioning must be used to match data stored in the KDC with data stored in the Cisco BTS 10200 Softswitch (pre-setup).

The MTA must contact the KDC to obtain the credentials to talk to the server, which is in this case the Cisco BTS 10200 Softswitch.


Note For information on compliance to specific paragraphs of PacketCable standards and ECNs, contact your Cisco account team.



Note See the "Installing" section regarding the requirement for setting the IPSEC_ENABLED parameter at the time of Cisco BTS 10200 Softswitch software installation.


Event Message Feature

This section describes Cisco BTS 10200 Softswitch support for the event message (EM) feature.

Billing Data Options

The Cisco BTS 10200 Softswitch has the ability to provision billing support using either of the following billing data generation methods:

Call Detail Blocks (CDBs)—This is traditional post-call billing data, which is assembled into Call Detail Records (CDRs) by an external billing mediation system or billing server.

PacketCable event messages (EMs)—This is real-time call data flow, which is transferred to an external Record Keeping Server (RKS) that assembles CDRs from the EMs.

The Cisco BTS 10200 Softswitch should be provisioned to generate either EMs or CDBs, but not both.


Caution Cisco strongly recommends that you provision the Cisco BTS 10200 Softswitch to generate either EMs or CDBs, but not both. Attempting to generate both types of records simultaneously can significantly degrade system performance. See the "Provisioning the System to Generate EMs for Billing" section for provisioning details.


Note The contents of CDBs is outside the scope of this document. See the Cisco BTS 10200 Softswitch Billing Interface Guide for information about CDBs.


Description of the Event Message Feature

EMs are real time data records containing information about network usage and activities. (They must not be confused with system event messages that report events and sometimes trigger alarms.) EMs are used in PacketCable networks to collect resource usage data for billing purposes. In the PacketCable architecture EM generation is based on the half-call model. A single EM can contain a complete set of usage data or it might contain only part of the usage information.

The Record Keeping Server (RKS) is a PacketCable network element that receives EMs from network elements, such as the Call Management Server (CMS), Media Gateway Controller (MGC), and the Cable Modem Termination System (CMTS). The physical Cisco BTS 10200 Softswitch contains both CMS and MGC logical network elements. The EMs generated by both the CMS and MGC are sent to the RKS. The RKS correlates the information in multiple EMs and provides the complete record of service for a call, which is referred to as a Call Detail Record (CDR).


Note For information about EM-related operations on the Cisco BTS 10200 Softswitch, see to the "EM Generation Details and Content" section.


Figure 3 illustrates the PacketCable network elements that are involved in the EM process.

Figure 3 Event Message Interfaces

The EM related interfaces illustrated here are described as follows:

1. MGC to RKS—EMs generated by MGC (Cisco BTS 10200 Softswitch) are sent to RKS

2. CMS to RKS—EMs generated by CMS (Cisco BTS 10200 Softswitch) are sent to RKS

3. CMTS to RKS—EMs generated by CMTS are sent to RKS. The Cisco BTS 10200 Softswitch (MGC/CMS) is not involved

4. CMS to CMTS—CMS (Cisco BTS 10200 Softswitch) sends the Billing Correlation ID (BCID) to the CMTS using the DQoS GateSet message

5. CMS to MGC—An internal exchange of originating/terminating information such as BCID and FEID.

PacketCable EMs can support billing and settlement activities for single-zone architectures. The originating and terminating CMSs exchange unique Billing Correlation IDs (BCIDs) and Financial Entity IDs (FEIDs) for each half of the call. The originating CMS sends a BCID and an FEID in the INVITE message. The Cisco BTS 10200 Softswitch allocates the BCID for calls it originates or terminates. Along with the FEID, the BCID is used across network elements to reference calls. The FEID is provisioned on a system-wide basis (a single setting for the Cisco BTS 10200 Softswitch) as defined in the "Provisioning the System to Generate EMs for Billing" section.

Event Message Generation Details and Content

See the "EM Generation Details and Content" section for information on EM data.

Timestamp Support for Event Messages

The system-generated timestamps for EMs are based on the host operating system (OS) time and time zone. This data is not affected by CLI provisioning. The Solaris OS obtains the time automatically through network time protocol (NTP) services.


Caution Users should never attempt to modify the system date or time in their Cisco BTS 10200 Softswitch host machines while system components (CA, FS, EMS, and BDMS) are running. This could cause the system to have serious problems. Allow the Solaris OS to obtain the time automatically through NTP services.

Event Message Transport

The RADIUS transport protocol is used between the Cisco BTS 10200 Softswitch (CMS/MGC) and the RKS. EMs are sent to an RKS without waiting for acknowledgement of the previous message. The maximum number of pending ACK messages is 256.

EMs are first sent to the primary RKS and, after the specified number of retry attempts fail, they are sent to the secondary RKS. If one RKS is found to be unreachable, then the other RKS is considered for subsequent messages. If both the primary and secondary RKS become unreachable, the EMs are stored in an error file on the hard disk (as described in the "Event Message Storage on the CA" section) and a timer is started. When the timer expires, newly-arriving EMs will be sent to the primary RKS.


Note If EMs are being sent to the primary RKS, and the primary RKS goes down, the Cisco BTS 10200 Softswitch sends subsequent EMs to the secondary RKS. When the primary RKS comes back up, the Cisco BTS 10200 Softswitch will continue to send EMs to the secondary RKS. (It will not automatically begin sending them to the primary RKS.) Provisioning of timers and retry attempts is described in the "Provisioning Support for EM Transmission and Storage" section.



Note Remote Access Dial-In User Service (RADIUS) is a client/server protocol used for Authorization, Authentication, and Accounting (AAA). The RADIUS protocol is an industry standard for remote access AAA defined in a set of Internet Engineering Task Force (IETF) standards: RFC 2865 and RFC 2866.


Event Message Storage on the CA


Note For information on compliance to specific paragraphs of PacketCable standards and ECNs listed in this document, contact your Cisco account team.


EMs are stored in the network element (CA) that generates them until successful transfer to the RKS. Once receipt of the EMs is acknowledged by the RKS, they are deleted. The number of EMs generated by the Cisco BTS 10200 Softswitch depends on the number of calls processed. Multiple EMs are generated for each call. Depending on provisioning in the call-agent-profile table, and the type of call, EMs can be generated by the CMS or MGC (or both) within the CA. The exact storage requirement varies depending on the rate of EM generation and how long the Cisco BTS 10200 Softswitch is required to keep the records before transferring them to an RKS.

The Cisco BTS 10200 Softswitch generates and stores EMs with the following characteristics:

EMs are generated in real time during a call. EMs contain timestamps with a granularity of 1 millisecond. The time interval between generation and transmission is not specified.

The Cisco BTS 10200 Softswitch synchronizes with the network clock using NTP at least once per hour. The deviation of the clock in the Cisco BTS 10200 Softswitch remains within ± 100 milliseconds between NTP synchronizations.

EMs that cannot be successfully transferred to the RKS due to loss of communication are stored in the /opt/BTSem directory on the CA. The system uses the file naming conventions specified in the PacketCable Event Messages Specification (PKT-SP-EM-I07-030815) for the stored EMs. The maximum EM file size, and the time limit on keeping a file open, are provisionable as described in the "Provisioning Support for EM Transmission and Storage" section. These files are not automatically deleted nor transferred out of the CA—the operator must transfer these files to the RKS when communication is restored. The procedure for doing this is provided in the "Manual Recovery and Transfer of Stored EMs" section.


Caution Event messages that cannot be successfully transferred to the RKS due to loss of communication are not automatically deleted nor transferred out of the CA. You must transfer these files to the RKS when communication is restored.

The procedure for doing this is provided in the "Manual Recovery and Transfer of Stored EMs" section.

Each time an EM file is placed in local storage, the system checks current disk usage and takes the following actions:

The system generates an alarm if the disk space allocated to EMs fills up to a certain level—
50% (Minor alarm), 70% (Major alarm), or 100% Critical alarm.

When the critical condition is reached, and after raising the critical alarm, further EMs are dropped without any additional warning.

When the critical condition is reached, the disk usage is monitored periodically (one time every minute) to check if disk space usage has decreased and EMs can be stored again.

Planning

Delivery of the features and functions described in this document requires interoperability with the network elements connected to the Cisco BTS 10200 Softswitch. See the "Component Interoperability" section in the Cisco BTS 10200 Softswitch Release Notes, which lists the specific peripheral platforms, functions, and software loads that have been tested by Cisco for interoperability with the Cisco BTS 10200 Softswitch.


Note The "Component Interoperability" section in the Cisco BTS 10200 Softswitch Release Notes is intended as a guide. Earlier or later releases of platform software might be interoperable and it might be possible to use other functions on these platforms. The list certifies only that the required interoperation of these platforms, the functions listed, and the protocols listed have been successfully tested with the Cisco BTS 10200 Softswitch.


Installing

Installation of Cisco BTS 10200 Softswitch software follows a standard process. For details, see the Application Installation Procedure in the Cisco BTS 10200 Softswitch documentation set. Of the three main PacketCable feature areas (DQoS, EM, and security), two of them (DQoS and EM) are always installed, and do not require the setting of any special flags during software installation. However, the third area (security) is not installed unless a special flag (IPSEC_ENABLED) is set in the opticall.cfg file during software installation.


Caution Cisco strongly recommends that you contact Cisco TAC if you believe that you may need to reinstall Cisco BTS 10200 Softswitch software in order to change the value of IPSEC_ENABLED.

Configuring

This section explains how to perform the following procedures:

Provisioning Basic PacketCable and DQoS Features

Provisioning Security Interfaces

Provisioning Event Messages


Tip These tasks include examples of CLI commands that illustrate how to provision the specific feature. Most of these tables have additional tokens that are not included in the examples. For a complete list of all CLI tables, tokens, descriptions, valid ranges, and default values, see the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide.



Note The command sequences shown in this section provide guidance on how to provision a new system. Therefore, in most cases the commands are "add" commands. If you are modifying previously-provisioned GWs, TGs, and so forth, use the "change" commands.


Provisioning Basic PacketCable and DQoS Features

This section describes how to provision the Cisco BTS 10200 Softswitch interfaces to connect to other PacketCable-based NEs, and how to select dynamic quality of service (DQoS) options. It includes the following tasks:

Provisioning CMS Parameters

Provisioning the CMS (Interfaces to the CMTS and eMTA)

Provisioning DQoS Parameters for Codec Negotiation Service

Provisioning TGCP Interfaces to TGW

Provisioning the Keepalive AUEP and ICMP Ping Options (Release 4.4.x and Later)

Provisioning CMS Parameters

This section describes how to provision DQoS functionality for the CMS logical entity on the Cisco BTS 10200 Softswitch (Call Agent).

SUMMARY STEPS

1. Enable DQoS support—change call-agent-profile.

2. Set CMS timers in Call Agent Configuration (ca-config) table (optional, if using other than the default values)—change ca-config.

3. Set the local ringback flag, differential service code point (DSCP)/type of service (TOS) parameter, and maximum MGCP datagram sizes in the ca-config table (optional, if using other than the default values)—change ca-config.


Note The token values shown in this section are examples.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

CHANGE CALL-AGENT-PROFILE

Example:

change call-agent-profile id=CA146; dqos-supp=y; description=BostonCA33


Enables DQoS support.

Tip The command is shown as change call-agent-profile ... . However, if the system responds that the call-agent-profile ID does not exist, reenter the command as add call-agent-profile.

Step 2 

CHANGE CA-CONFIG

Example:

CHANGE CA-CONFIG TYPE=DQOS-T1-TIMER;
DATATYPE=INTEGER; VALUE=250;


CHANGE CA-CONFIG TYPE=DQOS-DS-SLACK-TERM;
DATATYPE=INTEGER; VALUE=30000;


CHANGE CA-CONFIG TYPE=DQOS-GATE-TIMER;
DATATYPE=INTEGER; VALUE=3;

Specifies values other than the defaults for individual CMS timers in the ca-config table. The applicable timers are DQOS-T1-TIMER, DQOS-T5-TIMER, DQOS-T7-TIMER, DQOS-T8-TIMER, DQOS-DS-SLACK-TERM, DQOS-US-
SLACK-TERM, and DQOS-GATE-TIMER.

Tip The default values for these timers may be adequate for your specific case. In each case, you can use the show command to find out how the parameter is currently set. See the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide for parameter definitions and valid ranges.
Tip The command is shown as change ca-config ... . However, if the system responds that the parameter does not exist, reenter the command as add ca-config.

Step 3 

CHANGE CA-CONFIG

Example:

CHANGE CA-CONFIG TYPE=LOCAL-RINGBACK;
DATATYPE=BOOLEAN; VALUE=N;


CHANGE CA-CONFIG TYPE=COPS-DSCP-TOS;
DATATYPE=INTEGER; VALUE=240;


CHANGE CA-CONFIG TYPE=MAX-MGCP-DATAGRAM;
DATATYPE=INTEGER; VALUE=3900;


Specifies additional ca-config parameters that can be set to values other than the defaults.

Tip The default values for these parameters may be adequate for your specific case. In each case, you can use the show command to find out how the parameter is currently set. See the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide for parameter definitions and valid ranges.

Note The MAX-MGCP-DATAGRAM parameter specifies the maximum size of an MGCP message datagram (that may include one or more piggybacked messages) the Cisco BTS 10200 Softswitch could decode before discarding the rest of the message part. The default value of 4000 bytes is adequate for most applications, and Cisco does not recommend that you change this value unless you are deploying MGCP-based media gateways or MTAs that require larger datagram sizes.

Provisioning the CMS (Interfaces to the CMTS and eMTA)

This section describes how to provision the interfaces to the CMTS and eMTA nodes:

CMTS—The Aggregation (aggr) table defines the parameters for the connected CMTS devices. These parameters are used by the COPS adapter to establish and terminate TCP connections to the CMTS.

MTA (or eMTA)—The Cisco BTS 10200 Softswitch uses the Media Gateway Profile (mgw-profile), mgw, and termination tables to establish and terminate connections to the eMTAs. The supported MGCP variant is NCS.

The mgw-profile table provides templates for defining each type of eMTA by hardware vendor. It identifies the specifications and settings necessary for communications between the Cisco BTS 10200 Softswitch (which functions as the CMS) and each type of eMTA. A mgw-profile ID must be created in this table before entries can be added to the mgw table. Several tokens have values that can be overwritten after the Cisco BTS 10200 Softswitch (CMS) queries the eMTA for supported capabilities. If the eMTA returns a value different from the value originally provisioned in the Cisco BTS 10200 Softswitch, the returned value automatically replaces the originally provisioned value.

The mgw table holds information about each eMTA managed by the Cisco BTS 10200 Softswitch (CMS). The eMTA can be uniquely addressed by domain name, an IP address, or the TSAP address.

The termination table holds information about each endpoint in eMTAs managed by the CMS. Termination events and signals are grouped into packages, which are groupings of events and signals supported by a particular type of endpoint, such as an eMTA endpoint. One or more packages can exist for a given endpoint-type.

SUMMARY STEPS

1. Create the CMTS and enable DQoS support—add aggr.

2. Create the profile for eMTA and specify the appropriate parameters—add mgw-profile.

3. Verify that all parameters affecting eMTAs are properly populated, either by default or by the operator—show mgw-profile.

4. Modify parameters affecting eMTAs, if necessary—change mgw-profile.

5. Create the specific eMTA, associate it with the applicable CMTS, and set appropriate parameters—add mgw.

6. Add the line termination for an eMTA—add termination.

7. Bring the eMTA into service—control mgw.

8. Equip the termination and place it in service— equip/control subscriber-termination.


Note The token values shown in this section are examples.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD AGGR

Example:

add aggr id=cmts777;
tsap-addr=ADDRESS123.cisco.com;
dqos-supp=Y;

Creates the CMTS (aggregation device) and enables DQoS support.

Note The TSAP-ADDR can be a DNS or IP address. If you enter a DNS address, it must be a fully qualified domain name (FQDN).


Caution DQoS is disabled (DQOS-SUPP=N) by default. Set this value to Y to enable DQoS.

Step 2 

ADD MGW-PROFILE

Example:

add mgw-profile id=mgwprofile777; mgcp-version=MGCP-1-0; mgcp-variant=NCS-1-0; mgcp-default-pkg=LINE; mgcp-conn-id-at-gw-supp=n;

Creates the mgw-profile for this type of eMTA, and specifies values for the optional parameters.

Tip The default values for these parameters may be adequate for your specific case. In each case, you can use the show command to find out how the parameter is currently set. See the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide for parameter definitions and valid ranges.

Step 3 

SHOW MGW-PROFILE

Example:

show mgw-profile id=mgwprofile777;


Verify that the following values are present:

vendor=Cisco [or applicable vendor name]

mgcp-version=MGCP-1-0

mgcp-variant=NCS-1-0

mgcp-default-pkg=LINE

codec-neg-supp=y

pc-mptime-supp=y

mgcp-xdlcx-supp=n

domain-name-caching-supp=y

mgcp-conn-id-at-gw-supp=y

Shows the provisioned values for the parameters in the mgw-profile table.

Step 4 

CHANGE MGW-PROFILE

Example:

change mgw-profile id=mgwprofile777; mgcp-version=MGCP-1-0; mgcp-variant=NCS-1-0;


If any of the mgw-profile token values need to be changed, use the change mgw-profile command.

Step 5 

ADD MGW

Example:

add mgw id=CiscoGW50; tsap-addr=192.168.26.104; call-agent-id=CA146; mgw-profile-id=mgwprofile777; type=rgw; aggr-id=cmts777;


Creates the MGW ID for a single eMTA, and specifies values for the other required parameters.

Note Be sure to set TYPE=RGW for an eMTA.

Note You must enter the value for AGGR-ID to identify the appropriate CMTS for this eMTA.

Step 6 

ADD TERMINATION

Example:

add termination prefix=aaln/; port-start=1; port-end=2; type=LINE; mgw-id=CiscoGW50;


Creates the line termination for the eMTA, and specifies values for the required parameters.

Note For eMTA terminations, always enter TYPE=LINE.

Step 7 

CONTROL MGW


STATUS MGW

Example:

CONTROL MGW ID=CiscoGW50; TARGET-STATE=INS; MODE=FORCED;


STATUS MGW ID=CiscoGW50;


Verify that the system responds that the administrative state is in service (INS).

Brings the eMTA in service (INS state), and verifies it is INS.

Step 8 

EQUIP SUBSCRIBER-TERMINATION


CONTROL SUBSCRIBER-TERMINATION


STATUS SUBSCRIBER-TERMINATION

Example:

EQUIP SUBSCRIBER-TERMINATION ID=sub3456;


CONTROL SUBSCRIBER TERMINATION ID=sub3456; TARGET-STATE=INS; MODE=FORCED;


STATUS SUBSCRIBER TERMINATION ID=sub3456;


Verify that the system responds that the administrative state is in service (INS).

Equips the termination, places it in service (INS state), and verifies it is INS.

Provisioning DQoS Parameters for Codec Negotiation Service

The Quality of Service (qos) table is used in providing the codec negotiation service. Codec negotiation is the process the Cisco BTS 10200 Softswitch uses to find a common codec for the compression or decompression of a signal between two gateways. The Subscriber Profile (subscriber-profile) and Subscriber (subscriber) tables point to the qos table.

The following commands allow you to specify the required characteristics for these tables.

SUMMARY STEPS

1. Provision QOS parameters—add qos.

2. Assign a specific QOS to each subscriber-profile or subscriber—
add subscriber-profile; add subscriber.


Note The token values shown in this section are examples.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD QOS

Example:

add qos id=Gold1; codec-type=PCMU;


Adds a qos with the preferred codec type and other parameters.

Step 2 

ADD SUBSCRIBER-PROFILE


ADD SUBSCRIBER

Example:

add subscriber-profile id=NorthDallas; dial-plan-id=dp1; POP=BLDG222; qos-id=Gold1;


add subscriber id=Person29; dn1=800-555-0029; sub-profile-id=richardson;


add subscriber id=Person123; dn1=800-555-0123;

sub-profile-id=richardson; qos-id=Gold1;


Assigns a qos ID to each subscriber-profile and/or subscriber.

Provisioning TGCP Interfaces to TGW

This section describes how to provision the TGCP interfaces to the TGWs.


Note The mgw-profile table provides templates for defining each type of TGW by hardware vendor. It identifies the specifications and settings necessary for communications between the Cisco BTS 10200 Softswitch (which functions as the MGC) and each type of TGW. Several tokens in this table have values that can be overwritten after the Cisco BTS 10200 Softswitch (MGC) queries the TGW for supported capabilities. If the TGW returns a value different from the value originally provisioned in the Cisco BTS 10200 Softswitch, the returned value automatically replaces the originally provisioned value.


SUMMARY STEPS

1. Enable TGCP support for each type of TGW—add mgw-profile.

2. Link each TGW to a mgw-profile—add mgw.

3. Add the trunk termination for a TGW—add termination.

4. Provision QOS parameters—add qos.

5. Assign a QOS-ID to the TGW—add trunk-grp.


Note The token values shown in this section are examples.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD MGW-PROFILE

Example:

add mgw-profile id=tgwprf222; vendor=cisco; mgw-type=MGX8850; mgcp-version=MGCP-1-0; mgcp-variant=TGCP-1-0; mgcp-default-pkg=TRUNK; pc-mptime-supp=y;

Creates a mgw-profile for this type of TGW, and specifies values for required parameters.

Note For most TGWs, set PC-MPTIME-SUPP to Y. However, for a Cisco MGX8850 VISM gateway, the MP function is not available. Therefore, set the PC-MPTIME-SUPP token to N for a Cisco MGX8850 VISM gateway.

Note Be sure to set the following values for a TGW:
MGCP-VERSION=MGCP-1-0
MGCP-VARIANT=TGCP-1-0
MGCP-DEFAULT-PKG=TRUNK

Step 2 

ADD MGW

Example:

add mgw id=tgw50; tsap-addr=TGW1515.cisco.com; call-agent-id=CA146; mgw-profile-id=tgwprf222; type=tgw;


Links a specific TGW to the applicable mgw-profile.

Note Be sure to set TYPE=TGW.

Step 3 

ADD TERMINATION


Example:

add termination prefix=S0/ds1-2/; mgw-id=tgw50; port-start=1; port-end=24; type=TRUNK;


Creates trunk terminations for the TGW.

Note Be sure to set TYPE=TRUNK.

Step 4 

ADD QOS


Example:

add qos id=gold-service; lptime=20; hptime=20; codec-type=PCMU;


Adds a qos with the preferred codec type and other parameters.

Step 5 

ADD TRUNK-GRP


Example:

add trunk-grp id=101; call-agent-id=CA146; tg-type=ss7; qos-id=gold-service; mgcp-pkg-type=IT;


Assigns a qos ID to each TRUNK-GRP.

Note For trunk groups on TGCP-based TGWs (MGCP-VARIANT=TGCP-1-0 in the mgw-profile table), set the MGCP-PKG-TYPE value to IT (ISUP trunk package).

Provisioning the Keepalive AUEP and ICMP Ping Options (Release 4.4.x and Later)

This section explains how to provision the keepalive AUEP and ICMP ping options. There are two tokens to provision:

AUEP and ICMP pings can be globally disabled on the system using the mgw-monitoring-enabled token in the Call Agent (call-agent) table.

If globally enabled in the call-agent table, these pings can be selectively enabled or disabled for each mgw-profile using the keepalive-method token in the mgw-profile table. Each MGW (eMTA) is linked to a mgw-profile using the mgw table.

SUMMARY STEPS

1. Show the setting for mgw-monitoring-enabled—show call-agent.

2. If necessary, change the value of mgw-monitoring-enabled—change call-agent.

3. Show the setting for keepalive-method—show mgw-profile.

4. If necessary, change the value of keepalive-method—change mgw-profile.

5. Link individual MGWs (eMTAs) to MGW profiles—add mgw.


Note If mgw-monitoring-enabled=Y (the default value) in the call-agent table, the system checks the provisioning of the keepalive-method token in the mgw-profile table for each MGW.

However, if mgw-monitoring-enabled=N, both AUEP and ICMP ping are globally disabled, and the keepalive-method token is not checked.



Note The token values shown in this section are examples. In addition, these tables have many additional optional tokens not shown in these examples. For a complete list of all the tokens for each table, see the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

SHOW CALL-AGENT

Example:

SHOW CALL-AGENT ID=CA146;


The system responds with the current settings for the call-agent table. The default value of MGW-MONITORING-ENABLED is Y.


Show the setting for mgw-monitoring-enabled in the call-agent table.

Step 2 

CHANGE CALL-AGENT

Example:

change call-agent id=CA146; tsap-addr=sim-CA146.cisco.com; mgw-monitoring-enabled=Y;


If the current value of mgw-monitoring-enabled is N, use this command to change it to Y. (Otherwise, skip to Step 3.

Step 3 

SHOW MGW-PROFILE

Example:

show mgw-profile id=mgwprofile001;


The system responds with the current settings for the mgw-profile table.

Show the setting for keepalive-method in the mgw-profile table.

Step 4 

CHANGE MGW-PROFILE

Example:

change mgw-profile id=mgwprofile001; keepalive-method=<value (see options)>;


change mgw-profile id=mgwprofile001; keepalive-method=auep-icmp;


If necessary, change the value of keepalive-method in the mgw-profile table.

The options for keepalive-method are:

none—Disable both AUEP and ICMP ping.

auep—Enable AUEP ping but not ICMP ping (this is the default value).

auep-icmp—Enable sending of an AUEP ping followed (if AUEP is unsuccessful) with an ICMP ping.

Step 5 

ADD MGW

Example:

add mgw id=mgw_abc; mgw-profile-id=mgwprofile001;


Links an individual MGW (eMTA) to a mgw-profile.

Provisioning Security Interfaces

This section describes the PacketCable-based security interface feature and how to provision security options. The subsections are as follows:

Provisioning Parameters for Secured Media

Provisioning Security Interfaces to the MTA

Provisioning Security Interfaces to the CMTS

Provisioning Security Interfaces to the TGW

Provisioning Security Interfaces to the RKS

Provisioning IPsec Security Associations and Ciphersuite Algorithms


Note A global security parameter, IPSEC_ENABLED, must already be set in the initial configuration file (opticall.cfg) during the Cisco BTS 10200 Softswitch software installation process. This parameter enables or disables the IPsec feature on the Cisco BTS 10200 Softswitch. See the detailed requirement in the "Installing" section.


Provisioning Parameters for Secured Media

This section describes how to provision the SECURED-MEDIA-ONLY flag, which affects transmission of security parameters from the qos and ciphersuite tables when connecting a call. This parameter affects the setup of calls to unsecured MGWs.

SUMMARY STEPS

1. Show the current setting of the SECURED-MEDIA-ONLY flag—show ca-config.

2. If necessary, change the value of the secured media flag—change ca-config.

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

SHOW CA-CONFIG

Example:

SHOW CA-CONFIG TYPE=SECURED-MEDIA-ONLY;


Displays the current setting of the secured-media-only flag:

If set to Y, the Cisco BTS 10200 Softswitch forces the security parameters from the qos and ciphersuite tables to the endpoint while making the connection. This may result in call failure if either side cannot handle these parameters.

If set to N, the Cisco BTS 10200 Softswitch forces the security parameters from the qos and ciphersuite tables while making the connection to the endpoint only if both sides can handle the security parameters.

Step 2 

CHANGE CA-CONFIG

Example:

CHANGE CA-CONFIG TYPE=SECURED-MEDIA-ONLY;
DATATYPE=BOOLEAN; VALUE=Y;


If necessary, change the setting of the secured-media-only flag.


Caution Do not change this value unless specified by your network administrator. This command can affect the setup of calls to unsecured MTAs.

Provisioning Security Interfaces to the MTA

The MTA is the only device class that uses Kerberos key management. This section explains how to provision the MTA IP security (IPsec) interface, including:

Provisioning Kerberos

Provisioning IPsec policy

Enabling IPsec


Note The token values shown in this section are examples. For detailed token descriptions, see the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide.


SUMMARY STEPS

1. Provision Kerberos parameters—add ipsec-kerberos.

2. Display the rolling list of old Kerberos service keys—show ipsec-kerberos-keys (optional).

3. Add an IPsec policy for all incoming and outgoing traffic on the MTA—add ipsec-policy.

4. Enter values for additional security parameters—change mgw-profile (optional).

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD IPSEC-KERBEROS

Example:

add ipsec-kerberos krb-fqdn=cms-ca1.ciscolab.com; krb-realm=cisco-realm.com; krb-srv-key=546869732069732061206b6579206f6620 3234206368612e; srv-key-version=12345;

Provisions Kerberos parameters.

Note The KRB-FQDN must be the FQDN used on the KDC for this node.

KRB-REALM is used to create the CMS principal name.

If the krb-serv-key is changed, the srv-key-version must also be changed, and if the srv-key-version is changed, the krb-srv-key must also be changed.

For krb-srv-key and srv-key-version, each cannot already exist in the ipsec-kerberos-keys table. The system updates the ipsec-kerberos table before it updates the ipsec-kerberos-keys table.

Step 2 

SHOW IPSEC-KERBEROS-KEYS;


Displays the rolling list of old Kerberos service keys.

Note This step is optional. Use this command when you need to display the list.

Step 3 

ADD IPSEC-POLICY;

Example:

See substeps a. and b. below.

Adds an IPsec policy for all incoming and outgoing traffic on the MTA. Perform one or more of the following steps, as applicable:

Full-duplex security policy

Using FQDN

Using IP addresses

Half-duplex security policy

a.

Provisioning example using FQDNs:

Use these two commands (examples shown):

add ipsec-policy id=mta01-out; src-fqdn=cms-ca1.ciscolab.com; dest-fqdn=mta1.ciscolab.com; action=apply;

add ipsec-policy id=mta01-in; src-fqdn=mta1.ciscolab.com; dest-fqdn=cms-ca1.ciscolab.com; action=permit;



or use this one command (example shown):

add ipsec-policy id=mta01; src-fqdn=cms-ca1.ciscolab.com; dest-fqdn=mta1.ciscolab.com; action=ipsec


Provisioning example using IP addresses:

Use these two commands (examples shown):

add ipsec-policy id=mta02-out; src_ipaddr=192.168.45.211; src_ipmask=255.255.255.0; dest_ipaddr=192.168.17.222; action=apply;

add ipsec-policy id=mta02-in; src_ipaddr=192.168.45.211; src_ipmask=255.255.255.0; dest_ipaddr=192.168.17.222; action=permit;



or use this one command (example shown):

add ipsec-policy id=mta02; src_ipaddr=192.168.45.211; src_ipmask=255.255.255.0; dest_ipaddr=192.168.17.222; action=ipsec


Full-duplex security policy—When the MTA vendor applies security policy on all ports, use action=apply for outbound traffic and action=permit for inbound traffic. Alternatively, you can use a single command with action=ipsec for all outbound and inbound traffic.


Caution You must specify at least one of the following: src-fqdn, or src-ipaddr, or src-port.
You must also specify at least one of the following: dest-fqdn, or dest-ipaddr, or dest-port.

The value of the action token defines whether security is applied to outbound or inbound traffic, both, or neither. This is a mandatory token. The allowed values are:

PERMIT—Security on inbound traffic.

APPLY—Security on outbound traffic.

IPSEC—Security on both inbound and outbound traffic.

BYPASS—No security

b.

Use these two commands (examples shown):

add ipsec-policy id=mta01-out; src-fqdn=cms-ca1.ciscolab.com; dest-fqdn=mta1.ciscolab.com; action=apply;

add ipsec-policy id=mta01-in; src-fqdn=mta1.ciscolab.com; dest-fqdn=cms-ca1.ciscolab.com; action=permit; dest-port=2727;


Half-duplex security policy—When the MTA vendor applies security policy on a specific signaling port only, use action=apply for outbound traffic, and action=permit and dest-port=<destination port> for inbound traffic.

Step 4 

CHANGE MGW-PROFILE;

Example:

change mgw-profile id=cvmdqos; krb-reest-flag=[y|n]; ipsec-sa-esp-cs=[cipher suite for ESP]; ipsec-sa-lifetime=[IPsec SA expiration time]; ipsec-sa-grace-period=[expiration grace period]; ipsec-ulp-name=[IP | UDP | TCP]; ike-group=[1|2]; ike-sa-lifetime=[IKE SA expiration time]; ike-cs=[cipher suite for IKE]; ike-key=[IKE pre-shared key];


Enters values for additional security parameters.

Note This step is optional. Use this command only if you need to modify these values in your system.

Tip The default values of these security parameters are sufficient for some networks. Before making any changes, you can use the show command to determine if changes are needed to any of the default values.

Provisioning Security Interfaces to the CMTS

This section explains how to provision security interfaces to the CMTS.

SUMMARY STEPS

1. Add a security policy for the CMTS—add ipsec-policy.

2. Enables IPsec for the CMTS—change aggr.

3. Enter values for additional security parameters for this CMTS—change aggr (optional).


Note The token values shown in this section are examples.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD IPSEC-POLICY;

Example:

add ipsec-policy id=cmts01; src-fqdn=cms-ca1.ciscolab.com; dest-fqdn=cmts1.ciscolab.com; action=ipsec;


Adds a security policy for the CMTS.

Step 2 

CHANGE AGGR;

Example:

change aggr id=cmts1; tsap-addr=[DNS/IP-address]; ike-key=<IKE preshared security key>;


Enables IPsec for the CMTS.

Step 3 

CHANGE AGGR;

Example:

change aggr id=cmts1; tsap-addr=[DNS/IP-address]; ipsec-sa-esp-cs=[cipher suite for ESP]; ipsec-sa-lifetime=[IPsec SA expiration time]; ipsec-sa-grace-period=[expiration grace period]; ipsec-ulp-name=[IPsec SA upper layer protocol]; ike-group=[1|2]; ike-sa-lifetime=[IKE SA expiration time]; ike-cs=[cipher suite for IKE]; ike-key=234; description=CMTS_City1;


Enters values for additional security parameters for this CMTS.

Note This step is optional. Use this command only if you need to modify these values in your system.

Tip The default values of these security parameters are sufficient for some networks. Before making any changes, you can use the show command to determine if changes are needed to any of the default values.

Note The aggr id and tsap-addr are both required in this command.


Provisioning Security Interfaces to the TGW

This section explains how to provision security interfaces to the TGW.

SUMMARY STEPS

1. Add a security policy for the TGW—add ipsec-policy.

2. Enables IPsec for the TGW—change mgw-profile.

3. Enter values for additional security parameters for this TGW—change mgw-profile (optional).


Note The token values shown in this section are examples.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD IPSEC-POLICY;

Example:

add ipsec-policy id=tgw01; src-fqdn=cms-ca1.ciscolab.com; dest-fqdn=tgw1.ciscolab.com; action=ipsec;


Adds a security policy for the TGW.

Note You must specify at least one source (src-fqdn, or src-ipaddr, or src-port), and at least one destination (dest-fqdn, or dest-ipaddr, or dest-port).

Note You cannot specify both a SRC-FQDN and a SRC-IPADDR at the same time. You cannot specify both a DEST-FQDN and a DEST-IPADDR at the same time.

Step 2 

CHANGE MGW-PROFILE;

Example:

change mgw-profile id=tgw1; ike-key=<IKE preshared security key>;


Enables IPsec for the TGW—To enable IPsec on the TGW, change the mgw-profile entry associated with this TGW.

Note Changing this entry will enable security for all TGWs that use this profile so you may want to have a security-enabled and security-disabled profile for each vendor class.

Step 3 

CHANGE MGW-PROFILE;

Example:

change mgw-profile id=cvmdqos; krb-reest-flag=[y|n]; ipsec-sa-esp-cs=[cipher suite for ESP]; ipsec-sa-lifetime=[IPsec SA expiration time]; ipsec-sa-grace-period=[expiration grace period]; ipsec-ulp-name=[IP | UDP | TCP]; ike-group=[1|2]; ike-sa-lifetime=[IKE SA expiration time]; ike-cs=[cipher suite for IKE]; ike-key=[IKE pre-shared key];


Enters values for additional security parameters for this mgw-profile.

Note This step is optional. Use this command only if you need to modify these values in your system.

Tip The default values of these security parameters are sufficient for some networks. Before making any changes, you can use the show command to determine if changes are needed to any of the default values.

Provisioning Security Interfaces to the RKS

This section explains how to provision security interfaces to the RKS.

SUMMARY STEPS

1. Add a security policy for the RKS—add ipsec-policy.

2. Enables IPsec for the primary and secondary RKS units—change radius-profile.

3. Enter values for additional security parameters for this RKS—change radius-profile (optional).


Note The token values shown in this section are examples.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD IPSEC-POLICY;

Example:

add ipsec-policy id=rks01; src-fqdn=cms-ca1.ciscolab.com; dest-fqdn=rks1.ciscolab.com; action=ipsec;


Adds a security policy for the RKS.

Note You must specify at least one source (src-fqdn, or src-ipaddr, or src-port), and at least one destination (dest-fqdn, or dest-ipaddr, or dest-port).

Note You cannot specify both a SRC-FQDN and a SRC-IPADDR at the same time. You cannot specify both a DEST-FQDN and a DEST-IPADDR at the same time.

Step 2 

CHANGE RADIUS-PROFILE;

Example:

change radius-profile id=[primary RKS id | secondary RKS id]; tsap-addr=[ip-address | ip-address:port-number]; ike-key=<IKE preshared security key>;


Enables IPsec for the primary and secondary RKS units.

Step 3 

CHANGE RADIUS-PROFILE;

Example:

change radius-profile id=[primary RKS id | secondary RKS id]; tsap-addr=[ip-address | ip-address:port-number]; ipsec-sa-esp-cs=[cipher suite for ESP]; ipsec-sa-lifetime=[IPsec SA expiration time]; ipsec-sa-grace-period=[expiration grace period]; ipsec-ulp-name=[SA upper layer protocol]; ike-group=[1|2]; ike-sa-lifetime=[IKE SA expiration time]; ike-cs=[cipher suite for IKE];


Enters values for additional security parameters for this radius-profile.

Note This step is optional. Use this command only if you need to modify these values in your system.

Tip The default values of these security parameters are sufficient for some networks. Before making any changes, you can use the show command to determine if changes are needed to any of the default values.

Provisioning IPsec Security Associations and Ciphersuite Algorithms

This section explains how to provision the IPsec Security Associations (SAs) and the ciphersuite encryption and authentication algorithms.

The IPsec SA (ipsec-sa) table contains the IPsec SAs that are not associated with IKE or Kerberos key management.

A cipher is an algorithm that transforms data between plain text and encrypted text. A ciphersuite consists of both an encryption algorithm and a message authentication algorithm. The Ciphersuite Profile (ciphersuite-profile) and Ciphersuite (ciphersuite) tables provision the allowed ciphersuites for media security (encryption of bearer path data) between two MTAs.

SUMMARY STEPS

1. Add a security association for a device—add ipsec-sa.

2. Create a ciphersuite profile—add ciphersuite-profile.

3. Create the ciphersuite data supporting the ciphersuite profile—add ciphersuite.


Note The token values shown in this section are examples. For a complete list of tokens and detailed descriptions, see the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD IPSEC-SA;

Example:

add ipsec-sa id=cmts01; auth-algo=HMAC-SHA-1; auth-key=2069732061206b6579206f662032342063686 12e; dest=10.10.7.7; encrypt-algo=DES; encrypt-key=4bb586a120532c07; spi=-85723; src=10.10.2.2; soft-lifetime=3600; hard-lifetime=7200;


Adds a security association for a device.

Note The range of values is 1 to 8 ASCII characters. The suggested format is <device-type>NN, for example, mta01, cmts01, rks01. This token is mandatory.

Step 2 

ADD CIPHERSUITE-PROFILE;

Example:

add ciphersuite-profile id=cp1gold; description=This ID is used for QoS gold.


Creates a ciphersuite-profile.

Step 3 

ADD CIPHERSUITE;

Example:

add ciphersuite id=cp1gold; proto-type=RTP; auth-algo=RTP-MMH-4; encrypt-algo=RTP-3DES-CBC; priority=1;


add ciphersuite id=cp1gold; proto-type=RTCP; auth-algo=RTCP-HMAC-MD5-96; encrypt-algo=RTCP-AES-CBC; priority=1;


Creates the ciphersuite data supporting the ciphersuite-profile.

Provisioning Event Messages

This section explains how to provision EM functionality on the Cisco BTS 10200 Softswitch. It includes the following tasks:

Provisioning Support for EM Transmission and Storage

Provisioning the System to Generate EMs for Billing

Provisioning Media_Alive Verification for EMs

Provisioning Support for EM Transmission and Storage

The commands in the following procedure specify the required IDs for the primary and secondary RKSs, and link them with the Call Agent (CMS/MGC). They also control parameters related to the transmission of EMs to the RKS, and parameters related to storage of EMs on the CA.

The RADIUS Profile (radius-profile) table is required in PacketCable networks when using an EM-based billing system and a RADIUS-based Record Keeping Server (RKS). This table includes provisionable parameters such as primary and secondary RKS node IDs, IP address and port address, RADIUS retry intervals and retry counts.

The call-agent-profile table establishes a link between the Call Agent (CMS) and the primary and secondary RKSs.

SUMMARY STEPS

1. Create the interfaces to the primary and secondary RKS—Add radius-profile.

2. Specify parameters for storage of EM files on the CA—change ca-config.

3. Provision batch mode handling of EMs—change ca-config.

4. Set the DSCP for signaling packets on RADIUS interfaces between the CMS and RKS—change ca-config.

DETAILED STEPS


Note The token values shown in this section are examples. In addition, these tables have many additional optional tokens not shown in these examples. For a complete list of all the tokens for each table, see the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD RADIUS-PROFILE;


Example:

ADD RADIUS-PROFILE;


add radius-profile id=prirks; tsap-addr=192.168.100.100; encryption-key=abcdef1234567890; acc-rsp-timer=7;  acc-req-retransmit=4; description=primary_billing_server


add radius-profile id=secrks; tsap-addr=192.168.100.101; encryption-key=abcdef1234567890; acc-rsp-timer=6;  acc-req-retransmit=2; description=secondary_billing_server


Creates the interfaces to the primary and secondary RKS units, and sets values for various parameters.

Note The ACC-RSP-TIMER and ACC-REQ-RETRANSMIT tokens control the retransmission of EMs from the CA to the RKSs when the first attempt does not go through. ACC-RSP-TIMER controls how long the system waits before retransmitting, and ACC-REQ-RETRANSMIT controls how many retransmission attempts are made to the target RKS.

Step 2 

CHANGE CA-CONFIG;

Example:

CHANGE CA-CONFIG;


change ca-config type=retry-pri-rks-timer; datatype=integer; value=14;

change ca-config type=em-file-open-time; datatype=integer; value=900;

change ca-config type=em-file-size; datatype=integer; value=50;


Specifies how the system stores EMs in files on the CA (when loss of communication with the RKSs prevents EMs from being transmitted to the RKSs).

Note An open EM file does not close automatically when communication to the RKS is restored. The file closes automatically according to the provisioned values in EM-FILE-OPEN-TIME and EM-FILE-SIZE, whichever occurs first.

Step 3 

CHANGE CA-CONFIG;

Example:

CHANGE CA-CONFIG;


change ca-config type=batch-mode-supp; value=Y;

change ca-config type=batch-latency; value=240;


Provisions batch mode handling of EMs.

Step 4 

CHANGE CA-CONFIG;

Example:

CHANGE CA-CONFIG;


change ca-config type=RADIUS-DSCP-TOS; value=240;


Sets the DSCP for signaling packets on RADIUS interfaces between the CMS and RKS.

Provisioning the System to Generate EMs for Billing

The Cisco BTS 10200 Softswitch has the ability to provision billing support using either Call Detail Blocks (CDBs), which are assembled into Call Detail Records (CDRs) by an external billing server, or PacketCable EMs, which are transferred to an external RKS that assembles CDRs from the EMs.

The Cisco BTS 10200 Softswitch contains two PacketCable-based logical network elements, the CMS and MGC. The CMS and MGC have provisionable element IDs as described in this section. The applicable element ID is included in each EM sent from the CMS and MGC.

To provision the Cisco BTS 10200 Softswitch to generate EMs for billing, complete the following steps:

SUMMARY STEPS

1. Display the current CA profile—show call-agent-profile.

2. Modify CA profile parameters related to EM generation and RKS profiles, if necessary—change call-agent-profile.

3. Identify the CMS and MGC logical network elements, and the financial entity ID (FEID)—change call-agent-profile.

DETAILED STEPS


Note The token values shown in this section are examples. In addition, these tables have many additional optional tokens not shown in these examples. For a complete list of all the tokens for each table, see the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide.



Note The value for id shown in this section (CA146) is an example.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

show call-agent-profile;


Example:

show call-agent-profile id=CA146;


Displays the current parameters for the CA profile.

Step 2 

CHANGE CALL-AGENT-PROFILE;


ADD CALL-AGENT-PROFILE;

Example:

change call-agent-profile id=CA146; cdb-billing-supp=N; em-billing-supp=Y; pri-rks-profile-id=prirks; sec-rks-profile-id=secrks;


add call-agent-profile id=CA146; cdb-billing-supp=N; em-billing-supp=Y; pri-rks-profile-id=prirks88; sec-rks-profile-id=secrks88;


If the system response (in the display from Step 1) contains data, use the change call-agent-profile command if you want to change any of the parameter values.

If the system response (in the display from Step 1) indicates that this table does not exist, then you must create it using the add call-agent-profile command. Otherwise, the EM function is not supported and EMs will not be generated.


Caution If the call-agent-configuration table is not created, the Cisco BTS 10200 Softswitch will generate CDBs but not EMs.
EM and CDB Billing Options:

In a PacketCable network, typically EM-based billing is used and CDB-based billing is generally not required.


Caution Cisco strongly recommends that you do not set both of these tokens (EM and CDB billing support) to y. Attempting to generate both types of records simultaneously can significantly degrade system performance.

Note (Release 4.4.x) To set both tokens to y, you must also include forced=y in the command line.

RKS IDs:

The value for pri-rks-profile-id (primary RKS profile ID) must be the same as the radius-profile ID for the primary RKS, and the value for sec-rks-profile-id (secondary RKS profile ID) must be the same as the radius-profile ID for the secondary RKS.

Step 3 

CHANGE CALL-AGENT-PROFILE;


Example:

change call-agent-profile id=CA146; cms-id=12345; mgc-id=67890; feid=feid0001;


Identifies the CMS and MGC logical network elements, and the financial entity ID (FEID). The system uses these IDs when generating EMs.

Note The Cisco BTS 10200 Softswitch contains both the CMS and MGC logical entities. For PacketCable systems, the CMS-ID must be entered. If your Cisco BTS 10200 Softswitch communicates with a TGW, you must also enter the MGC-ID. The FEID value is also required for EM billing.

Note The CMS-ID and MGC-ID tokens must be provisioned to support the Communication Assistance for Law Enforcement Act (CALEA). For provisioning procedures related to CALEA support, see the Cisco BTS 10200 Softswitch Provisioning Guide.

Provisioning Media_Alive Verification for EMs

Use the Activity (activity) table to schedule and configure Media_Alive EMs. These EMs are used during longer-duration calls to verify that the media connection is still alive. For information on these operational commands, see the "Viewing Media_Alive Verification for EMs" section.


Note For an additional sample provisioning sequence, see the Cisco BTS 10200 Softswitch Provisioning Guide. For additional reference information on CLI tables and parameters, see the Cisco BTS 10200 Softswitch Command Line Interface Guide.


Operating

This section covers the operational features of the Cisco BTS 10200 Softswitch PacketCable implementation, including the following topics:

Status Command

Manual Recovery and Transfer of Stored EMs

Viewing Media_Alive Verification for EMs

EM Generation Details and Content

Measurements

Events and Alarms

Announcements

Status Command

The system supports a status command to display the operational service state of external interfaces. For example, the status aggr command displays the operational service state of the CMTS.


Note For the STATUS AGGR command, the available displayed values include INS (in service), OOS (out of service), or CONNECTING. CONNECTING state means that the Cisco BTS 10200 Softswitch is reattempting to connect to the CMTS.


Manual Recovery and Transfer of Stored EMs

This section describes how to manually transfer stored EM files from the CA to the RKS. This procedure must be used if communication to both RKS units goes down. Perform these procedures after communication is restored.

Recovering the Billing Files


Note For information on compliance to specific paragraphs of PacketCable standards and ECNs, contact your Cisco account team.


Billing data is normally transferred to the Record Keeping Server (RKS) on a real-time basis. In the unlikely event that communications with the RKS go down, alarms are raised and billing data files are written to a local drive on the Cisco BTS 10200 Softswitch (see the /opt/BTSem directory on the Call Agent (CA) that generated the Event Messages. If communications are not promptly restored, additional billing alarms of increasing severity are raised at time intervals of 1 hour (minor), 3 hours (major), and 5 hours (critical).

Event messages that are not successfully transferred to the RKS are stored on the Call Agent. The system uses the naming conventions in the PacketCable Event Messages Specification (PKT-SP-EM-I07-030815), with file names in the format PKT-EM-yyyymmddhhmmss-pri-nodeid-seq.bin, where

PKT-EM—is fixed and does not change across files

yyyymmddhhmmss—is a timestamp, where

yyyy-is the year, such as 2003

mm-is the month, from 01 through 12

hh—is the hour, from 00 through 23

mm-is the minute, from 00 through 59

ss-is the second, from 00 through 59

priority—which is always set to 1, but can change according to the PacketCable specification

CMS ID or MGC ID—depending on whether the file contains event messages generated by the CMS or the MGC function of the Call Agent

file sequence number—the CMS and MGC files are numbered independently

.bin—binary file type designation

An example of a typical event message file name would look similar to

PKT-EM-20030915103142-1-00001234-000002.bin

All billing data generated during the period of the communication outage are stored in the /opt/BTSem directory. If communication with the RKS is lost for an extended period, the available disk space on the local Softswitch drives can begin to fill up with Event Message (EM) files. The system monitors the amount of space available on the disks and raises alarms of increasing severity when the disks are 50 percent (minor), 70 percent (major) and 100 percent (critical) full.


Note There could be billing data files on both CAs, primary and secondary, depending on whether there have been any switchovers during the loss of communication with the RKS.


Cisco recommends that you monitor the available disk space on a regular basis to prevent the possible loss of billing data. If the disks should become full, the data on the disk is preserved and new EMs are discarded.


Caution Do not allow the disk to become full. If you do not transfer the billing data files to the RKS, billing data might be lost. If Event Messages are discarded, they cannot be recovered and revenue will be lost.

Sending Billing Files to the RKS via FTP

To send billing files from the Call Agent (CA) to the RKS, perform the following steps:


Step 1 On the CA, navigate to the subdirectory to which the billing data is written.

cd /opt/BTSem


Step 2 At the prompt, establish an FTP session with the RKS.

ftp <record keeping server name>


Step 3 When prompted, enter your user name and password for the RKS. The FTP prompt should appear.

Step 4 At the FTP prompt, enter bin to enable binary transfer:

bin


Step 5 On the RKS, navigate to the subdirectory to which the billing files will be written.

cd /.../.../Billing_Data


Step 6 Place the applicable billing files in the billing data subdirectory.

put <billing-filename>


Step 7 After the transfer is complete and the FTP prompt reappears, exit the FTP session.

bye


Comparing Checksums

To compare the checksums to ensure that the data was transferred correctly, perform the following steps:


Step 1 Login to the RKS, using your user name and password for that system.

Step 2 Navigate to the subdirectory to which the billing data files were written.

cd /.../.../Billing_Data


Step 3 List the files in the billing directory. The following command will list the files in reverse order by creation date.

ls -lrt


Step 4 Run a cksum on the files that were backed up.

cksum <billing-filename>


Step 5 Compare these cksum values to the corresponding cksum values on the CA.

a. If the cksum values are the same, the file transfer has completed without error.

b. If the cksum values are not the same, repeat Step 1 through Step 5.

If the cksum values are still different, contact Cisco TAC for assistance.


Viewing Media_Alive Verification for EMs

Use the activity table to schedule and configure Media_Alive EMs. These EMs are used during longer-duration calls to verify that the media connection is still alive.


Step 1 Configure Media_Alive generation according to local requirements (example shown here):

add activity id=MEDIA-ALIVE-EM; freq=6H; start-time=HH:MM;

where:

id—The value must be MEDIA-ALIVE-EM, which is a fixed system value listed in the Activity Base (activity-base) table.


Note You can view other tokens in the activity-base table by using the command:
show activity-base;
However, you cannot change any values in that table.


freq—Frequency: Number of times to schedule the specified EM Media_Alive activity.

start-time—Time of day in the format of HH:MM ranging from 00:00 to 23:59 (default is 00:00).


Note The activity table has several other tokens that support other EM Media_Alive options. For more detailed information about these options, see the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide.


Step 2 To view the MEDIA-ALIVE-EM activity enter the following command:

show activity id=MEDIA-ALIVE-EM;

Example Command Line Output:

ID=MEDIA-ALIVE-EM

FREQ=30 MINUTES

DAY_OF_MONTH=NA

DAY_OF_WEEK=NA

START_TIME=00:00

FIXED_TIME_INTERVAL=N

ENABLED=N

SO_ENABLED=N

RESTART_ENABLED=N

LAST_CHANGED=2004-10-20 16:45:30


EM Generation Details and Content

This section describes the internal processes for EM generation and the content of the EMs. These features are based on the PacketCable Event Message Specification (PKT-SP-EM-I07-030815) and a number of PacketCable ECNs.


Note For information on compliance to specific paragraphs of PacketCable standards and ECNs, contact your Cisco account team.


EM Generation Details

The event messages generated by specific call configurations are listed in Table 1. The details of what event messages are required in each call configuration along with supported services are found in the PacketCable Event Message Specification (PKT-SP-EM-I07-030815).

Table 1 Event Messages Generated by Call Configuration 

Cisco BTS 10200 Softswitch Generates Event Messages for —
Call Configuration
on-net to on-net
on-net to off-net
off-net to on-net

Originating CMS

X

X

 

Terminating CMS

X

 

X

Originating MGC

 

 

X

Terminating MGC

 

X

 


The specific event messages that can be generated by the CMS and MGC are listed in Table 2:

Table 2 Event Messages Generated by Logical Entity 

Event Message
CMS
MGC

Signaling_Start

X

X

Signaling_Stop

X

X

Interconnect_Start

 

X

Interconnect_Stop

 

X

Call_Answer

X

X

Call_Disconnect

X

X

Database_Query

X

 

Service_Instance

X

 

Service_Activation

X

 

Service_Deactivation

X

 

Media_Alive

X

X

Time_Change

X

X


The details of what event messages are required in each call configuration along with supported services are found in the PacketCable Event Message Specification (PKT-SP-EM-I07-030815). Table 3 lists the event messages for a call and the triggers that generate them (single zone scenario only) in the appropriate logical entities running in the Cisco BTS 10200 Softswitch (CMS/MGC).

Table 3 Event Message Triggers by Logical Entity 

Event Message
Originating CMS
Terminating CMS
Originating MGC
Terminating MGC

Signaling_Start

Timestamp: Receipt of NCS NTFY
Send: after translation

Prop trigger

1. Receipt of IAM
or
2. Receipt of TGCP NTFY

Receipt of Invite (prop)

Signaling_Stop

If T-CMS releases first: receipt of 250RSP to DLCX

If O-CMS releases first: before deallocating call block

If O-CMS releases first: receipt of 250RSP to DLCX

If T-CMS releases first: before deallocating call block

If T-MGC releases first: upon last of following events: 1.Receipt/Transmit RLC from/to SG 2.Receipt/transmit of Ack for TGCP DLCX 3.Receipt/transmit last msg from/to T-CMS (prop)

If O-MGC releases first: before deallocating call block

Receipt of 250OK to DLCX

Interconnect_Start

 

 

Transmit/receipt of ACM

Transmit/receipt of ACM

Interconnect_Stop

 

 

Release of PSTN bandwidth

Release of PSTN bandwidth

Call_Answer

Receipt of 200OK to Invite with call answer

Receipt of NCS NTFY for off-hook of T-MTA

1. Receipt of ANM or
2. answer ind on op.service

1. Receipt of ANM or
2. answer ind on op.service

Call_Disconnect

Transmit DLCX or
delete connection on errors

Transmit DLCX

1. Receipt of REL or 2. Transmit BYE for REL

1. Receipt of REL or 2. Disconnect ind on op. service trunk disconnect

Database_Query

Receipt of response from DB/Intelligent peripheral

Receipt of response from DB/Intelligent peripheral

 

 

Service_Instance

Operation of service

Operation of service

 

 

Service_Activation

Successful activation

Successful activation

 

 

Service_Deactivation

Successful deactivation

Successful deactivation

 

 

Media_Alive

Periodic, based on provisioned parameters

Periodic, based on provisioned parameters

Periodic, based on provisioned parameters

Periodic, based on provisioned parameters

Time_Change

When time is adjusted

When time is adjusted

When time is adjusted

When time is adjusted


Table 4 lists the PacketCable 1.0 features, the event messages generated for them, and the event that triggers the message. Some of the triggering events include the logical entities—Originating CMS (O-CMS) and Terminating CMS (T-CMS)—running in the Cisco BTS 10200 Softswitch.

Table 4 PacketCable 1.0 Features and Associated Event Messages 

PacketCable 1.0 Feature
EMs Sent in Addition to Basic Call EMs
Comments
Event Message
Trigger

1.

911 service - similar to on-net to off-net call on a unique trunk group ID.

none

 

 

2.

Other N11 services - similar to above

none

 

 

3.

Database query

 

a. Send all database queries to PSTN
on special trunk

none

 

 

 

b. Query database and route accordingly

db_query

O-CMS on receipt of response to database dip

Query types:

1=Toll Free Number Lookup

2=LNP Number Lookup

3=Calling Name Delivery Lookup


If the query is successful—that is, the query returns the calling party's name—the query type (1, 2, or 3) is included in the EM.

For types 1 and 2, the value in the EM Return_Number field contains the new called party digits.

For type 3, the value in the EM Return_Number field contains a valid string, such as "O" or "P". (See footnote). 1


If the query fails, no EM is sent.

4.

Operator service

 

a. 0- service (no digit after 0)

none

Called party # 0 is replaced by Operator Service Provider #

Only call routing

 

b. 0+ service (digits after 0, not needed in PacketCable 1.0)

 

 

Only call routing

5.

Call block service (with new call to announcement server)

service instance

O-CMS and T-CMS decide to block call

If announcement server is connected, event messages are generated for call with same BCID

6.

Call waiting

 

a. Announcement server on net

Service instance

O-CMS and T-CMS when call waiting is initiated. Second call BCID for service instance

Only two calls, one active and one on hold is required. Each half call generates EM. Half call for on-net announcement server for call waiting tone need not generate EM.

A calls B, C calls A (CfiA AfiB) BCID1 for A(O), other leg BCID2
BCID2 for B(T), other leg BCID1
BCID3 for C(O), other leg BCID4
BCID4 for A(T), other leg BCID3

BCID4 for CW service instance, related BCID = BCID1

 

b. Announcement server on PSTN

not supported

 

 

7.

Call forwarding

Service instance

CMS (O/T) when forwarded call leg is initiated

A calls B, B forwards to C. (AfiBfiC)
BCID1 for A(O), other leg BCID2
BCID2 for B(T), other leg BCID1
BCID3 for B(O), other leg BCID4
BCID4 for C(T), other leg BCID3
BCID3 for CFW service instance, related BCID=BCID2

8.

Return call (with caller ID privacy restriction)

CMS-CMS signaling is not supported in this release.

 

a. Announcement server on net

service instance

O-CMS on feature initiation

 

 

b. Announcement server on PSTN

not supported

 

 

9.

Repeat call (*66)

CMS-CMS signaling is not supported in this release.

 

a. Announcement server on net

service instance

Repeat call is initiated

Separate BCID for service instance

 

b. Announcement server on PSTN

not supported

 

 

10.

Voice mail (voice mail server on off-net)

none

   
 

Deposit & retrieval: similar to on-net to off-net call

none

 

 

11.

Message waiting indicator

none

 

No event messages for message waiting.

1 "O" = Name is out of area, unknown, or not available. "P" = Name presentation is restricted.


EM Content

The following event messages for a call contain the attributes listed, and are based on the four logical entities—Originating CMS (O-CMS), Terminating CMS (T-CMS), Originating MGC (O-MGC), and Terminating MGC (T-MGC)—running in the Cisco BTS 10200 Softswitch.

Signaling Start
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call
 

Direction Indicator

X

X

X

X

MTA endpoint name

originating

terminating

name of endpoint (EP) in MGW

name of endpoint (EP) in MGW

Calling party number

X

X

X

X

Called party number

X

X

X

X

Routing number

X

X

X

X

Location routing number

X

X

X

X

CIC

 

 

X

X

Trunk Group ID

 

 

X

X


Signaling Stop
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call
 

BCID of T-CMS or T-MGC

X

 

X

 

BCID of O-CMS or O-MGC

 

X

 

X

FEID of T-CMS or T-MGC

X

 

X

 

FEID of O-CMS or O-MGC

 

X

 

X


Interconnect Start
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call
 

Routing number

 

 

X

X

CIC

 

 

X

X

Trunk Group ID

 

 

X

X


Interconnect Stop
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call
 

CIC

 

 

X

X

Trunk Group ID

 

 

X

X


Call Answer
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call
 

Charge Number

X

X

X

X

BCID of T-CMS or T-MGC

X

 

X

 

FEID of T-CMS or T-MGC

X

 

X

 

BCID of O-CMS or O-MGC

 

X

 

X

FEID of O-CMS or O-MGC

 

X

 

X


Call Disconnect
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call
 

Call Termination Cause

X

X

X

X


Service Instance
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call

 

Service Name (plus specified attributes in the table below)

X

X

 

 



Note These are the only services supported in the PacketCable 1.0 Specification. The Cisco BTS 10200 Softswitch supports many other features; however, it does not send event messages for those features to a standard RKS because the feature codes for those features have not yet been defined by PacketCable.


Service Specific Attributes
Call Forward
Call Waiting
Repeat Call
Return Call
Call Block
Three-Way Call

Related BCID

X

X

 

 

 

X

Charge Number

X

X

X

X

 

X

1st Call Calling Party #

 

X

 

 

 

 

2nd Call Calling Party #

 

X

 

 

 

 

Called Party Number

 

X

 

 

 

 

Routing Number

 

 

X

X

 

 

Calling Party Number

 

 

X

X

 

 

Termination Cause

 

 

 

 

X

 

Service Activation
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call

 

Service Name (plus specified attributes in the table below)

X

X

 

 


Service Specific Attributes
Call Forward
Call Waiting
Call Block
Customer Originated Trace

Charge Number

X

X

X

X

Calling Party Number

X

X

X

X

Forwarded Number

X

 

 

 

Service Deactivation
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call

 

Service Name (plus specified attributes in the table below)

X

X

 

 


Service Specific Attributes
Call Forward
Call Waiting
Call Block

Charge Number

X

X

X

Calling Party Number

X

X

X


Database Query
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call
 

Database ID

X

X

 

 

Query Type

X

X

 

 

Called Party Number

X

X

 

 

Returned Number

X

X

 

 


Activity
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call
 

Media Alive

X

X

X

X


Time Change
Attribute
O-CMS
 
T-CMS
 
O-MGC
off-net to on-net call
T-MGC
on-net to off-net
call
 

Time Adjustment

X

X

X

X


Measurements

There are a number of traffic measurements applicable to the PacketCable implementation. For detailed descriptions see the Measurements section in the Cisco BTS 10200 Softswitch Operations Guide.

Creating Reports and Displays of Measurements

This section provides an overview of how to create reports and displays of measurements. It uses the DQoS feature as an example.


Note Additional details about measurement provisioning, reporting, and display commands for all features can be found in the Cisco BTS 10200 Softswitch Operations Guide and the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide.


To create a report file of the DQoS counters for all time intervals in the period starting and ending at specific times, enter the following command. The system will prepend the file with the string "Tm_" and write the file to the /opt/ems/report directory on the active EMS.

report measurement-dqos-summary; start-time=[start-time]; end-time=[end-time]; 
aggr-id=[ID of the aggregation router (CMTS) for which data should be reported]; 
output=[desired file name for the report]; output-type=[CSV | XML]

where:

start-time and end-time have a format of yyyy-mm-dd hh:mm:ss

CSV = comma-separated value


Note Time intervals can be every 5, 15 minutes, 30 minutes, or 60 minutes. This is provisionable in another command, change measurement-prov, as described later in this section.


Use any of the following commands to display DQoS counters on your monitor.


To display DQoS counters for all time intervals in the past 48 hours for all CMTS IDs, enter the following command.

report measurement-dqos-summary; interval=ALL;


To display DQoS counters tracked at every interval in the period starting at a specific start-time and for all aggregation IDs, enter the following command.

report measurement-dqos-summary; start-time=[start-time];
(start-time has a format of yyyy-mm-dd hh:mm:ss, and the end-time defaults to 
the most recent interval)

To display DQoS counters for the most recent time interval for all aggregation IDs, enter the following command.

report measurement-dqos-summary;
(start-time and end-time both default to the most recent interval)

Example:

CLI>report measurement-dqos-summary

Reply : Request was successful.

TIMESTAMP       20020310184428

DQOS_GATESET_ATTMP       10

DQOS_GATESET_SUCC           9

DQOS_GATE_COMMIT            9

Example using display token to specify desired counters (separated by commas):

CLI>report measurement-dqos-summary; display=DQOS_GATESET_ATTMP,DQOS_GATE_COMMIT;

Reply : Request was successful.

TIMESTAMP 20020310184428

DQOS_GATESET_ATTMP 10

DQOS_GATE_COMMIT            9

To manage the collection of DQoS measurements, use the following commands.

To display the current provisioning settings of DQoS measurements (enabled or disabled status), enter the following command.

show measurement-prov type=DQOS;

To change the current provisioning settings of DQoS measurements (enabled or disabled status) and/or the time interval (5, 15 [default], 30 or 60 minutes), enter the following command.

change measurement-prov type=dqos; enable=yes; time-interval=30;

Measurements for the DQoS Feature on COPS Interface

The following DQoS measurements are provided to support the COPS interface.


Tip The Cisco BTS 10200 Softswitch tracks and reports measurements separately for each of the CMTS units (aggregation routers) it supports.


DQOS_GATESET_ATTMP—The number of DQOS GATE-SET attempts of all types on the reporting CMTS.

DQOS_GATESET_SUCC—The number of successful DQOS GATE-SET attempts of all types on the reporting CMTS.

DQOS_GATE_COMMIT—The number of successfully committed DQOS gates of all types on the reporting CMTS.

Measurements for the EM Feature

The following operational measurement counts and/or statistics are supplied for the EM feature:

BILLING_EM_ACKED—The number of EMs acknowledged by the RKS.

BILLING_EM_LOGGED—The number of EMs written to disk but not sent to any RKS.

BILLING_EM_RETRANS—The number of EMs that were transmitted to an alternate RKS due to the lack of a response from a previously-tried RKS, excluding retries. The counter is incremented when an EM is first sent to an alternate RKS. Any retries that occur at the RADIUS stack level (as provisioned in the radius-profile table) are not included in this count.

Use the following CLI command to retrieve these measurements:

report measurement-em-summary

A typical system response is as follows:

CLI>report measurement-em-summary

TIMESTAMP

CALL_AGENT_ID

CONDITION

BILLING_EM_ACKED

BILLING_EM_LOGGED

BILLING_EM_RETRANS

2003-07-10 16:15:00

CA146

Normal

2

3

3

Reply : Success: Entry 192 of 192 returned.

CLI>


Events and Alarms

This section lists the events and alarms applicable to the PacketCable implementation, including:

Events and Alarms Specific to PacketCable-Based Network Elements

Events and Alarms for the EM Feature

Events and Alarms for the Security Interface Feature


Note This section lists only the events and alarms that are specific to the PacketCable-based implementation, and includes only the name and description of each alarm. Detailed descriptions of all events and alarms, and recommended corrective actions, are presented in the Cisco BTS 10200 Softswitch Operations, Maintenance, and Troubleshooting Guide.


Events and Alarms Specific to PacketCable-Based Network Elements

The following events and alarms can be generated in response to processing problems or network connection issues with PacketCable-based network elements.

CALL PROCESSING Event #15—CMTS ER ID Not found in MGW table (INFO)

SIGNALING Alarm #103—AGGR Connection Down (MAJOR)

SIGNALING Event #104—AGGR Unable To Establish Connection (INFO)

SIGNALING Event #105—AGGR GATE-SET Failed (INFO)

SIGNALING Alarm #106—ESA BTS DF Connection Down (MINOR)

Events and Alarms for the EM Feature

The following alarms and events can be generated by the EM feature.

BILLING Alarm #38—EM log file access error (MAJOR)

BILLING Alarm #39—RADIUS accounting receive failure (MINOR)

BILLING Alarm #40—EM encode failure (MINOR)

BILLING Alarm #41—Message content error (MINOR)

BILLING Event #42—Error reading provisioned data-using default (WARNING)

BILLING Event #44—RKS switch occurred (INFO)

BILLING Event #45—Event Message log file opened (INFO)

BILLING Event #46—Event Message log file closed (INFO)

BILLING Alarm #47—RKS unreachable for 1hr (MINOR)

BILLING Alarm #48—RKS unreachable for 3 hours (MAJOR)

BILLING Alarm #49—RKS unreachable for 5 hours (CRITICAL)

BILLING Alarm #53—Event Message disk space 50 percent full (MINOR)

BILLING Alarm #54—Event Message disk space 70 percent full (MAJOR)

BILLING Alarm #55—Event Message disk space 100 percent full (CRITICAL)

Events and Alarms for the Security Interface Feature

The following events and alarms can be generated in response to PacketCable-related security signaling conditions;

SECURITY Alarm #3—IPsec connection down (MAJOR)

SECURITY Event #4—IPsec MTA Key Establish Error (WARNING)

SECURITY Event #5—IPsec outgoing SA not found (WARNING)

Announcements


Note The Cisco BTS 10200 Softswitch supports a full range of announcements. However, there are no announcements specific to the PacketCable protocol implementation. For details on the announcement files and announcement provisioning, see the Announcements section in the Cisco BTS 10200 Softswitch Provisioning Guide.


References

Related Documents

Related Topic
Document Title

Overview of current release

Cisco BTS 10200 Softswitch Release Notes

Technical description

Cisco BTS 10200 Softswitch System Description

Provisioning procedures

Cisco BTS 10200 Softswitch Provisioning Guide

Provisioning commands reference

Cisco BTS 10200 Softswitch Command Line Interface Reference Guide


Industry Standards

Standards
Title

IETF RFC 2748

The COPS (Common Open Policy Service) Protocol, January 2000.

PKT-SP-CODEC-I04-021018

PacketCable Audio/Video Codecs Specification, October 18, 2002.

PKT-SP-DQOS-I07-030815

PacketCable Dynamic Quality of Service Specification, August 15, 2003.

PKT-SP-MGCP-I08-030728

PacketCable Network-Based Call Signaling Protocol Specification, July 28, 2003.

PKT-SP-TGCP-I05-030728

PacketCable PSTN Gateway Call Signaling Protocol Specification, July 28, 2003.

PKT-SP-EM-I07-030815

PacketCable Event Message Specification, August 15, 2003.

PKT-SP-SEC-I09-030728

PacketCable Security Specification, July 28, 2003.

PKT-SP-ESP-I01-991229

PacketCable Electronic Surveillance Specification, December 29, 1999.



Note For information on compliance to specific paragraphs of PacketCable standards and ECNs, contact your Cisco account team.


Copyright © 2005 Cisco Systems, Inc. All rights reserved.