Cisco Bts 10200 Soft Switch

Cisco BTS 10200 Softswitch Operations and Maintenance GuideRelease 4.1, 4.2, and 4.4

October 13, 2006

Corporate HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 526-4100

Text Part Number: OL-4495-04

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Cisco BTS 10200 Softswitch Operations and Maintenance GuideCopyright © 2006, Cisco Systems, Inc.All rights reserved.

CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)

Cisco BTOL-4495-04

C O N T E N T S

Preface xv

Document Objective xv

Audience xv

Document Change History xv

Document Organization xvii

Document Conventions xviii

Documentation Suite xx

Obtaining Documentation xxi

Cisco.com xxi

Documentation CD-ROM xxii

Ordering Documentation xxii

Documentation Feedback xxii

Obtaining Technical Assistance xxii

Cisco TAC Website xxiii

Opening a TAC Case xxiii

TAC Case Priority Definitions xxiii

Obtaining Additional Publications and Information xxiv

C H A P T E R 1 Hardware 1-1

Rack Configuration 1-1

Power On and Off 1-4

Power On Procedure 1-4

Power Off Procedure 1-4

Hardware Monitoring 1-6

CPU 1-6

Memory Consumption 1-6

Disk and Disk Utilization 1-6

Alarm Reports 1-6

Hardware Monitoring Commands 1-7

Host Operating System Time 1-10

Intelligent Alarm Panel 1-10

iiiS 10200 Softswitch Operations and Maintenance Guide

Contents

C H A P T E R 2 Operator Interfaces 2-1

Logging in Using Secure Shell 2-2

EMS Services 2-3

EMS Users and Services Commands 2-3

Show 2-3

Change 2-3

EMS NTP Server Configuration 2-3

C H A P T E R 3 Provisioning External Media Gateways 3-1

C H A P T E R 4 Managing Access and Users 4-1

User and Command Privilege Levels 4-2

Command Level Provisioning 4-2

User Account Administration 4-3

Predefined User Accounts 4-3

Users 4-3

Invalid User Privilege Level 4-4

User and Optiuser Set Password/Reset Password 4-4

Command Table 4-5

Workgroups 4-7

Adding Descriptions to Security Classes 4-7

Session Manager 4-8

Show Command 4-8

Block Command 4-9

Change Command 4-9

Unblock Command 4-9

Stop Command 4-10

Security Summary Report 4-10

C H A P T E R 5 Digit Manipulation 5-1

Digit Manipulation Rules 5-2

Digit Manipulation Tables 5-6

Pretranslations Stage 5-8

Dial Plan Profile Table 5-8

International Dial Plan Profile Table 5-8

Translations Stage 5-9

Dial Plan Table 5-9

International Dial Plan Table 5-10

ivCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

Digit Manipulation Profile Table 5-10

Digit Manipulation Table 5-10

Sample Provisioning 5-16

Routing Stage 5-16

Destination Table 5-17

Route Table 5-17

Trunk Group Table 5-17

C H A P T E R 6 Local Number Portability 6-1

Introduction to LNP 6-1

LNP Implementation 6-2

Process Flows 6-3

Flow Chart Legend 6-3

Service Provisioning 6-4

Service Order Cancellation 6-5

Service Disconnection 6-6

Conflict Resolution 6-7

Audit Requests 6-8

Report Requests 6-8

Data Management 6-9

NPAC Network Data 6-9

Service Provider Data 6-9

Subscription Version Data 6-9

Troubleshooting LNP Problems 6-9

Cisco BTS 10200 Softswitch LNP Function 6-10

Establishing a Session 6-10

Logging in Using Secure Shell 6-10

Logging in to the Secondary EMS (Optional) 6-11

Provisioning Ported Office Codes 6-12

Provisioning the Unconditional LNP Trigger 6-13

Provisioning Ported Numbers 6-14

Porting-in a Subscriber 6-14

Provisioning Ported-in Numbers 6-14

Transition Period 6-16

Changing lnp-trigger to Y 6-17

Activating a Media Gateway 6-17

Activating a Subscriber 6-18

Changing lnp-trigger to N 6-18

LNP Call Flow 6-19

vCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

Porting-out a Subscriber 6-20

Changing lnp-trigger to Y 6-20

Changing DN Status to Ported-Out 6-20

Deactivating Service 6-21

Local Exchange Routing Guide 6-22

C H A P T E R 7 Maintenance and Administration of System Components 7-1

Redundant Architecture 7-1

Status and Control States 7-2

Success and Failure Responses 7-2

Status States 7-3

Control States 7-4

Status Application Command 7-4

Control Application Command 7-5

Call Agent Status and Control 7-6

Status Command 7-6

Control Command 7-6

Feature Server Status and Control 7-7

Status Command 7-7

Control Command 7-7

Element Management System Status and Control 7-7

Status Command 7-7

Control Command 7-8

Bulk Data Management System Status and Control 7-8

Status Command 7-8

Control Command 7-9

Additional BDMS Status and Control Examples 7-9

Status System Command 7-10

Process Restartability 7-11

Host Operating System Time 7-11

Guidelines for Regular System Health Checks 7-12

Read the Automatic System Health Report 7-12

Check System Clocks 7-16

Check Billing Server and Local Billing Directory 7-17

Check Traffic Measurements 7-18

Check Event and Alarm Reports 7-18

Perform Database Backup 7-18

Check OS Log 7-18

Check Mirroring On the Disk 7-19

viCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

CA/FS Side A 7-19

CA/FS Side B 7-20

EMS Side A 7-21

EMS Side B 7-21

Audit Database 7-22

Backup Software Image 7-22

Task 1: Ensure Side A System is ACTIVE 7-23

Task 2: Perform a Full Database Audit 7-23

Task 3: Perform Shared Memory Integrity Check 7-23

Task 4: Perform Flash Archive on EMS Side B 7-25

Task 5: Perform Flash Archive on CA/FS Side B 7-26

Task 6: Switch Activity from Side A to Side B 7-27

Task 7: Perform Flash Archive on EMS Side A 7-28

Task 8: Perform Flash Archive on CA/FS Side A 7-29

Task 9: Release Forced Switch 7-30

Check DNS Server 7-31

Run Diagnostic On Trunk Group 7-31

Run Diagnostic On Subscriber Terminations 7-31

Check Power Supply 7-32

Clean Filters 7-32

C H A P T E R 8 Maintenance and Diagnostics for External Resources 8-1

Service States—Overview 8-1

Status, Control, and Administrative Commands 8-2

SIP Phone Address of Record and Registered Contact 8-3

SIP-REG-CONTACT 8-3

Aggregation Status 8-4

Destination Point Code 8-4

H.323 Gateway 8-5

Status Command 8-5

Control Command 8-6

ISDN Switchover 8-6

Media Gateway 8-7

Status Command 8-7

Control Command 8-7

Signaling Gateway Process 8-9

Status Command 8-9

Stream Control Transmission Protocol Association 8-9

Status Command 8-9

viiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

Control Command 8-9

Subscriber Termination 8-9

Status Command 8-12

Control Command 8-14

Subsystem 8-16

Status Command 8-16


Trunk Group 8-16

Status Command 8-17


Trunk Termination 8-19

Status Command 8-22


Reset Command 8-26

Equip Command 8-27

Unequip Command 8-28

Diagnostic Tests 8-29

Media Gateway Tests 8-29

Subscriber Termination Tests 8-30

SS7 Trunk Termination Tests 8-32

ISDN Trunk Termination Tests 8-36

CAS Trunk Termination Tests 8-37

Announcement Trunk Termination Tests 8-38

Command Responses 8-39

Generic Responses to Status or Control Command Failures 8-39

Generic Success and Failure Responses 8-40

System Error Response 8-41

Termination Reason Responses 8-41

Trunk Reason Responses 8-42

Trunk Termination Reason Responses, SS7 Only 8-43

Fault Reason Responses 8-44

Status Update Processor 8-45

C H A P T E R 9 Managing Billing Interface and Billing Records 9-1

Record Retention Mechanisms in the EMS 9-1

Billing Alarm Tracking Mechanisms 9-1

Call Detail Block Correlation and Format 9-2

Northbound Billing Data Transport 9-2

viiiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

C H A P T E R 10 Traffic Measurements 10-1

Filtering Traffic Measurements 10-1

Traffic Measurement Data Transport and Access 10-2

Retrieving Traffic Measurement Report Summaries 10-3

Display Report Summaries on Operator Terminal 10-3

Create Report Summary Files 10-5

Report Current Interval Counts 10-7

Clearing Current Interval Counts 10-7

Format of Traffic Measurement Summaries 10-9

Events and Alarms for Traffic Measurement 10-9

List of Traffic Measurements (Counters) 10-10

Resources and Definitions 10-10

ISDN Measurements 10-10

Call Processing Measurements 10-12

MGCP Adapter Measurements 10-17

Session Initiation Protocol Measurements 10-19

Service Interaction Manager Measurements 10-21

POTS Local Feature Server Measurements 10-22

POTS Miscellaneous Feature Server Measurements 10-27

POTS Class of Service Feature Server Measurements 10-29

POTS Screen List Editing Feature Server Measurements 10-30

POTS Customer Originated Trace Feature Server Measurements 10-30

POTS Automatic Callback, Recall, and Call Return Feature Server Measurements 10-31

AIN Services Feature Server Measurements 10-32

TSA Protocol Measurements 10-34

SCCP Protocol Measurements 10-35

TCAP Protocol Measurements 10-37

INAP Protocol Measurements 10-41

SUA Measurements 10-44

M3UA Protocol Measurements 10-46

SCTP Protocol Measurements 10-48

ISUP (ANSI) Measurements 10-51

ISUP (ITU-China) Measurements 10-53

ISUP (ITU-Mexico) Measurements 10-55

ISUP (ITU-HongKong) Counters 10-57

Audit Measurements 10-59

SIP Interface Adapter Measurements 10-59

Call Detail Block Measurements 10-61

Event Messaging Measurements 10-63

ixCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

Dynamic QoS Measurements 10-63

SNMP Protocol Measurements 10-64

Trunk Group Usage Measurements 10-64

Announcement Measurements 10-66

H.323 Protocol Measurements 10-67

Call Tools Measurements 10-69

AIN Tools Measurements 10-70

PCT Tools Measurements 10-71

C H A P T E R 11 Audit Database and Table Name 11-1

Audit Database 11-1

Table Name 11-1

C H A P T E R 12 Show and Change Database Usage Commands 12-1

Show Command Paging Capability for Batch Data Retrieval 12-1

Example: Controlling the Volume and Format of Data 12-1

Example: Ordering and Displaying Specific Data 12-2

Show Database Usage Command 12-2

Change db-usage 12-2

C H A P T E R 13 Transactions 13-1

Transaction Queue 13-1

Show 13-1

Delete 13-1

Queue Throttle 13-2

Show 13-2

Change 13-2

C H A P T E R 14 History 14-1

Show 14-1

Report 14-1

C H A P T E R 15 Call Trace Summary 15-1

C H A P T E R 16 Command Scheduler 16-1

Show 16-1

Add 16-1

Change 16-2

xCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

Delete 16-2

C H A P T E R 17 SNMP Interface 17-1

Element Management System (SNMP Agent) 17-1

SNMP Agent Functions 17-1

Statistics/Traffic Measurement 17-2

SNMP Trap Reports 17-3

Status and Controls 17-4

Querying and Controlling EMS, BDMS, CA and FS 17-4

Querying and Controlling Various Components 17-4

Querying and Controlling Bulk Status of Various Components 17-5

Accessing the SUN Solaris SNMP Agent 17-6

Direct Access to a Non-Standard SNMP Port 17-6

Through the Cisco BTS 10200 Softswitch SNMP Master Agent Using Port 161 17-7

C H A P T E R 18 Managing Event Message and Alarm Logs 18-1

Managing Event and Alarm Reports 18-2

Show Alarm Command 18-2

Ack Alarm Command 18-3

Clear Alarm Command 18-3

Format of Event and Alarm Reports 18-3

Event Message and Alarm Logs 18-4

Viewing Event or Alarm Logs 18-5

Event Queue 18-6

Saving Events to Log Files 18-6

Show Report-Properties 18-6

Changing Report-Properties 18-7

Changing Threshold and Throttle Values 18-7

Managing and Responding to Events and Alarms 18-8

C H A P T E R 19 Event Messages and Alarms 19-1

C H A P T E R 20 Congestion Detection and Protection 20-1

Special Treatment for Emergency Messages 20-1

Billing Records 20-2

Events and Alarms 20-2

Additional References 20-3

xiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

C H A P T E R 21 Disaster Recovery Procedures 21-1

Flash Archive 21-1

Creating an Archive 21-1

Restoring an Archive 21-2

Booting Up the System From Disk 0 21-4

Restoring the Cisco BTS 10200 Softswitch Application 21-5

Setting Up Interfaces 21-6

Setting Up Mirroring 21-6

EMS Database Backup 21-8

EMS Database Disaster Recovery From Hot Backup 21-11

Recovery Goal 21-11

Recovery Procedure 21-12

Post Recovery – Cold Backup 21-15

Recovering the Oracle Secondary EMS Database 21-16

Recovering the EMS Database from Another Database 21-16

Recovery Procedures 21-16

Recovering Shared Memory Data 21-24

Recovering Shared Memory 21-24

Restoring Subscriber and Trunk Terminations to Service 21-25

Controlling Trunks and Trunk Groups 21-26

Using the cs-control Tool to Bring Subscribers In-Service 21-26

C H A P T E R 22 Manual System Recovery 22-1

Disk 1 on the Primary Call Agent and Feature Server is Corrupt 22-1

Disk 0 on the Primary Call Agent and Feature Server is Corrupt 22-2

Disk 1 on the Secondary Call Agent and Feature Server is Corrupt 22-4

Disk 0 on the Secondary Call Agent and Feature Server is Corrupt 22-5

Disk 1 on the Primary Element Management System is Corrupt 22-7

Disk 0 on the Primary Element Management System is Corrupt 22-9

Disk 1 on the Secondary Element Management System is Corrupt 22-10

Disk 0 on the Secondary Element Management System is Corrupt 22-11

C H A P T E R 23 Replacing a Disk 23-1

Before You Start 23-1

Replace Disk 0 on CA/FS and EMS 23-1

Replace Disk 1 on CA/FS and EMS 23-6

xiiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

A P P E N D I X A Feature Tones A-1

List of Tones Applicable to Specific Features A-1

Tone Frequencies and Cadences A-6

A P P E N D I X B Recoverable and Nonrecoverable Error Codes B-1

A P P E N D I X C Release Cause Codes C-1

xiiiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Contents

xivCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Preface

This preface describes the objectives, audience, organization, and conventions of this document and explains how to find additional information on related Cisco products and services.

Document ObjectiveThis guide provides instructions for operating, and maintaining the Cisco BTS 10200 Softswitch for release 4.1. You should read the other documentation supplied with your system before using this guide. A complete list of these documents is included in the Documentation Suite, page xx section of this guide.

AudienceThis guide is intended for three audiences: system administrators, system operators, and system technicians.

• The system administrator manages the host administrative functions, including configuring and maintaining system parameters, granting group and user IDs, and managing all Cisco MGC files and directories. The system administrator should have an in-depth knowledge of UNIX and a basic knowledge of data and telecommunications networking.

• The system technician should be familiar with telecommunication protocols, basic computer software operations, computer terminology and concepts, hierarchical file systems, common UNIX shell commands, log files, the configuration of telephony switching systems, the use of electrical and electronic telephony test equipment, and basic troubleshooting techniques.

Document Change HistoryTable 1 describes the change history for this document.

xvCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

PrefaceDocument Change History

Table 1 Change History

Release, Change Date Subject Change Summary

October 13, 2006

Chapter 10, “Traffic Measurements”

• Updated measurements tables with which counters are 4.4.0 and which are 4.4.1.

• Updtated measurements tables field names to match requirement specification.

August 14, 2006

Chapter 19, “Event Messages and Alarms

• Transfered the events and alarms information to the Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 4.4, Chapter 2 through Chapter 12.

June 16, 2006

Chapter 21, “Disaster Recovery Procedures”

• Replaced the section “Fresh Download” with “Recovering Shared Memory Data.” This new section contains new procedures and cautions.

4.1

December 1, 2004

Chapter 8, “Maintenance and Diagnostics for External Resources”

• Updated this chapter with a note on using the change/show commands to update or display the status of aor2sub.

• Removed the procedure for putting individual AORs in service (INS) or out of service (OOS).

4.1

Nov. 9, 2004

Chapter 21, “Disaster Recovery Procedures”

• Deleted the statement on creating the flash archive without disk mirror in the “Flash Archive” section.

4.1

Nov. 9, 2004

Chapter 20, “Backup and Restore”

• Deleted this chapter. The disaster recovery procedures in Chapter 21, “Disaster Recovery Procedures” define the correct method of doing backups (flash archive) and restores.

4.1,Oct. 27,2004

Chapter 19, “Event Messages and Alarms”

• Updated this chapter with a note pertaining to the Database #11 alarm that may report ORA-01595 and ORA-01594 errors in the alert.log file.

4.1,Oct. 14,2004

Chapter 8, “Maintenance and Diagnostics for External Resources”

• Added a table for RAS states for H.323 gateways.

4.1,Oct. 14,2004

Appendix D, “Deactivating and Acting Omni”

• Deleted this appendix.

4.1Oct. 11, 2004

Chapter 12, “Show and Change Database Usage Commands”

• Added description of the show command with paging capability.

4.4 Chapter 10, “Traffic Measurements”

• Added new measurements generated by the Query Verification and Translation Verification Tools in the “Call Tools Measurements”, “AIN Tools Measurements”, and “PCT Tools Measurements” sections.

4.4 Chapter 4, “Managing Access and Users”

• Added new predefined user accounts information in the “Predefined User Accounts” section.

4.2 Chapter 10, “Traffic Measurements”

• Added measurements for ISUP (ITU-HongKong) in the “ISUP (ITU-HongKong) Counters” section.

4.1 Chapter 23, “Replacing a Disk”

• Updated the disk replacement procedure in this chapter.

4.1 Initial version of this document.

• Made updates and added new information throughout this document using the Cisco BTS 10200 Softswitch Operations Manual Release 3.1 as a base.

xviCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

PrefaceDocument Organization

Document OrganizationThis document consists of the following chapters:

• Hardware

• Operator Interfaces

• Provisioning External Media Gateways

• Managing Access and Users

• Digit Manipulation

• Local Number Portability

• Maintenance and Administration of System Components

• Maintenance and Diagnostics for External Resources

• Managing Billing Interface and Billing Records

• Traffic Measurements

• Audit Database and Table Name

• Show and Change Database Usage Commands

• Transactions

• History

• Call Trace Summary

• Command Scheduler

• SNMP Interface

• Managing Event Message and Alarm Logs

• Event Messages and Alarms

• Congestion Detection and Protection

• Disaster Recovery Procedures

• Manual System Recovery

• Replacing a Disk

• Feature Tones

• Recoverable and Nonrecoverable Error Codes

• Release Cause Codes

xviiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

PrefaceDocument Conventions

Document ConventionsThis section describes the directory structure in which the Cisco BTS 10200 Softswitch software is installed. Refer to the Cisco BTS 10200 Softswitch Release 4.1 Software Installation Guide for a more detailed description of configuring the Softswitch environment.

Note Refer to the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide for a detailed description of all commands and tokens discussed in this document.

Typographic conventions used in this guide are shown in Table 2.

Table 2 Conventions Used in this Guide

Convention Meaning Description / Comments

Boldface Commands and keywords you enter as shown.

offset-list

Italics Variables for which you supply values.

command type interface

You replace the variable with specific information.

In contexts that do not allow italics, such as online help, arguments are enclosed in angle brackets (< >).

Square brackets ([ ]) Optional elements. command [abc]

abc is optional (not required), but you can choose it.

Vertical bars ( | ) Separated alternative elements.

command [ abc | def ]

You can choose either abc or def, or neither, but not both.

Braces ({ }) Required choices. command { abc | def }

You must choose either abc or def, but not both.

Braces and vertical bars within square brackets ([ { | } ])

A required choice within an optional element.

command [ abc { def | ghi } ]

You have three options:

nothing

abc def

abc ghi

Caret character (^) Control key. The key combinations ^D and Ctrl-D are equivalent: Both mean “hold down the Control key while you press the D key.” Keys are indicated in capital letters and are not case sensitive.

xviiiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

PrefaceDocument Conventions

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Timesaver Means reader may be able to save some time. Taking the action described could achieve a result in less time than might be achieved otherwise.

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.

Conventions used in the Cisco BTS 10200 Softswitch software are shown in Table 3.

A non-quoted set of characters

A string. For example, when setting an SNMP community string to public, do not use quotation marks around the string; otherwise, the string will include the quotation marks.

System prompts Denotes interactive sessions, indicates that the user enters commands at the prompt.

The system prompt indicates the current command mode. For example, the prompt Router (config) # indicates global configuration mode.

Screen font Terminal sessions and information the system displays.

Angle brackets (< >) Non-printing characters such as passwords.

Exclamation point (!) at the beginning of a line

A comment line. Comments are sometimes displayed by the Cisco IOS software.

Table 2 Conventions Used in this Guide (continued)

Convention Meaning Description / Comments

Table 3 Data Type Conventions

Data Type Definition Example

Integer A series of decimal digits from the set of 0 through 9 that represents a positive integer. An integer may have one or more leading zero digits (0) added to the left side to align the columns. Leading zeros are always valid as long as the number of digits is less than or equal to ten digits. Values of this type have a range of zero through 4294967295.

1230001234200000000

Signed integer

The same basic format as the integer but can be either positive or negative. When negative, it is preceded by the sign character (-). As with the integer data type, this data type can be as many as ten digits in length, not including the sign character. The value of this type has a range of minus 2147483647 through 2147483647.

123-000123-2100000000l

xixCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

PrefaceDocumentation Suite

Note Hexadecimal and integer fields in files may have different widths (numbers of characters) for column alignment.

Documentation SuiteThe documents that make up the Cisco BTS 10200 Softswitch documentation set are listed in Table 4.

Hexadecimal A series of 16-based digits from the set of 0 through 9, a through f, or A through F. The hexadecimal number may have one or more leading zeros (0) added to the left side. For all hexadecimal values, the maximum size is 0xffffffff (eight hexadecimal digits).

1f301f3000

Text A series of alphanumeric characters from the ASCII character set, where defined. Tab, space, and double quote (“ ” ) characters cannot be used. Text can be as many as 255 characters; however, it is recommended that you limit the text to no more than 32 characters for readability.

EntityIDLineSES_Threshold999

String A series of alphanumeric characters and white-space characters. A string is surrounded by double quotes (“ “). Strings can be as many as 255 characters; however, it is recommended that you limit the strings to no more than 80 characters for readability.

“This is a descriptive string.”

Table 3 Data Type Conventions (continued)

Data Type Definition Example

Table 4 Cisco BTS 10200 Softswitch Documentation

Functional Area Publication Description and Audience

Hardware Installation

Cisco BTS 1200 Softswitch Site Surveys and Cabling Procedures

Describes the hardware components of the Cisco BTS 10200 Softswitch. Includes detailed information on the environmental requirements for all the components. Also provides a checklist of the hardware you should have before starting the installation and a checklist of all the connections for the components.

The audience for these publications is the engineering personnel responsible for installing the components and verifying the hardware installation.

Software Release Notes

Cisco BTS 1200 Softswitch Software Release Notes for Release 4.1

Provides information that is specific to a particular release of the Cisco BTS 10200 Softswitch software.

The audience for these publications is the engineering personnel responsible for installing, configuring, and upgrading software for the respective solutions.

Software Installation

Cisco BTS 1200 Softswitch Release 4.1 Application Installation Procedures

Describes the steps necessary to install the software components of the Cisco BTS 10200 Softswitch.

The audience for this publication is the engineering personnel responsible for installing and configuring software for the Cisco BTS 10200 Softswitch.

xxCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

PrefaceObtaining Documentation

Obtaining DocumentationCisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.comYou can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:


International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Software Upgrade Cisco BTS 1200 Softswitch Release 4.1 Software Upgrade Procedures

Describes the steps necessary to ugpgrade the software components of the Cisco BTS 10200 Softswitch from any previous release to Release 4.1.

The audience for this publication is the engineering personnel responsible for upgrading and configuring software for the Cisco BTS 10200 Softswitch.

Reference Cisco BTS 1200 Softswitch Release 4.1 Command Line Interface Reference Guide

Provides reference information for the hardware and software of the Cisco BTS 10200 Softswitch.

The audience for this publication is the engineering personnel responsible for installing, configuring, operating, and upgrading the software for the respective components of the system.

Provisioning Cisco BTS 10200 Softswitch Provisioning Guide

Provides procedures for provisioning your Cisco BTS 10200 Softswitch.

The audience for this document is Cisco BTS 10200 Softswitch users, network operators, and administrators.

Provisioning Cisco BTS 10200 Softswitch Release 4.1 ISDN Provisioning and Troubleshooting Guide,

Describes ISDN Provisioning and Troubleshooting for the Cisco BTS 10200 Softswitch.

This document is intended for use by service provider management, system administration, and engineering personnel who are responsible for designing, installing, provisioning, and maintaining networks that use the Cisco BTS 10200 Softswitch.

Billing Cisco BTS 1200 Softswitch Billing Interface Guide

Provides billing interface information for the Cisco BTS 10200 Softswitch software.

This guide is intended for network operators and administrators who have experience with telecommunications networks, protocols, and equipment and who have familiarity with data communications networks, protocols, and equipment.

Table 4 Cisco BTS 10200 Softswitch Documentation (continued)

Functional Area Publication Description and Audience

xxiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

http://www.cisco.com/univercd/home/home.htm



PrefaceObtaining Technical Assistance

Documentation CD-ROMCisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order annual or quarterly subscriptions through the online Subscription Store:

http://www.cisco.com/go/subscription

Ordering DocumentationYou can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation FeedbackYou can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can send your comments in e-mail to [email protected].

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco SystemsAttn: Customer Document Ordering170 West Tasman DriveSan Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical AssistanceFor all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance.

xxiiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04


http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

http://www.cisco.com/go/subscription

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

http://www.cisco.com/en/US/partner/ordering/index.shtml

PrefaceObtaining Technical Assistance

Cisco TAC WebsiteThe Cisco TAC website (http://www.cisco.com/tac) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC CaseThe online TAC Case Open Tool (http://www.cisco.com/tac/caseopen) is the fastest way to open P3 and P4 cases. (Your network is minimally impaired or you require product information). After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using these recommendations, your case will be assigned to a Cisco TAC engineer.

For P1 or P2 cases (your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227) EMEA: +32 2 704 55 55 USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority DefinitionsTo ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

xxiiiCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

http://www.cisco.com/tac

http://tools.cisco.com/RPF/register/register.do

http://www.cisco.com/tac/caseopen

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

PrefaceObtaining Additional Publications and Information

Obtaining Additional Publications and InformationInformation about Cisco products, technologies, and network solutions is available from various online and printed sources.

• The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

• Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

• Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/go/packet

• iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

• Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html

xxivCisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

http://www.ciscopress.com

http://www.cisco.com/go/packet

http://www.cisco.com/go/iqmagazine

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

http://www.cisco.com/en/US/learning/index.html

Cisco BTS 10200 SoftswOL-4495-04

C H A P T E R 1
Hardware
This chapter describes aspects of the Cisco BTS 10200 Softswitch hardware, such as powering on and off the hardware for the Cisco BTS 10200 Softswitch, monitoring the hardware, and using the system Intelligent Alarm Panel. This information applies to Cisco BTS 10200 Softswitch systems residing within a Continuous Computing Corporation rack, although other vendors are supported.

This chapter contains the following sections:

• Rack Configuration, page 1-1

• Power On and Off, page 1-4

• Hardware Monitoring, page 1-6

• Host Operating System Time, page 1-10

• Intelligent Alarm Panel, page 1-10

Rack ConfigurationThis section describes the layout of the host machines and other hardware for the Cisco BTS 10200 Softswitch using host machines based on the Continuous Computing Corporation AXmp unit. There are four host machines as shown in Figure 1-1.

• Element Management System (EMS) and Bulk Data Management System (BDMS), Side A

• EMS and BDMS, Side B

• Call Agent (CA) and Feature Server (FS), Side A

• CA and FS, Side B

The host machines are supplied as field-replaceable units (FRUs). On the front face of each host machine are an LCD display and several LED lights. These provide information on the current status of the system (including power on or off) and show any problems or failures with the FRU. A silver switch to the left of the LEDs powers the FRU on and off. The hardware also includes two Catalyst Ethernet switches, a DC power distribution unit (PDU) or AC power strips, and an terminal server or alarm panel with terminal server.

Note The Sun Microsystems Inc. SunFire V120, Netra 120, and Netra 20 hosts are also used in other configurations on which the Cisco BTS 10200 Software can run. For a complete description of Cisco approved hardware options, refer to the Cisco BTS 10200 Softswitch System Description.

1-1itch Operations and Maintenance Guide

Chapter 1 HardwareRack Configuration

Caution Be sure to use one of the Cisco specified hardware sets. The software is not supported on any other types or combinations of hardware.

Figure 1-1 Example of Rack Configuration for Cisco BTS 10200 Softswitch (AXmp Option Shown)

1049

37

12

13

1

5

2

6

7

4

2

4

8

3 4

2

2

2

4 9

2

1011

1011

1011

1011

1-2Cisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04

Chapter 1 HardwareRack Configuration

Legend for Figure 1-1:

In the following legend, the terms CCN node address and PDU power feed refer to the following:

• Continuous Control Node (CCN) address—Address on the internal interface used for communications and management support for the host machines in the rack. The CCN acts as an interface to the front panel switches and displays.

• PDU power feed—Identifier for the power feed from the PDU to the various machines in the rack.

Note When the hardware for the Cisco BTS 10200 Softswitch is purchased as a complete system from Cisco, the cables for the CCN and PDU connections in the rack are included (and appropriately labeled).

1. Intelligent Alarm Panel, PDU power feed 8A

PDU (DC systems)

2. Unused space

3. EMS/BDMS B

CCN node address = 1

PDU power feed 1A/1B

4. Field-replacement unit (FRU)

5. CA/FS B



6. Ethernet switch (HUB) B (2924M)

7. Ethernet switch (HUB) A (2924M)

8. EMS/BDMS A



9. CA/FS A



10. LEDs

11. Power switch

12. 48U (ref)—Approximately 84 in. (2.14 m)

13. 43U (ref)—Approximately 75 in. (1.91 m)


OL-4495-04

Chapter 1 HardwarePower On and Off

Power On and OffThis section describes how to power on and off the hardware for the Cisco BTS 10200 Softswitch.

Power On ProcedurePerform the following procedure to power on the hardware for the Cisco BTS 10200 Softswitch.

Note Boot completion times vary with system type (CA/EMS) as well as size of database.

Step 1 Ensure that all power cables are properly fastened to the back of all the machines in the Cisco BTS 10200 Softswitch.

Step 2 Power on the Catalyst switch routers by plugging them into a viable power source.

Note The Catalyst switch routers do not have a power button.

Step 3 On the front side of the machines, power on the primary and secondary EMS by pulling on the silver switch to the left of the LEDs and putting it in the ON position.

When you hear the fans operate on the unit, you can release the knob to its neutral position.

Step 4 Power on the CA and FS units by pulling on the silver switch to the left of the LEDs and putting it in the ON position.

When you hear the fans operate in the unit, you can release the knob to its neutral position.

The hardware for the Cisco BTS 10200 Softswitch is now powered on.

Power Off ProcedurePerform the following procedure to power off the Cisco BTS 10200 Softswitch:

Step 1 Check status of your system and ensure the primary CA and primary EMS are active, and that the secondary CA and secondary EMS are in standby.

Step 2 Log in to the primary CA, secondary CA, primary EMS, and secondary EMS using Secure Shell (SSH).

Note The order for shutdown should be secondary EMS, secondary CA, primary CA then primary EMS.

Step 3 Enter the following command to begin the platform shutdown process:

#> platform stop all

When the prompt returns to (#>) the operating system is ready for shutdown.

Step 4 Enter the following for each node to shut down the FRUs:

#> shutdown -i5 -g0 -y


OL-4495-04

Chapter 1 HardwarePower On and Off

You will see when the SSH sessions are disconnected. If you are connected via local Console to the host machines, you will see the system shut down.

You can see the unit is ready to power off when the LCD on the FRU reads “HALTED” or “Coma.”

When all the FRUs have reached the HALTED or Coma state, continue to the next step.

Step 5 Power off the primary and secondary Call Agents and Feature Server by pulling on the silver switch to the left of the LEDs and putting it in the OFF position.

When you hear the fans turn off in the unit, you can release the knob to its neutral position.

Step 6 Power off the primary and secondary EMS by pulling on the silver switch to the left of the LEDs and putting it in the OFF position.

When you hear the fans turn off in the unit, you can release the knob to its neutral position.

Step 7 To power off the Catalyst switch routers, unplug the unit from its power source.

Note The Catalyst switch routers do not have a power button.

The hardware for the Cisco BTS 10200 Softswitch is now powered off.


OL-4495-04

Chapter 1 HardwareHardware Monitoring

Hardware MonitoringThe hardware monitor (HMN) subsystem monitors the CPUs, memory consumption, disk, and disk control utilization, and returns information and alarms as appropriate.

CPUThe HMN monitors one or more CPUs on a physical node and reports the following:

• Percentage of CPU idle

• Percentage of CPU in system mode

• Percentage of CPU in user mode

• Percentage of CPU in blocked I/O

Memory ConsumptionThe HMN monitors memory consumption and reports the following:

• Total “real” memory

• Free memory available

• Total swap space

• Free swap space available

Disk and Disk UtilizationThe HMN monitors the disk and disk control utilization on a physical disk and controller level. This measurement is dependent on the driver support supplied for the SCSI controller from the vendor.

Note The device names follow those of a Solaris kernel. These vary from device to device. A physically understandable “mapping” of these devices may be required.

The HMN reports the following for disk and disk control utilization:

• Utilization of disk devices (sd0, sd1, and so on)

• Transfer rates, transactions per second (TPS), and hard or soft errors

Alarm ReportsThe HMN monitors the top ten processes in the system. These processes are tracked based on the amount of CPU time they consume. This is a measure over time where a process can start running hot. This monitor function does not report transient spikes in CPU usage by any individual process.

The HMN generates alarm reports on devices and facilities that exceed their default settings. Default settings can be adjusted to fit a specific set of customer requirements.


OL-4495-04


Alarms are generated under the following conditions:

• A process exceeds 70 percent of the CPU.

• The Call Agent CPU is over 90 percent busy (10 percent idle).

• The load average exceeds 5 for at least a 5-minute interval.

• Memory is 95 percent exhausted and swap is over 50 percent consumed. This indicates the system is spending excessive time in paging virtual memory.

• A partition that is 70 percent consumed generates a minor alarm (MAINTENANCE #90).

• A partition that is 80 percent consumed generates a major alarm (MAINTENANCE #66).

• A partition that is 90 percent consumed generates a critical alarm (MAINTENANCE #65).

Hardware Monitoring CommandsThis section describes the hardware monitoring commands.

Note In the following examples, “prica42” is used as an example of a node name.

Use the following example to create an HTML report file on the condition of a node. This commands displays a substantial amount of information on the node, including statistics for disk, CPU, memory, and host machine interfaces. The report can be viewed on a Web browser at http://<hostname>:10200/report/HMN-Metrics/

report node node=prica42;

Use the following example to show the status of a node and its components. This commands displays a substantial amount of information on the node, including statistics for disk, CPU, memory, and host machine interfaces. (The information is similar to that created by the report node command.)

status node node=prica42;

Use the following example to show the status (enabled or disabled) of services on a node:

show node node=prica42; service=telnet;

Caution The change command (below) is a low-level maintenance activity that can affect the operation of the host machine. Execute with extreme caution.

Caution Changing the service on a node after the delivery of a Cisco BTS 10200 Softswitch can create security issues in your network.

Use the following example to change the status of a service on a node:

change node node=prica42; service=ftp; enable=Y;

Caution The control commands (below) are low-level maintenance activities that can affect the operation of the host machine. Execute with extreme caution.


OL-4495-04


If a platform goes down (status FAULTY), you can use the following example to reboot the host machine on which the platform resides. This command reboots the host machine, not just the individual platform.

control node node=prica42; action=REBOOT;

If a host machine requires a low-level maintenance activity, such as replacement of a hard drive, you can use the following example to bring the host machine into maintenance mode.

Caution After halting a Cisco BTS 10200 Softswitch node, you will need local console access or a power cycle to restart the node.

control node node=prica42; action=HALT;

The parameters for the node commands are described in the table below. An asterisk preceding a token name means the token is mandatory. A token without an asterisk is optional.

* NODE The logical host name of the target node in the Cisco BTS 10200 Softswitch. This replaces manually telneting to the box.

STRING: Physical name of a Call Agent, Feature Server, or Element Management System.

* ACTION Valid only for the control command. The action indicates the type of activity to perform. Both parameters are required.

STRING: REBOOT or HALT are the only valid actions for this token.

REBOOT—Reloads the operating system and subsequently restarts all the applications processes.

HALT—Stops the operating system and all application processes. It then halts the CPU. This action is intended to take a node into a maintenance mode and can be used, for example, to bring down a node to replace a bad CPU or memory.

CPU Valid only for the status and report commands. Specifies whether to generate a report of CPU utilization.

STRING: Y/N (Default = Y).

MEMORY Valid only for the status and report commands. Specifies whether to generate a report of memory utilization.


PROCESS Valid only for the status and report commands. Specifies whether to generate a report of process utilization.


NETWORK Valid only for the status and report commands. Specifies whether to generate a report of network utilization.



OL-4495-04


ENABLE Valid only for the change command. Specifies whether to turn a service on (Y) or off (N).


SERVICE Valid only for the show and change commands. Specifies the standard UNIX service.

STRING: Any valid UNIX service.

Note These values must be entered in lowercase.

Permitted values are:

ftp—File Transfer Protocol

telnet—Text-based terminal service

echo—Application space service to verify a remote host

discard—Solaris testing facility

day—Solaris testing facility

time—Solaris testing facility

chargen—Solaris testing facility

smtp—Solaris mail service

finger—UNIX user ID service

sunrpc—Solaris Remote Procedure Call service

exec—Remote execution service

login—BSD remote login service

shell—BSD remote shell service

printer—Solaris printer services

uucp—UNIX-to-UNIX copy service

nfs—Network File System service

lockd—Remote file locking facility

X11—X Window graphical services

dtscp—Solaris management services

font_service—Solaris character set service

http—Hyper-Text Transfer Protocol service


OL-4495-04

Chapter 1 HardwareHost Operating System Time

Host Operating System TimeThe Solaris OS obtains the system time automatically through Network Time Protocol (NTP) services.

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

Intelligent Alarm PanelSee the Continuous Computing: Alarm Panel User Guide and the Continuous Computing: Alarm Panel v1.3.0 Release Notes for detailed information on the Intelligent Alarm Panel.


OL-4495-04


C H A P T E R 2
Operator Interfaces
This chapter describes the operator interfaces used for communication with the Cisco BTS 10200 Softswitch and contains the following sections:

• Logging in Using Secure Shell

• EMS Services

Note After entering any of the commands in this chapter, press the Return or Enter key.

Figure 2-1 illustrates the Cisco BTS 10200 Softswitch operator interfaces of the Element Management System (EMS). These interfaces support several types of communications:

• Local Operations Console—the following options are available:

Interactive CLI session—operator connects to the EMS using Secure Shell (SSH) and uses the command line interface (CLI) in an interactive session

Bulk Provisioning—operator connects to the EMS using FTP for batch-mode provisioning (requires highest privilege levels)

Note See the Cisco BTS 10200 Softswitch Provisioning Guide for Bulk Provisioning information.

• Network Management System—provides events, alarms, thresholds and traffic monitoring management commands into the EMS using SNMP

• CORBA Client—provides events, alarms, thresholds and traffic monitoring management commands into the EMS via Common Object Request Broker Architecture (CORBA)

The EMS database holds up to 100 operator logins, and up to 50 user sessions can be active at any time.

The EMS interfaces internally with the Call Agent (CA) and Feature Server (FS) using the Java Message Service (JMS) protocol over IP Protocol.


Chapter 2 Operator InterfacesLogging in Using Secure Shell

Figure 2-1 Operator Interfaces (Billing Interfaces Also Shown)

Logging in Using Secure Shell[This section describes how to log in to the Cisco BTS 10200 Softswitch using SSH. SSH is the method of access to the Cisco BTS 10200 Softswitch CLI, or maintenance (MAINT) modes. SSH provides encrypted communication between a remote machine and the EMS or Call Agent for executing CLI, or MAINT commands. The SSH server runs on the EMSs and CAs of the Cisco BTS 10200 Softswitch. To connect, the client and server sides must run the secure shell daemon (SSHD).

With SSH enabled, new users are prompted to enter a new password and reenter that password during their first login. From that point, they are prompted once for a password only.

Step 1 To log in from the client side, enter the following:

ssh username@IPaddress

On the first SSH login from the client side, expect a message similar to this:

The authenticity of host [hostname] can't be established.Key fingerprint is 1024 5f:a0:0b:65:d3:82:df:ab:42:62:6d:98:9c:fe:e9:52.Are you sure you want to continue connecting (yes/no)?

Step 2 Enter yes.

The default password prompt appears. From this point on, all communications are encrypted. Enter the default password.

Note Subsequent SSH logins will prompt only for a password.

LAN

Packetnetwork

EMS/BDMS

JMS

CA/FS

9796

2

Ethernet

Cisco BTS 10200Softswitch

OSSinfrastructure

systems

SSHLocal

operator(CLI/MAINT)

SFTPBulk

provisioning(CLI scripts)

XML/CORBALocal

operator(EPOM)

SSH, SFTPSNMP, XML/CORBA

MACRO-XML/CORBA

SSH, SFTPSNMP, XML/CORBA

MACRO-XML/CORBA

Service-provider managed network


OL-4495-04

Chapter 2 Operator InterfacesEMS Services

Step 3 At the login prompt, enter your CLI username.

The password prompt appears.

Step 4 Enter your password.

The system responds with a CLI> prompt. You are now ready to send commands to the EMS.

Step 5 Enter the desired provisioning commands.

Step 6 To log off, enter exit at the prompt.

EMS ServicesThis section describes EMS activity commands. EMS activity commands are available to manage the users and other services on the system. The activity timer for user sessions is not part of any schema or table. This is a system configuration parameter.

EMS Users and Services CommandsThis section describes the EMS user and other service commands on the system.

Show

Use the following command example to show user activity on the EMS:

show ems;

Change

Use one of the following command examples to change a service on the EMS:

change ems interface=hma0;ip-alias=<the ip-address>change ems ntp-server=ntp_server_1,ntp_server_2

EMS NTP Server ConfigurationThe network time protocol (NTP) is designed to synchronize the clocks of computers over a network. It uses multiple redundant servers in order to achieve high accuracy and reliability.

Use the following CLI command to configure the NTP server:

change ems ntp_server=<ntp_server_1>,<ntp_server_2>

where:

ntp_server_1 and ntp_server_2 are the IP addresses of reference time source servers.


OL-4495-04

Chapter 2 Operator InterfacesEMS Services


OL-4495-04


C H A P T E R 3
Provisioning External Media Gateways
The Media Gateway Provisioning (MGP) command allows a service provider direct command access to provision a gateway through the Cisco BTS 10200 Softswitch. After an MGP entry is added to the system, you can access the gateway using the escape command sequence at the command line interface (CLI), FTP adapter, or by using the MGP object interface in the CORBA adapter.

This command applies only to the following media gateways:

• Cisco MGX 8260

• Cisco AS5850

• Cisco MGX 8850

• Cisco AS5400

Use one of the following examples to show, add, change or delete an external media gateway.

show mgp

add mgp ip-addr=10.89.224.10; type=As5400; user-name=cisco; password=cisco123;

Note After adding a gateway, use your applicable vendor documentation to configure the gateway using the escape command. The format for the escape command is: mgp <IPaddress> gateway command.

The mgp keyword indicates to the CLI that the command is not for the Cisco BTS 10200 Softswitch. It is to be sent to the gateway defined by the IP address. This is the same address as the one used to create the MGP entry in the add mgp command.

change mgp gateway1.cisco.com; password=cisco

delete mgp ip-addr=10.89.224.10;


Chapter 3 Provisioning External Media Gateways


OL-4495-04


C H A P T E R 4
Managing Access and Users
The security management system controls and monitors access to the Cisco BTS 10200 Softswitch from outside sources. This security system is important in preventing the following:

• Errors by personnel not trained in specific procedures

• Unauthorized changes to system provisioning

• Unauthorized viewing or modification of databases

Internal security functions include:

• Providing a user interface to provision users and security classes (privilege levels)

• Storing user login profiles

• Performing user authentication

• Managing the level of access on a per-user basis

• Providing session-oriented security measures

• Providing transaction-oriented security measures

• Logging all access activity to a log

• Maintaining security log for 7 days

• Providing a user interface for security log reporting

Note Refer to the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide for specific CLI commands and tokens.


Chapter 4 Managing Access and UsersUser and Command Privilege Levels

User and Command Privilege LevelsEach command (verb-noun combination) is preassigned a security class of 1 to 10, with 1 being the lowest level and 10 the highest level. The security class indicates the minimum privilege level required for an operator to complete the command. The system administrator can assign an alphanumeric description with each of these security classes.

Note The security classes are preassigned for each command, but can be changed by the system administrator.

The system administrator enters a new user and assigns a privilege level from 1 to 10 (level 10 is typically reserved for the system administrator). Each time a user enters a command, the system compares the user’s privilege level to the security class of the specific command. The command is denied if the user has a privilege level less than the command level.

The user interface of the security management system allows users with the highest privilege levels to perform the following security tasks:

• Enter users into the system database

• Assign or modify a user’s privilege level

• Reset the password of any user

• Modify descriptions of a security level

• Manage security log reporting and obtain security reports

Command Level ProvisioningThe Command Level (command-level) table identifies the ten command levels and their descriptions. The system is delivered with levels 1, 5 and 10 preset with descriptions. These are the lowest level, the mid level and the highest level administration access. Preset levels can be changed. Every security level can be assigned an alphanumeric description. The optional description token is intended for the service provider.

Step 1 To show a command level ID, use the following example:

show command-level id=10;

Step 2 To add a description to any command level ID, use the following example:

change command-level id=10; description=This is the highest level administration access;


OL-4495-04

Chapter 4 Managing Access and UsersUser Account Administration

User Account AdministrationThis section describes user account administration.

Predefined User AccountsFor software releases prior to Release 4.4, the Cisco BTS 10200 Softswitch system is delivered with one account predefined as username=optiuser and password=optiuser. Cisco recommends resetting this password. New users can be added by this superuser. A new user who logs in for the first time is prompted to enter a new password and to reenter the new password for verification purposes. Passwords must be at least six characters in length and cannot contain the first three characters of the login name

Beginning with Release 4.4, the Cisco BTS 10200 Softswitch system is delivered with three predefined accounts, as follows:

• Username=btsadmin and password=btsadmin—Comparable to optiuser in previous releases.

• Username=btsuser and password=btsuser—Provides lower access permissions than btsadmin and is suitable for generic provisioning access.

• Username=secadmin and password=secadmin—Currently similar to btsadmin.

Btsadmin and secadmin are MAINT shell users. The MAINT shell is an enhanced CLI interface and does not log off an idle user.

If you use one of the new accounts added in Release 4.4 and encounter errors accessing directories, enter the following command at the UNIX prompt to resolve the problem:

chown -R<user_name>:staff /opt/ems/users/<user_name>

UsersThis section describes how to show, add, change and delete users.

Note After adding a new user to the system a default or initial password must be supplied with the following command: reset password name=<user name>; new-password=<user password>;

This is the standard Cisco BTS 10200 Softswitchcommand for the system administrator to reset a password.

Step 1 To show the details for a user, use the following example:

show user name=UserABC;

Step 2 To add a user, use the following example:

add user name=UserABC; command-level=9; warn=10; days-valid=30; workgroups=somegroup;

Reply Example:

Executing command, please wait...Reply: Request was successfully completed


OL-4495-04

Chapter 4 Managing Access and UsersUser and Optiuser Set Password/Reset Password

Note The warn, days-valid, and workgroups tokens are optional.

Step 3 To change details for a specific user, use the following example:

change user name=UserABC; command-level=1; workgroups=somegroup;

Reply Example:


Note The change user command changes only the privilege level of the user, and not the identity of the user. The command-level and workgroups tokens are optional; however, one of them must be changed.

Step 4 To delete a user, use the following example:

delete user name=UserABC;

Reply Example:


Invalid User Privilege LevelThe following example shows what happens when a user with a privilege level less than 9 attempts to enter an add, show, change, or delete user command:

change user name=UserABC;command-level=6;

Reply Example:

Not authorized to execute change user:User command-level: 2 level needed: 10

Caution Never add, change, or delete the username root, because this affects proper access to the system.

User and Optiuser Set Password/Reset PasswordThe password command allows the system administrator to reset any user’s password. It also allows setting the number of days that the password is valid and the number of days before password expiration that the user is warned. It also forces the system administrator to enter a new password. A user who logs in for the first time must execute this command again to change the password.

Users can reset only their own passwords. Users are allowed to reset the days a password is valid, the number of days before password expiration, and the user must enter a new password when executing this command.

Passwords must be constructed to meet the following UNIX standards:

• A password must have at least six characters. If it is longer than six characters, only the first eight characters are significant.


OL-4495-04

Chapter 4 Managing Access and UsersCommand Table

• A password must contain at least two alphabetic characters and at least one numeric or special character. In this case, alphabetic refers to all upper- or lowercase letters.

• A password must differ from the user's login name and any reverse or circular shift of that login name. For comparison purposes, an uppercase letter and its corresponding lowercase letter are equivalent.

• New passwords must differ from the old by at least three characters. For comparison purposes, an uppercase letter and its corresponding lowercase letter are equivalent.

The system default user/password combination for the system administrator is optiuser/optiuser. The username optiuser can never be deleted from the system. As a security measure, the system administrator should change the password for user optiuser on each system.

To change the password to optiuser, perform the following steps.

Note Perform the same steps to change the password for any system user.

Step 1 Log on using SSH to one EMS unit with the username optiuser and the current password for optiuser.

ssh -1 <username> <ipaddress>

The CLI prompt appears.

Step 2 Enter the reset command:

reset password name=optiuser; days-valid=<number of days the new password will be valid>; warn=<number of days before password expiration to warn user>;

reset password name=optiuser; days-valid=45; warn=10;

Step 3 Enter exit to exit the CLI shell.

Step 4 Log on using SSH to the same EMS with user name optiuser.

The system prompts you for a new password.

Step 5 Enter the new password.

Step 6 The system prompts you for the new password again.

Step 7 Enter your new password.

The password for user optiuser is changed and the CLI prompt appears. You can continue with the CLI session if desired, or exit again.

Command TableThe Command Table (command-table) table allows a system administrator to show, change, and reset the command privilege level (CPL) of a specific noun-verb pair. This command requires a security level of 10 to execute. Security classes are preassigned for each command, but can be changed with the command-table command.

Step 1 To show the command privilege level of a specific noun-verb pair, use the following example:

show command-table noun=mgw; verb=add;


OL-4495-04

Chapter 4 Managing Access and UsersCommand Table

Step 2 To change the command privilege level of a specific noun-verb pair, use the following example:

change command-table noun=mgw; verb=add; sec-level=9;

Step 3 To reset the command privilege level of a specific noun-verb pair, use the following example:

reset command-table noun=mgw; verb=add;


OL-4495-04

Chapter 4 Managing Access and UsersWorkgroups

WorkgroupsWork-groups are created when you use the User or Command tables. The first time you use the work-groups token, you create the work-group and add the User/Command to the work-groups. Additional User/Commands are added to the work-groups the same way. The only exception is that the work-groups is already created.

The work-groups token is a logical collection of commands created by the service provider. Work-groups are valid only for the change command. An equal sign (=) without a plus sign (+) or minus sign (–) creates a new work-group. A plus sign (+) before the work-group name adds a work-group to a user. A minus sign (–) before the work-groups name removes a work-group from a user.

Step 1 To add a user to a work-group for the first time, use the following example:

change command-table noun=mgw; verb=add; work-groups=latex;

Reply Example:

Reply : Success: Request was successfully completed

Step 2 To add one or more work-groups to an existing user, use the following example.

Note This does not replace any already existing work-groups.

change user name=trs80nut; work-groups=+rubber;

Reply Example:


Step 3 To remove one or more work-groups from an existing user, use the following example:

change user name=trs80nut; work-groups=-latex;

Reply Example:


Adding Descriptions to Security ClassesEach of the ten security levels can be assigned an alphanumeric description using the following command. This procedure is optional.

change command-level id=<#>; description=<alphanumeric description>

Note <#> = 1 to 10 and <alphanumeric description> can have up to 64 ASCII characters.


OL-4495-04

Chapter 4 Managing Access and UsersSession Manager

Session ManagerThe Session Manager (SMG) user management tool tracks the session clients (users) that have logged in to the Cisco BTS 10200 Softswitch.

This section describes the session management activity commands. The stop, block, and unblock commands cannot be executed on the same terminal from which the command was entered. In this section, command information in square brackets ( [ ] ) is mandatory and command information in curly braces ( { } ) is optional. There is no mandatory information for the show command.

Show CommandThe show command queries all terminals in the system. The SMG returns a list of currently defined terminals. It allows the service provider to differentiate the list based on a user ID. If a terminal is not listed, all terminals are shown. The asterisk (*) wildcard is not supported.

Step 1 To query all terminals in the system, use the following example:

show session terminal={1-32 characters}

Reply Example:

Reply : Success

TERMINAL=USR5USER=optiuserSTATE=ACTIVETYPE=CLITIME=2001-May-18 14:32:27

TERMINAL=USR4USER=wenyangSTATE=ACTIVETYPE=CLITIME=2001-May-18 13:48:49

TERMINAL=USR3USER=optiuserSTATE=ACTIVETYPE=CLITIME=2001-May-18 12:18:49

=========


OL-4495-04

Chapter 4 Managing Access and UsersSession Manager

Block CommandThe block command is executed on a single terminal ID. The terminal is then blocked and a notification is sent to the terminal to suspend all further operation. The state of the specified terminal is changed to blocked.

Step 1 To block a terminal, use the following example:

block session terminal=USR16;

Reply Example:

Reply : Success

Caution If the terminal type of a terminal is associated with an external application such as SNMP, the external application is blocked as well.

Change CommandThe change command changes the idle time of a session. The idle time defines the number of minutes that a user can be idle on a CLI or MAINT interface before being automatically logged off the Cisco BTS 10200 Softswitch.

Step 1 To change the session idle time, use the following example:

change session idle-time=30;

Reply Example:

Reply : Success: Idle time set to 30 for new sessions.

Unblock CommandThe unblock command is executed on a single terminal ID. The terminal is then unblocked and a notification is sent to the terminal for the user to resume normal operation. The state of the specified terminal is changed to unblocked.

Step 1 To unblock a single terminal, use the following example:

unblock session terminal=USR16;

Reply Example:

Reply : Success


OL-4495-04

Chapter 4 Managing Access and UsersSecurity Summary Report

Stop CommandThe stop command is executed on a single terminal ID. The selected terminal is then notified to terminate and its associated terminal definition in the SMG is removed.

Step 1 To stop a specified terminal, use the following example:

stop session terminal=USR16;

Reply Example:

Reply : Success: Stop attempted on terminal <USR16>.

Security Summary ReportThe Security Summary command provides a summary report of security infractions by source and start/stop times from the Security Log (securitylog) table. The EMS maintains seven days of security infractions.

Step 1 To run a Security Summary report, use the following example:

report security-summary start-time=2002-09-26 00:00:00; end-time=2002-09-27 00:00:00; source=all;

Note If you enter this command without any tokens, the report shows all security infractions.

Step 2 Using the Cisco BTS 10200 Softswitch http:// server in an external browser (Netscape, Internet Explorer, and so forth), perform the following steps to retrieve the security-summary report file.

a. Enter the http:// server name.

http://<your bts domain name>:10200>

b. Once on the main page, double-click the reports link.

A set of directories appears.

c. Select the Security Summary report by double-clicking security-summary.html.

The security-summary log appears.


OL-4495-04


Example of Security Summary Report:

In the following example, user wwalbash, with a command-level 5 security level, tried to add a media gateway, which requires a security level of 8 or above. The attempt failed and is recorded in the Security Summary report for the Security manager.

report security-summary

Reply : Success: Request was successful.

USER=wwalbashVERB=addNOUN=mgwDATE=2002-09-26 13:25:50.0USER=wwalbashVERB=addNOUN=subscriberDATE=2002-09-26 13:26:02.0


OL-4495-04



OL-4495-04


C H A P T E R 5
Digit Manipulation
The Digit Manipulation (DIGMAN) feature provides the ability to modify the calling party number, also known as automatic number identification (ANI), and/or the called party number, also known as dialed number information service or (DNIS) for both incoming and outgoing calls within the Cisco BTS 10200 Softswitch. The digit manipulation tables can also be used to modify the nature of address (NOA) of ANI and/or DNIS numbers.

In this chapter, references to ANI or DNIS manipulation include both digit manipulation and NOA manipulation unless otherwise stated. ANI manipulation refers to the calling party number (CPN) that is normally displayed when a call is terminated to a device with the calling number delivery (CND) feature.

In countries like China, there are additional requirements regarding ANI display. The requirements are to display ANI in the “dialable” format. The term dialable means the user can simply call up the display and press the dial button to place a return call based on the received ANI. This requires the ANI to contain the national destination code (NDC), usually referred to as the “area code,” for a long-distance call, while only displaying subscriber number for a local call. The rules defined in this chapter can be used to manipulate ANI or DNIS digits to the desired format.

The DIGMAN feature provides several benefits over previous releases:

• Robust dial plans—NANP or E.164

• Flexible call processing

• ANI- or DNIS-based routing

Specific restrictions applicable to various commands used with the DIGMAN feature are described in the “Digit Manipulation Tables” section on page 5-6.

The DIGMAN feature is not platform dependent. It is supported on any platform that has been certified as a host system for the Cisco BTS 10200 Softswitch.

The DIGMAN feature supports the following industry standards:

• North American Numbering Plan (NANP)—See http://www.nanpa.com/

• E.164 Numbering Plan—The international public telecommunication numbering plan—See http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-E.164


http://www.nanpa.com/

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-E.164

Chapter 5 Digit ManipulationDigit Manipulation Rules

Digit Manipulation RulesThis section describes the capabilities the digman tables provide for the Cisco BTS 10200 Softswitch.

Digit manipulation is performed using as many as 20 different digit manipulation (digman) tables as designated by the digman-id and a rule number. Each of the 20 tables can have a unique set of match-string and replace-string tokens or match-NOA and replace-NOA tokens.

The match-string is compared to the input-string. If a match is found, based on the rules specified here, then the replace-string replaces the matched string in all further call processing actions.

The match-string and replace-string tokens are constructed using the characters specified here:

• digits 0 through 9, asterisk (*), pound sign (#)—Valid for use at any position in the input-string token, match-string token, and replace-string token.

• Caret (^)—Beginning of match-string characters.

The caret (^) can only be the first character in a match-string. If it appears at any other position in the match-string, an error is generated.

– If the caret (^) is the only character in the match-string, the input string is prefixed by the characters in the replace-string.

In this example, the digit string 011 is prefixed to the input-string.

input-string=9127210112; match-string=^; replace-string=011output-string=0119127210112

– If other characters are present in the match-string, the caret (^) indicates that matching characters at the beginning of the input-string are to be replaced by the characters in the replace-string.

The replace string does not have to be the same number of characters as the match-string; it can be a greater or a fewer number of characters.

In this example, if the digit string 011 appears at the beginning of the input string, it will be replaced with the digit string 0122 in the replace-string.

input-string=0119127210112; match-string=^011; replace-string=0122output-string=01229127210112

– In this example, if the first character in the input-string is the prefix 1, it is removed and the remainder of the input-string is passed unaltered.

input string=14692551234; match-string=^1; replace-string=output-string=4692551234

– In this example, a 10-digit input-string (the dialed number) is converted to a 5-digit extension by removing the first 6 digits and replacing them with the number 5.

input string=4692551234; match-string=^469255; replace-string=5output-string=51234

– This example prefixes the specified digit(s) at the beginning of the input-string.

input string=222; match-string=^; replace-string=1output-string=1222


OL-4495-04

http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-E.164


• Dollar sign ($)—End of match-string character.

The dollar sign ($) can only be the last (or only) character in a match-string. If it appears at any other position in the match-string, an error is generated.

– If the dollar sign ($) is the only character that appears in the match-string, the characters in the replace-string are appended to the input-string.

In this example, the digits 567 from the replace-string are appended to the end of the input-string.

input-string=4692551234; match-string=$; replace-string=567output-string=4692551234567

– If the dollar sign ($) appears at the end of a match-string, the matching characters at the end of the input-string are replaced by the characters in the replace-string.

In this example, the digits 0000 in the replace-string will replace the digits 1234 in the input-string.

input-string=4692551234; match-string=1234$; replace-string=0000output-string=4692550000

– In this example, the dollar sign ($) coupled with 4 question marks (?) deletes the last 4 digits from the input-string, regardless of what they are.

input-string=4692551234; match-string=????$; replace-string=output-string=469255

– Adding a replace-string in this example replaces the last 4 digits in the input string with 0000, regardless of what the last 4 digits are.

input-string=4692551234; match-string=????$; replace-string=0000output-string=4692550000

– This example appends the specified digits (0000) to the input-string without deleting or replacing any characters in the input-string.

input-string=469255; match-string=$; replace-string=0000output-string=4692550000

• Dot (.)—The dot (.) character is a “don’t care” character that can appear at the beginning, the end, or both the beginning and end of a match-string. It is used to identify the position of characters in the input-string that are disregarded during the matching operation.

– Dots (.), if specified, can appear as leading dots, trailing dots, or both.

match-string=...555; match-string=555....; match-string=...555....;

– If dot (.) characters are the leading characters in the match-string, the corresponding positions at the beginning of the input-string are disregarded.

This example indicates that 555 appears in positions 4 through 6 in the input-string and the matching operation does not care what characters are in digit positions 1 through 3 or in digit positions that follow position 6.

This match-string (...555) produces a match on the input-string 4695551234, and the replace-string (777) replaces the matched string.

input-string=4695551234; match-string=...555; replace-string=777output-string=4697771234


OL-4495-04


– If dot (.) characters are the last characters in the match-string, the corresponding positions at the end of the input-string are disregarded.

This example indicates that 555 precedes the last four characters in the input-string.

This match string (555....) also produces a match on the input-string 4695551234, and the replace-string replaces the matched string.

input-string=4695551234; match-string=555....; replace-string=666output-string=4696661234

– In this example only input-strings with the digit 5 in positions 4, 5, and 6 will be matched; however, the ampersand (&) in the replace-string indicates that if a match occurs, the entire input-string is passed unaltered.

input-string=4695551234; match-string=...555; replace-string=&output-string=4695551234

– The replace-string “none” in this example indicates if the input-string has the digit 3 in positions 4 and 5, a match occurs and those 2 digits are deleted, but all other digits in the input-string are passed unaltered.

input-string=222333; match-string=...33; replace-string=noneoutput-string=2223

The dot (.) character can also be used to check the length of the input string, as shown in the following example.

– In this example, if the input-string is 10 digits, the ampersand (&) in the replace-string indicates that the input-string should be passed unaltered.

input-string=4695551234; match-string=..........;#CHECKS IF INPUT STRING LENGTH=10replace-string=&output-string=4695551234

• Question Mark (?)—The question mark (?) can appear anywhere in a match-string as a wildcard character; however, multiple question marks (two or more) must be contiguous at the beginning or at the end of a match-string and not separated by any other character(s)—nor can they separate any other characters in a match-string.

– Question mark (?) character(s) can be used to match characters at the beginning or the end of the input-string.

The following example indicates that the digits 555 must be preceded in the input-string by at least 3 digits.

This match-string (???555) matches the input-string 4695551234. When a match is found, the replace-string replaces the matched string.

match-string=???555

The following example indicates that the digits 555 must be followed by at least 4 digits.

This match-string (555????) matches the input-string 4695551234. When a match is found, the replace-string replaces the matched string.

match-string=555????


OL-4495-04


– Question marks (?), if specified, cannot appear between digits in a string.

The following example is not valid:

input-string=123456; match-string=12??56

The following examples are valid:

match-string=123???match-string ???456

– In this example, the first 4 digits are deleted if the input-string begins with the digit 1.

input-string=14692551234; match-string=^1???; replace-string=noneoutput-string=2551234

– In this example, the first 4 digits are deleted regardless of what they are.

input-string=4692551234; match-string=????$; replace-string=noneoutput-string=469255

– This example replaces any 3 digits followed by 555 with a single digit 5.

input-string=4695551234; match-string=???555; replace-string=5output-string=51234

• Ampersand (&)—The ampersand character (&) is a suffix character that can appear only as the last character in a replace-string.

– If the ampersand (&) is specified by itself in a replace-string, it indicates that no digit manipulation is required on the matched input-string and it should be left as it is. If a match occurs, it confirms that the input-string matches the match-string.

input-string=4695551234; match-string=…555….; replace-string=&;MATCHED

The input-string matches the match-string. This does not affect the input-string, but does return an indication of the match.

– If the ampersand (&) is specified with other digits preceding it in a replace-string, the specified digits are prefixed to the matched string.

input-string=4695551234; match-string=???555….; replace-string=1&output-string=14695551234

– If the first 3 digits of the input-string are followed by the digits 255 in positions 4, 5, and 6, then the digit 1 is prefixed to the input-string.

input-string=4692551234; match-string=???255; replace-string=1&output-string=14692551234

– This match-string is used to check if the input-string consists of a 1 followed by any 10 digits.

input-string=14692551234; match-string=^1..........; replace-string=&output-string=14692551234

– This match-string checks if the input-string is 10 digits with digits 555 in positions 4, 5, and 6.

input-string=4695551212; match-string=^...555....; replace-string=&output-string=4695551212


OL-4495-04

Chapter 5 Digit ManipulationDigit Manipulation Tables

• None (or none)—The word “None” (or “none”) can appear in either a match-string or a replace-string to specify a NULL string.

– If the word “None” (or “none”) appears in the match-string, it indicates when input-string is NULL, it should be replaced with the replace-string.

input-string=NULL; match-string=none; replace-string=4692550000;output-string=4692550000

The input-string (NULL) matches the match-string (none), so the input-string is replaced by the replace-string (4692550000).

– If the word “None” (or “none”) appears in the replace-string, it indicates when a match occurs, the input-string should be replaced with NULL.

input-string=4692551234; match-string=469255; replace-string=none;output-string=1234

A portion of the input-string matches the match-string, so the matched portion of the input-string is replaced with NULL (nothing), which essentially deletes the matched portion of the input-string. After the digit manipulation, the resultant string will be 1234.

Digit Manipulation TablesThe Digit Manipulation Profile (digman-profile) and the Digit Manipulation (digman) tables were added to the Cisco BTS 10200 Softswitch software to support digit manipulation in Release 3.3 V04. Prior to this release, digit manipulation was accomplished in the Dial Plan (dial-plan) table using del_digits and pfx_digits, but it was available only for called party number (DNIS).

Digit manipulation can take place at several points in call processing, as illustrated in Figure 5-1.

Figure 5-1 Digit Manipulation Locations

The digit and NOA manipulation rules described in the “Digit Manipulation Rules” section on page 5-2 can be applied during the pretranslations, translations, or routing stages.

• Pretranslations Stage—In the pretranslations stage, the Dial Plan Profile table is used to specify if ANI, DNIS or both are to be manipulated. The purpose of the pretranslations stage is to normalize the digits as required during the translations stage. For example, if a region supports 7-digit dialing, you can use DNIS manipulation in the Dial Plan Profile table to add an HNPA (Home NPA) to make it a 10-digit directory number (DN).

• Translations Stage—The Dial Plan table can be used to manipulate the called party number (DNIS). Simple delete/prefix functionality is supported; however, this capability is no longer necessary.

• Routing Stage—The Destination table and/or Route table can be used to specify digit manipulation of ANI, DNIS or both. The dialed number can be normalized using the Destination table. In addition, if special manipulation is required based on the route selected, then that can be specified with each trunk group within a route.

8796

5

PretranslationsDial Plan Profile table

Digit and/or NOAmanipulation

ANI DNIS

TranslationsDial Plan table

Digit manipulationonly

DNIS

RoutingDestination, Route,Trunk Group tablesDigit and/or NOA

manipulation

ANI DNIS


OL-4495-04


If the called party 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.

Figure 5-2 illustrates the provisioning relationships for Cisco BTS 10200 Softswitch dial plans, which include the ANI/DNIS digital manipulation functions described in this chapter.

Figure 5-2 Dial Plan Provisioning Relationships

Tip Refer to Chapter 3, “Routing Provisioning,”in the Cisco BTS 10200 Softswitch Command Line Interface Guide for information on the tokens and values used in the Digit Manipulation Profile (digman-profile) table, Digit Manipulation (digman) table, Dial Plan Profile (dial-plan-profile) table, International Dial Plan Profile (intl-dial-plan-profile) table, Dial Plan (dial-plan) table, International Dial Plan (intl-dial-plan) table, Destination (destination) table, and Route (route) table. Refer to Chapter 2, “Office Provisioning,” for information on the tokens and values for the Trunk Group (trunk-group) table.

The following sections describe the provisioning and actions in each of the three stages in more detail.

8796

6

Digman Profiletable

Digman table(s)1 through 20 (max)

Dial Plan Profiletable

Dial Plan table

Intl Dial PlanProfile table

Intl Dial Plantable

Destinationtable

Trunk Grouptable

Route table

match-stringreplace-strngmatch-noareplace-noa

digman-id

ani-digman-iddnis-digman-id

nat-dial-plan-id

dialed-digits

noadel-digitspfx-digits

intl-dial-plan-id

intl-dial-plan-iddest-id

tgn-id (1 through 10)

call-typecarrier-iddial-plan-idroute-idroute-guide-id

call-agent-idcarrier-idcause-code-map-iddial-plan-idmain-sub-idpop-idqos-idsp-id

alt-route-idcall-agent-id (1 through 10)





dest-id


OL-4495-04

http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts4_1/cli/03rout.htm

http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts4_1/cli/02office.htm

http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts4_1/cli/02office.htm


Pretranslations StageIn the pretranslations stage, the Dial Plan Profile table (or International Dial Plan Profile table) is used to specify if ANI, DNIS, or both are to be manipulated. The purpose of the pretranslations stage is to normalize the digits, as required, during the translations stage.

In addition to manipulating the ANI/DNIS digits, the pretranslations stage can also be used to determine the nature of address (NOA) of the incoming digits (either ANI or DNIS or both).

Dial Plan Profile TableThe Dial Plan Profile (dial-plan-profile) table has been modified to allow provisioning of the ANI and DNIS digit manipulation rules. A dial-plan-profile ID can be assigned to a subscriber, an incoming trunk group, or a service provider. All records that share a common dial-plan-profile id are considered a dial plan. The dial-plan-profile table provides the following functions:

• Defines dial-plan tables

• National dial-plan-ID

• International dial-plan-ID

• NOA-based routing

Examples:

• In the first example, because the first character of the input string matches the specified match-string (^*), the NOA is changed to a vertical service code (VSC).

add digman id=pretrans; rule=1; match-string=^*; replace-string=&; match-noa=any; replace-noa=vsc;

input-string *55#; match-string=^*; replace-string=&output-string=*55#

• In the second example, because the last character of the input string matches the specified match-string (#), the NOA is changed to a VSC.

add digman id=pretrans; rule=2; match-string=#; replace-string=&; match-noa=any; replace-noa=vsc;

input-string=*55#; match-string=#; replace-string=&output-string=*55#

• In the third example there is no match, so the NOA is not changed and the output-string is the same as the input-string.

add digman id=pretrans; rule=3; match-string=*; replace-string=&; match-noa=any; replace-noa=vsc;

input-string=5555; match-string=*; replace-string=&output-string = 5555

International Dial Plan Profile Table

The International Dial Plan Profile (intl-dial-plan-profile) table is used to create unique IDs for international dial plans. An intl-dial-plan ID must be created before you can provision an International Dial Plan (intl-dial-plan) table.


OL-4495-04


Determining NOA for China

Use Table 5-1 to determine the NOA of incoming calls for China.

Note In North America the digman processing will not be available until after the hardcode parser is available. This means that all calls will be parsed and a NOA determined prior to performing the digman processing described in this chapter.

Feature Interaction

When a call is terminated to a subscriber with call forwarding activated, a feature interaction occurs if the call is forwarded out of the Cisco BTS 10200 Softswitch. In China, the Cisco BTS 10200 uses H.323 signaling to route calls to the PSTN; however, this scenario applies to any call which is forwarded over a non-SS7 signaling interface.

The H.323 protocol and other non-SS7 signaling protocols do not support the charge number parameter, original called party number, or redirecting party number. When call forwarding occurs, the ANI manipulation is performed on the redirecting party number if it is available. The DN of the forwarding party should also be sent as ANI digits and, as such in a forwarding scenario, the called number of the forwarding party should also be manipulated for the call.

Translations StageThe Dial Plan (dial-plan) table or International Dial Plan (intl-dial-plan) table is used during the translations stage to manipulate only the called party number. The previously existing capability of a simple delete and/or prefix digit manipulation function is also supported.

Note Although the simple delete and/or prefix digit manipulation function is still supported, it is no longer necessary because the same function(s) can now be accomplished in the other two stages.

Dial Plan TableMultiple Dial Plan (dial-plan) tables can be created by generating multiple dial-plan IDs in the dial-plan-profile table described above. The dial-plan table contains dial plan information for a specific type of call. It defines valid dialing patterns and determines call routing.

Examples:show dial-plan id=sub; digit-string=972-671;add dial-plan id=sub; digit-string=972-671; noa=national; dest-id=richardson;change dial-plan id=sub; digit-string=972-671; noa=national; dest-id=plano;delete dial-plan id=sub; digit-string=972-671; noa=national; dest-id=plano;help dial-plan;

Table 5-1 NOA Determination for China

Rule #Match-String

Replace-String

Match-NOA

Replace-NOA Remarks

1 * & Any VSC If first digit is a *, treat it as a VSC code.

2 # & Any VSC If first digit is a #, treat it as a VSC code.


OL-4495-04


International Dial Plan Table

International Dial Plan (intl-dial-plan) tables hold international dial plan information for calls to regions outside the NANP. It contains the country code, minimum and maximum digits, the country name, and the route-grp-id.

Examples:show intl-dial-plan id= default; cc=122;add intl-dial-plan id= default; cc=122; min-digits=7; max-digits=10;change intl-dial-plan id= default; cc=122; description=UK;delete intl-dial-plan id= default; cc=122;help intl-dial-plan;

Digit Manipulation Profile TableThe Digit Manipulation Profile (digman-profile) table is used to define IDs (1-16 ASCII characters) for Digit Manipulation (digman) tables. These IDs can be associated with service provider-defined descriptions (1-64 ASCII characters) for the corresponding digman tables.

The digman-profile table provides a digman-id that can be combined with up to 20 different match-string rules (one in each digman table) to be compared to the input-string. Each digman table is based on a unique combination of the digman-id and rule number. When a digman table is found and both the match-string and replace-string are provisioned, the string manipulation function is invoked, which applies the match rule to the input-string. If there is a match to the rule, the replace-string replaces the match-string and the manipulated string is the resultant output-string.

When there is a digit string match, NOA manipulation is also applied. If both match-noa and replace-noa are provisioned, and a match is obtained, the matched input-noa will be replaced with the replace-noa and the resultant NOA is the output-noa.

Digit Manipulation TableThe Digit Manipulation (digman) table is used to perform the actual digit and/or NOA manipulation. If a match is made between the input-string (or input-noa) and the specified match-string (or match-noa), the input-string (or input-noa) is replaced by the match-string (or match-noa).

See the “Digit Manipulation Rules” section on page 5-2 for detailed information on the use of the match-string, replace-string, match-noa, and replace-noa tokens.

The digman table supports the following functions:

• Delete Digits Function

• Prefix Digits Function

• Replace Digits Function

Delete Digits Function

The digman table supports the following delete digit capabilities:

• Deletion of Leading Digits

• Deletion of Specific Leading Digits

• Deletion of Trailing Digits

• Deletion of Specific Trailing Digits

• Deletion of Leading Digits if Length Matches

• Deletion of Trailing Digits if Length Matches


OL-4495-04


The following sections provide examples of the digman table provisioning required to implement the delete digit functions.

Deletion of Leading Digitsadd digman id=del3; match-string=???; replace-string=none;oradd digman id=del3; match-string=^???; replace-string=none;********************************************************Enter input string4692551234Match string???Replace string noneMATCHED

Output string = 2551234**************************************************

Deletion of Specific Leading Digitsadd digman id=del00; match-string=^00; replace-string=none;*********************************************************************Enter input string 0012345Match string ^00Replace string noneMATCHED

Output string = 12345*********************************************************************

Deletion of Trailing Digitsadd digman id=dellast4; match-string=????$; replace-string=none;*********************************************************************Enter input string 4692551234Match string ????$Replace string noneMATCHED

Output string = 469255******************************************************************

Deletion of Specific Trailing Digitsadd digman id=delx1212; match-string=1212$; replace-string=none;****************************************************************Enter input string 4695551212Match string 1212$Replace string noneMATCHED

Output string = 469555****************************************************************

Deletion of Leading Digits if Length Matches

Leading digits are deleted only if the length of the input-string matches the length of the match-string.

add digman id=del310; match-string=^???…….; replace-string=none;oradd digman id=del310; match-string=???…….; replace-string=none; *********************************************************************


OL-4495-04


Enter input string 4692551234Match string ???.......Replace string noneMATCHED

Output string = 2551234**********************************************************

Deletion of Trailing Digits if Length Matches

Trailing digits are deleted only if the length of the input-string matches the length of the match-string.

add digman id=dellast4; match-string=……????; replace-string=none;oradd digman id=del310; match-string=^……????$; replace-string=none; *********************************************************************Enter input string4692551234Match string ......????Replace string noneMATCHED

Output string = 469255****************************************************

Prefix Digits Function

The Digit Manipulation table also supports the prefixing of digits. The following prefix functions are supported:

• Prefixing Leading Digits

• Prefixing Leading Digits if Length Matches

The following sections provide examples of the Digit Manipulation (digman) table provisioning required to implement the prefix functions.

Prefixing Leading Digitsadd digman id=pfx469; match-string=^; replace-string=469;**********************************************************Enter input string 5551234Match string ^Replace string 469MATCHED

Output string = 4695551234*******************************************************

Prefixing Leading Digits if Length Matchesadd digman id=pfx469if7; match-string=^…….; replace-string=469;oradd digman id=pfx469if7; match-string=…….; replace-string=469;*********************************************************************Enter input string5551234Match string^.......Replace string469MATCHED

Output string = 4695551234****************************************************


OL-4495-04


Replace Digits Function

The Digit Manipulation table supports digit replacement based on matched string. When a match is found, the matched string is replaced with the replace-string.

• Replacing Leading Digits

• Replacing Trailing Digits

• Replacing Specific Digits

• Replacing Leading Digits if Length Matches

• Replacing Specific Digit Positions

• Replacing Specific Digits by Position

• Replace if Input String NULL

The following sections provide examples of the digman table provisioning required to implement the replace digits functions.

Replacing Leading Digitsadd digman id=del6pfx5; match-string=??????; replace-string=5; oradd digman id=del6pfx5; match-string=^??????; replace-string=5;*******************************************************************Enter input string4692551234Match string??????Replace string5MATCHED

Output string = 51234******************************************************Enter input string4692551234Match string^??????Replace string5MATCHED

Output string = 51234*******************************************

Replacing Trailing Digitsadd digman id=del4rep0000; match-string=????$; replace-string=0000;*******************************************************************Enter input string4692551234Match string????$Replace string0000MATCHED

Output string = 4692550000******************************************************

Replacing Specific Digitsadd digman id=del469255pfx5; match-string=469255; replace-string=5;*******************************************************************Enter input string4692551234Match string469255Replace string5MATCHED

Output string = 51234******************************************************


OL-4495-04


Replacing Leading Digits if Length Matchesadd digman id=del6pfx5; match-string=469255….; replace-string=5;****************************************************************Enter input string4692551234Match string469255....Replace string5MATCHED

Output string = 51234*************************************************Enter input string4692550Match string469255....Replace string5Not MATCHED

Output string = 4692550***********************************************************

Replacing Specific Digit Positionsadd digman id=rep456w222; match-string=…???….; replace-string=222;add digman id=replast4; match-string=……????; replace-string=0000;******************************************************************Enter input string4695551234Match string...???....Replace string222MATCHED

Output string = 4692221234*********************************************Enter input string4695551234Match string......????Replace string0000MATCHED

Output string = 4695550000****************************************************

Replacing Specific Digits by Positionadd digman id=rep555; match-string=…555….; replace-string=222;**************************************************************Enter input string4695551234Match string...555....Replace string222MATCHED

Output string = 4692221234****************************************************

Replace if Input String NULLadd digman id=repifnull; match-string=none; replace-string=4692550000;**********************************************************************Enter input stringnoneMatch stringnoneReplace string4692550000MATCHED

Output string = 4692550000****************************************************


OL-4495-04


Enter input string4695551234Match stringnoneReplace string4692550000Not MATCHED

Output string = 4695551234****************************************************

Nature of Address Manipulation

The Digit Manipulation (digman) table also supports nature of address (NOA) manipulation.

To perform NOA manipulation only, the match-string and the replace-string should both be NULL.

add digman id=dg1; rule=1; match-noa=any; replace-noa=subscriber;

If both digit and NOA manipulation rules are defined, then digit manipulation is performed only if the NOA value specified in the match-noa token matches the input-noa and the value specified in the match-string token matches the input-string.

add digman id=dg1; rule=1; match-string=%255; replace-string=5;match-noa=national; replace-noa=abbr;

Table 5-2 Nature of Address Table

NOA Description

ANY When specified, matches any other NOA. This NOA can only be specified in the MATCH-NOA field

ABBR Abbreviated number

INTL International number

NATIONAL National number

NS0 Network specific (111 1000) number







OPERATOR Operator call

PRIVATE Private numbering plan

SUBSCRIBER Subscriber number

TEST-LINE Test line number

UNKNOWN NOA is unknown

VSC Vertical service code


OL-4495-04


Sample Provisioning

Figure 5-3 provides a sample provisioning script for implementation of the digman functionality.

Figure 5-3 Sample Provisioning

Caller A, using dial-plan-id=cdp20, dials 8007654321. The call hits the dial-plan-profile table (1) and uses the pretrans entry (2 and 3). It matches on the 800 number (4) and replaces it with 8881234 (5).

Routing StageThe digit manipulations for an outgoing call can be performed using one of the following methods:

• Destination Table

• Route Table

• Trunk Group Table

The ANI/DNIS digit manipulation specified in the Destination table is applied during the outgoing call setup. The dialed number can also be normalized using the destination table. In addition, if special digit 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 (ROUTE-TYPE=CARRIER), the ANI/DNIS digit manipulation IDs specified in the Destination table are ignored and carrier-based routing is performed.

Note Although both pfx_digits and del_digits still work in the Cisco BTS 10200 Softswitch Dial Plan table, if the subscriber dials a 7-digit number, but LNP queries require a 10-digit DN, then the digman tables should be set up to add an NPA, making the called number a 10-digit DN before performing an LNP query.

8796

7

Add digman id=pretrans; rule=1; match_string=8007654321; replace_string=8881234;

match_noa=any; replace_noa=unknown;

Add dial-plan-profile ID=cdp20; description=china dial plan profile;

nanp-dial-plan=N; ani-digman-id=ani_20; dnis-digman-id=pretrans;

Add route id=rt_h323_id; lcr=n; tgn1-id=4092; del-digits1=0; del-digits2=0;

del-digits3=0; del-digits4=0; del-digits5=0; del-digits6=0; del-digits7=0;

del-digits8=0; del-digits9=0; del-digits10=0; tg-selection=seq;

ani-digman-id1=dm_ani_add_0; dnis-digman-id1=dm_dnis_remove_0;

1

2

3

54


OL-4495-04


Destination Table

The Destination table is used to manipulate ANI digits, DNIS digits, or both for an outgoing call. The digits are manipulated at the ANALYZED_INFO PIC during the outgoing route selection process. If the destination ID indicates that the outgoing call is based on the carrier ID, the ANI/DNIS digit manipulation is not performed and the call is routed based on the carrier data.

The Destination table is used to define the call type and the routing information for the dialed digits. Multiple digit strings in the Dial Plan table can use the same destination id.

Examples:show destination dest-id=DallasAustin;add destination dest-id=DallasAustin; call-type=toll;

route-type=route; route-guide-id=rg10; change destination dest-id=DallasAustin; route-guide-id=rg11;delete destination dest-id=DallasAustin;help destination

Route Table

The Route table gives a list of up to 10 trunk groups to route a call. If all the trunk groups are either busy or not available, call processing uses alt-route-id (if specified) to route the call.

• If ANI/DNIS digman IDs are specified with selected trunk group, they are applied during routing.

• If DNIS digman ID is specified, the Delete Digits and Prefix Digits tokens are ignored.

• If Tech-prefix is to be pre-pended, it can be specified via the DNIS-DIGMAN-ID.

Examples:show route id=Dallas1;add route id=Dallas1; tgn1-id=dallas-tg; prefix-digits1=972;

del-digits1=0;change route id=Dallas1; del-digits1=3;delete route id=Dallas1;help route

Trunk Group Table

The Trunk Group (trunk-grp) table identifies the trunk group and maps it to an associated media gateway.

Trunk group-based digit manipulation is applied only if the trunk group is retreived as part of subscriber termination.

Examples:show trunk-group id=101; add trunk-group id=101; call-agent-id=CA146; tg-type=ss7;

dial-plan-id=tg-dp; dpc=101-55-103; tg-profile-id=SS71change trunk-group id=101; cost=200;delete trunk-group id=101;help trunk-group


OL-4495-04



OL-4495-04


C H A P T E R 6
Local Number Portability
This chapter describes local number portability (LNP) and its implementation and operation on the Cisco BTS 10200 Softswitch. This chapter consists of the following sections:

• Introduction to LNP, page 6-1

• Cisco BTS 10200 Softswitch LNP Function, page 6-10

• Provisioning Ported Numbers, page 6-14

• Local Exchange Routing Guide, page 6-22

Introduction to LNP

Note If you are already familiar with Local Number Portability and the operations of the Number Portability Administration Center Service Management System (NPAC SMS), you can proceed directly to the “Cisco BTS 10200 Softswitch LNP Function” section on page 6-10.

Local number portability (LNP), which is required by the Telecommunications Act of 1996, is defined by the Federal Communications Commission (FCC) as “the ability of [subscribers] to retain, at the same location, existing telecommunications numbers without impairment of quality, reliability, or convenience when switching from one telecommunications carrier to another.”

The North American Numbering Council (NANC) is the Federal Advisory Committee created to advise the FCC on numbering issues. NANC was also charged with the responsibility for selecting the entities to serve as Local Number Portability Administrators (LNPAs). The LNPA Selection Working Group developed the process for selecting LNPA(s) and prescribed the specific duties of the LNPA(s).

Eight regional LNP databases were established in North America, with each of the seven U. S. regions coinciding with the seven original Bell Operating Company (BOC) regions; the eighth region is Canada. Lockheed-Martin Information Management services (now NeuStar, Inc.), was the vendor of choice for all eight regions and is currently the LNPA managing the Number Portability Administration Center Service Management System (NPAC SMS).

The NPAC SMS currently consists of two data centers with the primary data center in Sterling, VA and a backup data center in Charlotte, N.C. To access NPAC services, service providers (SPs) are required to provide an Operating Company Number (OCN), which is assigned by the National Exchange Carrier Association (NECA). NPAC uses the individual service provider's OCN as the Service Provider Identification Number (SPID).


Chapter 6 Local Number PortabilityIntroduction to LNP

LNP ImplementationThe LNPA Working Group was also given the responsibility for directing the implementation of a nationwide system of regional SMS databases for number portability, and determining possible future SMS needs. Number Portability Switching Systems (T1.TRQ.02-2001), a technical requirements document that is available for a fee from the Alliance for Telecommunications Industry Solutions (ATIS) Document Center located at http://www.atis.org/doccenter.shtml, defines the switch requirements for Number Portability (NP) between wireline networks using the Location Routing Number (LRN) method. Under the LRN method, a unique 10-digit number is assigned to each central office switch to identify each switch in the network for routing purposes. The LRN serves as a network address.

The type of telephone number portability that local telephone companies must currently provide under the terms of the Telecommunications Act of 1996 and FCC docket 95-116 is called “service provider Portability.” The NANC Functional Requirements Specification (FRS) Release 3.2.1a, which was issued July 28, 2003, defines the functional requirements of the NPAC SMS that enable service provider portability (see http://www.npac.com/documents.htm#v3.2).

To provide the Service Provider Portability type of LNP in North America, the Alliance for Telecommunications Industry Solutions (ATIS) T1S1 committee’s LRN database lookup scheme was approved by FCC Order 97-289, 18 August 1997. When customers change service providers, the LRN of the switch to which they transfer is returned in response to all LNP queries generated by calls to the subscriber’s telephone number (TN).

As stated previously, the LRN is a 10-digit number—the network address of the switch that received the subscriber’s telephone number from the previous service provider—that uniquely identifies a switch or point of interconnection (POI). The LRN is used to route all calls to numbers that have been ported. According to the ATIS Industry Numbering Committee's (INC's) Location Routing Number Assignment Practices, “a unique LRN may be assigned to every LNP-equipped switch. Service providers should select and assign one (1) LRN per Local Access and Transport Area (LATA)—the geographic area over which the Local Exchange Carrier (LEC) may provide toll calls—within their switch coverage area.”

Telephony switches contain a database of the office codes (NPA-NXXs) associated with subscriber numbers that have been ported from or to any switch. This information is available in two different formats from two different locations:

• The database at the NPAC SMS contains the LRNs of all switches (NPA-NXX) that have had at least one telephone number ported in or ported out.

• The Local Exchange Routing Guide (LERG) designates all switches (NPA-NXX) that are currently open to portability.

When a service provider needs a new exchange number (NXX), it enters the required information into the Routing Database System (RDBS), which is a mechanized database maintained by NeuStar. All NPA/NXX activity in the United States is reported to the RDBS, and the information is used to produce the LERG and the Terminating Point Master (TPM) used for Signaling System 7 (SS7) information.

The LERG information is used by most service providers in the North America Numbering Plan (NANP) to maintain their OSS databases with the information needed for rating and routing. More detailed information on the contents of the LERG is provided at the end of this document.


OL-4495-04

http://www.atis.org/doccenter.shtml

http://www.npac.com/documents.htm#v3.2


Process FlowsThe NPAC SMS prescribes the operational and administrative aspects of the intercompany procedures that are required to change a subscriber from one service provider to another. The following sections describe most of the process flows, which indicate how the NPAC SMS procedures are used by service providers in the business processes associated with porting subscriber telephone numbers. The specific requirements generated by these process flows are included in the appropriate sections that follow.

The process flows supported by the NPAC SMS that are described here include:

• Service Provisioning, page 6-4

• Service Order Cancellation, page 6-5

• Service Disconnection, page 6-6

• Conflict Resolution, page 6-7

• Audit Requests, page 6-8

• Report Requests, page 6-8

The NPAC SMS supported work flows that are not described here include:

• Service Repair

• Disaster Recovery and Backup

• Data Administration Requests

Refer to the NANC Functional Requirements Specification (FRS) Release 3.2.1a, July 28, 2003, for the process flows for these three areas (see http://www.npac.com/documents.htm#v3.2).

Flow Chart Legend

1043

07

The oval shape represents the termination or end point of a process flow.

Rectangular boxes represent Service Provider (SP) procedures external to the NPAC SMS.

Boxes with rounded corners represent NPAC SMS sub-process work flows.

Diamonds represent decisions - either by the Service Provider or NPAC SMS personnel.

Circles represent connections to a process in another flowchart. The text indicates acorresponding connection point in another flowchart.

The following flow charting symbols are used in the process flow charts in this document.

text


OL-4495-04

http://www.npac.com/documents.htm#v3.2


Service Provisioning

This section defines the service provisioning work flow by which a telephone number is ported to a new service provider. The service provisioning flow activities are shown in Figure 6-1.

Figure 6-1 Service Provisioning Work Flow

The service provisioning process includes all the steps necessary to complete the porting-in process; however, some situations may preclude the process from being completed (see the “Service Order Cancellation” section on page 6-5).

To provision a subscriber’s ported-in telephone number, complete the following steps:

Step 1 The new service provider obtains the customer’s authorization to port the subscriber’s telephone numbers and notifies the old service provider according to the internal business processes of the respective service providers.

The processes for obtaining authorization from the subscriber to port a number are defined solely by the service providers. The NPAC does not obtain or verify customer approval to port a telephone number.

Step 2 Both the old and new service provider can send notifications of the impending change to the NPAC SMS from their Service Order Administration Systems (SOAs).

Step 3 The NPAC SMS receives the notifications, performs validation checks, and attempts to match the notification received from the new service provider with a concurring notification that may (or may not) be sent from the old service provider.

If the NPAC SMS receives a notification from the old service provider, but none from the new service provider, it automatically cancels the request and the subscriber remains with the old service provider.

Step 4 If both notifications that NPAC receives are valid, NPAC notifies both service providers that they can complete any physical changes required.


OL-4495-04


Step 5 Both service providers complete any physical changes that are required, such as moving the subscriber loop.

Step 6 When the due date for providing service by the new service provider is reached, the new service provider sends an activation notice to the NPAC SMS.

Step 7 The NPAC SMS broadcasts the update in real time to each of the eight regional SMSs.

Step 8 Upon receiving the update from the NPAC SMS, all service providers update their network switches with the latest LNP information.

The NPAC SMS records any transmission failures and takes the appropriate action.

End-office switches have a table identifying all office codes (NPA-NXX) that include one or more subscriber numbers that have been ported in or ported out.

The routing of calls to ported numbers should be accomplished by the originating switch; however, if a donor switch receives a call for a number that has been ported-out it can send a query to its regional LNP database (NPAC SMS), retrieve the recipient switch’s LRN, and reroute the call to that switch.

Service Order Cancellation

Some situations can preclude the service provisioning process from being completed. When these situations occur, the NPAC SMS has some very explicit rules regarding the cancellation of service orders, as illustrated in Figure 6-2.

The following list describes the rules that are applied in different scenarios:

• If a Create Subscription notification is sent by both service providers, either service provider can send a message to the NPAC SMS to cancel the Subscription Version (SV).

If both service providers concur with the cancellation, the NPAC SMS sets the Subscription Version to “canceled” and notifies both service providers that the Subscription Version has been canceled.

• If a Create Subscription notification is sent by only the new service provider, only the new service provider can send a message to the NPAC SMS to cancel the Subscription Version.

If cancellation concurrence is not provided by the old service provider, the Subscription Version is still set to the “canceled” state by the NPAC SMS.

• If a Create Subscription notification is sent by only the old service provider, only the old service provider can send a message to the NPAC SMS to cancel the Subscription Version.

If cancellation concurrence is not provided by the new service provider, the Subscription Version is placed in the “conflict” state by the NPAC SMS, and the process for handling conflicts is invoked.


OL-4495-04


Figure 6-2 Service Order Cancellation Work Flow

Service Disconnection

Disconnecting a subscriber who has a ported telephone number also requires interaction with the NPAC SMS, as illustrated in Figure 6-3.

To disconnect a subscriber who has a ported telephone number, complete the following steps:

Step 1 The subscriber and service provider agree on a disconnect effective date and time.

Step 2 The current service provider sends an update indicating the disconnect to the appropriate NPAC SMS.

Step 3 NPAC SMS broadcasts the update to all service providers based on the disconnect effective date.

Step 4 On the effective date, NPAC SMS removes the ported telephone number from its database of ported numbers.

If the service provider needs to change the Customer Disconnect Date (CDD) or Effective Release Date (ERD) of the disconnect, the service provider sends a modify request to the NPAC SMS.

Step 5 Upon receiving an update, all service providers remove the telephone number from their LNP databases.

NPAC SMS logs the update in a history file, and calls to the telephone number are routed as if it were a non-ported number.

Yes

No

End

Conflict

Old SP

New SP

SP issues acancellation notice

NPAC issues acancellation notice

Has onlyone SP

issued a create?

Is requesterthe SP that issuedcreate or is it NPAC

initiated?

NPAC SMS cancelsthe Subscription

Version and notifiesboth SPs

Was theprevious SV statecancel-pending

?

Is SV statein conflict

?

Did cancel-requesting SP

concur on previouscancel

?

Cancelacknowledgments

received withintunable number

of hours?

Subscription Versionstatus set to "cancel-pending." Notify both

SPs

1040

35

Reject

Yes

Yes

One

No

NPAC requests missingacknowledgments

Was Ackreceived from

Old SP orNew SP?

YesNo

No

Yes

Yes

No

No


OL-4495-04


Figure 6-3 Disconnect Ported Number Work Flow

Conflict Resolution

Some conflicts can arise in the LNP processes. Figure 6-4 illustrates the causes of conflicts and the procedures that the NPAC SMS uses to resolve them.

If either the old or new service provider did not send a notification to the NPAC SMS, the NPAC SMS notifies the service provider from which it did not receive a notification that it is expecting a notification. If the NPAC SMS receives the missing notification, and both notifications indicate agreement among the service providers, the process proceeds as normal.

The following list describes the actions that the NPAC SMS takes in different situations:

• If the NPAC SMS does not receive a concurring notification from the old service provider, the NPAC SMS logs the failure to respond and allows the new service provider to proceed with activation when the new service provider due date is reached.

• If the NPAC SMS does not receive a concurring notification from the new service provider, the NPAC SMS logs the failure to respond, cancels the request, and notifies both service providers of the cancellation.

• If the service providers disagree as to who will provide service for the telephone number, the NPAC SMS places the request in the “conflict” state and notifies both service providers of the conflict status and the Status Change Cause Code.

– The service providers then determine between them who will serve the customer using their internal business processes.

– When a resolution is reached, the NPAC SMS is notified by the new service provider and removes the request from the conflict state.

Within the first 6 hours, only the old service provider can initiate “conflict off.” After 6 hours, either service provider can remove the conflict status. The new service provider can alternatively request cancellation of the Subscription Version.

End

Repair

1040

36

Yes

No

Customer notifies SPof disconnect request.

SP notifies NPAC SMS.

"EffectiveRelease Date/Time"

= current ?

Customer disconnectdate modification to

SOA

NPAC SMSbroadcastsDisconnect

Wait until "EffectiveRelease Date/Time"=current date/time

Broadcast/Rebroadcast

subflow

BroadcastAcknowledged

?

TunablesExceeded

?

Yes

No

YesNo


OL-4495-04


Figure 6-4 Conflict Resolution Work Flow

Audit Requests

An audit function is necessary for troubleshooting customer problems and as a maintenance process to ensure Subscription Version data integrity across the entire LNP network. Audits are concerned with the process of comparing the NPAC SMS view of the LNP network's Subscription Version data with one or more of the service provider's views of its network.

The following methods help ensure data integrity across the LNP network:

• On-demand audits can be initiated by any service provider who believes a problem may exist in another service provider’s network. These audits are executed through queries to the appropriate service provider’s network, and corrected by means of downloads to those same networks.

• Local service providers are also responsible for comparing database extracts of Subscription data written to an FTP site by the NPAC SMS with their own versions of the same Subscription data.

• The NPAC SMS selects a random sample of active Subscription Versions from its own database, then compares those samples to the representation of that same data in the various local SMS databases.

Report Requests

The NPAC SMS supports report generation for predefined and ad hoc reports. The report generation function creates output report files according to specified format definitions, and distributes reports to output devices as requested. The report distribution service supports distribution to electronic files, to local or remote printers, to e-mail addresses, and to fax machines.

End

1040

37

Yes

No

Cancel-pendingacknowledgmentfrom the new SP

is missing

NPAC changesSubscription Versionstatus to conflict and

notifies both SPs.

New SPcoordinatesresolution.

Old SP requestsconflict status

Rec'dprior to

noon on businessday beforedue date

?

Havetunable max

# of days (30)elapsed?

ConflictResolved?

(see note 1)

First timeinto conflict

?

NPAC SMS cancelsSubscription Version

and notifies both SPs.

Record is placed inpending status. Status

change notificationsent to both SPs.

Yes

No

No

Yes

Requestrejected

Yes

No


OL-4495-04


Data ManagementThe NPAC SMS supports functionality to manage network, service provider, and Subscription Version data.

NPAC Network Data

The NPAC SMS database contains data that defines configuration of the LNP service and the network. This includes such data as:

• Participating service providers

• NPA-NXXs that are portable

• LRNs associated with each service provider

An NPAC SMS database can reside in a service control point (SCP), or it can be combined with signal transfer point (STP) equipment in the SS7 network. When the database returns the LRN of a subscriber’s new switch, the call is redirected to the LRN and the original called number is included as additional data. When the recipient switch receives a call to its LRN, the original called number is extracted and the incoming call is routed to that number.

Service Provider Data

Service provider data indicates who the LNP service providers are and includes location, contact name, security, routing, and network interface information.

Subscription Version Data

The Subscription Version data indicates how local number portability should operate to meet subscribers needs.

Troubleshooting LNP ProblemsProblems can arise when porting a subscriber’s telephone number from one service provider to another. The Network Interconnection Interoperability Forum (NIIF), a part of the ATIS organization, has published a document (ATIS/NIIF-0017) that includes detailed steps that service providers should follow when LNP problems are encountered. The document is titled Guidelines for Reporting Local Number Portability Troubles in a Multiple Service Provider Environment, and it is available at http://www.atis.org/atis/clc/NIIF/niifdocs.htm.

The NIIF also maintains the National LNP Contact Directory, a protected document that provides telephone numbers of 24x7 LNP-qualified contacts for each service provider. The directory is located at the URL given above. You can download and submit an application for a password at the same URL.


OL-4495-04

http://www.atis.org/atis/clc/NIIF/niifdocs.htm

Chapter 6 Local Number PortabilityCisco BTS 10200 Softswitch LNP Function

Cisco BTS 10200 Softswitch LNP FunctionThis section describes how to provision the local number portability (LNP) functionality on a Cisco BTS 10200 Softswitch to support both ported-in and ported-out subscriber telephone numbers.

Establishing a SessionUsing the Cisco BTS 10200 Softswitch command line interface (CLI), you can initiate an interactive CLI session using the Secure Shell (SSH) to build and send CLI commands by typing them in. You can also install a GUI tool, such as the Extensible Provisioning Object Manager (EPOM), or you can build and send CLI commands using predefined scripts, depending on the extent of the operations you want to do.

The following sections specify how you can create the CLI commands, and where you can obtain the values of the CLI command parameters. Command parameters that are hard coded are shown in the commands as they would be generated: for example, port-start=1. Command parameters that must be obtained elsewhere are shown in traditional variable brackets in italics <parameter>: for example,

tsap-addr=<network_address_of_MTA>

Provisioning commands can be successfully executed only on the Cisco BTS 10200 Softswitch Element Management System (EMS) that is in an active status. Therefore, at the beginning of each session you must determine which EMS is the active EMS. Using the IP addresses and identifiers of the primary and secondary EMSs, query each to determine which EMS is active, as described in the following sections.

Logging in Using Secure Shell

Secure Shell (SSH) is the method used to access the Cisco BTS 10200 Softswitch CLI prompt and login to the primary EMS. SSH provides encrypted communication between a remote machine and the EMS or Call Agent for executing CLI or MAINT commands. SSH servers run on both EMSs and CAs of the softswitch. To connect, the client and server sides must both be running the secure shell daemon (SSHD).

You can get IP addresses and identifiers for the primary and secondary EMSs from the SOFTSW_INFO table by using the subscriber’s TN (the TN_INFO table contains the SOFTSW_ID as a foreign key).

To establish an SSH session and log in to the primary EMS, complete the following steps:

Step 1 To log in from the client side, use an SSH client program or enter the following at a console:

ssh <username>@<IPaddress>

On the first SSH log in from the client side, you might see a message similar to the following:

The authenticity of host [hostname] can't be established.Key fingerprint is 1024 5f:a0:0b:65:d3:82:df:ab:42:62:6d:98:9c:fe:e9:52.

Are you sure you want to continue connecting (yes/no)?

Step 2 If a message similar to one above is displayed, enter yes to continue.

The default password prompt appears. From this point on, all communications are encrypted.

Step 3 Enter the default password.

With SSH enabled, new users are prompted to enter a new password and you must reenter that password during your first log in. From that point on, you are prompted only once at the beginning of each session for your password.


OL-4495-04


Step 4 At the log in prompt, enter your CLI username.

The password prompt appears.

Step 5 Enter your password.

• If the EMS you attempt to log in to is the primary EMS, a message similar to the following is displayed:

Last login: Thu Apr 15 10:24:15 2004 from 64.101.149.247Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001CLI>

If the system responds with a CLI> prompt, you are ready to send commands to the EMS. Proceed to Step 6.

• If the EMS you attempt to log in to is the secondary EMS, a message similar to the following is displayed:

Last login: Thu Apr 15 10:24:15 2004 from 64.101.149.247Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001Unable to initialize the Session ERROR reply from Session Manager -->No login allowed on the STANDBY EM01 application.CLI will terminate in 30 seconds

The system will log you off. Determine the the IP address and identifier of the other EMS and repeat Step 1 through Step 5.

If you cannot establish an SSH session with, or log in to the primary EMS, you can attempt to log in to the secondary EMS, as described in the next section.

Step 6 Use the following command to show user activity on the EMS:

CLI>show ems

You should receive a response similar to the following:

Reply : Success: Current EMS logical IP assignment.

IP_ALIAS=Not-defined-yetINTERFACE=hme0

CLI>

Step 7 Enter any other desired commands.

Step 8 To log off and terminate the SSH session, enter exit at the CLI> prompt.

Logging in to the Secondary EMS (Optional)

You can optionally attempt to log in to the secondary (standby) EMS in the same manner described in the previous section by using the IP address of the secondary EMS. If a login to the secondary EMS fails, the system returns an error message.

If you cannot log in to either the primary (active) EMS or the secondary (standby) EMS, consult your Cisco BTS 10200 administrator or contact Cisco TAC for assistance.


OL-4495-04


Provisioning Ported Office CodesThe Local Exchange Routing Guide (LERG) designates all switches (NPA-NXX) that are currently open to portability. The assigned NPA-NXXs are managed by the Cisco BTS 10200 Softswitch in the PORTED-OFFICE-CODE table. The ranges of portable office codes are listed in NPA-NXX, NPA-NXX-X, NPA-NXX-XX, NPA-NXX-XXX, or NPA-NXX-XXXX formats depending on how wide a range of numbers is needed (10,000, 1,000, 100, 10, or 1 respectively).

If the Cisco BTS 10200 Softswitch has office codes that have been ported-in, the in-call-agent flag associated with those office codes in the PORTED-OFFICE-CODE table is set to Y (Yes).

• If the in-call-agent flag for an office code is set to Y (Yes), the Cisco BTS 10200 Softswitch performs an internal DB lookup in the DN2SUBSCRIBER table.

– If the directory number (DN) is found, the call is terminated locally within the switch.

– If the directory number (DN) is not found, an LNP query is made to determine how to route the call.

• If the in-call-agent flag for an office code is set to N (No), an LNP query is made to determine how to route the call.

To set up a ported-office-code in the Cisco BTS 10200 Softswitch, complete the following steps:

Step 1 Log in to the Cisco BTS 10200 Softswitch and display the CLI prompt.

Step 2 Enter a command similar to the following:

add ported-office-code digit-string=469-255;

Reply: Success: CLI add successfulTransaction 106634552016805 was processed.

Step 3 Verify the office code you entered by entering the following command:

show ported-office-code;

DIGIT_STRING=469255IN_CALL_AGENT=N

Reply: Success: Entry 1 of 1 returned.

Step 4 Set the in-call-agent flag to Y by entering a command similar to the following:

change ported-office-code; digit-string=469-255; in-call-agent=y;

Reply: Success: CLI change successfulTransaction 106641008260905 was processed.

Step 5 Verify the setting of the in-call-agent flag by entering the following command:

show ported-office-code;

DIGIT_STRING=469255IN_CALL_AGENT=Y



OL-4495-04


Provisioning the Unconditional LNP TriggerUnconditional LNP triggers are assigned on a per-DN basis. The Cisco BTS 10200 manages it in the DN2SUBSCRIBER table by setting the lnp-trigger flag to Y (Yes).

• If the lnp-trigger flag for a number in the DN2SUBSCRIBER table is set to Y (Yes), an unconditional LNP query of the NPAC SMS database is initiated to determine where to route the call.

• If the lnp-trigger flag for a number in the DN2SUBSCRIBER table is set to N (No), the call is terminated locally within the Cisco BTS 10200 without generating an LNP query.

To provision an unconditional LNP trigger, complete the following steps:


Step 2 Enter a command similar to the following:

show dn2subscriber office-code-index=6; dn=1112;

OFFICE_CODE_INDEX=6DN=1112STATUS=ASSIGNEDRING_TYPE=1LNP_TRIGGER=NNP_RESERVED=NSUB_ID=yoda


Step 3 Set the lnp-trigger flag to Y by entering a command similar to the following:

change dn2subscriber office-code-index=6; dn=1112; lnp-trigger=y;

Reply: Success: Transaction 106641047028705 was processed.

Step 4 Verify that the lnp-trigger flag has been set to Y by entering the following command:

show dn2subscriber office-code-index=6; dn=1112;

OFFICE_CODE_INDEX=6DN=1112STATUS=ASSIGNEDRING_TYPE=1LNP_TRIGGER=YNP_RESERVED=NSUB_ID=yoda



OL-4495-04

Chapter 6 Local Number PortabilityProvisioning Ported Numbers

Provisioning Ported NumbersThe Cisco BTS 10200 Softswitch can accommodate the following two LNP situations:

• A new subscriber moves to the switch from another service provider’s switch and requests LNP service (ported-in).

• An existing subscriber moves to another service provider and requests LNP service (ported-out). See the “Porting-out a Subscriber” section on page 6-20.

Porting-in a SubscriberTo port-in a subscriber requesting LNP service, you must complete the following procedures:

• Provisioning Ported-in Numbers, page 6-14

• Transition Period, page 6-16

• Changing lnp-trigger to Y, page 6-17

• Activating a Media Gateway, page 6-17

• Activating a Subscriber, page 6-18

• Changing lnp-trigger to N, page 6-18

Provisioning Ported-in Numbers

To provision the Cisco BTS 10200 Softswitch for ported-in numbers, perform the following steps:


Step 2 If you have been notified that a subscriber number (or numbers) are to be ported in to your switch, but the physical move has not been completed, enter a command similar to the following:

add ported-office-code digit-string=469-255; in-call-agent=y;

This command sets up a 6-digit office code (469-255) in the PORTED-OFFICE-CODE table with the in-call-agent flag set to Y (Yes), which indicates that a subset of the numbers from 469-255-0000 through 469-255-9999 within that office code are portable, and are serviced by this switch.

Step 3 Before a DN can be assigned to a ported-in subscriber, the subscriber’s office code also has to be defined in the OFFICE-CODE table. To define an office code (NDC), enter a command similar to the following:

add ndc digit-string=469;


Step 4 To define an exchange code, enter a command similar to the following

add exchange-code ndc=469; ec=255;


Step 5 To assign the office code to a Call Agent, enter a command similar to the following:

add office-code ndc=469; ec=255; call-agent-id=CA146; dn-group=xxxx;



OL-4495-04


Step 6 Verify that the office code has been entered by entering the following command:

show office-code ndc=469; ec=255;

DIGIT_STRING=469255OFFICE_CODE_INDEX=11DID=NCALL_AGENT_ID=CA146DIALABLE=YNDC=469EC=255DN_GROUP=xxxx


Step 7 To add the ported-in subscriber, enter a command similar to the following:

add subscriber ID=<subscriber ID>; category=INDIVIDUAL; name=<subscriber name>; status=ACTIVE; address1=<address line 1 from billing system>; city=<city from billing system>; state=<state from billing system>; zipcode=<zip code from billing system, no hyphens>; billing-dn=<TN to be used in CDR’s>; dn1=<TN to be associated with this subscriber>; privacy=<privacy option>; ring-type-dn1=1; term-id=aaln/1; mgw-id=<mgw-id>; pic1=<carrier for interlata calls>; pic2=<carrier for intralata toll calls>; pic3=<carrier for international calls>; grp=N; usage-sens=Y; sub-profile-id=mototampa; cos-restrict-id=INTL; term-type=TERM;

This command creates a new subscriber in the switch, specifying information about the subscriber, their VoIP telephone number, the MTA MAC address, and several service characteristics. This command also loads the subscriber’s VoIP TN into the DN2SUBSCRIBER table in the Cisco BTS 10200 Softswitch, provided that the NPA-NXX has been loaded into the OFFICE-CODE table. If the NPA-NXX has not been loaded in the OFFICE-CODE table by this time, this command will generate an error message.

Data elements specified in this command are:

• subscriber ID—Unique identifier of the subscriber’s VoIP service, formed by concatenating the subscriber’s identifier from the division billing system and the number of the voice port used for the service on the MTA (for example, 8223130012388228_01).

• category—Set to INDIVIDUAL for all subscribers.

• name—This field is used for the Calling Party Name Delivery (CNAM) feature if the local CNAM option is set in the POP table.

• status—Set to ACTIVE for all subscribers.

• Address fields—Taken from values used by the division billing system.

• billing-dn—The telephone number that will be used when creating call detail records for this subscriber.

• DN1—The first telephone number that will be routed to this service. Initially, there will only be one telephone number per VoIP subscriber.

• privacy—Can be set to NONE (display name and number), FULL (display neither name nor number), or NAME (display number, but not name).

• ring-type-dn1—Set to 1 for every subscriber.

• term-id—Set to aaln/1 for every subscriber.

• mgw-id—The unique identifier of the subscriber’s MTA, which is created by taking the MTA MAC address and stripping out all the hyphens.


OL-4495-04


• pic1, pic2, pic3—Parameters that are used by the Cisco BTS 10200 Softswitch to route calls from the subscriber:

– pic1 is the preferred interLATA carrier.

– pic2 is the preferred intraLATA carrier.

– pic3 is the preferred international carrier.

However, if the only gateway to an LD carrier is through a competitive local exchange carrier (CLEC) partner (that is, no direct trunks exist from our media gateway to the LD carrier), then pic1 should be the CIC code of the CLEC partner, not the LD carrier, because the CLEC partner would have to carry LD calls from the subscriber to their preferred LD carrier.

• grp—Indicates if the subscriber is an individual or a group. Default value is N.

• usage-sens—Specifies if usage-sensitive features are active for this subscriber. Default value is Y.

• sub-profile-id—Identifies the subscriber profile assigned to the subscriber.

• cos-restrict-id—Identifies the class of service (CoS) restriction profile assigned to the subscriber.

• term-type—Identifies the termination type for the subscriber.

Transition Period

During the transition period when a subscriber telephone number is in the process of being ported out or ported in, the subscriber loop move may not be completed.

The process of porting a number out of a donor switch and porting it into the recipient switch requires some amount of time to complete the physical move plus the administrative changes that are necessary. Special call processing might be required during this brief transition period between the time that the subscriber requests that its numbers be ported, the physical move is coordinated, the subscriber’s LNP activation in the national LNP databases is completed, and the updated LNP information is disseminated to all of the switches within the NANP. During this brief period of time, the LNP databases at the NPAC SMS are the ultimate authority on how calls to the ported telephone number are to be routed.

In the Cisco BTS 10200 LNP implementation, the subscriber’s 10-digit DN and an unconditional trigger are used during the transition period. When the unconditional trigger is assigned to a 10-digit DN, all calls to that subscriber’s number generate an LNP query regardless of whether the call originates on-net or off-net. Based on the response to the LNP query, the call may terminate on the old service provider’s switch or it might be routed to the new service provider’s switch based on the LRN that is returned.

The DN2SUBSCRIBER table is checked for the dialed number as follows:

• If the subscriber’s number is present in the DN2SUBSCRIBER table, the setting of the lnp-trigger flag is checked to determine whether an LNP query is to be issued.

– If the lnp-trigger flag is set to Y (Yes), an LNP query is issued to determine the correct LRN (switch) to which to route the call.

– If the lnp-trigger flag is set to N (No), the call is terminated locally, if possible.

• If the subscriber’s number is not present in the DN2SUBSCRIBER table, an LNP query is issued to determine the correct LRN (switch) to which to route the call.


OL-4495-04


Changing lnp-trigger to Y

If the LNP transaction has not yet been activated in the national LNP databases, calls to this telephone number are routed to the current VoIP service provider’s switch. Any calls originating outside the Cisco BTS 10200 Softswitch will perform an LNP lookup, get the LRN of the current service provider’s switch, and route the call. However, calls originating on the Cisco BTS 10200 Softswitch will see the DN in the DN2SUBSCRIBER table, which has the lnp-trigger for this DN in the DN2SUBSCRIBER table set to N (No) by default.

For the Cisco BTS 10200 Softswitch to perform an unconditional LNP query, the lnp-trigger flag in the DN2SUBSCRIBER table must be set to Y (Yes). Changing lnp-trigger settings requires execution of a change transaction in the DN2SUBSCRIBER table, which is indexed by the OFFICE-CODE-INDEX.

To change the lnp-trigger flag to Y (Yes), complete the following steps:

Step 1 To retrieve the office-code-index, enter the following command:

show office-code digit-string=<NPA-NXX of the ported TN>;

The Cisco BTS 10200 Softswitch returns the office-code-index.

Step 2 Using the captured office-code-index, change the lnp-trigger for the ported-in subscriber’s DN by entering a command similar to the following:

change dn2subscriber office-code-index=11; dn=1234; lnp-trigger=y;

This command sets the lnp-trigger to Y, which generates an unconditional LNP query.

Activating a Media Gateway

The control command is used to change the state of the MTA to “in service.” You should monitor the Cisco BTS 10200 Softswitch transaction queue to verify that the media gateway has been successfully added before trying to activate the media gateway.

To verify that the media gateway has been added and to activate the media gateway, complete the following steps:

Step 1 Execute the following command, using the transaction-id of the command that added the media gateway:

show transaction-queue transaction-id=1029944382523

Reply: Success: Database is void of entries.

Step 2 If the above response is received, you can execute the control command to activate the media gateway:

control mgw id=<mgw-id>; target-state=ins; mode=forced;


• mgw id—The unique identifier of the voice port on the subscriber’s MTA, which is created by taking the voice port’s MAC address and stripping out all the hyphens.

• target-state—Use “ins” to indicate “in service” for all activations.

• mode—Use “forced” for all activations.


OL-4495-04


Activating a Subscriber

This control command changes the state of the subscriber to “in service.” Monitor the Cisco BTS 10200 Softswitch transaction queue to verify that the subscriber has been successfully added before trying to activate the subscriber.

To verify that the subscriber has been added and to activate the subscriber, complete the following steps:

Step 1 Execute the following command, using the transaction-id of the command that added the subscriber:

show transaction-queue transaction-id=1029944382524

Reply: Success: Database is void of entries.

Step 2 If the above response is received, execute the control command to activate the subscriber:

control subscriber-termination id=<subscriber id>; target-state=INS; mode=FORCED;


• subscriber-termination id—Unique identifier of the subscriber’s VoIP service, formed by concatenating the subscriber’s identifier from the division billing system and the number of the voice port used for the service on the MTA (for example, 8223130012388228_01).

• target-state—Use “ins” to indicate in service for all activations.

• mode—Use “forced” for all activations.

Changing lnp-trigger to N

After activation for a ported-in number is complete, the Cisco BTS 10200 Softswitch needs to be updated so that calls to this number from MTAs on this switch are routed directly to the subscriber’s MTA, instead of having the switch perform an LNP query and route the call to the CLEC switch, only to have it route the call back to the Cisco BTS 10200. This is accomplished by resetting the lnp-trigger flag to N.

To reset the lnp-trigger flag to N, complete the following steps:




Step 2 Change the lnp-trigger flag to N by entering the following command:

change dn2subscriber office-code-index=<office-code-index of ported TN’s NPA-NXX>;

dn=<XXXX of the ported TN>; lnp-trigger=N;

Setting the lnp-trigger flag to N (No) prevents the initiation of unconditional LNP queries.


OL-4495-04


LNP Call FlowFigure 6-5 shows the processing of a call in which the office code is not one that is normally assigned to the switch. This chart points out the various parameters and flags that must be set to ensure that calls are processed correctly before, during, and after a subscriber’s number is ported-in or ported-out of a switch.

Figure 6-5 Ported-in Call Processing for Originating Calls

The porting-in process is complete when:

• The subscriber’s line is physically connected to the switch.

• The subscriber’s office code is added to the OFFICE-CODE table.

• The subscriber’s number is added to the DN2SUBSCRIBER table.

• The in-call-agent flag is set to Y (ported-in) in the PORTED-OFFICE-CODE table.

• The lnp-trigger flag is set to N in the DN2SUBSCRIBER table.

1040

38

Yes

Office Code is notassigned to switch

IsOffice Code

in Ported OfficeCode table

?

Do LNP query

Is sub indn2subscriber

table?

Is theIn-Call-Agent

flag set?

Check theDestination

table

Is theLNP-trigger

flag set?

Check theStatus field

Do LNP query

Play AnnouncementRelease the call

Terminate toSubscriber

Subscriber Route Ported-out Assigned

No

Yes

No

YesDuringtransition

Aftertransition

No

Perform normalcall processing

No

Yes


OL-4495-04


Porting-out a SubscriberIn some cases, subscribers will want to discontinue their service, but take their telephone number with them to their new service provider. This is similar to the port-in case described previously, where the lnp-trigger is set to Y at the beginning of the porting process to ensure that all calls are routed according to the national LNP databases. This is necessary because the national LNP database has authority on when and where to route calls to a ported number, although the number may still exist in the local DN2SUBSCRIBER table.

When subscribers want to move their service to another service provider and request LNP service, log in to the Cisco BTS 10200 Softswitch as described in the “Establishing a Session” section on page 6-10, and enter the CLI commands as described in the following sections:

• Changing lnp-trigger to Y, page 6-20

• Changing DN Status to Ported-Out, page 6-20

• Deactivating Service, page 6-21

Changing lnp-trigger to YWhen a service order to port out a number has been issued, change the lnp-trigger to Y (Yes) to ensure the routing of calls to the number is done according to the NPAC SMS national LNP databases.

To change the lnp-trigger to Y (Yes), perform the following steps:



The Cisco BTS 10200 returns the office-code-index.

Step 2 Change the lnp-trigger to Y (Yes) by entering the following command:

change dn2subscriber office-code-index=<office-code-index of ported TN’s NPA-NXX>;

dn=<XXXX of the ported TN>; lnp-trigger=y;

Changing the lnp-trigger to Y (Yes) results in calls to this DN initiating an unconditional LNP query.

Leave the status of the DN=ASSIGNED in the DN2SUBSCRIBER table, because initially calls to the DN may have to be routed to the porting-out subscriber’s MTA, based on the results of the LNP queries. Wait until the CLEC reports a Completed state for the transfer before changing the status of the DN.

Changing DN Status to Ported-OutAfter the CLEC reports a Completed state, change the status of the number in the DN2SUBSCRIBER table to “ported-out” by completing the following steps:


show office-code digit-string=<NPA-NXX of the porting TN>;


Step 2Change the status of the DN to ported-out by entering a command similar to the following:

change dn2subscriber office-code-index=<office-code-index of porting TN’s NPA-NXX>;

dn=<XXXX of the porting TN>; status=ported-out; sub-id=null;


OL-4495-04


Deactivating Service

To deactivate the customer’s service, complete the following steps:

Step 1 To change the status of the subscriber’s termination to out of service, enter the control command:

control subscriber-termination target-state=oos; mode=forced; id=<subscriber id>;


• target-state—Use “oos” to indicate out of service for all deactivations.

• mode—Use “forced” for all deactivations.

• subscriber id —Unique identifier of the subscriber’s VoIP service.

Step 2 To deactivate the subscriber's MTA (media gateway), enter the control command:

control mgw id=<mgw-id>; target-state=oos; mode=forced;


• mgw id—The unique identifier of the voice port on the subscriber's MTA, which is created by taking the voice port's MAC address and stripping out all the hyphens.

• target-state—Use “oos” to indicate out of service for all deactivations.

• mode—Use “forced” for all deactivations.

Step 3 To remove the association between the subscriber and the VoIP service ID, enter the delete command:

delete subscriber-service-profile sub-id=<subscriber id>; service-id=1;


• subscriber id—Unique identifier of the subscriber’s VoIP service.

• service-id—Identifies the “bundle” of CLASS features enabled for the subscriber.

Step 4 To remove the subscriber from the Cisco BTS 10200 Softswitch database, enter the delete command:

delete subscriber id=<subscriber-id>;

The only data element specified in this command is:

• subscriber id—Unique identifier of the subscriber’s VoIP service.

Step 5 To remove the VoIP service from the MTA (media gateway), enter the delete command:

delete termination prefix=aaln/; port-start=1; port-end=2; mgw_id=<mgw-id>;

Data elements specified by this command are:

• termination prefix—Use “aaln/” for all subscribers, indicating “analog line”.

• port-start—Use 1 for all subscribers. Ensure that this is consistent with MTA configuration files.

• port-end—Use 2 for all subscribers. Ensure that this is consistent with MTA configuration files.

• mgw-id—The unique identifier of the voice port on the subscriber’s MTA, which is created by taking the voice port’s MAC address and stripping out all the hyphens.

Step 6 To remove the subscriber’s MTA from the Cisco BTS 10200 database, enter the delete command:

delete mgw id=<mgw-id>;

The only data element specified by this command is:

• mgw-id—The unique identifier of the voice port on the subscriber’s MTA, which is created by taking the voice port’s MAC address and stripping out all the hyphens.


OL-4495-04

Chapter 6 Local Number PortabilityLocal Exchange Routing Guide

Local Exchange Routing GuideTable 6-1 provides more detailed information on the contents of the different LERG sections.

Table 6-1 Local Exchange Routing Guide Contents

LERG Section Description

LERG1: Operating Company Names (OCN) and Numbers.

LERG2: Operating Company Contact List.

LERG3: NPA Activity (Relief, splits, overlays).

LERG4: NPAs and Location.

LERG5: LATAs and associated NPAs. Lists RBOC region, LATA, and NPAs within LATA.

LERG6: NPA/NXX information.

Lists NPA/NXX, dates of changes, COC type, OCN, LATA, Home switch CLLI, Ported Indicator, Access Tandem information, Associated Rate Center, Locality Name and State/Province, Line Range.

Useful for constructing, maintaining DN database, Local Calling Areas, Reporting.

LERG6 ATC: NPA/NXX—Access Tandem Code.

LERG6 INS: NPA/NXX—Activity.

LERG7: Switching Entity.

Switch CLLI, dates of changes, LATA, Equipment type, OCN, City/State/Zip, Int'l Dialing Indicator, Point Code Flag, V&H, Feature Group Tandems, SAC (800,500) serving switches, Serving Office flags.

Useful for setting up and maintaining switch tables for routing.

LERG7 INS: Switching Entity Activity.

LERG8: Rate Centers.

Lists Rate Center Identifiers, Type, dates of changes, LATA, V&H (major and minor), NPAs, Localities served. Also establishes limits to boundaries for limited geographic LNP as stated in the RFP.

Useful for setting up and maintaining switch rating tables.

LERG9: Tandem Homing Arrangements.

LERG9 ATC: Tandem Homing Arrangements—Access Tandem Code.

LERG10: Operator services by NPA/NXX.

Lists NPA/NXX, dates of changes, location info, Operator service Codes for each NPA/NXX.

Multiple uses, very helpful in planning for network changes.

LERG11: Operator services by location.

Similar to LERG10, organized a little differently.

LERG12: Location Routing Numbers (LRN).

Lists LRN, LRN type, Switch CLLI, dates of changes, LATA, OCN.

Useful for setting up and maintaining SS7 information on STPs/SCPs.


OL-4495-04


C H A P T E R 7
Maintenance and Administration of System Components
The Cisco BTS 10200 Softswitch provides a user interface for administering and monitoring the following internal system components:

• Call Agent (CA)

• Feature Server (FS)

• Element Management System (EMS)

• Bulk Data Management System (BDMS)

The following topics are discussed in this section:

• Redundant Architecture, page 7-1

• Status and Control States, page 7-2

• Process Restartability, page 7-11

• Host Operating System Time, page 7-11

• Guidelines for Regular System Health Checks, page 7-12

Redundant ArchitectureEach logical component (EMS, BDMS, CA, and FS) is deployed in a dual active/standby configuration, with the two sides running on separate computers (hosts). The active side of each component is backed up by a standby side on the other host. The communication paths among the components are also redundant. The redundant architecture supports the reliability and availability of the entire system. The active and standby sides of each logical component pair operate as follows:

• There is no traffic load sharing between the active and standby sides; the active side performs all of the call processing, and the standby does none.

• Call and feature data from the active side are replicated to the standby side at specific checkpoints of a call (when a call is answered, released, and so forth).

• An automatic internal audit function runs on the standby side of each component—EMS, BDMS, CA, and FS. It checks all the shared memory tables in the components to verify consistency and to check for any corruption. The audit reports any data structure inconsistencies or corruption via alarms and trace messages.


Chapter 7 Maintenance and Administration of System ComponentsStatus and Control States

• Each side maintains a keep-alive channel with the corresponding mate side. The keep-alive process on each side determines if the mate is faulty. If there is a failure on the active side (or if the operator intentionally brings down the active side), the other side becomes active and takes over the traffic load. All stable calls continue to be processed without any loss of calls. There is no service outage, but during a switchover, transient calls can be impacted.

Note H.323 call stability relies on H.323 Annex E functionality at both H.323 endpoints.

When the side that failed is brought back in service, it remains in standby mode and the system runs in normal duplex mode.

• The operator can manually switch (force) either side to become active, which automatically forces the other side into standby mode.

• The system does not remove the logical IP addresses when logical IP addresses are brought down administratively.

Status and Control StatesThis section describes the use of status and control states, and includes the following topics:

• Status States

• Control States

• Status Application Command

• Control Application Command

• Call Agent Status and Control

• Feature Server Status and Control

• Element Management System Status and Control

• Bulk Data Management System Status and Control

• Status System Command

Success and Failure ResponsesOne of the following messages is returned upon the success of a command:

Application instance reconfigured successfullyApplication instance response success already in request configuration

One of the following messages is returned upon the failure of a command:

Application instance mate time-out at change-over requestApplication instance mate refused to change-over when requestApplication instance request invalid configurationApplication instance local time-out at change-over requestApplication instance local change-over failureApplication instance request causes system outageApplication instance in unstable state


OL-4495-04


Status StatesThe operational (status) states of the components are displayed using the status command. Typical examples of the command are:

status element-manager id=EM01;status element-manager id=BDMS01;status call-agent id=CA146;status feature-server=FSPTC235;status feature-server=FSAIN205;

Status states can be in either Normal or Forced mode. Table 7-1 lists status state modes and descriptions.

.Table 7-1 Status State Descriptions

State Description

Note In Release 4.5, the words FORCED and NORMAL are no longer returned in command responses. For example, ACTIVE_NORMAL becomes ACTIVE, STANDBY_NORMAL becomes STANDBY, and so forth.

ACTIVE

ACTIVE-NORMAL

ACTIVE-FORCED

STANDBY

STANDBY-NORMAL

STANDBY-FORCED

The only Cisco BTS 102100 Softswitch states that allow switchover (forced or normal).

Active component is automatically assigned at startup.

Active component was manually assigned by the operator.

Standby component is automatically assigned at startup.

Standby component was manually assigned by the operator.

INIT-NORMAL

INIT-FORCED

Transitional states, produced during startup or switchover. Do not issue a switchover command if a Cisco BTS 10200 Softswitch component is in transitional state.

TRANSITION-TO-ACTIVE-NORMAL

TRANSITION-TO-ACTIVE-FORCED


TRANSITION-TO-STANDBY-NORMAL

TRANSITION-TO-STANDBY-FORCED


N/A Not a valid state.

FAULTY

This state is not supported as of Release 4.5.

Instance is not running, other side is active if it is not faulty. Do not issue a switchover command if a Cisco BTS 10200 Softswitch component is FAULTY.

OOS_FAULTY (Release 4.5)

OOS_ADMIN (Release 4.5)

Component has failed.

Returned when an operator manually takes down a component.


OL-4495-04


Control StatesThe operator can use the control commands to switch the administrative service state (target state, or control state) of each internal component pair—EMS pair, BDMS pair, CA pair and FS pair. Each switching command will take approximately 20 seconds to complete on the system.

Typical examples of the command are:

control element-manager id=EM01; target-state=FORCED-ACTIVE-STANDBY;control element-manager id=BDMS01; target-state=FORCED-ACTIVE-STANDBY;control call-agent id=CA146; target-state=FORCED-STANDBY-ACTIVE;control feature-server=FSPTC235; target-state=NORMAL;control feature-server=FSAIN205; target-state=NORMAL;

Control states can be in either Normal or Forced mode. Table 7-2 lists control state modes and descriptions.

.

One of the following messages is returned upon the success of a control command:

Reconfigured Successfully

Already in this configuration

One of the following messages is returned upon the failure of a control command:

Mate Changeover Timeout

Mate Refused Changeover

If this command is executed it will cause a System Outage

Invalid Configuration

Local Changeover Timeout

Local Changeover Failure

Status Application CommandThe status application command shows the state of any Cisco BTS 10200 Softswitch application (CA, FS, EMS, BDMS), including uptime, side indications and additional qualifying reason information.

Tip The status application command is a CLI command that provides more detail than the status <element-manager, call-agent, feature-server, or bdms> commands, including, for example, time stamps and restart counters. The status application command provides information similar to the nodestat command without using a root command.

Table 7-2 Control States and Descriptions

Control State Description

NORMAL Primary is active and secondary is standby.

FORCED-ACTIVE-STANDBY

Primary has been forced to active and secondary is standby.

FORCED-STANDBY-ACTIVE

Primary has been forced to standby and secondary is active.


OL-4495-04


Command Types Status

Examples status application id=CA146;

status application id=CA146;

status application id=EM01;

status application id=EM01;

Syntax Description

Control Application CommandThe control application command controls the state of an application instance. This command takes the application specified either in service or out of service.

Tip The control application command is a CLI command that provides functionality similar to the platform stop/start commands without using a root command.

Caution Use this command with extreme caution, because it has a significant affect on operation of the host machine.

Command Types Control

Examples control application id=CA146; action=start

control application id=CA146; action=stop

control application id=EM01; action=start

control application id=EM01; action=stop

ID Type of application.

VARCHAR(8): 1–8 ASCII characters. Permitted values are:

CAnnn (or cannn)—CA

EMnn (or emnn)—EMS

BDMSnn (or bdms)—BDMS

FSPTCnnn (or fsptcnnn)—FSPTC

FSAINnnn (or fsainnnn)—FSAIN


OL-4495-04


Syntax Description

Call Agent Status and ControlThis section describes the status and control commands for the Cisco BTS 10200 Softswitch Call Agent.

Status Command

The status command reports the status of a Call Agent.


Examples status call-agent id=CA146;

Reply Example:

Reply: Request was successful.REPLY=CONFIGURATION COMMAND EXECUTED-> status call-agentPRIMARY STATUS -> ACTIVE_NORMALSECONDARY STATUS -> STANDBY_NORMAL

Control Command

The control command puts the Call Agent into a specific mode (state).


Examples control call-agent id=CA146; target-state=forced-standby-active;

control call-agent id=CA146; target-state=forced-active-standby;

control call-agent id=CA146; target-state=normal;

Reply Example:

Request was successfulREPLY=CONFIGURATION COMMAND EXECUTED->Reconfigured successfully.

ID Type of application.

VARCHAR(8): 1–8 ASCII characters. Permitted values are:

CAnnn (or cannn)—CA

EMnn (or emnn)—EMS

BDMSnn (or bdms)—BDMS

FSnnn (or fsnnn)—FS

ACTION Activity to perform. Permitted values are:

START—Start a CA, EMS, BDMS, or FS.

STOP—Stop a CA, EMS, BDMS, or FS.


OL-4495-04


Feature Server Status and ControlThis section describes the status and control commands for the Cisco BTS 10200 Softswitch Feature Server.

Status Command

The status command reports the status of a Feature Server.


Examples status feature-server id=FSAIN205.Cisco.com;

Reply Example:

Request was successful.REPLY=CONFIGURATION COMMAND EXECUTED-> status feature-serverPRIMARY STATUS -> ACTIVE-NORMALSECONDARY STATUS -> STANDBY-NORMAL

Control Command

The control command puts a Feature Server into a specific mode (state).


Examples control feature-server id=FSAIN205.Cisco.com; target-state=normal;

Reply Example:

Request was successfulREPLY=CONFIGURATION COMMAND EXECUTED->control feature-server LOCAL STATUS

Element Management System Status and ControlThis section describes the status and control commands for the Cisco BTS 10200 Softswitch Element Management System (EMS). These commands are specific to the EMS. For Billing commands, see the “Bulk Data Management System Status and Control” section on page 7-8.

Status Command

The status command reports the status of an EMS.



OL-4495-04


Examples status element-manager id=EM01;

Reply Example:

Reply : Success:

ELEMENT MANAGER STATUS IS... ->

APPLICATION INSTANCE -> Element Manager [EM01] PRIMARY STATUS -> ACTIVE_NORMAL SECONDARY STATUS -> FAULTY

EMS MYSQL STATUS IS ... -> Daemon is running!

ORACLE STATUS IS... -> Daemon is running! Control Command

Control Command

The control command puts an EMS into a specific mode (state).


Examples control element-manager id=EM01; target-state=FORCED-ACTIVE-STANDBY;

Reply Example:

Request was successfulREPLY=CONFIGURATION COMMAND EXECUTED->CONTROL EMS LOCAL STATUS

Bulk Data Management System Status and ControlThis section describes the status and control commands for the Cisco BTS 10200 Softswitch Bulk Data Management System (BDMS).

Status Command

The status command reports the status of the BDMS.


Examples status bdms id=BDMS01;

Reply Example:

Reply : Success:BILLING SERVER STATUS IS... -> APPLICATION INSTANCE -> Bulk Data Management Server [BDMS01]PRIMARY STATUS -> ACTIVE_NORMAL


OL-4495-04


SECONDARY STATUS -> STANDBY_NORMAL BILLING MYSQL STATUS IS... -> Dameon is running!

Control Command

The control command puts the BDMS into a specific state (mode).


Examples control bdms id=BDMS01; target-state=FORCED-ACTIVE-STANDBY;

Reply Example:

Reply : Success: APPLICATION INSTANCE -> Bulk Data Management Server [BDMS01]REASON -> CONFIGURATION COMMAND EXECUTED->CONTROL BDMS LOCAL STATUS System

Additional BDMS Status and Control Examples

Use the following steps to verify the status of the BDMS and switch the administrative states.

Step 1 Verify the status of the BDMS.

status bdms; id=BDMS01;

BILLING SERVER STATUS IS... ->

APPLICATION INSTANCE -> Bulk Data Management Server [BDMS01]PRIMARY STATUS -> ACTIVE_NORMALSECONDARY STATUS -> FAULTY

BILLING ORACLE STATUS IS... -> Daemon is running!

Reply : Success:

Step 2 Modify the status of the BDMS.

control bdms id=BDMS01; target-state=FORCED_ACTIVE_STANDBY

Reply : Success:

APPLICATION INSTANCE -> Bulk Data Management Server [BDMS01]REASON -> Application instance reconfigured successfully


status bdms; id=BDMS01;

Reply : Success:

REPLY=CONFIGURATION COMMAND EXECUTED -> status billing_serverPRIMARY STATUS -> ACTIVE_FORCED


OL-4495-04


SECONDARY STATUS -> STANDBY_FORCED


control bdms id=BDMS01; target-state=FORCED_STANDBY_ACTIVE

Reply : Request was successful.

REPLY=CONFIGURATION COMMAND EXECUTED -> Reconfigured Successfully


status bdms id=BDMS01;


REPLY=CONFIGURATION COMMAND EXECUTED -> status billing_serverPRIMARY STATUS -> STANDBY_FORCEDSECONDARY STATUS -> ACTIVE_FORCED


control bdms id=BDMS01; target-state=FORCED-ACTIVE-STANDBY;


REPLY=CONFIGURATION COMMAND EXECUTED -> Reconfigured Successfully

Status System CommandThe status system command returns the status of all applicable components of the system.


Examples status system;

Reply Example:

Checking Call Agent status ... Checking Feature Server status ... Checking Billing Server status ... Checking Billing Oracle status ... Checking Element Manager status ... Checking EMS MySQL status ... Checking ORACLE status ...

CALL AGENT STATUS IS... ->

APPLICATION INSTANCE -> Call Agent [CA146]PRIMARY STATUS -> STANDBY_NORMALSECONDARY STATUS -> ACTIVE_NORMAL

FEATURE SERVER STATUS IS... ->

APPLICATION INSTANCE -> Feature Server [FSPTC235]


OL-4495-04

Chapter 7 Maintenance and Administration of System ComponentsProcess Restartability

PRIMARY STATUS -> STANDBY_NORMALSECONDARY STATUS -> ACTIVE_NORMAL

FEATURE SERVER STATUS IS... ->

APPLICATION INSTANCE -> Feature Server [FSAIN205]PRIMARY STATUS -> STANDBY_NORMALSECONDARY STATUS -> ACTIVE_NORMAL

BILLING SERVER STATUS IS... ->

APPLICATION INSTANCE -> Bulk Data Management Server [BDMS01]PRIMARY STATUS -> ACTIVE_NORMALSECONDARY STATUS -> STANDBY_NORMAL

BILLING ORACLE STATUS IS... -> Daemon is running!

ELEMENT MANAGER STATUS IS... ->

APPLICATION INSTANCE -> Element Manager [EM01]PRIMARY STATUS -> STANDBY_NORMALSECONDARY STATUS -> ACTIVE_NORMAL

EMS MYSQL STATUS IS ... -> Daemon is running!

ORACLE STATUS IS... -> Daemon is running!

Reply : Success:

Process RestartabilityWhen a Cisco BTS 10200 Softswitch process exits due to an internal error (such as SIGSEGV on UNIX) or is terminated by the platform, the system automatically restarts the process that shut down. Restarting the process is a preferred alternative to switching over to the mate, because the restart preserves stable calls and also attempts to preserve transient calls. When a process is restarted, the process audits information such as resource states and attempts to repair inconsistencies. If a process experiences a high failure rate (even after repeated restarts), the system will switch over to the mate.

Host Operating System TimeThe Solaris OS obtains the system time automatically through network time protocol (NTP) services.

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


OL-4495-04

Chapter 7 Maintenance and Administration of System ComponentsGuidelines for Regular System Health Checks

Guidelines for Regular System Health ChecksThis section describes system health checks that the operator should perform regularly on the Cisco BTS 10200 Softswitch. Cisco recommends that you perform these checks on the schedule described in Table 7-3, or more frequently if recommended by your system administrator.

Read the Automatic System Health ReportThe system provides a provisionable mechanism to gather data and create a report on overall health. This process automatically gathers data about selected events, such as alarms, statistics, and platform switchovers (on the EMS, BDMS, CA, and FS). The service provider can use the data to detect operational problems or system performance issues, such as hardware failures or traffic congestion, and take action proactively to correct the issue. The report can be created on a regularly scheduled basis, for example, every 24 hours at midnight. The reports are placed in a directory viewable with a Web browser.

Use the following commands to configure, schedule, and view system-health reports.

Step 1 Use the following CLI command to display the report(s) that are scheduled on your system:

Note The system health report is automatically scheduled by default for any new system.

show scheduled-command verb=report; noun=system_health

Note Be sure to enter the noun as system_health (not system-health).

Table 7-3 Regular System Health Checks

# Maintenance Item Frequency

1 Read the Automatic System Health Report Daily

2 Check System Clocks Daily

3 Check Billing Server and Local Billing Directory Daily

4 Check Traffic Measurements Daily

5 Check Event and Alarm Reports Daily

6 Perform Database Backup Daily

7 Check OS Log Daily

8 Check Mirroring On the Disk Weekly

9 Audit Database Monthly

10 Backup Software Image Monthly

11 Check DNS Server Quarterly

12 Run Diagnostic On Trunk Group Quarterly

13 Run Diagnostic On Subscriber Terminations Quarterly

14 Check Power Supply Quarterly

15 Clean Filters Quarterly


OL-4495-04


The system response is similar to the following example.

ID=881958957176113006VERB=reportNOUN=system_healthSTART_TIME=2/13/2004 1:0:0NEXT_START_DAY=13USER_NAME=optiuserEXECUTION_COUNTER=0RECURRENCE=DAILY


Reply : Success: Entries 1-2 of 2 returned.

Step 2 To show a single scheduled report by ID number, enter the following command:

show scheduled-command id=881958666704177006


Reply : Success: Entry 1 of 1 returned.

Step 3 To add a scheduled system-health command, use a command similar to the following example:

add scheduled-command verb=report; noun=system_health; start-time=2003-10-01 12:22:22; recurrence=DAILY; keys=period; key-values=<1 ... 720>;

where:

– start-time specifies the time the system should create the report, yyyy-mm-dd hh:mm:ss.

– recurrence specifies how frequently to run a report. Valid values are none (one time only), daily, weekly, and monthly.

– keys=period; key-values=<1 ... 720>; specifies the amount of time to collect (from the current time back) in hours. If this token is not specified, then the system uses the default of 24 (the last 24 hours worth of data).

Step 4 To create a report immediately, use the following command:

report system-health period=<1 ... 720>;

Step 5 To reschedule the system-health command at another time, change the recurrence, or change the collection period, use a change command similar to the following example:

change scheduled-command id=881958666704177006; start-time=2003-10-01 14:14:14; recurrence=DAILY; keys=period; key-values=24;


OL-4495-04


Note The ID number is required to change or delete an existing scheduled system-health report.

Step 6 To delete a scheduled system-health command, use a delete command similar to the following example:

delete scheduled-command id=881958666704177006;

Step 7 Using a Web browser, view the desired report(s) at the URL:

http://<active EMS hostname>:10200/report/system_health

Following is an example of a system-health report:

System Health Report created on 02/12/2004 10:28:51 by the Cisco ReportBuilder.

System Health Report collected since Wed Feb 11 10:28:49 CST 2004System Health Report Counters Count MTP Congestion Indications DPC Congested 0 Signaling Error Messages H323: H323 Message Parsing error 0 H323: H323 Message encoding error 0 SIP: Cannot receive SIP messages from network 0 SIP: Failed to allocate SIP Control Block 0 SIP: Failed to send complete SIP message 0 SIP: Timeout on IP Address 0 Link Failures H323: Error while binding to socket 0 H323: Reached maximum socket limit 0 SIP: Socket Failure 0 SS7: ISDN Calls lost due to D-channel down for period of time 0 SS7: ISDN Unable to establish D-channel 0 SS7: ISDN Unable to restore D-channel due to failed communication 0 Number of Point Code Failures DPC is not available 0 Platform Statistics id node state qualifier side reason last_start rdm_state version restarts FSAIN205 secca16 ACTIVE NORMAL SECONDARY 2004/02/12-09:58:25 Replication Operational Status: REPLICATING;RDM Mode: SEND;RDM TCP Conn. Status: CONNECTED;TCP Address: CONNECTED TO 10.10.121.174 PORT 5205 1 FSPTC235 secca16 ACTIVE NORMAL SECONDARY 2004/02/12-09:59:24 Replication Operational Status: REPLICATING;RDM Mode: SEND;RDM TCP Conn. Status: CONNECTED;TCP Address: CONNECTED TO 10.10.120.174 PORT 5235 1 CA146 secca16 ACTIVE NORMAL SECONDARY 2004/02/12-09:58:05 Replication Operational Status: NOT REPLICATING;RDM Mode: IDLE;RDM TCP Conn. Status: NOT CONNECTED;TCP Address: N/A 1 FSAIN205 prica16 STANDBY NORMAL PRIMARY 2004/02/12-10:00:01 Replication Operational Status: REPLICATING;RDM Mode: RECEIVE;RDM TCP Conn. Status: CONNECTED;TCP Address: CONNECTION ACCEPTED ON PORT 5205 1 FSPTC235 prica16 STANDBY NORMAL PRIMARY 2004/02/12-10:01:50 Replication Operational Status: REPLICATING;RDM Mode: RECEIVE;RDM TCP Conn. Status: CONNECTED;TCP Address: CONNECTION ACCEPTED ON PORT 5235 1 CA146 prica16 FAULTY NORMAL PRIMARY Outgoing HB period 6595ms exceeded Max. HB period 2500ms 2004/02/12-09:59:30 Replication Operational Status: NOT REPLICATING;RDM Mode: IDLE;RDM TCP Conn. Status: NOT CONNECTED;TCP Address: N/A 1 ORACLE priems16 ACTIVE PRIMARY 1 MYSQL priems16 ACTIVE PRIMARY 1 EM01 priems16 ACTIVE NORMAL PRIMARY 2004/02/12-10:28:37 Replication Operational Status: DB COPY;RDM Mode: SEND;RDM TCP Conn. Status: CONNECTED;TCP Address: CONNECTED TO 10.10.122.73 PORT 6001 1 EM01 secems16 STANDBY NORMAL SECONDARY 2004/02/12-10:28:44 Replication Operational Status: REPLICATING;RDM Mode: RECEIVE;RDM TCP Conn. Status: CONNECTED;TCP Address: CONNECTION ACCEPTED ON PORT 6001 1


OL-4495-04


Trunk Circuit Usage Summary NODENAME TRKGRP_TYPE TRKGRP_ID TRKGRP_INCOM_ATTMP TRKGRP_OUTG_ATTMP TRKGRP_OUTBOUND_FAIL TRKGRP_TOTAL_OVERFLOW TRKGRP_INCOM_BUSY_TRK TRKGRP_OUTG_BUSY_TRK TRKGRP_TOTAL_OOS_TRK TRKGRP_INCOM_USAGE TRKGRP_OUTG_USAGE TRKGRP_TOTAL_USAGE TRKGRP_AVERAGE_USAGE Disk Usage History HISTORY Not Available Memory Usage A process exceeds 70% of CPU Usage 0 EMS REPORT_TYPE_DATABASE tablespace is out of free space 0 Memory is 95% exhausted and the swap is 50 consumed 0 Table Size Exceeds Critical Threshhold 0 Table Size Exceeds Major Threshhold 0 Table Size Exceeds Minor Threshhold 0 The CPU usage is over 90% busy 0 The load average exceeds 3 for at least 5 minutes 0 URGENT: EMS REPORT_TYPE_DATABASE archive log directory is getting full! 0 Current Active Alarms ID TYPE NUMBER DESCRIPTION SEVERITY ALARM_STATUS TIMESTAMP ORIGIN THREAD COMPONENT_ID DW1 DW2 DW3 DW4 DW5 DW6 DW7 DW8 1 MAINTENANCE 20 KAM: Lost KAM Connection to Mate MAJOR ON 20040212102847 PMG.PRIMARY.BDMS1 PMG.PRIMARY BDMS1 UNKNOWN 2 MAINTENANCE 4 KAM: Mate Side has become Faulty MAJOR ON 20040212102847 PMG.PRIMARY.BDMS1 PMG.PRIMARY BDMS1 STARTUP FAULTY LOST KAM CONNECTION SOFTWARE PROBLEM SUCCESSFUL Call Success/Failures Rates NODENAME CALLP_ORIG_ATTMP CALLP_TERM_ATTMP CALLP_ORIG_FAIL CALLP_TERM_FAIL CALLP_CALL_SUCC CALLP_CALL_ABAND Number of Critical Events Issued Critical Audit Events 0 Critical Billing Events 0 Critical Call Processing Events 0 Critical Config Events 0 Critical Database Events 0 Critical Maintenance Events 16 Critical OSS Events 0 Critical Security Events 0 Critical Signaling Events 0 Critical Stats Events 0 Critical System Events 0 DB Usage Billing Partition Disk Usage Critical Threshold Exceeded 0 Billing Partition Disk Usage Major Threshold Exceeded 0 Billing Partition Disk Usage Minor Threshold Exceeded 0 Billing Partition Disk Usage Within Normal Range 0


OL-4495-04


Check System ClocksPerform these steps to check system clocks on all four host machines. System clocks must be accurate to a tolerance of 2 seconds.

Note that the Solaris OS obtains the system time automatically through network time protocol (NTP) services. This procedure checks the system clock, but does not attempt to change it. Do not change the system clock.

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

Step 1 Log into primary and secondary EMS as root.

Step 2 Issue the date command:

<hostname># date

Step 3 Check the response on both boxes and ensure that time does not deviate more than +/- 2 seconds.

a. Ensure the day of week is correct

b. Ensure the day of month is correct

c. Ensure the month of year is correct

d. Ensure the year is correct

e. Ensure the Timezone is correct

Step 4 Log into primary and secondary CA as root.

Step 5 Issue the date command:

<hostname># date

Step 6 Check the response on both boxes and ensure that time does not deviate more than +/- 2 seconds.

a. Ensure the day of week is correct

b. Ensure the day of month is correct

c. Ensure the month of year is correct

d. Ensure the year is correct

e. Ensure the Timezone is correct

SAMPLETue Dec 16 09:49:07 MST 2003

[Day of week] [Month][Day of Month][Hour][Minutes] [Seconds] [Timezone] [Year]


OL-4495-04


Check Billing Server and Local Billing DirectoryPerform these steps to ensure that the billing server is receiving call detail blocks (CDBs) from the Cisco BTS 10200 Softswitch, and that the billing directory is not full.

Step 1 Log into CLI and execute the following command:

CLI>show billing-acct-addr

BILLING_DIRECTORY = /opt/bms/ftp/billing

BILLING_FILE_PREFIX = test-

BILLING_SERVER_DIRECTORY = /bts

BILLING_SERVER_ADDR = your.billingserver.address

USER_NAME = cisco

POLLING_INTERVAL = 2

Step 2 From the command issued in Step 1, observe the polling interval.

Step 3 Log into the billing server and ensure that billing files are received every XXminutes,where XX = polling_interval from billing-acct-addr table.

Step 4 Log into primary/secondary EMS and execute the following command:

<hostname>#df –k

Step 5 Observe the system display from the command in Step 4, and ensure the /opt directory is not more than 70% full. A sample display is shown below.

SAMPLE

Note The system generates maintenance alarms if a disk partition exceeds certain levels.A partition that is 70 percent consumed generates a minor alarm (MAINTENANCE #90).A partition that is 80 percent consumed generates a major alarm (MAINTENANCE #66).A partition that is 90 percent consumed generates a critical alarm (MAINTENANCE #65).

Filesystem kbytes used avail capacity Mounted on

/dev/md/dsk/d2 1488787 1074331 354905 76% /

/proc 0 0 0 0% /proc

fd 0 0 0 0% /dev/fd

mnttab 0 0 0 0% /etc/mnttab

/dev/md/dsk/d19 481316 84617 348568 20% /var

swap 4126808 16 4126792 1% /var/run

swap 4747640 620848 4126792 14% /tmp

/dev/md/dsk/d20 30690616 8912701 18708854 33% /opt


OL-4495-04


Step 6 If the /opt directory is more than 70% full, take appropriate action to remove directories and files that are no longer needed. The following steps are intended as a guide, to be used by a system administrator or designee familiar with UNIX commands and file structures on the Cisco BTS 10200 Softswitch. If you need assistance, contact Cisco TAC.

a. Remove scripting files and other user-generated files that are no longer needed.

b. Remove old files in the backup directory that are no longer needed.

<hostname># \rm -rf /opt/Build<hostname># \rm -rf /opt/8_rec<hostname># \rm -rf /opt/.upgrade

Check Traffic MeasurementsSee Chapter 10, “Traffic Measurements,” for the applicable procedures and specifications.

Check Event and Alarm ReportsSee Chapter 18, “Managing Event Message and Alarm Logs,” for the applicable procedures and specifications.

Perform Database BackupBack up your databse daily.

Check OS LogPerform these steps to check for any errors or warnings in the OS logs for all four host machines.

Step 1 Login as root.

Step 2 Enter the dmesg command to obtain a report of system messages.

Note This report typically contains recent messages such as memory hits, disk errors and frequent process restarts.

Example of system response:

Feb 11 12:39:03 priems33 last message repeated 5 timesFeb 11 12:58:41 priems33 ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:03:ba:2d:89:19' trying to be our address 010.089.224.249!Feb 11 12:58:41 priems33 last message repeated 1 timeFeb 11 13:18:35 priems33 ip: [ID 903730 kern.warning] WARNING: IP: Hardware address '00:03:ba:2d:89:19' trying to be our address 010.089.224.249!Feb 11 13:20:26 priems33 last message repeated 5 timesFeb 15 03:10:01 priems33 syslogd: going down on signal 15

Step 3 For additional history, edit the /var/adm/messages file and locate any errors or warnings.


OL-4495-04


Step 4 Repeat for the other host machines.

Check Mirroring On the DiskPerform these steps to check the mirroring on the disk for all four host machines.

CA/FS Side A

Step 1 Log in as root to CA/FS Side A using telnet.

Step 2 Enter the following command:

<hostname># metastat | grep c0

Step 3 Verify the return result is identical to the table listed below:

c0t0d0s6 0 No Okay

c0t1d0s6 0 No Okay

c0t0d0s1 0 No Okay

c0t1d0s1 0 No Okay

c0t0d0s5 0 No Okay

c0t1d0s5 0 No Okay

c0t0d0s7 0 No Okay

c0t1d0s7 0 No Okay

c0t0d0s0 0 No Okay

c0t1d0s0 0 No Okay

c0t0d0s3 0 No Okay

c0t1d0s3 0 No Okay

Step 4 If the results differ from what is shown in Step 3, use the following steps to synchronize and verify the disk mirroring.

a. Enter the following commands to synchronize the disk mirroring:

<hostname># cd /opt/setup

<hostname># sync_mirror

This takes about 30 minutes.

b. Enter the following command to check the disk mirroring:


c. Verify the results again as in Step 3.


OL-4495-04


Caution If the problem persists, stop! Contact Cisco TAC.

CA/FS Side B

Step 1 Log in as root to CA/FS Side B using telnet.




c0t0d0s6 0 No Okay

c0t1d0s6 0 No Okay

c0t0d0s1 0 No Okay

c0t1d0s1 0 No Okay

c0t0d0s5 0 No Okay

c0t1d0s5 0 No Okay

c0t0d0s7 0 No Okay

c0t1d0s7 0 No Okay

c0t0d0s0 0 No Okay

c0t1d0s0 0 No Okay

c0t0d0s3 0 No Okay

c0t1d0s3 0 No Okay











OL-4495-04


EMS Side A

Step 1 Log in as root to EMS Side A using telnet.




c0t0d0s6 0 No Okay

c0t1d0s6 0 No Okay

c0t0d0s1 0 No Okay

c0t1d0s1 0 No Okay

c0t0d0s5 0 No Okay

c0t1d0s5 0 No Okay

c0t0d0s7 0 No Okay

c0t1d0s7 0 No Okay

c0t0d0s0 0 No Okay

c0t1d0s0 0 No Okay

c0t0d0s3 0 No Okay

c0t1d0s3 0 No Okay










EMS Side B

Step 1 Log in as root to EMS Side B using telnet.



OL-4495-04




c0t0d0s6 0 No Okay

c0t1d0s6 0 No Okay

c0t0d0s1 0 No Okay

c0t1d0s1 0 No Okay

c0t0d0s5 0 No Okay

c0t1d0s5 0 No Okay

c0t0d0s7 0 No Okay

c0t1d0s7 0 No Okay

c0t0d0s0 0 No Okay

c0t1d0s0 0 No Okay

c0t0d0s3 0 No Okay

c0t1d0s3 0 No Okay










Audit DatabaseSee Chapter 11, “Audit Database and Table Name,” for the applicable procedures and specifications.

Backup Software ImageThis section describes how to backup the software image. The procedure consists of the following tasks:

• Task 1: Ensure Side A System is ACTIVE

• Task 2: Perform a Full Database Audit


OL-4495-04


• Task 3: Perform Shared Memory Integrity Check

• Task 4: Perform Flash Archive on EMS Side B

• Task 5: Perform Flash Archive on CA/FS Side B

• Task 6: Switch Activity from Side A to Side B

• Task 7: Perform Flash Archive on EMS Side A

• Task 8: Perform Flash Archive on CA/FS Side A

• Task 9: Release Forced Switch

Task 1: Ensure Side A System is ACTIVE

In this task, you will ensure that the EMS Side A applications are active.

Step 1 Log in as root to ACTIVE EMS

Step 2 Log in as CLI user

Step 3 CLI>control call-agent id=CAxxx; target-state=forced-active-standby; <Return>

Step 4 CLI>control feature-server id=FSAINyyy; target-state=forced-active-standby; <Return>

Step 5 CLI>control feature-server id=FSPTCzzz; target-state=forced-active-standby; <Return>

Step 6 CLI>control bdms id=BDMS01; target-state=forced-active-standby; <Return>

Step 7 CLI>control element-manager id=EM01; target-state=forced-active-standby; <Return>

Step 8 CLI>status system; <Return>

Verify CAxxx on CA/FS Side A is in forced ACTIVE state.

Verify FSAINyyy on CA/FS Side A is in forced ACTIVE state.

Verify FSPTCzzz on CA/FS Side A is in forced ACTIVE state.

Verify BDMS01 on EMS Side A is in forced ACTIVE state.

Verify EM01 on EMS Side A is in forced ACTIVE state.

Verify Oracle DB is in service

Step 6 CLI>exit <Return>

Task 2: Perform a Full Database Audit

In this task, you will go to EMS Side A and perform a full database audit and correct errors, if there are any. Contact Cisco TAC if errors need to be fixed.

Step 1 Log in as CLI user on EMS Side A

Step 2 CLI>audit database type=full; <Return>

Step 3 Check the audit report and verify there is no discrepancy or errors found. If errors are found, try to correct the errors. If you are unable to make the correction, contact Cisco TAC.

Task 3: Perform Shared Memory Integrity Check

In this task, you will perform shared memory integrity check to detect any potential data problems.


OL-4495-04


From CA/FS Side A

Step 1 Log in as root

Step 2 <hostname># cd /opt/OptiCall/CAxxx/bin <Return>

Step 3 <hostname># ca_tiat data <Return>

Step 4 Press “Enter” to continue

The result should be identical to the following:

All tables are OK.

For detail, see ca_tiat.out

If the result does NOT show “All tables are OK”, Stop! Contact Cisco TAC.

Step 5 <hostname># cd /opt/OptiCall/FSPTCzzz/bin <Return>

Step 6 <hostname># potsctx_tiat data <Return>



All tables are OK.

For detail, see potsctx_tiat.out


Step 8 <hostname>#cd /opt/OptiCall/FSAINyyy/bin <Return>

Step 9 <hostname>#ain_tiat data <Return>



All tables are OK.

For detail, see ain_tiat.out


From CA/FS Side B


Step 2 <hostname>#cd /opt/OptiCall/CAxxx/bin <Return>

Step 3 <hostname>#ca_tiat data <Return>



All tables are OK.

For detail, see ca_tiat.out


Step 5 <hostname>#cd /opt/OptiCall/FSPTCzzz/bin <Return>

Step 6 <hostname>#potsctx_tiat data <Return>




OL-4495-04


All tables are OK.

For detail, see potsctx_tiat.out


Step 8 <hostname>#cd /opt/OptiCall/FSAINyyy/bin <Return>

Step 9 <hostname>#ain_tiat data <Return>



All tables are OK.

For detail, see ain_tiat.out


Task 4: Perform Flash Archive on EMS Side B

In this task, you will perform a flash archive on EMS Side B to save a copy of OS and applications to a remote server. This process takes about 1 hour.

Note Perform Task 4: Perform Flash Archive on EMS Side B and Task 5: Perform Flash Archive on CA/FS Side B in parallel.

From EMS Side BStep 1 Log in as root

Step 2 <hostname>#/etc/rc2.d/S75cron stop <Return>

Step 3 <hostname>#ps -ef | grep cron <Return>

Verify no result is returned, which means cron daemon is no longer running.

Step 4 <hostname>#cd /etc/rc3.d <Return>

Step 5 <hostname>#mv S99platform _S99platform <Return>

Step 6 <hostname>#platform stop all <Return>

Step 7 <hostname>#nodestat <Return>

Verify applications are out of service.

Step 8 <hostname>#\rm –rf /opt/Build <Return>

Step 9 <hostname>#\rm –rf /opt/8_rec <Return>

Step 10 <hostname>#\rm –rf /opt/.upgrade <Return>

Step 11 Remove all directories and files that are no longer needed such as core files, patch directories.

Step 12 <hostname>#mv /bin/date /bin/date.orig <Return>

Step 13 <hostname>#mv /bin/.date /bin/date <Return>

Step 14 <hostname>#tar –cvf - /opt/* | gzip –c > /opt/<hostname_release>.tar.gz <Return>

Where: hostname_release is the tar file name.

Example: tar –cvf - /opt/* | gzip –c > /opt/secems10_4.1V00.tar.gz

Step 15 <hostname>#flarcreate -n <archive name> -x /opt -c /opt/<file name> <Return>

Where: archive name is the archive identification.


OL-4495-04


Example: flarcreate -n CCPU-EMS –x /opt -c /opt/secems10_4.1V00.archive

Step 16 FTP the archive to an NFS server to be used later.

<hostname>#cd /opt <Return>

<hostname>#ftp <nfs server name> <Return>

ftp>bin <Return>

ftp>cd <target directory> <Return>

ftp>put <archive file name> <Return>

ftp>put <opt tar file name> <Return>

ftp>bye <Return>

Step 17 <hostname>#mv /bin/date /bin/.date <Return>

Step 18 <hostname>#mv /bin/date.orig /bin/date <Return>

Step 19 <hostname>#/etc/rc2.d/S75cron start <Return>


Verify cron daemon is running.


Step 22 <hostname>#mv _S99platform S99platform <Return>

Step 23 <hostname>#platform start <Return>


Verify EM01 is in forced STANDBY.

Verify BDMS01 is in forced STANDBY.

Verify Oracle and Billing DB are in service.

Task 5: Perform Flash Archive on CA/FS Side B

In this task, you will perform a flash archive on CA/FS Side B to save a copy of OS and applications to a remote server. This process takes about 1 hour.

Note Perform Task 4: Perform Flash Archive on EMS Side B and Task 5: Perform Flash Archive on CA/FS Side B in parallel.

From CA/FS Side BStep 1 Log in as root



Verify no result is returned, which means cron daemon is no longer running



Step 6 (Not used)

Step 7 <hostname># platform stop all <Return>



OL-4495-04











Example: tar –cvf - /opt/* | gzip –c > /opt/secca10_4.1V00.tar.gz



Example: flarcreate -n CCPU-CA –x /opt -c /opt/secca10_4.1V00.archive




ftp>bin <Return>




ftp>bye <Return>










Verify CAxxx is in forced STANDBY.

Verify FSAINyyy is in forced STANDBY.

Verify FSPTCzzz is in forced STANDBY.

Task 6: Switch Activity from Side A to Side B

In this task, you will switch activity from Side A to Side B.

From EMS Side AStep 1 Log in as CLI user


OL-4495-04


Step 2 CLI>control call-agent id=CAxxx; target-state=forced-standby-active; <Return>

Step 3 CLI>control feature-server id=FSAINyyy; target-state=forced-standby-active; <Return>

Step 4 CLI>control feature-server id=FSPTCzzz; target-state=forced-standby-active; <Return>

Step 5 CLI>control bdms id=BDMS01; target-state=forced-standby-active; <Return>

Step 6 CLI>control element-manager id=EM01; target-state=forced-standby-active; <Return>

Step 7 CLI session will terminate when EM01 switchover is successful.

Task 7: Perform Flash Archive on EMS Side A

In this task, you will perform a flash archive on EMS Side A to save a copy of the OS and applications to a remote server. This process takes about 1 hour.

Note Perform Task 7: Perform Flash Archive on EMS Side A and Task 8: Perform Flash Archive on CA/FS Side A in parallel.

From EMS Side AStep 1 Log in as root



Verify no result is returned, which means cron daemon is no longer running.














Example: tar –cvf - /opt/* | gzip –c > /opt/priems10_4.1V00.tar.gz



Example: flarcreate -n CCPU-EMS –x /opt -c /opt/priems10_4.1V00.archive





OL-4495-04


ftp>bin <Return>




ftp>bye <Return>










Verify EM01 is in forced STANDBY.

Verify BDMS01 is in forced STANDBY.

Verify Oracle and Billing DB are in service.

Task 8: Perform Flash Archive on CA/FS Side A

In this task, you will perform flash archive on CA/FS Side A to save a copy of OS and applications to a remote server. This process takes about 1 hour.

Note Perform Task 7: Perform Flash Archive on EMS Side A and Task 8: Perform Flash Archive on CA/FS Side A in parallel.

From CA/FS Side AStep 1 Log in as root



Verify no result is returned, which means cron daemon is no longer running



Step 6 (Not used)








OL-4495-04







Example: tar –cvf - /opt/* | gzip –c > /opt/prica10_4.1V00.tar.gz



Example: flarcreate -n CCPU-CA –x /opt -c /opt/prica10_4.1V00.archive




ftp>bin <Return>




ftp>bye <Return>










Verify CAxxx is in forced STANDBY.

Verify FSAINyyy is in forced STANDBY.

Verify FSPTCzzz is in forced STANDBY.

Task 9: Release Forced Switch

In this task, you will release the forced switch.

From EMS Side BStep 1 Log in as CLI user

Step 2 CLI>control call-agent id=CAxxx; target-state=forced-active-standby; <Return>

Step 3 CLI>control feature-server id=FSPTCyyy; target-state=forced-active-standby; <Return>

Step 4 CLI>control feature-server id=FSAINzzz; target-state=forced-active-standby; <Return>


OL-4495-04


Step 5 CLI>control bdms id=BDMS01; target-state =forced-active-standby; <Return>

Step 6 CLI>control element-manager id=EM01; target-state=forced-active-standby; <Return>

Step 7 CLI session will terminate when the EM01 switchover is successful.

From EMS Side AStep 1 Log in as CLI user

Step 2 CLI>control call-agent id=CAxxx; target-state=normal; <Return>

Step 3 CLI>control feature-server id=FSPTCyyy; target-state=normal; <Return>

Step 4 CLI>control feature-server id=FSAINzzz; target-state=normal; <Return>

Step 5 CLI>control bdms id=BDMS01; target-state =normal; <Return>

Step 6 CLI>control element-manager id=EM01; target-state=normal; <Return>

Step 7 CLI>exit <Return>

This completes the flash archive process.

Check DNS ServerPerform these steps to check the DNS server.

Step 1 Login as root on the Primary CA.

Step 2 Execute “more /etc/resolv.conf” and look for “nameserver <ip address” line.

Step 3 Execute “nslookup” <hit return”. This will default to the first DNS server.

Step 4 Enter any known good gateway name and hit return.

Step 5 An ip address associates to that gateway should return.

Step 6 At the prompt “>”, execute “server <second dns server ip>” then repeat Step 4.

Step 7 Enter “exit” to quit.

Step 8 Repeat Step 1 through Step 7 for all other nodes.

Run Diagnostic On Trunk GroupSee Chapter 8, “Maintenance and Diagnostics for External Resources” for the applicable procedures and specifications.

Run Diagnostic On Subscriber TerminationsSee Chapter 8, “Maintenance and Diagnostics for External Resources” for the applicable procedures and specifications.


OL-4495-04


Check Power SupplyRefer to the equipment manufacturer documentation for specifications, and procedures.

Clean FiltersCisco recommends that you clean all filters frequently to maintain proper air flow and avoid possible overheating of the equipment. The filter should be in front of the unit.

Refer to the equipment manufacturer documentation for part numbers and procedures.


OL-4495-04


C H A P T E R 8
Maintenance and Diagnostics for External Resources
This chapter describes the administration, diagnostic, and maintenance (ADM) commands for external resources accessed by the Cisco BTS 10200 Softswitch. These include, for example, status and control commands. The following topics are covered in this chapter:

• Service States—Overview

• Status, Control, and Administrative Commands

• Diagnostic Tests

• Command Responses

• Status Update Processor

Note This chapter explains how to perform maintenance and diagnostics on external resources that have already been entered into the database. The procedures for entering these resources into the database are provided in the Cisco BTS 10200 Softswitch Provisioning Guide. For example, refer to Chapter 11, “SS7 Provisioning”, in the Cisco BTS 10200 Softswitch Provisioning Guide for the procedure to add SS7 resources.

Service States—OverviewADM commands control or show the status of an external resource. The Cisco BTS 10200 Softswitch monitors and administers resource states, and accesses the following external resources:

• Aggregation routers

• Media gateways (MGWs), including the following gateway types:

– Residential gateways (RGWs)

– Trunking gateways (TGWs)

• Trunk groups (TGs)

• Trunks

• Subscriber terminations

The following resources have dependencies:

• Allowed subscriber states depend upon the current RGW or IAD state.


Chapter 8 Maintenance and Diagnostics for External ResourcesStatus, Control, and Administrative Commands

• Allowed trunk states for ISDN depend upon the current TG state, which in turn depends upon the current TGW state.

• Allowed trunk states depend upon the TGW.

There are two types of service states for external resources:

• Administrative—The state that the Cisco BTS 10200 Softswitch operator has provisioned for the link to that resource

• Operational—The physical condition of the link to the resource (or the physical condition of the resource)

These two types of service states are independent of each other. This is illustrated with the following example:

A Cisco BTS 10200 Softswitch operator executes the control command to place an MGW connection in service. The administrative state is now “In Service” (ADMIN_INS). However, the link between the Softswitch and the MGW might be out (cut, damaged, or placed out of service by the owner/operator of the MGW) or the MGW itself might be physically removed or placed out of service. Thus, the operational state of the MGW link is MGW_STATUS_DOWN. A status report of the MGW lists both the administrative state and operational state of the link to the MGW.

Status, Control, and Administrative CommandsThis section explains how to use status, control, and other administrative commands applicable to external resources, including:

• SIP Phone Address of Record and Registered Contact

• Aggregation Status

• Destination Point Code

• H.323 Gateway

• ISDN Switchover

• Media Gateway

• Signaling Gateway Process

• Stream Control Transmission Protocol Association

• Subscriber Termination

• Subsystem

• Trunk Group

• Trunk Termination


OL-4495-04


SIP Phone Address of Record and Registered Contact This section describes the status and control commands related to SIP phone contact information.

Note The system automatically creates an Address of Record (AOR) to subscriber (aor2sub) record when a subscriber is created.

Use the change command to update the status of aor2sub and the show command to display the status of aor2sub.

The SIP register contact (status sip-reg-contact) command queries the status of the registered contact for the particular AOR (SIP phone subscriber). Calls can be originated from or terminated to a SIP subscriber only if the AOR has a currently registered contact. Calls cannot be originated or terminated if the registered contact for the AOR is expired or freed.

SIP-REG-CONTACT

Use the status sip-reg-contact command to display the operational status of the dynamic contact for a specific AOR.

Examples status sip-reg-contact [email protected];

Note In this example, the registered contact for this AOR ID has expired, and calls cannot be originated from or terminated to this host.


AOR ID -> [email protected];USER -> 4692551885HOST -> 64.101.150.141PORT -> 5062USER TYPE -> USER_IP_TYPEEXPIRES -> 1800EXPIRETIME -> Wed Jun 4 11:08:33 2003

STATUS -> EXPIRED CONTACT

Reply : Success:

status sip-reg-contact [email protected];

Note In this example, the registered contact for this AOR ID is valid, and calls can be originated from and terminated to this host.


AOR ID -> [email protected];USER -> 7132551833HOST -> 64.100.120.125


OL-4495-04


PORT -> 5060USER TYPE -> USER_IP_TYPEEXPIRES -> 3600EXPIRETIME -> Wed Jun 4 11:37:44 2003

STATUS -> REGISTERED CONTACT

Reply : Success:

Aggregation StatusThis section details the status command for an aggregation (aggr) router. Aggregation routers are used in cable and network-based call signaling (NCS) markets. In cable markets, they are used as cable modem termination systems (CMTSs). In NCS markets, they are used as edge routers.

Step 1 Use the following example to check the status of an aggregation router:

status aggr id=CMTS1

Reply Example:

Reply : Success:

AGGR ID -> CMTS1OPER STATE -> AGGR IN ServiceRESULT -> ADM configure result in successREASON -> ADM executed successful

The following list provides the AGGR operational-state values and possible responses for the command:

1. IN SERVICE

a. Means the TCP connection to the AGGR is up.

b. CLI output: AGGR IN SERVICE.

2. CONNECTING

a. Means the TCP connection to the AGGR is being set up.

b. CLI output: AGGR CONNECTING.

3. INITIALIZING

a. Identifies the initial state of the AGGR before a Call Agent (CA) attempts to connect to it.

b. CLI output: AGGR INITIALIZING (this is a transitional state, which a user may rarely see).

4. OUT OF SERVICE

a. Means the AGGR is out of service.

b. CLI output: AGGR OUT OF SERVICE.

Destination Point CodeThis section describes the ADM status command for destination point codes (DPCs).


OL-4495-04


Examples status dpc id=dpc1;

H.323 GatewayThis section describes the status and control commands for H.323 gateways.

The following table contains the RAS states for H.323 gateways:

Status Command

This section describes the status command for H.323 gateways.


Examples status h323-gw id=CHINA-1;

Reply Example:

Reply : Success:

ADMIN_STATE -> ADMIN_INSH3A PROCESS NUMBER -> 30H3A PROCESS NAME -> H3A1ENDPOINT ID -> ACTIVE CALLS -> 0RAS STATE -> CCH323_RAS_STATE_GRQRAS PORT -> 35881IP ADDRESS -> 10.89.224.125REGISTERED GATEKEEPER ID -> PRIMARY GATEKEEPER ID -> PRIMARY GATEKEEPER PORT -> 0PRIMARY GATEKEEPER IP -> H323 VERSION -> 4TIME TO LIVE -> 0NUM ALT GATEKEEPERS -> 0ALT GATEKEEPER PERMANENT -> TRUETHRESHOLD_ENABLED -> FALSEOUT_OF_RESOURCES -> FALSEALT GATEKEEPER LIST ->

RAS State Description

CCH323_RAS_STATE_NONE The H.323 gateway operational state is ADMIN OOS.

CCH323_RAS_STATE_GRQ The H.323 gateway is in the Gatekeeper Discovery State.

CCH323_RAS_STATE_RRQ The H.323 gateway is in the Gateway Registration State.

CCH323_RAS_STATE_IDLE The H.323 gateway is ready for calls.

CCH323_RAS_STATE_URQ The H.323 gateway is in the Un-registration state.


OL-4495-04


Control Command

This section describes the control command for H.323 gateways.

Examples control h323-gw id=CHINA_1; target-state=INS;

Reply Example:

Reply : Failure:

INITIAL STATE -> ADMIN_INSREQUEST STATE -> ADMIN_INSRESULT STATE -> ADMIN_INSFAIL REASON -> ADM entity in desired stateREASON -> ADM is in request stateRESULT -> ADM configure result in warningH323GW ID -> CHINA_1

ISDN SwitchoverThis section describes the control command for ISDN switchover. For ISDN status, use the status trunk group command described in the “Trunk Group” section on page 8-16. This command is only applicable to nonfacility-associated signaling (NFAS). It switches the D channel that is active to standby, and the D channel that is standby to active.

Step 1 Use the following example to display the current TGs with ISDN D channels.

show isdn-dchan

Following is an example of the display:

TGN_ID=1700DCHAN_TYPE=PRIMARYSET_ID=backset1DCHAN_SLOT=3DCHAN_PORT=0DCHAN_INTF=0

TGN_ID=1701DCHAN_TYPE=PRIMARYSET_ID=backset1DCHAN_SLOT=3DCHAN_PORT=1DCHAN_INTF=0

Reply : Success: Entries 1-2 of 2 returned.

Step 2 Use the following example to switch over an ISDN D channel.

control isdn-dchan tgn-id=1;

Reply Example:

Reply : Success


OL-4495-04


Media GatewayThis section describes the status and control commands for media gateways.

Status Command

This section describes how to check the status of a media gateway.

Step 1 The following example checks the status of a media gateway:

status mgw id=c5300_197;

Reply Example:

Reply : Success:

MGW ID -> c5300_197RESULT -> ADM configure result in successREASON -> ADM executed successfulADMIN STATE -> ADMIN_INSOPER STATE -> Media gateway in working status

Table 8-1 lists the administrative states the system can return.

The system can report the following MGW operational states:

• Media gateway in unknown status

• Media gateway in working status

• Media gateway in down status

• Media gateway cannot be reached

Control Command

This section shows how to control a media gateway in service. Modes can be either forced or graceful. Forced mode tears down all calls immediately; graceful mode allows calls in progress to complete before teardown.

Step 1 Use the following example to control a media gateway in service:

control mgw id=c5300_162; mode=forced; target-state=INS;

Table 8-1 Returnable Administrative States

State Definition

ADMIN-INS In Service.

ADMIN-OOS Out of Service.

ADMIN-MAINT Maintenance Mode.

ADMIN-OOS-PENDING Transitioning to Out of Service.

ADMIN-MAINT-PENDING Transitioning to Maintenance Mode.


OL-4495-04


Reply Example:

Reply : Success: CLI change successful

MGW ID -> c5300_162INITIAL STATE -> ADMIN_OOSREQUEST STATE -> ADMIN_INSRESULT STATE -> ADMIN_INSFAIL REASON -> ADM found no failureREASON -> ADM executed successfulRESULT -> ADM configure result in success

Note The rules for placing an MGW into the OOS, INS, and MAINT states are shown in Figure 8-1.

Figure 8-1 Administrative and Operational Maintenance States for MGW

5207

7

P_INS (MGW)

MGW = NP

MGW = OOS

MGW = INS

P_MNT (MGW)

P_INS (MGW)

Add (MGW) Del (MGW)

DISCOVER MGW, *MGW = INS

P_MNT (MGW)

MGW = MNT

DISCOVER MGW, *MGW = MNT

MGW = MNTAll (T = INS) = MNT

MGW = OOSAll T = OOS

MGW = INS

P_OOS (MGW) P_OOS (MGW)

P_OOS = Place out of serviceP_INS = Place in serviceP_MNT = Place maintenanceNP = Not provisioned

* "Discover" means to establish MGCP communication with MGW


OL-4495-04


Signaling Gateway ProcessThis section details the status command for the signaling gateway process (SGP) table.

Status Command

The SGP status command returns the state of the SGP.

Examples status sgp id=sgp1;

where sgp-id is the ID of the selected signaling gateway process in the sgp table, for example sgp222. This is an optional token.

Stream Control Transmission Protocol AssociationThis section details the status and control commands for the Stream Control Transmission Protocol (SCTP) Association table.

Status Command

Use the following command example to check the status of an SCTP association.

Examples status sctp-assoc id=sctpassoc1;

Control Command

The following command example shows how to control an SCTP out of service. Modes can be either forced or graceful. Forced tears down all calls immediately; graceful allows calls in progress to complete before teardown.

Examples control sctp-assoc id=sctpassoc1; target-state=INS; mode=FORCED;

Subscriber TerminationThis section describes the status and control commands for subscriber terminations. Either a range of subscribers can be specified by using *@mgw-id for the ID parameter, or a single subscriber can be specified (for example: [email protected]).

Note When first provisioned, all subscriber terminations are in the unequipped (UEQP) state. A subscriber termination must also be in the UEQP state before it can be deleted.


OL-4495-04


Individual subscriber terminations can be placed into any of three administrative service states: INS, OOS, and MNT. The relationship between subscriber termination states and the residential gateway (RGW) state is provided in Table 8-2.

where:

• OOS—out of service

• MAINT—maintenance

• INS—in service

• UEQP—unequipped

The rules for placing RGW subscriber terminations into the OOS, INS, and MAINT states (which depend upon the RGW state) are shown in Figure 8-2.

Table 8-2 RGW and Subscriber Termination States

RGW State Allowed Subscriber Termination States

OOS • OOS

• UEQP

INS • OOS

• MAINT

• INS

• UEQP

MAINT • OOS

• MAINT

• UEQP


OL-4495-04


Figure 8-2 Administrative and Operational Maintenance States for Residential Gateways

6985

5

If SL = UEQPDel (SL)

RGW = INSSL = NP/OOS/MNT/INS P_OOS (SL)

If SL = UEQP SL=OOSif SL = OOS warnif SL = INS/MNT

SL = OOS

If SL = NESL = UEQP

Del (SL)*Add (SL)*

P_INS (SL)

If SL = INS warnelse {

{if SL = OOSdiscover SL*2}

init SL*3,SL = INS}

P_MNT (SL)If SL = UEQP SL=MNTif SL = MNT warn

else {{if SL = OOS

discover SL *2}init SL*3,

SL = MNT}


RGW = MNTSL = OOS/MNT P_OOS (SL)

If SL = OOS warnif SL = MNTSL = OOS

If SL = NESL = UEQP

Del (SL)*Add (SL)*

P_INS (SL)

Warning

P_MNT (SL)If SL = MNT warnelse {

{if SL = OOSdiscover SL*2}

init SL*3,SL = MNT}

* Provisioning command*2 Establish MGCP communication with subscriber loop*3 Determine capabilities and program terminations


If SL = NESL = UEQP

RGW = OOSSL = NP/UEQP P_OOS (SL)

Warning

Del (SL)*Add (SL)*

P_INS (SL)

Warning

P_MNT (SL)Warning

P_OOS = Place out of serviceP_INS = Place in serviceP_MNT = Place maintenanceNP = Not provisionedSL = Suscriber line


OL-4495-04


Status Command

This section describes how to show the status of subscriber terminations. It is organized as follows:

• Single Subscriber Termination Status

• All Subscriber Terminations Status

• Administrative State Token

• Operating State Token

• Source Token

Single Subscriber Termination Status

This section describes how to check the status of a single subscriber termination.

Step 1 The following example checks the status of a single subscriber termination:

status subscriber-termination id=ubr204_1;

Reply Example:

RESULT -> ADM configure result in successREASON -> ADM executed successfulADMIN STATE -> ADMIN_INSOPER STATE -> Termination is idleSUBCRIBER DN -> ubr204_1FAULT REASON -> No fault reason available

Note Table 8-3 lists the administrative states the system can return.

All Subscriber Terminations Status

This section describes how to show the status of all subscriber-terminations on a particular gateway.

Step 1 The following example shows the status of all subscriber-terminations on a particular gateway:

status subscriber-termination id=*@ubr235;

Table 8-3 Returnable Administrative States

State Definition

ADMIN-UEQP Unequipped.







OL-4495-04


Reply Example:

SUBCRIBER DN -> ubr235_1ADMIN STATE -> ADMIN_UEQPOPER STATE -> Termination is unequipedREASON -> ADM executed successfulRESULT -> ADM configure result in successFAULT REASON -> No fault reason available

SUBCRIBER DN -> ubr235_2ADMIN STATE -> ADMIN_UEQPOPER STATE -> Termination is unequipedREASON -> ADM executed successfulRESULT -> ADM configure result in successFAULT REASON -> No fault reason available Reply : Success:

Administrative State Token

The Administrative State (admin-state) token returns the administrative state of the subscriber termination. Valid values are:

• UEQP—Unequipped; resource is not commissioned. Resource is not registered.

• OOS—Termination was manually controlled out of service.

• INSQ Termination was manually controlled in service, but operationally may be available or unavailable.

• OOS-PENDING—Termination was manually controlled out of service with mode graceful, termination is still involved in a call.

• MAINT—Termination was in maintenance mode, can run diagnostic commands.

• MAINT-PENDING—Termination was manually controlled to MAINT state, but termination is still involved in call.

• ALL—Return all possible states.

The following command example returns only those trunk terminations that are in administrative state OOS (if any), and operating state IDLE (if any):

status trunk-termination tgn-id=12; cic=1-1000; admin-state=OOS; oper-state=idle

Operating State Token

The Operating State (oper-state) token expands the range of useful information returned by the status subscriber-termination command.

Note The values for the oper-state token are not the same as the status response returned for the command.The oper-state token is optional.

The operational status of the subscriber termination is always returned by the command, whether or not the oper-state token is used.

For the valid values for the oper-state token, see the BTS 10200 Command Line Interface Guide.


OL-4495-04


Source Token

The source token specifies whether to query the Call Agent, or the EMS, for status information. It is an optional token.

Valid values for the source token are:

• EMS (Default)—Query the local EMS database for most current status.

• AGENT—Query the remote Call Agent database for most current status.

The following example returns the current status of a Call Agent:

status subscriber-termination id=*@ubr235; source=AGENT;

Control Command

This section describes how to control subscriber terminations on a particular gateway. To control a subscriber termination to the unequipped or equipped state, use the equip or unequip commands in the “Equip Command” section on page 8-15 and the “Unequip Command” section on page 8-15. This section is organized as follows:

• Control a Single Subscriber Termination

• Control All Subscriber Terminations

• Equip Command

• Unequip Command

Control a Single Subscriber Termination

To control one subscriber-termination on a particular gateway using the following command.

Note To control a subscriber termination to the unequipped or equipped state, use the equip or unequip commands.

Step 1 The following example controls a single subscriber termination into service:

control subscriber-termination id=*@c3810_167; mode=forced; target-state=INS;

Reply Example:


ID -> c3810_167REQUEST STATE -> ADMIN_INSRESULT STATE -> ADMIN_INSFAIL REASON -> ADM found no failureREASON -> ADM executed successfulRESULT -> ADM configure result in success

Control All Subscriber Terminations

This section describes how to control all subscriber-terminations on a particular gateway.

Step 1 The following example controls to MAINT all subscriber-terminations on a particular gateway:


OL-4495-04


control subscriber-termination id=*@ubr235; mode=forced; target-state=MAINT

Reply Example:


ID -> ubr235REASON -> ADM executed successfulRESULT -> ADM configure result in successREQUEST STATE -> ADMIN_MAINTRESULT STATE -> ADMIN_MAINTFAIL REASON -> ADM found no failureCLI>diag subscriber-terminationReply : Success: Diagnostic Subscriber Menu.

Equip Command

The equip command changes the administrative state of terminations that are in the UEQP state to OOS state. It ignores the terminations in the states INS, MAINT, or OOS.

Step 1 Use the following example to equip a subscriber termination:

equip subscriber-termination [email protected];

Reply Example:


ID -> Subcriber ID -> [email protected] -> ADM executed successfulRESULT -> ADM configure result in successFAIL REASON -> ADM found no failure

Unequip Command

The unequip command changes the administrative state of subscriber terminations that are in OOS state into UEQP state. It ignores the terminations in the INS, MAINT, or UEQP states.

Step 1 Use the following command to unequip a subscriber termination:

unequip subscriber-termination [email protected];

Reply Example:


ID -> Subcriber ID -> [email protected] -> ADM executed successfulRESULT -> ADM configure result in successFAIL REASON -> ADM found no failureFAIL REASON -> ADM found no failure


OL-4495-04


SubsystemThis section describes the status and control commands for the Subsystem table. This table holds the information for all the subsystems using signaling connection control part (SCCP). Because the Cisco BTS 10200 Softswitch supports multiple origination point codes (OPCs), both the subsystem ID and OPC_ID are required to determine subsystem information.

Use the show command to display information about the provisioned subsystem(s), including IDs and OPC_IDs.

show subsystem;

Typical system response:

ID=LNP_SSNLOCAL_SSN=248REMOTE_SSN=248SCCP_NW_ID=1OPC_ID=opcSCCP_VERSION=ANS92TCAP_VERSION=ANS92APPLICATION_VERSION=AIN01STATUS=UISReply : Success: Entries 1-1 of 1 returned.

Status Command

The status subsystem command returns the state of a subsystem. You must enter the ID and OPC_ID in this command.status subsystem id=LNP_SSN; opc_id=opc;

Typical system response:

SUBSYSTEM ID -> LNP_SSN OPC ID -> opcADMIN STATE -> User in serviceOPER STATE -> Subsystem allowedREASON -> ADM executed successfulRESULT -> ADM configure result in success

Reply : Success:

Control Command

The following example shows how to control a subsystem out of service in forced mode:

control subsystem id=LNP_SSN; opc_id=opc; target-state=OOS; mode=FORCED;

Trunk GroupThis section describes the status and control commands for trunk groups (TGs). Individual TGs can be placed into any of three administrative service states: INS, OOS, and MAINT. The relationship between TGW and TG state is provided in Table 8-4.


OL-4495-04


Status Command

This section describes how to show the status of one TG ID.

Step 1 The following example shows the status of a single TG ID:

status trunk-grp id=2;

Reply Example:

RESULT -> ADM configure result in successREASON -> ADM executed successfulADMIN STATE -> ADMIN_INSOPER STATE -> Trunk group in-serviceTGN ID -> 2

Table 8-5 lists the administrative states the system can return.

The system can return the following operating states:

• Trunk group in-service

• Trunk group out-of-service

Table 8-4 ISDN TGW/TG State Relationships

TGW State Allowed TG States

INS • OOS

• MAINT

• INS

MAINT • OOS

• MAINT

Table 8-5 Example Returnable Administrative States

State Definition




ADMIN-OOS-Pending Transitioning to Out of Service.

ADMIN-MAINT-Pending Transitioning to Maintenance Mode.

ACL Congestion is at level 1



TFC Congestion is at level 1




OL-4495-04


• Trunk group manually busy

• Trunk group operate in wait state

• Trunk group operate in standby state

• Trunk group restore session request normal

• Trunk group restore session request switch-over

• Trunk group restore session request maintenance

• Trunk group restore session fail normal

• Trunk group restore session fail switch-over

• Trunk group restore session fail maintenance

• Trunk group restore establish request normal

• Trunk group restore establish request switch-over

• Trunk group restore establish request maintenance

• Trunk group restore establish fail normal

• Trunk group restore establish fail switch-over

• Trunk group restore establish fail maintenance

• Trunk group in maintenance state

• Trunk group down session set fail soft normal

• Trunk group down session set fail hard normal

• Trunk group down session set fail soft maintenance

• Trunk group down session set fail hard maintenance

• Trunk group down establish request soft normal

• Trunk group down establish request hard normal

• Trunk group down establish request soft maintenance

• Trunk group down establish request hard maintenance

• Trunk group down establish fail soft normal

• Trunk group down establish fail hard normal

• Trunk group down establish fail soft maintenance

• Trunk group down establish fail hard maintenance

• Trunk group delete graceful

• Trunk group request remove release

• Trunk group request remove session set

• Trunk group remove graceful in-service and maintenance state

• DPC is inaccessible

Control Command

This section describes how to control one trunk group ID.


OL-4495-04


Note When performing the following commands in immediate succession, always wait at least one second before performing the second command:

control trunk-grp tgn-id=129; mode=forced; target-state=oos; control trunk-grp tgn-id=129; mode=forced; target-state=ins;

Step 1 The following example controls a single trunk group ID into service:

control trunk-grp id=2; mode=forced; target-state=INS;

Reply Example:


INITIAL STATE -> ADMIN_OOSREQUEST STATE -> ADMIN_INSRESULT STATE -> ADMIN_INSFAIL REASON -> ADM found no failureREASON -> ADM executed successfulRESULT -> ADM configure result in successTGN ID -> 2

Caution When you control an ISDN trunk in-service, the media gateway must be in-service. When you control an ISDN trunk group, all ISDN trunks in that trunk group are controlled to the same state.

Trunk TerminationThis section describes the status and control commands for trunk terminations. Either a range (for example, cic=1-24;) or a single value (for example, cic=1;) for the CIC parameter can be specified for the status and control of trunk terminations.

Individual ISDN trunks and trunking groups can be placed into any of three administrative service states: INS, OOS, and MAINT. The relationship between trunk/trunk group state and the TGW state is provided in Table 8-6. For all other trunk types, the trunk state and trunk group state are independent.

where:

• TGW—trunking gateway

• TG—trunk group

Table 8-6 ISDN TGW/TG State Relationships

TGW State Allowed TG States Allowed Trunk States

INS • OOS

• MAINT

• INS

• UEQP OOS

• UEQP OSS, MAINT

• UEQP OOS, MAINT, INS

MAINT • OOS

• MAINT

• UEQP OOS

• UEQP OSS, MAINT


OL-4495-04


• OOS—out of service

• MAINT—maintenance

• INS—in service

• UEQP—unequipped

The rules for placing trunks and TG into the OOS, INS, and MAINT states (which depend upon the TGW state) are shown in Figure 8-3.


OL-4495-04


Figure 8-3 ISDN Administrative and Operational Maintenance States for a Trunking Gateway

5207

9

P_OOS = Place out of serviceP_INS = Place in serviceP_MNT = Place maintenanceNP = Not provisioned

if TGP = OOSdel (TGP)

TGP = OOS

TGW = OOSTGP = NP/OOSTRK = NP/OOS

Del (TRK, TGP)

if (TRK, TGP) = OOSdel (TRK, TGP)

Del(TGP)

Add (TGP)

Add (TRK, TGP)

if TGP = OOSadd (TRK)

TRK = OOS

TGW=INSTGP=NP/OOS/MNT/INSTRK=NP/OOS/MNT/INS

if TGP=OOS/INSTGP=MNT

all TRK=MNTbearer=MNT

signaling=MNTP_MNT(TRK, TGP)

Del (TGP)

if TGP=OOSdel (TGP)

P_OOS (TGP)

if TGP!=NPTGP=OOS

all TRK=OOSbearer=OOS

signaling=OOS

if TGP=MNTif (TRK, TGP)=OOS(TRK, TGP)=MNT

bearer=MNTsignaling=MNT

P_OOS (TRK, TGP)

if (TRK, TRG)=INS/MNT(TRK, TGP)=OOS

bearer=OOSsignaling=OOS

P_INS (TGP)

if TGP=OOS/MNTTGP=INS

all TRK=INSinit bearer,signaling

Add (TRK, TGP)

if TGP!=NPadd(TRK)TRK=OOS

Del (TRK, TGP)

if (TRK, TGP)=OOSdel (TRK, TGP)

Add (TGP) TGP=OOS

P_INS (TRK, TGP)

if TGP=INSif (TRK, TGP)!=NP(TRK, TGP)=INS

bearer=INSsignaling=INS

TGW=INSTGP=NP/OOS/MNT/INSTRK=NP/OOS/MNT/INS

if TGP=OOSTGP=MNT

all TRK=MNTbearer=MNT

signaling=MNT

P_MNT(TRK, TGP)P_MNT (TGP)

Del (TGP)

if TGP=OOSdel (TGP)

P_OOS (TGP)

If TGP=MNTif (TRK, TGP)=OOS(TRK, TGP)=MNT

bearer=MNTsignaling=MNT

P_OOS (TGP)

if TGP!=MNTTGP=OOS

all TRK=OOSbearer=OOS

signaling=OOSDel (TRK, TGP)

if (TRK, TGP)=OOSdel (TRK, TGP)

Add (TGP) TGP=OOS

Add(TRK, TGP)

if TGP!=NPADD(TRK)TRK=OOS

if (TRK, TRG)=INS/MNT(TRK, TGP)=OOS

bearer=OOSsignaling=OOS

P_MNT (TGP)


OL-4495-04


Status Command

This section describes how to check trunk termination status. This section is organized as follows:

• Trunk Termination Status—Basic Command

• Trunk Termination Status—Optional Tokens

• Trunk Termination Status—”status tt” Command

Trunk Termination Status—Basic Command

This section describes how to check the status of one trunk termination. This command can be executed for one CIC (for example, cic=1;), a range of CICs (for example, cic=1-12;) or for all CICs (cic=all;).

Step 1 Use the following example to check the status of one trunk termination:

status trunk-termination tgn-id=2; cic=8;

Reply Example:

Reply : Success:

RESULT -> ADM configure result in successREASON -> ADM executed successfulTGN ID -> 2CIC -> 8TERM ADMIN STATE -> ADMIN_INSTERM OPER STATE -> Termination is idleTERM REASON -> No fault reason availableTRUNK STATIC STATE -> ACTVTRUNK DYNAMIC STATE -> TRNSTRUNK REASON -> NON_FAULTY

Note Table 8-7 lists the administrative states the system can return for the term admin status response.

.Table 8-7 Example Returnable Administrative States

State Definition

ADMIN-UNEQP Unequipped.






ADMIN-NULL Resource does not exist.


OL-4495-04


Trunk Termination Status—Optional Tokens

The following optional tokens can be used with the status trunk-termination command. They expand the range of useful information returned. Either all, or none of the tokens can be used, with the exception of the off-normal token, which must be used by itself (without any other tokens).

• Administrative State (admin-state). Valid values are:

– UEQP—Unequipped; resource is not commissioned. Resource is not registered.

– OOS—Termination was manually controlled out of service.

– INS—Termination was manually controlled in service, but operationally may be available or unavailable.

– OOS-PENDING—Termination was manually controlled out of service with the graceful mode, termination is still involved in a call.

– MAINT—Termination was in maintenance mode, can run diagnostic commands.

– MAINT-PENDING—Termination was manually controlled to the MAINT state, but termination is still involved in call.

– ALL—Return all possible states.

The following command example returns only those trunk terminations that are in administrative state OOS (if any), and operating state IDLE (if any):

status trunk-termination tgn-id=12; cic=1-1000; admin-state=OOS; oper-state=idle

• Operating State (oper-state). Valid values for the oper-state token are:

– FA—Includes FAULTY, UNREACH, TEMP-DOWN, and DOWN.

– FAULTY—The MGCP endpoint returned a permanent error code.

– UNREACH—The MGCP endpoint was declared as not reachable. This indicates gateway connectivity problems.

– TEMP-DOWN—The MGCP endpoint is temporarily down.

– DOWN—MGCP endpoint is down because GW termination has sent an RSIP-down message.

– NF—Includes INT-MAINT, IDLE, BUSY, and ACTIVE.

– INT-MAINT—Internal error recovery is in progress.

– IDLE—Termination is not involved in a call, but is available.

– BUSY— Termination is involved in transient call.

– ACTIVE—Termination is involved in stable call.

– UEQP—Termination is not equipped.

– ALL—Returns all possible operational states.

The following command example returns only those trunk terminations that are FA (if any):

status trunk-termination tgn-id=12; cic=ALL; oper-state=FA;

• Static State (static-state). Valid values for the static-state token are:

– UEQP—Unequipped resource is not commissioned. Resource is not registered.

– LBLK—Termination is locally blocked: either manually taken OOS/MAINT (block reason can be MANUAL-OOS, MAINT-OOS), or automatically went out of service.

– RBLK—Termination is remotely blocked (blocked by remote side).


OL-4495-04


– ACTV—Available.

– All—Returns all possible static states.

The following command example returns only those terminations that are locally blocked (if any):

status trunk-termination tgn-id=101; cic=1-24; static-state=lblk;l

• Dynamic State (dynamic-state). Valid values for the dynamic-state token are:

– IBSY—Trunk-termination is involved in an incoming active call.

– OBSY—Trunk-termination is involved in an outgoing active call.

– TRNS—Transient maintenance state (sent maintenance signaling message and waiting for response).

– IDLE—Termination is not involved in a call.

– IBSY-TRNS—Termination is involved in an incoming transient call.

– OBSY-TRNS—Termination is involved in an outgoing transient call.

– ALL—All possible dynamic states.

The following command example returns only those terminations that are idle (if any):

status trunk-termination tgn-id=101; cic=1-24; dynamic-state=idle;

• Off-normal State (off-normal)

– Yes—Return all terminations in off-normal state.

– No—Return all terminations in normal state.

The following command example returns only those terminations in an off-normal state (if any).

status trunk-termination tgn-id=101; cic=1-24; off-normal=yes;

A termination is in an off-normal state when it is not in one of the state combinations shown in Table 8-8.

• Source (source)—Specifies whether to query the Call Agent or the Element Management System (EMS) for status information. It is an optional token.

– EMS (Default)—Query the local EMS database for most current status.

– AGENT—Query the remote Call Agent database for most current status.

The following command example returns the current status of the Call Agent:

status trunk-termination tgn-id=101; cic=1-24; source=AGENT;

Table 8-8 Valid Normal Trunk Termination States

State/Token ADMIN-STATE OPER-STATE STATIC-STATE DYNAMIC-STATE

UNEQP UNEQP ANY UEQP IDLE

MANUALLY OOS OOS ANY LBLK IDLE

MANUALLY MAIN MAINT IDLE LBLK IDLE

IDLE INS IDLE ACTV IDLE

ACTIVE INCOMING INS IDLE ACTV IDLE

ACTIVE OUTGOING INS ACTIVE ACTV OBSY


OL-4495-04


Trunk Termination Status—”status tt” Command

The following command example (status tt) returns current status as a table.

status tt tgn-id=994; cic=all

Reply Example:

994 1 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 2 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 3 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 4 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 5 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 6 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 7 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 8 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 9 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 10 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 11 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 12 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 13 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 14 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 15 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 16 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 17 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 18 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 19 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 20 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 21 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 22 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 23 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY994 24 ADMIN_INS TERM_ACTIVE_IDLE ACTV IDLE NON_FAULTY

Reply : Success:

Control Command

This section describes how to control trunk terminations. The section is organized as follows:

• Control One Trunk Termination

• Control All Trunk Terminations

Control One Trunk Termination

This section describes how to control a trunk termination.

Step 1 Use the following example to control one trunk termination into OOS:

control trunk-termination tgn-id=22; cic=1; target-state=OOS; mode=forced;

TRANSIENT INCOMING

INS ACTIVE ACTV IBY-TRNS

TRANSIENT OUTGOING

INS BUSY ACTV OBSY-TRNS

Table 8-8 Valid Normal Trunk Termination States (continued)

State/Token ADMIN-STATE OPER-STATE STATIC-STATE DYNAMIC-STATE


OL-4495-04


Reply Example:


TGN ID -> 22REASON -> ADM executed successfulRESULT -> ADM configure result in successCIC START -> 1CIC END -> 1FAIL REASON -> ADM found no failureREQUEST STATE -> ADMIN_OOSRESULT STATE -> ADMIN_OOS

Control All Trunk Terminations

This section describes how to control all trunk terminations for a group of circuit identification codes (CICs).

Step 1 Use the following example to control all trunk terminations for a particular CIC group to OOS:

control trunk-termination tgn-id=17; cic=1-23; target-state=oos; mode=forced;

Reply Example:

Reply: Request was successful.TGN ID -> 17REASON -> ADM executed successfulRESULT -> ADM configure result in successCIC START -> 1CIC END -> 24FAIL REASON -> ADM found no failureREQUEST STATE -> ADMIN_OOSRESULT STATE -> ADMIN_OOS

Reset Command

The reset command clears all manual and blocked states as well as any active/transient calls on a trunk termination, with the exception of SS7 trunk terminations. It brings a trunk into INS mode. This section is organized as follows:

• Reset a Single CIC

• Reset a Range of CICs

• Reset All CICs

Reset a Single CIC

This section describes how to reset a single CIC.

Step 1 The following example resets a single CIC on a specific trunk:

reset trunk-termination tgn-id=22; cic=1

Reply Example:

Reply : Success:


OL-4495-04


TGN ID -> 22REASON -> ADM executed successfulRESULT -> ADM configure result in successCIC START -> 1CIC END -> 1FAIL REASON -> ADM found no failure

Reset a Range of CICs

This section describes how to reset a range of CICs.

Step 1 The following example resets a range of CICs on a specific trunk:

reset trunk-termination tgn-id=13; cic=1-6;

Reply Example:


Reset All CICs

This section describes how to reset all CICs.

Step 1 The following example resets all CICs on a specific trunk:

reset trunk-termination tgn-id=13; cic=all;

Reply Example:


Equip Command

The equip command changes the administrative state of terminations that are in the UEQP state to the OOS state. It ignores the terminations in the INS, MAINT, or OOS states.

Use the equip command or the control trunk-grp command to change the termination state for a subscriber to an ISDN trunk. The control trunk-grp command changes all trunks in the specified trunk group to the specified state. For trunk types other than ISDN, use the equip command to set the subscriber termination state. Thereafter, to change the termination state, use the control command.

A subscriber termination state must set to unequipped before it can be deleted.


OL-4495-04


You cannot use the control command to change a termination state to UEQP. Furthermore, you cannot use the control command to change the state of any subscriber termination that is already in the UEQP state.

For example, consider a case in which 24 CICs in a trunk group are in the following initial states:

• CICs 1–10 in OOS state

• 11–15 in UEQP state

• 16–24 in MAINT state

For this case, issuing the control, equip, or unequip commands would affect the initial state of the CICs as follows:

• If a control command is used with target-state = ins, the final states of all the CICs are:

– CICs 1–10 in INS state

– CICs 11–15 in UEQP state

– CICs 16–24 in INS state

• If a equip command is applied to the CICs in the initial states, the final states of all the CICs are:

– CICs 1–10 in OOS state

– CICs 11–15 in OOS state

– CICs 16–24 in MAINT state

• If an unequip command is applied to the CICs in the initial states, the final states of the CICs are:



– CICs 16–24 in MAINT state

Step 1 Use the following example to equip a trunk termination:

equip trunk-termination tgn-id=13; cic=all;

Reply Example:



Unequip Command

The unequip command changes the administrative state of terminations that are in the OOS state into the UEQP state. It ignores the terminations in the INS, MAINT, or UEQP states.

Step 1 Use the following example to unequip terminations:

unequip trunk-termination tgn-id=13; cic=all;

Reply Example:


OL-4495-04

Chapter 8 Maintenance and Diagnostics for External ResourcesDiagnostic Tests


TGN ID -> 13REASON -> ADM executed successfulRESULT -> ADM configure result in successCIC START -> 1CIC END -> 24

Diagnostic TestsThis section describes diagnostic tests that can be performed on media gateways, subscriber terminations, and trunk terminations. All media gateways, subscriber and trunk terminations must be in the MAINT state for testing. The following tests are described in this section:

• Media Gateway Tests

• Subscriber Termination Tests

• SS7 Trunk Termination Tests

• ISDN Trunk Termination Tests

• CAS Trunk Termination Tests

• Announcement Trunk Termination Tests

Media Gateway TestsThis section describes the tests that can be performed on media gateways. A gateway must be in the MAINT state.

Step 1 Force the media gateway into MAINT state:

control mgw id=c2421.65; mode=forced; target-state=maint;

Reply Example:


MGW ID -> c2421.65INITIAL STATE -> ADMIN_INSREQUEST STATE -> ADMIN_MAINTRESULT STATE -> ADMIN_MAINTFAIL REASON -> ADM found no failureREASON -> ADM executed successfulRESULT -> ADM configure result in success

Step 2 Display the Test Menu.

diag mgw

Reply Example:

Reply: Diagnostic MGW Menu.===(1) MGW Network Connectivity Test(2) MGW MGCP Connectivity Test(3) ALL


OL-4495-04


Note Test #1 tests if there is a path to the device (ping). Test #2 tests if MGCP has access to the device. Test #3 performs tests 1 and 2.

Step 3 To perform a specific test, use the following examples as a guide.

diag mgw id=ubr-03; test=1;

Reply Example:

MEDIA GATEWAY LINE DIAGNOSTIC TEST EXECUTED -> diag mgwID -> ubr-03TEST-TYPE -> ADM-MGW-NETW-CONNECTIVITY-TESTTEST-DURATION -> 0RESULT -> TEST-SUCCESSREASON -> PASSEDReply: Diagnostic command executed.


Reply Example:

MEDIA GATEWAY LINE DIAGNOSTIC TEST EXECUTED -> diag mgwID -> ubr-03TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TESTTEST-DURATION -> 0RESULT -> TEST-SUCCESSREASON -> PASSEDReply: Diagnostic command executed.


Reply Example:

MEDIA GATEWAY LINE DIAGNOSTIC TEST EXECUTED -> diag mgwID -> ubr-03TEST-TYPE -> ADM-MGW-NETW-CONNECTIVITY-TESTTEST-DURATION -> 11RESULT -> TEST-SUCCESSREASON -> PASSED

MEDIA GATEWAY LINE DIAGNOSTIC TEST EXECUTED -> diag mgwID -> ubr-03TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TESTTEST-DURATION -> 0RESULT -> TEST-SUCCESSREASON -> PASSEDReply: Diagnostic command executed.

Subscriber Termination TestsThis section describes the tests that can be performed on subscriber terminations. All terminations must be in the MAINT state.

Step 1 Force the subscriber termination into MAINT state:

control subscriber-termination id=sub2-ctx2; mode=forced; target-state=maint;


OL-4495-04



diag subscriber-termination;

Reply Example:

Reply: Diagnostic Subscriber Menu.===(1) Subscriber MGCP Connectivity Test(2) Subscriber Termination Connection Test(3) Subscriber Termination Ring Test(4) ALL

Note Test #1 tests if MGCP has access to the termination. Test #2 tests if there is a path to the device (ping). Test #3 tests if the subscriber can be rung. The Ring parameter must be specified in seconds for this test. The default is 5 seconds. Test #4 performs tests 1 through 3.


diag subscriber-termination id=sub2-ctx2; test=1;

Reply Example:

SUBSCRIBER LINE DIAGNOSTIC TEST EXECUTED -> diag subscriber-terminationID -> sub2-ctx2TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TESTTEST-DURATION -> 10RESULT -> TEST-SUCCESSREASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510Reply: Diagnostic command executed.

diag subscriber-termination [email protected]; test=2;

Reply Example:

SUBSCRIBER LINE DIAGNOSTIC TEST EXECUTED -> diag subscriber-terminationID -> [email protected] -> ADM-TERM-CONNECTION-TESTTEST-DURATION -> 55RESULT -> TEST-SUCCESSREASON -> PASS successfully.Reply: Diagnostic command executed.

diag subscriber-termination [email protected]; test=3; ring-duration=10;

Reply Example:

SUBSCRIBER LINE DIAGNOSTIC TEST EXECUTED -> diag subscriber-terminationID -> [email protected] -> ADM-TERM-RING-TESTTEST-DURATION -> 9989RESULT -> TEST-SUCCESSREASON -> PASSEDReply: Diagnostic command executed.


OL-4495-04


Note Ring-duration values are 0–999 (Default = 5). Maximum ring time is 30 seconds regardless of whether the duration is set higher than or equal to 31.

SS7 Trunk Termination TestsThis section describes the tests that can be performed on SS7 trunk terminations. All terminations must be in the MAINT state for testing.

Step 1 Force the SS7 trunk termination into MAINT state:

control ss7-trunk-termination tgn-id=103; mode=forced; target-state=maint;

Note Set COT, CVM, and CQM on the terminating gateway or switch to perform these tests. Otherwise, the test or tests will fail.


diag ss7-trunk-termination

Reply Example:

Reply: Diagnostic SS7 Trunk Group Menu.====== (1) SS7 MGCP Connectivity Test(2) SS7 Termination Connection Test(3) SS7 COT Test(4) SS7 CQM Test(5) SS7 CVT Test(6) SS7 CIC Audit(7) ALL

Note Test #1 tests if MGCP has access to the SS7 trunk termination. Test #2 tests if there is a path to the device (ping). Test #3 tests the integrity of the SS7 Bearer Path. Test #4 queries the SS7 circuit (or group of circuits) status. A range of CICs can be specified (to a maximum of 24). Both remote and local trunk states are displayed in the results.Test #5 tests to ensure that each end of the circuit has sufficient and consistent information for using the circuit in call connections. CLLI names are included.Test #6 returns status of CICs.Test #7 performs tests 1 through 6.

Step 3 To perform a specific test, use the following examples as a guide:

diag ss7-trunk-termination tgn-id=103; cic=13; test=1;

Reply Example:

TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunkTG-NUM -> 103CIC -> 13


OL-4495-04


TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TESTTEST-DURATION -> 0RESULT -> TEST-SUCCESSREASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510Reply: Diagnostic command executed.


Reply Example:

TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunkTG-NUM -> 103CIC -> 13TEST-TYPE -> ADM-TERM-CONNECTION-TESTTEST-DURATION -> 33RESULT -> TEST-SUCCESSREASON -> PASS successfully.Reply: Diagnostic command executed.


Reply Example:

TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunkTG-NUM -> 103CIC -> 14TEST-TYPE -> ADM-SS7-COT-TESTTEST-DURATION -> 0RESULT -> TEST-FAILUREREASON -> ADM-MAINT-STATE-REQUIREDReply: Diagnostic command executed.

diag ss7-trunk-termination tgn-id=2;cic=1-24;test=4

Reply Example:

Reply : Success:

TGN ID -> 2START CIC -> 1END CIC -> 24TEST TYPE -> ADM running SS7 circuit query message testTEST DURATION -> 0RESULT -> ADM ran test successfullyREASON -> CQM test passCIC COUNT -> 24CIC STATES ->

Remote State Local State

CIC 1 -> CS_IDLE ACTV IDLE












OL-4495-04


Note Table 8-9 lists the responses that can be returned for the CQM test:

diag ss7-trunk-termination tgn-id=2;cic=1;test=5

Reply Example:

Reply : Success:

TGN ID -> 2START CIC -> 1END CIC -> 1TEST TYPE -> ADM running SS7 circuit validation test TEST DURATION -> 0RESULT -> ADM ran test successfullyREASON -> CVT test passCLLI -> DALLTXRCDN5















OL-4495-04


Table 8-9 CQM Responses

Response Description

CS_TRANSIENT Transient

CS_UNEQUIPPED Unequipped

CS_IC_BUSY Incoming Busy

CS_IC_BUSY_LOCBLOC Incoming Busy and Locally Maintenance Blocked

CS_IC_BUSY_REMBLOC Incoming Busy and Remotely Maintenance Blocked

CS_IC_BUSY_BOTH_BLOC Incoming Busy and Remotely and Locally Maintenance Blocked

CS_OG_BUSY Outgoing Busy

CS_OG_BUSY_LOCBLOC Outgoing Busy and Locally Maintenance Blocked

CS_OG_BUSY_REMBLOC Outgoing Busy and Remotely Maintenance Blocked

CS_OG_BUSY_BOTH_BLOC Outgoing Busy and Remotely and Locally Maintenance Blocked

CS_IDLE Idle

CS_IDLE_LOCBLOC Idle and Locally Maintenance Blocked

CS_IDLE_REMBLOC Idle and remotely maintenance blocked

CS_IDLE_BOTH_BLOC Idle and Remotely and Locally Maintenance Blocked

CS_HW_LOCBLOC Locally Hardware Blocked

CS_HW_LOCBLOC_LOCBLOC Locally Hardware and Locally Maintenance Blocked

CS_HW_LOCBLOC_REMBLOC Locally Hardware and Remotely Maintenance Blocked

CS_HW_LOCBLOC_BOTHBLOC Locally Hardware and Remotely and Locally Maintenance Blocked

CS_HW_REMBLOC Remotely Hardware Blocked

CS_HW_REMBLOC_LOCBLOC Remotely Hardware and Locally Maintenance Blocked

CS_HW_REMBLOC_REMBLOC Remotely Hardware and Remotely Maintenance Blocked

CS_HW_REMBLOC_BOTHBLOC Remotely Hardware and Remotely and Locally Maintenance Blocked

CS_HW_BOTHBLOC Remotely and Locally Hardware Blocked

CS_HW_BOTHBLOC_LOCBLOC Remotely and Locally Hardware and Locally Maintenance Blocked

CS_HW_BOTHBLOC_REMBLOC Remotely and Locally Hardware and Remotely Maintenance Blocked


OL-4495-04


ISDN Trunk Termination TestsThis section describes the tests that can be performed on ISDN trunk terminations. All terminations must be in the MAINT state for testing.

Step 1 Force the ISDN trunk termination into MAINT state:

control isdn-trunk-termination tgn-id=17; mode=forced; target-state=maint;


diag isdn-trunk-termination

Reply Example:

Reply: Diagnostic ISDN Trunk Group Menu.=== (1) ISDN MGCP Connectivity Test(2) ISDN Termination Connection Test(3) ALL

Note Test #1 tests if MGCP has access to the ISDN termination. Test #2 tests if there is a path to the device (ping). Test #3 performs tests 1 and 2.


diag isdn-trunk-termination test=1; tgn-id=17; cic=1;

Reply Example:

TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunkTG-NUM -> 17CIC -> 1TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TESTTEST-DURATION -> 0RESULT -> TEST-SUCCESSREASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510Reply: Diagnostic command executed.

diag isdn-trunk-termination test=2; tgn-id=17; cic=1;

Reply Example:

TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunkTG-NUM -> 17CIC -> 1TEST-TYPE -> ADM-TERM-CONNECTION-TESTTEST-DURATION -> 0RESULT -> TEST-SUCCESS

CS_HW_BOTHBLOC_BOTHBLOC Remotely and Locally Hardware and Remotely and Locally Maintenance Blocked

Table 8-9 CQM Responses (continued)

Response Description


OL-4495-04


REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510Reply: Diagnostic command executed.

CAS Trunk Termination TestsThis section describes the tests that can be performed on CAS trunk terminations. All terminations must be in the MAINT state for testing.

Step 1 Force the CAS trunk termination into MAINT state:

control cas-trunk-termination tgn-id=64; mode=forced; target-state=maint;


diag cas-trunk-termination

Reply Example:

Reply: Diagnostic CAS Trunk Group Menu.===(1) CAS MGCP Connectivity Test(2) CAS Termination Connection Test(3) ALL

Note Test #1 tests if MGCP has access to the CAS termination. Test #2 tests if there is a path to the device (ping). Test #3 performs tests 1 and 2.

Step 3 To perform a specific test, use the following examples as a guide:

diag cas-trunk-termination tgn-id=64;cic=1;test=1;

Reply Example:



Reply Example:



Reply Example:


OL-4495-04


TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunkTG-NUM -> 64CIC -> 1TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TESTTEST-DURATION -> 11RESULT -> TEST-SUCCESSREASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510


Announcement Trunk Termination TestsThis section describes the tests that can be performed on Announcement trunk terminations. All terminations must be in the MAINT state for testing.

Step 1 Force the Announcement trunk termination into MAINT state:

control annc-trunk-termination tgn-id=13; mode=forced; target-state=maint;


diag annc-trunk-termination:

Reply Example:

Reply: Diagnostic ANC Trunk Group Menu.===(1) ANC MGCP Connectivity Test(2) ANC Termination Connection Test(3) ALL

Note Test #1 tests if MGCP has access to the ANC termination. Test #2, tests if there is a path to the device (ping). Test #3 performs tests 1 and 2.


diag annc-trunk-termination;test=1;tgn-id=13;cic=1

Reply Example:




OL-4495-04

Chapter 8 Maintenance and Diagnostics for External ResourcesCommand Responses

Reply Example:



Reply Example:

TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunkTG-NUM -> 13CIC -> 1TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TESTTEST-DURATION -> 11RESULT -> TEST-SUCCESSREASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510


Command ResponsesThis section describes success and failure responses to commands, as well as values for the term-reason and trunk-reason responses. The topics in this section include:

• Generic Responses to Status or Control Command Failures

• Generic Success and Failure Responses

• System Error Response

• Termination Reason Responses

• Trunk Reason Responses

• Trunk Termination Reason Responses, SS7 Only

• Fault Reason Responses

Generic Responses to Status or Control Command FailuresThese generic status and control commands apply to all MGWs, subscribers, trunks, and TGs. If a command fails, it can return one of the following generic failure reasons, as well as ones specific to the command (shown in following sections).

• Subscriber, media gateway, trunk group or trunk database was not found in shared memory.


OL-4495-04


• Component is already in the requested state.

• Graceful mode only. Appears when a command is executed and operation is INS going OSS or INS going MAINT.

• A required resource is not available.

If the MGW for a subscriber is down, the subscriber cannot be added.

For ISDN

– A trunk cannot be added unless both the MGW and trunk group are available.

– A trunk group cannot be added unless the MGW is available, and vice versa.

For SS7, CAS, Announcement

– A trunk cannot be added unless both the MGW and trunk group are available.

– A trunk group does not require the MGW to be available, and vice versa.

• An associated resource of the database cannot be found.

• An assigned resource is not valid (supported). For example: A subscriber is assigned to a PBX and the PBX is not supported.

Generic Success and Failure ResponsesThe following message is returned upon the success of a command:

• Configuration Command Executed.

One of the following messages can be returned upon the failure of a command:

• ADM found no failure.

• ADM MGW(s) cannot be found.

• ADM subscriber(s) cannot be found.

• ADM trunk group(s) cannot be found.

• ADM trunk(s) cannot be found.

• ADM no termination(s) found in MGW.

• ADM no trunk group(s) found in trunking gateway.

• ADM no trunk(s) found in trunk group.

• ADM fail while in termination table.

• ADM fail while in trunk group table.

• ADM fail while in trunk table.

• ADM fail while looking to find trunk index.

• ADM fail while getting MGW administration state.

• ADM fail while getting trunk group administration state.

• ADM fail while looking for MGW index.

• ADM administration state invalid.

• ADM failed to allocate IPC message(s).

• ADM failed to dispatch IPC message(s).


OL-4495-04


• ADM operational state invalid.

• ADM MGW(s) state change and pending.

• ADM subscriber(s) state change and pending.

• ADM trunk group(s) state change and pending.

• ADM trunk(s) state change and pending.

• ADM found subscriber category invalid.

• ADM found trunk group type invalid.

• ADM found trunk group state invalid.

• ADM found MGW admin state not ready.

• ADM found trunk group admin state not ready.

• ADM entity in desired state.

• ADM not allow trunk to reset.

• ADM not allow subscriber to reset.

• ADM change to out-of-service state required.

• ADM change to request graceful mode error.

• ADM found entity unequipped in initial state.

• ADM operation not allowed because D Channel(s) is down.

• The H.323 Gateway was not found in DBM.

• ADM found unknown failure reason(s).

System Error ResponseThe following error message applies to system processes, not to processes for individual databases:

• Shared memory conflict between processes

Termination Reason ResponsesThe following values can be returned for the termination reason (term-reason) response for subscriber termination and trunk termination commands:

• The media gateway is down.

• The media gateway is unreachable.

• The media gateway is in a faulty state.

• The media gateway is transitioning to another state.

• The transaction could not be executed due to a transient error.

• The transaction could not be executed because the endpoint is unknown.

• The transaction could not be executed because the endpoint is not ready.

• The transaction could not be executed, endpoint does not have enough resources available.

• The transaction could not be executed because a protocol error was detected.


OL-4495-04


• The transaction could not be executed because the command contained an unrecognized extension.

• The transaction could not be executed because the gateway is not equipped to detect one of the requested events.

• The transaction could not be executed because the gateway is not equipped to generate one of the requested signals.

• The transaction could not be executed because the gateway cannot send the specified announcement.

• Invalid conn identifier.

• Invalid call ID.

• Unsupported mode or invalid mode.

• Unsupported or unknown package.

• Endpoint does not have a digit map.

• The transaction could not be executed because the endpoint is restarting.

• Endpoint redirected to another Call Agent.

• No such event or signal.

• Unknown action or illegal combination of actions.

• Internal consistency in local connection options.

• Unknown extensions in local connection options.

• Insufficient bandwidth.

• Missing remote connection descriptor.

• Incompatible protocol version.

• Internal hardware failure.

• CAS signaling protocol error.

• Failure of a group of trunks.

• Unsupported values on local connection options.

• Response too big.

• Endpoint malfunctioning.

• Loss of lower connectivity.

• Endpoint taken out of service.

• No fault reason available.

Trunk Reason Responses The following statements can be returned for the trunk reason (trunk-reason) response. One or more statements can be returned, depending upon the operating conditions of the Call Agent.

• NON-FAULTY—Not blocked, available for service.

• MAINT-OOS—trunk-termination is manually controlled OOS.

• MAINT-BUSY—trunk-termination is in maintenance state; controlled to MAINT.

• TERM-FAULT—Bearer termination is in faulty condition.

• SIGNALLING-FAULT—Signaling link (for example, SS7 link, or ISDN D-channel) is faulty.


OL-4495-04


• MAINT-BLOCK—trunk-termination is manually controlled OOS (controlled mode=GRACE).

• HARDWARE-BLOCK—trunk-termination is manually controlled OOS (controlled mode=FORCED).

• OUTGOING_RESTRICTED—the outgoing call is not allowed

• DPC_INACCESSIBLE—the DPC is not accessible.

• ACL_CONGESTION_LEVEL_1—Automatic Congestion Level (ACL) congestion is at level 1.

• ACL_CONGESTION_LEVEL_2—ACL congestion is at level 2.

• ACL_CONGESTION_LEVEL_3—ACL congestion is at level 2.

• TFC_CONGESTION_LEVEL_1—Transfer Controlled (TFC) congestion is at level 1.

• TFC_CONGESTION_LEVEL_2—TFC congestion is at level 2.

• TFC_CONGESTION_LEVEL_3—TFC congestion is at level 3.

Trunk Termination Reason Responses, SS7 OnlyThe following values can be returned for the trunk terminations on SS7 trunks. One or more values can be returned, depending upon the operating conditions of the Call Agent, in addition to the reason responses listed under “Trunk Reason Responses”.

• ACT_LOC_INIT_RESET—Reset circuit at startup.

• ACT_LOC_MML_RESET—Craft reset request.

• ACT_LOC_QUERY—Circuit query.

• ACT_LOC_UPU—Action to perform user part unavailable.

• ACT_LOC_VALIDATE—Circuit validation.

• ACT_LOC_COTTEST—COT test.

• ACT_LOC_STOP—Action to stop the call.

• BLK_LOC_UPU—Trunk is blocked because user part is unavailable.

• DES_LOC_GRACE—Local hardware RSIP graceful.

• DES_LOC_SIG—SS7 signaling fault (link fail).

• DES_LOC_FORCE—Local hardware RSIP forced.

• DES_LOC_MML—MML; also used for unsolicited blocks from MDL due to circuit query reservation (CQR).

• DES_LOC_UPU—Trunk needs to be blocked because of user part unavailability.

• JOB_PENDING—Ongoing job in progress.

• JOB_REC—Job was received by the MDL component and is being processed.

• OPER_ACTIVE—Trunk is available for calls.

• REMOTE_GRACE—Trunk is blocked remotely because of a CLI command on the remote switch.

• REMOTE_FORCE—Trunk is blocked remotely because of a hardware failure on the remote switch.

• RESERVE_SPARE1—Reserved for future use.

• RESERVE_SPARE2—Reserved for future use.

• TERM_GRACE—Trunk is gracefully blocked because of an RSIP graceful from the MGW.


OL-4495-04


Fault Reason ResponsesThe following statements can be returned for the fault reason (fault-reason) response for a subscriber termination command. One or more statements can be returned, depending upon the operating conditions of the Call Agent.

• The media gateway is down.

• The media gateway is unreachable.

• The media gateway is in a faulty state.

• The media gateway is transitioning to another state.

• The transaction could not be executed, due to a transient error.

• The transaction could not be executed because the endpoint is unknown.

• The transaction could not be executed because the endpoint is not ready.

• The transaction could not be executed, endpoint doesn't have enough resources available.

• The transaction could not be executed because a protocol error was detected.

• The transaction could not be executed because the command contained an unrecognized extension.

• The transaction could not be executed because the gateway is not equipped to detect one of the requested events.

• The transaction could not be executed because the gateway is not equipped to generate one of the requested signals.

• The transaction could not be executed because the gateway cannot send the specified announcement.

• Invalid conn identifier.

• Invalid call ID.

• Unsupported mode or invalid mode.

• Unsupported or unknown package.

• Endpoint does not have a digit map.

• The transaction could not be executed because the endpoint is restarting.

• Endpoint redirected to another Call Agent.

• No such event or signal.

• Unknown action or illegal combination of actions.

• Internal consistency in local connection options.

• Unknown extensions in local connection options.

• Insufficient bandwidth.

• Missing remote connection descriptor.

• Incompatible protocol version.

• Internal hardware failure.

• CAS signaling protocol error.

• Failure of a group of trunks.

• Unsupported values on local connection options.

• Response too big.


OL-4495-04

Chapter 8 Maintenance and Diagnostics for External ResourcesStatus Update Processor

• Endpoint malfunctioning.

• Loss of lower connectivity.

• Endpoint taken out of service.

• No fault reason available.

Status Update ProcessorThe Status Update Processor (SUP) configuration table stores configurable values used by the SUP process to poll various components on the CA/FS. Each value is used to “tweak” the SUP so that the collection of statuses is least intrusive depending on the number of MGWs, trunk groups, and terminations. Most of the values are used for performance tuning.

Note This table is initially provisioned with default values at installation. During upgrades the values in these tables are not maintained.

Examples show sup-config

change sup-config type= refresh-rate; value=600

Usage Guidelines Primary Key Token(s): type

Table Lock Set: None

Change Rules: None

“*” in the table below indicates token is mandatory


OL-4495-04

Chapter 8 Maintenance and Diagnostics for External ResourcesStatus Update Processor

Syntax Description *TYPE Identifies the configurable property of the SUP process to change or show.

Primary key. VARCHAR: 1–64 ASCII characters.

Permitted values are:

REFRESH-RATE—Specifies the interval between each collection period in seconds. The valid range is an integer from 30 to MAXINT, and the default value is 600.

Note MAXINT is defined as the largest possible 4-byte integer, [2 to the power 32] - 1 = 2,147,483,647.

PRIORITY—Specifies the inner priority of the Collection Thread. The value can range from 1 to 10 and the default value is 5. Modifying this value has a minor effect in changing the CPU utilization of the SUP.

SUBTERM-MGW-BLOCK—Specifies the block of sub terms within a gateway to retrieve and update at a time. The range is 0 to MAXINT. The default value is 5 SUB term blocks at a time.

SUBTERM-BLOCK-PAUSE—Specifies the time to pause between each sub term block from each subterm-mgw-block retrieved. The value is in milliseconds. The range is 0 to MAXINT, and the default value is 9000 milliseconds (9 seconds).

SUBTERM-STATUS-PAUSE—Specifies the time to pause between each bulk subterm status command. The value is in milliseconds. The range is 0 to MAXINT, and the default value is 0 milliseconds.

TRUNKTERM-TG-BLOCK—Specifies the block of trunk terms within a trunk group to retrieve and update at a time. The range is 0 to MAXINT. The default value is 5 Trunk Term blocks at a time.

TRUNKTERM-BLOCK-PAUSE—Specifies the time to pause between each trunk term block for each trunkterm-tg-block retrieved. The value is in milliseconds. The range is 0 to MAXINT, and the default value is 9000 milliseconds (9 seconds).

TRUNKTERM-STATUS-PAUSE—Specifies the time to pause between each bulk trunk term status command. The value is in milliseconds. The range is 0 to MAXINT, and the default value is 0 milliseconds.

TRUNKTERM-RANGE-BLOCK—Specifies the range of CICs to retrieve on each bulk trunk term status. The range is 0 to MAXINT, and the default value is 1000 CICs per query.

TRUNKTERM-RANGE-PAUSE—Specifies the time to pause between each block of the trunkterm-range-block retrieved. The value is in milliseconds. The range is 0 to MAXINT, and the default value is 20000 milliseconds (20 seconds).

*VALUE Identifies the values of the configurable property specified in the type token.

VARCHAR: 1–64 ASCII characters.


OL-4495-04


C H A P T E R 9
Managing Billing Interface and Billing Records
The billing subsystem on the EMS gathers all billing related call events from call processing, formats them into a standard format, and transmits them to an external collection device. The interface to the billing mediation device can vary from carrier to carrier, thus this subsystem supports a flexible profiling system.

The billing subsystem includes the following functions:

• Provides FTP transfer of call data records to a remote billing server

• Supports batch record transmission via FTP

• Issues events and alarms as appropriate including potential billing data overwrites

• Saves up to 48 hours of billing data in persistent store

• Support for user-provisionable billing subsystem tokens

• Support for on-demand Call Detail Block (CDB) queries based on ranges of timestamps, ranges of sequence numbers, a calling number, a called number, or last record written

See also the Cisco BTS 10200 Softswitch Billing Interface Guide.

Record Retention Mechanisms in the EMSA “worst case number of records required” is determined, based on predicted call capacities and call type mixtures. Once this number of records has been reached, the next entry rolls over to the first record in the database and starts overwriting from this record onwards.

The following sample calculation is used to predict the number of records needed to store 48 hours of records:

100 calls/second in busy hour yields an average daily mean of 45 calls/second X 60 seconds/ minute X 60 minutes/hour X 48 hours = 7,776,600 records.

Billing Alarm Tracking MechanismsThe billing manager process in the EMS tracks the total number of records the billing database can store, the number of unacknowledged records, and the current percentage of the database that is occupied by unacknowledged records. This information is then compared against the threshold levels set in the billing alarm database. If the current amount of billing data exceeds thresholds in the database, then the billing manager issues alarms. The billing manager resets the alarms as the storage levels drop below the thresholds.


Chapter 9 Managing Billing Interface and Billing RecordsCall Detail Block Correlation and Format

Call Detail Block Correlation and FormatCDBs are produced from the current information sent from the billing generator in the CA to the billing manager in the EMS. An indication that the call has completed all signaling activities can be detected and used as a marker that all billing for the given call is now complete. Each of the billing event messages (BEM) that are portions of a call in progress, are stored in a staging area in the billing generator, waiting for call completion. Once the complete call content is present, the CDB is constructed from the individual BEMs and sent to the billing manager in the EMS.

Northbound Billing Data TransportBilling data is transported to the customer’s OSS network via FTP of batch files containing the Call Detail Blocks.


OL-4495-04

Chapter 9 Managing Billing Interface and Billing RecordsNorthbound Billing Data Transport

Figure 9-1 Billing Database Redundancy and Scalability Configuration

Note Contact Cisco TAC for billing questions for your specific softswitch system.

5207

2

SCSI

EMS-A

Batch filestaging

area

A1000

TCP

FTPRemote

accountingoffice

SCSI

Local disk

EMS-B

Batch filestaging

area Local disk

CA-A

OutboundBEMs

Correlationstaging

area

EMStracking

area

Local disk

CA-B

OutboundBEMs

Correlationstaging

area

Local disk

TCPTCP

FTP

EMStracking

area


OL-4495-04

Chapter 9 Managing Billing Interface and Billing RecordsNorthbound Billing Data Transport


OL-4495-04


C H A P T E R 10
Traffic Measurements
This chapter describes the traffic measurement information provided by the Cisco BTS 10200 Softswitch, and explains how to manage the generation of this data. The Cisco BTS 10200 Softswitch provides the following capabilities:

• Collection of all statistics in 5, 15, 30, or 60 minute intervals

• Clears counters after each interval without loss of ongoing counts

• Saves 48 hours of statistical data in 5, 15, 30, or 60 minute increments in persistent store

• Provides display of summary report of past 24 hour period

• Provides for on-demand report queries keyed by collection interval

• Issues events as appropriate

Filtering Traffic MeasurementsUse one of the following commands to specify which types of measurements are to be stored in the system:

show measurement-prov type=<type>;

change measurement-prov type=<type>; enable=<yes or no>; time-interval=<time interval>;

Valid values for <type> are:

• ISDN—ISDN signaling protocol related information

• CALLP—Call processing specific information

• MGCP—MGCP signaling protocol related information

• SIM—Service interaction manager related information

• POTS-FS—POTS/Centrex/Tandem Feature Service related information

• AINSVC—AIN Feature Service related information

• TSA—TSA application related information

• SCCP—SCCP protocol related information

• TCAP—TCAP related protocol information

• INAP—INAP related protocol information


Chapter 10 Traffic MeasurementsTraffic Measurement Data Transport and Access

Caution The INAP protocol measurements are not used in Release 4.1. They are disabled (enable=no) by default. The TCAP measurements (see “TCAP Protocol Measurements” section on page 10-37) cover the information formerly available from INAP. Information that could show in the INAP counters could be misleading, and should be ignored.

• SUA—SUA signaling protocol related information

• M3UA—M3UA signaling protocol related information

• SCTP—SCTP signaling protocol related information

• ISUP—ISDN User Part (ISUP) SS7 signaling protocol related information, applicable in a signaling gateway configuration

• AUDIT—Auditing related information

• SIA—Signaling interface adapter related information

• BILLING—Call detail block (CDB) data-related information

• EM—Event messaging billing-related information

• DQOS—Dynamic quality of service related information

• SNMP—SNMP agent protocol related information

• TG-USG—Trunk group usage information

• ANM—Announcement server related information

• H323—H.323 signaling protocol related information

Valid values for enable are yes and no. This string specifies whether or not to perform collection on the specified measurement type. This is an optional token that is preprovisioned with a value of YES at the factory. Either this token and/or the time-interval token must be entered.

Valid values for time-interval are listed below. This value indicates the number of minutes each reporting interval is to span for the given report type. The reporting interval is always synchronized to zero minutes after the hour for consistency. This is an optional token that is preprovisioned with a value of 15 at the factory. Changing this value does not take effect until the completion of the current collection interval based on the previous time-interval setting. Either this token and/or the enable token must be entered.

• 5

• 15

• 30

• 60

Note These commands are not case-sensitive. See the Cisco BTS 10200 Command Line Interface Reference Guide for additional details on these commands and report types.

Traffic Measurement Data Transport and AccessThe measurement data collected on the Cisco BTS 10200 Softswitch can be accessed via several different mechanisms:

• Command-line interface (CLI), which runs over a Telnet or secure shell (SSH) session


OL-4495-04

Chapter 10 Traffic MeasurementsRetrieving Traffic Measurement Report Summaries

• Comma-separated value (CSV) or Extensible Markup Language (XML) format via FTP or SFTP interface

• SNMP MIB (the supported version of SNMP on the Cisco BTS 10200 Softswitch is v2c)

Retrieving Traffic Measurement Report SummariesUse one of the commands listed in this section to retrieve specific types of measurement summaries from the data that is stored in the system. These commands allow you to specify a time interval, a specific type of data, and the source of data. The system supports the following methods for retrieving summaries:

• Display Report Summaries on Operator Terminal

• Create Report Summary Files

• Report Current Interval Counts

Note Any measurement counters that do not contain data for a given interval are suppressed out of the reports generated by the Cisco BTS 10200 Softswitch. Only counters that were pegged are included in the reports.

Display Report Summaries on Operator TerminalThe following are examples of command line queries to display report summaries on the operator’s terminal screen. Report summaries can be generated for measurements collected from the designated Cisco BTS 10200 Softswitch platforms between the specified start time and end time. The time interval specified must be prior to the current collection interval.

Note Definitions of the terms used in these examples follows the list of commands.

report measurement-isdn-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

report measurement-callp-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

report measurement-mgcp-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

report measurement-sim-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

report measurement-pots-local-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSPTC ID>;

report measurement-pots-misc-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSPTC ID>;

report measurement-pots-sle-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSPTC ID>;


OL-4495-04


report measurement-pots-acar-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSPTC ID>;

report measurement-pots-cos-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSPTC ID>;

report measurement-pots-cot-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSPTC ID>;

report measurement-ainsvc-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSAIN ID>;

report measurement-tsa-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSAIN ID>;

report measurement-sccp-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSAIN ID>;

report measurement-tcap-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSAIN ID>;

report measurement-inap-summary start-time=<start time>; end-time=<end time>; feature-server-id=<FSAIN ID>;

report measurement-sua-summary start-time=<start time>; end-time=<end time>; sgp-id=<SGP ID>;

report measurement-m3ua-summary start-time=<start time>; end-time=<end time>; sgp-id=<SGP ID>;

report measurement-sctp-summary start-time=<start time>; end-time=<end time>; sctp-assoc-id=<SCTP ASSOCIATION ID>;

report measurement-isup-summary start-time=<start time>; end-time=<end time>; tgn-id=<TGN ID>;

report measurement-audit-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

report measurement-sia-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

report measurement-billing-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

report measurement-em-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

report measurement-dqos-summary start-time=<start time>; end-time=<end time>; aggr-id=<AGGR ID>;

report measurement-snmp-summary start-time=<start time>; end-time=<end time>;

report measurement-tg-usage-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>; tgn-id=<TGN ID>;


OL-4495-04


report measurement-anm-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

report measurement-h323-summary start-time=<start time>; end-time=<end time>; call-agent-id=<CA ID>;

where:

• start-time is a timestamp value in the format yyyy-mm-dd hh:mm:ss. This value indicates the starting interval time to search within the EMS database. This is an optional token; when it is omitted from the command, the system displays the last collected interval.

• end-time is a timestamp value in the format yyyy-mm-dd hh:mm:ss. This value indicates the stopping interval time to search within the EMS database. This is an optional token; when it is omitted from the command, the system displays the last collected interval.

Note The <time> value can be any time during the 5, 15, 30, and 60-minute interval for which the summary is requested. Each 30-minute collection interval starts on the hour or half-hour. If busy-hour data is needed, measurement summaries can be taken 10:00–10:30 a.m. and 10:30–11:00 a.m. Monday through Friday, or at the provider’s own busy hour.

• call-agent-id is the ID of the selected CA in the call-agent table, for example, CA146. This is an optional token that defaults to all CAs.

• feature-server-id is one of the following IDs. This is an optional token that defaults to all FSs.

– ID of the selected POTS/Centrex/Tandem FS (FSPTC) in the feature-server table, for example FSPTC235

– ID of the selected Advanced Intelligent Network (AIN) FS (FSAIN) in the feature-server table, for example FSAIN205

• sgp-id is the ID of the selected signaling gateway process in the sgp table, for example sgp222. This is an optional token.

• sctp-assoc-id is the ID of the selected SCTP association in the sctp-assoc table, for example sctp-assoc3. This is an optional token.

• tgn-id is the ID of the selected TG as provisioned in the trunk-grp table, for example chicago01. This is an optional token that defaults to all tgn-id.

• aggr-id is the ID of the selected aggregation device (CMTS in PacketCable networks) in the aggr table, for example AGGR01. This is an optional token.

Create Report Summary FilesThis section describes how to use command line queries to generate reports from historical measurement data that can be retrieved from the local EMS. Measurement data is placed into CSV or XML files for viewing or for FTP/SFTP transfer. The time interval specified in this command must be prior to the current collection interval.

Tip To create a report summary file, both the output token and the output-type token must be specified.


OL-4495-04


Note Definitions of the terms used in these examples follows the list of commands.

In the examples below measurement data that was collected from 10am until noon on March 27, 2003, and placed into CSV files for viewing or for FTP transfer.

Note These examples are for illustration purposes, and are not intended to provide a complete list of the measurement summary types. See the “Display Report Summaries on Operator Terminal” section on page 10-3 for a complete list of measurement summary types.

Examples:

report measurement-sim-summary start-time=2003-03-27 10:00:00; end-time=2003-03-27 12:00:00; call-agent-id=CA146; output=sim-report; output-type=csv;

report measurement-pots-local-summary start-time=2003-03-27 10:00:00; end-time=2003-03-27 12:00:00; feature-server-id=FSPTC235; output=pots-local-report; output-type=csv;

report measurement-em-summary start-time=2003-03-27 10:00:00; end-time=2003-03-27 12:00:00; call-agent-id=CA146; output=em-report; output-type=csv;

report measurement-dqos-summary start-time=2003-03-27 10:00:00; end-time=2003-03-27 12:00:00; aggr-id=AGGR01; output=dqos-report; output-type=csv;

where:

• interval is an optional token. It is used to specify that a report be generated that contains counter information for the interval currently under collection (CURRENT) or all of the collected intervals persisted on disk (ALL). If this token is used on the command line, it will override start-time and end-time tokens if they are specified. If entered, the corresponding call-agent-id or feature-server-id must be specified. There is no default value for this token. If this token and the start-time token are not entered by the user, the last collected interval is reported.

• sum is used to indicate if the resulting report request is to contain the individual interval reports (N) or a summation of all interval reports into one composite report (Y). The default value for this token is N. This token is not allowed in combination with the trunk group category.

• output specifies the name of the file to create, into which the resulting measurement data is to be placed. The system prepends the file name with the string “Tm_” and places it in the /opt/ems/report directory on the active EMS.

• output-type specifies the format of the output file as either CSV or XML format.

• display is a token that allows the user to specify which columns of data are to be presented in the resulting report. Only those columns specified are shown in the report. If the value “%” is entered, then a list of all possible column values is displayed, but the report itself is not created.

Note Additional token descriptions are listed in the “Display Report Summaries on Operator Terminal” section on page 10-3.


OL-4495-04

Chapter 10 Traffic MeasurementsClearing Current Interval Counts

Report Current Interval CountsThe system provides a CLI command to query in-progress partial interval counts of measurement data from the actual source of the data. This mechanism provides the ability to specify the current collection interval and the particular type and source of data.

Tip To display or create a report summary file, the reporting component (for example, call-agent-id or feature-server-id) must be specified and interval=current must also be specified. (SNMP is an exception, because there is no reporting component to specify.)

The following are examples of the command line queries to generate reports on the various types of measurements currently being collected from call agents and feature servers during the current interval.

Note These examples are for illustration purposes, and are not intended to provide a complete list of the measurement summary types. See the “Display Report Summaries on Operator Terminal” section on page 10-3 for a complete list of measurement summary types. and token descriptions.

Note This command is not supported for the tg-usage measurement types.

Examples:

report measurement-isdn-summary call-agent-id=CA146; output=isdn-partial-report; output-type=csv; interval=current;

report measurement-pots-acar-summary feature-server-id=FSPCT235; output=pots-acar-partial-report; output-type=csv; interval=current;

report measurement-ainsvc-summary call-agent-id=FSAIN205; output=ainsvc-partial-report; output-type=csv; interval=current;

report measurement-snmp-summary output=snmp-partial-report; output-type=csv; interval=current;

report measurement-h323-summary call-agent-id=CA146; output=h323-partial-report; output-type=csv; interval=current;

Clearing Current Interval CountsThe Cisco BTS 10200 Softswitch provides a CLI command to clear in-progress partial counts of measurement data at the actual source of the data. This mechanism provides the ability to specify the particular type and source of data. This is a destructive command that will erase the partial counts for the current interval permanently. Use this command with caution. The following examples clear all of the currently accumulating counters in CAs and FSs.

Caution This is a destructive command that will erase the partial counts for the current interval permanently. Use this command with caution.


OL-4495-04

Chapter 10 Traffic MeasurementsClearing Current Interval Counts

clear measurement-isdn-summary call-agent-id=CA146;

clear measurement-callp-summary call-agent-id=CA146;

clear measurement-mgcp-summary call-agent-id=CA146;

clear measurement-sim-summary call-agent-id=CA146;

clear measurement-pots-local-summary feature-server-id= FSPTC235;

clear measurement-pots-misc-summary feature-server-id= FSPTC235;

clear measurement-pots-sle-summary feature-server-id= FSPTC235;

clear measurement-pots-acar-summary feature-server-id= FSPTC235;

clear measurement-pots-cos-summary feature-server-id= FSPTC235;

clear measurement-pots-cot-summary feature-server-id= FSPTC235;

clear measurement-ainsvc-summary feature-server-id=FSAIN205;

clear measurement-sccp-summary feature-server-id=FSAIN205;

clear measurement-sccp-summary feature-server-id=FSAIN205;

clear measurement-inap-summary feature-server-id=FSAIN205;

clear measurement-tcap-summary feature-server-id=FSAIN205;

clear measurement-audit-summary call-agent-id=CA146;

clear measurement-sia-summary call-agent-id=CA146;

clear measurement-billing-summary call-agent-id=CA146;

clear measurement-em-summary call-agent-id=CA146;

clear measurement-snmp-summary

clear measurement-anm-summary call-agent-id=CA146;

clear measurement-h323-summary call-agent-id=CA146;


OL-4495-04

Chapter 10 Traffic MeasurementsFormat of Traffic Measurement Summaries

Format of Traffic Measurement SummariesA traffic measurement summary lists the counters of the type requested in the report command, followed by the count. An example of a report is shown below.

>====================== Start Traffic Report =============<

>====================== End Traffic Report =============<

Events and Alarms for Traffic MeasurementThe system issues events and alarms applicable to traffic measurement functions. These events and alarms are labeled “STATISTICS”, and are described in Chapter 19, “Event Messages and Alarms.”

TIMESTAMP 20040206135919

NODENAME CA146

CONDITION NORMAL

ANM_TPM_CKT_UNAVAIL 25

ANM_TPM_CALL_REJECTED 3

ANM_TPM_ADDR_INCOMPLETE 11

ANM_TPM_FAC_REJECTED 0

ANM_TPM_PRE_0_1_ABSENT 8

ANM_TPM_PRE_0_1_PRESENT 21

ANM_TPM_HNPA_ABSENT 30

ANM_TPM_NO_ROUTE_DEST 17

ANM_TPM_UNALLOCATED_NUM 0

ANM_TPM_NUM_CHANGED 3

ANM_TPM_DEST_OUTOFORDER 8

ANM_TPM_TEMP_DISCONNECT 15

ANM_TPM_FEAT_NOT_SUBS 2

ANM_TPM_AUTHCODE_INVALID 23

ANM_TPM_NO_RTE_TRANSITNW 8

ANM_TPM_CAUSE_UNKNOWN 11


OL-4495-04

Chapter 10 Traffic MeasurementsList of Traffic Measurements (Counters)

List of Traffic Measurements (Counters)The tables in this section list the various types of measurements (counters) that are collected by the Cisco BTS 10200 Softswitch. The measurements are grouped into logical categories for easy identification.

It is useful to monitor the measurements that are most important to your operation. Some of the measurements are particularly useful in alerting you to potential problems in the system. In some cases a rapid buildup of counts might indicate a problem such as congestion, processing failures, and so forth. In the tables below, an asterisk (*) is used to identify measurements for which a rapid increase in counts indicates a potential problem.

In addition, some potential network problems can be noticed by looking at specific pairs of measurements that should normally be equal. The greater the difference between two measurements (when those two measurements should be equal), the more likely it is that there could be a problem in the system.

Example:

SIP_TOTAL_INCOMING_MSG and SIP_TOTAL_SUCCESS_INCOMING_MSG

In this case, the total number of successful incoming messages should be about equal to the total number of incoming messages. Any difference between the two counts, especially a rapidly growing difference, might indicate a problem.

Resources and DefinitionsThe following reference materials are available to assist you in interpreting and using these tables:

• For information on SIP terminology (methods and response codes), refer to Internet Engineering Task Force (IETF) Recommendation RFC2543.

• For information on subscriber features, refer to the “Subscriber Features” section in the Cisco BTS 10200 Softswitch System Description document

• For a list of acronyms, see the Glossary in the Cisco BTS 10200 Softswitch System Description document.

ISDN MeasurementsTable 10-1 lists the ISDN measurements.

Table 10-1 ISDN Measurements

MeasurementDescription(* = rapid count could mean a potential problem in the system)

ISDN_SETUP_TX The number of ISDN SETUP messages sent from the reporting call agent

ISDN_SETUP_RX The number of ISDN SETUP messages received by the reporting call agent

ISDN_SETUP_ACK_TX The number of ISDN SETUP ACK messages sent from the reporting call agent

ISDN_SETUP_ACK_RX The number of ISDN SETUP ACK messages received by the reporting call agent

ISDN_CALL_PROCEED_TX The number of ISDN CALL PROCEED messages sent from the reporting call agent

ISDN_CALL_PROCEED_RX The number of ISDN CALL PROCEED messages received by the reporting call agent


OL-4495-04


ISDN_ALERTING_TX The number of ISDN ALERTING messages sent from the reporting call agent

ISDN_ALERTING_RX The number of ISDN ALERTING messages received by the reporting call agent

ISDN_PROGRESS_TX The number of ISDN PROGRESS messages sent from the reporting call agent

ISDN_PROGRESS_RX The number of ISDN PROGRESS messages received by the reporting call agent

ISDN_CONNECT_TX The number of ISDN CONNECT messages sent from the reporting call agent

ISDN_CONNECT_RX The number of ISDN CONNECT messages received by the reporting call agent

ISDN_CONNECT_ACK_TX The number of ISDN CONNECT ACK messages sent from the reporting call agent

ISDN_CONNECT_ACK_RX The number of ISDN CONNECT ACK messages received by the reporting call agent

ISDN_DISCONNECT_TX The number of ISDN DISCONNECT messages sent from the reporting call agent

ISDN_DISCONNECT_RX The number of ISDN DISCONNECT messages received by the reporting call agent

ISDN_RELEASE_TX The number of ISDN RELEASE messages sent from the reporting call agent

ISDN_RELEASE_RX The number of ISDN RELEASE messages received by the reporting call agent

ISDN_RELEASE_COMPLETE_TX The number of ISDN RELEASE COMPLETE messages sent from the reporting call agent

ISDN_RELEASE_COMPLETE_RX The number of ISDN RELEASE COMPLETE messages received by the reporting call agent

ISDN_RESTART_TX The number of ISDN RESTART messages sent from the reporting call agent

ISDN_RESTART_RX The number of ISDN RESTART messages received by the reporting call agent

ISDN_RESTART_ACK_TX The number of ISDN RESTART ACK messages sent from the reporting call agent

ISDN_RESTART_ACK_RX The number of ISDN RESTART ACK messages received by the reporting call agent

ISDN_INFORMATION_TX The number of ISDN INFORMATION messages sent from the reporting call agent

ISDN_INFORMATION_RX The number of ISDN INFORMATION messages received by the reporting call agent

ISDN_NOTIFY_TX The number of ISDN NOTIFY messages sent from the reporting call agent

ISDN_NOTIFY_RX The number of ISDN NOTIFY messages received by the reporting call agent

ISDN_STATUS_TX The number of ISDN STATUS messages sent from the reporting call agent

ISDN_STATUS_RX The number of ISDN STATUS messages received by the reporting call agent

ISDN_STATUS_ENQUIRY_TX The number of ISDN STATUS ENQUIRY messages sent from the reporting call agent

ISDN_STATUS_ENQUIRY_RX The number of ISDN STATUS ENQUIRY messages received by the reporting call agent

ISDN_SRVC_TX The number of ISDN SERVICE messages sent from the reporting call agent

ISDN_SRVC_RX The number of ISDN SERVICE messages received by the reporting call agent

ISDN_SRVC_ACK_TX The number of ISDN SERVICE ACK messages sent from the reporting call agent

ISDN_SRVC_ACK_RX The number of ISDN SERVICE ACK messages received by the reporting call agent

ISDN_FACILITY_TX The number of ISDN FACILITY messages sent from the reporting call agent

ISDN_FACILITY_RX The number of ISDN FACILITY messages received by the reporting call agent

Table 10-1 ISDN Measurements (continued)



OL-4495-04


Call Processing MeasurementsTable 10-2 lists the call processing measurements.

Table 10-2 Call Processing Measurements


CALLP_ORIG_ATTMP The number of originating call attempts of all types on the reporting call agent

CALLP_TERM_ATTMP The number of terminating call attempts of all types on the reporting call agent

CALLP_ORIG_FAIL The number of originating call attempts of all types that failed on the reporting call agent

CALLP_TERM_FAIL The number of terminating call attempts of all types that failed on the reporting call agent

CALLP_CALL_SUCC The number of successful originating and terminating call attempts of all types on the reporting call agent

CALLP_CALL_ABAND The number of originating call attempts of all types that were abandoned on the reporting call agent

CALLP_ISDN_ORIG_ATTMP The number of originating ISDN call attempts on the reporting call agent

CALLP_ISDN_TERM_ATTMP The number of ISDN terminating call attempts on the reporting call agent

CALLP_ISDN_ORIG_FAIL The number of ISDN originating call attempts that failed on the reporting call agent

CALLP_ISDN_TERM_FAIL The number of ISDN terminating call attempts that failed on the reporting call agent

CALLP_ISDN_CALL_SUCC The number of successful ISDN originating and terminating call attempts on the reporting call agent

CALLP_ISDN_CALL_ABAND The number of ISDN originating call attempts that were abandoned on the reporting call agent

CALLP_SS7_ORIG_ATTMP The number of originating SS7 call attempts on the reporting call agent

CALLP_SS7_TERM_ATTMP The number of SS7 terminating call attempts on the reporting call agent

CALLP_SS7_ORIG_FAIL The number of SS7 originating call attempts that failed on the reporting call agent

CALLP_SS7_TERM_FAIL The number of SS7 terminating call attempts that failed on the reporting call agent

CALLP_SS7_CALL_SUCC The number of successful SS7 originating and terminating call attempts on the reporting call agent

CALLP_SS7_CALL_ABAND The number of SS7 originating call attempts that were abandoned on the reporting call agent

CALLP_SIP_ORIG_ATTMP The number of originating SIP call attempts on the reporting call agent

CALLP_SIP_TERM_ATTMP The number of SIP terminating call attempts on the reporting call agent

CALLP_SIP_ORIG_FAIL The number of SIP originating call attempts that failed on the reporting call agent

CALLP_SIP_TERM_FAIL The number of SIP terminating call attempts that failed on the reporting call agent

CALLP_SIP_CALL_SUCC The number of successful SIP originating and terminating call attempts on the reporting call agent

CALLP_SIP_CALL_ABAND The number of SIP originating call attempts that were abandoned on the reporting call agent

CALLP_MGCP_ORIG_ATTMP The number of originating MGCP call attempts on the reporting call agent

CALLP_MGCP_TERM_ATTMP The number of MGCP terminating call attempts on the reporting call agent


OL-4495-04


CALLP_MGCP_ORIG_FAIL The number of MGCP originating call attempts that failed on the reporting call agent

CALLP_MGCP_TERM_FAIL The number of MGCP terminating call attempts that failed on the reporting call agent

CALLP_MGCP_CALL_SUCC The number of successful MGCP originating and terminating call attempts on the reporting call agent

CALLP_MGCP_CALL_ABAND The number of MGCP originating call attempts that were abandoned on the reporting call agent

CALLP_CAS_ORIG_ATTMP The number of originating CAS call attempts on the reporting call agent

CALLP_CAS_TERM_ATTMP The number of CAS terminating call attempts on the reporting call agent

CALLP_CAS_ORIG_FAIL The number of CAS originating call attempts that failed on the reporting call agent

CALLP_CAS_TERM_FAIL The number of CAS terminating call attempts that failed on the reporting call agent

CALLP_CAS_CALL_SUCC The number of successful CAS originating and terminating call attempts on the reporting call agent

CALLP_CAS_CALL_ABAND The number of CAS originating call attempts that were abandoned on the reporting call agent

CALLP_ISDN_SS7_CALL The number of successfully completed calls from an ISDN originator to an SS7 terminator on the reporting call agent

CALLP_ISDN_ISDN_CALL The number of successfully completed calls from an ISDN originator to an ISDN terminator on the reporting call agent

CALLP_ISDN_SIP_CALL The number of successfully completed calls from an ISDN originator to an SIP terminator on the reporting call agent

CALLP_ISDN_MGCP_CALL The number of successfully completed calls from an ISDN originator to an MGCP terminator on the reporting call agent

CALLP_ISDN_CAS_CALL The number of successfully completed calls from an ISDN originator to an CAS terminator on the reporting call agent

CALLP_SS7_SS7_CALL The number of successfully completed calls from an SS7 originator to an SS7 terminator on the reporting call agent

CALLP_SS7_ISDN_CALL The number of successfully completed calls from an SS7 originator to an ISDN terminator on the reporting call agent

CALLP_SS7_SIP_CALL The number of successfully completed calls from an SS7 originator to an SIP terminator on the reporting call agent

CALLP_SS7_MGCP_CALL The number of successfully completed calls from an SS7 originator to an MGCP terminator on the reporting call agent

CALLP_SS7_CAS_CALL The number of successfully completed calls from an SS7 originator to an CAS terminator on the reporting call agent

CALLP_SIP_SS7_CALL The number of successfully completed calls from a SIP originator to an SS7 terminator on the reporting call agent

CALLP_SIP_ISDN_CALL The number of successfully completed calls from a SIP originator to an ISDN terminator on the reporting call agent

CALLP_SIP_SIP_CALL The number of successfully completed calls from a SIP originator to an SIP terminator on the reporting call agent

Table 10-2 Call Processing Measurements (continued)



OL-4495-04


CALLP_SIP_MGCP_CALL The number of successfully completed calls from a SIP originator to an MGCP terminator on the reporting call agent

CALLP_SIP_CAS_CALL The number of successfully completed calls from a SIP originator to an CAS terminator on the reporting call agent

CALLP_MGCP_SS7_CALL The number of successfully completed calls from an MGCP originator to an SS7 terminator on the reporting call agent

CALLP_MGCP_ISDN_CALL The number of successfully completed calls from an MGCP originator to an ISDN terminator on the reporting call agent

CALLP_MGCP_SIP_CALL The number of successfully completed calls from an MGCP originator to an SIP terminator on the reporting call agent

CALLP_MGCP_MGCP_CALL The number of successfully completed calls from an MGCP originator to an MGCP terminator on the reporting call agent

CALLP_MGCP_CAS_CALL The number of successfully completed calls from an MGCP originator to an CAS terminator on the reporting call agent

CALLP_CAS_SS7_CALL The number of successfully completed calls from an CAS originator to an SS7 terminator on the reporting call agent

CALLP_CAS_ISDN_CALL The number of successfully completed calls from an CAS originator to an ISDN terminator on the reporting call agent

CALLP_CAS_SIP_CALL The number of successfully completed calls from an CAS originator to an SIP terminator on the reporting call agent

CALLP_CAS_MGCP_CALL The number of successfully completed calls from an CAS originator to an MGCP terminator on the reporting call agent

CALLP_CAS_CAS_CALL The number of successfully completed calls from an CAS originator to an CAS terminator on the reporting call agent

CALLP_INTERLA_ATTMP The number of Interlata call attempts on the reporting call agent

CALLP_INTERLA_FAIL The number of Interlata call attempts that failed on the reporting call agent

CALLP_INTERLA_SUCC The number of Interlata call attempts that completed successfully on the reporting call agent

CALLP_INTERLA_ABAND The number of Interlata call origination attempts that were abandoned on the reporting call agent

CALLP_INTRALA_ATTMP The number of Intralata call attempts on the reporting call agent

CALLP_INTRALA_FAIL The number of Intralata call attempts that failed on the reporting call agent

CALLP_INTRALA_SUCC The number of Intralata call attempts that completed successfully on the reporting call agent

CALLP_INTRALA_ABAND The number of Intralata call origination attempts that were abandoned on the reporting call agent

CALLP_INTL_ATTMP The number of International call attempts on the reporting call agent

CALLP_INTL_FAIL The number of International call attempts that failed on the reporting call agent

CALLP_INTL_SUCC The number of International call attempts that completed successfully on the reporting call agent




OL-4495-04


CALLP_INTL_ABAND The number of International call origination attempts that were abandoned on the reporting call agent

CALLP_EMGNCY_ATTMP The number of Emergency call attempts on the reporting call agent

CALLP_EMGNCY_FAIL The number of Emergency call attempts that failed on the reporting call agent

CALLP_EMGNCY_CALL_SUCC

The number of Emergency call attempts that completed successfully on the reporting call agent

CALLP_EMGNCY_CALL_ABAND

The number of Emergency call origination attempts that were abandoned on the reporting call agent

CALLP_LOCAL_ATTMP The number of Local call attempts on the reporting call agent

CALLP_LOCAL_FAIL The number of Local call attempts that failed on the reporting call agent

CALLP_LOCAL_SUCC The number of Local call attempts that completed successfully on the reporting call agent

CALLP_LOCAL_ABAND The number of Local call origination attempts that were abandoned on the reporting call agent

CALLP_TOLL_FREE_ATTMP The number of Toll Free call attempts on the reporting call agent

CALLP_TOLL_FREE_FAIL The number of Toll Free call attempts that failed on the reporting call agent

CALLP_TOLL_FREE_SUCC The number of Toll Free call attempts that completed successfully on the reporting call agent

CALLP_TOLL_FREE_ABAND The number of Toll Free call origination attempts that were abandoned on the reporting call agent

CALLP_H323_ORIG_ATTMP The number of originating H323 call attempts on the reporting call agent

CALLP_H323_TERM_ATTMP The number of terminating H323 call attempts on the reporting call agent

CALLP_H323_ORIG_FAIL The number of originating H323 call attempts that failed on the reporting call agent

CALLP_H323_TERM_FAIL The number of terminating H323 call attempts that failed on the reporting call agent

CALLP_H323_CALL_SUCC The number of originating and terminating H323 call attempts that completed successfully on the reporting call agent

CALLP_H323_CALL_ABAND The number of terminating and originating H323 call attempts that were abandoned on the reporting call agent

CALLP_ISDN_H323_CALL The total number of successfully completed calls from an ISDN originator to an H323 terminator on the reporting call agent

CALLP_SS7_H323_CALL The total number of successfully completed calls from an SS7 originator to an H323 terminator on the reporting call agent

CALLP_SIP_H323_CALL The total number of successfully completed calls from a SIP originator to an H323 terminator on the reporting call agent

CALLP_MGCP_H323_CALL The total number of successfully completed calls from an MGCP originator to an H323 terminator on the reporting call agent

CALLP_CAS_H323_CALL The total number of successfully completed calls from a CAS originator to an H323 terminator on the reporting call agent

CALLP_H323_SIP_CALL The total number of successfully completed calls from an H323 originator to a SIP terminator on the reporting call agent




OL-4495-04


CALLP_H323_ISDN_CALL The total number of successfully completed calls from an H323 originator to an ISDN terminator on the reporting call agent

CALLP_H323_SS7_CALL The total number of successfully completed calls from an H323 originator to an SS7 terminator on the reporting call agent

CALLP_H323_MGCP_CALL The total number of successfully completed calls from an H323 originator to an MGCP terminator on the reporting call agent

CALLP_H323_CAS_CALL The total number of successfully completed calls from an H323 originator to a CAS terminator on the reporting call agent

CALLP_H323_H323_CALL The total number of successfully completed calls from an H323 originator to an H323 terminator on the reporting call agent

CALLP_NAS_AUTH_SUCC The total number of successful NAS Authentication Requests on the reporting call agent

CALLP_NAS_AUTH_FAIL The total number of failed NAS Authentication Requests on the reporting call agent

CALLP_NAS_OP_FAIL The total number of operation failures that occurred on the reporting call agent - typically indicative of a modem failure

CALLP_NAS_ISP_PORT_LIMIT The total number of NAS calls that failed on the reporting call agent due to the port limit of a modem being exceeded

CALLP_NAS_NO_MODEMS The total number of NAS calls that failed on the reporting call agent due to the unavailability of a modem

CALLP_NAS_CLG_UNACC The total number of NAS calls that failed on the reporting call agent due to the calling party number being blocked

CALLP_NAS_CLD_UNACC The total number of NAS calls that failed on the reporting call agent due to the called party number being blocked

CALLP_NAS_USER_REQUEST The total number of User Requests - Reason Code 801 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_LOST_CARRIER The total number of Lost Carrier - Reason Code 802 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_LOST_SERVICE The total number of Lost Service - Reason Code 803 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_IDLE_TIMEOUT The total number of Idle Timeout - Reason Code 804 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_SESSION_TIMEOUT

The total number of Session Timeout - Reason Code 805 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_ADMIN_RESET The total number of Admin Reset - Reason Code 806 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_ADMIN_REBOOT The total number of Admin Reboot - Reason Code 807 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_PORT_ERROR The total number of Port Error- Reason Code 808 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_NAS_ERROR The total number of NAS Error- Reason Code 809 - that are received in the DLCX messages on the reporting call agent




OL-4495-04


MGCP Adapter MeasurementsTable 10-3 lists measurements for the MGCP Adapter.

CALLP_NAS_NAS_REQUEST The total number of NAS Request - Reason Code 810 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_NAS_REBOOT The total number of NAS Reboot- Reason Code 811 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_PORT_UNNEEDED

The total number of Port Unneeded - Reason Code 812 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_PORT_PREEMPTED

The total number of Port Pre-empted - Reason Code 813 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_PORT_SUSPENDED

The total number of Port Suspended - Reason Code 814 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_SERVICE_UNAVAIL

The total number of Service Unavailable - Reason Code 815 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_CALLBACK The total number of NAS Callback - Reason Code 816 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_USER_ERROR The total number of User Error - Reason Code 817 - that are received in the DLCX messages on the reporting call agent

CALLP_NAS_HOST_REQUEST The total number of Host Request - Reason Code 818 - that are received in the DLCX messages on the reporting call agent

CALLP_IVR_NETWORK_REQ The total number of requests for network based IVR service on the reporting call agent

Note This counter appears in release 4.4.0, but not 4.4.1.

CALLP_IVR_NATIVE_REQ The total number of requests for native IVR service on the reporting call agent


CALLP_IVR_RESOURCE_FAIL The total number of IVR sessions that could not be established on the reporting call agent


CALLP_IVR_OPERATION_FAIL The total number of IVR sessions that were established on the reporting call agent, but the actual IVR operation failed





OL-4495-04


Table 10-3 MGCP Adapter Measurements


MGCP_DECODE_ERROR The number of MGCP messages received that failed decoding on the reporting call agent

MGCP_ENCODE_ERROR The number of MGCP messages to be sent that failed encoding on the reporting call agent

MGCP_UNREACHABLE The number of MGCP messages sent from the reporting call agent that failed due to the target gateway being unreachable

MGCP_SEND_FAILED The number of MGCP messages sent from the reporting call agent that failed while being sent to the target gateway

MGCP_CRCX_ACK_RX The number of MGCP CRCX acknowledgement messages received by the reporting call agent

MGCP_CRCX_NACK_RX The number of MGCP CRCX non-acknowledgement messages received by the reporting call agent

MGCP_CRCX_TX The number of MGCP CRCX messages sent by the reporting call agent

MGCP_MDCX_ACK_RX The number of MGCP MDCX acknowledgement messages received by the reporting call agent

MGCP_MDCX_NACK_RX The number of MGCP MDCX non-acknowledgement messages received by the reporting call agent

MGCP_MDCX_TX The number of MGCP MDCX messages sent by the reporting call agent

MGCP_DLCX_RX The number of MGCP DLCX messages received from gateways by the reporting call agent

MGCP_DLCX_TX The number of MGCP DLCX messages sent by the reporting call agent

MGCP_DLCX_ACK_RX The number of MGCP DLCX acknowledgement messages received by the reporting call agent

MGCP_DLCX_NACK_RX The number of MGCP DLCX non-acknowledgement messages received by the reporting call agent

MGCP_RQNT_ACK_RX The number of MGCP RQNT acknowledgement messages received by the reporting call agent

MGCP_RQNT_NACK_RX The number of MGCP RQNT non-acknowledgement messages received by the reporting call agent

MGCP_RQNT_TX The number of MGCP RQNT messages sent by the reporting call agent

MGCP_AUEP_ACK_RX The number of MGCP AUEP acknowledgement messages received by the reporting call agent

MGCP_AUEP_NACK_RX The number of MGCP AUEP non-acknowledgement messages received by the reporting call agent

MGCP_AUEP_TX The number of MGCP AUEP messages sent by the reporting call agent

MGCP_NTFY_RX The number of MGCP NTFY messages received from gateways by the reporting call agent

MGCP_RSIP_RX The number of MGCP RSIP messages received from gateways by the reporting call agent

MGCP_RSIP_ACK_TX The number of MGCP RSIP acknowledgement messages sent by the reporting call agent


OL-4495-04


Session Initiation Protocol MeasurementsTable 10-4 lists measurements for the Session Initiation Protocol (SIP). These counters are common to several reporting types including: SIM, AIN-SVC, POTS-MISC, and SIA.

Table 10-4 Session Initiation Protocol (SIP) Measurements


SIP_TOTAL_INCOM_MSG The number of SIP messages the reporting call agent or feature server attempted to receive

SIP_TOTAL_SUCC_INCOM_MSG The number of SIP messages the reporting call agent or feature server successfully received

SIP_TOTAL_OUTG_MSG_ATTMP The number of SIP messages the reporting call agent or feature server attempted to send

SIP_TOTAL_SUCC_OUTG_MSG The number of SIP messages the reporting call agent or feature server successfully sent

SIP_REQ_RETRAN_RX The number of SIP request retransmission messages the reporting call agent or feature server received

SIP_REQ_RETRAN_TX The number of SIP request retransmission messages the reporting call agent or feature server sent

SIP_RSP_RETRAN_RX The number of SIP response retransmission messages the reporting call agent or feature server received

SIP_RSP_RETRAN_TX The number of SIP response retransmission messages the reporting call agent or feature server sent

SIP_T1_TIMER_EXPIRED The number of SIP T1 Timer expirations that occurred on the reporting call agent or feature server received over the collection interval

SIP_T2_TIMER_REACHED The number of SIP T2 Timer expirations that occurred on the reporting call agent or feature server received over the collection interval

SIP_INVITE_RX The number of SIP INVITE messages the reporting call agent or feature server received

SIP_INVITE_TX The number of SIP INVITE messages the reporting call agent or feature server sent

SIP_CANCEL_RX The number of SIP CANCEL messages the reporting call agent or feature server received

SIP_CANCEL_TX The number of SIP CANCEL messages the reporting call agent or feature server sent

SIP_BYE_RX The number of SIP BYE messages the reporting call agent or feature server received

SIP_BYE_TX The number of SIP BYE messages the reporting call agent or feature server sent

SIP_ACK_RX The number of SIP ACK messages the reporting call agent or feature server received

SIP_ACK_TX The number of SIP ACK messages the reporting call agent or feature server sent

SIP_OPTIONS_RX The number of SIP OPTIONS messages the reporting call agent or feature server received

SIP_OPTIONS_TX The number of SIP OPTIONS messages the reporting call agent or feature server sent


OL-4495-04


SIP_REGISTER_RX The number of SIP REGISTER messages the reporting call agent or feature server received

SIP_REGISTER_TX The number of SIP REGISTER messages the reporting call agent or feature server sent

SIP_INFO_RX The number of SIP INFO messages the reporting call agent or feature server received

SIP_INFO_TX The number of SIP INFO messages the reporting call agent or feature server sent

SIP_NOTIFY_RX The number of SIP NOTIFY messages the reporting call agent or feature server received

SIP_NOTIFY_TX The number of SIP NOTIFY messages the reporting call agent or feature server sent

SIP_100_RX The number of 100 class (TRYING) messages the reporting call agent or feature server received

SIP_100_TX The number of 100 class (TRYING) messages the reporting call agent or feature server sent

SIP_18x_RX The number of 18x class (INFORMATIONAL) messages the reporting call agent or feature server received

SIP_18x_TX The number of 18x class (INFORMATIONAL) messages the reporting call agent or feature server sent

SIP_200_RX The number of 200 class (SUCCESS) messages the reporting call agent or feature server received

SIP_200_TX The number of 200 class (SUCCESS) messages the reporting call agent or feature server sent

SIP_3xx_RX The number of 3xx class (REDIRECTION) messages the reporting call agent or feature server received

SIP_3xx_TX The number of 3xx class (REDIRECTION) messages the reporting call agent or feature server sent

SIP_4xx_RX The number of 4xx class (REQUEST FAILURES) messages the reporting call agent or feature server received

SIP_4xx_TX The number of 4xx class (REQUEST FAILURES) messages the reporting call agent or feature server sent

SIP_5xx_RX The number of 5xx class (SERVER FAILURES) messages the reporting call agent or feature server received

SIP_5xx_TX The number of 5xx class (SERVER FAILURES) messages the reporting call agent or feature server sent

SIP_6xx_RX The number of 6xx class (GLOBAL FAILURES) messages the reporting call agent or feature server received

SIP_6xx_TX The number of 6xx class (GLOBAL FAILURES) messages the reporting call agent or feature server sent

SIP_7xx_RX The number of 7xx class (RESERVED) messages the reporting call agent or feature server received

Table 10-4 Session Initiation Protocol (SIP) Measurements (continued)



OL-4495-04


Service Interaction Manager MeasurementsTable 10-5 lists measurements for the Service Interaction Manager Measurements (SIM).

SIP_7xx_TX The number of 7xx class (RESERVED) messages the reporting call agent or feature server sent

SIP_PROV_RSP_RETRAN_RX The number of SIP provisioning response retransmission messages the reporting call agent or feature server received

SIP_PROV_RSP_RETRAN_TX The number of SIP provisioning response retransmission messages the reporting call agent or feature server sent

SIP_PRACK_RX The number of SIP PRACK messages the reporting call agent or feature server received

SIP_PRACK_TX The number of SIP PRACK messages the reporting call agent or feature server sent

SIP_SUBSCRIBE_RX The number of SIP SUBSCRIBE messages the reporting call agent or feature server received

SIP_SUBSCRIBE_TX The number of SIP SUBSCRIBE messages the reporting call agent or feature server sent

SIP_REFER_RX The number of SIP REFER messages the reporting call agent or feature server received

SIP_REFER_TX The number of SIP REFER messages the reporting call agent or feature server sent

SIP_REFER_W_REPLACES_RX The number of SIP REFER with REPLACES messages the reporting call agent or feature server received

SIP_INVITE_REPLACES_TX The number of SIP INVITE REPLACES messages the reporting call agent or feature server sent

SIP_INVITE_REPLACES_RX The number of SIP INVITE REPLACES messages the reporting call agent or feature server received

SIP_REL100_RX The number of REL100 class (TRYING) messages the reporting call agent or feature server received

SIP_REL100_TX The number of REL100 class (TRYING) messages the reporting call agent or feature server sent

SIP_UNSUPPORTED_RX The number of unsupported SIP messages the reporting call agent or feature server received

SIP_UPDATE_RX The number of SIP UPDATE messages the reporting call agent or feature server received

SIP_UPDATE_TX The number of SIP UPDATE messages the reporting call agent or feature server sent

Table 10-4 Session Initiation Protocol (SIP) Measurements (continued)



OL-4495-04


POTS Local Feature Server MeasurementsTable 10-6 lists local POTS measurements.

Table 10-5 Service Interaction Manager Measurements


SIM_BCM_MSG The number of messages received by call processing from a feature server in the reporting call agent

SIM_RELATIONS The number of TDP-Rs received from call processing by SIM in the reporting call agent

SIM_TDP_N The number of Trigger Detection Point messages received from call processing in the reporting call agent that do not require a response from the target feature server

SIM_TDP_R The number of Trigger Detection Point messages received from call processing in the reporting call agent that do require a response from the target feature server

SIM_EDP_N The number of Event Detection Point messages received from call processing in the reporting call agent that do not require a response from the target feature server

SIM_EDP_R The number of Event Detection Point messages received from call processing in the reporting call agent that do require a response from the target feature server

SIM_INSTRUCT The number of INSTRUCT messages sent to feature servers by the reporting call agent

SIM_INSTRUCT_RSP The number of INSTRUCT messages received from feature servers by the reporting call agent

SIM_TERMINATE_RX The number of TERMINATE messages received from feature servers by the reporting call agent

SIM_TERMINATE_TX The number of TERMINATE messages sent to feature servers by the reporting call agent

SIM_FS_MSG_TX The number of FCP messages sent to feature servers by the reporting call agent

SIM_FS_MSG_RX The number of FCP messages received from feature servers by the reporting call agent

SIM_FS_PING_MSG_TX The number of PING messages sent to feature servers by the reporting call agent

SIM_FS_PING_NO_RSP_FAULTY The number of times no response was received from the target feature server when sent a PING message by the reporting call agent

SIM_FS_RESTART_MSG_TX The number of RESTART messages sent to feature servers by the reporting call agent

SIM_FS_ASYNC_MSG_TX The number of ASYNC messages sent to feature servers by the reporting call agent

Table 10-6 Local POTS Local Measurements


POTS_CFU_ACT_ATTMP The number of Call Forward Unconditional activation attempts on the reporting feature server

POTS_CFU_DEACT_ATTMP The number of Call Forward Unconditional deactivation attempts on the reporting feature server


OL-4495-04


POTS_CFU_ACT_REFUSED The number of Call Forward Unconditional activation attempts refused on the reporting feature server

POTS_CFU_ACT_ANSWERED The number of Call Forward Unconditional activation attempts answered by the called party on the reporting feature server

POTS_CFU_ACT_SECOND The number of Call Forward Unconditional second activation attempts on the reporting feature server

POTS_CFU_FORWARD_FAIL The number of Call Forward Unconditional service instances that failed on the reporting feature server

POTS_CFU_FORWARD_SUCC The number of Call Forward Unconditional service instances that succeeded on the reporting feature server

POTS_CFB_ACT_ATTMP The number of Call Forward Busy activation attempts on the reporting feature server

POTS_CFB_DEACT_ATTMP The number of Call Forward Busy deactivation attempts on the reporting feature server

POTS_CFB_ACT_REFUSED The number of Call Forward Busy activation attempts refused on the reporting feature server

POTS_CFB_FORWARD_FAIL The number of Call Forward Busy service instances that failed on the reporting feature server

POTS_CFB_FORWARD_SUCC The number of Call Forward Busy service instances that succeeded on the reporting feature server

POTS_CFNA_ACT_ATTMP The number of Call Forward No Answer activation attempts on the reporting feature server

POTS_CFNA_DEACT_ATTMP The number of Call Forward No Answer deactivation attempts on the reporting feature server

POTS_CFNA_ACT_REFUSED The number of Call Forward No Answer activation attempts refused on the reporting feature server

POTS_CFNA_FORWARD_FAIL The number of Call Forward No Answer service instances that failed on the reporting feature server

POTS_CFNA_FORWARD_SUCC The number of Call Forward No Answer service instances that succeeded on the reporting feature server

POTS_CW_ATTMP The number of Call Waiting service instance attempts on the reporting feature server

POTS_CW_ANSWERED The number of Call Waiting service instance attempts answered by the called party on the reporting feature server

POTS_CW_NOT_ANSWERED The number of Call Waiting service instance attempts not answered by the called party on the reporting feature server

POTS_CW_REJECT_NO_RSRC The number of Call Waiting service instance attempts that were rejected due to a lack of available resources on the reporting feature server

POTS_CW_REJECTE_INTERACT

The number of Call Waiting service instance attempts that were rejected due to feature interactions on the reporting feature server

POTS_CCW_ATTMP The number of Cancel Call Waiting attempts on the reporting feature server

POTS_CCW_REJECT_NO_RSRC

The number of Cancel Call Waiting attempts that were rejected due to a lack of available resources on the reporting feature server

Table 10-6 Local POTS Local Measurements (continued)



OL-4495-04


POTS_CCW_REJECT_BY_CCW The number of Cancel Call Waiting attempts that were rejected due to Call Waiting not already being active on the reporting feature server

POTS_CCW_LENGTH The total time in subscriber-seconds that Cancel Call WAITING was active on the reporting feature server

POTS_CHD_ATTMP The number of Call Hold service instance attempts on the reporting feature server

POTS_CHD_ANSWER The number of Call Hold service instance attempts resulting in reconnection on the reporting feature server

POTS_CHD_NOT_ANSWER The number of Call Hold service instance attempts that were not reconnected on the reporting feature server

POTS_CHD_REJECT_NO_RSRC The number of Call Hold service instance attempts that were rejected due to a lack of available resources on the reporting feature server

POTS_CHD_REJECT_INTERACT

The number of Call Hold service instance attempts that were rejected due to feature interactions on the reporting feature server

POTS_MDC_ATTMP The number of Mid Call Trigger attempts made by subscribers on the reporting feature server

POTS_MDC_REJECT_NO_RSRC

The number of Mid Call Trigger attempts made by subscribers that were rejected due to a lack of available resources on the reporting feature server

POTS_MDC_REJECT_INTERACT

The number of Mid Call Trigger attempts made by subscribers that were rejected due to feature interactions on the reporting feature server

POTS_MDC_REJECT_OTHERS The number of Mid Call Trigger attempts made by subscribers that were rejected due to unknown reasons on the reporting feature server

POTS_CT_ATTMP The number of Call Transfer service instance attempts on the reporting feature server

POTS_CT_ANSWER The number of Call Transfer service instance attempts answered by the called party on the reporting feature server

POTS_CT_TRANSFER The number of Call Transfer service instance attempts resulting in a successfully transferred call on the reporting feature server

POTS_CT_CONF The number of Call Transfer service instance attempts resulting in a successfully setup conference call on the reporting feature server

POTS_CT_FAIL The number of Call Transfer service instance attempts that failed on the reporting feature server

POTS_TWC_ATTMP The number of Three Way Call service instance attempts on the reporting feature server

POTS_TWC_ANSWERED The number of Three Way Call service instance attempts answered by the called party on the reporting feature server

POTS_TWC_CONF The number of Three Way Call service instance attempts resulting in a successfully setup conference call on the reporting feature server

POTS_TWC_FAIL The number of Three Way Call service instance attempts that failed on the reporting feature server

POTS_DRCW_ATTMP The number of Distinctive Ring Call Waiting service instance attempts on the reporting feature server

POTS_DRCW_REJECT_NO_RSRC

The number of Distinctive Ring Call Waiting attempts that were rejected due to a lack of available resources on the reporting feature server




OL-4495-04


POTS_DRCW_SUCC The number of Distinctive Ring Call Waiting attempts that were successful on the reporting feature server

POTS_RACF_ATTMP The number of Remote Activation Call Forward attempts on the reporting feature server

POTS_RACF_REFUSE The number of Remote Activation Call Forward service instances refused by the reporting feature server

POTS_RACF_REJECT_NO_RSRC

The number of Remote Activation Call Forward service instances refused due to a lack of available resources on the reporting feature server

POTS_RACF_CFU_ACT The number of Remote Activation Call Forward activation attempts that were successful on the reporting feature server

POTS_RACF_CFU_DEACT The number of Remote Activation Call Forward deactivation attempts that were successful on the reporting feature server

POTS_RACF_CFU_UNCHANGED

The number of Remote Activation Call Forward service instances that were successful but resulted in no change to the forwarding-to number on the reporting feature server

POTS_RACF_PIN_ATTMP The number of Remote Activation Call Forward PIN input attempts on the reporting feature server

POTS_RACF_PIN_REFUSE The number of Remote Activation Call Forward PIN input attempts that were refused on the reporting feature server

POTS_RACF_PIN_REJECT_NO_RSRC

The number of Remote Activation Call Forward PIN input attempts that were refused due to a lack of resources on the reporting feature server

POTS_RACF_PIN_CHANGE The number of Remote Activation Call Forward PIN input attempts that resulted in a change to the previous PIN for that subscriber on the reporting feature server

POTS_RACF_PIN_UNCHANGE The number of Remote Activation Call Forward PIN input attempts that resulted in no change to the previous PIN for that subscriber on the reporting feature server

POTS_CPRK_SUCC_ATTMP The number of Call Park Attempts that were successful during the collection interval

POTS_CPRK_FAIL_ATTMP The number of Call Park Attempts that failed during the collection interval

POTS_CPRK_SUCC_RET_ATTMP

The number of Call Park Retrieval Attempts that were successful during the collection interval

POTS_CPRK_FAIL_RET_ATTMP

The number of Call Park Retrieval Attempts that failed during the collection interval

POTS_CPRK_FORWARD The number of Call Park Attempts to forward a call during the collection interval

POTS_CPRK_CLEAR The number of Call Park Attempts to clear during the collection interval

POTS_SC_1_DIGIT_ATTMP The number of Speed Call 1 digit attempts during the collection interval

POTS_SC_2_DIGIT_ATTMP The number of Speed Call 2 digit attempts during the collection interval

POTS_SC_SUCC_CCSC The number of CCSC successful attempts during the collection interval

POTS_DND_ACT_SUCC The number of Do Not Disturb activation attempts during the collection interval

POTS_DND_ACT_FAIL The number of Do Not Disturb deactivation attempts during the collection interval

POTS_DND_DEACT_SUCC The number of Do Not Disturb activation attempts that failed due to a lack of resources during the collection interval

POTS_DND_DEACT_ FAIL The number of Do Not Disturb deactivation attempts during the collection interval




OL-4495-04


POTS_DND_REJECT The number of Do Not Disturb activation attempts that were successful during the collection interval

POTS_RC_SUCC The number of Return Call attempts that were successful during the collection interval

POTS_CWD_ATTMP The number of Call Waiting Deluxe service instance attempts on the reporting feature server

POTS_CWD_ANSWER The number of Call Waiting Deluxe service instance attempts answered by the called party on the reporting feature server

POTS_CWD_ACT_SUCC The number of Call Waiting Deluxe successful service activation attempts on the reporting feature server

POTS_CWD_ACT_FAIL The number of Call Waiting Deluxe unsuccessful service activation attempts on the reporting feature server

POTS_CWD_DEACT_SUCC The number of Call Waiting Deluxe successful service deactivation attempts on the reporting feature server

POTS_CWD_DEACT_FAIL The number of Call Waiting Deluxe unsuccessful service deactivation attempts on the reporting feature server

POTS_CWD_INTERROG_SUCC The number of Call Waiting Deluxe successful service interrogation attempts on the reporting feature server

POTS_CWD_INTERROG_FAIL The number of Call Waiting Deluxe unsuccessful service interrogation attempts on the reporting feature server

POTS_TWCD_ATTMP The number of Three Way Calling Deluxe service instance attempts on the reporting feature server. Incremented when a subscriber in a stable two-way call presses flash button followed by DN of a third party

POTS_TWCD_CONF The number of Three Way Calling Deluxe service instance conferencing attempts on the reporting feature server. Incremented when a subscriber attempts to bridge all three parties (flash button followed by digit 3)

POTS_OCB_LOCAL_BLOCK The number of local calls that were blocked on the reporting feature server via Outward Call Barring

POTS_OCB_NATL_BLOCK The number of national calls that were blocked on the reporting feature server via Outward Call Barring

POTS_OCB_INTL_BLOCK The number of international calls that were blocked on the reporting feature server via Outward Call Barring

POTS_OCB_INVOCATION The number of Outward Call Barring invocation attempts on the reporting feature server

POTS_OCB_ACT_SUCC The number of Outward Call Barring successful activation attempts on the reporting feature server

POTS_OCB_DEACT_SUCC The number of Outward Call Barring successful deactivation attempts on the reporting feature server

POTS_OCB_INTERROG_SUCC The number of Outward Call Barring successful interrogation attempts on the reporting feature server

POTS_OCB_INVALID_PASSWORD

The number of Outward Call Barring attempts that were unsuccessful due to invalid password entry by the user on the reporting feature server




OL-4495-04


POTS Miscellaneous Feature Server MeasurementsTable 10-7 lists the miscellaneous POTS measurements.

POTS_CFU_INTERROG_ATTMP

The number of Call Forward Unconditional interrogation attempts on the reporting feature server

POTS_CFB_INTERROG_ ATTMP

The number of Call Forward Busy interrogation attempts on the reporting feature server

POTS_CFNA_INTERROG_ ATTMP

The number of Call Forward No Answer interrogation attempts on the reporting feature server

POTS_CNDB_ATTMP The number of Calling Number Delivery Blocking attempts made on the reporting feature server

POTS_CNAB_ATTMP The number of Calling Name Delivery Blocking attempts made on the reporting feature server

POTS_CIDS_ATTMP The number of Calling Identity Delivery attempts made on the reporting feature server

POTS_CIDSS_ATTMP The number of Calling Identity Delivery Suppression attempts made on the reporting feature server

POTS_REFER_ATTMP The number of REFER attempts made on the reporting feature server

POTS_REFER_FAIL The number of REFER failed attempts made on the reporting feature server

POTS_REFER_SUCC The number of REFER successful attempts made on the reporting feature server

POTS_TOTAL_CNAM_QUERY The number of CNAM translation queries attempted on the reporting feature server

POTS_EXT_CNAM_QUERY The number of CNAM translation queries that resulted in an external query to a network database attempted on the reporting feature server

POTS_EXT_CNAM_QUERY_SUCC

The number of CNAM translation queries that resulted in a successful external query to a network database attempted on the reporting feature server

POTS_EXT_CNAM_FAIL_APP The number of CNAM translation queries that resulted in a failed external query to a network database due to an application failure from the reporting feature server

POTS_EXT_CNAM_FAIL_NETW

The number of CNAM translation queries that resulted in a failed external query to a network communication failure from the reporting feature server



Table 10-7 Miscellaneous POTS Measurements


POTS_HOTLINE_ATTMP The number of Hotline service instance attempts on the reporting feature server

POTS_WARMLINE_ATTMP The number of Warmline service instance attempts on the reporting feature server

POTS_BLV_ATTMP The number of Busy Line Verification service instance attempts on the reporting feature server

POTS_OP_INTERRUPT_ATTMP The number of Operator Interrupt service instance attempts on the reporting feature server


OL-4495-04


POTS_CTX_SFG_OVERFLOW The number of Centrex SFG counters that overflowed during the collection interval on the reporting feature server

POTS_HOTV_ATTMP The number of successful Hotline Variable instance attempts on the reporting feature server

POTS_HOTV_ACT_SUCC The number of successful Hotline Variable activation attempts on the reporting feature server

POTS_HOTV_DEACT_SUCC The number of successful Hotline Variable deactivation attempts on the reporting feature server

POTS_HOTV_INTERROG_SUCC The number of successful Hotline Variable interrogation attempts on the reporting feature server

POTS_LCD_AUTH_ATTMP The number of authorization attempts made for Limited Call Duration feature


POTS_LCD_AUTH_SUCC The number of successful authorization attempts made for Limited Call Duration feature invocations on the reporting feature server


POTS_LCD_AUTH_FAIL The number of unsuccessful authorization attempts made for Limited Call Duration feature invocations on the reporting feature server


POTS_LCD_REAUTH_FAIL The number of unsuccessful re-authorization attempts made for Limited Call Duration feature invocations on the reporting feature server


POTS_LCD_FORCED_DISC The number of forced call disconnections made for Limited Call Duration calls on the reporting feature server


Table 10-7 Miscellaneous POTS Measurements (continued)



OL-4495-04


POTS Class of Service Feature Server MeasurementsTable 10-8 lists the POTS class of service (COS) measurements.

Table 10-8 POTS Class of Service Measurements


POTS_COS_ANI_ATTMP_SUCC The number of Automatic Number Identification directory number lookups that were successfully attempted on the reporting feature server.

An ANI attempt is successful when the ANI DN is available on the reporting FS, and ANI status is allowed as per provisioning. In the case of casual calls, ALL ANI attempts are successful if the Casual Code is valid and allowed on reporting feature server.

POTS_COS_ANI_BLOCKED_CALL The number of calls that were blocked based on Automatic Number Identification directory number lookups on the reporting feature server. In the case of Casual calls, ANI does also get blocked if Casual Codes are invalid.

POTS_COS_NANP_BLOCKED_BW The number of NANP based calls that were blocked due to a match on a black list or an exclusion from a white list on the reporting feature server

POTS_COS_INTL_BLOCKED_BW The number of International based calls that were blocked due to a match on a black list or an exclusion from a white list on the reporting feature server

POTS_COS_900_BLOCKED The number of calls denied due to subscriber based 900 restrictions on the reporting feature server

POTS_COS_976_BLOCKED The number of calls denied due to subscriber based 976 restrictions on the reporting feature server

POTS_COS_NANP_RESTRICT The number of calls denied due to subscriber based NANP restrictions on the reporting feature server

POTS_COS_INTL_RESTRICT Not currently used.

POTS_COS_CASUAL_RESTRICT The number of calls denied due to subscriber based casual dialing restrictions on the reporting feature server

POTS_COS_DA_BLOCKED The number of calls denied due to subscriber based directory assistance restrictions on the reporting feature server

POTS_COS_NANP_OP_BLOCKED The number of calls denied due to subscriber based NANP operator restrictions on the reporting feature server

POTS_COS_INTL_OP_BLOCKED The number of calls denied due to subscriber based international operator restrictions on the reporting feature server

POTS_COS_AUTH_CODE_SUCC The number of successful authentication code validations on the reporting feature server

POTS_COS_AUTH_CODE_FAIL The number of unsuccessful authentication code validations on the reporting feature server

POTS_COS_ACCT_CODE_SUCC The number of successful account code validations on the reporting feature server. Account codes do not get validated - any dialed account code entered by the user is considered valid - including an empty account code.

POTS_COS_ACCT_CODE_FAIL Not currently used.


OL-4495-04


POTS Screen List Editing Feature Server MeasurementsTable 10-9 lists the POTS screen list editing (SLE) measurements.

POTS Customer Originated Trace Feature Server MeasurementsTable 10-10 lists the POTS customer originated trace (COT) measurements.

Table 10-9 POTS Screen List Editing Measurements


POTS_SCR_ATTMP The number of Selective Call Rejection service instance attempts on the reporting feature server

POTS_SCA_ATTMP The number of Selective Call Acceptance service instance attempts on the reporting feature server

POTS_SCR_REJECT_NO_RSRC The number of Selective Call Rejection attempts made by subscribers that were rejected due to a lack of available resources on the reporting feature server

POTS_SCA_REJECT_NO_RSRC The number of Selective Call Acceptance attempts made by subscribers that were rejected due to a lack of available resources on the reporting feature server

POTS_SCR_SUCC The number of Selective Call Rejection service instance attempts resulting in successful rejections of the call on the reporting feature server

POTS_SCA_SUCC The number of Selective Call Acceptance service instance attempts resulting in successful acceptance of the call on the reporting feature server

POTS_SCF_ATTMP The number of Selective Call Forwarding service instance attempts on the reporting feature server

POTS_SCF_REJECT_NO_RSRC The number of Selective Call Forwarding attempts that were rejected due to a lack of available resources on the reporting feature server

POTS_SCF_SUCC The number of Selective Call Forwarding attempts that were successful on the reporting feature server

Table 10-10 POTS Customer Originated Trace Measurements


POTS_COT_ACCESS The number of times the Caller Originated Trace star code was dialed by the subscriber (feature accesses and activations)

POTS_COT_DENY The number of times the Caller Originated Trace data was unsuccessfully accessed on the reporting feature server

POTS_COT_ACT Same as POTS_COT_ACCESS in this release. When 2-level COT (the digit “1” dialed) is available - this counter would include both those and the current 1-level activations tracked in POTS_COT_ACCESS.

POTS_COT_ABAND The number of Caller Originated Trace service activation abandonments that occurred on the reporting feature server


OL-4495-04


POTS Automatic Callback, Recall, and Call Return Feature Server Measurements

Table 10-11 lists the POTS automatic callback, recall, and call return (ACAR) measurements.

POTS_COT_DN_UNAVAIL The number of Caller Originated Trace service activation that failed due to the calling party directory number not be available on the reporting feature server

POTS_COT_TRACE_CONFIRM The number of Caller Originated Trace service instances that were successfully completed on the reporting feature server

POTS_COT_TRACE_OUTPUT The number of Caller Originated Trace service instances that were successfully completed and the data was stored persistently on the reporting feature server

Table 10-10 POTS Customer Originated Trace Measurements


Table 10-11 POTS Automatic Callback, Recall, and Call Return Measurements


POTS_AC_ACT_ATTMP The number of Automatic Callback service activation attempts on the reporting feature server

POTS_AC_OVERFLOW The number of Automatic Callback service activation attempts resulting in an overflow on the reporting feature server

POTS_AC_IMMEDIATE_PROC The number of Automatic Callback service activation attempts that resulted in immediate connection on the reporting feature server

POTS_AC_DELAYED_PROC The number of Automatic Callback service activation attempts that resulted in delayed connection on the reporting feature server

POTS_AC_DEACT_BY_SYSTEM The number of Automatic Callback service activation attempts that were deactivated by the system on the reporting feature server

POTS_AC_DEACT_ATTMP The number of Automatic Callback service activation attempts that were deactivated by the requesting subscriber on the reporting feature server

POTS_AC_INTERLATA_ATTMP The number of Automatic Callback service activation attempts performed on an interlata basis on the reporting feature server

POTS_AR_ACT_ATTMP The number of Automatic Recall service activation attempts on the reporting feature server

POTS_AR_OVERFLOW The number of Automatic Recall service activation attempts resulting in an overflow on the reporting feature server

POTS_AR_IMMEDIATE_PROC The number of Automatic Recall service activation attempts that resulted in immediate connection on the reporting feature server

POTS_AR_DELAYED_PROC The number of Automatic Recall service activation attempts that resulted in delayed connection on the reporting feature server


OL-4495-04


AIN Services Feature Server MeasurementsTable 10-12 lists the AIN services (AIN SVC) measurements.

POTS_AR_DEACT_BY_SYSTEM The number of Automatic Recall service activation attempts that were deactivated by the system on the reporting feature server

POTS_AR_DEACT_ATTMP The number of Automatic Recall service activation attempts that were deactivated by the requesting subscriber on the reporting feature server

POTS_AR_INTERLATA_ATTMP The number of Automatic Recall service activation attempts performed on an interlata basis on the reporting feature server

POTS_AR_2LEVEL_ACC_CODE_ATTMP

The number of Automatic Callback service activation attempts on the reporting feature server


POTS_AR_2LEVEL_ACT_CODE_ATTMP

The number of times the activation code (*69) is dialed for the two level Automatic Recall activation procedure on the reporting feature server


POTS_ACART_QUEUED_REQ The number of Automatic Callback and Automatic Recall service requests that were queued on the reporting feature server

POTS_ACART_TERM_SCAN_REQ The number of Automatic Callback and Automatic Recall service requests that were queued for terminators on the reporting feature server

POTS_ACART_ORIG_SCAN_REQ The number of Automatic Callback and Automatic Recall service requests that were queued for originators on the reporting feature server

POTS_ACART_REJECT_NO_RSRC The number of Automatic Callback and Automatic Recall service requests that were rejected due to a lack of resources on the reporting feature server

POTS_ACR_ACT_ATTMP The number of Anonymous Call Rejection activation attempts during the collection interval

POTS_ACR_DEACT_ATTMP The number of Anonymous Call Rejection deactivation attempts during the collection interval

POTS_ACR_ACT_REJECT_NO_RSRC The number of Anonymous Call Rejection activation attempts that failed due to a lack of resources during the collection interval

POTS_ACR_DEACT_ REJECT_NO_RSRC

The number of Anonymous Call Rejection deactivation attempts during the collection interval

POTS_ACR_SUCC The number of Anonymous Call Rejection attempts that were successful during the collection interval

Table 10-11 POTS Automatic Callback, Recall, and Call Return Measurements (continued)



OL-4495-04


Table 10-12 AIN Services Measurements


AINSVC_TOTAL_QUERY The total number of queries attempted on the reporting feature server

AINSVC_8XX_QUERY The number of 8XX translation queries attempted on the reporting feature server

AINSVC_EXT_8XX_QUERY The number of 8XX translation queries that resulted in an external query to a network database attempted on the reporting feature server

AINSVC_EXT_8XX_QUERY_SUCC The number of 8XX translation queries that resulted in a successful external query to a network database attempted on the reporting feature server

AINSVC_EXT_8XX_FAIL_APP The number of 8XX translation queries that resulted in a failed external query to a network database due to an application failure from the reporting feature server

AINSVC_EXT_8XX_FAIL_NETW The number of 8XX translation queries that resulted in a failed external query to a network database due to a network communication failure from the reporting feature server

AINSVC_LOC_8XX_QUERY The number of 8XX translation queries attempted to be processed locally on the reporting feature server

AINSVC_LOC_8XX_QUERY_SUCC The number of 8XX translation queries successfully processed locally on the reporting feature server

AINSVC_LOC_8XX_ANI_BLOCK The number of 8XX translation queries that were blocked due to ANI screening processed locally on the reporting feature server

AINSVC_LOC_8XX_II_BLOCK The number of 8XX translation queries that were blocked due to II screening processed locally on the reporting feature server

AINSVC_LOC_8XX_DNIS_SUCC The number of 8XX DNIS translation queries successfully processed locally on the reporting feature server

AINSVC_LOC_8XX_ROUTING_SUCC The number of 8XX routing translation queries successfully processed locally on the reporting feature server

AINSVC_LOC_8XX_REROUTE The number of 8XX translation queries successfully processed locally on the reporting feature server that resulted in re-routing

AINSVC_LOC_8XX_FAIL_APP The number of 8XX translation queries that resulted in a failure due to an application error on the reporting feature server

AINSVC_TOTAL_LNP_QUERY The number of LNP translation queries attempted on the reporting feature server

AINSVC_EXT_LNP_QUERY The number of LNP translation queries that resulted in an external query to a network database attempted on the reporting feature server

AINSVC_EXT_LNP_QUERY_SUCC The number of LNP translation queries that resulted in a successful external query to a network database attempted on the reporting feature server

AINSVC_EXT_LNP_FAIL_APP The number of LNP translation queries that resulted in a failed external query to a network database due to an application failure from the reporting feature server

AINSVC_EXT_LNP_FAIL_NETW The number of LNP translation queries that resulted in a failed external query to a network database due to a network communication failure from the reporting feature server

AINSVC_EXT_8XX_QUERY_FAIL The number of 8XX queries that failed due to an SCP timeout when attempted by the reporting feature server


OL-4495-04


TSA Protocol MeasurementsTable 10-13 lists the TSA protocol measurements.

AINSVC_EXT_LNP_QUERY_LRN The number of LNP queries that resulted in a successful response from the SCP with an LRN when attempted by the reporting feature server

AINSVC_EXT_LNP_QUERY_FAIL The number of LNP queries that failed due to an SCP timeout when attempted by the reporting feature server

Table 10-12 AIN Services Measurements (continued)


Table 10-13 TSA Measurements


TSA_OPERATION_REQ_RX The total number of operation request messages received on the reporting feature server

TSA_OPERATION_CONFIRM_RX The total number of operation confirm messages received on the reporting feature server

TSA_OPERATION_IND_RX The total number of operation indication messages received on the reporting feature server

TSA_COMPONENT_REQ_RX The total number of component request messages received on the reporting feature server

TSA_COMPONENT_CONFIRM_RX The total number of component confirm messages received on the reporting feature server

TSA_COMPONENT_IND_RX The total number of component indication messages received on the reporting feature server

TSA_DATA_IND_RX The total number of data indication messages received on the reporting feature server

TSA_UDATA_IND_RX The total number of data indication messages received on the reporting feature server

TSA_DATA_REQ_RX The total number of data request messages received on the reporting feature server

TSA_DELIMITER_REQ_RX The total number of delimiter request messages received on the reporting feature server

TSA_DELIMITER_IND_RX The total number of delimiter indication messages received on the reporting feature server

TSA_OPEN_IND_RX The total number of open indication messages received on the reporting feature server

TSA_OPEN_CONFIRM_RX The total number of open confirm messages received on the reporting feature server

TSA_STATUS_IND_RX The total number of status indication messages received on the reporting feature server

TSA_DIALOG_CONFIRM_RX The total number of dialog confirm messages received on the reporting feature server

TSA_CLOSE_IND_RX The total number of close indication messages received on the reporting feature server


OL-4495-04


SCCP Protocol MeasurementsTable 10-14 lists the SCCP protocol measurements.

TSA_ABORT_IND_RX The total number of abort indication messages received on the reporting feature server

TSA_TCAP_BIND_CONFIRM_RX The total number of TCAP bind confirm messages received on the reporting feature server

TSA_TCAP_STAT_CONFIRM_RX The total number of TCAP statistics confirm messages received on the reporting feature server

TSA_TCAP_NOTICE_IND_RX The total number of TCAP notice indication messages received on the reporting feature server

TSA_TCAP_STAT_IND_RX The total number of TCAP statistics indication messages received on the reporting feature server

TSA_INAP_NOTICE_IND_RX The total number of INAP notice indication messages received on the reporting feature server

TSA_INAP_STAT_IND_RX The total number of INAP statistics indication messages received on the reporting feature server

TSA_INAP_STAT_CONFIRM_RX The total number of INAP statistics confirm messages received on the reporting feature server

TSA_INAP_BIND_CONFIRM_RX The total number of INAP bind confirm messages received on the reporting feature server

Table 10-13 TSA Measurements (continued)


Table 10-14 SCCP Measurements


SCCP_NO_TRANS_ADDR_FAIL The total number of routing errors due to no translation for address of such nature on the reporting feature server

SCCP_NO_TRANS_SPEC_ADDR_FAIL The total number of routing errors due to no translation for this specific address on the reporting feature server

SCCP_NETWORK_FAIL The total number of routing errors due to a network failure from the point code being unavailable on the reporting feature server

SCCP_NETWORK_CONGEST_FAIL The total number of routing errors due to network congestion on the reporting feature server

SCCP_SUBSYS_FAIL The total number of routing errors due to a subsystem failure on the reporting feature server

SCCP_SUBSYS_CONGEST_FAIL The total number of routing errors due to subsystem congestion on the reporting feature server

SCCP_UNEQUIP_USER_FAIL The total number of routing errors due to an unequipped user on the reporting feature server


OL-4495-04


SCCP_HOP_COUNTER_FAIL The total number of routing errors due to a hop counter violation on the reporting feature server

SCCP_SYNTAX_ERR The total number of syntax errors on the reporting feature server

SCCP_UNKNOWN_FAIL The total number of routing errors due to an unknown reason on the reporting feature server

SCCP_TOTAL_UDATA_TX The total number of unit data sent on the reporting feature server

SCCP_TOTAL_UDATA_SVC_TX The total number of unit data service sent on the reporting feature server

SCCP_TOTAL_UDATA_RX The total number of unit data received on the reporting feature server

SCCP_TOTAL_UDATA_SVC_RX The total number of unit data service received on the reporting feature server

SCCP_TOTAL_EXT_UDATA_TX The total number of extended unit data sent on the reporting feature server

SCCP_TOTAL_EXT_UDATA_SVC_TX The total number of extended unit data service sent on the reporting feature server

SCCP_TOTAL_EXT_UDATA_RX The total number of extended unit data received on the reporting feature server

SCCP_TOTAL_EXT_UDATA_SVC_RX The total number of extended unit data service received on the reporting feature server

SCCP_TOTAL_LONG_UDATA_TX The total number of long unit data sent on the reporting feature server

SCCP_TOTAL_LONG_UDATA_SVC_TX The total number of long unit data service sent on the reporting feature server

SCCP_TOTAL_LONG_UDATA_RX The total number of long unit data received on the reporting feature server

SCCP_TOTAL_LONG_UDATA_SVC_RX The total number of long unit data service received on the reporting feature server

SCCP_TOTAL_MSG The total number of messages handled on the reporting feature server

SCCP_TOTAL_LOCAL_MSG The total number of messages intended for local subsystems on the reporting feature server

SCCP_TOTAL_GLOBAL_ADDR_TRAN The total number of messages requiring global address translation on the reporting feature server

SCCP_TOTAL_CLASS_0_TX The total number of class 0 messages sent on the reporting feature server

SCCP_TOTAL_CLASS_1_TX The total number of class 1 messages sent on the reporting feature server

SCCP_TOTAL_CLASS_0_RX The total number of class 0 messages received on the reporting feature server

SCCP_TOTAL_CLASS_1_RX The total number of class 1 messages received on the reporting feature server

SCCP_SUBSYS_OOS_REQ_GRANT The total number of subsystem out-of-service requests granted on the reporting feature server

SCCP_SUBSYS_OOS_REQ_DENY The total number of subsystem out-of-service requests denied on the reporting feature server

SCCP_MSG_TX_BACKUP_SUBSYS The total number of messages sent to a backup subsystem on the reporting feature server

SCCP_USAP_TOTAL_CLASS_0_TX The total number of class 0 messages sent on the reporting feature server

SCCP_USAP_TOTAL_CLASS_1_TX The total number of class 1 messages sent on the reporting feature server

SCCP_USAP_TOTAL_CLASS_0_RX The total number of class 0 messages received on the reporting feature server

Table 10-14 SCCP Measurements (continued)



OL-4495-04


TCAP Protocol MeasurementsTable 10-12 lists the TCAP protocol measurements.

SCCP_USAP_TOTAL_CLASS_1_RX The total number of class 1 messages received on the reporting feature server

SCCP_NSAP_ALLOW_MSG_RX The total number of subsystem allowed messages received on the reporting feature server

SCCP_NSAP_OOS_GRANT_RX The total number of subsystem out-of-service grant messages received on the reporting feature server

SCCP_NSAP_OOS_REQ_RX The total number of subsystem out-of-service request messages received on the reporting feature server

SCCP_NSAP_PROHIBIT_RX The total number of subsystem prohibited messages received on the reporting feature server

SCCP_NSAP_STAT_TEST_RX The total number of subsystem status test messages received on the reporting feature server

SCCP_NSAP_CONGEST_RX The total number of subsystem congested messages received on the reporting feature server

SCCP_NSAP_ALLOW_MSG_TX The total number of subsystem allowed messages sent on the reporting feature server

SCCP_ NSAP_OOS_GRANT_TX The total number of subsystem out-of-service grant messages sent on the reporting feature server

SCCP_ NSAP_OOS_REQ_TX The total number of subsystem out-of-service request messages sent on the reporting feature server

SCCP_ NSAP_PROHIBIT_TX The total number of subsystem prohibited messages sent on the reporting feature server

SCCP_ NSAP_STAT_TEST_TX The total number of subsystem status test messages sent on the reporting feature server

SCCP_NSAP_CONGEST_TX The total number of subsystem congested messages sent on the reporting feature server

Table 10-14 SCCP Measurements (continued)


Table 10-15 TCAP Measurements


TCAP_TOTAL_MSG_RX The total number of messages received by the reporting feature server

TCAP_TOTAL_MSG_TX The total number of messages sent by the reporting feature server

TCAP_TOTAL_UNI_MSG_RX The total number of unidirectional messages received by the reporting feature server

TCAP_TOTAL_UNI_MSG_TX The total number of unidirectional messages sent by the reporting feature server

TCAP_ABORT_MSG_RX The total number of abort messages received on the reporting feature server

TCAP_ABORT_MSG_TX The total number of abort messages sent by the reporting feature server


OL-4495-04


TCAP_BEGIN_MSG_RX The total number of begin messages received on the reporting feature server

TCAP_BEGIN_MSG_TX The total number of begin messages sent by the reporting feature server

TCAP_CONT_MSG_RX The total number of continue messages received on the reporting feature server

TCAP_CONT_MSG_TX The total number of continue messages sent by the reporting feature server

TCAP_END_MSG_RX The total number of end messages received on the reporting feature server

TCAP_END_MSG_TX The total number of end messages sent by the reporting feature server

TCAP_PERMISS_QUERY_RX The total number of query with permission messages received on the reporting feature server

TCAP_PERMISS_QUERY_TX The total number of query with permission messages sent by the reporting feature server

TCAP_NO_PERMISS_QUERY_RX The total number of query without permission messages received on the reporting feature server

TCAP_NO_PERMISS_QUERY_TX The total number of query without permission messages sent by the reporting feature server

TCAP_PERMISS_CONVERS_RX The total number of conversation with permission messages received on the reporting feature server

TCAP_PERMISS_CONVERS_TX The total number of conversation with permission messages sent by the reporting feature server

TCAP_NO_PERMISS_CONVERS_RX

The total number of conversation without permission messages received on the reporting feature server

TCAP_NO_PERMISS_CONVERS_TX

The total number of conversation without permission messages sent by the reporting feature server

TCAP_RSP_RX The total number of response messages received on the reporting feature server

TCAP_RSP_TX The total number of response messages sent by the reporting feature server

TCAP_TOTAL_COMP_RX The total number of components received on the reporting feature server

TCAP_TOTAL_COMP_TX The total number of components sent by the reporting feature server

TCAP_INVOKE_COMP_RX The total number of invoke components received on the reporting feature server

TCAP_INVOKE_COMP_TX The total number of invoke components sent by the reporting feature server

TCAP_RETURN_RESULT_COMP_RX

The total number of return-result components received on the reporting feature server

TCAP_RETURN_RESULT_COMP_TX

The total number of return-result components sent by the reporting feature server

TCAP_RETURN_ERR_COMP_RX The total number of return-error components received on the reporting feature server

TCAP_RETURN_ERR_COMP_TX The total number of return-error components sent by the reporting feature server

TCAP_REJECT_COMP_RX The total number of reject components received on the reporting feature server

TCAP_REJECT_COMP_TX The total number of reject components sent by the reporting feature server

TCAP_ACT_TRANSACTIONS The total number of active transactions on the reporting feature server

TCAP_ACT_INVOCATIONS The total number of active invocations on the reporting feature server

Table 10-15 TCAP Measurements (continued)



OL-4495-04


TCAP_TRANSACTION_IDS_INUSE

The total number of transaction ids in use on the reporting feature server

TCAP_TOTAL_DROPPED_MSG_RX

The total number of received messages dropped on the reporting feature server

TCAP_UNRECOG_MSG_TYPE_RX

The total number of unrecognized messages types received on the reporting feature server

TCAP_UNRECOG_MSG_TYPE_TX

The total number of unrecognized messages types sent by the reporting feature server

TCAP_INCORRECT_TRANS_PORT_RX

The total number of incorrect transaction portions received on the reporting feature server

TCAP_INCORRECT_TRANS_PORT_TX

The total number of incorrect transaction portions sent by the reporting feature server

TCAP_BAD_STRUCT_TRANS_PORT_RX

The total number of badly structured transaction portions received on the reporting feature server

TCAP_BAD_STRUCT_TRANS_PORT_TX

The total number of badly structured transaction portions sent by the reporting feature server

TCAP_UNRECOG_TRANS_ID_RX The total number of unrecognized transaction ids received on the reporting feature server

TCAP_UNRECOG_TRANS_ID_TX The total number of unrecognized transaction ids sent by the reporting feature server

TCAP_RSCR_LIMIT_RX The total number of resource limitations received on the reporting feature server

TCAP_RSCR_LIMIT_TX The total number of resource limitations sent by the reporting feature server

TCAP_TRANS_PORT_PERM_REL_RX

The total number of transaction portion permission to release problems received on the reporting feature server

TCAP_ TRANS_PORT_PERM_REL_TX

The total number of transaction portion permission to release problems sent by the reporting feature server

TCAP_UNRECOG_DIALOG_PORT_ID_RX

The total number of unrecognized dialog portion ids received on the reporting feature server

TCAP_UNRECOG_DIALOG_PORT_ID_TX

The total number of unrecognized dialog portion ids sent by the reporting feature server

TCAP_BAD_STRUCT_ DIALOG_PORT_RX

The total number of badly structured dialog portions received on the reporting feature server

TCAP_BAD_STRUCT_ DIALOG_PORT_TX

The total number of badly structured dialog portions sent by the reporting feature server

TCAP_MISSING_DIALOG_PORT_RX

The total number of missing dialog portions received on the reporting feature server

TCAP_MISSING_DIALOG_PORT_TX

The total number of missing dialog portions sent by the reporting feature server

TCAP_INCONSIST_DIALOG_PORT_RX

The total number of inconsistent dialog portions received on the reporting feature server

TCAP_INCONSIST_DIALOG_PORT_TX

The total number of inconsistent dialog portions sent by the reporting feature server




OL-4495-04


TCAP_UNRECOG_COMP_RX The total number of unrecognized components received on the reporting feature server

TCAP_UNRECOG_COMP_TX The total number of unrecognized components sent by the reporting feature server

TCAP_INCORRECT_COMP_PORT_RX

The total number of incorrect component portions received on the reporting feature server

TCAP_INCORRECT_COMP_PORT_TX

The total number of incorrect component portions sent by the reporting feature server

TCAP_BAD_STRUCT_ COMP_PORT_RX

The total number of badly structured component portions received on the reporting feature server

TCAP_BAD_STRUCT_ COMP_PORT_TX

The total number of badly structured component portions sent by the reporting feature server

TCAP_DUP_INVOKE_ID_RX The total number of duplicate invoke ids received on the reporting feature server

TCAP_DUP_INVOKE_ID_TX The total number of duplicate invoke ids sent by the reporting feature server

TCAP_UNRECOG_OPCODE_RX The total number of unrecognized opcodes received on the reporting feature server

TCAP_UNRECOG_OPCODE_TX The total number of unrecognized opcodes sent by the reporting feature server

TCAP_INCORRECT_PARAM_RX The total number of incorrect parameters received on the reporting feature server

TCAP_INCORRECT_PARAM_TX The total number of incorrect parameters sent by the reporting feature server

TCAP_UNRECOG_LINK_ID_RX The total number of unrecognized link ids received on the reporting feature server

TCAP_UNRECOG_LINK_ID_TX The total number of unrecognized link ids sent by the reporting feature server

TCAP_INIT_REL_RX The total number of initiating releases received on the reporting feature server

TCAP_INIT_REL_TX The total number of initiating releases sent by the reporting feature server

TCAP_UNEXPECT_LINK_RSP_RX

The total number of unexpected link responses received on the reporting feature server

TCAP_UNEXPECT_LINK_RSP_TX

The total number of unexpected link responses sent by the reporting feature server

TCAP_UNEXPECT_LINK_OPER_RX

The total number of unexpected link operations received on the reporting feature server

TCAP_UNEXPECT_LINK_OPER_TX

The total number of unexpected link operations sent by the reporting feature server

TCAP_UNRECOG_RE_INVOKE_ID_RX

The total number of unrecognized invoke ids on return-error received on the reporting feature server

TCAP_UNRECOG_RE_INVOKE_ID_TX

The total number of unrecognized invoke ids on return-error sent by the reporting feature server

TCAP_UNEXPECT_RR_RX The total number of unexpected return-results received on the reporting feature server

TCAP_UNEXPECT_RR_TX The total number of unexpected return-results sent by the reporting feature server

TCAP_INCORRECT_PARAM_RR_RX

The total number of incorrect parameters on return-results received on the reporting feature server

TCAP_INCORRECT_PARAM_RR_TX

The total number of incorrect parameters on return-results sent by the reporting feature server




OL-4495-04


INAP Protocol MeasurementsTable 10-16 lists the INAP protocol measurements.

Caution The INAP protocol measurements are not used in Release 4.1. They are disabled (enable=no) by default. The TCAP measurements (see “TCAP Protocol Measurements” section on page 10-37) cover the information formerly available from INAP. Information that could show in the INAP counters could be misleading, and should be ignored.

TCAP_UNRECOG_INVOKE_ID_RX

The total number of unrecognized invoke ids on return-results received on the reporting feature server

TCAP_UNRECOG_INVOKE_ID_TX

The total number of unrecognized invoke ids on return results sent by the reporting feature server

TCAP_UNEXPECT_RE_RX The total number of unexpected return error received on the reporting feature server

TCAP_UNEXPECT_RE_TX The total number of unexpected return error sent by the reporting feature server

TCAP_INCORRECT_COMP_ENCODE_RX

The total number of incorrect component encoding errors received on the reporting feature server

TCAP_ INCORRECT_COMP_ENCODE_TX

The total number of incorrect component encoding errors sent by the reporting feature server

TCAP_INVOKE_RSCR_LIMIT_PROB_RX

The total number of resource limitation invoke problems received on the reporting feature server

TCAP_ INVOKE_RSCR_LIMIT_PROB_TX

The total number of resource limitation invoke problems sent by the reporting feature server

TCAP_UNRECOG_ERR_CODE_RX

The total number of unrecognized error codes on return-error received on the reporting feature server

TCAP_UNRECOG_ERR_CODE_TX

The total number of unrecognized error codes on return-error sent by the reporting feature server

TCAP_UNEXPECT_ERR_CODE_RX

The total number of unexpected error codes on return-error received on the reporting feature server

TCAP_UNEXPECT_ERR_CODE_TX

The total number of unexpected error codes on return-error sent by the reporting feature server

TCAP_INCORRECT_PARAM_RE_RX

The total number of incorrect parameters on return errors received on the reporting feature server

TCAP_INCORRECT_PARAM_RE_TX

The total number of incorrect parameters on return errors sent by the reporting feature server




OL-4495-04


Table 10-16 INAP Measurements


INAP_CANCEL_RX The total number of cancels messages received by the reporting feature server

INAP_CANCEL_TX The total number of cancels messages transmitted by the reporting feature server

INAP_UNRECOG_INVOKE_ID_RX The total number of unrecognized invoke id messages received by the reporting feature server

INAP_UNRECOG_INVOKE_ID_TX The total number of unrecognized invoke id messages sent by the reporting feature server

INAP_DATABSE_ERR_RX The total number of database error messages received by the reporting feature server

INAP_DATABASE_ERR _TX The total number of database error messages sent by the reporting feature server

INAP_ETC_FAIL_RX The total number of ETC failure messages received by the reporting feature server

INAP_ETC_FAIL _TX The total number of etc failure messages sent by the reporting feature server

INAP_IMPROP_CALLER_RSP_RX The total number of improper caller response messages received by the reporting feature server

INAP_IMPROP_CALLER_RSP_TX The total number of improper caller response messages sent by the reporting feature server

INAP_INFO_KEY_ERR_RX The total number of information key error messages received by the reporting feature server

INAP_INFO_KEY_ERR_TX The total number of information key error messages sent by the reporting feature server

INAP_MISSING_CUST_REC_RX The total number of missing customer record messages received by the reporting feature server

INAP_MISSING_CUST_REC_TX The total number of missing customer record messages sent by the reporting feature server

INAP_MISSING_PARM_RX The total number of missing parameter messages received by the reporting feature server

INAP_MISSING_PARM_TX The total number of missing parameter messages sent by the reporting feature server

INAP_PARM_OUT_OF_RANGE_RX The total number of parameter out of range messages received by the reporting feature server

INAP_ PARM_OUT_OF_RANGE _TX The total number of parameter out of range messages sent by the reporting feature server

INAP_REFERRAL_RX The total number of referral messages received by the reporting feature server

INAP_ REFERRAL _TX The total number of referral messages sent by the reporting feature server

INAP_REQ_INFO_RX The total number of request information messages received by the reporting feature server

INAP_ REQ_INFO _TX The total number of request information messages sent by the reporting feature server

INAP_SYS_FAIL_RX The total number of system failure messages received by the reporting feature server


OL-4495-04


INAP_ SYS_FAIL _TX The total number of system failure messages sent by the reporting feature server

INAP_TASK_REFUSED_RX The total number of task refused messages received by the reporting feature server

INAP_ TASK_REFUSED_TX The total number of task refused messages sent by the reporting feature server

INAP_UNAVIL_RSRC_RX The total number of unavailable resource messages received by the reporting feature server

INAP_ UNAVIL_RSRC_TX The total number of unavailable resource messages sent by the reporting feature server

INAP_UNEXPECT_COMP_SEQ_RX The total number of unexpected component sequence messages received by the reporting feature server

INAP_ UNEXPECT_COMP_SEQ_TX The total number of unexpected component sequence messages sent by the reporting feature server

INAP_UNEXPECT_DATA_VAL_RX The total number of unexpected data value messages received by the reporting feature server

INAP_ UNEXPECT_DATA_VAL_TX The total number of unexpected data value messages sent by the reporting feature server

INAP_UNEXPECT_PARM_RX The total number of unexpected parameter messages received by the reporting feature server

INAP_ UNEXPECT_PARM_TX The total number of unexpected parameter messages sent by the reporting feature server

INAP_UNKNOWN_LEG_ID_RX The total number of unknown leg id messages received by the reporting feature server

INAP_ UNKNOWN_LEG_ID_TX The total number of unknown leg id messages sent by the reporting feature server

INAP_UNKNOWN_RSRC_RX The total number of unknown resource messages received by the reporting feature server

INAP_ UNKNOWN_RSRC_TX The total number of unknown resource messages sent by the reporting feature server

INAP_REPORT_ERR_RX The total number of report error messages received by the reporting feature server

INAP_ REPORT_ERR_TX The total number of report error messages sent by the reporting feature server

INAP_ NUM_CHANNEL_BUSY The total number of times a channel busy situation occurred on the reporting feature server

INAP_ NUM_RSRC_NOT_AVAIL The total number of times a resource not available situation occurred on the reporting feature server

INAP_ NUM_RSRC_NOT_SUPP The total number of times a resource not supported situation occurred on the reporting feature server

INAP_ NUM_TASK_REFUSED The total number of times a task refused situation occurred on the reporting feature server

INAP_ NUM_INVALID_CALLER_RSP The total number of times an invalid caller response situation occurred on the reporting feature server

Table 10-16 INAP Measurements (continued)



OL-4495-04


SUA MeasurementsTable 10-17 lists the SUA measurements.

INAP_ NUM_CAPAB_FAIL The total number of times a capability failure situation occurred on the reporting feature server

INAP_ NUM_SUPPL_SVC_INVOKE The total number of times a supplementary service invoke situation occurred on the reporting feature server

INAP_ NUM_SEND_RSCR_CANCEL The total number of times a send to resource request cancelled situation occurred on the reporting feature server

INAP_ NUM_TEMP_FAIL The total number of times a temporary failure situation occurred on the reporting feature server

INAP_ NUM_IP_TMO The total number of times an IP timeout situation occurred on the reporting feature server

INAP_ NUM_UNAUTH_REQ The total number of times an unauthorized request situation occurred on the reporting feature server

INAP_ NUM_UNAUTH_DEST The total number of times an unauthorized destination situation occurred on the reporting feature server

INAP_ NUM_PROCED_ERR The total number of times a procedural error situation occurred on the reporting feature server

Table 10-16 INAP Measurements (continued)


Table 10-17 SUA Measurements


SUA_ERR_TX The total number of errors sent on the reporting signaling gateway process

SUA_ERR_RX The total number of errors received on the reporting signaling gateway process

SUA_NOTIFY_TX The total number of NOTIFYs sent on the reporting signaling gateway process

SUA_NOTIFY_RX The total number of NOTIFYs received on the reporting signaling gateway process

SUA_DUNA_RX The total number of DUNAs received on the reporting signaling gateway process

SUA_DAVA_RX The total number of DAVAs received on the reporting signaling gateway process

SUA_DAUD_TX The total number of DAUDs sent on the reporting signaling gateway process

SUA_SCON_TX The total number of SCONs sent on the reporting signaling gateway process

SUA_SCON_RX The total number of SCONs received on the reporting signaling gateway process

SUA_DRST_RX The total number of DRSTs received on the reporting signaling gateway process

SUA_DUPU_RX The total number of DUPUs received on the reporting signaling gateway process

SUA_UP_TX The total number of UPs sent on the reporting signaling gateway process

SUA_DOWN_TX The total number of DOWNs sent on the reporting signaling gateway process

SUA_BEAT_TX The total number of BEATs sent on the reporting signaling gateway process


OL-4495-04


SUA_BEAT_RX The total number of BEATs received on the reporting signaling gateway process

SUA_UP_ACK_RX The total number of UP Acknowledges received on the reporting signaling gateway process

SUA_DOWN_ACK_RX The total number of DOWN Acknowledges received on the reporting signaling gateway process

SUA_BEAT_ACK_TX The total number of BEAT Acknowledges sent on the reporting signaling gateway process

SUA_BEAT_ACK_RX The total number of BEAT Acknowledges received on the reporting signaling gateway process

SUA_ACTIVE_TX The total number of ACTIVEs sent on the reporting signaling gateway process

SUA_INACTIVE_TX The total number of ACTIVEs received on the reporting signaling gateway process

SUA_ACTIVE_ACK_RX The total number of ACTIVE Acknowledges received on the reporting signaling gateway process

SUA_INACTIVE_ACK_RX The total number of INACTIVE Acknowledges received on the reporting signaling gateway process

SUA_CLDT_TX The total number of CLDTs sent on the reporting signaling gateway process

SUA_CLDT_RX The total number of CLDTs received on the reporting signaling gateway process

SUA_CLDR_TX The total number of CLDRs sent on the reporting signaling gateway process

SUA_CLDR_RX The total number of CLDRs received on the reporting signaling gateway process

SUA_DATA_BYTES_TX The total number of data bytes sent on the reporting signaling gateway process

SUA_DATA_BYTES_RX The total number of data bytes received on the reporting signaling gateway process

SUA_INVALID_SCTP_SIGNALS

The total number of invalid SCTP signals on the reporting signaling gateway process

SUA_SINCE_LAST_RESET_ASSOC

The total number of SCTP errors since last reset of association on the reporting signaling gateway process

SUA_ASSOC_FAIL The total number of association failures on the reporting signaling gateway process

SUA_SCTP_TX_FAIL The total number of SCTP send failures on message processing errors on the reporting signaling gateway process

SUA_MSG_INVALID_LENGTH_RX

The total number of messages of invalid length received on the reporting signaling gateway process

SUA_NO_MEMORY_FAIL The total number of no memory for message errors on the reporting signaling gateway process

SUA_VERSION_ERR The total number of version errors on the reporting signaling gateway process

SUA_MSG_CLASS_ERR The total number of message class errors on the reporting signaling gateway process

SUA_MSG_TYPE_ERR The total number of message type errors on the reporting signaling gateway process

SUA_STREAM_ID_ERR The total number of stream id errors on the reporting signaling gateway process

SUA_UNEXPECT_MSG_ERR

The total number of unexpected message errors on the reporting signaling gateway process

SUA_PROTOCOL_ERR The total number of protocol errors on the reporting signaling gateway process

SUA_PARAM_VALUE_ERR

The total number of parameter value errors on the reporting signaling gateway process

SUA_PARAM_FIELD_ERR The total number of parameter field errors on the reporting signaling gateway process

Table 10-17 SUA Measurements (continued)



OL-4495-04


M3UA Protocol MeasurementsTable 10-12 lists the M3UA protocol measurements.

SUA_UNEXPECT_PARAM_ERR

The total number of unexpected parameter errors on the reporting signaling gateway process

SUA_NETWORK_APPEAR_ERR

The total number of network appearance errors on the reporting signaling gateway process

SUA_ROUTING_CONTEXT_ERR

The total number of routing context errors on the reporting signaling gateway process

Table 10-17 SUA Measurements (continued)


Table 10-18 M3UA Measurements


M3UA_SGP_ID The id of the signaling gateway process that these counters are associated with.

M3UA_ERR_TX The total number of errors sent on the reporting signaling gateway process

M3UA_ERR_RX The total number of errors received on the reporting signaling gateway process

M3UA_NOTIFY_TX The total number of NOTIFYs sent on the reporting signaling gateway process

M3UA_NOTIFY_RX The total number of NOTIFYs received on the reporting signaling gateway process

M3UA_DUNA_RX The total number of DUNAs received on the reporting signaling gateway process

M3UA_DAVA_RX The total number of DAVAs received on the reporting signaling gateway process

M3UA_DAUD_TX The total number of DAUDs sent on the reporting signaling gateway process

M3UA_SCON_TX The total number of SCONs sent on the reporting signaling gateway process

M3UA_SCON_RX The total number of SCONs received on the reporting signaling gateway process

M3UA_DRST_RX The total number of DRSTs received on the reporting signaling gateway process

M3UA_DUPU_RX The total number of DUPUs received on the reporting signaling gateway process

M3UA_UP_TX The total number of UPs sent on the reporting signaling gateway process

M3UA_DOWN_TX The total number of DOWNs sent on the reporting signaling gateway process

M3UA_BEAT_TX The total number of BEATs sent on the reporting signaling gateway process

M3UA_BEAT_RX The total number of BEATs received on the reporting signaling gateway process

M3UA_UP_ACK_RX The total number of UP Acknowledges received on the reporting signaling gateway process

M3UA_DOWN_ACK_RX The total number of DOWN Acknowledges received on the reporting signaling gateway process

M3UA_BEAT_ACK_TX The total number of BEAT Acknowledges sent on the reporting signaling gateway process

M3UA_BEAT_ACK_RX The total number of BEAT Acknowledges received on the reporting signaling gateway process

M3UA_ACTIVE_TX The total number of ACTIVEs sent on the reporting signaling gateway process

M3UA_INACTIVE_TX The total number of ACTIVEs received on the reporting signaling gateway process


OL-4495-04


M3UA_ACTIVE_ACK_RX

The total number of ACTIVE Acknowledges received on the reporting signaling gateway process

M3UA_INACTIVE_ACK_RX

The total number of INACTIVE Acknowledges received on the reporting signaling gateway process

M3UA_DATA_TRANS_TX

The total number of data transfers sent on the reporting signaling gateway process

M3UA_DATA_TRANS_RX

The total number of data transfers received on the reporting signaling gateway process

M3UA_DATA_BYTES_TX The total number of data bytes sent on the reporting signaling gateway process

M3UA_DATA_BYTES_RX

The total number of data bytes received on the reporting signaling gateway process

M3UA_INVALID_SCTP_SIGNALS

The total number of invalid SCTP signals on the reporting signaling gateway process

M3UA_SINCE_LAST_RESET_ASSOC

The total number of SCTP errors since last reset of association on the reporting signaling gateway process

M3UA_ASSOC_FAIL The total number of association failures on the reporting signaling gateway process

M3UA_SCTP_TX_FAIL The total number of SCTP send failures on message processing errors on the reporting signaling gateway process

M3UA_MSG_LENGTH_ERR

The total number of messages of invalid length received on the reporting signaling gateway process

M3UA_NO_MEMORY_ERR

The total number of no memory for message errors on the reporting signaling gateway process

M3UA_VERSION_ERR The total number of version errors on the reporting signaling gateway process

M3UA_MSG_CLASS_ERR

The total number of message class errors on the reporting signaling gateway process

M3UA_MSG_TYPE_ERR The total number of message type errors on the reporting signaling gateway process

M3UA_STREAM_ID_ERR The total number of stream id errors on the reporting signaling gateway process

M3UA_UNEXPECT_MSG_ERR

The total number of unexpected message errors on the reporting signaling gateway process

M3UA_PROTOCOL_ERR The total number of protocol errors on the reporting signaling gateway process

M3UA_PARAM_VALUE_ERR

The total number of parameter value errors on the reporting signaling gateway process

M3UA_PARAM_FIELD_ERR

The total number of parameter field errors on the reporting signaling gateway process

M3UA_UNEXPECT_PARAM_ERR

The total number of unexpected parameter errors on the reporting signaling gateway process

M3UA_NETWORK_APPEAR_ERR

The total number of network appearance errors on the reporting signaling gateway process

Table 10-18 M3UA Measurements (continued)



OL-4495-04


SCTP Protocol MeasurementsTable 10-19 lists the SCTP protocol measurements.

M3UA_ROUTING_CONTEXT_ERR

The total number of routing context errors on the reporting signaling gateway process

M3UA_MSG_RX_OTHER_ERR

The total number of messages received with other errors on the reporting call agent or feature server

Table 10-18 M3UA Measurements (continued)


Table 10-19 SCTP Measurements


SCTP_SCTP_ASSOC_ID The id of the SCTP association that the measurement counter block is associated with.

SCTP_DATA_CHUNK_RX The total number of data chunks received on the reporting sctp association

SCTP_DATA_CHUNK_RX_SEQ_ERR The total number of out-of-sequence data chunks received on the reporting sctp association

SCTP_DATA_CHUNK_RX_ORDER The total number of ordered data chunks received on the reporting sctp association

SCTP_DATA_CHUNK_RX_UNORDER The total number of unordered data chunks received on the reporting sctp association

SCTP_DATA_CHUNK_TX The total number of data chunks sent on the reporting sctp association

SCTP_DATA_CHUNK_TX_ORDER The total number of ordered data chunks sent on the reporting sctp association

SCTP_DATA_CHUNK_TX_UNORDER The total number of unordered data chunks sent on the reporting sctp association

SCTP_DATA_CHUNK_DISCARD The total number of received duplicate data chunks that were discarded on the reporting sctp association

SCTP_DATA_CHUNK_RETRAN The total number of data chunks that were retransmitted on the reporting sctp association

SCTP_DATA_CHUNK_TX_BUNDLE The total number of bundled data chunks that were sent on the reporting sctp association

SCTP_DATA_CHUNK_RX_BUNDLE The total number of bundled data chunks that were received on the reporting sctp association

SCTP_DATA_BYTE_TX The total number of data bytes sent over SCTP on the reporting sctp association

SCTP_DATA_BYTE_RX The total number of data bytes received over SCTP on the reporting sctp association

SCTP_CONTROL_CHUNK_TX The total number of control chunks sent on the reporting sctp association

SCTP_CONTROL_CHUNK_RX The total number of control chunks received on the reporting sctp association

SCTP_ULP_TX The total number of ULP datagrams sent on the reporting sctp association

SCTP_ULP_READY The total number of received datagrams that are ready to be sent to upper layer processes on the reporting sctp association


OL-4495-04


SCTP_ULP_RX The total number of received upper layer process datagrams on the reporting sctp association

SCTP_ULP_QUEUE The total number of upper layer process datagrams queued to be transmitted on the reporting sctp association

SCTP_SCTP_DATAG_TX The total number of datagrams sent on the reporting sctp association

SCTP_SCTP_DATAG_RX The total number of datagrams received on the reporting sctp association

SCTP_INVALID_DATAG_LENGTH The total number of datagrams received with an invalid length on the reporting sctp association

SCTP_PARTIAL_CHUNK_ERR The total number of partial chunks that were received in a datagram on the reporting sctp association

SCTP_EMPTY_DATAG_ERR The total number of datagrams received with no data chunks on the reporting sctp association

SCTP_INVALID_CHECKSUM The total number of SCTP datagrams received with an invalid checksum on the reporting sctp association

SCTP_INVALID_BUNDLE_CHUNK The total number of invalid bundle chunks received on the reporting sctp association

SCTP_INVALID_VERIF_TAG The total number of datagrams with invalid verification tags received on the reporting sctp association

SCTP_OOTB The total number of out of the blue packets received on the reporting sctp association

SCTP_INVALID_STREAM The total number of datagrams with invalid stream ids received on the reporting sctp association

SCTP_ASSOC_COMM_LOST The total number of times the SCTP association communication was lost on the reporting sctp association

SCTP_DEST_ADDR_FAIL The total number of times a destination address failed on the reporting sctp association

SCTP_CHUNK_ORDER_ERR The total number of ordered chunks that were in error on the reporting sctp association

SCTP_ECNE_CHUNK_RX The total number of ECNE chunks received on the reporting sctp association

SCTP_CWR_CHUNK_RX The total number of CWR chunks received on the reporting sctp association

SCTP_UNKNOWN_CHUNK_TYPE The total number of datagrams with an unknown chunk type received on the reporting sctp association

SCTP_UNKNOWN_INIT_PARAM The total number of INIT datagrams with an unknown parameter received on the reporting sctp association

SCTP_INVALID_COOKIE_SIG The total number of invalid cookie signals received on the reporting sctp association

SCTP_EXPIRED_COOKIE_ERR The total number of times a cookie echo was received after the cookie timer expired on the reporting sctp association

SCTP_STALE_COOKIE_ERR The total number of times other endpoint indicates that the cookie echo was received after the cookie time expired on the reporting sctp association

Table 10-19 SCTP Measurements (continued)



OL-4495-04


SCTP_PEER_RESTART_ERR The total number of times the SCTP peer restarted on the reporting sctp association

SCTP_V6_ADDR_PARAM_RX The total number of packets received with version 6 parameters on the reporting sctp association

SCTP_INVALID_STREAM_ERR_RX The total number of times an SCTP peer reported receiving a data chunk on a non-existing stream on the reporting sctp association

SCTP_MISSING_PARAM_ERR_RX The total number of times an INIT or INIT ACK was missing one or more mandatory parameters received on the reporting sctp association

SCTP_STALE_COOKIE_ERR_RX The total number of times an SCTP peer received a valid cookie that had expired on the reporting sctp association

SCTP_OUT_OF_RSCR_ERR_RX The total number of times an SCTP peer reported it was out of resources on the reporting sctp association

SCTP_UNRESOLV_ADDR_ERR_RX The total number of times an SCTP reported that it received a packet with an address it could not resolve on the reporting sctp association

SCTP_UNRECOG_CHUNK_ERR_RX The total number of times an SCTP peer reported that it received a chunk that is could not understand on the reporting sctp association

SCTP_INVALID_PARAM_ERR_RX The total number of times an SCTP peer reported that it received an INIT or INIT ACK chunk containing one or more mandatory parameters that were set to an invalid value on the reporting sctp association

SCTP_UNRECOG_PARAM_ERR_RX The total number of times an SCTP peer reported that it received an INIT ACK containing one or more parameters that were unrecognized on the reporting sctp association

SCTP_NO_USER_DATA_ERR_RX The total number of times an SCTP peer reported that it received a data chunk with no user data in it on the reporting sctp association

SCTP_COOKIE_IN_SHUTDOWN_ERR_RX

The total number of times an SCTP peer reported that is received a COOKIE ECHO while in the SHUTDOWN_ACK_SENT state on the reporting sctp association

SCTP_CHUNK_TOO_SMALL_ERR The total number of data chunks received that were too small on the reporting sctp association

SCTP_CHUCK_TOO_LARGE_ERR The total number of data chunks received that were too big on the reporting sctp association

SCTP_MISSING_PARAM_ERR The total number of times that an INIT or INIT ACK chunk was received with one or more mandatory parameters missing on the reporting sctp association

SCTP_NO_SPACE_INCOM_ERR The total number of data chunks that were dropped due to no space being available in the local receive window on the reporting sctp association

Table 10-19 SCTP Measurements (continued)



OL-4495-04


ISUP (ANSI) MeasurementsTable 10-20 lists the ISUP (ANSI) measurements.

Table 10-20 ISUP (ANSI) Measurements


SGA_MSG_TX The total number of messages sent on the reporting trunk group

SGA_MSG_RX The total number of messages received on the reporting trunk group

SGA_ACM_TX The total number of ACM messages sent on the reporting trunk group

SGA_ACM_RX The total number of ACM messages received on the reporting trunk group

SGA_ANM_TX The total number of ANM messages sent on the reporting trunk group

SGA_ANM_RX The total number of ANM messages received on the reporting trunk group

SGA_BLO_TX The total number of BLO messages sent on the reporting trunk group

SGA_BLO_RX The total number of BLO messages received on the reporting trunk group

SGA_BLA_TX The total number of BLA messages sent on the reporting trunk group

SGA_BLA_RX The total number of BLA messages received on the reporting trunk group

SGA_CCR_TX The total number of CCR messages sent on the reporting trunk group

SGA_CCR_RX The total number of CCR messages received on the reporting trunk group

SGA_CFN_TX The total number of CFN messages sent on the reporting trunk group

SGA_CFN_RX The total number of CFN messages received on the reporting trunk group

SGA_CPG_TX The total number of CPG messages sent on the reporting trunk group

SGA_CPG_RX The total number of CPG messages received on the reporting trunk group

SGA_CGB_TX The total number of CGB messages sent on the reporting trunk group

SGA_CGB_RX The total number of CGB messages received on the reporting trunk group

SGA_CGU_TX The total number of CGU messages sent on the reporting trunk group

SGA_CGU_RX The total number of CGU messages received on the reporting trunk group

SGA_CGBA_TX The total number of CGBA messages sent on the reporting trunk group

SGA_CGBA_RX The total number of CGBA messages received on the reporting trunk group

SGA_CGUA_TX The total number of CGUA messages sent on the reporting trunk group

SGA_CGUA_RX The total number of CGUA messages received on the reporting trunk group

SGA_COT_TX The total number of COT messages sent on the reporting trunk group

SGA_COT_RX The total number of COT messages received on the reporting trunk group

SGA_CQM_TX The total number of CQM messages sent on the reporting trunk group

SGA_CQM_RX The total number of CQM messages received on the reporting trunk group

SGA_CQR_TX The total number of CQR messages sent on the reporting trunk group

SGA_CQR_RX The total number of CQR messages received on the reporting trunk group

SGA_CRA_TX The total number of CRA messages sent on the reporting trunk group

SGA_CRA_RX The total number of CRA messages received on the reporting trunk group


OL-4495-04


SGA_CRM_TX The total number of CRM messages sent on the reporting trunk group

SGA_CRM_RX The total number of CRM messages received on the reporting trunk group

SGA_CVR_TX The total number of CVR messages sent on the reporting trunk group

SGA_CVR_RX The total number of CVR messages received on the reporting trunk group

SGA_CVT_TX The total number of CVT messages sent on the reporting trunk group

SGA_CVT_RX The total number of CVT messages received on the reporting trunk group

SGA_EXM_TX The total number of EXM messages sent on the reporting trunk group

SGA_EXM_RX The total number of EXM messages received on the reporting trunk group

SGA_FAC_TX The total number of FAC messages sent on the reporting trunk group

SGA_FAC_RX The total number of FAC messages received on the reporting trunk group

SGA_FOT_TX The total number of FOT messages sent on the reporting trunk group

SGA_FOT_RX The total number of FOT messages received on the reporting trunk group

SGA_GRS_TX The total number of GRS messages sent on the reporting trunk group

SGA_GRS_RX The total number of GRS messages received on the reporting trunk group

SGA_GRA_TX The total number of GRA messages sent on the reporting trunk group

SGA_GRA_RX The total number of GRA messages received on the reporting trunk group

SGA_IAM_TX The total number of IAM messages sent on the reporting trunk group

SGA_IAM_RX The total number of IAM messages received on the reporting trunk group

SGA_INF_TX The total number of INF messages sent on the reporting trunk group

SGA_INF_RX The total number of INF messages received on the reporting trunk group

SGA_INR_TX The total number of INR messages sent on the reporting trunk group

SGA_INR_RX The total number of INR messages received on the reporting trunk group

SGA_LPA_TX The total number of LPA messages sent on the reporting trunk group

SGA_LPA_RX The total number of LPA messages received on the reporting trunk group

SGA_PAM_TX The total number of PAM messages sent on the reporting trunk group

SGA_PAM_RX The total number of PAM messages received on the reporting trunk group

SGA_REL_TX The total number of REL messages sent on the reporting trunk group

SGA_REL_RX The total number of REL messages received on the reporting trunk group

SGA_RLC_TX The total number of RLC messages sent on the reporting trunk group

SGA_RLC_RX The total number of RLC messages received on the reporting trunk group

SGA_RSC_TX The total number of RSC messages sent on the reporting trunk group

SGA_RSC_RX The total number of RSC messages received on the reporting trunk group

SGA_RES_TX The total number of RES messages sent on the reporting trunk group

SGA_RES_RX The total number of RES messages received on the reporting trunk group

SGA_SUS_TX The total number of SUS messages sent on the reporting trunk group

Table 10-20 ISUP (ANSI) Measurements (continued)



OL-4495-04


ISUP (ITU-China) MeasurementsTable 10-21 lists the ISUP (ITU-China) measurements.

SGA_SUS_RX The total number of SUS messages received on the reporting trunk group

SGA_UBL_TX The total number of UBL messages sent on the reporting trunk group

SGA_UBL_RX The total number of UBL messages received on the reporting trunk group

SGA_UBA_TX The total number of UBA messages sent on the reporting trunk group

SGA_UBA_RX The total number of UBA messages received on the reporting trunk group

SGA_UCIC_TX The total number of UCIC messages sent on the reporting trunk group

SGA_UCIC_RX The total number of UCIC messages received on the reporting trunk group

SGA_USR_TX The total number of USR messages sent on the reporting trunk group

SGA_USR_RX The total number of USR messages received on the reporting trunk group

SGA_ABNORMAL_REL_RX The total number of RELs received with a cause other than NORMAL on the reporting trunk group

SGA_UNEXPECT_MSG_RX The total number of unexpected messages received on the reporting trunk group

SGA_UNRECOG_MSG_RX The total number of unrecognized messages received on the reporting trunk group

Table 10-20 ISUP (ANSI) Measurements (continued)


Table 10-21 ISUP (ITU-China) Measurements












SGA_CCL_TX The total number of CCL messages sent on the reporting trunk group

SGA_CCL_RX The total number of CCL messages received on the reporting trunk group





OL-4495-04











SGA_CON_TX The total number of CON messages sent on the reporting trunk group

SGA_CON_RX The total number of CON messages received on the reporting trunk group









SGA_OPR_TX The total number of OPR messages sent on the reporting trunk group

SGA_OPR_RX The total number of OPR messages received on the reporting trunk group









SGA_SAM_TX The total number of SAM messages sent on the reporting trunk group

SGA_SAM_RX The total number of SAM messages received on the reporting trunk group

SGA_SGM_TX The total number of SGM messages sent on the reporting trunk group

SGA_SGM_RX The total number of SGM messages received on the reporting trunk group



Table 10-21 ISUP (ITU-China) Measurements (continued)



OL-4495-04


ISUP (ITU-Mexico) MeasurementsTable 10-22 lists the ISUP (ITU-Mexico) measurements.





SGA_ABNORMAL_REL_TX The total number of RELs sent with a cause other than NORMAL on the reporting trunk group




Table 10-21 ISUP (ITU-China) Measurements (continued)


Table 10-22 ISUP (ITU-Mexico) Measurements












SGA_CCL_TX The total number of CCL messages sent on the reporting trunk group

SGA_CCL_RX The total number of CCL messages sent on the reporting trunk group








OL-4495-04














SGA_CQM_TX The total number of CQM messages sent on the reporting trunk group

SGA_CQM_RX The total number of CQM messages received on the reporting trunk group

SGA_CQR_TX The total number of CQR messages sent on the reporting trunk group

SGA_CQR_RX The total number of CQR messages received on the reporting trunk group




















Table 10-22 ISUP (ITU-Mexico) Measurements (continued)



OL-4495-04


ISUP (ITU-HongKong) CountersTable 10-23 lists the ISUP (ITU-HongKong) measurements provided in Release 4.2.








SGA_UCIC_TX The total number of UCIC messages sent on the reporting trunk group

SGA_UCIC_RX The total number of UCIC messages received on the reporting trunk group





Table 10-22 ISUP (ITU-Mexico) Measurements (continued)


Table 10-23 ISUP (ITU-HongKong) Counters
















OL-4495-04















SGA_FAC_TX The total number of FAC messages sent on the reporting trunk group

SGA_FAC_RX The total number of FAC messages received on the reporting trunk group











SGA_PAM_TX The total number of PAM messages sent on the reporting trunk group

SGA_PAM_RX The total number of PAM messages received on the reporting trunk group

SGA_NRM_TX The total number of NRM messages sent on the reporting trunk group

SGA_NRM_RX The total number of NRM messages received on the reporting trunk group










OL-4495-04


Audit MeasurementsTable 10-24 lists the audit measurements.

SIP Interface Adapter MeasurementsTable 10-25 lists the SIP interface adapter measurements.





SGA_SGM_TX The total number of SGM messages sent on the reporting trunk group

SGA_SGM_RX The total number of SGM messages received on the reporting trunk group











Table 10-24 Audit Measurements


SS7_AUDIT_TRUNK_STATE_SYNCED The total number of SS7 trunks that had their local and remote states synchronized on the reporting trunk group

SS7_AUDIT_LONG_DUR_EXCEEDED The total number of SS7 calls that exceeded the long duration threshold on the reporting trunk group

Table 10-25 SIP Interface Adapter Measurements


SIA_SIP_OUTG_INIT The number of outgoing SIP call initializations on the reporting call agent

SIA_SIP_OUTG_SUCC The number of successful outgoing SIP calls on the reporting call agent


OL-4495-04


SIA_SIP_OUTG_FAIL The number of failed outgoing SIP calls on the reporting call agent

SIA_SIP_INCOM_INIT The number of incoming SIP call initializations on the reporting call agent

SIA_SIP_INCOM_SUCC The number of successful incoming SIP calls on the reporting call agent

SIA_SIP_INCOM_FAIL The number of failed incoming SIP calls on the reporting call agent

SIA_TOTAL_SUCC The total number of successfully completed SIP calls on the reporting call agent

SIA_TOTAL_FAIL The total number of unsuccessfully completed SIP calls on the reporting call agent

SIA_TOTAL_OUTG_MSG_FAIL The number of outgoing SIP message attempts that were not successfully transmitted by the reporting call agent

SIA_TOTAL_INCOM_MSG_FAIL The number of incoming SIP message attempts that were not successfully received by the reporting call agent

SIA_REFRESHES_TX The number of SIP message refreshes that occurred on the reporting call agent

SIA_TOTAL_SESS_TIMER_FAIL The number of call failures due to session timer expiry that occurred on the reporting call agent

SIA_CALL_FAIL_BY_EXPIRED_REG The number of call failures due to a registration expiration on the reporting call agent

SIA_MWI_NOTIFY_TX The number of SIP Notify MWIs sent to SIP phones by the reporting call agent

SIA_MWI_NOTIFY_TX_FAIL The number of SIP Notify MWIs that failed to be sent to SIP phones by the reporting call agent

SIA_MWI_NOTIFY_RX The number of SIP Notify MWIs received from SIP subscribers by the reporting call agent

Table 10-25 SIP Interface Adapter Measurements (continued)



OL-4495-04


Call Detail Block MeasurementsTable 10-26 lists the call detail block measurements.

Table 10-26 Call Detail Block Measurements


BILLING_TOTAL_NULL The number call detail block of type "null" (non-routed calls) created by the reporting element management system


BILLING_TOTAL_TEST The number call detail block of type test call created by the reporting element management system

BILLING_TOTAL_INTL The number call detail block of type international created by the reporting element management system

BILLING_TOTAL_LOCAL The number call detail block of type local created by the reporting element management system

BILLING_TOTAL_TOLL The number call detail block of type toll created by the reporting element management system

BILLING_TOTAL_INTERLATA The number call detail block of type interlata created by the reporting element management system

BILLING_TOTAL_TANDEM The number call detail block of type tandem created by the reporting element management system

BILLING_TOTAL_EMG The number call detail block of type emergency created by the reporting element management system

BILLING_TOTAL_NON_EMG The number call detail block of type non-emergency created by the reporting element management system

BILLING_TOTAL_DA The number call detail block of type directory assistance created by the reporting element management system

BILLING_TOTAL_DA_TOLL The number call detail block of type directory assistance toll created by the reporting element management system

BILLING_TOTAL_REPAIR The number call detail block of type repair created by the reporting element management system

BILLING_TOTAL_RELAY The number call detail block of type relay created by the reporting element management system

BILLING_TOTAL_BUSINESS The number call detail block of type business created by the reporting element management system

BILLING_TOTAL_TOLL_FREE The number call detail block of type toll free created by the reporting element management system

BILLING_TOTAL_900 The number call detail block of type 900 created by the reporting element management system



OL-4495-04




BILLING_TOTAL_VACANT The number call detail block of type vacant created by the reporting element management system

BILLING_TOTAL_PCS The number call detail block of type pcs created by the reporting element management system

BILLING_TOTAL_INVALID The number call detail block of type invalid created by the reporting element management system

BILLING_TOTAL_NONE The number call detail block of type none created by the reporting element management system

BILLING_TOTAL_LRN The number call detail block of type LRN created by the reporting element management system

BILLING_TOTAL_EXTENSION The number call detail block of type extension created by the reporting element management system

BILLING_TOTAL_CUT_THRU The number call detail block of type cut thru created by the reporting element management system

BILLING_TOTAL_OP The number call detail block of type cut operator created by the reporting element management system

BILLING_TOTAL_CARRIER_OP The number call detail block of type carrier operator created by the reporting element management system

BILLING_TOTAL_OP_ASSIST The number call detail block of type operator assisted created by the reporting element management system

BILLING_TOTAL_BLV The number call detail block of type busy line verification created by the reporting element management system

BILLING_TOTAL_SPEED_DIAL The number call detail block of type speed dial created by the reporting element management system

BILLING_TOTAL_NATIONAL The number call detail block of type national (NANP) created by the reporting element management system

BILLING_TOTAL_TW The number call detail block of type time and weather created by the reporting element management system

BILLING_TOTAL_INFO The number call detail block of type information (i.e. 976 calls) created by the reporting element management system

BILLING_TOTAL_PREMIUM The number call detail block of type premium (i.e. 900 calls) created by the reporting element management system

BILLING_TOTAL_ATTENDANT The number call detail block of type attendant created by the reporting element management system

BILLING_TOTAL_NAS The number call detail block of type NAS created by the reporting element management system

Table 10-26 Call Detail Block Measurements (continued)



OL-4495-04


Event Messaging MeasurementsTable 10-27 lists the event messaging measurements.

Dynamic QoS MeasurementsTable 10-28 lists the dynamic quality of service (QoS) measurements.

BILLING_TOTAL_POLICE The number call detail block of type police created by the reporting element management system

BILLING_TOTAL_FIRE The number call detail block of type fire created by the reporting element management system

BILLING_TOTAL_AMBULANCE The number call detail block of type ambulance created by the reporting element management system

BILLING_TOTAL_TIME The number call detail block of type time created by the reporting element management system

BILLING_TOTAL_WEATHER The number call detail block of type weather created by the reporting element management system

BILLING_TOTAL_TRAFFIC The number call detail block of type traffic created by the reporting element management system

Table 10-26 Call Detail Block Measurements (continued)


Table 10-27 Event Messaging Measurements

MeasurementDescription(*=rapid count could mean a potential problem in the system)

BILLING_EM_ACKED The number of event messages acknowledged by the Record Keeping System.

BILLING_EM_LOGGED The number of event messages written to disk but not sent to any RKS.

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

Table 10-28 Dynamic QoS Measurements


DQOS_GATESET_ATTMP The number of DQOS gate set attempts of all types on the reporting aggregator.

DQOS_GATESET_SUCC The number of successful DQOS gate set attempts of all types on the reporting aggregator.

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


OL-4495-04


SNMP Protocol MeasurementsTable 10-29 lists the SNMP protocol measurements.

Trunk Group Usage MeasurementsTable 10-30 lists the trunk group usage measurements.

Table 10-29 SNMP Protocol Measurements


SNMP_TRAP_TX The total number of SNMP TRAPs generated by the reporting element management system

SNMP_SET_RX The total number of SNMP SETs received by the reporting element management system

SNMP_SET_TX The total number of SNMP SETs transmitted by the reporting element management system

SNMP_GET_RX The total number of SNMP GETs received by the reporting element management system

SNMP_GET_TX The total number of SNMP GETs transmitted by the reporting element management system

SNMP_GET_NEXT_RX The total number of SNMP GET NEXTs received by the reporting element management system

SNMP_GET_NEXT_TX The total number of SNMP GET NEXTs transmitted by the reporting element management system

Table 10-30 Trunk Group Usage Measurements


TRKGRP_TYPE The signaling type of the reporting trunk group.

TRKGRP_ID The identification number of the reporting trunk group.

TRKGRP_INCOM_ATTMP The number of times the system recognizes an incoming seizure for any trunk within the reporting trunk group:

• In the case of a SIP trunk, this is incremented for every Invite received on a trunk.

• In the case of an H.323 trunk, this is incremented for each Incoming Setup received on a trunk when not associated with a H.323 subscriber.

TRKGRP_OUTG_ATTMP The number of times the system tries to access any trunk for an outbound call within the reporting trunk group:

• In the case of a SIP trunk, this is incremented for each received SetupReq request for a SIP trunk.

• In the case of an H.323 trunk, this is incremented for each Outgoing Setup sent on a trunk when not associated with a H.323 subscriber.


OL-4495-04


TRKGRP_OUTBOUND_FAIL The number of times the system tries to access any trunk for an outbound call unsuccessfully within the reporting trunk group:

• In the case of a SIP trunk, this is incremented for each outgoing initial Invite request failure over a SIP trunk. For each failure response received over a trunk for any other failure causing failure of the outbound call setup. If an Invite is cancelled, the counter for failure is not incremented as this includes just an outbound call.

• In the case of an H.323 trunk, this is incremented for each Outgoing Setup sent on a trunk that failed when not associated with a H.323 subscriber.

TRKGRP_TOTAL_OVERFLOW The number of outbound trunk call attempt failures due to all trunks within the reporting trunk group being in a busy state. This counter is not incremented for SIP or H.323 trunk groups.

TRKGRP_TOTAL_TRK The number of trunks within the reporting trunk group

TRKGRP_INCOM_BUSY_TRK Summation of the number of trunk circuits within the reporting trunk group marked as busy with terminating calls taken every 100 seconds during the interval. This counter is not incremented for SIP or H.323 trunk groups.

TRKGRP_OUTG_BUSY_TRK Summation of the number of trunk circuits within the reporting trunk group marked as busy with originating calls taken every 100 seconds during the interval. This counter is not incremented for SIP or H323 trunk groups.

TRKGRP_TOTAL_OOS_TRK The number of transitions to the locally blocked state for all trunks within the reporting trunk group. This counter is not incremented for SIP or H.323 trunk groups.

TRKGRP_INCOM_USAGE Summation of the number of trunk circuits within the reporting trunk group marked as busy or in the maintenance state with terminating calls taken every 100 seconds during the interval.

This counter is mapped to the same value as the TRKGRP_INCOM_BUSY_TRK in this release. This counter will be re-implemented to account for the MAINT state in a later release.

TRKGRP_OUTG_USAGE Summation of the number of trunk circuits within the reporting trunk group marked as busy or in the maintenance state with originating calls taken every 100 seconds during the interval.

This counter is mapped to the same value as the TRKGRP_OUTG_BUSY_TRK in this release. This counter will be re-implemented to account for the MAINT state in a later release.

TRKGRP_TOTAL_USAGE Summation of the incoming usage and the outgoing usage counters for the reporting trunk group.

TRKGRP_AVERAGE_USAGE The total usage counter divided by the number of trunks in the reporting trunk group. This counter is not incremented for SIP or H.323 trunk groups.

Table 10-30 Trunk Group Usage Measurements (continued)



OL-4495-04


Announcement MeasurementsTable 10-31 lists the announcement measurements.

Table 10-31 Announcement Measurements


ANM_CKT_UNAVAIL The number of calls resulting in the playing of the circuit unavailable announcement by the reporting call agent

ANM_CALL_REJECTED The number of calls resulting in the playing of the call rejected announcement by the reporting call agent

ANM_ADDR_INCOMPLETE The number of calls resulting in the playing of the address incomplete announcement by the reporting call agent

ANM_FAC_REJECTED The number of calls resulting in the playing of the facility rejected announcement by the reporting call agent

ANM_PRE_0_1_ABSENT The number of calls resulting in the playing of the prefix of 0 or 1 absent announcement by the reporting call agent

ANM_PRE_0_1_PRESENT The number of calls resulting in the playing of the prefix 0 or 1 present announcement by the reporting call agent

ANM_HNPA_ABSENT The number of calls resulting in the playing of the HNPA area code announcement by the reporting call agent

ANM_NO_ROUTE_DEST The number of calls resulting in the playing of the no route to destination announcement by the reporting call agent

ANM_UNALLOCATED_NUM The number of calls resulting in the playing of the unallocated directory number announcement by the reporting call agent

ANM_NUM_CHANGED The number of calls resulting in the playing of the directory number changed announcement by the reporting call agent

ANM_DEST_OUTOFORDER The number of calls resulting in the playing of the destination out of order announcement by the reporting call agent

ANM_TEMP_DISCONNECT The number of calls resulting in the playing of the temporarily disconnected announcement by the reporting call agent

ANM_FEAT_NOT_SUBS The number of calls resulting in the playing of the feature not subscribed to announcement by the reporting call agent

ANM_AUTHCODE_INVALID The number of calls resulting in the playing of the authorization code invalid announcement by the reporting call agent

ANM_NO_RTE_TRANSITNW The number of calls resulting in the playing of the no route to specified network announcement by the reporting call agent

ANM_CAUSE_UNKNOWN The number of calls resulting in the playing of the cause unknown announcement by the reporting call agent


OL-4495-04


H.323 Protocol MeasurementsTable 10-32 lists the H.323 protocol measurements.

Table 10-32 H.323 Protocol Measurements


H323_SETUP_RX The total number of H323 SETUPs received by the reporting call agent

H323_SETUP_TX The total number of H323 SETUPs transmitted by the reporting call agent

H323_SETUP_FAIL The total number of H323 SETUPs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_CONNECT_RX The total number of H323 CONNECTs received by the reporting call agent

H323_CONNECT_TX The total number of H323 CONNECTs transmitted by the reporting call agent

H323_CONNECT_FAIL The total number of H323 CONNECT CONFIRMs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_ALERT_RX The total number of H323 ALERTs received by the reporting call agent

H323_ALERT_TX The total number of H323 ALERTs transmitted by the reporting call agent

H323_ALERT_FAIL The total number of H323 ALERTs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_IN_PROGRESS_RX The total number of H323 IN PROGRESSs received by the reporting call agent

H323_IN_PROGRESS_TX The total number of H323 IN PROGRESSs transmitted by the reporting call agent

H323_IN_PROGRESS_FAIL The total number of H323 IN PROGRESSs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_CALL_PROCEEDING_RX The total number of H323 CALL PROCEEDINGs received by the reporting call agent

H323_CALL_PROCEEDING_TX The total number of H323 CALL PROCEEDINGs transmitted by the reporting call agent

H323_CALL_PROCEEDING_FAIL The total number of H323 CALL PROCEEDINGs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_RELEASE_COMPLETE_RX The total number of H323 RELEASEs received by the reporting call agent

H323_RELEASE_COMPLETE_TX The total number of H323 RELEASEs transmitted by the reporting call agent

H323_RELEASE_COMPLETE_FAIL The total number of H323 RELEASEs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_REJECT_RX The total number of H323 REJECTs received by the reporting call agent

H323_REJECT_TX The total number of H323 REJECTs transmitted by the reporting call agent

H323_REJECT_FAIL The total number of H323 REJECTs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.


OL-4495-04


H323_INFORMATION_RX The total number of H323 INFOs received by the reporting call agent

H323_INFORMATION_TX The total number of H323 INFOs transmitted by the reporting call agent

H323_INFORMATION_FAIL The total number of H323 INFOs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_USER_INFO_RX The total number of H323 USER INFOs received by the reporting call agent

H323_USER_INFO_TX The total number of H323 USER INFOs transmitted by the reporting call agent

H323_USER_INFO_FAIL The total number of H323 USER INFOs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_FACILITY_RX The total number of H323 FACILITYs received by the reporting call agent

H323_FACILITY_TX The total number of H323 FACILITYs transmitted by the reporting call agent

H323_FACILITY_FAIL The total number of H323 FACILITYs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_NOTIFY_RX The total number of H323 NOTIFYs received by the reporting call agent

H323_NOTIFY_TX The total number of H323 NOTIFYs transmitted by the reporting call agent

H323_NOTIFY_FAIL The total number of H323 NOTIFYs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_PASSTHROU_RX The total number of H323 PASS THROUGHs received by the reporting call agent

H323_PASSTHROU_TX The total number of H323 PASS THROUGHs transmitted by the reporting call agent

H323_PASSTHROU_FAIL The total number of H323 PASS THROUGHs that failed. The failure is due to one of the following scenarios: unable to send due to full socket queue, unable to compose message due to invalid socket, or lack of available memory.

H323_GRQ_TX The total number of H323 GRQs transmitted by the reporting call agent

H323_GRQ_RX The total number of H323 GRQs received by the reporting call agent

H323_GCF_TX The total number of H323 GCFs transmitted by the reporting call agent

H323_GCF_RX The total number of H323 GCFs received by the reporting call agent

H323_GRJ_TX The total number of H323 GRJs received by the reporting call agent

H323_GRJ_RX The total number of H323 GRJs transmitted by the reporting call agent

H323_RRQ_TX The total number of H323 RRQs transmitted by the reporting call agent

H323_RRQ_RX The total number of H323 RRQs received by the reporting call agent

H323_RCF_TX The total number of H323 RCFs transmitted by the reporting call agent

H323_RCF_RX The total number of H323 RCFs received by the reporting call agent

H323_RRJ_TX The total number of H323 RRJs transmitted by the reporting call agent

H323_RRJ_RX The total number of H323 RRJs received by the reporting call agent

H323_RIP_TX The total number of H323 RIPs transmitted by the reporting call agent

Table 10-32 H.323 Protocol Measurements (continued)



OL-4495-04


Call Tools MeasurementsTable 10-33 lists the Call Tools measurements.

H323_RIP_RX The total number of H323 RIPs received by the reporting call agent

H323_RAI_TX The total number of H323 RAIs transmitted by the reporting call agent

H323_RAI_RX The total number of H323 RAIs received by the reporting call agent

H323_RAC_TX The total number of H323 RACs transmitted by the reporting call agent

H323_RAC_RX The total number of H323 RACs received by the reporting call agent

H323_ARQ_TX The total number of H323 ARQs transmitted by the reporting call agent

H323_ARQ_RX The total number of H323 ARQs received by the reporting call agent

H323_ACF_TX The total number of H323 ACFs transmitted by the reporting call agent

H323_ACF_RX The total number of H323 ACFs received by the reporting call agent

H323_ARJ_TX The total number of H323 ARJs transmitted by the reporting call agent

H323_ARJ_RX The total number of H323 ARJs received by the reporting call agent

H323_URQ_RX The total number of H323 URQs received by the reporting call agent

H323_URQ_TX The total number of H323 URQs transmitted by the reporting call agent

H323_UCF_RX The total number of H323 UCFs received by the reporting call agent

H323_UCF_TX The total number of H323 UCFs transmitted by the reporting call agent

H323_URJ_RX The total number of H323 URJs received by the reporting call agent

H323_URJ_TX The total number of H323 URJs transmitted by the reporting call agent

H323_BRQ_RX The total number of H323 BRQs received by the reporting call agent

H323_BRQ_TX The total number of H323 BRQs transmitted by the reporting call agent

H323_BCF_RX The total number of H323 BCFs received by the reporting call agent

H323_BCF_TX The total number of H323 BCFs transmitted by the reporting call agent

H323_BRJ_RX The total number of H323 BRJs received by the reporting call agent

H323_BRJ_TX The total number of H323 BRJs transmitted by the reporting call agent

H323_DRQ_RX The total number of H323 DRQs received by the reporting call agent

H323_DRQ_TX The total number of H323 DRQs transmitted by the reporting call agent

H323_DCF_RX The total number of H323 DCFs received by the reporting call agent

H323_DCF_TX The total number of H323 DCFs transmitted by the reporting call agent

H323_DRJ_RX The total number of H323 DRJs received by the reporting call agent

H323_DRJ_TX The total number of H323 DRJs transmitted by the reporting call agent

Table 10-32 H.323 Protocol Measurements (continued)



OL-4495-04


AIN Tools MeasurementsTable 10-34 lists the AIN feature server tools measurements.

Table 10-33 Call Tools Measurements


TOOLS_TRUNK_TRANS_ATTMP The total number of times the TVT process on the reporting call agent received a request to perform a trunk based translation.


TOOLS_TRUNK_TRANS_SUCC The total number of times the TVT process on the reporting call agent received a request to perform a trunk based translation and completed it successfully.


TOOLS_LINE_TRANS_ATTMP The total number of times the TVT process on the reporting call agent received a request to perform a line based translation.


TOOLS_LINE_TRANS_SUCC The total number of times the TVT process on the reporting call agent received a request to perform a line based translation and completed it successfully.


Table 10-34 AIN Tools Measurements


TOOLS_LNP_QUERY_ATTMP The total number of times the reporting feature server received a request to perform an LNP query from the QVT tool.


TOOLS_LNP_QUERY_SUCC The total number of times the reporting feature server received a request to perform an LNP query from the QVT tool and completed it successfully.



OL-4495-04


PCT Tools MeasurementsTable 10-35 lists the PCT feature server tools measurements.

TOOLS_TOLLFREE_QUERY_ATTMP

The total number of times the reporting feature server received a request to perform a Toll Free query from the QVT tool.


TOOLS_TOLLFREE_QUERY_SUCC The total number of times the reporting feature server received a request to perform a Toll Free query from the QVT tool and completed it successfully.


Table 10-34 AIN Tools Measurements (continued)


Table 10-35 PCT Tools Measurements


TOOLS_LIDB_QUERY_ATTMP The total number of times the reporting feature server received a request to perform an LIDB query from the QVT tool.


TOOLS_LIDB_QUERY_SUCC The total number of times the reporting feature server received a request to perform an LIDB query from the QVT tool and completed it successfully.



OL-4495-04



OL-4495-04


C H A P T E R 11
Audit Database and Table Name
This chapter describes how to audit databases and table names. The commands described in this chapter allow a user to audit either the complete database or entries in every table that can be provisioned in both the Oracle database and shared memory.

Note All audit commands are time intensive. Completion time depends upon the number of entries in the table or database.

Audit DatabaseThe audit database command allows users to audit table entries two ways using the type and/or the platform state token. Users can either audit every entry in every table that can be provisioned, by omitting all tokens, which returns a listing of every entry in every table. Or, the audit can be restricted using the type and platform state tokens.

Note If a type parameter is not specified, the type default is full. If a platform-state is not specified, the default is active.

Step 1 Use one of the following examples to audit the entire database, or restrict the audit using tokens:

audit database; audit database type=row-count; audit database platform-state=ems;

Table NameThe audit table name command audits only the entries in a particular table <table-name> (where table-name is any provisionable table). The audit is made more specific by specifying tokens and values from the particular table being audited that narrow the search. For example, if a user types audit service, that audits the entire service table. If a user types audit service id=123, that audits only the service entry with the ID of 123. The audit is also made more specific by specifying a type and/or platform state from the particular table that narrows the search.


Chapter 11 Audit Database and Table NameTable Name

Step 1 Use one of the following examples to audit the entire database, or restrict the audit by using the type token:

audit trunk type=row-count;audit trunk platform-state=active; tgn-id=42;audit subscriber id=jer%;

Note The last example shows how to use the percent sign (%) to specify a search range. This example returns any subscriber entries that have an ID field beginning with jer.


OL-4495-04


C H A P T E R 12
Show and Change Database Usage Commands
This chapter describes the show command paging capability for batch data retrieval, the show command for database usage, and the change db-usage command.

Show Command Paging Capability for Batch Data RetrievalThe show command paging capability is used for retrieving subscriber related records (such as SUBSCRIBERS, TERMINATIONS, SUBSCRIBER_SERVICE_PROFILES) in batches.

The following parameters apply to all show commands that operate on provisioning data. These parameters are particularly useful when displaying tables containing large amounts of data such as SUBSCRIBERS and TERMINATIONS.

• limit specifies the page size for the maximum number of rows (or lines) returned in response to the query.

• start_row specifies the location in the data set where to start the page to be displayed. (The data set is the entire set of data that can be displayed as a result of the show command.)

Note The default value for start_row is 1 (or the first row of data).

• display shows only the columns of data requested. The display is a comma-separated list of the desired columns.

• order provides a key for ordering or sorting the data. More than one item can be specified for the sort.

Example: Controlling the Volume and Format of Data

In the following example, the following show command parameters are used to control the volume and format of data to be displayed:

show subscriber limit=1000; start_row=<next page value>;

Where:

• subscriber limit=1000 specifies the page size as 1000 rows. The first page contains the total size of the display (such as 12,000 rows).

• start_row=<next page value> specifies the location in the data set where to start the page to be displayed.


Chapter 12 Show and Change Database Usage CommandsShow Database Usage Command

Example: Ordering and Displaying Specific Data

In the following example, the following show command parameters are used to order and display only the desired data:

show subscriber limit=1000; start_row=<next page value>; display=id,sub_service_profile; order=id;

Where:

• subscriber limit=1000 indicates that 1000 is the maximum number of rows in a page. The first page contains the total size of the display (such as 12,000 rows).

• start_row=<next page value> specifies the location in the data set where to start the page to be displayed.

• display=id,sub_service_profile indicates that the data is sorted by id column. The subscribers can be alphabetized by sorting according to the name or another parameter. The display parameter is a comma-separated list of parameters used to sort the returned data. In this example, only the id and sub_profile_id columns of data are displayed from the subscriber table.

• order=id means that the data is sorted by id column.

Show Database Usage CommandThe show db-usage command returns and modifies the maximum number of records allowed, as well as the number of licensed and current database records. Records can be shown and changed but cannot be deleted.

The current number of records field is updated by the EMS in real time. The db-usage command also uses the Database Threshold (db-thresholds) table, which contains default alarm threshold parameters that are provisioned during installation. Parameters can be changed and shown. The default threshold parameters are:

• 80 percent minor

• 85 percent major

• 90 percent critical

Note Do not use a hyphen (-) in the actual name of a table when using this command. Use the underscore (_). For example, dial_plan is correct; dial-plan is not correct.

Step 1 Use the following command example to show db-usage statistics:

show db-usage table-name=dial_plan;

Change db-usageThis section describes the change db-usage command.

Step 1 Use the following command example to change db-usage tokens and values.


OL-4495-04

Chapter 12 Show and Change Database Usage CommandsChange db-usage

change db-usage table-name=dial-plan; minor-threshold=70;major-threshold=80; critical-threshold=95;


OL-4495-04

Chapter 12 Show and Change Database Usage CommandsChange db-usage


OL-4495-04


C H A P T E R 13
Transactions
This chapter describes the commands and tables for viewing and manipulating transactions.

Transaction QueueThe transaction-queue command allows users to view and delete entries in a transaction queue, if any exist. The Transaction Queue table tracks updates into the database, as well as into the shared memory of the Call Agent and Feature Servers. Entries should never remain in the transaction queue for more than a few seconds, unless an Element Management System (EMS), Call Agent, or Feature Server is in an error state. In the case of an error state, the transaction queue continues to store entries for later updates. Transaction queue entries can be deleted but not changed.

ShowThis section describes the transaction-queue show command.

Step 1 Use the following command example to show any entries in a transaction queue:

show transaction-queue target=CA146

DeleteThis section describes the transaction-queue delete command.

Step 1 Use the following command example to delete any entries in a transaction queue.

delete transaction-queue target=CA146

Caution The delete transaction-queue command causes a database inconsistency. Call the Cisco Systems Technical Assistance Center to determine usage necessity.


Chapter 13 TransactionsQueue Throttle

Queue ThrottleThe queue-throttle command allows provisioning commands to be throttled by changing the percentage of the maximum download capacity used for transaction queuing. It constrains transactions on a particular Call Agent, Feature Server, or EMS during provisioning. Queue throttle entries can be changed but not deleted.

ShowThis section describes the show queue-throttle command:

Step 1 Use the following command example to show any queue throttle entries:

show queue-throttle

ChangeThis section describes the change queue-throttle command.

Step 1 Use the following command example to change a queue throttle entry.

change queue-throttle network-id=CA145; percent=20;

Reply Example:

The Queuing Manager is operating within normal parameters. Queuing Manager activity may be suspended using the block session command.


OL-4495-04


C H A P T E R 14
History
The history command returns a list of all executed commands. A list of all executed commands can be sent to a file (report history) or displayed on the screen (show history).

ShowThis section describes the history show command. Results of this command are sent to the terminal screen. Using this command without any tokens returns all entries.

Step 1 Use the following command example to show all history entries:

show history;

ReportThis section describes the history report command. Results of this command are sent to report file. Using this command without any tokens returns all entries.

Step 1 Use the following command example to report all history entries:

report history;

Step 2 Using the Cisco BTS 10200 Softswitch http:// server in an external browser (Netscape, Internet Explorer, and so forth), perform the following steps to retrieve the history report file:

a. Enter the http:// server name.

http://<your bts domain name>:10200> <enter>

b. Once on the main page, click the reports link.

A set of directories appears.

c. Select the Command History report by clicking history.html.

The history log appears.


Chapter 14 History


OL-4495-04


C H A P T E R 15
Call Trace Summary
The Call Trace Summary command reports the information gathered when a customer activates a trace by pressing *57 on the telephone. This command logs information pertaining only to the most recently received call. Report is the only command type. Using the command without any tokens returns all entries in the table.

Use the following command example to report call trace information:

report call-trace-summary

Note Table information is logged from the switch. If the system cannot decipher the information from the switch, it returns the value UNKNOWN in the applicable field.

The report appears on the screen. No HTML report is generated.


Chapter 15 Call Trace Summary


OL-4495-04


C H A P T E R 16
Command Scheduler
The Command Scheduler allows you to schedule a command to execute daily, weekly, or monthly at a specific time. Once a command is scheduled, the Scheduler allows you to remove a command from the schedule. Regardless of whether the command previously executed, the command can be removed at any time. If the command is scheduled to recur and is currently executing within the Element Management System (EMS), the command completes in a normal fashion but is removed from the list from that point forward.

It is often necessary to schedule commands to occur during periods of least system activity. Using the start-time and recurrence command tokens, you can schedule commands at any time and at any frequency. The recurrence token schedules a command daily, weekly, or monthly. Scheduling a command without the recurrence token causes the Command Scheduler to execute the command only once.

The characteristics of a scheduled command are read once at execution time. During execution, the characteristics can be changed but do not affect the command that is running.

ShowThis section describes the scheduled-command show command.

Step 1 Use the following command example to show a particular scheduled command:

Note A command must be added before it can be shown.

show scheduled-command id=1234;

AddThis section describes the scheduled-command add command.

Step 1 Use the following command example to add a scheduled command:

add scheduled-command start-time=2001-10-01 12:22:22; noun=database; verb=audit;


Chapter 16 Command Scheduler

ChangeThis section describes the scheduled-command change command.

Step 1 Use the following command example to change a scheduled command:

change scheduled-command id=1234; start-time=2001-10-02 20:00:00;

DeleteThis section describes the scheduled-command delete command.

Step 1 Use the following command example to delete a scheduled command:

delete scheduled-command id=1234;


OL-4495-04


C H A P T E R 17
SNMP Interface
The Cisco BTS 10200 Softswitch supports Simple Network Management Protocol (SNMP) operations that allow communications between the Element Management System (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. (See Figure 1.) Status and control operations as well as traffic and statistics query operations are supported.

Figure 1 NMS/EMS Interaction Via SNMP

Element Management System (SNMP Agent)The Softswitch SNMP Agent supports SNMPv2c operations defined by the opticall.mib Management Information Base (MIB). The MIB is located in the directory /opt/BTSsnmp/etc on the EMS. The MIB opticall.mib uses variables from three other MIBs: IPCELL-TC, SNMPv2-TC, and SNMPv2-SMI. The NMS needs to load the main MIB (opticall.mib), that will in turn import the three other MIBs.

SNMP Agent FunctionsThe following functions are supported by the Softswitch SNMP Agent:

• "MIB-II System branch information

• Collection of statistics and traffic management data

• Status and control

• Bulk Status and control

NMS

GETGETNEXTGETBULK

SET TRAPS

5438

9EMS


Chapter 17 SNMP InterfaceSNMP Agent Functions

• SNMP trap reports

• SNMP trap retransmission

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.

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

. In addition, in order to perform Status/Control via SNMP, the community string used must also be at a minimum level to perform those commands as defined by the BTS 10200 Command Line Interface (CLI) security privileges. For example, if the community string used to control a termination in service (INS) is below the minimum level in the CLI, then the SNMP request fails with General Error.

The SNMP community table in the 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=.....; key1=command_level; value1=8;

– To add write community-add snmpconfig type=writecommunity; value=.....; key1=command_level; value1=8;

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

Statistics/Traffic MeasurementStatistical data (traffic measurements) are collected for the following components of the Softswitch:

• AINSVC

• Announcement

• Audit

• Billing

• Call Processing

• DQOS

• Element Manager

• H323

• INAP

• ISDN

• ISUP SGA

• M3UA


OL-4495-04


• MGCP Adapter

• POTS-Feature Server

• SCCP

• SCTP

• SIA

• SIM

• SNMP

• SUA

• TCAP

• Trunk group usage

• TSA

SNMP Trap ReportsTraps are sent from the 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 to SNMPTRAPDEST via CLI. For the specific CLI command, refer to the CLI Reference Guide.

• 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 - Ranges from 0-32767. Default is 32767. A bitmask that specifies which subsystem types of the events to filter or permitted to be sent to this address. This is used in combination with Filterlevels to provide a granular filter for traps from the SNMP Agent side. From right to left the following bits specifies the following subsystem types: Bit #1: BILLING (right-most bit) Bit #2: CALLP Bit #3: CONFIG Bit #4: DATABASE Bit #5: MAINTENANCE Bit #6: OSS Bit #7: SECURITY Bit #8: SIGNALING Bit #9: STATISTICS Bit #10: SYSTEM Bit #11: AUDIT (left-most bit) For example, in order to receive only CONFIG, DATABASE, and SIGNALING traps, then the filter in binary would be (0010001100) which converts to integer value of (140) to be


OL-4495-04


entered as the token value. If all types are to be received then the binary would be (1111111111) which converts to (1023) as the token value. And likewise if no types are to be received then the binary would be (0000000000) which converts to (0) as the token value.

• Filter Levels - Ranges from 0-63. Default is 56. A bitmask that specifies which levels of the events to filter or permitted to be sent to this address. This is used in combination with Filtertypes to provide a granular filter for traps from the SNMP Agent side. From right to left the following bits specifies the following levels: Bit #1: DEBUG (right-most bit) Bit #2: INFO Bit #3: WARNING Bit #4: MINOR Bit #5: MAJOR Bit #6: CRITICAL (left-most bit) For example, in order to receive only INFO, MINOR, and MAJOR traps, then the filter in binary would be (011010) which converts to integer value of (26) to be entered as the token value. If all levels are to be received then the binary would be (111111) which converts to (63) as the token value. And likewise if no levels are to be received then the binary would be (000000) which converts to (0) as the token value. WARNING: Any filter that permits levels DEBUG and/or INFO traps will cause a high number of traps to be sent and tax the system resources on the SNMP Agent on the EMS; care must be taken when specifying numbers that converts to binary containing bits 1 or 2 turned on such as (49-51), (57-59), (61-63), etc.

Once this is done, the NMS will start receiving traps.

Note It is the responsibility of the NMS operator to filter the traps that are displayed on the NMS and those that are discarded.

Status and Controls

Querying and Controlling EMS, BDMS, CA and FS

Status queries on the following components can be performed by simple GET/GETNEXT operations:

• Primary and secondary EMS

• Primary and secondary BDMS

• Primary and secondary CA

• Primary and secondary POTS/Centrex/Tandem FS

• Primary and secondary AIN FS

Controls can be performed on these components using the SET operation, but only on the primary component (primary EMS, primary CA and primary FS). The primary component, in turn, controls the secondary component. If the operator tries to perform a SET operation on the secondary component, the agent returns an error.

Querying and Controlling Various Components

Status queries on the current status of the following components can be performed by GET/GETNEXT operations on the variousState columns in the MIB.

• Media Gateway (MGW)

• Trunk Group (TG)




OL-4495-04


• SGP

• DPC

• SCTP Association

In addition, controls can be performed on the following components by SETs on various columns in the MIB.

• Media Gateway (MGW)

• Trunk Group (TG)



• SCTP Association

Controls can be performed as follows.

Step 1 Perform SET operations on all the necessary fields (Mode column and TargetState column, and so forth).

Step 2 Perform a SET operation on ControlState column, using the value of 1 (commit) to actually put the component into its target state.

If the user performs a GET/GETNEXT operation on the ControlState when all necessary fields are NOT set, then a value of 2 (insufficient-data) is returned. If all necessary fields ARE set, then a value of 3 (ready-to-commit) is returned.

Querying and Controlling Bulk Status of Various Components

Bulk Status queries on the current status of the following components can be performed by GET/GETNEXT operations on the following branch: .iso.org.dod.internet.private.enterprises.ipcell.opticall.statusControlBulk. The results return from querying these components are a Page Number column and a Status Value column. The Status Value column specifies each component id and the statuses in enumerated value correlating to the statuses of those components above.

• Media Gateway (MGW) - The Status Value column specifies delimited string of X number of MGWs. The delimiters are: ';' = delimits each MGW. '|' = delimits status fields. The protocol of which is: 'MGW_ID|admin_state|oper_state;MGW_ID|admin_state...' And example: 'MGW_ABC|1|3;MGW_XYZ|1|3...' The enumerated states are the same as that of mediaGatewayOAMPTable.

• Trunk Group (TG) - The Status Value column specifies delimited string of X number of Trunk Groups. The delimiters are: ';' = delimits each Trunk Group. '|' = delimits status fields. The protocol of which is: 'TGN_ID|admin_state|oper_state;TGN_ID|admin_state...' And example: '232|1|3;233|1|3...' The enumerated states are the same as that of trunkGroupOAMPTable.

• Subscriber Termination - The Status Value column specifies delimited string of X number of Subscriber Terminations. The delimiters are: ';' = delimits each Subscriber Termination. '|' = delimits status fields. The protocol of which is: 'SUB_ID|admin_state|oper_state;SUB_ID|admin_state...' And example: 'SUB_ABC|1|3;SUB_XYZ|1|3...' The enumerated states are the same as that of subscrLineTermOAMPTable.

• Trunk Termination - The Status Value column specifies delimited string of X number of Trunk Terminations. The delimiters are: ';' = delimits each Trunk Termination. '|' = delimits status fields. '.' = delimits CIC and TGN_ID. The protocol of which is:


OL-4495-04

Chapter 17 SNMP InterfaceAccessing the SUN Solaris SNMP Agent

'TGN_ID.CIC|admin_state|oper_state|static_state|dynamic_state;CIC.TGN_ID|admin_state...' And example: '232.22|1|3|1|1;233.22|1|3|1|1...' The enumerated states are the same as that of trunkTermOAMPTable.

Accessing the SUN Solaris SNMP AgentThere are two possible methods to access and query the SUN Solaris SNMP Agent:

1. Directly through a non-standard SNMP port.

Note The Cisco BTS 10200 Softswitch SNMP Master Agent cannot be full when accessing or querying through a non-standard SNMP port.

2. Through the Cisco BTS 10200 Softswitch SNMP Master Agent using standard port 161.

Note You must be SNMPv2c compliant because the Cisco BTS 10200 Softswitch SNMP Agent proxies queries to the SUN Solaris Agent, which only supports SNMPv1. You must specify SNMPv1 as the SNMP version when accessing or querying using standard port 161..

Direct Access to a Non-Standard SNMP PortPerform the following steps to access and query the SUN Solaris SNMP Agent using a non-standard SNMP port:

Step 1 Modify following parameters in /etc/snmp/conf/snmpd.conf file:

a. read-community

- specify a user-defined community string for read access

- enter only one value

b. managers

- specify the IP or hostname for querying the entity (NMS)

- you can specify multiple entries delimited by spaces

Note You must retain the localhost as one of the entries in order to retain communication with BTS SNMP Master Agent.

Step 2 Restart SUN Solaris SNMP Agent

/etc/init.d/S98mibiisa stop/etc/init.d/S98mibiisa start

Step 3 Begin directly querying SUN Solaris SNMP Agent with the specified read-community string using port 13230.


OL-4495-04


Through the Cisco BTS 10200 Softswitch SNMP Master Agent Using Port 161Perform the following steps to access and query the SUN Solaris SNMP Agent Through the Cisco BTS 10200 Softswitch SNMP Master Agent Using Port 161:

Step 1 Modify following parameters in /etc/snmp/conf/snmpd.conf file:

a. read-community

- specify a user-defined community string for read access

- enter only one value

b. managers

- verify that the localhost is one of the entries

Step 2 Modify the SNMP configuration type and value:

add snmpconfig type=SETTING; value=COUPLE_SUN_AGENT

Step 3 Restart BTS SNMP Master Agent.

Step 4 Log in as root.

kill `ps -ef | grep -i sad | grep -v grep | awk '{print $2}'`

Step 5 Begin querying the SUN Solaris SNMP Agent object id (OID) with the specified read-community string using standard port 161.


OL-4495-04



OL-4495-04


C H A P T E R 18
Managing Event Message and Alarm Logs
The Cisco BTS 10200 Softswitch generates messages, or events, to notify you of network conditions. Events with severity levels of critical, major, and minor are classified as alarms. Events and alarms are reported to the operator console and can be retrieved through command-line interface (CLI) commands or a Simple Network Management Protocol (SNMP) manager.

Alarms and informational events produce different system responses.

• An alarm is reported whenever an alarmed state changes (assuming the alarm has a reported severity).

• An informational event is reported just once, upon its occurrence, through the operator interfaces without any state change being required.

An informational event indicates that a condition worthy of note has occurred. The event is transient and it needs to be reported; however, there is no corrective action that can be initiated by the network operations center. An invalid protocol call state transition is an example of an informational event.

The Cisco BTS 10200 Softswitch software writes event and alarm messages to log files that are set up during system initialization. This chapter provides information on using and working with event and alarm log files.

This chapter contains the following sections:

• Managing Event and Alarm Reports, page 18-2

• Format of Event and Alarm Reports, page 18-3

• Event Message and Alarm Logs, page 18-4

• Viewing Event or Alarm Logs, page 18-5

• Saving Events to Log Files, page 18-6

• Managing and Responding to Events and Alarms, page 18-8

Note Refer to the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide, Release 4.1 for a detailed description of all commands and tokens discussed in this chapter.


http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts4_1/cli/index.htm

Chapter 18 Managing Event Message and Alarm LogsManaging Event and Alarm Reports

Managing Event and Alarm ReportsThere are two ways to view events and alarms—by subscribing to event and alarm reports (automatic, real-time) and by retrieving event or alarm summaries from the log files by operator query.

Use the following subscribe commands to subscribe to reports of real-time event messages or alarms:

subscribe event-report type=all | type=<type>; severity=all | severity=<severity>;

subscribe alarm-report type=all | type=<type>; severity=all | severity=<severity>;

Note In the subscribe event-report or subscribe alarm-report commands you can specify “type=all” and/or “severity=all” or you can specify the specific types and severities of events and alarms you wish to display. Cisco recommends that you choose to receive all types and all severities of all event and alarm reports. This allows you to monitor the system for all events or alarms and you will be alerted quickly if there is trouble.

Show Alarm CommandUse the show alarm command to view all real-time alarms. All of the following tokens are optional.

show alarm id=<sn>; type=<type>; number=<num>; severity=<sev>; component-id=<comp>; origin=<process>; start-time=<yyyy-mm-dd hh:mm:ss>; end-time=<yyyy-mm-dd hh:mm:ss>

Note If the show alarm command is issued without any tokens (parameters), all alarms of all types for all components are displayed. Issuing the show alarm command with any combination of the optional tokens limits the display to a subset of alarms as determined by which optional tokens are specified.

The show alarm command can include any or all the following optional tokens:

• id—The unique system-assigned serial number of an alarm.

• type—Type of alarm to show, which can be any one of the following:

– audit

– billing

– callp

– config

– database

– maintenance

– oss

– security

– signaling

– statistics

– system

• number—The numerical identifier of the alarm of the specified type (1 to 150).

Specifying a type and a number shows only alarms of that type and number. You can specify a number without specifying a type; and you can specify a type without specifying a number.


OL-4495-04

Chapter 18 Managing Event Message and Alarm LogsManaging Event and Alarm Reports

• severity—The severity level of the alarm, which can be any one of the following:

– critical

– major

– minor

• origin—The internal designation of the process generating the alarm(s) (1 to 64 ASCII characters).

• component-id—The id of the component reporting the alarm(s) (1 to 64 ASCII characters).

• start-time or end-time—Timestamp indicating the time the monitoring of the specified alarm states should start or end in the format yyyy-mm-dd hh:mm:ss where:

– yyyy—year (4-digit number)

– mm—month (01 to 12)

– dd—day (01 to 31)

– hh—hour (00 to 23)

– mm—minute (00 to 59)

– ss—second (00 to 59)

Ack Alarm CommandUse the ack alarm command to acknowledge an alarm.

ack alarm id=<sn>;

The id token is required for the ack alarm command, which acknowledges only the specified alarm.

Clear Alarm CommandUse the clear alarm command to clear an alarm.

clear alarm id=<sn>;

The id token is required for the clear alarm command, which clears only the specified alarm.

Format of Event and Alarm ReportsThe general format of an event or alarm report, as displayed on an operator console, is shown below. An event or alarm summary contains multiple event or alarm reports, selected according to the query that is entered. For example, the following query produced the result shown here.

show alarm type=callp; number=23; [email protected]

Reply : Success: Request was successfully completedID=123456TYPE=callpNUMBER=23TEXT=Trunk Group Out Of ServiceSTATUS=ACKNOWLEDGEDSEVERITY=MAJORTIME=2004-04-23 10:54:20COMPONENT [email protected]


OL-4495-04

Chapter 18 Managing Event Message and Alarm LogsEvent Message and Alarm Logs

ORIGIN=bcm@ca146THREAD=DATAWORD1=

through

DATAWORD8=

Table 18-1 describes the format of event and alarm reports.

Event Message and Alarm LogsIt is recommended that you manage the event and alarm messages and logs in a manner that permits the operator to access all events and alarms and watch for unexpected events or alarms. For example, if any of the following anomalies are seen, investigate promptly to determine the required action:

• Congestion warnings

• Routing errors

• Termination failures

• Billing errors

• Security warnings

• Diagnostic failures

• Process failovers

Table 18-1 Format of Event and Alarm Reports

Event or Alarm Report Contents Description

Event or Alarm Serial Number All events and alarms have a unique, system-assigned serial number.

Event or Alarm Type Type is the designated category of the report: AUDIT, BILLING, CALLP, CONFIG, DATABASE, MAINTENANCE, OSS, SECURITY, SIGNALING, STATISTICS, or SYSTEM.

Event or Alarm Number Event or alarm numbers are preset in the Cisco BTS 10200 Softswitch. They are not provisionable and cannot be changed.

Event or Alarm Description Up to an 80-character description of the event or alarm.

Alarm Status Status for an alarm can be ALARM_ON, ALARM_OFF, or ALARM_IGNORE.

Event or Alarm Severity Severity of the alarm: CRITICAL, MAJOR, MINOR.Severity of the event: WARNING, or INFO

Event or Alarm Date and Time Date and time of report in the format yyyy-mm-dd hh:mm:ss.

Year, month, and day plus hours, minutes, and seconds of an alarm or event, displayed in Greenwich Mean Time (GMT).

Event or Alarm Component ID ID for the component reporting the event or alarm, for example, [email protected].

Event or Alarm Origin ID for the process generating the event or alarm.

Event or Alarm Thread Thread within the BTS process that initially issued the alarm.

Event or Alarm DataWordn= Header for additional data fields to an event or alarm. Up to 8 data fields can be reported, depending on the event or alarm.


OL-4495-04

Chapter 18 Managing Event Message and Alarm LogsViewing Event or Alarm Logs

Viewing Event or Alarm LogsUse the following show commands to view event or alarm logs. The event and alarm logs are typically used if the user session is disrupted, or if all events or alarms of one kind are needed in a single report.

show event-log id=<sn>; type=<type>; number=<num>; severity=<severity>; component-id= <component-id>; origin=<process-id>;start-time=<yyyy-mm-dd hh:mm:ss>; end-time=<yyyy-mm-dd hh:mm:ss>;

show alarm-log id=<sn>; type=<type>; number=<num>; severity=<severity>; component-id=<component-id>; origin=<process-id>; start-time=<yyyy-mm-dd hh:mm:ss>; end-time=<yyyy-mm-dd hh:mm:ss>;

Note If the show event-log or show alarm-log commands are issued without any tokens (parameters), all events or alarms of all types and all severities for all components are displayed.

Issuing the show event-log or show alarm-log commands with any combination of optional tokens limits the display to a subset of events or alarms as determined by the optional tokens specified.

The show commands can include any or all of the following optional tokens:

• id—The unique serial number of the event or alarm assigned by the system.

• type—The type of event or alarm to show, which can be any one of the following:

– audit

– billing

– callp

– config

– database

– maintenance

– oss

– security

– signaling

– statistics

– system

• number—The numerical identifier of the event or alarm of the specified type (1 to 150).

• severity—The severity level of the event or alarm, which can be any one of the following:

– critical

– major

– minor

– warn (events only)

– info (events only)

• origin—The internal designation of the process generating the event or alarm (1 to 64 ASCII characters).

• component-id—The id of the component reporting the event or alarm (1 to 64 ASCII characters).

Specifying the component-id, setting type to a value, and specifying a number displays only alarms of that type and number from the designated component.


OL-4495-04

Chapter 18 Managing Event Message and Alarm LogsSaving Events to Log Files

• start-time or end-time—The timestamp indicating the time interval for reporting events or alarms in the format <yyyy-mm-dd hh:mm:ss> where:

– yyyy—year (4-digit number)

– mm—month (01 to12)

– dd—day (01 to 31)

– hh—hour (00 to 23)

– mm—minute (00 to 59)

– ss—second (00 to 59)

Event QueueThe event-queue commands allow showing, adding, or deleting an event queue on a Call Agent or Feature Server.

show event-queue instance=CA146add event-queue instance=CA146delete event-queue instance=CA146

The event-queue commands must include the mandatory instance token, which specifies the Call Agent or Feature Server (CAnnn, FSPTC, FSAIN) where the event queue is located. Only one instance can be shown, added, or deleted at a time.

Saving Events to Log FilesUse the commands in this section to manage the way events and alarms are saved to their respective logs.

Show Report-PropertiesUse the following show report-properties command to view the event or alarm properties currently used to specify which event levels, events, and alarms are saved to the event or alarm logs:

CLI>show report-propertiesReply : Success: Entries 1-3 of 3 returned.

TYPE=EVENT_LOGSIZEVALUE=30000

TYPE=ALARM_LOGSIZEVALUE=30000

TYPE=EVENT_LEVELVALUE=INFO

Note The show report-properties command, without any tokens, returns all alarm-logsize, event-logsize, and event-level data.

There are no mandatory tokens (parameters) required for the show report-properties command; however, you can optionally use the type and/or value tokens described below.


OL-4495-04


Changing Report-PropertiesUse the following change report-properties command to specify the maximum number and/or the severity of event or alarm entries to be saved to the event or alarm logs:

change report-properties type=<event-logsize|alarm-logsize>; value=<logsize>;

or

change report-properties type=<event-level>; value=<severity>

The type and value tokens are both mandatory for the change report-properties command.

• If type=event-logsize or alarm-logsize, then value must be an integer between 1 to 30000.

• If type=event-level, then value designates the severity of the events or alarms to include in the log files, which can be critical, major, minor, warn, or info.

All events or alarms whose severity is equal to or greater than the event level specified are included in the designated event or alarm log file.

Tip Cisco recommends that you store events of all severity levels in the event and alarm log files by entering info as the value in this command. This permits the operator to access all event and alarm reports.

Changing Threshold and Throttle ValuesThe threshold and throttle values used in event and alarm reporting are user-provisionable. You can use the following show event-prov command to display the current threshold and throttle values for any event or alarm message:

CLI>show event-prov type=callp; number=9;Reply : Success: Entry 1 of 1 returned.

REPORTTYPE=2REPORTNUMBER=9REPORTDESCRIPTION=No Route Available for Carrier DialedTHRESHLIM=100THROTTLELIM=20DW1NAME=Orig Type(Trunk or SDW2NAME=Orig Sub or TG idDW3NAME=Calling Party NumberDW4NAME=Called Party NumberDW5NAME=Carrier Code DialedDW6NAME=n/aDW7NAME=n/aDW8NAME=n/aCAUSE1=No route is available for the interexchange carrier (IXC) dialed.ACTION1=The data words in the event report indicate the parameters that need to be corrected. Refer to office records for the carrier.CAUSE2=Parameter(s) in the carrier and/or route-grp table are missing or incorrect for the carrier.ACTION2=Determine whether the routing parameters were entered correctly in the carrier and/or route-grp tables.ACTION3=If the carrier-id or route-grp-id are not specified, or are incorrect in the dial-plan table, enter the correct values. Use the change carrier or change route-grp command.

The command show event-prov with no parameters displays all events that are provisioned. The command show event-prov with only type specified displays all events of that type.


OL-4495-04


Use the following change event-prov command to specify event threshold and throttle values other than the defaults:

change event-prov type=<type>; number=<n>; threshold=<n>; throttle=<n>;

• threshold—This value is the maximum number of reports of the event or alarm that can be reported in a 30-minute interval. Valid values are 1 to 100.

• throttle—This value is the number of occurrences of the designated event or alarm message required to trigger the issuance of one report. Valid values are 1 to 100.

The total number of occurrences of the designated event or alarm message is determined by multiplying these two parameters (threshold X throttle). The system maximum number of occurrences of an event or alarm that can be reported in any 30-minute interval is 100x100 or 10,000.

Managing and Responding to Events and AlarmsTo manage and respond to events and alarms, complete the following steps:

Step 1 Set the event-logsize and event-level parameters as desired using the report-properties command (see the “Changing Report-Properties” section on page 18-7).

Step 2 Subscribe to events and request event summary reports as needed using the subscribe command (see the “Managing Event and Alarm Reports” section on page 18-2).

Step 3 Set the alarm-logsize and event-level parameters as desired using the report-properties command (see the “Changing Report-Properties” section on page 18-7).

Step 4 Subscribe to alarms and request alarm summary reports as needed using the subscribe command (see the “Managing Event and Alarm Reports” section on page 18-2).

Step 5 Set the threshold and throttle parameters as desired using the change event-prov command (see the “Changing Threshold and Throttle Values” section on page 18-7).

Step 6 View event and alarm reports and investigate potential problems.

Examples of problems to look for include: congestion warnings, routing errors, termination failures, billing errors, diagnostic failures, security warnings, and process failovers.

Step 7 Refer to the “Probable Cause” and “Corrective Action” instructions for events and alarms in Chapter 19, “Event Messages and Alarms.”

Step 8 Take the necessary corrective action; escalate the problem if necessary.

The situation that caused an event or alarm must be resolved before the event or alarm can be cleared.

Step 9 After the problem is fixed, enter the following command to clear a specific alarm:

clear alarm id=<sn>

where id is the system-assigned serial number of the event or alarm.

Events (severity levels of info or warn) do not need to be cleared.


OL-4495-04


C H A P T E R 19
Event Messages and Alarms
For the information on the event and alarm messages, refer to the Cisco BTS 10200 Troubleshooting Guide, Release 4.4, Chapter 2 through Chapter 12.


Chapter 19 Event Messages and Alarms


OL-4495-04


C H A P T E R 20
Congestion Detection and Protection
This chapter describes the congestion detection and protection feature, which includes the following capabilities:

• The system detects internal messaging congestion caused by traffic overload or other extraordinary events, and takes preventive action to avoid system failure (including shedding of traffic)

• The system generates alarms when internal messaging congestion is detected, and clears the alarms when congestion abates

• When the internal call processing engine is congested, the system places the access control list (ACL) parameter (indicating congestion) into the release messages sent to the SS7 network.

This feature functions automatically, and is not provisionable via command line interface (CLI) commands.

Special Treatment for Emergency MessagesWhen the Cisco BTS 10200 Softswitch is in a congested state, emergency messages are given special treatment, and are allowed to pass through. The dialed digit strings for emergency calls are specific to each region. Up to ten digit strings can be specified (911 and 9911 are included by default). Your Cisco account team can provide additional information about how your Cisco BTS 10200 Softswitch is set up to detect dialed digit strings for emergency calls.

Tip The emergency.lst file is described in the following paragraph. Note that this file should be filled out prior to bringing your system into service. If you need to make changes to this file after your system is in service and carrying live traffic, it will be necessary to modify the list and then restart the CA. Do not attempt to make these modifications on your own. Instead, contact Cisco TAC for assistance.

Caution Do not modify the emergency.lst file on a live traffic-carrying system until you have an approved procedure, applicable to your specific installation, from Cisco TAC.

The Cisco BTS 10200 Softswitch uses emergency numbers stored in the emergency.lst file to determine which calls to force through to the destination. The emergency.lst file is stored in the /opt/OptiCall/CA146/bin directory. The default emergency.lst file, containing the default 911 and 9911 dialed digits, is shown below. Note that each digit pattern is listed on a separate line.


Chapter 20 Congestion Detection and ProtectionBilling Records

### Copyright (c) 2002, 2003 by Cisco Systems, Inc.

#

# This file contains the possible dialed digit-patterns

# for emergency calls.

# Each line should contain only one digit-pattern.

# Line started with '#' is considered as comment.

# There could be up to 10 (at most) digit-patterns included

# in this file.

# Each digit-pattern could have at most 15 digits.

911

9911

Billing RecordsThe following billing records are created when a call is rejected due to overload conditions:

• SS7 termination cause code 42

• Cable signaling stop event cause code “resource unavailable”

Note Calls rejected by the signaling adapter will not generate a billing record.

Events and AlarmsTable 20-1 lists the alarms and events the Cisco BTS 10200 Softswitch can generate for congestion detection and protection events.

Table 20-1 Alarms for Congestion Detection and Protection Events

Alarm Severity Comments Maintenance(97) Critical The indicated thread is not able to process its IPC1 input messages

fast enough. The input queue has grown too large and is using up too much of the IPC memory pool resource.

1. IPC = Interprocess communications (an internal Cisco BTS 10200 Softswitch process)

Maintenance(98) Minor The indicated thread is not able to process its IPC input messages fast enough. The input queue has grown too large and is at 25% of the level at which it will enter the throttle state.

Maintenance(99) Major The indicated thread is not able to process its IPC input messages fast enough. The input queue has grown too large and is at 50% of the level at which it will enter the throttle state.

Maintenance(100) Critical The indicated thread is not able to process its IPC input messages fast enough. The input queue has grown too large and is at 75% of the level at which it will enter the throttle state.


OL-4495-04

Chapter 20 Congestion Detection and ProtectionAdditional References

See Chapter 19, “Event Messages and Alarms,” for a complete description of all alarms and events generated by the Cisco BTS 10200 Softswitch.

Additional ReferencesFor additional information on the industry standard for this feature, refer to Telcordia LSSGR document GR-317-CORE /3.1.4.12, Automatic Congestion Control Procedures.

For additional information related to Cisco BTS 10200 Softswitch billing functions, refer to the following documents:

• Cisco BTS 10200 Softswitch Release 4.1 Billing Interface Guide—Management procedures and contents of the call detail blocks (CDBs) generated by the Call Agent for billing

• Cisco BTS 10200 Softswitch Release 4.1 PacketCable Feature Guide—Management procedures and contents of the event messages (EMs) generated by the Call Agent for billing (typically used in PacketCable-based networks)


OL-4495-04

Chapter 20 Congestion Detection and ProtectionAdditional References


OL-4495-04


C H A P T E R 21
Disaster Recovery Procedures
This chapter describes how to archive your database, when and how to backup your database, how to recover your database in a disaster situation, how to recover your database from another database, and how to recover the data in the Call Agent shared memory.

Cisco recommends backing up all data on the Element Management System (EMS), Call Agent (CA) and Feature Server (FS) platforms on a daily basis. Then save the backed up data to a remote server. Data backup files are needed in the unlikely event that data on both the primary and secondary sides of any platform become corrupted. In that case, the data must be restored from a backup file.

Flash ArchiveThe purpose of this section is to show how the flash archive tool is used with the Cisco BTS 10200 Softswitch. This procedure is used ONLY when both mirrored disks are corrupted or cannot be booted.

Flash Archive is a Sun Solaris tool that allows you to take an image of a host and store it on a NFS server that can be used later for disaster recovery. The tool is available on Solaris 8 hardware release 04/01 or higher.

For the Cisco BTS 10200 Softswitch, it is recommended to take a system flash archive whenever the Solaris Operation System has been modified by adding patches.

Creating an ArchivePerform the following steps to create an archive


Step 2 Stop all platforms. If this is a primary node, then use the CLI command to control the standby forced active.

Step 3 At the # prompt, type the following commands:

#mv /bin/date /bin/date.orig#mv /bin/.date /bin/date# tar -cvf /mnt/<local_hostname>.tar host*


Chapter 21 Disaster Recovery ProceduresFlash Archive

Step 4 At the # prompt, type the following command:

flarcreate -n <archive name> -c /opt/<file name>

Note archive name: is the archive identification.

Example: <hostname>#flarcreate -n CCPU-EMS -c /opt/secems04.archive

Step 5 Ftp the archive and tar files to an nfs server.

Step 6 Remove the archive and tar files from /opt.

Step 7 At the # prompt, type the following commands:

#mv /bin/date /bin/.date#mv /bin/date.orig /bin/date

Restoring an ArchiveBefore restoring your archive you must have the following information:

• Solaris 8 CD 1 of 2

• Host name

• IP address and netmask

• DNS information

• Location of an archive

• Console access

To restore your archive, perform the following steps:

Step 1 Connect the laptop to the console. Put the Solaris-8 1 of 2 CD into the CD-ROM drive.

Step 2 At the ok> prompt, type: boot cdrom

Step 3 Enter 0 for English

Step 4 Enter 0 for English again

Step 5 Enter 13 for other

Step 6 Enter vt100 for terminal type

Step 7 Press Esc-2 to continue


Step 9 Press Esc-2 to continue, use default setting (Mark X on Yes for Networked)

Step 10 Press Esc-2 to continue, use default setting (Mark X on No for Use DHCP)

Step 11 Press Esc-2 to continue, use default setting (Mark X on hme0 for Primary Network Interface)

Step 12 Enter <hostname>, then press Esc-2 to continue

Step 13 Enter <IP address>; then press Esc-2 to continue

Step 14 Press Esc-2 to continue, use default setting (Mark X on Yes for System part of a subnet)

Step 15 Enter <Netmask>; then press Esc-2 to continue


OL-4495-04


Step 16 Press Esc-2 to continue, use default setting (Mark X on No for Enable IPv6)


Step 18 Press Esc-2 to continue, use default setting (Mark X on No for Configure Kerberos Security)


Step 20 Mark X on DNS for Name service, press Esc-2 to continue

Step 21 Enter <Domain name>, press Esc-2 to continue

Step 22 Enter <Server's IP address>, press Esc-2 to continue

Step 23 Enter <Search domain>, press Esc-2 to continue


Step 25 Press Esc-2 to continue, use default setting (Mark X on United States)

Step 26 Mark X on Timezone, press Esc-2 to continue

Step 27 Set date and time, press Esc-2 to continue


Step 29 After receiving message “System identification is completed.”

a. Enter Esc-4 for Initial OS installation

b. Enter Esc-4 for Flash OS installation

c. Mark X on NFS, Press Esc-2 to continue

Step 30 Provide the location of the archive.

Example 21-1 Archive Location

10.89.224.1:/archive/prica18.archiveEsc-2 to continue


Step 32 Press Esc-2 to continue, use default setting (Mark X on c0t0d0)


Step 34 Press Esc-4 to choose Customize on disk partition

Step 35 Press Esc-4 for Options

Step 36 Mark X on Load existing slices from VOTC label, press Esc-2 to OK

Step 37 Press Esc-2 to OK






Step 43 Press Esc-2 to begin installation, use default setting (Mark X on Manual Reboot)


OL-4495-04


Booting Up the System From Disk 0To boot up the system from disk 0, perform the following steps:

Step 1 When system finishes Solaris Flash Install, enter the following commands:

a. #cp /a/etc/system /a/etc/system.mirror

b. #cp /a/etc/vfstab /a/etc/vfstab.mirror

c. #cp /a/etc/inittab /a/etc/inittab.mirror

d. #mv /a/etc/rc3.d/S99platform /a/etc/rc3.d/saved.S99platform

Step 2 Edit the /a/etc/system file and remove the following lines if they appear:

• Begin MDD root info (do not edit)

forceload: misc/md_trans

forceload: misc/md_raid

forceload: misc/md_hotspares

forceload: misc/md_stripe

forceload: misc/md_mirror

forceload: drv/pcipsy

forceload: drv/simba

forceload: drv/glm

forceload: drv/sd

rootdev:/pseudo/md@0:0,2,blk

• End MDD root info (do not edit)

• Begin MDD database info (do not edit)

set md:mddb_bootlist1=”sd:244:16 sd:244:1050 sd:244:2084 sd:260:16”

set md:mddb_bootlist2=”sd:260:1050 sd:260:2084”

• End MDD database info (do not edit)

Step 3 Enter: #cp /a/etc/inittab.orig /a/etc/inittab

Step 4 Enter: #cp /a/etc/vfstab.org.mirror /a/etc/vfstab

Step 5 Edit the /a/etc/vfstab file. It will look like the following example:

##############################################################################device device mount FS fsck mount mount#to mount to fsck point type pass at boot options##/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes-fd - /dev/fd fd - no -/proc - /proc proc - no -/dev/dsk/c0t0d0s3 - - swap - no -/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no -/dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0s1 /var ufs 1no-/dev/dsk/c0t0d0s5 /dev/rdsk/c0t0d0s5 /opt ufs 2yes


OL-4495-04


-swap - /tmp tmpfs - yes -##############################################################################

Step 6 Enter: #cp /bin/date /bin/.date

Step 7 Enter: #mv /bin/date.orig /bin/.date

Step 8 Enter: #shutdown -y -g0 -i6

Step 9 Enter root, <password>, Return

Step 10 Enter root, <password> again, Return

Restoring the Cisco BTS 10200 Softswitch ApplicationTo restore the software application, perform the following steps:

Step 1 Copy the tar file from NFS server to /opt directory

Step 2 Enter: <hostname>#gzip -cd <hostname_release>.tar.gz | tar -xvf -

Step 3 Enter: <hostname>#cp /etc/system.mirror /etc/system

Step 4 Enter: <hostname>#cp /etc/vfstab.mirror /etc/vfstab

Step 5 Enter: <hostname>#cp /etc/inittab.mirror /etc/inittab

Step 6 Ftp the following file from its mate

cd /tmp

Step 7 Ftp <its mate ip address>


Step 9 Enable binary transfer:

ftp>bin

Step 10 At the ftp prompt, enter the following commands:

a. cd /etc

b. get hosts host

c. get netmasks

d. cd inet

e. get ntp.conf

f. get resolv.conf

g. get passwd

h. get shadow

i. get group

Step 11 Exit the FTP session:

ftp>bye

Step 12 Enter: <hostname>#cd /tmp


OL-4495-04


Step 13 Enter: <hostname>#cp -p passwd /etc/

Step 14 Enter: <hostname>#cp -p shadow /etc/

Step 15 Enter: <hostname>#cp -p group /etc/

Step 16 Enter: <hostname>#cp -p resolv.conf /etc/

Step 17 Enter: <hostname>#cd /opt/setup

Setting Up InterfacesTo setup your interfaces, perform the following steps:

Step 1 Enter: <hostname>cd /opt/setup

Step 2 Perform this step only if the system has a znb interface:

a. Enter: cd /opt

b. Enter: tar -xvf ZNYXnb.sparc.tar

c. Enter: pkgadd -d. ZNYXnb

d. Answer n

e. Answer y

f. Answer q to quit

Step 3 Run sethost.sh for CA/FS and setconems.sh for EMS.

Setting Up MirroringTo setup mirroring, perform the following steps:

Step 1 Set up the mirror on the Call Agent and Feature Server (CA/FS):

a. Enter: cd /opt/setup

b. Enter: /setup_mirror_ca

Ignore this error: mv: cannot access ./vfstab_mirror.

c. Enter: ./setup_trans

Ignore this error: mv: cannot access ./vfstab_trans.


OL-4495-04


d. Edit the /etc/vfstab file. It will look like the following example:

#######################################################device device mount FS fsck mount #to mount to fsck point type pass at boot options##/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -fd - /dev/fd fd - no -/proc - /proc proc - no -/dev/md/dsk/d8 - - swap - no noatime/dev/md/dsk/d2 /dev/md/rdsk/d2 / ufs 1 no noatime/dev/md/dsk/d19 /dev/md/rdsk/d19 /var ufs 1 no noatime/dev/md/dsk/d20 /dev/md/rdsk/d20 /opt ufs 2 yes noatimeswap - /tmp tmpfs - yes -#######################################################

e. Type: reboot

f. Log in as root

g. Enter: cd /opt/setup

h. Enter: ./sync_mirror

Step 2 Set up the mirror on the EMS:

a. Enter: cd /opt/setup

b. Enter: ./setup_mirror_ems

Ignore this error: mv: cannot access ./vfstab_mirror.

c. Enter: ./setup_mirror_trans

Ignore this error: mv: cannot access ./vfstab_trans.

d. Edit the /etc/vfstab file. It will look like the following example:

#######################################################device device mount FS fsck mount #to mount to fsck point type pass at boot options##/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -fd - /dev/fd fd - no -/proc - /proc proc - no -/dev/md/dsk/d8 - - swap - no noatime/dev/md/dsk/d2 /dev/md/rdsk/d2 / ufs 1 no noatime/dev/md/dsk/d19 /dev/md/rdsk/d19 /var ufs 1 no noatime/dev/md/dsk/d20 /dev/md/rdsk/d20 /opt ufs 2 yes noatimeswap - /tmp tmpfs - yes -######################################################

e. Type: reboot

f. Log in as root

g. Enter: cd /opt/setup

h. Enter: ./sync_mirror

Wait until the mirroring is complete. This process will take some time.

Step 3 Enter: <hostname>#mv /etc/rc3.d/saved.S99platform /etc/rc3.d/S99platform

Step 4 Bring up the platform and verify that all platforms are in service


OL-4495-04

Chapter 21 Disaster Recovery ProceduresEMS Database Backup

EMS Database BackupThis backup procedure, written for the experienced Unix user, describes how to save the provisioning database from the EMS, and the shared memory data from the CA/FS, to a remote server. It is important

that the remote server be connected to a corporate LAN and backed up daily. This section also pro-vides steps to configure EMS database backups of the BTS 10200 system in order to sup-port a production environment.

Step 1 Cross check database before enabling backup processes. This has to be done on both primary and secondary EMS sites.

This step is required before ora_hot_backup.ksh and ora_arch_backup.ksh is scheduled. This process will validate database and archived log files for RMAN processes. The crosscheck process is only required to be executed once.

a. Login as oracle, or su - oracle

b. Enter the following command:

$ dbadm -E backup_crosscheck

The following is displayed

*****************************************************************You are about to execute the following process:

==> Oracle DB crosscheck for RMAN backup

database: optical1hostname: priems09

*****************************************************************

Do you want to continue? [y/n] y

/opt/oracle/admin/scripts/ora_arch_crosscheck.ksh ===> begins at Thu Apr 25 17:26:49 CDT 2002RMAN> 2> 3> 4>RMAN archivelog crosscheck completed at Thu Apr 25 17:26:55 CDT 2002

Log file: /opt/oracle/tmp/ora_arch_crosscheck_200204251726.log

c. Verify the log file to make sure that there is no error except the “validation failed for archived log” messages.

The “validation failed for archived log” of /data1/arch/opticalx_yyy.arc files can be ignored since the validation directs RMAN not to look for these *.arc files. These *.arc files have been purged by the ora_purge_archlog.ksh process.

RMAN-06157: validation failed for archived logRMAN-08514: archivelog filename=/data1/arch/optical1_25.arc recid=1 stamp=461878656


OL-4495-04


Step 2 Remove the archive log purge process, and schedule backup processes. This has to be done on both primary and secondary EMS sites.

a. Disable the ora_purge_archlog.ksh process

b. Enable the ora_hot_backup.ksh process

c. Optional: Enable the ora_arch_backup.ksh process

d. Login as oracle, or su - oracle:

e. Enter the following command:

$ crontab –e

f. Modify the crontab file as follows. This is on the primary EMS site, database name optical1.

## Daily Oracle Hot backup - this also include archive log backup# Note: Set hot backup process to run at 2:00am every day.#0 2 * * * /opt/oracle/admin/scripts/ora_hot_backup.ksh optical1 > /opt/oracle/tmp/ora_hot_backup.log 2>&1## Oracle archive log backups, in addition to daily hot backup.# Note: Set one additional archive log backup to run at 6:00pm every day.#0 18 * * * /opt/oracle/admin/scripts/ora_arch_backup.ksh optical1 > /opt/oracle/tmp/ora_arch_backup.log 2>&1## Purge archive log files# Note: Delete or uncomment this line to stop purging archive log files.##0 1,3,…,23 * * * /opt/oracle/admin/scripts/ora_purge_archlog.ksh optical1 > /opt/oracle/tmp/ora_purge_archlog.log 2>&1

g. Repeat step f. by replacing optical1 with optical2 on the secondary EMS site.

Step 3 Configure the remote FTP site.

a. Verify oracle user access and create backup directory on FTP server site.

Example:

Primary EMS hostname: priems Secondary EMS hostname: secems FTP server hostname: ftpserver FTP server Oracle password: ora00 FTP server backup directory: /opt/backup

First, test connection to remote ftpserver using oracle user access. If password of oracle is not ‘ora00’, the ORA_PW variable in /opt/oracle/admin/etc/dba.env file needs to be updated.

b. Perform the following on both primary and secondary EMS sites:

$ telnet ftpserverlogin: oraclepassword: ora00


OL-4495-04


c. Create the /opt/backup directory. Make sure the oracle user has write permission to this directory.

$ mkdir /opt/backup

Note It is your responsibility to archive the backup files from the ftp server /opt/backup directory to a tape device or enterprise tape library.

Step 4 Schedule the FTP process.

a. Perform the following on both primary EMS and secondary EMS sites:

Log in as oracle, or su – oracle:

$ crontab –e

b. Add the following line to the oracle crontab on the primary EMS.

## FTP backup files from primary (optical1) to /opt/backup directory of ftpserver. #0 6 * * * /opt/oracle/admin/scripts/ora_ftp_backup.ksh optical1 ftpserver /opt/backup > /opt/oracle/tmp/ora_ftp_backup.log 2>&1

c. Replace ftpserver with correct hostname of the remote FTP server. Replace /opt/backup with correct target directory name if they are different.

The 0 6 *** /opt/oracle/admin/scripts/ora_ftp_backup.ksh ……… ora_ftp_backup.log 2>&1 are all typed in the same line.

d. Edit the oracle crontab on secondary EMS site by replacing optical1 with optical2.

Step 5 Verify backup files by typing the following commands:

The ora_hot_backup.ksh process backs up database data files, control files, and archive logs. The ora_arch_backup.ksh process only backs up archive logs. The target backup directory on both primary and secondary EMS systems is /opt/oraback. The backup files in /opt/oraback directory will later be transferred to the /opt/backup directory in remote ftp site. After the files are successfully transferred to the remote ftp site they will be purged from the /opt/oraback directory.

$ cd /opt/oraback ⎜ EMS systems$ cd /opt/backup ⎜ Remote FTP system

Files generated by ora_hot_backup.ksh at January 21,2002, 2:00 are as follows:

(timestamp=200201210200)

$ ls *200201210200*

optical1_arc_full_1_3:200201210200.Z <<= archivelog file setoptical1_ctl_binary:200201210200.Z <<= binary control file optical1_ctltrc:200201210200:tar.Z <<= control file traceoptical1_hot_full_1_2:200201210200.Z <<= database file setoptical1_ora_hot_full_backup_200201210200.log <<= hot backup log fileoptical1_rman_del_records_200201210200.log <<= purge records log file


OL-4495-04

Chapter 21 Disaster Recovery ProceduresEMS Database Disaster Recovery From Hot Backup

Files generated by ora_arch_backup.ksh at January 21,2002, 18:00 are as follows:

(timestamp=200201211800)

$ ls *200201211800*

optical1_arc_incr_1_4:200201211800.Z <<= archivelog file setoptical1_ctl_binary:200201211800.Z <<= binary control fileoptical1_ctltrc:200201211800:tar.Z <<= control file traceoptical1_ora_arc_incr_backup_200201211800.log <<= arch backup log file

EMS Database Disaster Recovery From Hot BackupThis section provides procedures to restore your Oracle EMS database data files from the most current hot backup and then recover your database from the backup. If additional archivelog backup (by ora_arch_backup.ksh) was done after the hot backup, the additional archivelog backup file sets need to be restored also. All of these backup file sets are assumed to be located on the remote ftp site.

Directory to restore backup files: /opt/oraback

The following assumptions were made for this procedure:

Daily backup schedule:

2:00am – daily hot backup (by ora_hot_backup.ksh process)

18:00pm – daily archivelog backup (by ora_arch_backup.ksh process)

Oracle databases on both primary and secondary EMS systems crashed completely at January 10, 2002, 20:00pm.

Recovery Goal The goal in the scenario above is to recover the primary EMS Oracle database using your most recent backups.

In this case, since the database crashed January 10, 2002, 20:00pm, we need to restore the backup file sets with timestamp ‘200201100200’ from 2:00am hot backup and those with timestamp ‘200201101800’ from 18:00 archivelog backup. Timestamp is formatted as YYYYMMDDhhmm.

If your database crashes before the archivelog backup, you only need to restore the 2:00am hot backup file sets.

If your system does not perform extra archivelog backup daily by ora_arch_backup.ksh, use backup file sets from hot backup only.

In this sample scenario, the primary EMS database will be recovered first to resume operation. Then the secondary EMS will be recovered using the procedures that recover data from the primary EMS.

Note Before this recovery process is applied, it is assumed that the entire system, including all corrupted applications, has been restored.


OL-4495-04


Recovery ProcedureOn the primary EMS system the following steps must be executed to recover the primary EMS database from your most recent backups files:

Step 1 Make sure the platform is shut down and the system cron process has stopped

Login as root:

# platform stop all

# /opt/oracle/admin/bin/stop_cron.sh

Execute platform stop all and stop_cron.sh on the secondary EMS also if the secondary EMS platform is active.

Step 2 Login as oracle user, or su – oracle

Step 3 Verify free disk space

$ df –k /opt/oraback

The EMS system needs to have enough disk space in the /opt/oraback directory to restore all database data files and archivelog files. The database data files can take up to 3.6GB if it is fully populated with data; each archivelog file requires 5MB additional space. The number of archivelog files in the backup set can be identified from the optical1_ora_hot_full_backup_<timestamp>.log and/or the optical1_ora_arc_incr_backup_<timestamp>.log file in /opt/oraback directory.

Step 4 Restore targeted backup file sets from remote FTP site.

FTP the targeted database backup file sets from the remote FTP server to the /opt/oraback directory on the EMS system. Then uncompress all the .Z files.

a. Enter the following commands:

cd /opt/orabackftp <remote_ftp_server>

b. Log in as oracle.

c. Enter the password (default password is ora00).

a. Enter the following commands:

ftp> cd <remote_backup_directory>ftp> bin

Note Use binary transfer mode.

b. Get the following files. If archivelog backup is not performed, get only the hot backup files.

– Backup files from 2:00 hot backup:

– optical1_arc_full_1_167:200201100200.Z

– optical1_arc_full_1_168:200201100200.Z

– optical1_ctl_binary: 200201100200.Z

– optical1_ctltrc:200201100200:tar.Z

– optical1_hot_full_1_166:200201100200.Z


OL-4495-04


– optical1_ora_hot_full_backup_200201100200.log

c. Back up files from the 18:00 archivelog backup:

– optical1_arc_incr_1_169:200201101800.Z

– optical1_ctl_binary:200201101800.Z

– optical1_ctltrc:200201101800:tar.Z

– optical1_ora_arc_incr_backup_200201101800.log

d. Enter the following commands:

ftp> promptftp> mget optical1*200201100200*ftp> mget optical1*200201101800*ftp> quit$ ls *200201100200*$ ls *200201101800*

e. Uncompress your files:

uncompress *200201100200*.Zuncompress *200201101800*.Z

Note At this point, all files are restored from remote FTP server in the /opt/oraback directory. You are now ready to apply the database recovery processes to bring your database up to the point of your last backup.

Step 5 Clean up old database data files by entering the following commands:

cd /data1/oradata/optical1

Note (If on secondary EMS, cd to /data1/oradata/optical2.)

rm data/* db1/* db2/* index/*

df –k /data1/oradata

Note You must have a minimum of 3.6 GB free disk space on /data1/oradata/optical1 to accommodate all database data files from the backup.

Step 6 Restore backup binary control file to database target directories.

Use the most current backup binary control file. In this case, use the optical1_ctl_binary:200201101800 file from 18:00pm archivelog backup. If the archivelog backup was not restored, use the binary control file from 2:00am backup. Copy the backup binary control file to both db1/control01.ctl and db2/control02.ctl files.

cp /opt/oraback/optical1_ctl_binary:200201101800 db1/control01.ctlcp /opt/oraback/optical1_ctl_binary:200201101800 db2/control02.ctl


OL-4495-04


Step 7 Recover the database using recover_db_until_time.ksh script.

The recover_db_until_time.ksh script uses the restored binary control file to mount the database. Then it restores all data files from the restored database datasets. Then it applies all applicable archivelog files through the restored archivelog file sets. Finally it opens the database with resetlogs option, and adds the tempfile backup to TEMP tablespace. When this script is completed successfully, database will be recovered to point of time of the backups.

Before executing the recovery_db_until_time.ksh process all Oracle instance processes must be shut down.

Enter the following commands:

cd /opt/oracle/admin/backup./recover_db_until_time.ksh $ORACLE_SID

System response similar to the following is displayed:

*************************************************************************************This process will perform database recovery using RMAN backup datasets.

Target: hostname=priems16 database=optical1

You must complete the following procedures before this process:

1. platform stop all2. stop_cron.sh3. restore all required backup datasets to /opt/oraback directory4. copy optical1_ctl_binary file to /data1/../<db1 and db2>

*************************************************************************************

Do you want to continue? [y/n] y << Enter y Log file: /opt/oracle/tmp/recover_db_until_time_200201101636.log

<Thu Jan 10 16:36:51 CST 2002> ./recover_db_until_time.ksh started.Mounting controlfile...Connected to an idle instance.ORACLE instance started.

Total System Global Area 287912096 bytesFixed Size 73888 bytesVariable Size 181915648 bytesDatabase Buffers 104857600 bytesRedo Buffers 1064960 bytesDatabase mounted.

Restoring all datafiles ..RMAN> 2> 3> 4> 5> 6> 7> 8><Thu Jan 10 16:40:15 CST 2002> All datafiles are restored.

<Thu Jan 10 16:40:15 CST 2002> Begin to recover database.

Recover database until time '20020111 14:00:13' << until time is always the restored timestamp+1dayLast logseq=6782 thread=1

RMAN msglog file: /opt/oracle/tmp/recover_db_until_time_200201101636.logRMAN> 2> 3> 4> 5> 6> 7> 8>**** You can Ignore RMAN error messages regarding to: << Ignore this error message from the log file**** MAN-08060: unable to find archivelog**** RMAN-08510: archivelog thread=1 sequence=6783


OL-4495-04


**** .......**** RMAN-06054: media recovery requesting unknown log:

<Thu Jan 10 16:44:27 CST 2002> Database recovery ended.

<Thu Jan 10 16:44:27 CST 2002> Alter database open resetlogsConnected.Database altered.….Database is successfully recovered.

<Thu Jan 10 16:44:38 CST 2002> ./recover_db_until_time.ksh ended.

Post Recovery – Cold BackupOnce you have recovered your database, you need to make a cold backup of the database using the dbadm –E cold_backup command. The following tar files will be created from the cold backup script. You need to save a copy of these files to the /opt/oraback directory. Make sure that these files are saved to the offsite ftp server.

• /opt/oracle/tmp/optical1_DB_upd.tar.gz

• /opt/oracle/tmp/optical1_ADMIN_upd.tar

• /opt/oracle/tmp/optical1_upd.crontab

Step 1 Log in as oracle, or su – oracle:


dbadm -E cold_backup

Note This process can take more than 10 minutes to complete, depending on the volume of data in the database.

Text similar to the following is displayed:

*****************************************************************This process performs the following tasks:

1. Shutdown optical1 database on priems09.2. Backup /opt/oracle/admin directory (except arch dump and log).3. Cold backup database.4. Backup oracle crontab file.5. Startup database.

The following backup files are generated at the end of process:

/opt/oracle/tmp/optical1_DB_upd.tar.gz/opt/oracle/tmp/optical1_ADMIN_upd.tar/opt/oracle/tmp/optical1_upd.crontab

Free disk space left on /opt/oracle/tmp: 1383 MB

*****************************************************************LOG file: /opt/oracle/tmp/ora_cold_backup.log


OL-4495-04

Chapter 21 Disaster Recovery ProceduresRecovering the EMS Database from Another Database


f. Once the cold backup is completed you need to save a copy of the backup files to the /opt/oraback directory for the ftp script to transfer offsite.

$ cd /opt/oracle/tmp$ cp optical1_ADMIN_upd.tar /opt/oraback $ cp optical1_upd.crontab /opt/oraback $ cp optical1_DB_upd.tar.gz /opt/oraback

g. Clean up the restored files in /opt/oraback directory to claim the disk space back.

$ ls /opt/oraback/*200201100200*$ ls /opt/oraback/*200201101800*

$ rm /opt/oraback/*200201100200*$ rm /opt/oraback/*200201101800*

Step 3 Resume operations.

You are now ready to shut down the Oracle database and start the platform and cron process.

a. Login as root, or su - root

b. Enter the following commands:

$ su – root# platform stop –i oracle # platform start# /opt/oracle/admin/bin/start_cron.sh# nodestat

Recovering the Oracle Secondary EMS DatabaseTo recover the secondary EMS database and copy data from the primary EMS database, refer to the “Recovering the EMS Database from Another Database” section on page 21-16.

Recovering the EMS Database from Another DatabaseThis section provides the procedures to recover one corrupted EMS database from another active database.

Recovery ProceduresThe steps in this section show you how to recover a corrupted EMS database from the other active peer database assuming the following scenarios (this procedure applies to both scenarios):

Scenario 1 The primary EMS database is corrupted. You would like to restore data from the secondary EMS database.

Scenario 2 The secondary EMS database is corrupted. You would like to restore data from the primary EMS database.


OL-4495-04


Step 1 On the active EMS site, terminate the DBHeartBeat process and disable PUSH job (job 2).

a. On the active EMS site, log in as oracle, or su - oracle.

b. Enter the following command to terminate DBHeartBeat process:

$ dbinit -H -i stop

$ ps -ef | grep hbmgr | grep -v grep

c. Disable PUSH job (job 2).

$ dbadm -A disable_push_job

d. Respond y at the prompt and enter the following:

$ dbadm –r get_broken_jobs


2 Y 0 declare rc binary_integer; begin rc := sys.dbms_defer_s ys.push(destination=>'OPTICAL1', stop_on_error=>FALSE,

delay_seconds=>0, parallelism=>1); end;

Step 2 Shut down all processes on the corrupted EMS site:

a. On the corrupted EMS site, login as root.

b. Stop the cron process and shut down the platform:

# /opt/oracle/admin/bin/stop_cron.sh# platform stop all# nodestat

Verify whether all database processes are terminated:# nodestat# ps –ef | grep ora_ # ps –ef | grep hbmgr # ps –ef | grep tnslsnr

Tip You can use kill –9 to kill any process not being terminated by platform stop all.

# ipcs –p | grep oracle

Tip You can use the ipcrm command to remove any shared memory or semaphore still allocated to oracle now. For example: ipcrm –m <ID>, ipcrm –s <ID>

Step 3 This step is optional. Save all current database logs and trace files on the corrupted EMS site.

If the disk that stores the Oracle database dump and log files still exists, you can save the dump and log files to use later if needed.

a. On the corrupted EMS site, log in as oracle, or su – oracle:


$ su - oracle $ cd /data1/dump $ tar -cvf /opt/oraback/data1_dump_corrupted.tar *$ cd /opt/oracle/tmp$ tar -cvf /opt/oraback/opt_oracle_tmp_corrupted.tar *


OL-4495-04


Timesaver You can gzip or compress the tar files if they are very large.

Step 4 On the corrupted EMS site, rebuild the Oracle database from one of the following three options:

Reinstalling the BTS Software on the Corrupted EMS

a. Update /etc/opticall.cfg file. You can copy this file from active EMS. Verify that the contents are correct.

b. Create the /opt/ems/utils directory, if it does not already exist. Enter the following command:

# mkdir -p /opt/ems/utils

c. FTP the file /opt/ems/utils/Version from the active EMS to the corrupted EMS, then rename the file to Version.save for reference. Enter the following commands:

# cd /opt/ems/utils# cat Version.save

900-xx.yy.zz.D00

d. Enter the following commands to create the version file from Version.save, but change the version number to D00 (D zero zero). This D00 version value is only a tag; it does not affect the target version to be installed.

# sed 's/...$/D00/' Version.save > Version# cat Version

900-xx.yy.zz.D00

e. Change to the CD Build directory and run install.sh with the -upgrade option. Enter the following command:

# ./install.sh -upgrade

Note For procedures on how to mount the installation CD and load or untar the software packages to /opt/Build, see the following sections in “Application Installation Procedure (Release 4.4)”:

- “Load the K9-opticall.tar(.gz) File on the EMS and CA/FS Platforms” on page 15- “Load the K9-oracle.tar(.gz) File on the EMS” on page 23

f. After the corrupted EMS system is reinstalled, enter the commands below to shut down the platform and only start up Oracle listener and database:

# platform stop all

Option 1 If only database is corrupted and BTS re-installation is not required, go to Step 5 to reload the database from the database backup file. Continue to Step 6.

Option 2 If the entire system is corrupted and flash archive system backup is available, recover the system from the flash archive, as detailed in the “Restoring an Archive” section on page 21-2. The flash archive backup file should have BTS applications included. Continue to Step 6.

Option 3 If the entire system is corrupted and the flash archive backup file is not available, you must jump start the system, and reinstall the BTS software from the installation CD, as shown below, Reinstalling the BTS Software on the Corrupted EMS.


OL-4495-04


# su - oracle# dbinit -L -E -i start

Continue to Step 6.

Step 5 Reload the database from cold backup to the corrupted EMS site.

If the EMS system is intact, but only the Oracle database is corrupted, you can use the cold backup tar file to restore the database data files. The cold backup tar file optical1_DB_upd.tar.gz is for the primary EMS, and optical2_DB_upd.tar.gz is for the secondary EMS.

• If the tar file is not in /opt/oraback directory and the same file still exists in the /opt/oracle/tmp directory, copy this file from /opt/oracle/tmp to /opt/oraback directory.

• If the file does not exist on either directory, restore this file from remote FTP server to /opt/oraback directory, then execute the steps in this section to restore database data files from the cold backup tar file.

Note If there is no cold backup database tar file, you can restore database from hot backup. Refer to the “EMS Database Disaster Recovery From Hot Backup” section on page 21-11 to recover your database from hot backup.

a. Restore the database from the cold backup tar file. Log in as oracle:

If the corrupted database is the primary EMS database use the optical1_DB_upd.tar.gz file:

$ cd /data1/oradata/optical1 $ rm -r data/* db1/* db2/* index/*$ gzip -cd /opt/oraback/optical1_DB_upd.tar.gz | tar xvf -

If the corrupted database is the secondary EMS database, use the optical2_DB_upd.tar.gz file:

$ cd /data1/oradata/optical2 $ rm –r data/* db1/* db2/* index/*$ gzip –cd /opt/oraback/optical2_DB_upd.tar.gz | tar xvf -

b. Start the database restore process. After the database data files are re-stored, execute the following command to start up the EMS database process:

$ dbadm -L -E -i start

Step 6 Stop all transactions except northbound traffic on the active EMS. From the active EMS side, stop all transactions to the database except northbound traffic and status control update from CA or FS.

Caution There is no CLI provisioning and SNMP processes must be stopped.

a. Log in as root.


# pkill smg3

Step 7 Copy data from the active EMS database to the corrupted database:


OL-4495-04


Caution During this step the dbadm -A copy_all process will truncate local tables first, then copy data from the tables on the other site. Make sure that you execute this step on the corrupted EMS side only.

a. On the corrupted EMS side, log in as oracle, or su – oracle.

Note Make sure that you are on the corrupted database site.


$ dbadm -A copy_all


*****************************************************************You are about to execute the following process:

==> Copy all OAMP/OPTICALL/BILLING tables from remote DB optical1 at priems47

database: optical2hostname: secems47

*****************************************************************

c. At the prompt, enter y to continue:



***This will EMPTY all the tables on: *** local host ==> secems47*** local database ==> optical2****** Then copy data from remote DB optical1 at priems47

d. At the prompt, enter y to continue:


Note This process will take some time. At a database with maximum capacity, it can take approximately 2 hours to copy all OAMP and OPTICALL tables.

Response similar to the following example is displayed:

<Mon Jan 24 11:40:23 CST 2005> INFO: DMMgr::Configuration loaded<Mon Jan 24 11:40:23 CST 2005> INFO: DMMgr::243 rows updated<Mon Jan 24 11:40:24 CST 2005> INFO: DMMgr::Disabling Foreign Key constraints for BILLING.<Mon Jan 24 11:40:24 CST 2005> INFO: DMMgr::Disabling triggers for BILLING...<Mon Jan 24 11:40:25 CST 2005> INFO: copy table => BILLING.BILLING_ACCT_ADDR..<Mon Jan 24 11:40:26 CST 2005> INFO: copy table => BILLING.BILLING_ACCT_ADDR ......Mon Jan 24 11:40:28 CST 2005> INFO: copy tables => OK=3, FAIL=0, SKIP=0, OTHERS=0<Mon Jan 24 11:40:28 CST 2005> INFO: DMMgr::Enabling Foreign Key constraints for BILLING.<Mon Jan 24 11:40:28 CST 2005> INFO: DMMgr::Enabling triggers for BILLING...<Mon Jan 24 11:40:29 CST 2005> INFO: DMMgr::Disabling Foreign Key constraints fo


OL-4495-04


r OAMP...<Mon Jan 24 11:40:29 CST 2005> INFO: DMMgr::Disabling triggers for OAMP...<Mon Jan 24 11:40:29 CST 2005> INFO: copy table => OAMP.CALL_TRACE..<Mon Jan 24 11:40:30 CST 2005> INFO: copy table => OAMP.CALL_TRACE ...OK(0 row)...<Mon Jan 24 11:41:41 CST 2005> INFO: copy tables => OK=50, FAIL=0, SKIP=0, OTHERS=0<Mon Jan 24 11:41:41 CST 2005> INFO: DMMgr::Enabling Foreign Key constraints for OAMP...<Mon Jan 24 11:41:41 CST 2005> INFO: DMMgr::Enabling triggers for OAMP...<Mon Jan 24 11:41:41 CST 2005> INFO: DMMgr::Disabling Foreign Key constraints for OPTICALL…<Mon Jan 24 11:42:07 CST 2005> INFO: DMMgr::Disabling triggers for OPTICALL...<Mon Jan 24 11:42:47 CST 2005> INFO: copy table => OPTICALL.AAA_SERVER_GRP..<Mon Jan 24 11:42:48 CST 2005> INFO: copy table => OPTICALL.AAA_SERVER_GRP ...OK (0 row)...Mon Jan 24 11:46:41 CST 2005> INFO: copy table => OPTICALL.WIRETAP..<Mon Jan 24 11:46:42 CST 2005> INFO: copy table => OPTICALL.WIRETAP ...OK(0 row)<Mon Jan 24 11:46:42 CST 2005> INFO: copy tables => OK=190, FAIL=0, SKIP=0, OTHERS=0<Mon Jan 24 11:46:42 CST 2005> INFO: DMMgr::Enabling Foreign Key constraints for OPTICALL...<Mon Jan 24 11:47:20 CST 2005> INFO: DMMgr::Enabling triggers for OPTICALL...

Step 8 On the active EMS, truncate all replication queues since all data are already copied over, then start the DBHeartBeat process. The DBHeartBeat process automatically enables the broken push job.

From active EMS side:

a. Truncate replication queues. Enter the following commands:

# su - oracle

$ dbadm -A truncate_def

$ dbadm -r get_unpushed_trans


no rows selected

b. Start the DBHeartBeat process. Enter the following command:

$ dbinit -H -i start

$ dbadm -r get_broken_jobs


2 N 0 declare rc binary_integer; begin rc := sys.dbms_defer_sys.push(destination=>'OPTICAL1', stop_on_error=>FALSE,delay_seconds=>0, parallelism=>1); end;

Step 9 Verify the database status and audit contents of tables. This step can be executed on either the primary or secondary EMS site. In this case, it is executed on the primary EMS site.

a. On the active EMS site, log in as oracle, or su - oracle.


$ dbadm -C db

Response similar the following example is displayed:


OL-4495-04


Checking table => OPTICALL.AGGR....OK Checking table => OPTICALL.ANI....OK .. ..

Number of tables to be checked: xxx Number of tables checked OK: xxx Number of tables out-of-sync: 0

Step 10 Synchronize table contents from the uncorrupted EMS site to the corrupted EMS site.

If the dbadm -C db command from Step 9 returns out-of-sync table(s) like the examples below, follow the commands in Step a. and Step b. (below) to synchronize the contents of data from the active EMS database to the corrupted EMS database.

Text similar to the following example is displayed:

Number of tables to be checked: 130Number of tables checked OK: 127Number of tables out-of-sync: 3

List of out of sync tables:

OAMP.TABLE_NAME => 22/0

In this example, one table owned by the OAMP is out of sync. Follow the steps below to synchronize the contents of the tables:

Note Execute these commands on the corrupted EMS database to synchronize the table.

OPTICAL1::Deftrandest is empty? YES

OPTICAL1::dba_repcatlog is empty? YES

OPTICAL1::Deferror is empty? YES

OPTICAL1::Deftran is empty? YES

OPTICAL1::Has no broken job? YES

OPTICAL1::JQ Lock is empty? YES

OPTICAL2::Deftrandest is empty? YES

OPTICAL2::dba_repcatlog is empty? YES

OPTICAL2::Deferror is empty? YES

OPTICAL2::Deftran is empty? YES

OPTICAL2::Has no broken job? YES

OPTICAL2::JQ Lock is empty? YES


OL-4495-04


Truncate the content of the table on the local database, then copy the data from the remote database, as follows:

a. Log in as oracle, or su - oracle:


$ dbadm -A copy -o <owner> -t <table_name>

$ dbadm -A copy -o oamp -t table_name

Step 11 Verify the Oracle crontab file:

a. Log in as oracle, or su - oracle:

b. Verify the Oracle crontab file on the corrupted EMS site. Compare the schedules of jobs with those on the active EMS site. If any schedule needs to be modified, enter the following command:

$ crontab -e

Step 12 Shut down the Oracle database and start up the platform on the standby EMS sites. Both primary and secondary databases have identical data. You must start the platform and system cron processes on the standby EMS.

On the corrupted EMS site, log in as root and enter the following commands to bring up the platform:

# platform stop -i oracle# platform start# /opt/oracle/admin/bin/start_cron.sh

The EMS database recovery from another database is now complete.


OL-4495-04

Chapter 21 Disaster Recovery ProceduresRecovering Shared Memory Data

Recovering Shared Memory DataThe download database command refreshes data in the Call Agent (CA) shared memory. In the event that shared memory data cannot be recovered, it recovers data in the CA shared memory. The download database command wipes out Call Agent shared memory data and causes a total outage.

Caution Read this section in its entirety before attempting this procedure.

Do not use this command on any live traffic production systems. Contact Cisco TAC regarding the use of this command for disaster recovery.

Caution Do not download the database through the console port because the TTY can cause long delays.

Downloads of the CA, FSAIN and FSPTC applications can be done in parallel.

You can perform the download database command by ID. The download by ID command allows you to copy database information from the EMS to a specific CA or Feature Server (FS). If a CA ID is not specified, the command copies to all IDs.

Use one of the following examples to download database by ID.

download database target=ca; id=CAxxxdownload database target=fsptc; id=FSPTCxxxdownload database target= fsain; id=FSAINxxx

See the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide for table and token descriptions.

Recovering Shared MemoryPerform the following procedure:

Step 1 Check the transaction queue. Use the following command:

show transaction-queue

Step 2 If you find any transaction in the queue, delete the queue by entering the following CLI command.

Note There should be no provisioning activity on the system—if the show transaction-queue command does not return the message "Void of entries," assume that a transaction is in the queue. If there is no transaction in the queue, proceed to Step 3

delete transaction-queue

Examples:

delete transaction-queue target=CAxxx;

delete transaction-queue target=FSPTCxxx;

delete transaction-queue target=FSAINxxx


OL-4495-04


Step 3 Enter the shared memory command to recover the CA and FS databases. Enter following CLI download database commands:

download database target=CA; file=/opt/tmp/download-CAdownload database target=FSAIN; file=/opt/tmp/download-FSAINdownload database target=FSPTC; file=/opt/tmp/download-FSPTC

Step 4 Stop both CA platforms. Enter the following command:

platform stop all

Step 5 Delete the following data directories (as shown below) on the primary and secondary CA and FSs. Enter the following commands:

cd /opt/OptiCall\rm -rf */bin/data

Step 6 Use ftp to transfer the file created in Step 3 to the primary CA. Enter the following commands:

download-CA -ftp to-> /opt/OptiCall/CAxxx/bindownload-FSPTC -ftp to-> /opt/OptiCall/FSPTCxxx/bindownload-FSAIN -ftp to-> /opt/OptiCall/FSAINxxx/ bin

Step 7 Start the primary CA and FS platforms. Enter the following command:

platform start

Step 8 Go into MYSQL on the primary CA/FS and upload the database as shown below.

Note Perform this step in parallel with three different sessions opened to the appropriate CA or FS.

The following steps may take up to 2 hours, depending on the size of the database being recovered.

a. Enter the following from the /opt/OptiCall/CAxxx/bin command line:

/dbm_sql.CAxxx ./data ./catalog < download-CA

b. Enter the following from /opt/OptiCall/FSPTCxxx/bin command line:

/dbm_sql.FSPTCxxx ./data ./catalog < download-FSPTC

c. Enter the following from /opt/OptiCall/FSAINxxx/bin command line:

/dbm_sql.FSAINxxx ./data ./catalog < download-FSAIN

Step 9 Start the secondary CA and FS platforms after Step 8 completes.

platform start

Step 10 Continue to the following procedure, Restoring Subscriber and Trunk Terminations to Service.

Restoring Subscriber and Trunk Terminations to ServiceControl all provisioned network devices in service, as shown in the following subsections.


OL-4495-04


Caution You must run the following procedures in parallel, to limit the amount of down time. For example, one engineer can be working on subscribers while another engineer is working on trunks or trunk groups.

Controlling Trunks and Trunk Groups

Control trunks and trunk groups with scripts created through the following CLI commands:

Using the cs-control Tool to Bring Subscribers In-Service

Use the cs-control tool to bring subscribers in-service. Obtain the cs-control tool from Cisco. You must write a script (as shown in the following example) to be used by the cs-control tool.

Example of a Script

control subscriber-termination id=sub1;mode=forced;target-state=INScontrol subscriber-termination id=sub2;mode=forced;target-state=INScontrol subscriber-termination id=sub3;mode=forced;target-state=INScontrol subscriber-termination id=sub4;mode=forced;target-state=INS

Note The completed script will be placed in the /opt/OptiCall/CAxxx/bin directory on the primary CA.

The cs-control script is invoked from /opt/OptiCall/CAxxx/bin directory to place subscribers in-service as follows:

cs-control data <name of the script used in the step above>

CLI Command Example

control trunks oos control trunk-termination tgn-id=1;cic=1-24;mode=forced; target-state=oos;

control trunk-grps oos control trunk-grp id=1;mode=forced;target-state=oos;

control h323gws oos control h323-gw id=h323;mode=forced;target-state=oos;

unequip trunk terminations unequip trunk-termination tgn-id=1;cic=all;

control h323gws ins control h323-gw id=h323;mode=forced;target-state=ins;

control trunk-grps ins control trunk-grp id=1;mode=forced;target-state=ins;

equip trunk terminations equip trunk-termination tgn-id=1;cic=all;

control trunks ins control trunk-termination tgn-id=1;cic=1-24;mode=forced;target-state=ins;


OL-4495-04


C H A P T E R 22
Manual System Recovery
This chapter describes how to manually recover a Cisco BTS 10200 Softswitch system if you have one of the following types of hardware failures:

• Disk 1 on the Primary Call Agent and Feature Server is Corrupt

• Disk 0 on the Primary Call Agent and Feature Server is Corrupt

• Disk 1 on the Secondary Call Agent and Feature Server is Corrupt

• Disk 0 on the Secondary Call Agent and Feature Server is Corrupt

• Disk 1 on the Primary Element Management System is Corrupt

• Disk 0 on the Primary Element Management System is Corrupt

• Disk 1 on the Secondary Element Management System is Corrupt

• Disk 0 on the Secondary Element Management System is Corrupt

Disk 1 on the Primary Call Agent and Feature Server is CorruptTo manually recover your system when disk 1 on the primary CA/FS is corrupt perform the following procedure:

Step 1 Connect the laptop to console.

Step 2 Bring the system to an OK prompt.

Step 3 Power off the system, remove the disk 1 (bad disk) and insert new disk 1.

Step 4 Bring the system up as single user mode. Run boot -s.

Step 5 Execute metadb -d c0t1d0s4

Step 6 Execute fsck -y /dev/rdsk/c0t0d0s0

Step 7 Execute reboot -- -s. The system will reboot and come up in a single user mode.

Step 8 Execute mount -o rw,remount /dev/md/dsk/d2 /

Step 9 Execute metaroot d2.

Step 10 Execute cp /etc/vfstab /etc/saved.vfstab

Step 11 Execute cp /etc/vfstab.org.mirror /etc/vfstab

Step 12 Execute cp /etc/rc3.d/S99platform /etc/rc3.d/saved.S99platform

Step 13 Execute halt


Chapter 22 Manual System RecoveryDisk 0 on the Primary Call Agent and Feature Server is Corrupt

Step 14 At the OK prompt, execute boot disk0

Step 15 Execute metadetach -f d2 d1






Step 21 Execute metaclear d4





Step 26 Use the format command to set up your partition on disk 1 (new disk) the same as disk 0

Step 27 Execute metadb -a -f -c 3 c0t1d0s4

Step 28 Execute metainit -f d1 1 1 c0t1d0s0






Step 34 Execute metaroot d2

Step 35 Execute metattach d2 d1






Step 41 Run mv /etc/rc3.d/saved.S99platform /etc/rc3.d/S99platform

Step 42 Run cp /etc/saved.vfstab /etc/vfstab

Step 43 Verify everything is okay by executing metastatmore

Step 44 Run /usr/sbin/installboot /usr/platform/ùname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t1d0s0

Step 45 Run metastat|grep % to ensure that mirror is running.

Disk 0 on the Primary Call Agent and Feature Server is CorruptTo manually recover your system when disk 0 on the primary Call Agent/Feature Server (CA/FS) is corrupt perform the following procedure:


OL-4495-04

Chapter 22 Manual System RecoveryDisk 0 on the Primary Call Agent and Feature Server is Corrupt





Step 5 If the system will not boot up with disk 1, then you need to boot the system with the Solaris CD. Run boot cdrom -s

Step 6 At the prompt, run /usr/sbin/installboot /usr/platform/ùname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t1d0s0

Step 7 Execute reboot -- -s








Step 15 Edit the /etc/vfstab file and replace c0t0 with c0t1


Step 17 Edit the /etc/vfstab file and replace c0t0 with c0t1.














Step 31 Use the format command to set up partition on disk 0 (new disk) the same as disk 1







OL-4495-04

Chapter 22 Manual System RecoveryDisk 1 on the Secondary Call Agent and Feature Server is Corrupt












Step 48 Verify that everything is okay by executing metastat |grep c0.


Step 50 Run metastat|grep % to ensure that mirror is running

Disk 1 on the Secondary Call Agent and Feature Server is Corrupt

To manually recover your system when disk 1 on the secondary Call Agent/Feature Server (CA/FS) is corrupt perform the following procedure:



















OL-4495-04



























Step 43 Verify that everything is okay by executing metastat|grep c0.


Disk 0 on the Secondary Call Agent and Feature Server is Corrupt

To manually recover your system when disk 0 on the secondary Call Agent/Feature Server (CA/FS) is corrupt perform the following procedure:






OL-4495-04







































OL-4495-04

Chapter 22 Manual System RecoveryDisk 1 on the Primary Element Management System is Corrupt









Disk 1 on the Primary Element Management System is CorruptTo manually recover your system when disk 1 on the primary Element Management System (EMS) is corrupt perform the following procedure:


























OL-4495-04























OL-4495-04


Disk 0 on the Primary Element Management System is CorruptTo manually recover your system when disk 0 on the primary Element Management System (EMS) is corrupt perform the following procedure:















Step 15 Edit the /etc/vfstab and replace c0t0 with c0t1



















OL-4495-04

Chapter 22 Manual System RecoveryDisk 1 on the Secondary Element Management System is Corrupt

















Disk 1 on the Secondary Element Management System is Corrupt

To manually recover your system when disk 1 on the secondary Element Management System (EMS) is corrupt perform the following procedure:

















OL-4495-04































Disk 0 on the Secondary Element Management System is Corrupt

To manually recover your system when disk 0 on the secondary Element Management System (EMS) is corrupt perform the following procedure:




OL-4495-04




Step 5 Action: If the system will not boot up with disk 1, then you need to boot the system with the Solaris CD. Run boot cdrom -s



































OL-4495-04













OL-4495-04



OL-4495-04


C H A P T E R 23
Replacing a Disk
This section describes how to replace a defective disk on the Cisco BTS 10200 Softswitch. This procedure contains the following sections:

• Before You Start

• Replace Disk 0 on CA/FS and EMS

• Replace Disk 1 on CA/FS and EMS

Before You StartPerform the following before replacing a disk:

• Identify the disk that needs replacing by viewing /var/adm/messages

• Cisco recommends that you obtain a new disk with the same part number as the defective disk.

• Perform a Flash Archive procedure.

Replace Disk 0 on CA/FS and EMSPerform the following procedure to replace a defective disk (Disk 0):

Note The letter “x” in cxt0d0 or cxt1d0 throughout the procedure refers to the SCSI controller ID of the system (either 0 or 1). To find out the controller ID, use the “format” command.


Note If this node is primary, then you need to change the state of the nodes to forced standby active.

Step 2 Run the procedure in Replace Disk 0 on CA/FS and EMS, page 23-1 if this node is CA/FS.

Step 3 Type the following entries at the prompts:

<hostname># platform stop all

<hostname>#/usr/sbin/metadb –d –f cxt0d0s4 cxt1d0s4

<hostname>#mount /dev/dsk/cxt1d0s0 /mnt


Chapter 23 Replacing a Disk

Note Run “fsck –y /dev/rdsk/cxt1d0s0” if the file system cannot be mounted.

<hostname>#cp /mnt/etc/system /mnt/etc/system.mirror

<hostname>#cp /mnt/etc/vfstab /mnt/etc/vfstab.mirror

<hostname>#mv /mnt/etc/rc3.d/S99platform /mnt/etc/rc3.d/saved.S99platform

<hostname>#eprom auto-boot?=false

Step 4 Edit the /mnt/etc/system file and remove the following lines if any of these are present:

##############################

* Begin MDD root info (do not edit)








forceload: drv/glm

forceload: drv/sd


* End MDD root info (do not edit)

* Begin MDD database info (do not edit)

set md:mddb_bootlist1="sd:244:16 sd:244:1050 sd:244:2084

sd:260:16”

set md:mddb_bootlist2=”sd:260:1050 sd:260:2084”

* End MDD database info (do not edit)

###############################

Step 5 Edit the /mnt/etc/vfstab:

Note Before editing /etc/vfstab or replacing a disk, verify /dev/dsk/ or use the format command to determine the correct disk identification. For Sun Fire 1280, the disk is c1t0d0.

The following output is similar to the output for CCPU and Sun Netra 1405 platforms:

######################################################

#device device mount FS fsck mount mount

#to mount to fsck point type pass at boot options

#

#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -

fd - /dev/fd fd - no -


OL-4495-04


/proc - /proc proc - no -

/dev/dsk/c0t1d0s3 - - swap - no -

/dev/dsk/c0t1d0s0 /dev/rdsk/c0t1d0s0 / ufs 1 yes -

/dev/dsk/c0t1d0s1 /dev/rdsk/c0t1d0s1 /var ufs 1 yes -

/dev/dsk/c0t1d0s5 /dev/rdsk/c0t1d0s5 /opt ufs 2 yes -

swap - /tmp tmpfs - yes -

######################################################

The following output is similar to the output for Sun Fire 1280, V120, Netra 20, Netra 440 platforms:

######################################################



#









######################################################

Step 6 Type the following entries at the prompt:

<hostname>#sync

<hostname>#shutdown –y –g0 –i5

Step 7 Power off the system.

Step 8 Remove the bad disk (disk0).

Step 9 Insert the new disk 0 into slot and power on the system.

Step 10 At the prompt, type:

ok>boot disk1

Note If necessary, run fsck –y on a file system that cannot be mounted.


Step 12 Verify the system is booting up and all file systems are mounted.

Step 13 Partition all slices on disk 0 exactly like disk 1, label it and exit.


OL-4495-04


If the replacing disk does not have the same Model number, use the “format” command to manually partition the new disk as follows:

Slice 0 /(root) 1500MB

Slice 1 /var 500MB

Slice 3 swap 2000MB

Slice 4 unassigned 16MB

Slice 5 /opt The rest of the disk space




<hostname>#/usr/sbin/metadb -a -f -c 3 cxt0d0s4 cxt1d0s4

<hostname>#/usr/sbin/metainit -f d0 1 1 cxt0d0s0


<hostname>#/usr/sbin/metainit d2 -m d1

<hostname>#/usr/sbin/metaroot d2

<hostname>#/usr/sbin/lockfs –fa
















<hostname>#/usr/sbin/metainit -f d18 -t d14 d17



<hostname>#cp /etc/system.mirror /etc/system

<hostname>#cp /etc/vfstab.mirror /etc/vfstab

<hostname>#sync

<hostname>#halt


OL-4495-04


Step 15 At the prompt, type:

OK>boot disk1



<hostname># installboot /usr/platform/ùname -i`/lib/fs/ufs/bootblk /dev/rdsk/cxt0d0s0

<hostname>#/usr/sbin/metattach d2 d0






Step 18 At this time, disk 0 is syncing with disk 1. The process will take a while.

Caution Do not continue until the syncing process is 100% completed.

Step 19 Run metastat|grep % to monitor the percentage complete.

<hostname>#metastat |grep cx

Step 20 Verify that all slices are okay.

Ex: cxt0d0s6 0 No Okay

cxt1d0s6 0 No Okay

cxt0d0s1 0 No Okay

cxt1d0s1 0 No Okay

cxt0d0s5 0 No Okay

cxt1d0s5 0 No Okay

cxt0d0s7 0 No Okay

cxt1d0s7 0 No Okay

cxt0d0s0 0 No Okay

cxt1d0s0 0 No Okay

cxt0d0s3 0 No Okay

cxt1d0s3 0 No Okay

Step 21 Once the syncing process is completed, reboot the system using disk0 to verify.


<hostname>#sync



Step 24 Start the platform:

<hostname>#platform start



OL-4495-04



<hostname>#mv /etc/rc3.d/saved.S99platform /etc/rc3.d/S99platform

<hostname>#eprom auto-boot?=true

Replace Disk 1 on CA/FS and EMSPerform the following procedure to replace a defective disk (Disk 1).

Note The letter “x” in cxt0d0 or cxt1d0 throughout the procedure refers to the SCSI controller ID of the system (either 0 or 1). To find out the controller ID, one can use the “format” command.


Note If this node is primary, then you need to change the sate of the nodes to forced standby active



<hostname>#cp /etc/system /etc/system.mirror

<hostname>#cp /etc/vfstab /etc/vfstab.mirror

<hostname>#mv /etc/rc3.d/S99platform /etc/rc3.d/saved.S99platform

<hostname>#/usr/sbin/metadb –d –f cxt0d0s4 cxt1d0s4

Step 4 Edit the /etc/system file and remove the following lines if any of these are present:

##############################

* Begin MDD root info (do not edit)








forceload: drv/glm

forceload: drv/sd


* End MDD root info (do not edit)

* Begin MDD database info (do not edit)

set md:mddb_bootlist1="sd:244:16 sd:244:1050 sd:244:2084


OL-4495-04


sd:260:16"

set md:mddb_bootlist2="sd:260:1050 sd:260:2084"

* End MDD database info (do not edit)

###############################

Step 5 Edit the /etc/vfstab:

The following output is for CCPU and Sun Netra 1405 platforms:

######################################################



#









######################################################

The following output is for Sun Fire 1280, V120, Netra 20, Netra 440 platforms:

######################################################



#









######################################################


<hostname>#sync


Step 7 Power off the system.

Step 8 Remove the bad disk (disk1).


OL-4495-04


Step 9 Insert the new disk1 into the slot and power on the system.

Note If necessary, run fsck –y on a file system that cannot be mounted.

Step 10 Verify the system is booting up and all file systems are mounted.

Step 11 Partition all slices on disk 1 exactly like disk 0, label it and exit.

If the replacing disk does not have the same Model number, using the “format” command to manually partition the new disk as follow:

Slice 0 /(root) 1500MB

Slice 1 /var 500MB

Slice 3 swap 2000MB


Slice 5 /opt The rest of the disk space


Slice 7 unassigned 64M

Step 12 Perform the following steps to set up disk mirroring:

CA/FS:

cd /opt/setup

./setup_mirror_ca

Note Ignore this error “mv: cannot access ./vfstab_mirror”

./setup_trans

Note Ignore this error “mv: cannot access ./vfstab_trans”

cp /etc/system.mirror /etc/system

cp /etc/vfstab.mirror /etc/vfstab

sync

reboot

login as root

cd /opt/setup

./sync_mirror

EMS:

cd /opt/setup

./setup_mirror_ems

Note Ignore this error “mv: cannot access ./vfstab_mirror”

./setup_mirror_trans


OL-4495-04


Note Ignore this error “mv: cannot access ./vfstab_trans

cp /etc/system.mirror /etc/system

cp /etc/vfstab.mirror /etc/vfstab

sync

reboot

login as root

cd /opt/setup

./sync_mirror

Step 13 At this time, disk 1 is syncing with disk 0. The process will take a while.

Caution Do not continue until the syncing process is 100% completed.

Step 14 Run metastat|grep % to monitor the percentage completion:

<hostname>#metastat|grep cx

Step 15 Verify that all slices are okay.

Ex: cxt0d0s6 0 No Okay

cxt1d0s6 0 No Okay

cxt0d0s1 0 No Okay

cxt1d0s1 0 No Okay

cxt0d0s5 0 No Okay

cxt1d0s5 0 No Okay

cxt0d0s7 0 No Okay

cxt1d0s7 0 No Okay

cxt0d0s0 0 No Okay

cxt1d0s0 0 No Okay

cxt0d0s3 0 No Okay

cxt1d0s3 0 No Okay

Step 16 Start the platform:

<hostname>#platform start

Step 17 Run the procedure in Replace Disk 1 on CA/FS and EMS, page 23-6, if this node is CA/FS.

Step 18 Type the following entry at the prompt:

<hostname>#mv /etc/rc3.d/saved.S99platform /etc/rc3.d/S99platform


OL-4495-04



OL-4495-04


A P P E N D I X A
Feature Tones
The Cisco BTS 10200 Softswitch supports special tones on various subscriber and operator features by sending MGCP messages to the gateways. These tones are based on the information in the following documents:

• Telcordia document GR-506-CORE, Signaling for Analog Interfaces

• Telcordia document TR-NWT-506, Issue 3, Signaling

• Telcordia document GR-590-CORE, Call Pickup Features (FSD 01-02-2800)

• Telcordia document GR-317-CORE, Switching System Generic Requirements for Call Control Using the Integrated Services Digital Network User Part (ISDNUP)

• Telcordia document GR-219-CORE, Distinctive Ringing/Call Waiting (FSD 01-01-1110).

• IETF document RFC 2705, Media Gateway Control Protocol (MGCP) Version 1.0

List of Tones Applicable to Specific FeaturesTable A-1 lists the tones used with each feature, and the condition that triggers the sending of each tone.

Note See the Glossary for the meaning of acronyms used in this table.

Table A-1 Feature Tones

Feature Tone Condition(s) That Cause the Specified Tone To Be Played 1

AC ALERTING PATTERN 3

ACR No special tone delivered

ACRA

ACRD

CONFIRMATION TONE Anonymous call rejection (ACR) was successfully activated or deactivated by user actions.

REORDER TONE ACR was not successfully activated or deactivated by user actions.

AR ALERTING PATTERN 3

A-1itch Operations and Maintenance Guide

Appendix A Feature TonesList of Tones Applicable to Specific Features

BLV/OI REORDER TONE Normal access is not available.

There is a local office problem.

The line is momentarily unavailable.

No-test access is not available.

BUSY VERIFICATION CFU is activated on the terminating line.

Terminating line is a data-only line or a denied line.

PERMANENT SIGNAL TONE

Line up to receiver off-hook tone.

Terminating line receiving a permanent signal announcement.

Terminating line is high and wet (battery and ground shorted) or high and dry (off hook for an extended period).

CW

CIDCW

CW TONE If called party has MDN feature: primary DN matched.

If called party is in Centrex system with DACWI: there is no extension for the number dialed.

If called party has DRCW feature: calling party is not on the DRCW screening list.2

CW TYPE 2 If called party has MDN feature: second DN matched.

If called party is in Centrex system with DACWI: extension exists for the number dialed.

CW TYPE 3 If called party has MDN feature: third DN matched.

CW TYPE 4 If called party has DRCW feature: calling party is on the DRCW screening list.2

STUTTER TONE For Centrex subscriber with CHD feature and currently on an active call: A third party calls in, and the called party hears a call-waiting tone. The called party presses Flash button or switchhook to place the current remote station on hold, and hears the stutter tone.

The called party has the following options:

• Press Flash button or switchhook again to return to the original call.

• Dial a designated vertical service code (VSC)—typically *52—to be connected to the new calling party; the first calling party is kept on hold.

TONES OFF No tones are played for CW or CIDCW. (Tones are turned off under certain special circumstances.)

ALERTING PATTERN 1 Alerting pattern (ringing) is provided to the calling party and called party, as applicable, for all reconnect, re-ring, callback and recall scenarios.

Table A-1 Feature Tones (continued)


A-2Cisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04


CCW CONFIRMATION TONE User in two-way call cancels call waiting.

DIAL TONE POTS or Centrex user picks up phone to cancel call waiting.

STUTTER TONE User places the other party on hold (CHD) and then activates CCW while call is still on hold.

ALERTING PATTERN 1 User goes on hook with the other party still on hold; the system provides alerting pattern (ringing).

CDP DIAL TONE User is granted access to an outside (public) line, typically after dialing 9.

ALERTING PATTERN 3 Member of a Centrex group receives an incoming call from the group attendant.

CFU REMINDER RING TONE Alerting pattern (ringing) is provided on the called station to indicate that a call has been received and automatically forwarded.

CFU-ACT STUTTER TONE User has successful activated CFU from the handset.

DIAL TONE User has dialed the CFU-ACT star code, and the system is ready to receive digits for the forward-to DN.

1-second timer elapses following the confirmation tone.

CONFIRMATION TONE Centrex user successfully activates extension forwarding.

If the user has multiple call forwarding (MCF), the user has successfully activated a chain call forwarding scenario

POTS user receives ROUTE SELECTED DIALING PLAN.

REORDER TONE The CFU-ACT attempt was not successful due to

• Attempt to activate CFU when it was already activated

• Attempt to forward calls to a DN that could not be reached

• Attempt to forward call from a DN to itself.

CFU-DEACT CONFIRMATION TONE User successfully deactivates CFU.

DIAL TONE 1-second timer elapses following the confirmation tone.

REORDER TONE User attempts to deactivate CFU when it was already deactivated

CFB-ACT and CFNA-ACT

DIAL TONE User has dialed the CFB-ACT or CFNA-ACT star code, and the system is ready to receive digits for the forward-to DN.

CONFIRMATION TONE User successfully activates CFB or CFNA.

DIAL TONE 1-second timer elapses following the confirmation tone.

CFB-DEACT and CFNA-DEACT

CONFIRMATION TONE User has dialed the CFB-DEACT or CFNA-DEACT star code, and CFB or CFNA has been deactivated.

DIAL TONE Issued after a 1-second timer elapses following the confirmation tone.




OL-4495-04


CHD STUTTER TONE For Centrex subscriber (controlling party) currently on an active call: The controlling party places the other party on hold by pressing the Flash button or switchhook, and hears the stutter tone.

Controlling party has the following options:

• Press Flash button or switchhook again to return to the original call.

• Dial a designated vertical service code (VSC)—typically *52—hear the stutter tone again, then dial the number of a third party. The first calling party is kept on hold.

ALERTING PATTERN 1 Alerting pattern (ringing) is provided to the calling party and called party, as applicable, for all reconnect, re-ring, callback and recall scenarios.

CNAM

CNDNo special tone delivered

CNDB

CNAB

CIDB

CIDS

DIAL TONE User has dialed the star code for the identity blocking feature, and the system is ready to receive digits for the DN to be called.

COS:

Account Codes

CONFIRMATION TONE The system prompts the user to enter the account code.

COS:

Authorization Codes

CONFIRMATION TONE The system prompts the user to enter the authorization code.

CPRK REORDER TONE User has dialed the call park (CPRK) access code, but is not subscribed to the CPRK feature.

The user is subscribed to the CPRK feature, and has dialed the CPRK access code, but the CPRK attempt was not successful.

Note In this case (CPRK attempt was not successful), the reorder tone is played for two seconds, and then the user is reconnected to the original call.

STUTTER TONE User presses Flash button or switchhook to park the call.

CPRK_RET REORDER TONE The user is subscribed to the CPRK feature, and has dialed the CPRK access code, but is unable to retrieve the call.

STUTTER TONE The user enters the CPRK_RET access code, and the system is waiting for the user to dial the extension against which the parked call should be retrieved.

CT/TWC ALERTING PATTERN 1 User hangs up with one party on hold.

DACWI ALERTING PATTERN 3 Distinctive ring pattern.




OL-4495-04


DPN STUTTER TONE User has dialed DPN access code, and DPN access has been granted.

REORDER TONE Reorder tone is returned to the user who initiated a DPN request when any of the following occurs:

• The DPN feature has not been assigned to the requesting line.

• The dialed extension is not assigned in the business group dialing plan.

• The line associated with the dialed extension is not being rung. (Note that "being rung" should not include being given call-waiting treatment.)

• The call has been answered, picked up, or abandoned.

• The requesting line is not allowed to pick up the particular call because of being assigned the fully restricted terminating or the denied termination feature.

DPU STUTTER TONE User has dialed DPU access code, and DPU access has been granted.

REORDER TONE Reorder tone is returned to the user who initiated a DPU request when any of the following occurs:

• The dialed extension is not assigned in the business group dialing plan.

• The line associated with the dialed extension is not assigned the DPU feature.

• The line associated with the dialed extension is neither being rung nor involved in a stable two-way call. (Note that "being rung" should not include being given call-waiting treatment. Note also that DPU should not allow a user to barge-in on the controller of a multiway connection, that is, a call-waiting configuration, a call-hold configuration, or a conference call.)

• The call is abandoned by the caller before the DPU request is recognized or has been picked up by a line without DPU assigned.

• The requesting line is not allowed to pick up the particular call because of being assigned the fully restricted terminating or the denied termination feature.

CONFIRMATION TONE Barge-in connection is being processed and connection will occur within one second.

Note Confirmation tone is repeated twice.

DRCW ALERTING PATTERN 1 DN of incoming call is not on the DRCW screening list.

ALERTING PATTERN 6 DN of incoming call is on the DRCW screening list.

CW TONE DN of incoming call is not on the DRCW screening list.

CW TYPE 4 DN of incoming call is on the DRCW screening list.

Emergency—911 ALERTING PATTERN 1 After a normal two-party call, the user presses the Flash button or hookswitch, dials 911, and then hangs up before the 911 operator answers.




OL-4495-04

Appendix A Feature TonesTone Frequencies and Cadences

Tone Frequencies and CadencesTable A-2 lists the frequency and cadence for tones applicable to subscriber and operator features. Tones are requested by the Cisco BTS 10200 Softswitch and delivered to the subscriber or operator by the MGW. Some MGWs can be provisioned to play tone cadences different than the ones described in this table.

MDN ALERTING PATTERN 1 Station is on hook and there is an incoming call to primary DN.

ALERTING PATTERN 4 Station is on hook and there is an incoming call to secondary DN.

ALERTING PATTERN 5 Station is on hook and there is an incoming call to the third DN.

CW TONE Station is off hook and there is an incoming call to primary DN.

CW TYPE 2 Station is off hook and there is an incoming call to secondary DN.

CW TYPE 3 Station is off hook and there is an incoming call to the third DN.

MWI 3 MWI TONE User, who is subscribed to MWI service, has a message waiting.

MIDCALL STUTTER TONE After pressing Flash button or hookswitch and the system acknowledges it is as a valid midcall action.

ALERTING PATTERN 1 User goes on hook with the other party still on hold; the system provides alerting pattern (ringing).

SC1D-ACT

SC2D-ACT

STUTTER TONE Stutter tone is used once after the user enters the *74 (SC1D activation) or *75 (SC2D activation) to begin the process of collecting the information required to provision one of the speed call slots. After a speed call slot has been successfully provisioned, the user will again receive the stutter tone to signify that the speed call slot was successfully provisioned.

VMWI 3 STUTTER TONE User, who is subscribed to VMWI service, has a message waiting, but the serving MGW does not have a visual indicator.

1. When more than one condition is listed for a single tone, any one of the conditions can cause the tone to be played.

2. For more information on the screening list, refer to the Cisco BTS 10200 Softswitch System Description.

3. MWI = message waiting indicator; VMWI = visual message waiting indicator.



Table A-2 Subscriber and Operator Tone Descriptions

Tone Frequency (Hz) Cadence Played by MGW

Alerting pattern (ringing) 1 440 + 480 2 sec on, 4 sec off, repeating

Alerting pattern (ringing) 2 440 + 480 0.8 sec on, 0.4 sec off, 0.8 sec on, 4.0 sec off, repeating

Alerting pattern (ringing) 3 440 + 480 0.4 sec on, 0.2 sec off, 0.4 sec on, 0.2 sec off, 0.8 sec on, 4 seconds off, repeating

Alerting pattern (ringing) 4 440 + 480 0.3 sec on, 0.2 sec off, 1 sec on, 0.2 sec off, 0.3 sec on, 4 sec off, repeating

Alerting pattern (ringing) 5 440 + 480 0.5 sec on once

Alerting pattern (ringing) 6 440 + 480 1 sec on, 3sec off, repeating


OL-4495-04


Table A-3 lists the maintenance tones used for continuity testing. See the Telcordia document GR-317-CORE for additional details.

Busy verification(used for operator BLV 1)

440 2 sec burst, followed by 0.5 sec burst every 10 sec

CW tone 440 0.3 sec on once

CW Type 1 440 0.3 sec on once

CW Type 2 440 0.1 sec on, 0.1 sec off, 2 times

CW Type 3 440 0.1 sec on, 0.1 sec off, 3 times

CW Type 4 440 0.1 sec on, 0.1 sec off, 0.3 sec on, 0.1 sec off, 0.1 sec on

Confirmation tone 350 + 440 0.1 sec on, 0.1 sec off, 3 times

Dial tone 350 + 440 steady on

Line busy tone 480 + 620 0.5 sec on, 0.5 sec off, repeating

Message waiting indicator tone 350 + 440 10 bursts (0.1 sec on, 0.1 sec off), then steady on

Off-hook warning tone(receiver off-hook tone)

1400 + 2060 + 2450 + 2600

0.1 sec on, 0.1 sec off, repeating

Permanent signal(used for operator BLV 1)

480 Steady on

Reminder ring tone (ring splash) 440 + 480 0.5 sec ring

Reorder tone 480 + 620 0.25 sec on, 0.25 sec off, repeating

Ringback tone (audible ringing) 440 + 480 2 sec on, 4 sec off (repeated)

Stutter (recall) dial tone 350 + 440 3 bursts (0.1 sec on, 0.1 sec off), then steady on

1. BLV = busy line verification

Table A-2 Subscriber and Operator Tone Descriptions (continued)

Tone Frequency (Hz) Cadence Played by MGW

Table A-3 Maintenance Tone Descriptions

Tone Frequency (Hz) Description

2010-Hz continuity tone

2010 Used for single-tone test under either of the following conditions:

• The circuit is a 4-wire circuit at both the transceiver end and the distant end

• The circuit is a 2-wire circuit at the transceiver end

1780-Hz continuity tone

1780 Used for dual-tone test with a 4-wire circuit at the transceiver end and a 2-wire circuit at the distant end


OL-4495-04



OL-4495-04

Cisco BTS 10200 Softswitch OL-4495-04

A
P P E N D I X B Recoverable and Nonrecoverable Error Codes
This appendix lists normal, recoverable and nonrecoverable error codes for the Cisco BTS 10200 Softswitch. Table B-1 categorizes MGCP error codes into three categories: normal, recoverable, and non-recoverable. Table B-1 also provides some of the behaviors of the Cisco BTS 10200 for different MGCP message error codes. Endpoint connection (EPCF) and audit connection (AUCX) messages are not sent by the Cisco BTS 10200 Softswitch to the gateway.

Table B-1 MGCP Normal, Recoverable, and Nonrecoverable Error Codes

MGCP Error Code Description AUEP DLCX CRCX MDCX RQNT

200 The requested transaction was executed normally.

N N N N N

250 The connection was deleted. F N N N R

400 Transient error. If this code is received, the Cisco BTS 10200 tries to recover by retransmitting the MGCP message with a different transaction identifier for a predefined number of times before declaring the endpoint faulty. The number of times is configurable at platform startup time, its default is 2.

R R R R R

401 Phone is already offhook. If this code is received, the Cisco BTS 10200 updates the endpoint resource state and continues with normal operation

F F R N N

402 Phone is already onhook. If this code is received, the Cisco BTS 10200 updates the endpoint resource state and continues with normal operation.

F F R N N

403 Endpoint does not have sufficient resources at this time. If this code is received, the Cisco BTS 10200 automatically recovers by auditing the endpoint, deleting any available connections and then idling the endpoint.

R F N N R

B-1Operations and Maintenance Guide

Appendix B Recoverable and Nonrecoverable Error Codes

404 Insufficient bandwidth at this time. If this code is received, the Cisco BTS 10200 automatically recovers by auditing the endpoint, deleting any available connections and then idling the endpoint.

F F N N R

405 The transaction could not be executed, because the endpoint is “restarting.”

R F N N R

406 Transaction time-out. The transaction did not complete in a reasonable period of time and has been aborted.

R F N N R

407 Transaction aborted. The transaction was aborted by some external action, e.g. a ModifyConnection command aborted by a DeleteConnection command

R F N N R

500 Endpoint is unknown. If this code is received during idling of an endpoint, the Cisco BTS 10200 marks the endpoint as faulty and perform automatic recovery.

F F F N F

501 Endpoint is not ready. If this code is received, the Cisco BTS 10200 automatically recovers by auditing the endpoint, deleting any available connections and then idling the endpoint.

R F N N R

502 The transaction could not be executed, because the endpoint does not have sufficient resources (permanent condition)

R F N N R

503 “All of” wildcard too complicated F F N N R

509 Error in RemoteConnectionDescriptor F F F N F

510 The transaction could not be executed, because some unspecified protocol error was detected. Automatic recovery from such an error will be very difficult, and hence this code SHOULD only be used as a last resort

R F N N R

511 The transaction could not be executed, because the command contained an unrecognized extension. This code SHOULD be used for unsupported critical parameter extensions (“X+”)

F F F N F

Table B-1 MGCP Normal, Recoverable, and Nonrecoverable Error Codes (continued)


B-2Cisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04


512 The transaction could not be executed, because the gateway is not equipped to detect one of the requested events

F F N N F

513 The transaction could not be executed, because the gateway is not equipped to generate one of the requested signals.

F F N N F

514 The transaction could not be executed, because the gateway cannot send the specified announcement.

F F N N R

515 The transaction refers to an incorrect connection-id (may have been already deleted).

F N N N R

516 The transaction refers to an unknown call-id, or the call-id supplied is incorrect (e.g. connection-id not associated with this call-id).

F N N N R

517 Unsupported or invalid mode. F F F N R

518 Unsupported or unknown package. It is RECOMMENDED to include a PackageList parameter with the list of supported packages in the response, especially if the response is generated by the Call Agent.

F F F N F

519 Endpoint does not have a digit map F F N N R

520 The transaction could not be executed, because the endpoint is “restarting.” In most cases this would be a transient error, in which case, error code 405 SHOULD be used instead. The error code is only included here for backwards compatibility

R F N N R

521 Endpoint redirected to another Call Agent. The associated redirection behavior is only well-defined when this response is issued for a RestartInProgress command

F F N N R

522 No such event or signal. The request referred to an event or signal that is not defined in the relevant package (which could be the default package).

F F N N F

523 Unknown action or illegal combination of actions

R F N N R

524 Internal inconsistency in LocalConnectionOptions.

F F N N R




OL-4495-04


525 Unknown extension in LocalConnectionOptions. This code SHOULD be used for unsupported mandatory vendor extensions (“x+”).

F F F N R

526 Insufficient bandwidth. In cases where this is a transient error, error code 404 SHOULD be used instead.

F F N N R

527 Missing RemoteConnectionDescriptor. F F F N R

528 Incompatible protocol version F F F N F

529 Internal hardware failure F F F N F

530 CAS signaling protocol error R F N N R

531 Failure of a grouping of trunks (e.g. facility failure)

F F N N R

532 Unsupported value(s) in LocalConnectionOptions.

F F F N R

533 Response too large. F F N N R

534 Codec negotiation failure. F F N N R

535 Packetization period not supported. F F N N R

536 Unknown or unsupported RestartMethod F F N N R

537 Unknown or unsupported digit map extension

F F N N F

538 Event/signal parameter error (e.g. missing, erroneous, unsupported, unknown, etc.).

F F N N F

539 Invalid or unsupported command parameter. This code SHOULD only be used when the parameter is neither a package or vendor extension parameter

F F N N R

540 Per endpoint connection limit exceeded. F F N N R

800 F F N F F

801 F F N F F

802 F F N F F

803 F F N F F

Unknown like 900

F F F F F




OL-4495-04


Invalid or absent transaction identifier

RX RX RX RX RX

Note AUEP—Audit Endpoint, DLCX—Delete Connection, CRCX—Create Connection, MDCX—Modify Connection, RQNT—Notification Request

Note Normal (N)—other than 200 error code, the BTS 10200 clears the call. Recoverable (R)—: the BTS 10200 clears the call and starts finite recovery. Non-recoverable(NR) or Faulty(F)— the BTS 10200 clears the call.

Note For 400 error codes,the BTS 10200 retransacts (RT) the corresponding MGCP message. The BTS 10200 also retransmits (RX) the MGCP message with the same transaction.




OL-4495-04



OL-4495-04


A P P E N D I X C
Release Cause Codes
For reference purposes, the Cisco BTS 10200 Softswitch defined call release cause codes are listed in Table C-1 through Table C-7.

Table C-1 lists the generic release cause codes for normal events.

Table C-1 Cisco BTS 10200 Softswitch Release Cause Codes—Normal Events

Call Release Cause Code

SS7A.2.4.3/GR-905-CORE

ISDNTable I.2/Q.931 MGCP

Normal Event

1. [Note 1] 1. Unallocated number 1. Unallocated (Unassigned) number

N/A

2. 2. No route to specified transit network

2. No route to specified transit network

N/A

3. [Note 1] 3. No route to destination 3. No route to destination N/A

4. [Note 2] N/A 6. Channel unacceptable

5. [Note 3] N/A 7. Call awarded and being delivered in an established channel

6. 16. Normal clearing 16. Normal call clearing N/A

7. 17. User busy 17. User busy 401. Phone is already off hook

— — 402. Phone is already on hook

8. 18. No user responding 18. No user responding Notified event

9. 19. User alerting, no answer 19. User alerting,

no answer

Notified event

10. [Usr->Nw] 21. Call rejected 21. Call rejected

11. [Note 1] 22. Number changed 22. Number changed

C-1itch Operations and Maintenance Guide

Appendix C Release Cause Codes

Table C-2 lists the generic call release cause codes when network resources are unavailable.

12.1 26. Misrouted call to a ported number

N/A

13. [Note 3] N/A 26. Nonselected user clearing

14.1 27. Query on Release (QoR) number not found (No procedures for US networks

15. 27. Destination out of order 27. Destination out of order 520

16. [Note 1] 28. Address incomplete 28. Invalid number format (incomplete number)

N/A

17. [nw->usr] 29. Facility rejected N/A

18. [Note 4] 30. Response to STATUS ENQUIRY

N/A

500. The transaction could not be executed because the endpoint is unknown

19. [Note 5] 31. Unspecified (default) 31. Unspecified (default)

1. ANSI Standard release cause code only

Table C-1 Cisco BTS 10200 Softswitch Release Cause Codes—Normal Events (continued)




Table C-2 Cisco BTS 10200 Softswitch Release Cause Codes—Network Resource Unavailable




Network resource unavailable

31. 34. No Circuit available 34. No circuit/channel available

32. 38. Network out of order Can not reach MGW, network interface down

33. 41. Temporary failure 41. Temporary failure 400. Transaction not completed due to transient error

34. 42. Switching congestion 42. Switching equipment congestion

N/A

35. [Note 6] 43. Access information

discarded1

43. Access information discarded

C-2Cisco BTS 10200 Softswitch Operations and Maintenance Guide

OL-4495-04


Table C-3 lists the generic call release cause codes when a service or option is not available.

Table C-4 lists the generic cause codes when a service or option is not implemented.

36. Circuit Reservation Rejected (CMJ)

44. Requested circuit/channel not available

501.Endpoint not ready

37. 47. Resource unavailable (default)

47. Resource unavailable, unspecified

502. Endpoint does not have sufficient resource

1. ANSI standard cause value

Table C-2 Cisco BTS 10200 Softswitch Release Cause Codes—Network Resource Unavailable




Table C-3 Cisco BTS 10200 Softswitch Release Cause Codes—Service Or Option Not Available




Service or option not available

41. 57. Bearer capability not authorized

57. Bearer capability not authorized

N/A

42. 58. Bearer capability not presently available

58. Bearer capability not presently available

N/A

43. 63. Service/Option not available (default)

63. Service or option not available, unspecified

N/A

Table C-4 Cisco BTS 10200 Softswitch Release Cause Codes—Service/Option Not Implemented




Service or option not implemented

51. 65. Bearer capability not implemented

65. Bearer capability not implemented

N/A

52. 66. Channel type not implemented

N/A

53. 69. Requested facility not implemented

N/A

54. 70. Only restricted digital information bearer capability is available

N/A

55. 79. Service/Option not implemented (default)

79. Service or option not implemented, unspecified

N/A


OL-4495-04


Table C-5 lists the generic call release cause codes for invalid messages.

Table C-6 lists the genericcall release cause codes for protocol errors.

Table C-5 Cisco BTS 10200 Softswitch Release Cause Codes—Invalid Message




Invalid message (local significance only)

61. 81. Invalid call reference value

516

62. 82. Identified channel does not exist

500. Unknown endpoint

63. 83. A suspended call exists, but this call identity does not

64. 84. Call identity in use

65. 85. No call suspended

66. 86. Call having the requested call identity has been cleared

402. The phone is already on hook

67. 88. Incompatible destination 88.Incompatible destination

68. 91. Invalid transit network selection

91. Invalid transit network selection

69. 95. Invalid message (default) 95. Invalid message, unspecified

70. 96. Mandatory information element is missing

71. 97. Message type nonexistent or not implemented

Table C-6 Cisco BTS 10200 Softswitch Release Cause Codes—Protocol Error




Protocol error (local significance only)

81. 97. Message type nonexistent or not implemented

98. Message not compatible with call state or message type nonexistent or not implemented or 41 Temporary failure


OL-4495-04


Table C-7 lists the generic call release cause codes for interworkings.

The numbered notes are listed below:

1. If, following the receipt of a SETUP message or during overlap sending, the network determines that the call information received from the user is invalid, (for example, an invalid number), then the network follows the procedures for a cause such as one of the following: #1—Unassigned (unallocated) number#3—No route to destination#22—Number changed#28—Invalid number format (incomplete number)

2. The SETUP message can specify the channel identification information element (IE) for B-channel selection preference indicating preferred channel and alternative channel. If there is no B-channel available for the given criteria, this cause code is sent.

3. In the case of call offering, where multiple terminating exchanges are served with SETUP messages and they in turn respond back with CONNECT messages, the network sends a RELEASE message to the selected users with the cause code call awarded and being delivered in an established channel (#7), and with cause code nonselected user clearing (#26).

82. 99. Parameter not existent or implemented—discarded

99. Information element nonexistent or not implemented or 41 Temporary failure

83. 100. Invalid information element contents

84. 101. Parameter not existent or implemented—passed on

101. Message not compatible with call state or 41 Temporary failure

85. 102. Recovery on timer expiry

102. Recovery on time expiry

86. 111. Protocol error (default) 111. Protocol error, unspecified or 41 Temporary failure

510. Protocol Error was detected

Table C-6 Cisco BTS 10200 Softswitch Release Cause Codes—Protocol Error (continued)




Table C-7 Cisco BTS 10200 Softswitch Release Cause Codes—Interworking



ISDNtable I.2/Q.931 MGCP

Interworking

91. 127. interworking—unspecified (default)

127. Interworking, unspecified


OL-4495-04


4. Upon receipt of a STATUS ENQUIRY message, the receiver responds with a STATUS message, reporting the current call state (the current state of an active call or a call in progress, or the null state if the call reference does not relate to an active call or to a call in progress) and cause #30, as a response to the STATUS ENQUIRY.

5. The terminating exchange can interpret an unspecified cause code as normal clearing (#16), and the originating exchange during the call setup procedure can interpret it as call rejected (#21).

6. IEs with a length exceeding the maximum length are treated as an IE with content error. But for access IEs (for example, a user to user information element or a called-party subaddress IE), cause #43, access information discarded, is used instead of cause No. 100, invalid IE contents.


OL-4495-04

Documents

Cisco Bts 10200 Soft Switch