Page tree
Skip to end of metadata
Go to start of metadata

Tenor Survivable SIP Gateway (SSG)


S108 Maintenance Release Notes

This document lists all software fixes for the following VoIP MultiPath Switch/Gateway products running maintenance software S108-09-38 (SSG or "SIP Survivable Gateway") and previous.

Products Affected

Analog Gateways

  • Tenor S AX
  • Tenor S AS
  • Tenor S AF

Digital Gateways

  • Tenor S BX
  • Tenor S DX

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

Upgrading to Tenor S Software from Standard Gateway Software

The Tenor S (survivability) software runs on many of the same hardware platforms, but 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 S108 software from P10x software. This will ensure proper defaults, good security and the best operating behavior.

Also, note that a license upgrade is required to use survivable software. Survivable software (prefixed with an "S", such as S108) 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.


  • The Tenor-S AX, Tenor-S AS, Tenor-S AF, Tenor-S BX, and Tenor-S DX running S107-xx-xx interoperate with Tenor Configuration Manager, CM108-10-00.
  • The SSG interoperates successfully with several IP PBXs and soft-switches, such as Avaya, Broadsoft and Asterisk.
  • The following proxies have incompatibility issues with the SSG: SER, Ondo and ININ.
Table of Contents

Resolved Issues/Feature Enhancements


Tenor-55 Under View Menu changed menu item name "Whole Database" to just "Database"

In the Tenor Configuration Manager, under View, the sub-menu option "Whole Database" has been renamed to "Database"

Tenor-58 After Tenor Factory Reset, Wizard takes too long to launch

After Tenor Factory Reset, the Wizard took too long to launch. This has been resolved.

Tenor-67 Tenor Config Manager: Add Test Call, Test Dial Tone and Test Line Monitor CAS diagnostics commands

Previously, the ability to perform diagnostics on the CAS Lines with Test call, dial tone, etc., was available only from the CLI. These commands are now available from the Tenor Configuration Manager, as follows:

CAS Signaling Phone (FXS Ports)

A new tab "Diagnostics" has been added, which includes the following new command:

  •  Test Call: Attempts to ring the phone connected to the specified FXS port.

CAS Signaling Line (FXO Ports)

A new tab "Diagnostics" has been added. This tab includes the following new commands:

  • Dial Tone Test: Performs the dial tone test on the specified FXO port.
  • Calibrate Line: Performs the line calibration test on the specified FXO port for the impedance specified (Analog Specific Tab) or for All Impedances.            
  • Test Call: Performs a test call on the specified FXO port using the phone number specified with the command.
  • Monitor Line: Starts to Monitor the specified port and after stopping the test, will report the Voltage and Current observed on that port.       

Tenor-68 GUI: Added ability to receive event logs from Tenor Configuration Manager

A new button Event Logging has been added to the Tool Bar.  Event Logging enables logging for Call Handler (ch), Analog/Digital CAS (cas), and SIP protocol modules. For each module, three levels of logging are offered: BasicDetailed or Verbose. The event logging buffer can be cleared with the Clear Logs button. After performing test calls, click on "Retrieve Logs" to view the event logs.

Tenor-75 Tenor Configuration Manager Displayed Un-Authorized (under Basic View), when refresh was clicked multiple times

 Under the Basic View, when refresh was clicked quickly multiple times, an Un-Authorized error message was displayed. This has been resolved.

Tenor-76 Tone Profile settings not used to disconnect signal

When the Progress Tone Country was configured to 19 (Germany) in the ProgressToneCountry.xml, the Tenor did not honor the configured Tone Profile for disconnect tone, but instead forced a single frequency tone of 425 Hz with 1000ms on and 4000ms off. The Tenor now uses the tone profile settings in the ProgressToneCountry.xml file.

Tenor-77 SIP Configuration - Added prepend PLUS Configuration to CLI and GUI

Previously, for SIP Calls, the Tenor could be configured to send a '+' in front of the Called or Calling number via a setting in the 'var_config.cfg' file. This can now be configured in the SIP Signaling Group.

Tenor-80 Added a configuration for List of Endpoints allowed to communicate with the Tenor

Previously, the filtertelnetftp command, which blocked Telnet and FTP access into the Tenor, was available only by specifying the allowable source IP's defined in a var_config file. This feature is now configurable under the Filter IP Directory.  A new configuration option Access Mode has been added for each Filter Ip. Access Mode has two options: Call Access (default, only those endpoints can make VoIP calls with the Tenor) or Management Access (only those end points can have FTP access to the Tenor, and manage the Tenor via Telnet and Tenor Configuration Manager).

Tenor-82 Varconfig gDNSCacheRefreshInterval is now configurable item under DNS Server

The DNS Cache Refresh timer feature was previously implemented using varconfig gDNSCacheRefreshInterval. This feature can now be configured under DNS Server configuration via CLI and Tenor Configuration Manager.

Tenor-83 Varconfig DNSLoadBalance is now configurable under DNS Server Config

The varconfig DNSLoadBalance (DNS Load Balancing feature) is now configurable under DNS Server configuration via CLI and Tenor Configuration Manager.

Tenor-84 Varconfig SipUserPhone is now configurable under SIP Sig Group Config

The varconfig SipUserPhone command (on outgoing Invites, the Tenor turns on/off user=phone in ONLY the RequestURI and To headers) is now configurable under SIP Signaling Group as user=phone in URIs, with the following configuration options: 

    •  No. No user=phone in any SIP URI (default).
    •  All URIs. User=phone in all SIP URIs.
    •  Request URI, To Header. User=phone in the Request-URI and To: header of an Outgoing Invite.

The varconfig SipUserPhone is no longer used.              

Tenor-89 CLI command "cmd sip resolve" added into Tenor Configuration Manager 

The CLI command cmd sip resolve (performs DNS resolution for a specified FQDN) is now available in the Tenor Configuration Manager (via View > Tenor Status/Info).

Tenor-94 Added the "echoTailSize" parameter into the GUI and CLI

The DSP Echo Tail Size parameter (for optimizing echo cancellation) is now configurable in the Configuration Manager (via Gateway) as Echo Tail Size (in msec). The echoTailSize options include: 128, 64, 32, or 16 msecs.       

Tenor-95 Bypass Filter-IP for all Statically configured Servers in the Tenor

When a list of allowed IPs was configured under Filer IP Directory, the Tenor would exclude filtering out IPs that were configured in the Tenor for DNS Servers, CDR Servers, SysLog Servers, Radius Servers, etc, so that the user does not have to explicitly configure them again in the Filter IP list.

Tenor-97 Basic Config – Improve Call Status view layout / info

In the Tenor Configuration Manager, the call statistics information (via Basic Config> Basic Status> Call Status) has been improved to be more intuitive.

 Tenor Configuration Manager - required a "Right" click first before a user was allowed to "Left" click to create a group or new entity

When switching the menu with a Right click, you would need to right-click once again before the content menu was displayed. This has been resolved.

Tenor-100 Rename the "Filter-IP" Directory to Allowed Access List

The Filter IP (for white list) has been renamed to Allowed Access IP for consistency.    

Tenor-101 Filter-IP: Could not ping Tenor via configured broadcast IP's

When an endpoint's IP was configured under the Filter IP (Allowed Access IP, previously Filter IP) with Management Access, the Tenor could not be pinged. This has been resolved.

Tenor-106 Tenor GUI - Remove Menu items for viewing draft database in the Tenor

Under Configuration Manager View> Database, (previously View> Whole Database), all options for viewing the draft version of the database have been removed.

Tenor-107 Version Info was not shown when displaying working db via CLI or Configuration Manager 

The Tenor version information was printed at the end of sh -l command but not for the sh -w-l command. This has been resolved.   

Tenor-109 Ribbon re-branding of Tenor's GUI

The Tenor Configuration Manager has been rebranded for Ribbon.

Tenor-110 Change Field name Destination in Allowed Access IP (TENOR-80, TENOR-100) to Allowed Access IP Allowed IP Address

Under Allowed Access IP (formerly Filter IP), the field name Destination for the end point IP has been renamed to Allowed IP Address, to be more intuitive.                     

Tenor-113 Tenor did not sent digit to FXO on DNCM match after enabling local routing with routing table

When Use Routing Table and Enable Local Routing are enabled, and a DNCM configured for a FXO port, when the call was made from the FXS and the DN matches the FXO port's DNCM, the Tenor did not dial out the DN from the FXS (when the call was placed on the matching FXO). This has been resolved.  



Tenor-45 New CAS Diagnostics Commands added to Tenor Configuration Manager

In the Tenor Configuration Manager, a new Diagnostics tab panel has been added under Cas Signaling Group Line with the following four options: 

  • Calibrate Line - Calibrates the line. Click this option to enter the FXO line number in which the calibration will be completed. Two Impedance options are available: Configured Impedance (calibrates for the Impedance value set in CAS Signaling Group-line >Analog Specific) and All Impedances (calibrates for all possible Imepedance values).

  • Dial Tone Test - DIal Tone Test is performed on the FXO line. Click this option to enter the FXO line in which the Dial Tone Test will be completed.

  • Test Call (FXO or FXS) - Manually initiates a test call on the FXO or FXS port. Click this option to enter the desired FXO or FXS line number and a phone number to dial out. The Tenor then attempts an outgoing call on the chosen FXO or FXS line with the specified destination number.

  • Monitor Line - Monitors the signal levels on the FXO line. Click this option to enter the desired FXO line number. The Tenor then continuously monitors the signal on the FXO port until the user terminates it from the Configuration Manager.


Tenor-29 Names for several Configuration options have been changed

In Auto Provisioning (available through System-Wide Configuration> Auto Provisioning), several configuration options in the Configuration Manager have been updated to the following names:


Table : Configuration Options - Updated Names

Original Configuration NameNew Configuration NameDefinition
Profile RuleProvisioning Server URLURL of the Tenor Configuration File Location
Provision EnableProvisioning ProfileSpecifies how to apply the configuration
Provision Error PolicyError Provisioning PolicySpecifies how to handle errors (if any) when the configuration is applied
Forced Resync DelayResync Reset DelayForces delay before resetting the Tenor, in seconds
Upgrade RuleSoftware Location (Server URL)URL of new Tenor Software file location
Upgrade EnableEnable Software UpgradeIf enabled, upgrades to "Software Version" by TFTP from "Software Location"
Upgrade Error Retry Delay (in sec.)Error Delay (in sec.)Forces this amount of delay time before the Tenor re-tries to retrieve the file
Upgrade ReleaseSoftware VersionSpecifies the version to which the Tenor should upgrade
Allow New Calls in Forced Resync DelayAllow New Calls in Resync DelayEnables/disables whether new calls are allowed in the Tenor

Tenor-31 Resync on Reset command added new option

The Resync on Reset option (available through System-Wide Configuration>Auto Provisioning> General) has been updated to include a drop down list whch includes the following:

    • Disabled
    • After Every Reset
    • After Next Reset Only

Tenor-33 Option added to Auto Provisioning to manually sync the Tenor on demand

Auto Provisioning has a new option (available through the CLI and Configuration Manager) which enables you to manually sync the Tenor on demand.

For CLI: The command cmd apsync has been added.

For Configuration Manager: The Sync Now button (available through Auto Provisioning> General) is available only if:

    • The Tenor release is P108-09-33 and higher. 
    • The Provisioning Server URL field is not empty.

Tenor-35 Commands added to generate db.xml without Auto Provisioning items

New commands are added to view the db.xml files in draft and permanent forms (for the Configuration Manager and CLI).

For CLI:
    • sh -xml -noap
    • sh -w xml -noap

For Configuration Manager:
Commands are available through View>Database: Draft Version in XML (no AP) and Permanent Version in XML (no AP).

Tenor-40/Tenor 41 Default Values updated for Auto Provisioning

The following default values (located in System-Wide Configuration> Auto Provisioning) are updated for Auto Provisioning.


Table : Auto Provisioning Default Fields

 Original Default ValueNew Default Value
Provisioning ProfileOnly for setting Auto Provisioning parameters; Ignore all others

Apply retrieved file on top of current DB; Reset Tenor if necessary

Resync on ResetAfter Every Reset OnlyAfter Next Reset Only
Resync Periodic86400


Note: When this field is set  to "0", a periodic resync will not occur.

Tenor-42 For Auto Provisioning, update to Profile/Software Upgrade URL required reboot

For Auto Provisioning previously, if a URL was newly configured for a Profile or Software Upgrade, the Tenor required a reboot for this change to take effect. Now, these changes take effect dynamically and do not require a reboot.

Tenor-43 For Auto Provisioning,  Supplementary Rule integrated into Software Upgrade

For a software upgrade, you are now only required to specify a URL of the folder which contains all the Tenor files required for upgrade (tnrsys.bin and all supplementary files). The SupplementaryRule URL field as now been integrated into the Software Location (Server URL) function (available System-Wide Configuration> Auto Provisioning> Auto Software Upgrade)  and is no longer required as a separate URL.


Tenor-44 Progress Tone for New Zealand has been added

Support for the Progress tone for New Zealand has been added.

Tenor-50 - For Auto Provisioning, configuration has been simplified

To simplify Auto Provisioning configuration, the ResyncAfterUpgradeAttempt command has been removed. 

Tenor-54 For FXO Line Test, CMD test did not exit process if an error occurred

The cmd test command performs line calibration or dial tone tests, etc. on the FXO ports. When this command ran and an error resulted (i.e., no dial tone detected or a DSP could be allocated), the test task continued to run in the background. As a result, when the command was run again, an error indicated that the test process was still running. This has been fixed.



4930 SNMP - Tenor AXT/AFT did not return active calls or active channels in certain situations

The Tenor AXT/AFT models did not return active calls or active channels when being queried by the SNMP server. This has been resolved.

4931 SIP Session ID and Session ID changed but version in SDP stayed the same

The Tenor changed the Session ID, while leaving the version number unchanged in the SDP between the 180 ringing and 200 OK responses to the INVITE. This was treated as non-compliance by the TSS, and the call was dropped. This has been resolved and the call is now compliant with the RFC for SDP Session ID and Version Number.

4932 SDP changes in ACK messages were not processing for calls going On Hold 

Tenor did not process any SDP changes for calls that were going On Hold (if the SDP changes coming from the IP-PBX / SBC were in the SIP ACK message). As a result, calls were not re-sent out properly after receiving a Music on Hold. This has been resolved.

4933 Modem Bypass setting in LCRG/TCRG was unable to be set when "New Routing" was enabled

When "New Routing" was used in the Tenor, the user was unable to enable/set the Modem Bypass setting to 2 (MoIP) in the LCRG. This setting was restricted and could not be accessed via Configuration Manager or Command Line Interface (CLI). This has been resolved.

4934 Tenor was not interpreting absence of "a=" media direction field

When the peer side put the Tenor on Hold and later sent a Re-invite without the "a=" media direction field, the Tenor did not interpret the absence of the direction field in SDP as a sendRecv. As a result, the call had one way audio. This has been resolved.

4935 Factory default setting for G729 codec's payload size was changed

If a new G729 codec was added or an existing G729 code was changed, the payload size setting defaulted to 40 ms.The default has been changed to 30ms.

4936 Time Server IP in DHCP offer causes the Tenor to reboot continuously

During the boot up / DHCP IP assignment process, if an NTP Time Server IP Address was configured, it caused the Tenor gateway to get stuck in a reboot cycle. This has been resolved.

4937 Caller ID detection issue with the  PSTN Line

PSTN lines connected to the Tenor’s FXO ports were not detecting Caller ID. This has been resolved.

4938 New configuration item in SIP Signaling Group

To enable a Tenor to negotiate for a ReInvite that puts the Tenor on hold, a new configuration option Negotiate Media in Hold Reinvite (check to negotiate media; uncheck to disable negotiating media) has been added to the Configuration Manager under SIP Signaling Group> Advanced Tab. This configuration field was previously included in the varconfig as sipNegotiateMediaInHoldReInviteas (see 4925).

Click the field to enable/disable: Check (Enables a Tenor to negotiate negotiate media when it receives a ReInvite that put the Tenor on hold) or Uncheck (Disables Tenor from negotiating media when it receives a ReInvite that put the Tenor on hold).

4939 EnableLocalRouting configuration item displayed when New Routing was not used

Configuration parameter EnableLocalRouting was displayed even when Routing Table was not used. The EnableLocalRouting field must be displayed only when Routing Table is used. This has been resolved.

4940 New configuration item in Gateway  

To support Direct SIP Enhanced Gateway in support of Microsoft® Lync™ Server 2010 deployments, a configuration option Lync Interworking (check to enable Tenor to drop short packets, such as STUN and comfort noise; uncheck to disable Tenor from dropping short packets) has been added to the Configuration Manager under Gateway. This configuration item was previously included in the varconfig as lyncInterOp (see 4874). In order to use a Tenor in a Lync Environment, the field must be checked.

Click the field to enable/disable: Check (Enables a Tenor to drop short packets, such as STUN and comfort noise) or Uncheck (Disables Tenor from dropping short packets, such as STUN and comfort noise).

4942 SIP Trace: Inconcistent output format of SIP messages

In SIP Trace (sproto), some SIP messages (i.e., Invite, 183, 180) were formatted by indenting to the right while some other messages (i.e., Trying, Cancel) did not have the same formatting and indentation.This has been resolved.

4943 Evlogsys now configurable in Configuration Manager and CLI

The varconfig evsyslog command is now configurable in the Configuration Manager and CLI; this command is used to control sending evlog output to the Syslog Server. Configure the command as follows:

  • In Configuration Manager:
    • The Enable Event Logging Server checkbox is available under System-Wide Configuration> SysLog Server > SysLog Server -1. Click to enable (evlog output is sent to syslog); unclick to disable (evlog output is not sent to syslog). The default is unchecked. This field can be enabled only for the first Sys-Log Server in the list.
  • In CLI:
    • The SYSLogEnableEvlog command is available under SYSLogServer-1. Valid entry: 0 (disable, default) or 1 (enable). This field can be enabled only for the first SysLog Server in the list.



4929 CID feature works in Receive Direction only

The E&M Caller ID feature implemented by MR 4923 worked in Receive Direction only. When the Tenor made outgoing calls, it sent only DNIS, independent of configuration. This has been resolved.


4928 GUI does not connect to Analog Tenors running P108-09-24

When MR 4923 (E&M Caller ID feature) was added to the Tenor DX, it caused the Tenor Configuration Manager to not connect with the Analog Tenors. As a work around, enable the feature changes in the CLI database for Digital Tenor only, not Analog.


4920 SIP Decode failed when CallID had % character

When the Tenor decoded the CallID header and found a % character present, it would interpret the character (rather than taking it as a literal character). As a result, the Decode failed. This has been resolved.

4921 No ISDN Connect message for 911 calls

Some T1/ISDN carriers do not provide an ISDN level connect message for 911 calls. As a result, the Tenor never sent a 200Ok message to the SIP side to connect the call. A new feature enables you to configure up to 8 phone numbers for mapping of ISDN Progress to SIP connect. Each phone number handles a maximum of 16 digits. This feature is applicable only for calls coming into SIP and out ISDN (Trunk/ISDN). The DN specified is used to match against the final translated DN (not the original incoming DN) that is sent out on the DN side.

A new varconfig file is available to support this feature: mapIsdnProgressToSipConnectDN1 DN1 (where DN1 indicates the DN number).

4922 IP to IP Calls: Unsupported Codecs in the SDP caused unexpected behavior

If the Tenor was configured for IP to IP calls and if the originating IP device/phone had any codecs in its profile that the Tenor’s DSP did not support, the incoming SIP invite caused the Tenor to crash and reboot. This has been resolved.

4923 Calling Party Number (Caller ID) support in CAS E&M

Although the current CAS E&M implementation does not support receiving and sending of ANI (calling party number), new configuration options are included for E&M to support a modified DNIS that includes ANI.

To support this feature, the following new configuration items are available for the CLI only (not available in the Tenor Configuration Manager) under CASSG-1:

  • ENMAniDnisSequence
  • ENMStartDigit
  • ENMAniDnisDelimiter
  • ENMEndDigit

For detailed information about the commands, see the Command Reference Guide.

4924 Three Beeps when making outgoing call via Tenor DX

When a call was made from a Lync Mediation Server, a user would receive three quick beeps when making any outbound call from the Tenor DX before the user on the Lync client side heard any ring back. This has been resolved.

4925 T.38 offered in reInvite to Tenor, but Tenor chose G.711ulaw instead

When a Tenor was making an outbound fax call through a SIP Trunk, and a T.38 in the INVITE was returned, the Tenor chose G.711ulaw instead of T.38 and the fax subsequently failed. The Tenor was unable to re-negotiate media when it received a ReInvite that put the Tenor on hold. A new var_config item is now available that configures the Tenor to accept and negotiate media change on a ReInvite even if it indicates Hold.

To enable a Tenor to negotiate for a ReInvite that puts the Tenor on hold, a new varconfig configuration option is added: sipNegotiateMediaOnHold.

4927 R2 ANI Collection more than once (Applies to Tenor Digital only)

Under certain conditions the Tenor would attempt to collect ANI more than once, causing an R2 call to fail. This has been resolved.



4918 Effect of EnableLocalRouting parameter was not retained after Reboot (Analog only)

If EnableLocalRouting was set to 1, DNCM routing took precedence over the Routing Table. However, after a power cycle the local routing did not work. This has been resolved.



4915 Disable Auto Switch: Ignore AutoSwitch License if found

The Autoswitch feature has been disabled, even if a valid AutoSwitch license is discovered.

4916 PSTN_to_SIP call: Music on Hold not heard when Lync put Call on Hold

When a call was made from the PTSN to Tenor to Lync and then the call was put on hold from the Lync side with a re-INVITE SDP from Lync Mediation contained a=sendonly, the PSTN caller could not hear the music on hold played from the Lync Server. This has been resolved.

4917 UDP Port 17185 (WIN Debug Agent) not to be opened

For security reasons, Port 17185 will not be opened.



4717 If no media in re-Invite, do not send Hold to remote end

After an IP-IP call was up through the Tenor, 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, which would result in an OK with SDP to the server and a received ACK with SDP from the server. This has been resolved.

4855 Denmark Caller ID generation and detection

Note: A varconfig implemented this feature in P108-09-14 ("DtmfCidStartDelimiter” and “DtmfCidEndDelimiter”) but are now removed and replaced with the below configuration options available in the Command Line Interface (CLI).

Denmark Caller ID generation and detection is now included as a feature. There are two new configuration fields available for Caller ID generation and detection: DtmfCidStartDigit and DtmfCidEndDigit. These fields are available via Command Line Interface (CLI) under Gateway.

DtmfCidStartDigit. Valid entry: 0 - 15. Default entry: 13

DtmfCidEndDigit. Valid entry: 0 - 15. Default entry: 12

Entry definitions include the following:

0-9: Digit '0'-'9'

10: Digit 'A'

11: Digit 'B'

12: Digit 'C'

13: Digit 'D'

14: Digit '*'

15: Digit '#'


  •     For this feature to work, CallerIDDetection must be set to 7 (DTMF, FSK, No Ring) in CASSG-Line and 7 (DTMF, No Ring) in CASSG-Phone.
  •     When a call comes into the Tenor with CallerID that is restricted or unavailable, and is routed out to the Tenor’s FXS, the Tenor will send CallerId "D1#" to the phone.

4874 Tenor certified in support of Microsoft® Lync™ Server 2010

The Tenor DX Series Digital and Analog VoIP MultiPath Switches has been qualified for Direct SIP Enhanced Gateway in support of Microsoft® Lync™ Server 2010 deployments.

A new varconfig file is available to support this feature:

lyncInterOp 1. This enables Tenor to drop short packets (i.e., STUN and Comfort Noise).

lyncInterOp 0. This disables Tenor from dropping short packets (i.e., STUN and Comfort Noise).


  •     In order to use a Tenor in a Lync Environment, the following varconfig MUST be used: lyncInterOp 1`
  •     The previous varconfig lyncEarlyMediaDropShortPackets has been removed and replaced by lyncInterOp.

4890 IVR Prompt when MultiPath Call is routed to PSTN

Using an IVR prompt when a Multipath call is routed to the PSTN is now supported in MultiPath routing. This has been fixed to support MultiPath routing.

4895 Tenor did not send PRACK on SIP 182 queued message from IP-PBX

The Tenor did not send a PRACK message on a SIP 182 message from an IP-PBX, which caused the PBX to not open the audio path for the queued call. The Tenor will now respond back with a PRACK message.

4896 Music On Hold did not work in IP to IP calls

When a call was put on hold from a Lync client, the caller did not hear the music on hold coming into the Tenor from Lync. This has been resolved.

4899 Invite message was not properly encoded

When a message was sent to SSG having Request-URI as INVITE, the message was not completely sent through. This has been resolved.

4900 Digit missing for the DNIS (from To header or Request-URI)

A digit was missing for the DNIS number (from the To header or Request URI). This has been resolved.

4902 P108 New Routing; allow use of Routing Table instead of direct DNCM Routing

NOTE:: For upgrades to P108-09-21: When using the New Routing Table and direct DNCM routing, ensure EnableLocalRouting is configured to 1 (enabled). If this field is not configured properly, the existing direct DNCM routing will not work.

With Multipath routing, if the dialed number matched a DNCM, the Tenor would directly route the call between the analog ports, and not use the Routing Table. A new feature enables the Tenor to use the Routing Table to send the call to a SIP server, and have the call routed back to the Tenor, instead of doing Direct local routing.

A new configuration item, EnableLocalRouting (available via Command Line Interface (CLI) under Gateway.) can be configured to enable/disable this option. Valid entries: 0: Default, disabled (the Tenor by default will use the Routing Table instead of direct DNCM Routing) or 1: Enabled (direct DNCM routing is used).

4903 NAT IP Directory Feature added the wrong external NAT address

When a NAT IP directory was configured, the Tenor sent out the external NAT IP address (configured under the Ethernet setting) as NAT in the SIP invite and in the SDP to the IP side, rather than sending out its own locally configured Ethernet IP address. This has been resolved.

4907 No Ring Back on Calls with Ring No answer Forward to another Lync client

When a Lync client (A) was forwarded with a Ring No Answer to another Lync Client (B) within the Lync environment, the caller heard a partial ring before silence (even though the Lync Client B was still ringing until it went to voice mail). This has been resolved.

4908 Order of parameters causes Tenor to not encode Telephone Event 101 in forwarded Invite

When a Tenor received an Invite with SDP parameters, the forwarded invite from the Tenor was properly encoded. However, if the incoming parameters were not in irder, the forwarded invite from the Tenor was incorrect. This has been resolved.

4910 Tenor does not Ring specific channels/phone numbers in DN-Channel Map table

When the Tenor (using the New Routing Table) received a SIP invite with any of the configured phone numbers in the DN-Channel map table, the Tenor rang the first available FXS channel (like a hunt group) rather than ringing the specific FXS channel based on the phone number that is in the DN-Channel map table. This has been resolved.

4911 Under specific conditions, the Tenor reboot

If a Tenor had both FXO and FXS lines configured for offline operation nd the CallerID detection type configured in CAS (set to Type 7), a call into the Tenor would cause a reboot. This has been resolved.

4913 Tenor UAS - UAC Refresh Session Timer

With Session Timer supported in the Tenor, when a SIP End Point sent an Invite indicating that it wanted to be the refresher (refresher=uac), the Tenor was overriding with refresher=uas in its response, instead of honoring the client’s request to be the refresher. This has been resolved.

4914 After receiving Call Progress Tenor was not sending 180 ring or 183 SIP message to Lync

When the Tenor BX received a Call Progress, it would not send the 180 Ring or 183 SIP message to the Lync/ Mediation Server. As result, the Tenor would receive a SIP CANCEL message from the Lync/Mediation Server. This has been resolved.

4896 Music On Hold did not work in IP to IP calls

When a call was put on hold from a Lync client, the caller did not hear the music on hold coming into the Tenor from Lync. This has been resolved.



4883 Hook flash was not working

When an INFO message for the Hook Flash signal was sent from the SIP Messenger to Tenor, the Tenor failed to decode the INFO message and the following message was displayed:

excp |01/01| 2011/07/26|11:36:39:495 |> SIP < > SipInfoDtmf(CF), Digit or Duration field NOT decoded, or NOT present <.

This has been resolved.


4838 SSG not passing Session timers end to end

The Tenor did not pass the session timers correctly from end to end. As a result, calls were not going through correctly. This has been resolved.



4831 Allow registration restrictions

Two new varconfig options now makes it possible to allow restrictions for registration attempts destined for the SSG. The two options include SSGNeverFinalDest (Allows the Tenor to fail all registrations destined for the SSG, i.e. Register URI = SSG) and SSGRegInSurvMode (fail any new registrations while in survivable mode). When the Server goes down, this new security measure will stop SSG from accepting registrations during this time.

Fail registrations AND calls that are destined for the SSG (i.e. Request URI=SSG)

Valid var_config entries:

  • SSGNeverFinalDest 0. Default entry. Allows SSG to be the final destination. This is how SSG has always operated.
  • SSGNeverFinalDest 1. Does not allow SSG to be the final destination. Calls and registrations with request URI equal to SSG ADDR will fail.

Fail any new registrations while in survivable mode

Valid var_config entries:

  • SSGRegInSurvMode 0. Does not allow new registrations while in survivable mode.
  • SSGRegInSurvMode 1. Default entry. Allows registration while in survivable mode (this is how SSG has always operated).

4840 Allow Only Proxy Calls not working under certain circumstance

Note: This applies only when Gateway is being used.

AOPC (Allow Only Proxy Calls) was not working when using DNS for registration purposes. This has been resolved.



4819 Authentication-Info header not being passed through correctly

When the Tenor received an OK with an Authentication-Info header, the header was not being passed through properly and the outgoing Invite was incorrect.This has been resolved.

4821 Response to Subscribe needed Contact and To-Tag

The Tenor did not put a To-tag or Contact header in the OK message to a Subscribe Request. Some endpoints will not accept a Subscribe without a Contact and to-tag. If the Subscribe was not accepted, the Subscribe session failed to be established. This has been resolved.


4813 Analog phone did not hear disconnect tone after hold

When an Analog phone answered a call, and the call was put on/off hold, if the far end disconnected the call, the Analog phone would not hear the disconnect tone. This has been resolved.



4788 DNS Host timer refresh issue

When a call failed, the Tenor was not handling the call failover properly. This had to do with a DNS Host Timer refresh issue, but has been resolved.



4768 Branch parameter in ACK incorrect

For SSG, when the terminating end checked the validity of the ACK’s branch parameter and it was incorrect in the SSG’s ACK, calls failed to establish. This has been resolved.

4764 SSG reset when Subscribe is received

If the varconfig configuration entry SSGOptionsKeepAlive was set to 1, and the Tenor SSG received a Subscribe request, the SSG would reset. The SSG would reset continuously, as long as the
source re-transmitted the Subscribe request (if theSSGOptionsKeepAlive was set to 0 or no varconfig was present, the SSG would forward the Subscribe to the MWI server and there is no reset). This has been resolved.



4686 SSG new features

A few new features for SSG have been added:

Subscribe Feature

When a phone continued to send subscribe messages repeatedly when the Tenor was in survivable mode, the Tenor was flooded with requests, which seemed to seize up the Tenor. A new feature allows the Tenor to send back a 302 (which includes a forward address of the Primary SIP Server, located in SIPSG) when it receives a Subscribe message.

A new var_config.cfg command, SSG302Subscribe, enables this feature. Valid entries: SSG302Subscribe 0 (302 not sent when Subscribe is received) and SSG302Subscribe 1 (302 is sent when a Subscribe is received). For example, if SIPSG has a Primary SIP Server of and the phone number received in the request URI of the subscribe message is 1234567, the SSG will send a 302 with a Contact that looks like <sip:1234567@>.

Static Routes in Non-Survivable Mode

SIP static routes are now able to be used when in non-survivable mode. The static routes (in the ssg.cfg) will be the first attempted. If the static route fails, other routes will be attempted in the following order: request URI, registration, and default route (to the gateway itself).

A new var_config.cfg command, SSGStaticRouteFirst, enables this feature. Valid entries: SSGStaticRouteFirst 0 (default, the route order is: request-uri, ACD, registration, regular expression static route, default route) and SSG302StaticRouteFirst 1 (static route first, the route order is: static route, request-uri, ACD, registration, and default route).

Survivable mode with Options Request

A new feature will allow the Tenor to trigger survivable mode with SIP option message failure as opposed to failed call responses. When a new Invite message is received by the SSG, it will compare the request URI to the Primary SIP Server. If they are the same, the SSG will only route to the request URI if the end is alive (based on Options monitoring). Otherwise, the SSG will operate as if in the survivable mode.

A new var_config.cfg command, SSGOptionsKeepAlive, enables this feature. Valid entries: SSGOptionsKeepAlive 0 (default, health of the server not checked with Options) and SSGOptionsKeepAlive 1 (health of the server checked with Options).

New alarm generated

When the SSGOptionsKeepAlive var_config.cfg option is enabled, and the SIP Server is down, an alarm will be generated. The alarm will be cleared when the server comes back up.

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.



4742 IVR is now accessible with New Routing

IVR types were not accessible using the New Routing.IVR type 0, 8 are exposed. IVR in SSG, will work only in survivable mode.



4731 SSG dropped header field(s) from Notify message

The Tenor SSG dropped the Subscription-State and Call-Info headers from the outgoing Notify message. These headers should have been retained. This has been resolved.



  • No labels