Guest

Cisco BTS 10200 Softswitch

Field Notice: FN - 62308 - BTS 10200 R3.X Call Agent Utilizing the Omni SS7 Stack Can Have Circuit Identification Code (CIC) Mismatches Between the Call Agent and the Omni SS7 Stack


Revised February 8, 2006

February 6, 2006

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Product Affected

Comments

BTS Other - 3.X

BTS 10200 R3.X call agent utilizing the Omni SS7 stack.

Problem Description

Circuit Identification Code (CIC) mismatches between the call agent and the Omni SS7 stack.

Background

It has been reported that managing CICs add/deletes over time could cause a CIC mismatch between the call agent and the Omni SS7 stack.

Mismatches between the call agent and the Omni stack will happen if CICs are added while one side of the call agent is active, then later deleted when the other side is active. When CICs are added, Omni associates them with either the A-side or the B-side. If a CIC added while the A-side is active is later deleted when the B-side is active, Omni will return "success" to the call agent, but will not delete the CIC from Omni's registry. This causes a mismatch. The CIC is deleted from the call agent, but still exists in Omni's registry. Further attempts to re-add the same CIC will be unsuccessful.

Problem Symptoms

Cannot add CICs to the call agent.

Workaround/Solution

The workaround would be to ensure that all SS7 CICs are managed (added/deleted) on one call agent instance, preferably side A. This will ensure all CICs are associated to one BTS instance, keeping the call agent and the Omni SS7 stack in sync.

The following procedure will assist BTS Users in identifying which CIC is associated with what BTS instance so the User can ensure the CIC is managed on the proper BTS instance:

The command is available in BTS CA /opt/omni/bin directory. The OMNI tool is a7isdbg "

From BTS CA unix prompt under /opt/omni/bin issue..

unix btsca> a7isdbg a7n1

ISMG dbg cmd> #is,cic <-----(this command displays CIC ownership)

ISMG application CIC registration:

..... 
aix = 4, application = bts-ca-2.a7n1_isup_4, backup = bts-ca-1.a7n1_isup_4 
rs = 3, DPC=239-8-4 
min = 2501, max = 2596 
min = 2601, max = 2696 
min = 3001, max = 3004 
aix = 5, application = bts-ca-1.a7n1_isup_2, backup = bts-ca-2.a7n1_isup_2 
rs = 3, DPC=239-8-4 
min = 961, max = 962 
min = 2101, max = 2124 
aix = 6, application = bts-ca-1.a7n1_isup_1, backup = bts-ca-2.a7n1_isup_1 
rs = 3, DPC=239-8-4 
min = 25, max = 25 
min = 1425, max = 1496 
.... 

In the above output, bts-ca-1 is Side A of a duplex BTS, while bts-ca-2 is the Side B.

CICs 2501 - 2596 are owned by bts-ca-2

CICs 2601 - 2696 are owned by bts-ca-2

CICs 961 - 962 are owned by bts-ca-2

CICs 25 and 1425-1496 are owned by bts-ca-1

While on RLS 3.x with Omni, there is a solution to permanently eliminate the problem so that CICs can be managed by either the A-side or the B-side without leading to mismatches between the call agent and Omni. Implementing the solution requires a brief full call processing outage. The solution involves changing the Omni ISUP application mode from "load share" (default) to "active-standby", as described in defects CSCdy66933 and CSCeb69782. The following steps are required to implement the solution:

  1. Put the omni configuration file into place to override default configuration on both A and B side of call agent

    - cp -p /opt/ems/utils/isup_conf_info.225 /opt/omni/conf

  2. Stop the standby side call agent/feature server

    - platform stop all

  3. Stop the active side call agent/feature server

    - platform stop all

    *** Note: full call processing outage is encountered here ***

  4. Restart the side that was last active

    - platform start

  5. Restart the remaining side

    - platform start

This will be resolved in the RLS 4.x BTS application due to the elimination of the Omni SS7 stack.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCdy66933 (registered customers only)

Need OMNI ISUP_CONF_INFO file to address exception cases

CSCeb69782 (registered customers only)

ISUP_CONF_INFO file is available but not installed

Revision History

Revision

Date

Comment

1.1

08-FEB-2006

Edited format in Workaround/Sol

1.0

06-FEB-2006

Initial Public Release

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.