-
Cisco IOS XR Session Border Controller Configuration Guide Release 3.6
-
About This Guide
-
About SBC Deployment Models
-
SBC Configuration Prerequisites
-
Implementing SBC Adjacencies
-
Configuring SIP Method Profiles
-
Configuring Header Profiles
-
Restricting Codecs
-
SIP Tel URI Support
-
SIP Timer
-
H.323 Support
-
H.323-SIP Interworking
-
Implementing SBC Policies
-
Tracking Policy Failure Statistics
-
Implementing SBC Firewall Traversal and NAT
-
Implementing SBC Interworking DTMF
-
SIP 3xx Redirect Responses
-
SIP Call Hold
-
SIP Call Transfer
-
Encrypted SIP Signaling
-
SIP Outbound Authentication
-
SIP Inbound Authentication
-
SIP-I Transparency and Profile Support
-
SIP Configuration Flexibility
-
Implementing SBC QoS (Marking)
-
DoS Prevention and Dynamic Blacklisting
-
Unexpected Source Address Alerting
-
Implementing SBC Billing
-
Implementing SBC Redundancy (High Availability)
-
Implementing SBC Multi-VRF
-
Implementing SBC Transcoding
-
Configuring DBE Overload Reporting
-
Media Address Pools
-
Early Media
-
Fax Support
-
Nine-Tier Termination Name Hierarchy
-
Multiple Streams in a H.248.1 v3 Termination
-
DBE Signaling Pinhole Support
-
IPv6 Support on the DBE
-
Extension of H.248 Termination Wildcarding
-
Optional H.248 Ginfo Package
-
H.248.1 v3 Support
-
H.248 Traffic Management (Tman)
-
Context Attribute Descriptor Support
-
H.248 Historical Event Notification
-
H.248 Segmentation Package Support
-
H.248 Configurable T-Max
-
H.248 Configurable VRF
-
Implementing H.248 nt/qualert Events
-
H.248 Gateway Profile Configuration
-
Interim Authentication Header Support
-
IP NAPT Traversal Support
-
MGC-Controlled Gateway-Wide Properties
-
MGC-Specified Local Addresses and Ports
-
Optional Local and Remote Descriptors
-
Provisioned Inactivity Timer
-
Disabling RTP Flows
-
Discarded Packet Statistics
-
IPv4/IPv6 Voice Clipping Avoidance
-
Secure Media Support
-
RADIUS VPN Support
-
Configurable Base Root Package
-
MGC Information Package Support
-
Ia Profile Support
-
Integration of Resource Management and SIP
-
P-CSCF Support
-
IBCF Processing Support
-
End-to-End SBC Configuration Example on a Cisco XR 12000 Series Router
-
Additional Information about Billing Support
-
Index
-
Table Of Contents
H.248 Traffic Management (Tman)
Explicit Leaky Bucket Parameters
H.248 Traffic Management (Tman)
Traffic Management (Tman) package allows a media gateway controller (MGC) to use the Tman property in the H.248 message to provide the appropriate policy limits. The media gateway (MG), in turn, imposes these policy limits on the flow. By default, the DBE calculates its flow policing based on the codec information carried in the SDP (applicable for voice and video calls).
The Tman feature allows MGC to over-ride this calculation and specify the parameters explicitly. This is done using the sustainable data rate (tman/sdr) and maximum burst size (tman/mbs) fields. It is now possible to support different Tman properties in the two terminations in a stream, and do asymmetric traffic policing.
The following Tman properties are supported: pol (Policing), sdr (Sustainable Data Rate), mbs (Maximum Burst Rate), pdr (Peak Data Rate), and dvt (Delay Variation Tolerance).
Note
The SBC can asymmetrically police the flows. Tman properties may be assigned to both media and signaling flows (per termination / stream).
Feature History for H.248 Tman
Contents
This module contains the following sections:
Restrictions for H.248 Tman
•
•
•
–
–
Information About H.248 Tman
DBE reports support for the Tman package during the initial auditing. The supported fields (pol, sdr, pdr, mbs and dvt) are used, if present, on Megaco Add and Modify requests. If Tman fields are defined using Add and Modify, they are returned on subsequent responses to Megaco Audit requests.
If tman/pol has a value FALSE, the DBE interprets it as "do not police traffic flow". This does not mean that the DBE accepts the call regardless of available bandwidth. The DBE still calculates the expected bandwidth based on TMAN sdr and mbs, if available, or the Session Description Protocol (SDP), and may fail the call if it finds the bandwidth insufficient. However, after determining that sufficient bandwidth is available, the DBE does not police traffic usage for this flow.
If you do not specify any Tman properties, the MGC calculates the required bandwidth of the media flow from the Session Description Protocol (SDP) in the local descriptor.
If tman/pol is present and has a value TRUE, the DBE does not require tman/sdr and tman/mbs to be present. If either tman/sdr or tman/mbs is present, then the other must be present as well, but the absence of both is permissible. The DBE polices traffic based on the sdr/mbs parameters or SDP as appropriate.
Explicit Policing
The tman/pol flag allows an MGC to indicate to an MG that it does not want any policing of a stream to occur. This is signaled by overriding the implicit default value of ON and setting a value of OFF on the given stream.
Explicit Leaky Bucket Parameters
By default, DBE calculates its flow-policing leaky-bucket parameters from the codec information carried in the SDP. This feature allows an MGC to override this calculation and specify which parameters to use directly. This is done using the sustainable data rate (tman/sdr) and maximum burst size (tman/mbs) fields.
Note
Since DBE tracks total packet rate as well as total bandwidth, it needs to translate the bandwidth parameters provided by the Tman package into packet rates. It does this by assuming a packetization of 10ms. This applies to both signaling and media pinholes.
Peak Data Rate
The Tman package allows an additional flow-policing parameter to be specified: the peak data rate (pdr). The pdr defines the peak data rate in bytes per second that is permitted for the stream. The DBE polices the flow to make sure it does not exceed the pdr value. The range for the pdr value is 0 through 4294967295.
Asymmetric Policing
The flexibility added by the Tman package means allows MGCs to impose different flow policing on traffic traveling in different directions on the same stream. For example, MGCs could police traffic flowing from an end-point to an internal server via the SBC, but not the reverse flow, since this flow is coming from a trusted source.
Delay Variation Tolerance
Delay Variation Tolerance (dvt) defines the delay variation tolerance for the stream in tenths of microseconds when enforcing the PDR value in the first leaky bucket. The DBE polices the dvt value in the stream and drops the packet if it exceeds tolerance value. The range for tolerance (dvt) value is 0 through 4294967295.
Note
Additional References
The following sections provide references related to H.248 Tman.
Related Documents
Standards
No new or modified standards are supported by this feature, and support from existing standards has not been modified by this feature.
—
MIBs
—
To locate and download MIBs using Cisco IOS XR software, use the Cisco MIB Locator found at the following URL and choose a platform under the Cisco Access Products menu:
Technical Assistance
