Cisco PGW 2200 Softswitch H.248
Protocol–Phase 2 Feature Module
Document Release History
Publication Date
Comments
December 2009
Updated the values for CallHoldInterworkingEnabled.
July 2009
Added the following properties to Table 3:
•
*.GWDefaultAudioCodecString
•
*.GWDefaultVideoCodecString
Added the following properties to Table 4:
•
*.DummyAudioCodecString
•
*.DummyVideoCodecString
November 2008
Initial version of the document.
February 2009
Second version of the document.The following two sections are added:
•
Supplemental Provisioning Examples, page 22
•
Troubleshooting H.248 Protocol - Phase 2, page 37
Feature History
Release
Modification
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, page 2
•
Related Documents, page 19
•
Provisioning Examples, page 20
•
MML Command Reference, page 26
•
Software Changes for This Feature, page 30
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
© 2008 Cisco Systems, Inc. All rights reserved.
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
•
Obtaining Documentation, Obtaining Support, and Security Guidelines, page 41
•
Glossary, page 41
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
•
Play announcements
•
Select codecs
•
Detect DTMF
•
Support tones
H.248–Phase 2 enhances the Cisco PGW Gateway 2200 Softswitch’s interaction with media gateways.
With this feature the PGW 2200 can both control TDM media gateways through H.248 messages and it
can support IP-to-IP gateway communications. H.248–Phase 2 also introduces the SPDM, which enables
the Cisco PGW 2200 Softswitch to select specific gateways to perform media anchoring.
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:
•
VPN discrimination package—By using a Cisco Session Border Control (SBC) enhanced VPN
discrimination package, the Cisco PGW 2200 Softswitch can instruct border gateways to perform
network address and port translation (NAPT) for media streams by allocating different IP address
spaces on either side of the border gateway. The Cisco PGW 2200 Softswitch can also make
VPN-aware VPN interconnections in service provider's core networks without enabling and
configuring Multiprotocol Label Switching (MPLS) and the Border Gateway Protocol (BGP).
•
ETSI NAT traversal package—By using the ETSI NAT traversal package or ITU IP NAPT traversal
package, the Cisco PGW 2200 Softswitch can instruct the border gateway to direct the downstream
media packets to the external address of remote NAT (this operation is known as media stream
latching).
H.248 Protocol-Phase 2
2
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
•
Tones and announcements package—For IP-to-IP calls, if an IP gateway is capable of playing tones
and announcements, the Cisco PGW 2200 Softswitch can instruct the gateway to play them.
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
•
Tone and announcement playing (to the IP side)
•
Transcoding
•
Termination ID support—The Cisco PGW 2200 Softswitch supports termination IDs created for
Cisco VXSM gateways and data border element (DBE) gateways (such as the Cisco 7600). The
naming convention format of termination IDs for VXSM gateways is prefix/<id>. The format for
DBE termination IDs is prefix/<group>/<interface>/<id>.
Typically, to use the added functionality introduced by H.248–Phase 2, the Cisco PGW 2200 Softswitch
interworks with either a Cisco VXSM or DBE gateway (for example, the Cisco 7600).
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:
•
A gateway pool ID, which is unique within the Cisco PGW 2200 Softswitch.
•
A gateway pool profile, which defines the capability set of the gateway pool. The capabilities
include playing tones and announcements, transcoding, and processing DTMF. The gateway
selection method within a gateway pool is also part of the gateway pool profile.
•
A gateway pool includes a list of gateways.
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:
– Always—The Cisco PGW 2200 will always anchor media on this call leg.
– Optional—The Cisco PGW 2200 will determine whether to anchor media on this call leg based
on an SPDM decision.
– Never—The Cisco PGW 2200 never anchors media on this call leg.
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.
H.248 Protocol-Phase 2
3
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
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:
•
The services required for a call
•
The need to perform media anchoring on the ingress and egress sides of a call
•
The side of a call on which to provide services in a later phase, for example, when an egress gateway
is required to play a tone
•
The need to invoke a Message Definition Language (MDL) engine interface to select the appropriate
border gateway to provide media anchoring if it is required
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.
•
If the AnchorMedia property is set to Always, the SPDM uses a gateway pool on a gateway.
•
If the AnchorMedia property is set to Optional, the SPDM might not use a gateway pool on a
gateway. However, after the SPDM checks the services configured on the gateway pool, it might use
the gateway pool on a gateway
•
If the AnchorMedia property is set to Never, the SPDM never uses a gateway pool on a 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:
•
0—Do not change gateway pool usage in SPDM. If a service check fails, the SPDM does not use a
gateway pool even if the AnchorMedia property is set to Optional for the trunk group. Consequently,
SPDM tries the next trunk group.
•
1—SPDM enables gateway pool usage on an IP trunk if the AnchorMedia property is set to
Optional. The SPDM enables the gateway pool if it concludes that the gateway pool satisfies service
requirements for the call.
•
2—Reserved to enable a future option.
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:
•
Mandatory—If the SPDM determines that a trunk group cannot provide announcements, it tries the
next trunk group.
H.248 Protocol-Phase 2
4
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
•
Optional—If the SPDM concludes that a trunk group cannot provide announcements, it continues
to check whether the trunk group can provide other services.
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:
•
Mandatory—If the SPDM discovers that the trunk group cannot provide the tone service, it tries the
next trunk group.
•
Optional—If the SPDM discovers that the trunk group cannot provide the tone service, it continues
to check whether the trunk group can provide other services.
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
•
If the current ingress/egress gateway pool can support a service, the SPDM continues to check other
service requirements.
•
If the current ingress/egress gateway pool cannot support a service, and if the AnchorPolicy property
on the egress trunk group is set to 1 (optional—use the gateway pool) and the AnchorMedia property
is set to Optional, the SPDM will check whether the gateway pool can support other services. If the
gateway pool can support other services, the SPDM may or may not use it.
•
If a trunk group cannot support a particular service but the service is not mandatory, the SPDM
continues to check other services.
The SPDM can perform a service check for the gateway and trunk group on the egress side of a call only.
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:
•
Media anchoring is optional.
•
A gateway pool is currently not used.
H.248 Protocol-Phase 2
5
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
•
The gateway pool supports the playing of announcements.
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.
•
If the requirement to play announcements is mandatory and no border gateway on the ingress or
egress side can play announcements, the SPDM checks another egress trunk group.
•
If the requirement to play announcements is optional and no border gateway on the ingress or egress
side can play announcements, the SPDM continues to check other service requirements on the egress
trunk group.
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:
•
If the protocol on the called side is not SIP or EISUP, no tone is required for the calling side.
•
If the protocol on the called side is SIP or EISUP, and the property GatewayRBToneSupport on the
ingress trunk group is set to 0, no tone is required for the calling side. If the GatewayRBToneSupport
property is set to 1, tone is required for the calling side.
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 you set AnchorPolicy to 0 for the trunk group, the SPDM does not initialize a gateway pool and
tries the next trunk group.
H.248 Protocol-Phase 2
6
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
•
If you set AnchorPolicy to 1 for the trunk group, the SPDM first checks the ingress trunk group and
then the egress trunk group to determine if the following conditions are satisfied:
– Media anchoring is optional.
– The gateway pool is not being used currently.
– The gateway pool supports DTMF interworking.
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.
•
TDM-to-TDM calls are not addressed by H.248–Phase 2. The Cisco PGW 2200 Softswitch does not
use gateway pools for such calls.
•
For TDM-to-IP calls, the Cisco PGW 2200 Softswitch operates as it did prior to the introduction of
H.248–Phase 2. When the Cisco PGW 2200 Softswitch seizes the originating-side media gateway,
it compares the response codec with the egress codec. If these codecs are incompatible, the Cisco
PGW 2200 Softswitch tries the next trunk group.
•
For IP-to-TDM calls, the Cisco PGW 2200 Softswitch continues to manage such calls as it did prior
to the introduction of H.248–Phase 2.
•
The SPDM initializes a gateway pool only to resolve a codec mismatch for an IP to IP call. Prior to
the introduction of H.248–Phase 2, if the Cisco PGW 2200 Softswitch detected a mismatch between
the ingress and egress codecs, the Cisco PGW 2200 Softswitch tried the next trunk group.
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:
– If there is a transcoding-capable gateway pool currently in use on the egress side, the Cisco
PGW 2200 Softswitch seizes terminating leg control.
– If you set the AnchorPolicy property to 1, the SPDM checks the ingress side first and then the
egress side to determine if the following conditions are satisfied:
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.
– If you set the AnchorPolicy property to 0, the SPDM tries the next trunk group.
H.248 Protocol-Phase 2
7
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
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:
•
The gateway is unreachable.
•
The gateway is congested.
•
The maximum value set for the call-limiting parameter on the gateway has been reached.
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
You cannot configure the parameter engine.CallLimitingControl for former call-limiting functions.
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.
If you set the cutthrough parameter to 2 (ACM-Address Complete Message) and the Cisco PGW
2200 Softswitch receives Session Description Protocol (SDP) data for cutthrough when it receives
the ACM, the Cisco PGW 2200 Softswitch performs cutthrough and does not play a local ringback
tone.
2.
If a called subscriber is accessed by SIP, the Cisco PGW 2200 Softswitch checks the 180 message
to determine whether or not it specifies SDP. If the 180 (Ringing) message indicates SDP, the Cisco
PGW 2200 Softswitch concludes that the remote side will provide ringback tone. If the 180 message
does not indicate SDP, the Cisco PGW 2200 Softswitch plays local ringback tone.
3.
If a called subscriber is accessed by TDM and has inbandinfo in the Alerting message, the
Cisco PGW 2200 Softswitch concludes that the remote side provides ringback tone and does not
play local ringback tone.
Note
4.
The parameter inbandinfo appears in a TDM alerting message to indicate remote ringback tone.
If a caller and called subscriber are both accessed by TDM, the Cisco PGW 2200 Softswitch checks
the value set for the GatewayRBToneSupport property. If the property is set to 3 or 4, the Cisco PGW
2200 Softswitch plays local ring back tone.
H.248 Protocol-Phase 2
8
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
5.
If a caller is TDM and the called subscriber is SIP/HSI/EISUP, the Cisco PGW 2200 Softswitch
checks the value set for the GatewayRBToneSupport property. If the property is 1, 2, or 3, the
Cisco PGW 2200 Softswitch plays local ring back tone.
6.
If a caller is SIP/HSI/EISUP, the Cisco PGW 2200 Softswitch checks the value set for the
GatewayRBToneSupport property. If the property is set to 1, 2, 3, or 4, the Cisco PGW 2200
Softswitch plays local ring back tone.
The GatewayRBToneSupport property values are:
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:
•
Level 0—At Level 0, a codec or list of codecs is specified in local and remote descriptors within the
SDP data of an INVITE message.
•
Level 1—At Level 1, a codec or list of codecs is specified in a signaling path (sigpath) property.
•
Level 2—At Level 2, a codec or list of codecs is specified in a trunk group property
(DummyCodecString).
•
Level 3—At Level 3, a codec or list of codecs is configured by a dial plan. At this level the codecs
are marked either as Mandatory (0) or Preferred (1).
H.248 Protocol-Phase 2
9
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
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
Level 3: Dialplan
result type
Level 2: Egress
trunk group
Level 2: Ingress
trunk group
Level 0: SDP
within message
PGW
Level 1: Ingress
Sigpath
Level 1: Egress
Sigpath
Leg 1
TDM GWX
Leg 2
Leg 3
Leg 4
271581
TDM GWX
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.
H.248 Protocol-Phase 2
10
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
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
Level 3: Dialplan
result type
Level 2: Egress
trunk group
Level 2: Ingress
trunk group
Level 0: SDP
within message
Outgoing
PGW
Level 1: Ingress
Sigpath
Level 1: Egress
Sigpath
Leg 1
IP-IP GWX
Leg 2
Leg 3
Leg 4
271583
IP-IP GWX
H.248 Protocol-Phase 2
11
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
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
Level 0
Level 1
Codec Selection for an Ingress Gateway
Codec list is exchanged in SDP
contained in local/remote
descriptors between the originating
and terminating gat eway.
Codec list set
on ingress
Megaco signal
path?
Yes
Set codec selection
list to ingress
sigpath codec list.
Yes
Set codec selection
list to ingress trunk
group codec list.
Yes
Result type
Mandatory?
No
Level 2
Codec list set
on ingress
trunk group?
No
Level 3
Result type
CODEC
defined?
No
Yes
Set codec
selection list
to Codec
Result String.
No
271582
Append Codec Result
String to L2/L1/L0 String.
On the egress side, only the codec lists selected at Level 1 and Level 2 are considered.
H.248 Protocol-Phase 2
12
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
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
2
Terminating
PGW Leg
(Codec
configured)
3
4
Leg 2
IP-IP GWX
Leg 3
6
SIP
Originator
5
IP-IP GWX
Leg 4
271584
Leg 1
Originating
PGW Leg
(Codec
configured)
1
SIP
Originator
1.
In phase 1, the Cisco PGW 2200 Softswitch receives an INVITE message that includes SDP data.
2.
In phase 2, the Cisco PGW 2200 Softswitch sends an ADD command to the IP gateway on the
ingress side and includes the codecs listed in the SDP data of the INVITE message, plus the codec
lists derived from the sigpath, trunk group, and generic analysis (GA). This action conforms to the
codec selection procedure for an ingress side.
3.
In phase 3, the IP gateway on the ingress side sends a REPLY to the Cisco PGW 2200 Softswitch
with the codecs preferred by Leg 1 and Leg 2.
4.
In phase 4, the Cisco PGW 2200 Softswitch sends an ADD to Leg 3 with the codecs preferred by
Leg 2. The Cisco PGW 2200 Softswitch sends an ADD to Leg 4 with the terminating codec list
obtained from the sigpath, trunkgroup, and GA, which conforms to the codec selection procedure
for an egress side.
5.
In phase 5, the IP gateway on the egress side sends a REPLY to the Cisco PGW 2200 Softswitch
with the terminating codec preferred by Leg 3 and Leg 4.
6.
In phase 6, the Cisco PGW 2200 Softswitch sends an outgoing INVITE with the terminating codec
preferred by Leg 4.
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.
Table 1
Codec Selection on the Ingress Side
Ingress Gateway
Egress
Gateway
VXSM
(IP-IP Gateway)
DBE
TDM Gateway
No Gateway
VXSM
Leg 1
Leg 1 and Leg 2
Leg 2
Leg 3
DBE
Leg 1
Leg 1 and Leg 2
Leg 2
Leg 3
TDM Gateway
Leg 1
Leg 1 and Leg 2
Leg 2
Not affected
No Gateway
Leg 1
Leg 1 and Leg 2
Leg 2
Not affected
H.248 Protocol-Phase 2
13
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
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.
Table 2
Codec Selection on the Egress Side
Ingress Gateway
Egress
Gateway
VXSM
(IP-IP Gateway)
DBE
TDM Gateway
No Gateway
VXSM
Leg 4
Leg 4
Leg 4
Leg 4
DBE
Leg 3 and Leg 4
Leg 3 and Leg 4
Leg 3 and Leg 4
Leg 3 and Leg 4
TDM Gateway
Leg 3
Leg 3
Leg 3
Leg 3
No Gateway
Leg 2
Leg 2
Not affected
Not affected
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 package according to ETSI TS 102 333
•
IP NAPT traversal package according to H.248.37
•
Cisco SBC enhanced VPN discrimination 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:
•
0—Indicates that NAT traversal in not enabled
•
1—Indicates that NAT traversal is enabled
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:
•
0—Indicates that NAT traversal will use the ETSI NAT traversal package
•
1—Indicates that NAT traversal will use the IP NAPT package, which is based on the H.248.37
specification
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:
•
If NATTraversalEnabled is set to 0, the Cisco PGW 2200 Softswitch does not add the NAT traversal
package in the local control part.
H.248 Protocol-Phase 2
14
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
•
If NATTraversalEnabled is set to 1 and NATTraversalMethod is set to 0, the Cisco PGW 2200
Softswitch sets ntr/nap = true in the local control part.
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.
•
If NATTraversalEnabled is set to 1 and NATTraversalMethod is set to 1, the Cisco PGW 2200
Softswitch sets signal ipnapt/latch (napt=LATCH or RELATCH).
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.
H.248 Protocol-Phase 2
15
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
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 1
prov-add:trnkgrpprof:name="2000", profile="profile2" // for the trunkgroup 2
Figure 5
VRF Names on Two DBE Gateways
Vrf1
GW1
Vrf2
GW2
Vrf3
Vrf4
273227
PGW
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)
Vrf1
GW1
H.248 Protocol-Phase 2
16
Vrf4
273228
PGW
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
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)
Vrf1
GW2
Vrf4
273229
PGW
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
Communication between PGW 2200 Softswitches is controlled by the EISUP. Cisco recommends that
you do not configure a DBE for inter-PGW 2200 call legs. Inter-PGW 2200 communications within a
service provider’s network are always conducted over EISUP interfaces.
H.248–Phase 2 Feature Restrictions
H.248 Protocol–Phase 2 has the following restrictions:
•
In SIP proxy mode, even if anchorMedia is always present on an ingress or egress trunk group, the
Cisco PGW 2200 Softswitch does not perform as a media anchor.
•
H.248–Phase 2 does not support Recursive SIP 302 handling.
•
For an H.323-originated call, because the Session Description Protocol (SDP) is identified remotely
by the Cisco H.323 Signaling Interface (HSI) in an ACM message, no announcement or local
ringback tone is played towards the H.323 side.
•
For a SIP-originated call, if the INVITE message does not identify the SDP, the Cisco PGW 2200
Softswitch does not play an announcement or local ring back tone toward the SIP side.
•
For an end call announcement, if there is no border gateway or gateway available on the ingress or
egress side for this service, the Cisco PGW 2200 Softswitch ignores this announcement.
•
For a midcall announcement or tone request, if no border gateway is available to play the
announcement or tone, the Cisco PGW 2200 Softswitch discards the request.
•
The Cisco PGW 2200 Softswitch uses only the DTMFCap trunk group property (dialplan result
type) when it performs IP trunk group selection.
•
The codec for T.38 Fax support is hardcoded to udptl in SDP.
•
If the IP side (SIP/EISUP/HSI) invokes T.38 Fax support, the Cisco PGW 2200 Softswitch does not
initiate upspeed or fallback to voice if the T.38 Fax request is rejected.
•
If a Cisco HSI in involved in supporting T.38 Fax service, the media cannot fall back to voice
because of an HSI limitation.
H.248 Protocol-Phase 2
17
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Understanding the H.248 Protocol–Phase 2 Feature
•
If an IP-IP gateway is involved in a call, a T.38 Fax call cannot fall back to voice.
Supported Standards, MIBs, and RFCs
Standards
H.248 Protocol–Phase 2 supports the following standards:
•
ITU-T H.248.1 05-2002—Gateway Control Protocol (Version 2)
•
ITU-T H.248.1 V2 (2002) 03-2004—Corrigendum 1
•
ITU-T H.248.2 (Annex F) 1/2000—Facsimile, Text Conversation and Call Discrimination Packages
•
ITU-T H.248.3 (Annex G) 11/2000—User Interface Elements and Action Packages
•
ITU-T H.248.3 (2000) 03-2004—Corrigendum 1
•
ITU-T H.248.4 (Annex H) 11/2000—Transport over Stream Control Transmission Protocol (SCTP)
•
ITU-T H.248.4 (2000) 03-2004—Corrigendum 1
•
ITU-T H.248.5 (Annex I) 11/2000—Transport over ATM
•
ITU-T H.248.6 (Annex J) 11/2000—Dynamic Tone Definition Package
•
ITU-T H.248.7 (Annex K) 11/2000—Generic Announcement Package (determined text)
•
ITU-T H.248.8 (Annex L 11/2000—Error codes and service change reason description
•
ITU-T H.248.8 (2002) 03/2004—Amendment 1
•
ITU-T H.248.9 (Annex M1) 01/2005—Advanced Media Server Packages
•
ITU-T H.248.10 (Annex M2) 07/2001—Media Gateway Resource Congestion Handling Package
•
ITU-T H.248.12 (Annex M4) 07/2001—H.248 Packages for H.323 and H.324 Interworking
•
ITU-T H.248.12 11/2002—Amendment 1
•
ITU-T H.248.13 (Annex M5) 03/2002—Quality Alert Ceasing Package
•
ITU-T H.248.14 (Annex M6) 03/2002—Inactivity Timer Package
•
ITU-T H.248.15 (Annex M2) 03/2002—SDP H.248 package attribute
•
ITU-T H.248.16 11/2002—Enhanced Digit Collection Packages and Procedures
•
ITU-T H.248.16 (2002) 03-2004—Corrigendum 1
•
ITU-T H.248.17 11/2002—Line Test Packages
•
ITU-T H.248.17 (2002) 03/2004—Corrigendum 1
•
ITU-T H.248.18 11/2002—Package for Support of Multiple Profiles
•
ITU-T H.248.20 11/2002—The use of local and remote descriptors with H.221/H.223 multiplexing
•
ITU-T H.248.22 07/2003—Shared Risk Group Package
•
ITU-T H.248.22 (2003) 01/2004—Erratum 1
•
ITU-T H.248.23 07/2003—Enhanced Alerting packages
•
ITU-T H.248.23 (2003) 03/2004—Corrigendum 1
•
ITU-T H.248.24 07/2003—Multi-frequency tone generation and detection packages
•
ITU-T H.248.25 07/2003—Basic CAS packages
•
ITU-T H.248.25 (2003) 03/2004—Corrigendum 1
H.248 Protocol-Phase 2
18
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Related Documents
•
ITU-T H.248.26 07/2003—Enhanced analogue lines packages
•
ITU-T H.248.26 (2003) 03/2004—Corrigendum 1
•
ITU-T H.248.26 (2003) 01/2005—Amendment 1
•
ITU-T H.248.27 07/2003—Supplemental tones packages
•
ITU-T H.248.28 03/2004—International CAS packages
•
ITU-T H.248.29 01/2005—International CAS Compelled Register Signaling Packages
•
ITU-T H.248.30 03/2004—RTCP extended performance metrics packages
•
ITU-T H.248.31 04/2004—Adaptive jitter buffer package
•
ITU-T H.248.32 01/2005—Detailed congestion reporting package
•
ITU-T H.248.33 01-2005—PCM frame spare bit package
•
ITU-T H.248.37 09-2005—PCM frame spare bit package
•
ETSI TS 102 333 V1.1.2 07-2004—Gate control protocol
•
ETSI TS 283 018 V1.1.1 06-2006— Resource and admission control: H.248 profile for controlling
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).
H.248 Protocol-Phase 2
19
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Provisioning Examples
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=6000
prov-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=1
prov-add: IPGW:POOLID="101", GW="h248-DBE-01"
H.248 Protocol-Phase 2
20
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Provisioning Examples
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=1
prov-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"
H.248 Protocol-Phase 2
21
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Provisioning Examples
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=0
prov-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=0
prov-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=1
prov-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",
prov-add:GWPOOL:NAME="101",
prov-add:IPGW:poolid="101",
prov-add:IPGW:poolid="104",
H.248 Protocol-Phase 2
22
DESC="gsr", PROFILE="dbe-profile"
DESC="default vxsm gateway pool", PROFILE="vxsm-profile1"
gw="mgx-8850-6"
gw="asr-1000"
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Provisioning Examples
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=1
prov-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=1
prov-add:rttrnk:weightedTG="OFF", name="rt1350", trnkgrpnum=1350
prov-add:rtlist:name="rtlist1350", rtname="rt1350", distrib="OFF"
H.248 Protocol-Phase 2
23
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Provisioning Examples
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-config
logging console 7
logging monitor 7
login timeout 0
line vty
session-limit 10
hostname 7635-SLOT11
boot system image: c76-sbck9-mzg.3.0.1_AS3_0_01.bin
serverfarm host cisco
serverfarm host sun
interface vlan 130
ip address 10.130.10.2 255.255.255.240
alias 10.130.10.4 255.255.255.240
peer ip address 10.130.10.3 255.255.255.240
no shutdown
ft interface vlan 131
ip address 10.130.10.18 255.255.255.240
peer ip address 10.130.10.19 255.255.255.240
no shutdown
ft peer 1
heartbeat interval 300
heartbeat count 10
ft-interface vlan 131
ft group 1
peer 1
associate-context Admin
inservice
ip route 0.0.0.0 0.0.0.0 10.130.10.1
ip route 10.130.10.4 255.255.255.255 10.130.10.1
username admin password 5 $1$faXJEFBj$TJR1Nx7sLPTi5BZ97v08c/ role Admin domain
default-domain
username www password 5 $1$UZIiwUk7$QMVYN1JASaycabrHkhGcS/ role Admin domain
default-domain
sbc sbc-11
dbe
vdbe
global
dtmf-duration 200
congestion-cleared 60
congestion-threshold 80
local-port 2944
control-address h248 ipv4 10.130.10.4
controller h248 1
remote-address ipv4 10.0.7.230
transport udp
h248-profile gatecontrol
attach-controllers
H.248 Protocol-Phase 2
24
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Provisioning Examples
media-address pool ipv4 10.130.10.4 10.130.10.13 port-range 5000 6000 signaling
media-address pool ipv4 10.130.10.4 10.130.10.13 port-range 17000 32000 voice
media-timeout 30
overload-time-threshold 100
deact-mode normal
activate
Sample 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 SBC1
ip address 33.33.36.101 255.255.255.0 secondary
ip address 33.33.36.1 255.255.255.0
!
!
sbc pgw dbe
vdbe global
h248-napt-package napt
h248-inactivity-duration 6000
local-port 2944
control-address h248 ipv4 33.33.36.1
controller h248 1
remote-address ipv4 10.0.248.98
controller h248 2
remote-address ipv4 10.0.248.99
attach-controllers
location-id 1
media-address pool ipv4 33.33.36.110 33.33.36.116
media-timeout 3
activate
!
!
H.248 Protocol-Phase 2
25
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
MML Command Reference
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.
addmgcdn
2.
addmgcip
3.
addmgcgrpmgc
4.
addh248assoc
5.
cnfh248param
6.
cnfh248nameschema
7.
addtermtype
8.
cnfh248is
For a detailed description of the VXSM CLI commands, see the Cisco Voice Switch Services(VXSM )
Configuration and Com m and Reference G uide for M G X 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
H.248 Protocol-Phase 2
26
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
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
Purpose:
Adds a gateway pool in the Cisco PGW 2200 Softswitch.
Syntax:
prov-add:GWPOOL:NAME=”gateway pool id”, DESC=”Gateway pool description”,
PROFILE=”gateway pool profile”
Input
Description:
NAME—Gateway pool ID, which is an integer in the range 1–9999. The values 2–100
are reserved for future use.
DESC—Gateway pool description; this description can be up to 128 characters long.
PROFILE—MML name of a previously configured gateway pool.
Example:
Comments:
prov-add:GWPOOL:NAME=”101”, DESC=”DBE gateway pool”,
PROFILE=”GWPool_profile1”
1.
The gateway pool ID 1 identifies the global default VXSM gateway pool.
2.
You can use the MML command prov-ed to change the gateway pool profile. In
this case, the new gateway pool profile is checked against all of the gateways in
this gateway pool. Also, you can use the command prov-ed to change the
gateway pool description.
3.
prov-dlt:GWPOOL. The associated board gateways are disassociated from this
gateway pool first.
H.248 Protocol-Phase 2
27
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
MML Command Reference
PROV-ADD:IPGW:POOLID—Add Border Gateway to Gateway Pool
Purpose:
Add a border gateway to a gateway pool.
Syntax:
prov-add:IPGW:POOLID="gateway pool id", GW="external node"
Input
Description:
POOLID—Gateway pool ID, which is an integer in the range of 1–9999.
Example:
prov-add: IPGW:POOLID="100", GW="dbe-01"
Comments:
H.248 Protocol-Phase 2
28
GW—MML name of previously configured gateway name.
1.
The parameters are stored in the data file gwPools.dat, which contains the
EXTNODE compID.
2.
To add a gateway to the global default VXSM gateway pool, enter DEFAULT in
the POOLID field.
3.
Use the MML command prov-dlt:IPGW to remove a border gateway from the
gateway pool. If you wish to remove a gateway, first you should remove it from
each gateway pool.
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
MML Command Reference
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
Purpose:
Configuring a gateway pool profile.
Syntax:
prov-add:PROFILE:NAME=”profile name”, TYPE=”GWPOOLPROFILE”,
VALIDATION=”ON”, Cat=”Category”, PropertyName1=”Property Value1”,
PropertyName2=”Property Value2”
Input
Description:
NAME—MML name of a gateway pool profile. This name can be up to 20
alphanumeric characters long.
TYPE—In this case, the profile type is GWPOOLPROFILE.
VALIDATION—Perform property validation.
Cat—Property category name that is used to filter the properties.
Example:
Prov-add:PROFILE:NAME=”VXSM-Profile1”, TYPE=”GWPOOLPROFILE”,
VALIDATION=”ON”, Cat=”Profile”, GatewayAnnSupport=”1”,
GatewayToneSupport=”1”, GatewayDTMFSupport="1", GatewayCodecSupport=”1”,
GatewaySelectionMethod="1"
Comments:
The parameters are stored in the data file profiles.dat.
PROV-ADD:H248PATH:NAME—Add Call Limiting Label to Gateway
Purpose:
Add a call limiting label to a gateway.
Syntax:
prov-add:H248PATH:NAME=”h248-sigpath-01“, DESC=”service to H248”,
EXTNODE=”external node”, LABEL=”loclbl1”
Input
Description:
LABEL—Call limiting label for this gateway.
Example:
prov-add:H248PATH:NAME=”h248-sigpath-01”, DESC=”Service to H248”,
EXTNODE=”h248-VXSM-01”, LABEL=”loclbl1”
Comments:
1.
LABEL is used only to control the simultaneous contexts on a gateway. You
cannot use the same label elsewhere on a sigPath/trunk group/dialplan.
2.
Only the IP-IP call is counted for this label. Provision LABEL only for DBE.
Note
Because a VXSM can be used simultaneously as a TDM gateway, never add
LABEL for a VXSM gateway.
H.248 Protocol-Phase 2
29
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
PROV-ED:PROFILE:NAME—Add a VRF Name to a PROFILE
Purpose:
Add a VRF name property to a profile.
Syntax:
prov-ed:profile:name="profile name", insidevrfname="vrf name"
prov-ed:profile:name="profile name", outsidevrfname="vrf name"
Input
Description:
vrfname—The VRF name for the trunkgroup or domain.
Example:
prov-ed:profile:name="sipprofile", insidevrfname="vpn_a"
Comments:
The profile is a SIP, EISUP or Domain profile, and is attached to the trunkgroup or
domain.
PROV-ED:PROFILE:NAME—Add Codecs to a Profile for a DBE Gateway
Purpose:
Add an ordered series of valid codecs to a profile.
Syntax:
prov-ed:profile:name="profile_name", gwdefaultcodecstring="G.711u;
G.711a"
Input
Description:
gwdefaultcodecstring—The ordered list of acceptable codecs.
Example:
prov-ed:profile:name="profile_name", gwdefaultcodecstring="G.711u;
G.711a"
Comments:
The specification of codec strings can be from 1–140 characters.
The valid values are: NULL, G.711u, G.711a, G.726-32, G.726-24, G.726-16, G.729,
G.729a, G.729b, G.729b-L, G.723.1-H, G.723.1-L, G.723.1a-L, G.GSM-F,
G.GSM-H, or G.GSM-eF
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, page 31
•
Properties, page 31
•
Billing Interface, page 36
H.248 Protocol-Phase 2
30
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
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 3
Gateway Pool Profile Properties
Property Name
Purpose
GatewayToneSupport
Specifies whether the gateway pool 0—Does not support tone
supports playing a tone to the IP side. 1—Supports tone
GatewayAnnSupport
Specifies whether the gateway pool
supports playing an announcement
package to the IP side.
0—Not supported
Specifies whether the gateway pool
supports transcoding for IP-to-IP
traffic.
0—Not supported
Describes the DTMF capability
support for a gateway pool
0—Not supported
GatewayCodecSupport
GatewayDTMFSupport
Value Range
1—Supported
1—Supported
1—RFC 2833
2—Inband and RFC 2833
GatewaySelectionMethod
Specifies the border gateway
selection method within a gateway
pool
0—Sequence
1—Round robin
H.248 Protocol-Phase 2
31
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
Table 3
Gateway Pool Profile Properties (continued)
Property Name
Purpose
*.GWDefaultAudioCodecString Gateway default audio codec string.
Enables the IOCC-MGCP to send the
ordered series of codec choices
separated by semicolons. Refer to
your gateway documentation for a
list of supported codec names. The
following values represent some of
the more common codec names.
Value Range
Values: NULL, G.711a,
G.711u, G.729, G.729a, and
G.729b
Additional values:
G.726-32, G.726-24,
G.726-16, G.729b-L,
G.723.1-H, G.723.1-L,
G.723.1a-L, G.GSM-F,
G.GSM-H, and G.GSM-eF
Default: NULL
*.GWDefaultVideoCodecString
H.248 Protocol-Phase 2
32
Gateway default video codec string.
Enables the IOCC-MGCP or
IOCC-H248 to send the ordered
series of codec choices separated by
semicolons. Refer to your gateway
documentation for a list of supported
codec names. The following values
represent some of the more common
codec names.
Values are: NULL, H.264;
H263; H261; H263-1988;
JPEG; MPV; CelB; MP2T
and nv.
Default: NULL
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
Table 4 lists new trunk group and gateway pool properties that support operation of
H.248 Protocol–Phase 2.
Table 4
Trunk Group and Gateway Pool Properties
Property
Definition
GatewayPool
Associates the default gateway pool with an IP trunk group so that media can
be anchored on this gateway pool.
Integer: 0–9999,
Default: 0 (indicates that there is no gateway pool associated with this IP
trunk group)
AnchorMedia
Defines the media anchor policy on this IP trunk group.
Integer: 1–3:
1—Never anchor media on the IP trunk group.
2—Optional. The policy function determines whether to anchor media on the
IP trunk group.
3—Always anchor media on the IP trunk group.
Default: 1
AnchorPolicy
Defines the media anchor policy in the policy function. Specifies whether to
enable a gateway pool on an IP trunk group. The anchor policy applies only
to an egress IP trunk group.
Integer: 0 or 1
0—Do not enable the SPDM to change gateway pool usage. In response to a
service check failure, the SPDM does not enable use of the gateway pool
even if the AnchorMedia property is set to Optional on this trunk group.
Consequently, the Cisco PGW 2200 Softswitch tries the next trunk group.
1—The SPDM enables use of the gateway pool on an IP trunk if the
AnchorMedia property is set to Optional. If the enabled gateway pool
satisfies the service requirement, the SPDM enables the Cisco PGW 2200
Softswitch to use the gateway pool.
Default: 0
AnnouncementOption
Specifies whether playing an announcement to the originating side is
mandatory. This applies only to an ingress IP trunk group.
Integer: 0 or 1
0—Playing an announcement is optional.
1—Playing an announcement is mandatory.
Default: 0
H.248 Protocol-Phase 2
33
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
Table 4
Trunk Group and Gateway Pool Properties (continued)
Property
Definition
ToneOption
Specifies whether playing a tone to the originating side is mandatory. This
applies only to an ingress IP trunk group.
Integer: 0 or 1
0—Playing a tone is optional.
1—Playing a tone is mandatory.
Default: 0
*.DummyAudioCodecString
Specifies the dummy codec list in an H.248 add request when neither remote
SDP nor a local codec is provisioned. This property applies only for a DBE.
Values are NULL, G.711u, G.711a, G.726-32, G.726-24, G.726-16, G.729,
G.729a, G.729b, G.729b-L, G.723.1-H, G.723.1-L, G.723.1a-L, G.GSM-F,
G.GSM-H, and G.GSM-eF. You must separate the values in the dummy
codec list with separated by semicolons.
Valid values: a string from 1-140 characters
Default dummy codec string:
G.711u;G.711a;G.726-32;G.726-24;G.726-16;G.729;G.729a;G.729b;G.729
b-L;G.723.1-H;G.723.1-L;G.723.1a-L;G.GSM-F; G.GSM-H;G.GSM-eF
*.DummyVideoCodecString
Specifies the dummy video codec list in an H.248 add request when neither
remote SDP nor a local codec is provisioned. This property applies only for
a DBE. Values are: NULL; H.264; H263; H261; H263-1998; JPEG; MPV;
CelB; MP2T; nv, separated by semicolons.
Valid values: a string from 1-140 characters
Default: NULL
NATTraversalEnabled
Specifies whether the Cisco PGW 2200 Softswitch performs NAT traversal
in an add or modify request. The detailed NAT traversal method depends on
the provisioning of the sigPath property NATTraversalMethod.
Integer: 0 or 1
0—NAT traversal is not enabled.
1—NAT traversal is enabled.
Default: 0
NATTraversalMethod
Specifies the NAT traversal method that the Cisco PGW 2200 Softswitch
applies to the gateway.
Integer: 0 or 1
0—Apply NAT traversal using the ETSI NAT traversal package.
1—Apply NAT traversal using the IP NAPT package according to H248.37.
Default: 0
H.248 Protocol-Phase 2
34
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
Table 4
Trunk Group and Gateway Pool Properties (continued)
Property
Definition
IPTermNumGroups
According to the ETSI profile, an RTP termination ID conforms to the
format ip/group id/interface id/id. This property specifies the largest group
number provisioned on this gateway.
Integer: 0–255. (0 specifies that the group field for the RTP termination ID
is not used.)
Default: 255
IPTermNumInterfaces
According to the ETSI profile, an RTP termination ID conforms to the
format ip/group id/interface id/id. This property specifies the number of
interfaces that are provisioned for this gateway.
Integer: 0–8
Default: 0. (0 specifies that the interface field for RTP termination ID is not
used.)
IPTermNumTerms
According to the ETSI profile, an RTP termination ID conforms to the
format ip/group id/interface id/id. This property specifies the number of
terminations that are allowed in a particular group ID and interface ID.
Integer: 1–1364
Default: 1364
CallHoldInterworkingEnabled
Indicates whether Cisco PGW 2200 Softswitch interworks call hold and
terminal portability (TP) between SIP/H.323, EISUP, and ISUP. When this
property is configured as disabled, Cisco PGW 2200 Softswitch drops
HOLD and TP indications coming from the ISUP side. If the property is
configured enabled, Cisco PGW 2200 Softswitch maps the ISUP side HOLD
and TP to SIP Re-Invite.
Valid values:
0—TDM to IP hold interworking disabled (but IP to TDM hold interworking
enabled)
1—Bidirection hold interworking enabled
2—IP to TDM hold interworking disabled (but TDM to IP hold interworking
enabled)
3—Bidirection hold interworking disabled
Default Value: 1
Dynamically Reconfigurable: yes
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).
H.248 Protocol-Phase 2
35
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
•
If CallHoldInterworkingEnabled is set to 0, the held party is not informed that the call is held.
•
If CallHoldInterworkingEnabled is set to 1, the Cisco PGW 2200 Softswitch informs the held party
of this call hold (with an INVITE message for SIP or a NOTIFY message for EISUP), and changes
the mode of the leg controller that is closest to the held party after response.
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.
H.248 Protocol-Phase 2
36
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
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 EST
RTRV
"LMAgent:
-----------------------------------------------------------------SBE Fully Featured License
9.8 permanent
-----------------------------------------------------------------Interface Name
Entitled
Provisioned
SS7Interface
Y
N
PRIInterface
Y
N
PBXInterface
Y
N
INAPInterface
Y
N
LIInterface
Y
N/A
SBEInterface
Y
Y
-----------------------------------------------------------------Configure TDM Ports
Entitled
Provisioned
Available
Call Control
100060
0
100060
-----------------------------------------------------------------M
<Press 'SPACE' for next page, 'Enter' for next line or 'q' to quit this output>
Runtime TimesTen
Entitled
Provisioned
Available
License
2000000
0
2000000
-----------------------------------------------------------------Run Time License
TDMPorts
SIP
H323
Entitled Number
100060
400060
400060
Current Usage
0
0
0
Peak Usage(15 min)
0
0
0
Peak Usage(1 hour)
0
0
0
Peak Usage(24 hour)
0
0
0
------------------------------------------------------------------"
;
H.248 Protocol-Phase 2
37
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
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.
$lmreport
SIP sigPath:
Yes
SS7 sigPath:
No
DPNSS sigPath: No
BRI sigPath:
No
QSIG sigPath:
No
PRI sigPath:
No
INAP interface: No
SBE interface: Yes
Configuration Time Ports count = 0
Provisioned TimesTen count = 0
Check 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::
M
MGC-02 - Media Gateway Controller 2008-11-24 01:17:28.083 EST
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:
M
MGC-02 - Media Gateway Controller 2008-11-24 12:04:21.940 CST
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.
H.248 Protocol-Phase 2
38
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
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 CST
RTRV
"session=1031-test-eisuptype:profile"
/*
ProfileType
ProfileName
-------------------- -------------------sipprofile
p1340
----------------------------------------anchormedia = 3
anchorpolicy = 1
custgrpid = 1111
gatewaypool = 101
insessiontimer = 90
mgcdomain = 10.0.248.97
M
Check 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 CST
RTRV
"session=1031-test-eisuptype:profile"
/*
ProfileType
ProfileName
-------------------- -------------------sipprofile
p1340
----------------------------------------anchormedia = 3
anchorpolicy = 1
custgrpid = 1111
gatewaypool = 101
insessiontimer = 90
mgcdomain = 10.0.248.97
M
H.248 Protocol-Phase 2
39
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Software Changes for This Feature
Capturing 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
Issue the command sta-sc-trc to start the MDL trace
sh-vwjetta mml> sta-sc-trc:sip-path-1:log="CHK",confirm
MGC-02 - Media Gateway Controller 2008-11-25 05:37:21.580 CST
COMPLD
"sip-path-1 - this trace will stop automatically after 1800 seconds, or when MCL
reaches MCL1, or when provision is changed."
M
Step 2
Make the call.
Step 3
Issue the following command to stop the MDL trace.
sh-vwjetta mml> stp-sc-trc:all:
M
MGC-02 - Media Gateway Controller 2008-11-25 05:40:22.740 CST
COMPLD
"ALL:Trace stopped for the following files:
../var/trace/CHK_sip-path-1_20081125053721.btr
"
;
Step 4
Change directory to /opt/CiscMGC/var/trace/.
Step 5
Issue command ‘get_trc.sh CHK_sip-path-1_20081125053721.btr’ to generate the trace file
CHK_sip-path-1_20081125053721_btr_1.trc.
Step 6
Send the trace file to the Cisco TAC.
To collect the a platform.log file for the Cisco PGW 2200 Softswitch, complete the steps of the following
procedure.
Step 1
Enable SIP module debug level by issuing the MML command set-log:sip-1:DEBUG, confirm
Step 2
Enable H248 module debug level by issuing the MML command set-log:H248-1:DEBUG, confirm
Step 3
Enable Engine module debug level by issuing the MML command set-log:ENG-01:DEBUG, confirm
Step 4
Make the call.
Step 5
Collect the file /opt/CiscoMGC/var/log/platform.log.
Step 6
Disable SIP module debug level by issuing the MML command set-log:sip-1:ERR, confirm
Step 7
Disable H.248 module debug level by issuing the MML command set-log:H248-1:ERR, confirm
Step 8
Disable Engine module debug level by issuing the MML command set-log:ENG-01:DEBUG, confirm
H.248 Protocol-Phase 2
40
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Obtaining Documentation, Obtaining Support, and Security Guidelines
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.
Table 5
Acronyms and Expansions
Acronym
Expansion
BGP
Border Gateway Protocol
CDR
Call detail record
DBE
data border element
DSCP
DiffServ Code Point
DSP
digital signal processor
DSS1
Digital Subscriber Signaling 1
DTMF
Dual Tone Multi Frequency
DTMFCAP
Dual Tone Multi-Frequency Capability
EISUP
Enhanced ISUP
ETSI
European Telecommunications Standards Institute
HSI
H.323 Signaling Interface
IETF
Internet Engineering Task Force
IP
Internet Protocol
ISUP
ISDN User Part
ITU
International Telecommunication Union
MDL
Message Definition Language
MG
media gateway
MGC
media gateway controller
MGCF
Media Gateway Control Function
MGCP
Media Gateway Control Protocol
MML
Man-Machine Language
MPLS
Multiprotocol label switching
NAPT
network address and port translation
NAT
network address translation
H.248 Protocol-Phase 2
41
Cisco PGW 2200 Softswitch H.248 Protocol–Phase 2 Feature Module
Glossary
Table 5
Acronyms and Expansions (continued)
Acronym
Expansion
NGNSP
Next Generation Network Service Provider
PGW
PSTN gateway
PSTN
public switched telephone network
RTCP
Real Time Conferencing Protocol
RTP
RealTime Transport Protocol
SBC
Session Border Control
SDP
Session Description Protocol
SIP
Session Initiation Protocol
SPDM
service policy decision module
SS7
Signaling System 7
TDM
time-division multiplexing
TGW
trunking gateway
VPN
Virtual Private Network
VRF
Virtual Routing and Forwarding
VXSM
Voice Switch Service Module
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase,
Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good,
Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks;
Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card,
and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, 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 Lumin, Cisco Nexus,
Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast,
EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream,
Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV,
PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, 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. (0910R)
H.248 Protocol-Phase 2
42