Guest

Cisco PGW 2200 Softswitch

Release Notes for Cisco H.323 Signaling Interface Release 4.3 and Related Patches

  • Viewing Options

  • PDF (424.4 KB)
  • Feedback
Release Notes for Cisco H.323 Signaling Interface Release 4.3 and Related Patches

Table Of Contents

Release Notes for Cisco H.323 Signaling Interface Release 4.3 and Related Patches

Contents

Platform Support

Hardware

Software

New Features

Related Documentation

Before Installation

After Installation

General Purpose Documents

Installation Requirements

Installation Checklist

Installing the Cisco HSI

Installing HSI Software Patches

Manual Patch Installation

Patch Removal

HSI 4.3(2) Patch 16 Information

Caveats Resolved by Cisco HSI 4.3(2) Patch 16

HSI 4.3(2) Patch 14 Information

Caveats Resolved by Cisco HSI 4.3(2) Patch 14

HSI 4.3 Patch 13 Information

Caveats Resolved by Cisco HSI 4.3 Patch 13

HSI 4.3 Patch 12 Information

Caveats Resolved by Cisco HSI 4.3 Patch 12

HSI 4.3 Patch 11 Information

Caveats Resolved by Cisco HSI 4.3 Patch 11

HSI 4.3 Patch 10 Information

New Features of HSI 4.3 Patch 10

Call Hold/Resume Codec Mismatch Support

Setting the TCP Keepalive Interval

Caveats Resolved by Cisco HSI 4.3 Patch 10

HSI 4.3 Patch 9 Information

New Features of HSI 4.3 Patch 9

Bearer Cap Mapping for H.323 to PSTN Calls

Call Preservation for Active-Connected Calls with CallManager

RFC 3555-G7231 Format Support in SDP

RFC 3555-G729 Format Support in SDP

Caveats Resolved by Cisco HSI 4.3 Patch 9

HSI 4.3 Patch 8 Information

New Features of HSI 4.3 Patch 8

HSI Support for Active/Connected Call Preservation with Cisco CallManager

Customize a H.225 Release Cause Code for the MML Command stp-callproc

Caveats Resolved by Cisco HSI 4.3 Patch 8

HSI 4.3 Patch 7 Information

New Features of HSI 4.3 Patch 7

HSI 4.3 Patch 7 Runs on Sun Opteron Platform

HSI Overload Mechanism for Multiple Processors

Caveats Resolved by Cisco HSI 4.3 Patch 7

HSI 4.3 Patch 6 Information

Caveats Resolved by Cisco HSI 4.3 Patch 6

HSI 4.3 Patch 5 Information

New Feature in HSI 4.3 Patch 5

Per Call Support for the G.723.1 Codec

Caveats Resolved by Cisco HSI 4.3 Patch 5

HSI 4.3 Patch 4 Information

New Features in HSI 4.3 Patch 4

Support for New Sys_Config_Dynamic Parameter—enableAnnexEinRRQ

Support New H323_SYS Parameter—maxDescs

Caveats Resolved by Cisco HSI 4.3 Patch 4

HSI 4.3 Patch 3 Information

New Features in HSI 4.3 Patch 3

Support for New Sys_Config_Dynamic Parameter—UsePayloadTypeMapping

Caveats Resolved by Cisco HSI 4.3 Patch 3

HSI 4.3 Patch 2 Information

New Features in HSI 4.3 Patch 2

Support for TOS/QoS Setting in IP Headers

HSI Support for New Cause Codes Sent Through a PGW 2200 EISUP Interface

Caveats Resolved by Cisco HSI 4.3 Patch 2

HSI 4.3 Patch 1 Information

Caveats Resolved by Cisco HSI 4.3 Patch 1

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco H.323 Signaling Interface Release 4.3 and Related Patches


Revised: Sep 30, 2013, OL-11617-16

The Cisco H.323 Signaling Interface (HSI) interoperates with the Cisco PSTN Gateway 2200 (PGW 2200) to enable calls between the Public Switched Telephone Network (PSTN) and the H.323 network. The HSI provides:

Translation of signaling protocols for establishing, controlling, and releasing calls

Administration of network parameters and protocol capabilities

System and call-related statistics

Fault reporting

Overload management

Event logging

Simple Network Management Protocol (SNMP) interface

The Cisco HSI 4.3 release supports H.323 Version 4.

Contents

Platform Support

New Features

Related Documentation

Installation Requirements

HSI 4.3(2) Patch 16 Information

HSI 4.3(2) Patch 14 Information

HSI 4.3 Patch 13 Information

HSI 4.3 Patch 12 Information

HSI 4.3 Patch 11 Information

HSI 4.3 Patch 10 Information

HSI 4.3 Patch 9 Information

HSI 4.3 Patch 8 Information

HSI 4.3 Patch 7 Information

HSI 4.3 Patch 6 Information

HSI 4.3 Patch 5 Information

HSI 4.3 Patch 4 Information

HSI 4.3 Patch 3 Information

HSI 4.3 Patch 2 Information

HSI 4.3 Patch 1 Information

Obtaining Documentation and Submitting a Service Request

Platform Support

Hardware

The Cisco HSI is developed to run on a Sun Netra 210, a Sun Netra 240, or a Sun Fire V210 platform.

Software

The Cisco HSI 4.3(2) runs on the Solaris 10 operating system.

New Features

Cisco HSI Release 4.3(2) introduces support for the following features:

H.323 Annex M.1 Support—Enables the interoperability of enhanced services with H.323 networks that support the H.323Annex M.1 protocol (for example, Cisco Call Manager). The tunneled QSIG content enabled by this feature supports interoperability not only with QSIG PBXs but also with SIP and other protocols (such as DPNSS and SS7), in conjunction with the Cisco PGW 2200 Softswitch. Enhanced service interoperability includes services such as call transfer/divert, call back services, and call completion. In addition, this feature enables full, end-to-end Route Optimization/Path Replacement for mixed Cisco Call Manager and DPNSS/QSIG PBX networks. Other services, such as message-waiting indication and caller ID services are also available.

H.323 Alternate Endpoint Routing Capability—Enables greater call-completion rates by allowing the HSI to attempt connection to multiple H.323 gateway destinations. An external route server can interface with H.323 gatekeepers by using the simple but powerful GKTMP interface, which provides a selection of destinations to which the HSI can attempt to connect.

Enhanced Performance—The Cisco HSI Release 4.3 provides improved performance. HSI 4.3 supports up to 10,000 simultaneous calls per HSI, at rates several times faster than previous releases.


Note To support N+1 redundancy, you must use at least two HSIs.


Sun Solaris 10—Cisco HSI 4.3 runs on the Sun Solaris 10 operating system.

Related Documentation

Before Installation

Before you install the Cisco HSI software, consult the Cisco H.323 Signaling Interface User Guide.

After Installation

After you install the Cisco HSI software, consult the following related documentation for information on configuring and provisioning your system:

Cisco H.323 Signaling Interface User Guide

The Provisioning Guide for your solution

General Purpose Documents

The Gateway Installation Guide for your solution

Cisco PGW 2200 Softswitch Release 9.7 Software Installation and Configuration Guide

Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide

Cisco PGW 2200 Softswitch Release 9 Provisioning Guide

Installation Requirements

Installation Checklist

Before you attempt to install the HSI application software, you must obtain the following information:

Cisco H.323 Signaling Interface base directory path

Base directory path

Cisco H.323 User name and group name

Gatekeeper IP address and port number

Gateway prefix

Terminal alias

Gatekeeper ID

EISUP host port number

VSC1 name and port number

Installation node ID

Hardware platform description

Installation location

Your company's internal support and Cisco support contact information

Installing the Cisco HSI

For installation instructions refer to the Cisco H.323 Signaling Interface User Guide. See Chapter 2: Installing and Configuring Cisco HSI Software.

Installing HSI Software Patches

When you install an HSI software patch, the included updated binary, provisioning, library, and script files will be updated in the following directories depending on the type of file being delivered:

/opt/GoldWing/currentPM/bin binaries

/opt/GoldWing/currentPM/etc data files

Before installing a patch, you must shut down the Cisco HSI application, as the affected programs are part of the running system. To ensure that the HSI application has been shutdown, execute the following command:

# /etc/init.d/CiscoGW stop 

Manual Patch Installation

Complete the following procedure to install a software patch:


Step 1 Change user to root.

Step 2 Use the following command to create a patch directory (if one does not exist) on the HSI machine:

mkdir /export/PATCHES 

Step 3 Transfer the hsi-4_3_p<n>.tar.Z file into the new directory.


Note <n> represents the patch number that you are installing.


Step 4 To create a 4.3_P<n> directory, execute the following commands:

uncompress hsi-4_3_p<n>.tar.Z
tar xvf hsi-4_3_p<n>.tar.Z

Step 5 Ensure the HSI application is shutdown and all previous patches are uninstalled.

Step 6 Use the following commands to change to the 4.3_P<n> patch directory and install the patch:

cd ./4.3_P<n> 
./install_patch.sh 

Step 7 Use the following command to restart the HSI application:

/etc/init.d/CiscoGW start 
 
   

Patch Removal

Complete the following procedure to remove a software patch:


Step 1 Change user to root.

Step 2 Issue the following command to shutdown the HSI application:

/etc/init.d/CiscoGW stop 

Step 3 Use the following commands to change directories and uninstall the patch:

cd /export/PATCHES/4.3_P<n> 
./uninstall_patch.sh 

Note <n> represents the patch number that you are removing.


Step 4 Issue the following command to restart the HSI application:

/etc/init.d/CiscoGW start 

HSI 4.3(2) Patch 16 Information

This section includes information on:

Caveats Resolved by Cisco HSI 4.3(2) Patch 16

Caveats Resolved by Cisco HSI 4.3(2) Patch 16

The following anomaly identified in the operation of the Cisco HSI is resolved by HSI 4.3(2) Patch 16:


Note Version 4.3(2) Patch 16 in CDETS is mentioned as 4.3(2.16).


Identifier
Version
Severity
Description

CSCug64541

4.3

2

HSI issue with asymmetric codec.


Symptoms: HSI has issue with asymmetric codec handling when HSI is elected as Master during MSD procedure.

Resolution: None.

Identifier
Version
Severity
Description

CSCue65938

4.3

2

PGW P18 Opteron: SDP version check.


Symptoms: Consulting transfer failed.

Resolution: None.

HSI 4.3(2) Patch 14 Information

This section includes information on:

Caveats Resolved by Cisco HSI 4.3(2) Patch 14

Caveats Resolved by Cisco HSI 4.3(2) Patch 14

The following anomaly identified in the operation of the Cisco HSI is resolved by HSI 4.3(2) Patch 14:


Note Version 4.3(2) Patch 14 in CDETS is mentioned as 4.3(2.14).


Identifier
Version
Severity
Description

CSCte01439

4.3

4

rasSendRequestMessage() caused HSI core dump.


Symptoms: In certain scenarios, the rasSendRequestMessage() function triggered a core dump of the process.

Resolution: The HSI software is modified to eliminate the problem.

Identifier
Version
Severity
Description

CSCtk18786

4.3

4

Status update of EISUP links causes HSI to core on shutdown test.


Symptoms: When performing a switchover test on a redundant HSI pair by shutting down the active HSI to force the switchover, the HSI core dump happens.

Resolution: The HSI software is modified to eliminate the problem.

Identifier
Version
Severity
Description

CSCts10435

4.3

2

G722 codec does not work on HSI.


Symptoms: HSI is not able to understand G722 and gives out an error: "Channel information not found: 9 = g722."

Resolution: The HSI software is modified to eliminate the problem.

Identifier
Version
Severity
Description

CSCtx68491

4.3

3

HSI failed to build OLC (t38) due to incompatible capability.


Symptoms: When HSI uses the remote data capability received in TCS to build OLC, if HSI does not find "receiveAndTransmitDataApplicationCapability", it fails to build OLC.

Resolution: The HSI software is modified to eliminate the problem.

HSI 4.3 Patch 13 Information

This section includes information on:

Caveats Resolved by Cisco HSI 4.3 Patch 13

Caveats Resolved by Cisco HSI 4.3 Patch 13

The following anomaly identified in the operation of the Cisco HSI is resolved by HSI 4.3 Patch 13:

Identifier
Version
Severity
Description

CSCte75424

4.3

4

GWmain core dump happened on 4.3(2) P11.


Symptoms: GWmain core dump happened on 4.3(2)P11.

Resolution: The HSI software is modified to eliminate the problem.

HSI 4.3 Patch 12 Information

This section includes information on:

Caveats Resolved by Cisco HSI 4.3 Patch 12

Caveats Resolved by Cisco HSI 4.3 Patch 12

The following anomaly identified in the operation of the Cisco HSI is resolved by HSI 4.3 Patch 12:

Identifier
Version
Severity
Description

CSCte80784

4.3

3

HSI crashes on receipt of an H323 SETUP message that includes a corrupted element.


Symptoms: An HSI failed when it received an H.323 SETUP message in which an H.450 element was corrupted.

Resolution: The HSI software is modified to sucessfully decode the H.450 element of a SETUP message that had been a problem.

HSI 4.3 Patch 11 Information

This section includes information on:

Caveats Resolved by Cisco HSI 4.3 Patch 11

Caveats Resolved by Cisco HSI 4.3 Patch 11

The following anomaly identified in the operation of the Cisco HSI is resolved by HSI 4.3 Patch 11:

Identifier
Version
Severity
Description

CSCtb31835

4.3

3

The HSI experienced an overload level 3 condition with call gapping.


Symptoms: The HSI experienced an overload level 3 status with call gapping.

Resolution: The HSI software is modified to eliminate the problem.

Identifier
Version
Severity
Description

CSCtc09929

4.3

3

An HSI experienced high demand on the CPU due to an SNMP process named hostagt.


Symptoms: An HSI encountered high CPU usage due to the activation of the SNMP process hostagt.

Resolution: The HSI software is modified to eliminate the problem.

Identifier
Version
Severity
Description

CSCtd60437

4.3

3

In response to an H.323 thread load, an HSI reached an with MCL 3 overload status with call gapping.


Symptoms: An HSI reached an MCL 3 overload status, with call gapping, due to an H.323 thread load.

Resolution: The HSI software is modified to eliminate the problem.

HSI 4.3 Patch 10 Information

This section includes information on:

New Features of HSI 4.3 Patch 10

Call Hold/Resume Codec Mismatch Support

Setting the TCP Keepalive Interval

Caveats Resolved by Cisco HSI 4.3 Patch 10

New Features of HSI 4.3 Patch 10

Cisco HSI 4.3 Patch 10 introduces the following new features.

Call Hold/Resume Codec Mismatch Support

Before this patch, when a Cisco HSI (operating as a slave) encountered a mismatched codec in a call hold/resume condition, it failed to open a logical channel with a matching codec.

Cisco HSI 4.3 Patch 10 enables the HSI to close and reopen a logical channel so that the codecs match at both ends of the logical channel.

Setting the TCP Keepalive Interval

If a network firewall was deployed between a Cisco HSI and another H.323 gateway or endpoint, the firewall could set the maximum idle duration of a TCP connection to a value that is less than the tcp_keepalive_interval of the operating system. This condition tears down a long-duration call when its connected duration reaches the tcp_keepalive_interval of the operating system. In this case, you must decrease the tcp_keepalive_interval of the operating system to make it less than the firewall limitation.

To check the current tcp_keepalive_interval of the Solaris operating system, issue the following command in shell:

#/usr/sbin/ndd -get /dev/tcp tcp_keepalive_interval 
 
   

To modify the tcp_keepalive_interval of the operating system, you must configure the new Cisco HSI SYS_CONFIG_STATIC parameter tcp_keepalive_interval.

For example, if the tcp_keepalive_interval on the Solaris operating system is 2 hours and the firewall sets the idle duration for a TCP connection to a maximum of 1 hour, you must alter the tcp_keepalive_interval for the operating system. In this case, you must set the tcp_keepalive_interval to a value less than 1 hour (perhaps 50 minutes). To do so, complete the following steps:


Step 1 Start a new MML provisioning session.

gw mml> prov-sta::....
 
   

Step 2 Provision the tcp_keepalaive_interval parameter.

gw mml> prov-add::name=SYS_CONFIG_STATIC, tcp_keepalive_interval=3000000 //3000000 
milliseconds = 3000 seconds = 50 minutes
 
   

Step 3 Copy the newly provisioned parameter to the configuration.

gw mml> prov-cpy
 
   

Step 4 Restart the Cisco HSI to make the newly provisioned static parameter valid.

gw mml> restart-softw
 
   

Caveats Resolved by Cisco HSI 4.3 Patch 10

The following anomaly identified in the operation of the Cisco HSI is resolved by HSI 4.3 Patch 10:

Identifier
Version
Severity
Description

CSCsx75216

4.3

3

A Cisco HSI did not retain in-service status for an EISUP path when the Cisco PGW 2200 Softswitch to which it was connected was switched from standalone to master mode.


Symptoms: A Cisco HSI was connected to a Cisco PGW 2200 Softswitch, which was in standalone mode. When the Cisco PGW 2200 Softswitch was switched from standalone mode to master mode, the HSI indicated that the EISUP path was out of service (OOS).

Resolution: The HSI software is modified to correctly indicate that the EISUP path remains in service (IS) under similar circumstances.

HSI 4.3 Patch 9 Information

This section includes information on:

New Features of HSI 4.3 Patch 9

Bearer Cap Mapping for H.323 to PSTN Calls

Call Preservation for Active-Connected Calls with CallManager

RFC 3555-G7231 Format Support in SDP

RFC 3555-G729 Format Support in SDP

Caveats Resolved by Cisco HSI 4.3 Patch 9

New Features of HSI 4.3 Patch 9

Cisco HSI 4.3 Patch introduces the following new features.

Bearer Cap Mapping for H.323 to PSTN Calls

For certain networks, the Cisco HSI must map the bearerCap IE into the ISUP user service information parameter as well as the TMR parameter. With Cisco HSI 4.3 Patch 9, you can enable this mapping as an option.

To enable the feature, configure the parameter MapBearerCapToUsi to any text value (for example, "enabled"):

gw mml> prov-add:name=sys_config_dynamic, MapBearerCapToUsi=enabled
 
   

To disable the feature, delete the parameter MapBearerCapToUsi or set it to blank (""):

gw mml> prov-dlt:name=sys_config_dynamic, MapBearerCapToUsi

Call Preservation for Active-Connected Calls with CallManager

Cisco HSI 4.3 Patch 9 adds the parameter H323CallPreserve, which enables the HSI to preserve active-connected calls when the Cisco CallManager (CCM) is restarted or when the CCM is handling a call and the IP Phone call-leg link becomes OOS.

When you enable the H323CallPreserve parameter and CCM closes the H.323 TCP connection without sending an H.323 release message to the HSI, the HSI does not send a release message to the Cisco PGW 2200 Softswitch for active calls. This action prevents losing a connected call even if the CCM fails.

To enable the preservation of H.323 calls, set the parameter H323CallPreserve to any none-null string.

To disable the preservation of H.323 calls, delete the parameter H323CallPreserve from the configuration or set H323CallPreserve as a null string.

The following sample MML commands show how to enable H.323 call preservation on the Cisco HSI:

gw mml> prov-sta::...
gw mml> prov-add::name=SYS_CONFIG_STATIC, H323CallPreserve=enable
gw mml> prov-cpy
gw mml> restart-softw

RFC 3555-G7231 Format Support in SDP

RFC 3555 defines "G723/8000" as the encoding name of the attribute "a=rtpmap:" in SDP, and defines the G723 "annexa" parameter of the attribute "a=fmtp:" in SDP.

For example:

a=rtpmap:100 G723/8000

a=fmtp:100 annexa=yes

Before the introduction of the dynamic system configuration parameter, UseRFC3555G723, in Cisco HSI 4.3 Patch 9, the HSI did not recognize the encoding name "G723/8000" and the parameter "annexa."

This enhancement to the HSI software supports the RFC 3555 G7231 format in SDP.

The following example shows how the enhancement is implemented in the HSI configuration (assuming that you have 6 codecs configured already. The new codecs will start from 7):

* SYS_CONFIG_STATIC.UseRFC3555G723 = true

* SYS_CONFIG_DYNAMIC.UsePayloadTypeMapping = true

* h245.caps.table[7].audio.g7231-dyn.maxAudioFrames = 1

* h245.caps.table[7].audio.g7231-dyn.silencesuppression = 0

* h245.caps.table[7].entryNo = 72311

* h245.chan[7].audio.g7231-dyn.maxAudioFrames = 1

* h245.chan[7].audio.g7231-dyn.silencesuppression = 0

* h245.chan[7].name = g7231-dyn

* h245.modes[7].audio.g7231-dyn = NULL

* h245.modes[7].name = g7231-dyn

* h245.caps.table[8].audio.g7231a-dyn.maxAudioFrames = 1

* h245.caps.table[8].audio.g7231a-dyn.silencesuppression = 1

* h245.caps.table[8].entryNo = 72312

* h245.chan[8].audio.g7231a-dyn.maxAudioFrames = 1

* h245.chan[8].audio.g7231a-dyn.silencesuppression = 1

* h245.chan[8].name = g7231a-dyn

* h245.modes[8].audio.g7231a-dyn = NULL

* h245.modes[8].name = g7231a-dyn

To disable the feature, delete the SYS_CONFIG_STATIC.UseRFC3555G723 parameter or set it to blank (""). The following sample MML command disables support for RFC 3555-G723:

mml> prov-dlt:name=SYS_CONFIG_STATIC, UseRFC3555G723

Note Before Cisco HSI 4.3 Patch 9, the Cisco HSI always implemented the static payload type 4 in SDP as G7231 without annexa. If you disable this feature, the HSI performs as it did in previous versions on static payload type 4 in SDP. If you enable this feature, the HSI implements the static payload type 4 in SDP as G7231Annexa if no annexa parameter is set for payload type 4 in SDP according to RFC 3555.


RFC 3555-G729 Format Support in SDP

RFC 3555 defines "G729/8000" as the encoding name of the attribute "a=rtpmap:" in SDP and defines the G729 parameter "annexb" of the attribute "a=fmtp:" in SDP.

For example:

a=rtpmap:101 G729/8000

a=fmtp:101 annexb=yes

Previous versions of the Cisco HSI did not recognize the "G729/8000" encoding name and the "annexb" parameter. That is, when the HSI received static payload type 18 (without the annexb parameter) in SDP, the HSI set the codec as G729. This action conflicts with RFC 3555.

According to RFC 3555, if annexb is omitted, the specification "annexb=yes" is implied.

To comply with RFC 3555, the HSI 4.3 Patch 9 software introduces the parameter UseG729bByDefault, which enables you to provision G729 Annex B.

To provision G729b, set the parameter UseG729bByDefault to any string value. The following sample MML command provisions G729b:

prov-add::name=SYS_CONFIG_DYNAMIC,UseG729bByDefault=enable
 
   

Alternatively, to provision G729, you delete the parameter UseG729bByDefault or set the value of the parameter as a null string. The following sample MML command instructs the HSI to provision G729:

prov-dlt::name=SYS_CONFIG_DYNAMIC,UseG729bByDefault
 
   

Caveats Resolved by Cisco HSI 4.3 Patch 9

The following anomalies identified in the operation of the Cisco HSI are resolved by HSI 4.3 Patch 9:

Identifier
Version
Severity
Description

CSCsh70912

4.1

3

The HSI must map the EISUP IAM.USI.Layer1 protocol to the H.323 SETUP.BC.Layer1 protocol.


Symptoms: Previous versions of the Cisco HSI did not map the EISUP IAM.USI.Layer1 protocol to the H.323 SETUP.BC.Layer1 protocol.

Resolution: The HSI software is modified to correctly map the protocols.

Identifier
Version
Severity
Description

CSCsx19824

4.2

enhance-ment

Calls failed when an HSI received EmptyCapabilitySet before channels were established.


Symptoms: Normally, an HSI receives EmptyCapabilitySet after two logical channels have been created. The HSI could not process the abnormal call scenario.

Resolution: The HSI is modified to properly process this anomalous call condition.

Identifier
Version
Severity
Description

CSCsx26094

4.3

enhance-ment

Occasionally an HSI displayed the output of LMserver process for licensing on an MML command console.


Symptoms: Rather than properly sending LMserver process output to the correct log file, the HSI displayed output on an MML console session.

Resolution: The HSI software is modified to redirect the output of the LMserver process into the file /opt/GoldWing/currentPM/var/log/LMserver*.log.

Identifier
Version
Severity
Description

CSCsr30408

4.2, 4.3

3

In some cases, an HSI did not correctly increase the counter FC_INC_CALL_SUCC_TOT.


Symptoms: In certain call conditions, the HSI did not increase the Q.931 counter correctly.

Resolution: The HSI software is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsy13909

4.3

enhance-ment

The HSI should support use of the parameter DynamicPacketizationSupported for endpoints that use the codecs g729AnnexA and g729wAnnexB.


Symptoms: Extend support of the parameter DynamicPacketizationSupported on the HSI for endpoints that use the codecs g729AnnexA and g729wAnnexB.

Resolution: The HSI software now allows users to set the parameter DynamicPacketizationSupported so that the HSI can interoperate with endpoints that specify the codecs g729AnnexA and g729wAnnexB.

Identifier
Version
Severity
Description

CSCsy70931

4.3

enhance-ment

The HSI must accept the attribute "a=rtpmap:" with encoding parameters in SDP.


Symptoms: The RFC standard defines the attribute "a=rtpmap:" in SDP in the following format:

"a=rtpmap:<payload type> <encoding name>/<clock rate> [/<encoding parameters>]"

In previous versions, the HSI ignored the attribute "a=rtpmap:" with encoding parameters in SDP.

Resolution: The HSI software is modified to accept the attribute "a=rtpmap:" with encoding parameters.

Identifier
Version
Severity
Description

CSCsw26472

4.3

enhance-ment

Enable users to provision the HSI to disable T.38 fax capability for RFC 3407 in SDP.


Symptoms: Some SIP servers might not recognize T.38 fax capability for RFC 3407 in SDP. This causes the SIP server to release the call with T.38 fax capability.

Resolution: This patch adds the parameter DisableRFC3407T38 to the HSI software to enable users to suppress the T.38 fax capability in SDP.

To suppress the T.38 fax capability in SDP, set DisableRFC3407T38 to any none-null string.

To not suppress the T.38 fax capability in SDP, delete the parameter DisableRFC3407T38 from the configuration or set DisableRFC3407T38 as a null string.

The following sample MML command shows how to suppress the T.38 fax capability in SDP on a Cisco HSI.

gw mml> prov-add::name=SYS_CONFIG_DYNAMIC,DisableRFC3407T38=true
gw mml> prov-cpy

Identifier
Version
Severity
Description

CSCsx08727

4.2

3

An HSI might not clear all call resources when an H.225 setup message and an H.225 releaseComplete message for a single call arrive simultaneously.


Symptoms: The HSI did not clear call resources as expected when it received H.225 setup and H.255 releaseComplete messages at the same time.

Resolution: The HSI software is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsx09305

4.2, 4.3

3

Under very rare circumstances, when the HSI is started, an EISUP link state goes out of service (OOS).


Symptoms: Due to a very rare process timing issue, an EISUP link can go out of service when the HSI is started.

Resolution: The HSI software is modified to eliminate this problem.

HSI 4.3 Patch 8 Information

This section includes information on:

New Features of HSI 4.3 Patch 8

HSI Support for Active/Connected Call Preservation with Cisco CallManager

Customize H225 Release Cause Code for the MML Command stp-callproc

Caveats Resolved by Cisco HSI 4.3 Patch 8

New Features of HSI 4.3 Patch 8

Cisco HSI 4.3 Patch 8 introduces the following new features.

HSI Support for Active/Connected Call Preservation with Cisco CallManager

This feature implements call preservation for active/connected calls when Cisco CallManager (CCM) is restarted or when the CallManager is handling a IP Phone call leg link that becomes out of service (OOS). A new static parameter, H323CallPreserve, is added to the Cisco HSI software.

When this feature is enabled and CCM closes a H.323 TCP connection without sending an H.323 release message to the Cisco HSI, the Cisco HSI does not send a release message to the Cisco PGW 2200 Softswitch for active calls. This prevents the loss of a connected call even when CCM fails.

To enable H323CallPreserve, set the parameter H323CallPreserve to any none-null string.

To disable H323CallPreserve, delete the parameter H323CallPreserve or set H323CallPreserve as a null string.

The following sample MML commands enable the call preservation feature on the Cisco HSI.

gw mml> prov-sta::srcver=active, dstver=CallPreserve
gw mml> prov-add::name=SYS_CONFIG_STATIC, H323CallPreserve=enable
gw mml> prov-cpy
gw mml> restart-softw
 
   

Note The introduction of the property H225StpCallprocCauseCode is associated with the resolution of the caveat CSCsv82347.


Customize a H.225 Release Cause Code for the MML Command stp-callproc

The new property, H225StpCallprocCauseCode, is added to the Cisco HSI software, which enables you to customize an H.225 release cause code for the MML command stp-callproc.

To enable the customizing of the cause code for the MML command stp-callproc, set the property H225StpCallprocCauseCode to the preferred cause code.

The following sample MML commands show how to set the property H225StpCallprocCauseCode:

mml> prov-sta :: ...
mml> prov-add::name=CCPackage, H225StpCallprocCauseCode=63
mml> prov-cpy
 
   

Note The introduction of the property H225StpCallprocCauseCode is associated with the resolution of the caveat CSCsv11745.


Caveats Resolved by Cisco HSI 4.3 Patch 8

The following anomalies identified in the operation of the Cisco HSI are resolved by HSI 4.3 Patch 8:

Identifier
Version
Severity
Description

CSCsg04881

4.1

3

Incorrect encoding of 64 kbit Bearer Capability IE.


Symptoms: Sometimes, the Cisco HSI incorrectly encoded Bearer Capability IE when the Information Transfer Rate equaled 64 kbit/s.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsv11745

4.3

3

Add the property H225StpCallprocCauseCode to the HSI 4.3 software.


Symptoms: Calls from H.323 devices to the Cisco HSI were disconnected with a disconnect cause "Call Rejected" REL#21. This value could not be changed.

Resolution: Cisco HSI 4.2 Patch 8 includes the H225StpCallprocCauseCode property. See the section "Customize a H.225 Release Cause Code for the MML Command stp-callproc."

Identifier
Version
Severity
Description

CSCsv82347

4.3

3

HSI must support call preservation with Cisco CallManager.


Symptoms: The Cisco HSI should preserve calls when the Cisco CallManager is restarted or when the CallManager that is managing the IP phone call leg link becomes OOS.

Resolution: Cisco HSI 4.3 Patch 8 supports call preservation with Cisco CallManager. See the section "HSI Support for Active/Connected Call Preservation with Cisco CallManager."

HSI 4.3 Patch 7 Information

This section includes information on:

New Features of HSI 4.3 Patch 7

HSI 4.3 Patch 7 Runs on Sun Opteron Platform

HSI Overload Mechanism for Multiple Processors

Caveats Resolved by Cisco HSI 4.3 Patch 7

New Features of HSI 4.3 Patch 7

Cisco HSI 4.3 Patch 7 introduces the following new features.

HSI 4.3 Patch 7 Runs on Sun Opteron Platform

The Cisco HSI 4.3 Patch 7 is the first version of the Cisco HSI to run on the Sun Opteron platform. Previous versions of the Cisco HSI ran on the Sun Sparc platform.

HSI Overload Mechanism for Multiple Processors

Normally, an HSI has two busy threads. The original CPU overload mechanism was based on a calculation for CPU usage on the whole HSI system. On multiple processor platforms, if one of the busy threads becomes overloaded, the whole-system CPU usage may retain a low-usage status. Therefore, on multiple processor platforms, the original mechanism cannot manage the HSI thread level overload sufficiently.

The new overload mechanism monitors the thread statistics of four HSI core threads: an H.323 thread, a call-control thread, an EISUP thread, and an RUDP thread. The HSI uses the busiest thread for the overload calculation.

When a platform has only one processor, the HSI uses the CPU overload level for the entire system.

When the platform has more than one processor, the HSI uses the new overload mechanism.

HSI Overload Mechanism Examples

The following sample rtrv-ne-health and rtrv-overload MML commands show the overload level information that is generated by the whole-system CPU mechanism.

gw mml> rtrv-ne-health
CPU load  : 5% <--- the whole system CPU usage 5%
Disk usage: 11%
Number of connected calls: 200
Number of calls in setup : 8
 
   
 
   
gw mml> rtrv-overload
Overload/Gapping Information
NumCalls : 0 |  CPU : 5% | DiskUsage : 11% <---CPU: 5% : the whole system CPU usage 5%
Status   : Not in Ovld
Overload Configuration
DiskUsageLimit             : 98%
OvldSampleRate             : 3000ms
OvldLevel1Percent          : 20%
OvldLevel1Filter           : NORMAL
OvldLevel1ThreshLowerCpu   : 60% 
OvldLevel1ThreshUpperCpu   : 65% <---when the whole system CPU usage is above 65%, HSI will 
overload

The following sample rtrv-ne-health and rtrv-overload MML commands show the overload level information that is generated by the thread-usage mechanism.

gw mml> rtrv-ne-health
H323 thread load:       6.003399% <----H323 is the busiest thread, usage is 6%
RUDP thread load:       1.013712%
EISUP thread load:      1.000200%
CallControl thread load:        5.000421%
Disk usage: 29%
Number of connected calls: 200
Number of calls in setup : 8
gw mml> rtrv-overload	
Overload/Gapping Information
NumCalls : 0  |  CPU : 6%  | DiskUsage : 11% <---CPU: 6% : the busiest thread usage is 6%
Status   : Not in Ovld
Overload Configuration
DiskUsageLimit             : 98%
OvldSampleRate             : 3000ms
OvldLevel1Percent          : 20%
OvldLevel1Filter           : NORMAL
OvldLevel1ThreshLowerCpu   : 60% 
OvldLevel1ThreshUpperCpu   : 65% <---when the busiest thread usage is above 65%, HSI will 
overload

Caveats Resolved by Cisco HSI 4.3 Patch 7

The following anomalies identified in the operation of the Cisco HSI are resolved by HSI 4.3 Patch 7:

Identifier
Version
Severity
Description

CSCsr30544

4.3

2

When a user attempted to start an MML session after an MML session was run 65536 times, the process froze.


Symptoms: The number of time an MML process could be run was limited.

Resolution: The HSI is modified so that an MML session will not fail.

Identifier
Version
Severity
Description

CSCsr93298

4.3

3

An HSI must select a codec according to the master TCS order.


Symptoms: For a slow start call, the HSI always chooses its OLC codec by its TCS order, whether it is functioning as slave or master. However, the H.323 protocol recommends that a codec be selected by master TCS order.

Resolution: The HSI is modified to select a codec by master TCS order.

Identifier
Version
Severity
Description

CSCsu09628

4.3

3

A fax request sent to the HSI through a SIP connection failed.


Symptoms: The HSI generated duplicated RFC 3407 capability declarations for T.38 fax in SDP.

Resolution: The HSI software is modified to manage Fax requests properly.

Identifier
Version
Severity
Description

CSCsr95565

4.3

2

The fix to the caveat CSCsq16261 in HSI 4.3 Patch 6 breaks a particular call flow.


Symptoms: The fix for CSCsq16261 Patch 6 caused the HSI not to map a Progress Indicator (PI) that was present in an H225 PROGRESS with tunneled QSIG to a FACILITY message as usual because the FACILITY message cannot express this PI. Instead, the HSI mapped the PI to a PROGRESS message. (Refer to H.323 Annex M1).

However, when the HSI received an incoming EISUP ACM message that contained the indication ("ISDN user part not used all the way"), the HSI could not detect whether the in-band information was available. In response to this condition, the HSI 4.3 Patch 6 fix always mapped the PI to a PROGRESS message.

It is preferable to control the mapping by enabling a new configuration property.

Resolution: HSI 4.3 Patch 7 provides the new property EnableTunnelQSIGProgress, which enables you configure the HSI to map the PI to an H.323 QSIG Progress message.

The following sample MML commands show how to enable the new property:

gw mml> prov-sta::....   // start a new provision
gw mml> prov-add::name=SYS_CONFIG_DYNAMIC, EnableTunnelQSIGProgress=enable
gw mml> prov-cpy
 
   

Identifier
Version
Severity
Description

CSCsr30566

4.3

2

An HSI experienced a PM SNMP coredump on a SUN Opteron platform.


Symptoms: The coredump occurred due to thread competition.


Note Because the power and the number of processors on a Sun Opteron platform differs from the power and number of processors on a Sun Sparc platform, the issue could not be reproduced on a Sparc platform.


Resolution: The HSI software is modified so that this problem will not occur for the Cisco HSI running on either a Sun Opteron or Sun Sparc platform.

Identifier
Version
Severity
Description

CSCsu27763

4.3

3

When an HSI was stopped manually, it could not be restarted.


Symptoms: This problem was related to the version of the binary file /opt/GoldWing/currentPM/bin/critagt.

Resolution: HSI 4.3 Patch 7 eliminates this problem.

Identifier
Version
Severity
Description

CSCsr57839

4.2

3

An HSI RUDP thread exhausted CPU resources.


Symptoms: Under very rare circumstances, an RUDP thread exhausted CPU resources on an HSI.

Resolution: The HSI software is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsr65141

4.3

3

An HSI showed no overload when it was actually at the overload 1 condition.


Symptoms: When an HSI changed from overload level 2 to over load level 1, the information returned by the MML rtrv-overload command indicated no overload condition.

Resolution: The HSI software is modified to accurately indicate overload conditions.

Identifier
Version
Severity
Description

CSCsr72935

4.3

3

Sometimes, the HSI overload level changed from level 3 to level 2 but the HSI showed no overload.


Symptoms: An HSI overload level changed from level 3 to level 2; however, the HSI did not identify the overload condition.

Resolution: The HSI software is modified to accurately indicate overload levels.

Identifier
Version
Severity
Description

CSCsr67372

4.3

3

The rtrv-overload command showed no overload, but the rtrv-alms command did show overloading.


Symptoms: Occasionally, the information generated by the MML command rtrv-overload indicated no overload condition but the MML command rtrv-alms indicated that an overload condition did exist.

Resolution: The HSI software has been modified so that the rtrv-overload and rtrv-alms commands do not return contradictory information.

HSI 4.3 Patch 6 Information

This section includes information on:

Caveats Resolved by Cisco HSI 4.3 Patch 6

Caveats Resolved by Cisco HSI 4.3 Patch 6

The following anomalies identified in the operation of the Cisco HSI are resolved by HSI 4.3 Patch 6:

Identifier
Version
Severity
Description

CSCsd84533

4.2

3

The HSI sent the old RTP address/port in the connect message after ECS


Symptoms: The HSI sent an incorrect RPT address/port in a connect message after ECS.

Resolution: Now HSI uses the correct RTP address/port after ECS.

Identifier
Version
Severity
Description

CSCsm43414

4.2

2

File handle is not clear when log level = debug.


Symptoms: When HSI platform.log was rotated, the old file handle was not cleared.

Resolution: The HSI is modified to process the file handle correctly.

Identifier
Version
Severity
Description

CSCsm59911

4.3

3

HSI did not establish an H.245 control channel for an h323-to-h323 connection for an CFNA to PRIQSIG call.


Symptoms: HSI did not pass H.245 address to or from the Cisco PGW 2200 when in hairpin mode and the message was CPG/EISUP or PROGRESS/H225.

Resolution: The HSI is modified to process such a connection correctly.

Identifier
Version
Severity
Description

CSCsm73487

4.2

3

An HSI ignored the re-negotiation MSD procedure


Symptoms: When HSI rejected the MSD status and the peer H.323 element restarted the MSD procedure, the HSI ignored the re-negotiation MSD procedure.

Resolution: The HSI is modified to process a restarted MSD procedure properly.

Identifier
Version
Severity
Description

CSCsm99667

4.2

3

An HSI refreshed only the first value in response to an SNMP bulk get request.


Symptoms: An HSI did not respond correctly to an SNMP get request.

Resolution: The HSI is modified to process an SNMP get request properly.

Identifier
Version
Severity
Description

CSCsq18800

4.3

3

An HSI experienced a core failure when attempting to process a setup request that included extremely large nonStandardControl data.


Symptoms: An HSI could not properly process a setup request with an extremely large nonStandardControl field.

Resolution: The HSI is modified to process the setup request correctly.

Identifier
Version
Severity
Description

CSCsq47384

4.2

2

An EISUP thread could exhaust CPU resources rarely after EISUP OOS.


Symptoms: When an EISUP link goes out of service, an EISUP thread could become unrecoverable.

Resolution: The HSI is modified to respond properly when an EISUP link goes out of service.

Identifier
Version
Severity
Description

CSCsq55198

4.2

3

An HSI gapped incoming H.323 calls and did not release resources cleanly.


Symptoms: When an HSI was in overload status, the HSI gapped calls. Also, the HSI did not release H.323 resources cleanly.

Resolution: The HSI is modified to process such H.323 calls properly.

Identifier
Version
Severity
Description

CSCso33166

4.3

2

The HSI does not release a call in non-RAS mode if it receives a TCP reset.


Symptoms: When the HSI attempted to open a TCP connection to port 1720 of a peer H323 endpoint, the HSI received a TCP Reset request instead of a SYN ACK message. The HSI did not send an EISUP RLC to the Cisco PGW 2200.

Resolution: The HSI is modified to respond to the Reset request correctly.

Identifier
Version
Severity
Description

CSCso16939

4.3

2

The HSI could not support an EISUP path when the SDP content in a message was large and the message size was greater than 1024 bytes.


Symptoms: The HSI could not process an EISUP message larger than 1024 bytes.

Resolution: The HSI is modified to process an EISUP message that is larger than 1024 bytes.

Identifier
Version
Severity
Description

CSCso02261

4.3

Enhance

The HSI did not advertise T.38 Fax capability by way of SDP in an EISUP message to a Cisco PGW 2200.


Symptoms: The HSI did not support RFC 3407 by advertising T.38 Fax capability in SDP.

Resolution: The HSI now advertises T.38 Fax capability according to the format specified by RFC 3407.

Identifier
Version
Severity
Description

CSCsq16261

4.3

Enhance

For a slow start call with tunneled QSIG to SIP, the HSI did not process ringback tone.


Symptoms: When the HSI received an EISUP CPG that included a Progress Indicator for inband information for a QSIG call, the HSI sent a Facility message to Cisco CallManager to support tunneled QSIG. A Progress Indicator cannot be included in a Facility message so the Cisco CallManager did not attempt to respond by using the H.245 protocol.

Resolution: The HSI now sends a Progress message to include the Progress Indicator for a QSIG tunnel call.

Identifier
Version
Severity
Description

CSCsl11969

4.3

3

The HSI did not clear call records of calls connected for a long duration.


Symptoms: If a call was in the connected state, and both the Cisco PGW 2200 and the other H.323 endpoint did not send a release message to the Cisco HSI the HSI would never release the call. This could occur as a result of a network failure.

Resolution: A new property, ConnectedCallsMaxDuration, is added to the HSI software, which enables an operator to set a maximum duration for a connected call.

If a call exceeds the maximum duration, the HSI removes it from the connected state.

The ConnectedCallsMaxDuration property is a static property. When an operator provisions this property, he must restart the HSI to enable the property to take effect. The ConnectedCallsMaxDuration property is set for a number of hours. The range of hours is 0-100. The default value is 0, which represents an infinite duration of time.

As a result of the following sample MML provisioning session, the HSI removes any call that exceeds the maximum limit of 100 hours.

gw mml> prov-sta::srcver=active,dstver=connectedDuration
gw mml> prov-add::name=CCPackage, ConnectedCallsMaxDuration=100
gw mml> prov-cpy
gw mml> restart-softw
 
   

Identifier
Version
Severity
Description

CSCsq21713

4.3p5

2

During a performance test, a Cisco HSI running on the Sun Solaris 10 operating system did not respond as expected to an IAM message.


Symptoms: A Cisco HSI running on the Sun Solaris 10 operating system did not process an IAM message correctly.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCso13039

4.3

Enhance

The HSI did not support mapping between H.245 fpp (frames per packet) to EISUP SDP ptime.


Symptoms: The HSI did not map H.245 frames per packet with EISUP SDP ptime.

Resolution: The HSI now supports mapping from H.245 fpp to ptime for G723, G728 and G729 codecs.

A new property, EnableFramePerPacketMapping, is added to the HSI software to enable this mapping. The EnableFramePerPacketMapping property is a dynamic property.

The following sample MML session enables the EnableFramePerPacketMapping dynamic property:

gw mml> prov-sta::....   // start a new provision
gw mml> prov-add::name=SYS_CONFIG_DYNAMIC, EnableFramePerPacketMapping=enable
gw mml> prov-cpy

Identifier
Version
Severity
Description

CSCsq58029

4.3

2

During a performance test of the Cisco HSI, the system experienced a Sun Solaris 10 operating system failure.


Symptoms: The Sun Solaris 10 operating system, on which the HSI was running, failed during a performance test.

Resolution: The system problem has been eliminated.

Identifier
Version
Severity
Description

CSCsr00736

4.3

2

The HSI rejected a call and set a link to out of service (OOS) after the Cisco PGW 2200 removed the EISUP parameter 169.


Symptoms: In response to the Cisco PGW 2200 removing the EISUP parameter 169, the HSI rejected a call and set the link to OOS.

Resolution: The HSI is modified to eliminate this problem.

HSI 4.3 Patch 5 Information

This section includes information on:

New Feature in HSI 4.3 Patch 5

Caveats Resolved by Cisco HSI 4.3 Patch 5

New Feature in HSI 4.3 Patch 5

Cisco HSI 4.3 Patch 5 introduces per call support for the G.723.1 codec (silence suppression).

Per Call Support for the G.723.1 Codec

For releases of the Cisco HSI prior to HSI 4.3 Patch 5, the silence suppression field of the G.723.1 codec was provisioned for all calls, which could cause problems for some IPIP gateways because IPIP gateways check the suppression parameter strictly for every call.

HSI 4.3 Patch 5 enables the HSI to support dynamic G.723.1 codecs on a per-call basis. For the Session Description Protocol (SDP), the HSI supports the following G.723.1 dynamic payload values:

G.723.1-H/8000 (7)

G.723.1-L/8000 (8)

G.723.1a-H/8000 (9)

G.723.1a-L/8000 (10)

In the preceding list, the HSI processes the codecs G.723.1-H/8000 and G.723.1-L/8000 as G.723.1 without silence suppression. The HSI processes codecs G.723.1a-H/8000 and G.723.1a-L/8000 as G.723.1 with silence suppression enabled.

If your HSI configuration has 6 codecs configured before you attempt to enable this enhancement, start the enumeration of the payload types for the new codecs with the value 7, as shown in the following example:

* SYS_CONFIG_STATIC.G7231DynCodecSupported = enabled

* SYS_CONFIG_DYNAMIC.UsePayloadTypeMapping = true

* h245.caps.table[7].audio.g7231-dyn.maxAudioFrames = 1

* h245.caps.table[7].audio.g7231-dyn.silencesuppression = 0

* h245.caps.table[7].entryNo = 72311

* h245.caps.table[8].audio.g7231a-dyn.maxAudioFrames = 1

* h245.caps.table[8].audio.g7231a-dyn.silencesuppression = 1

* h245.caps.table[8].entryNo = 72312

* h245.chan[7].audio.g7231-dyn.maxAudioFrames = 1

* h245.chan[7].audio.g7231-dyn.silencesuppression = 0

* h245.chan[7].name = g7231-dyn

* h245.chan[8].audio.g7231a-dyn.maxAudioFrames = 1

* h245.chan[8].audio.g7231a-dyn.silencesuppression = 1

* h245.chan[8].name = g7231a-dyn

* h245.modes[7].audio.g7231-dyn = NULL

* h245.modes[7].name = g7231-dyn

* h245.modes[8].audio.g7231a-dyn = NULL

* h245.modes[8].name = g7231a-dyn


Note Enabling this feature automatically disables the static payload type support of the G.723.1 codec (payload = 4). Cisco HSI customers can modify the value of maxAudioFrames to suit particular needs; however, the value of silencesuppression should not be modified for these two dynamic codecs.


Caveats Resolved by Cisco HSI 4.3 Patch 5

The following anomalies identified in the operation of the Cisco HSI are resolved by HSI 4.3 Patch 5:

Identifier
Version
Severity
Description

CSCsm25356

4.3

Enhance

Support G.7231 codec per call


Symptoms: Request for G.723.1 codec support per call.

Resolution: See the section Per Call Support for the G.723.1 Codec.

Identifier
Version
Severity
Description

CSCsl67650

4.2

3

H.323 cause code 14 (PortedNumber) must map to an EISUP cause code.


Symptoms: The HSI must map the H.323 cause code 14 (PortedNumber) to the appropriate EISUP cause code.

Resolution: Now you can use MML provisioning commands to provision the new static parameter CC_HC_PortedNumber to map the H.323 cause code 14 to any supported EISUP cause code. You must restart the HSI after provisioning the CC_HC_PortedNumber parameter. The following example of an MML session shows how to provision the parameter.

gw mml> prov-sta::srcver=active,dstver=HCPortedNum
gw mml> prov-add::name=CCPackage,CC_HC_PortedNumber=CC_EC_PortedNumber
gw mml> prov-cpy
gw mml> restart-softw

Identifier
Version
Severity
Description

CSCsl41086

4.2

3

The HSI crashed and generated the message
core _ZNK14 CCStateMachine8getStateEi.


Symptoms: The HSI crashed and generated the message core _ZNK14 CCStateMachine8getStateEi.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsl25593

4.3P4, 4.2

3

When the cause location =o in a H.323 message, the cause mapping was incorrect.


Symptoms: HSI cause location mapping from H.323 to EISUP was incorrect when location=0 in H.225 messages.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsl18435

4.3

3

When the value set for Q931.maxcalls was reached, the call was not freed immediately from the call list.


Symptoms: When the value set for Q931.maxcalls was reached, the call was not freed immediately from the call list. This problem occurred when the following conditions existed simultaneously.

1. The HSI runs continuously at high load

2. The value for the parameter Q931.maxCalls is not set high enough

3. The value for the parameter SYS_CONFIG_DYNAMIC.OvldLevel1ThreshLowerCPU is set too high

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsk84567

4.2

3

HSI might crash while processing heavy traffic.


Symptoms: HSI might crash while processing heavy traffic.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsl12998

4.3

3

Need to ensure presence of voice on both sides of a call when the Cisco PGW 2200 experiences a switchover.


Symptoms: This anomaly exhibited the following symptoms:

1. A connected call was placed on hold.

2. The Cisco PGW 2200 experienced a switchover.

3. The call resumed but voice was present on only one side of the call.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsm09866

4.3

3

HSI 4.3 P4 might fail when it receives an SDP message with invalid c= parameter content.


Symptoms: HSI 4.3 P4 might fail when it receives an SDP message with invalid c= parameter content.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsm80017

4.2, 4.2

3

When the HSI receives a logical channel name by type, it might return an invalid result.


Symptoms: Occasionally, when the HSI received a logical channel name by type, it might return an invalid result.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCse17090

4.2

3

PSTN to H.323 calls were improperly rejected due to the generation of an incorrect cause value.


Symptoms: PSTN to H.323 calls were improperly rejected due to the generation of an incorrect cause value.

Resolution: To enable the HSI to wait for the correct release cause value from Cisco CallManager, you must set the parameter OutgoingCallUnansweredRelWait to any text value, for example, "enabled," as shown in the following MML command example:

prov-add:name=sys_config_static, OutgoingCallUnansweredRelWait="enabled"
prov-cpy
restart-softw
 
   

To disable the parameter OutgoingCallUnansweredRelWait, set it to blank ("") and then restart the HSI.

HSI 4.3 Patch 4 Information

This section includes information on:

New Features in HSI 4.3 Patch 4

Caveats Resolved by Cisco HSI 4.3 Patch 4

New Features in HSI 4.3 Patch 4

Cisco HSI 4.3 Patch 4 introduces two new properties:

Support new Sys_Config_Dynamic Parameter—enableAnnexEinRRQ

Support new H323_SYS Parameter—maxDescs

Support for New Sys_Config_Dynamic Parameter—enableAnnexEinRRQ

Cisco HSI 4.3 Patch 4 introduces support for the new Sys_Config_Dynamic parameter, enableAnnexEinRRQ.

When enabled, the parameter enableAnnexEinRRQ sets the "H.323 Annex.E transport address" as an alternate signalling address. By default, this parameter it is not set. Currently, Cisco recommends retaining the default setting for this parameter, which is disabled.

Support New H323_SYS Parameter—maxDescs

Cisco HSI 4.3 Patch 4 introduces support for the new H323_SYS parameter, maxDescs. The parameter maxDescs is of type Integer. If this parameter is not set, or set to an empty value, the Cisco HSI operates with the default value 30000.

The maxDescs parameter establishes the maximum number of file descriptors used by the HSI.

Normally, a call uses two file descriptors, one for an H.225.0 TCP connection, the other for an
H.245 TCP connection.

Cisco recommends setting the value of maxDescs to a value that is twice the value set for the H323_SYS.maxCalls parameter. The maxDescs parameter can enhance HSI performance especially if a user wishes to set maxDescs to a value larger than 30000.

To add the maxDescs parameter, issue MML commands similar those provided in the following example:

prov-add:name=h323_sys, maxDescs=40000
prov-cpy
restart-softw

Caveats Resolved by Cisco HSI 4.3 Patch 4

The following anomalies identified in the operation of the Cisco HSI are resolved by HSI 4.3 Patch 4:

Identifier
Version
Severity
Description

CSCsk00113

4.3

3

The HSI experienced a core dump as it was processing a hairpin-call stress test.


Symptoms: By default, the HSI sent a RRQ message with one alternate address (Annex E address), which was not supported yet.

Resolution: The HSI is modified so that it does not send Annex E information unless a user enables a new sys_conf_dynamic parameter—EnableAnnexEinRRQ to a non-empty value.

To enable sending an Annex E address, issue the following MML command:

prov-add:name=sys_config_dynamic, EnableAnnexEinRRQ="true" 
 
   

To disable sending an Annex E address, issue the following MML command:

prov-ed: name=sys_config_dynamic, EnableAnnexEinRRQ=""

Identifier
Version
Severity
Description

CSCsk30552

4.3

3

The HSI did not correctly manage CCM 5.1 ECS in a call transfer to DPNSS.


Symptoms: The HSI did not correctly process codec selection in the ECS procedure, which caused calls to fail in some cases.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsj05326

4.3

6

Simplify the HSI log setting.


Symptoms: Previously, users had to type several MML commands to set up logging.

Resolution: The procedure for setting HSI logging is simplified so that users can issue the commands hsi_log_start and hsi_log_stop <traceFileName> to get the platform.log trace.

Identifier
Version
Severity
Description

CSCsk65404

4.3

2

The HSI did not open a H.245 two-way channel when it switched to T.38.


Symptoms: When a T.38 switchover was initiated, the HSI closed the audio channels but failed to open the two fax channels.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsj51932

4.3

3

The MML command rtrv-alms:cont did work properly.


Symptoms: The MML command rtrv-alms:cont was not operating as expected.

Resolution: The HSI is modified so that the rtrv-alarms command works correctly.

Identifier
Version
Severity
Description

CSCsk40531

4.3

3

An HSI-generated SDP caused a Linksys ATA to release a call.


Symptoms: The HSI generated an SDP that included a session ID that was longer than the receiving device was able to accept.

Resolution: The HSI is modified to generate an SDP that conforms to the appropriate RFC standard.

Identifier
Version
Severity
Description

CSCsk79895

4.3

3

HSI 4.3P3 or previous versions of the HSI running on the N240 platform experienced Call Control Thread performance problems.


Symptoms: The HSI experienced occasional CPU performance degradation while processing call-control-thread operations.

Resolution: Set the parameter OvldLevel1ThreshLowerCPU to the value 47 or lower to avoid any potential for call control thread performance problems.

Identifier
Version
Severity
Description

CSCsi21653

4.3

6

Increase the upper limit of the performance level that establishes an overload condition.


Symptoms: Establish higher performance limits.

Resolution: HSI 4.3 Patch 4 increases the upper limit of the following properties:

H323_SYS.maxCalls
For this parameter's association with the new H323_SYS parameter maxDescs, see the section Support New H323_SYS Parameter—maxDescs

Q931.maxCalls

SYS_CONFIG_DYNAMIC.OvldLevel1ThreshLowerCalls

SYS_CONFIG_DYNAMIC.OvldLevel1ThreshUpperCalls

SYS_CONFIG_DYNAMIC.OvldLevel2ThreshLowerCalls SYS_CONFIG_DYNAMIC.OvldLevel2ThreshUpperCalls

SYS_CONFIG_DYNAMIC.OvldLevel3ThreshLowerCalls

SYS_CONFIG_DYNAMIC.OvldLevel3ThreshUpperCalls

Identifier
Version
Severity
Description

CSCsj67783

4.3

3

The HSI experienced a flood of bulk error message while running a performance test.


Symptoms: A performance test generated a flood of error messages.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsj65790

4.3

2

HSI experienced a core dump during a performance test at 80 calls per second.


Symptoms: The HSI core dumped during a performance test.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsh64349

4.1

6

The HSI must map its Progress:CauseIndicator to ACM/CPG's CauseIndicator.


Symptoms: HSI is required to map H.323 Progress CauseIE to EISUP ACM/CPG's CauseIndicator.

Resolution: The HSI now maps H.323 Progress CauseIE to EISUP ACM/CPG's CauseIndicator.

HSI 4.3 Patch 3 Information

This section includes information on:

New Features in HSI 4.3 Patch 3

Caveats Resolved by Cisco HSI 4.3 Patch 3

New Features in HSI 4.3 Patch 3

Cisco HSI 4.3 Patch 3 introduces a new property:

Support new Sys_Config_Dynamic Parameter—UsePayloadTypeMapping

Support for New Sys_Config_Dynamic Parameter—UsePayloadTypeMapping

Cisco HSI 4.3 Patch 3 introduces support for the new Sys_Config_Dynamic parameter, UsePayloadTypeMapping. UsePayloadTypeMapping is a string parameter, which, if set to a non-empty value, the HSI negotiates the SDP payload type to be identical to the value received from the Cisco PGW 2200. By default, this parameter is disabled (set to an empty value). In the default case, the HSI uses the payload type that is hardcoded (static) in the HSI.

Cisco recommends enabling this parameter.

To enable payload mapping issue the following MML command:

prov-add:name=sys_config_dynamic, UsePayloadTypeMapping="true"
 
   

To disable payload mapping issue the following MML command:

prov-ed: name=sys_config_dynamic, UsePayloadTypeMapping=""
 
   

Caveats Resolved by Cisco HSI 4.3 Patch 3

The following anomalies identified in the operation of the Cisco HSI are resolved by HSI 4.3 Patch 3:

Identifier
Version
Severity
Description

CSCsi80243

4.1, 4.2, 4.3

2

The HSI MML command rtrv-ne-health required a mechanism to free suspended calls automatically.


Symptoms: Calls suspended on the HSI had to be freed manually by issuing the MML command rtrv-ne-health.

Resolution: Now, periodically, suspended calls are cleared automatically.

Identifier
Version
Severity
Description

CSCsj24795

4.1

3

In rare circumstances, some call setups became suspended on an HSI.


Symptoms: Issuing the MML command rtrv-overload displayed a higher call number than the setup call number displayed when the MML command rtrv-ne-health was issued.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsj61522

4.2

3

The HSI needs the ability to change the Payload Type for Clear CODEC


Symptoms: By default, the HSI uses a hard-coded payload type for dynamic codecs. Occasionally, this causes problems.

Resolution: HSI 4.3 Patch 3 introduces the Sys_Config_Dynamic parameter, UsePayloadTypeMapping, which enables the HSI to use a payload type that is consistent with the SDP from the Cisco PGW 2200.

To enable payload mapping issue the following MML command:

prov-add:name=sys_config_dynamic, UsePayloadTypeMapping="true"
 
   

To disable payload mapping issue the following MML command:

prov-ed: name=sys_config_dynamic, UsePayloadTypeMapping=""
 
   

Identifier
Version
Severity
Description

CSCsi91495

4.2

3

HSI includes 'h245Address' in progress message.


Symptoms: The HSI included an 'h245Address' in a progress message. The H.245 address was not suppressed in the progress message if SDP was delayed coming from a Cisco PGW 2200.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsi99563

4.1

3

HSI 4.1 Patch 14 software malfunctioned.


Symptoms: A system running HSI 4.1 Patch 14 stopped operating.

Resolution: This problem is resolved.

Identifier
Version
Severity
Description

CSCsj25244

4.3

3

A call hold operation between the HSI and
Cisco CallManager (CCM) failed.


Symptoms: During call hold/resume operation with the CCM, the port number is set to 255 while the IP address is 0.0.0.0. This SDP information caused a problem with some gateways or firewalls.

Resolution: The port number is changed to a 2048, valid even number.

Identifier
Version
Severity
Description

CSCsj76011

4.3

3

A retransmission from an EISUP link caused the HSI to malfunction.


Symptoms: The HSI malfunctioned and was unable to process new calls when it received retransmission of a large number of EISUP messages.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsj67781

4.3

3

HSI 4.3 coredumped while processing an SNMP operation.


Symptoms: The HSI 4.3 software coredumped during an SNMP operation.

Resolution: The HSI is modified to eliminate this problem.

Identifier
Version
Severity
Description

CSCsi83681

4.1, 4.2, 4.3

2

HSI 4.1 coredumped when processing an SNMP operation for OfTSnmpTrapHandlerImplJraiseTrapiTBRC6Mbasic_
sting7c_k.


Symptoms: The HSI coredumped after a switchover when it was processing an SNMP operation.

Resolution: The HSI is modified to eliminate this problem.

HSI 4.3 Patch 2 Information

This section includes information on:

New Features in HSI 4.3 Patch 2

Caveats Resolved by Cisco HSI 4.3 Patch 1

New Features in HSI 4.3 Patch 2

Cisco HSI 4.3 Patch 2 introduces two new features:

Support for Type of Service/Quality of Service (TOS/QoS) Setting in IP Headers

HSI Support for New Cause Codes Sent Through a PGW 2200 EISUP Interface

Support for TOS/QoS Setting in IP Headers

Cisco HSI 4.3 Patch 2 enables the HSI to set a TOS/QoS parameter in the IP header of Q931, H.225, RAS, and EISUP messages.

set-tos

The set-tos command sets the TOS/Qos field in the IP header of HSI messages.

set-tos::tos = <tos_value>

Syntax Description

tos_value

[0-184]


Usage Guidelines

The set-tos command takes effect immediately. However, the value set by the command is not saved during a restart of the HSI.

Valid values for tos_value are 0, 32, 40, 64, 72, 96, 104, 128, 136, 184. If you specify any other value in the range 0-184, the HSI sets the vale to the default 96.

You can establish a static setting for the system configuration static parameter IpTOS (which remains after an HSI restart) by entering the following MML command:

prov-add:name=SYS_CONFIG_STATIC, IpToS=64
 
   

In the Cisco H.323 Signaling Interface Users Guide, Release 4.3, see the section "SYS_CONFIG_STATIC Parameters" in Chapter 3 and Appendix A, "MML User Interface and Command Reference."

Examples

In the following example, the command sets the tos_value to 96 (the default):

gw mml> set-tos:tos=96
M SUCC

HSI Support for New Cause Codes Sent Through a PGW 2200 EISUP Interface

Cisco HSI 4.3 Patch 2 supports new internal cause codes sent by the Cisco PGW 2200 across EISUP interfaces. The new cause codes correspond to SIP response codes.

The new cause codes are included in the Appendix B, Appendix D, and Appendix E in the Cisco H.323 Signaling Interface User Guide, Release 4.3.

Caveats Resolved by Cisco HSI 4.3 Patch 2

The following anomalies identified in the operation of the Cisco HSI are resolved by HSI 4.3 Patch 2:

Identifier
Version
Severity
Description

CSCsh74179

4.2

3

The HSI experienced a coredump during an ACT test.


Symptoms: The HSI experienced a coredump during an Asymmetric Codec Treatment (ACT) test.

Resolution: The HSI is modified so that it does not coredump during an ACT test.

Identifier
Version
Severity
Description

CSCsi40187

4.3

3

The HSI 4.3 did not generate alarms when it interoperated with a version of the Cisco PGW 2200 prior to version 9.6.


Symptoms: The HSI 4.3 did not generate alarms when it interoperated with a version of the Cisco PGW 2200 prior to version 9.6.

Resolution: If one attempts to run HSI 4.3 in communication with a version of the Cisco PGW 2200 prior to version 9.6, the HSI now generates the alarm HSI_PGW_INCOMPATIBLE.

Identifier
Version
Severity
Description

CSCsi80297

4.3

3

HSI to CCM 5.1, call hold/resume not work.


Symptoms: For an HSI connected to Cisco CallManager 5.1, call hold/resume did not operate correctly.

Resolution: In response to this occurrence, issue the following MML command:

prov-add:name=SYS_CONFIG_DYNAMIC, WaitTCSAfterCallResume=true
 
   

Identifier
Version
Severity
Description

CSCsi18017

4.2

3

The HSI did not forward the Connected Line Restricted indicator to CCM.


Symptoms: The HSI did not forward the Connected Line Restricted indicator to CCM for a call from a CCM IP phone to a PSTN phone, via a PGW.

Resolution: The HSI now transmits the presentation indicator and screening indicator to CCM.

Identifier
Version
Severity
Description

CSCeb60409

4.1

3

The MML command prov-dlt did not work for some properties.


Symptoms: The MML command prov-dlt did not work for some properties and the HSI generated the error:

"DENY Not allowed to (because CONST) or did not find SYS_CONFIG_STATIC:name to 
delete."
 
   

Resolution: The HSI now processes the prov-dlt command correctly.

Identifier
Version
Severity
Description

CSCsi41915

4.3

3

The HSI GWmain process coredumped when the command restart-softw was issued when the HSI was processing fewer than 10 calls per second.


Symptoms: The HSI GWmain process coredumped when the command restart-softw was issued when the HSI was processing fewer than 10 calls per second.

Resolution: The HSI is modified to process the command restart-softw correctly.

Identifier
Version
Severity
Description

CSCsh87586

4.2

3

The HSI software failed when the H.323 stack received invalid packets during a call.


Symptoms: The HSI software failed when the H.323 stack received invalid packets during a call.

Resolution: The HSI is modified so that it does not fail in response to invalid packets.

Identifier
Version
Severity
Description

CSCsi40403

4.3

3

The HSI temporarily processed a few calls despite the absence of a valid license file.


Symptoms: The HSI temporarily processed a few calls despite the absence of a valid license file.

Resolution: The HSI does not operate without of a valid license file.

HSI 4.3 Patch 1 Information

This section includes information on:

Caveats Resolved by Cisco HSI 4.3 Patch 1

Caveats Resolved by Cisco HSI 4.3 Patch 1

The following anomalies identified in the operation of the Cisco HSI are resolved by HSI 4.3 Patch 1:

Identifier
Version
Severity
Description

CSCsi33947

4.3

3

A request to create an H.323 DPNSS call failed because the IAM message included an illegal calling party number.


Symptoms: When the HSI received a SETUP message that did not include a callingPartyIE, the HSI transmitted an IAM message in which the callingPartyNumber had empty digits.

Resolution: The HSI now manages such call requests correctly

Identifier
Version
Severity
Description

CSCsg85269

4.2

2

The HSI denied MML session requests.


Symptoms: When an active MML session was dropped, the HSI denied additional attempts to open a session.

Resolution: The HSI now manages MML sessions appropriately.

Identifier
Version
Severity
Description

CSCsi14944

4.3

3

The HSI did not release a call when it received illegal tunneled QSIG information.


Symptoms: When the HSI is configured with the ForceTunnReq parameter set to True and the parameter EnableInboundAnnexM1 is not configured, if the HSI receives a SETUP message that includes the tunnelingRequired field, it should release the call. However, in this cae, the HSI did not release the call but waited for the other side to terminate the call.

Resolution: The HSI now terminates such calls as expected.

Identifier
Version
Severity
Description

CSCsi05053

4.3

3

Correct the management of messages that require tunneling in the setup message


Symptoms: Some IOS versions send a SETUP message that include the tunnelingRequired field. By default, the HSI accepts this; however, this could result in mean GTD tunnelling.

Resolution: A new property has been added to the HSI that requires setting the parameters SYS_CONFIG_DYNAMIC and EnforceTunnReq. Now, by default, the tunnelingRequired field is ignored unless the customer enables EnforceTunnReq by setting the following parameters:

prov-add:name=sys_config_dynamic, EnforceTunnReq=true
 
   

Identifier
Version
Severity
Description

CSCsh62336

4.3

3

The HSI core dumped and an HSI-to-HSI call failed.


Symptoms: The HSI core dumped when an HSI-to-HSI call was attempted.

Resolution: This problem is fixed.

Identifier
Version
Severity
Description

CSCsh16955

4.2 and 4.3

3

Asymmetric codec handling resulted in a memory leak.


Symptoms: There was a small memory leak for asymmetric codec calls when HSI was negotiated as a slave in the MSD procedure.

Resolution: The memory leak is eliminated.

Identifier
Version
Severity
Description

CSCsg40768

4.2

3

The HSI needed a mechanism to change log timestamps to reflect HSI system time.


Symptoms: On the Cisco HSI, events are logged in files in the directory /opt/GoldWing/4.2/var/log and timestamped according to GMT time, not system time.

Resolution: Now you can configure the HSI optionally to use the system time. By default, this feature is disabled to ensure for backward-compatibility.

To enable the feature set the following parameters to any text value (for example, "true"):

prov-add:name=sys_config_static, UseSysTimeEnabled=true
 
   

To disable the feature, delete the parameters or set them to blank (""):

prov-ed:name=sys_config_static, UseSysTimeEnabled=""

Note This is a static property. If you change the configuration, you must restart the HSI.


Identifier
Version
Severity
Description

CSCsh48356

4.1

3

The MML command rtrv-ne-health call count failed during call processing and the system core dumped.


Symptoms: The HSI had some synchronous problems when the MML command rtrv-ne-health was executed.

Resolution: The synchronous problems have been eliminated.

Identifier
Version
Severity
Description

CSCsb16339

4.1

3

The HSI forwarded an incorrect source IP address for screening.


Symptoms: The IP address passed to the PGW as the source address is the sourceCallSignalAddress from within the setup message. However, the address should be the address from which the incoming H225 setup message came (that is, in the IP header) for screening.

Resolution: Now you can configure the HSI optionally to use the actual incoming IP address from the IP header. By default, this feature is disabled to ensure backward-compatibility.

To enable the feature, set the following parameters to any text value (for example, "true"):

prov-add:name=sys_config_dynamic, UseRealSourceIP=true 
 
   

To disable the feature, delete the parameters or set them to blank (""):

prov-ed:name=sys_config_dynamic, UseRealSourceIP=""
 
   

Identifier
Version
Severity
Description

CSCsh02337

4.2

2

EISUP links may stop carrying traffic when one receives an incorrect packet.


Symptoms: An EISUP link halted traffic after receiving incorrect packets.

Resolution: The HSI is modified so that an EISUP link does not stop traffic upon receiving an incorrect packet. This fix enhances RUDP reliability.

Identifier
Version
Severity
Description

CSCsh51478

4.2

3

The H225PavoSupported parameter overrides the Q931RedirSupported parameter setting.


Symptoms: The HSI did not support CCM PAVO (redirecting number) and Q931 redirecting number simultaneously., now you can configure both property to "true" to enable them.

Resolution: The HSI now enables setting both H225PavoSupported and Q931RedirSupported to true.

Identifier
Version
Severity
Description

CSCsh16949

4.2

3

HSI cleared a call that had asymmetric codec


Symptoms: When the HSI detected an asymmetric codec condition, it released the call.

Resolution: The HSI is modified so that it does not release a call that exhibits the asymmetric codec condition.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.