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

This document lists all software fixes for VoIP MultiPath Switch/Gateway and Call Relay Products running maintenance software P106-12-15 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 60
• 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 of bug.

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, P106-12-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

4428 Manufacturing test errors

When the manufacturing test is run for P106-12-14, some intermittent errors are seen on a few specific products ( DX4048, DX4060 and DX4120). Sometimes the errors start showing up within a few minutes of starting the test. As a work around, you can install a previous release.

Resolved Issues/Feature Enhancements

P106-12-15

4036 CallRelay supports supplementary services

The CallRelay now supports supplementary services when both ends of a call are using SIP.

4134 Two new CDR formats, 5 and 105 (Tenor CMS and Call Relay SP only)

Two new CDR format 5 and 105 have been added to support Call Relay SP and CMS only. These fields match contain the same data stream as Selection 99 and 199, respectively, but do not include the Access Number field.

4163 Routing Server heartbeat support for SS7 calls

For externally routed calls (using routing server) the Tenor did not send heart beat updates to the routing server. As a result, the Routing Server cleared the call on the trunk and there was a mismatch between the actual calls in the Tenor. This has been resolved.

4208 Negative call durations displayed for CMD Calls command

Sometimes, the Tenor displayed negative call durations when a cmd calls command was executed. This has been resolved.

4247 For SIP, a negative port number was sent out in the INVITE

If the port number was configured as 50600 (greater than 32767), a negative port number was sent out in the INVITE. This has been resolved.

4262 P-Asserted-Identity Decode failure/Register failure

When an Invite was sent with a P-asserted Identity header from SIP to the Tenor, the decoding of the P-asserted identity header failed because of the presence of the <tel:550011> line. Also, Tenor failed to decode a SIP 401 message at the authentication header field containing the stale="true". These issues have been resolved.

4271 Certain fields not applied to Q931 message in case of external routed call

For an IP outbound call, ANIScreenInd and ANIPresentationInd field in Q.931 are set according to user configuration in IPRG. But when the call was routed by external routing server, the IPRG configuration was not applied to the Q.931 message. This has been resolved.

4282 Calls dropped after Tenor sent connect too soon

If a call was answered automatically (without a ring first), the Tenor sent a connect too soon before the PSTN was ready and the call was dropped. This has been resolved.

4285 No Dialplan set TON/NPI to invalid value

In a call from a FXS port without dial plan configuration, the DNIS with EOD was translated to a wrong TON/NPI value (such as 165). This has been resolved.

4286 In Australian Dialplan, international number was translated into a wrong number

When using the Australian Dialplan, the international number was translated into a wrong number. (For example, the Australian Dialplan international number 001182324395299 was incorrectly translated to 6282324395299). This has been resolved.

4293 IVR MultiSession was not working

The IVRMultiSession feature was not working properly (entering ## did not work). This has been resolved.

4296 Max-Forwards not included in PRACK message

The Mediation Server expected Max-Forwards in the Tenor's PRACK message, but they were not included. As a result, calls failed. This has been resolved.

4308 G.729 with 10, 30, 50 or 70 msec has improved voice quality

When the Tenor interoperated with certain gateways (with G.729 codec with a payload size of 10, 30, 50 or 70 msec) the voice quality was not optimum. This resulted from a problem with the DSPs having a padding byte at the end of each RTP packet at payload sizes of 10, 30, 50, or 70 msec. As a way to remove these padding bytes (to improve voice quality), a new config item, NoRTPPadding, enables the Tenor to look for a Padding bit set in the RTP header of (non-fax) media packets (available through var_config.cfg). If a Padding bit is found to be set, it will be cleared and the length of the RTP packet will be reduced to remove the padding bytes. The following entry is needed in the file to activate this feature: NoRTPPadding 1.

4323 Upon receiving 180 Ringing, Tenor plays local ring back

Upon receiving an 180 Ringing, the Tenor will now play local ring back if media has not been received over the RTP channel, even if the 180 Ringing contains SDP. A new var_config.cfg option, EarlyMediaRingTone, enables the Tenor to determine if it should play ring back.

For example:

EarlyMediaRingTone 0. Upon receiving the 180 Ringing, the Tenor responds with a no RTP received.

EarlyMediaRingTone 1. Upon receiving the 180 Ringing, the Tenor plays a local ringback.

See the Command Reference for additional information about the var_config.cfg file.

4335 H.323 slow start resulted in one way audio (Call Relay only)

When the originating side was configured to use slow start (DisableFS=1 in IPRG and MediaAfterConnect=1 in H323SG), RTP was not established in the direction from the Call Relay to the originating end. This caused one way audio. This has been resolved.

4339 RelayANI 2 in external routing server

For external call routing, a new option 2 has been added for Relay ANI in the IPRG. This new option will relay the ANI and set the TON/NPI in the IPRG.

4348 Tenor reset under specific condition

The Tenor reset under the following condition: ivrtype was set to 9 in LCRG or TCRG and ToneBasedSupervision was set to 1 or 3 in cassg. This has been resolved.

4372 Nortel H323 Invalid TON

In the Tenor, the UPDP for Nortel set the H323 TON to an invalid number (i.e., TON = 07). This has been resolved.

4375 Tenor reset when UA was deleted

The Tenor reset when a record was removed from the UserAgent table (under SIPSignalingGroup) and then submitted for a change.

4390 Tenor reset while changing the ListenPort of SIP UA

The Tenor reset when the listen port of SIP UA was changed and submitted.

4400 Forward Disconnect did not work during Answer Supervision (Analog only)

When an outgoing call was in answer supervision state, the forward disconnect functionality was ignored. This has been resolved.

4422 Tenor sent out wrong number for TON (for Nortel configuration only)

For Nortel configuration only. While sending H.323 calls, the Tenor sent out International as the TON, rather than the configured National. This has been resolved.

P106-12-14

4385 CallerID Generation Altered Ring Cadence (Analog only)

CallerID Generation (type 1) increased the ring cadence (what is sent to the Phone/PBX) by approximately two seconds, which caused certain PBXs to drop the call. This has been resolved.

4394 SIP INFO encode/decode problem

SIP INFO was not being encoded/decoded correctly. When you pressed *, #, or A-D, the digits would not be translated correctly. For example, when a call was made to an Automated attendant and the user pressed the # key, the call would not go through. This has been resolved.

4417 New licensing options

You now have the option to acquire UM integration via a license upgrade. Contact your sales representative and/or price list for more information.

P106-12-12

4337 Tenor unable to retrieve parked call

When a call was made between two Response Point IP phones and the user tried to retrieve the call, the Response Point phone played a fast busy and displayed an error. This has been resolved.

P106-12-11

4338 Auto Provisioning: admin password error

When the admin password was included in the Auto Provisioning configuration file, an error would be displayed. This has been resolved.

P106-12-10

4311 Response Point FXO (AFT) configuration changes

Support and configuration changes have been made for the Response Point FXO. This has been resolved.

4312 CMD Test Command Fails on Response Point units

CMD Test was failing on the Response Point Unit. This has been resolved.

4313 Response Point decode error in INVITE

In an incoming INVITE message, the Response Point decoded the message incorrectly. This has been resolved.

4324 Response Point Device firmware upgrade support

Support for device firmware upgrade has been available has been made available through the Response Point Administrator.

4325 Response Point Changes to support static IP

Changes have been made to the Tenor to support Static IP for the Response Point.

P106-12-09

4303 Response Point Base fails to discover the Tenor

Due to a timing issue, the Tenor was not being discovered by the Response Point. This has been resolved.

P106-12-08

4235 Modify AutoUpdate

For ADP, AutoUpdate has been modified so that UpgradeRelease in the downloaded configuration file is not different than the UpgradeRelease in the running configuration (it will only be different than the firmware actually running on the device). Tenor will download and apply the new firmware from the provisioning server when the following conditions are met:

• The retrieved UpgradeRule is configured
• The retrieved UpgradeVersion is different from its current software
  version
• The retrieved UpgradeEnable is configured
  

4237 ADP: Configuration Resynchronization via SIP Notify

For ADP, the process of configuration resynchronization (i.e. download and installation of a new configuration file) is initiated with a SIP Notify command.

4238 New command enabled immediate resync with provisioning server

For ADP, a new command try resync (available under Auto Provisioning) is now available to enable the Tenor to resync with the provisioning server immediately after the command is issued. The Tenor retrieves the configuration file and resync activity is printed out in the console screen.

4239 Scheduled Resynchronization at a specified time

For ADP, the Tenor now has the ability to resynchronize the configuration files regularly at a particular time of day. The ability to schedule configuration resynchronization outside business hours minimizes the interruption caused by this process. A new field, ResyncTimeOfDay (available under Auto Provisioning) enables the Tenor to resync the configuration files according to the time of day. Valid entry: hh:mm format.

4240 New configuration capabilities via DHCP

The Tenor now supports the following new capabilities:

• Configure NTP servers and offset from UTC via DHCP. In its DHCP broadcast message, the Tenor will request an NTP server IP address and UTC offset. Once these values are received, the Tenor will connect with the NTP server to set its time (without requiring a reboot).

• Auto configure ProfileRule via DHCP. In its DHCP broadcast message, the Tenor will request a Profile Rule. When the Tenor receives a Profile Rule from the DHCP server, the Tenor performs the Auto Provisioning feature (without requiring a reboot).

4261 Response Point Changes

Many changes have been included to support Tenor's interoperability with the Response Point product, including license updates.

4288 DHCP: system kept resetting after getting new IP address

If the first DHCP offer comes from a server more than 30 seconds later, the Tenor kept rebooting. This has been resolved.

4298 Response Point

On a Response Point Tenor, if a user made changes to parameters set automatically by the system, these changes were overwrote upon reset/reboot of the Tenor. These changes should have stayed, despite the reboot. This has been resolved.

P106-12-07

3945 Support of SIP G.729 Codec with annexb=no

The Tenor now supports SIP G.729 Codec with annexb=no. On outgoing SIP calls, when G.729 is used, and VADEnable is disabled on IPRG, the SDP will include annexb=no. In reply, the Tenor will accept G.729 with or without annexb=no. In reply to inbound SIP G.729 calls with annexb=no, the Tenor will include annexb=no.

4015 Redirect Issue for the gateway address

If the Tenor's default gateway was set to one IP, and the network LAN redirected the IP traffic to another gateway address, the Tenor built a dynamic host table for this new destination. Although the initial calls were successful, eventually when there were too many entries in this host table and the Tenor was not accessible via telnet or FTP, and it required a reboot. The network buffers are now increased to support 1800 entries; once the number of entries reach 1800, the entries are deleted.

P106-12-06

4288 DHCP: system kept resetting after getting new IP address

If the first DHCP offer came from a server too late (more than 30 seconds), the Tenor kept rebooting. Improvements in DHCP timing have been made to resolve this issue.

P106-12-05

4261 Response Point Support

The Tenor now supports Microsoft's Response Point.

P106-12-04

4000 MWI support SIP to Q.SIG Direction

MWI support for SIP to Q.SIG direction has been added to the Tenor.

4116 Update Request not Ok'd Correctly

For SIP, when the Tenor received an Update, it was not Ok'd or handled properly. This has been fixed.

4192 CDR broken in case of call fail

For an incoming IP call, SIP or H323, under certain call failures, the Tenor would not properly report CDRs. This has been fixed.

4199 Microsoft OCS - SIP in "from uri" should not have been in uppercase

When making outbound calls from Exchange through OCS, the From URI header contained a URI with "SIP" (uppercase), which caused a decode failure. The Tenor is now able to decode the SIP (uppercase) parameter.

4204 SIP encode and decode failures in Replaces part of refer-to header

With a SIP call, the Refer-to field had REPLACES (uppercase), which caused a decode error. The Tenor is now able to decode the REPLACES (uppercase) parameter.

4205 AT&T Flexreach: decode failure of P-Asserted ID header

Invite messages for both P-Asserted_Identity and P-Preferred-Identity were not being decoded correctly. This has been corrected.

4207 Re-Invite due to session timer was treated as forked invite (SIP)

After a call was established, if the SIPUA sent a session timer re invite, the Tenor treated it as a forked invite and dropped the message. This resulted in UA taking down the call. This has been fixed.

4214 Payload negotiation sometimes failed

G.729 payload was not being set by the Tenor as expected. For example, an incoming payload of 30ms was being ignored sometimes and instead, the configured value of 20ms was being used. Although the rtp streams showed that both endpoints seemed to adjust to 20ms, the voice was not optimum. This has been fixed.

4216 Tenor reset on receipt of Re-Invite

When a call was up in the Tenor and the far end attempted to initiate a transfer, a Re-Invite was sent with a very large SDP. The SDP was converted to the Tenor's internal format and this resulted in the system crashing. The Tenor has been updated to increase its capability to handle a larger SDP size.

4218 Q.SIG Voicemail Interface did not decode proper fields

Q.SIG voicemail interface did not decode proper fields.

4223 Redirect did not pass through diversion reason field

When the Tenor sent an Invite and received a Redirect with a reason in the diversion header, the subsequent Invite had the diversion header, but did not include the reason field. The reason field is now being included in the Invite.

4224 Certain 20-port DSP card manufacturing defects not caught by Tenor AX Manufacturing Test

Some 20-port DSP cards (used in Tenor AX and DX units) have manufacturing defects, but they were not caught by the Tenor AX Manufacturing Test. Although the manufacturing test ran these cards "fine", problems occurred when one of the bad DSP channels was used. Either no dial tone was heard, or the DTMF was not recognized (depending on the nature of the DSP card defect). This problem has been fixed.

4226 FaxNominalDelay default changed

The FaxNominalDelay (available through VoIP Configuration > Fax Profile) default was 600, which caused many fax failures. This has been changes to 200.

4227 On receipt of unattended transfer to a bad number, Tenor disconnected

The Tenor now keeps the original call up in the event of a failed call on receipt of an unattended transfer.

P106-12-03

4206 Circuit switch video calls would not work in Aus and SS7 in Comstar (CMS only)

For circuit switched 'Unrestricted Digital' PRI calls, the video call was not working and for 'static channel connection' in SS7 mode, the links were not coming up. Both of these scenarios were happening when the lines were configured as E1. The problem occurred because the back plane law variable setting was inconsistent with how the Tenor code was using it internally.

A new var_config configuration option ForceBackplaneCompanding0E1T forces the back plane to 0 (E1) or 1 (T1). Set this option to 0 (E1) as a fix for the E1 problems (forces the backplane to be set to E1).

Note: A reboot of the Tenor is required for this change to take affect.

4231 E1 links would not come up when upgrading software

With a DS1 card with E1 and T1 on the same card, when upgrading the software to P106-12-00, the E1's physical layer went down. This resulted from a problem in the DS1 card, and has been fixed.

4246 Multiple contacts in redirect caused call failures

For SIP, if the Tenor received a 3XX response to INVITE with multiple contact headers, the call failed. This resulted in the Tenor sending a subsequent Re-INVITE filled with incorrect information. This has been fixed.

4255 RTP payload name now case selectable (Uppercase / Lowercase)

Previously, the Tenor sent lower case payload names (g729) in the SDP. Some switches only recognize uppercase payload names (G729). As a result, the RTP payload name can now be configured in Upper/Lowercase.

4263 Auto Provisioning parameters did not display correctly

When an XML file was loaded into the Tenor with the Auto Provisioning parameters configured, some of the parameters were still showing as default when a show, show –xc, or show –l command was used. This issue has been fixed.