Guest

Cisco BTS 10200 Softswitch

Release Notes for Release 5.0.x

Table Of Contents

Cisco BTS 10200 Softswitch Release Notes for Release 5.0.x

Contents

Before You Begin

System Requirements

Hardware Requirements

Interface Options

Optional Component (Hardware and Software)

Ancillary Hardware

Cisco ITP Signaling Gateways

Software Requirements

Definition of Major, Point, and Maintenance Releases

Release Naming Conventions

Network Time Protocol Software

Optional Software

Component Interoperability

Table Sizes

Operator Access

Installation Notes

Upgrade Procedures

Upgrades and SIP Session Timers

Caveats

Bug Toolkit

New Features and Enhancements for Release 5.0, Maintenance Release 2 (5.0.3)

Multiline Variety Package

IDX Soft Limits Enforcement

CMTS Discovery Using the Static Subnet Table Enhancements

Multiple EMS Spindles

PacketCable CMS Subscriber Provisioning with SOAP/XML

CALEA Support for MLHG

CALEA Support for SIP Triggers

Ring Tone Mapping with SIP Triggers

Call Disposition—Delineate Blocked Calls from Incomplete Calls

New Features and Enhancements for Release 5.0, Maintenance Release 1 (5.0.2)

SIP Triggers for SIP Endpoints

SIP Server Groups

CORBA Session Manageability

Seasonal Suspend

SIP Name Dialing

Disable Platform Shared Memory Replication

Aggregation ID Subnet

CMTS Discovery Using the Static Subnet Table

Bulk Data Export

Subscriber ID Parameter and DQoS Measurement Counters Support

ENUM Application

Own Calling Number Announcement Enhancement

Account Code Collection Enhancement

Terminal Make Busy and Group Make Busy

Database Table Size Enhancement

Switchover Data Mismatch Deferror Prevention

Retry After Period Enhancement

New Features for Release 5.0

Documentation for Release 5.0

Telephony Features

SIP Triggers

Own Calling Number Announcement

Multiple Directory Numbers

911 Overflow to Announcement

On-Net Routing and LNP for Inter-CMS Routing

CNAM Capability on a Trunk Group

Reception/Processing of DCS-LAES SIP Header

SIP Response Code 302

Limitations

OSPS Services over SIP Between BTS Nodes

911 Ringback over SIP Between BTS Nodes

BLV and EI over SIP Between BTS Nodes

IP Transfer Point Non-Stop Operation Mode

SIP-Based Endpoints Behind Cable Modem

Separation of CMS and MGC Architecture—Inter-CMS Routing

CALEA Interaction with SIP Endpoints

CALEA Interaction with SIP Triggers

SIP REFER and SIP INVITE with Replaces

PacketCable CALEA/ES I04 Compliance

Multi-Lingual Support for IVR and Announcement Services

Casual Dial Enhancement

Dial Around Indicator in SIP

MWI Manipulation through CLI

Non-IVR Activation and Deactivation of SCF, SCR, SCA, and DRCW

ISDN Backhaul Using IUA and SCTP

MGCP Asynchronous DNS Lookup

Extended Voice Quality Metrics Reporting for MGCP

Internal Secondary Authoritative DNS

Call Tracer

Cluster Routing

Emergency 911 Trunk Connection Loss Alarm

Temporary Disconnect

DTMF Relay Call Agent Controlled Mode

PacketCable Multimedia QoS Enhancements

Fax, Modem, and TDD Handling Enhancements

QoS Gate Audit

Operational Features

XML Over SOAP

Ability To Perform Full System Backup With Reduced Duration In Simplex Mode

CDB File Naming Convention

SUN 1280 (12 CPUs)

Enhanced Software Upgrade

Broadband Telephony Services Status

Security Advisory Due to Default User Names and Passwords

200K Subscriber DB Soft Limit

Transaction Throttling Capability

SNMP Access to Current Alarms

Core File Monitor

Tabular Display of CPI/CPM Data

Configurable Default Values in Subscriber Provisioning

Overload Control

Detecting Overload

Computing MCL

Reducing Overload

Slowing Overload Reduction

Call Processing Measurements

Service Interaction Manager Measurements

Traffic Measurements Monitor Counters

Miscellaneous Measurements

Modified H323-GW Table

Modified H323-TG-PROFILE Table

Pre-Manual Switchover Integrity Diagnostic Utility

MGCP Asynchronous DNS Lookup

Automatic Restart

LERG Support in OAMP

Other Enhancements

MGCP-Based Enhancements

CALEA Enhancements

Event Management Enhancements

Alarm Subsystem Enhancements and Redesign

Report Alarm Feature

Event Message Enhancements

EM Generation Details

North American Numbering Plan Administration (NANPA) Enhancements

LNP Event and Measurement Enhancements

Call Processing Measurements

AIN Service Measurements

Call Processing Events and Alarms

Modified DN2SUBSCRIBER Table

Other Features

Changes from Previous Releases

Billing Features

Additional QoS Parameters in the Billing Records

Billing Timer Resolution in Milliseconds

New Documentation

New and Updated Documentation for Release 5.0

Cisco Field Notices

Obtaining Documentation

World Wide Web

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone


Cisco BTS 10200 Softswitch Release Notes for Release 5.0.x


Revised: October 21, 2008, OL-10355-04

The Cisco BTS 10200 Softswitch is a class-independent software switch (softswitch) that provides next-generation integrated voice and data switching solutions for packet networks.

This document describes new features and enhancements provided in the initial Release 5.0, as well as Maintenance Release 1 (MR1) and Maintenance Release 2 (MR2). The new features and enhancements are for PacketCable telephony and operational tools and functionality.

For an overview of the components, functions and signaling protocols supported by the Cisco BTS 10200 Softswitch, see the Cisco BTS 10200 Softswitch System Description.

For descriptions of Release 5.0 network features, subscriber features, class of service (COS) functions, outgoing call barring (OCB), feature interactions, and interactive voice response (IVR) features, see the Cisco BTS 10200 Softswitch Network and Subscriber Feature Descriptions.

Contents

These release notes for the Cisco BTS 10200 Softswitch describe the enhancements and new features provided in Release 5.0 FCS (900-05.01.V00), MR1 (900-05.02.V00), MR1.1 (900-05.00.02.V05), and MR2 (900-05.00.03.V00).

Each Cisco BTS 10200 Softswitch release can include a series of maintenance Vxx releases following the initial release. The release notes for the Vxx releases are updated only if they contain new information about the release.

This document includes the following sections:

Before You Begin

System Requirements

Hardware Requirements

Software Requirements

Component Interoperability

Installation Notes

Upgrade Procedures

Bug Toolkit

New Features and Enhancements for Release 5.0, Maintenance Release 2 (5.0.3)

New Features and Enhancements for Release 5.0, Maintenance Release 1 (5.0.2)

New Features for Release 5.0

Cisco Field Notices

Obtaining Documentation

Obtaining Technical Assistance

These release notes are updated periodically on an as needed basis and contain important operational information.

Before You Begin


Caution All customers must be operating on the Sun Solaris 10 06/06 operating system (OS) prior to upgrading to Release 5.0, MR1 (5.0.2) or MR2 (5.0.3). Detailed information on installing and upgrading to Solaris 10 06/06 OS can be accessed at: http://www.cisco.com/en/US/products/hw/vcallcon/ps531/prod_installation_guides_list.html.


Note Beginning with Release 5.0 MR1, SUP functionality is disabled by default. If you require SUP functionality be enabled by default, contact Cisco TAC (http://www.cisco.com/tac) to obtain the necessary method of procedure (MOP).


System Requirements

This section describes the Cisco BTS 10200 Softswitch supported hardware platforms, their supported options and configurations, and the supported software releases.

Multiple hardware options are available. Service providers should consult with their Cisco account team and choose the option that best suits their network applications and traffic levels. For more information about the hardware options, refer to Table 1-1.

The physical plant requirements for installation of the Cisco BTS 10200 Softswitch are documented in the Cisco BTS 10200 Softswitch Site Preparation and Network Communications Requirements.

The Cisco BTS 10200 Softswitch requires the following equipment:

Call Agent/Feature Server (CA/FS)—Two hardware platforms for redundant operation.

Element Management System/Bulk Data Management System (EMS/BDMS) server— Two hardware platforms for redundant operation. The EMS minimum requirements for the Release 5.0 medium configuration is 8 GB.

Two Ethernet switches.


Note Both AC and DC systems require two redundant feeds. We highly recommend that uninterruptable power supplies be provided for both AC and DC systems. For information on the voltage required, refer the Sun Microsystems Web site.



Note The Cisco Technical Assistance Center (TAC) only supports Cisco software running on Cisco-approved hardware configurations. The software is not supported on any other hardware.

Sun Microsystems hardware can be ordered directly from the vendor or a Sun value added reseller; however, Cisco TAC does not support hardware or operating systems purchased directly from Sun or from any other vendor. Hardware support contracts should be purchased from Sun or the Sun value added reseller.


Hardware Requirements

The Cisco BTS 10200 Softswitch is available only in duplex (continuous-service) configurations. Determine if you need an AC or DC system, and if you want the hardware in a cabinet or ready to mount in a customer rack.

Table 1-1 lists the hardware requirements for the Cisco BTS 10200 Softswitch Call Agent (CA), Element Management System (EMS), and Feature Server (FS) platforms.


Caution Before choosing a hardware configuration, consult with your Cisco representative to determine the hardware that will give you the best results based on your network configuration, proposed traffic, and desired call processing power.

The minimum required memory for Release 5.0.x is 8 GB.

For best results, Cisco recommends using the hardware and memory options listed in Table 1-1.

Table 1-1 Host Hardware Requirements

Hardware Platforms
Processors
Required Memory
Disk Size

Sun Fire V240

2 x 1280

8 GB

2 x 73 GB

Sun Netra 240

2 x 1280

8 GB

2 x 73 GB

Sun Fire V245

2 x 1500

16 GB

4 x 73 GB

Sun Fire V440

4 x 1280

8 GB

4 x 73 GB

Sun Netra 440

4 x 1280

8 GB

4 x 73 GB

Sun Fire V445

4 x 1593

16 GB

2 x 73 GB

Sun Netra 1280

4 x 1200

8 GB

2 x 73 GB

Sun Netra 1280

8 x 1200

16 GB

2 x 73 GB

Sun Netra 1280

12 x 1200

24 GB

2 x 73 GB

Sun Fire V1280

4 x 1280

8 GB

4 x 73 GB

Sun Fire V1280

8 x 1200

16 GB

2 x 73 GB

Sun Fire V1280

12 x 1200

24 GB

4 x 73 GB

Sun Netra 1290

8 x 1500

32 GB

2 x 146 GB


Interface Options

The Cisco BTS 10200 Softswitch interface configurations are documented in the Cisco BTS 10200 Softswitch Cabling, VLAN, and IRDP Procedures.

In Release 5.0.x, the Call Agent (CA) requires four physical interfaces, and the Element Management System (EMS) requires two physical interfaces. If ordering your own hardware, make sure to purchase an adequate number of interfaces.


Note In Release 5.0.x, the Cisco BTS 10200 system must use the 4/2 configuration.


Optional Component (Hardware and Software)

The HTTP feature server (HTTP-FS) is an optional component of the Cisco BTS 10200 Softswitch that enables users to configure user-parameters for certain applicable Cisco BTS 10200 features. The feature server performs ASCII text-based (rather than tones) queries to a CMXML-aware (v3.0 and above) SIP client.

For example, with a CMXML-aware Cisco 7960 IP phone, users can configure the Call Forwarding Unconditional (CFU) forwarding number using a text-based menu displayed on the phone's LCD panel.


Note Even though the LCD is capable of displaying graphical content, the HTTP-FS uses only text-based menus.


The HTTP-FS comprises two subcomponents: the GUI feature server (GUI-FS) and the Mini-Browser Adapter (MBA). To use the HTTP-FS, you must install the GUI-FS software package, which is part of the Feature Server for POTS/Tandem/Centrex (FSPTC). Install the FSPTC if not already installed.

Requirements for HTTP-FS

The Sun Fire V240 hardware and Solaris 8 are required to use the HTTP-FS. Load Solaris 8, and then install the MBA software package.


Note The software for both the GUI-FS and the MBA are included in the software supplied with your Cisco BTS 10200 Softswitch.


Ancillary Hardware

If you are using reference sale hardware, the following pieces of ancillary hardware are required for use with the Cisco BTS 10200 Softswitch.

For AC Systems

You need two AC system switch routers configured as listed in Table 1-2.

Table 1-2 AC Systems

Part Number
Description

WS-C2950M-XL-EN

Cisco Catalyst 2950m xl AC 10/100 Autosensing Fast Ethernet Switch


For DC Systems

You need two DC system switch routers configured as listed in Table 1-3.

Table 1-3 DC Systems 

Part Number
Description

WS-C2950M-XL-EN-DC

Cisco Catalyst 2950m xl DC 10/100 Autosensing Fast Ethernet Switch

WS-C2970G-24TS-E-DC

Cisco Catalyst 2970 x1 DC 10/100 Autosensing Fast Ethernet Switch


For All Systems

You need your own terminal server that allows for console login.

Cisco ITP Signaling Gateways

The Cisco IP Transfer Point (ITP) is required for SS7 interconnectivity. ITP is a comprehensive product for transporting Signaling System 7 (SS7) traffic over traditional time-division multiplexing (TDM) networks or advanced SS7-over-IP (SS7oIP) networks. You need Cisco ITP Signaling Gateways to provide SS7 interconnectivity for the Cisco BTS 10200 Softswitch in Release 5.0.x.


Note If using SS7 with Release 5.0, you must purchase ITP equipment as described here.


The Cisco IP Transfer Point is implemented on the Cisco 2600XM Series Router (2651XM), the Cisco 7301 Router, and the Cisco 7500 Series Router (7507, 7513). All hardware models function similarly by performing MTP3 routing over SS7 TDM links or over an IP (or dual IP) network.

The Cisco ITP 2651, 7301, and 7507 Signaling Gateways are carrier class routers with a transparent SS7oIP convergence solution. The 2651XM offers 2 or 4 SS7 links, the 73xx supports up to 80 SS7 links, and the 7507 provides from 32 to 256+ SS7 links.


Note When running ITP with Cisco BTS 10200, you might encounter an "Unrecognized Parameter" error message. The message appears because the Cisco BTS 10200 supports an optical SCTP feature that is not supported on the ITP, but it does not affect calls or performance.

Because the Cisco BTS 10200 and ITP both handle SS7 traffic using Sigtran protocols, they must be fully compatible in the version of the SCTP used.


Software Requirements

You need the Cisco BTS 10200 Softswitch Release 5.0 (900-05.00.00.Vxx) software in order to run the Cisco BTS 10200 Softswitch on the hardware platforms.

Definition of Major, Point, and Maintenance Releases

The following section describes the differences between major, point and maintenance releases.

Major Release

A major software release has significant new features, enhancements, architectural changes, and/or defect fixes. The major release number increments with each new version, and numbers cannot be skipped. This release is based on a previous main release and receives defect fixes synced from previous Main releases throughout the life of this release.

Point Release

A point software release has only a few new features of limited scope, enhancements and/or defect fixes. The point release number increments as content is added, and numbers can be non-sequential (skipped). This release is based on a previous major or minor release and receives defect fixes synced from previous major or minor releases throughout the life of this release.

Maintenance Release

A maintenance software release has defect fixes that address specific problems. The maintenance release number increments as content is added, and numbers can be non-sequential (skipped).

Release Naming Conventions

The Cisco BTS 10200 product release version numbering is defined as either:

Cisco BTS 10200 uu.ww.xx.yzz Pxx (for example, in the Release Notes)

900-uu.ww.xx.yzz Pxx (as a part number on a CD)

where:

uu is the (major) release ID (0-99)—for example, 900-03.ww.xx.yzz

ww is a point (minor) release (within a major) (0-99)—for example, 900-03.05.xx.yzz

xx is the maintenance package number (within a point) (0-99)—for example, 900-03.05.03.yzz

y is the Software State, such that—for example, 900-03.05.03V00

D = Development load

I = Integration load

Q = System test load

F = Field verification ready

V = Verified (specified for externally available)

When Pxx is at the end of the release numbering, a patch has been applied. P is the patch, and xx is the patch numbering.

Some naming convention examples are:

900-04.05.00.V01

900-04.05.01.V00

900-05.00.00.V00

900-05.00.02.V00

Network Time Protocol Software


Note Cisco BTS 10200 automatically installs and runs the Network Time Protocol (NTP) time synchronization software. However, you must specify which NTP servers to use with your installation, and you must use NTP servers that are rated STA 3 or better. For information on how to configure the NTP servers, refer to the Release 5.0 installation procedure.


NTP software is installed with Sun Solaris. Be sure to configure your Cisco BTS 10200 Softswitch to use NTP or the equivalent time synchronization software.


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 can cause the system to have serious problems. Allow the Solaris OS to obtain the time automatically through NTP services.

Optional Software

The following optional software can also be used with Cisco BTS 10200 Softswitch Release 5.0.

Cisco Extensible Provisioning Object Manager

You can use the Cisco Extensible Provisioning Object Manager (EPOM) Release 5.0 software as a provisioning tool for Cisco BTS 10200 Softswitch Release 5.0.x. For information on new EPOM features, refer to the Cisco BTS 10200 Softswitch EPOM Release Notes.


Note EPOM 5.0 is the only version intended to work with Cisco BTS 10200 Release 5.0.x


EPOM requires its own host server. For more information, refer to the Cisco EPOM Getting Started Guide.

CORBA and OpenORB

The CORBA Adapter (CAD) interface is an object-oriented provisioning tool for the BTS 10200 that parallels the BTS 10200 CLI adapter in capability.

The CAD uses the OpenORB 1.4 interface to develop and deploy distributed object-based applications, as defined in the CORBA specification 2.4.2. OpenORB is a third party software package that leverages the Internet Inter-ORB Protocol (IIOP) using either the Transmission Control Protocol or the User Datagram Protocol (UDP) for connections.

For detailed information on CORBA and OpenORB, refer to the Cisco BTS 10200 Softswitch CORBA Adapter Interface Specification Programmer Guide.

SOAP and XML

The SOAP adapter provides a machine-to-machine interface (MMI) over Simple Object Access Protocol (SOAP).

The goal of the SOAP interface is to provide a provisioning method for the Cisco BTS 10200 Softswitch product that parallels the Command Line Interface (CLI) adapter in capabilities. SOAP provides an abstraction of the Cisco BTS 10200 Softswitch in a consistent, object-oriented model.

The SOAP adapter uses the Tomcat AXIS version 1.4 package to develop and deploy the SOAP application. AXIS 1.4 is a third-party freeware provided as part of the BTS 10200 Tomcat package.

The XML interface is abstracted by SOAP itself. The Tomcat package uses either the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP) for connections. Narrowing on the NameService will also produce the BTS10200 objects. Narrowing is covered in great detail in the coding examples in the Cisco BTS 10200 Softswitch SDK package. This is bundled with the Cisco BTS 10200 Softswitch application.

For detailed information on SOAP and XML, refer to the Cisco BTS 10200 Softswitch SOAP Adapter Interface Specification Programmer Guide.

Component Interoperability

Table 1-4 lists the peripheral platforms, functions, and software loads that have been used in system testing for interoperability with the BTS 10200 Release 5.0.x software. Earlier or later releases of platform software might be interoperable, and it might be possible to use other functions on these platforms. This list certifies only that the required interoperation of these platforms, the functions listed, and the protocols listed has been successfully tested with the BTS 10200.

Table 1-4 Component Interoperability Matrix 

Platform(s) Tested
Function(s) Tested
Protocol(s) Tested
Load(s) Tested

ThinkEngine Networks 500X and 4000X

Announcement Server

MGCP 1.0

3.0

IP Unity Harmony 6000

Announcement Server

MGCP 1.0

3.1.19

IP Unity Harmony 6000

Privacy Director

SIP RFC3261

3.1

IP Unity Harmony 6000

Voicemail Server

SIP RFC3261

3.1

Cisco IAD 242x

Residential/Business Gateway

MGCP 1.0

12.3(21)

Cisco IAD 243x

Residential/Business Gateway

MGCP 1.0

12.4(4)T5

Cisco Cat 3550

Ethernet Switch

 

121-22.EA6

Cisco Cat 2950

Ethernet Switch

 

121-22.EA6

Cisco MGX 8850 VISM

Trunking Gateway

MGCP 1.0, TGCP

3.53.30.203

Cisco MGX VXSM

Trunking Gateway

MGCP 1.0, TGCP

5.3.10.201-P2

Cisco AS5300

Trunking Gateway1

MGCP 1.0, TGCP

12.4.12

Cisco AS5350

Trunking Gateway1

MGCP 1.0, TGCP

12.4.12

Cisco AS5400

Trunking Gateway

MGCP 1.0, TGCP

12.4.12

Cisco PXM45/AXSM

Trunking Gateway

MGCP 1.0, TGCP

5.52(10.255)D

Cisco PXM1-4-155

Trunking Gateway

MGCP 1.0, TGCP

5.3.1

Cisco VISM-PR

Trunking Gateway

MGCP 1.0, TGCP

5.2.00

Cisco RPM

Trunking Gateway

MGCP 1.0, TGCP

12.4(6) T6

Cisco 2651

SS7 Signaling Gateway

SIGTRAN M3UA/SUA

12.2(25)SW7, 12.4(11)SW

Cisco 2811 ITP

SS7 Signaling Gateway

SIGTRAN M3UA/SUA

12.4(11)SW

Cisco 73xx ITP

SS7 Signaling Gateway

SIGTRAN M3UA/SUA

12.2(25)SW7, 12.2(18)ixc

Cisco 750x ITP

SS7 Signaling Gateway

SIGTRAN M3UA/SUA

12.2(25)SW7, 12.4(11)SW

Cisco uBR7246VXR Router

CMTS

PacketCable EM 08

12.3(13a)BC1, 12.3(13a)BC3

Cisco uBR 10K

CMTS

CALEA SII

12.3(13a)BC1, 12.3(13a)BC3

Cisco MSFC1

IP Core-Cat 6500

 

6.4-20

Cisco MSFC1

IP Core-Cat 6500

 

121-26.E4

Embedded MTAs
     

Arris TM402P

eMTA

NCS 1.0, IPSEC

TS0440559_022406_MODEL_4_5_TELNET_ON

Motorola SBV5220

eMTA

NCS 1.0, IPSEC

2.16.1.1

Motorola SBV5120

eMTA

NCS 1.0, IPSEC

2.16.1.1

Motorola SBV4200

eMTA

NCS 1.0, IPSEC

2.16.1.1

Scientific Atlanta Dpx2203

eMTA

NCS 1.0, IPSEC

v1.1.2r1151-050224b-5

SIP Endpoints
     

Linksys PAP2

SIP endpoint

SIP

3.1.5(Lsd)

Cisco 7940

SIP phone

SIP

6.2

Cisco 7960

SIP phone

SIP

6.2

Policy Servers
     

Camiant Multimedia Service Controller

Policy server

 

2.3

CableMatrix On-Demand Service Platform (ODSP)

Policy server

 

1.0.0b6

ENUM (Release 5.0 MR1)
     

Netnumber Titan

ENUM application

 

5.2.11

1 The Cisco AS5350 and AS5400 have also been tested as Announcement Servers


Table Sizes

To check the size of all tables specific to your BTS 10200 configuration, perform the command show db-usage.

Operator Access

Operator access to the Cisco BTS 10200 Softswitch is available only by secure shell (SSH) session to the EMS over Ethernet. The BTS 10200 does not support nonsecure FTP; in order for you to FTP to any other system, your BTS 10200 system must have secure FTP (SFTP) capabilities.

For security purposes, SSH access is limited to using defined management interfaces.

Installation Notes

Before running an installation, plan accordingly, by using the Install and Upgrade Guides. These guides provide detailed installation procedures. Installing the BTS 10200 Softswitch consists of:

1. Installing and cabling the hardware

2. Running the jumpstart procedure

3. Running the software (application) installation procedure

After installing and cabling the hardware, use the jumpstart procedure to have the system jumpstarted with the proper OS version and kernel patch level. Once the system is configured properly, you can begin the application installation.


Caution Do not modify any operating system parameters that the Cisco BTS 10200 Softswitch Jumpstart installs.


Note The application installation procedure is for duplex systems, the only installation type supported for Release 5.0.x.


Upgrade Procedures


Note All customers must be operating on the Sun Solaris 10 06/06 OS prior to upgrading to Release 5.0.x. Detailed information on installing and upgrading to Solaris 10 06/06 OS can be accessed at: http://www.cisco.com/en/US/products/hw/vcallcon/ps531/prod_installation_guides_list.html.


A procedure is available for customers upgrading between Cisco BTS 10200 releases.

The Upgrade Guides are available on the Install and Upgrade Guides documentation web site.

Upgrades and SIP Session Timers

SIP Session Timer values configured prior to Release 5.0 are reset to the default values after an upgrade to Release 5.0. Additionally, you cannot configure the SIP session timers, such as minSE and session_expires_delta_secs, on the CA-CONFIG table.

To configure the SIP timers, you must use the new SIP-TIMER-PROFILE table and reference the SIP timers in the CA-CONFIG table.

Caveats

The Bug Toolkit online application allows you to query defects and caveats.

Bug Toolkit

To access Bug Toolkit, you must have an Internet connection, a Web browser, and a Cisco.com username and password. To query defects and caveats, follow this procedure:


Step 1 Click here to log onto Bug Toolkit. You must have a Cisco.com user name and password.

Step 2 Click the Launch Bug Toolkit hyperlink.

Step 3 If you are looking for information about a specific caveat, enter the ID number in the "Enter known bug ID" field.

To view all caveats for Cisco BTS 10200, go to the "Search for bugs in other Cisco software and hardware products" section, and start typing BTS in the Product Name field.


Note Cisco BTS 10200 Softswitch appears after you type the first two letters, B and T.


Step 4 Click Next. The Cisco BTS 10200 Softswitch search page appears.

Step 5 Select the filters to query for caveats. You can choose any or all of the available options.


Note To make queries less specific, use the All wildcard for the Major/Minor release, Features/Components, and keyword options.


Step 6 Next to version (see Definition of Major, Point, and Maintenance Releases):

Select Major for the major releases (that is 5.0, 4.5, 4.4, 4.2, 4.1, 3.5).

Select Minor Release for more specific information—for example, selecting major Version 5.0 and minor Version 1 queries for Release 5.0.2 caveats.

Select the Features or Components to query.

Use keywords to search for a caveat title and description.

Select the Advanced Options, including the Bug Severity level, Bug Status Group, and Release Note Enclosure options.

Click Next.

Bug Toolkit returns the list of caveats based on your query.


New Features and Enhancements for Release 5.0, Maintenance Release 2 (5.0.3)

New documentation for these Release 5.0, MR2 features can be accessed at: http://www.cisco.com/en/US/products/hw/vcallcon/ps531/products_feature_guides_list.html

The following features were added or enhanced for Release 5.0, MR2:

Multiline Variety Package

IDX Soft Limits Enforcement

CMTS Discovery Using the Static Subnet Table Enhancements

Multiple EMS Spindles

PacketCable CMS Subscriber Provisioning with SOAP/XML

CALEA Support for MLHG

CALEA Support for SIP Triggers

Ring Tone Mapping with SIP Triggers

Call Disposition—Delineate Blocked Calls from Incomplete Calls

Multiline Variety Package

The BTS 10200 Multiline Variety Package (MVP) feature allows service providers to create logical groupings of subscribers and provide centrex features such as call-hold, call-park/retrieve and extension dialing to the subscribers within the group without requiring them to use access codes.

Although the MVP feature does not require access codes, you can configure the BTS 10200 to use prefixed extensions to reach subscribers within the group. For example, you can configure a group of eight subscribers with 1-digit extensions ranging from *2 to *9 or a group of up to 30 subscribers with 2-digit extensions ranging from *20 to *49. You can assign *0 for operator or attendant access.

For more detailed information on the MVP feature, refer to the Multiline Variety Package Feature Module.

IDX Soft Limits Enforcement

The IDX Soft Limits Enforcement feature sets soft limits on table sizes so that the IDX index cannot increment past the bounds. This feature synchronizes the memory size between a BTS 10200 Softswitch side A network element (NE) and a side B NE when the maximum memory size configuration increments in soak mode during a software upgrade to a new release. This addresses the backward replication issue that may cause data corruption due to the IDX being out of bounds.

When table sizes grow in soak mode while upgrading, call activity during soak mode may cause the following potential problems:

Handset provisioning tables may increment past the bounds.

Dynamic tables may increment past the bounds.

Limited subscriber provisioning may cause subscriber tables to increment past the bounds.

Note that this feature addresses issues caused when table sizes increase. Currently, full system fallback is not supported if the new release has a larger table size.

Implementation of the IDX Soft Limits Enforcement feature involves the following:

IDX library provides an API to set the soft limit (the maximum allocatable index) for an IDX table.

RDM process automatically exchanges the table size information and sets the soft limit when the platform starts up.

The soft limit stays even when the other side goes down.

A new major alarm, DATABASE(27)—Failure setting IDX table soft limit, is implemented with this feature.

CMTS Discovery Using the Static Subnet Table Enhancements

This feature was introduced in Release 5.0 MR1. See the CMTS Discovery Using the Static Subnet Table feature description.

In Release 5.0 MR2, this feature was enhanced to provide the following new CLI commands:

Non-DQoS call display

Refreshing IP address cache

Termination connection test with the DQoS command

For more detailed information on this feature and the new CLI commands, refer to the CMTS Discovery Using the Static Subnet Table Feature Module.

Multiple EMS Spindles

The Multiple EMS Spindles feature is an optional configuration that offers improved provisioning performance on the BTS 10200. The addition of EMS spindles (hard disks) significantly improves provisioning throughput, thereby increasing the capacity of the BTS 10200.

Multiple EMS spindles are installed on the BTS 10200 through a single, executable script which is run during a fresh OS install. The installation script migrates the existing Oracle database to a new disk pool, and the new file system is maintained after any reboots or application upgrades. There are no changes to any existing BTS 10200 application software.

For more information on multiple EMS spindles, refer to the Multiple EMS Spindles Feature Module.

PacketCable CMS Subscriber Provisioning with SOAP/XML

CMS subscriber provisioning over SOAP/XML interface was introduced in Release 5.0. This initial release supported only the Pkt-p1 interface to the Provisioning Server (PS)/Call Management Server (CMS) and the PcspService Object, without extensions.

In Release 5.0 MR2, CMS subscriber provisioning with SOAP/XML is fully compliant with the PKT-SP-CMSPROV1.5-I01-050128 PacketCable specification, allowing full support of PacketCable 1.5 subscriber provisioning.

In addition, the BTS 10200 now supports Cisco-specific extensions and customer-specific extensions to allow full provisioning and turn up of an in-service subscriber. The SOAP/XML interface enables you to peform the following provisioning operations:

Login/logout

Add a new subscriber

Delete an existing subscriber

Modify an existing subscriber

Get/Query an existing subscriber

Requests and responses between the Call Management Server (CMS) and Provisioning Server (PS) must be encapsulated in SOAP version 1.1. Secure transport protocol is achieved through the use of IPSec.

For more information on CMS subscriber provisioning with SOAP/XML, refer to the PacketCable CMS Subscriber Provisioning with SOAP/XML Feature Module (Beta Version).

CALEA Support for MLHG

BTS10200 provides CALEA support for the multiline hunt group (MLHG) where by a group or an individual member (i.e. Terminal) of a group can be placed under surveillance. If the whole MLHG group is under surveillance (i.e. Pilot DN is tapped), the BTS10200 will send call-identiying information for all the incoming calls to the group and outgoing calls from the group. If an individual member of group is under surveillance (i.e. associate DN is tapped), the BTS10200 will send call-identifying information for all the calls originating from the tapped terminal or terminated to the tapped terminal.


Note Call Identifying Informaiton for Extention dialing i.e. calls within the MLHG groups are not sent towards the delivery function server.


CALEA Support for SIP Triggers

In Release 5.0 MR2, CALEA is supported for SIP triggers. The BTS 10200 CMS sends a CALEA Service Instance Message (SIM) with a service name of Call Block. The message is sent when SIP trigger calls are blocked by the Announcement Server (AS). Cause code 21 appears in the reason header of the message.

Ring Tone Mapping with SIP Triggers

Prior to Release 5.0 MR2, a BTS 10200 deployed with SIP triggers did not accept the Alert-info header sent from the Application Server (AS). As a result, certain features on the AS could not have distinctive ring tones and call waiting tones assigned to them.

In Release 5.0 MR2, the BTS 10200 is enhanced to accept the Alert-info header from the AS. The following values are allowed in the Alert-info header:

<file://Bellcore-drx>—Where x can be a digit from 1-7 and maps to ring type 1-7 as specified in the DN2Subscriber table. The corresponding ring type is the ringing tone for the user, unless another feature on the BTS 10200 overwrites it.

Alert-info header maps to the SAI_ALERTING_PATTERN (1-7) on the interface between BCM and SIA.

If the called NCS subscriber has call waiting, then the BTS 10200 applies the call waiting tone (CWT). If the call waiting tone is CWT1, then the BTS 10200 overwrites the tone based on the information in the Alert-info header received from the AS as follows:

DR2 = CWT2

DR3 = CWT3

DR4-7 = CWT4

Call Disposition—Delineate Blocked Calls from Incomplete Calls

To delineate blocked calls from incomplete calls requires the BTS 10200 to translate the reason code sent to the BTS 10200 from the SIP application server in BYE (only) into a new service type in the CDR. The new service type will indicate that Call-Blocked-because of Privacy Plus to the billing servers.

To make this requirement extendable to new features to be provided by application servers in future, the following is implemented:

The BTS 10200 treats the reason-code received in BYE from the application server as an application server specific service type.

The BTS 10200 provides a base value of 200 for all the application server specific service types.

All of the service type values under 200 are used by the BTS 10200 for natively provided features.

The BTS 10200 will capture TAT/OHT Service Type in without any modifications.

During the invocation of the SIP trigger feature, if BYE is received from the application server with a reason-header having a code (can be any 2 digit or 3 digit code), the BTS 10200 will add a value of 200 to the code and capture it as the service type in billing. The code capture can be used by the billing server to determine the feature provided by the application server. For example if BYE is received with reason-code 21 from the application server, the BTS will capture code in CDR as 221.

The following is an example of the CDR that will be seen when a user executes a show command on the BTS 10200.


Note SERVICETYPE 1 is used to identify TAT1/TAT2/OHT depending on the originating or terminating triggers.


Example:

SERVICETYPE 1 = AS_SERVICE_221 
FEATUREDATAONE1= NULL. 
USAGESENSITIVE1=False
SERVICERESULTCODE1=Success 

The numeric value that is captured in the CDR file for this service type is 221.

In the future, instead of adding the 200 to the reason code sent by the application server, the application server will send the Right Reason code (200 onwards). This removes the need for adding 200 at the BTS 10200 and at the CDR and the reason code value will be consistent.

New Features and Enhancements for Release 5.0, Maintenance Release 1 (5.0.2)

New documentation for these Release 5.0, MR1 features can be accessed at: http://www.cisco.com/en/US/products/hw/vcallcon/ps531/products_feature_guides_list.html.


Note All customers must be operating on the Sun Solaris 10 06/06 OS prior to upgrading to Release 5.0, MR1 (5.0.2). Detailed information on installing and upgrading to Solaris 10 06/06 OS can be accessed at: http://www.cisco.com/en/US/products/hw/vcallcon/ps531/prod_installation_guides_list.html.


The following features were added or enhanced for Release 5.0, MR1:

SIP Triggers for SIP Endpoints

SIP Server Groups

CORBA Session Manageability

Seasonal Suspend

SIP Name Dialing

Disable Platform Shared Memory Replication

Aggregation ID Subnet

CMTS Discovery Using the Static Subnet Table

Bulk Data Export

Subscriber ID Parameter and DQoS Measurement Counters Support

ENUM Application

Own Calling Number Announcement Enhancement

Account Code Collection Enhancement

Terminal Make Busy and Group Make Busy

Database Table Size Enhancement

Switchover Data Mismatch Deferror Prevention

SIP Triggers for SIP Endpoints

The SIP triggers feature was first supported in Release 5.0 for MGCP and NCS subscribers. For Release 5.0, MR1 and later, the BTS 10200 Softswitch supports SIP triggers for SIP endpoints (SIP subscribers) when the incoming call is based on a Directory Number (DN):

Termination attempted trigger 1(TAT_1)

Termination attempted trigger 2 (TAT_2)

The SIP triggers feature is supported with the following limitations:

SIP triggers are not supported for Centrex subscribers.

The system does not support the off-hook trigger for SIP subscribers.

The BTS 10200 does not invoke any SIP triggers for SIP subscribers in the following cases:

For incoming calls based on address of record (AOR)

For features that are performed by the SIP endpoint, rather than the BTS 10200

For more detailed information on SIP triggers for SIP endpoints, refer to the Cisco BTS 10200 Softswitch SIP Triggers for SIP Endpoints Feature Module.

SIP Server Groups

The SIP Server Groups feature provides an alternative to the DNS-SRV (RFC-3263) method for destination selection on the BTS 10200 SIP interface, while providing capabilities that extend beyond what DNS-SRV provides. These additional capabilities are:

Tree model approach to SIP element selection

Blacklisting of SIP endpoints that are unreachable

SIP element advance on 5XX SIP responses

Server groups for established dialog requests

This feature eliminates the need for the BTS 10200 SIP interface to perform DNS lookups for call processing. The elimination of DNS lookups helps avoid performance impacts on SIP call processing on the BTS 10200 as a result of DNS server latency, which can occur due to network congestion.

For more information on the SIP server groups feature, refer to the Cisco BTS 10200 Softswitch SIP Server Groups Feature Module.

CORBA Session Manageability

The CORBA session manageability enhancements affect the manageability of CORBA user sessions and impact the following areas:

New CLI commands to manage CLI and CORBA user sessions—Includes stop client-session to free up resources

Policy-driven Smart Session Management—Includes the smart removal of idle sessions allowing new sessions to login

New password aging notification and password reset API in CORBA Software Developer's Kit (SDK)

New functionality to disable password aging by setting user status to PERSIST

SDK Programmer's Guide containing details of session management features and commands

For more information on the CORBA manageability enhancements, refer to the Cisco BTS 10200 Softswitch CORBA Manageability Featurette.

Seasonal Suspend

The Seasonal Suspend feature allows subscribers to suspend, rather than disconnect, their telephone service when going away for the off-season. This feature affects both inbound and outbound calls on the subscriber line.

This feature disables all domestic and international inbound and outbound calling, operator services, directory assistance, caller ID blocking, vertical service codes (VSCs), midcall and hookflash-based features, and all calling features other than the following:

Emergency (911)

Toll-free customer service numbers

Voicemail—Customers can retrieve messages and access voicemail functions.

The Seasonal Suspend feature is not available to Centrex or MLHG subscribers.

The BTS 10200 does not place any restrictions on the start and stop dates for seasonal suspend.

If no referral number is provisioned for a subscriber in the subscriber-feature-data table, then the system plays the generic seasonal suspend message.

For more information on the Season Suspend feature, refer to the Cisco BTS 10200 Softswitch Seasonal Suspend Feature Module.

SIP Name Dialing

The SIP Name Dialing feature enables the BTS 10200 to support the SIP soft clients.

For Release 5.0, MR1, only the voice portion of the SIP name dialing feature is implemented.

SIP soft clients can be provisioned in multiple BTS 10200 Softswitches within a network.

For more information on the SIP Name Dialing feature, refer to the Cisco BTS 10200 Softswitch SIP Name Dialing Feature Module.

Disable Platform Shared Memory Replication

Beginning with Release 5.0, MR1, the BTS 10200 supports replication disabling. This capability is used when performing upgrade procedures.

Aggregation ID Subnet

The Aggregation ID (aggr-id) Subnet feature allows a service provider to use the Subnet table to configure all subnets handled by every cable modem termination system (CMTS). The BTS 10200 Softswitch uses the IP address of the embedded multimedia terminal adapter (eMTA) and Subnet table to determine the CMTS handling of a particular eMTA. A CMTS is an aggregation device for multiple eMTAs.

For more information on the Aggregation ID Subnet feature, refer to the Cisco BTS 10200 Softswitch Aggregation ID Subnet Feature Module.

CMTS Discovery Using the Static Subnet Table

The CMTS Discovery Using the Static Subnet Table feature uses the statically provisioned Subnet table in the BTS 10200 system. The service providers must configure all subnets handled by every CMTS using the Subnet table. The BTS 10200 uses the IP address of the MTA and the Subnet table information to determine the CMTS (AGGR) handling the MTA.

The BTS 10200 uses the following data precedence to decide MTA Effective-AGGR-ID:

MTA's Effective-AGGR-ID is equivalent to its Manual-AGGR-ID (Aggr-Id provisioned in the MGW table) as long as the latter is provisioned (NOT NULL).

If MTA's Manual-AGGR-ID is not provisioned, then MTA's Effective AGGR-ID is equivalent to its Subnet's Manual AGGR-ID (Aggr-Id provisioned in the Subnet table).

For more detailed information on this feature, refer to the CMTS Discovery Using the Static Subnet Table Feature Module.

Bulk Data Export

The Bulk Data Export feature introduces a new database tool to export the BTS 10200 EMS provisioning data from the Oracle database to raw ASCII data files. The new tool provides a transport for the customer to migrate the BTS 10200 data to other reporting systems. This feature also serves as a supplemental backup mechanism.

This new data export tool reduces the total data export time from several hours to minutes. It also provides customers with better granularity and flexibility to specify the export contents.

The user must logon to the BTS 10200 EMS system as one of the following users to execute the tool:

The btsoper user

Any user that belongs to the btsoper group

The Oracle user

The operating system btsoper group and btsoper user is created at the BTS 10200 installation.

A few dbexp operations can only be executed by the privileged Oracle user.

For more information on the Bulk Data Export feature, refer to the Cisco BTS 10200 Softswitch Bulk Data Export Feature Module.

Subscriber ID Parameter and DQoS Measurement Counters Support

This feature (PacketCable ECN, DQoS 1.5-N-06.0339-4) adds a Subscriber ID in all Gate Control messages and enhances error codes returned from the Cable Modem Termination System (CMTS).

In the current DQoS (Dynamic Quality-of-Service) specification, the Gate ID is unique only to individual CMTS. With the CMTS proxying all Call Management Server (CMS) Gate control messaging through a central device, the CMS only has a single Common Open Policy Service (COPS) association to the proxy device. Since Gate IDs can be duplicated when using multiple CMTSs, this feature adds a Subscriber ID to each Gate Control message to disambiguate the Gate IDs between the CMS and proxy device.

The ECN DQoS 1.5-N-06.0339-4 augments the following COPS messages, where the Subscriber ID parameter is added:

GATE-INFO

GATE-DELETE

GATE-OPEN

GATE-CLOSE

The Subscriber ID is already available on the CMS and is currently used in the Gate-Alloc and Gate-Set messages.

This feature also enhances the error codes returned from CMTS or its proxy to allow more precise reasons as to why a particular gate operation failed.

For more information on the Subscriber ID Parameter and DQoS Measurement Counters Support feature, refer to the Cisco BTS 10200 Softswitch Subscriber ID Parameter and DQoS Measurement Counters Support Feature Module.

ENUM Application

The ENUM Application feature allows translation of E.164 address and SIP URL for call routing. The BTS 10200 interfaces with an external ENUM server for call routing.

This feature enables the BTS 10200 to perform ENUM query of calls and determine if a call is on-net. After the ENUM query, the BTS 10200 routes calls on-net or towards PTSN.

The new CDR field, ENUM-ROUTE-USED, is implemented for this feature.

For more information on the ENUM Application feature, refer to the Cisco BTS 10200 Softswitch ENUM Capability Feature Module.

Own Calling Number Announcement Enhancement

The Own Calling Number Announcement (OCNA) feature was enhanced in Release 5.0, MR1 to allow you to provision and activate the feature through a vertical service code (VSC).

For more information on the OCNA feature, refer to the Cisco BTS 10200 Softswitch Own Calling Number Announcement Feature Module.

Account Code Collection Enhancement

The following provisionable FEATURE-CONFIG parameters are added to the Feature Configuration Base table for account code collection:

ALLOW-NCS-ACCT-CODE-PROMPT—Allows you to delay NSC endpoints before prompting for an account code. The default behavior is for NSC endpoints to not delay.

LOCAL-NOD-ACCT-CODE-COLLECT—Calls with a Nature-Of-Dial (NOD) of LOCAL result in a prompt for an account code. The default behavior is LOCAL NOD calls do not prompt for an account code.

TOLLFREE-NOD-ACCT-CODE-COLLECT—Calls with a NOD of TOLLFREE result in a prompt for an account code. The default behavior is TOLLFREE NOD calls do not prompt for an account code.

NON-EMG-NOD-ACCT-CODE-COLLECT—Calls with a NOD of NON-EMG will result in a prompt for an account code. The default behavior is NON-EMG NOD calls prompt for an account code.

Also, the CA-CONFIG parameter ACCT-CODE-PROMPT-DELAY accepts a maximum value of 10000.

For more information on the these new parameters for account code collection, refer to Cisco BTS 10200 Softswitch Call Processing Command Line Interface Reference - Call Processing Commands