Cisco BTS 10200 Softswitch Operations and Maintenance Guide Release 6.0.1 February 18, 2010 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
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.
CONTENTS Preface ix Introduction CHAPTER 1 iii-ix Starting and Shutting Down the BTS Introduction 1-1 Meeting Power Requirements Starting BTS Hardware Starting BTS Software 2 1-1 1-1 Shutting Down BTS Hardware CHAPTER 1-1 1-2 1-2 Managing BTS Users and Commands Using EMS Introduction 2-1 Logging into the EMS Using CLI Managing Users 2-1 2-1 2-2 Managing Commands 2-5 Adapter and User Security 2-6 Solaris OS Security and BTShard Package 2-7 Operator Interface 2-10 Vulnerabilities in H
Contents CHAPTER 3 Monitoring and Backing Up the BTS Introduction 3-1 3-1 Detecting and Preventing BTS Congestion Monitoring BTS Hardware 3-1 3-1 Checking BTS System Health 3-2 Using BTS System-Health Reports 3-3 Checking BTS System Time 3-4 Checking the OS Log of Each Host Machine 3-4 Checking Disk Mirroring on Each Host Machine 3-5 CA/FS Side A 3-5 CA/FS Side B 3-5 EMS Side A 3-6 EMS Side B 3-6 Auditing Databases and Tables 3-7 Exporting Provisioned Data 3-8 Limitations 3-10 Creating Numbering Re
Contents LAF Alarm Information Moving Core Files CHAPTER 4 Operating the BTS Introduction 3-29 4-1 4-1 Managing Subscribers Viewing Calls 3-29 4-2 4-6 Using Status and Control Commands 4-7 Using Show and Change Commmands Using ERAC Commands 4-9 Managing Transactions 4-12 Scheduling Commands Limitations 4-13 CHAPTER 5 4-13 Managing External Resources Introduction 4-9 5-1 5-1 Viewing BTS System-Wide Status 5-1 Managing Trunk Groups and Trunks 5-3 Managing Subscriber Terminations
Contents POTS Application Server Measurements 6-22 POTS Miscellaneous FS Measurements 6-22 POTS Class of Service FS Measurements 6-24 POTS Screen List Editing FS Measurements 6-25 POTS Customer Originated Trace FS Measurements 6-25 POTS Automatic Callback, Recall, and Call Return Measurements 6-26 POTS Limited Call Duration (Prepaid/Postpaid) with RADIUS Interface to AAA Measurements POTS Call Forwarding Combination Measurements 6-28 AIN Services FS Measurements 6-29 SCCP Protocol Measurements 6-31 TCAP Pr
Contents Disk I/O Usage Measurements 6-78 ENUM Measurements 6-78 Diameter Message Counters 6-79 Single Number Reach Counters 6-80 CHAPTER 7 Using the BTS SNMP Agent Introduction 7-1 7-1 Managing User Access to the SNMP Agent Viewing SNMP Trap Reports 7-2 Viewing and Managing BTS Components Querying the SNMP Agent 7-1 7-4 7-6 Enabling NMS to Query/Poll Solaris SNMP Agent APPENDIX A Feature Tones Introduction A-1 A-1 Tones per Feature A-1 Tone Frequencies and Cadences APPENDIX B FIM/XML
Contents Feature Configuration B-10 Subscriber-Sip-Trigger-Profile B-11 Service-Id B-11 Subscriber-Service-Profile B-11 Feature Restrictions and Limitations B-11 Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
Preface Revised: February 18, 2010, OL-16000-07 Introduction This document is the Operations and Maintenance Guide for the Cisco BTS 10200 Softswitch, Release 6.0.1.
Preface Introduction Document Change History This table provides the revision history for the Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.x. Table 1 Revision History Version Number Issue Date OL-16000-01 31 Mar 2008 Initial Initial document for Release 6.0 OL-16000-02 31 July 2008 Updated Added Change Number instructions for subscribers.
Preface Introduction Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0. Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
Preface Introduction Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
CH A P T E R 1 Starting and Shutting Down the BTS Revised: February 18, 2010, OL-16000-07 Introduction This chapter tells you how to start up and shut down the BTS. Meeting Power Requirements To meet high availability requirements: • Do not have common parts in the power feeds to the redundant hardware that could be a common single point of failure. • Use uninterruptible power supply (UPS) for both AC and DC systems.
Chapter 1 Starting and Shutting Down the BTS Shutting Down BTS Hardware Step 2 Plug in Catalyst switch routers. Step 3 Power on EMS/BDMS hosts A and B. Step 4 Power on CA/FS hosts A and B. Shutting Down BTS Hardware Step 1 Ensure CA side A and EMS side A are active. Step 2 Ensure CA side B and EMS side B EMS are standby. Step 3 Log into CA side A and B and EMS side A and B using Secure Shell (SSH). Step 4 Shut down the system in order: 1. EMS side B 2. CA side B 3. CA side A 4.
Chapter 1 Starting and Shutting Down the BTS Starting BTS Software Step 4 Once all components start, enter nodestat to ensure proper startup. Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
Chapter 1 Starting and Shutting Down the BTS Starting BTS Software Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
CH A P T E R 2 Managing BTS Users and Commands Using EMS Revised: February 18, 2010, OL-16000-07 Introduction This chapter describes operator interfaces to the BTS and how to manage access and users. The Element Management System (EMS) database holds up to 256 logins and up to 50 active user sessions.Using the command line interface (CLI) you can locally connect to the EMS in an interactive session.The EMS system administrator can: • Add a new user.
Chapter 2 Managing BTS Users and Commands Using EMS Managing Users The “ciscouser” login is a high-level security login for TAC and other BTS support personnel that restricts access to certain commands. Anyone else trying to execute such commands receives an error message. After installation, on the EMS, the system prompts you to change the passwords of root, btsadmin, btsuser and calea if they have default passwords.
Chapter 2 Managing BTS Users and Commands Using EMS Managing Users Table 2-1 Managing Users (continued) Task Sample Command Viewing user activity show ems; Changing a user change user name=UserABC; command-level=1; work-groups=somegroup; Deleting a user delete user name=UserABC; You cannot delete optiuser.
Chapter 2 Managing BTS Users and Commands Using EMS Managing Users Table 2-1 Managing Users (continued) Task Blocking an active user Sample Command 1. Select operation mode: • MAINTENANCE—(default) for regular maintenance • UPGRADE—for upgrades 2. block session terminal=USR16; Note You cannot block the session of a user with higher privileges than yours.
Chapter 2 Managing BTS Users and Commands Using EMS Managing Commands Note All commands should be assigned to a work-group. If a command is not assigned to a work-group, a user will able to execute that command, which is not recommended. You can also assign users and the commands to multiple work-groups. Managing Commands Each command (verb-noun combination) has a security class of 1-10; 1 is lowest, 10 is highest.
Chapter 2 Managing BTS Users and Commands Using EMS Adapter and User Security Security is an important part of the BTS 10200. The BTS 10200 has interfaces to customer premise equipment (CPE) as well as northbound Operations Support System (OSS) interfaces. All of these interfaces are subject to attacks. In addition, users who are allowed onto the BTS 10200 can also find ways to exploit applications that can lead to service-affecting situations.
Chapter 2 Managing BTS Users and Commands Using EMS Solaris OS Security and BTShard Package Solaris OS Security and BTShard Package This section details the security packages for the BTS 10200 OS. These packages are automatically installed at installation. These packages are derived from both Sun Microsystems security bulletins and Cisco internal policies for safety of the OS and its applications. All services can be reactivated for the lifetime of the current kernel instance.
Chapter 2 Managing BTS Users and Commands Using EMS Solaris OS Security and BTShard Package • The following UNIX accounts are to be LOCKED but not removed from the system: lp, uucp, nuucp, nobody, listen, and any other Cisco support accounts not used in the normal course of field operation. Services managed by root are the only accounts allowed to utilize one of these identities. This is the default behavior.
Chapter 2 Managing BTS Users and Commands Using EMS Solaris OS Security and BTShard Package • IP_RESPOND_TO_ECHO_BROADCAST—This option determines whether to respond to ICMP broadcast echo requests (ping). An attacker may try to create a denial of service attack on subnets by sending many broadcast echo requests to which all systems will respond. This also provides information on systems that are available on the network. The Solaris default value is 1 (True).
Chapter 2 Managing BTS Users and Commands Using EMS Solaris OS Security and BTShard Package – S88sendmail – S93cacheos.finish – S99dtlogin Operator Interface Additional commands have been added to manage the UNIX services in the BTS 10200. These commands are available from the CLI/MAINT interface. In addition, these same commands are also available from the CORBA and bulk-provisioning interface. There are no schemas and tables associated with these commands. They directly control the UNIX services.
Chapter 2 Managing BTS Users and Commands Using EMS Solaris OS Security and BTShard Package Table 2-3 Node Command for UNIX Services (continued) Noun Verb Options Description Node Show SERVICE [Required] Defines the service to display. Must be one of the following: FTP, TELNET, ECHO, DISCARD, PRINTER, DAYTIME, CHARGEN, SMTP, TIME, FINGER, SUNRPC, EXEC, LOGIN, SHELL, UUCP, NFS, LOCKD, X11, DTSCP, FONT-SERVICES, HTTP.
Chapter 2 Managing BTS Users and Commands Using EMS Sun Microsystems Configurations Pluggable Authentication Module Support The BTS 10200 deploys a Secure Shell (SSH) package with Pluggable Authentication Module (PAM) support. The package includes the PAM support required to utilize the Radius and LDAP servers. The supporting configuration allows local accounts to fall through if the Radius and LDAP servers are not available.
Chapter 2 Managing BTS Users and Commands Using EMS Sun Microsystems Configurations Table 2-4 Solaris Architectural- or Hardware-Specific Optional Package List (continued) Package Description Type Status SUNWdfb Dumb Frame Buffer device drivers SYSTEM — SUNWensqr Ensoniq ES1370/1371/1373 Audio device driver (32-bit) (Root) SYSTEM — SUNWensqx Ensoniq ES1370/1371/1373 Audio device driver (64-bit) (Root) SYSTEM — SUNWeridx Sun RIO 10/100 Mb Ethernet drivers (64-bit) SYSTEM — SUNWfcip S
Chapter 2 Managing BTS Users and Commands Using EMS Solaris OS Patches Table 2-4 Solaris Architectural- or Hardware-Specific Optional Package List (continued) Package Description Type Status SUNWpdx PCI drivers (64-bit) SYSTEM — SUNWpiclh PICL Header files SYSTEM — SUNWpiclr PICL Framework (Root) SYSTEM — SUNWpiclu PICL libraries and Plugin modules (Usr) SYSTEM — SUNWpiclx PICL libraries (64-bit) SYSTEM — SUNWqfed Sun Quad FastEthernet Adapter driver SYSTEM — SUNWqfedx Sun
Chapter 2 Managing BTS Users and Commands Using EMS Solaris OS Patches • SUNWtnfd—Utilities needed by developers using TNF facilities. • SUNWtnfx—The 64-bit utilities needed to enable probe points, in the kernel and in applications, that can generate TNF records in a trace file. XML Libraries The Sun VTS software requires the use of the XML libraries on the BTS 10200. These are in the supplemental part of the Solaris distribution with the VTS packages.
Chapter 2 Managing BTS Users and Commands Using EMS Solaris OS Patches • 108993-38—The SunOS 5.8: LDAP2 client, libc, libthread and libnsl libraries patch. • 109326-16—The SunOS 5.8: libresolv.so.2 and in.named patch. • 110615-13—The SunOS 5.8: sendmail patch. Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
CH A P T E R 3 Monitoring and Backing Up the BTS Revised: February 18, 2010, OL-16000-07 Introduction This chapter includes overall BTS maintenance strategies. Detecting and Preventing BTS Congestion When congested the BTS automatically does the following: • Detects internal messaging congestion caused by traffic overload or other extraordinary events. • Takes preventive action to avoid system failure (including shedding of traffic). • Generates alarms when it detects internal messaging.
Chapter 3 Monitoring and Backing Up the BTS Checking BTS System Health • Partitions consumed: – A partition 70 percent consumed generates a minor alarm. – A partition 80 percent consumed generates a major alarm. – A partition 90 percent consumed generates a critical alarm. Table 3-1 Managing Hardware Task Sample Command Running node reports report node node=prica42; Note Results may take a few minutes to display.
Chapter 3 Monitoring and Backing Up the BTS Checking BTS System Health Table 3-2 BTS System Health Checklist (continued) Auditing Databases and Tables Monthly Cleaning Filters Monthly See equipment manufacturer’s documentation.
Chapter 3 Monitoring and Backing Up the BTS Checking BTS System Health Table 3-3 Using BTS System-Health Reports (continued) Task Sample Command Deleting reports delete scheduled-command id=881958666704177006; Viewing completed reports In a web browser enter https://:/report/system_health Generating a report immediately report system-health period=<1 ... 720>; Note Results may take a few minutes to display.
Chapter 3 Monitoring and Backing Up the BTS Checking BTS System Health Checking Disk Mirroring on Each Host Machine Each procedure takes about 30 minutes. CA/FS Side A Before doing this procedure, ensure your BTS platform is connected to controller 1 or controller 0. Step 1 Log in as root to CA/FS side A using telnet.
Chapter 3 Monitoring and Backing Up the BTS Checking BTS System Health c0t0d0s7 c0t1d0s7 c0t0d0s0 c0t1d0s0 c0t0d0s3 c0t1d0s3 0 0 0 0 0 0 No No No No No No Okay Okay Okay Okay Okay Okay If the results differ synchronize the disk mirroring: # cd /opt/setup # sync_mirror Verify the results using Step 1 through Step 3. Caution In case of a mismatch, synchronize once. If the mismatch continues contact Cisco TAC. EMS Side A Step 1 Log in as root to EMS side A using telnet.
Chapter 3 Monitoring and Backing Up the BTS Checking BTS System Health Step 2 Enter # metastat | grep c0.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data Table 3-4 Auditing Databases and Tables (continued) Task Auditing mismatches across network elements Sample Command 1. Log in as root. 2.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data ######################### add clli_code ID=ABCD1234567; ########################## ##### Add call_agent ##### ########################## add call_agent id=CA146;tsap_addr=CA146.A.12345678901234567890123456789012345678 901234567890123456;mgw_monitoring_enabled=N;clli=ABCD1234567; ############################## ##### Add feature_server ##### ############################## add feature_server ID=FSAIN205;TSAP_ADDR=FSAIN.A.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data ############################################# ##### Change command_throttle_threshold ##### ############################################# change command_throttle_threshold SESSION_TYPE=CLI;THRESHOLD=100;ENABLE=Y; change command_throttle_threshold SESSION_TYPE=CORBA;THRESHOLD=100;ENABLE=Y; change command_throttle_threshold SESSION_TYPE=FTP;THRESHOLD=1000;ENABLE=Y; change command_throttle_threshold SESSION_TYPE=MNT;THRESHOLD=100;ENABLE=
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data – Non-Native = Y/N To generate the following reports, use report dn-summary: • All DNs in NDC and EC • Thousands group in NDC and EC • Operating company number (OCN) • Switch Common Language Location Identifier (CLLI) code • OCN + CLLI code—entries must match LERG data Creating Reports for Nonrural Primary and Intermediate Carriers NRUF reporting for nonrural primary and intermediate carriers: • Occurs at a thousands-block
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data Table 3-5 NRUF Report Data for Nonrural Carriers (continued) Data Groups Aging DNs Matching Data from the DN2SUBSCRIBER Table • DISC DNs: ndc=; ec=; DN=[0-9][0-9][0-9][0-9]; (status=DISC) • Changed Number DNs: ndc=; ec=; DN=[0-9][0-9][0-9][0-9]; (status=CN) • DISC DID DNs: ndc=; ndc=; ndc=; ndc=; • • DN=xxxx; (status=DISC) X 10000 DN=[0-9]xxx; (status=DISC) X 1000 DN=[0-9][0-9]xx; (st
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data • The Rural Primary Carrier (U2 form) NPA-NXX report has: – NPA-NXX (input as ndc, ec) – Rate Center (read from LERG) – State (read from LERG) – Number of Assigned DNs – Number of Intermediate DNs – Number of Reserved DNs – Number of Aging DNs – Number of Administrative DNs – Donated to Pool (always 0) • The Rural Intermediate Carrier (U4 form) report has: – NPA-NXX (input as ndc, ec) – Rate Center (read from LERG) – State (read fro
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data Table 3-6 Data Groups Assigned DNs NRUF Report Data for Rural Carriers Matching Data from the DN2SUBSCRIBER Table • Individual DNs: ndc=; ec=; DN=[0-9][0-9][0-9]; (status=assigned) AND ADMIN-DN=N ndc=; ec=; DN=[0-9][0-9][0-9]; (status=ported-out) AND ADMIN-DN=N • DID DNs: ndc=; ec=; DN=xxxx; (status=assigned) AND ADMIN-DN=N; X 10000 ndc=; ec=; DN=xxxx; (status=ported-out) AND ADMIN-DN=N; X
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data Table 3-6 NRUF Report Data for Rural Carriers (continued) Data Groups Aging DNs Matching Data from the DN2SUBSCRIBER Table DISC DNs: • ndc=; ec=; DN=[0-9][0-9][0-9][0-9]; (status=DISC) Changed Number DNs: • ndc=; ec=; DN=[0-9][0-9][0-9][0-9]; (status=CN) DISC DID DNs: • ndc=; ndc=; ndc=; ndc=; DN=xxxx; (status=DISC) X 10000 DN=[0-9]xxx; (status=DISC) X 1000 DN=[0-9][0-9]xx; (status=DI
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data Full Database Auditing Step 1 Log in as CLI user on EMS side A. Step 2 Enter audit database type=full;. Step 3 Check the audit report and verify that there is no mismatch or error. If errors are found, try to correct the errors. If you cannot make the correction, contact Cisco TAC. Checking Shared Memory This task checks shared memory to detect potential data problems. From CA/FS Side A Step 1 Log in as root.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data The result should match the following: All tables are OK. For detail, see ain_tiat.out Caution If the result is not“All tables are OK”, stop and contact Cisco TAC. From CA/FS Side B Step 1 Log in as root. Step 2 Enter: #cd /opt/OptiCall/CAxxx/bin #ca_tiat data Step 3 Press Enter. The result should match the following: All tables are OK. For detail, see ca_tiat.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data Caution If the result is not“All tables are OK”, stop and contact Cisco TAC. Backing Up the Full BTS Do this before and after software upgrades or as routine, always during a maintenance window.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data /opt/OptiCall/FSAINxxx/bin/data /opt/OptiCall/FSAINxxx/bin/logs /opt/OptiCall/FSPTCxxx/bin/data /opt/OptiCall/FSPTCxxxx/bin/logs where xxx is the instance number Step 10 Back up the system, enter: #mv /bin/date /bin/date.archive #mv /bin/.date /bin/date #flarcreate -n -X /tmp/excluded_dir -c /mnt/.archive #mv /bin/date /bin/.date #mv /bin/date.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data #flarcreate -n -X /tmp/excluded_dir -c /mnt/.archive #mv /bin/date /bin/.date #mv /bin/date.archive /bin/date Step 11 Unmount the NFS server, enter #umount /mnt.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data c. Optional: Enable the ora_arch_backup.ksh process. d. Log in as oracle, or su - oracle. e. Enter 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/t mp/ora_hot_backup.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data Step 2 Schedule the FTP process. a. Do this on the primary and secondary EMSs: Log in as oracle, or su – oracle and enter the following command: 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.
Chapter 3 Monitoring and Backing Up the BTS Exporting Provisioned Data # su - oracle $ cd /opt/orahome/.ssh $ sftp root@priems sftp> cd /opt/orahome/.ssh sftp> get id_rsa* sftp> quit $ ls -l /opt/orahome/.ssh/id_rsa* -rw-------1 oracleorainst1675 Mar 10 15:42 id_rsa -rw-r--r--1 oracleorainst397 Mar 10 15:42 id_rsa.pub Now both primary and secondary EMSs have the same "id_rsa" and "id_rsa.pub" files in /opt/orahome/.ssh directory.
Chapter 3 Monitoring and Backing Up the BTS Archiving Your Database -rw-------1 oraoragrp394 Mar 10 16:48 id_rsa.pub Step 6 Sftp the "id_rsa" and "id_rsa.pub" files generated in Step 1 to remote SFTP server /opt/orahome/.ssh directory. Make the file owned by "oracle:orainst" owner and group. Step 7 Test SSH and SFTP from both the primary and secondary EMSs to the remote SFTP server: a. From BTS primary EMS: # su - oracle $ sftp_ping oracle SFTPserverName Connecting to SFTPserverName...
Chapter 3 Monitoring and Backing Up the BTS Archiving Your Database Step 6 Restore the Solaris “date” command to create the system Flash Archive. Enter: mv /bin/date /bin/date.orig mv /bin/.date /bin/date Step 7 Create the archive. Enter #flarcreate -n -x /opt -S -c /mnt/ Note Example archive name: flarcreate -n CCPU-EMS -x /opt -S -c /mnt/secems04.archive Step 8 Back up the /opt directory. Enter tar -cvf - /opt/* |gzip -c >/opt/.tar.
Chapter 3 Monitoring and Backing Up the BTS Log Archive Facility (LAF) Step 1 Log in as root on the active CA. Step 2 Enter more /etc/resolv.conf. Note nameserver Step 3 Enter nslookup This defaults to the first DNS server. Step 4 Enter a valid gateway name and press Enter. An IP address associated to gateway appears. Step 5 Enter server Step 6 Enter a valid gateway name and press Enter. An IP address associated to gateway appears.
Chapter 3 Monitoring and Backing Up the BTS Log Archive Facility (LAF) Other Capabilities This section lists the additional capabilities of the LAF process. • It performs disk space management when 90% of the disk space quota specified for the target directory is reached. • It gracefully recovers from any abnormal conditions and re-initiates the process to continue the transfer of files. • It generates alarms when any unsuccessful scenarios are encountered.
Chapter 3 Monitoring and Backing Up the BTS Log Archive Facility (LAF) The steps to set up the authorization in external archive server and turn the LAF processes to active is listed below: Setup Non-Interactive SSH Login to External Archive Server Note The external archive system is recommended to be located such that it can be accessed by the management network.
Chapter 3 Monitoring and Backing Up the BTS Moving Core Files Adding Static Routes To add static routes to all Cisco BTS 10200 systems, perform the following steps: Step 1 From the shell or window of the primary call agent, change directory to /opt/utils. cd /opt/utils Step 2 Edit S96StaticRoutes using an editor.
Chapter 3 Monitoring and Backing Up the BTS Moving Core Files The BTS automatically removes these core files when disk space is critically low or the core file has aged beyond a maximum allowable time. However, to ensure proper BTS performance move these core files off the BTS to another storage area as soon as they are generated. Refer to the Directory Containing Core Files dataword for the location of the core file. Use the settings in the cfm.cfg file to configure how to monitor and manage core files.
CH A P T E R 4 Operating the BTS Revised: February 18, 2010, OL-16000-07 Introduction This chapter tells you how to operate the BTS. This chapter assumes the following are true: • Connecting components have been correctly installed. • Connecting components have been successfully started. • You are a system administrator with past BTS experience. Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
Chapter 4 Operating the BTS Managing Subscribers Managing Subscribers Table 4-1 Managing Subscribers Task Sample Command Activating added subscribers control subscriber-termination id=; target-state=INS; mode=FORCED; Deactivating subscribers Force the subscriber OOS: Ensure you specify mode=FORCED;; when assigning a DN to a ported-out subscriber.
Chapter 4 Operating the BTS Managing Subscribers Table 4-1 Managing Subscribers (continued) Task Sample Command Viewing subscribers voice mail indicator (VMI) status status subscriber ID=278-222-1917 Resetting subscribers voice mail waiting indicator (VMWI) control subscriber ID=278-222-1917; mwi=on Reporting all subscribers that use “best effort” (non DQoS) calls in the network having or not having a specific aggr id report subscriber id=%; oper-status=qos-best-effort; aggr-id=aggr1; start_row=1
Chapter 4 Operating the BTS Managing Subscribers Table 4-1 Managing Subscribers (continued) Task Sample Command Changing Delete the changed-number entry. subscribers delete changed-number old-DN=; announcements Change the status of the old DN to DISC in the dn2subscriber table. change dn2subscriber DN=; status=DISC; Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
Chapter 4 Operating the BTS Managing Subscribers Table 4-1 Managing Subscribers (continued) Task Sample Command Changing subscribers DNs Change the subscriber DN to the new DN. change sub id=; dn1=; CN-REFERRAL=Y; Example: change sub id=sub1; dn1=206-222-1841; CN-REFERRAL=Y; The CN-REFERRAL token adds an entry in the changed-number table for the changed subscriber DN. By default, the CN-REFERRAL token is set to Y.
Chapter 4 Operating the BTS Viewing Calls Viewing Calls These tasks allows you to view information related to call forwarding features. If A calls B and the call is forwarded to C: • Querying A shows A is connected to C and provide C's information. • Querying C shows C is connected to A and provide A's information. • Querying B shows A is calling C and the call is forwarded through B. • Even when the call is forwarded through B, B can originate another call. B can also forward multiple calls.
Chapter 4 Operating the BTS Using Status and Control Commands Using Status and Control Commands Table 4-3 Using Status and Control Commands Task Sample Command Viewing BTS system status system; status Viewing component states status element-manager id=EM01; Possible states: • STARTUP—During platform startup, the two sides are communicating to determine which side will come up active. – INIT-NORMAL—primary will be active, secondary will be standby; switchover allowed.
Chapter 4 Operating the BTS Using Status and Control Commands Table 4-3 Using Status and Control Commands (continued) Task Sample Command Changing states of component pairs (EMS, BDMS, CA, and FS) control call-agent id=CA146; target-state=FORCED-STANDBY-ACTIVE; Possible states: • ACTIVE_STANDBY • STANDBY_ACTIVE • NORMAL—Primary is active and secondary is standby. • FORCED-ACTIVE-STANDBY—Primary has been forced to active and secondary is standby.
Chapter 4 Operating the BTS Using Show and Change Commmands Using Show and Change Commmands Table 4-4 Using Show and Change Commands Task Sample Command Viewing subscriber-related batch data: subscribers, terminations, subscriber service profiles show subscriber limit=1000; start_row=;display=id,sub_service_profile; order=id; Viewing database usage statistics Where • limit—Page size for the maximum number of rows (or lines) to display • start_row—Which page to display first •
Chapter 4 Operating the BTS Using ERAC Commands These are standard commands and their parameters. Several are associated with BTS tables. However, several parameters are derived from multiple sources and do not map directly to a table. They may have real database representation but be modified for ease of use or readability. Tasks Descriptions Examples Viewing account IDs An account id can be assigned to one or more subscribers. An account id is used only for identification purposes.
Chapter 4 Operating the BTS Using ERAC Commands Tasks Descriptions Examples Viewing speed dial settings by DN This command returns a list of all speed dial show dn-sd-list dn=4692550529; sub-id=foo_123; telephone numbers by the specified DN or account-id=ABC123456789; primary subscriber directory number. All one digit speed dial values are returned as well as the feature state of speed dial. T Only a single row is returned with the complete list of speed dial numbers.
Chapter 4 Operating the BTS Managing Transactions Tasks Descriptions Examples Viewing list DNs that not in a hunt group show sub-dn-find This command returns a list of all DNs account-id=ABC1234%; associated with a specified subscriber and sub-id=foo-123; that are not associated with a hunt group. Under the present definition, the list can be long. Each row of the data indicates a TN with a free association.
Chapter 4 Operating the BTS Scheduling Commands Table 4-5 Viewing and Deleting Transactions (continued) Task Sample Command Enabling/Disabling queue throttling 1. Go to the bts.properties file. /opt/ems/etc/bts.properties 2. To enable throttling, set throttleEnable to Y. To disable throttling, set throttleEnable to N. throttleEnable=Y 3. Restart the platform.
Chapter 4 Operating the BTS Scheduling Commands Table 4-6 Scheduling Commands (continued) Task Sample Command Viewing scheduled commands show scheduled_command recurrence=HOURLY;key_values=720; Changing scheduled commands change scheduled_command id=3871788758088233209;recurrence=MINUTE;on_minute=19; Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
CH A P T E R 5 Managing External Resources Revised: February 18, 2010, OL-16000-07 Introduction This chapter tells you how to manage external resources provisioned on the BTS using administrative (ADM) commands.
Chapter 5 Managing External Resources Viewing BTS System-Wide Status Table 5-1 Using BTSSTAT Task Sample Command Viewing status of entire BTS btsstat system (including components not on the same host) Viewing status of specific components CA btsstat -caport FSAIN btsstat -fsainport FSPTC btsstat -fsptcport EMS btsstat -emsport BDMS btsstat -bdmsport Running BTSSTAT from a non-BTS host (requires an SSL connection to the BTS) btsstat -f my_cfg_file Specify BTS hosts in a configuration file: •
Chapter 5 Managing External Resources Managing Trunk Groups and Trunks Managing Trunk Groups and Trunks Table 5-2 Managing Trunk Groups Task Sample Command Viewing TG status status trunk-grp id=2; Possible operational states: • in-service • out of service • manually busy • operate in wait state, operate in standby state • restore session request normal, restore session request switchover, restore session request maintenance, restore session fail normal, restore session fail switch-over, res
Chapter 5 Managing External Resources Managing Trunk Groups and Trunks Table 5-2 Managing Trunk Groups (continued) Task Sample Command Resetting trunks reset trunk-termination tgn-id=13; cic=1-6; Resetting does the following: Changing trunk states • Clears all manual and blocked states • Clears active/transient calls on a trunk termination, with the exception of SS7 trunk terminations.
Chapter 5 Managing External Resources Managing Trunk Groups and Trunks Table 5-2 Managing Trunk Groups (continued) Task Sample Command Viewing test menus SS7 trunks diag ss7-trunk-termination test= diag ss7-trunk-termination test= ISDN trunks diag isdn-trunk-termination test= diag isdn-trunk-termination test= CAS trunks diag cas-trunk-termination test= diag cas-trunk-termination test= Announcement trunks diag annc-trunk-termination test= diag annc-trunk-
Chapter 5 Managing External Resources Managing Trunk Groups and Trunks Table 5-2 Managing Trunk Groups (continued) Task Sample Command Testing trunks SS7 trunks (place in MAINT state first) diag ss7-trunk-termination tgn-id=103; cic=13; test=1; Test 1: SS7 MGCP Connectivity Test—tests if MGCP has access to the SS7 trunk termination Test 2: SS7 Termination Connection Test—tests if there is a path to the device (ping). Test 3: SS7 COT Test—tests the integrity of the SS7 Bearer Path.
Chapter 5 Managing External Resources Managing Trunk Groups and Trunks Table 5-3 Valid Normal Trunk Termination States (continued) State/Token ADMIN-STATE OPER-STATE STATIC-STATE DYNAMIC-STATE IDLE INS IDLE ACTV IDLE ACTIVE INCOMING INS IDLE ACTV IDLE ACTIVE OUTGOING INS ACTIVE ACTV OBSY TRANSIENT INCOMING INS ACTIVE ACTV IBY-TRNS TRANSIENT OUTGOING INS BUSY ACTV OBSY-TRNS If a TG or trunk command fails, it can return one of the following generic failure reasons, as well as
Chapter 5 Managing External Resources Managing Trunk Groups and Trunks Table 5-4 Understanding Trunk Group and Trunk Generic Command Responses (continued) Command Entered Command Response any Failure Possible Conditions • Found no failure • TG(s) cannot be found, trunk(s) cannot be found, no TG(s) found in trunking gateway, no trunk(s) found in TG • Fail while in termination table, fail while in TG table, fail while in trunk table, fail while looking to find trunk index, fail while getting TG
Chapter 5 Managing External Resources Managing Trunk Groups and Trunks Table 5-4 Command Entered Understanding Trunk Group and Trunk Generic Command Responses (continued) Command Response Trunk Failure Termination commands Possible Conditions • The transaction could not be executed due to a transient error, the endpoint is unknown, the endpoint is not ready, endpoint does not have enough resources available, a protocol error was detected, the command contained an unrecognized extension, the endpoint
Chapter 5 Managing External Resources Managing Trunk Groups and Trunks Table 5-4 Understanding Trunk Group and Trunk Generic Command Responses (continued) Command Entered Command Response Trunk commands Failure Possible Conditions • 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.
Chapter 5 Managing External Resources Managing Trunk Groups and Trunks Table 5-4 Understanding Trunk Group and Trunk Generic Command Responses (continued) Command Entered Command Response SS7 trunk commands Failure Possible Conditions • 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.
Chapter 5 Managing External Resources Managing Subscriber Terminations Managing Subscriber Terminations Table 5-5 Managing Subscriber Terminations Task Sample Command Checking subscriber status status subscriber-termination id=ubr204_1; Possible states: • ADMIN-UEQP—Unequipped.
Chapter 5 Managing External Resources Managing Subscriber Terminations Table 5-5 Managing Subscriber Terminations (continued) Task Sample Command Changing subscriber termination states control subscriber-termination id=*@c3810_167; mode=forced; target-state=INS; Possible states: • INS—In-service • OOS—Out of service • MNT—Maintenance mode control subscriber-termination id=sub2-ctx2; mode=forced; target-state=maint; Forces MAINT state, do this before testing equip subscriber-termination id=97_
Chapter 5 Managing External Resources Managing Subscriber Terminations Table 5-6 Understanding Subscriber Command Responses Command Entered Command Response status Failure or Possible Conditions • Subscriber database was not found in shared memory. • Component is already in the requested state. • Graceful mode only, this appears when a command is executed and operation is INS going OSS or INS going MAINT. • A required resource is not available.
Chapter 5 Managing External Resources Managing Subscriber Terminations Table 5-6 Understanding Subscriber Command Responses (continued) Command Entered Command Response Any failure Subscriber commands Failure Possible Conditions • Found no failure, subscriber category invalid, entity unequipped in initial state, unknown failure reason(s). • Subscriber(s) cannot be found, subscriber(s) state change and pending. • No termination(s) found in MGW. • Fail while in termination table.
Chapter 5 Managing External Resources Managing Gateways Managing Gateways Table 5-7 Managing Gateways Task Sample Command Viewing H.323 gateways status h323-gw id=CHINA-1; Possible RAS states: • CCH323_RAS_STATE_NONE—operational state is ADMIN OOS • CCH323_RAS_STATE_GRQ—Gatekeeper Discovery state • CCH323_RAS_STATE_RRQ—Gateway Registration state • CCH323_RAS_STATE_IDLE—ready for calls • CCH323_RAS_STATE_URQ—Un-registration state. Setting the state of H.
Chapter 5 Managing External Resources Managing Gateways Table 5-7 Managing Gateways (continued) Task Sample Command Changing media gateways status control mgw id=c5300_162; mode=forced; target-state=INS; Modes can be forced or graceful. Forced tears down all calls immediately; graceful allows calls in progress to complete before teardown. Note Rules for changing an MGW states are in Figure 5-1. control mgw id=c2421.
Chapter 5 Managing External Resources Managing Other External Resources Table 5-8 Understanding Gateway Command Responses Command Entered Command Response status Failure Possible Conditions • Media gateway database was not found in shared memory. or • Component is already in the requested state. control • 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.
Chapter 5 Managing External Resources Managing Other External Resources Table 5-9 Managing External Resources (continued) Task Sample Command Shows all CMTS (Aggr-ID) that are not referred by any Subnet.
Chapter 5 Managing External Resources Learning External Resource Dependencies Table 5-9 Managing External Resources (continued) Task Sample Command Ensuring billing server receives Call Detail Blocks (CDBs) 1. On both the primary and secondary EMS enter: CLI>show billing-acct-addr 2. Note the polling interval. 3. Log in to the billing server. 4. Ensure it receives billing files every XX minutes from the BTS, where XX = polling interval. Clearing billing directory Caution 1.
Chapter 5 Managing External Resources Learning External Resource Dependencies Table 5-10 RGW and Subscriber Termination States (continued) RGW State Allowed Subscriber Termination States INS MAINT Table 5-11 • OOS • MAINT • INS • UEQP • OOS • MAINT • UEQP ISDN TGW/TG State Relationships TGW State Allowed TG States INS MAINT • OOS • MAINT • INS • OOS • MAINT This table lists the administrative states BTS returns.
Chapter 5 Managing External Resources Learning External Resource Dependencies Table 5-13 ISDN TGW/TG State Relationships TGW State Allowed TG States INS MAINT Table 5-14 Allowed Trunk States • OOS • UEQP OOS • MAINT • UEQP OSS, MAINT • INS • UEQP OOS, MAINT, INS • OOS • UEQP OOS • MAINT • UEQP OSS, MAINT 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 MA
Chapter 5 Managing External Resources Learning External Resource Dependencies Table 5-15 Returnable Operational States (continued) State UNREACHABLE FAULTY Definition • The termination is unreachable. • This occurs when MGW KEEPALIVE declares an MGW unreachable. • This changes to ACTIVE when MGW KEEPALIVE detects an MGW is reachable or any termination previously UNREACHABLE starts sending MGCP messages (NTFY, RSIP).
Chapter 5 Managing External Resources Learning External Resource Dependencies Source Token Figure 5-1 Administrative and Operational Maintenance States for MGW P_OOS = Place out of service P_INS = Place in service P_MNT = Place maintenance NP = Not provisioned MGW = NP Add (MGW) Del (MGW) P_MNT (MGW) P_INS (MGW) MGW = OOS DISCOVER MGW, * MGW = MNT DISCOVER MGW, * MGW = INS MGW = OOS All T = OOS P_OOS (MGW) P_OOS (MGW) MGW = MNT MGW = INS MGW = INS MGW = MNT All (T = INS) = MNT 52077 P_IN
Chapter 5 Managing External Resources Learning External Resource Dependencies Administrative and Operational Maintenance States for Residential Gateways If SL = NE SL = UEQP P_INS (SL) Add (SL)* If SL = UEQP Del (SL) Del (SL)* RGW = OOS SL = NP/UEQP P_OOS (SL) Warning Warning Warning If SL = NE SL = UEQP P_INS (SL) If SL = INS warn else { {if SL = OOS discover SL*2} init SL*3, SL = INS} If SL = NE SL = UEQP P_INS (SL) P_OOS = Place out of service P_INS = Place in service P_MNT = Place maint
Chapter 5 Managing External Resources Learning External Resource Dependencies Figure 5-3 ISDN Administrative and Operational Maintenance States for a Trunking Gateway Add (TGP) TGP = OOS Add (TRK, TGP) TGW = OOS TGP = NP/OOS TRK = NP/OOS if TGP = OOS add (TRK) TRK = OOS if (TRK, TGP) = OOS del (TRK, TGP) if TGP = OOS del (TGP) Del(TGP) if TGP=OOS/INS TGP=MNT all TRK=MNT bearer=MNT signaling=MNT Del (TRK, TGP) P_OOS = Place out of service P_INS = Place in service P_MNT = Place maintenance NP =
Chapter 5 Managing External Resources Learning External Resource Dependencies Add (TGP) TGP = OOS Add (TRK, TGP) TGW = OOS TGP = NP/OOS TRK = NP/OOS if TGP = OOS add (TRK) TRK = OOS if (TRK, TGP) = OOS del (TRK, TGP) if TGP = OOS del (TGP) Del(TGP) if TGP=OOS/INS TGP=MNT all TRK=MNT bearer=MNT signaling=MNT Del (TRK, TGP) P_OOS = Place out of service P_INS = Place in service P_MNT = Place maintenance NP = Not provisioned Add (TGP) TGP=OOS P_MNT (TGP) if TGP=MNT if (TRK, TGP)=OOS (TRK, TGP)=M
Chapter 5 Managing External Resources GigE Support GigE Support The purpose of implementing the GigE Support Feature provisioning is to increase the bandwidth between the network switches and the Cisco BTS 10200 from 100 Mbps to 1000 Mbps. This section describes the steps needed to enable GigE support on the UNIX hosts of the Cisco BTS 10200 Softswitch. Use this procedure only after you upgrade to Cisco BTS 10200 Release 6.0(1) or later. Caution This is not an upgrade procedure.
Chapter 5 Managing External Resources Provisioning the GigE Interface shut no shut Step 5 Save the switch configuration. Step 6 Reboot the Cisco BTS 10200 host using the shutdown -g0 -y -i6 command. We recommend that you execute the shutdown command using the console port to avoid loss of connectivity during the reboot. After the reboot, all the targeted Cisco BTS 10200 applications should automatically restart and go into standby state.
Chapter 5 Managing External Resources Provisioning the GigE Interface Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
CH A P T E R 6 Using BTS Measurements Revised: February 18, 2010, OL-16000-07 Introduction This chapter describes BTS traffic measurements and tells you how to use them. BTS does the following: • Collects statistics in 5-, 15-, 30-, or 60-minute intervals. • Collects TG statistics at 100 second intervals. • Clears measurements 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.
Chapter 6 Using BTS Measurements Learning the Measurement Types SIP_TOTAL_INCOMING_MSG and SIP_TOTAL_SUCCESS_INCOMING_MSG Table 6-1 Using Measurements Task Sample Command Viewing measurement types show measurement-prov type=; Enabling measurements change measurement-prov type=; enable=; time-interval=
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-2 ISDN Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) ISDN_CALL_PROCEED_RX ISDN CALL PROCEED messages received. ISDN_CALL_PROCEED_TX ISDN CALL PROCEED messages sent from the reporting CA. ISDN_CONG_CNTL_TX ISDN Congestion Control messages sent from the reporting CA, this only applies to ETSI PRI. ISDN_CONNECT_ACK_RX ISDN CONNECT ACK messages received.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-2 ISDN Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) ISDN_SETUP_ACK_RX ISDN SETUP ACK messages received. ISDN_SETUP_ACK_TX ISDN SETUP ACK messages sent from the reporting CA. ISDN_SETUP_RX ISDN SETUP messages received. ISDN_SETUP_TX ISDN SETUP messages sent from the reporting CA. ISDN_SRVC_ACK_RX ISDN SERVICE ACK messages received.
Chapter 6 Using BTS Measurements Learning the Measurement Types Call Processing Measurements Table 6-3 Call Processing Measurements Measurement Description (* = rapid count could mean a potential problem in the system) CALLP_ NCT_TEST_FAIL Unsuccessful Network Continuity Tests completed, both call setup failures and resource failures. These are test calls abnormally released by the CA due to resource priorities. CALLP_ NLB_TEST_FAIL Unsuccessful Network Loop Back Tests completed.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-3 Call Processing Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) CALLP_H323_TERM_ATTMP Terminating H323 call attempts. CALLP_H323_TERM_FAIL Terminating H323 call attempts that failed. CALLP_INTERLA_ABAND Interlata call origination attempts abandoned. CALLP_INTERLA_ATTMP Interlata call attempts. CALLP_INTERLA_FAIL Interlata call attempts that failed.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-3 Call Processing Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) CALLP_LNP_SND_MISROUTED_ PORTED Misrouted calls to a ported number detected after an LNP query. CALLP_LNP_SND_MISROUTED_ PORTED Misrouted calls to a ported number detected after an LNP query in the reporting CA.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-3 Call Processing Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) CALLP_MGCP_SS7_CALL Successfully completed calls from an MGCP originator to an SS7 terminator. CALLP_MGCP_TERM_ATTMP MGCP terminating call attempts. CALLP_MGCP_TERM_FAIL MGCP terminating call attempts that failed. CALLP_MODEM_MEDIA_SETUP_ Failed Modem calls.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-3 Call Processing Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) CALLP_OHD_DIALTONE_TIMEO UT Times the off hook delay trigger timed out. CALLP_OLM _ ACCEPT Calls accepted by OLM. CALLP_OLM _ ACCEPT_MCL0 Calls accepted by OLM at MCL0. CALLP_OLM _ ACCEPT_MCL1 Calls accepted by OLM at MCL1. CALLP_OLM _ ACCEPT_MCL2 Calls accepted by OLM at MCL2.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-3 Call Processing Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) CALLP_SIP_ORIG_CALL_NOT_A NS This counter is pegged when the incoming call is not answered by the called party. CALLP_SIP_ORIG_END_USR_BU SY This counter is pegged when the incoming call is not complete due to the called party being busy.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-3 Call Processing Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) CALLP_SS7_TERM_ATTMP SS7 terminating call attempts. CALLP_SS7_TERM_FAIL SS7 terminating call attempts that failed. CALLP_T38_FAX_MEDIA_SETUP _FAIL Unsuccessful T.38 media connections between the endpoints for T.38 fax transmission. CALLP_T38_FAX_MEDIA_SETUP _SUCC Successful T.
Chapter 6 Using BTS Measurements Learning the Measurement Types MGCP Adapter Measurements Table 6-4 MGCP Adapter Measurements Measurement Description (* = rapid count could mean a potential problem in the system) MGCP_AUCX_ACK_RX AUCX ACK (Audit Connection Acknowledgement) messages received. Note MGCP_AUCX_NACK_RX AUCX NACK (Audit Connection NotAcknowlegement) messages received. Note MGCP_AUCX_TX This is enabled in a future release. This is enabled in a future release.
Chapter 6 Using BTS Measurements Learning the Measurement Types DQoS Measurements Table 6-5 DQoS Measurements Measurement Description (* = rapid count could mean a potential problem in the system) DQOS_GATE_CLOSE_RX DQOS Gate-Open messages received by the reporting BTS. DQOS_GATE_DELETE _ACK_RX DQOS Gate-Delete-Ack messages received by the reporting BTS. DQOS_GATE_DELETE _TX DQOS Gate-Delete messages sent from the reporting BTS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-6 Session Initiation Protocol (SIP) Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SIS_7xx_RX 7xx class (RESERVED) messages the reporting CA or FS received. SIS_7xx_TX 7xx class (RESERVED) messages the reporting CA or FS sent. SIS_ACK_RX SIP ACK messages the reporting CA or FS received. SIS_ACK_TX SIP ACK messages the reporting CA or FS sent.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-6 Session Initiation Protocol (SIP) Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SIS_SUBSCRIBE_TX SIP SUBSCRIBE messages the reporting CA or FS sent. SIS_T1_TIMER_EXPIRED SIP T1 Timer expirations that occurred on the reporting CA or FS received over the collection interval.
Chapter 6 Using BTS Measurements Learning the Measurement Types Service Interaction Manager Measurements Table 6-7 Service Interaction Manager Measurements Measurement Description (* = rapid count could mean a potential problem in the system) SIM_AUDIT_CCB_FREED SIM relationships terminated with SSF due to the SIM memory audit. SIM_AUDIT_SIP_CCB_FREED SIM to SIP relationships released with the FS do to the SIM memory audit.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-8 Local POTS Local Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) POTS_CCW_LENGTH Subscriber-seconds that Cancel Call WAITING was active on the reporting FS. POTS_CCW_REJECT_BY_CCW Cancel Call Waiting attempts rejected due to Call Waiting not already being active on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-8 Local POTS Local Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) POTS_CFU_ACT_ANSWERED Call Forward Unconditional activation attempts answered by the called party on the reporting FS. POTS_CFU_ACT_ATTMP Call Forward Unconditional activation attempts on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-8 Local POTS Local Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) POTS_CW_ATTMP Call Waiting service instance attempts on the reporting FS. POTS_CW_NOT_ANSWERED Call Waiting service instance attempts not answered by the called party on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-8 Local POTS Local Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) POTS_EXT_CNAM_QUERY CNAM translation queries that resulted in an external query to a network database attempted on the reporting FS. POTS_EXT_CNAM_QUERY_SUCC CNAM translation queries that resulted in a successful external query to a network database attempted on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-8 Local POTS Local Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) POTS_RACF_PIN_REJECT_NO_RSRC Remote Activation Call Forward PIN input attempts refused due to a lack of resources on the reporting FS. POTS_RACF_PIN_UNCHANGE Remote Activation Call Forward PIN input attempts that resulted in no change to the previous PIN for that subscriber on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types POTS Application Server Measurements Table 6-9 POTS Application Server Measurements Measurement Description (* = rapid count could mean a potential problem in the system) POTS_AS_ORIG_ABANDON Times a origination to the Application Server was abandoned while trying to connect. POTS_AS_ORIG_ATTMP attempts to place a call to an Application Server on the originating side.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-10 Miscellaneous POTS Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) POTS_HOTV_ATTMP Successful Hotline Variable instance attempts on the reporting FS. POTS_HOTV_DEACT_SUCC Successful Hotline Variable deactivation attempts on the reporting FS. POTS_HOTV_INTERROG_SUCC Successful Hotline Variable interrogation attempts on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types POTS Class of Service FS Measurements Table 6-11 POTS Class of Service Measurements Measurement Description (* = rapid count could mean a potential problem in the system) POTS_COS_900_BLOCKED Calls denied due to subscriber based 900 restrictions on the reporting FS. POTS_COS_976_BLOCKED Calls denied due to subscriber based 976 restrictions on the reporting FS. POTS_COS_ACCT_CODE_FAIL Not currently used.
Chapter 6 Using BTS Measurements Learning the Measurement Types POTS Screen List Editing FS Measurements Table 6-12 POTS Screen List Editing Measurements Measurement Description (* = rapid count could mean a potential problem in the system) POTS_SCA_ATTMP Selective Call Acceptance service instance attempts on the reporting FS. POTS_SCA_REJECT_NO_RSRC Selective Call Acceptance attempts made by subscribers rejected due to a lack of available resources on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types POTS Automatic Callback, Recall, and Call Return Measurements Table 6-14 POTS Automatic Callback, Recall, and Call Return Measurements Measurement Description (* = rapid count could mean a potential problem in the system) POTS_AC_ACT_ATTMP Automatic Callback service activation attempts on the reporting FS. POTS_AC_DEACT_ATTMP Automatic Callback service activation attempts deactivated by the requesting subscriber on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-14 POTS Automatic Callback, Recall, and Call Return Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) POTS_AR_DELAYED_PROC Automatic Recall service activation attempts that resulted in delayed connection on the reporting FS. POTS_AR_IMMEDIATE_PROC Automatic Recall service activation attempts that resulted in immediate connection on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types POTS Limited Call Duration (Prepaid/Postpaid) with RADIUS Interface to AAA Measurements Table 6-15 POTS Limited Call Duration (Prepaid/Postpaid) with RADIUS Interface to AAA Description (* = rapid count could mean a potential problem in the system) Measurement POTS_LCD_AUTH_ATTMP authorization attempts made for Limited Call Duration feature invocations on the reporting FS. Note For three-leg calls, each call is authorized separately.
Chapter 6 Using BTS Measurements Learning the Measurement Types AIN Services FS Measurements Table 6-17 AIN Services Measurements Measurement Description (* = rapid count could mean a potential problem in the system) AINSCV_LOC_LNP_FAIL_APP Failures in querying the local LNP database. AINSCV_LOC_LNP_QUERY DN look ups in local LNP database. AINSCV_LOC_LNP_QUERY_RN_ FOUND Successful queries to the local LNP database that returned an RN corresponding to the DN.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-17 AIN Services Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) AINSVC_LOC_8XX_ANI_BLOCK 8XX translation queries blocked due to ANI screening processed locally on the reporting FS. AINSVC_LOC_8XX_DNIS_SUCC 8XX DNIS translation queries successfully processed locally on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types SCCP Protocol Measurements Table 6-18 SCCP Measurements Measurement Description (* = rapid count could mean a potential problem in the system) SCCP_ NSAP_OOS_GRANT_TX Subsystem out-of-service grant messages sent on the reporting FS. SCCP_ NSAP_OOS_REQ_TX Subsystem out-of-service request messages sent on the reporting FS. SCCP_ NSAP_PROHIBIT_TX Subsystem prohibited messages sent on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-18 SCCP Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SCCP_TOTAL_LOCAL_MSG Messages intended for local subsystems on the reporting FS. SCCP_TOTAL_LONG_UDATA_RX Long unit data received on the reporting FS. SCCP_TOTAL_LONG_UDATA_SVC_RX Long unit data service received on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types TCAP Protocol Measurements Table 6-19 TCAP Measurements Measurement Description (* = rapid count could mean a potential problem in the system) TCAP_ INCORRECT_COMP_ ENCODE_TX Incorrect component encoding errors sent by the reporting FS. TCAP_ INVOKE_RSCR_LIMIT_ PROB_TX Resource limitation invoke problems sent by the reporting FS. TCAP_ TRANS_PORT_PERM_REL_TX Transaction portion permission to release problems sent by the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-19 TCAP Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) TCAP_DIALOG_CONFIRM_RX Dialog confirm messages received on the reporting FS. TCAP_DUP_INVOKE_ID_RX Duplicate invoke ids received on the reporting FS. TCAP_DUP_INVOKE_ID_TX Duplicate invoke ids sent by the reporting FS. TCAP_END_MSG_RX End messages received on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-19 TCAP Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) TCAP_OPEN_CONFIRM_RX Open confirm messages received on the reporting FS. TCAP_OPEN_IND_RX Open indication messages received on the reporting FS. TCAP_OPERATION_CONFIRM_RX Operation confirm messages received on the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-19 TCAP Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) TCAP_UNEXPECT_ERR_CODE_ TX Unexpected error codes on return-error sent by the reporting FS. TCAP_UNEXPECT_LINK_ OPER_RX Unexpected link operations received on the reporting FS. TCAP_UNEXPECT_LINK_OPER_TX Unexpected link operations sent by the reporting FS.
Chapter 6 Using BTS Measurements Learning the Measurement Types SUA Measurements Table 6-20 SUA Measurements Measurement Description (* = rapid count could mean a potential problem in the system) SUA_ACTIVE_ACK_RX ACTIVE Acknowledges received on the reporting signaling gateway process. SUA_ACTIVE_TX ACTIVEs sent on the reporting signaling gateway process. SUA_ASSOC_FAIL Association failures on the reporting signaling gateway process.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-20 SUA Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SUA_PROTOCOL_ERR Protocol errors on the reporting signaling gateway process. SUA_ROUTING_CONTEXT_ERR Routing context errors on the reporting signaling gateway process. SUA_SCON_RX SCONs received on the reporting signaling gateway process. SUA_SCON_TX SCONs sent on the reporting signaling gateway process.
Chapter 6 Using BTS Measurements Learning the Measurement Types M3UA Protocol Measurements Table 6-21 M3UA Measurements Measurement Description (* = rapid count could mean a potential problem in the system) M3UA_ACTIVE_ACK_RX ACTIVE Acknowledges received on the reporting signaling gateway process. M3UA_ACTIVE_TX ACTIVEs sent on the reporting signaling gateway process. M3UA_ASSOC_FAIL Association failures on the reporting signaling gateway process.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-21 M3UA Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) M3UA_ROUTING_CONTEXT_ERR Routing context errors on the reporting signaling gateway process. M3UA_SCON_RX SCONs received on the reporting signaling gateway process. M3UA_SCON_TX SCONs sent on the reporting signaling gateway process.
Chapter 6 Using BTS Measurements Learning the Measurement Types SCTP Measurements Table 6-22 SCTP Measurements Measurement Description (* = rapid count could mean a potential problem in the system) SCTP_ASSOC_COMM_LOST Times the SCTP association communication was lost on the reporting sctp association. SCTP_CHUCK_TOO_LARGE_ERR Data chunks received too big on the reporting sctp association. SCTP_CHUNK_ORDER_ERR Ordered chunks in error on the reporting sctp association.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-22 SCTP Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SCTP_INVALID_PARAM_ERR_RX Times an SCTP peer reported that it received an INIT or INIT ACK chunk containing one or more mandatory parameters set to an invalid value on the reporting sctp association. SCTP_INVALID_STREAM Datagrams with invalid stream ids received on the reporting sctp association.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-22 SCTP Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SCTP_UNRECOG_CHUNK_ERR_RX Times an SCTP peer reported that it received a chunk that it could not understand on the reporting sctp association. SCTP_UNRECOG_PARAM_ERR_RX Times an SCTP peer reported that it received an INIT ACK containing one or more parameters unrecognized on the reporting sctp association.
Chapter 6 Using BTS Measurements Learning the Measurement Types IUA Measurements Table 6-23 IUA Measurements Measurement Description IUA_ACTIVE_ACK_RX ASP_ACTIVE_ACK messages received on the reporting SCTP association. IUA_ACTIVE_TX ASP_ACTIVE messages transmitted on the reporting SCTP association. IUA_ASSOC_FAIL SCTP association establishment failures on the reporting SCTP association. IUA_BEAT_ACK_RX HEARTBEAT ACK messages received on the reporting SCTP association.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-23 IUA Measurements (continued) Measurement Description IUA_MSG_OTHER_ERR Other message errors on the reporting SCTP association. IUA_MSG_TYPE_ERR Unsupported message type errors on the reporting SCTP association. IUA_NO_MEMORY_ERR No memory for message errors on the reporting SCTP association. IUA_NOTIFY_RX NOTIFY messages received on the reporting SCTP association.
Chapter 6 Using BTS Measurements Learning the Measurement Types ISUP MeasurementsI Table 6-24 ISUP Protocol Measurements ISUP_ABNORMAL_REL_RX Release messages received with a cause other than NORMAL on the reporting trunk group. ISUP_ABNORMAL_REL_TX Release messages sent with a cause other than NORMAL on the reporting trunk group. ISUP_ACM_RX Address Complete messages received on the reporting trunk group. ISUP_ACM_TX Address Complete messages sent on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-24 ISUP Protocol Measurements (continued) ISUP_COT_TX Continuity messages sent on the reporting trunk group. ISUP_CPG_RX Call Progress messages received on the reporting trunk group. ISUP_CPG_TX Call Progress messages sent on the reporting trunk group. ISUP_CQM_RX Circuit Query messages received on the reporting trunk group. ISUP_CQM_TX Circuit Query messages sent on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-24 ISUP Protocol Measurements (continued) ISUP_IAM_RX Initial Address messages received on the reporting trunk group. ISUP_IAM_TX Initial Address messages sent on the reporting trunk group. ISUP_IDR_RX ID Request messages received on the reporting trunk group. ISUP_IDR_TX ID Request messages sent on the reporting trunk group. ISUP_INF_RX Information messages received on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-24 ISUP Protocol Measurements (continued) ISUP_RSC_TX Reset Circuit messages sent on the reporting trunk group. ISUP_SAM_RX Subsequent Address messages received on the reporting trunk group. ISUP_SAM_TX Subsequent Address messages sent on the reporting trunk group. ISUP_SGM_RX Segmentation messages received on the reporting trunk group. ISUP_SGM_TX Segmentation messages sent on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-25 CGUA Message Measurements Applicable to ISUP Variants (continued) X CON X X X X X X X X X X X X X X X X X X X X X X COT X X X X X X X X X X X X CPG X X X X X X X X X X X X CQM X X X CQR X X X CRA X CRM X X X X X X X X CRG X CVR X CVT X EXM X FAA FAC X X FAR FOT X X FRJ X FWT X GRA X X X X X X X X X X X X GRS X X X X X X X X
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-25 Message Measurements Applicable to ISUP Variants (continued) UBL X UCIC X X X X UPA X X X UPT X X X X X X USR X X X X X X X X X X X X Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
Chapter 6 Using BTS Measurements Learning the Measurement Types ISUP (ANSI) Measurements Table 6-26 ISUP (ANSI) Measurements Measurement Description (* = rapid count could mean a potential problem in the system) SGA_ABNORMAL_REL_RX RELs received with a cause other than NORMAL on the reporting trunk group. SGA_ACM_RX ACM messages received on the reporting trunk group. SGA_ACM_TX ACM messages sent on the reporting trunk group. SGA_ANM_RX ANM messages received on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-26 ISUP (ANSI) Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SGA_CVR_TX CVR messages sent on the reporting trunk group. SGA_CVT_RX CVT messages received on the reporting trunk group. SGA_CVT_TX CVT messages sent on the reporting trunk group. SGA_EXM_RX EXM messages received on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-26 ISUP (ANSI) Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SGA_UBA_RX UBA messages received on the reporting trunk group. SGA_UBA_TX UBA messages sent on the reporting trunk group. SGA_UBL_RX UBL messages received on the reporting trunk group. SGA_UBL_TX UBL messages sent on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types ISUP (France) Measurements Table 6-27 ISUP (France) Measurements Measurement Description (* = rapid count could mean a potential problem in the system) SGA_ITX_RX Charge Unit (ITX) message received on the reporting trunk group. SGA_ITX_TX ITX messages sent on the reporting trunk group. SGA_TXA_RX Charging Acknowledgement (TXA) messages received on the reporting trunk group. SGA_TXA_TX TXA messages sent on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-29 ISUP (ITU-China) Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SGA_CGBA_RX CGBA messages received on the reporting trunk group. SGA_CGBA_TX CGBA messages sent on the reporting trunk group. SGA_CGU_RX CGU messages received on the reporting trunk group. SGA_CGU_TX CGU messages sent on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-29 ISUP (ITU-China) Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SGA_SUS_TX SUS messages sent on the reporting trunk group. SGA_UBA_RX UBA messages received on the reporting trunk group. SGA_UBA_TX UBA messages sent on the reporting trunk group. SGA_UBL_RX UBL messages received on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types ISUP (ITU-Mexico) Measurements Table 6-30 ISUP (ITU-Mexico) Measurements Measurement Description (* = rapid count could mean a potential problem in the system) SGA_ABNORMAL_REL_RX RELs received with a cause other than NORMAL on the reporting trunk group. SGA_ABNORMAL_REL_TX RELs sent with a cause other than NORMAL on the reporting trunk group. SGA_ACM_RX ACM messages received on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-30 ISUP (ITU-Mexico) Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SGA_GRA_RX GRA messages received on the reporting trunk group. SGA_GRA_TX GRA messages sent on the reporting trunk group. SGA_GRS_RX GRS messages received on the reporting trunk group. SGA_GRS_TX GRS messages sent on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types ISUP (ITU-HongKong) Measurements Table 6-31 ISUP (ITU-HongKong) Measurements Measurement Description (* = rapid count could mean a potential problem in the system) SGA_ABNORMAL_REL_RX RELs received with a cause other than NORMAL on the reporting trunk group. SGA_ABNORMAL_REL_TX RELs sent with a cause other than NORMAL on the reporting trunk group. SGA_ACM_RX ACM messages received on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-31 ISUP (ITU-HongKong) Measurements Measurement Description (* = rapid count could mean a potential problem in the system) SGA_INF_RX INF messages received on the reporting trunk group. SGA_INF_TX INF messages sent on the reporting trunk group. SGA_INR_RX INR messages received on the reporting trunk group. SGA_INR_TX INR messages sent on the reporting trunk group. SGA_MSG_RX Messages received on the reporting trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Audit Measurements Table 6-32 Audit Measurements Description (* = rapid count could mean a potential problem in the system) Measurement AUDIT_FS_TOTAL_CA_SWITCHOVER Audits to check all active CCBs in response to a CA platform switchover occurring. This is only applicable when the standby CA becomes active.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-33 SIP Interface Adapter Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) SIA_MWI_NOTIFY_RX SIP Notify MWIs received from SIP subscribers. SIA_MWI_NOTIFY_TX SIP Notify MWIs sent to SIP phones. SIA_MWI_NOTIFY_TX_FAIL SIP Notify MWIs that failed to be sent to SIP phones. SIA_OC_INVITE_REJECT Incoming INVITE messages rejected due to an overload.
Chapter 6 Using BTS Measurements Learning the Measurement Types Call Detail Block Measurements Table 6-34 Call Detail Block Measurements Measurement Description (* = rapid count could mean a potential problem in the system) BILLING_TOTAL_500 CDBs of type 500 created by the reporting EMS. BILLING_TOTAL_700 CDBs of type 700 created by the reporting EMS. BILLING_TOTAL_900 CDBs of type 900 created by the reporting EMS. BILLING_TOTAL_976 CDBs of type 976 created by the reporting EMS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-34 Call Detail Block Measurements (continued) Measurement Description (* = rapid count could mean a potential problem in the system) BILLING_TOTAL_OP CDBs of type cut operator created by the reporting EMS BILLING_TOTAL_OP_ASSIST CDBs of type operator assisted created by the reporting EMS BILLING_TOTAL_PCS CDBs of type pcs created by the reporting EMS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Event Messaging Measurements Table 6-35 Event Messaging Measurements Measurement Description (*=rapid count could mean a potential problem in the system) BILLING_EM_ACKED Event messages acknowledged by the Record Keeping System. BILLING_EM_LOGGED Event messages written to disk but not sent to any RKS.
Chapter 6 Using BTS Measurements Learning the Measurement Types PCMM Measurements Table 6-37 PCMM Measurements Measurement Description (*=rapid count could mean a potential problem in the system) PCMM_GATE_INFO_TX PCMM Gate-Info messages sent from the reporting BTS. PCMM_GATE_INFO_ACK_ RX PCMM Gate-Info-Ack messages received by the reporting BTS. PCMM_GATE_INFO_ERR_ RX PCMM Gate-Info-Err messages received by the reporting BTS.
Chapter 6 Using BTS Measurements Learning the Measurement Types Trunk Group Usage Measurements Table 6-39 Trunk Group Usage Measurements Measurement Description (*=rapid count could mean a potential problem in the system) TRKGRP_401S_SENT TRKGRP_AVERAGE_USAGE The percent of the trunk group used, between 0-100. This is not incremented for SIP or H323 trunk groups.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-39 Trunk Group Usage Measurements (continued) Measurement TRKGRP_OUTBOUND_FAIL Description (*=rapid count could mean a potential problem in the system) 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.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-39 Trunk Group Usage Measurements (continued) Measurement Description (*=rapid count could mean a potential problem in the system) TRKGRP_SIP_4xx_TX Number of 4xx class (REQUEST FAILURES) messages the reporting call agent transmitted on a SIP trunk group. TRKGRP_SIP_5xx_RX Number of 5xx class (SERVER FAILURES) messages the reporting call agent received on a SIP trunk group.
Chapter 6 Using BTS Measurements Learning the Measurement Types Announcement Measurements Table 6-40 Announcement Measurements Measurement Description (*=rapid count could mean a potential problem in the system) ANM_SEASONAL_SUSPEND calls that cause the CA to play the seasonal suspend announcement.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-41 H.323 Protocol Measurements (continued) Measurement Description (*=rapid count could mean a potential problem in the system) H323_ALERT_TX H323 ALERTs transmitted H323_ALERT_FAIL 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.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-41 H.323 Protocol Measurements (continued) Measurement Description (*=rapid count could mean a potential problem in the system) H323_NOTIFY_TX H323 NOTIFYs transmitted H323_NOTIFY_FAIL 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.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-41 H.
Chapter 6 Using BTS Measurements Learning the Measurement Types Call Tools Measurements Table 6-42 Call Tools Measurements Description (*=rapid count could mean a potential problem in the system) Measurement TOOLS_TRUNK_TRANS_ATTMP Times the TVT process on the reporting CA received a request to perform a trunk based translation. TOOLS_TRUNK_TRANS_SUCC Times the TVT process on the reporting CA received a request to perform a trunk based translation and completed it successfully.
Chapter 6 Using BTS Measurements Learning the Measurement Types CPU Usage Measurements Table 6-45 CPU Usage Measurements Measurement Description (*=rapid count could mean a potential problem in the system) CPU_USAGE_CPU_ID The id of CPU. CPU_USAGE_IDLE The percent of CPU in idle in the last sample interval (100 sec CCS based). CPU_USAGE_USER The percent of CPU in idle in the last sample interval (100 sec CCS based).
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-48 Disk Usage Measurements Measurement Description (*=rapid count could mean a potential problem in the system) DISK_USAGE_TOTAL_AVAILABLE blocks on file system. DISK_USAGE_TOTAL_USED used blocks. Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
Chapter 6 Using BTS Measurements Learning the Measurement Types System Load Usage Measurements Table 6-49 System Load Usage Measurements Description (*=rapid count could mean a potential problem in the system) Measurement SYSTEM_LOAD_AVERAGE_1MIN Decaying averages over the last 1 minute of the sum of user + system times +runqueue wait times. The decaying averages are updated once per second.
Chapter 6 Using BTS Measurements Learning the Measurement Types Description (*=rapid count could mean a potential problem in the system) Measurement ENUM_QUERY_NO_VALID_URI The number of ENUM queries for which the reporting call agent received only malformed URIs. ENUM_QUERY_NO_URI The number of ENUM queries for which the reporting call agent did not receive any URIs. ENUM_QUERY_NO_SERVER The number of ENUM queries for which the reporting call agent did not find any server.
Chapter 6 Using BTS Measurements Learning the Measurement Types Table 6-51 Diameter Message Measurement Counters Measurement Description (*=rapid count could mean a potential problem in the system) DI_SUBSCRIBER_NOTIFICATION_ANS Diameter Subscriber-Notification-Answer DI_PROFILE_NOTIFICATION_REQ Diameter Profile-Notification-Request DI_PROFILE_NOTIFICATION_ANS Diameter Profile-Notification-Answer DI_SH_ERROR_MSG Diameter Sh Interface error message Single Number Reach Counters Table 6-52 lists
CH A P T E R 7 Using the BTS SNMP Agent Revised: February 18, 2010, OL-16000-07 Introduction This chapter explains how to use the Simple Network Management Protocol (SNMP) agent. The BTS uses a SNMP agent to communicate with a service provider’s network management system (NMS). Working together, the SNMP agent and NMS monitor and control BTS components on the managed network. The NMS does most of the processing and provides the majority of memory resources.
Chapter 7 Using the BTS SNMP Agent Viewing SNMP Trap Reports Table 7-1 Managing SNMP Agent Access Task Sample Command Viewing all read user show snmpconfig type=readcommunity groups The default is “public”. A user needs read level access to: Viewing all write user groups Adding read user groups • Collect statistics on BTS components • View status on individual BTS components • View status on a group of BTS components show snmpconfig type=writecommunity The default is “public”.
Chapter 7 Using the BTS SNMP Agent Viewing SNMP Trap Reports Table 7-2 Receiving Trap Reports Task Operation Receiving traps reports from the SNMP agent Add an entry to SNMPTRAPDEST including the following: • NMS IP address or hostname • Port number to receive traps • Community string (not used) • Owner string (not used) • Filter Types—This specifies which subsystem events to receive: – BILLING – CALLP – CONFIG – DATABASE – MAINTENANCE – OSS – SECURITY – SIGNALING – STATISTICS – SYSTEM – AUD
Chapter 7 Using the BTS SNMP Agent Viewing and Managing BTS Components Viewing and Managing BTS Components Table 7-3 Viewing and Managing BTS Components Task Operation Viewing individual BTS components GET/GETNEXT • Primary and secondary EMS • Primary and secondary BDMS • Primary and secondary CA • Primary and secondary POTS/Centrex/Tandem FS • Primary and secondary AIN FS GET/GETNEXT on MIB State columns • MGW • TG • Subscriber Termination • Trunk Termination • SGP • DPC • SC
Chapter 7 Using the BTS SNMP Agent Viewing and Managing BTS Components Table 7-3 Viewing and Managing BTS Components (continued) Task Changing settings on BTS components Operation 1. SET necessary fields (Mode column, TargetState column, etc). 2. SET on the ControlState column, using 1 (commit) to change the state.
Chapter 7 Using the BTS SNMP Agent Querying the SNMP Agent Querying the SNMP Agent Table 7-4 Querying the SNMP Agent Task Querying the SNMP agent directly Operation 1. Open the /etc/snmp/conf/snmpd.conf file. 2. In read-community enter a single user group for read access. 3. In managers enter the IP address or hostname of NMS to query, enter multiple addresses separated by spaces. Note 4. To keep communication with the Master Agent leave the localhost entry.
Chapter 7 Using the BTS SNMP Agent Enabling NMS to Query/Poll Solaris SNMP Agent The active EMS node runs the SAD process, which converts the BTS 10200 specific events/alarms into SNMP traps and sends them to the configured SNMP Trap listeners or the NMSes. The SAD process handles the SNMPWALK/GET/GETNEXT/SET on the OIDs that are defined in the opticall.mib file. The SAD process also runs on the standby EMS, but does not perform any function. Note The SAD process does not run on the CA nodes.
Chapter 7 Using the BTS SNMP Agent Enabling NMS to Query/Poll Solaris SNMP Agent Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
A P P E N D I X A Feature Tones Revised: February 18, 2010, OL-16000-07 Introduction This appendix explains special tones the BTS supports for subscriber and operator features. The BTS supports these tones by sending MGCP messages to the gateways. Tones per Feature Table A-1 Feature Tones Condition(s) That Initiate Tone1 Feature Tone AC ALERTING PATTERN 3 ACR No tone ACRA CONFIRMATION TONE Anonymous call rejection (ACR) was successfully activated or deactivated by subscriber actions.
Appendix A Feature Tones Tones per Feature Table A-1 Feature Tones (continued) Feature Tone Condition(s) That Initiate Tone1 CW CW TONE If called party has MDN feature: primary DN matched. CIDCW 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.
Appendix A Feature Tones Tones per Feature Table A-1 Feature Tones (continued) Feature Tone Condition(s) That Initiate Tone1 CFU-ACT STUTTER TONE The subscriber has successful activated CFU from the handset. DIAL TONE The subscriber has dialed the CFU-ACT star code, and the BTS is ready to receive digits for the forward-to DN. 1-second timer elapses following the confirmation tone. CONFIRMATION TONE Centrex subscriber successfully activates extension forwarding.
Appendix A Feature Tones Tones per Feature Table A-1 Feature Tones (continued) Feature Tone Condition(s) That Initiate Tone1 CNDB DIAL TONE The subscriber has dialed the star code for the identity blocking feature, and the BTS is ready to receive digits for the DN to be called. CONFIRMATION TONE The BTS prompts the subscriber to enter the account code. CONFIRMATION TONE The BTS prompts the subscriber to enter the authorization code.
Appendix A Feature Tones Tones per Feature Table A-1 Feature Tones (continued) Feature Tone Condition(s) That Initiate Tone1 DPU STUTTER TONE The subscriber has dialed DPU access code, and DPU access has been granted. REORDER TONE Reorder tone is returned to the subscriber who initiated a DPU request when any of the following occurs: CONFIRMATION TONE • The dialed extension is not assigned in the business group dialing plan.
Appendix A Feature Tones Tone Frequencies and Cadences Table A-1 Feature Tones (continued) Feature Tone Condition(s) That Initiate Tone1 SC1D-ACT STUTTER TONE Stutter tone is used once after the subscriber 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.
Appendix A Feature Tones Tone Frequencies and Cadences Table A-2 Subscriber and Operator Tone Descriptions (continued) Tone Frequency (Hz) Cadence Played by MGW 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.
Appendix A Feature Tones Tone Frequencies and Cadences Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
A P P E N D I X B FIM/XML Revised: February 18, 2010, OL-16000-07 This appendix describes the FIM/XML feature for Release 6.0.1 of the Cisco BTS 10200 Softswitch and explains how to use it.
Appendix B FIM/XML Tool Requirements • Specify the precedence order for the external features • Define the list of features that inhibit the external feature • Define error response operations Advantages of the FIM/XML Tool The FIM/XML tool enables the service provider or operator to specify the SIP trigger-based features. The SIP trigger-based feature examples are, Off-Hook Delay Trigger (OHD), Termination Attempt Triggers TAT-1 and TAT-2.
Appendix B FIM/XML Writing an External FIM/XML File • The service provider or operator has write permission for the directory where the FIM/XML offline tool is located. • The service provider or operator has read permission for all the input XML files. Writing an External FIM/XML File To write an external FIM/XML file, do the following: Step 1 Use any XML editor. Step 2 Open a new XML file in it.
Appendix B FIM/XML Defining Features Define Element The properties of the external feature are configured in the Define Element. The FIM/XML tool processes the external FIM/XML file in the Define Element. Table 1 lists the attributes in the Define Element. Table 1 Attributes of Define Element Attribute Name Required Description feature_name Yes Name of the feature being defined.
Appendix B FIM/XML Defining Features Inhibit Others Element The Inhibit Others Element tag defines the list of features that are inhibited when a given feature is in an Assigned or Invoked state. Table 3 lists the attributes of the Inhibit Others Element. Feature Inhibitions prevent invocation of a given feature if a specified feature is Activated, Deactivated, Invoked, Assigned. For example, when the emergency call is involved then the Call Waiting is inhibited.
Appendix B FIM/XML Defining Features Error The list of error elements is matched one by one to see if the error response received during the external feature invocation falls within its specified range. When a match is found, the error handling operation specified within the respective error element is executed. Table 5 Error Attributes Attribute Name Required Description range-start Optional The start range of the error responses of the element that is matched.
Appendix B FIM/XML Installing the FIM/XML File Using the Offline FIM/XML Tool Installing the FIM/XML File Using the Offline FIM/XML Tool Each Cisco BTS 10200 release includes an original FIM/XML file that is installed during system setup and upgrades. The offline FIM/XML tool allows the service provider to define a new external feature or modify existing interactions involving the ISC features. In order to enable the service provider to add external features, a separate XML configuration file is provided.
Appendix B FIM/XML Installing the FIM/XML File Using the Offline FIM/XML Tool Step 6 Run the following Java application: java —jar fimxml.jar param1 param2 param3 param4 Where • param1 = the name of the external FIM/XML file described in Step 3 • param2 = the name of the original FIM/XML file produced during the Cisco BTS 10200 installation. Copy this file from the following path: /opt/OptiCall/etc/fimxml/FSPTC235/FIMXMLRules.xml.
Appendix B FIM/XML FIM/XML File and Shared iFC File FIM/XML File and Shared iFC File A Shared Initial Filter Criteria (iFC) file specifies all the data required to provision a new feature in the Element Management System (EMS). Using the shared iFC file is analogous to provisioning feature data through the CLI. You can provision all the user commands supported through CLI using the shared iFC.
Appendix B FIM/XML Provisioning iFC Provisioning iFC To enable the operator to provision iFC (s) through the XML file, the service provider must generate and install the new XML file (Shared iFC file).
Appendix B FIM/XML Feature Restrictions and Limitations Subscriber-Sip-Trigger-Profile This command adds the Subscriber-Sip-Trigger-Profile. add subscriber-sip-trigger-profile sub-id=sub_1; fname=ABC; sip-trigger-profile-id=AS_1; Service-Id This command adds the Service ID. add service id=ohd_vsc; fname1=ABC; Subscriber-Service-Profile This command adds the Subscriber-Service-Profile.
Appendix B FIM/XML Feature Restrictions and Limitations Cisco BTS 10200 Softswitch Operations and Maintenance Guide, Release 6.0.
