Guest

Cisco BTS 10200 Softswitch

Release Notes for Release 4.5.1

Table Of Contents

Cisco BTS 10200 Softswitch Release Notes for Release 4.5.1

Contents

System Requirements

Hardware Requirements

Installation Parameters

Interface Options

Optional Component (Hardware and Software)

Ancillary Hardware

Cisco ITP Signaling Gateways

Table Sizes

Software Requirements

Definition of Major, Minor, and Maintenance Releases

Release Naming Conventions

Network Time Protocol Software

Sun Solaris Version Upgrade

Optional Software

Component Interoperability

Gateway Caveat

H.323 Applications

Operator Access

Installation Notes

Upgrade Procedures

Upgrades and SIP Session Timers

Upgrades and CALEA

Caveats

Bug Toolkit

Errata

New or Enhanced Features for Release 4.5.1, Maintenance Release 2

Colombia ISUP

OpenSSH Upgrade

Audit Performance Enhancement

SIP Diversion Header Enhancement

Multiline Hunt Group Call Transfer

ISDN Table Size Increase

Support for Sun T2000 IPGE Ethernet Interface

Privacy Parameters in SIP Diversion Header

Account Codes for Local Calls

CODEC-NEG-SUPP Token in the Media Gateway Profile

MGCP Debug Message Enhancement

New or Enhanced Features for Release 4.5.1, Maintenance Release 1

Fast Audit and Sync Tools

Network Loopback Test for ISDN PRI Trunks

Block Provisioning

Validation of Source IP Address for Incoming SIP Messages

Virtual IP Address Functionality for CORBA Adapter

Optional Prefix Dialing for Toll and Toll-Free (8xx) Calls

Media Gateway—Unreachable Condition

New or Enhanced Features for Release 4.5.1

French ISUP

ITU LNP

Mexico ISUP

Thailand ISUP

T.38 Fax with SIP Endpoints

Metered Billing Featurette

H.323 Support

Table Size Increase

CORBA SDK

EM Privacy Indicator

Poland ISUP Support

Poland LNP

Privacy Manager with Cognitronics

Automatic Shared Memory Backup

Internal Secondary Authoritative DNS

New Features for Release 4.5

Telephony Features

MLHCentrexGroupName Data for Billing Call Detail Records

Temporarily Disconnected Subscriber Status and Soft Dial Tone

Block Toll Free Calls per Subscriber

Star Code to Access Voice Mail

Single Vertical Service Code to Activate or Deactivate Call Forwarding No Answer and Call Forwarding on Busy

Stand-Alone Call Redirection to Voice Mail

Inter-LATA Option

Privacy Director or Calling Identity with Enhanced Screening

No Solicitation Announcement

Trace Active Call per Directory Number and Trunk Identification

T.38 Fax Relay Call Agent Controlled Mode Across SIP Trunk Interface

Account/Authorization Code Support on PRI Trunks

Alerting Notification to Third-Party Feature Server

Operational Features

Network Continuity Test and TDM Test Enhancements

Alarm Correlation Enhancements

CDB File Naming Convention

Support of SUN 1280 (8 CPUs)

Measurement Report on a Per Market (POP) Basis

30 Originating Point Codes

Encrypted IPSEC Keys

.DONE Indicator After Successful Transmission of Call DB Records to Billing Mediation Server

Enhanced Software Upgrade

Secure Provisioning for SIP Endpoints

Testing Capability Required for 911 FGD-OS Trunks

Support for 2048 Bytes in Digit Map

Better Management of Alarms

Hungarian ISUP

ITU Local LNP

North American Numbering Plan Administration Audit Feature

ISUP Transparency on the Cisco BTS 10200-Cisco PGW 2200 Interface

Limited Call Duration Service (Prepaid/Postpaid)

Web Report Interface Authentication

Log Archive Facility

Other Enhancements

IP Addresses

Solaris 10

Oracle 10g

Display of System Status

Own Calling Number Announcement

Billing Record Cause Codes

Billing Record Enhancements

Alarms/Events Reported for DNS Failures

FDT and SDT Flags

ACR and SS7 Incoming Calls

OverDecadic Digit Support for Generic DN Parser

NDC Now Optional

Parameters for Noun=User Are Changeable

Password Key Added for CLI User Command

Provision CA-CONFIG Defaults in Call Agent and Feature Servers

Configuring Slot/Sub-Slot/Port for ISDN D-Channel Backhaul

Increase Table Size for Region Profile Table

Provisioned Subscriber DN and Privacy

No Automatic Alarm-status=Off After System Recovery

Billing Information for CF Interrogation

ACR and 200-OK Message

Show Faulty Trunks

Speed Call 1 Digit

SIM Memory Audit

SIP Dynamic Memory Audit

SIP Transport

INVITE Retries Are Configurable

SIP Session Timers

SIP Retry

Bypass Flag for Time Difference

Nodestat Obtains and Shows Status Information from Hub

SIP Stack Message Size

SIP Trunk Hop Counter

Cisco BTS 10200 Sends SDP for SIP Call When rbk=N for Call Waiting

SIA Diversion Header

SIA Restart

SIP Outbound Numbers Require +CC Depending on NOA

SIP Stack

DOMAIN-NAME Verified on SIP INVITE Messages

Time-Out (TO) to Ring Signal for MGCP/NCS

POP OFFICE SERVICE ID

SIP Stack Attempts Next Address If TCP Connection Fails for INVITE

A-Law to U-Law Transcoding Interworking

SIA Authentication

SIP NOTIFY Rejected from Unity

SIM Feature Server Status Saved in Feature Server Table

Change Counter Names to SIS and SIP for Release 4.5 Measurements

Change in RACF Service Logic

Heap Memory Monitor

VMWI and SDT on Per Line Basis

Piggybacked MGCP Messages Now Configurable Using MGW-PROFILE

New Field OSS-SIG-TYPE

Configurable Field for Sending FastStart in CALL PROCEEDING or ALERTING

Updated EventObject and Version ID Field

Updated H.323 Stack

Ringback on CAS Trunking Gateway

Measured Rate Flag

Account Code in Event Message Billing

New, Modified, or Deprecated Alarms

Other Features

Changes from Previous Releases

Vertical Service Code Limitation

Measurement Changes

New Documentation

New and Updated Documentation for Release 4.5.x

Previous 4.x Releases

Release 4.4.1

Configurable ACM Timer Based On Incoming Trunk Group

Physical Interface 4/2

OCB Enhancements

LNP Enhancement

ETSI v2 ISUP

Replaced Commands

Non-Facilities Associated Signaling

Release 4.4.0

NSCD Enabled on All Platforms

PacketCable Certified CMS, MGC

Simultaneous Support for CALEA Methods: PacketCable + SII

SIP Features

Cisco Self-Service Phone Administration

Range of Channels for TGCP Endpoints

Architecture Enhancements

Operational Enhancements

Support for Sun Netra 1280

Security Enhancements

Billing Changes in Call Agent Profile Table

Two-Level Automatic Recall

TCAP Signal Adaptor Recovery from Signaling Link Failure

Adjustable Timer for COS-Restrict Feature Confirmation Tone

Physical Interface 4/2

SSH Version 2

Distributed Message Transfer Part Level 3

Basic Network Loop-Back Test for NCS/MGCP End-Points

Originating Point Codes

VXSM Gateway

Flash Archive and Disk Mirroring

Exchange Code Table

Feature Profile Base and FEATURE-CONFIG Tables

Command Line Interface Guidelines

User Side State Machine Enabled

RSC Coordination Behavior

Increased ISDN Trunk Groups

9 Bits Used for ISDN D Channel Port

Release 4.2

H.323 Video, Routing, and Transparency Features

New Call Detail Record Field

SIP-T

Calling Party Number Options for Outgoing SETUP Message

Enhancements for Release 4.2

PacketCable

New Field for Signaling 68 Event/Trap

CODEC Negotiation

T.38 CA Mode Fax

Hook-Flash with Warmline and Hotline-Variable Feature

Capability for NAS Digital Calls

Release 4.1

Reduced Physical Interfaces

Signaling Capabilities

SIGTRAN-Based SS7 ANSI Signaling

SS7 ITU ISUP

China SS7 ISUP

Mexico SS7 ISUP Support

OpenORB Support

Installation

Cisco OSS Applications

Name Service Feature

Billing Subsystem Redesign

Billing Data Generation

PacketCable-Based Features

H.323 Annex E Redundancy

Call Manager/H.323 Interworking

IP Manager

SS7 CIC Audits

Process Restartability

SIP Trunks

OAMP Enhancements

Modified and New Subscriber Features

New Documentation for Release 4.4

New Documentation for Release 4.2

Cisco Field Notices

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

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 4.5.1


Revised: October 23, 2007

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.

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

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

Contents

These release notes for the Cisco BTS 10200 Softswitch describe the enhancements and new features provided in Release 4.5.1 (900-04.05.01.Vxx).

Also, these release notes describe the enhancements and new features provided in Release 4.5.1, Maintenance Releases 1 and 2 (MR1, MR2).

This document includes the following sections:

System Requirements

Hardware Requirements

Software Requirements

Caveats

New or Enhanced Features for Release 4.5.1

Previous 4.x Releases

Cisco Field Notices

Obtaining Documentation

Obtaining Technical Assistance

These release notes are updated periodically on an as needed basis. Please read these release notes in their entirety, because they contain important operational information that can impact your network.

System Requirements

This section details 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. Refer to Table 1 for host hardware options.

The physical plant requirements for installation of the Cisco BTS 10200 Softswitch are documented in the Cisco BTS 10200 Softswitch Site Preparation and Network Communication 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 requirement for the Release 4.5.1 medium configuration is 4 GB.

Two Ethernet switches.


Note Both AC and DC systems require two redundant feeds. We highly recommend that uninterruptible 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

Hardware available from Cisco Systems Inc. for PacketCable North American customers is listed below. Determine if you need AC or DC, and if you want the hardware in a cabinet or ready to mount in a customer rack. Work with a Cisco BTS 10200 product manager to determine the appropriate load for your situation.

The Cisco BTS 10200 Softswitch is available only in duplex (continuous-service) configurations.

Table 1 lists the hardware requirements for the Cisco BTS 10200 Softswitch Call Agent (CA) and Feature Server (FS) platform.


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. In particular, called-number analysis or screening, long call hold times, and service control point (SCP) queries might require additional resources.


Note Cisco Systems announced the end of sale and end of life for the SunFire V120s, Sun Netra 120s, and AXmp hardware and accessories. The last day to order these parts was January 1, 2005. Customers will continue to receive support from Cisco TAC until January 1, 2010. For more information, refer to the following EOS/EOL of BTS 10200 Hardware Web pages.

For Sun Fire V120s and Sun Netra 120:
http://www.cisco.com/en/US/products/hw/vcallcon/ps531/prod_eol_notice0900aecd800fe180.html

For AXmp: http://www.cisco.com/en/US/products/hw/vcallcon/ps531/prod_eol_notice0900aecd800f896a.html



Note Cisco Systems announced the end of sale and end of life for the Sun Fire V240s, V440s, 1280s, and Sun Netra 240s, 440s, and 1280s. The last day to order these parts was March 16, 2007. Customers will continue to receive support from Cisco TAC until March 14, 2012. For more information, refer to the following EOS/EOL of BTS 10200 Hardware Web page:
http://www.cisco.com/en/US/products/hw/vcallcon/ps531/prod_eol_notice0900aecd80532e24.html


The memory requirement for Release 4.5.1 is 8 GB. Using 4 GB (as in previous 4.x releases) may result in a loss of data while upgrading to Release 4.5.1, and users may need a fresh download if 4 GB memory is used.

For best results, Cisco recommends following the memory requirements listed in Table 1.

Table 1 Host Hardware Requirements 

Hardware
Processors
Required Memory for R4.x
Recommended Memory for R4.x
Disk Size

Sun Fire V240

2 x 1280

8 GB

8 GB

2 x 73 GB

Sun Netra 240

2 x 1280

8 GB

8 GB

2 x 73 GB

Sun Fire V440

4 x 1280

8 GB

8 GB

4 x 73 GB

Sun Netra 440

4 x 1280

8 GB

8 GB

4 x 73 GB

Sun Netra 1280

4 x 1200

8 GB

8 GB

2 x 73 GB

Sun Netra 1280

8 x 1200

16 GB

16 GB

2 x 73 GB

Sun Fire V1280

4 x 1280

8 GB

8 GB

2 x 73 GB

EMS

2 x 1280

4 GB

8 GB

2 x 73 GB


Installation Parameters


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

Interface Options


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


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

In Release 4.5.1, 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.

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. It enables this by performing ASCII text-based (rather than tones) user-interaction 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) number using a text-based menu displayed on its 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 it is 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 2.

Table 2 Ancillary Hardware for 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 3.

Table 3 Ancillary Hardware for DC Systems 

Part Number
Description

WS-C2950M-XL-EN-DC

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


or

WS-C2970G-24TS-E-DC

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


For All Systems

You need one alarm panel or your own terminal server that allows for console login. The Cisco BTS 10200 alarm panel is listed in Table 4.

Table 4 Ancillary Hardware for All Systems

Part Number
Description

BTS10200-ALRM

Cisco BTS 10200 Alarm Panel


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 4.5.1


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


The Cisco IP Transfer Point is implemented on the Cisco 2600XM Series Router (2650XM, 2651XM), the Cisco 7200 Series Router (7204VXR, 7206VXR), 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 26xx 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 may 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 transport protocol used.


For more information on the ITP equipment, see the Cisco ITP Product Data Sheet.

Table Sizes

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

Software Requirements

The Cisco BTS 10200 Softswitch Release 4.5.1 (900-04.05.01.Vxx) software is required for you to run the Cisco BTS 10200 Softswitch on the hardware platforms.

Definition of Major, Minor, and Maintenance Releases

The following section describes the differences between major, minor, 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 may NOT be skipped in deliveries to customers. This release is based on previous Main release and receives defect fixes synced from previous main releases throughout the life of this release.

Minor Release

A minor software release has only a few new features of limited scope, enhancements and/or defect fixes. The minor release number increments as content is added and numbers may be nonsequential (skipped). This release is based on a previous 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 nonsequential (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; also noted in Packaged-IN-XX.XX(XX) DDTS enclosure)

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 number.

Some naming convention examples are:

900-04.01.00V03

900-04.04.00.V01

900-04.04.01.V00

900-04.05.00.V01

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 reconfigure the NTP, refer to the Release 4.5 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. Doing so can cause the system to have serious problems. Allow the Solaris OS to obtain the time automatically through NTP services.

Sun Solaris Version Upgrade

The Sun Solaris software was upgraded to Version 10; the upgrade is part of the Release 4.5 upgrade.

For information about the Netscape browser requirements in Release 4.5, refer to the EPOM datasheets.

Optional Software

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

Cisco Extensible Provisioning Object Manager

You can use the Cisco Extensible Provisioning Object Manager (EPOM) Release 4.5 software as a provisioning tool for Cisco BTS 10200 Softswitch Release 4.5.1.


Note EPOM 4.5 is the only version intended to work with Cisco BTS 10200 Release 4.5.1.


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.3.1 interface to develop and deploy distributed object-based applications, as defined in the CORBA specification 2.4. 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 CORBA Adapter Interface Specification Programmer Guide.

Cisco Self-Service Phone Administration

You can use the Cisco Self-Service Phone Administration (SPA), Version 1.1, which allows phones to be organized into accounts and managed by end users to manipulate existing features and query account information without service provider intervention. This reduces service provider costs, while enhancing the end user's product experience. When the service provider has installed Cisco SPA and configured it using the Cisco SPA operation and configuration tool, all that remains is creating accounts for users to manage using their own phones. The Cisco SPA application and the Cisco SPA operation and configuration tool are described in the Cisco SPA Installation and Users Guide.

Component Interoperability

Table 5 lists specific peripheral platforms, functions, and software loads used in system testing for interoperability with the Cisco BTS 10200 Softswitch Release 4.5.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 Cisco BTS 10200 Softswitch.

Table 5 Component Interoperability Matrix 

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

Cognitronics CX500

Announcement Server

MGCP 1.0

3.0

IP Unity Harmony 6000

Privacy Director

SIP RFC3261

3.1

IP Unity Harmony 6000

Voicemail Server

SIP RFC3261

3.1

IP Unity Harmony 6000

Announcement 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 ITP

SS7 Signaling Gateway

SIGTRAN M3UA/SUA

12.2(25)SW9

Cisco 73xx ITP

SS7 Signaling Gateway

SIGTRAN M3UA/SUA

12.2(25)SW9

Cisco 750x ITP

SS7 Signaling Gateway

SIGTRAN M3UA/SUA

12.2(25)SW9

Cisco uBR7246VXR Router

CMTS

PacketCable EM 08

12.3(13a)BC3

Cisco uBR 10K

CMTS, CALEA

CALEA SII, PCCMTS

12.3(17b)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

TS040559_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 ATA188

SIP endpoint

SIP

3.2.1

Policy Servers
     

Camiant Multimedia Service Controller

Policy server

 

2.3

CableMatrix On-Demand Service Platform (ODSP)

Policy server

 

1.0.0b6

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


Gateway Caveat

An invalid CRCX (inactive + r:cl) is sent during call waiting scenarios. The Cisco IOS gateway generates error 524 for a CRCX with "L: ..., r:cl" and "M: inactive" on a call waiting scenario when the media gateway for the call waiting subscriber is provisioned to use "CL" for RSVP.

This a Cisco IOS media gateway issue, not a Cisco BTS 10200 Softswitch issue. The workaround for this is to not use CL for RSVP for the media gateway.

H.323 Applications

H.323 applications are supported in Release 4.5.1, but not Release 4.5.0.

Operator Access

Operator access to the Cisco BTS 10200 Softswitch is available only by secure shell (SSH) session to the EMS over Ethernet. The Cisco BTS 10200 Softswitch does not support nonsecure FTP; in order for you to FTP to any other system, your Cisco BTS 10200 Softswitch 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 Site Preparation and Network Communications Requirement document, the Network Site Survey, and a Building and Environment Site Survey.

For detailed installation procedures on installing the Release 4.5.x software, refer to the CD Jumpstart Procedure and Application Installation for Duplex Systems links in the Cisco BTS 10200 Softswitch Application Installation Guide.

Installing the Cisco BTS 10200 Softswitch consists of following:

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.


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


Upgrade Procedures


Note All customers must be on the latest load of a release prior to executing any upgrade procedure.


A procedure is available for customers upgrading between Cisco BTS 10200 releases. The procedures are provided for customers upgrading from the following releases:

From Release 4.5.0V13 to 4.5.1Vxx

From Release 4.5.13V06 to 4.5.1Vxx

From Release 4.5.13V08 to 4.5.1Vxx

From Release 4.5.1Vxx to 4.5.1Vyy

For additional information about the upgrade or fallback procedures, refer to the "Enhanced Software Upgrade" section.

The upgrade guide is available from the Cisco BTS 10200 Release 4.5.x Installation and Upgrade Guides Web page.

Upgrades and SIP Session Timers

SIP Session Timer values configured prior to Release 4.5.1 are reset to the default values after you upgrade to Release 4.5.1. 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 that in the CA-CONFIG table.

Upgrades and CALEA

The following information is relevant for CALEA users upgrading from Release 3.5.5 to Release 4.5.x.

In some cases, CALEA will not function after upgrade without the CALEA-related components being modified. Use the following steps for Task 7, Continue Upgrade Process, in the Release 3.5.5 to 4.5.x upgrade guide to ensure that CALEA functions properly.

Once side B is active with Release 4.5.x, go to SSDF and make the following modification:

MODIFY-AFRI:AFID=Cactus-TWC,IFID=1,IPADDR=qfe0_ip,PORT=14146,VERSION=I08;
MODIFY-AFRI:AFID=Cactus-TWC,IFID=2,IPADDR=qfe1_ip,PORT=14146,VERSION=I08;

Note To use SII architect for wiretapping, leave the CCCID field in IPCCC blank in the surveillance provision.


Caveats

Caveats are not listed in the Release Notes. Instead, caveats are available through the online tool, Bug Toolkit, allowing customers to query defects according to their own needs.

Bug Toolkit

To access Bug Toolkit, you need an Internet connection, a Web browser and a Cisco.com username and password.


Note Use your Cisco.com username and password when accessing Bug Toolkit, not the Cisco BTS 10200 Softswitch documentation username and password. If you access Bug Toolkit from the Cisco BTS 10200 documentation page, the Cisco BTS 10200 documentation username and password are the default. Change the default to your Cisco.com username and password instead.


To use Bug Toolkit, 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 To find 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 To query by version (see Definition of Major, Minor, and Maintenance Releases):

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

Select Minor Release for more specific information—for example, selecting Major Version 3.5 and Minor Version 4 queries for Release 3.5.4 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.


Errata

The Feature Descriptions document for Release 4.5x (http://www.cisco.com/en/US/docs/voice_ip_comm/bts/4.5/feature/description/fd201sft.html#wp1228569) lists an incorrect dial tone duration of 4 seconds for the Call Hold (CHD) feature. The current wording is "If the activating party does nothing, the network waits 4 seconds, then removes the dial tone." However the actual behavior is: If the activating party does nothing, the network waits 16 seconds, then removes the dial tone and provides an announcement.

New or Enhanced Features for Release 4.5.1, Maintenance Release 2

New feature documentation for Release 4.5.x 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 in Release 4.5.1, Maintenance Release 2 (MR2):

Colombia ISUP

OpenSSH Upgrade

Audit Performance Enhancement

SIP Diversion Header Enhancement

Multiline Hunt Group Call Transfer

ISDN Table Size Increase

Support for Sun T2000 IPGE Ethernet Interface

Privacy Parameters in SIP Diversion Header

Account Codes for Local Calls

CODEC-NEG-SUPP Token in the Media Gateway Profile

MGCP Debug Message Enhancement

Colombia ISUP

Release 4.5.1 MR2 supports the Colombia ISUP Q.767 variant on the BTS 10200 Softswitch.

This feature adds a new value to the installed default variant base. A new id token, Q767_Colombia, is added to the User Part Variant Base and User Part Variant tables.

OpenSSH Upgrade

OpenSSH is a third-party SSH connectivity tool. Prior to Release 4.5.1 MR2, the BTS 10200 Softswitch used the OpenSSH 4.2p1 package. For Release 4.5.1 MR2, the OpenSSH package is ugraded to OpenSSH 4.4.

Audit Performance Enhancement

This enhancement reduces the time of a BTS 10200 EMS-A to EMS-B database audit by two-thirds. In a system with 200,000 subscribers, the audit completes in 7.5 minutes with no impact on EMS operations. The user enters the existing commands, su-oracle and dbadm-C db, to execute the audit.

SIP Diversion Header Enhancement

The BTS 10200 imposes limits on the decoding of incoming SIP messages. These limitations protect the system from performance problems due to the decoding of extremely large messages.

Prior to Release 4.5.1 MR2, the maximum number of allowable parameters in the SIP Diversion Header was five. Beginning with Release 4.5.1 MR2, the maximum number of allowable parameters is increased to ten. For more detailed information on SIP messages and maximum parameters, refer to the Cisco BTS 10200 Softswitch SIP Protocol User Guide.

Multiline Hunt Group Call Transfer

In Release 4.5.1 MR2, the Multiline Hunt Group (MLHG) call transfer feature allows all members of a MLHG to perform attended call transfers with 3-way calling. Members of a MLHG must be subscribed to call transfer and 3-way calling service in order to use the MLHG call transfer feature.

ISDN Table Size Increase

In Release 4.5.1 MR2, the following BTS 10200 ISDN tables were increased in capacity:

ISDN DCHAN

ISDN_INTF

BACKHAUL_SET

RUDP_BACKHAUL_SESSION

The BTS 10200 now supports up to 2000 ISDN trunk groups.

Support for Sun T2000 IPGE Ethernet Interface

The Sun Netra T2000 has four 1 GB ipge ports integrated into its motherboard. Beginning with Release 4.5.1 MR2, the BTS 10200 is enhanced to support these new ipge interfaces.

Privacy Parameters in SIP Diversion Header

In Release 4.5.1 MR2 and later, if the SIP diversion feature is enabled, privacy parameters are sent and received in the SIP Diversion header for INVITEs sent out on a BTS 10200 SIP trunk.

Also, if the original called number (OCN) and/or the redirected DN (RDN) are being sent in Diversion headers towards local SIP subscribers, the system applies `anonymous' to the headers as follows:

If an OCN exists, it populates the URL as anonymous@anonymous.invalid in the To header.

If a Diversion header is added, it populates the `user' part of the header with `anonymous'.

For more information on the SIP diversion header feature and privacy parameters, refer to the Cisco BTS 10200 SIP Protocol User Guide (Release 4.5.x).

Account Codes for Local Calls

Prior to Release 4.5.1 MR2, the BTS 10200 supported account codes for long distance calls only. In Release 4.5.1 MR2 and later, the BTS 10200 is enhanced to support account codes for local calls in addition to long distance calls.

CODEC-NEG-SUPP Token in the Media Gateway Profile

In Release 4.5.1 MR2, the CODEC-NEG-SUPP token enforcement is updated in the Media Gateway (MGW) Profile table. This parameter specifies a list of codecs common to both sides of a call in the local connection option (LCO) parameter of the create connection (CRCX) message. The default value for this parameter is `Y'. Available codec types are listed in the Quality of Service (QoS) table, using the codec-type token.

For more information on the CODEC-NEG-SUPP token, refer to "Office Provisioning—Media Gateway Profile Table, page 2-34" of the Cisco BTS 10200 Softswitch Command Line Interface Reference for Call Processing.

MGCP Debug Message Enhancement

During certain conditions, debug messages appear in the BTS 10200 call trace logs. This enhancement allows printing the content of MGCP messages that are sent/received at default trace level (INFO3). This can be done under the following conditions:

When the BTS 10200 receives NACK (return code larger than 299, other than 401/402) for MGCP commands sent to the endpoint, the response message is printed along with the original command sent by the BTS 10200.

When the BTS 10200 retransmits MGCP commands to the endpoint. An exception is periodically sent keep-alive AUEP messages.

When the BTS 10200 receives RSIP messages from the endpoint or MGW.

When the BTS 10200 receives Gateway initiated DLCX commands.

New or Enhanced Features for Release 4.5.1, Maintenance Release 1

New documentation for Release 4.5.x 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 in Release 4.5.1, Maintenance Release 1 (MR1):

Fast Audit and Sync Tools

Network Loopback Test for ISDN PRI Trunks

Block Provisioning

Validation of Source IP Address for Incoming SIP Messages

Virtual IP Address Functionality for CORBA Adapter

Optional Prefix Dialing for Toll and Toll-Free (8xx) Calls

Media Gateway—Unreachable Condition

Fast Audit and Sync Tools


Note The bts_audit and bts_sync process tools should be used only during maintenance windows due to high CPU usage requirements.


The Cisco BTS 10200 Softswitch Fast Audit and Sync Tools feature consists of two expect shell scripts that use other unix scripts and utilities to perform full-database and table audits of the databases on the various network elements of the system, and synchronize the mismatches found. The bts_audit tool determines the tables when performing full database audit by analyzing the catalog of the CA, FSPTC and FSAIN databases. The scripts will create copies of the data from the tables in a standardized format. The data files are used to generate a checksum for each table. The check sums are compared, and if they are not equal, the network element data file will be transferred to the EMS. On the EMS, the data is compared row by row, and mismatches are printed to a file that may be used by the bts_sync tool to restore synchronization of the table on the network element.

The bts_audit tool is able to:

Find tables with mismatches

Find rows missing in application database

Find rows missing in EMS database

Find rows with data mismatches between two databases

Generate a report that lists these mismatches

Generate the SQL to be used to correct the mismatches

The bts_sync tool is used to send the generated SQL statements to the appropriate destination to bring the databases into synchronization.

Release 4.5.1 or later of the Cisco BTS 10200 Softswitch software must be installed and operating on the system to utilize the Cisco BTS 10200 Softswitch Fast Audit and Sync Tools feature.

Network Loopback Test for ISDN PRI Trunks

Network Loopback Test for ISDN PRI trunks (ISDN NLB) feature allows operators to conduct network loopback testing originating from shared ISDN PRI trunks. The shared test trunk group accepts both normal and NLB test calls. NLB test calls are identified by provisioning the call-type and call-subtype tokens in the Destination table.

The Cisco BTS 10200 Softswitch cannot perform network loopback test calls that originate from another switch and does not route NLB test calls from a testing device on an H.323 or SIP interface.


Note The network loopback test cannot be performed if the status of the subscriber to be tested is unequipped (UEQP) or operational-out-of-service (OOS).


For detailed information on this feature, refer to the feature module.

Block Provisioning

The Block Session Enhancement allows users of the Cisco BTS 10200 Softswitch to prevent provisioning during an upgrade or maintenance window. The Block Session Enhancement can block/unblock a specific session type, or a specific session user. You can block provisioning from the following interfaces:

CLI

FTP

CORBA

SNMP

The Block Session Enhancement features two levels of blocking:

PROVISION—prevents all provisioning commands from executing

COMPLETE—prevents all commands from executing

Only terminal type "MNT" users can use block provisioning, and "MNT" users are never blocked from provisioning. "MNT" users can block provisioning from either the Active or Standby side of the EMS.

When used, the Block Session Enhancement feature applies to all non-"MNT" users on terminals on either the Active or Standby side of the EMS. The commands of users already logged in, or those who login after the block command is issued, are prevented from executing.

The Block Session Enhancement is designed to remain in effect during the entire upgrade or maintenance window. After the upgrade or maintenance is complete, the unblock command clears the blocked state on both the Active and Standby side of the EMS.

For more information, refer to the Cisco BTS 10200 Softswitch Operations and Maintenance Guide.

Validation of Source IP Address for Incoming SIP Messages

The Cisco BTS 10200 Softswitch can perform source IP address validation of incoming messages received on SIP trunks. This validation process is intended to reduce the risk of security attacks, which can occur if a packet is sniffed in the network and then sent from a different or rogue IP address, or domain, as present in the Via header. By default, IP address validation is disabled on the Cisco BTS 10200 Softswitch. The service provider can enable this capability using the SIA-TG-VALIDATE-SOURCE-IP token in the ca-config table. This is a switch-wide parameter, and applies to all SIP trunk groups.

Provisioning details can be found in the Chapter 2 of the Cisco BTS 10200 Softswitch SIP Protocol Provisioning Guide.

Virtual IP Address Functionality for CORBA Adapter

Beginning with Release 4.5.1, Maintenance Release 1 (MR1), the CORBA Adapter (CAD) installation automatically uses Virtual IP (VIP) Address as the iiop.hostname. VIP allows the NameService to listen to all IP addresses on the active EMS. The VIP feature is configured through the CLI.

The CORBA installation automatically selects the VIP (Virtual IP) if the VIP is configured, otherwise the first management IP address is selected. This change will be seen in the /etc/inittab folder.

Refer to the CORBA Adapter Interface Specification Programmer Guide for information on how to change the network configuration for CORBA and for more information on the VIP functionality.

Optional Prefix Dialing for Toll and Toll-Free (8xx) Calls

The BTS 10200 Softswitch can be provisioned to specify whether dialing a prefix 1 for 500, 800 (toll-free), 900, and toll calls is required. If dialing a prefix 1 is required and not dialed, an announcment is played. The following token is updated in the CLI Subscriber Service Profile table:

TOLL-PFX1-OPT

VARCHAR(3)—1-3 ASCII characters (Default=RQ)

RQ (Default)—Prefix 1 required

NR—Prefix 1 not required

OPT—Prefix 1 is optional (ok to dial if prefix 1 not dialed)

For more information, refer to the Subscriber Service Profile table in the Cisco BTS 10200 Softswitch CLI Guide.

Media Gateway—Unreachable Condition

Beginning in Release 4.5.1 MR1, you can provision the BTS 10200 through CLI to release calls if and when the MGW becomes unreachable. This enhancement uses the SPARE1-SUPP token in the MGW-Profile Table.

Prior to this release, the BTS 10200 did not release calls if the MGW was unreachable. This default behavior was not configurable.

This enhancement allows you to configure the SPARE1-SUPP token:

Y—If the MGW is unreachable, then all active calls on the MGW are released.

N—If the MGW is unreachable, then all active calls on the MGW are not released.

For more detailed information, refer to the MGW-Profile Table in the Cisco BTS 10200 Softswitch CLI Guide.

New or Enhanced Features for Release 4.5.1

The following features were added or enhanced in Release 4.5.1:

French ISUP

ITU LNP

Mexico ISUP

Thailand ISUP

T.38 Fax with SIP Endpoints

Metered Billing Featurette

H.323 Support

Table Size Increase

CORBA SDK

EM Privacy Indicator

Poland ISUP Support

Poland LNP

Privacy Manager with Cognitronics

Automatic Shared Memory Backup

Internal Secondary Authoritative DNS

French ISUP

The French ISUP is an ISUP variant named Q761_ETSIV3_FRENCH ISUP, which is based on the 1997 version of Q.761/ISUP V3. The French ISUP feature supports and works in conjunction with the ITU LNP feature on the Cisco BTS 10200 Softswitch.

ITU LNP

Release 4.5.1 introduced the International Telecommunication Union (ITU) Local Number Portability (LNP) feature for the Cisco BTS 10200 Softswitch.

Local Number Portability (LNP) gives a telephone customer the ability to retain a local phone number if he or she switches to another local telephone service provider either within or outside the same geographic area.

To enable LNP functions on the Cisco softswitches, the Cisco BTS 10200 Softswitch maintains subscriber porting data in an internal database in the DN2RN table. In some countries, the system periodically connects to the country's central database and downloads the most recent set of LNP updates. These updates are stored in the DN2RN table in the Cisco BTS 10200 Softswitch's internal data format.

Mexico ISUP

Release 4.5.1 supports the Mexico ISUP variant, NOM112, on the Cisco BTS 10200 Softswitch. Mexico ISUP support also requires implementation of the Q.767 protocol family.

This feature provides SS7-based connectivity to the PSTNs in various countries, along with a large suite of local subscriber services. The requirement is for support with the ITP SS7 SG providing the SS7 access.

Mexico ISUP provides the service provider full and partial E1 access for delivering small business voice services.

Thailand ISUP

Release 4.5.1 also supports the Thailand ISUP variant, based on the ITU-T Q.761-4 specifications and part of Q767, on the Cisco BTS 10200 Softswitch.

This featurette adds a new value to the installed default variant base. It introduces the value Q761_Thailand for the ID token in the User Part Variant Base and User Part Variant tables.

T.38 Fax with SIP Endpoints

In Release 4.5, the T.38 fax relay feature did not support SIP endpoints. However, the feature was updated for this version, and Release 4.5.1 now supports SIP endpoints.

Metered Billing Featurette

The new Release 4.5.1 featurette, metered billing, allows the Cisco BTS 10200 Softswitch to collect metered "pulses" from operators signaled to UPC via SPIROU (French ISUP) ITX messages.

This SS7 messaging is used for audio services that are paid by for by either a flat rate calculation or a time-based calculation. The calls are routed to the operator, and the operator reports the payment amount by the ITX messages. Every ITX has the same value.

For example, if 1 charging unit was equivalent to 0.1 Euro and a caller dialed a service such as a weather forecast with a 1 Euro fee, then the network would send 10 ITX messages.

H.323 Support

H.323 applications were not supported in Release 4.5.0, but are supported in Release 4.5.1. The Cisco BTS 10200 Softswitch implements H.323 interfaces and functions in Release 4.5.1, and also provides H.323 provisioning, operating, and troubleshooting procedures.

In Release 4.5.1, information about the reattempt, route advance, and hairpinning (redirect) functions was updated and enhanced. A new token (SEND-FS-CALLP) was added in the H.32