Table Of Contents
SS7 ANSI Implementation
Contents
Information about SS7 ANSI
Prerequisites for SS7 ANSI Implementation
CLI Command Reference
New Object Commands
DPC
OPC
Signaling Gateway
Signaling Gateway Group
User Part Variant
Call Control Route
Routing Key
Signaling Gateway Process
SCTP Association Profile
SCTP Association
SS7 ANSI Trunk Group Profile
SS7 CIC
Subsystem
SCCP Network
SLHR Profile
Service Logic Host Route (SLHR)
Modified CARRIER Table
Modified FEATURE SERVER Table
Modified CALL AGENT Table
Provisioning SS7 ANSI
Provisioning Example
Operations
Traffic Statistics Measurements
New ISUP Measurements
M3UA Measurements
SCCP Measurements
SCTP Association Measurements
TCAP Measurements
INAP Measurements
SS7 ANSI ISUP Trunk Reasons
Troubleshooting
MDL Protocol Tracing
Overview
Start MDL Trace
Stop MDL Trace
Events and Alarms
Additional References
Related Documents
Standards
RFCs
Technical Assistance
SS7 ANSI Implementation
The Cisco BTS 10200 Softswitch SS7 ANSI feature implements North America SS7 through a signaling transportation (SIGTRAN)-based ANSI signaling gateway, providing the ability to port SIGTRAN (SCTP/M3UA) and the upper SS7 layers (ISUP, SCCP, TCAP, AIN) to an IP network. It also provides the framework for providing international SS7 signaling, to be added to the BTS in the future through an international signaling gateway interface.
Feature Specifications for the SS7 ANSI Feature
Feature History
|
|
Release
|
Modification
|
Release 4.0
|
This feature was introduced.
|
Supported Platforms
|
Cisco Broadband Telephony Switch 10200 (BTS 10200)
|
Contents
This addendum documents the SS7 ANSI feature and includes the following sections:
•
Information about SS7 ANSI
•Prerequisites for SS7 ANSI Implementation
•CLI Command Reference
•Provisioning SS7 ANSI
•Operations
•Troubleshooting
Information about SS7 ANSI
All IP transport networks must address the conversion between IP and SS7. As IP networks are accepted as more cost-effective and equally reliable to the legacy ANSI SS7 networks, the ANSI signaling market will migrate to the SIGTRAN standard over next few years.
Prerequisites for SS7 ANSI Implementation
This feature removes embedded signaling links and relies on ITP signaling gateways to handle the the conversion between IP and SS7 networks. It requires that the BTS communicate with one or more Cisco ITP signaling gateways.
CLI Command Reference
This document describes new or modified CLI commands introduced with the implementation of SS7 ANSI.
All existing commands used with this feature are documented in the Cisco BTS 10200 Softswitch Release 3.2, 3.3, and 3.5 Command Reference Guide.
New Object Commands
Configuring SS7 ANSI includes provisioning the following new objects:
•DPC
•OPC
•Signaling Gateway
•Signaling Gateway Group
•User Part Variant
•Call Control Route
•Routing Key
•Signaling Gateway Process
•SCTP Association Profile
•SCTP Association
•SS7 ANSI Trunk Group Profile
•SS7 CIC
•Subsystem
•SCCP Network
•SLHR Profile
•Service Logic Host Route (SLHR)
Note An asterisk preceding a token name in the following tables indicates that the token is mandatory.
DPC
A destination point code (DPC) is the SS7 address of an end point with which the BTS 10200 Softswitch communicates. In previous releases, the DPC was configured as a token in the TRUNK GROUP table. In Release 4.0, the new DPC table stores information for all DPCs configured for the Cisco BTS 10200.
Table Name: DPC
Table Containment Area: Call Agent, FSPTC, FSAIN
show dpc id=dpc1;
add dpc id=dpc1;point-code=1.1.1;net-ind=national;description=destination point code;
change dpc id=dpc1;description=gateway dpc;
delete dpc id=dpc1;
status dpc id=dpc1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
DPC Table
|
Defines destination point codes with which the BTS 10200 Softswitch communicates
|
*ID
|
Primary key. Unique identifier for the DPC. VARCHAR(16)—1-16 ASCII characters. Primary key.
|
NET-AP
|
Unique key. Network appearance. INTEGER—0-32767; (Default=1)
Note Reserved for future use
|
* POINT-CODE
|
Point code value. VARCHAR(16)—1-16 ASCII characters.
|
* POINT-CODE-TYPE
|
Type of point code. VARCHAR(16). Valid values are:
•ANSI-CHINA (Default)
•ITU
|
NET-IND
|
Network indicator. VARCHAR(16). A valid value is one of the following strings:
INTERNATIONAL (Default)
SPARE
NATIONAL
RESERVED
|
DESCRIPTION
|
Service provider defined description of the DPC. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): id
Unique Index Token(s): POINT-CODE and NET-AP
•Add Rules: None.
•Change Rules: ID must exist; point code cannot be modified
•Delete Rules: ID does not exist in any dependency table
OPC
An originating point code (OPC) is the SS7 address of a network node sending a message to another network node.
In previous releases, the OPC was derived from the SS7-CIC table. In Release 4.0, the new OPC table stores information for all originating point codes configured for the Cisco BTS 10200.
Table Name: OPC
Table Containment Area: Call Agent, FSPTC, FSAIN
show opc id=opc1;
add opc id=opc1;point-code=2.2.1;description=destination point code;
change opc id=opc1;description=gateway opc;
delete opc id=opc1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
OPC Table
|
Defines all origination point codes configured for the Cisco BTS 10200 Softswitch.
|
* ID
|
Primary key. Unique OPC identifier. VARCHAR(16)—1-16 ASCII characters.
|
* POINT-CODE
|
Unique key. Origination point code. VARCHAR(16)—1-16 ASCII characters.
|
* POINT-CODE-TYPE
|
The type of point code.Valid values are:
ANSI-CHINA (Default)
ITU
JAPAN
|
DESCRIPTION
|
Service provider defined description of OPC. VARCHAR(64)—1-64 ASCII characters.
|
Usage Guidelines
Primary Key Token(s): id
Unique Index Token(s): POINT-CODE
•Add Rules: None.
•Change Rules: Point-code cannot be modified
•Delete Rules: ID cannot exist in any dependency table
Signaling Gateway
A signaling gateway passes signaling messages between the SS7 network and the IP nodes.
It is a new object introduced in Release 4. The Signaling Gateway table identifies all signaling gateways managed by the Call Agent.
Table Name: SG
Table Containment Area: Call Agent, FSPTC, FSAIN
show sg id=sg1;
add sg id=sg1;
change sg id=sg1;description=Signaling Gateway 1;
delete sg id=sg1;
get-trace sg id=sg1;
set-trace sg id=sg1;
Syntax Description
SG Table
|
Identifies all signaling gateways managed by the call agent.
|
* ID
|
Primary key. Unique signaling gateway identifier. VARCHAR(16)—1-16 ASCII characters.
|
PRIORITY
|
INTEGER. Valid values are:
1=HIGH (Default)
2=LOW
|
TRACE-SG-STATE
|
CHAR(1)—Y/N
(Default=N)
|
TRACE-DPC-STATE
|
CHAR(1)—Y/N
(Default=N)
|
TRACE-ERR
|
CHAR(1)—Y/N
(Default=N)
|
TRACE-ERRIND
|
CHAR(1)—Y/N
(Default=N)
|
DESCRIPTION
|
Service provider defined description of the signaling gateway. VARCHAR(125) —1-125 ASCII characters.
|
Primary Key Token(s): id
Unique Index Token(s):
•Add Rules: None.
•Change Rules: ID must exist; only changeable token is DESCRIPTION
•Delete Rules: ID cannot exist in any dependency table.
Signaling Gateway Group
A signaling gateway group is a new object that associates paired signaling gateways for redundancy and load sharing.
Table Name: SG-GRP
Table Containment Area: Call Agent, FSPTC, FSAI
show sg-grp id=sgpair1;
add sg-grp id=sgpair1;sg1=sg1;sg2=sg2;
change sg id=sg1;description=Signaling Gateway 1;
delete sg-grp id=sgpair1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
SG-GRP Table
|
Associates paired signaling gateways
|
* ID
|
Primary key. Unique SG group identifier. VARCHAR(16)—1-16 ASCII characters.
|
* SG1-ID
|
Unique key; foreign key from SG table. First signaling gateway ID. VARCHAR(16)—1-16 ASCII characters.
|
SG1-2D
|
Second signaling gateway ID. Unique key; foreign key from SG table. VARCHAR(16)—1-16 ASCII characters.
|
DESCRIPTION
|
Service provider defined description of the signaling gateway group. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): id
Unique Index Token(s): SG1 -ID and SG2-ID
•Add Rules: ID cannot exist; SG1-ID and SG2-ID cannot be the same
•Change Rules: ID must exist; only changeable token is DESCRIPTION
•Delete Rules:ID cannot exist in any dependency table
User Part Variant
The USER-PART-VARIANT table identifies all supported SS7 user part variants and their protocol families.
Table Name: USER-PART-VARIANT
Table Containment Area: Call Agent
show user-part-variant;
show user-part-variant id=variantname1;
add user-part-variant;proto-fam=SS7-ANSI;
change user-part-variant id=ANSISS7_GR317;reset-supported=N;
delete user-part-variant id=ANSISS7_GR317;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
USER-PART-VARIANT Table
|
Identifies all supported SS7 user part variants and their protocol families.
|
* ID
|
Primary key. Variant ID in the format <protocol family>_<variant name. VARCHAR(32)—1-32 ASCII characters.
|
PROTO-FAM
|
Protocol family. VARCHAR(16). Valid value is:
SS7
|
RESET-SUPPORTED
|
Indicates if the protocol supports sending and receiving reset messages to the line. Used to determine if a reset event can be signaled to the protocol.
|
MAX_RESET_MASTER_RANGE
|
Maximum number of master or individual calls in reset at one time. INTEGER; (Default=1)
|
MAX_RESET_SLAVE_RANGE
|
Maximum number of slave calls in reset at one time. INTEGER—0=No group reset(; Default=23)
|
MAX_BLOCK_MASTER_RANGE
|
Maximum number of master or individual calls in block at one time. INTEGER; (Default=1)
|
MAX_BLOCK_SLAVE_RANGE
|
Maximum number of slave calls in block at one time. INTEGER; 0=No group reset; (Default=23)
|
MAX_PARALLEL_JOBS
|
Number of parallel channel management jobs that can be signaled by subsequent passes through the channel management queue. INTEGER; (Default=10)
|
Primary Key Token(s): id
Unique Index Token(s):
Call Control Route
The CALL CONTROL ROUTE table identifies the call control routes defined between various OPCs, DPCs, and SG Groups.
Table Name: CALL-CTRL-ROUTE
Table Containment Area: Call Agent
show call-ctrl-route id=routeset1;
add call-ctrl-route id= routeset1; routing-key-id=rk1; dpc-id=dpc1;
user-part-variant-id=standardansiss7;si=isup;
delete call-ctrl-route id= routeset1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
CALL CONTROL ROUTE Table
|
Identifies all call control routes defined between various OPCs, DPCs, and SG Groups.
|
* ID
|
Primary key. Unique call control route identifier. VARCHAR(16)—1-16 ASCII characters.
|
* DPC-ID
|
Foreign key from the DPC table. Unique destination point code identifier. VARCHAR(16)—1-16 ASCII characters.
|
* ROUTING-KEY-ID
|
Foreign key from the routing key table. Unique routing key identifier. VARCHAR(16)—1-16 ASCII characters.
|
* USER-PART-VARIANT-ID
|
Foreign key from theSS7-ISUP-VARIANT Table. Name of the SS7 variant. VARCHAR(16)—1-16 ASCII characters.
|
* SI
|
Service indicator. VARCHAR(16). Valid values are one of the following strings:
•ISUP
•TUP
•SCCP
|
DESCRIPTION
|
Service provider defined description of the SS7 route set. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): id
Unique Index Token(s):
•Add Rules: None
•Change Rules: Only description can be modified.
•Delete Rules: ID cannot exist in any dependency table.
Routing Key
A routing key describes a set of SS7 parameters and parameter values that uniquely define the range of signaling traffic to be handled by an associated Call Agent or Feature Server.
The ROUTING-KEY table stores the information for all M3UA/SUA routing keys managed by the Call Agent.
Table Name: ROUTING-KEY
Table Containment Area: Call Agent, FSPTC, FSAIN
show routing-key id=rk1;
add routing-key id= rk1; opc-id=opc1;sg-grp-id=sggrp1;rc=5;si=isup; platform-id=ca146
delete routing-key id= rk1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
ROUTING-KEY Table
|
Stores information for all M3UA/SUA routing keys managed by the Call Agent.
|
* ID
|
Primary key. Unique routing key identifier. VARCHAR(16)—1-16 ASCII characters.
|
* SG-GRP-ID
|
Foreign key from SG-GRP table. Unique signaling gateway group identifier. VARCHAR(16)—1-16 ASCII characters.
|
* OPC-ID
|
Foreign key from OPC table. Unique OPC identifier. VARCHAR(16)—1-16 ASCII characters.
|
DPC-ID
|
Foreign key from DPC table. Unique DPC identifier. VARCHAR(16)—1-16 ASCII characters.
|
* SI
|
Service indicator. VARCHAR(4). Valid values are one of the following strings:
•SCCP
•TUP
•ISUP
|
SSN-ID
|
Mandatory if SI=SCCP;Optional if SI=TUP or ISUP. Foreign key from SUBSYSTEM table. Unique subsystem identifier. VARCHAR(16)—1-16 ASCII characters. Required if SI=SCCP.
|
* RC
|
Routing context. INTEGER—0-65535.
|
* PLATFORM-ID
|
Unique platform identifier. VARCHAR(16)—1-16 ASCII characters. Valid values are any valid Call Agent or Feature Server ID.
|
DESCRIPTION
|
Service provider defined description of the routing key. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): id
Unique Index Token(s):
•Add Rules: The same DPC cannot cross multiple SG-GRPs; the NET-AP must be the same as the NET-AP of the DPC if specified; SSN-ID is required when SI=SCCP.
•Change Rules: None
•Delete Rules: ID cannot exist in any dependency table.
Signaling Gateway Process
The Signaling Gateway Process (SGP) table identifies all the signaling gateway processes associated with each signaling gateway.
Table Name: SGP
Table Containment Area: Call Agent, FSPTC, FSAIN
show sgp id=sgp1;
add sgp id= sgp1; sg-id=sg1;
delete sgp id= sgp1;
status sgp id=sgp1;
get-trace sgp id=sgp1;
set-trace sgp id=sgp1; trace-err=Y
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
SGP Table
|
Identifies all the signaling gateway processes associated with each signaling gateway.
|
* ID
|
Primary key. Unique signaling gateway process identifier. VARCHAR(16)—1-16 ASCII characters.
|
* SG-ID
|
Foreign key from SG table.Unique signaling gateway identifier. CHAR(1)—Y/N (Default=N).
|
TRACE_SCTP
|
CHAR(1)—Y/N (Default=N).
|
TRACE-PAK
|
CHAR(1)—Y/N (Default=N).
|
TRACE-HB
|
CHAR(1)—Y/N (Default=N).
|
TRACE-ERR
|
CHAR(1)—Y/N (Default=N).
|
TRACE-ERRIND
|
CHAR(1)—Y/N (Default=N).
|
DESCRIPTION
|
Service provider defined description of the signaling gateway process. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): id
Unique Index Token(s): SG ID + ID
•Add Rules: ID cannot already exist.
•Change Rules: ID must exist; only DESCRIPTION value can be modified
•Delete Rules: ID cannot exist in any dependency table.
SCTP Association Profile
The SCTP Association Profile table stores the configuration parameters that can be referenced by any SCTP Association.
Table Name: SCTP-ASSOC-PROFILE
Table Containment Area: Call Agent
show sctp-assoc-profile id=sctpassocprof1;
add sctp-assoc-profile id=sctpassocprof1;
change sctp-assoc-profile id= sctpassocprof1;
delete sctp-assoc-profile id= sctpassocprof1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
SCTP-ASSOC-PROFILE Table
|
Stores the configuration parameters that can be referenced by any SCTP Association.
|
* ID
|
Unique SCTP association profile identifier. VARCHAR(16)—1-16 ANSII characters.
|
BUNDLE-TIMEOUT
|
Maximum time, in milliseconds, that SCTP will wait for outgoing datagrams for bundling. INTEGER—0-600 ms; (Default=0)
|
MAX-PATH-RETRANS
|
Maximum number of retransmissions to either remote TSAP address1 or TSAP address2 before the association is declared failed. INTEGER—2-6; (Default=3).
|
MAX-ASSOC-RETRANS
|
Maximum number of retransmissions over all destination addresses before the association is declared failed. SMALLINT—(Default=4)
Note This value should not exceed (MAX-PATH-RETRANS) X (number of destinations)
|
RETRIEVE-FLAG
|
Indicates if the ULP wants to be able to retrieve datagrams after the association fails. CHAR(1)—Y/N; (Default=Y)
|
MAX-RTO
|
Maximum value, in milliseconds, for the retransmission timer. INTEGER—300-60000 ms; (Default=3000)
|
SACK-TIMEOUT
|
Maximum time, in milliseconds, after a datagram is received before a SCPT SACK will be sent. INTEGER—100-60000 ms; (Default=200).
|
MIN-RTO
|
Minimum value, in milliseconds, configurable for the retransmission timer. INTEGER—300-60000 ms; (Default=300)
|
HB-TIMEOUT
|
Time, in milliseconds, between heartbeats. The heartbeat will be this value plus the current retransmission timeout value. INTEGER—0-10000 ms; (Default=2000); 0=Disabled
|
DESCRIPTION
|
Service provider defined description of the SCTP association profile. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): id
Unique Index Token(s):
•Add Rules: ID cannot already exist.
•Change Rules: ID must exist
•Delete Rules: ID must exist
SCTP Association
The SCTP Association table identifies the association between local and remote SGPs.
Table Name: SCTP-ASSOC
Table Containment Area: Call Agent, FSPTC, FSAIN
show sctp-assoc id=sctpassoc1;
add sctp-assoc id=sctpassoc1; signaling-gateway-id=sg1;
change sctp-assoc id= sctpassoc1; signaling-gateway-id=sg2;
delete sctp-assoc id= sctpassoc1;
status sctp-assoc id=sctpassoc1;
control sctp-assoc id=sctpassoc1; target-state=OOS
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
SCTP-ASSOC Table
|
Identifies the association between local and remote SGPs.
|
* ID
|
Primary key. Unique SCTP association identifier. VARCHAR(16)—1-16 ASCII characters.
|
* PLATFORM-ID
|
Unique platform identifier. VARCHAR(8)—1-8 ASCII characters.
|
* SGP-ID
|
Foreign key from the SGP table. Unique signaling gateway process identifier. VARCHAR(16)—1-16 ASCII characters.
|
* SCTP-ASSOC-PROFILE-ID
|
Foreign key from the SCTP-ASSOC-PROFILE table. VARCHAR(16)—1-16 ASCII characters.
|
* REMOTE-PORT
|
SMALLINT—1024-65535.
|
* REMOTE-TSAP-ADDR1
|
Unique key. VARCHAR(64)—1-64 ASCII characters.
|
REMOTE-TSAP-ADDR2
|
Unique key. VARCHAR(64)—1-64 ASCII characters.
|
STATUS
|
Administrative status. VARCHAR(5). Valid values are one of the following strings:
•OOS-Out of Service (Default)
•INS-In Service
•OOS-PENDING-Request to put SGP in OOS state is pending
|
DSCP
|
Differential service code point.
This value will be placed in the DSCP portion of the Type Of Service field of outgoing SCTP datagrams.
VARCHAR(16). Valid values are one of the following strings:
•EF
•AF11
•AF12
•AF13
•AF21
•AF22
•AF23
•AF31
•AF32
•AF33
•AF41
•AF42
•AF43
•N/A (Default)
|
IP-TOS-PRECEDENCE
|
Internet Protocol precedence/ this value will be placed in the IP PRECEDENCE portion of the Type Of Service field of outgoing SCTP datagrams. VARCHAR(16). Valid values are one of the following strings:
One of the following strings:
0-ROUTINE (Default)
1-PRIORITY
2-IMMEDIATE
3-FLASH
4-FLASHOVERRIDE
5-CRITICAL
6-INTERNETCONTROL
7-NETCONTROL
|
LOCAL-RCVWIN
|
Number of bytes to advertise for the local receive window. INTEGER; (Default=18000).
|
MAX-INIT-RETRANS
|
Maximum number of times to retransmit SCTP INIT message. SMALLINT—1-5; (Default=3).
|
MAX-INIT-RTO
|
Maximum initial timer transmission value, in milliseconds. SMALLINT—500-3000; (Default=500).
|
DESCRIPTION
|
Service provider defined description of the SCTP association. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): id
Unique Index Token(s): SGP-ID + ID
•Add Rules: ID cannot already exist; SGP-ID must exist
•Change Rules: ID must exist; SCTP association must be in OOS state when being modified; SGP-ID cannot be modified
•Delete Rules: ID must exist.
SS7 ANSI Trunk Group Profile
The existing SS7-TG-PROFILE Table stores common information about an SS7 ANSI trunk group. This table can be shared by multiple SS7 trunk groups. The TYPE token has been deleted from this table, and the following new tokens have been added:
•ALARM CARRIER
•ALLOW-EXM
•ALLOW-CRMCRA
•CCT-GRP-CARRIER
Table Name: SS7-ANSI-TG-PROFILE
Table Containment Area: Call Agent
show ss7-ansi-tg-profile id=ss7tgpf1;
add ss7-ansi-tg-profile id=ss7tgpf1; cot-duration=20;
change ss7-ansi-tg-profile id=ss7tgpf1; cot-duration=3;
delete ss7-ansi-tg-profile id=ss7tgpf1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
SS7-TG-PROFILE Table
|
Stores common information about an SS7 ANSI trunk group.
|
* ID
|
Primary key. Unique SS7 trunk group profile identifier. VARCHAR(16)—1-16 ASCII characters.
|
TYPE (Deleted)
|
Since this is an SS7 ANSI information table, specifying the type is not necessary.
|
FAST-ANSWER-SUPP
|
Indicates if FAST answer is supported. This token is used when a call is being terminated to a NAS server. CHAR(1)—Y/N
(Default=Y)
|
ALARM-CARRIER
(New token)
|
Alarm carrier. VARCHAR(16). Valid values are one of the following strings:
•UNKNOWN (Default=UNKNOWN)
•SOFTWARE
•HARDWARE
|
ALLOW-EXM
(New token)
|
Send EXM indicator. CHAR(1)—Y/N; (Default=Y)
|
ALLOW-CRMCRA
(New token)
|
Allow circuit reservation indicator. CHAR(1)—Y/N; (Default=Y)
|
CCT-GRP-CARRIER
(New token)
|
Circuit group carrier indicator field of circuit group characteristics parameter. VARCHAR(32). Valid values are one of the following strings:
•UNKNOWN
•ANALOG
•DIGITAL (Default)
•DIGITAL-ANALOG
|
CFN-SUPP
|
Confusion message support indicator. CHAR(1)—Y/N; (Default=N); Y=Far-end switch supports Confusion Message.
|
COT-DURATION
|
Duration of continuity test. SMALLINT—1=60 (Default=1).
|
COT-FREQ
|
Cot percentage. SMALLINT—0-100 (Default=7)
|
COT-ORIG
|
Continuity test indicator on originating (outgoing) SS7 calls. CHAR(1)—Y/N; (Default=N);
|
COT-TONE
|
Continuity tone. VARCHAR(8)—Valid values are:
4W-to-4W (Default)
2W-to-2W
2W-to-4W
4W-to-2W
|
DEFAULT-BC
(New token)
|
The default bearer capability to be used in USI parameter. VARCHAR(6). Valid values are one of the following strings:
•SPEECH 3_1
•KHZ
|
DEFAULT-CHGNOA
(New token)
|
VARCHAR(32). Valid values are one of the following strings:
•NOTUSED (Default)
•ANI_CGSUB_SUB_NUM
•ANI_NOT_AVAIL
•ANI_CGSUB_NAT_NUM
•ANI_CDSUB_SUB_NUM
•ANI_CDSUB_NO_NUM
•ANI_CDSUB_NAT_NUM
|
DEFAULT-CHGNPI
(New token)
|
Default Charge Number NPI. VARCHAR(32). Valid values are one of the following strings::
•NOTUSED (Default)
•NONE
•E164
•DATA
•TELEX
•PNP
•NATIONAL
•TELEPHONY
•MARITIME_MOBILE
•LAND_MOBILE
•ISDN_MOBILE
|
DEFAULT-OLI
(New token)
|
Default Originating Line Information. VARCHAR(32). Valid values include one of the following strings:
•NOTUSED (Default)
•POTS
•MULTIPARTY_LINE
•ANI_FAILURE
•STATION_LEVEL_RATING
•SPECIAL_OPERATOR_REQ
•AIOD
•COIN_DATABASE
•800_SERVICE_CALL
•COIN
•PRISON_INMATE_SERVICE
•INTERCEPT_BLANK
•INTERCEPT_TROUBLE
•INTERCEPT_REGULAR
•TELCO_OPERATOR_CALL
•OUTWATS
•TRS_1
•TRS_2
•TRS_3
•CELLULAR_SVC_1
•CELLULAR_SVC_2
•CELLULAR_SVC_ROAMING
•PRIVATE_PAYSTATIONS
•ACCESS_FOR_VPN_TYPES_OF_SVC
•INTERLATA_RESTRICTED
•TESTCALL
•TOLLFREE_FROM_PAYSTATION
•CUSTOMER_SPECIFIC_1
•CUSTOMER_SPECIFIC_2
•INTERLATA_RESTRICTED_HOTEL
•INTERLATA_RESTRICTED_COINLESS
|
ECHO-SUPP-REQUIRED
|
Echo suppression required indicator. CHAR(1)—Y/N (Default=N).
|
HOP-COUNTER
|
Number of SS7 hops allowed. SMALLINT—0, 10-20(Default); 0=Not Supported.
|
INBAND-INFO
|
Send release, provide tone or announcement. CHAR(1)—Y/N ; (Default=N)
|
REDIR-MAX
(New token)
|
Maximum Redirections. SMALLINT—1 - 10; (Default = 5)
|
SATELLITE-CIRCUIT
|
Satellite circuit indicator. CHAR(1)—Y/N ; (Default=N)
|
SEND-ATP
|
Send access transport parameter indicator. CHAR(1)—Y/N ; (Default=N)
|
SEND-CHNOLIP
(New token)
|
Send Charge Number Originating Line Info. Presentation Indicator. CHAR(1)—Y/N ; (Default=N)
|
SEND-CHN-NONGEO
(New token)
|
Send Charge Number Non-Geographic Indicator. CHAR(1)—Y/N ; (Default=N)
|
SEND-CIP
|
Send carrier information parameter (GR-394). CHAR(1)—Y/N ; (Default=N)
|
SEND-CIP-NONGEO
(New token)
|
Carrier Info. Parameter Non-Geographic Include. CHAR(1)—Y/N ; (Default=N)
|
SEND-CPN
|
Send calling party number should always be included. CHAR(1)—Y/N ; (Default=Y)
|
SEND-CPN-PRES
(New token)
|
Send Calling Party Number Presentation Info. CHAR(1)—Y/N ; (Default=N)
|
SEND-GAP
|
Send generic address parameter indicator. CHAR(1)—Y/N ; (Default=Y)
|
SEND-GN
|
Send generic name indicator. CHAR(1)—Y/N ; (Default=N)
|
SEND-HOPCOUNTER
(New token)
|
Send Hop Counter Indicator. CHAR(1)—Y/N; (Default=Y)
|
SEND-JIP
|
Send jurisdiction information parameter. CHAR(1)—Y/N ; (Default=Y)
|
SEND-NOTIFICATION
(New token)
|
Send notification indicator. CHAR(1)—Y/N ; (Default=N)
|
SEND-OCN
|
Send original called number indicator. CHAR(1)—Y/N ; (Default=Y)
|
SEND-REDIR-NUM
|
Send redirecting number indicator. CHAR(1)—Y/N ; (Default=Y)
|
SEND-REDIRINFO
(New token)
|
Send Redirecting Information Indicator. CHAR(1)—Y/N; (Default=Y)
|
SEND-REDIRCAP
(New token)
|
Send Redirection Capability Info Indicator. CHAR(1)—Y/N; (Default=N)
|
SEND-REDIRCOUNTER
(New token)
|
Send Redirection Counter Indicator. CHAR(1)—Y/N ; (Default=N)
|
SEND-SERVICECODE
(New token)
|
Send service code indicator. CHAR(1)—Y/N ; (Default=N)
|
SEND-TRANSREQ
(New token)
|
Send transaction request parameter indicator. CHAR(1)—Y/N ; (Default=N)
|
T-8
|
Timer: When receipt of IAM indicating previous or incoming continuity check, awaiting COT. SMALLINT—10-15 seconds.
|
T-9
(New token)
|
Ring No Answer Timer. SMALLINT—0-255 seconds; (Default = 255)
|
T-BLO
|
Timer: When sending BLO (blocking) or UBL, awaiting BLA or UBA; shorter timer used for retransmission. SMALLINT—4-6 seconds (Default=6).
|
T-CCR-R
|
Timer: When responding to a CCR (continuity check request), awaiting a COT or REL. SMALLINT—10-12 seconds (Default = 12).
|
T-CGB
|
Timer: When sending second CGB (circuit group blocking) or first CGU, awaiting CGBA or CGUA. SMALLINT—4-15 seconds (Default = 15).
|
T-COT-L
|
Timer: When receiving second COT coded "failed," awaiting receipt of CCR. SMALLINT—240-300 seconds (Default = 300).
|
T-COT-R
|
Timer: When receiving first COT coded "failed," awaiting receipt of CCR. SMALLINT—16-20 seconds (Default = 20).
|
T-GRS
|
Timer: When sending second GRS (circuit group reset), awaiting GRA. SMALLINT—4-15 seconds (Default = 15).
|
T-IAM
|
Sent IAM, waiting for ACM/ANM/REL. SMALLINT—20-30 seconds (Default = 30).
|
T-REL
|
Timer: When sending REL (release), awaiting RLC; shorter timer used for retransmission. SMALLINT—4-6 seconds (Default = 6).
|
T-RSC
|
Timer: When sending RSC, waiting RLC; shorter timer used for retransmission. SMALLINT—4-15 seconds (Default = 15).
|
DESCRIPTION
|
VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): id
Unique Index Token(s):
•Add Rules: ID cannot exist
•Change Rules: ID must exist
•Delete Rules: ID must exist; ID must not exist in any dependency table
SS7 CIC
The SS7-CIC Table is automatically created when SS7 trunks are provisioned. This table is not provisionable.
SS7-CIC Table
|
|
* TRUNK-ID
|
Identifies the trunk ID; constructed from the CIC start and CIC end tokens. System generated. Primary key; foreign key Trunk table. INTEGER
|
* OPC
|
Origination point code. Automatically provisioned from the route set table, which is referenced by the Trunk Group table. Primary Key; foreign key OPC table. VARCHAR(16)—1-16 ASCII characters.
|
* DPC
|
Destination point code. Automatically provisioned from the Trunk Group table. Primary key; foreign key in DPC table. VARCHAR(16)—1-16 ASCII characters.
|
* NET-AP
|
Automatically provisioned from the DPC table. INTEGER.
|
* CALL-CTRL-ROUTE-ID
|
Automatically provisioned from the TG table. Foreign key, Route Set table. VARCHAR(16)—1-16 ASCII characters.
|
* TGN-ID
|
Identifies the trunk group ID. INTEGER—1-99999999.
|
Subsystem
A subsystem is a new object that identifies ?????
The subsystem table stores information for all subsystems using SCCP.
Table Name: SUBSYSTEM Table
Table Containment Area: FSPTC, FSAIN
show subsystem id=SSN1;
add subsystem id=SSN1; ssn=2; nw-id=nw1; platform-id=FSAIN5;
delete subsystem id=SSN1; ssn=2; nw-id=nw1;
status subsystem id=SSN1;
control subsystem id=SSN1; target-state=UIS; mode=FORCED;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
SUBSYSTEM Table
|
Stores information for all subsystems using SCCP.
|
* ID
|
Primary key. Unique subsystem identifier. VARCHAR(16)—1-16 ASCII characters.
|
* LOCAL-SSN
|
Unique key. Local subsystem number. SMALLINT—0-255.
|
* OPC-ID
|
Foreign key from OPC table. VARCHAR(16)—1-16 ASCII characters.
|
* SCCP-NW-ID
|
Foreign key from SCCP-NW table. SMALLINT—0-255.
|
* PLATFORM-ID
|
Foreign key from FEATURE-SERVER table. Platform identifier. VARCHAR(16)—1-16 ASCII characters.
|
* SCCP-VERSION
|
Protocol familySCCP Version to be used. VARCHAR(5)—Valid values are one of the following strings:
•ANS88
•ANS92
•ITU88
•ITU92
•ITU96
•CHINA
|
* TCAP-VERSION
|
Version of TCAP to use. VARCHAR(8)—Valid values are one of the following strings:
•ANS88
•ANS92
•ANS96
•ITU88
•ITU92
•ITU96
•CHINA
•ETS196
|
APPLICATION-VERSION
|
TCAP protocol version to be used in the query message. Valid values are one of the following strings:
One of the following strings:
•AIN02 (Future)
•QWEST_AIN02 (Future)
•AIN01
•IN1
•ETSI-INAP (Future)
•ITU-INAP (Future)
|
STATUS
|
Administrative status of the subsystem. VARCHAR(3)—Valid values are one of the following strings:
•IUS-User in service
•UOS-User out of service (Default)
|
OPER-STATUS
|
VARCHAR(16)—Valid values are one of the following strings:
•SSA-Subsystem Allowed
•SSP-Subsystem Prohibited
|
DESCRIPTION
|
Service provider defined description of the subsystem. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): ID
Unique Index Token(s): SSN + NW-ID
•Add Rules: None
•Change Rules: Change is not permitted.
•Delete Rules: ID of the subsystem must not exist in any dependency table
SCCP Network
The SCCP Network table stores the attributes associated with the SS7 network. Each network is associated with one point code.
Table Name: SCCP NW Table
Table Containment Area: FSPTC, FSAIN
show sccp-nw id=1;
add sccp-nw id=1; opc-id=opc1; proto-fam=ANS92; sub-svr=SSF_NAT; description=SCCP
network;
change sccp-nw id=1; NET-IND=NATIONAL;
delete sccp-nw id=1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
SCCP NW Table
|
Stores the attributes associated with the SS7 network. Each network is associated with one point code.
|
* ID
|
Primary key. Unique SCCP Network identifier. SMALLINT—1-255.
|
NET-IND
|
Network indicator. VARCHAR(16)—Valid values are one of the following strings:
•INTERNATIONAL
•SPARE
•NATIONAL (Default)
•RESERVED
|
* SUB-SVC
|
VARCHAR(16)—One of the following strings:
•INTERNATIONAL
•SPARE
•NATIONAL
|
* HOP-COUNT
|
Number of hops. SMALLINT—0-15
|
DESCRIPTION
|
VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): ID
Unique Index Token(s): OPC-ID
•Add Rules: None
•Change Rules: OPC-ID cannot be changed.
•Delete Rules: ID of the SCCP network must not exist in any dependency table
SLHR Profile
Service Logic Host Route (SLHR) defines the route of a TDP request message to an SCP.
The SLHR-Profile table identifies all parameters of an SLHR.
Table Name: SLHR PROFILE Table
Table Containment Area: EMS
show slhr-profile id=1;
add slhr-profile id=slhr1;
delete slhr-profile id=slhr1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
SLHR PROFILE Table
|
Identifies an SLHR.
|
* ID
|
Primary key. Unique identifier of the SLHR.VARCHAR(16)—1-16 ASCII characters.
|
DESCRIPTION
|
Service provider defined description of the SLHR profile. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): ID
Unique Index Token(s):
•Add Rules: None
•Change Rules:
•Delete Rules:
Service Logic Host Route (SLHR)
The SLHR table stores the information necessary to route a TDP request message to an SCP.
Table Name: SLHR Table
Table Containment Area: FSPTC, FSAIN
•show slhr id=1;
•add slhr id=slhr1; opc-id=opc1; dpc-id=dpc1; rk-id=rk1; remote-ssn=251;sccp-route-id=sccp_route1; ssn-id=ssn1;
•change slhr id=slhr1; remote-ssn=254;sccp-route-id=1;
•delete slhr id=slhr1;
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was introduced.
|
Syntax Description
SLHR Table
|
Stores the information necessary to route a TDP request message to an SCP.
|
* ID
|
Primary key; foreign key from SLHR-PROFILE Table. Unique SLHR route identifier.VARCHAR(16)—1-16 ASCII character.
|
* OPC-ID
|
Primary key; foreign key from OPC table. Originating point code. VARCHAR(16)—1-16 ASCII character.
|
* DPC-ID
Note DPC-ID is for the STP or SCP where the query is processed.
|
Foreign key from DPC table. Destination Point Code. VARCHAR(16)—1-16 ASCII character.
|
* RK-ID
|
Foreign key from RK table. Routing Key ID associated with the route to DPC. VARCHAR(16)—1-16 ASCII character.
|
* Remote-SSN
|
Unique key. Remote subsystem number. SMALLINT—0-255.
|
GTT-REQ
|
GTT Required Flag. CHAR(1)—Y/N; (Default=Y)
|
TT
|
Translation type. SMALLINT—0-255.
|
GTT-ADDR-TYPE
|
Identifies the GTT Address Type [Called, Calling or Network defined DN]. VARCHAR(4)—Valid values are one of the following strings:
•CDPN (Default)
•CLGN
•DN
|
GTT-ADDR
|
Identifies the GTT Address. VARCHAR(10)—3, 6, or 10 digits.
|
BPC-ID
|
Backup Point Code.
|
BRK-ID
|
Foreign key from the DPC table. Routing Key ID associated with the route to BPC, this must be present when BPC is present.VARCHAR(16)—1-16 ASCII character.
|
DESCRIPTION
|
Service provider defined description of the SLRH. VARCHAR(64)—1-64 ASCII characters.
|
Primary Key Token(s): ID
Unique Index Token(s):
•Add Rules: TT is mandatory if GTT-REQ=Y; GTT-ADDR-TYPE is mandatory if GTT-REQ=Y; GTT-ADDR IS MANDATORY IF GTT-ADDR-TYPE=DN
•Change Rules:
•Delete Rules:
Modified CARRIER Table
The existing CARRIER Table defines the characteristics and capabilities supported by interLATA carriers, intraLATA carriers, international carriers, and provides routing information. LATA stands for local access transport area and is predefined by geographical area
Table Name: CARRIER Table.
Table Containment Area: Call Agent
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was modified to introduce new tokens.
|
Syntax Description
Table 1
CARRIER Table
|
|
ID*
|
Unique carrier identification number. Primary key. CHAR(4); 4 numeric characters.
|
STATUS
|
Status of the carrier. CHAR(3); valid values are OOS (default) and INS.
|
INTER
|
Identifies whether carrier supports interLATA (long distance) calls. CHAR(1)—Y/N; (Default=Y).
|
INTRA
|
Identifies whether carrier supports intraLATA (toll) calls. CHAR(1)—Y/N; (Default=N)
|
INTL
|
Identifies whether the carrier supports international calls. CHAR(1)—Y/N; (Default=N
|
CASUAL
|
Identifies whether the carrier supports 101XXXX calls. CHAR(1)—Y/N; (Default=Y)
|
CUT-THRU
|
Identifies whether carrier supports 101XXX# calls.The called number is not dialed. CHAR(1)—Y/N; (Default=Y)
|
OP-SERVICES
|
Identifies whether carrier supports operator services. Use LEC OSS if Operator Services are not supported. CHAR(1)—Y/N; (Default=Y)
|
SEND-CN
|
Identifies whether carrier requires sending a charge number; used when charged number is different from the calling number. (Collect calls, for example) Also identifies whether the type of line making a call (OLI:origin line info) must be sent to the carrier. CHAR(1)—Y/N; (Default=N)
|
SEND-CSP (Carrier Selection Parameter)
|
Identifies whether the information parameter must be sent to the carrier. It identifies how the call was dialed for the carrier, for example, PIC, Casual, or Casual-same-as-PIC. CHAR(1)—Y/N; (Default=N)
|
USE-DIAL-PLAN
|
Identifies whether to use the Route Guide defined in the dial plan table (Y) or to use the Route Guide defined in the Carrier table for routing. CHAR(1)—Y/N; (Default=N
|
SP-ID
|
Service provider identifier associated with the carrier. If SP-ID is not NULL, the routing information from the Service Provider table is used. Foreign key from Service Provider table. VARCHAR(16); 1-16 ASCII characters.
|
ROUTE-GUIDE-ID
|
Defines the routing data for the carrier. Foreign key from the Route-Guide table. VARCHAR(16)/ 1-16 ASCII characters.
|
DESCRIPTION
|
Service provider's description of the carrier. VARCHAR(64).
|
Modified FEATURE SERVER Table
The existing FEATURE SERVER Table identifies the location and type of an existing feature server. The following tokens have been added to the table. These new tokens can only be retrieved or changed using the GET-TRACE and SET-TRACE commands.
Table Name: FEATURE SERVER Table
Table Containment Area:
get-trace
set-trace
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was modified to introduce new tokens.
|
Syntax Description
FEATURE SERVER Table
|
|
TRACE-SCTP-API
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-TXRXCHUNKS
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-STATE
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-SIGNAL
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-MULTIHOME
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-CONGESTION
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-INIT
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCCP
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-TCAP
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-INAP
|
CHAR(1)—Y/N; (Default=N).
|
Primary Key Token(s): ID
Unique Index Token(s):
•Add Rules:
•Change Rules: The fields in Table ... can only be changed using the set-trace command.
•Show Rules: The fields in Table ... can only be changed using the get-trace command.
Modified CALL AGENT Table
The existing CALL AGENT Table stores the domain name of the Call Agent switch and the primary and secondary IP addresses of the EMS. The following tokens have been added to the table. These new tokens can only be retrieved or changed using the GET-TRACE and SET-TRACE commands.
Table Name: CALL AGENT Table
Table Containment Area:
get-trace
set-trace
Note These tokens are new additions to the CALL AGENT table and can only be retrieved using get-trace and changed using set-trace.
Command History
Release
|
Modification
|
Cisco BTS 10200 Softswitch Release 4.0
|
This command was modified to introduce new tokens.
|
Syntax Description
CALL AGENT Table
|
|
TRACE-SCTP-API
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-TXRXCHUNKS
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-STATE
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-SIGNAL
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-MULTIHOME
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-CONGESTION
|
CHAR(1)—Y/N; (Default=N).
|
TRACE-SCTP-INIT
|
CHAR(1)—Y/N; (Default=N).
|
Primary Key Token(s): ID
Unique Index Token(s):
•Add Rules:
•Change Rules: The fields in this table can only be changed using the set-trace command.
•Show Rules: The fields in this table can only be changed using the get-trace command.
Provisioning SS7 ANSI
Provision in the following order:
CA
user part variant
SG
SG-GRP
SGP
OPC
DPC
Routing key
Call control route
SCTP assoc profile
SCTP assoc
MGW profile
MGW
Dial plan profile
SS& tg profile
SS7 TG
Route
Route guide
Destination
Dial plan
Termination
Trunk
Provisioning Example
This section lists the CLI commands to provision the components related to this project only.
###############################################################################
#
# Sample Borg config. This is not a complete config. It has objects which are
# specific to Borg only.
#
###############################################################################
#
###############################################################################
# ISUP components
###############################################################################
#
# CA
#
add call-agent id=CA146; tsap-addr-sidea=va-spades.cisco.com; mgw-monitoring-enabled=N;
#
# User part variant
#
add user-part-variant id=ANSISS7_STANDARD; proto-fam=SS7;
#
# SG
#
add sg id=sg1; description=Siganling gateway 1;
add sg id=sg2; description=Siganling gateway 2;
#
# SG group
#
add sg-grp id=sg-grp1; sg1-id=sg1; sg2-id=sg2; description=SG group 1;
#
# SG process
#
add sgp id=sgp1-1 ; sg-id=sg1; description=SG process 1 for sg1;
add sgp id=sgp2-1 ; sg-id=sg2; description=SG process 1 for sg2;
#
# OPC
#
add opc id=opc; point-code=1-1-1; description=OPC;
#
# DPC
#
add dpc id=dpc1; point-code=1-2-1; description=DPC 1;
add dpc id=dpc2; point-code=1-2-2; description=DPC 2;
#
# Routing key
#
add routing-key id=rk1; opc-id=opc; sg-grp-id=sg-grp1; si=ISUP; rc=1; platform-id=CA146;
#
# Call control route
#
add call-ctrl-route id=dpc1-route1; dpc-id=dpc1; routing-key-id=rk1; si=isup; user-part-variant-id=ANSISS7_STANDARD;
add call-ctrl-route id=dpc2-route1; dpc-id=dpc2; routing-key-id=rk1; si=isup; user-part-variant-id=ANSISS7_STANDARD;
#
# SCTP assoc profile
#
add sctp-assoc-profile id=sctp-prof1;
#
# SCTP assoc
#
add sctp-assoc id=sgp1-1-sctp; sgp-id=sgp1-1; sctp-assoc-profile-id=sctp-prof1; platform-id=CA146; remote-port=1111; remote-tsap-addr1=10.10.10.10; remote-tsap-addr2=10.10.20.10; dscp=AF11; ip-tos-precedence=ROUTINE;
add sctp-assoc id=sgp2-1-sctp; sgp-id=sgp2-1; sctp-assoc-profile-id=sctp-prof1; platform-id=CA146; remote-port=1111; remote-tsap-addr1=10.10.30.10; remote-tsap-addr2=10.10.40.10; dscp=AF11; ip-tos-precedence=ROUTINE;
#
# MGW profile
#
add mgw-profile id=as5300-prof; vendor=Cisco; packet-type=IP; mgcp-max2-retries=3; fax-t38-camode-supp=Y; mgcp-keepalive-interval=60; mgcp-keepalive-retries=10; mgcp-t-tran=400; mgcp-max1-retries=2; mgcp-t-longtran=5; mgcp-default-pkg=NONE;
#
# MGW
#
add mgw id=as5300-1; tsap-addr=as5300.cisco.com; call-agent-id=CA146; mgw-profile-id=as5300-prof; type=TGW;
#
# Dial plan profile
#
add dial-plan-profile id=dp-1;
#
# SS7 TG profile
#
add ss7-tg-profile ID=ss7-prof1; mgcp-pkg-type=T;
#
# SS7 TG
#
add trunk-grp ID=1000; call_agent_id=CA146; tg_type=SS7; direction=BOTH; tg_profile_id=ss7-prof1; call-ctrl-route-id=dpc1-route1; dial-plan-id=dp-1; status=INS;
add trunk-grp ID=2000; call_agent_id=CA146; tg_type=SS7; direction=BOTH; tg_profile_id=ss7-prof1; call-ctrl-route-id=dpc2-route1; dial-plan-id=dp-1; status=INS;
#
# Route
#
add route id=dpc1-route1; tg_selection=RR; tgn1_id=1000;
add route id=dpc2-route1; tg_selection=RR; tgn1_id=2000;
#
# Route guide
#
add route-guide id=dpc1-rg1; policy-type=ROUTE; policy-id=dpc1-route1;
add route-guide id=dpc2-rg1; policy-type=ROUTE; policy-id=dpc2-route1;
#
# Destination
#
add destination dest-id=ansi-1000; call-type=LOCAL; route-type=RID; route-id=dpc1-route1;
add destination dest-id=ansi-2000; call-type=LOCAL; route-type=RID; route-id=dpc2-route1;
#
# Dial plan
#
add dial-plan id=dp-1; digit-string=703; reqd-digits=10; dest-id=ansi-1000; noa=NATIONAL;
add dial-plan id=dp-1; digit-string=301; reqd-digits=10; dest-id=ansi-2000; noa=NATIONAL;
#
# Termination
#
add termination prefix=S1/DS1-0/; port-start=1; port-end=24; type=trunk; mgw-id=as5300-1;
add termination prefix=S1/DS1-1/; port-start=1; port-end=24; type=trunk; mgw-id=as5300-1;
#
# Trunk
#
add trunk cic-start=1; cic-end=24; tgn-id=1000; mgw-id=as5300-1; termination-prefix=S1/DS1-0/; termination-port-start=1; termination-port-end=24;
add trunk cic-start=1; cic-end=24; tgn-id=2000; mgw-id=as5300-1; termination-prefix=S1/DS1-1/; termination-port-start=1; termination-port-end=24;
Operations
This section documents operations processes and procedures that are introduced to the Cisco BTS 10200 Softswitch by the SS7 ANSI feature. Refer to the Cisco BTS 10200 Softswitch Operations Manual for Release 3.5 for general information about operations processes for the Cisco BTS 10200 Softswitch.
Traffic Statistics Measurements
The Traffic Management Subsystem provides the following functions:
· Collects statistics
· Clears counters
· Saves 48 hours of statistical data in persistent store
· Displays of summary reports
· Provides on-demand report queries
· Issues events as appropriate
For detailed information about Cisco BTS 10200 Softswitch traffic measurements provisioning and reporting, refer to the Cisco BTS 10200 Softswitch Operations Manual, Release 3.1.
SS7 ANSI implements new traffic statistic measurements (counters) for the following signaling protocols:
•ISUP
•M3UA
•SCCP
•SCTP
•TCAP
•INAP
New ISUP Measurements
Table 2 identifies and describes the signaling gateway based ISUP protocol Call Agent counters implemented by the SS7 ANSI feature.
Table 2 New ISUP Measurements
Measurement
|
Description
|
SGA_CCR_TX
|
The total number of CCR messages sent on the reporting call agent.
|
SGA_CCR_RX
|
The total number of CCR messages received on the reporting call agent.
|
SGA_CFN_TX
|
The total number of CFN messages sent on the reporting call agent.
|
SGA_CFN_RX
|
The total number of CFN messages received on the reporting call agent.
|
SGA_COT_TX
|
The total number of COT messages sent on the reporting call agent.
|
SGA_COT_RX
|
The total number of COT messages received on the reporting call agent.
|
SGA_CQM_TX
|
The total number of CQM messages sent on the reporting call agent.
|
SGA_CQM_RX
|
The total number of CQM messages received on the reporting call agent.
|
SGA_CQR_TX
|
The total number of CQR messages sent on the reporting call agent.
|
SGA_CQR_RX
|
The total number of CQR messages received on the reporting call agent.
|
SGA_CRA_TX
|
The total number of CRA messages sent on the reporting call agent.
|
SGA_CRA_RX
|
The total number of CRA messages received on the reporting call agent.
|
SGA_CRM_TX
|
The total number of CRM messages sent on the reporting call agent.
|
SGA_CRM_RX
|
The total number of CRM messages received on the reporting call agent.
|
SGA_CVR_TX
|
The total number of CVR messages sent on the reporting call agent.
|
SGA_CVR_RX
|
The total number of CVR messages received on the reporting call agent.
|
SGA_CVT_TX
|
The total number of CVT messages sent on the reporting call agent.
|
SGA_CVT_RX
|
The total number of CVT messages received on the reporting call agent.
|
SGA_EXM_TX
|
The total number of EXM messages sent on the reporting call agent.
|
SGA_EXM_RX
|
The total number of EXM messages received on the reporting call agent.
|
SGA_FAC_TX
|
The total number of FAC messages sent on the reporting call agent.
|
SGA_FAC_RX
|
The total number of FAC messages received on the reporting call agent.
|
SGA_FOT_TX
|
The total number of FOT messages sent on the reporting call agent.
|
SGA_FOT_RX
|
The total number of FOT messages received on the reporting call agent.
|
SGA_INF_TX
|
The total number of INF messages sent on the reporting call agent.
|
SGA_INF_RX
|
The total number of INF messages received on the reporting call agent.
|
SGA_INR_TX
|
The total number of INR messages sent on the reporting call agent.
|
SGA_INR_RX
|
The total number of INR messages received on the reporting call agent.
|
SGA_LPA_TX
|
The total number of LPA messages sent on the reporting call agent.
|
SGA_LPA_RX
|
The total number of LPA messages received on the reporting call agent.
|
SGA_PAM_TX
|
The total number of PAM messages sent on the reporting call agent.
|
SGA_PAM_RX
|
The total number of PAM messages received on the reporting call agent.
|
SGA_RES_TX
|
The total number of RES messages sent on the reporting call agent.
|
SGA_RES_RX
|
The total number of RES messages received on the reporting call agent
|
SGA_SUS_TX
|
The total number of SUS messages sent on the reporting call agent.
|
SGA_SUS_RX
|
The total number of SUS messages received on the reporting call agent.
|
SGA_UCIC_TX
|
The total number of UCIC messages sent on the reporting call agent.
|
SGA_UCIC_RX
|
The total number of UCIC messages received on the reporting call agent.
|
SGA_USR_TX
|
The total number of USR messages sent on the reporting call agent.
|
SGA_USR_RX
|
The total number of USR messages received on the reporting call agent.
|
SGA_ABNORMAL_REL_RX
|
The total number of RELs received on the reporting call agentl with a cause other than NORMAL.
|
SGA_UNEXPECT_MSG_RX
|
The total number of unexpected messages received on the reporting call agent.
|
SGA_UNRECOG_MSG_RX
|
The total number of unrecognized messages received on the reporting call agent.
|
M3UA Measurements
Table 3 identifies and describes the M3UA protocol Call Agent and Feature Server counters implemented by the SS7 ANSI feature.
Table 3 M3UA Measurements
Measurement
|
Description
|
M3UA_ERROR_SENT (U32)
|
Number of Error Msg. Sent
|
M3UA_ERROR_RCVD (U32)
|
Number of Error Msg. Received
|
M3UA_NOTIFY_RCVD (U32)
|
Number of Notify Msg. Received
|
M3UA_DUNA_RCVD (U32)
|
Number of Destination Unavailable Msg. Received
|
M3UA_DAVA_RCVD (U32)
|
Number of Destination Available Msg. Received
|
M3UA_DAUD_SENT (U32)
|
Number of Destination State Audit Msg. Sent
|
M3UA_SCON_SENT (U32)
|
Number of SS7 Network Congestion Msg. Sent
|
M3UA_SCON_RCVD (U32)
|
Number of SS7 Network Congestion Msg. Received
|
M3UA_DRST_RCVD (U32)
|
Number of Destination Restricted Msg. Received
|
M3UA_DUPU_RCVD (U32)
|
Number of Destination User Part Unavailable Msg. Received
|
M3UA_UP_SENT (U32)
|
Number of ASP Up Msg. Sent
|
M3UA_UPACK_RCVD (U32)
|
Number of ASP Up Acknowledgement Msg. Received
|
M3UA_DOWN_SENT (U32)
|
Number of ASP Down Msg. Sent
|
M3UA_DOWNACK_RCVD (U32)
|
Number of ASP Down Acknowledgement Msg. Received
|
M3UA_BEAT_SENT (U32)
|
Number of Heart Beat Msg. Sent
|
M3UA_BEAT_RCVD (U32)
|
Number of Heart Beat Msg. Received
|
M3UA_BEATACK_SENT (U32)
|
Number of Heart Beat Acknowledgement Msg. Sent
|
M3UA_BEATACK_RCVD (U32)
|
Number of Heart Beat Acknowledgement Msg. Received
|
M3UA_ACTIVE_SENT (U32)
|
Number of ASP Active Msg. Sent
|
M3UA_ACTIVEACK_RCVD (U32)
|
Number of ASP Active Acknowledgement Msg. Received
|
M3UA_INACTIVE_SENT (U32)
|
Number of ASP Inactive Msg. Sent
|
M3UA_INACTACK_RCVD (U32)
|
Number of ASP Inactive Acknowledgement Msg. Received
|
M3UA_DATA_TRANSFER_SENT (U32)
|
Number of Data Transfer Msg. Sent
|
M3UA_DATA_TRANSFER_RCVD (U32)
|
Number of Data Transfer Msg. received
|
M3UA_DATA_BYTES_SENT (U32)
|
Number of Data Bytes Sent
|
M3UA_DATA_BYTES_RCVD (U32)
|
Number of Data Bytes Received
|
M3UA_INVALID_SCTP_SIG_TOTAL (U32)
|
Total Number of Invalid SCTP Signals
|
M3UA_INVALID_SCTP_SIG_SLR (U32)
|
Number of Invalid SCTP Signals Since Last Reset
|
M3UA_SCTP_ASSOC_FAIL (U32)
|
Number of SCTP Association Failures
|
M3UA_SCTP_SENT_FAIL (U32)
|
Number of SCTP Sent Failures
|
M3UA_XUA_VERSION_ERR (U32)
|
Number of Msg. Received with an invalid version
|
M3UA_XUA_MSG_CLASS_ERR (U32)
|
Number of Msg. Received with an unexpected or unsupported message Class
|
M3UA_XUA_MSG_TYPE_ERR (U32)
|
Number of Msg. Received with an unexpected or unsupported Message Type
|
M3UA_XUA_MSG_LENGTH_ERR (U32)
|
Number of Msg. Received with message Length Errors
|
M3UA_XUA_STREAM_ID_ERR (U32)
|
Number of Message received with Stream ID Error
|
M3UA_XUA_UNEXP_MSG_ERR (U32)
|
Number of Unexpected Msg. Received
|
M3UA_XUA_PROTO_ERR (U32)
|
Number of Message received with Protocol Errors
|
M3UA_XUA_PARAM_VALUE_ERR (U32)
|
Number of Message received with a Parameter Value Error
|
M3UA_XUA_PARAM_FIELD_ERR (U32)
|
Number of Message received with a Parameter Field Error
|
M3UA_XUA_UNEXP_PARAM_ERR (U32)
|
Number of Message received with an Unexpected Parameter Error
|
M3UA_XUA_NTWK_AP_ERR (U32)
|
Number of Message received with a Network Appearance Error
|
M3UA_XUA_RC_ERR (U32)
|
Number of Message received with an invalid Routing Context
|
M3UA_XUA_NO_MEM_FOR_MSG_ERR (U32)
|
Number of Message that were dumped because memory ran out
|
M3UA_XUA_MSG_OTHER_ERR (U32)
|
Number of Message received with Other Errors
|
SCCP Measurements
Table 4 identifies and describes thethe SCCP protocol counters implemented by the SS7 ANSI feature.
Table 4 SCCP Measurements
Measurement
|
Description
|
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
|
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
|
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
|
SCTP Association Measurements
Table 5 identifies and describes the SCTP protocol Call Agent and Feature Server counters implemented by the SS7 ANSI feature.
Table 5 SCTP Association Measurements
Measurement
|
Description
|
SCTP_NUM_RX_DATA_CHNK
|
Number of received data chunks
|
SCTP_NUM_RX_DATA_OUT_SEQ_CHNK
|
Number of out-of-sequence data chunks received
|
SCTP_NUM_RX_DATA_CHNK_ORDERED
|
Number of ordered data chunks received
|
SCTP_NUM_RX_DATA_CHNK_UNORDER
|
Number of un-ordered data chunks received
|
SCTP_NUM_TX_DATA_CHNK
|
Number of data chunks transmitted
|
SCTP_NUM_TX_DATA_CHNK_ORDERED
|
Number of ordered data chunks transmitted
|
SCTP_NUM_TX_DATA_CHNK_UNORDER
|
Number of unordered data chunks transmitted
|
SCTP_NUM_RX_DATA_CHNK_DISCARD
|
Number of received data chunks that were discarded (these were duplicates).
|
SCTP_NUM_TX_DATA_CHNK_RETRANS
|
Number of data chunks that were retransmitted.
|
SCTP_NUM_TX_DATA_CHNK_BUNDLED
|
Number of bundled data chunks that were transmitted
|
SCTP_NUM_RX_DATA_CHNK_BUNDLED
|
Number of bundled data chunks that were received
|
SCTP_NUM_TX_DATA_BYTES
|
Number of data bytes sent over SCTP
|
SCTP_NUM_RX_DATA_BYTES
|
Number of data bytes received over SCTP
|
SCTP_NUM_RX_CTRL_CHNK
|
Number of control chunks received
|
SCTP_NUM_TX_CTRL_CHNK
|
Number of control chunks transmitted
|
SCTP_NUM_TX_DATA_DGRAM
|
Number of "data" datagrams transmitted
|
SCTP_NUM_TX_ULP_DGRAM
|
Number of transmitted ULP datagrams
|
SCTP_NUM_RX_READY_ULP_DGRAM
|
Number of received datagrams that are ready to be sent to upper layer process.
|
SCTP_NUM_RX_ULP_DGRAM
|
Number of received upper layer process datagrams
|
SCTP_NUM_TX_QUED_ULP_DGRAM
|
Number of upper layer process datagrams queued to be transmitted
|
SCTP_NUM_RX_DATA_DGRAM
|
Number of received "data" datagrams
|
SCTP_NUM_RX_INV_DGRAM_LEN
|
Number of datagrams received with invalid length
|
SCTP_NUM_RX_PARTIAL_CHNK
|
Number of times that a partial chunk was received in a datagram.
|
SCTP_NUM_RX_EMPTY_DGRAM
|
Number of empty datagrams received (ones with no chunks).
|
SCTP_NUM_RX_INV_CHKSUM
|
Number of SCTP datagrams received with an invalid checksum
|
SCTP_NUM_RX_INV_BUNDLED_CHNK
|
Number of invalid bundled chunks received (chunk was bundled with an Init, Init Ack or Shutdown Complete chunk).
|
SCTP_NUM_RX_INV_VERIF_TAG
|
Number of datagrams received with an invalid verification tag
|
SCTP_NUM_RX_OUT_OF_BLUE_PKTS
|
Number of "out of the blue" packets received
|
SCTP_NUM_RX_INV_STRM
|
Number of received datagrams with invalid stream Id
|
SCTP_NUM_ASSOC_COMM_LOST
|
Number of time that the SCTP association communication was lost.
|
SCTP_NUM_DEST_ADDR_FAIL
|
Number of times a destination address failed (number of retransmits on this address exceeded maximum path retransmit value).
|
SCTP_NUM_RX_CHNK_UNORDER_ERR
|
Number of unordered chunks that were in error - a chunk that must be first chunk (i.e. Init) was in the incorrect place in a received datagram
|
SCTP_NUM_RX_ECNE_CHNK
|
Number of ECNE chunks received
|
SCTP_NUM_RX_CWR_CHNK
|
Number of CWR chunks received
|
SCTP_NUM_RX_DGRAM_UNKN_CHUNK
|
Number of datagrams received with an unknown chunk type.
|
SCTP_NUM_RX_BAD_INIT_DGRAM
|
Number of Init datagrams received with an unknown parameter
|
SCTP_NUM_RX_INV_COOKIE_SIGS
|
Number of invalid cookie signals received
|
SCTP_NUM_RX_EXPIRED_COOKIE
|
Number of times a cookie echo was received after cookie timer had expired (sending stale cookie error).
|
SCTP_NUM_RX_STALE_COOKIE
|
Other endpoint indicates that cookie echo was received after cookie timer had expired - received an error datagram. (Problem is that the Cookie Echo took too long to cross the network. Next time association is retried, cookie timer will be increased to compensate for network delays.)
|
SCTP_NUM_NO_LISTENING
|
Number of No Listening Messages
|
SCTP_NUM_INV_LINK_TYPE
|
Number of Invalid Link Type
|
SCTP_NUM_PEER_RESTART
|
Number of times that SCTP peer restarted
|
SCTP_NUM_RX_UNORD_DGRAM
|
Number of unordered datagrams received
|
SCTP_NUM_RX_V6_ADDR_PARM
|
Number of packets received with version 6 address parameters.
|
SCTP_NUM_PEERIND_INV_STRM_ERR
|
Number of times SCTP peer reported that it received a data chunk sent to a non-existing stream
|
SCTP_NUM_PEERIND_MISSING_PARM
|
Number of times SCTP peer reported that one or more mandatory TLV parameters are missing in a received INIT or INIT ACK.
|
SCTP_NUM_PEERIND_STALE_COOKIE
|
Number of times SCTP peer reported that it received a valid state cookie that has expired.
|
SCTP_NUM_PEERIND_OUT_OF_RESRC
|
Number of times SCTP peer reported that it is out of resource.
|
SCTP_NUM_PEERIND_UNRESOV_ADDR
|
Number of times SCTP peer reported that it received a packet that has an address that it is unable to resolve.
|
SCTP_NUM_PEERIND_UNREC_CHUNK
|
Number of times SCTP peer reported that it received a chunk that it cannot understand (and the upper bits of the chunk type are set to 01 or 11).
|
SCTP_NUM_PEERIND_INV_PARM
|
Number of times SCTP peer reported that it received an INIT or INIT ACK chunk when one of the mandatory parameters is set to a invalid value.
|
SCTP_NUM_PEERIND_UNRECOG_PARM
|
Number of times SCTP peer reported that it received an INIT ACK chunk that had one or more optional TLV parameters that it did not recognize.
|
SCTP_NUM_PEERIND_NO_USR_DATA
|
Number of times SCTP peer reported that it received a DATA chunk with no user data.
|
SCTP_NUM_PEERIND_SHUT_COOKIE
|
Number of times SCTP peer reported that it received a COOKIE ECHO when it was in SHUTDOWN-ACK-SENT state.
|
SCTP_NUM_RX_CHNK_TOO_SMALL
|
Number of received chunks that were too small
|
SCTP_NUM_RX_CHNK_TOO_BIG
|
Number of received chunks that were too large
|
SCTP_NUM_RX_MISS_PARM
|
Number of times one or more mandatory TLV parameters are missing in a received INIT or INIT ACK chunks.
|
SCTP_NUM_DGRAM_DRP_NO_SPACE
|
Number of datagrams dropped because no room in local receive window
|
TCAP Measurements
Table 6 identifies and describes the TCAP protocol Call Agent and Feature Server counters implemented by the SS7 ANSI feature.
Table 6 TCAP Measurements
Measurement
|
Description
|
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
|
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
|
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
|
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
|
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
|
INAP Measurements
Table 7 identifies and describes the INAP protocol Call Agent and Feature Server counters implemented by the SS7 ANSI feature.
Table 7 INAP Measurements
Measurement
|
Description
|
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
|
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
|
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
|
For further information about provisioning and displaying the current measurement settings, refer to the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide , Software Releases 3.2, 3.3 and 3.5.
SS7 ANSI ISUP Trunk Reasons
The following new trunk-reasons have been introduced by the implementation of the SS7 ANSI feature:
- BLK_LOC_UPU
- DES_LOC_UPU
- DES_LOC_MML
- DES_LOC_FORCE
- DES_LOC_SIG
- DES_LOC_GRACE
- JOB_PENDING
- ACT_LOC_STOP
- ACT_LOC_COTTEST
- ACT_LOC_VALIDATE
- ACT_LOC_UPU
- ACT_LOC_QUERY
- ACT_LOC_MML_RESET
- ACT_LOC_INIT_RESET
Troubleshooting
This section describes troubleshooting problems introduced by the SS7 ANSI feature. For information about troubleshooting problems with the Cisco BTS 10200 Softswitch, refer to the Cisco BTS 10200 Softswitch Operations Manual, Release 3.5.
MDL Protocol Tracing
Overview
In addition to existing BTS trace capabilities, you can now invoke a new kind of trace, MDL protocol tracing, to track ANSI ISUP message processing at various levels of detail. MDL protocol tracing records the ANSI ISUP protocol processing at any time during call processing.
The new protocol tracing commands provide the ability to turn MDL tracing on and off for a trunk group, circuit, or set of circuits. Tracing can be either conditional or unconditional.
Conditional tracing is turned on for an entire trunk group when a specified bit pattern, as a Hex string, is detected in an incoming or outgoing message. The trace stays on for the default 5 minutes or until after an optional time specified in the command, when the trace is automatically deactivated.
Unconditional tracing records activity on a trunk group, a specific circuit, or a range of circuits and begins when the trace is turned on with the CLI command. As with conditional tracing, the trace is automatically deactivated after an optionally specified period of time or after the default 5 minute time period.
Only one trace can be running on a circuit at a time. If a trace command is issued for a circuit that is already being traced, and a stop-trace command has not been issued on the first trace prior to issuing a second start-trace command on the same circuit, the second start-trace command will be ignored.
Caution The BTS response to a second start ss7-trace CLI command issued on the same CIC will indicate success, but the trace output will continue to be added to the file specified in the first start-ss7trace command. To be sure you capture the necessary information, it is important to avoid specifying overlapping circuit ranges.
Refer to the Cisco BTS 10200 Softswitch Operations Manual, Release 3.5, for more information about existing trace mechanisms.
Start MDL Trace
Use a CLI command similar to the following to turn on an MDLtrace. The example includes the expected CLI response to the command.
cli>start ss7-trace tgn-id=4;cic=424;file-prefix=trace_test
FILENAME -> trace_test_20021217105415
REASON -> ADM executed successfully
RESULT -> ADM configure result in success
TRACE STATUS -> SS7-TRACE successful
Table 8 describes valid mandatory and optional arguments to the start ss7-trace command.
Note Mandatory arguments are marked by an asterisk.
Table 8
Argument
|
Description
|
* tgn-id
|
Trunk group ID of the pre-existing trunk group on which to turn on the trace. Conditional tracing can only be issued for a complete trunk group.
|
* file-prefix
|
Prefix for the trace file; maximum of 16 characters. The system appends a date and time stamp to this file name prefix to avoid duplicate file names. The complete file name is returned in the CLI response to the start ss7-trace command, as in the example above.
Note The default location for MDL trace files is /opt/OptiCall/CAxxx/mdltrace, where CAxxx is the identifier for the Call Agent, for example, CA146.
|
trace-time
|
Indicates the length of time that the trace will be turned on.
|
cic
|
Circuit identifier. You can specify a single CIC or a range of CICs in an unconditional trace. If this argument is omitted, tracing will be applied to all circuits in the trunk group.
Note This is not a valid argument for a conditional trace and should not be used when a bit-pattern is specified.
|
bit-pattern
|
The Hex bit pattern which, when encountered in an incoming or outgoing message on the trunk group, will turn on a conditional mdl trace. Maximum bit-pattern length is 32 Hex digits.
|
Start Trace Command Arguments
Stop MDL Trace
Use a CLI command similar to the following to turn off an MDL trace.
cli>stop ss7-trace tgn-id=4;file-name=trace_test_20021217105415
REASON -> ADM executed successful
RESULT -> ADM configure result in success
TRACE STATUS -> SS7-TRACE successful
Note The filename is a mandatory parameter to the stop ss7-trace command.
Events and Alarms
Protocol states maintained in the SS7 layers are traceable through log and alarm events. The SS7 ANSI feature implements the following new alarms:
SIGNALING #4
Invalid message received.
Level
WARN
Threshold/Throttle
100 / 0
Data Reported
endpoint name (40), message type (40)
Probable Cause
Issued when a signaling adapter has received an invalid message from the specified endpoint.
Corrective Action
Monitor the associated signaling link to see if there is an interruption of service on the link. If there is a communication problem, restart the link.
Verify that the version of the protocol used by the device at the endpoint is consistent with the version expected by the Call Agent. If there is a mismatch, then either the endpoint or Call Agent must be reprovisioned.
SIGNALING #109 SCTP Association Failure
Cannot communicate over an SCTP association due to a failure.
Level: MAJOR
Threshold/Throttle:100 / 0
Data Reported: SCTP Association ID(17)
Probable Cause:
•Ethernet cables on SGP are unplugged or severed.
•SGP is not operational.
Corrective Action:
•Plug Ethernet cables in or fix severed connection.
•Check SGP alarms to determine why it is not operating properly.
SIGNALING #110 Signaling Gateway Group is out-of-service
Cannot communicate between the CA and SGs.
Level: Critical
Threshold/Throttle:100 / 0
Data Reported: SG Group ID - STRING [17]
Probable Cause:
•All SCTP Associations between CA and SGs are out-of-service.
•The M3UA layer is down between the CA and SGs.
Corrective Action:
•Make sure all Ethernet connections on the CA and SGs are plugged in. Also make sure all associated IP routers are operational.
•Use Cisco Snooper application to determine why the M3UA layer is down.
SIGNALING #111 SCTP Association Degraded (one of two IP connections down).
Cannot communicate over an SCTP association due to a failure.
Level: Major
Threshold/Throttle: 100/0
Data Reported: SCTP Association ID(17), Destination IP Address(11)
Probable Cause:
•Single Ethernet connection on CA or SGP is unplugged or severed.
•SCTP communication problem - protocol timeout.
Corrective Action:
•Plug in all Ethernet connections or repair if severed.
•Use Cisco Snooper application to determine why SCTP association is degraded.
SIGNALING #112 SCTP Association Configuration Error
Level: Minor
Threshold/Throttle: 100/0
Data Reported: SCTP Association ID(17)
Probable Cause:
•Destination IP address is invalid
•Local IP address is invalid
•IP Routing Table is not configured properly.
Corrective Action:
•Input new destination IP address - see log for additional details
•Input new Local IP address information
•Have System Administrator configure IP routing table
SIGNALING #113 Signaling Gateway Failure
Level: Major
Threshold/Throttle: 100/0
Data Reported: Signaling Gateway ID(17)
Probable Cause: All associated Signaling Gateway Processes are out-of-service.
Corrective Action: Determine why each associated Signaling Gateway Process is out-of-service (see SGP alarm definition).
SIGNALING #114 Signaling Gateway Process is out-of-service
Level: Major
Threshold/Throttle: 100/0
Data Reported: Signaling Gateway Process - STRING [17]
Probable Cause:
•All SCTP associations between the SGP and the CA are out-of-service.
•The M3UA layer is down between the CA and SGP.
Corrective Action:
•See SCTP Association Alarm definition to determine how to rectify the problem.
•Use Cisco Snooper utility to determine why M3UA layer is down. Also see log for additional information.
SIGNALING #115 Invalid Routing Context Received
Level: Warning
Threshold/Throttle: 100/0
Data Reported:
•invalid routing cont - FOUR_BYTES
•SG from which the in - STRING [17]
Probable Cause: routing context was configured improperly on CA or SG
Corrective Action: Reconfigure routing context on CA or SG so that they match in both places.
SIGNALING #123 Destination Point Code is unavailable
Level: Minor
Threshold/Throttle: 100/0
Data Reported:
Destination Point Co - STRING [20]
Probable Cause: Link loss or DPC equipment out of service.
SIGNALING #124 Remote subsystem is out of service.
Level: Minor
Threshold/Throttle: 100/0
Data Reported:
•Destination Point Co - STRING [20]
•Remote Subsystem Num - ONE_BYTE
Probable Cause: Link loss or the remote subsystem out of service.
SIGNALING #125 SCCP routing error
Level: Major
Threshold/Throttle: 100/0
Data Reported:
Probable Cause:SCCP route invalid or not available.
Corrective Action:Provision the right SCCP route.
SIGNALING #126 SCCP Binding Failure
Level: Major
Threshold/Throttle: 100/0
Data Reported:
•Local Point Code - STRING [20]
•Local Subsystem Number - ONE_BYTE
Probable Cause: Trillium stack binding failure
Corrective Action: Reinitialize the TSA process or remove the subsystem from the EMS table and add it again.
SIGNALING #127 TCAP Binding Failure
Level: Major
Threshold/Throttle: 100/0
Data Reported:
Probable Cause: Trillium stack binding failure
Corrective Action: Reinitialize the TSA process or remove the subsystem from the EMS table and add it again.
SIGNALING #128 INAP Binding Failure
Level: Major
Threshold/Throttle: 100/0
Data Reported:
•Local Point Code - STRING [20]
•Local Subsystem Numb - ONE_BYTE
Probable Cause: Trillium stack binding failure
Corrective Action: Reinitialize the TSA process or remove the subsystem from the EMS table and add it again.
SIGNALING #131 INAP reaches the provisioned resource limit.
Level: Warning
Threshold/Throttle: 100/0
Data Reported: Dialogue/Invoke ID - ONE_BYTE
Probable Cause: INAP runs out of all the preconfigured dialogue ids or invoke ids.
Corrective Action: Switch over and add number of dialogue ids and invoke ids in the stack configuration file.
SIGNALING #132 TCAP reaches the provisioned resource limit.
Level: Warning
Threshold/Throttle: 100/0
Data Reported: Dialogue/Invoke ID - ONE_BYTE
Probable Cause: TCAP runs out of all the preconfigured dialogue ids or invoke ids.
Additional References
For additional information related to the Cisco BTS 10200 Softswitch, refer to http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/index.htm and to the following documents:
Related Documents
Related Topic
|
Document Title
|
Cisco BTS 10200 Softswitch
|
Cisco BTS 10200 Softswitch System Description for Release 3.1
|
Cisco BTS 10200 Softswitch objects, tokens, and CLI commands
|
Cisco BTS 10200 Softswitch Release 3.2, 3.3, and 3.5Command Reference Guide
|
Cisco BTS 10200 Softswitch operations, maintenance, and troubleshooting
|
Cisco BTS 10200 Softswitch Operations Manual for Release 3.5
|
Cisco BTS 10200 Softswitch events and alarms
|
Cisco BTS 10200 Softswitch Error Messages and Alarms Reference Guide
|
For additional information related to SS7 ANSI ISUP, refer to the following documents:
Standards
|
|
Title
|
ANSI T1.113
|
Telecommunications Signaling System No. 7 (SS7)- Integrated Services Digital Network (ISDN) User Part (ISUP)
|
GR-317-CORE
|
Switching System Requirements for Call Control Using the Integrated Services Digital Network User Part
|
GR-394-CORE
|
Switching System Generic Requirements for Interexchange Carrier Interconnection using the Integrated Services Digital Network User Part,
|
GR-533-CORE
|
LSSGR: Database Services Service Switching Points - Toll-Free Service
|
GR-1188-CORE
|
LSSGR: CLASS Feature: Calling Name Delivery Generic Requirements
|
RFCs
|
|
Title
|
[RF1] draft-ietf-sigtran-m3ua-11.txt
|
SS7 MTP3-User Adaptation Layer (M3UA)
|
RFC2960
|
Stream Control Transport Protocol (SCTP)
|
(IETF Draft Version 14)
|
Signalling Connection Control Part User Adaptation Layer (SUA)
|
IETF RFC-3332
|
Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)
|
Technical Assistance
Description
|
Link
|
Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, tools, and lots more. Registered Cisco.com users can log in from this page to access even more content.
|
http://www.cisco.com/public/support/tac/home.shtml
|
Feedback
