H.323 Provisioning, Operating, and Troubleshooting Guide (Release 4.5.1) - Revised 10/25/2006
Available Languages
Table Of Contents
Cisco BTS 10200 Softswitch in the H.323 Packet Network
Interoperability with Cisco CallManager and Other Endpoints
Prerequisites for Interoperability
Limitations on Interoperability
Restart and Failover Scenarios
Limitations on Annex E Support
Message Tunneling and Protocol Transparency for H.323-Based Transit Traffic
Reattempt, Route Advance, and Hairpinning (Redirection)
Reattempt and Route Advance on H.323-Based Calls
Hairpinning (Call Redirection) on H.323-Based Calls
Supported Interfaces and Interworking
End-to-End SDP Exchange for T.38 Media and the H.323 Interface
Provisionable Parameters for T.38 Fax Over H.323
Additional H.323-Related Features
Planning for Redundant Operation of H.323 Links
Prerequisites for H.323 Networks
Networks Without GKs (Direct Routing)
Interoperability with Other H.323 Endpoints
Functionality Related to Video Phones
Functionality Related to ATA Clients
Interoperability Data for Cisco IOS GWs, Cisco CallManager, and MGCP GWs
Provision H.323-Based TGs, Logical GWs, and GKs
H.323-Based Logical GWs Internal to the Cisco BTS 10200 Softswitch
Provision H.323-Based Video Phone Terminals and Subscribers
Provision H.323-Based Outbound Routing Data
Understanding the Outbound Routing Process
Outbound Routing Option Summary
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
Provision ANI Screening and Routing
ANI Screening vs. ANI-Based Routing
Identification of H.323 Terminal Property Based on ANI
Provision for Interoperability with Cisco CallManager
Assign a Main Subscriber ID when Cisco CallManager Is Used as a PBX
Provision Annex E Functionality
Provision Additional H.323 Options
H.323 Protocol Transparency Functions
H.323-Based T.38 Fax Parameters
Additional Advanced H.323 Features
Example of Provisioning Script
Identifying Call Legs As Video-Enabled
Billing Data Generation for Video Calls
Billing Records for Calls to/from Cisco CallManager
Updated Billing Field Descriptions
Dual Links for H.323 Signaling Transport
Automatic Recovery Process When GWs are Registered to a GK
Automatic Recovery Process When No GK Is Used (Direct Routing)
Outgoing Trunk Group is Out of Service
Outgoing H.323 Gateway is Out of Service
H.323 Gateway Fails to Register With GK (Invalid Alias)
Outgoing H.323 Gateway Unregistered With GK and Needs to Use RAS
Stable Calls Are Dropped When CA Switches Over
No Matching Dial Plan Found on Incoming H.323 Trunk Group
Configuration at Softswitch or Gatekeeper Has Placed Routing Into a Loop
Outgoing H.323 Calls Routed to Incorrect Endpoint When Using RAS
Outgoing H.323 Calls Routed to Incorrect Endpoint When Using Direct Signaling
RAS Still Used When Outgoing H.323 Call is Provisioned to Use Direct Signaling
Cisco IOS - Cisco CallManager - MGCP Interoperability Data
H.323 Provisioning, Operating, and Troubleshooting Guide for the
Cisco BTS 10200 Softswitch, Release 4.5.1
Revised: October 25, 2006, OL-8300-03This document describes how the Cisco BTS 10200 Softswitch implements H.323 interfaces and functions in Release 4.5.1. It also provides H.323 provisioning, operating, and troubleshooting procedures.
Note
H.323 applications are supported in Release 4.5.1, but not in Release 4.5.0.
Feature History
Release 4.5.1
Document OL-8300-03:
•
Document OL-8300-02:
•
Document OL-8300-01:
•
•
–
–
–
–
•
Release 4.4.1
Document OL-7280-05:
•
Document OL-7280-04:
•
•
Document OL-7280-03: Applicability to Release 4.4.1 was clarified.
The document title and introduction were modified for clarity.Document OL-7280-02: References were included to the Cisco BTS 10200 Softswitch Provisioning Guide and Cisco BTS 10200 Softswitch Command Line Interface Guide.
Document OL-7280-01:
•
•
•
Release 4.2
The following enhancements were provided in this release:
•
•
•
•
•
•
•
•
•
Release 4.1
Annex E UDP capability was introduced.
Release 3.2
H.323 signaling was introduced on the Cisco BTS 10200 Softswitch.
Contents
This document contains the following sections:
Overview
This section provides technical information about the implementation of H.323 features. It covers the following topics.
•
•
•
•
•
•
Cisco BTS 10200 Softswitch in the H.323 Packet Network
The Cisco BTS 10200 Softswitch provides native H.323 signaling, which allows it to communicate directly with H.323 gatekeepers (GKs) and gateways (GWs). The Cisco BTS 10200 Softswitch can be configured as up to four logical H.323 GWs. The Cisco BTS 10200 Softswitch H.323 subsystem includes H.225 and registration, administration, and status (RAS) signaling control, and H.245 connection control. The Cisco BTS 10200 Softswitch also provides signaling for other trunks and lines over Media Gateway Control Protocol (MGCP) and Session Initiation Protocol (SIP). In addition, the Cisco BTS 10200 Softswitch provides access to the public switched telephone network (PSTN). It communicates with IP transfer points (ITPs) that act as signaling gateways (SGs) for SS7-based networks, and with the trunking gateways (TGWs) that provide the bearer path. The details of these signaling links are shown in Figure 1.
Figure 1 Signaling Links with the Cisco BTS 10200 Softswitch and Cisco CallManager
Note
The Cisco BTS 10200 Softswitch H.323-based functions can be used on managed H.323 networks that contain the Cisco BTS 10200 Softswitch and the following network element types:
•
•
•
•
•
•
•
Note
Note
- Fast-start refers to fast-connect procedures.
- Slow-start refers to non-fast-connect mode.
Summary of H.323 Capabilities
The following H.323 features and services are provided:
•
•
•
•
•
•
•
•
•
•
•
The Cisco BTS 10200 Softswitch supports the following signaling capabilities:
•
•
–
–
–
•
•
•
Interoperability with Cisco CallManager and Other Endpoints
The interoperability between the Cisco BTS 10200 Softswitch, Cisco CallManager, and Cisco IOS H.323 GWs enhances the delivery of call control features between enterprise networks and service provider networks.
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 Connection of Calls between Phones on Separate Cisco CallManager Systems
The following details are covered in this section:
•
•
Prerequisites for Interoperability
To ensure that the Cisco BTS 10200 Softswitch, the Cisco CallManager, and IOS-based H.323 GWs interoperate properly, ensure that your system meets the following conditions:
•
–
–
–
Note
Note
•
Note
•
–
Note
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.
–
–
–
Caution
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:
•
•
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 the Cisco BTS 10200 Softswitch and Cisco CallManager resumes after the H.323 call processing function is running.
Note
Note
•
Cisco CallManager.Limitations on Subscriber Features
The Cisco BTS 10200 Softswitch provides connectivity with H.323 IOS-based GWs, Cisco CallManager, and MGCP-based GWs. These systems interoperate to provide subscriber features such as call forwarding, call waiting, call transfer, and three-way calling. See the "Cisco IOS - Cisco CallManager - MGCP Interoperability Data" section for additional data regarding interoperability of the Cisco BTS 10200 Softswitch with H.323 IOS-based gateways, Cisco CallManager, and MGCP-based gateways.
Annex E UDP Functionality
This section describes how the Cisco BTS 10200 Softswitch supports the User Datagram Protocol (UDP)-based Annex E feature of ITU-T Recommendation H.323 v4.
Note
Throughout this document, Annex E refers to UDP-based Annex E functionality. (The Cisco BTS 10200 Softswitch does not implement TCP-based Annex E.) In this document, TCP refers to TCP-based signaling without Annex E functionality.
Restart and Failover Scenarios
Annex E implementation allows H.323 signaling to be transported between the Cisco BTS 10200 Softswitch and the far-end H.323 endpoint using UDP (connectionless) signaling instead of TCP (connection-oriented) signaling. The choice of UDP or TCP signaling is important in a Cisco BTS 10200 Softswitch H.323 process restart or CA failover scenario.
Note
CA failover means an automatic CA switchover, in which the standby CA side becomes active and takes over for the previously active CA side. To support the stability of active calls, the CA preserves call processing data, and replicates this data from the active CA side to the standby CA side on a regular basis.
If an H.323 restart or CA failover occurs, a remote H.323 endpoint using TCP signaling cannot reestablish the connection with the previously active process or CA. Therefore, the stable H.323 call(s) on that connection are cleared. However, a remote H.323 endpoint using UDP to communicate with the Cisco BTS 10200 Softswitch in a connectionless session can continue to communicate with the newly active process or CA side using the same connectionless session. This allows the remote endpoint to preserve and support the active call. The Annex E feature must be enabled on the Cisco BTS 10200 Softswitch, the H.323 GK, and the remote H.323 endpoint.
Note
Use of the Annex E feature is optional and configurable in the Cisco BTS 10200 Softswitch. Each H.323 trunk group (TG) in the Cisco BTS 10200 Softswitch can be independently provisioned to support either Annex E UDP-based signaling or non-Annex-E TCP-based signaling. Each logical H.323 GW instance in the Cisco BTS 10200 Softswitch can have multiple outgoing TGs, with each TG independently configured for Annex E UDP signaling or non-Annex-E TCP signaling.
Limitations on Annex E Support
Annex E must be supported and enabled on both the originating and terminating sides of a call leg for the Annex E redundancy to be supported. If the far-end H.323 device does not support Annex E UDP (or if Annex E is disabled), the following limitations apply:
•
Note
•
Following are additional limitations on Annex E support:
•
•
•
•
If the H.323-GW process in the Cisco BTS 10200 Softswitch restarts, or if the CA fails over to the other side, Annex E UDP-based transient calls (calls that are in the process of being set up) can be impacted as follows:
•
•
–
–
–
After the ringing has terminated, the called party can receive a new incoming call or can go off-hook to receive dial tone.
•
–
–
After the ringback tone has terminated, the calling party can receive a new incoming call or can go off-hook to receive dial tone.
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:
•
Note
•
–
–
–
–
•
•
•
•
•
•
–
–
–
Reattempt, Route Advance, and Hairpinning (Redirection)
The Cisco BTS 10200 Softswitch supports reattempt, route advance, and hairpinning (redirection). In H.323-based networks, the system supports these functions only for calls that use fast-start procedures on the H.323-based call leg(s). It does not support these features for calls that use slow-start procedures.
Note
Reattempt and Route Advance on H.323-Based Calls
If a call does not complete, the Cisco BTS 10200 Softswitch can reattempt the call based on the release cause code. The action for each received cause code is provisionable in the Cause Code Map (cause-code-map) table. The call can be reattempted to the same TG or to another TG. The selection of the next TG depends on the cause code mapping analysis and on carrier-dependent routing rules.
Table 1 shows an example of mapping cause codes to actions for H.323 TGs.
The specific action for route advance is based on provisioning of the route table in the Cisco BTS 10200 Softswitch database. The service provider uses the route table 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 individual TGs can be H.323-based, or can be based on any of the other supported protocols. 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.
Hairpinning (Call Redirection) on H.323-Based Calls
On an incoming PSTN call, if the GK cannot route the incoming call, or if the GK determines that the call termination is on PSTN, the Cisco BTS 10200 Softswitch can send the call back out to the PSTN (hairpinning) or to another H.323 call leg (redirection).
T.38 Fax Support Over H.323
This section describes T.38 fax support over H.323.
Supported Interfaces and Interworking
The Cisco BTS 10200 Softswitch supports ITU-T T.38 procedures on the following H.323 interfaces:
•
•
•
•
•
Note
The Cisco BTS 10200 Softswitch supports interworking of T.38 procedures between H.323 trunks and the following interfaces:
•
•
•
•
T.38 Fax Call Features
The following call features apply to T.38 fax calls:
•
•
•
Note
Cisco CallManager.
T.38 Glare Handling
The Cisco BTS 10200 applies a call agent controlled switch to T.38 Fax media when initiated by either the originating or terminating endpoint. This includes when both endpoints initiate the switch, causing a glare condition at the Cisco BTS 10200.
For details about glare handling, contact your Cisco support representative.
End-to-End SDP Exchange for T.38 Media and the H.323 Interface
Note
The H.323 protocol must negotiate T.38 fax connection attributes (example: bit rate, maximum buffer size) during the voice call establishment using Terminal Capability Set (TCS) messages. However, for SIP and MGCP, the endpoint does not report T.38 fax connection attributes until the fax actually starts. When this occurs between an interworking H.323 endpoints to SIP/MGCP endpoints, and the H.323 endpoint is ready to send TCS message during voice call establishment phase, the T.38 fax attributes are not available from MGCP/SIP endpoints.
To overcome this interworking limitation, all Cisco IOS gateways assume the defaults for these attributes while exchanging TCS messages. Cisco BTS 10200 follows the same philosophy for H.323 to/from MGCP/NCS and H.323 to/from SIP calls. Cisco BTS 10200 assumes following defaults:
•
•
•
•
•
•
•
•
To overcome other interworking limitations with SIP, IOS H.323 gateways send the fax UDP port in H.245 Open Logical Channel (OLC) messages. A provisioning field (REMOTE_FAX_PORT_ RETRIEVAL_MSG) is added in h323-tg-profile and h323-term-profile, enabling the H.323 interface to read the remote endpoint fax UDP port either from OLC message or from OLC Ack message.
Provisionable Parameters for T.38 Fax Over H.323
For details on provisioning parameters, see the "H.323-Based T.38 Fax Parameters" section.
Additional H.323-Related Features
The Cisco BTS 10200 Softswitch provides the following additional provisionable H.323-based features:
•
•
•
•
•
–
–
•
Planning
This section provides guidelines and procedures for planning your H.323-based systems. It includes the following sections:
•
•
Tip
Restrictions and limitations are special conditions or scenarios for which these features might not work, or might behave in an unexpected manner.
Planning for Redundant Operation of H.323 Links
Figure 3 shows an H.323 network with the Cisco BTS 10200 Softswitch, H.323 GW (with Cisco IOS), and a gatekeeper (GK). Refer to this figure as needed during the planning procedures described in this section. During startup, the Cisco BTS 10200 Softswitch registers its active IP address (the address used for H.323 signaling) with the GK. The peer H.323 GW dynamically obtains the IP address by sending a query to the GK. When the GW signals the Cisco BTS 10200 Softswitch, it transmits to this IP address.
Figure 3 H.323 Network with Gatekeeper Present
The internal interfaces of the Cisco BTS 10200 Softswitch are shown in Figure 4. There are two signaling links on each CA (shown in the drawing as IF1 and IF2 on each CA unit).
•
•
Figure 4 Cisco BTS 10200 Softswitch Network Configuration
Note
Prerequisites for H.323 Networks
This section lists prerequisites for video phones, and for networks with and without GKs.
Video Phones
It might 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:
•
•
Networks with GKs
If the Cisco BTS 10200 Softswitch is connected to one or more GKs in the H.323 network, the GKs must be configured to support video calls:
•
•
Networks Without GKs (Direct Routing)
Setting Up Direct Routing on the Cisco BTS 10200 Softswitch
For direct routing scenarios (not using RAS signaling to a GK) the transport service access point (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. The TSAP addresses are provisioned for each applicable TG or terminal.
Setting Up Direct Routing on the Peer H.323 GW
If a GK is not used, direct routing must be set up on each of the peer H.323 GWs that communicates with the Cisco BTS 10200 Softswitch. Use this procedure to set up direct routing. While performing this procedure, refer to Figure 4 for a description of signaling interfaces and parameters.
Obtain information from the Cisco BTS 10200 Softswitch and provision the H.323 GW in the following way:
Step 1
host# nslookup h3a-SYS37CA146.ipclab.cisco.comTypical system response:Server: lion.ipclab.cisco.com Address: 10.89.224.1Name: h3a-SYS37CA146.ipclab.cisco.com Addresses: 10.89.226.17, 10.89.225.17
Tip
Step 2
status h323-gw id=GW37_Central_4;A typical system response is shown below.
Note
status h323-gw id=TB37_Central_4;ADMIN STATE -> ADMIN_INSH3A PROCESS NUMBER -> 40H3A PROCESS NAME -> H3A4ENDPOINT ID -> 6333EC4400000005ACTIVE CALLS -> 0RAS STATE -> CCH323_RAS_STATE_IDLERAS PORT -> 57781IP ADDRESS -> 10.89.225.17REGISTERED GATEKEEPER ID -> H5-GKPRIMARY GATEKEEPER ID -> H5-GKPRIMARY GATEKEEPER PORT -> 1719PRIMARY GATEKEEPER IP -> 10.89.227.80H323 VERSION -> 4TIME TO LIVE -> 60NUM ALT GATEKEEPERS -> 0ALT GATEKEEPER PERMANENT -> TRUETHRESHOLD ENABLED -> FALSEOUT OF RESOURCES -> FALSEALT GATEKEEPER LIST ->Step 3
Tip
a.
b.
Step 4
Note
Step 5
Restrictions and Limitations
This section describes restrictions and limitations applicable to the H.323 implementation.
Interoperability with Other H.323 Endpoints
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 you are selecting H.323-based devices, we recommend that you discuss your specific requirements with your Cisco account team.
The Cisco BTS 10200 Softswitch Release Notes document identifies the specific peripheral platforms and software loads that have been tested by Cisco for H.323 interoperability with the Cisco BTS 10200 Softswitch software. If you would like to use additional features and devices, ask your Cisco account team for assistance.
Note
Functionality Related to Video Phones
The Cisco BTS 10200 Softswitch supports basic call functions for video phones, along with the following subscriber features:
•
•
The following restrictions and limitations apply to video phone calls connected through the Cisco BTS 10200 Softswitch:
•
•
•
•
•
Functionality Related to ATA Clients
The Cisco BTS 10200 Softswitch supports basic call functions for ATA clients using H.323 protocol, along with the following subscriber features:
•
•
•
•
Interoperability Data for Cisco IOS GWs, Cisco CallManager, and MGCP GWs
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 the "Cisco IOS - Cisco CallManager - MGCP Interoperability Data" section for additional interoperability data.
Installing
There are no H.323-specific requirements for installation procedures for the Cisco BTS 10200 Softswitch as a result of the features covered in this document. (Installation procedures include hardware installation, cabling, jumpstart, application installation, software upgrade, and hardware upgrade.)
Configuring
This section explains how to perform the following tasks:
•
•
•
•
•
•
•
•
To see a complete set of commands, see the "Example of Provisioning Script" section.
Note
Note
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 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 one is 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.
2.
3.
4.
5.
6.
Note
DETAILED STEPS
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 one is 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.
2.
3.
4.
5.
DETAILED STEPS
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 parameter (or both) for the outbound call leg.
This section covers the following topics:
•
•
•
•
Understanding the Outbound Routing Process
Outbound routing is managed through a four-step process that starts when an H.323-based call is originated or received on the Cisco BTS 10200 Softswitch:
1.
2.
3.
4.
Tip
Table 2 describes several routing terms used in this section, and indicates the relationship of network terminology, H.225-message terminology, and the tokens used to control this data in the Cisco BTS 10200 Softswitch.
Outbound Routing Option Summary
Table 3 summarizes the outbound routing data options. It shows how the provisioned values affect the outbound routing data sent by the system.
Note
Table 3 Summary of H.323 Outbound Routing Data Options
Data Sent
or Outbound
TRUNK-GRP Table(Figure 5)
—
Set both
SEND-SRC-CIRCUIT-ID
and SEND-DEST-CIRCUIT-ID
to N (no).—
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 6)
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 7)
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 in the H323-TG-PROFILE table. See Figure 5, Part A.
Note
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:
•
•
See Figure 5, Part B.
Figure 5 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:
•
•
•
See Figure 6, 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:
•
•
•
See Figure 6, 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:
•
•
See Figure 6, Part C.
Figure 6 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 in the H323-TG-PROFILE table.
See Figure 7, 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.)
•
•
See Figure 7, Part B.
Figure 7 SS7-originated Calls Retransmitted as Outbound H.323 Calls with Circuit Info
SUMMARY STEPS
1.
2.
DETAILED STEPS
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 can be set to Y to send the circuit info parameters in the outgoing ARQ/SETUP messages.
TipStep 2
Matches incoming H.323 calls on a specific IP:port to a specific TG. It also disables automatic number identification (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
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 GK:
•
•
Figure 8 provides an overview of the H.323 inbound routing process.
Figure 8 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 9 TG Match with Source-Based Routing Disabled
Figure 10 TG Match with Source-Based Routing Enabled
Figure 11 H.323 TERM Check
Figure 12 ANI Screening and ANI Routing
Provision ANI Screening and Routing
This section provides 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:
•
•
•
•
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, the system compares the ANI received in the incoming SETUP message against the DN ranges provisioned in the ANI-SCREENING table:
•
•
Note
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 endpoint, the billing record (CDB) is labeled as video.
Provision for Interoperability with Cisco CallManager
Provision the Cisco BTS 10200 Softswitch interface to Cisco CallManager as you would any H.323 GW. Refer to the section on H.323 GW provisioning in the Cisco BTS 10200 Softswitch Provisioning Guide for this procedure. In addition, perform the following provisioning tasks to support interoperability between the two switches:
•
Assign a Main Subscriber ID when Cisco CallManager Is Used as a PBX
The Cisco BTS 10200 Softswitch connects to Cisco CallManager via an H.323 TG. 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.
Note
To provision a main subscriber ID on the TGs connecting the Cisco BTS 10200 Softswitch to Cisco CallManager, use this procedure.
Step 1
Step 2
show trunk-grp id=<ID of the TG towards Cisco CallManager>;
Example:
show trunk-grp id=TG001;
Step 3
Step 4
change trunk-grp id=<ID of the TG towards Cisco CallManager>; main-sub-id=<Main Subscriber ID for this Cisco CallManager>;
Example:
change trunk-grp id=TG001; main-sub-id=CallManager001;
Provision QoS Codec
To provision the QoS codec on the TGs that connect to Cisco CallManager, use this procedure.
Step 1
Step 2
show trunk-grp id=<ID of the TG towards Cisco CallManager>;
Example:
show trunk-grp id=TG001;
Step 3
Step 4
change trunk-grp id=TG001; qos_id=gold3;
Step 5
show qos id=<QOS ID>;
Example:
show qos id=gold3;
Step 6
a.
change qos id=<QOS ID>; codec-type=<desired codec type>;
Example:
change qos id=gold3; codec-type=PCMU;
b.
Step 7
Step 8
Disable GTD
We recommend that GTD be disabled on the TGs toward Cisco CallManager. This can be done either by disabling the GTD at Call Agent (CA) level or at the TG level.
Caution
Option to Disable GTD at CA Level
If specified in your local work order, you can disable GTD at the CA level. However, if your local work order requires GTD to be disabled only for certain trunks, skip these steps and go to the "Option to Disable GTD at TG Level" section.
Caution
Step 1
Step 2
show call-agent-profile id=<ID of the CA to which the Cisco CallManager is connected>;
(Example) show call-agent-profile id=CA146;
Step 3
a.
change call-agent-profile id=<ID of the CA to which the Cisco CallManager is connected>; gtd-supp=N;
(Example) change call-agent-profile id=CA146; gtd-supp=N;
b.
Step 4
Option to Disable GTD at TG Level
If specified in your local work order, you can disable GTD at the individual TG level.
Step 1
Step 2
show h323-tg-profile id=<ID of the TG-profile applicable to the Cisco CallManager>;
(Example) show h323-tg-profile id=TG501;
Step 3
a.
change h323-tg-profile id=<ID of the TG-profile applicable to the Cisco CallManager>; gtd-supp=N;
Example:
change h323-tg-profile id=TG501; gtd-supp=N;
b.
Step 4
Step 5
Provision Annex E Functionality
This section highlights the special parameters that must be provisioned to support Annex E functionality.
Note
Step 1
Step 2
change h323-gw id=city1gw; annexe-supp=Y; annexe-udp-port=2517; annexe-retransmit-timer=500; annexe-retransmit-multiplier=2; annexe-retransmit-attempts=8;
where:
•
•
Explanation–
–
–
–
•
•
•
•
Step 3
a.
status h323-gw id=city1gw;
b.
c.
d.
control h323-gw id=city1gw; target-state=INS;
e.
status h323-gw id=city1gw;
Step 4
CLI> change h323-tg-profile id=h323tg01; ras=Y; annexe-supp=Y; call-connect-mode=FAST-START; transport-pref-mode=UDP-MODE;
where:
•
•
•
•
•
–
–
Step 5
Note
Provision Additional H.323 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 sections:
•
•
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
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
Note
Permitted values for this token are as follows:
•
Note
•
•
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
•
•
Note
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 H.245 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
Note
•
•
Note
H.323-Based T.38 Fax Parameters
This section provides tips on provisioning H.323-based parameters for T.38 fax.
Provisioning fax-t38-enabled in the QoS Table
This parameter is a binary flag (Y/N) with default = `Y'. SIP-to-SIP and H.323-to-H.323 calls ignore this flag. QOS is optional for endpoints and trunks. The settings work as follows:
•
•
Table 4 illustrates under what conditions the Cisco BTS 10200 uses T.38 fax protocol when fax is detected. This depends on the value of the QOS FAX_T38_ENABLED field for each endpoint involved in the call, and the protocol type of each endpoint. The symbols are described as follows:
•
•
•
Provisioning remote-fax-port-retrieval-msg in the H323 TG Profile and H323 Term Profile Tables
The H.323 GW can report the UDP port for T.38 fax transmission in either H.245 OLC (default) or OLC ACK. To provision the H.323 interface, use the REMOTE-FAX-PORT- RETRIEVAL-MSG field in the h323-tg-profile and h323-term-profile tables. This parameter indicates the field in which the system should look for this value.
Note
Provisioning H.323 Parameters in the CA-CONFIG Table
The H.323 interface uses the following global parameters when negotiating the T.38 fax connection during voice call establishment when interworking with a non-H323 endpoint.
•
•
•
Additional Advanced H.323 Features
Additional H.323 advanced features include:
•
•
•
DTMF Relay Support on MGCP-to-H.323 Calls
For MGCP-to-H.323 (fast-connect) calls, RFC2833 capabilities are advertised for the H.323 call leg based on static information provisioned for the H.323 TG or terminal. Ensure that all far-end H.323 capabilities are provisioned in the appropriate table:
•
•
Asymmetric Codec Resolution
To enable the asymmetric codec resolution feature, set the CODEC-NEG-SUPP field in H323-TG-PROFILE (for H323 trunk-grp) or H323-TERM-PROFILE (for H323 subscriber) to Y, which is the default value. The configurable fields CODEC-NEG-TIMER and CODEC-NEG-ATTEMPTS in the H323-GW table control the codec resolution procedure. If the CODEC-NEG-SUPP field is configured as Y, it is not necessary for a codec to be configured in the QOS table of the 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 expects the far-end H.323 device (particularly one not using the fast-connect procedure) to use the codec configured in the QOS table entry of both the incoming and outgoing trunk-grp tables (or subscriber table). If the codecs of the two end devices do not match, the call will fail.
Note
Facility Message
The FACILITY message is used primarily 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 the far-end device supports receiving of the FACILITY message. The default value is Y. If H245-TUNNELING is set to AUTO or ENABLE, then the FACILITY-SUPP token should be set to Y.
Note
Media Cut-Through
The CUT-THRU-PARAM token 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
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
•
•
•
Configurable Status Enquiry Timer
If a CA failover occurs, the Cisco BTS 10200 Softswitch sends a STATUS ENQ message and starts the STATUS ENQ timer for each 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.
Reattempt, Route Advance, and Hairpinning (Redirection)
By default, the system attempts to send the FastStart element in the CALLPROCEEDING message if it is available; otherwise, the element is sent in the ALERTING or PROGRESS message, whichever is sent first. For H.323-to-H.323 (transit) calls, sending the FastStart element in the CALLPROCEEDING message could cause reattempt, route advance, or hairpinning to fail. To support these features for transit calls, you must set the SEND-FS-CALLP token (in the h323-tg-profile or h323-term-profile table) to N (No) to suppress sending the FastStart element in the CALLPROCEEDING message. The default value of this token is Y.
Tip
Table 5 lists the appropriate settings for the SEND-FS-CALLP token.
Example of Provisioning Script
##################################################################
# 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=813;
ADD OFFICE_CODE CALL_AGENT_ID=CA146; NDC=972; EC=813; 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; H245_SESSION_MODE=AUTO; CALL_CONNECT_MODE=AUTO; H245_TUNNELING=AUTO; SEND_CALL_PROCEEDING=AUTO; REMOTE_FAX_PORT_RETRIEVAL_MSG=H245_OLC; SEND_FS_CALLP=Y
# Add QOS ID to enable T38 Fax
ADD QOS ID=PCMU; CODEC_TYPE=PCMU; FAX_T38_ENABLED=Y;
# 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; QOS_ID=PCMU;
# 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; 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; REMOTE_FAX_PORT_RETRIEVAL_MSG=H245_OLC; SEND_FS_CALLP=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=Jane Doe; status=ACTIVE;
address1=9651 n glenville; address2=Richardson tx 75081; ss-number=111-11-1111; sip-url=//gateway21.home.com; billing-dn=972-813-5100; dn1=972-813-5100; sub-profile-id=sp1; TERM_TYPE=H323; H323_TERM_ID=TERM1-h323;add subscriber id=video_2; category=INDIVIDUAL; name=John Smith; status=ACTIVE; address1=8651 n glenville suite 200; address2=Richardson tx 75081; ss-number=222-22-2222; sip-url=//gateway21.home.com; billing-dn=972-813-5111; dn1=972-813-5111; 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;
Note
Operating
This section covers the operational features of the Cisco BTS 10200 Softswitch H.323 implementation, including billing, measurements, events and alarms, and announcements.
Billing
This section describes several billing features applicable to H.323, including:
•
•
•
•
•
Note
Identifying Call Legs As Video-Enabled
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
Billing Data Generation for Video Calls
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:
•
•
The following calling conditions do not have any effect on the billing record generated by the Cisco BTS 10200 Softswitch:
•
•
Billing Records for Calls to/from Cisco CallManager
For calls involving a connection between the Cisco BTS 10200 Softswitch and Cisco CallManager, the Cisco BTS 10200 Softswitch creates the completed call billing record before the voice path is fully established. (For calls not involving Cisco CallManager, the Cisco BTS 10200 Softswitch creates call billing records after the voice path is fully established.)
Updated Billing Field Descriptions
Descriptions of the following fields were updated in the Cisco BTS 10200 Softswitch Billing Guide. See the updated descriptions for these (and all other billing fields) in that document.
•
•
•
•
•
•
Measurements
There are a number of traffic measurements applicable to H.323. For detailed information regarding billing fields, see the "Traffic Measurements" section in the Cisco BTS 10200 Softswitch Operations and Maintenance Guide.
Events and Alarms
There are a number of events and alarms applicable to H.323. For a detailed list and description of these data fields, see the Cisco BTS 10200 Softswitch Troubleshooting Guide.
Announcements
The Cisco BTS 10200 Softswitch supports a full range of announcements; however, there are no announcements specific to the H.323 protocol implementation.
Note
Link Failure Recovery Process
This section explains what to do if the active signaling link on the Cisco BTS 10200 Softswitch goes down. The procedures in this section are based on the configuration tasks described in the "Prerequisites for H.323 Networks" section.
Dual Links for H.323 Signaling Transport
There are two signaling links on each CA. During normal operation, one of these links on the active CA is active and used for transporting H.323 (and other VoIP) signaling. The other link is standby. If the active signaling link goes down, the H.323 process restarts, and reestablishes communications over a good link (either of the signaling links on the CA). Typically, the link that comes up active is not the same link that originally went down. For example, if the system was originally transmitting H.323 traffic through IF1 (IP address 10.89.225.17), after the restart it might transmit through IF2 (IP address 10.89.226.17).
Automatic Recovery Process When GWs are Registered to a GK
When the Cisco BTS 10200 Softswitch H.323 GWs are registered to a GK, typically, no operator intervention is required. The link failure and recovery process occurs as follows.
1.
2.
3.
Automatic Recovery Process When No GK Is Used (Direct Routing)
If a GK is not used, direct routing has been set up on each peer H.323 GW that communicates with the Cisco BTS 10200 Softswitch. This should have been done when the network was set up, as described in the "Setting Up Direct Routing on the Peer H.323 GW" section.
Link Failure and Recovery Scenario
The link failure and recovery scenario is as follows:
1.
2.
3.
Manual Intervention for Process Recovery (Optional)
When not connected to a GK, the H.323 GW, cannot automatically update its IP address data; therefore, the 3-second call setup delays will continue. If you want to restore normal call setup times (optional) perform the following steps:
Step 1
prica37# nslookup h3a-SYS37CA146.ipclab.cisco.comTypical system response:Server: lion.ipclab.cisco.com Address: 10.89.224.1Name: h3a-SYS37CA146.ipclab.cisco.com Addresses: 10.89.226.17, 10.89.225.17
Tip
Step 2
status h323-gw id=GW37_Central_4A typical system response is shown below.
Note
status h323-gw id=TB37_Central_4ADMIN STATE -> ADMIN_INSH3A PROCESS NUMBER -> 40H3A PROCESS NAME -> H3A4ENDPOINT ID -> 6333EC4400000005ACTIVE CALLS -> 0RAS STATE -> CCH323_RAS_STATE_IDLERAS PORT -> 57781IP ADDRESS -> 10.89.225.17REGISTERED GATEKEEPER ID -> H5-GKPRIMARY GATEKEEPER ID -> H5-GKPRIMARY GATEKEEPER PORT -> 1719PRIMARY GATEKEEPER IP -> 10.89.227.80H323 VERSION -> 4TIME TO LIVE -> 60NUM ALT GATEKEEPERS -> 0ALT GATEKEEPER PERMANENT -> TRUETHRESHOLD ENABLED -> FALSEOUT OF RESOURCES -> FALSEALT GATEKEEPER LIST ->Step 3
Step 4
Step 5
Step 6
Troubleshooting
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 -> 8991ADMIN STATE -> ADMIN_OOSOPER STATE -> Trunk group in-serviceREASON -> ADM executed successfulRESULT -> ADM configure result in successSolution
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_OOSH3A PROCESS NUMBER -> 32H3A PROCESS NAME -> H3A3ENDPOINT ID ->ACTIVE CALLS -> 0RAS STATE -> CCH323_RAS_STATE_NONERAS PORT -> 0IP ADDRESS ->REGISTERED GATEKEEPER ID -> NOT REGISTEREDPRIMARY GATEKEEPER ID ->PRIMARY GATEKEEPER PORT -> 0PRIMARY GATEKEEPER IP ->H323 VERSION -> 4TIME TO LIVE -> 0NUM ALT GATEKEEPERS -> 0ALT GATEKEEPER PERMANENT -> FALSETHRESHOLD ENABLED -> FALSEOUT OF RESOURCES -> FALSEALT 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 successfulH323GW ID -> CHINA_3INITIAL STATE -> ADMIN_OOSREQUEST STATE -> ADMIN_INSRESULT STATE -> ADMIN_INSFAIL REASON -> ADM found no failureREASON -> ADM executed successfulRESULT -> ADM configure result in successH.323 Gateway Fails to Register With GK (Invalid Alias)
When the H.323 gateway registers with a GK, sometimes an alias list is provided to the GK 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 GK but the GK 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 . . ] " }"•
Local gatekeeper that gateway is trying to register with configured as follows:
–
–
–
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)
–
–
–
–
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:
–
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 stateH225_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 GK, 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_INSH3A PROCESS NUMBER -> 32H3A PROCESS NAME -> H3A3ENDPOINT ID ->ACTIVE CALLS -> 0RAS STATE -> CCH323_RAS_STATE_GRQRAS PORT -> 59723IP ADDRESS -> 10.89.225.165REGISTERED GATEKEEPER ID -> NOT REGISTEREDPRIMARY GATEKEEPER ID -> China-GKPRIMARY GATEKEEPER PORT -> 1719PRIMARY GATEKEEPER IP -> 10.89.227.198H323 VERSION -> 4TIME TO LIVE -> 0NUM ALT GATEKEEPERS -> 0ALT GATEKEEPER PERMANENT -> TRUETHRESHOLD ENABLED -> FALSEOUT OF RESOURCES -> FALSEALT GATEKEEPER LIST -> CLI>status h323_gw id=CHINA_3;This shows that the H.323 gateway is in service, but it is not registered with a GK. 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 . . ] " }"GK is down (no alternate GK, or alternate is also down) --- this can be verified by trace logs as a timeout would occur (waiting for GCF or GRJ) after the H.323 GRQ has been sent.
Stable Calls Are Dropped When CA Switches Over
If Annex E functionality is provisioned on the Cisco BTS 10200 Softswitch, but stable calls are being dropped when the H.323 process restarts or CA switches over, check to see whether configuration is correctly registered with the GK:
Step 1
Step 2
Step 3
aaa.bbb.ccc.ddd
1234
eee.fff.ggg.hhh
12345
City GK
VOIP-GW
E
iii.jjj.kkk.lll
5678
ppp.qqq.rrr.sss
56789
City GK
VOIP-GW
E
Step 4
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=139 " [h3a_alarms.c:281]Solution
The routing problem could be in either the GK or the Cisco BTS 10200 Softswitch. Check the GK against the dialedDigits pattern in the ARQ, example:
destinationInfo "[+ . H3A3 . . ] " {"[+ . H3A3 . . ] " dialedDigits : "9991231234""[+ . H3A3 . . ] " }"There are multiple ways that a GK could determine the destCallSignalAddress to send back in a ACF:
–
–
–
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 the GK that the outgoing H.323 gateway is registered with and determine the routing for called number. Gatekeeper could be configured to route based on several configurations:
–
–
–
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=8991CALL_AGENT_ID=CA146TG_TYPE=H323SOFTSW_TSAP_ADDR=10.89.227.119;TG_PROFILE_ID=CHINASTATUS=INSDIRECTION=BOTHSEL_POLICY=ASCGLARE=SLAVEALT_ROUTE_ON_CONG=NSIGNAL_PORTED_NUMBER=NDIAL_PLAN_ID=cdp1DEL_DIGITS=0OPER_STATUS=NFSolution
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=8991CALL_AGENT_ID=CA146TG_TYPE=H323TG_PROFILE_ID=CHINASTATUS=INSDIRECTION=BOTHSEL_POLICY=ASCGLARE=SLAVEALT_ROUTE_ON_CONG=NSIGNAL_PORTED_NUMBER=NDIAL_PLAN_ID=cdp1DEL_DIGITS=0OPER_STATUS=NFQOS_ID=china_qos1TRAFFIC_TYPE=LOCALH323_GW_ID=CHINA_3CAUSE_CODE_MAP_ID=H323_CHINAANI_BASED_ROUTING=NNO_ANSWER_TMR=185Since 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;References
This section provides reference material applicable to the H.323 implementation.
Cisco IOS - Cisco CallManager - MGCP Interoperability Data
Table 6 through Table 12 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 6 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 7 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 8 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 9 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 10 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 11 lists interoperability support for the consultative call transfer (consultative CT) feature without codec speedup:
Note
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 12 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
Related Documents
Industry Standards
ITU-T Recommendation H.323
Packet-based multimedia communications systems, Draft v4 (11/2000)
H.323 Provisioning, Operating, and Troubleshooting Guide for the Cisco BTS 10200 Softswitch, Release 4.5.1
© 2006 Cisco Systems, Inc. All rights reserved.
Feedback