-
Cisco Unified Border Element (SP Edition) Configuration Guide: Unified Model
-
Preface
-
Part 1: Basics
-
Using the Command-Line Interface in Cisco IOS XE Software
-
Cisco Unified Border Element (SP Edition) Overview
-
Configuring Cisco Unified Border Element (SP Edition)
-
Media Address Pools
-
Implementing Multi-VRF
-
Implementing Adjacencies
-
Implementing Policies
-
Implementing Firewall Traversal and NAT
-
Call Duration Monitoring
-
IP Realm
-
Managing Emergency Calls
-
- Part 2: Security
- Part 3: Dual Tone Multifrequency (DTMF)
- Part 4: Redundancy-High Availability
- Part 5: Media
- Part 6: Session Initiation Protocol (SIP)
- Part 7: H.323
- Part 8: Billing
- Part 9: Secure Real-Time Transport Protocol (SRTP)
- Part 10: Quality of Service (QoS)
- Part 11: Transcoding
- Part 12: Management and Operations
- Part 13: Service
- Part 14: IPv6
- Part 15: IP Multimedia Subsystem (IMS)
- Part 16: CALEA IRI Interface Support
- Part 17: H.248
- Appendix
-
Glossary
-
Feedback
Table Of Contents
Tracking Policy Failure Statistics
Restrictions for Tracking Call Policy Failure Statistics
Information About Policy Failure Statistics
Policy Failure Statistics for a Specified Time Interval
Policy Set and Per-Entry Statistics
Automatic Tracking of Policy Failure Statistics
Policy Failure Statistics and Hunting
Global Statistics and Call Hunting
Per-table and Per-entry Statistics and Call Hunting
Per-adjacency and Per-Account Statistics and Call Hunting
Tracking Policy Failure Statistics
Users can track the number of calls that Cisco Unified Border Element (SP Edition) rejected based on the rules established in the number analysis policies, routing policies, or Call Admission Control (CAC) policies. Users can also view and query the policy failure statistics associated with these rejected calls, which can help them determine whether changes need to be made to the existing policies.
Cisco Unified Border Element (SP Edition) was formerly known as Integrated Session Border Controller and may be commonly referred to in this document as the session border controller (SBC).
For a complete description of the commands used in this chapter, refer to the Cisco Unified Border Element (SP Edition) Command Reference: Unified Model at:
http://www.cisco.com/en/US/docs/ios/sbc/command/reference/sbcu_book.html.
For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or a Cisco IOS master commands list.
Note
For Cisco IOS XE Release 2.4, this feature is supported in the unified model only.
Feature History for Policy Failure Statistics
Cisco IOS XE Release 2.4
This feature was introduced on the Cisco IOS XR along with support for the unified model.
Contents
This module contains the following sections:
•
•
Restrictions for Tracking Call Policy Failure Statistics
Review the following restrictions for policy failure statistics:
•
•
Information About Policy Failure Statistics
The section provides information on the following:
•
•
•
•
Policy Failure Statistics for a Specified Time Interval
Table 52 lists the command to view and clear the failure statistics on the specified signaling border element (SBE) for a certain time interval.
Table 52 Commands for Time-Based Policy Failure Statistics
clear sbc service-name sbe policy-failure-stats
Clears the policy failure statistics for the current and previous time interval.
Policy Set and Per-Entry Statistics
To determine whether calls failed due to policies configured in the routing, number validation, or CAC tables, users can view the policy failure statistics for a specific policy table or table entry. Table 53 lists the commands to view and clear the statistics on policy tables associated with a policy set.
Table 54 lists the commands to view the detailed information for a specific entry in a CAC policy table and routing table.
Automatic Tracking of Policy Failure Statistics
Cisco Unified Border Element (SP Edition) automatically tracks policy failure statistics for call attribute sets representing the following:
•
•
•
•
Table 55 lists the commands to view and clear automatically tracked policy failure statistics.
The statistics are collected at 5 minute intervals past the hour (that is, at 0, 5, 10, 15 minutes, and so on past the hour). For example, the periods covered by the various buckets at 12:43 would be as follows:
•
•
•
•
•
•
•
•
A counter can keep increasing. It keeps a count of events that have completed. When reporting the value of a counter, it's the sum total of events that happened in the period. Some examples of counters are total call attempts, failed call attempts, and active call failures.
A gauge is a counter that can go up and down. It typically tells you how many of something there are now. When reporting the value of a gauge, it's either the current value, or when measured over a longer time period, it's the average value during the period. Some examples of gauges are active calls, activating calls, and deactivating calls.
Policy Failure Statistics and Hunting
If the CAC module refuses a call or if a call cannot be signaled to the chosen destination adjacency because of a negative or no response, call hunting occurs. Call hunting is the process of selecting an alternative adjacency from the routing tables and retrying the call using the newly selected destination adjacency.
Hunting continues until one of the following conditions is fulfilled:
•
•
•
Global Statistics and Call Hunting
If a call gets connected after hunting, Cisco Unified Border Element (SP Edition) does not include it in any of the following global statistics:
•
•
•
•
•
•
•
•
If a call fails after number analysis, hunting does not occur. Cisco Unified Border Element (SP Edition) includes it in the following global statistics:
•
•
If a call fails the first time it is routed because no destination adjacency is found in the routing table, then Cisco Unified Border Element (SP Edition) includes it in the following global statistics:
•
•
If a call fails because a CAC policy refused it permission to proceed, Cisco Unified Border Element (SP Edition) includes the failure in the total call setups failed due to CAC statistics. Additionally, the call is included in one of the following statistics depending on the nature of the CAC limit:
•
•
•
•
Per-table and Per-entry Statistics and Call Hunting
If a call undergoes N iterations of hunting, then it traverses the number analysis tables once, and the routing and the CAC tables N times. But the CAC tables can reject the call each time it traverses the CAC table. For each time the CAC table rejects the call, Cisco Unified Border Element (SP Edition) finds the table and entry that was responsible for setting the CAC limit, and increments the following:
•
•
Per-adjacency and Per-Account Statistics and Call Hunting
If a call gets connected after hunting, Cisco Unified Border Element (SP Edition) does not include it in the following per-account or per-adjacency statistics:
•
•
•
•
•
•
If a call fails due to number analysis, then hunting does not occur and Cisco Unified Border Element (SP Edition) includes the call in the following per-account and per-source adjacency statistics:
•
•
If a call fails in the routing tables before hunting occurs, Cisco Unified Border Element (SP Edition) includes the call in the following per-source account and per-source-adjacency statistics:
•
•
A call included in the total call setup failures statistics is included in the per-source adjacency, per-destination-adjacency, per-source-account adjacency, and per-destination account statistics. Additionally, if the most recent hunting attempt failed because a CAC policy refused the call permission to proceed, Cisco Unified Border Element (SP Edition) includes the failure in the total call setups failed due to CAC statistics in the per-source-adjacency, per-destination-adjacency, per-source-account, and per-destination-account statistics. The call is also included in one of the following statistics depending on the nature of the CAC limit depending on the nature of the CAC limit:
•
•
•
•
