Downloads |
Table Of Contents
Cisco PGW 2200 Softswitch H.248 Protocol-Phase 2 Feature Module
Understanding the H.248 Protocol-Phase 2 Feature
Effects of the AnchorMedia Property on a Gateway
Setting Trunk Group Properties for Media Anchoring
Selecting a Gateway Pool for Announcements
Gateway Pool Support for Playing Tone
Gateway Pool Support for DTMF Interworking
Selecting a Gateway Pool for Codec Interworking
Selecting a Border Gateway Through an MDL Engine Interface
Ringback Tone Support for an IP-to-IP Gateway
Codec Selection for IP Gateway-to-IP Gateway Calls
H.248 Protocol Package Support
ETSI NAT Traversal and IP NAPT Traversal Package Support
Enhanced VPN Discrimination Package Support
H.248-Phase 2 Feature Restrictions
Supported Standards, MIBs, and RFCs
Prerequisites for Using This Feature
Adding, Editing, and Deleting a Gateway Pool
Edit a Gateway Pool to Use Another Profile
Adding, Editing, and Deleting a Border Gateway with Gateway Pool
Add a DBE to a Gateway Pool with Call Limiting
Add a VXSM Gateway to a Global Default VXSM Gateway Pool
Remove a Gateway from a Gateway Pool
Provisioning a Gateway Pool in the Dialplan
Provisioning a Gateway Pool in A Number Analysis
Provisioning GATEWAYPOOL in B Number Analysis for Media Anchor Bypass
Provisioning a Codec String Property for a DBE Gateway
Supplemental Provisioning Examples
Provisioning an H.248 Path to a Cisco VXSM
Provisioning Service to a Cisco ASR 1000
Provisioning an Incoming SIP Trunk
Provisioning an Outgoing SIP Trunk
Sample of a Provisioned Cisco 7600 SBC
Sample of a Provisioned Cisco ASR 1000 SBC
PROV-ADD:GWPOOL:NAME—Adding a Gateway Pool in Cisco PGW 2200 Softswitch
PROV-ADD:IPGW:POOLID—Add Border Gateway to Gateway Pool
PROV-ADD:PROFILE:NAME—Add Gateway Pool Profile
PROV-ADD:H248PATH:NAME—Add Call Limiting Label to Gateway
PROV-ED:PROFILE:NAME—Add a VRF Name to a PROFILE
PROV-ED:PROFILE:NAME—Add Codecs to a Profile for a DBE Gateway
Software Changes for This Feature
The CallHoldInterworkingEnabled Property for Call Hold
Ingress Media Gateway Pool ID (Tag: 4110)
Egress Media Gateway Pool ID (Tag: 4111)
Ingress Intergateway Packet Info (Tag: 4112)
Egress Intergateway Packet Info (Tag: 4113)
License Rejecting Reason (Tag: 4244)
License Rejecting Direction (Tag: 4245)
Troubleshooting H.248 Protocol - Phase 2
Check the Configuration of an SBC Interface
Check for the Presence of a Configured Interface that is not Licensed
Check the Status of an H.248 Link
Check the Provisioning of the AnchorMedia and AnchorPolicy Properties
Check the Provisioning of Gateway Pool Properties
Capturing Cisco PGW 2200 Softswitch Trace Files and Platform.log for Debugging
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco PGW 2200 Softswitch H.248 Protocol-Phase 2 Feature Module
Document Release History
July 2009
Added the following properties to Table 3:
•
*.GWDefaultAudioCodecString
•
Added the following properties to Table 4:
•
•
November 2008
Initial version of the document.
February 2009
Second version of the document.The following two sections are added:
•
Feature History
9.8(1)
The H.248 Protocol-Phase 2 feature was introduced on the Cisco MGC software.
This document describes the H.248 Protocol-Phase 2 feature in the following sections:
•
•
•
Understanding the H.248 Protocol-Phase 2 Feature
H.248 Protocol-Phase 2 enables the Cisco PGW 2200 Softswitch to perform media anchoring on ingress or egress border gateways for IP traffic. This feature includes a simple service policy decision module (SPDM), which determines whether a session border element (SBE) should perform media anchoring and, if so, identifies which border gateway will perform the media anchoring based on service requirements. The border gateway control interface conforms to the ITU-SG16/IETF specification of the H.248 protocol and an additional optional package.
By supporting media anchoring, a gateway can:
•
•
•
•
Note
System Overview
Before the introduction of H.248-Phase 2, the Cisco PGW 2200 Softswitch was deployed to perform the Media Gateway Control Function (MGCF), connecting TDM networks (which used SS7 ISUP signaling, ISDN DSS1 and variants) to IP telephony networks (which used H.323 and SIP signaling). The Cisco PGW 2200 Softswitch could not do media anchoring for IP traffic.
H.248-Phase 2 gives the Cisco PGW 2200 Softswitch the capacity to anchor media on ingress or egress border gateways for IP traffic, no matter whether a call is TDM to IP, IP to TDM, or IP to IP. With H.248-Phase 2, the Session Border Element (SBE) engine can select border gateways in gateway pools, and, through the use of H.248, instruct these border gateways to anchor the Realtime Transport Protocol (RTP)/Real Time Conferencing Protocol (RTCP) media streams.
H.248-Phase 2 includes the following packages, which operate for connections to IP-IP border gateways as well as TDM-IP media gateways:
•
•
•
If the border gateway supports a digital signal processor (DSP) farm, the Cisco PGW 2200 Softswitch can support the following new services for IP traffic:
•
•
•
Note
Gateway Pool Management
In the context of H.248-Phase 2, a set of border gateways with the same capabilities is organized as a gateway pool, which can be associated with a specific IP trunk group. Some users might wish to group border gateways at one geographic location into a gateway pool. A gateway pool has the following properties:
•
•
•
One border gateway can belong to several gateway pools. You define a gateway pool profile before you create a gateway pool. Each gateway in the gateway pool supports all the capabilities specified in the gateway pool profile. The configuration is stored in the text file gwPools.dat.
You can associate a gateway pool with an IP trunk group by provisioning the trunk group property, GatewayPool. However, to enable the system to use a gateway pool, you must set another trunk group property, AnchorMedia. You can set the AnchorMedia property to one of three options:
–
–
–
The Cisco PGW 2200 Softswitch has a global default VXSM gateway pool, which the Cisco PGW 2200 Softswitch uses when the SPDM concludes that media anchoring is to be established on a call leg, but no gateway pool is defined on the trunk group. You provision a global default VXSM gateway pool as you would any normal gateway pool.
The properties GatewayPool and AnchorMedia established on an ingress or egress trunk group can be overridden by the result type GATEWAYPOOL in the dial plan. The result type GATEWAYPOOL can be set on A number analysis or B number analysis. The B number analysis has greater priority than A number analysis when a result type such as GATEWAYPOOL is provisioned on both A number analysis and B number analysis. Specifically, if AnchorMedia is set to Never on the ingress and egress sides in the dialplan, no media anchoring operates on ingress and egress call legs.
SPDM and Media Anchoring
H.248-Phase 2 introduces the SPDM to the Cisco PGW 2200 Softswitch to perform media anchoring. The SPDM resides in generic analysis as a stand alone function. The Cisco PGW 2200 Softswitch calls the SPDM function immediately after routing analysis to determine the following:
•
•
•
•
Effects of the AnchorMedia Property on a Gateway
The Cisco VXSM is a gateway that can play both tones and announcements to the IP side of a call. The SPDM tries to select a single gateway (such as the VXSM) to play tones and announcements if both of those services are required by a call.
The H.248-Phase 2 feature provides the new property AnchorMedia. The SPDM checks the setting of the AnchorMedia property to determine whether to use a gateway pool on an ingress or egress gateway.
•
•
•
Setting Trunk Group Properties for Media Anchoring
H.248-Phase 2 also introduces several new trunk group properties that enable the SPDM to establish media anchoring.
You configure the AnchorPolicy property on an egress trunk group to enable the SPDM to determine the media anchor policy for the trunk group. You can specify one of the following values for the AnchorPolicy property:
•
•
•
You configure the AnnouncementOption property on an ingress trunk group to indicate whether the trunk group is required to play announcements. You can specify one of the following values for the AnnouncementOption property:
•
•
You configure the ToneOption property on an ingress trunk group to indicate whether the trunk group is required to play tones. You can specify one of the following values for the ToneOption property:
•
•
The SPDM checks the service requirements for a call one by one. The requirements can include announcements, tone, codecs, and DTMF interworking. The SPDM checks for such service requirements as follows:
•
•
•
Note
After the SPDM checks all services requested for a call, it records which gateway supports announcements, tones, and other services. The SPDM then calls an MDL-engine interface to select the appropriate border gateway to perform media anchoring if it is required. If the selection of a border gateway fails, the SPDM tries another trunk group.
The maximum number of times that the SPDM tries another trunk group is established by the value set for the parameter MaxNumTGAdvances in the file XECfgParm.dat.
Selecting a Gateway Pool for Announcements
Prior to the introduction of H.248-Phase 2, you could enable the Cisco PGW 2200 Softswitch to play announcements to the TDM side of a call if the gateway on that side supported announcements. With H.248-Phase 2 you can enable the Cisco PGW 2200 Softswitch to play announcements to the IP side of a call also.
For a precall announcement, the Cisco PGW 2200 Softswitch still uses the current result type ANNOUNCEMENT on B number analysis of the dial plan to determine whether to play an announcement to the originating side.
The SPDM checks the current gateway pool or gateway usage on the ingress and egress sides. If a gateway pool or gateway on one side or the other of a call supports announcements, the SPDM records which side will support the service during the appropriate phase of the call. The SPDM proceeds to check other services that might be requested for the call.
If you set the AnchorPolicy property to 1 on the egress trunk group, SPDM checks the egress side first and then the ingress side to determine if the following conditions are established:
•
•
•
If the preceding conditions are met, the SPDM uses the gateway pool and the SPDM records which side will play announcements. The SPDM then proceeds to check other services. For the egress side of a call, the SPDM checks only the egress side.
If neither the ingress nor egress side can support announcements, the SPDM checks the new trunk group property AnnouncementOption on the ingress side to check whether playing announcements to the calling side is optional or mandatory.
•
•
For end-of-call and mid-call announcements provisioned on cause analysis in the dial plan, the Cisco PGW 2200 Softswitch performs as it did prior to the introduction of H.248-Phase 2.
If a gateway pool or gateway is available to support end-of-call or mid-call announcements, the Cisco PGW 2200 Softswitch uses this gateway pool or gateway to play the announcements. Thus, the Cisco PGW 2200 Softswitch will be able to play announcements to the IP side.
Gateway Pool Support for Playing Tone
Prior to the introduction of H.248-Phase 2, you could enable the Cisco PGW 2200 Softswitch to play tone to an originating TDM side of a call if the terminating side of the call was IP and you did not set the property GatewayRBToneSupport on the originating gateway to 0.
With H.248-Phase 2 you can enable the Cisco PGW 2200 Softswitch to extend tone service to the IP side of a call based on the configuration of the property GatewayRBToneSupport on the trunk group on the ingress side of the call. H.248-Phase 2 operates according to the following conditions:
•
•
Gateway Pool Support for DTMF Interworking
Prior to the introduction of H.248-Phase 2, you would provision DTMF support on an ingress side in A-number or B-number analysis. B-number analysis overrode A-number analysis. You would provision DTMF support on an egress side by setting the egress trunk group property DTMFCap. For IP-to-IP calls, if the ingress DTMF capability provisioned on the ingress trunk group was different from the DTMF capability provisioned on the egress trunk group, and the property was not set to 0 (Ignore DTMF capability) on either side, the Cisco PGW 2200 Softswitch tried the next trunk group.
With H.248-Phase 2 you can enables the use of a border gateway to perform DTMF interworking. If you establish a gateway pool on either the egress or ingress trunk group, and you configure that gateway pool to support DTMF interworking, the gateway pool resolves any mismatch in DTMF support that might exist between the two sides.
H.248-Phase 2 decides whether to use a gateway pool according to the following conditions:
•
•
–
–
–
If the preceding conditions are met, the SPDM uses the gateway pool and proceeds with a codec check. If the preceding conditions are not met, the SPDM tries the next trunk group.
Selecting a Gateway Pool for Codec Interworking
This section offers four possible cases for codec interworking: TDM to TDM, TDM to IP, IP to TDM and IP to IP.
•
•
•
•
H.248-Phase 2 enables you to configure the AnchorPolicy property to instruct the SPDM to either try the next trunk group or to select a gateway pool that can perform transcoding. H.248-Phase 2 addresses transcoding as follows:
–
–
Media anchoring is optional.
The gateway pool is not being used currently.
The gateway pool supports transcoding.
If the preceding conditions are met, SPDM initializes the gateway pool. If the conditions are not met, the SPDM tries the next trunk group.
–
Selecting a Border Gateway Through an MDL Engine Interface
For any gateway pool, you can set the property GatewaySelectionMethod to determine the method by which a border gateway is selected. Currently, there are two methods, sequential and round robin. With the sequential method, the Cisco PGW 2200 Softswitch checks for gateways according to an established sequence, starting with the first gateway in the list, until an appropriate gateway is chosen. With the round robin method, the Cisco PGW 2200 Softswitch checks a different gateway for each call in succession. If the gateway that is checked initially rejects the call, the next gateway is checked.
A gateway rejects support for a call for the following reasons:
•
•
•
You can configure a call-limiting parameter for a gateway that sets the maximum number of contexts permitted on the gateway at one time. Every call has two contexts. Each context can use a different gateway. Call limiting applies to individual contexts.
Each time the gateway is selected, the call-limiting parameter on that gateway is increased by 1. When a call context on a gateway is deleted, the value of the parameter on that gateway is decreased by 1. If the value set for the call limiting parameter is reached, the MDL engine checks another gateway. The call limiting parameter is engine.CallLimitingControl, which is located in the file XECfgParm.dat.
Note
Ringback Tone Support for an IP-to-IP Gateway
When a Cisco PGW 2200 Softswitch with H.248-Phase 2 interworks with an IP gateway, the Cisco PGW 2200 Softswitch manages the playing of ringback tone according to the following conditions:
1.
2.
3.
Note
4.
5.
6.
Note
0—no local tone application support
1—local ring back tone application support for MGCP-to-EISUP calls using the MDCX message connection method
2—local ring back tone application support for MGCP-to-EISUP calls using the RQNT message connection method
3—local ring back tone application support for MGCP-to-EISUP and MGCP-to-MGCP calls using the MDCX message connection method
4—local ring back tone application support for MGCP-to-MGCP calls only by using the MDCX message connection method
For the description of the GatewayRBToneSupport property, see Appendix A: Components, Processes, and Properties in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Codec Negotiation
H.248 codec selection is established at four levels:
•
•
•
•
Figure 1 illustrates the levels at which codecs are selected for the call legs of a basic TDM to TDM connection.
Figure 1 Codec Provisioning Levels for TDM-to-TDM Calls
At Level 1, you define the default codec string in the sigpath property GWDefaultCodecString. The Cisco PGW 2200 Softswitch sends to the gateway an ADD command that includes a list of codec types for the local connection. The gateway returns a message that contains only the codecs it supports.
The Cisco PGW 2200 Softswitch extends the codec list defined at Level 1 to the trunk group level (Level 2).
On the ingress side, codecs selected at Level 2 override codecs defined at Level 1. On the egress gateway, codecs configured at Level 2 override codecs defined at all other levels.
For Level 3, you can set the result type CODEC (47) for A number analysis or B number analysis. If the result specifies that the analysis is mandatory in data word 2, then the codec list from previous stages is ignored and the egress call must support the codec specified in data word 1. When data word 2 is configured as Preferred, the codec list from previous stages is appended to the codec specified in the data word. Codec selections at Level 3 override the selections made at previous levels if the preference is mandatory on the ingress side.
Codec Selection for IP Gateway-to-IP Gateway Calls
Figure 2 shows the levels at which codecs are selected for IP gateway to IP gateway calls.
Figure 2 Codec Selection Levels for IP-to-IP Calls
For IP gateway to IP gateway calls, codec selection for the ingress side proceeds according to the sequence of actions shown in Figure 3.
Figure 3 Codec Selection for an Ingress Gateway
On the egress side, only the codec lists selected at Level 1 and Level 2 are considered.
Figure 4 shows the phases of codec selection for IP gateway to IP gateway calls when both gateways are Cisco VXSMs.
Figure 4 Codec Selection for Calls with Two IP-to-IP Gateways
1.
2.
3.
4.
5.
6.
Results of Codec Selection on the Ingress Side of Calls
Table 1 indicates the call legs that determine the codec that the Cisco PGW 2200 Softswitch selects for the ingress side of a call for several combinations of ingress and egress gateway types.
Results of Codec Selection on the Egress Side of Calls
Table 2 indicates the call legs that determine the codec that the Cisco PGW 2200 Softswitch selects for the egress side of a call for several combinations of ingress and egress gateway types.
H.248 Protocol Package Support
For H.248 Protocol-Phase 2, the Cisco PGW 2200 Softswitch supports the following additional standard H.248 packages as well as a Cisco SBC-specified H.248 package:
•
•
•
ETSI NAT Traversal and IP NAPT Traversal Package Support
H.248-Phase 2 provides a new trunk group property, NATTraversalEnabled. You provision this property to specify whether or not NAT traversal is required for a trunk group. The property NATTraversalEnabled has two valid values:
•
•
The detailed NAT traversal method that the Cisco PGW 2200 Softswitch uses depends on the setting of an additional new signaling path (sigPath) property, NATTraversalMethod. You must provision NATTraversalMethod on the H.248 sigPath. The property NATTraversalMethod has two valid values:
•
•
After you provision the NATTraversalEnabled and NATTraversalMethod properties, when the Cisco PGW 2200 Softswitch sends an H.248 ADD or MODIFY request to a gateway, it checks the properties for the following conditions:
•
•
In this context, ntr is the package name for NAT Traversal. This package enables you to configure a media gateway to support media flows that have passed through a unknown number of customer premises equipment or network-based NAPT devices.
The term nap is the property ID of a property called is NAT processing. This property instructs the media gateway to apply NAPT processing to the incoming flow.•
In this context, ipnapt is the package ID for the IP NAT Traversal Package. This package enables the MGC to instruct the MC to perform latching on an H.248 Termination/stream for the purposes of IP NAPT traversal.
The term latch is a SignalID. This signal orders NAPT Traversal processing.Enhanced VPN Discrimination Package Support
H.248 Protocol-Phase 2 includes the Cisco SBC enhanced VPN discrimination package, which supports your ability to implement VRF name properties.
You can set a VRF name on Legs 1, 2, 3, and 4.
You create the VRF name as a property in the profile, which is attached to a trunkgroup and domain. When sending H.248 ADD requests to the gateway, the Cisco PGW 2200 Softswitch sets the vrfname property in the termination state field based on the configuration.
The Cisco DBE supports multi-VPN routing and forwarding (multi-VRF) on customer edge (CE) devices (for example, customer premises routers). Multi-VRF enables the Cisco PGW 2200 Softswitch to suppress provider edge (PE) checks that are required to prevent loops when the PE performs a mutual redistribution of packets. Multi-VRF enables service providers to use a single router to accomplish the tasks usually performed by multiple routers. By running Multi-VRF on a network, a service provider eliminates the requirement to install and run Multiprotocol Label Switching (MPLS) and Border Gateway Protocol (BGP).
If you run VRF on a router that is not a PE, you can turn off checks to enable the router to populate the VRF routing table with routes to IP prefixes. Multi-VRF is important because virtual private network (VPN) functionality is not completely supported on low-end systems. Multi-VRF provides logical separation of routing instances (and, by implication, address space) within one router.
By running multi-VRF, you can split a single, physical router into multiple virtual routers. In such a configuration, each router contains its own set of interfaces, routing table, and forwarding table. SBC supports multiple (overlapping and independent) routing tables per customer. You can use the distinct virtual routing contexts to divide routing domains within a single router.
Configuring VRF
You can implement VRF name properties only for gateways operating as data border elements (DBEs). In association with the PGW 2200, you can configure two VRF names on a DBE gateway, one as an inside VRF name and one as an outside VRF name. You apply VRF names to a profile (SIP, EISUP, Domain) and attach the profile to a trunk group or domain. (The default value for a VRF name is NULL.)
The following sample MML commands present a way to configure VRF names for the DBE gateways shown in Figure 5. In this illustration, both GW1 and GW2 are enabled as DBE gateways. The VRF names configured on the related trunk groups or domains are applied to the H.248 contexts in GW1 and GW2.
prov-ed:profile:name="profile1", insidevrfname="vrf2", outsidevrfname="vrf1"prov-ed:profile:name="profile2", insidevrfname="vrf3", outsidevrfname="vrf4"prov-add:trnkgrpprof:name="1000", profile="profile1" // for the trunkgroup 1prov-add:trnkgrpprof:name="2000", profile="profile2" // for the trunkgroup 2Figure 5 VRF Names on Two DBE Gateways
If only GW1 is enabled as a DBE gateway, only the VRF names configured on the related trunk group or domain is applied to the H.248 context on GW1, as shown in Figure 6.
Figure 6 VRF Names on a Single DBE Gateway (GW1)
Similarly, if only GW2 is enabled as a DBE gateway, only the VRF names configured on the related trunk group or domain is applied to the H.248 context on GW2, as shown in Figure 7.
Figure 7 Names on a Single DBE Gateway (DBE2)
For details on how to implement Multi-VRF, see Chapter 10: "Implementing SBC Multi-VRF" in the Cisco 7600 Series Routers Session Border Controller Configuration Guide or the chapter "Implementing SBC Multi-VRF" in the Cisco IOS XR Session Border Controller Configuration Guide.
Note
H.248-Phase 2 Feature Restrictions
H.248 Protocol-Phase 2 has the following restrictions:
•
•
•
•
•
•
•
•
•
•
•
Supported Standards, MIBs, and RFCs
Standards
H.248 Protocol-Phase 2 supports the following standards:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Cisco Media Gateway Controller Hardware Installation Guide - Releases 7 & 9.
Prerequisites for Using This Feature
The Cisco PGW 2200 Softswitch must be running Cisco MGC software Release 9.8(1) Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.7(3).
Related Documents
This document contains information that is related to this feature. Refer to documents that contain additional information related to the Cisco Media Gateway Controller (MGC).
Provisioning Examples
This section provides provisioning examples for enabling H.248 Protocol-Phase 2.
Adding, Editing, and Deleting a Gateway Pool
Add a Gateway Pool for DBE
Prov-add:PROFILE:NAME="DBE-Profile1", TYPE="GWPOOLPROFILE", VALIDATION="ON", CAT="profile", GatewayAnnSupport="0", GatewayCodecSupport ="0", GatewayDTMFSupport="1", GatewayToneSupport="0", GatewaySelectionMethod="1"Prov-add:GWPOOL:NAME="101", DESC="DBE GW POOL TO CUSTOMER 1", PROFILE="DBE-Profile1"Add a Gateway Pool for VXSM
Prov-add:PROFILE:NAME="VXSM-Profile1", TYPE="GWPOOLPROFILE", VALIDATION="ON", CAT="profile", GatewayAnnSupport="1", GatewayCodecSupport ="1", GatewayDTMFSupport="1", GatewayToneSupport="1", GatewaySelectionMethod="1"Prov-add:GWPOOL:NAME="1",DESC="DEFAUL VXSM Gateway Pool",PROFILE="VXSM-Profile1"Edit a Gateway Pool to Use Another Profile
Prov-add:PROFILE:NAME="VXSM-Profile2", TYPE="GWPOOLPROFILE", VALIDATION="ON", CAT="profile", GatewayAnnSupport="0", GatewayCodecSupport ="1", GatewayDTMFSupport="0", GatewayToneSupport="0", GatewaySelectionMethod="1"Prov-ed:GWPOOL:NAME="1", PROFILE="VXSM-Profile2"Delete a Gateway Pool
Prov-dlt:GWPOOL:NAME="101"Adding, Editing, and Deleting a Border Gateway with Gateway Pool
Add a DBE to a Gateway Pool with Call Limiting
prov-add:EXTNODE:NAME="h248-DBE-01", DESC="DBE-01", TYPE="C7600"prov-add:loclabel:name="loclbl2", desc="local label 2", calllimit=6000prov-add:H248PATH:NAME="h248-sigpath-UDP", DESC="Service to H248", EXTNODE=" h248-DBE-01", LABEL="loclbl2"prov-add:IPLNK:NAME="h248-udp-link-1", DESC="UDP link to h248-sigpath-UDP", SVC="h248-sigpath-UDP", IPAddr="IP_Addr1", PORT=2944, PEERADDR="10.74.57.205", PEERPORT=2944,PRI=1prov-add: IPGW:POOLID="101", GW="h248-DBE-01"Add a VXSM Gateway to a Global Default VXSM Gateway Pool
prov-add:EXTNODE:NAME="h248-VXSM-01", DESC="VXSM-01", TYPE="VXSM"prov-add:H248PATH:NAME="h248-sigpath-UDP2", DESC="Service to H248", EXTNODE="h248-VXSM-01"prov-add:IPLNK:NAME="h248-udp-link-2", DESC="UDP link to h248-sigpath-UDP2", SVC="h248-sigpath-UDP2", IPAddr="IP_Addr1", PORT=2944, PEERADDR="10.74.57.206", PEERPORT=2944,PRI=1prov-add: IPGW:POOLID="1", GW="h248-VXSM-01"Remove a Gateway from a Gateway Pool
prov-dlt:IPGW:POOLID="101", EXTNODE="h248-DBE-01"Provisioning a Gateway Pool in the Dialplan
Provisioning a Gateway Pool in A Number Analysis
numan-add:resultset:custgrpid="1111", name="set1"numan-add:resulttable:custgrpid="1111", resulttype="GATEWAYPOOL", dw1="100", dw2="3", dw3="101", dw4="1", setname="set1", name="rt1"numan-add:adigittree:custgrpid="1111", digitstring="1", callside="originating", setname="set1"Provisioning GATEWAYPOOL in B Number Analysis for Media Anchor Bypass
numan-add:resultset:custgrpid="1111", name="set2"numan-add:resulttable:custgrpid="1111", resulttype="GATEWAYPOOL", dw1="100", dw2="3", dw3="101", dw4="1", setname="set2", name="rt2"numan-add:bdigittree:custgrpid="1111", digitstring="1", callside="originating", setname="set2"Provisioning a Codec String Property for a DBE Gateway
The property gwdefaultcodecstring enables a DBE gateway to specify an ordered series of codec choices, separated by semicolons.
prov-ed:profile:name="profile_name", gwdefaultcodecstring="G.711u; G.711a"Supplemental Provisioning Examples
The following sections provide supplemental provisioning examples for various elements that might be associated with implementing the H.248 - Phase 2 feature on a Cisco PGW 2200 Softswitch.
Provisioning an H.248 Path to a Cisco VXSM
The following sequence of sample MML commands presents a way to provision the Cisco PGW 2200 Softswitch to interoperate with an IP gateway (VXSM).
prov-add:EXTNODE:NAME="mgx-8850-6", DESC="MGX8800-VXSM6", TYPE="VXSM", ISDNSIGTYPE="N/A", GROUP=0prov-add:H248PATH:NAME="h248-vxsm6", DESC="Service to vxsm6", EXTNODE="mgx-8850-6"prov-add:IPLNK:NAME="h248-udp-vxsm6", DESC="udp to vxsm6", SVC="h248-vxsm6", IPADDR="IP_Addr1", PORT=2944, PEERADDR="10.0.181.2", PEERPORT=2945, PRI=1, IPROUTE=""prov-add:sigsvcprop:NAME="h248-vxsm6", GWProtocolVersion="H248 V2"prov-add:sigsvcprop:NAME="h248-vxsm6", h248profilename="CISCO_GW"Provisioning Service to a Cisco ASR 1000
The following sequence of sample MML commands presents a way to provision the Cisco PGW 2200 Softswitch to interoperate with the Cisco ASR 1000
prov-add:extnode:name="asr-1000", desc="asr1000", type="ASR1000", isdnsigtype="N/A", group=0prov-add:H248PATH:name="h248-udp-asr1000", desc="service to asr1000", extnode="asr-1000"prov-add:iplnk:name="h248-asr1000", desc="udp to asr1000", svc="h248-udp-asr1000", ipaddr="IP_Addr1", port=2944, peeraddr="33.33.36.1", peerport=2944, pri=1prov-add:sigsvcprop:name="h248-udp-asr1000", GWProtocolVersion="H248 V2"Provisioning an IP Gateway
The following sequence of sample MML commands presents a way to provision the Cisco PGW 2200 Softswitch to operate as an IP gateway.
prov-add:PROFILE:NAME="dbe-profile", TYPE="gwpoolprofile", gatewayselectionmethod="1"prov-add:PROFILE:NAME="vxsm-profile1", TYPE="gwpoolprofile", gatewayannsupport="1", gatewaycodecsupport="1", gatewaydtmfsupport="1", gatewayselectionmethod="1", gatewaytonesupport="1"prov-add:GWPOOL:NAME="104", DESC="gsr", PROFILE="dbe-profile"prov-add:GWPOOL:NAME="101", DESC="default vxsm gateway pool", PROFILE="vxsm-profile1"prov-add:IPGW:poolid="101", gw="mgx-8850-6"prov-add:IPGW:poolid="104", gw="asr-1000"Provisioning a SIP Path
The following sequence of sample MML commands presents a way to provision on the Cisco PGW 2200 Softswitch a SIP path to a SIP device.
prov-add:SIPPATH:NAME="sip-path-1", DESC="SIP path 1", MDO="IETF_SIP", ORIGLABEL="", TERMLABEL=""prov-add:SIPLNK:NAME="sip-link-1", DESC="SIP link 1", SVC="sip-path-1", IPADDR="Virtual_IP_Addr1", PORT=5060,PRI=1prov-add:sigsvcprop:NAME="sip-path-1", LocalAnnBehavior="2"Provisioning an Incoming SIP Trunk
The following sequence of sample MML commands presents a way to provision an incoming SIP trunk on the Cisco PGW 2200 Softswitch, including the parameters anchormedia and gatewaypool.
prov-add:trnkgrp:NAME="6001", CLLI="NULL", SVC="sip-path-1", TYPE="SIP_IN", SELSEQ="LIDL", QABLE="N"prov-add:PROFILE:NAME="p6001", TYPE="sipprofile", anchormedia="3", anchorpolicy="1", custgrpid="1111", gatewaypool="101", insessiontimer="90", mgcdomain="10.0.248.97"prov-add:trnkgrpprof:name="6001", profile="p6001"Provisioning an Outgoing SIP Trunk
The following sample MML commands show how to provision an outgoing SIP trunk on the Cisco PGW 2200 Softswitch, including the parameters anchormedia and gatewaypool.
prov-add:trnkgrp:NAME="1350", CLLI="NULL", SVC="sip-path-1", TYPE="IP_SIP", SELSEQ="LIDL", QABLE="N"prov-add:PROFILE:NAME="p1350", TYPE="sipprofile", anchormedia="3", custgrpid="1111", gatewaypool="104", insessiontimer="90", mgcdomain="10.0.248.97"prov-add:trnkgrpprof:name="1350", profile="p1350"prov-add:siprttrnkgrp:name="1350", url="10.0.50.135", srvrr=0, sipproxyport=5060, version="2.0", cutthrough=3, extsupport=1prov-add:rttrnk:weightedTG="OFF", name="rt1350", trnkgrpnum=1350prov-add:rtlist:name="rtlist1350", rtname="rt1350", distrib="OFF"Sample of a Provisioned Cisco 7600 SBC
The following data represents the provisioning of a Cisco 7600 router operating as a Session Border Controller. To display this data, issue the following command:
show running-configlogging console 7logging monitor 7login timeout 0line vtysession-limit 10hostname 7635-SLOT11boot system image: c76-sbck9-mzg.3.0.1_AS3_0_01.binserverfarm host ciscoserverfarm host suninterface vlan 130ip address 10.130.10.2 255.255.255.240alias 10.130.10.4 255.255.255.240peer ip address 10.130.10.3 255.255.255.240no shutdownft interface vlan 131ip address 10.130.10.18 255.255.255.240peer ip address 10.130.10.19 255.255.255.240no shutdownft peer 1heartbeat interval 300heartbeat count 10ft-interface vlan 131ft group 1peer 1associate-context Admininserviceip route 0.0.0.0 0.0.0.0 10.130.10.1ip route 10.130.10.4 255.255.255.255 10.130.10.1username admin password 5 $1$faXJEFBj$TJR1Nx7sLPTi5BZ97v08c/ role Admin domain default-domainusername www password 5 $1$UZIiwUk7$QMVYN1JASaycabrHkhGcS/ role Admin domain default-domainsbc sbc-11dbevdbeglobaldtmf-duration 200congestion-cleared 60congestion-threshold 80local-port 2944control-address h248 ipv4 10.130.10.4controller h248 1remote-address ipv4 10.0.7.230transport udph248-profile gatecontrolattach-controllersmedia-address pool ipv4 10.130.10.4 10.130.10.13 port-range 5000 6000 signalingmedia-address pool ipv4 10.130.10.4 10.130.10.13 port-range 17000 32000 voicemedia-timeout 30overload-time-threshold 100deact-mode normalactivateSample of a Provisioned Cisco ASR 1000 SBC
The following data represents the provisioning of a Cisco ASR 1000 router operating as a Session Border Controller. To display this data, issue the following command:
show running-config!interface SBC1ip address 33.33.36.101 255.255.255.0 secondaryip address 33.33.36.1 255.255.255.0!!sbc pgw dbevdbe globalh248-napt-package napth248-inactivity-duration 6000local-port 2944control-address h248 ipv4 33.33.36.1controller h248 1remote-address ipv4 10.0.248.98controller h248 2remote-address ipv4 10.0.248.99attach-controllerslocation-id 1media-address pool ipv4 33.33.36.110 33.33.36.116media-timeout 3activate!!Configuring a Cisco VXSM
To provision a Cisco VXSM to interoperate with the Cisco PGW 2200 Softswitch running the H.248 Protocol - Phase 2 feature, you must issue the VXSM CLI commands in the following sequence:
1.
2.
3.
4.
5.
6.
7.
8.
For a detailed description of the VXSM CLI commands, see the Cisco Voice Switch Services (VXSM) Configuration and Command Reference Guide for MGX Switches, Release 5.3.
MML Command Reference
This section documents new, modified, or deleted Man-Machine Language (MML) commands. All other MML commands are documented in the Cisco Media Gateway Controller Software Release 9 MML Command Reference
New MML Commands
This section contains the MML commands that are new for this feature.
PROV-ADD:GWPOOL:NAME—Adding a Gateway Pool in Cisco PGW 2200 Softswitch
PROV-ADD:IPGW:POOLID—Add Border Gateway to Gateway Pool
Modified MML Commands
This section contains the MML commands that are modified for the H.248 Protocol-Phase 2 feature.
PROV-ADD:PROFILE:NAME—Add Gateway Pool Profile
PROV-ADD:H248PATH:NAME—Add Call Limiting Label to Gateway
PROV-ED:PROFILE:NAME—Add a VRF Name to a PROFILE
PROV-ED:PROFILE:NAME—Add Codecs to a Profile for a DBE Gateway
Software Changes for This Feature
This section describes the software changes in the Cisco PGW 2200 Softswitch that support the H.248-Phase 2 protocol.
Alarms
No new alarms are added for this feature and no existing alarms are modified.
For information on the alarms for the Cisco MGC software, see the Cisco Media Gateway Controller Software Release 9 Messages Reference.
Properties
This section identifies the new properties associated with H.248 Protocol-Phase 2. For information on other properties for the Cisco MGC software, see the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Table 3 presents new properties that support H.248 Protocol-Phase 2. The default value for each of these new properties is 0.
Table 4 lists new trunk group and gateway pool properties that support operation of
H.248 Protocol-Phase 2.
The CallHoldInterworkingEnabled Property for Call Hold
If the Cisco PGW 2200 Softswitch is interworking with either a VXSM or DBE IP-IP gateway, when the Cisco PGW 2200 Softswitch receives a call hold request from a holding party, the Cisco PGW 2200 Softswitch changes the mode of the call leg that is closest to the held party. The Cisco PGW 2200 Softswitch sends a signaling message to inform the held party that the call is on hold based on the configuration of the trunk group property CallHoldInterworkingEnabled.
The PGW 2200 checks the property CallHoldInterworkingEnabled only if the held party called using SIP/EISUP by way of a Cisco H.323 Signaling Interface (HSI).
•
•
Billing Interface
This section identifies the call detail record (CDR) data modified for this feature. For billing interface information for the rest of the Cisco MGC software, see the Cisco Media Gateway Controller Software Release 9 Billing Interface Guide.
Ingress Media Gateway Pool ID (Tag: 4110)
Tag 4110 contains the ingress media gateway pool ID.
Egress Media Gateway Pool ID (Tag: 4111)
Tag 4111 contains the egress media gateway pool ID.
Ingress Intergateway Packet Info (Tag: 4112)
Tag 4112 contains values for packets sent, packets received, packets lost, octets sent, octets received, jitter, latency information (reserved 1 and 2) from the ingress intergateway traffic (that is, Leg 2).
Egress Intergateway Packet Info (Tag: 4113)
Tag 4113 contains values for packets sent, packets received, packets lost, octets sent, octets received, jitter, latency information (reserved 1 and 2) from the egress intergateway traffic (that is, Leg 3).
License Rejecting Reason (Tag: 4244)
Tag 4244 indicates that a call is rejected due a license restriction. The Cisco PGW 2200 Softswitch performs a license check for calls that are controlled by a license. The Cisco PGW 2200 Softswitch rejects a call if no license is present for the protocol interface or when the call limit is reached. This record identifies the license that failed the call.
License Rejecting Direction (Tag: 4245)
Tag 4255 indicates whether a call was rejected by a license on the Cisco PGW 2200 Softswitch that is associated with the origination (incoming) side or a license associated with the terminating (outgoing) side. The value 1 indicates the incoming side. The value 2 indicates the outgoing side.
Troubleshooting H.248 Protocol - Phase 2
This section provides ways to check various requirements that must be met to ensure proper operation of the H.248 Protocol - Phase 2 feature on the Cisco PGW 2200 Softswitch such as the presence of a interface license and correctly configured devices with which the Cisco PGW 2200 Softswitch must interoperate.
Check for an SBC License
The following sample MML command requests the display of all licenses that exist for the SBC.
mml> rtrv-lics:all
MGC-02 - Media Gateway Controller 2008-11-24 01:06:19.751 ESTM RTRV"LMAgent:------------------------------------------------------------------SBE Fully Featured License 9.8 permanent------------------------------------------------------------------Interface Name Entitled ProvisionedSS7Interface Y NPRIInterface Y NPBXInterface Y NINAPInterface Y NLIInterface Y N/ASBEInterface Y Y------------------------------------------------------------------Configure TDM Ports Entitled Provisioned AvailableCall Control 100060 0 100060------------------------------------------------------------------<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>Runtime TimesTen Entitled Provisioned AvailableLicense 2000000 0 2000000------------------------------------------------------------------Run Time License TDMPorts SIP H323Entitled Number 100060 400060 400060Current Usage 0 0 0Peak Usage(15 min) 0 0 0Peak Usage(1 hour) 0 0 0Peak Usage(24 hour) 0 0 0------------------------------------------------------------------";Check the Configuration of an SBC Interface
To ensure that the SBC interface is configured correctly, you can run the lmreport utility. The following example shows a sample of the data displayed when you run the lmreport utility. In this example, the value "Yes" in the SBE interface field shows that the SBE interface license is present.
$lmreportSIP sigPath: YesSS7 sigPath: NoDPNSS sigPath: NoBRI sigPath: NoQSIG sigPath: NoPRI sigPath: NoINAP interface: NoSBE interface: YesConfiguration Time Ports count = 0Provisioned TimesTen count = 0Check for the Presence of a Configured Interface that is not Licensed
You can check for the presence of an appropriate license for a configured interface (SBC interface license) by issuing the MML command rtrv-alms.
mml> rtrv-alms::MGC-02 - Media Gateway Controller 2008-11-24 01:17:28.083 ESTM RTRV"LMAGT-01: 2008-11-24 01:16:41.910 EST,""LMAGT-01:ALM=\"Unlicensed interface configured\",SEV=MJ";Check the Status of an H.248 Link
You check the status of an H.248 link by issuing the MML command rtrv-iplink. The status IS indicates that the link is in service. The status OOS indicates that the link is out of service.
sh-vwjetta mml> rtrv-iplnk:all:MGC-02 - Media Gateway Controller 2008-11-24 12:04:21.940 CSTM RTRV"h248-udp-vxsm6:IS""h248-asr1000:IS""iplnk-plum:IS""sip-link-1:IS"If a link is OOS, first ensure that the IP connection between the Cisco PGW 2200 and the DBE is operating properly. Then change the status of the DBE from not active to active (if the DBE is a Cisco VXSM, issue the command cnfh24oos then cnfh248is). Finally, collect the snoop trace on the Cisco PGW 2200 side and contact the Cisco TAC.
Check the Provisioning of the AnchorMedia and AnchorPolicy Properties
If no IP-to-IP gateway is invoked as expected for a call between two IP DBEs, you should check to ensure that the properties AnchorMedia and AnchorPolicy are provisioned correctly by issuing the MML command prov-rtrv.
sh-vwjetta mml> prov-rtrv:profile:name="p1340","prop"MGC-02 - Media Gateway Controller 2008-11-25 05:27:20.280 CSTM RTRV"session=1031-test-eisuptype:profile"/*ProfileType ProfileName-------------------- --------------------sipprofile p1340-----------------------------------------anchormedia = 3anchorpolicy = 1custgrpid = 1111gatewaypool = 101insessiontimer = 90mgcdomain = 10.0.248.97Check the Provisioning of Gateway Pool Properties
To check the values that are set for the gateway pool properties, issue the MML command prov-rtrv.
sh-vwjetta mml> prov-rtrv:profile:name="p1340","prop"MGC-02 - Media Gateway Controller 2008-11-25 05:27:20.280 CSTM RTRV"session=1031-test-eisuptype:profile"/*ProfileType ProfileName-------------------- --------------------sipprofile p1340-----------------------------------------anchormedia = 3anchorpolicy = 1custgrpid = 1111gatewaypool = 101insessiontimer = 90mgcdomain = 10.0.248.97Capturing Cisco PGW 2200 Softswitch Trace Files and Platform.log for Debugging
To capture an MDL trace file and platform.log for the Cisco PGW 2200 Softswitch, complete the steps in the following procedure.
Step 1
sh-vwjetta mml> sta-sc-trc:sip-path-1:log="CHK",confirmMGC-02 - Media Gateway Controller 2008-11-25 05:37:21.580 CSTM COMPLD"sip-path-1 - this trace will stop automatically after 1800 seconds, or when MCL reaches MCL1, or when provision is changed."Step 2
Step 3
sh-vwjetta mml> stp-sc-trc:all:MGC-02 - Media Gateway Controller 2008-11-25 05:40:22.740 CSTM COMPLD"ALL:Trace stopped for the following files:../var/trace/CHK_sip-path-1_20081125053721.btr";Step 4
Step 5
Step 6
To collect the a platform.log file for the Cisco PGW 2200 Softswitch, complete the steps of the following procedure.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Glossary
Table 5 contains expansions of acronyms used in this feature module.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0807R)
© 2008 Cisco Systems, Inc. All rights reserved.
