Release Notes for P105 Maintenance Releases

Tenor Gateways and Call Relays

These maintenance release notes apply to the following products;

• Tenor AS VoIP MultiPath Switch/Gateway
• Tenor AF VoIP MultiPath Switch/Gateway
• Tenor AX VoIP MultiPath Switch/Gateway
• Tenor BX VoIP MultiPath Switch/Gateway
• Tenor DX VoIP MultiPath Switch/Gateway
• Tenor DXi PCIe VoIP Multipath Switch/Gateway (Release P105-19-09 or higher)
• Tenor CMS VoIP MultiPath Switch/Gateway

• Tenor Call Relay 60
• Tenor Call Relay SP

• Tenor Gatekeeper+

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 previous release of Generally Available (GA) software or a maintenance release. They may also add features. Maintenance software goes through limited testing from Quintum, but has been verified as resolved by the customer who identified the 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, P102-11-00 is the latest GA software, then the first maintenance for this software will be P102-11-01.

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 releases that will have been put through full system tests.

We hope that this process will aid our customers by providing fixes in a more rapid manner.

CMS COMPATIBILITY NOTE:

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

See this document for more details:

http://www.quintum.com/support/products/2G/cms/sysdoc/CMS_series2_notice.pdf

The notes below are cumulative since the last GA Release, P105-19-00. The most recent changes are in the top section, the history is similarly in most recent first order.

Known Open Inconsistencies

None

Resolved Issues and Feature Enhancements

P105-19-14

3928 Incoming IP call may reset system (Rare)

In case of an incoming IP call, if the call was connected and disconnected by the termination side first, the Tenor reset. This appeared rarely, when the system was under a heavy load.

3929 Change of Border element IP address may have reset system (Rare)

When the Border Element IP Address was changed from Primary or Secondary in GateKeeperParam, the system reset. This appeared rarely, when the system was under a heavy load.

3930 BorderElement client reset occasionally when it received a URQ message (Rare)

The Tenor reset when a Border Element client received an unregister request message. This appeared rarely, when the system was under a heavy load.

4018 PRI Outbound DNIS was not working properly

The first digit in PRI setup message was being deleted.

4026 Translated ANI resulted in malformed accounting packet

For RADIUS based ANI translation, the length of the attribute used for this purpose had an incorrect value, which resulted in a malformed radius packet.

4047 Request mode message sent unnecessarily

A Request Mode was sent by a Call Relay to its origination side, but the origination side did not respond. The Tenor now sends a request only when a mode change is necessary.

4052 IVR call was aborted when pre-authentication was rejected

For IVRType 2,3, and 11, when IVR pre-authentication was rejected, the IVR call was aborted, rather than the welcome prompt being played immediately for the next authentication.

4065 IVR Multisession key did not work in certain situation

For a PRI to IP call, the multisession key did not work during the ringback.

4073 CLID set to 'P' when ANI has a ' +'

When an incoming call had a '+' in the CLID, it came through as a 'P'. Now, the Tenor strips the '+' automatically and passes the rest of the CLID.

4076 Outbound CID translation did not work without translation table association

Outbound CID translation did not work for outgoing IP calls if the inbound CID translation table was not associated with the outbound CID translation table (through IPRG).

4077 H323 Alternate routing did not generate a stopAccounting

When a GK had a multiple DN registration, the Tenor provided alternate routing in case of an outgoing setup fail, but it did not generate stopAccounting for H323 calls. The Tenor now generates a stopAccounting message for alternate routing.

4083 Relaxing the Decoding of Progress Indicator

If the Incoming Progress IE extension bit was not set correctly, the Tenor would not be able to decode it properly. Decoding for the extension bit has been "relaxed" in the Tenor to allow for flexibility.

4092 FGD not working

When the Tenor routed a call with no DNIS, FGD (Feature Group D) did not work.

P105-19-13

3375 Dynamic population of more information in UserAgentHeader

The UserAgentHeader field sent by the Tenor in the Registration or Invite request, now gets dynamically populated with the User Agent information for the following:

• MAC address
• Tenor's serial number and firmware version
• Value that is set in the UserAgentHeader field (available through the SIPSG).

3545 InBoundAccessLevel and OutBoundAccessLevels did not work for passthrough calls

InBoundAccessLevel and OutBoundAccessLevel configuration did not work for circuit calls (i.e., when a passthrough call or a bypass call was made).

3820 Host Name Support in Port Mapping

For IP Extension/Port Mapping configuration, you are now able to configure a FQDN (Fully Qualified Domain Name) of a DNS rather than an IP address. Two fields, available through the IP Extension tab, support this new feature: RemotePort (5060 for SIP, 1720 for H.323) and IPAddress (IP address or FQDN domain name).

3847 Calling Identity Handling in ISUP (Q.1912.5 P-Asserted-Identity)

SIP message support (Q1912.5) for P-Asserted-Id, P-Preferred-Id and Privacy has been added. The Tenor now generates P-Asserted Identity and P-Preferred Identity headers in INVITE sent for an inbound call. To enable this feature, the parameter SendRemotePartyID field (available under SIPSG) has been renamed CLIHeaderType. Valid values: 0 (disabled), 1 (sends Remote-Party-Id), 2 (Q.1912.5 coded as tel uri) or 3 ( Q.1912.5 coded as sip uri).

3883 T.38 Fax problem

In case of a non-Tenor device calling into the Tenor, fax was detected but H245 negotiation was not handled properly.

3899 End of dial digit '#' not working correctly

End of dial digit '#' was not working for Call Transfer. When the dialed number was terminated using the dial digit '#', the call was not immediately transferred. The calls now transfer correctly.

3941 Wrong Remote IP in CDR when call was routed through Routing Server

The remote IP address was not populated correctly in the CDR when a call was routed through the Routing Server. The IP address is now populated correctly.

3954 IVR multisession key (## or **) interdigit timer was not working correctly

For IVR calls, when the user was prompted "to make another call press the # key twice", and the first "#" was pressed, the interdigit timer did not expire.

3956 Fax fallback with authentication not working

A Tenor that initiated a FAX re-invite would terminate the session without authenticating itself again with the proxy.

3379 ANI translation using RADIUS interface

The Tenor now allows ANI translation to occur within the RADIUS server, and be returned to the Tenor in the RADIUS authorization response message.

3898 SIP calls did not handle internal TCP sockets efficiently

For SIP calls, the Tenor was not handling internal TCP sockets efficiently.

3953 Tenor automated reset schedule now configurable

A new configuration option enables the Tenor to be reset according to an automated reset schedule. The new command AutoReset is configurable through the var_config.cfg file as follows: AutoReset <resettime>. Reset time is in 24 hour format (hhmm) without a colon separating the hour and minute.

For example:

Midnight is entered as AutoReset 0000

1:00 AM is entered as AutoReset 0100

5:15 PM is entered ast AutoReset 1715

Note: AutoReset will not work within 5 hours of a reset. Also, ensure the time is initialized on the Tenor for this feature to work properly (this is done through SNTP; see the Command Reference for additional information).

3971 AnswerSupervisionHoldOff has increased timer (Analog only)

The AnswerSupervisionHoldOff timer option (available through CASSG) has been increased from a maximum of 20 seconds to a maximum of 60 seconds.

3993 IP Route Prefix configuration changed upon reboot

After a Tenor reboot, the value of IPRoutePrefix (available under DialPlan) was set back to the default value 6, regardless of the entry.

3995 Offline/online configuration changed when Tenor was reset

For a PPPoE enabled Tenor, after a reset, the Tenor's configuration changed from online to offline.

3998 Caller ID name was not working in SIP setup outgoing message

The Caller ID name was not working correctly in the SIP setup outgoing messages for NI-2 protocol.

4004 Disable TCP Linger For H323 Calls

A new configuration option will disable TCP Linger for H.323 calls not using the MUX feature. The new option DisableTCPLinger is available through the var_config_cfg file. Enter DisableTCPLinger 1 to disable TCP linger for H.323.

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

P105-19-12

3499 Two stage dialing operation inconsistent

Through different configuration scenarios, Two Stage Dialing worked inconsistently.

3590 Added authentication based upon DNIS in IVR type 9

When you select IVR type 9, there is a new configuration option to enable the Tenor to send the authentication message to RADIUS server based on the DNIS. To enable this feature, configure IVRAuthType 6 (available through TCRG and LCRG). IVRType must be set to 9 for this option to be available.

3708 Autoswitch number not recognized when prefixed with long distance prefix

Intended autoswitch (DID) calls to a Tenor were not being recognized as an autoswitch number if the long distance digit prefixed the DNIS.

3717 IVR interdigit timeout incorrectly forced to 3 seconds when ivrCardLength was not 255

If IVRCardNumLength was not configured at the default of 255, the interdigit timer was always set incorrectly at 3 seconds. This has been resolved.

3723 Added optional PSTN call termination indication tone

A new configurable option has been added to enable tone generation for all PSTN connected calls. Configure this option through the following new field:

CallTerminationINDication (available through LCRG and TCRG). Valid values: 0 (disabled) and 1 (enabled, PSTN Termination).

3739 FXO channels may remain off-hook when PassThrough was set to "Enabled Block of Channels"

When PassThrough was set to "EnabledBlock of Channels", FXO went off-hook immediately, and may have remained off-hook.

3742 Added ability to perform DNIS-based authentication after normalization

When you select IVR type 9, there is a new option for the Tenor to send the authentication message to the RADIUS server according to normalized DNIS based authentication. To enable this feature, configure IVRAuthType 7 (available through TCRG and LCRG). IVRType must be set to 9 for this option to be available.

3748 Tenor DSPs became unavailable when used with Reverse Battery Caller ID

In random situations, the Tenor's DSPs became unavailable when used with Reverse Battery Caller ID. The DSPs got stuck in an "open" state. Even without an active call, the DSPs were not available. The only way to recover would be to reset the Tenor.

3772 Reset may have resulted if ARP resolution failed

A Tenor may have reset in some cases if an incoming SIP call was made to a phone connected to a FXS port and the incoming SIP call was the first call after a reset.

3779 When performing a factory default, 'teltrail.log' is now cleared

The teltrail.log file (which is a log of all configuration information on the Tenor) is now deleted when a factory default is performed on the Tenor unit. As a result, sensitive information (such as passwords) can be purged after a factory default.

3794 Added 'h323-ivr-out' to RADIUS authentication to enhance PortaBilling Interoperability

The "h323-ivr-out" is now included in the RADIUS authentication request. This authentication is now included for IVR types 4, 5 and 9.

3836 Allow SelectNet for IP Trunking Calls from TCRG

A new feature enables SelectNet to work from TCRG to TCRG and via hair pinning through a single TCRG. Use the following new command to enable this feature:

EnableAutoSwitch (available through TCRG). Valid entries: 0 (disabled, default) or 1 (enabled).

3851 Added support for 'ResourcesAvailableIndicate' (RAI) in H.323

A new features is supported on the Tenor to generate the Resource Availability Indication (RAI) messaging. The Tenor will use the RAI messaging to tell the Gatekeeper to which it is registered that it is nearly out of resources. There are two new commands available to support this feature:

ResourceThresholdHigh. Available through GateWay. Defines the maximum number of active calls. When this number is met or exceeded, the Tenor sends a "RAI true" to the Gatekeeper. (Calls over the maximum will be rejected by the Gatekeeper). Valid entries: 1 - 99 or 0 (disable, default).

ResourceThresholdLow. Available through GateWay. Defines the least number of active calls in the gateway. Any calls meeting this number or below, the Tenor sends an "RAI false" to the Gatekeeper. (Call below this minimum will go through successfully) Valid entries: 1 - 99 or 0 (disable, default). This field cannot be set higher than ResourceThresholdHigh.

For example, the fields are set at the following: ResourceThresholdHigh 7 (indicates 7 calls are active in the gateway) and ResourceThresholdLow 5 (indicates 5 active calls in the Gateway). When more than 7 calls are active (resource is used up), the Tenor sends a RAI "AlmostOutOfResource” true. If less than 5 calls are active (resource is available), the Tenor sends a RAI “AlmostOutOfResource" false.

These fields are not available when OutgoingIPRouting is set to 1 (SIP).

3880 Under rare situations the Call Relay SP setup calls with one-way audio transport

In rare situations, and in a specific call flow, the Call Relay set up calls with one-way audio transport. This has been resolved.

3881 Call Relay incorrectly passing GSM codec in SIP SDP in a Reinvite Message (Call Relay only)

The Call Relay received a Re-Invite with GSM and G711 in its SDP list. Although the media was negotiated, the CallRelay was still passing on GSM. This has been corrected for G711 to be passed instead.

3882 Call Relay SP reboot after long period of full load operation (CR-SP only)

The CR-SP with both legs of a call in H323 mode rebooted after a long period of time running at full capacity.

3895 Multiple FIPD attachment caused system reset

After adding multiple Filter IP Directories, attaching them, and submitting, the Tenor would reset, and the entries would not re-appear.

3900 SIP 'Refer' not working if 'Bye' received immediately after '202 Accepted' sent

When the Tenor sent out a 202 Accepted (upon receipt of a SIP refer message that had a new destination number), the call setup successfully, but as soon as the first IP call was cleared, the Tenor had a cause code 41 (Temporary Failure) and the call disconnected.

3904 HND translated event log entry reinstated

The event log of the Tenor indicated that the HDN translation information was missing from the trace. This information has been reinstated.

3910 Security Enhancements for Telnet/FTP

A new features provides security enhancement for allowing only certain access to the Tenor. The new command filtertelnetftp, available through the var_config.cfg, allows Telnet, FTP and GUI access only from the IP address specified, and blocks access from all other IPs.

For example, in the var_config.cfg file, enter filtertelnetftp 192.123.45.11 255.255.255.255. This allows Telnet, FTP & GUI access only from 192.123.45.11 and blocked access from all other IPs.

In addition, the command debug allowdump 1 is used to display the Telnet/FTP/GUI filter IP addresses.

3913 Played wrong prompt when RADIUS return code 7 was received

When Radius returned "Return Code 7" in the authentication response, the Tenor played "Account Expired" prompt. The same prompt was used when Radius returned "Return Code 7" in authorization response. The Tenor now plays out the appropriate response.

3914 Incorrect conversion of H.245 DTMF digits to SIP RFC2833 message insertion

Some devices did not generate DTMF digits when RFC 2833 packets were generated by the Tenor. This happened when the Tenor converted DTMF digits received as H.245 messages to RFC2833.

3948 EPAD SourceCallSignalAddress Security Problem

Calls were being authorized even if they did not arrive from an IP address in the EPAD's allow list. Instead, the Tenor would use the IP address from the allow list set in the SourceCallSignalAddress element of the SETUP H.225 message. This has been resolved.

3959 Added Call Throttling Origination IP Address to event log

If a call was throttled due to exceeding certain limits, the exception that was logged in the event log did not log the IP address or the origination of the call.

3962 Generate ringback tone in slow-start H.323 call setup procedure

Tenor did not generate ringback tone for an incoming slow-start call. Tone was not generated because of an issue with the media ports.

3974 Remote Party ID Privacy value always set to "full"

The RPIDDefaultPrivacy (available through SIPSG) field was always set to "full", rather than the setting configured.

3975 Incorrect calculation of Gatekeeper port usage versus license

Calls were dropped when there was a discrepancy between the Gatekeeper port usage and the Gatekeeper license port. This discrepancy has been cleared.

3984 Callers Hearing Busy Tone Before Connect

Sometimes, the caller would hear a busy tone on a normal call before the call was connected.

3986 SIP Notify Message may have caused Memory Leak

When the Tenor received a SIP notify message, it caused a memory leak.

3987 Call Relay 60 data alignment problem with media loopback causing reset

Note: This problem did not apply to Tenor CMS or Tenor CR-SP.

The Tenor would reset under certain situations because of an internal media loopback problem.

3990 Incorrect data displayed on active 'call' output

When the system booted up and a cmd call was executed, incorrect data may have shown in the display.

P105-19-11

3569 RTP Packet Validation

A new method changes how the Tenor validates RTP packets. Previously the Tenor looked at the SSRC value and only accepted RTP packets with a matching SSRC value (the var_config parameter was disableSSRCcheck 1, which has been removed). The new method looks at the peer media IP and port given in the signaling messages for a particular call and compares it to what is subsequently received from incoming RTP packets. Packets with mismatching Port or IP are discarded. A new parameter, RTPValidation (available through the var_config.cfg file), enables you to enable or disable the applicable ports.

Valid options:

0 - Check SSRC (does not check IP or port)
1 - disabled (SSRC & IP/Port check turned off)
2 - default (IP and Port checking enabled)

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

3591 Did not allow 'replaces' tag in 'Supported' and 'Required' SIP headers

For SIP headers, the Tenor was not accepting Require and Supported headers that have the option tag "replaces" in it, and the Invite was rejected.

3592 Improper global call pickup handling

The global call pickup handling feature was not working correctly.

3638 Unable to delete configuration parameters containing a space character via the CLI

The user could create a name containing a space through the CLI, but it could not be deleted. For example, when a new TCRG was created with the name "chn test" (containing space) as follows new tcrg "chn test", this new name could not be deleted.

3641 Description field under Radius Servers discarded strings ending in a space character

By default, the description field under Radius Servers contains a name with a space. When this name was configured through CLI with a space in between, the Tenor accepted only the 1st string and discarded the string that was followed by a space.

3767 On-hold music not set up correctly

The music to be played when a caller was "on hold" was not set up correctly.

3817 SSG events caused reset

Due to a memory leak, on a fully loaded system, the SSG may have reset.

3819 Allow Japan NAVI dial (0570-0xxxxxx) calls

In Japan (BRI NTT user side), outbound calls to NAVI dial (0570-0xxxxx, numbers which can be dialed from anywhere in the country) failed.

3822 Improper handling of Channel Group names containing spaces

If spaces were used when creating a new Channel Group name using the Tenor Configuration Manager, when the Tenor is rebooted, the channel mapping did not work correctly.

3835 RPID not being passed on H323 to SIP calls

RPID was not being passed on inbound H323 calls or translated through to SIP correctly.

3859 Enhanced Tenor GUI Reset log message

Enhanced log messages can now be displayed for when the Tenor is reset from the Configuration Manager or auto provisioning. These messages include the "source" that causes the Tenor to reboot.

3860 RADIUS does not report new Tenor IP acquired by PPPOE mechanism

If PPPOE changed the Tenor IP, the Radius module did not obtain the new IP until the Tenor was rebooted.

3862 Caller ID detection failed under rare condition

A rare problem appeared where Caller ID was not detected from the PSTN side. This has been verified that Caller ID is now working correctly.

3865 An HND object containing a space character lost its configuration

When a new HND contained space characters (i.e., new hnd "PSTN LD"), the data would be lost and the Tenor would reboot.

3875 Unconfigured Tenor yielded error message upon startup

In a new Tenor unit, when the "i" was select to configure the Static IP address, the following error message was displayed: arptnew failed on 7f000001.

3878 Modified SIP restricted caller ID handling for better OCS Interoperability

There are two changes in the Tenor to improve OCS interoperability:

On incoming PRI calls with PI set to restricted, the anonymous URI is sent.

On outgoing calls to SIP, if there is no caller id (either not present on incoming calls or removed by configuration), and the CLIHeaderType is set to either 2 or 3, the Tenor sends "unavailable" rather than "anonymous". This configuration can be changed through setting "SIPMissingCIDURI xxx" in the var_config.cfg.

P105-19-10

3796 Tenor DXi Manufacturing Test Enhancement

Added support for proper LED handling to reflect the pass/fail status of the Tenor DXi Manufacturing test including the PCIe bus test. Also, enabled test operation using the Tenor DXi in a manufacturing test fixture instead of a PC environment.

3863 Improper Memory Management For Certain SIP Response Messages

Resolved an issue whereby receive SIP response message processing may have resulted in the improper deallocation of memory buffers. In particular, reception of a response message containing code 181 (Call is being forwarded), caused this condition.

P105-19-09

3852 Improper SIP TCP Socket Management In Certain Error Cases

The Tenor gateways would improperly deallocate network sockets when certain error cases in the normal call flow occurred. This would have eventually resulted in the depletion of network sockets, and the inability of Tenor to process new calls.

3853 Buffer Leak When Using TCP SIP Authentication

The Tenor gateways would deplete 1K memory buffer pools when SIP authentications would take place using TCP transport. Certain 1K memory buffers allocated to receive SIP message processing were improperly being deallocated.

P105-19-08

3636 Facility Message Resets Digital Tenors Using IVR

Tenors DX and Tenor CMS gateways would reset if an ISDN Facility Message was received by the Tenor for a call which was currently being handled by the built-in Tenor IVR function.

3718 Modified H.245 Terminal Capabilities Set Encoding

Modified the Maximum Frame per Packet encoded in the H.245 Terminal Capabilities Set (TCS) to reflect the currently configured values, rather than the maximum that the Tenor can support. This change resolved certain interoperability issues which could have resulted in improper media stream setup.

3839 SIP Cancel Message Processing Causing Hanging Calls

Resolved hanging SIP calls caused by a SIP Cancel message received from the origination side. The processing of this SIP Cancel message resulted in depletion of system memory and hanging SIP calls in P105-19-06 and P105-19-07.

3843 Tenor Monitor Interoperability

The Tenor gateways would reset when using the Tenor Monitor to monitor the gateway. This was caused by incorrect handling of the query for active alarms that the Tenor gateways received from the Tenor Monitor.

3845 TCP SIP Bye Transaction Timeout Socket Leak

Resolved a problem related to a SIP Bye transaction processing using TCP transport. If a timeout were to occur while waiting for the transaction to complete, a TCP socket leak occur when the Tenor attempted to resend the message.

P105-19-07

2526 Call Routing Server SIP Calls

For an originating SIP call with the Call Routing Server, the Tenor will look up its configured SIPSG's for an IP Address matching the Call Routing Server response, in order to determine the applicable SIP parameters to use for the call.

3645 ISDN cause code '44' SIP Mapping

Mapping of ISDN cause code '44' (Requested channel/circuit not available) to a SIP failure code has changed. In prior releases, cause code '44' mapped to a SIP '601 Busy' response. Tenor now maps this cause code to a SIP '503 Service Unavailable' response.

3721 QOS/DiffServ tagging for Call Signaling

All H.323 and SIP signaling packets are now tagged with a configured ToS/Diffserv value. Previously, only media packets were tagged (not signaling). The Tos/DiffServ value used to tag signaling and media packets is now configured in the MediaQOSValue attribute in the default IPRG. A gateway reset is required for the new setting to take effect.

3763 New FXS/FXO hardware revision identification

The manufacturing test has been modified to be aware of new revisions of FXS/FXO hardware, and respond appropriately.

3791 Random CallRelay 60 Resets

Random resets occasionally seen in the CallRelay 60 product in certain environments have been resolved.

3796 Manufacturing test support has been added for the Tenor DXi

Support for a new product, the Tenor DXi PCIe Adapter, has been added to Quintum's manufacturing test routines.

3813 Random Tenor CallRelay 60 H.245 Resets

Random resets related to reception processing of H.245 packets has been resolved.

3816 Network Buffer Resource Depletion

Packets sent to unallocated Tenor UDP/RTP ports, would cause eventual Tenor network buffer resource depletion. Over time, this would cause the Tenor not to be able to generate or receive network traffic, and thus appear to hang. This problem has been resolved.

3818 ISDN Cause Code '88' to SIP mapping (Microsoft Interoperability)

A modification has been made to the ISDN cause code to SIP message mapping to enhance interoperability with Microsoft Office Communication Server 2007 (OCS). ISDN cause code '88' now maps to a SIP response '400 Bad Request', instead of '503 Service Unavailable' in previous releases.

3821 Tenor CMS and Call Relay SP Web Server (port 8080)

In certain circumstances, the Tenor web server would incorrectly close network sockets in a Tenor CMS or Call Relay SP, occasionally causing a system reset. This problem has been resolved.

3826 Tenor DX failure to boot

Tenor DX would fail to boot if a configuration database was manually loaded onto the DX, which resulted in a mismatch of the database versus actual DS1 hardware installed in the product. This problem has been resolved.

3827 Single DS1 Span License for Tenor DXi

The product feature license mechanism has been extended to allow for the licensing of a single DS1 span. This is required to support the new Tenor DXi PCIe Adapter product.

3828 CNG Fax Tone Detection When Using G.711 (Microsoft Interoperability)

To enhance interoperability with Microsoft Office Communications Server 2007 (OCS), CNG Fax tone detection is enabled when using the G.711 codec. This is in addition to the existing CNG tone detection which currently exists for when using low bit-rate codecs such as G.729 and G.723.

3838 Call Routing Server and IVR Multisession Incompatibility

When using IVR Multisession with the Quintum Call Routing server, the second call, if any, would fail. The CMS sent stop accounting to the Call Routing Server after the first call, which caused the Call Routing Server to reject any additional Route requests for that session. This problem has been resolved.

P105-19-06

3423 Multipath Call Failure to FXO Configured For Busyout

A multipath call failure happened when a fallback to an FXO port was configured for Busyout. Previously, Multipath calls would not complete when outbound calls were attempted on a FXO port in a Busyout state.

3423 Tenor DXi PCIe Adapter Support

Support has been added to the Tenor software to recognize and support the new Tenor DXi PCIe Adapter product line.

3665 Expanded 'show -v' version number field

The format of the show -v CLI command output has been changed to allow for longer version numbers.

3713 Normalized Number Printing in Nortel Call Flow

Normalized number printing in event logs and CDR records did not not correctly handle non-NULL terminated numbers which can be encountered in certain Nortel call flows involving SIP redirect. Non-Null terminated normalized numbers did not print correctly.

3714 Increased SIP Stack Size for Tenor AS/AF/AX/DX/BX

The size of the SIP task stack has been increased for Tenor Enterprise Gateways (Tenor AS/AF/AX/DX/BX), and CallRelay 60 product lines.

3759 Remove '+' from Incoming DNIS (Microsoft Interoperability)

To enhance interoperability with Microsoft Office Communication Server 2007 (OCS), the Tenor will strip off the leading '+' character in the DNIS number received in incoming SIP INVITE messages from OCS.

3731 Outbound Caller ID Translation Problem

Corrected a malformed Caller ID Information Element which may have occurred when no Outbound Caller ID Translation was configured in a 'CallerIDXlationDirectory' attached to a TCRG or LCRG. The outbound Caller ID is now correctly formed regardless of the Outbound Caller ID Translation Directory configuration.

3760 Multiple Transactions with TCP SIP Signaling

Correctly supports multiple SIP transactions which may occur over a single TCP connection. Previously the TCP socket was erroneously and prematurely closed.

3762 DS1 E1 Transmit Pulse Template Adjustment

Adjusted hardware parameters to meet E1 Transmit Pulse Templates when using newer revision DS1 Framer / LIU.

3766 Changed Default SIP Failure Response

To enhance interoperability with Microsoft Office Communication Server 2007 (OCS), the Tenor will default to a SIP '404 Not found' response for any ISDN cause code which is not represented in RFC 3398. In prior releases, Tenor would have sent a SIP '603 Decline' response.

3778 CID Translation Memory Optimization

The amount of memory required for internal Caller ID Translation structures has been optimized.

3780 BRI Q.SIG Facility IE Reset

Resolved an intermittent problem whereby the Tenor BX could reset upon receiving a Q.SIG message which contains a Facility Information Element (IE).

3782 DNS Library Optimization

Modified the DNS library to use mutual exclusion methods which have less impact on system performance.

3788 CallRelay SP with H.323 Reset

In certain traffic conditions, the CallRelay SP may have reset when processing H.323 calls. The buffer pools that the Memory Manager uses have been optimized to eliminate the condition which causes a reset.

P105-19-05

3726 Fax Relay setting did not work correctly

Using both SIP and H.323, the Fax Relay feature was not working correctly. Settings 2, 3, 4 and 5, and different combinations of them did not work properly. This has been resolved.

3737/3768 Proper 200 OK not created when call was connected

For a PBX to PSTN call, the Tenor never sent the proper 200 Ok message when a call was connected.

3743 Packet Saver feature not working correctly

PacketSaver was not working correctly. Some calls were disconnected because of the issue. This has been resolved.

3746 SIP modem calls not working under specific configurations

In a few cases, SIP modem calls were not working under specific configurations. Now, SIP modem calls are working correctly.

3754/3769 Tenor reset if Call Waiting feature was enabled

In certain situations, the Tenor would reset if the Call Waiting feature was enabled. This has been resolved.

3773 Background noise heard on Tenor

In a certain situation, background/white noise could be heard on the IP phone call when the user spoke. This has been resolved.

P105-19-04

3709 If Caller ID generation was enabled and no Calling Name, the Tenor reset

If Caller ID was enabled, and a call was made without a caller name, the Tenor reset. This has been resolved.

3619 Support for Dialing a Pause Character

A new feature sipTSDPauseLen (available through var_config.cfg), enables the Tenor to support the "p" character in the SIP invite as a pause character. With this feature enabled, incoming SIP calls are processed to use the pause character, and wait the pause length in seconds.

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

3706 Autoswitch event was initiated for all calls between Tenors

When auto switch was configured, it was triggered after 2 seconds, regardless of whether there was packet loss in the network. This has been resolved.

P105-19-03

3710 Memory report not accurate

The memory module was not reporting memory correctly. As a result, the memory would have not been used correctly and the Tenor would have eventually crashed. This has been resolved.

P105-19-02

3544 Encoded characters not working correctly

For SIP messages, the Tenor did not decode the escaped sequence in the "To" field of the INVITE message.

3585 Non-numeric digits are now supported

On outbound SIP calls, digits other than 0-9, *, # and + are now supported.

3618 SIP messages sent in Upper and Lower Case

In order to interoperate with the certain servers, the Tenor will now send out SIP messages in upper and lower case (rather than just lower case).

3623 Added software support for new NO FAILOVER (-NF) FXS cards

Analog Multipath units are now available with a new feature to failover to PSTN during a power failure (for security reasons).

3666 Low speed modem (credit card machine) support

In certain situations, credit card machines were using low speed modems (2400 baud) and their calls to the modem service provider were failing. This has been resolved.

3703 Resource leak when using TCP caused problems

Due to a resource leak, some Tenors would lose IP connectivity after a number of days, and would need to be reset. The resource issue has been corrected.

3704 No voice path for incoming SIP call using Alias Name (instead of DN)

If a call came into the Tenor using SIP protocol, and if the Called Party was an Alias Name (instead of a DN), it gets connected, but there was no voice path in both directions. This has been resolved.

P105-19-01

3529 Incoming PRACK triggered second Call

An incoming PRACK launched a second call to the PBX side. A work around would have been to disable PRACK. This has been resolved.

3566 Remote Party ID header could not decoded as name only

The Remote Party ID header has been changed to support a name only parameter.

3578 New Caller ID type prefixed by the NDD

The Caller ID received from the PSTN is now prefixed by the NDD (National Prefix) based on the TON in the ISDN setup message. A new Caller ID type 5 is available through the TCRG only.

3646 Certain IVR fields were not working correctly

The IVRCardNumLength and IVRAccountNumLength fields (available under TrunkCircuitRoutingGroup, LineCircuitRoutingGroup and IPRoutingGroup) were not accepting the correct number of digits. This has been resolved.

3651 Transfer/refer could cause UDP ports to be used up

A call was not being properly brought up and transferred.

3652 Codec type change after many hold/off hold sequences

After several hold/off hold sequences, the Tenor ended up using codec type G.723 for a call that was supposed to be using codec type G.711. The Tenor now uses the correct codec.

3670 Using certain Tenor port would cause the unit to crash

Using port 9001 would cause the Tenor to crash. Now, using port 900 works as expected.

3675 Incoming SIP calls with + prepended could cause calls to fail

When a SIP call came into the Tenor with a '+' prepended, (i.e., the Tenor using +91442031), the call would fail to route over LCRG/TCRG.

3683 When a Caller ID was missing, an outbound SIP populated the From field with invalid identifier

On outbound SIP calls, if a caller id was missing, the From header field was populated with the wrong identifier.

3684 Outbound PRI calls passed non-numeric caller ID in the calling party IE

Non-numeric caller IDs were passed in the calling party IE.

3685 Retry 1+ calls without 1 on failure (PRI only)

In some geographic areas, calls to certain local exchanges must be dialed without a 1. Previously, when these calls were dialed with a "1", the call would not go through successfully and be returned with a cause code. A new feature enables these types of calls to be automatically "retried" without the 1. This feature LocakNxxRetry is available through the var_config.cfg file which enables you to set the value of the cause code being returned. Valid options: LocalNxxRetry (followed by the value of the cause code being returned).

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