Cisco BTS 10200 Installation guide

CISCO CONFIDENTIAL
Cisco BTS 10200 Softswitch —
Release Notes for Release 3.3 V04
December 13, 2002
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.
These release notes for the Cisco BTS 10200 Softswitch describe the enhancements and new features
provided in Release 3.3 V04.
These release notes are updated as needed. Please read the applicable sections in their entirety, because
they contain important operational information that can impact your network.
Contents
This document includes the following sections:
•
System Requirements, page 2
•
New and Changed Information, page 3
•
Enhancements, page 18
•
Caveats, page 23
•
Documentation Updates, page 55
•
Related Documentation, page 56
•
Obtaining Documentation, page 57
•
Obtaining Technical Assistance, page 58
Corporate Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Copyright © 2002. Cisco Systems, Inc. All rights reserved.
System Requirements
CISCO CONFIDENTIAL
System Requirements
The Cisco BTS 10200 Softswitch consists of the following equipment:
•
Call Agent/Feature Server (CA/FS)—Two application servers, each with four CPUs.
Continuous Computing Corp. Model AXmp: 4 CPUs, 4 GBytes RAM, 4 Disks (36 GBytes each)
•
Element Management System (EMS)/Bulk Data Management System (BDMS) servers—
Two administration processors, each with one CPU.
Continuous Computing Corp. Model AXi: 2 CPUs, 2 GBytes RAM, 4 Disks (36 GBytes each)
•
Two Cisco 2924M switch routers.
•
Continuous Computing Corp. Intelligent Alarm Panel (IAP)
•
Power distribution unit (PDU) for DC systems.
DC-powered systems require two (redundant) feeds of 40A at -48 VDC. AC-powered systems
require two (redundant) circuits of 20A at 120 VAC.
The physical requirements for installation of the Cisco BTS 10200 Softswitch are documented in the
Cisco BTS 10200 Softswitch Building Environment and Power Site Survey.
For more detailed information, refer to the Cisco BTS 10200 Softswitch System Description.
Operator Access
Operator access to the Cisco BTS 10200 Softswitch is available only by secure shell (SSH) session
to the EMS over Ethernet. Communications can be interactive or can be in batch mode using FTP.
Installation Notes
For detailed installation procedures for the Release 3.3 V04 software, refer to the Cisco BTS 10200
Softswitch Application Installation Guide.
Limitations and Restrictions
The Release 3.3 V04 software requires that the measurement-prov command use the type token
“announce” rather than “anm” as it is for all other CLI commands. Entering “type=anm” for the
measurement-prov command returns an error message.
Provisioning Cisco BTS 10200 the Generate EMs or CDBs
Provision the Cisco BTS 10200 to generate either EMs or CDBs, but not both. Attempting to generate
both types of records simultaneously can significantly degrade the call processing rate. Refer to the
"Event Message Billing Support" section for provisioning details.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
2
OL-1835-04
New and Changed Information
CISCO CONFIDENTIAL
New and Changed Information
This section lists the new features and enhancements available in Release 3.3 V04.
New Hardware Features
The Cisco BTS 10200 Softswitch complies with Network Equipment-Building System (NEBS) Level 1
and Level 3 Requirements (SR-3580).
New Software Features
The following new applications and services are available in Release 3.3 V04. For more detailed
information on each of the applications or services described here, refer to the relevant Cisco BTS 10200
Softswitch Feature Module or manual.
•
PacketCable Features, page 3
•
Inter-Office Automatic Callback, Automatic Recall, page 7
•
T108 Test Line Support, page 8
•
8XX Enhancement with NOA Processing, page 9
•
Provisionable CLLI Codes, page 10
•
Digit Manipulation Table, page 12
•
SNMP Interface, page 13
PacketCable Features
The following sections provide brief descriptions of the new PacketCable features included in the
Cisco BTS 10200 Softswitch software Release 3.3 V04 including:
•
Dynamic Quality of Service (DQoS)
•
PacketCable Event Messages
•
PacketCable NCS 1.0 Compliance
•
Billing Data Generation Methods
For more detailed information, refer to the Cisco BTS 10200 Softswitch PacketCable Feature Module.
Dynamic Quality of Service
This section provides a brief overview of the PacketCable Dynamic Quality of Service (DQoS) function
included in Release 3.3 V04. For more information, refer to the “PacketCable Dynamic Quality of
Service Specification,” PKT-SP-DQOS-I03-020116, January 16, 2002. PacketCable defines the
specifications for delivery of enhanced communication services to a consumer’s home using packet data
transmission technology over the cable television hybrid fiber coax data network running the Data Over
Cable Service Interface Specification (DOCSIS) protocol.
PacketCable DQoS defines a QoS architecture for the “access” portion of the PacketCable network,
which is defined as the segment between the Multimedia Terminal Adapter (MTA) and the Cable Modem
Termination System (CMTS), including the DOCSIS network. Cisco’s DQoS implementation uses the
Cisco BTS 10200 as a Cable Management Server (CMS) and Media Gateway Controller (MGC).
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
3
New and Changed Information
CISCO CONFIDENTIAL
Commercial voice communications capability requires a very high level of transport and signaling
performance, including:
•
Absolute minimum packet delay/loss, session setup latency time, and post pickup delay.
•
Provide accounting for QoS resources on a per-session basis.
•
Both two-phase (reserve-commit) and single phase (commit) QoS activation models.
•
Prevent (or minimize) abusive QoS usage.
•
Reclamation of QoS resources for dead/stale sessions.
The DOCSIS 1.1 specification provides the network layer QoS mechanisms responsible for classifying,
policing, scheduling, and marking packets once the traffic flows are established by the DQoS signaling
protocols. The role of DQoS is the coordination between call signaling (NCS/MGCP), which controls
access to the voice application service, and resource management, which controls access to DOCSIS
network-layer resources. This coordination ensures that users are authenticated and authorized before
receiving access to the enhanced QoS associated with the service. It also ensures that network resources
are available end-to-end before alerting the destination MTA.
The main function of the Cisco BTS 10200 is the Gate Controller function as defined in the DQoS
specification. In this role it ensures that enhanced QoS is provided only to authorized users and the use
of resources is properly accounted for, consistent with the conventions of providers that are part of the
Public Switched Telephone Network (PSTN), in which charging occurs only after the called party picks
up. This includes prevention of utilization of reserved resources for purposes other than the session to
which they are assigned.
Features supported in this release include:
•
MTA/RGW signaling (NCS)—additional parameters required for DQoS. The Cisco BTS 10200 is
enhanced to handle large number of MTA’s.
•
Gate control signaling (COPS)—a new interface to the Cisco BTS 10200. It covers the messaging
and parameters required for the CMS/GC to CMTS interface supporting DQoS and CALEA related
functions.
•
Admission control for up stream and downstream traffic—allows service providers to provision
the necessary parameters and/or the alternative policies as a Gate Controller, such as session class
for normal voice calls or overlapping session class for emergency calls. Session classes can further
enable pre-emption of already reserved resources, where the policy for pre-emption is provisioned
by the service provider.
•
Call scenarios supported:
– On-net to on-net call without gate coordination.
– On-net to off-net call without gate coordination.
– Off-net to on-net call without gate coordination.
•
Residential Gateway (RGW) support.
– DQoS capable PacketCable MTA
– Non-DQoS capable PacketCable MTA
•
Resource control—ensures that the use of resources is properly accounted for. This function is
performed by CMTS with the resource control data provided by the Cisco BTS 10200, such as
session class, maximum sessions allowed, maximum bandwidth allowed, and so on.
•
Dynamic binding of resources—specifically support of the call waiting feature. CMTS is directed
by the CMS/CA to switch resource between gates. This function is initiated by the MTA with the
information provided by the BTS over the NCS interface. The provided resource ID will be used by
the MTA to perform RSVP signaling which triggers the resource binding over the DOCSIS link.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
4
OL-1835-04
New and Changed Information
CISCO CONFIDENTIAL
PacketCable Event Messages
This section describes the requirements for PacketCable Event Messages, as provided in the PacketCable
Event Messages Specification, PKT-SP-EM-I03-011221, December 21, 2001.
The DQoS feature described previously is required in the PacketCable network so that PacketCable event
messages can be used by the Record Keeping Server (RKS) for billing. PacketCable event messages are
data records containing information about network usage and activities which are collected for billing
purposes. The RKS is a trusted PacketCable network element that receives event messages from other
network elements; specifically the CMS, MGC, and CMTS. The RKS is, at a minimum, a short term
repository for billing event messages.
In the PacketCable architecture, event message generation is based on the half-call model. A single event
message might contain a complete set of data regarding usage, or it might contain only part of the total
usage information. The RKS correlates the information in multiple billing event messages and provides
the complete record of service for a call, referred to as a Call Detail Record (CDR).
The physical Cisco BTS 10200 Softswitch node contains the logical network elements CMS and MGC.
The billing event messages generated by CMS and MGC are sent by the Cisco BTS 10200 to the RKS.
PacketCable NCS 1.0
This section describes the PacketCable Network-based Call Signaling Protocol (NCS) compliance
portion of the Cisco BTS 10200 Softswitch PacketCable Feature Module.
The NCS compliance matrix is depicted in the Cisco BTS 10200 Softswitch PacketCable Feature
Module. The individual compliance elements listed in the feature module are extracted from the
PacketCable NCS Protocol Specification, PKT-SP-EC-MGCP-I04-011221, December 21, 2001.
The Multimedia Terminal Adapters (MTAs) currently supported by the Cisco BTS 10200 include:
•
•
Motorola
TelIabs
Billing Data Generation Methods
The Cisco BTS 10200 Softswitch has the ability to provision billing support using either of the following
billing data generation methods:
•
Call Detail Blocks (CDBs)—This is traditional post-call billing data, which is assembled into Call
Detail Records (CDRs) by an external billing mediation system or billing server.
•
PacketCable event messages (EMs)—This is real-time call data flow, which is transferred to an
external Record Keeping Server (RKS) that assembles CDRs from the EMs.
The Cisco BTS 10200 must be provisioned to generate either EMs or CDBs, but not both.
Caution
Provision the Cisco BTS 10200 to generate either EMs or CDBs, but not both. Attempting to generate
both types of records simultaneously can significantly degrade the call processing rate. Refer to the
provisioning steps for the call-agent-profile command (below) to see how to turn EMs on and turn CDBs
off.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
5
New and Changed Information
CISCO CONFIDENTIAL
Provisioning the Cisco BTS 10200 Softswitch to Generate EMs
These steps provision the Cisco BTS 10200 Softswitch to generate EMs.
Note
The value for id shown in this section (CA146) is an example.
Step 1
Login to a CLI session on the Cisco BTS 10200 Softswitch.
Step 2
Use the following command to display the current values for the call-agent-profile table:
show call-agent-profile id=CA146;
where:
•
Step 3
id—Domain name of the specific Call Agent (CA), in the format CAnnn, where nnn = 3-digit
number previously assigned to the CA. This value is case-sensitive (for example, CA146 and ca146
are not the same). This is the unique identifier for this Call Agent (CMS) node, which was
permanently assigned at time of software installation on the Cisco BTS 10200 Softswitch.
If the system response indicates that this table does not exist, then you must create it using the following
command. Otherwise, the EM function is not supported and EMs will not be generated.
add call-agent-profile id=CA146; cdb-billing-supp=N; em-billing-supp=Y;
Caution
If the call-agent-configuration table is not created, the Cisco BTS 10200 Softswitch will generate CDBs
but not EMs.
Step 4
If the call-agent-profile table already exists, check (in the display from Step 2) to see if cdb-billing-supp
is set to N (no) and em-billing-supp is set to Y (yes). If not already shown in the display, enable EM
billing support by entering the following command:
change call-agent-profile id=CA146; cdb-billing-supp=N; em-billing-supp=Y;
where:
Caution
Step 5
•
cdb-billing-supp—Specifies whether to generate Call Detail Blocks (CDBs). The value of this
optional token is a single ASCII character (Y or N); the default value is Y (yes). The value of this
token must be set to N (no) if the Cisco BTS 10200 Softswitch is to provide event message
generation.
•
em-billing-supp—Specifies whether to generate PacketCable event messages. The value of this
optional token is a single ASCII character (Y or N); the default value is N (no). The value of this
token must be set to Y (yes) if the Cisco BTS 10200 Softswitch is to provide event message
generation.
Be sure the system is configured to generate either EMs, and not CDBs. Attempting to generate both
types of records simultaneously can significantly degrade the call processing rate.
Enter the following command to generate EMs based on CMS and MGC logical network elements, and
to specify the financial entity ID.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
6
OL-1835-04
New and Changed Information
CISCO CONFIDENTIAL
change call-agent-profile id=CA146; cms-supp=y; cms-id=12345; mgc-supp=y; mgc-id=67890;
feid=9876;
In the above command, use different (unique) IDs for cms-id and mgc-id.
Note
where:
•
cms-supp—Specifies if EMs are generated based on CMS functionality. The value of this optional
token is a single ASCII character (Y or N); the default value is N (no). Set this value to Y (yes).
•
cms-id—Specifies the 5-digit element ID of the CMS. The range of values is 0 through 99999.
This token is mandatory if the value of the cms-supp token is set to Y.
•
mgc-supp—Specifies if EMs are generated based on MGC functionality. The value of this optional
token is a single ASCII character (Y or N); the default value is N (no).
•
mgc-id—Specifies the 5-digit element ID of the MGC. The range of values is 0 through 99999.
This token is mandatory if the value of the mgc-supp token is set to Y.
•
feid—Financial entity ID (FEID) of the Cisco BTS 10200 Softswitch (CMS/MGC) that is included
in event messages sent to the RKS for billing purposes. PacketCable zones can be divided into one
or more logical financial entity IDs. A single CMS/MGC is assigned at most one FEID; however,
more than one CMS can be assigned the same FEID. This optional token becomes a mandatory token
if the cms-supp token, the mgc-supp token, (or both) are set to Y (yes).
Inter-Office Automatic Callback, Automatic Recall
Inter-Office Automatic Callback (AC) is an outgoing call management feature that allows a subscriber
to automatically setup a call to the last station (directory number or DN) called without having to redial
the number. If the called party is busy when AC is activated, call setup is automatically performed when
the called station becomes idle.
Inter-Office Automatic Recall (AR) is an incoming call management feature that allows a subscriber to
automatically setup a call to the last incoming number. The AR subscriber does not need to know the
calling number or the calling party of the last incoming call. If the party is busy when AR is activated,
call setup is performed automatically when the original calling station becomes idle.
Previous releases of the Cisco BTS 10200 Softswitch software supported the AC and AR features only
for calls between Cisco BTS 10200 Softswitch subscribers. The AC and AR features did not work for
calls between a Cisco BTS 10200 Softswitch subscriber and a subscriber at an external office or the
PSTN. To provide the AC and AR features between Cisco BTS 10200 Softswitch subscribers and
external subscribers, the Cisco BTS 10200 Softswitch communicates with the PSTN through SS7
Transaction Capability Application Part (TCAP) messaging. The AC and AR features are implemented
in the Cisco BTS 10200 Softswitch plain old telephone service feature server (FSPTC) using SS7.
The AC and AR features are not supported for interoffice calls during FSPTC switchovers. Subscribers
who activated these features before a switchover will not receive these services during or after the
switchover. This includes subscribers activating the AC and AR features on an interoffice call or PSTN
subscribers activating the AC and AR features on a Cisco BTS 10200 Softswitch subscriber. Subscribers
must repeat the activation procedure after the FSPTC switchover is complete.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
7
New and Changed Information
CISCO CONFIDENTIAL
T108 Test Line Support
The T108 test line feature is used for determining the performance of trunks connecting digital exchange
switches, including voice over packet (VoP) softswitches. Currently, Cisco BTS 10200 incoming trunks
requesting 100-type test lines are routed to shared test lines for the requested tests, regardless of which
gateway terminates the trunk or which gateway/IAD terminates the test line. The T108 test line feature
requests a test to be performed within the same gateway where the trunk under test (TUT) is terminated,
and provides a digital loopback within the gateway. The T108 test line feature supports manual and
automated testing.
Figure 1
T108 Test Line Operation
Near End
Switch
Far End
Switch
Incoming
Trunk
Termination
Switch
Matrix
ROTL
Or
Test
Position
Transmission
Facility
Outgoing
Trunk
Termination
Trunk Circuit
108
Test
Line
Incoming
Outgoing
Test Controller
(Optional)
Digital Test Pattern
Generator
Remote or Local
Test System
Digital
Test Receiver
The T108 test line sequence is as follows:
•
The near end switch originates the test sequence by placing a test call, identifying the trunk to be
selected, and the test line number. A digital test pattern generator, such as a Sage 930A, is used in
the test setup shown in Figure 1.
•
The near end switch uses the trunk identifier to override normal call processing and select only the
requested trunk.
•
The far end switch responds to the destination number and connects to the T108 test line. The T108
test line enables a digital loopback.
•
When the near end receives answer supervision, it conducts digital test sequences to ascertain trunk
performance.
•
Once the test sequences are completed, the near end releases the test call and both switches release
the trunk connection.
•
The far end switch can detect if the test connection exceeds a preset time, and releases the test
connection if the preset time is exceeded.
The T108 test line is also used for trunk redirection (wholesale dial) for Internet services where the
carrier modem termination is integrated into the trunk gateway. In this case, the integral digital stored
program (DSP) normally supports modem-only transmissions.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
8
OL-1835-04
New and Changed Information
CISCO CONFIDENTIAL
The T108 test line feature involves the following external interfaces:
•
Alarms
No alarms are changed or added with this feature.
•
Billing Interface
No changes. The billing system currently collects data for test-type calls.
•
Operator Interface
Added—CLI command to set a global 108 test call timer in minutes (range of values is 0 through
60 minutes, default = 20 minutes)
Example: change ca-config type=test-call-tmr; datatype=integer; value=10;
Added—CLI command to add/change/delete 108 test call capability for each connected gateway
Example: change destination dest-id=dallasaustin; call-type=lb-test;
8XX Enhancement with NOA Processing
Effective with Release 3.3 V04, the Cisco BTS 10200 Softswitch supports network-specific Nature of
Address (NOA) processing for outbound 8XX toll-free calls. To implement this feature, the service
provider provisions the NOA token in the dial plan table.
The system processes outbound 8XX calls as follows:
•
The CA signals the AIN FS to perform an 8XX query.
•
The AIN FS performs an internal database query.
– If an internal record is found for the 8XX number, the AIN FS provides the routing information
to the CA and the call is attempted.
If the AIN FS query finds a record for a network-specific 8XX call in the internal database, the
Database Query Type1 is set to 2 (TOLL_FREE_LOCAL) in the resulting call detail record (CDR).
– If no internal record is found for the 8XX number, the next action depends on how the NOA
token is provisioned in the dial plan table:
•
If the NOA token is provisioned as NATIONAL, the AIN FS performs an external service
control point (SCP) query.
If a route is found, the CA completes the call. Otherwise the call is released.
•
If the NOA token is provisioned as network-specific, the call is released.
The release cause is “No Route to Destination.”
The valid values for the NOA parameter in the dial-plan table for a toll-free call are as follows:
•
NATIONAL
National (significant) number
•
NS0 through NS6
Network-specific (as provisioned)
Provisioning Examples
Add dial-plan id=dp1; digit-string=888; noa=NATIONAL; dest-id=dest888nat;
Add dial-plan id=dp1; digit-string=888; noa=NS0; dest-id=dest888ns0;
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
9
New and Changed Information
CISCO CONFIDENTIAL
Provisionable CLLI Codes
This section describes the COMMON LANGUAGE® Location Identifier1 (CLLI™) Code feature
implementation for the Cisco BTS 10200 Softswitch.
The COMMON LANGUAGE® Location Identifier (CLLI™) code is an 11-character descriptor field
assigned to a Class 4 or Class 5 switch.
The format of CLLI Code is T1T2T3T4S1S2B1B2U1U2U3 where,
T1
T2
T3
T4
S1
S2
Town (1st character)
Town (2nd character)
Town (3rd character)
Town (4th character)
State (1st character)
State (2nd character)
B1
B2
U1
U2
U3
Building (1st character)
Building (2nd character)
Building Subdivision (1st character)
Building Subdivision (2nd character)
Building Subdivision (3rd character)
The CLLI feature includes the following functions in Release 3.3 V04:
•
New tokens in the Call Agent table and Trunk Group table
•
Provide CLLI code information in the CVR message
•
Display CLLI code of the responding switch in response to a CVT message
•
Provide originating and terminating CLLI codes in the billing record
New CLI Command Tokens
The following CLI command tokens are added in this release:
Own Switch Identification
The CLLI code identifying the local Cisco BTS 10200 Softswitch is provisioned in the Call Agent table.
Provisioning of the CLLI token is optional.
Example: change call-agent id=ca145; clli=dalltxrcdn5;
Remote Switch Identification
The Cisco BTS 10200 uses the CLLI code of the remote switch for populating the call detail block
(CDB) in the billing record and for circuit validation testing. The CLLI code identifying the remote
switch (the switch at the far end of the trunk group) is provisioned in the TG table.
Provisioning of the CLLI token is optional.
Example: change trunk-grp id=101; clli=denvcorsch3;
Circuit Validation Messages
The Cisco BTS 10200 supports sending and receiving of circuit validation response (CVR) messages. A
CVR message is sent in response to circuit validation test (CVT) message. The implementation is based
on information in document GR-317-CORE, LSSGR: Switching System Generic Requirements for Call
Control Using the Integrated Services Digital Network User Part (ISDNUP), Issue 3 (Telcordia,
November 1999).
1. COMMON LANGUAGE is a registered trademark and CLLI is a trademark of Telcordia Technologies
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
10
OL-1835-04
New and Changed Information
CISCO CONFIDENTIAL
Sending Circuit Validation Response (CVR) Message
If the CVT is “successful”, and if both the local CLLI code (own) and remote CLLI code are available,
the circuit identification name parameter is coded as shown in Figure B-17, Appendix B
[GR-317-CORE], and is included in the CVR. If the circuit identification name is not available, this
parameter is omitted.
If the CVT fails (CVR indicator octet is coded as “failed”) and if the own CLLI code is available, the
CLLI code parameter of the CVR is coded as shown in Figure B-18, Appendix B [GR-317-CORE], and
is included in the CVR. If the CLLI code is not available, this information is omitted.
Receiving Circuit Validation Response (CVR) Message
When the operator initiates a diagnostic CVT command, the success or failure of the CVT command is
displayed as follows:
•
If the CVR message is received with a successful CVR indication, the following requirements apply:
– R3-148 [GR-317-CORE]: If a CVR is received before the CVT timer expires with a
“successful” circuit validation response indication, the CLLI code information in the circuit
identification name parameter in the CVR need not be checked (against the corresponding
information at the SPCS initiating the test) and shall not cause the CVT to fail.
– R3-149 [GR-317-CORE]: If the applicable one-way trunk group or two-way trunk group
requirement for CVT/CVR is not satisfied, the CVT has failed and maintenance shall be notified
of the failure. If the circuit identification code has been received, it is also reported with the
failure indicator to the operator.
•
If the CVR message is received before the CVT timer expires with a “failed” CVR indication,
maintenance should be notified that the test has failed. If the CVR message contains the CLLI code
parameter (see Figure B-18, Appendix B [GR-317-CORE]), the received CLLI code is included in
the failure indicator to the operator.
Billing Interface
The billing call data block (CDB) contains the parameters OCLLI (CLLI of the originating TG) and
TCLLI (CLLI of the terminating TG).
Alarms
If a CVT message is received for an invalid CIC, the system generates a minor alarm.
If a CVR message is received with a failed indicator, or is failed locally, the system also generates a
minor alarm.
Measurements
The following measurements are supported:
•
Number of CVT messages transmitted
•
Number of CVT messages received
•
Number of CVR messages transmitted
•
Number of CVR messages received
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
11
New and Changed Information
CISCO CONFIDENTIAL
Digit Manipulation Table
The Digit Manipulation (digman) table is a new table added in the Cisco BTS 10200 Softswitch in this
release to support digit manipulation. Digit manipulation was previously done in the dial plan table using
pfx_digits and del_digits, but it was available only on the called party number. With the introduction of
the digman table, the Cisco BTS 10200 Softswitch is now able to handle digit manipulation of both the
calling party and called party numbers.
The following is a brief overview of what the digman table provides for the Cisco BTS 10200 Softswitch.
Digit/NOA manipulation rules can be applied to:
•
Directory Number (calling number or called number)
•
Nature of Address (NOA) (calling number or called number)
•
Both DN and NOA
Digit manipulation can take place at several points in call processing, including:
•
Pre-translations—In the pre-translations stage, the dial-plan-profile table is used to specify if ANI,
DNIS, or both are to be manipulated. The purpose of the pre-translation stage is to normalize the
digits as required during the translations stage.
•
Translations—The dial-plan table can be used to manipulate the called party number. Simple
Delete / Prefix function is supported.
•
Routing—Routing is performed in the Analyzed Info PIC (Point In Call). The destination table
and/or route table can be used to specify digit manipulation of ANI, DNIS, or both. The out-pulsing
number can be normalized using the destination table. In addition, if special manipulation is
required based on the route selected, it can be specified for each Trunk Group within a route.
If the called number terminates within the Cisco BTS 10200 Softswitch, and the subscriber number
points to a Trunk Group, then digit manipulation rules for ANI, DNIS, or both can be specified in
the Trunk Group table.
If the call is an interLATA call or requires Carrier Routing, the ANI/DNIS digit manipulation IDs
specified in the destination table are ignored and carrier based routing is performed.
Note
Although pfx_digits and del_digits still work in the dial plan table, if the system supports 7-digit
dialing and the number is an LNP number, then you must put the digit manipulation in the digman
table and reference the entry from the dial plan profile table.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
12
OL-1835-04
New and Changed Information
CISCO CONFIDENTIAL
Hardware Changes
There are no hardware changes in Release 3.3 V04.
Software Changes
The following sections detail the software changes made in Release 3.3 V04.
SNMP Interface
Replace Chapter 3, “SNMP Interface,” pages 3-1 through 3-4 of the Cisco BTS 10200 Softswitch
Operations Manual for Release 3.1, with the text on the following four pages.
Overview
The Cisco BTS 10200 Softswitch supports Simple Network Management Protocol (SNMP) operations that
provide communications between the EMS and a service provider's network management system (NMS).
The EMS sends SNMP traps to the NMS, and the NMS can query the EMS for specific data elements, as
illustrated in Figure 3-1. Status and control operations are also supported.
Figure 3-1
NMS/EMS Interaction Via SNMP
NMS
GET
GETNEXT
GETBULK
SET
EMS
54389
TRAPS
EMS (SNMP Agent)
The Cisco BTS 10200 Softswitch SNMP agent supports SNMPv2c operations defined by the
opticall.mib Management Information Base (MIB). The opticall.mib file is located in the directory
/opt/BTSsnmp/etc on the EMS. The opticall.mib file uses variables from three other MIBs: IPCELL-TC,
SNMPv2-TC, and SNMPv2-SMI. When the NMS loads the main MIB (opticall.mib), it will import the
other three MIBs.
SNMP Agent Functions
The following functions are supported by the Cisco BTS 10200 Softswitch SNMP Agent:
•
Collection of statistics and traffic management data
•
Status and control
•
SNMP trap reports
Read access to the SNMP agent is required for the statistics and traffic management queries and for
status queries. Write access is required for the control commands. Trap reports do not involve read/write
access.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
13
New and Changed Information
CISCO CONFIDENTIAL
Read/write access to the SNMP agent is restricted by requiring the NMS to pass a valid community string
to the agent. The community string passed in by the NMS message is authenticated against a list of
community strings maintained by the SNMP agent. The SNMP agent uses each string as a password, and
disallows access if the password is not valid.
The SNMP community table in the Cisco 10200 Softswitch database provides persistent storage of
community strings for the SNMP agent. The default value for both the read and write communities is
“public”. This default value can be deleted by the user and replaced with specific communities using the
following CLI commands:
•
To show all read communities—show snmpconfig type=READCOMMUNITY
•
To show all write communities—show snmpconfig type=WRITECOMMUNITY
•
To add read community—add snmpconfig type=READCOMMUNITY; value=.....
•
To add write community—add snmpconfig type=WRITECOMMUNITY; value=.....
•
To delete read community—delete snmpconfig type=READCOMMUNITY; value=.....
•
To delete write community—delete snmpconfig type=WRITECOMMUNITY; value=.....
The provisioned values must be ASCII strings and can be up to 64 characters long.
Note
The READCOMMUNITY, WRITECOMMUNITY, and PUBLIC tokens in the SNMP community
table are case insensitive beginning in Release 3.3 V04. These tokens can be entered in uppercase,
lowercase, or any combination of the two.
Statistics/Traffic Measurement
Statistical data (traffic measurements) are collected for the following components of the Cisco BTS 10200
Softswitch:
•
AIN Feature Server
•
Billing
•
Call Processing
•
ISDN
•
ISUP
•
MGCP Adapter
•
POTS / Feature Server
•
SIA
•
SIM
•
SNMP
•
Trunk group usage
•
Announcement
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
14
OL-1835-04
New and Changed Information
CISCO CONFIDENTIAL
SNMP Trap Reports
Traps are sent from the Cisco BTS 10200 Softswitch SNMP agent to the NMS. Traps are mapped to all
alarms generated from the EMS. Any alarms that cannot be mapped to a specific trap are mapped to a
generic trap. Mapped traps and generic traps contain one or more of the following information types,
depending upon availability of the information:
•
Severity level
•
Alarm ID associated with the trap
•
Alarm category
•
Set/Cleared flag
•
Component (instance) ID
•
Component type
•
Details of the trap
•
Time that trap was generated
An operator of an NMS who would like to receive traps from the SNMP agent needs to add an entry with
the following parameters to the SNMPTRAPDEST table using the command line interface (CLI). For
more information on the specific CLI add command, refer to Chapter 31, “SNMP Trap Destination,” in
the Cisco BTS 10200 Command Line Interface Reference Guide for Release 3.2 and Release 3.3 V04.
•
Index (1 to 2147483647)
•
IP address or hostname of the NMS
•
Port number on which to receive traps
•
Community string—(currently not used)
•
Owner string—(currently not used)
•
Filter types (0 to 32767 - default: 32767)
The filter types parameter is a 10-bit bitmask specifying the event types to filter and send to this
address. The filter types parameter is used in combination with the filter levels parameter to provide
a user-definable granular filter for traps from the SNMP agent.
– For example, in order to send only CONFIG, DATABASE, and SIGNALING event types, the
binary filter is 0010001100, which converts to an integer value of 140. This integer value is
entered as the token value in the CLI command (filtertypes=140).
– If all event types are to be sent, the binary filter is 1111111111, which converts to an integer
value of 1023. The integer value is again entered as the token value (filtertypes=1023).
– If no event types are to be sent, the binary filter is 0000000000, which converts to an integer
value of 0 as the token value (filtertypes=0).
•
Filter levels (0 to 63 - default: 56)
The filter levels parameter is a 6-bit bitmask specifying what event levels to filter and send to this
address. The filter levels parameter is used in combination with the filter types parameter to provide
a user-definable granular filter for traps from the SNMP agent.
– For example, in order to send only INFO, MINOR, and MAJOR event levels, the binary filter
is 011010, which converts to an integer value of 26. The integer value is entered as the token
value (filterlevels=26).
– If all event levels are to be sent, the binary filter is 111111, which converts to an integer value
of 63. The integer value is again entered as the token value (filterlevels=63).
– If no event levels are to be sent, the binary filter is 000000, which converts to an integer value
of 0. The integer value is again entered as the token value (filterlevels=0).
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
15
New and Changed Information
CISCO CONFIDENTIAL
These values can also be viewed (read-only) using the NMS. The tree hierarchy is
enterprises.ipcell.opticall.generalTraps.trapDestTable.
When this entry is made in the SNMPTRAPDEST table, the NMS can start receiving traps.
It is the responsibility of the NMS operator to apply any additional filters to the traps that are received
on the NMS if more granular filtering is desired. It is also the responsibility of the NMS operator to filter
the traps that are displayed on the NMS and those that are discarded.
Procedure to Set Up Time and Weather Call Type
The following procedure for setting up a Time and Weather Call Type is provided in response to
CSCdy31912.
To set up a time and weather number, complete the following steps:
Step 1
A time and weather dial plan must be created for the feature to work. To add a dial plan for time and
weather, enter the following command:
CLI> add dial-plan id=dp1; digit-string=301-844; REQD_DIGITS=10; DEST_ID=inter-rte-3333;
Note
Step 2
A dial-plan-profile must be added before you can add a dial-plan id. See the Cisco BTS 10200 Softswitch
Operations manual for the procedures for adding a dial plan and a dial plan profile.
To add a special call type for time and weather (TW), enter the following command:
CLI> add special-call-type digit-string =844; call-type=TW; description=Time and Weather;
Step 3
Verify that a digit-string for time and weather was added with a call type of TW by entering the following
command:
CLI> show special-call-type digit_string=844;
Reply: Success: 1 entry found.
DIGIT_STRING=844
CALL_TYPE=TW
DESCRIPTION=Time and Weather
Procedure for Equal Access Routing
This procedure defines how to setup a subscriber and the Cisco BTS 10200 Softswitch for equal access
dialing based on inter-exchange carrier (IXC) carrier PIC. This applies to direct dialed domestic (DDD)
and international direct dial domestic (IDDD) dialing and dial plans. This procedure can also be applied
to local service provider equal access using the PIC2 field in the Cisco BTS 10200 Softswitch subscriber
table.
This procedure assumes that all residential gateways, trunking gateways, and all other translations
support the commands below.
For general carrier and US domestic dialing information see http://www.nanpa.com
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
16
OL-1835-04
New and Changed Information
CISCO CONFIDENTIAL
To set up a subscriber for equal access routing, complete the following steps:
Step 1
Add the carrier ID. This sets the carrier up and puts it in-service.
add CARRIER ID=0288; STATUS=INS; INTER=Y; INTRA=Y; INTL=Y; CASUAL=Y; CUT-THRU=Y;
OP-SERVICES=Y; SEND-CN=N; SEND-CSP=Y; USE-DIAL-PLAN=N;
Step 2
Change PIC1 to the appropriate interlata and international carrier PIC. This pre-subscribes a subscriber to
a carrier so the subscriber does not have to dial 101+4 digit carrier code + the number to make the call.
change subscriber; id=motfb4/1;name=John Doe;PIC1=0288;PIC2=NONE;PIC3=NONE;
Step 3
Add an interlata dummy route. This is required to set up a dial plan.
add route id=EA-IXC;lcr=n;tgn1-id=null;
Step 4
Add a route-guide. This is also required to set up a dial plan.
add route-guide id=EA-IXC;policy-type=route;policy-id=EA-IXC;
Step 5
Add a destination for interlata calls. This is also required to set up a dial plan.
add destination dest-id=Interlata-IXC;call-type=InterLata;route-type=route;
route-guide-id=EA-IXC;
Step 6
Add dial plan entries for all US supported NPAs. This allows verification that a subscriber can call a
particular NPA.
add dial-plan id=dp-mot;digit-string=201;reqd-digits=10;dest-id=Interlata-IXC
Step 7
Add an international dummy route. This is required to set up an international dial plan.
Add route id=INTL-IXC;lcr=n;tgn1-id=null
Step 8
Add the international route-guide. This is also required to set up an international dial plan.
add route-guide id=INTL-IXC;policy-type=route;policy-id=INTL-IXC;
Step 9
Add the international destination. This is also required to set up an international dial plan.
add destination dest-id=INTL-IXC;call-type=INTL;route-type=route;route-guide-id=INTL-IXC;
Step 10
Add international dial-plans for all supported country codes. This allows verification that a subscriber
can call a particular country.
add INTL-DIAL-PLAN ID=RTP01; CC=34; MIN-DIGITS=6; MAX-DIGITS=16;dest-id=INTL-IXC
Step 11
Add the SS7 Feature Group D (FGD) equal access trunk group to the IXC switch. This builds a trunk to
the next service provider.
add ss7-tg-profile id=IXC-FGD; type= A7; cot-orig=y; cot-freq=10;T-IAM=20;
add trunk-grp id=205;call-agent-id=CA146; tg-type=ss7;
dpc=214-110-205;traffic-type=tandem;
sel-policy=DSC;glare=all;tg-profile-id=IXC-FGD;dial-plan-id=Incoming;No-answer-tmr=240;CLL
I=RLGHIXC;
Note
Step 12
Consult GR-394 for SS7 parameters that must be sent in SS7 messages through the FGD interface.
Add the SS7 trunks to the IXC switch. This sets up the actual bearer channel.
add trunk cic-start=1; cic-end=24; tgn-id=205; mgw-id=C0201_VISM5;
termination-prefix=vism/t1-1/; termination-port-start=1; termination-port-end=24;
equip trunk-termination tgn-id=205; cic=1-48;
Note
This assumes that the trunks will be controlled in service when ready.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
17
Enhancements
CISCO CONFIDENTIAL
Step 13
Add the route to the IXC switch. This provides the path to the service provider providing equal access.
add route id=SS7-IXC;lcr=N;tgn1-id=205;
Step 14
Add the route-guide to the IXC switch. This is required to route to a service provider.
add route-guide id=SS7-IXC;policy-type=route;policy-id=SS7-IXC;
Step 15
Add the route-guide to the Carrier table. This provides the path to route directly to a service provider.
change CARRIER ID=0288; STATUS=INS; INTER=Y; INTRA=Y; INTL=Y; CASUAL=Y; CUT-THRU=Y;
OP-SERVICES=Y; SEND-CN=Y; SEND-CSP=Y; USE-DIAL-PLAN=N; route-guide-id=SS7-IXC;
Note
Step 16
The parameters datafilled above may differ based on the IXC carrier, however, this should be typical data
fill for most IXCs.
Add circuit code (only if the TNS parameter is required).
add circuit-code tgn-id=205; nat-cc=9; opr-cc=14; nat-opr-cc=14; sac-cc=9; da-cc=9;
Note
The parameters datafilled above may differ based on the IXC carrier, however this table is datafilled
only if there are special requirements. The Cisco BTS 10200 Softswitch default values work for most
IXCs.
Enhancements
The section describes enhancements that have been incorporated into the Cisco BTS 10200 Softswitch
software in Release 3.3 V04. The DDTS IDs listed in Table 1 are Cisco internal tracking numbers.
Table 1
Enhancements
DDTS ID
Headline
Enhancement
CSCdw63217
Security enhancements
RequestLogger is enhanced to include a new interface which
allows classes outside of the CPI to log command history.
The EMS supports an entry in the command history to indicate
that a user has logged into or out of the BTS 10200, which
contains the user name, time, date, and terminal information.
The CMS adapter logs all transactions in the command history.
As a result, most event level items are stored in this history. In
addition, an invalid login attempt or use of an invalid security
certificate, are also logged in the command history.
CSCdw79719
State token for add/delete/show command The show command is enhanced so that it shows the status of
event-queue
both the active and standby states.
CSCdx21154
RHM monitors /tmp disk space
RHM is enhanced to periodically monitor the /tmp disk space
and platform is shut down when the /tmp disk space reaches the
critical threshold.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
18
OL-1835-04
Enhancements
CISCO CONFIDENTIAL
Table 1
Enhancements (continued)
DDTS ID
Headline
Enhancement
CSCdx25215
Platform start script now backs up the data When a platform goes down or is switched over due to an
directory
abnormal condition, trace logs alone are not sufficient to
determine the root cause of the problem. Shared memory data
would be useful; however, if the system is restarted before the
data directory is saved, this important data is lost.
The platform start script is enhanced so that the PMG
automatically saves a copy of the data directory when the
platform starts. The recommended practice is to keep two
backup copies in case an original fault is followed by a
secondary fault in start up.
This enhancement provides additional help for TAC and
Cisco BTS 10200 support in identifying problems in the field.
CSCdx35680
Register new events for TCAP
Alarm events for the SCCP, TCAP, and INAP layers have been
added for the TCAP framework.
CSCdx43263
A new process EMA has been added
A new process, PacketCable Event Message Adapter (EMA),
has been added in the Call Agent.
CSCdx44927
CALEA requirements for abandoned calls When a station provisioned for surveillance on the Cisco BTS
10200 Softswitch makes a call that's abandoned without dialing
any digits or after dialing some digits, an origination message
and release message are expected at the LEA.
In the partial dial situation, the customer entered digits field
should contain the partially-dialed digit string. The availability
of partial digits is dependent on the digit map downloaded to
the access device and if a critical timer expired or was canceled
by entering a “#.”
CSCdx46511
Diagnostic ss7-trunk-termination test=4
modified to show local or remote state
The diagnostic ss7-trunk-termination test=4 (CQM) has been
modified to show local or remote state.
CSCdx48883
Support now available for 0+7D dialing
A hard coded check to not allow 0+7D calls has been removed.
The LOCAL-7D-DIALING flag in the POP table should be set
to “Y”. The ZERO-PLUS flag in the DESTINATION table must
also be set to “Y.”
The DNIS-DIGMAN-ID must be set up to prefix NPA or the
DIAL-PLAN table should be set up to prefix NPA. The digit
map needs to be modified to replace 0[2-9]xx[2-9]xxxxxx with
0[2-9]xxxxxx.T|0[2-9]xxxxxxxxx).
CSCdx53249
PMG enhanced to check process status
more often in some circumstances
Previously PMG checked process status once every second
during bring up and switchover. This time interval has been
decreased so that PMG detects process status more often and
thereby decreases switchover time.
CSCdx67757
Perform pstack dumps only if necessary
making switchovers faster
The CREATE_THREAD() function in IPC has been enhanced:
1. pstack dumps are done only when the number of threads
cancelled is not equal to the number of threads created.
2. end_all_threads() sleeps only as long as the number of threads
cancelled is not equal to the number of threads created.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
19
Enhancements
CISCO CONFIDENTIAL
Table 1
Enhancements (continued)
DDTS ID
Headline
Enhancement
CSCdx67773
Apache server also installed on Call Agent The Apache Server is now installed on CA boxes, but it is not
boxes
started via inittab; initially it is started manually.
CSCdx74854
Provision the desired Solaris services for
security
The user of the CLI, MAC, CORBA, FTP, and other user
interfaces can now enable or disable standard UNIX (Solaris)
services on the Cisco BTS 10200 Softswitch. This feature does
NOT support configuration of the resources, just whether they
are enabled or disabled based on the current configuration.
The services covered in these new commands include FTP,
Telnet, echo, discard, daytime, chargen, SMTP, time, finger,
sunrpc, exec, login, shell, printer, uucp, nfs, lockd, X11, dtscp,
font-service, and http.
Please note that since users are still allowed to logon to the
system as “root,” that any means to control these services can
be bypassed by an operator working as “root.”
CSCdx75026
CPI interface provides help information
for Cisco BTS 10200 commands.
The CPI interface now provides preformatted text designed to
be displayed without modification. The CPI help mechanism
provides information about using the help mechanism.
For help on a given command noun, which consists of a list of
all commands related to a given table, this mechanism provides
a URL reference to the Cisco BTS 10200 Softswitch Command
Line Interface Users Guide.
For help on a specific command noun/verb pair, this provides:
•
•
•
•
•
a list of all parameters sorted into groups of “Required” and
“Optional/Conditional” parameters
the data format is described or, for those parameters which
require a value, the list of permitted values is provided
the default value for the parameter is provided, if one exists
if the parameter is associated with a database column that
has a foreign key constraint, this dependency is provided
all related commands are listed for each help request
One parameter is supported: VERB = a valid verb. % is not
allowed.
Support for this verb is hard-coded in ManagedObject.java to
avoid significant changes to the CommandParameter table.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
20
OL-1835-04
Enhancements
CISCO CONFIDENTIAL
Table 1
Enhancements (continued)
DDTS ID
Headline
Enhancement
CSCdx75032
An IP alias can be defined for the active
EMS on the telnet interface
This new feature allows the user to define an interface that can
migrate between ACTIVE EMS application instances. This
interface can be used by OSS operators to direct all activity to
the ACTIVE EMS and not be concerned with which EMS is
active.This does not impact direct access to either node, so the
user can still access the specific nodes as required.
Since this feature could be impacted by changes to the customer
OSS network, this information is provisioned. A CLI command
is used to manage the values for the IP alias. This information
is then applied by the system manager process (SMG). Once
provisioned, this information is equalized between the EMS
instances.
CSCdx75253
Platform supports system time change
notification
Platform monitors system events and reports them to registered
threads. The platform also monitors changes in system time and
notifies the registered threads via IPC messages.
CSCdx76071
PMG supports SS7 and NON-SS7 AIN
platforms.
Process Manager (PMG) now supports both SS7 and
NON-SS7-related shared memory creation.
As part of this release new shared memory is to be created.
The shared memory creation API exposed to the PMG is
changed. PMG uses this new shared memory created APIs
and includes the SS7-related Include files.
2. In this release, the PMG need not link to the ACG library
as creation of shared memory for ACG is now provided by
the SHM library in fsain.
3. Same holds for RDM Makefile
4. A new entry is made in Mem.cfg for ASM aggregated
parameters.
1.
CSCdx76541
Allow 50 sessions with variable timeout in This release provides 50 concurrent sessions and a
SMG
provisionable time-out value of 10 to 30 minutes.
CSCdy05673
Set default slack term value in Gate Set
message
CSCdy05682
Incorporated T7, T8 timers as required by T7 and T8 timers have been added to the CA-config table. The
PacketCable ECR-2095
T7 and T8 timers are set in the Gate Set message sent to the
CMTS, using the new Gate Set message format.
CSCdy05691
After switchover, GATE-INFO is sent to
audit active gates
A provisionable “slack term” value is provided in the Gate Set
message to a CMTS. The user can provision a default “slack
term” value in the CA-config table. BTS will set the value in the
Gate Set message.
Following a switchover, GATE-INFO is sent to the CMTS to
audit active gate status to avoid hung gates.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
21
Enhancements
CISCO CONFIDENTIAL
Table 1
Enhancements (continued)
DDTS ID
Headline
Enhancement
CSCdy10774
The named.conf file is overwritten during When upgrading to a new version of the Cisco BTS 10200, the
upgrade
/etc/named.conf file might be overwritten.
This file should be backed up before performing an install or
uninstall of the software. The file name used for the backup file
should not be /etc/named.conf.orig.
If the upgrade has already been performed, and the platform
will not start due to nslookup errors, the /etc/named.conf file
must be manually corrected.
Changes are made to uninstall.sh to not restore the named.conf,
resolv.conf, system, and inetd.conf files in order to keep user
changes, if any.
CSCdy22056
Date command without arguments does
not return date and time
The /bin/date script has been modified to return the current date
and time (by calling /bin/.date) if it is called without arguments.
It prints an error message if it is called with arguments, which
indicates an attempt to change the date/time.
This allows the “trivial case” use of the date command, while
preventing the user from arbitrarily changing the date/time.
CSCdy22420
EMA supports time change and replication Support has been added to the Event Message Adapter (EMA)
of BCM event counter
for the following:
1.
2.
Reporting NTP time change to the RKS
Replicating BCM's event counter (used in BCID
generation) to the standby side so that BCM uses
appropriate event counters after a switchover occurs.
CSCdy27392
PacketCable EM time change provided for Time Change message is sent by the BTS to the RKS when the
Daylight Savings Time.
local time is changed due to Daylight Savings Time changes.
CSCdy67940
COPS GATE-SET Event-Generation-Info On COPS GATE-SET messages, in Event-Generation-Info, the
flag setting
flag should be set as 0x01. If the flag is set as 0x01, the CMTS
accumulates event records as part of a batch file and sends them
to the RKS at periodic intervals.
CSCdz13178
RDM has to report replication status to
nodestat
RDM has to report replication status (such as port /ip address
used, connection status, current replication status [such as DB
Copy or Call data updates]) to the nodestat.
CSCic05344
IPC pool status in the PDM tool is now
displayed properly
IPC pool status was displayed as numbers. A meaningful string
(allocated, dispatched, retrieved) is now displayed.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
22
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Caveats
Caveats describe unexpected behavior in the Cisco BTS 10200 Softswitch software Release 3.3 V04.
This section describes two types of caveats:
•
Open Caveats, page 23
•
Resolved Caveats, page 39
Open Caveats
The open issues existing in Cisco BTS 10200 software release 3.3 V04 are described in Table 2.
The DDTS ID numbers listed in Table 2 are Cisco internal tracking numbers.
Table 2
Open Caveats
DDTS ID
Description
Workaround
CSCdx02249
Secondary CA does not come up after
switchback
Symptom: If a second switch-over occurs shortly after the
initial switch-over, OMNI is not stabilized and the CA will not
be in a proper working state.
Impact: Calls that use SS7 signaling cannot be completed.
Conditions: A switch-over occurs. OMNI is not yet stabilized
when a second switch-over occurs and the switch-back “kills” it.
Workaround: The platform does not update last-switch-over
time, so be sure to wait at least 10 minutes after a switch-over to
let OMNI stabilize before attempting another switch-over.
CSCdx05784
Duplicated CDR records for the same
call.
Symptom: Duplicate billing records are recorded.
Impact: The billing record for a single call can appear in the
billing data more than once. The duplicate records are visible
both in the billing FTP file and in the output of the report
billing-record command.
Conditions: This problem is seen in conjunction with BILLING
29 (CDB Send failed) alarms. The BILLING 29 alarms may, in
turn, be instigated by running the report billing-record
command.
Workaround: Duplicate billing records can be identified by
examining the “OverallCorrelationId” field of the billing
record(s). If two records have the same overall correlation ID,
they are duplicates.
Note: Correlation IDs can repeat for unrelated calls, but this
should only happen approximately 2**32 (4,294,967,296)
records after a given correlation ID first appears.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
23
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdx07689
Temp Rel fails on FWD offnet calls.
Symptom: When a call is forwarded out ISUP due to certain
feature like CFB,CFNA, etc.and the originator hangs up at the
exact time the call is forwarded, then an abandon is sent to the
ISUP and ISUP sends in a temp failure for the call.
Impact: There is no negative impact for this issue, the call is not
dropped.
Conditions: This only exists on calls forwarded out ISUP where
the originator abandons the call.
Workaround: None.
CSCdx08615
BCM should not send RLC until call
completed.
Symptom: BCM sends RLC before call is actually completed.
Impact: Call is prematurely terminated.
Conditions: BCM should not send a RLC until the call is
completely deleted.
Workaround: Hang up and place call again.
CSCdx27042
Billing server trap has varbind=ignore.
Symptom: FTP of files to billing server is unsuccessful.
Impact: Files must be re-sent.
Conditions: When the billing- server attempts to FTP the files
to the configured billing server address and there is a problem,
the EMS will send a trap indicating that there was a problem.
However, this trap has a varbind which tells the trap manager to
ignore it based on the MIB.
Workaround: None. MIB will have to be changed.
CSCdx47728
The CA sends the wrong r value under
CRCX.
Symptom: The subscriber is in faulty state.
Impact: The IAD responds with a 524 response for the MDCX,
Note: This introduces a new requirement, putting the subscriber in faulty state.
Use the “r:xx” parameter coming from
Conditions: The gateway sets the “r:” parameter to the default
AUEP to perform the create connection
value “be” if it is not included in the MDCX message. This
action (CRCX).
default value conflicts with the value in the CRCX message.
The CA, when sending a CRCX for a CFNA to a subscriber,
sends “r:cl” instead of “r:be,” which was originally sent by the
AUEP from the IAD.
Workaround: This could be fixed from the gateway by not
assuming the default value if the “r:” parameter is not included
in the MDCX message.
From the CA, provision the subscriber to always use the “be”
value.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
24
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdx51589
Digit parser not working correctly for
table ani-wb-list
Symptom: Inserting hyphens in a digit string results in an
“invalid length” error.
Impact: Cannot use hyphens in digit strings.
Conditions: Hyphens should not be included in the total length
of a digit string.
Workaround: None. (Increase length field by 3 characters.)
CSCdx52231
Digit parser not working correctly for
table changed-number
Symptom: Inserting hyphens in a digit string results in an
“invalid length” error.
Impact: Cannot use hyphens in digit strings.
Conditions: Hyphens should not be included in the total length
of a digit string.
Workaround: None. (Increase length field by 3 characters.)
CSCdx53378
Digit parser not working correctly for
table cust-grp
Symptom: Inserting hyphens in a digit string results in an
“invalid length” error.
Impact: Cannot use hyphens in digit strings.
Conditions: Hyphens should not be included in the total length
of a digit string.
Workaround: None. (Increase length field by 3 characters.)
CSCdx61610
CLI used to change termination and
shared memory is corrupted
Symptom: When using the CLI to modify the termination, the
CLI response is successful; however, shared memory is not
being updated as expected.
Impact: Trunk-idx is 0 and call fails.
Conditions: Check shared memory used in ./ca_... ./data
termination table (38) and shown trunk-idx is 0. Off-hook from
SAGE got no response from CA.
Workaround: Delete the terminations and add them back again
with the correct information.
CSCdx66743
AC not working when Switch FSPTC
from primary to secondary
Symptom: Automatic-Callback and Automatic-Recall features
are not supported for inter-office calls when the FSPTC switches
over.
Impact: Subscriber who activated any of these features before
the switchover will not receive the service.
Conditions: Subscriber activating AC/AR on an inter-office
call, and FSPTC switches over, or PSTN Subscriber activating
AC/AR on BTS10200 subscriber, and FSPTC switches over.
Workaround: Subscriber needs to repeat the activation
procedure after FSPTC switchover is complete.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
25
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdx76010
Call data not replicated on failover,
resulting in CIC state mismatch
Symptom: Both IRDP (ISL) links failed on the primary side (side
A) causing a switchover to the secondary (side B).
Note: The root cause of this problem is
the platform stopping the “replication
pipe” when it detects a fault on the Active
side, so there is always possibility of the
RDM queue not being flushed.
Impact: Both sides of the CA lost communication due to the loss
of the dual redundancy link, thus preventing RDM from
replicating the CIC states.
Conditions: During failover some of the processes, such as
S7M/S7A/BCM, are still processing callp messages received
Also, since the peripheral (adapter)
from the far end. Some of these callp messages, in turn, resulted
processes are not stopped immediately, it in releasing of stable calls. Since the RDM was not able to
is also possible for adapters to process
replicate some of this data (for example, an active call becoming
some of the signaling messages and
IDLE), the result ended up with a trunk state mismatch.
change the CIC state while the platform Side B might still have the trunk state as ACTIVE, while in fact
is trying to bring down other processes. the trunk involved in the call has already been released prior to
Side A being completely taken down.
Workaround: An audit has to be done on the side that is
becoming active to reconcile the CIC states to the remote CIC
states.
CSCdx83432
Subscriber-termination can be brought IS Symptom: Diagnostic fails due to subscriber termination being
during diagnostics
brought in-service (IS).
Impact: Cannot complete diagnostics.
Conditions: While diagnostic procedures are being run, it
should not be possible to bring a subscriber termination
in-service (IS).
Workaround: Do not bring subscriber terminations in-service
while running diagnostics.
CSCdx83483
Trunk circuit removal while TC is in
transient state is possible
Symptom: Call is terminated.
Impact: Call cannot be completed because the trunk circuit is
removed by placing it in MAINT state.
Conditions: If a call is up and a graceful OOS is done on the
trunk circuit it goes OOS PENDING. If a graceful MAINT is
attempted it should fail, but it passes and brings down the call.
Workaround: Do not attempt graceful MAINT while trunk
circuit is in-service or OOS PENDING. Ensure that circuit is
OOS before invoking graceful MAINT.
CSCdx83532
Null for field term-id in table subscriber
causes dbm error.
Symptom: User datafilled a sub id with term-id set to null.
Impact: This caused a db invalid index error and the
transaction-queue became stuck.
Workaround: Delete this subscriber, then add it back correctly.
CSCdx83721
No INTL_OPERATOR call type
Symptom: Cannot reach the international operator.
Impact: Cannot make operator-assisted international calls.
Conditions: There is no INTL_OPERATOR in call-type table.
Workaround: Use OPERATOR call type.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
26
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdx85039
Call content missing one direction of
streams in call transfer scenarios
Symptom: Call content captured at DF server was missing one
direction of the voice streams at the tapped subscriber. In this
case, the voice stream of the off-net subscriber could not be
heard.
Impact: Does not meet CALEA requirements.
Conditions: Made an off-net to on-net call, then the on-net
subscriber (A) transferred the incoming call to another on-net
subscriber (B).
Workaround: None.
CSCdy04964
ISDN: service message interop problem
w/ Nortel 81c
Symptom: SERVICE message not being responded to by a
remote Nortel PBX.
Impact: Unrecognized SERVICE message.
Conditions: SERVICE message sent from BTS has protocol
discriminator of 0x43 (network management) as compliant to
ANSI specs; Nortel PBX only recognizes protocol discriminator
of 0x3 in SERVICE message.
Workaround: Configure SERVICE-SUPP=N in isdn-tg-profile
table.
CSCdy05664
MDN & CFB able to call forward busy
MDN primary to MDN secondary
Symptom: Activation of call forwarding features (CFU, CFB, or
CFNA) for TARGET_MARKET North-America does not check
for the subscriber having MDN feature.
The subscriber can activate call forwarding to his own or another
MDN number, but the call forwarding will fail and the
subscriber will not know that it fails.
Impact: MDN subscribers can activate forwarding features to
himself using other MDN numbers.
Conditions: TARGET_MARKET=North-America
Subscriber having MDN feature
Subscriber activating forwarding features
Workaround: 1. Do not provide MDN feature to subscribers
planning to use call forwarding features.
2. Tell subscribers that they should not try to activate call
forwarding to their own number.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
27
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdy05972
NCS SDP parameter order not honored
Symptom: Using the NCS protocol, if the 'm' parameter is sent
in any position except the second to the last the call will fail.
Impact: Any call using NCS protocol and the 'm' parameter is
sent in an order not expected like the second to the end, the call
will drop.
Conditions: This only happens with the NCS protocol and when
the 'm' parameter is sent in any other position except the second
to the last.
Workaround: Make sure the gateway sends the sdp parameters
in the expected order.
CSCdy12366
PRI origination to CIDCW active line No CID/CNAM info displayed
Symptom: When making a call from a PRI line to a CIDCW line
on net, the CID/CNAM info is not being displayed. The CIDCW
line is engaged in a call and is on a IAD analog port.
Impact: All PRI originating lines will not be displayed to all
CIDCW lines.
Conditions: Make a call from a PRI interface to IAD and
terminate to a IAD analog line with CIDCW assigned and active.
Check the CIDCW display.
Workaround: Remove CNAM from the terminal.
CSCdy18145
call-agent-profile allows cms-id = mgc-id Symptom: Cisco BTS 10200 version 3.3, allows the mgc-id to
be set the same as the cms-id.
Impact: Cannot distinguish between CMS and MGC activity in
alarms, event messages, or logs,
Conditions: When provisioning a call-agent-profile the system
allows mgc-id to equal cms-id. This is an invalid configuration
per the PacketCable Event Messages Specification
(PKT-SP-EM-I03-011221).
Workaround: Be sure that these two IDs are not the same.
CSCdy18307
Excessive RDM traces from
FullDownloader.c:633
Symptom: The RDM FullDownloader thread prints excessive
trace messages while DB Copying.
Impact: This might adversely impact the performance of call
processing during DB copy during high traffic periods.
Conditions: This occurs when the mate machine is brought up
during high traffic periods.
Workaround: Bring up standby machine during low traffic
periods.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
28
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdy19400
T306 is not started when announcement is Symptom: CA does not start T306 timer after sending
played on ISDN termination
PROGRESS message when an announcement is played. The
circuit gets hung if the originator does not release the call.
Impact: If a call is made and then connected to the
announcement server, the originator must drop the call or it will
hang.
Conditions: This defect involves calls that get connected to
announcement servers.
Workaround: ANM is added timer to tear down the connection
when it expires.
CSCdy21735
DQoS endpoint still ringing after CA
failover
Symptom: A calls B. B rings and A hears ring back tone.
Switch-over occurs at CA. B has not answered and is still
ringing. Even after B picks up, A still hears ring back tone until
it (A) goes on-hook.
Impact: If the call is not stable when the CA switchover occurs,
then the user has to hangup and try the call again. On the
terminating side the ring will not stop until the user answers.
Conditions: This happens when gateways don’t handle
encapsulated RQNT with DLCX (this is a variation of DLCX
where all connections are deleted, i.e., DLCX without Call Id
and Conn Id). This behavior is configured in the Call Agent as
DLCX supported (Y/N).
All IOS gateways support encapsulated RQNT with DLCX;
however, it should be noted that gateways are not required to
support this according to the protocol.
Workaround: Originator hangs up. Terminator picks and hangs
up. Originator calls again.
CSCdy23189
BTS: SIA exits after one virtual IP went
down via cable pullout
Symptom: SIA process exited and CA went out of service on the
active node after cables were removed from qfe0-3.
Impact: Switchover to standby machine occurs. Normal BTS
failover impacts are experienced.
Conditions: This initially resulted in the ACTIVE node showing
that everything was up, including the virtual IPs, but after five
minutes the SIA process exited and the CA went out of service,
resulting in a switchover to the standby machine.
Workaround: The outage is occurring because the DNS server
is unreachable. To ensure redundancy of the DNS lookup
function in the event of a network/cable outage, it is
recommended that two DNS units be reachable via separate
networks with diverse routing paths.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
29
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdy23604
Dup RTP packets not sent by CMTS for
2nd party tap in CF for NDQoS CALEA
Symptom: Feature calls, such as CFNA and CFU, will not send
duplicated RTP stream to the DF server properly if the middle
parties are wiretapped.
Impact: Calls will work fine, but the duplicated RTP path will
not be sent to the DF server for tapping.
Conditions: This is due to the fact that if the middle parties are
wiretapped, we need to delete the original gate and create a new
gate based on the exchanged SDP info.
Workaround: None. Code fix is required.
CSCdy27601
CDR ANI is incorrect when no ANI on
incoming call
Symptom: Incorrect ANI information in CDRs.
Impact: This could impact revenue if it occurs on a billable call.
Conditions: Problem occurs when an incoming call does not
have ANI info. The CDR contains old ANI info and since there
is no new ANI to overwrite it, the old ANI info remains,
Workaround: None.
CSCdy27700
BTS10200: 180 Ringing is sent without
SDP
Symptom: 180 ringing is sent to the originating SIP endpoint
without any SDP.
Impact: SIA needs to wait until it gets an SDP before sending
out 180 ringing.
Conditions: A call is made from a SIP phone to a PSTN phone
via BTS.The call comes to BTS over a SIP trunk and a 5850 GW
is used as the trunking GW. The IAM is sent out to a DMS and
when the ACM comes back from the DMS, 180 ringing is sent
to the originating SIP endpoint without any SDP.
Workaround: None.
CSCdy30920
Call Waiting with Codec Selection Fail
Symptom: No voice path among all parties.
Impact: When H323 is involved in a call, the call cannot be up
speeded because H323 does not support up speeding.
Conditions: MGCP (A) with qos id=G729 calls h323 (B) with
only G729 available in the codec list at the h323 gateway. This
call completes with a G729 codec. A (MGCP) has CWD
activated. A also has the capability to do PCMA. C (h323) calls
A (MGCP) and C hears RBT and A gets CWT. C(h323) is only
configured for PCMA. A (MGCP) hookflashes and dials 2 to
answer C. PCMA is the codec for this call. A(MGCP)
hookflashes again and dials 3 for 3-way conference, but there is
no voice path among all the parties.
Workaround: Use the same codec for all endpoints.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
30
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdy37084
Sendevent does not show up in FMG.log Symptom: Sendevent.sh -s 2 -l 2 -i 2 was typed and nothing
appeared in the file FMG.log
Impact: Events do not show up on FMG.log file.
Conditions: Running of test case Event_Management_
NA_SNG_00016 did not work.
Workaround: Issue the command “CLI> subscribe event-report
type=all; severity=all”, then any events issued (either through
normal operation or sendevent.sh) can be seen.
CSCdy46844
“Cannot receive SIP messages from
network” alarm does not clear
Symptom: BTS 10200 software version 3.3 does not properly
clear “Cannot receive SIP messages from network” alarms.
Impact: If the alarm remains on after the port conflict has been
resolved and the process that issued the alarm has been
successfully restarted, there is no direct service impact.
Conditions: This alarm is issued when the a process using the
SIP stack cannot open the port it is configured to use. This can
happen if the BTS is not configured properly, or if some other
program running on the BTS is using the port that the process is
configured to use.
If a process that uses the SIP stack cannot open the port it is
configured to receive messages on, it will issue this alarm and
exit. In order to get the system to work properly, the port conflict
must be resolved and the process must be restarted.
Workaround: Follow the steps described in the alarm
description to remove any port conflicts.
Before restarting the call agent, use the CLI to manually clear
the alarm. Then restart the call agent and verify the alarm is not
issued again.
The current alarm description does not tell the operator to clear
the alarm.
CSCdy47391
Unable to display all sub /trunk
termination status via COBRA interface
Symptom: When user inputs ID for all subscribers id=*@mgw,
EPOM came up with error: java.lang.NullPointerException
Impact: Cannot view all subscribers using EPOM.
Conditions: Current EPOM is able to display individual CIC for
a specified trunk group when the user selects to view
trunk-termination status. However, it failed to display for all
CICs in a trunk group.
Workaround: Use CLI command to view all subscribers,
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
31
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdy48410
batch file execution may halt while
executing large files
Symptom: Batch execution of large files may halt unexpectedly.
Impact: Batch file execution becomes unavailable after this
error. Active EMS Unix server has to be restarted to continue
executing batch CLI commands. Command execution speed
drops as the file size gets bigger.
Conditions: It may happen if the batch command file has more
than 5000 lines.
Workaround: Large batch files should be divided into smaller
files. For example, each file may contain 500 lines.
CSCdy53932
DNS server down caused CA146 OOS
due to DNS cache was not enabled
Symptom: During DNS server maintenance, BTS call agent
process (CA146) went out of service due to DNS query time out.
Impact: CA146 goes OOS.
Conditions: Currently in the worst case scenario the longest
time the MGA can wait for DNS lookup is 20 seconds.
Workaround: Enable DNS cache.
CSCdy55778
TSAP-ADDR for mgw appends. if not
FQDN
Symptom: Calls do not go through.
Impact: Calls cannot be completed.
Conditions: TSAP_ADDR is configured as “o5-emtaa1” in the
mgw_profile. In the trace log, it says “Invalid IP address:
o5-emtaa1.”
This happens when the TSAP_ADDR in mgw_profile is
configured as a name where the last character of the name is a
digit.
Workaround: Configure TSAP_ADDR as a name where the last
character is not a digit. For example, TSAP_ADDR could be
configured as “o5-emta” or “o5-emta.yy.com” but not
“o5-emta1.”
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
32
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdy61772
BCM: must not report a DP to SIM when Symptom: Asynchronous events usually caused by user action
awaiting instruct for previous DP
(Abandon, Disconnect, HookFlash, Answer, Exception)
currently result in BCM reporting to SIM a NOTIFY for a DP
without regard to the current state of the relationship.
Impact: When this occurs, BCM may be in the middle of
processing a sequence of instructions, or BCM may be awaiting
instructions for a previously reported DP, and so on.
The effect of these events results in unpredictable behavior,
erroneous behavior and, in some cases, catastrophic failure
resulting from SIM or SSF being transitioned to an unplanned
non-integral state.
Conditions: User action, such as Abandon, Disconnect,
HookFlash, Answer, or Exception.
Workaround: BCM will not report a DP if it is awaiting
instructions for a previously reported DP or if it is currently
processing instructions received from a FS.
The instructions from a FS could be consequent to a previously
reported DP or due to an asynchronous event occurring at the FS.
BCM will queue up DPs to be reported and report them singly
and in sequence to SIM.
CSCdy61807
SIM: Indicate last instruction in a set, in
INSTRUCT message to BCM
Symptom: Asynchronous events usually caused by user action
(Abandon, Disconnect, HookFlash, Answer, Exception)
currently result in BCM reporting to SIM a NOTIFY for a DP
without regard to the current state of the relationship.
Impact: Loss of some feature functionality.
Conditions: When a set of instructions are received from a FS,
SIM forwards them to BCM one at a time, sending the next
INSTRUCT only after receiving a successful response to each.
SIM will indicate in each INSTRUCT message to BCM whether
or not more instructions are forthcoming. When an INSTRUCT
is received by BCM with the indication that there are no more
instructions in the set, BCM can report the next DP after sending
the INSTRUCT response for the last INSTRUCT.
Workaround: None.
CSCdy61823
SIM: Send a 500 response to FS sending
instructions at inopportune time
Symptom: Erratic feature behavior or loss of feature.
Impact: A feature may not be provided.
Conditions: Race conditions introduced by concurrent
asynchronous events at feature servers and call agent.
Workaround: None.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
33
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdy68085
No ring back is sent when a subscriber
with CW is called from mobile sub
Symptom: Mobile (cell) caller does not hear ring back tone
when calling a BTS subscriber with CW feature.
Impact: Calls might not be completed.
Conditions: Subscriber A has call waiting activated and is
talking to subscriber B who is on-net. An off-net mobile (cell)
subscriber is calling subscriber A, subscriber A receives an
RQNT with 'L/wt' telling it to play call waiting tone to
subscriber A indicating an incoming call, but BTS never sends a
G package 'rt' or 'rbk' to the terminating GW (IAD2421) so it can
play a ring back tone to the mobile subscriber.
Workaround: None.
CSCdy72183
Cannot configure different netmasks in
hostconfig
Symptom: After jumpstart of a EMS, the hostgen file in the
/opt/setup directory needs to be updated per information from
the NIDS, but there is no provision in the hostgen parameters for
a different netmask for each of the three external networks
(NETWORK1, NETWORK2, and NETWORK3).
Impact: This results in wrong /etc/hosts and /etc/netmasks files
being created, which have to be hand edited to put in the correct
values.
Conditions: It is assumed that all three networks will have the
same netmask, which may not be true in all cases. The ENDFIX
argument for each of the machines, which is applied later to each
of the three networks, is also taken to be only one. This may not
always be the case; the last octet of all three networks may be
different. This also leads to wrong information being filled in the
/etc/hosts file.
Workaround: Hand edit the /etc/hosts and /etc/netmasks file
and put in the correct values for each of the three external
networks.
CSCdy72985
Cannot equip the termination of mlhg.
Symptom: When a subscriber is provisioned as MLHG (one
subscriber ID with any terminals), one cannot do an
equip/unequip or control command on the subscriber.
Impact: Users can not make calls to or receive calls from that
subscriber.
Conditions: When a subscriber is provisioned as a MLHG (one
subscriber ID with many terminal to it), all attempts to equip the
termination fail.
Workaround: None.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
34
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdy76798
redundant billing-server does not appear
to be working
Symptom: EMS initiates FTP transportation to billing server A,
but does not switch to billing server B when billing server A is
disconnected.
Impact: Billing records might be lost.
Conditions: When EMS initiates FTP transportation, it sticks
with that server even when the server is disconnected.
Workaround: Remove and restore the BDMS's.
CSCdy78749
CLI account is not disabled/locked after
45 to 90 days with no activity.
Symptom: User accounts do not lock after a period of inactivity.
Impact: None, this in an enhancement / new feature.
Conditions: User account has long period of inactivity.
Workaround: System administrator can delete users that are no
longer accessing the system.
CSCdy80561
EMS CLI ran out of memory during show Symptom: Show commands resulting in large amounts of data
subscriber
cause the JVM to run out of stack space (memory).
Impact: Subscribers will hear dead air in these cases.
Conditions: This occurs when the IP network has problems, and
therefore, MGA does not get adequate responses to their
messages.
Workaround: When the network comes back, this situation will
clean itself up.
CSCdy81313
Dead air on calls following IP outage and Symptom: When the IP network has difficulties, MGA will have
recovery
problems responding to the delete connection message sent by
BCM to MGA.
Impact: Caller terminates call due to apparent dead connection.
Conditions: Problem seems to be in MGCP command
sequencer.
Workaround: None.
CSCdy85260
Suspend timer set to 0 does not work.
Symptom: When the suspend timer is set to 0, the call should be
released immediately without setting the timer. However when
the value is set to 0, the call is never released by the terminating
end, the originator needs to release the call.
Impact: Subscriber’s line is hung.
Conditions: Setting this value to 0 will cause the terminator to
never release the call, and wait for the originator to release.
Workaround: In table ca-config, set the
TERMINATING_IMMEDIATE_RELEASE flag to Y which
will tell BCM to handle the call as immediate release--NO TRD.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
35
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdy86586
Alarm not issued for 70% disk utilization Symptom: No maintenance alarm #59 issued when disk is filled
more than 70%.
Impact: Disk could be filled and records lost if maintenance
alarms are not issued.
Conditions: Disk was filled to much more than 70% and no
alarm was issued. When disk space fills to 70% system should
issue maintenance alarm #59.
Workaround: None.
CSCdy87871
800 dip that returns local number sends
0110 tns to access
Symptom: Some 800 calls may fail with an announcement.
Impact: 800 call failures for local intralata numbers
Conditions: 800 calls fail if the N00 TCAP response has carrier
id of 0110 and translated number is local to the access tandem to
which the call is being sent. TNS with carrier id of 0110 gets
populated in the IAM to the access tandem, which in turn tries
to dip the already translated number.
Workaround: Create a separate trunk group that has a carrier id
of 0110, then route calls over that trunk-grp. The IAM will not
contain TNS parameter as carrier id is defined on the trunk-grp.
CSCdz03077
Unable to place call after taking a
trunk-term OOS/INS, mode=graceful
Symptom: Unable to place calls.
Impact: Cannot place calls.
Conditions: Placing ISDN to ISDN call through a Lucent PBX
and taking the trunk termination OOS and INS with mode =
graceful. After bringing the trunk termination INS the next call
fails with “No circuit/channel available” error message.
Workaround: None.
CSCdz03475
Critical database alarm generated for
alert.log shows deadlock detected
Symptom: Update on a child table fails with a deadlock error,
which is a critical database alarm.
Impact: In deadlock situations one transaction is rolled back.
Conditions: EMS OPTICALL schema has many tables with
parent-child relationship. For update and delete operations on a
parent table the child table is locked (in shared lock). In the
situation when process A updates on a parent table (before
commit), then process A updates the child table while process B
also attempts to update the child table (without commit), then
process B executes another update on the same child table,
process A's update on the child table fails with a deadlock error.
This error occurs only when multiple processes are updating or
deleting parent and child tables. INSERT statement isn’t affected.
Workaround: The alarm directs the operator to look into the
alert.log file, which points to related trace file(s) in the
/data1/dump/udump directory. The trace file logs the failed SQL
statement. The operator can then execute the SQL statement
manually from the Oracle PL/SQL interface.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
36
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdz04433
CNM get_remote_sdp() does not work in Symptom: When a SIP phone dials a number that is not in the
SIP to Announcement Server call.
dial plan and gets routed to an announcement, the announcement
is not heard on the SIP phone.
Impact: This is only an impact on the SIP phones. The call
cleans up and the problem does not have any adverse affects on
the system.
Conditions: This only effects SIP to announcement calls.
Workaround: None.
CSCdz05865
XML/Corba sometimes provides
malformed XML
Symptom: Certain values in XML cause errors in the XML
parser.
Impact: This problem can cause errors in EPOM's XML parser.
Conditions: The problem occurs in special situations in which
“<“ and “>” characters are embedded in reply text.
Workaround: Use valid values in commands so that error
message are not transmitted via XML.
CSCdz07020
EMS platform does not meet performance Symptom: The EMS platform is not capable of supporting a call
requirements
agent running at rated capacity of 100 calls per second.
Impact: System does not meet stated performance.
Conditions: During soak tests running approx. 30 calls per
second with background SNMP and provisioning activity the
EMS CPU is 0% idle for the duration of the soak test.
Workaround: Under investigation.
CSCdz10259
ISDN called party number truncated to 19 Symptom: The BTS truncates the called number to only 19
digits.
digits, and fails this international call with no route to
destination cause.
Impact: With this limitation, dial around international calls
from ISDN cannot be executed.
Conditions: An ISDN call is made by dialing a dial around
operator assisted international call. The dialed number is
1019999-01-861234567890 (21 digits).
Workaround: None.
CSCdz15836
Operator call fails with operator system
access in OCT 3a
Symptom: Operator call fails.
Impact: Users cannot reach operator.
Conditions: Problem found during pri-pbx interop testing with
Nortel-NI. Call flow is as follows:
Phone1----PBX---PRI---IAD---PRI-backhaul----BTS----SS7
When making an operator call from Phone1 off PBX, Nortel
PBX does not send 0 in the called party number, but marks
operator system access in oct 3a, which gets rejected with cause
mandatory information element missing.
Workaround: None.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
37
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdz36865
CoderType field is missing for G729 call Symptom: The "coder type" field in the billing record
sometimes is not populated when it should be.
Impact: The "CODERTYPE" line will be missing from the
output of the "report billing-record" CLI command. The field
will be unpopulated in the flat file.
Conditions: This problem has been reported on an
MGCP-to-MGCP call where a G.729 codec was used.
Workaround: None.
CSCdz37125
Round-robin of announcement trunk
groups fails
Symptom: Only one trunk group in an announcement route will
be selected even if more than one is provisioned and Round
Robin is set.
Impact: Minor, the trunk group that is provisioned first will
always be the one that is provided.
Conditions: Trunk group selection method is set to RR (round
robin) for announcement trunks, but when making calls the
trunk in TGN1_ID is always selected even though TGN2_ID is
also populated. RR works for selecting H.323 trunks.
Workaround: Provision only one trunk group per
announcement route.
CSCdz45786
CLI sessions unable to issue status and
control commands
Symptom: Since upgrade to v.21 sometimes CLI sessions are
unable to status and control.
Impact: Status and control commands do not work. Show
commands continue to work.
Conditions: Problem appears to be random, but it only seems to
happen when there are a lot of users logged in and running CLI.
Workaround: Logging out of CLI and then back in normally
fixes it.
CSCdz48717
CFNA would not work for calls coming
from CCM subscribers
Symptom: When a call is made from the call manager via H323
if the called subscriber has call forward no answer assigned, then
the call to the third endpoint will fail.
Impact: This problem only occurs when a call comes in from
CCM-cisco call manager via H323. This is a slow start call
which means that SDP is not exchanged until the answer occurs.
Conditions: This problem occurs when a call from CCM over
H323 using slow start comes into the BTS and the call is
attempted to be CFNAed. This call has no adverse affects on the
system.
Workaround: None.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
38
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 2
Open Caveats (continued)
DDTS ID
Description
Workaround
CSCdz52685
911 call with ODR default routing fails.
Symptom: 911 call fails.
Impact: 911 calls cannot be completed.
Conditions: During 3.3 V04 upgrade a 911 call is placed from a
CAS trunk group. The call is routed using policy-odr with the
default calling number. The call fails if the calling number
DEFAULT is used.
The CA-CONFIG table default-odr is incorrectly provisioned
with "default" (lowercase) instead of "DEFAULT" (uppercase).
Workaround: Reprovision the CA-CONFIG table default with
“default” (lowercase).
CSCdz53077
Office code can not be added properly if
DN_GROUP contains uppercase letters.
Symptom:
Impact:
Conditions: The DN_GROUP XXXX is appended to the
digit_string in the office_code table if the DN_GROUP=XXXX
instead of xxxx.
Workaround: The BTS either needs to accept both lowercase
and uppercase, or the CLI Guide needs to specify that the
DN_GROUP has to be lowercase when provisioning the
office_code table.
CSCdz53865
POTS feature server Core
Symptom: POTS feature server had a core dump.
Impact: Feature server had to be restarted.
Conditions: SIGSEGV was caused in FSPTC while accessing
an invalid pointer stored in a subscriber record.
Based on the stored data in the subscriber record, user's first
attempt for CFU-Activation was treated as "2nd attempt within
2 minutes". From the logs it was verified that the data wasn't
stored in last hour of this attempt. This indicates that the data
may have been in the subscriber record a long time. Information
available so far does not point to reason/scenario which can lead
to this data being stored for long time (normally the data is
stored for 2 minutes). Investigation for the same will continue.
Workaround: Even though we do not know the root cause of the
problem, the immediate issue of SIGSEGV can be fixed by not
accessing the memory in this scenario, which will not affect any
functionality.
Resolved Caveats
Resolved caveats listed in this section include only those critical and major caveats that were found
during system test or critical issues found during customer verification tests of earlier releases and
resolved in Release 3.3 V04. DDTS ID numbers listed in Table 3 are Cisco internal tracking numbers.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
39
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats
DDTS ID
CSCdu03520
CSCdu12799
CSCdu24104
CSCdu43961
CSCdu46893
CSCdv10502
CSCdv25360
CSCdv26491
CSCdv87249
CSCdv88204
CSCdv90681
CSCdw01814
CSCdw03030
CSCdw14479
CSCdw16766
CSCdw21044
CSCdw22859
CSCdw26383
CSCdw31559
CSCdw43387
CSCdw50934
CSCdw51015
CSCdw61017
CSCdw62246
CSCdw62310
CSCdw62853
CSCdw63217
CSCdw63262
CSCdw64582
CSCdw71821
CSCdw71907
CSCdw72308
CSCdw72666
CSCdw72723
CSCdw79265
CSCdw79719
CSCdw80034
CSCdw80124
CSCdw85046
CSCdw94766
CSCdx01905
Description
CQM Fails for CIC range when sent from the CLI
Cleanup internal thread structures in IPC on thread cancellation/exit
ANNC SEND_ANSWER does not work for ACR
Stdout from processes should be line buffered
CA sets CICs IDLE awaiting response to RLC
911 can be put on hold by Centrex subscriber
ssf and sim changes for TERMINATE and NOTIFY crossing problem
MGCP codec-types not mapping to standards
Invalid error from CHP lib - get_entity_indexes()- t_conn_id is 0
SUS message not sent when CFNA involved (any call forward or transfer)
BCM - CTXG sub with TWC does not receive busy after dialing invalid number
KAM needs to handle fault detection/recovery properly when CPU overloaded
Errors need to be eliminated
EMS platform exit left behind Java orphaned processes
Missing Mandatory IE in Alert message
SC1D/SC2D Tables Allow any Information to be Entered
Billing needs to check if QOS messages arrived for abandoned call.
No option to provide in-band tones on ISDN originations
BTS diag ss7-trunk-termination test=2 fail due to TOS set wrong
MGA - ca-config trigger is not available
CallerID showing GMT as time zone instead of local time zone
SUS message is not generated for SS7-H323 call
BCM rejects IAM containing reserved called party nature of address
China dial-plan feature id
The CMS XML Translator for the Homework project
3.2 new development
Security requirements for the Homework Project
System Management features for the Homework project
SIM has performance issues
TECH-PREFIX-GRP Table excepts Invalid Tech-Prefix
Field TG in table subscriber receives invalid column name
MGCP-H323 reattempt 6 times with different conference ID
Change of sub dn1 does not update table dn2subscriber
Implement inter-office AC/AR feature
CPRK-CLEAR traffic measurement not pegged after cprk is cleared.
State token for CLI command add/delete/show even-queue NOT implemented
H3A Delay Time unacceptable (12 sec) after CTRL_END_PROCESS message
ENHANCEMENT: Need multiple IP addresses on fewer Ethernets
Tone cannot be conferenced for China Residential CW/TWC
BORG Project Development (SGA)
Exception DP reported in wrong leg
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
40
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdx03204
CSCdx08857
CSCdx17599
CSCdx18267
CSCdx21154
CSCdx23021
CSCdx25215
CSCdx27449
CSCdx28302
CSCdx28952
CSCdx28973
CSCdx30067
CSCdx32283
CSCdx32416
CSCdx32652
CSCdx32668
CSCdx33242
CSCdx33278
CSCdx33288
CSCdx33294
CSCdx33646
CSCdx33697
CSCdx33740
CSCdx33832
CSCdx34571
CSCdx34759
CSCdx34760
CSCdx35074
CSCdx35615
CSCdx35680
CSCdx36219
CSCdx36767
CSCdx36791
CSCdx36870
CSCdx36884
CSCdx36903
CSCdx37200
CSCdx37240
CSCdx37949
CSCdx37979
CSCdx38135
Description
BTS does not handle graceful shutdown RSIP from 5400 correctly
OAMP Application Test Suite
Unnecessary free of message buffer and VerifyReqHeader for all calls
911: need to support interaction with TWCD
RHM need to monitor /tmp disk space
TGA: use new API application provided.
Platform start script should backup the data directory
Remove deprecated TPM API.
Northbound updates cause audit failure.
Feature Support: idx_replace_idx() should support IDX triggers
SIM: Save and print state of processing threads
Command parameter table incorrect for USER_NAME in activity-summary
SIA cleanup: CCB holding local SDP heap not necessary.
New counters for POTS, SIP
108 test calls need to be supported in BTS
Support of CAS blocking/unblocking feature
Improve switchover time in TGA and Traffic (EMS) code
Sia and Sim go active times need to be reduced
Billing: on net calls tagged as off net
Create an ipc priority scheme for common and platform specific messages
BORG dbm2 development
BORG project development - OAMP Applications
Changes for BORG
Trigger event in FIM when feature-interaction not supported
Use DEFAULT-POP when POP is assigned.
ENHANCEMENT: PMG state machine needs to be restructured for going active
Last stage of schema related change, db sizing change
BCM needs events added for routing errors
Call Park/Retrieval is not working
Register events for BORG project
H323 slow start to slow start calls
Improve switchover times for billing
POTS FS framework code review defects
SIS: CCB print tool should print prov resp info list and prov resp Q
SIM: Re-use FsInfo struct if a FS needs to be Notified after receiving BYE
EMS sends wrong values to H3A process when provisioning h245TunnelControl
Provision CW-Deluxe feature
Disallow subscriber to activate CFx to his own DN
C utilities need to move to CUTL library from CMN library
No local time zone option in POP table for China
Need additional trace topics for new libraries
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
41
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdx38437
CSCdx38685
CSCdx38699
CSCdx38701
CSCdx39084
CSCdx39100
CSCdx39520
CSCdx39704
CSCdx39776
CSCdx39928
CSCdx39948
CSCdx40339
CSCdx40350
CSCdx40362
CSCdx40380
CSCdx40475
CSCdx40743
CSCdx40773
CSCdx40812
CSCdx41184
CSCdx41395
CSCdx41474
CSCdx41535
CSCdx41585
CSCdx41617
CSCdx42691
CSCdx42808
CSCdx42832
CSCdx42854
CSCdx42865
CSCdx42919
CSCdx43197
CSCdx43246
CSCdx43263
CSCdx43329
CSCdx43362
CSCdx43511
CSCdx43822
CSCdx43985
CSCdx43990
CSCdx44114
Description
ASM enhancements for BORG release
DQoS feature support
DQoS feature support
DQoS feature support
Delay in call processing when POTS feature server is not running
Sync command allows user to input incorrect target
G723 codecs not supported
Making CDSL-API Header file independent of FSPTC-DBM.
PMG core after 2.1V13 installation - installation problem or operator error
This defect is needed for all 3.2 software upgrade checkins
SIM cored when making 3-way call
Change MGA process binary name from mga2 to mga
BCM fails to send LPT req on incoming COT call
Dial China PSTN, BTS should stop playing local tone
Silence is played when no associated dial-plan is provisioned.
Dumping excessive pstacks is very expensive
LCO es_cci need to use hex value
SIS: should print the config parameters at startup and shutdown
Audit - do not display mismatch when call-agent sides value is null
Suppress the ISDN compilation warnings
DN2subscriber range add fails to 11 digit DN
remove compile warnings for S7M/S7A
Enable parallel builds for Borg and Non-Borg projects.
CDP Tables does not allow SPEED_CALL, Custom-Dial-Plan does.
SSF: should delay freeing relations with no subscriptions & send TERMINATE
LogReport was generated for DLCX 250 return code
Import the BORG TCAP Adapter Library code for the first time
SIA Re-organization of functions and files.
BTS does not copy the timestamp header from provisional 18x to PRACK
GOS Conditional Trywait could possibly end up in an infinite loop
SIM: trace error in source proc_sip_msg.c is a core possibility
Sip applications need new API to open receive port
IPCQMsgDispatch not allowing thread type=0, instance=1
Add a new process EMA
Java wrapper does not allow passing in arguments into java programs
SNMP changes for Release 3.3 of the BTS10200
BTS sends 481 for cancel message in PRACK scenario
Upgrade to V12 caused 2 copies of init to run -- hub does not run
PacketCable EventMessaging stack development
RADIUS stack development for PacketCable
BCM did not send setup response to MGA after call is answered
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
42
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdx44118
CSCdx44150
CSCdx44374
CSCdx44861
CSCdx44927
CSCdx44936
CSCdx45357
CSCdx45376
CSCdx45388
CSCdx45423
CSCdx45951
CSCdx46504
CSCdx46511
CSCdx46558
CSCdx46745
CSCdx47230
CSCdx47720
CSCdx47749
CSCdx47897
CSCdx48883
CSCdx48921
CSCdx49006
CSCdx49281
CSCdx49814
CSCdx50238
CSCdx50418
CSCdx50602
CSCdx51499
CSCdx51573
CSCdx51835
CSCdx51841
CSCdx51979
CSCdx52005
CSCdx52275
CSCdx52292
CSCdx52927
CSCdx53002
CSCdx53249
CSCdx53301
CSCdx53550
CSCdx53566
Description
ANM enhancement Phase 3
SIM: leaks CCB when BYE received from FS after EDP-N NOTIFY
H323 GW fails to ack the receiving of a GCF
CAS termination becomes faulty after retransmission.
BTS does not meet CALEA requirements for abandoned calls
BTS does not meet CALEA requirements for abandoned calls
PacketCable Event Message support in BCM
Release 3.3 schema design changes
Could not bring up CICs in service, after provisioning
Use old wrapper for SAD as the common one does not work for SAD
CF*-Act does not send correct release cause for call-barring due to nod-restrict
Audit command does not leave space between descriptions
Diag ss7-trunk-termination test=4 does not shows local or remote state
Equip trunk-termination does not update status in Oracle
CLI reports wrong result for reset trunk-termination command
H323 process went down, during the China Testing
Feature Support: Need utility getUTCoffset to support PacketCable Event Msg
SIM:TERMINATE crossing INSTRUCT results in SIP CCB leak
Tech prefix not being registered with GK
TWC requesting support for 0+7D dialing
BTS SIP uses ansi92 version for the ISUP MIME type. It should be ansi.
MGA stuck in init loop after failover
ENHANCEMENT: Create a generic list class for use by all
OLI info not sent in IAM when CF or CT to switched 8XX number
Create new trans table in SHM for PacketCable DQOS
Common wrapper has to call end_all_threads()
CFNA and CFU calls would not release, CIC will bounce between RES & SUS
SIS: SipCcb space needs to be reclaimed for tran data to prevent realloc failure
Process does not startup after system install
Cannot add token into table annc-trunk
FIM does not inhibit CWD on CHD invocation
Cannot hook flash after dialing digits during feature call
CUTL library string function improvement
Component id in Event should reflect originating resource
Changes required to support Borg Signaling Gateway adapter
New Arguments in platform.cfg for ESA
Field in nod-wb-list is invalid in table cos-restrict
PMG should check process status more often in some circumstances
Event/Alarm enhancements for R3.3
Call not established to SIP endpoint on redirection to different number.
need to add mgcp_cas_block_unsupp
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
43
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdx53683
CSCdx53786
CSCdx54665
CSCdx55310
CSCdx55330
CSCdx55334
CSCdx55669
CSCdx55714
CSCdx55733
CSCdx55798
CSCdx55809
CSCdx56676
CSCdx57292
CSCdx58266
CSCdx58350
CSCdx58400
CSCdx58456
CSCdx59809
CSCdx59884
CSCdx60451
CSCdx60505
CSCdx60665
CSCdx60980
CSCdx61827
CSCdx61844
CSCdx61934
CSCdx62182
CSCdx62581
CSCdx62588
CSCdx62589
CSCdx62590
CSCdx62603
CSCdx62841
CSCdx62876
CSCdx63264
CSCdx63850
CSCdx64231
CSCdx64326
CSCdx64357
CSCdx64488
CSCdx64602
Description
Proper events need to be armed if fax event is received and is not ACTIVE
BTS Fails to Release Active Calls after receiving RSIP Forced and Restart
Fields NOA and NEW-NOA in table dial-plan should not be case sensitive
EMS getting watchdog timeouts on all links
PDM tool core-dumps when sending a message to PMG.
H3A not generating core --- hung on malloc call
SIP Parser: Notify MWI does not work. Event in message is not found.
SIP Parser: 3XX with diversion hdr with unknown reason fails parser.
SIA: Receiving Invite with Redirecting number error does not send 400.
Adi Slf attempts to validate non DN collected-info DialedDigits.
Centrex subscribers are not barred on call-type basis for ADI features.
SDP: traces should use own topic name
Unit OOS should be FAULTY not FAULTY-NORMAL or FAULTY-FORCED.
Need generalized configuration file parser
T_Busy DP reported in wrong BCSM state
Regression Unit Test Framework Library
Need new parsers to support ANI Manipulation
termination state goes to cannot be reached after switchover
two inbound calls to main mlhg sub with cfna active, 1st call does not forward
KAM needs to trace some special messages for switchover time analysis
Calling Name not displayed if Generic Name parameter length < 16
Report activity-summary command succeeds with Exception output.
The BTS doe not release the CIC from OBSY state
get_all_stat.sh failed
CAS MO terminations cannot be set to idle.
Billing records not displayed/generated.
During switchover, mga was stuck and watchdog timer for mga thread expired
Undefined NOA blocks call from Unicom PSTN
Call to Unicom H323/PSTN from one ATA changes another ATA to ACTIVE
ANI-digman does not change NOA from UNKNOWN to NATIONAL
CFU call failed due to NDC for local call not manipulate ANI
TWC call cannot return to A->B leg when A->C leg got busy tone.
New TSA process in AIN/POTS feature server platforms
Copy SIA files from CVS 3.3 to CC 3.3.
New Build Migration: For R3.3
Broadcast address being set as Mac-Address with boom in slot1
Corba interface adding only in ems database
MGA should recover temp_down indefinitely in CABLE market
SIP framework errors exist in FS code
CW disconnect timer restart during switchover
SIA: Signal handler function should only call Async-signal-safe routines
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
44
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdx64667
CSCdx65180
CSCdx65226
CSCdx65230
CSCdx65608
CSCdx65649
CSCdx65753
CSCdx65850
CSCdx65976
CSCdx66547
CSCdx66562
CSCdx66660
CSCdx66958
CSCdx67245
CSCdx67251
CSCdx67380
CSCdx67607
CSCdx67757
CSCdx67773
CSCdx68031
CSCdx68120
CSCdx68174
CSCdx68291
CSCdx69010
CSCdx69036
CSCdx69655
CSCdx69776
CSCdx70247
CSCdx70731
CSCdx70770
CSCdx70893
CSCdx71425
CSCdx71428
CSCdx71464
CSCdx71809
CSCdx72486
CSCdx72516
CSCdx72519
CSCdx72786
CSCdx73129
Description
BTS sends NOTIFY without Contact header
SEGV when TCA received CANCEL_TERM_SCAN with invalid transaction id
Original Call take down in case of CFB
Interaction between AC/AR and PPS features for delayed processing fails
CAS call not restricted by COS Local Only.
Take care of Schema updates.
Field mgw-id in table mlhg-terminal should be a varchar(32)
Deprecate the old wrappers from the system
CNM should accept G. style codec names from QOS table
CheckCFG fails if host files has # in it.
Call Waiting Second leg does not provide ring back to PSTN user
omni port_daemon needs to be killed following platform stop -i omni
IPManager does not map IP for SIA on time
CNM not releasing connections on abnormal release
Accessing SIP-Msg pointer after sending, causes core-dump.
Core after CAS 100 trying messages.
For CENTREX subscriber CFU, CFNA, CFB forward incorrect ANI
Enhancement: Perform pstack dumps only if necessary
Apache server to be installed on Call Agent boxes also
MGA clears CID when DNS lookup fails
Sub allowed to forward Calls to himself.
800 translated number route by carrier need dial plan to terminated.
MGCP messages retransmitted only 2 times after NACK.
TWCD to Unicom PSTN heard both local and remote ring-back tones
H323 process got killed when DRQ not getting response from KP
A CLI command results in a warning stating MySQL is not running
Cannot activate CFU from a Centrex subscriber to a non-Centrex subscriber if
they do not pick up the call
Table Dial-Plan Mandatory Fields must be the same for add/ch/del
FCP to support SCP-Db-Id OpParam
Sending more than 4K msg using SENDTO_W_TRACE causes core.
HOTV feature not available for NA; HOTVA, HOTVD and HOTVI were
H3A2 and H3A1 in infinite loop --No line package for NCS
Cannot use change for digman table
Maintaining Unit-Test tool UUTest for FSPTC.
Copy SIS file changes in 3.3 CVS to CC REL3.3 for copying timestamp
Reduce PMG CPU usage consumption
New Billing Process Needed for Packet Cable
Measurement_Billing_Summary schema missing columns
bmg2 dies when attempting to write records to flat file
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
45
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdx74013
CSCdx74143
CSCdx74388
CSCdx74582
CSCdx74854
CSCdx75026
CSCdx75032
CSCdx75253
CSCdx75417
CSCdx76023
CSCdx76060
CSCdx76063
CSCdx76067
CSCdx76071
CSCdx76176
CSCdx76615
CSCdx76678
CSCdx76691
CSCdx77221
CSCdx77404
CSCdx77450
CSCdx77462
CSCdx77476
CSCdx77580
CSCdx78033
CSCdx78304
CSCdx78366
CSCdx78401
CSCdx78413
CSCdx78436
CSCdx78860
CSCdx80016
CSCdx80052
CSCdx80098
CSCdx80155
CSCdx80508
CSCdx81594
CSCdx81611
CSCdx81641
CSCdx81815
Description
3.3. software upgrade development
Field default-std-cause-code show invalid for table cause-code-map-profile
Fields min-dn-length and max-dn-length invalid for table exchange-code
CHP: Define Version Ids for DBM CHP, PC CHP, CA CHP, FS CHP
Provision the desired Solaris services for security
CPI interface to get help information on BTS commands
IP Alias for the Active EMS on the Telnet interface
ENHANCEMENT: Platform should support system time change notification
Network ID in CIp is set to 0 on terminating end
Billing record writes a release of Net out of order as resource unavailable
BMG overwrites the call type field in the query statement.
BORG Project Development (SGA)
CNM Needs to print out verbose trace messages in cnm_billing.c
PMG should support BORG and NON-BORG AIN platform.
Parser should not fail when parsing unknown content types and attachments.
Fax_supp in H323-TG-PROFILE should be of type fax_supp_t
Socket monitoring allowing same fd to be monitored more than once
Field tg in table circuit-code should not be invalid
Enhanced build mechanisms based on EDCS-204034
Mysql_bill.sh not installed
Cannot execute ./backup_db_cold_v32.sh $ORACLE_SID after upgrade
BORG Project development (OAMP)
Table destination field call-type should allow hyphens and underscores
Print and compare functions need to be added in ca_repl_verify
In T38 CA controlled mode, BCM does not send SAI_CCM_OOBINFO_REQ to
MGCP
Use supervision type NO IMMEDIATE REL on forced and graceful control
Need to modify makefiles to conform to build process for clearcase
Centrex-id not checked before dispatching to AC/AR
Database-id of responding SCP needs to be reported in FCI to BCM
Originator phone keep ringing back even though terminator answer
Checklog script does not check location before removing files
CFNA: After call clearing leaves behind a connection
DBM API causing heap-leakage in pots process for FSPTC.
When residential gateway is put in MAINT with graceful mode, stays pending
After CA switchover, hook-flash ignored
MLHG: Line Service Type is not consistent for INDIVIDUAL subscriber.
Table h323-tg-profile not adhering to delete rules
Fax-T38-CAMODE-SUPP MGW-Profile entry DEFAULT must be N
FSPTC core dumped when AC invoked
Provisioning of table nod-restrict-list populates shared mem incorrectly
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
46
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdx81880
CSCdx82443
CSCdx82468
CSCdx82556
CSCdx82583
CSCdx83678
CSCdx83721
CSCdx84512
CSCdx84765
CSCdx85669
CSCdx86219
CSCdx86625
CSCdx87244
CSCdx87710
CSCdx87769
CSCdx87870
CSCdx88021
CSCdx88058
CSCdx88125
CSCdx89402
CSCdx89535
CSCdx89862
CSCdx91554
CSCdx93331
CSCdx93497
CSCdx94035
CSCdx94434
CSCdx94658
CSCdx94975
CSCdx95305
CSCdy00874
CSCdy01950
CSCdy01992
CSCdy01997
CSCdy02609
CSCdy02874
CSCdy02927
CSCdy02944
CSCdy03058
CSCdy03065
CSCdy03568
Description
CAS ANI not delivered to CAS MO operator
cSeq is not handled correctly during switchovers
CNM needs to use the right API to post ipc message to SGA
SIA IPC message leak in pool 4
Multiple call forwarding has ringback issue
When call is up, BTS10200 does not perform CQM
No Operator Call Type
No ring back on ISDN originated calls to some mobile subscribers
H3A limits codec selection to single codec
No IRR messages sent in response to IRQ
MWI tone played for feature calls requiring stutter dial tone
Makefile needs to be modified as per new template
Requirements for RO-S-103 need to be met
Makefile: migrate makefile to new form
POTS and AIN-FS need to gracefully terminate threads if one thread returns.
SIM: fix coding error in ProcessFcpList function
New Build Migration for 3.3 - for unit test drivers
STATUS msg w/wrong cause (101 instead of 97) when FACILITY is received
New HOTV TO (Time Out) value will not work if changed from default value
Incoming SIP calls requiring announcement server should now work.
H323 ignores the Presentation Indicator bits in Setup message
call-type and route-type need to be consistency when add destination
Extra un-needed MGCP RQNT message for CAS to RGW call.
ANM internal faulty management did not implement
CLI QOS Table not accepting several CODEC types
45 minute 911 call timer not working.
Makefile update
Secondary RKS in call-agent-profile should be optional
Billing record does not show call-type when cause=no_route_destination
H323 stack post octantis2 sev1/2 bug fixes
BW-list of OCB not checked in OCB deactivated state
Default T108 timer (TEST-CALL-TMR) is inaccurate
Event portion of OATS requires R3.3 update
Audit between standby side EMS to standby side CA during upgrade
BCM data blocks leak.
ECR-2092 Radius security code must be on 4-byte boundary
HOTV fails to call original number aft FSPTC switchover
BCM cores because of wrong casting by a dbm API
(Enhancement) Remove Makefiles for platform include directories
Able to configure subscriber category = ctxg-mlhg without required tokens
Migrate Makefiles
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
47
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdy03664
CSCdy04049
CSCdy04052
CSCdy04157
CSCdy04251
CSCdy04427
CSCdy05001
CSCdy05067
CSCdy05075
CSCdy05105
CSCdy05323
CSCdy05429
CSCdy05485
CSCdy05496
CSCdy05557
CSCdy05673
CSCdy05682
CSCdy05691
CSCdy06275
CSCdy06323
CSCdy06785
CSCdy07336
CSCdy07569
CSCdy07579
CSCdy07640
CSCdy07824
CSCdy07980
CSCdy08703
CSCdy08715
CSCdy08798
CSCdy08841
CSCdy09228
CSCdy09602
CSCdy09960
CSCdy10756
CSCdy10767
CSCdy10811
CSCdy10864
CSCdy11028
CSCdy11810
CSCdy11986
Description
Warnings from LINT in the CNM 3.3 sources
Block manual changes to clock setting
Feature Interaction between NA and China CW/TWC features
install.sh does not verify proper jumpstart procedure
BCM process is in loop and dead when POLICY NXX route is used for call
CMTS is not sending QOS start message to DF Server
DLCX with I: and without C: is invalid. Tellab MTAs nack with 510.
Billing needs new-style make files
No GATE_DELETE in CFNA DQoS call
SIP stack rejects SUBSCRIBE msg containing content-length header with 415
First MDCX to the O-side is missing send-recv-resv DQoS parameter
SIA pass ISUP_VERSION instead SAI_VERSION to sipt converter
CQR has incorrect CIC status for CICs divided in two trunk groups
Codec G726-32k not send in L parameter of CRCX
show event-log fails when using start/stop parameters
Set default slack term value in Gate spec per ECR-2064
Incorporate T7, T8 timers as required by ECR-2095
After switchover, send GATE-INFO to audit active gates
CORBA needs to pool resources to speed processing.
AC and ACR interaction incorrect w/privacy=full
Incorrect Distinctive call waiting tone for the second MDN member
core dump after receiving SdpAlloc: - Failed to alloc SDP error
No voice for CFNA
H323 process leaking memory
audit call-agent returns mismatch error of shared memory status =null
Assigning CW, CIDCW to MLHG subscriber causes AR to fail.
Make codec filtering at H3A TG QOS table default OFF
calls w/o ANM disconnect after 4 minutes
In case of NCS GWs no need to play CW Tone more than once.
Event messages related event logs
NUMBER parameter no longer valid and SEVERITY is inconsistent
checklog program did not archive oversize log files
RDS incorrectly reports timeouts to application
S7M does not direct S7A to exit in a timely fashion
CA picks up wrong preferred codec when termination h323 TG not set QOS
Call failed due to different codec negotiation failure
Change of table dial-plan is using wrong digit-parser
Can not change an entry in table digman
DAT column should be type DATE for all measurement tables.
BCM core dump
Invalid fields in table carrier
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
48
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdy12161
CSCdy12738
CSCdy13061
CSCdy13110
CSCdy14313
CSCdy14536
CSCdy14688
CSCdy14700
CSCdy15505
CSCdy15568
CSCdy15685
CSCdy15997
CSCdy16054
CSCdy16577
CSCdy16578
CSCdy16581
CSCdy16673
CSCdy17109
CSCdy17241
CSCdy17369
CSCdy17376
CSCdy17808
CSCdy17882
CSCdy17896
CSCdy18022
CSCdy18064
CSCdy18278
CSCdy18399
CSCdy18443
CSCdy18529
CSCdy19189
CSCdy19466
CSCdy19695
CSCdy19726
CSCdy20205
CSCdy20303
CSCdy20395
CSCdy20571
CSCdy20581
CSCdy20657
CSCdy21613
Description
CA does not delete OBLV Connection
CFNA not functioning with on-net to on-net calls
no dial tone to active CFNA
Remove unnecessary TRACE log for PacketCable EM feature support
Need to be able to assign multiple MyLRNs in a POP
Slow start CFB to slow start, call failed due to codec
No communications received from feature server in trace
billing server bdms01 cores and exceeds restart
User data modified prior to pick-list check.
CNM change for DTMF RELAY for H323-H323 call
Outbound caller ID does not display on some PRI calls
MGA fails warmstart when there are thousands of gateways
Platform stop killing logins
CCM to PSTN call fails if PSTN uses a codec list
NOD-WB-LIST in COS-RESTRICT only work in BLACK list
CWD with a CCM call leg fails
RADIUS-PROFILE TSAP-ADDR does not accept port
EDCS-216305 mandates changes to architecture
Trace printing improper data
S7M dies after switchover
In the billing record fill codec field correctly for sstss calls
EMA is not registered for CA-CONFIG insert triggers
Update help files for Releases 3.2 and 3.3 of the BTS 10200
H323 GW2GK entry can be deleted while GW is in-service
dbm_sql failed to start up
ISDN calls are released when circuits are idle/active
BCM overwrites some parameters for SIP-T
CA sends RELEASE w/o cause #96 when DISC w/o cause is received
New security package from PGW to be added to BTS
Incorrect NOA for RGW to SS7 International Call.
SIP stack cannot decode SIP-T 180 ringing message
MGA auditing OOS endpoints when connectivity to GW is restored
NAS IPaddress attribute on Radius record is hard coded
Attribute Count on EM header shows wrong value
Handling remote side connection statistics in DLCX ack
Trace log stopped writing and trace log files missing
BTS needs to use mgw TSAP-ADDR for MTA-Endpoint-Name in EM per spec
h3a call leg not released when call is released immediately after SetupInd
CCM-->BTS-->IOS GW not working unless ALERTING is sent
BTS allows mgw id > 16 character, but control mgw truncates
Non-MGCP-MGCP calls ec, ss not correctly set in CRCX
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
49
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdy21635
CSCdy21653
CSCdy21714
CSCdy21969
CSCdy22420
CSCdy22436
CSCdy22532
CSCdy22645
CSCdy22833
CSCdy23117
CSCdy23118
CSCdy23663
CSCdy23756
CSCdy23962
CSCdy24049
CSCdy24212
CSCdy24264
CSCdy24384
CSCdy24897
CSCdy25464
CSCdy25505
CSCdy25721
CSCdy25777
CSCdy26179
CSCdy26223
CSCdy26498
CSCdy27059
CSCdy27392
CSCdy27461
CSCdy27471
CSCdy27938
CSCdy27991
CSCdy28423
CSCdy28597
CSCdy29533
CSCdy29653
CSCdy29796
CSCdy30116
CSCdy30150
CSCdy30736
CSCdy31014
Description
RSVP Not working
T38 fax does not work for h323 fast-start originated calls
libSEM reports SEM not initialized
Signaling Start message gets generated on off-hook (no dialed number)
EMA needs to support time change and replication of BCM event count
OAMP Performance and Resource Consumption improvements
EM-BILLING-SUPP not changed during initial ca-profile add
No FEID on Call Answer Message
SIA always sends PI #8 to BCM in Progress request and Alerting request
Corba needs to provide compatibility check with clients
No Carrier Identification Code on Interconnect Start/Stop
INTER AC not working when term sub goes off-hook during special rings
Provide incorrect controller address for MoveClDeletePL OP
EMS cant register with SNMP (Level now Severity)
Invoke of CPRK caused FSPTC to core dump
NAS IP address not populated for EM Encoding Version 3
Maintenance event and alarm could not display because mismatch type=Maint
Changing qos on CAS main sub caused transaction-queue problem
SIP-T mime attachment lost Content-Transfer-Encoding
Sequence Number in EM_Header is always all zeros
Event_time in EM_Header is always all zeros
Traffic Measurements cannot be displayed.
EMA Cores at Trace statement in library
FEID truncated
Mate version comparison is not being done correctly, causing replication to fail
BTS fails to do an LNP dip on an 800 SCP response with a ported number
MGCP-TERM-INIT-LEVEL based initialization feature not working
PacketCable EM Time Change needed for Daylight savings etc.
CA sends RELCOMP w/cause 34 instead of 44 when channel is OOS
cos-restrict cannot be changed to null for subscriber
CNDB feature is not working properly.
Wrong Call-Type in Billing Record
circuits get hung when CALLP (another DS1) is received
Static build of rdm fails because of ssf and cnm libs.
Core dump when making DQoS to SIP call
Update TCA per code review
BTS does not check Radius authenticator
800 route by carrier without dial-plan, sub orig. is not working
Neg-testing after down/up pri & back dchannel unable to place new calls
No Answer Timers not working
Mac GUI will not start with telnet nor ssh
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
50
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdy31174
CSCdy31394
CSCdy31738
CSCdy31758
CSCdy31787
CSCdy31849
CSCdy32192
CSCdy32231
CSCdy32927
CSCdy33024
CSCdy33186
CSCdy33199
CSCdy33372
CSCdy33575
CSCdy33996
CSCdy34046
CSCdy34052
CSCdy34069
CSCdy34092
CSCdy34493
CSCdy34737
CSCdy34764
CSCdy34800
CSCdy34827
CSCdy35288
CSCdy35321
CSCdy35553
CSCdy35572
CSCdy35653
CSCdy35775
CSCdy35934
CSCdy36739
CSCdy38886
CSCdy38922
CSCdy39006
CSCdy39080
CSCdy39279
CSCdy39523
CSCdy40015
CSCdy40022
CSCdy40184
Description
POTS is not exit after control FS switchover
MGA process does not update watchdog timer that cause pmg to go down
BTS10200 sends 2 8XX queries to FSAIN instead of 1.
Need to exclude optional fields for non required features on event Messages
CWD 2nd call hang up first, cant go back to 1st call
Dialed digits got lost for CAS DT package originated call
BCM cannot route the call fro MYLRN when received from LNP QUERY
CWD and CFNA interaction problem
NAS-IP-Address should precede Acct-STATUS-TYpe as per EM specifications
RDM CORE in sis_set_call_data due to error in sim_set_call_data
apache web server chunk handling vulnerability
CIDCW interaction with CFNA...call answered still forwarded
H323 SlowStart call should be Cleared if QOS ID is not present in TG
Invalid BCID Generated for I02
tracechk tool erroneously reports failure
BCM Process not checking for the Mode in the MDCX.
Default codec for the china market should be PCMA
RKS does not switch back from file on recovery
NorthBound Traffic is not working
Time_Change EM not generated
Network Specific Toll Free to SS7 gives wrong CgPN
SS7 toll free call gets incorrect OLI parameter
CAS-RGW clear back fails after failover of call agent
If TCS is received before CreateCx call fails
SCF not handling SIP BYE message properly
Chg port on gw w/out putting OOS is bad
Support for ISUP trunk (IT) package for TGCP
RADIUS-PROFILE TSAP-ADDR accepts invalid IP address
no r-dir sent in LCO for RSVP and RSVP features fails
BCM dead after CA switchover, caused by SIM relation data mismatch
Provisioning of 30 and 60 minute Collection Intervals Not Functioning
CNAME does not work for SS7-MGCP and CFB to MGCP
Miscellaneous issues with software upgrade from 2.1 to 3.3
COT fails when process S7A4 initiates request
Circuits are IDLE instead of RBLK when ISDN_Farend_init=Y
Newly added mgw not get allocated to worker thread in warm start.
Formatting wrong if try to immediately perform second CA switchover
CA fail the call when a gate control msg received with unexpected contents
open cursor error received when adding subscribers
maximum open cursor exceeded error received for office-code
Redundant SigStart msg for wiretapped terminating subscriber
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
51
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdy40193
CSCdy40392
CSCdy40603
CSCdy40763
CSCdy40993
CSCdy41343
CSCdy42347
CSCdy42999
CSCdy43074
CSCdy43667
CSCdy43779
CSCdy43921
CSCdy44248
CSCdy45544
CSCdy45552
CSCdy46445
CSCdy46620
CSCdy46801
CSCdy46823
CSCdy46907
CSCdy47278
CSCdy47290
CSCdy47656
CSCdy48180
CSCdy48549
CSCdy49376
CSCdy50328
CSCdy50355
CSCdy50371
CSCdy51821
CSCdy51833
CSCdy51971
CSCdy52459
CSCdy52935
CSCdy53116
CSCdy53384
CSCdy53639
CSCdy53811
CSCdy54272
CSCdy54345
CSCdy54361
Description
Table region-profile runs out of mem in shared mem
DOMAIN_NAME_CACHING_UNSUPP=Y should be defaulted to N
Clearing of TMM Reports generates Error
COT Trace not generated
Call Park timed recall is not working
No signaling stop when called party is busy
stack dump for MGA watchdog expiry
TG-Usage Summary Requests Return Database is Void of Entries Error
Share Memory mismatch after subscriber do 2nd *52 (CHD)
H3A process heap memory leak under high traffic
potsctx_repl_verify unable to print assigned features in subscriber table
“CNM, GCM code review update”
Trunk-group restore does not clear LBLK term-fault reason
200 OK is sent for invalid RSIP
soak traffic with CFU caused sim core
AC did not function right after FS switchover
Traffic measurement via SNMP is broken
New process KMS needs to be created
RNI information incorrect
Can not delete token from table special-call-type
connect/disconnect glare between appl and stack
Hop tree goes out of memory during capacity testing
call not term. for LNP ported-out. interswitch LNP call
no STATUS(99) message when SETUP w/invalid IE is received
H3A cores during capacity if socket multiplexing is on
No Call Content on TWC
AC is not working for ported-out subscriber
BCM WatchDog timer exp because of RWLock in SHM
Billing (6) Event Not Being Generated
BCM use wrong index copying FEID for CALEA call
ISUP 7d call fails to LNP lookup when prefix digits done in dial-plan-profile
show event log causes java.lang.OutOfMemoryError and locks up session
H3A stack cores after making on-net to off-net call
Intralata 1+7D and 0+7D calls failing
Revised security features to harden OS and control services.
MGA stuck in termination recovery loop
platform goes down due to trace compaction thread watchdog timeout
CPA not checking 4 out of range message length
BTS send s=on in lco when MTA does not support it.
CNM changes to support packet cable security parameters
Forwarder phone continues ringing when CFNA to offnet via SIP trunk
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
52
OL-1835-04
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdy56810
CSCdy56900
CSCdy57188
CSCdy57230
CSCdy58053
CSCdy58505
CSCdy59000
CSCdy59156
CSCdy59796
CSCdy59856
CSCdy61413
CSCdy61657
CSCdy61912
CSCdy61971
CSCdy62532
CSCdy64086
CSCdy64095
CSCdy64568
CSCdy65161
CSCdy65277
CSCdy65902
CSCdy66435
CSCdy66823
CSCdy66933
CSCdy67124
CSCdy68088
CSCdy68921
CSCdy68965
CSCdy69550
CSCdy71873
CSCdy73195
CSCdy73446
CSCdy74414
CSCdy74415
CSCdy74470
CSCdy74570
CSCdy74585
CSCdy75622
CSCdy75631
CSCdy76172
Description
H3A crashes in CNM library
SIM: Build a tool to print sim state information from debug file
Data in RPC field in ss7_cic table should be derived from DPC
Potential routing problem under load when not using ras
800 call without CgPN does not perform local query.
TG-Usage Summary only Reports Data on First Trunk-Grp in Database
Retransmission of command to be done at least after 5 secs after receiving
provisioning
ISDN PRI call fails when receiving STATUS after CONNECT
s7m/s7a robustness
SDP is not available when sip to rgw and CFNA to sip
PlatformLastChangeOverTime not maintained by KAM
lib/cslp/racf/racf_service_logic.c has incorrect number of TRACE argument
Call Forwarding features: necessary changes basing on deep code review
Basic DQoS calls not working
Data conversion from 2.1 to 3.3 upgrade
BTS changes LCO t: value in MDCX from what was specified in CRCX
TVT crashes
MGCP_PC_SEC_UNSUPP=N should be defaulted to Y
IC circuit gets hung when BCHAN_NEG_SUPP=N and CA receives diff. channel
incorrect event msg for SS7 traffic
RDM core when data is being replicated from 2.1 to 3.3
database mismatch when audit subscriber service profile sub id=xxxx
dial-plan table no longer able to prefix digits to 7 digit calls
need omni isup_conf_info file to address exception cases
Fail to insert Gate Alloc into AVLTREE
S7M died after call-agent switchover
name and number not toggle when *67 or *95 then *66 for AC/AR
No Answer Timer does not works for International Call.
SS7 call without CgPN cannot complete to DRCW line.
MGA core when running 15cps mgcp-ip hash table overflow warnings
BCM - COS with 0 or 00 Operator call fail
Event threshold broken for EGA -EMS has High CPU as a result
EM shared memory not replicated when EM-BILLING-SUPP changed
if dn2subscriber lnp_trigger=Y switch routing through destination
Trunk Terminations go to UNEQUIP during Reset operations
RDM Core
RES (resume) message is not passed out from the BTS to h323 trunk
Remove unused third party code for copyright reason
Step to alter tablespace temp missing from hotback DB recovery
Security pkg BTShard removes lines need by omni GUI from inetd.conf
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
53
Caveats
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdy76330
CSCdy76337
CSCdy76361
CSCdy77068
CSCdy77830
CSCdy78779
CSCdy79347
CSCdy79840
CSCdy80000
CSCdy80674
CSCdy81971
CSCdy83677
CSCdy84852
CSCdy85362
CSCdy85597
CSCdy85688
CSCdy86352
CSCdy89602
CSCdz00392
CSCdz00394
CSCdz01888
CSCdz03250
CSCdz03461
CSCdz04544
CSCdz06016
CSCdz06317
CSCdz06384
CSCdz06694
CSCdz08090
CSCdz08366
CSCdz08396
CSCdz08396
CSCdz08484
CSCdz08501
CSCdz08701
CSCdz09304
CSCdz09797
CSCdz09987
CSCdz13178
CSCdz15218
Description
Incorrect TRACE syntax
fs/lib/tcaf/tcaf_lm_alarm_hdlr.c - incorrect TRACE syntax
ca/sga/sga_isup_handler.c has incorrect TRACE0 syntax
Upgrade from 3.1 to 3.3
BLP.log should not have password in plain text
SUBCRIBER 1+TOLL fails when POP field ITP=N and trace level=5
Encoding error in LCO while sending MDCX for DQoS calls
needs to change mem.cfg files to reflect new changes in sizes for 3.3
BLV teardown send off hook warning tone to subscriber
BTS 3.3 Call Failure Trap not encoded correctly
Fix TRACEs in C++ code
AR - send sub id with garbage information
Need new triggers and scripts to limit EMS down time
SS7 Generic Name parameter sends 16 characters
Loading watchdog timer w/default in updateRSIPDelayInTermTable()
Connection is not deleted after user abandon the call with invalid digits.
BTS fails parsing SDP from Harris Modem
Service Instance EM has wrong RelBCID/BCID for Call Waiting
CA146: orphaned process found, switchover, SS7 failed
Alarm not defined correctly in ReportParameters.cfg
BLG core after blg dies and restarts
DQOS CFNA not working properly
IPmanager prog runs at wrong nice state
After installing security packages, the system must be rebooted at end of instal
EMA dies due to Recv thread watch dog
ISDN data got corrupted when upgrade load from 2.1 to 3.3
CALL_AGENT_TSAP_ADDR got corrupted in table rudp-backhaul-session
/opt become full, BDMS stopped generating CDR logs
connection is not cleared upon 502 Active connection exists
Changing MGCP-MAX-UNREACH-COUNT/MGCP-MAX-FAULT-COUNT
lower bound to 0
Call is received on a non-existent termination CA seems to hang
Call is received on a non-existent termination CA seems to hang
International dial plan fails after 2.1 to 3.3 upgrade.
dchannel goes down/up intermittently
rel 2.1 upgrade fails to convert Mid-call feature
ISDN local call mapped to CdPN TON=3 (network specific)
ISDN tg-profile changed to inband-info=n on 2.1-3.3 upgrade
rel 2.1 upgrade fails to convert traffic_type in trunk-grp table.
ENHANCEMENT: RDM has to report replication status to nodestat
Software Upgrade: connection ID is not replicated during fallback
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
54
OL-1835-04
Documentation Updates
CISCO CONFIDENTIAL
Table 3
Resolved Caveats (continued)
DDTS ID
CSCdz16674
CSCdz19741
CSCdz20056
CSCdz20947
CSCdz21165
CSCdz24192
CSCdz24722
CSCdz24763
CSCdz25893
CSCdz26349
CSCdz26515
CSCdz27017
CSCdz27541
CSCdz28039
CSCdz29593
CSCdz29911
CSCdz30985
CSCdz31231
CSCdz33172
CSCdz34907
CSCdz36027
CSCdz36027
CSCdz37559
CSCdz40696
CSCdz43454
CSCdz43543
CSCdz46560
CSCdz46744
CSCdz48149
CSCdz48216
CSCdz52339
CSCic04603
CSCic05344
CSCic06186
CSCuk35667
Description
CRCX_ACK was not reported to CNM for dollar CRCX
EM Service Activation not generated
Lost of dial-tone after recovery from lost of ip connectivity
annc trks are idle, calls get busy, annc trks hang
NOD_WB_LIST type for some block calls were set to NONE during upgrade.
Sync SUBSCRIBER_FEATURE_DATA cause oracle error
Call Agent passes call on a termination with ss7 cic table error
EMS gives Network Device Already in Use Errors Statusing Subscribers
G711u should map to PCMU in QOS table during 3.3 upgrade
data conversion for upgrade from 2.1->3.3
BTS generates incorrect Single Interface Restart message
BTS change packetization period to p:68
MGA core dumps after 11 hours of traffic
Traffic Not Being Collected After 10 Days of System Time
ANM core dump at startup
Wrong index_t is used for copying of sub index
Outgoing HB (Heart Beat) period exceeds MAX and shuts down platforms
BDMS01 OUT Service due to CallDetail table is full
3.3 to 2.1 fallback failed
tz_localtime is setting external variable tzname
data replication problem -- AVL tree corrupt for table trunk-grp
data replication problem -- AVL tree corrupt for table trunk-grp
Allow release 3.3 to be protocol compatible with ECN-02148
ISDN will cause CA out of service when fallback from 2.1 to 3.3
mga spitting out wrong trace: Invalid type of service, tos=255
BTS does not send DLCX after receiving a 526
ANM failed in ModifyCL
AUEP keep-alives (pings) stop after IP address change of MTA
Correct status application broken by CSCdz13178
s7a interworking, some ACMs result in progress=0 being sent to PRI
SIP sends privacy information to POTS in the CallingDN instead of seperate
param
Implement priority handling in IPC mechanism
IPC pool status in the PDM tool is not displayed properly
Additional DN2 Sub Entries can be added
ACR does not reject incoming call from SS7 with CLI missing
Documentation Updates
This section contains known documentation changes.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
55
Related Documentation
CISCO CONFIDENTIAL
The following information was changed in the Cisco BTS 10200 Softswitch Command Line Interface
Reference Guide to reflect changes since Release 3.1:
•
Deleted—DEFER value for the H245-TUNNELING token in the h323-gw table.
The H323 gateway (h323-gw) table defines the capabilities of each H.323-based gateway. The
H245-TUNNELING token in the h323-gw table previously accepted one of three values: DEFAULT,
DEFER, or DISABLE.
The requirement for the DEFER value was there because of a defect in IOS-based gateways, which
has since been fixed. The DEFER value is not valid and is not accepted effective with Release 3.2.
(See CSCdy55256, “SS7 to H323 with H.245 TUNNELING=DEFER does not complete.”)
Note
Changes applicable to a specific software release are so noted in the reference guide.
The following information was added to the Cisco BTS 10200 Softswitch Building Environment and
Power Site Survey for DC-powered systems:
•
The nominal current rating for a complete Cisco BTS 10200 system is 26A at -48 VDC, and the
maximum current rating is 40A at -48 VDC.
The following information was changed in the Cisco BTS 10200 Softswitch Network Site Survey for
Software Installation to reflect changes to the opticall.cfg installation file since Release 3.1:
•
Added—parameters for POTS TCA process
•
Removed—Allow Telnet Sessions
The following information was changed in the Cisco BTS 10200 Softswitch Network Information Data
Sheet for Software Installation to reflect changes to the opticall.cfg installation file since Release 3.1:
•
Note
Added—Target Market=North America
Target Market=China is not valid for Release 3.3 V04.
•
Added—parameters for POTS TCA process
•
Added—comment regarding MEM_CFG_SELECTION (not used)
•
Added—comment on GDRS_ENABLED parameter
•
Added—comment on H323_ENABLED parameter
•
Added—BDMS INSTALLING LIST parameter
•
Updated—DNS parameters (to match opticall.cfg file)
•
Removed—Allow Telnet Sessions
Related Documentation
The Release 3.3 Feature Modules and Release Notes should be used in conjunction with the following
Cisco BTS 10200 Release 3.1, Release 3.2, and Release 3.3 documents:
•
Cisco BTS 10200 Softswitch Physical and Network Site Surveys and Data Sheets
•
Cisco BTS 10200 Softswitch Cabling Procedures
•
Cisco BTS 10200 Softswitch Application Installation Procedures
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
56
OL-1835-04
Obtaining Documentation
CISCO CONFIDENTIAL
•
Cisco BTS 10200 Softswitch System Description
•
Cisco BTS 10200 Softswitch Operations Manual
•
Cisco BTS 10200 Softswitch Event Messages Guide
•
Cisco BTS 10200 Softswitch Billing Interface Guide
•
Cisco BTS 10200 Softswitch Command Line Interface Reference Guide
•
Cisco BTS 10200 Softswitch CORBA Installation and Programmer's Guides
All Cisco BTS 10200 Softswitch user documentation can be accessed through the following location:
http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/index.htm
The Cisco BTS 10200 Softswitch user documentation is password protected. Consult your Cisco
representative for access.
Feature Modules
Release 3.3 Feature Module documentation includes the following:
•
Cisco BTS 10200 Softswitch PacketCable Feature Module
•
Cisco BTS 10200 Softswitch Inter-Office Auto Callback–Auto Recall Feature Module
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Note
•
http://www.cisco.com
•
http://www-china.cisco.com
•
http://www-europe.cisco.com
Documentation for the Cisco BTS 10200 on the World Wide Web sites listed above is currently
available only through password access. Contact your Cisco representative for assistance.
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships
with your product. The Documentation CD-ROM is updated monthly and may be more current than
printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Note
Documentation for the Cisco BTS 10200 is not currently available on the Documentation CD-ROM.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
57
Obtaining Technical Assistance
CISCO CONFIDENTIAL
Ordering Documentation
Cisco documentation is available in the following ways:
•
Registered Cisco Direct Customers can order Cisco Product documentation from the Networking
Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
•
Registered Cisco.com users can order Documentation CD-ROMs through the online Subscription Store:
http://www.cisco.com/go/subscription
•
Nonregistered Cisco.com users can order documentation through a local account representative by
calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by
calling 800 553-NETS(6387).
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical
comments electronically. Click Feedback in the toolbar and select Documentation. After you complete
the form, click Submit to send it to Cisco.
You can also e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or
write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can
obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com
registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open
access to Cisco information and resources at anytime, from anywhere in the world. This highly
integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline
business processes and improve productivity. Through Cisco.com, you can find information about
Cisco and our networking solutions, services, and programs. In addition, you can resolve technical
issues with online technical support, download and test software packages, and order Cisco learning
materials and merchandise. Valuable online skill assessment, training, and certification programs are
also available.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
58
OL-1835-04
Obtaining Technical Assistance
CISCO CONFIDENTIAL
Customers and partners can self-register on Cisco.com to obtain additional personalized information and
services. Registered users can order products, check on the status of an order, access technical support,
and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product
or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC
website:
http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
•
P3—Your network performance is degraded. Network functionality is noticeably impaired, but most
business operations continue.
•
P4—You need information or assistance on Cisco product capabilities, product installation, or basic
product configuration.
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users
can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and
immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following
website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•
P1—Your production network is down, causing a critical impact to business operations if service is
not restored quickly. No workaround is available.
•
P2—Your production network is severely degraded, affecting significant aspects of your business
operations. No workaround is available.
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
59
Obtaining Technical Assistance
CISCO CONFIDENTIAL
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
60
OL-1835-04