Guest

Cisco BTS 10200 Softswitch

H.323 Video, Routing, and Transparency Features for Release 4.2

  • Viewing Options

  • PDF (631.8 KB)
  • Feedback
Cisco BTS 10200 Softswitch H.323 Video, Routing, and Transparency Features for Release 4.2

Table Of Contents

Cisco BTS 10200 Softswitch H.323 Video, Routing, and Transparency Features for Release 4.2

Contents

Prerequisites

Restrictions

Technical Information

Interoperability with Other Endpoints Including Cisco CallManager

Prerequisites for Interoperability

Limitations on Interoperability

Message Tunneling and Protocol Transparency for H.323-Based Transit Traffic

Additional H.323-Related Feature Enhancements

How to Provision H.323 Features for Release 4.2

Provision H.323-Based TGs, Logical GWs and GKs

H.323-Based Logical GWs Internal to the Cisco BTS 10200 Softswitch

Prerequisites

Provision H.323-Based Video Phone Terminals and Subscribers

Prerequisites

Provision H.323-Based Outbound Routing Data

Understanding the Outbound Routing Process

Outbound Routing Option Summary

Outbound H.323 Calls

H.323 Tandem Calls With Circuit Info Sent

SS7-originated Calls Retransmitted As Outbound H.323 Calls With Circuit Info

Provision H.323-Based Inbound Routing

Additional Information for Provisioning ANI Screening and Routing

ANI Screening vs. ANI-Based Routing

Identification of H.323 Terminal Property Based On ANI

ANI Screening

ANI-Based Routing

Advanced Provisioning Options

H.323 Protocol Transparency Functions

Additional Advanced H.323 Features

Configuration Example

Example

Troubleshooting Information

Outgoing Trunk Group is Out of Service

Solution

Outgoing H.323 Gateway is Out of Service

Solution

H.323 Gateway Fails to Register With GK (Invalid Alias)

Solution

Outgoing H.323 Gateway Unregistered With GK and Needs to Use RAS

No Matching Dial Plan Found on Incoming H.323 Trunk Group

Solution

Configuration at Softswitch or Gatekeeper Has Placed Routing Into a Loop

Solution

Outgoing H.323 Calls Routed to Incorrect Endpoint When Using RAS

Solution

Outgoing H.323 Calls Routed to Incorrect Endpoint When Using Direct Signaling

Solution

RAS Still Used When Outgoing H.323 Call is Provisioned to Use Direct Signaling

Solution

Appendix A: Interoperability Data

Appendix B: Billing Data Generation and Data Fields

Billing Data Generation

Billing Data Fields

Technical Assistance


Cisco BTS 10200 Softswitch H.323 Video, Routing, and Transparency Features for Release 4.2


This document describes the H.323 video, routing, and transparency feature enhancements for Release 4.2 of the Cisco BTS 10200 Softswitch. It also describes the tasks and commands for provisioning and using these capabilities. The following enhancements are provided in this release:

Support for video capability on H.323-based subscriber phones

Support for video on H.323-based trunk groups

H.323 routing enhancements for inbound and outbound call legs

ANI-based screening and routing enhancements

Additional H.323 and video-related billing records

Enhanced interoperability with other endpoints, including Cisco CallManager, using H.323 protocol interface

Improved message tunneling and protocol transparency for H.323-based transit traffic

Additional H.323-related feature enhancements

These enhancements can be applied to managed H.323 networks that contain the Cisco BTS 10200 Softswitch and the following network element types:


Note For interoperability with specific external devices, see "Restrictions" section.


H.323-based IP PBX systems, including Cisco CallManager

Analog phones connected to customer premises equipment (CPE) such as integrated access devices (IADs)

H.323 primary rate interface (PRI) gateways (GWs)

H.323 IP-to-IP GWs

H.323-based gatekeepers (GKs)

H.323-based video phones

H.323-based audio phones

Feature History for Cisco BTS 10200 Softswitch H.323 Video, Routing, and Transparency Features for Release 4.2

Release
Modification

Release 4.2

OL-5798-01 — This feature set was introduced.

OL-5798-02 — Added information about:

Route advance, reattempt, and redirection.

Troubleshooting procedures for H.323.

OL-5798-03 — Added information on route advance (number of attempts).


Contents

Prerequisites

Restrictions

Technical Information

How to Provision H.323 Features for Release 4.2

Configuration Example

Troubleshooting Information

Appendix A: Interoperability Data

Appendix B: Billing Data Generation and Data Fields


Note The following terminology is used throughout this document when referring to connection methods described in ITU-T Recommendation H.323, Packet-based multimedia communications systems, Draft v4 (11/2000):
    - Fast-start refers to fast-connect procedures.
    - Slow-start refers to non-fast-connect mode.


Prerequisites

For direct routing scenarios (not using RAS signaling to a GK) the TSAP addresses of the far-end H.323 endpoints must be identified, so that they can be provisioned in the Cisco BTS 10200 Softswitch database via CLI command (or other provisioning tool). The TSAP addresses are provisioned for each applicable TG or terminal.

If the Cisco BTS 10200 Softswitch is connected to one or more GKs in the H.323 network, the GKs must be configured appropriately to support video calls:

The GKs may be configured to reroute an originating call from a video terminal to the Cisco BTS 10200 Softswitch first (before completing the call to the terminating video terminal). The Cisco BTS 10200 Softswitch participates in the video call as an H.323 proxy (IP-to-IP MGW).

The GKs may be configured to provide validation and registration of the video phone functions performed by the Cisco BTS 10200 Softswitch. The Cisco BTS 10200 Softswitch does not provide GK functionalities such as registration and authentication of endpoints.


Note It may not be necessary to configure the GK address in the individual H.323 video phones. The Cisco BTS 10200 Softswitch can receive incoming calls from an H.323 phone with or without using the GK, provided that the H.323 phone supports direct routing


The H.323-based video phones must have the following capabilities:

The video phones must be able to communicate with the GK, if a GK is present in the network.

The video phones must be capable of using slow-start connection procedures.

Restrictions

The features described in this document are based on ITU-T Recommendation H.323, Packet-based multimedia communications systems, Draft v4 (11/2000). H.323-based endpoints that do not comply fully with this draft of the ITU-T recommendation might not support all of these same features. When selecting H.323-based devices, Cisco recommends that you discuss your specific requirements with your Cisco account team.

The list below identifies the specific peripheral platforms and software loads that have been tested by Cisco for H.323 interoperability with the Cisco BTS 10200 Softswitch Release 4.2 software. Earlier or later releases of platform software might be interoperable and it might be possible to use other functions on these platforms. This list certifies only that the required interoperation of these platforms, the functions listed, and the protocols listed have been successfully tested with the Cisco BTS 10200 Softswitch. If you would like to use additional features and devices, contact your Cisco account team for assistance.

H.323-based video phones:

Leadtek BVP8770, Version 1.2

Vizufon CIP-4500, CHIUNICOM v1.2

Analog telephone adapters (ATAs):

Cisco ATA Release 3.1.0

H.323-based PRI gateways

Cisco AS5300, Cisco AS5350, and Cisco AS5400 - IOS Release 12.3(7)T

H.323 IP-to-IP gateways

Cisco 2600 Gateway - IOS Release 12.3(7)T

H.323 Gatekeepers

Cisco 2600, Cisco 3600, Cisco 7200 - IOS Release 12.2(13)T9

IP PBX

Cisco CallManager 4.0(1)

The following restrictions and limitations apply to video phone calls connected through the Cisco BTS 10200 Softswitch:

Video calls must be originated using slow-start procedures. H.323 fast-connect signaling does not work for video calls.

If a video phone uses an H.245 tunneling feature, H.245 tunneling must be disabled in the Cisco BTS 10200 Softswitch H323-TERM-PROFILE table associated with that phone.

In some cases, video phones do not support codec negotiation. When codec negotiation is not supported by the phones, the originating and terminating video phones must use the same codec.

Video calls cannot be originated or terminated using multiline hunt group (MLHG) line access.

In general, the Cisco BTS 10200 Softswitch preserves stable calls during an internal transient such as a process restart or platform switchover. However, H.323-based calls can only be preserved if the connection uses both H.323 Annex E and fast-start functionalities. If the video endpoints in a call do not support fast-start, these calls are dropped when there is a platform switchover or a process restart that affects H.323 call processing.

The following limitations apply to Cisco BTS 10200 Softswitch support for route advance, reattempt, and redirection on H.323-based call legs:

You must provision a special token (MISC-UNSUPP in the H323-TG-PROFILE [or H323-TERM-PROFILE] table) to enable the system to support this feature set.

The system supports this feature set for calls using fast-start procedures on the H.323 call leg(s). It does not support this feature set for calls involving H.323-based GWs and endpoints using slow-start procedures.

The Cisco BTS 10200 Softswitch sends the fast-start element only in the ALERTING/PROGRESS message, and not in the CALL PROC message.

Number of route advance attempts—The route table in the Cisco BTS 10200 Softswitch database allows the service provider to provision a list of up to 10 trunk groups (TG1 to TG10), and a parameter for selecting the priority of the TGs for routing (TG-SELECTION). The system attempts to route the call on the highest priority TG. If the call cannot be completed on the highest priority TG, the system attempts to use the next (lower priority) TG, a process known as route advance. The system attempts route advance to lower priority TGs up to five times. (Any TG in the list that is administratively out of service is not counted as an attempt.) If all five attempts fail, the call is released, and the system provides a release announcement.

The Cisco BTS 10200 Softswitch provides connectivity with H.323 IOS-based gateways, Cisco CallManager, and MGCP-based gateways. These systems interoperate to provide subscriber features such as call forwarding, call waiting, call transfer, and three-way calling. See Appendix A: Interoperability Data (at the end of this document) additional data regarding interoperability of the Cisco BTS 10200 Softswitch with H.323 IOS-based gateways, Cisco CallManager, and MGCP-based gateways.

Technical Information

This section provides technical information about the implementation of H.323 features. The Cisco BTS 10200 Softswitch provides native H.323 signaling, which allows it to communicate directly with H.323 gatekeepers (GKs) and gateways. The Cisco BTS 10200 Softswitch can be configured as up to four logical H.323 gateway instances. The Cisco BTS 10200 Softswitch H.323 subsystem includes H.225/RAS signaling control and H.245 connection control. (RAS = registration, administration, and status protocol.)

The topics covered in this section are:

Interoperability with Other Endpoints Including Cisco CallManager

Message Tunneling and Protocol Transparency for H.323-Based Transit Traffic

Additional H.323-Related Feature Enhancements

Interoperability with Other Endpoints Including Cisco CallManager

The interoperability between the Cisco BTS 10200 Softswitch, Cisco CallManager, and Cisco IOS H.323 gateways enhances the delivery of call control features between enterprise networks and service provider networks.

The Cisco BTS 10200 Softswitch functions as a logical H.323 gateway to communicate with
Cisco CallManager and other H.323 gateways. The Cisco BTS 10200 Softswitch also provides signaling for other trunks and lines over MGCP and SIP protocols. In addition, the Cisco BTS 10200 Softswitch provides access to the public switched telephone network (PSTN). It communicates with signaling gateways (SGs) for SS7 signaling, and with trunking gateways (TGWs) that provide the bearer path. The details of these signaling links are shown in Figure 1.


Note The Cisco BTS 10200 Softswitch can be configured as up to four logical H.323 gateways.


Figure 1 Signaling Links with the Cisco BTS 10200 Softswitch and Cisco CallManager

The Cisco BTS 10200 Softswitch can be used to connect calls between two phones that reside on different Cisco CallManager systems (see Figure 2). Signaling of certain information, for example connected name and number information, is transparently passed from the terminating
Cisco CallManager via the Cisco BTS 10200 Softswitch back to the originating Cisco CallManager.

Figure 2 Example of Connecting Calls from Phones On Separate Cisco CallManager Systems


Note For a more complete description of all Cisco BTS 10200 Softswitch features, refer to the Cisco BTS 10200 Softswitch System Description.


The following details are covered in this section:

Prerequisites for Interoperability

Limitations on Interoperability

Prerequisites for Interoperability

For the Cisco BTS 10200 Softswitch, the Cisco CallManager and an IOS-based H.323 GW to interoperate, the following configurations are required:

Following are the software releases tested for interoperability with the features described in this document:

Cisco BTS 10200 Softswitch—Release 4.2

Cisco CallManager —4.0(1)

Cisco H.323 GWs—IOS Release 12.3(7)T


Note Contact your Cisco account team regarding any possible updates to these releases or patches that could occur after publication of this document.


On Cisco CallManager, configure the route to the Cisco BTS 10200 Softswitch as "intercluster trunk" with media termination point (MTP) selected on this trunk.


Note Some subscriber features can be provided by both the Cisco BTS 10200 Softswitch and Cisco CallManager. You must select MTP on Cisco CallManager so that Cisco CallManager can provide these subscriber features.


To ensure signaling compatibility between the Cisco BTS 10200 Softswitch and Cisco CallManager, the following provisioning operations should be performed on the Cisco BTS 10200 Softswitch. These procedure are provided in the "How to Provision H.323 Features for Release 4.2" section.

(Optional) Assign a main subscriber ID to the H.323 trunk group (TG) that connects the Cisco BTS 10200 Softswitch with Cisco CallManager. (This is similar to provisioning a TG to a PBX.)


Note Assign a main subscriber ID only if Cisco CallManager is used as a PBX. The system uses the subscriber ID to perform screening and routing.

If Cisco CallManager is not used as a PBX, do not assign a main subscriber ID, and the system uses the TG properties to perform screening and routing.


Enable quality of service (QoS) codecs PCMU and PCMA on any TG that is used for connection to Cisco CallManager. In addition, disable codec negotiation for the applicable H.323 TG profile. (Do not perform dynamic codec negotiation for these calls.)

Disable generic transparency descriptor (GTD) signaling on the Cisco BTS 10200 Softswitch for any trunk group (TG) used for connection to Cisco CallManager.

Verify that the value of the CODEC-MOD-DURING-CALL token in the CA-CONFIG table is set to its default value of Y (yes).


Caution CODEC-MOD-DURING-CALL must be set to Y. If you set it to N, some features may not work.

Limitations on Interoperability

This section describes limitations on interoperability between the Cisco BTS 10200 Softswitch and Cisco CallManager.

Signaling and Processing Limitations

Signaling and processing limitations are as follows:

DTMF signaling limitation—Only the out-of-band DTMF mode is used over H.323 for signaling between Cisco CallManager and the Cisco BTS 10200 Softswitch.

Limitation on H.323-based calls on failover:


Note If an H.323-based call processing function in the Cisco BTS 10200 Softswitch experiences a fault, it can restart automatically and begin processing new calls. If it is unable to restart automatically, the standby process in the companion host machine becomes active and takes over the H.323 functions. This event (standby process taking over for a previously active process on a companion host) is called failover.


The Cisco BTS 10200 Softswitch uses Annex E redundancy capabilities to preserve stable calls during a restart or failover. However, all stable calls between the Cisco BTS 10200 Softswitch and Cisco CallManager are dropped during a restart or failover in the Cisco BTS 10200 Softswitch. Normal processing of new calls between Cisco BTS 10200 Softswitch and Cisco CallManager resumes after the H.323 call processing function is running.


Note Annex E refers to ITU-T Recommendation H.323 - Annex E (05/99).


T.38 Fax calls cannot be connected between the Cisco BTS 10200 Softswitch and
Cisco CallManager.

Limitations On Subscriber Features

The Cisco BTS 10200 Softswitch provides connectivity with H.323 IOS-based gateways, Cisco CallManager, and MGCP-based gateways. These systems interoperate to provide subscriber features such as call forwarding, call waiting, call transfer, and three-way calling. See Appendix A: Interoperability Data (at the end of this document) additional data regarding interoperability of the Cisco BTS 10200 Softswitch with H.323 IOS-based gateways, Cisco CallManager, and MGCP-based gateways.

Message Tunneling and Protocol Transparency for H.323-Based Transit Traffic

The Cisco BTS 10200 Softswitch supports the interconnection of multiple H.323-based devices by transparently passing certain H.323 messages in calls that transit the Cisco BTS 10200 Softswitch. It also provides signaling functions that enable interoperability with a variety of H.323 and non-H.323 endpoints. These functions are collectively referred to as H.323 protocol transparency functions in this document, and are described below:

Tunneling of QSIG messages inside H.225 per H.323v4 Annex M1—The Cisco BTS 10200 Softswitch can receive QSIG messages tunneled inside the H.225 call signaling messages on incoming H.323-based calls, and forward the QSIG messages on the outgoing H.323 call leg. The Cisco BTS 10200 Softswitch does not open or process this tunneled data, it simply forwards it to the next H.323 endpoint. No service provider provisioning steps are required for this function.


Note QSIG messages include, for example, Setup, Alerting, Connect, and Release Complete. Some QSIG messages, such as Call Proceeding, Facility, Information, Notify, and so forth, are mapped to the H.225 Facility message, as described in Annex M1.


Call-connect mode transparency—This feature refers to the two procedures for H.323 call connection, fast-start and slow-start. Each TG profile (or terminal profile) can be provisioned to operate in slow-start mode, fast-start mode, or auto mode. Each call leg will use the connection mode provisioned for the applicable TG profile or terminal profile. In addition, the system takes the following action based on this provisioning:

If the incoming call leg is provisioned for fast-start, and the outgoing leg is provisioned for slow-start, the call can go through.

If the incoming leg is provisioned for slow-start, and the outgoing leg is provisioned for fast-start, the call will not go through.

In auto mode, the system automatically uses the same call-connection mode on both legs of an H.323 transit call.

There are additional limitations on the system actions for fast-start and slow-start legs. Contact Cisco TAC if you need additional information on these limitations.

Call-proceeding message transparency—The system has the capability of sending a call-proceeding message from the terminating endpoint to the originating endpoint immediately upon receiving enough called-party digits to route the call. The system provides provisionable options that control the sending of the call-proceeding messages for H.323-based calls.

Preferential codec order transparency—On an incoming call leg using fast-start connection method, the fast-start elements are contained in the SETUP message. For a leg using slow-start, the codec preferences come in the terminal capability set (TCS). The system transparently forwards this information to the remote endpoint on the outbound leg. This supports codec negotiation by the two endpoints. No service provider provisioning steps are required for this function.

Transparency of H.245 tunneling mode—The system receives H.245 messages that are tunneled inside H.225 messages on the incoming leg, and forwards the H.245 messages tunneled inside H.225 messages on the outgoing leg. This supports call processing functions between the originating and terminating endpoints, including scenarios in which one endpoint is H.323-based and the other is MGCP-based. The system provides provisionable options for H.245 tunneling. For H.323 transit calls, a provisionable option allows the system to consider what the peer leg is using as its tunneling mode.

H.245 message transparency—For H.323-to-H.323 calls, the system is capable of passing H.245 messages, including, for example, EndSession and OpenLogicalChannelAck messages, from the incoming call leg to the outgoing call leg. It can also pass any nonStandard information elements received in the H.245 messages. No service provider provisioning steps are required for this function.

Transparency of Flash button (hook switch) functionality—When a call is in process, and a user presses the Flash button or the hook switch on the handset, a hook-flash signal is sent to the Cisco BTS 10200 Softswitch in an H.245 message. The Cisco BTS 10200 Softswitch reacts by sending a hook-flash signal over H.245 to the other endpoint in the call.Cisco BTS 10200 Softswitch.
No service provider provisioning steps are required for this function.

DTMF relay method transparency—For H.323 transit calls, the Cisco BTS 10200 Softswitch transparently forwards the types of DTMF parameters listed below. (For this transparent passing functionality, no service provider provisioning steps are necessary.)

In-band

RTP payload (per IETF RFC 2833, RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals)

Out-of-band (alphanumeric and signal)

Additional H.323-Related Feature Enhancements

This release of the Cisco BTS 10200 Softswitch adds the following provisionable H.323 enhancements:

DTMF relay support on MGCP-to-H.323 calls—For MGCP to H.323 (fast-connect) calls, RFC-2833 capabilities are advertised for the H.323 call leg based on static information configured for H.323 TG. This is because the far-end H.323 endpoint capabilities (such as DTMF, Fax, and so forth) are not available at the time MGCP leg has to complete the two-ended connection. Therefore, all far-end H.323 capabilities must be configured in either the outgoing (for outgoing H.323 calls) or incoming (for inbound H.323 calls) H323-TG-PROFILE (or H323-TERM-PROFILE) table.

Asymmetric codec resolution—Asymmetric codec refers to the use of different codecs for forward and reverse logical channels created for a slow-start call. In most network scenarios, asymmetric codec is avoided by means of codec negotiation, and, if necessary, some additional resolution techniques when the call is set up. The Cisco BTS 10200 Softswitch resolves asymmetric codec based on a master/slave determination and a codec back-off algorithm.

Facility message—The FACILITY message is primarily used for passing tunneling and other special information. The service provider provisions a flag in the Cisco BTS 10200 Softswitch to indicate whether far-end device supports receiving of the FACILITY message. If the far-end device flag indicates that it does not support the FACILITY message, the Cisco BTS 10200 Softswitch can open a separate H.245 TCP connection and uses the PROGRESS message to send fast-start information elements backward in the direction of the call.

Media cut-through—The cut-through parameter can be used to trigger the originating far-end device to perform media cut-through. This is provisionable in the Cisco BTS 10200 Softswitch. In most cases the system handles media cut-through automatically (default behavior).

Empty capability set (ECS) message handling—When an endpoint in a call receives he ECS, it reacts by closing its forward logical channel. The sending endpoint may also close its forward logical channel. When the Cisco BTS 10200 Softswitch is the sending endpoint it closes the channel (or not) based on the values provisioned for ECS method. If provisioned for automatic ECS mode (default), the system acts as follows:

For call legs connecting to Cisco CallManager, the Cisco BTS 10200 Softswitch closes its own forward logical channel.

For all other types of H.323 devices, the Cisco BTS 10200 Softswitch does not close its own forward logical channel.

Configurable status enquiry timer—If a Call Agent failover occurs, the Cisco BTS 10200 Softswitch sends a STATUS ENQ message to all calls using Annex E UDP transport that were previously stable or transient, and starts the STATUS ENQ timer per call. This timer is stopped gracefully when a STATUS message is received from the far end. After timeout, the Cisco BTS 10200 Softswitch releases the corresponding call.

Route advance, reattempt, and redirection on H.323-based call legs—The system supports this feature set for calls using fast-start procedures on the H.323 call leg(s). It sends the fast-start element only in the ALERTING/PROGRESS message. You must provision a special token (MISC-UNSUPP token in the H323-TG-PROFILE [or H323-TG-PROFILE] table) to enable the system to support this feature set.

How to Provision H.323 Features for Release 4.2

This section describes the tables and tokens that must be provisioned to take advantage of the H.323 video, routing, and transparency features covered in this document. The provisioning tasks are as follows:

Provision H.323-Based TGs, Logical GWs and GKs

Provision H.323-Based Video Phone Terminals and Subscribers

Provision H.323-Based Outbound Routing Data

Provision H.323-Based Inbound Routing

Additional Information for Provisioning ANI Screening and Routing

Advanced Provisioning Options


Note The command sequences shown in this section provide guidance on how to provision a new system. Therefore, in most cases the commands are "add" commands. If you are modifying previously-provisioned GWs, TGs, and so forth, use the "change" commands.



Note This section covers only the H.323 enhancements for Cisco BTS 10200 Softswitch Release 4.2. For the complete sequence of H.323 provisioning commands, refer to the Cisco BTS 10200 Softswitch Provisioning Guide. For a complete reference of all tokens and commands, see the Cisco BTS 10200 Softswitch Command Line Interface Reference Guide.


Provision H.323-Based TGs, Logical GWs and GKs

The commands in this section provision the following entities on the Cisco BTS 10200 Softswitch:

H.323-based TGs

H.323-based logical GWs internal to the Cisco BTS 10200 Softswitch (the Cisco BTS 10200 Softswitch provides a maximum of four H.323-based GWs).

Connections to an H.323 GK, if GKs are present in the network.

H.323-Based Logical GWs Internal to the Cisco BTS 10200 Softswitch

Each of the H.323-based internal GWs supports trunks, lines, routing options, and communications with external H.323 endpoints. Each GW can communicate with a GK, if present in the network. The parameters described in this section support these functions.

Prerequisites

The Cisco BTS 10200 Softswitch database should already be populated with basic provisioning options as described in the Cisco BTS 10200 Softswitch Provisioning Guide.

SUMMARY STEPS

1. Set the connection parameters on the TG profile for this H.323 GW—ADD H323-TG-PROFILE

2. Match incoming H.323 calls on a specific IP:port to a specific TG and enable/disable ANI-based routing—ADD TRUNK-GRP

3. Identify the codec type in the QoS table—ADD QOS (required only if CODEC-NEG-SUPP=N in the H323-TG-PROFILE table, as used with slow-start)

4. Provision properties of the H.323 GWs—ADD H323-GW

5. Provision connections to the H.323 GKs—ADD H323-GW2GK

6. Change the TG to include the applicable H.323 GW ID—CHANGE TRUNK-GRP


Note Cisco recommends that you assign a specific type of inbound routing to each of the four H.323 GWs according to your network requirements. For example, assign tsap-addr routing on one GW, gw-id routing on one GW, "none" on one GW, and choose the routing type for the fourth GW according to your network design. Selecting "none" results in the most efficient processing, but it reduces flexibility.


DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD H323-TG-PROFILE

Example:
CLI> ADD H323-TG-PROFILE ID=TRUNK-PROFILE-1; 
H245-SESSION-MODE=AUTO;  
VIDEO-SUPP=Y; 
CODEC-NEG-SUPP=N;

Sets the connection parameters to support certain types of calls.

Note To enable H.323 video capability, set the parameters as follows:

H245-SESSION-MODE must be set to either AUTO or H245-FLOWAROUND

VIDEO-SUPP must be set to Y

If the far-end video device does not support dynamic codec negotiation, CODEC-NEG-SUPP must be set to N


Caution The default value for CODEC-NEG-SUPP is Y. Make sure that you change this value to N for video capability.

Note For TG profiles applicable to TGs that connect to Cisco CallManager, set the parameters as follows:

H245-SESSION-MODE must be set to AUTO

VIDEO-SUPP must be set to N

CODEC-NEG-SUPP must be set to N


Caution The default value for CODEC-NEG-SUPP is Y. Make sure that you change this value to N for TGs that connect to Cisco CallManager.

Step 2 

ADD TRUNK-GRP
Example:

This trunk group can be used as a match for incoming H.323 calls matched on the IP:port:

ADD TRUNK-GRP ID=318; CALL-AGENT-ID=CA146; 
TG-TYPE=H323; TG-PROFILE-ID=TRUNK-PROFILE-1; 
DIAL-PLAN-ID=cdp1; ANI-BASED-ROUTING=N; 
SOFTSW-TSAP-ADDR=10.89.227.114:1720; QOS-ID=Codec_1;
Example:

This trunk group would be used to match incoming H.323 call from CARRIER-A that is associated with H.323 GW 10.89.227.115, and apply ANI based routing. It can also be used for an outbound H.323 call with sourceCircuitInfo=CARRIER_A:

ADD TRUNK-GRP ID=418;CALL-AGENT-ID=CA146; 
TG-TYPE=H323; TG-PROFILE-ID=TRUNK-PROFILE-1; 
DIAL-PLAN-ID=cdp1; ANI-BASED-ROUTING=Y; 
SOFTSW-TSAP-ADDR=10.89.227.115:1720; 
TRUNK-SUB-GROUP=CARRIER_A; QOS-ID=Codec_1;

Matches incoming H.323 calls on a specific IP:port to a specific TG and enables/disables ANI-based routing.

QOS-ID specifies which QOS table to use for selection of codec type on outgoing calls to non-H.323 endpoints, for example an H.323 videophone attempting to establish an audio call with a non-H.323 endpoint. Codec negotiation is not supported for video calls, therefore the codec of the remote H.323 endpoint must be able to use the specified codec.

Additional TG provisioning examples:

Outbound TG with DNS support (no RAS)

Outbound/inbound TG (static IP)

Specified trunk subgroup

Specified service provider ID

TG with ANI-based screening

Step 3 

Note This step is required only if CODEC-NEG-SUPP=N in the H323-TG-PROFILE table.

ADD QOS
Example:
ADD QOS ID=Codec_1;  
CODEC-TYPE=PCMA; 

CODEC-TYPE identifies the codec to use; typically, video calls use PCMU (the default value) or PCMA

Step 4 

ADD H323-GW
Example:
ADD H323-GW ID=H323_GW1;  
GW-H225-PORT=1720;  
TGN-ID=318; 
SOURCE-BASED-ROUTING=SRC-TSAP-ADDR;

Provisions properties of the logical H.323 GW instance on the Cisco BTS 10200 Softswitch. The system can support up to four H323-GW IDs.

Note The Cisco BTS 10200 Softswitch can be configured as up to four logical H.323 GWs.

Note The system uses the SOURCE-BASED-ROUTING parameter to choose the incoming TRUNK-GRP.

Step 5 

ADD H323-GW2GK
Example:
ADD H323_GW2GK H323-GW-ID=H323_GW1; GK-ID=cisco-gk; 
GK-IP-ADDR=10.0.10.128; GK-RAS-PORT=1719; MULTICAST=N;

Provisions connections to the H.323 GK.

Step 6 

CHANGE TRUNK-GRP
Example:
CHANGE TRUNK-GRP; ID=318; CALL-AGENT-ID=CA146; 
DIAL-PLAN-ID=dp001; H323-GW-ID=H323_GW1;

Link the TG to the logical H.323 GW.

Provision H.323-Based Video Phone Terminals and Subscribers

The Cisco BTS 10200 Softswitch can be configured as up to four internal H.323-based logical GWs. Each of these GWs can support direct communications with external H.323 endpoints. Each GW can communicate with a GK, if present in the network. The commands in this section provision the subscriber lines for H.323-based video phone terminals and subscribers.

Prerequisites

The Cisco BTS 10200 Softswitch database should already be populated with basic provisioning options as described in the Cisco BTS 10200 Softswitch Provisioning Guide.

SUMMARY STEPS

1. ADD H323-TERM-PROFILE

2. ADD H323-TERM

3. ADD SUBSCRIBER-PROFILE

4. ADD SUBSCRIBER

5. ADD QOS (required only if CODEC-NEG-SUPP=N in the H323-TERM-PROFILE table, as used with slow-start)

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD H323-TERM-PROFILE

Example:
CLI> ADD H323-TERM-PROFILE ID=TERM-PROFILE-1; 
H245-SESSION-MODE=AUTO;  
VIDEO-SUPP=Y; 
CODEC-NEG-SUPP=N;
MAX-CALLS=<1, 2, ... 6>;

Creates a profile for a H.323 video-phone termination.

Note To enable H.323 video capability, set the parameters as follows:

H245-SESSION-MODE must be set to either AUTO or H245-FLOWAROUND

VIDEO-SUPP must be set to Y

If the far-end video device does not support dynamic codec negotiation, CODEC-NEG-SUPP must be set to N


Caution The default value for CODEC-NEG-SUPP is Y. Make sure that you change this value to N for video capability.

Note MAX-CALLS is the maximum number of calls allowed on the H.323 terminal. When the current number of calls exceed this number, any call termination to this terminal will result in `busy' condition (and may trigger CFB or CW feature if configured for the subscriber). The range is 1 to 6 and the default is 2.

Step 2 

ADD H323-TERM
Example:
ADD H323-TERM-ID=TERM1-h323; 
TSAP-ADDR=10.89.227.114:1720; 
H323-TERM-PROFILE-ID=TERM_PROFILE_1; 
H323-GW-ID=H323_GW1;

Links the H.323 termination to an H.323 termination profile and H.323 GW, and specifies the TSAP address (IP address and port).

Note If H323-GW-ID is set to NULL, the Cisco BTS 10200 Softswitch selects which GW to use based on a load-distribution algorithm.

Step 3 

ADD SUBSCRIBER-PROFILE
Example:

ADD SUBSCRIBER-PROFILE ID=SP1;
DIAL-PLAN-ID=CDP1;
POP-ID=27;


Creates a profile for a subscriber and links the profile to a specific dial plan and POP.

Step 4 

ADD SUBSCRIBER
Example:
ADD SUBSCRIBER ID=JSMITH; 
BILLING-DN=212-555-1212;  
DN1=212-555-1212; 
SUB-PROFILE-ID=SP1; 
TERM-TYPE=H323; 
H323-TERM-ID=TERM1-h323;
QOS-ID=Codec_1;

Adds a subscriber and links the subscriber to a specific subscriber profile, H.323 termination, and billing DN.

QOS-ID specifies which QOS table to use for selection of codec type on outgoing calls. Codec negotiation is not supported for video calls, therefore the codec of the remote H.323 endpoint must be able to use this codec. Otherwise, the video call cannot be completed.

Step 5 

Note This step is required only if CODEC-NEG-SUPP=N in the H323-TERM-PROFILE table.

ADD QOS
Example:
ADD QOS ID=Codec_1;  
CODEC-TYPE=PCMA;

CODEC-TYPE identifies the codec to use; typically, video calls use PCMU (the default value) or PCMA.

Provision H.323-Based Outbound Routing Data

This section explains how to provision H.323-based routing data for outbound calls on the Cisco BTS 10200 Softswitch. The Cisco BTS 10200 Softswitch supports sending of either the H.323/H.225 sourceCircuitID or destinationCircuitID parameters (or both) for the outbound call leg.

This section covers the following topics:

Understanding the Outbound Routing Process

Outbound Routing Option Summary

Outbound H.323 Calls

H.323 Tandem Calls With Circuit Info Sent

SS7-originated Calls Retransmitted As Outbound H.323 Calls With Circuit Info

Understanding the Outbound Routing Process

Outbound routing is managed via a four-step process that starts when an H.323-based call is originated or received on the Cisco BTS 10200 Softswitch:

1. The system examines the originating/incoming H.225 call data (H.323 ARQ/SETUP message).

2. The system examines the provisioned values of certain parameters in the internal database and prepares routing data that can be sent for the outbound call leg.

3. The system examines the provisioned values of certain parameters in the internal database to determine whether to transmit a sourceCircuitID, a destinationCircuitID, neither, or both, in the H.225 call data (ARQ/SETUP message) for the outbound leg.

4. If provisioned to send, the system transmits the applicable source and/or destination carrier IDs in the outbound ARQ/SETUP message.


Tip The settings in item 3. (above) take precedence over the first two steps: If the parameters in 3. are set to N (no), the system does not transmit this circuit information, regardless of the data or settings described in items 1. and 2.


Table 1 describes several routing terms used in this section, including the relationship of network terminology, H.225-message terminology, and the tokens used to control this data in the Cisco BTS 10200 Softswitch.

Table 1 H.323 Routing Terminology and Applicable Tokens

Network Terminology
H.225 Message Terminology
Applicable Cisco BTS 10200 Softswitch Database Tokens

Source carrier ID

sourceCircuitID

The Cisco BTS 10200 Softswitch database maps this value to the TRUNK-SUB-GROUP token in the TRUNK-GRP table. TRUNK-SUB-GROUP identifies a specific TG when multiple TGs exist between the Cisco BTS 10200 Softswitch and another softswitch.

Note The SEND-SRC-CIRCUIT-ID token in the H323-TG-PROFILE table specifies whether to send the sourceCircuitID in an outgoing H.323 ARQ/SETUP message. If this token is set to N (no), the sourceCircuitID will not be sent, even if its value is available in the TRUNK-GRP table.

Destination carrier ID

destinationCircuitID

The Cisco BTS 10200 Softswitch database maps this value to the SP-ID token in the TRUNK-GRP table. SP-ID specifies a unique ID for a particular service provider, and is used when there are multiple service providers providing service via a single logical Call Agent (CA).

Note The SEND-DEST-CIRCUIT-ID token in the H323-TG-PROFILE table specifies whether to send the destinationCircuitID in an outgoing H.323 ARQ/SETUP message. If this token is set to N (no), the destinationCircuitID will not be sent, even if its value is available in the TRUNK-GRP table.


Outbound Routing Option Summary

Table 2 provides a summary of the outbound routing data options. It shows how the provisioned values affect the outbound routing data sent by the system.


Note If no value is shown (-) the provisioning of the specified table has no effect in this scenario.


Table 2 Summary of H.323 Outbound Routing Data Options 

Outbound H.323-Based Call Type
Outbound Routing
Data Sent
Values to provision in terminating
or outbound
TRUNK-GRP table
Values to provision in H323-TG-PROFILE table
Values to provision in SERVICE-PROVIDER table

Outbound H.323 Calls

(Figure 3)

No circuit info sent in ARQ/SETUP messages

-

Set both
SEND-SRC-CIRCUIT-ID
and SEND-DEST-CIRCUIT-ID
to N.

-

sourceCircuitID based on TRUNK-SUB-GROUP in the terminating TRUNK-GRP table

Provision a value for TRUNK-SUB-GROUP in the terminating TG table.

Set SEND-SRC-CIRCUIT-ID to Y (yes) in the H323-TG-PROFILE table.

-

H.323 Tandem Calls With Circuit Info Sent

(Figure 4)

destinationCircuitID based on incoming SETUP message

Do not provision a value for SP-ID in the outbound TRUNK-GRP table.

Set SEND-DEST-CIRCUIT-ID to Y (yes).

Set SP-BASED-ROUTING to N (no).

destinationCircuitID based on SP-ID in outbound TRUNK-GRP table

Provision a value for SP-ID in the outbound TRUNK-GRP table.

Set SEND-DEST-CIRCUIT-ID to Y (yes).

Set SP-BASED-ROUTING to N (no).

sourceCircuitID and destination CircuitID based on incoming SETUP message

-

Set SEND-SRC-CIRCUIT-ID to Y (yes).

Set SP-BASED-ROUTING to Y (yes).

SS7-originated Calls Retransmitted As Outbound H.323 Calls With Circuit Info

(Figure 5)

sourceCircuitID based on TNS/CIP data received on the incoming SS7 circuit

-

Set SEND-SRC-CIRCUIT-ID to Y (yes).

-

sourceCircuitID overwritten by value of TRUNK-SUB-GROUP in the terminating TRUNK-GRP table

Provision a value for TRUNK-SUB-GROUP in the terminating TG table.

Set SEND-SRC-CIRCUIT-ID to Y (yes).

-


Outbound H.323 Calls

The following routing data options can be provisioned for outbound H.323 calls.

No circuit info sent in ARQ/SETUP messages

Take the following action to ensure that no circuit info is sent in the outbound ARQ/SETUP messages—Set both SEND-SRC-CIRCUIT-ID and SEND-DEST-CIRCUIT-ID to N (no) in the H323-TG-PROFILE table. See Figure 3, "Part A".


Note When you set these parameters to N (no), the system does not transmit this circuit information, regardless of the data received on the originating/incoming call and the settings in other tables.


sourceCircuitID based on TRUNK-SUB-GROUP in the terminating TRUNK-GRP table

Take the following action to send sourceCircuitID in the ARQ/SETUP message based on the provisioned TRUNK-SUB-GROUP in the terminating TG table:

Provision a value for TRUNK-SUB-GROUP in the terminating TG table.

Set SEND-SRC-CIRCUIT-ID to Y (yes) in the H323-TG-PROFILE table.

See Figure 3, Part "B".

Figure 3 Circuit-Info Options For Outbound H.323 Calls

H.323 Tandem Calls With Circuit Info Sent

The following routing data options can be provisioned for outbound H.323 Tandem calls.

destinationCircuitID based on incoming SETUP message

Take the following action to send destinationCircuitID in the ARQ/SETUP message based on the destinationCircuitID contained in the incoming SETUP message:

Set SP-BASED-ROUTING to N (no) in the SERVICE-PROVIDER table

Do not provision a value for SP-ID in the outbound TRUNK-GRP table

Set SEND-DEST-CIRCUIT-ID to Y (yes) in the H323-TG-PROFILE table.

See Figure 4, Part "A".

destinationCircuitID based on SP-ID in outbound TRUNK-GRP table

Take the following action to send destinationCircuitID in the ARQ/SETUP message based on the value provisioned for the SP-ID in the outbound TRUNK-GRP table:

Set SP-BASED-ROUTING to N (no) in the SERVICE-PROVIDER table

Provision a value for SP-ID in the outbound TRUNK-GRP table

Set SEND-DEST-CIRCUIT-ID to Y (yes) in the H323-TG-PROFILE table.

See Figure 4, Part "B".

sourceCircuitID and destination CircuitID based on incoming SETUP message

Take the following action to send sourceCircuitID in the ARQ/SETUP message based on the destinationCircuitID contained in the incoming SETUP message:

Set SP-BASED-ROUTING to Y (yes) in the SERVICE-PROVIDER table

set SEND-SRC-CIRCUIT-ID to Y (yes) in the H323-TG-PROFILE table.

See Figure 4, Part "C".

Figure 4 H.323 Tandem Calls With Circuit Info Sent

SS7-originated Calls Retransmitted As Outbound H.323 Calls With Circuit Info

The following routing data options can be provisioned for SS7-originated calls that are retransmitted as outbound H.323 calls.

sourceCircuitID based on TNS/CIP data received on the incoming SS7 circuit

Take the following action to send sourceCircuitID in the ARQ/SETUP message based on the TNS/CIP data received on the incoming SS7 circuit—Set SEND-SRC-CIRCUIT-ID to Y (yes) in the H323-TG-PROFILE table.

See Figure 5, Part "A".

sourceCircuitID overwritten by value of TRUNK-SUB-GROUP in the terminating TRUNK-GRP table

Take the following action to send sourceCircuitID in the ARQ/SETUP message based on the provisioned TRUNK-SUB-GROUP in the terminating TG table (the received TNS/CIP data is overwritten by the value provisioned for TRUNK-SUB-GROUP):

Provision a value for TRUNK-SUB-GROUP in the terminating TG table.

Set SEND-SRC-CIRCUIT-ID to Y (yes) in the H323-TG-PROFILE table.

See Figure 5, Part "B".

Figure 5 SS7-originated Calls Retransmitted as Outbound H.323 Calls With Circuit Info

SUMMARY STEPS

1. ADD h323-tg-profile

2. ADD trunk-grp

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

ADD H323-TG-PROFILE
ID=<TG-PROFILE ID>;
SEND-DEST-CIRCUIT-ID=<Y|N>

SEND-SRC-CIRCUIT-ID=<Y|N>

Example:
CLI> ADD H323-TG-PROFILE  
ID=TRUNK_PROFILE_1;  
SEND-DEST-CIRCUIT-ID=Y;  
SEND-SRC-CIRCUIT-ID=N;

The SEND-DEST-CIRCUIT and SEND-SRC-CIRCUIT flags control the use of circuit info parameters in the outgoing ARQ/SETUP messages. When set to Y (yes) the system sends the circuit information.

Tip To understand the impact of SEND-DEST-CIRCUIT-ID and SEND-SRC-CIRCUIT-ID tokens on outbound routing, see Table 2.

Step 2 

ADD TRUNK-GRP ID=<TG ID>; 
CALL-AGENT-ID=<CA ID>; 
TG-TYPE=H323;  
TG-PROFILE-ID=<TG PROFILE ID>;  
H323-GW-ID=<H.323 GW ID>; 
DIAL-PLAN-ID=<DIAL PLAN ID>;  
ANI-BASED-ROUTING=N;  
SOFTSW-TSAP-ADDR=<DOMAIN NAME OR IP:PORT>;  
QOS-ID=<QOS ID>;  
SP-ID=<SERVICE PROVIDER ID>;  
TRUNK-SUB-GRP=<TRUNK SUBGROUP ID>;

Example:
ADD TRUNK-GRP ID=318; CALL-AGENT-ID=CA146; 
TG-TYPE=H323; TG-PROFILE-ID=TG_PROFILE_1; 
H323-GW-ID=H323_GW1; DIAL-PLAN-ID=DP001; 
ANI-BASED-ROUTING=N; 
SOFTSW-TSAP-ADDR=10.89.227.114:1720; QOS-ID=Codec_1; 
SP-ID=SP_7777; TRUNK-SUB-GRP=SUBGRP_300;

Matches incoming H.323 calls on a specific IP:port to a specific TG. It also disables ANI-based routing.

SP-ID identifies a specific service provider when multiple service providers are provisioned on a single logical CA.

TRUNK-SUB-GRP identifies a specific trunk group when multiple trunk groups exist between a Cisco BTS 10200 Softswitch and another softswitch.

Tip To understand the impact of the SP-ID and TRUNK-SUB-GRP tokens on outbound routing, see Table 2.

Provision H.323-Based Inbound Routing

This section explains how to provision H.323-based inbound routing options on the Cisco BTS 10200 Softswitch. All incoming calls from the H.323 network are terminated by one of the four H.323 GW instances on the Cisco BTS 10200 Softswitch. Incoming calls can be routed to the Cisco BTS 10200 Softswitch with or without the use of a gatekeeper (GK):

When no RAS signaling to the GK is used, calls are routed directly from the far-end H.323 device

When there is RAS signaling to a GK, calls are routed by the GK toward the Cisco BTS 10200 Softswitch.

Figure 6 provides an overview of the H.323 inbound routing process.

Figure 6 Overview of H.323 Inbound Routing Process

The tables that follow provide details on how to provision inbound call routing, including the processes: listed below. Use these diagrams to determine how you need to provision the various parameters that affect inbound routing.

Figure 7—TG match with source-based routing disabled (SRC-BASED-ROUTING set to NONE in the H323-GW table)

Figure 8—TG match with source-based routing enabled (SRC-BASED-ROUTING set to a value other than NONE in the H323-GW table)

Figure 9—H.323 TERM check

Figure 10—ANI screening and ANI routing

Figure 7 TG Match with Source-Based Routing Disabled

Figure 8 TG Match with Source-Based Routing Enabled

Figure 9 H.323 TERM Check

Figure 10 ANI Screening and ANI Routing

Additional Information for Provisioning ANI Screening and Routing

This section provides additional information on provisioning H.323-based ANI screening and routing options on the Cisco BTS 10200 Softswitch.

ANI Screening vs. ANI-Based Routing

The Cisco BTS 10200 Softswitch provides the option to provision ANI-based screening and ANI-based routing on each TG. For ANI screening, the system compares the ANI received in the incoming SETUP message against the provisioned DN ranges. For ANI routing, the system uses the provisioned dial plan for the subscriber (or main subscriber for a PBX). If the subscriber or PBX is associated with a video-enabled endpoint, the billing record is labeled as video.

The system first checks the TRUNK-GRP table for the TG on which the call was received:

If the ANI-SCREENING and ANI-BASED-ROUTING tokens in the applicable TRUNK-GRP table are both set to N (no), the system uses the dial plan from the TRUNK-GRP table or the SERVICE-PROVIDER table to determine the destination for the called number. The choice between TRUNK-GRP and SERVICE-PROVIDER tables is based on the additional provisioning options that are described in Figure 10.

If ANI-SCREENING is set to N and ANI-BASED-ROUTING is set to Y (yes), the system performs legacy ANI-based routing based on provisioning in the DN2SUB table.

If ANI-SCREENING is set to Y and ANI-BASED-ROUTING is set to N, the system performs ANI screening. Based on the provisionable options that influence this screening, the system can use the dial plan from the SUBSCRIBER table, TRUNK-GRP table, or SERVICE-PROVIDER table to route the call (see Figure 10).

If ANI-SCREENING and ANI-BASED-ROUTING are both set to Y, ANI screening takes precedence.

Identification of H.323 Terminal Property Based On ANI

The Cisco BTS 10200 Softswitch uses the provisioned ANI data to assist in identifying the terminal property of a phone or PBX, specifically, whether the phone or PBX is video-capable. The system can identify the terminal property of an H.323-based video phone or PBX to which it is directly connected. If an H.323-based video phone is connected directly to the Cisco BTS 10200 Softswitch, the Cisco BTS 10200 Softswitch recognizes that it is a video call. However, if the call from a video phone goes first to an intermediate H.323 GW or endpoint which is connected to the Cisco BTS 10200 Softswitch, the Cisco BTS 10200 Softswitch must identify the terminal property (for example, video phone) based on information in the H323-TG-PROFILE for the applicable TG for that GW or endpoint. For example, the properties for a PBX-based TG are different than those for a tie TG. It is important to keep this in mind when provisioning H.323 endpoints and TGs.

ANI Screening

If the ANI-SCREENING token in the applicable inbound TRUNK-GRP table is set to Y (yes), the system compares the ANI received in the incoming SETUP message against the DN ranges provisioned in the ANI-SCREENING table:

If a match is found, the system accepts and routes the call with the appropriate screening-field value in the outgoing message. If the DN is associated with a video-enabled end-point, the billing record (CDB) is labeled as video.

If a match is not found, the system checks the ACTION token value in the ANI-SCREENING-PROFILE table, and takes further action.


Note A billing record (CDR) is generated for the call, even if the call is rejected based on ANI screening.


ANI-Based Routing

If ANI screening is performed successfully on a MAIN-SUB-ID that is associated with a particular TG (for example, if the TG is connected to a PBX), the system performs ANI-based routing using the dial plan for the MAIN-SUB-ID. If the MAIN-SUB-ID is associated with a video-enabled end-point, the billing record (CDB) is labeled as video.

Advanced Provisioning Options

This section describes a number of advanced H.323 provisioning options that affect protocol transparency and special H.323 messaging features supported by the Cisco BTS 10200 Softswitch. In the most common network configurations it is generally not necessary to provision these parameters—The default values are sufficient. However, these advanced options can be provisioned to nondefault values if desired. The information is contained in the following two subsections:

H.323 Protocol Transparency Functions

Additional Advanced H.323 Features

H.323 Protocol Transparency Functions

The Cisco BTS 10200 Softswitch supports the interconnection of multiple H.323-based devices by transparently passing certain H.323 messages in calls that transit the Cisco BTS 10200 Softswitch. There are three transparency functions that include optional service provider provisioning:

Call-Connect Mode Transparency

Call-Proceeding Message Transparency

Transparency of H.245 Tunneling Mode

Call-Connect Mode Transparency

The CALL-CONNECT-MODE token in the H323-TG-PROFILE and H323-TERM-PROFILE tables specifies the call setup method used for outbound and inbound H.323-based calls.


Note If this token is configured as FAST-START and the far-end H.323 endpoint does not support FAST-START, the Cisco BTS 10200 Softswitch will fall back to the SLOW-START method.



Note If the incoming call is using slow-start procedures, and this token is configured as FAST-START, this call leg will be slow-start only.


Permitted values for this token are as follows.


Note For most applications, the default value (AUTO) is sufficient.


AUTO (default)—Use fast-connect method for calls originated from non-H.323 endpoint and outbound H.323 calls. For H.323 transit calls, use the same method for outbound H.323 calls as that of inbound H.323 call.

FAST-START—Always use the fast-start procedures for outbound H.323 calls (except where an incoming call uses slow-start procedures), regardless of originating (inbound) call protocol type.

SLOW-START—Always use the slow-start procedures during call setup, regardless of originating (inbound) call protocol type.

Call-Proceeding Message Transparency

The SEND-CALL-PROCEEDING token in the H323-TG-PROFILE and H323-TERM-PROFILE tables specifies the conditions for sending a Call Proceeding message from the terminating endpoint to the originating endpoint.

The permitted values for this token are as follows.


Note For most applications, the default value (AUTO) is sufficient.


AUTO (default)—Generate and send a Call Proceeding message on the originating H.323 leg when the terminating leg is non-H.323. Pass the Call Proceeding message end-to-end for H.323 to H.323 calls.

LOCAL—Always generate and send a Call Proceeding massage on the originating H.323 leg, regardless of protocol type used on the terminating leg.

DISABLE—Never send a Call Proceeding message.

Transparency of H.245 Tunneling Mode

The H245-TUNNELING token in the H323-TG-PROFILE and H323-TERM-PROFILE tables specifies whether to enable or disable H245 tunneling mode on each of the call legs. When H.245 tunneling is enabled, all H.245 messages are tunneled inside a FACILITY message instead of through a separate H.245 TCP channel.

The permitted values for this token are as follows.


Note For most applications, the default value (AUTO) is sufficient.


AUTO (default)—The system automatically determines whether to enable or disable H.245 tunneling:

Use H.245 tunneling on the H.323-based call leg for calls between H.323 and non-H.323 endpoints.

For H.323 transit calls, the system automatically considers what the peer leg is using as its tunneling mode to help determine whether to enable or disable H.245 tunneling:


Note If H245-TUNNELING in the H323-TG-PROFILE (or H323-TERM-PROFILE) tables for either one of the endpoints in the call is not set to AUTO, the system enables or disables H.245 tunneling for each leg of the call individually.


ENABLE—Always use H.245 tunneling for outgoing calls, without considering the type of incoming call-leg protocol.

DISABLE—Always disable H.245 tunneling for outgoing call legs and use a separate H.245 TCP channel.

Additional Advanced H.323 Features

Additional H.323 advanced features include:

DTMF Relay Support on MGCP-to-H.323 Calls

Asymmetric Codec Resolution

Facility Message

Media Cut-Through

Empty Capability Set

Configurable Status Enquiry Timer

Route Advance, Reattempt, and Redirection

DTMF Relay Support on MGCP-to-H.323 Calls

For MGCP to H.323 (fast-connect) calls, RFC-2833 capabilities are advertised for the H.323 call leg based on static information configured for H.323 TG or terminal. Ensure that all far-end H.323 capabilities are configured in either the outgoing (for outgoing H.323 calls) or incoming (for inbound H.323 calls) H323-TG-PROFILE (or H323-TERM-PROFILE) table.

Asymmetric Codec Resolution

To enable the asymmetric codec resolution feature, the CODEC-NEG-SUPP field in H323-TG-PROFILE (for H323 trunk-grp) or H323-TERM-PROFILE (for H323 subscriber) should be configured as Y (yes), which is the default value. The configurable fields CODEC-NEG-TIMER and CODEC-NEG-ATTEMPTS in H323-GW table control the codec resolution procedure. If CODEC-NEG-SUPP field is configured as Y, it is not necessary for a codec to be configured in QOS table of incoming/outgoing trunk-grp.

If the CODEC-NEG-SUPP field (in H323-TG-PROFILE or H323-TERM-PROFILE) is configured as N (no), the Cisco BTS 10200 Softswitch will expect the far-end H.323 device (particularly those not using fast-connect procedure) to use the codec configured in QOS table entry of both incoming and outgoing trunk-grp table (or subscriber table). If the codecs of the two end devices do not match, the call will fail.


Note For all IOS gateways, set this token to Y. For connection to Cisco CallManager, set this token to N. Contact the Cisco TAC if you need additional details on this setting.


Facility Message

The FACILITY message is primarily used for passing tunneling and other special information. The service provider provisions the FACILITY-SUPP flag in the H323-TG-PROFILE (or H323-TERM-PROFILE) table to indicate whether far-end device supports receiving of the FACILITY message. The default value is Y.


Note For connection to Cisco CallManager, set FACILITY-SUPP to N.


Media Cut-Through

The CUT-THRU-PARAM can be used to trigger the far-end device to perform media cut-through. The service provider provisions the CUT-THRU-PARAM token in the incoming H323-TG-PROFILE (or H323-TERM-PROFILE) table to indicate whether to trigger cut-through on the far-end device. The default value is AUTO.


Note For connection to Cisco CallManager, and for most other applications, the default value (AUTO) is sufficient.


Empty Capability Set

Use the ECS-METHOD token in the H323-TG-PROFILE (or H323-TERM-PROFILE) table to set special handling of the ECS message.


Note For connection to Cisco CallManager, and for most other applications, the default value (AUTO) is sufficient.


AUTO (Default)—For connection to Cisco CallManager, the Cisco BTS 10200 Softswitch uses the ALL-PAUSE method. For all other types of H.323 devices, it uses the LOCAL-PAUSE method.

LOCAL-PAUSE—The far-end H.323 device receiving the ECS message closes the forward logical channel.

ALL-PAUSE—The far-end H.323 device receiving the ECS message closes the forward logical channel. The local side (Cisco BTS 10200 Softswitch) also closes its forward logical channel.

Configurable Status Enquiry Timer

If a Call Agent failover occurs, the Cisco BTS 10200 Softswitch sends a STATUS ENQ message and starts the STATUS ENQ timer per call. Provision the STATUS-ENQ-TIMER in the H323-GW table. The range of values is 1 to 30 (seconds) and the default is 4.

Route Advance, Reattempt, and Redirection

If you want the system to support this feature set, set the MISC-UNSUPP token in the H323-TG-PROFILE (or H323-TERM-PROFILE) table to 1. Otherwise, allow it to have the default value, 0.


Note This field is a bit mask. To enable this feature, you need to set only the first bit.


Configuration Example

This section provides examples of provisioning commands related to the H.323 video and signaling enhancements for this release. Some generic Cisco BTS 10200 Softswitch commands (such as add call-agent) are also included to illustrate the basic provisioning flow.

Example


Note Parameters that are new, or have important impact on the H.323 video and signaling enhancements in this release, are shown in bold type.



###################################################################
# Add Call Agent 
###################################################################
ADD CALL_AGENT ID=CA146; TSAP_ADDR_SIDEA=172.28.255.252; 
EMS_PRIMARY_TSAP=172.28.255.251; EMS_SECONDARY_TSAP=172.28.255.251; 
MGW_MONITORING_ENABLED=Y;

##################################################################
# Add Current Concerned NPA#
##################################################################

ADD NDC DIGIT_STRING=972;
ADD EXCHANGE_CODE NDC=972; EC=519;
ADD OFFICE_CODE CALL_AGENT_ID=CA146; NDC=972; EC=519; DN_GROUP=xxxx;

################################################################################
# Add POP
################################################################################
#
ADD POP ID=27;

################################################################################
# Add Service Providers
################################################################################
#

# This service provider can be used to match incoming h323 call that has used a
# destinationCircuitInfoID set to this service provider
ADD SERVICE_PROVIDER ID=SP1; SP_BASED_ROUTING=N; USE_DIAL_PLAN=Y; 
ANI_WB_LIST=NONE;


################################################################################
#
# Add H323 TRUNKS
################################################################################
#

ADD H323_TG_PROFILE ID=TRUNK_PROFILE_1; RAS=Y; H323_TCP_TIMER=10; 
DTMF_CISCO_RTP_SUPP=N; DTMF_H245_ALPHA_SUPP=Y; DTMF_H245_SIGNAL_SUPP=N; 
DTMF_RFC2833=N; DTMF_PREF_MODE=DTMF_H245_ALPHA; FAX_T38_GWMODE_SUPP=N; 
FAX_T38_CAMODE_SUPP=Y; FAX_INBAND_SUPP=N; FAX_PREF_MODE=FAX_T38_CAMODE; 
H245_SESSION_MODE=H245-FLOWAROUND; CALL_CONNECT_MODE=AUTO; H245_TUNNELING=AUTO; 
SEND_CALL_PROCEEDING=AUTO;

# This trunk can be used as a match for incoming h323 calls matched on IP:port 
ADD TRUNK_GRP ID=318; CALL_AGENT_ID=CA146; TG_TYPE=H323; 
TG_PROFILE_ID=TRUNK_PROFILE_1; DIAL_PLAN_ID=cdp1; ANI_BASED_ROUTING=N; 
SOFTSW_TSAP_ADDR=10.89.227.114:1720;

# This trunk group would be used to match incoming h323 call from CARRIER_A that 
is
# associated with H323 GW 10.89.227.115, also apply ANI based routing
# or for outbound h323 call with sourceCircuitInfo=CARRIER_A;
ADD TRUNK_GRP ID=418; CALL_AGENT_ID=CA146; TG_TYPE=H323; 
TG_PROFILE_ID=TRUNK_PROFILE_1; DIAL_PLAN_ID=cdp1; ANI_BASED_ROUTING=Y; 
SOFTSW_TSAP_ADDR=10.89.227.115:1720; TRUNK_SUB_GROUP=CARRIER_A;

##############################
# ANI SCREENING AND ROUTING
##############################

ADD SUBSCRIBER_PROFILE ID=sp0; DIAL_PLAN_ID=cdp1; POP_ID=27;
ADD TRUNK_GRP ID=469; CALL_AGENT_ID=CA146; TG_TYPE=H323; 
TG_PROFILE_ID=TRUNK_PROFILE_1; DIAL_PLAN_ID=cdp1; ANI_SCREENING=Y; 
ANI-SCREENING-ACTION=ALLOW;

ADD H323_TG_PROFILE ID=video_ani_tg; RAS=Y; H245_SESSION_MODE=H245-FLOWAROUND; 
CALL_CONNECT_MODE=AUTO; H245_TUNNELING=AUTO; SEND_CALL_PROCEEDING=AUTO;


ADD TRUNK-GRP ID=478; CALL-AGENT-ID=CA146; TG-TYPE=H323; 
TG-PROFILE-ID=VIDEO_ANI_BLOCK;

ADD SUBSCRIBER ID=ANI_972671_SUB; CATEGORY=PBX; GRP=Y; PRIVACY=USER; 
SEND-BDN-AS-CPN=N; SEND-BDN-EMG=N; SUB-PROFILE-ID=SP0; TERM-TYPE=TG; 
TGN-ID=NULL;

ADD ANI-SCREENING TGN-ID=469; ID=SCREEN-972671; FROM-DN=972-671-1000; 
TO-DN=972=671-2000; MAIN-SUB-ID= ANI_972671_SUB


################################################################################
#
# Add H323 SUBCRIBER DESTINATIONS
################################################################################
#
add destination dest_id=h323_video; call_type=LOCAL; route_type=SUB;

################################################################################
#
# Add H323 TRUNK DESTINATIONS
################################################################################
#
add destination dest_id=h323_318; call_type=LOCAL; route_type=RID; 
ROUTE_ID=h323_318;
add destination dest_id=h323_469; call_type=LOCAL; route_type=RID; 
ROUTE_ID=h323_469;

################################################################################
#
# Add H323 DIAL_PLANS
################################################################################
#
add dial-plan-profile id=cdp1;
add dial_plan id=cdp1; digit_string=972; dest_id=h323_video; min-digits=7; 
max-digits=10; NOA=NATIONAL;

################################################################################
#
# Add H323 TRUNK DIAL_PLANS
################################################################################
#
add dial_plan id=cdp1; digit_string=318; dest_id=h323_318; min-digits=7; 
max-digits=10; NOA=NATIONAL;
add dial_plan id=cdp1; digit_string=469; dest_id=h323_469; min-digits=7; 
max-digits=10; NOA=NATIONAL;

################################################################################
#
# Add H323 Gateways/Gatekeepers
################################################################################
#

ADD H323_GW ID=H323_GW1; GW_H225_PORT=1720; TGN_ID=318; SECURITY=N; 
PASSWORD=cisco; SECURITY_LEVEL=ENDPOINT; TCP_MAX_LIMIT=5; TCP_MAX_AGE=30; 
MAX_VOIP_CALLS=65535; HIGH_WATER_MARK=0; LOW_WATER_MARK=0; IRR_BANDWIDTH_SUPP=N; 
IPTOS_SIG_LOWDELAY=Y; IPTOS_SIG_THROUGHPUT=N; IPTOS_SIG_RELIABILITY=N; 
IPTOS_SIG_PRECEDENCE=FLASH; SOURCE-BASED-ROUTING=SRC-TSAP-ADDR

ADD H323_GW ID=H323_GW2; GW_H225_PORT=1820; TGN_ID=469; SECURITY=N; 
PASSWORD=cisco; SECURITY_LEVEL=ENDPOINT; TCP_MAX_LIMIT=5; TCP_MAX_AGE=30; 
MAX_VOIP_CALLS=65535; HIGH_WATER_MARK=0; LOW_WATER_MARK=0; IRR_BANDWIDTH_SUPP=N; 
IPTOS_SIG_LOWDELAY=Y; IPTOS_SIG_THROUGHPUT=N; IPTOS_SIG_RELIABILITY=N; 
IPTOS_SIG_PRECEDENCE=FLASH;

ADD H323_GW2GK H323_GW_ID=H323_GW1; GK_ID=cisco-gk; PRIORITY=1; 
GK_IP_ADDR=10.0.10.129; GK_RAS_PORT=1719; MULTICAST=N;
ADD H323_GW2GK H323_GW_ID=H323_GW2; GK_ID=cisco-gk; PRIORITY=1; 
GK_IP_ADDR=10.0.10.129; GK_RAS_PORT=1719; MULTICAST=N;

################################################################################
#
# Add H323 VIDEO Subscribers
################################################################################
#

ADD H323_TERM_PROFILE ID=TERM_PROFILE_1; RAS=Y; H323_TCP_TIMER=10; 
DTMF_CISCO_RTP_SUPP=N; DTMF_H245_ALPHA_SUPP=Y; DTMF_H245_SIGNAL_SUPP=N; 
DTMF_RFC2833=N; DTMF_PREF_MODE=DTMF_H245_ALPHA; FAX_T38_GWMODE_SUPP=N; 
FAX_T38_CAMODE_SUPP=Y; FAX_INBAND_SUPP=N; FAX_PREF_MODE=FAX_T38_CAMODE; 
SRC_CIRCUIT_ID_SUPP=Y; DST_CIRCUIT_ID_SUPP=Y; VIDEO_SUPP=Y; 
H245_SESSION_MODE=H245-FLOWAROUND; CALL_CONNECT_MODE=AUTO; H245_TUNNELING=AUTO; 
SEND_CALL_PROCEEDING=AUTO; USE_SUB_DN=Y;

ADD H323_TERM ID=TERM1-h323; TSAP_ADDR=10.89.227.114:1720; 
H323_TERM_PROFILE_ID=TERM_PROFILE_1; H323_GW_ID=H323_GW1; ADD H323_TERM 
ID=TERM2-h323; TSAP_ADDR=10.89.227.115:1720; 
H323_TERM_PROFILE_ID=TERM_PROFILE_1; H323_GW_ID=H323_GW1;

ADD SUBSCRIBER_PROFILE ID=sp1; DIAL_PLAN_ID=cdp1; POP_ID=27;

add subscriber id=video_1; category=INDIVIDUAL; name=John Elway; status=ACTIVE; 
address1=1651 n glenville suite 200; address2=Richardson tx 75081; 
ss-number=111-11-1111; sip-url=//gateway21.home.com; billing-dn=972-519-1000; 
dn1=972-519-1000; sub-profile-id=sp1; TERM_TYPE=H323; H323_TERM_ID=TERM1-h323;

add subscriber id=video_2; category=INDIVIDUAL; name=Dan Marino;status=ACTIVE; 
address1=1651 n glenville suite 200; address2=Richardson tx 75081; 
ss-number=222-22-2222; sip-url=//gateway21.home.com; billing-dn=972-519-1001; 
dn1=972-519-1001; sub-profile-id=sp1; TERM_TYPE=H323; H323_TERM_ID=TERM2-h323;

################################################################################
#
# CHANGE H323 TRUNKS
################################################################################
#

CHANGE TRUNK_GRP ID=318; CALL_AGENT_ID=CA146; DIAL_PLAN_ID=cdp1; 
H323_GW_ID=H323_GW1;
CHANGE TRUNK_GRP ID=469; CALL_AGENT_ID=CA146; DIAL_PLAN_ID=cdp1; 
H323_GW_ID=H323_GW2;

add qos id=silver_svc; 

Troubleshooting Information

This section provides examples of possible problems you may encounter while working with H.323, and recommended solutions.

Outgoing Trunk Group is Out of Service

[I4 10:40:00.299 BCM  01-1 BCM_Main]  "bcm_sel_term_tg_id(): get_tg_from_route() 
fail" [bcm_bcsm_util.c:2614]
[***ERROR*** 10:40:00.299 BCM  01-1 BCM_Main   ]  "Route Selection Failure" 
[bcm_obcsm_sa_proc.c:3961]

This is an indication that the outgoing H.323 trunk group is out of service.

Verify the status of outgoing trunk group as follows:

CLI>status trunk_grp id=8991;
Reply : Success: 

TGN ID -> 8991
ADMIN STATE -> ADMIN_OOS 
OPER STATE -> Trunk group in-service
REASON -> ADM executed successful
RESULT -> ADM configure result in success

Solution

Use CLI to place the trunk_grp in-service as follows:

CLI> control trunk_grp id=8991; target-state=ins; mode=forced;

Outgoing H.323 Gateway is Out of Service

[***WARN**** 10:47:44.793 H3A3 01-1 Main ] "Call failure H3A--->BCM sent for 
csaid=41 callid=0 reason=H323 gateway/gk seem to be OOS" [h3a_sig_sai.c:1525]

This is an indication that the outgoing H.323 gateway is "out of service".

Verify the status of outgoing H.323 gateway:

CLI>status h323_gw id=CHINA_3; 
Reply : Success: 

ADMIN STATE -> ADMIN_OOS 
H3A PROCESS NUMBER -> 32
H3A PROCESS NAME -> H3A3
ENDPOINT ID -> 
ACTIVE CALLS -> 0
RAS STATE -> CCH323_RAS_STATE_NONE
RAS PORT -> 0
IP ADDRESS -> 
REGISTERED GATEKEEPER ID -> NOT REGISTERED
PRIMARY GATEKEEPER ID -> 
PRIMARY GATEKEEPER PORT -> 0
PRIMARY GATEKEEPER IP -> 
H323 VERSION -> 4
TIME TO LIVE -> 0
NUM ALT GATEKEEPERS -> 0
ALT GATEKEEPER PERMANENT -> FALSE
THRESHOLD ENABLED -> FALSE
OUT OF RESOURCES -> FALSE
ALT GATEKEEPER LIST -> 

Solution

Use CLI to place the h323_gw in-service as follows:


CLI>control h323_gw id=CHINA_3; target-state=ins;
Reply : Success: CLI change successful

H323GW ID -> CHINA_3
INITIAL STATE -> ADMIN_OOS 
REQUEST STATE -> ADMIN_INS 
RESULT STATE -> ADMIN_INS 
FAIL REASON -> ADM found no failure
REASON -> ADM executed successful
RESULT -> ADM configure result in success

H.323 Gateway Fails to Register With GK (Invalid Alias)

When the H.323 gateway registers with a gatekeeper, sometimes an alias list is provided to the gatekeeper in the RRQ message from gateway. Currently, this configuration is supported on IOS gateways (not in use on Cisco BTS 10200 Softswitch) when FXS ports are involved. If an RRJ message is received by gateway with reject reason of "invalidAlias", this is symptomatic of an alias list being provided to the gatekeeper but the gatekeeper not configured to be responsible for the prefix associated with each of the aliases.

[+ .            H3A3 .    .          ] "value RasMessage ::= gatekeeperReject : 
"
[+ .            H3A3 .    .          ] "    {"
[+ .            H3A3 .    .          ] "      requestSeqNum 11"
[+ .            H3A3 .    .          ] "      protocolIdentifier { 0 0 8 2250 0 
3 }"
[+ .            H3A3 .    .          ] "      rejectReason invalidAlias : NULL"
[+ .            H3A3 .    .          ] "    }"


Example:

Local gatekeeper that gateway is trying to register with configured as follows:

zone prefix China-GK 30*

zone prefix China-GK 281*

zone prefix China-GK 29*

Gateway has the following aliases that it wishes to register with:

c2620.50#show gateway

Gateway China-GW1 is not registered to any gatekeeper

Alias list (CLI configured)

E164-ID 20751101

E164-ID 20751102

E164-ID 20751103

E164-ID 20751104

In this case, China-GK does not have a prefix to match any of the E164 numbers.

Solution

Add a zone prefix entry to China-GK that would cause a match on the alias numbers that are trying to be registered as follows:

zone prefix China-GK 20*

Outgoing H.323 Gateway Unregistered With GK and Needs to Use RAS

[I4 10:52:44.824 H3A3 01-1 Lib_DBM] "H3A: h3a_use_ras Checking for RAS" 
[h3a_dbm.c:543]
[I4 10:52:44.824 H3A3 01-1 Lib_DBM] "h3a_get_dest_ip_addr: Need to use RAS 
......" [h3a_dbm.c:484]
[4? 10:52:44.824 H3A3 01-1 H_EVT] ": for callID 5 <cch323_call_setup_normal in 
gw/src/cch323_gw_api.c:4247>"
 [bts/os/src/bts_debug.c:200]
[4? 10:52:44.824 H3A3 01-1 H_225_EVT]  "H.225 SM: process event 
H225_EVENT_RAS_RESOLVE, for callID 5 <cch323_send
_event_to_h225 in gw/src/cch323_h225.c:337>" [bts/os/src/bts_debug.c:200]
[4? 10:52:44.824 H3A3 01-1 H_225_EVT]  "cch323_run_h225_sm: received event 
H225_EVENT_RAS_RESOLVE while at state
H225_IDLE <cch323_run_h225_sm in gw/src/cch323_h225.c:10085>" 
[bts/os/src/bts_debug.c:200]
[4? 10:52:44.824 H3A3 01-1 H_EVT]  ": state = 0 
<cch323_traverse_enum_contact_list in gw/src/cch323_gw_api.c:
4652>" [bts/os/src/bts_debug.c:200]
[I3 10:52:44.824 H3A3 01-1 Main]  "Rel message from STACK--->H3A for callid=5, 
cause code=16" [h3a_sig_sai.c:1549] 

This is an indication that the outgoing H.323 gateway needs to use RAS to complete the call, but because the gateway is not registered with a gatekeeper, the call is released.

Verify the status of the H.323 gateway with CLI command as follows:

CLI>status h323_gw id=CHINA_3;
Reply : Success: 

ADMIN STATE -> ADMIN_INS  
H3A PROCESS NUMBER -> 32
H3A PROCESS NAME -> H3A3
ENDPOINT ID -> 
ACTIVE CALLS -> 0
RAS STATE -> CCH323_RAS_STATE_GRQ
RAS PORT -> 59723
IP ADDRESS -> 10.89.225.165
REGISTERED GATEKEEPER ID -> NOT REGISTERED
PRIMARY GATEKEEPER ID -> China-GK
PRIMARY GATEKEEPER PORT -> 1719
PRIMARY GATEKEEPER IP -> 10.89.227.198
H323 VERSION -> 4
TIME TO LIVE -> 0
NUM ALT GATEKEEPERS -> 0
ALT GATEKEEPER PERMANENT -> TRUE
THRESHOLD ENABLED -> FALSE
OUT OF RESOURCES -> FALSE
ALT GATEKEEPER LIST -> CLI>status h323_gw id=CHINA_3;

This shows that the H.323 gateway is inservice, but it is not registered with a gatekeeper. The following are possible reasons for this:Incorrect provisioning for H323_GW2GK ( incorrect gk name, incorrect gk ip address, security violation) ---- this can be verified by trace logs as a GRJ would be sent back by GK as follows:

[+  .            H3A3 .    .          ]  "value RasMessage ::= 
gatekeeperReject : "
[+  .            H3A3 .    .          ]  "    {"
[+  .            H3A3 .    .          ]  "      requestSeqNum 11"
[+  .            H3A3 .    .          ]  "      protocolIdentifier { 0 0 8 
2250 0 3 }"
[+  .            H3A3 .    .          ]  "      rejectReason 
terminalExcluded : NULL"
[+  .            H3A3 .    .          ]  "    }"

Gatekeeper is down ( no alternate GK or alternate is also down) --- this can be verified by trace logs as a timout would occur (waiting for GCF or GRJ) after the H.323 GRQ has been sent.

No Matching Dial Plan Found on Incoming H.323 Trunk Group

[I2 14:45:24.288 BCM  01-1 Lib_RTM]  "dial_plan(pcld=45145211, dp_idx=0): no 
match" [rtm_dial_plan.c:492]
[***ERROR*** 14:45:24.288 BCM  01-1 BCM_Main]  "No Dial Plan Entry for digits  
in dial plan 0" [bcm_obcsm_sa_proc.c:8916]

After the SETUP message has been received at incoming H.323 gateway, BCM uses the dial_plan_id in the incoming trunk group and the called number to find out how to route the call. If no match is found, then this error will be issued.

Solution

Add an entry to dial_plan for called number and assign the id to incoming trunk_grp.

CLI> add dial_plan id=cdp1; digit_string=451452; dest_id=ipdest; min_digits=7; 
max_digits=10;
CLI> change trunk_grp id=8991;  dial_plan_id=cdp1;

Configuration at Softswitch or Gatekeeper Has Placed Routing Into a Loop

[I5 10:16:20.921 BCM  01-1 BCM_Main]  "BCM:TPM:Incr Counter( 3 ):4199302144" 
[bcm_tpm_proc.c:106]
[***ERROR*** 10:16:20.921 H3A3 01-1 Main]  "alarm=99 reason=<Loop detected!!> 
call cleared for callid=1
39 " [h3a_alarms.c:281]

Solution

The routing problem could be in either the gatekeeper or the Cisco BTS 10200 Softswitch. Check the gatekeeper against the dialedDigits pattern in the ARQ, example:

destinationInfo "
[+  .            H3A3 .    .          ]  "      {"
[+  .            H3A3 .    .          ]  "        dialedDigits : "9991231234""
[+  .            H3A3 .    .          ]  "      }"

There are multiple ways that a gatekeeper could determine the destCallSignalAddress to send back in a ACF:

A registered E164 addresss ( in this case, highly unlikely)

A static route configured ( has been observed )

Default routing ( highest frequency of problem )

Outgoing H.323 Calls Routed to Incorrect Endpoint When Using RAS

[I3 14:25:17.215 H3A3 01-1 Main]  "Rel message from STACK--->H3A for callid=8, 
cause code=3" [h3a_sig_sai.c:1549]

After the SETUP message has been sent out, a RELEASE COMPLETE is received from the remote endpoint. In this case, the remote endpoint does not service the destination address ( cause code=3).

Solution

Login to gatekeeper that outgoing H.323 gateway is registered with and determine the routing for called number. Gatekeeper could be configured to route based on several configurations:

Called number is matched against static routing

No routing defined for called number, uses default routing

Routing is based on tech prefix ( will be prepended to called number in ARQ)

Outgoing H.323 Calls Routed to Incorrect Endpoint When Using Direct Signaling

[I3 14:25:17.215 H3A3 01-1 Main]  "Rel message from STACK--->H3A for callid=8, 
cause code=3" [h3a_sig_sai.c:1549]

After the SETUP message has been sent out, a RELEASE COMPLETE is received from the remote endpoint. In this case, the remote endpoint does not service the destination address ( cause code=3).

Verify the value assigned to the SOFTSW_TSAP_ADDR for the outgoing H.323 trunk group

CLI>show trunk_grp id=8991;
Reply : Success: Entry 1 of 1 returned.

ID=8991
CALL_AGENT_ID=CA146
TG_TYPE=H323
SOFTSW_TSAP_ADDR=10.89.227.119;
TG_PROFILE_ID=CHINA
STATUS=INS
DIRECTION=BOTH
SEL_POLICY=ASC
GLARE=SLAVE
ALT_ROUTE_ON_CONG=N
SIGNAL_PORTED_NUMBER=N
DIAL_PLAN_ID=cdp1
DEL_DIGITS=0
OPER_STATUS=NF

Solution

If the value for the SOFTSW_TSAP_ADDR is incorrect, use CLI to make the change as follows:

CLI> change trunk_grp id=8991;  softsw_tsap_addr=10.89.227.219;

RAS Still Used When Outgoing H.323 Call is Provisioned to Use Direct Signaling

[I4 14:29:21.163 H3A3 01-1 Lib_DBM ] "H3A: h3a_use_ras Checking for RAS" [h3a_dbm.c:543]

[I4 14:29:21.163 H3A3 01-1 Lib_DBM ] "H3A: we need to use the destIP from trunk_grp table " [h3a_dbm.c:489]

[***ERROR*** 14:29:21.163 H3A3 01-1 Lib_DBM ] "h3a_get_dest_ip_addr: softsw_tsap_addr not set..." [h3a_dbm.c:494]

Although the configuration has specified to no use RAS, if no valid remote endpoint is provided, the fallback mechanism is to try RAS to determine the remote endpoint.

Verify the configuration for the outgoing trunk group with CLI:

CLI>show trunk_grp id=8991;
Reply : Success: Entry 1 of 1 returned.

ID=8991
CALL_AGENT_ID=CA146
TG_TYPE=H323
TG_PROFILE_ID=CHINA
STATUS=INS
DIRECTION=BOTH
SEL_POLICY=ASC
GLARE=SLAVE
ALT_ROUTE_ON_CONG=N
SIGNAL_PORTED_NUMBER=N
DIAL_PLAN_ID=cdp1
DEL_DIGITS=0
OPER_STATUS=NF
QOS_ID=china_qos1
TRAFFIC_TYPE=LOCAL
H323_GW_ID=CHINA_3
CAUSE_CODE_MAP_ID=H323_CHINA
ANI_BASED_ROUTING=N
NO_ANSWER_TMR=185

Since the SOFTSW_TSAP_ADDR column is not displayed, it contains a null value.

Solution

Use CLI to change the outgoing trunk group as follows:

CLI> change trunk_grp id=8991;  softsw_tsap_addr=10.89.227.219;

Appendix A: Interoperability Data

Table 3 through Table 9 provide information on interoperability of the Cisco BTS 10200 Softswitch with H.323 IOS-based gateways, Cisco CallManager, and MGCP-based gateways.

The call configurations are described using designations A, B, and C as follows:

A=Input (incoming signaling from a remote endpoint)

B=MGCP-based subscriber line controlled by the Cisco BTS 10200 Softswitch, with the specific feature subscribed and activated

C=Output (outgoing signaling to a remote endpoint)

Table 3 lists interoperability support for the call forwarding unconditional (CFU) feature:

A->B(CFU)->C — A calls B (B has CFU activated), call is forwarded to C

A<->C — A connected to C

Table 3 CFU Interoperability via H.323 

A (Incoming)
C (Outgoing)
Supported or
Not Supported

H.323 IOS

H.323 IOS

Supported

H.323 IOS

MGCP

Supported

H.323 IOS

Cisco CallManager

Supported

Cisco CallManager

H.323 IOS

Supported

Cisco CallManager

MGCP

Supported

Cisco CallManager

Cisco CallManager

Supported

MGCP

H.323 IOS

Supported

MGCP

MGCP

Supported

MGCP

Cisco CallManager

Supported


Table 4 lists interoperability support for the call forwarding busy (CFB) feature:

A->B(CFB)->C — A calls B (B has CFB activated), call is forwarded to C

A<->C — A connected to C

Table 4 CFB Interoperability via H.323 

A (Incoming)
C (Outgoing)
Supported or
Not Supported

H.323 IOS

H.323 IOS

Supported

H.323 IOS

MGCP

Supported

H.323 IOS

Cisco CallManager

Supported

Cisco CallManager

H.323 IOS

Supported

Cisco CallManager

MGCP

Supported

Cisco CallManager

Cisco CallManager

Supported

MGCP

H.323 IOS

Supported

MGCP

MGCP

Supported

MGCP

Cisco CallManager

Supported


Table 5 lists interoperability support for the call forwarding no answer (CFNA) feature:

A->B(CFNA)->C — A calls B (B has CFNA activated), call is forwarded to C

A<->C — A connected to C

Table 5 CFNA Interoperability via H.323 

A (Incoming)
C (Outgoing)
Supported or
Not Supported

H.323 IOS

H.323 IOS

Supported

H.323 IOS

MGCP

Supported

H.323 IOS

Cisco CallManager

Not supported

Cisco CallManager

H.323 IOS

Not supported

Cisco CallManager

MGCP

Supported

Cisco CallManager

Cisco CallManager

Not supported

MGCP

H.323 IOS

Supported

MGCP

MGCP

Supported

MGCP

Cisco CallManager

Supported


Table 6 lists interoperability support for the three-way call (TWC) feature:

A->B — A connected to B

B->C — B calls C to establish TWC

A,B,C TWC — A, B, and C connected on TWC

Table 6 TWC Interoperability via H.323 

A (Incoming)
C (Outgoing)
Supported or
Not Supported

H.323 IOS

H.323 IOS

Supported

H.323 IOS

MGCP

Supported

H.323 IOS

Cisco CallManager

Supported

Cisco CallManager

H.323 IOS

Supported

Cisco CallManager

MGCP

Supported

Cisco CallManager

Cisco CallManager

Supported

MGCP

H.323 IOS

Supported

MGCP

MGCP

Supported

MGCP

Cisco CallManager

Supported


Table 7 lists interoperability support for the call waiting (CW) and call waiting deluxe (CWD) features. These scenarios are applicable with or without codec up-speed:

A<->B — A connected to B

C->B — C calls B

A on hold C<->B — B puts A on hold, and C is connected to B

Table 7 CW and CWD Interoperability via H.323 

A (Incoming)
C (Outgoing)
Supported or
Not Supported

H.323 IOS

H.323 IOS

Supported

H.323 IOS

MGCP

Supported

H.323 IOS

Cisco CallManager

Supported

Cisco CallManager

H.323 IOS

Supported

Cisco CallManager

MGCP

Supported

Cisco CallManager

Cisco CallManager

Supported

MGCP

H.323 IOS

Supported

MGCP

MGCP

Supported

MGCP

Cisco CallManager

Supported


Table 8 lists interoperability support for the consultative call transfer (consultative CT) feature without codec speedup:


Note Consultative CT means that the transferring party (caller B) is connected to the transferred-to party (caller C) before completing the connection of the transferred party (caller A) to caller C. Codec speedup refers to modification of the codec type to a higher compression rate, PCMU or MCMA, during the call.


A<->B — A connected to B

A on hold B->C — B puts A on hold, and calls C

B<->C — B connected to C

B on hook A<->C — B goes on hook, and A is connected to C

Table 8 Consultative CT without Codec Speedup—Interoperability via H.323 

A (Incoming)
C (Outgoing)
Supported or
Not Supported

H.323 IOS

H.323 IOS

Supported

H.323 IOS

MGCP

Supported

H.323 IOS

Cisco CallManager

Supported

Cisco CallManager

H.323 IOS

Not supported

Cisco CallManager

MGCP

Supported

Cisco CallManager

Cisco CallManager

Not supported

MGCP

H.323 IOS

Supported

MGCP

MGCP

Supported

MGCP

Cisco CallManager

Supported


Table 9 lists interoperability support for the consultative call transfer (consultative CT) feature with codec speedup:

A<->B — A connected to B

A on hold B->C — B puts A on hold, and calls C

B<->C — B connected to C

B on hook A<->C — B goes on hook, and A is connected to C

Table 9 Consultative CT with Codec Speedup—Interoperability via H.323 

A (Incoming)
C (Outgoing)
Supported or
Not Supported

H.323 IOS

H.323 IOS

Not supported

H.323 IOS

MGCP

Supported

H.323 IOS

Cisco CallManager

Not supported

Cisco CallManager

H.323 IOS

Not supported

Cisco CallManager

MGCP

Supported

Cisco CallManager

Cisco CallManager

Not supported

MGCP

H.323 IOS

Supported

MGCP

MGCP

Supported

MGCP

Cisco CallManager

Supported


Appendix B: Billing Data Generation and Data Fields

The VIDEO-SUPP flag in the H323-TG-PROFILE and H323-TERM-PROFILE tables allows the service provider to identify individual call legs as video-enabled in the billing data record.


Note This flag affects only CDB fields. It does not affect the fields in the PacketCable-based event messages.


Billing Data Generation

The Cisco BTS 10200 Softswitch uses H.245 flow-around mode to transmit video calls. In this mode, the system does not perform dynamic identification of video calls for billing purposes. Instead, the system identifies video-capable call legs by looking up the static provisioning in the H323-TG-PROFILE and H323-TERM-PROFILE tables for both the originating and terminating endpoints.

The Cisco BTS 10200 Softswitch examines the Bearer Capability field of incoming SETUP messages and takes the following actions:

For an outgoing H.323 call, if either of the endpoints is configured as not video-capable (in H323-TG-PROFILE and H323- TERM-PROFILE tables), the system identifies the outgoing call leg as "speech" in the CDR.

If the call is coming from (or going to) an H.323 TG that is video-capable (VIDEO-SUPP=Y), all call legs on this TG to (or from) H.323 video phones connected to the Cisco BTS 10200 Softswitch are identified as video-capable in the CDRs.

The following calling conditions do not have any effect on the billing record generated by the Cisco BTS 10200 Softswitch:

Use of the privacy button on either of the phones in the call

A midcall change from video mode to speech mode

Billing Data Fields

Table 10 lists the new and revised billing data fields for the new features covered in this document. For a complete list of existing billing data fields contained in the output CDB files transmitted from the Element Management System (EMS), refer to the Cisco BTS 10200 Softswitch Billing Interface Guide.

Table 10 CDB Fields New or Modified for Release 4.2 

Common Name
Field Type
Field Size
Potential Values
Field Description

Source Service Provider Id

String

16

Alphanumeric characters

The service provider ID supplied by the gatekeeper for calls coming into the PSTN gateway. The information is derived from the inbound trunk group. If this field is NULL, no data was captured for this record.

Note This field was introduced in a prior release, and is listed here for reference only.

Destination Service Provider Id

String

16

Alphanumeric characters

The service provider ID used for calls routing out of the PSTN gateway. The information is derived from the outbound trunk group. If this field is NULL, no data was captured for this record.

Note This field was introduced in a prior release, and is listed here for reference only.

Originating Network Provider Id

String

16

Alphanumeric characters

Originating network service provide (ISTP) id returned by the Gatekeeper in the ACF message for outbound H.323 calls. If this field is NULL, no data was captured for this record.

(New field in Release 4.2)

Destination Network Provider Id

String

16

Alphanumeric characters

Destination network service provide (ISTP) id returned by the Gatekeeper in the ACF message for outbound H.323 calls. If this field is NULL, no data was captured for this record.

(New field in Release 4.2)

Original Originating Number

String

64

DIGITS

This field contains the calling number received in the SETUP message after digit manipulation is performed but before any overriding occurs, such as overwriting with a billing DN. If this field is NULL, no data was captured for this field.

(New field in Release 4.2)

Video Codec

Numeric

 

None = 0 (default)

H.261 = 1 (future)

H.263 = 2 (future)

H.264 = 3 (future)

This is the codec that was use to transport the RTP traffic. The value in this field is pulled from the provisioning of the Cisco BTS 10200 Softswitch, not from the actual SDP message.

Note This field is always set to zero in Release 4.2.

(New field in Release 4.2)

Originating H323 Call Type

Numeric

 

VOIP = 1

TELEPHONY = 2

VIDEO = 3

Indication of the protocol family used on the originating leg of the call. This field is only populated for calls over an H.323 network. If this field contains a value of zero, no data was captured for this record.

(New type VIDEO added in Release 4.2)

Originating H323 Gateway Id

String

16

Alphanumeric characters

For incoming calls from the H.323 network, this field will contain the H323-ID of the originating (peer) H.323 gateway/endpoint. If this parameter is not available in the incoming H.323 call, the Cisco BTS 10200 Softswitch populates this field with the local H323-ID from the H323-GW that received the call. For incoming calls from non-H.323 networks, this field is NULL.

(Description modified in Release 4.2)

Terminating H323 Call Type

Numeric

 

VOIP = 1

TELEPHONY = 2

VIDEO = 3

Indication of the protocol family used on the terminating leg of the call. This field is only populated for calls over an H.323 network. If this field contains a value of zero, no data was captured for this record.

(New type VIDEO added in Release 4.2)

Terminating H323 Gateway Id

String

16

Alphanumeric characters

For outgoing calls from the Cisco BTS 10200 Softswitch terminating to an H.323 network, this field contains the H323-ID of the terminating (peer) H.323 gateway/endpoint if available in the backward call signaling message. If this parameter is not available from the terminating H.323 Gateway/endpoint, the Cisco BTS 10200 Softswitch populates the local H323-ID from the H.323-GW that is used to send out the call. For outgoing calls to non-H.323 networks, this field is NULL.

(Description modified in Release 4.2)


Technical Assistance

Description
Link

Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/public/support/tac/home.shtml