Quintum Home Page
Search
Enterprise Solutions | Service Provider Solutions | Resource Center | About Us | News | Technical Support | Partners/Resellers
Support

Tenor(tm) VoIP MultiPath Switch/Gateway and Call Relay Products
P108 Maintenance Release Notes

This document lists all software fixes for VoIP MultiPath Switch/Gateway and Call Relay Products running maintenance software P108-09-04 and previous.

Products Affected

These maintenance release notes apply to the following products:

  • Tenor DX VoIP MultiPath Switch/Gateway
  • Tenor AX VoIP MultiPath Switch/Gateway
  • Tenor AS VoIP MultiPath Switch/Gateway
  • Tenor AF VoIP MultiPath Switch/Gateway
  • Tenor BX VoIP MultiPath Switch/Gateway
  • Tenor CMS VoIP MultiPath Switch/Gateway
  • Tenor DXi PCIe VoIP Multipath Switch/Gateway (Release P105-19-09 or higher)
  • Tenor Call Relay SP
  • Tenor Gatekeeper+
  • Tenor Response Point Gateway

A software maintenance release is a release of software that has been created by Quintum to resolve an inconsistency or "bug" that has been identified within a release.

Maintenance releases (for Second Generation Tenors) can be identified by the 3rd set of digits in the release name as PX-Y-Z, where the Z is the maintenance number. All maintenance releases will be built on top of the latest GA release of software. For example, if P102-11-00 is the latest GA software, the first maintenance release of software will be P102-11-01. The notes below are cumulative since the last GA Release, P107-09-00. Generally Available (GA) software. Maintenance software goes through limited testing from Quintum, but has been verified as resolved by the customer who identified the problem.

If additional maintenance releases are required for a specific GA release, each new maintenance will contain all previous maintenance fixes. For example, maintenance release P100-11-02 will include all maintenance release changes from P100-11-01.

On a scheduled basis, Quintum will release a full GA version that will include all previous maintenance released that have undergone full system test.

Interoperability

CMS COMPATABILITY NOTE: P101 and LATER CODE ON CMS ONLY SUPPORTS SERIES 2 CONTROLLER AND PERIPHERAL CARDS!

For more information, see http://www.quintum.com/support/products/2G/cms/sysdoc/CMS_series2_notice.pdf

Open Issues

P108-09-04

4781 IPRG defined in static route not being applied for inbound SIP calls

When an IPRG is attached to a SIPSG (for inbound SIP calls), if there is a static route match based on destination address, the IPRG in the static route does not take effect.

4784 IP address in SDP is sent as private when it should be public

The IP address in the SDP is being sent by the Tenor as private, even when the external NAT is set. The IP address should be sent as public.

Resolved Issues/Feature Enhancements

P108-09-04

4758 Dual Register Proxy Failover Problem

In dual registration Proxy failover mode, the Primary Proxy should have attempted proxy fail over mode first, and if that failed, the secondary Proxy should have been attempted. Instead, the Tenor did not failover to the secondary SIP server on a no response from the Primary Proxy. As a result, all subsequent calls failed. This has been resolved.

4760 Routing with DNCM

When using FXO ports with IVR type 1 (second dial tone), when the user called in and received second dial tone, then dialed an extension that was configured as a specific channel DNCM, the call was not routed according to the DNCM parameters. This has been resolved.

4763 SS7: Enhance Continuity Check Support

For SS7, when calls were sent to the Tenor for a loopback test on a previous circuit, the Tenor would ignore the call. Now, the Tenor waits for the results of the loop back test to continue or drop the call.

4765 Ringback not working with IVR and EarlyMedia

Ringback was not working with IVR and early media enabled in SIPSG. This has been resolved.

4766 SipInfo Payload Decode Failure

Tenor failed to decode SipInfo payload when 11(*) and 12(#) were in the payload of the SipInfo received from a ResponsePoint unit.The Response Point unit encoded these characters differently depending on the brand of the phone from which the call originated. For example, if the call originated from a Syspine phone, characters * and # were in the payload. If the call originated
from an Astra phone, numbers 11 and 12 were in the payload. Tenor could only decode characters * and # and not numbers 11(*) and 12(#). This has been resolved.

4767 Cancel re-sent even though final response received

When the Tenor received a final response to an ongoing Invite, it re-sent a Cancel message, which made the call fail. Now, the Tenor will send a BYE.

4769 AllowOnlyProxyCalls did not work for TCP calls

The config parameter, AllowOnlyProxyCalls, in SIPSG did not work for TCP calls. This has been resolved.

P108-09-03

4744 Incorrect CName Encoding Under NI2 (Tenor DX only)

Cname was not being encoded properly for outgoing PRI calls when NI2 was used. This has been resolved.

4745 Change syntax of backup and restore commands

The names for two backup command have been changed (these are general commands available under configuration in CLI).

try restore database changed to restore database

try backup database changed to backup database

4746 Tel URI in Diversion header was not being decoded properly

When a Tenor received an Invite with the Diversion header field, the Tenor was unable to decode the Diversion header with a Tel URI, and the Invite was not processed. This has been resolved.

4748 Tenor used "To" header as called party rather than the P-Called-Party-ID header

Tenor routed calls based on the P-Called-Party-ID header as the called number. Now, the Tenor will route the calls based on the "To" header.

4750 New routing - wildcards did not work

In New Routing, a Number Table match was found even if the normalized number was longer or shorter than the configured number pattern using wildcard characters (dots). This has been resolved.

4751 Database directory enhancements

If the directory /hd/cfg/db/ was deleted accidentally, the system could not write any database files. As a result, any changes to the database were lost after the system reboot. Now, as a preventative measure for the files not to be lost, upon startup, the Tenor will check to see if the directory /hd/cfg/db/ is missing. If
it is, the system will create a new /hd/cfg/db/ directory in which the database files can be written.

4753 PRI ETSI Status message resulted in call failure

If a Digital Tenor received a STATUS message in response to an outgoing SETUP, it would have dropped the call. This has been resolved.

4756 Incorrect transportType used on Call 2 before attended transfer

When an initial call was made using UDP (because transportType in SIPSG was set to UDP), and the user hit flash hook and dialed another number, the call may have been made using TCP.The call should have been made using UDP. This has been resolved.

4757 CRSP with new routing asked for license

When a Tenor (CRSP) was upgraded to P108 (which includes new IP to IP routing), the Tenor Configuration Manager gave an error/warning message about needing the advanced routing P108 license.This should not have occurred and has been resolved.

P108-09-02

4741 Port mapping was not working in P108

Port mapping using SIP did not work in P108. This is now working.

4742 IVR is now accessible with New Routing

IVR types were not accessible using the New Routing. IVR type 0, 1 and 8 are now exposed.

P108-09-01

4705 REFER-TO header Transport tag was not working

The Tenor did not obey the transport specified in the REFER-TO header of a REFER message. Instead, it was using the transport type configured in the SIP Signaling Group to send the Invite out. This has been resolved.

4717 If no media in re-Invite, a Hold was being sent

After a call is up, the server was sending the Tenor a re-Invite with no SDP. The Tenor took this Re-Invite as a trigger to send a hold request to the far end. Instead, a regular re-Invite (with SDP) should have been sent to the far end. This has been resolved.

4718 When BYE was received at a non-existent session, the Tenor now sends 481 instead of ignoring

If a Tenor received a BYE at a session that did not exist, it would ignore the message. Instead, a 481 will now be sent in response to a BYE with non-existent call session.

4723 For new routing, call was not being re-routed

A call tried to route out PRI, but there were no available channels. The return cause was Busy (17), and an alternate route was not attempted. This has been resolved.

4727 Tenor improperly set "annexb=no" in SDP

If the Tenor received a request with SDP that did not contain annexb, then in response, the Tenor would improperly put annexb in the SDP. This has been resolved.

4732 Error in setting static IP address

Upon startup, there is an option of hitting the "i" key via the RS 232 interface to set a static IP address of the Tenor. Occasionally, the Tenor would not save the IP address correctly, and when it reboot, the IP address would show as 0.0.0.0 instead of the keyed-in IP address. This has been resolved.

4733 Transport type over rides entry in var_config file

When the Transport Type in SIPSG was set to UDP, it overrides the varconfig entry "SipTransportDefault" set to 1 to use TCP for the SIP calls. This has been resolved for the varconfig entry to take precedence, resulting in the call being sent over TCP.

4736 SIP Server field restricted

The PrimarySIPServer was restricted and unable to be configured. This has been resolved.

4737 Tenor stopped working when the command of "st ds1 call" was issued

The Tenor stopped working when the command "st ds1 call" was issued. This has been resolved.

4738 Factory Fresh Setting Static IP Address problem (Tenor CMS only)

There was an IP address configuration problem on a new Tenor CMS. This has been resolved.

4739 Changes over Multipath Routing Enhancements

Several new changes/feature enhancements have been included for the Tenor's new Routing feature.

  • In the Routing Table, the following configuration options have been changed as follows:

    Inbound TG changed to Incoming From
    OutboundTg changed to OutgoingTo
    InboundMatchCriteria changed to IncomingMatchCriteria
    NumberForDiversion changed to DiversionPilotNumber
    DiversionContent changed to DiversionMatchCriteria

  • For the DiversionMatchCriteria field, a third value of None (-1) has been added to the other two values available, CalleD (0) and CalliNg (1). The value of None will become the default value.
  • Currently when you enable the UseRoutingTable field, a warning is given about the permanent loss of non-Routing Table related settings. Two new commands are added for database backup and restore.

    try restore database. Restores db.txt file from db.bak file, if it's available.

    try backup database. Backs up db.txt file as db.bak file.

4740 CLI should put message for hunt group with New Routing

When new routing was enabled, and a user tried to access Hunt LDN, there was not a message stating that the hunt group was disabled. The following message now exists:

Error: This command is inaccessible in the current configuration.
An su login is required to access it.