Tenor S (tm) - Survivable Multipath Switch - S105-09-02 Release Notes

This document lists open issues for the following products running software version S105-09-02 (SSG or "SIP Survivable Gateway"), and issues resolved since S105-09-00:

Analog Gateways

Tenor S AX
Tenor S AS
Tenor S AF

Digital Gateways

Tenor S BX
Tenor S DX

Note: This document only addresses these products running survivability software (prefixed with an "S"), not standard gateway software (prefixed with a "P").

Upgrading to Tenor S Software from Standard Gateway Software

It should be noted that although the Tenor S (survivabilty) software runs on many of the same hardware platforms, it is a separate product with slightly different defaults for some parameters, and some new parameters that do not exist in the standard gateway software. With that in mind, it is best to restore factory defaults after upgrading to S105 software from P10x software. This will ensure proper defaults, good security and best operating behavior.

Also, note that a license upgrade is required to use survivable software. Survivable software (prefixed with an "S", such as S105) must not be run on a system without the proper license. It will not behave as expected if the proper license is not installed. Contact your distributor to obtain a license upgrade.

It is highly recommended that the Tenor S Application Guide be read and fully understood to ensure a seemless introduction to this product line.

Interoperability

The Survivable Gateway functions interoperates successfully with several IP PBXs and soft-switches, such as Avaya, Broadsoft, Asterisk, SER, Ondo and ININ.

See http://www.quintum.com/support for the latest changes in product interoperability or to download the latest code.

Open Inconsistencies in S105-09-02

Quintum's intent is to resolve open issues in a timely manner. Please check Quintum's support website for updated firmware on a regular basis.

3258 If ListeningPort port is modified for UserAgent, the calls fail

When the ListeningPort is modified for the UserAgent, it does not register internally. As a result, the calls will fail. There are two work arounds:

Before changing the ListeningPort, set the RegisterExpiryTime (available under SIPSG) to 0. Change the port and set RegisterExpiryTime back to non-zero value.

Reboot the gateway after a port change for any of the User Agents registering through the Survivable Gateway.

Resolved Inconsistencies Since S105-09-00 GA Release

3082 Certain Proxies were not compatible with the Tenors

The following proxies had compatibility issues with the SSG functions: SER, Ondo and ININ. As a result, calls could not be processed. This has been resolved.

3215 When creating a new Tenor DB file, the AllowOnlyProxyCalls is incorrectly set to 0

In some circumstances, including when you delete the Tenor's db.txt file or reset to factory defaults from the boot-time console prompt, AllowOnlyProxyCalls in SIPSignalingGroup would be set to 0 (zero), rather than 1. This potentially created a security vulnerability. As a precaution, after setting factory default using any method, you should ensure that AllowOnlyProxyCalls is set to 1. This has been resolved, but those upgrading from earlier versions of SSG software should verify the correct setting of this parameter.

3257 Changing the Survivable Listening Port required reboot

After changing the ListeningPort (available under SurvivabilityParameters) to 5060 and submitting the change, the SSG would not listen to the port until you reboot the system. This has been resolved.

3268/3228 No validation checking for multiple use of ports

There was no check to ensure the Survivability server ListeningPort did not conflict with the UserAgent Ports. Conflicting ports would result in undesirable results. The recommendation was to manually check to ensure the listening port in SurvivabilityParameters (default: 5060) did not conflict with the listening port of any UserAgent in any of the SIPSignalingGroups. We recommended leaving the Survivability ListenPort as 5060, and ensuring no UserAgent used 5060 (default is 5061 and higher). This has been resolved.