Cisco Systems ASR 1000 manual Multi-Stream Terminations, Nine-Tier Termination Name Hierarchy

Page 71

Chapter 7 H.248 Services—Signaling and Control

Multi-Stream Terminations

•Requested address or port is already in use by another flow, or was in use by a recently deleted flow. Megaco error 510 “Insufficient Resources.”

DBE Restrictions

The following are restrictions of DBE support for this feature:

•The addresses and ports specified must fall within a valid address or port range configured on the DBE, and not marked as “MGC-managed.”

•The class of service of the port range must match the type of flow being allocated.

•Real-time Transport Protocol (RTP) flows cannot be set up to use odd-numbered ports.

Multi-Stream Terminations

This enhancement allows a single H.248 termination to contain multiple streams. Previously, only a single stream for each termination was allowed, which meant that multi-stream calls needed to be signaled using multiple pairs of terminations. This enhancement supports the new H.248.1v3 syntax in which several streams can occupy the same termination.

DBE Restrictions

The following is a restriction of DBE support for this feature:

•Auditing of per-stream statistics is only supported when using H.248.1v3. This is a restriction of the H.248 protocol.

Nine-Tier Termination Name Hierarchy

The Nine-Tier Termination Name Hierarchy feature adds support for a nine-tier termination name schema, where the multi-tier prefix is supplied by the media gateway controller (MGC), and the final element, the channel ID, is generated by the media gateway (MG). All MGCs that the MG is configured to contact must use the same termination name schema. A termination is the point of entry or exit of media flows relative to the MG. The MG understands how the flows entering and leaving each termination are related to each other.

This feature plays an important role in identifying the company, transaction service (such as voice or video), and termination attributes (such as access, backbone, etc.).

Restrictions for Nine-Tier Termination Name Hierarchy

•Only the final element may contain the CHOOSE ($) wildcard. The DBE will not extract any meaning from any elements of the termination ID. The exception: “ * “ is reserved for wildcard notation.

•Multi-tier prefixes can be less than nine tiers, but must have the same depth.

Cisco IOS XE Integrated Session Border Controller Configuration Guide for the Cisco ASR 1000 Series Aggregation Services Routers

 

OL-15421-01

7-7

 

 

 

Page 70 Page 72
Image 71
Page 70 Page 72
Contents Americas Headquarters Page Iii N T E N T SQoS Bandwidth Allocation Traffic Management Package Support Local Source Properties Address and Port Vii IPv6 SupportEvents Storage Until Event Acknowledgment OL-15421-01 May 5 This document was first published PrefaceDocument Revision History ObjectivesOrganization Intended AudienceCisco IOS Release 12.2SR Software Publications Related DocumentationDocument Conventions Cisco ASR 1000 Series Router DocumentationXii Xiii Obtaining Documentation and Submitting a Service RequestXiv General Overview ContentsCisco ASR 1000 Series Routers Overview Example of SBC High Level Architecture Distributed and Unified ModelsOn page 1-3illustrates the unified model Release Feature Name Related SBC Commands Documented Supported Integrated Session Border Controller FeaturesPackage segment XE Release Cisco IOS Logging Level in ConfiguringCisco IOS NoneMedia-address ipv4 Deployment of the Integrated Session Border Controller Transaction-pending commandIntegrated SBC Used for VoIP Interworking Integrated Session Border Controller DBE Deployment Scenario Restrictions for Integrated Session Border Controller Configuring Integrated Session Border ControllerPrerequisites for Integrated Session Border Controller Summary Steps PrerequisitesEnters into interface configuration mode Enables privileged Exec modeEnter your password if prompted Enters global configuration modeController H.248 configuration mode Configures the DBE to use a specific IPv4 H.248 controlOwn address when connecting to the SBE Configures the H.248 controller for the DBE and enters intoExamples Troubleshooting TipsWhat To Do Next Configuring H.248 Logging Level Messages sent and received. Turns on console Creates the DBE service on the SBC and enters intoSBC-DBE configuration mode Sets a specified logging level to generate detailed logsEnabling H.248 Logging Requests and Responses Example H.248 Log Output Configuration ExamplesThis section provides the following configuration examples SBC DBE Configuration Steps Example Making Global Changes to Controllers Example == Make change to local port Following example shows the initial SBC configurationControl-address h248 ipv4 172.25.2.26 controller h248 Making Changes to Individual Controller Settings ExampleOverview of Profile Topology Priority Indicator Yes Emergency IndicatorIeps Indicator Yes Cisco H.248 ProfilePackage ID Version Profile PackagesPackage ID Version Support Dependent On Information About Dtmf Interworking Dtmf InterworkingSIP to RTP Interworking Configuring Default Duration of a Dtmf EventRTP to SIP Interworking Configures the default duration of a Dtmf event Enters the mode of a DBE service and enters into SBC-DBEConfiguration mode. Use the sbc-name argument to specify Name of the DBE servicePage Prerequisites for Implementing Media Address Pools Restrictions for Configuring Media Address PoolsMedia Address Pools Information About Media Address Pools Configuring Media Address PoolsCreates a port range for the configured media Is configuredEnters into SBC-DBE configuration mode Configuration modeConfiguring Media Address Pools Example Traffic Management Package Support Quality of Service and Bandwidth ManagementPage Parameters on AC and per SDP on Dscp Marking and IP Precedence MarkingDscp Re-Markings Rtcp Policing Rtcp Policing Using Tman PackageRtcp Policing Not Using Tman Package QoS Bandwidth AllocationImplementing Two-Rate Three-Color Policing and Marking Two-Rate Three-Color Policing and MarkingEnabling Two-Rate Three-Color Policing and Marking DBE Restrictions Related Commands Page Enabling Optional H.248 Packages Packages-Signaling and ControlSegmentation Package Support Address Reporting PackageSession Failure Reaction Package Termination State Control Package Tsc-quiesce FeatureTsc-suspend Feature Vlan Package Syntax-Level Support 248.1v3 SupportMGC-Controlled Gateway-Wide Properties Page Services-Signaling and Control DBE Signaling Pinhole Support Extension to H.248 Termination Wildcarding Support Extension to H.248 Audit SupportFlexible Address Prefix Provisioning No Napt Pinhole Hairpinning Local Source Properties Address and PortLocally Hairpinned Sessions Twice Napt Pinhole HairpinningMGC-Specified Local Addresses or Ports Restrictions for Nine-Tier Termination Name Hierarchy Multi-Stream TerminationsNine-Tier Termination Name Hierarchy Displaying the Nine-Tier Termination Name Hierarchy Information About Nine-Tier Termination Name HierarchyAbc/voice/gn/0/1/0/1/ac/3 Displaying the Nine-Tier Termination Name Hierarchy ExampleOptional Local and Remote Descriptors RTP Specific Behavior Support ServiceChange Notification for Interface Status ChangeRemote Source Address Mask Filtering Sbc interface-id value End Configuration Example Output Video on Demand VOD Support MAX TimerTsc-Delay Timer Tmax-timercommand configures the value of the T-MAX timerServices-Signaling and Control Video on Demand VOD Support Services-Signaling and Control Video on Demand VOD Support Integrated Session Border Controller Security Firewall Media Pinhole Control Latch and Relatch Support Interim Authentication Header SupportLocal Source Properties Address and Port Etsi TS 102 333 version 1.1.2 Gate Management Package Napt and NAT TraversalTraffic Management Policing Topology HidingTopology Hiding IPv6 Inter-Subscriber Blocking IPv4 Twice NaptRouter# show run interface gigabitEthernet 0/1.1101 QoS Policy-Map-Based Inter-Subscriber Blocking MethodRouter# show class-map IPv6intersubscriber ACL-Based Inter-Subscriber Blocking Method IPv6 SupportIPv6 No Napt Support for Media Flows IPv6 PinholesSend Recv IPv6 Single Napt for SignalingSingle Napt Signaling Flow No Napt Pinholes Topology Hiding No Napt Pinholes 10-1 High Availability SupportIntegrated Session Border Controller High Availability 10-2 Hardware RedundancySoftware Redundancy Route Processor Redundancy RPR10-3 SSO SupportIssu Support High Availability Support Issu Support 10-411-1 Quality Monitoring and Statistics GatheringEnhanced Event Notification and Auditing Congestion-threshold CommandBilling and Call Detail Records DBE Status Notification11-3 Retention and Returning of H.248 Event Information11-4 Association ResetResetting the Media Timeout Timers Silent Gate Deletion11-5 Middlebox Pinhole Timer Expired EventNetwork Package Quality Alert Event 11-6 Provisioned Inactivity TimerRelated Command IN-1 IN-2 IN-3 IN-4 Pinhole Pinhole timeoutPolicing Asymmetric policing Ipv6 packets RTP specific behavior support SBEIN-5 IN-6
Top Page Image Contents