 Feedback
|
Table Of Contents
Cisco BTS 10200 Softswitch H.323 Video, Routing, and Transparency Features for Release 4.2
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
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
Additional Information for Provisioning ANI Screening and Routing
ANI Screening vs. ANI-Based Routing
Identification of H.323 Terminal Property Based On ANI
H.323 Protocol Transparency Functions
Additional Advanced H.323 Features
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
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
Appendix A: Interoperability Data
Appendix B: Billing Data Generation and Data Fields
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
•
•
•
•
•
•
•
These enhancements can be applied to managed H.323 networks that contain the Cisco BTS 10200 Softswitch and the following network element types:
Note
•
•
•
•
•
•
•
Feature History for Cisco BTS 10200 Softswitch H.323 Video, Routing, and Transparency Features for Release 4.2
Contents
•
•
•
Note
- 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:
•
•
Note
The H.323-based video phones must have the following capabilities:
•
•
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.
•
–
–
•
–
•
–
•
–
•
–
•
–
The following restrictions and limitations apply to video phone calls connected through the Cisco BTS 10200 Softswitch:
•
•
•
•
•
The following limitations apply to Cisco BTS 10200 Softswitch support for route advance, reattempt, and redirection on H.323-based call legs:
•
•
•
•
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
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
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
The following details are covered in this section:
•
•
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:
•
–
–
–
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:
•
•
Note
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
•
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:
•
Note
•
–
–
–
–
•
•
•
•
•
No service provider provisioning steps are required for this function.•
–
–
–
Additional H.323-Related Feature Enhancements
This release of the Cisco BTS 10200 Softswitch adds the following provisionable H.323 enhancements:
•
•
•
•
•
–
–
•
•
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:
•
•
•
•
•
•
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 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 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 parameters (or both) for the outbound call leg.
This section covers the following topics:
•
•
•
•
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.
2.
3.
4.
Tip
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.
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
Table 2 Summary of H.323 Outbound Routing Data Options
Data Sent
or outbound
TRUNK-GRP table(Figure 3)
-
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)
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
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 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:
•
•
•
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:
•
•
•
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:
•
•
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):
•
•
See Figure 5, Part "B".
Figure 5 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 control the use of circuit info parameters in the outgoing ARQ/SETUP messages. When set to Y (yes) the system sends the circuit information.
TipStep 2
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
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):
•
•
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
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:
•
•
•
•
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:
•
•
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 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
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
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
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
AUTO (default)—The system automatically determines whether to enable or disable H.245 tunneling:
•
•
Note
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
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
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
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
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 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
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
#################################################################### 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 providerADD 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:portADD 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-ADDRADD 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 -> 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 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 . . ] " }"•
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 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_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 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=139 " [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:
–
–
–
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:
–
–
–
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;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 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 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 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 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 8 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 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
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
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:
•
•
The following calling conditions do not have any effect on the billing record generated by the Cisco BTS 10200 Softswitch:
•
•
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.
Technical Assistance
Copyright © 2004 Cisco Systems, Inc. All rights reserved.
Cisco BTS 10200 Softswitch H.323 Video, Routing, and Transparency Features for Release 4.2
