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

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

This document lists features and enhancements, as well as resolved and open inconsistencies, for VoIP MultiPath Switch/Gateway and Call Relay Products running software version P108-09-00. These Release Notes also incorporate all resolved issues and changes included in Maintenance Releases P107-09-01 through P107-09-09.

For Response Point only: All features/enhancements/inconsistencies noted for Response Point are applicable only to those units listed here: http://www.quintum.com/responsepoint/rp_products.html.

The following sections are included:

Products Affected

The following products run software version P108-09-00:

  • 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 DXi PCIe VoIP Multipath Switch/Gateway
  • Tenor CMS VoIP MultiPath Switch/Gateway
  • Tenor Call Relay SP
  • Tenor Gatekeeper+
  • Tenor Response Point

Interoperability

The Tenor DX, Tenor AX, Tenor AS, Tenor AF,and Tenor BX running software version P108-09-00 interoperate with Tenor Configuration Manager, CM108-10-00.

Tenor Monitor v2-0-2 interoperates with Tenor DX, AX, and AS.

See www.quintum.com/support for all required files and firmware update instructions for each product.

Note: For best results, your PC resolution for running the Tenor Configuration Manager should be set to 1024 x 768.

New Features/Enhancements

This section includes new enhancements/ features introduced in P108-09-00, as well as any new enhancements/features introduced in Maintenance Releases P107-09-01 through P107-09-09.

4362 SNMP reporting/monitoring of IP to IP calls (Call Relay SP only)

The Tenor now supports SNMP reporting/monitoring IP to IP calls, which includes the number of calls that are in the connected state. The Tenor will use the following MIB variables in SNMP to support this new feature:

activeInCalls. Number of incoming calls in any state.

activeOutCalls. Number of outgoing calls in any state.

activeChannels. Number of connected calls.

4435/4609 Multipath Routing Enhancements

A new MultiPath Routing enhancement enables the Tenor to now translate incoming Called and Calling numbers based on digits, pattern, and length. With the Tenor connected to the PBX, PSTN and IP, this new feature will support any-to-any routing. Two new Tables have been added to configure the new routing options: Routing Table and Number Table.

Routing Table. Translates incoming Called and Calling Numbers based on digits, pattern, and length. After DN Channel Mapping is complete, the Tenor checks to see if the Routing Table is configured. If so, routing will be complete using the definitions in this table. Configuration options in the Routing table include:

  • Inbound TG
  • Outbound TG
  • Inbound Matching Criteria
  • Called Number Table ID
  • Calling Number Table ID
  • Number for Diversion
  • Diversion Content

The Routing Table is available when you enable the UseRoutingTable option, configured through the Tenor Configuration Manager or CLI under VoIP Configuration > Gateway. For detailed information about configuring the options for the Routing Table, see the latest Command Reference guide.

Number Table. The Number Table includes the call definitions the Routing Table uses to translate incoming Called and Calling numbers. As a result, routing will be based on the definitions in this table. Configuration options in the Number table include:

  • Description
  • Incoming Pattern
  • Outgoing Pattern
  • TON
  • NPI

The Number Table options can be configured through the Tenor Configuration Manager or CLI under VoIP Configuration > Number Tables> Number Table-default. For each call route, you are able to add/select a Number Table that is used to translate that calling/called information. For detailed information about configuring these options for the Number Table, see the latest Command Reference guide.

SIPSG. The SIPSG (SIP Signaling Group) also incorporates two changes to support MultiPath Routing:

  • TransportType. Can be changed on a per SIPSG basis instead of system-wide through the var_config.cfg.
  • IPRG. An IPRG can now be attached to a SIP Signaling Group.

Fields not Applicable to MultiPath Routing. When new MultiPath Routing is enabled, the following fields are not applicable and greyed out in the Tenor Configuration Manager and CLI:

VoIP Configuration

  • Gateway: Modem Bypass Retention Hours
  • SIP Signaling Group: Direct Gateway Routing

LCRG

  • General: Pass Through, Pass Through ID, External Routing
  • Trunk/Caller ID: Outbound ANI Number Digits, Add End of Dial Digit
  • Advanced: Modem Bypass

TCRG

  • General: Pass Through, Pass Through ID, External Routing, Busy Out
  • Trunk/Caller ID: Outbound ANI Number Digits, Add End of Dial Digit
  • Advanced: Forced Routing Number Type, Forced Routing Number, Modem
    Bypass

IPRG

  • Advanced: Ignore TON NPI, Enable External Routing
  • ANI: Relay ANI, Default ANI, Default ANI Screen Indicator, Default ANI Presentation Indicator

ISDN Signaling Group

  • Advanced: Relay ANI, Default ANI, Default ANI TON, Default ANI NPI, Default ANI Screen Indicator, Default ANI Presentation Indicator

3910/4520 Filter IP feature available

A new configuration option, filtertelnetftp (available through var_config.cfg ) is a new feature which acts similar to a firewall, by creating an "allow list" of IP addresses and networks that are permitted to make any communication with the Tenor (i.e, Ping, Telnet, Radius Servers, SNMP Servers, etc). Use this option as follows: filtertelnetftp <IP address> <IP mask>.

Below are examples of using this option on a Tenor with class A, B and C IP addresses.

For class A IP 192.168.50.201: filtertelnetftp 192.168.50.11 255.255.255.255. This allows Telnet, FTP and GUI access only from 192.168.50.11 and blocks access from all other IPs.

For class B IP 172.12.200.10: filtertelnetftp 172.12.200.11 255.255.255.255. This allows Telnet, FTP and GUI access only from 172.12.200.11 and blocks access from all other IPs.

For class C IP 10.10.200.10: filtertelnetftp 10.10.200.11 255.255.255.255. This allows Telnet, FTP and GUI access only from 10.10.200.11 and blocks access from all other IPs.

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

4279 Support for IVR auto recharge

Support for IVR auto recharge has been added to the Tenor. When this feature is enabled, and IVR Type is set to 15 (through Trunk Circuit Routing Group-line and Line Circuit Routing Group-phone in Tenor Configuration Manager and CLI), it will enable IVR to recharge the account based on a valid calling card number and balance.

A new option TV Cable Ecuador has been added to the Billing Vendor option list (available under Radius Server - Info). Enable the new option as follows:

  • From the Tenor Configuration Manager, select Radius Servers >Radius-UserServer, then select TV Cable Equador from the Billing Vendor drop down list.
  • From the CLI, at the RadiusServer- UserServerprompt, type set billingvendor 5.

4438 Signaling-only support for SIP-to-SIP and SIP-to/from-H323 calls (Call Relay SP only)

Note: This feature is not available with the new MultiPath Routing.

The EnableSignalingOnly configuration parameter (available through IPRG) now supports SIP-to-SIP and SIP to/from H323 calls. Previously, this command supported H.323 only. To enable this feature:

For CLI: at the IPRG prompt, enter EnableSignalingOnly 1.

For Tenor Configuration Manager : access VoIP Configuration> IPRG and click on the General tab. Ensure the EnableSignalingOnly box (under the General tab) is checked.

4451 Flash (16) support in RFC2833 (Tenor Analog or Tenor DX only)

Note: This feature is only for Tenor Analog or small Tenor DX (lower capacity Tenor DX's that do not contain the 120 channel DSP cards).

The Tenor now supports event 16 (Flash) in an RFC2833 packet; the Tenor will use the DTMF digit "D" as the flash-hook indication.

To enable this feature, you must configure RFC2833FlashEvent 15 through the var_config.cfg file. This sets the event to 15 (digit D) in RFC2833 packets for the flash-hook signal.

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

4460 Add method=INVITE to Refer-To header

The Tenor now includes method=INVITE in the Refer-To header for each outgoing Refer request.

4461 Support tel: url in incoming To:header

The Tenor now supports receiving a tel: url in the To: header of an incoming Invite, and also includes it in responses. During the session, the header is also used in the From: header of any requests sent by the Tenor (i.e., Bye, Refer, etc.).

4463 Add support for "P-called-Party-Id" header

Support has been added for a new header called P-Called-Party-Id to be used in incoming Invites. With this new header present in an incoming Invite, the Tenor will use the phone number in the SIP URI of the P-Called-Party-Id as the called party number, instead of the value in the Request-URI.

4466 Allow "user=phone" parameter in only Request-URI/To, instead of all URIs

On outgoing Invites, a new configuration item. SIPUserPhoneParameter, can enable/disable the user=phone parameter in ONLY the RequestURI and To headers. (Previously, the Tenor was able to turn on/off=phone only for all sip URIs).

The SIPUserPhoneParameter is available through var_config.cfg with the following parameters:

0 user=phone is not in any sip uri (default)
1 user=phone in all sip uri's
2 user=phone in the Request-URI and To: header of an Outgoing Invite

4468 Contact field in Invite Request is now configurable

A new configuration item now available through var_config.cfg, UseUAContact, which enables the user to choose where the Tenor should obtain the User Info of the Contact field (in the Invite Request) as follows:

UseUAContact 0. Default. Obtains the number for the Contact field from CH (i.e, DNCM, alias name, etc.)

UseUAContact 1. Obtains the number for the Contact field from the Contact definition in the User Agent configuration.

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

4475/4608/4681/4682 Progress Tone support

Support for new Progress Tones have been added under ProgressToneCountry. To view the available progress tones through the CLI, access config-DialPlan and type help ptc to see available options: Russian, Netherlands, Swiss, Belgium, France, Germany, Spain, Sweden, India, Czech/Slovakia, Austria, Bulgaria, Denmark, Finland, Greece, Hungary, Iceland, Ireland, Latvia, Lichtenstein, Lithuania, Luxembourg, Malta, Norway, and Romania.

4486 Use prioritized codec list from origination

The codec chosen by the Tenor was based on the priority (or preference order) of the termination end's list of codecs. A new var_config option, UseMediaOfferedOrder 1, allows the Tenor to negotiate the codec based on the priority list offered by the origination.

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

4487 Updated help to document parameters unaffected by the Setfactory command

Updated help for the Setfactory command to document those parameters unaffected when a SetFactory is issued.

4492 Increase in number of DNCM entries supported

A new feature included in the Tenor will enable each number in the DNCM to be registered, along with support for the '+' character. Previously, only the first value in the DNCM was being registered. Also, up to 300 entries are permitted in the DNCM table. When the field RegisterAllDNCMEntries 1 is set in the var_config.cfg, all entries will be registered with the SIP Proxy. Set this new feature with the following configuration:

  • Through var_config.cfg, set the following parameters: SIPFailover 1, RegisterAllDNCMEntries 1
  • In SIPSG (through CLI or Configuration Manager), set the parameter SIPUseDNinRegister 1 (enabled)

4494 Alternate Primary/Secondary Proxy failover using Options message

The Tenor now can use the "Option" request for monitoring whether a SIP server is alive. When this method is selected, it means that an "Option" request is sent every 60 seconds (configurable). If a response is received, it means that the proxy (and Registration) is still alive. If no response is received from the primary server, then the Tenor will send the "option" to a secondary server and attempt to register there.

There are two configurations available through var_config.cfg to support this new Option fail over:

SIPFailover 0 (default, legacy Dual Register method) or 1 (option is sent every 60 seconds).

SIPOptionsTimer 60. Time in seconds. Indicates how often the Options keep alive will be sent. The default is 60.

4502 Registration header now includes "Proxy-Require"

When a Tenor is registered to a SIP server, the Registration Request now includes the header field Proxy-Require. To enable this feature through the var_config.cfg file, enter SIPProxyRequire <value to be sent in Proxy-Require>. For example, SIPProxyRequire xxx.yyy.zzz.

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

4514 MPOP (Multiple Point of Presence)

When an incoming circuit call is routed to the OCS by the Tenor, and OCS is configured to ring multiple endpoints, the Tenor will then receive provisional responses from multiple endpoints. When RTPSourceValidation (available through VoIP Configuration > Gateway > RTP Source Validation) is set to 2, the Tenor will latch to the rtp stream from the first endpoint. If the endpoint that responds first is not the first endpoint the Tenor attaches too, the Tenor will switch its attachment to that endpoint. If the endpoint that the Tenor is latched onto is not the one answering, the Tenor will switch to the one that answers the call.

4519 Redirected Number As Called Party Number

When the Tenor received called party and redirect information, the Tenor was not capable of taking the redirect information and populating the request URI. Now, with two new var_config.cfg options, the called party may be populated with the Redirect Number as follows:

UseRedirectNumberAsCalledParty 1. Will replace called party number with the redirect number and drop the redirect number. There will not be a diversion header in the invite message.

UseRedirectNumberAsCalledParty 2. Will replace called party number and redirect number and there will be the diversion header in the invite message.

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

4524 Echo canceller tail size is now configurable

Previously, the echo canceller tail size was fixed at 128 msec. This value is now configurable through the ecTailSize command. Through the var_config.cfg file, you can now enter the desired ecTailSize: ecTailSize <number>, where the number can be one of the following:

ecTailSize 0: Does nothing; same as the line not being there in the var_config.cfg file. Default value: 128 msec.
ecTailSize 1 - ecTail size set at 64 msec.
ecTailSize 2 - ecTail size set at 32 msec.
ecTailSize 3 - ecTail size set at 16 msec.

4532 Administrator roles changed on Tenor

The User login option can now be enabled through the CLI as follows:

  1. Enable User Login
  2. Login as admin
  3. Type user user
  4. Type config
  5. Type set e 1
  6. Submit the change

The User Login has the following guidelines/options:

  • View DB configuration
  • Unable to change DB configuration
  • Unable to use cmd commands
  • Unable to use debug commands

4534 Allow Route Advance on Call Failure After 183 (Progress ) Is Received

A new var_config.cfg parameter ReRouteAfterProg 1 allows re-route on a SIP 404 call failure after 183 Progress is received.

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

4539 IVR Prompt when Multipath Call is routed to the PSTN

A new feature enables the Tenor to play a recorded voice prompt (RerouteWarning.wav) before the call is sent to the PSTN. The Command Line Interface (CLI) and Tenor Configuration Manager has been updated to include the new option under CallTerminationINDication:

  • For CLI, option 2 (VoicePromptedPSTNReroute) has been added to CallTerminationINDication.
  • For the Tenor Configuration Manager, the Voice Prompted PSTN Re-route option has been added to the Call Termination Indication drop down box (available through Trunk Routing Configuration> Trunk Circuit Routing Group-line> Trunk ID/Caller ID tab and Line Circuit Routing Configuration> Line Circuit Routing Group-phone> Trunk ID/Caller ID tab).

4546 SDP Connection header

Instead of sending multiple connection (c=) headers in the SDP, the Tenor now sends one connection header – only in the session portion of the SDP. To enable this feature, a new var_config.cfg command is now supported: SDPConnInSessOnly. Configure this feature as follows:

In the var_config,cfg, enter the following:

SDPConnInSessOnly 0. Connection header is present in both the session and media sections of SDP in the Invite.

SDPConnInSessOnly 1. Connection header is present in the session section of the SDP only.

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

4594 Support FSK Caller ID before First Ring

The Tenor now supports caller ID being delivered using FSK signaling before the first ring. The CLI and Tenor Configuration Manager have been modified to support this change:

  • CallerIDDetection. For CLI, Option 7 has been changed from DTMF,No Ring to DTMF/FSK,No Ring. For the Tenor Configuration Manager, the drop down option DTMF,No Ring has been changed to DTMF/FSK,No Ring.
  • CallerIDGeneration. For CLI, a new value has been added: 8: FSK,No Ring. For the Tenor Configuration Manager, option FSK,No Ring has been added.

4599 On SIP inbound call, Immediate Progress is sent

When an incoming Invite is received, the Tenor is able to now send a Progress immediately following the Trying. This new feature is controlled by a new parameter SIPImmediateProgress, available through the var_config.cfg.

Valid entries are as follows:

SIPImmediateProgress 0 = Default. SIPImmediateProgress is not sent.
SIPImmediateProgress 1 = SIPImmediateProgress is sent.

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

4600 DNS load balancing

Calls can now be balanced from one DNS address to the next in a round robin fashion. This new feature is controlled by a new parameter DNSLoadBalance, available through the var_config.cfg.

Valid entries are as follows:

DNSLoadBalance 0 = Default. Do not do DNS Load Balancing.
DNSLoadBalance 1 = DNS Load Balancing.

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

4628 Disable Echo Canceller

The Tenor now supports disabling echo canceller selectively based on span or line. This new feature is controlled by a new parameter DisableEC, available through the var_config.cfg. To disable echo canceller, enter DisableEC <span/line> in the var_config.cfg file. For example, Disable EC 1 (for FXS), Disable EC 2 (for FXO).

Example configuration options to disable the echo canceller through the var_config.cfg are as follows:

DisableEC 1
Disables echo canceller on FSX channels of analog, first BRI interface of the Tenor BX or first span of Tenor DX.

DisableEC 1 2
Disables echo canceller on the FXS and FXO channels of the Tenor Analog first, second BRI interface of the Tenor BX, and first and second spans of Tenor DX.
Similarly you can disable echo canceller on all the spans of Tenor BX and Tenor DX using the following: DisableEC 1 2 3 4 5 6 7 8.

DisableEC 3 6
Disables echo cancellor only on span 3 and span 6.

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

4636 Automatic factory default feature did not work correctly

Although the Tenor can detect resets caused by database corruption and automatically switch to the factory default setting, it was found that under certain conditions, the Tenor went to factory default for no reason. This has been resolved.

4657 Enable AutoSwitch

The Tenor now supports the EnableAutoSwitch option (available through TCRG). Two options are available EnableAutoSwitch 0 (disable, default) or 1 (enable).

4702 Decode the Invite URL or "To" header as the DNIS

For an incoming Invite, the Tenor decodes the Request URI as the DNIS and decodes the "To" header as the DNIS only when the URI was blank. Now, a new features enables to the Tenor to take the Called Party Number from the To" header rather than the Request URI.

A var_config.cfg option, SIPUseToAsNumber, is used to control this feature with the following parameters:

SIPUSeToAsNumber 0. Incoming DNIS is taken from Request URI (default)

SIPUseToAsNumber 1. Incoming DNIS taken from the To: header

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

4708 Send Complete IE added to BRI Setup Message

The BRI setup messages from the Tenor BX did not include the Send Complete IE in the setup message. This message is now included.

4710 Open Backward Voice Path

The Tenor now enables the calling party to hear the call progress (backward voice path is open all the time). To resort to the previous functionality, a new var_config.cfg parameter,CloseSS7BackwardPath 1 will disable the the ability for the calling party to hear the call progress (backward voice path is closed).

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

Resolved Inconsistencies

This section includes inconsistencies resolved in P108-09-00, as well as inconsistencies resolved in Maintenance Releases P107-09-01 through P107-09-09.

3789/4334/4473/4495/4504/4507 Configuration Manager Help improved

The Tenor Configuration Manager help is now more clear in Gateway, Interdigit Timeout, CodecVoiceCoding, AccessFormat, Use10DigitLocal Dial, CodecVoiceCoding, InboundDNISTranslationDirectory.

4220 Pass Through Type 2 works with HLDND

Pass Through Enable type 2 works with Hunt LDN Directory (HLDND) only, but does not work with DN Channel map (DNCM).

4321 Incomplete help for TON and NPI

For InboundDNISXlationDirectory-1, incomplete help was displayed for TON and NPI. This has been corrected.

4341 DX Channel Group un-maps after reset

After configuring a Tenor DX for channel mapping, and then typing to complete a debug reboot, the configuration reverted back to the default mapping.This has been resolved.

4387 Response Point auto answer support

The Tenor Response Point system now reports an error after an upgrade, and requests that the device be removed and added again.

4414 Profile Rule accepts specific string

Profile Rule will now accept strings starting with tftp://, ftp:// or http:// only. Previously, the Profile Rule was accepting all strings.

4462 Large number of User Agents may have caused reset

If a large number of User Agents were configured and a database submit was done, the Tenor reset. For example, a crash was seen when about 70 UAs were configured on an Tenor AF and/or about 80 UAs were configured on a Tenor DX. This has been resolved.

4470 Decode 'early-only' field in Replaces Header

The 'early-only' field in Replaces Header was not being decoded correctly. This has been resolved.

4471 Enabling EarlyMediaTone could cause PRI call failure

With a call flow for incoming calls from PRI to SIP, and EarlyMediaRingTone was set to 1 in var_config.cfg, calls failed with the following excp resulting in a code cause 41: excp |01/01| 2009/03/27|10:53:15:760 |> CH < PriOrigCall:: no progress indicator ie found in fapi. This has been resolved.

4472 IVR help removed from LCRG

In the Command Reference Guide, the IVR help was removed from the LCRG tab.

4490 SDP contained extra 101 (Call Relay SP only)

The Tenor added an extra 101 in the SDP portion of the inbound invite message. This has been resolved.

4493 Route header not included in Re-Invite Messages sent by the Tenor

If the Tenor is the Originator of a call, the Route header was not put in any Re-Invite messages sent by the Tenor. This was causing fax calls to fail. This has been resolved.

4498 Help for G.726 not included

Updated the CodecPayloadSize screen to include help for G.726.

4499 Mishandled partially received content stream

When a SIP message came into a Tenor split into two streams, wherein SDP was across the two streams, the Tenor was not handling it correctly. As a result, the call would fail. This has been resolved.

4508 Forked invite error on re-Invite

When the Tenor was the Calling Party of a fax call, the call failed. When the Re-Invite was received to change over to fax mode, the Tenor ignored the request with the following message: [ua]:Forked Invite/Cancel - ignore. ruri=(75566651201), myname=(+8675566651201). If the stored myname value (sent in the From Header of Invite) did not equal the incoming request URI, the Tenor ignored the Invite and looked at it as a forked request. This has been resolved.

4510 CName was not sent in Facility IE (Digital only)

The Tenor was not delivering CName in the IP to PRI direction. Cname was not being sent when E1 PRI protocols were used. This has been resolved.

4512 Large number of User Agents caused IP Connectivity problems

The following problems occurred when a large number of User Agents were added in the SIPSG:

  • Unable to Telnet to Tenor
  • Unable to FTP
  • Unable to ping either from the Tenor or to the Tenor
  • Console link went down and GUI lost connectivity with the Tenor
  • Calls made from the Tenor would fail (since no IP connectivity)

As a fix, the maximum number of User Agents that can be added for each SIPSG is changed from 30 to 24 (with a maximum of 4 Signaling Groups, a total of 96 User Agents may be added).

4513 IP address configuration problem on a new CMS

When a new CMS (or a CMS where the data files have been removed and the system rebooted) automatically reboot itself following a manual configuration of IP Address/SubnetMask/Gateway, it was found that the configuration was not being saved. This has been resolved.

4516 One Number Fax match for incoming IP call caused problems

When a termination Tenor was configured for One Number Fax, and the DNIS from an incoming IP call matched the One Number Fax, the Tenor tried to route the call back over IP but the call failed. This has been resolved.

4522 IP loopback of media packets caused reset (CMS only)

Calls were being routed through the CMS in such a way that media packets loopback within the CMS. As a result, the Tenor reset. This was applicable for both SIP and H.323. This has been resolved.

4526 SIPSG accepted invalid IP

Through the CLI, under SIP Signaling Group, each of the following parameters were accepting an invalid IP address: PrimarySIPServer, SecondarySIPServer, OutboundPrimaryServer and OutboundSecondaryServer.This has been resolved.

4528 Very Long Incoming ISDN messages were not decoded properly

Incoming ISDN messages that were too long did not get coded properly. As a result, the call did not route correctly. This has been resolved.

4531 One way voice

The Tenor was experiencing one way voice for an H323 call flow. This has been resolved.

4537 If proxy was unregistered, calls should not have been made if the SIP registration was configured to enabled

If the registration configuration was enabled (i.e. RegisterExpiryTimer was not set to disabled(-1) ) and the proxy has unregistered, the Tenor would attempt to make a call, which became inefficient and led to unnecessary delay in alternate route attempts. This has been modified to make the process more efficient.

4540 Caller ID Detection may have resulted in Called Number (Analog only)

The Tenor wrongly detected caller ID from the circuit side as the called party number. This has been resolved.

4547 MWI message lost

When a user was off hook, and the server sent a message to clear the MWI message, the MWI message was ignored. This has been resolved.

4550 SIP info (*) character was being mis-interpreted

The * character signaling forwarding in a SIP message, was being mis-interpreted when a user tried to use it for call forwarding. This has been resolved.

4555 Adding more than 104 HDNs caused the Tenor to crash

When the user tried to add more than 104 entries using different Hopoff Number Directories, the Tenor crashed. This has been resolved with the support of 64 possible entries in each HDN.

4556 Caller ID translation inconsistency

When using the var_config.cfg file, Caller ID translation should have been able to use the '...' as a placeholder, which worked successfully in the LCRG and TCRG, but not in the IPRG. This has been resolved.

4557 Multipart MIME Content-length header

The Tenor was unable to decode SIP messages that contain Multipart MIME if the "Content-Length" header was not included in each multipart boundary. This has been resolved.

4559 SIP Registration could have caused reset

If the T1/E1 went down (unplugged) the Tenor would unregister with both the SIP servers. When the T1/E1 link came back up the Tenor would attempt to register with the SIP server again, but after the T1/E1 link came back up, the Tenor may have reset. This has been resolved.

4561 Re-Invite sent next call media to wrong IP

With two calls in the Tenor, the first call connected to the server and transferred correctly. While the first call was connected and a second call was made, the second call was sent to the correct port, but not the correct IP. This has been resolved.

4564 Media Control element of fast start uses 0.0.0.0 on outgoing leg rather than actual value

There was a problem where media was not coming up; the outgoing fast start information in the Setup from the CRL had the first MediaControlChan 0.0.0.0, even though the incoming MediaControlChan had a non-zero value. This has been resolved.

4566 SIP Failover Registrations using FQDN

With FQDN configured as the primary SIP Server and DNS answers with 2 IP addresses (and the Tenor received no response or failure on the initial registration), the Tenor did not send another registration to the second IP address until a DNS refresh. As a result, the Tenor could not receive calls from the second SIP Server until it successfully registered. This has been resolved.

4577 RFC2833 Digit Relay Could Cause Memory problems

Using RFC2833 Digit Relay with H323, may have caused the Tenor to run out of memory and reset. This has been resolved.

4582 For IVR, Second dial Tone did not work when Early Media Ring Back was enabled

When a Tenor was used to connect to OCS and early media ring tone was enabled, IVR type 1 generated ring back instead of a second dial on every other call. This has been resolved.

4586 Ringback did not occur during transfer

When a call came in to the following scenario, ring back tone did not occur during the following transfer:

ISDN -- DX -- SIP -- Sip Server AA - Transfer to local ext.

This has been resolved.

4592 For SIP, if no alternate route existed, the calls should have been dropped immediately

If an incoming SIP call had no routable entry in the Routing table, the call would linger until the "SIP no connect" timer expired, resulting in a "503 Service unavailable" response being sent out. As a result, this would cause waiting for the calling party. This has been fixed so that the call is dropped immediately.

4596 License mismatch issue

After a Tenor reset from a Telnet crash, the hardware was not being recognized. This has been resolved.

4605 DASS2 did not receive Calling Party Number (Tenor DX and Tenor CMS only)

The Tenor did not pass the calling party number from the circuit side to the IP side. The calling party digits were received as procInfo and were ignored. This has been resolved.

4614 For SIP: changing TransportType to TCP required reboot

If the TransportType (available through SIPSG) was set to 1 (TCP), and calls were made, the calls were still going over UDP. To change the transport from UDP to TCP, a reboot was required. This has been resolved.

4615 Codec and IPRG association with the right SIP Signaling group was not working

When two calls were received on the destination Tenor configured with different SIP signaling groups and codec profiles containing different codecs, both calls connected using the same codec. This has been resolved.

4622 Calling Name not received when PRI DMS protocol was used (Digital only)

When PRI protocol DMS was in use, the Tenor could not receive the Calling Name. This has been resolved.

4659 System kept re-booting with 64 entries HND

When the Tenor had two Hop Off number directories (HND) configured, and each HND was configured with 64 entries, the system kept rebooting. This has been resolved.

4677 Tenor sent multiple 183 message while phone was ringing

When a SIP call was ringing, the Tenor sent back multiple 183 Session Progress messages. This has been resolved.

4679 Ptime problem with G.729

In the IP outgoing direction, if G729 was the first codec, the ptime was always the default (40). In the IP incoming direction, if G729 was the negotiated codec, the ptime
was always the default (40). In both cases, the conf value for G.729 ptime was not being used in the offers or answers. This has been resolved.

4687 Forced Routing Number was not working with Table Based Routing

Forced Routing Number was not working with Table Based Routing. This has been resolved.

4696/4700 ISDN calls failed on receiving multiple progress messages

ISDN call failed if it received multiple progress messages from the far end. This has been resolved.

4697 Call not heard with certain SIP Digit Relay Payload types

When SIP Digit Relay Payload Type was set to 96, 97, or 98, DTMF tones were not heard during a call. This has been resolved.

4709 ST DS1 ALL "Active Channels" value incorrect

When executing the command ST DS1, the value for 'Active channels' was incorrect and sometimes a negative number. This has been fixed.

4712 IVR: Playing Wrong Currency Amount

If the server sent h323-currency=GBP, the Tenor would play dollars instead of pound. It was found that the pound was mapped to dollar. This has been resolved.

Other Changes

This sections includes other general changes (such as interoperability changes and configuration option changes) in P108-09-00, as well as changes that occurred in Maintenance Releases P107-09-01 through P107-09-09.

4322/3695 Help added for Barred field

Help has been added for the Barred field in the Inbound DNIS translation Directories.

4344 DN Channel Map Clarification

Help has been updated for DN Channel Map to clarify that if the user creates more than one entry in the DNCM with the same DN (Dialed Number), the system will only use the first DN. Even if the first DN is "busy" (engaged in a call), the system will not choose a second DN.

4352 CLI help column expanded

The column in the CLI that displays help has been expanded to display all help entries properly.

4459 Enable/disable of a UA now working for all Tenor products

The enable/disable configuration option in the SIP User Agent table was not having an effect (only for Response Point units). If a user agent was defined, regardless of the configuration parameter, the user agent was enabled. This feature has been changed to work for all Tenor products.

Change an entry for an existing User Agent as follows: at the User Agent table enter change {index} enabled [0|1] (0 confirm User Agent is not registered to its proxy; 1 confirms User Agent is registered to its proxy).

4365 One number Fax solution

Note: This feature was added in P107-09-00. All configuration fields were not listed in the Release Notes; all configuration fields are available through var_config.cfg and are listed below.

UMAddress 192.168.50.223:5060

  • Example specifies IP address.

UMPilotNum 3333

  • Example specifies the pilot (SA) number of the UM/Exchange. This is the number set as the destination number when the call is diverted to UM.

enableCNGdetection 1

  • Detects CNG tone.

oneNumberFAX <access_number_pattern> <fax_mailbox_number>

  • access_number_pattern is the partial or whole access number dialed to reach the Tenor (i.e., 17324609000 or 1732*).
  • fax_mailbox_number is the mailbox number on the Microsoft Exchange Server where the fax is stored.

CNGToneInitTimer <initial_time>

  • initial_timer is the interval between receiving the call and starting to look for the cng tone. Valid values:: 1 - 60 seconds, default 1 second.

CNGToneDetectTimer <cng_detection_duration>

  • cng_detection_duration is the period for which the Tenor listens for a fax cng tone. Valid values: 1 - 60 seconds, default is 8 seconds.

4467 If ANI was set to Anonymous as Caller ID, call failed

When the Tenor's call flow was SIP to E1/R2, if the ANI delivery was enabled over the R2 link but the Caller ID was set to Anonymous from the SIP side, the Tenor sent the word "Anonymous" as the Caller ID to CAS. CAS tried to send this as the ANI over R2 to the called side but this led to call failure. This has been resolved.

4503 EPAD Help needs to specify "H.323 only"

Help clarified to indicate that EPAD is applicable to H.323 only (not SIP).

4533 Fax CNG On OFF Time Tolerance adjusted

The duration of the off period in the CNG tone has been changed to ensure fax calls go through correctly:

CNG_ON_MIN from 450 to 425 msec
CNG_ON_MAX from 550 to 575 msec
CNG_OFF_MIN from 2750 to 2550 msec
CNG_OFF_MAX from 3750 to 3450 msec

4650 Generate a random initial Call Reference Value

The Tenor will now initiate the initial CRV value starting with the random value, and the subsequent CRV values will be incremented by 1. Previously, the initial CRV value always started with 1.

4684 Default Ethernet Interface speed for Tenor AF

For new Tenor AFs only: the unit supports a Speed of 10 Mbps and Full Duplex only. For Tenor AF units upgraded to the new version, this change will not apply.

Note: Ensure the Ethernet switch is set to a speed of 10 Mbps and Full Duplex. Otherwise, when the Tenor starts up and negotiates with the Ethernet switch about the Duplex and Speed, and the settings are different than those set in the Tenor, the following error will be displayed, "Resetting Tenor to apply database Etherenet configuration."

Open Inconsistencies

This section includes open inconsistencies in Release P108-09-00. Specific details are included for each open issue. If a work around is available, it is listed.

245 Windows XP file explorer does not interoperate well with the Tenor for FTP

When using Window XP's file explorer (explorer.exe), you may not be able to FTP all the unzipped system and help files to a Tenor. We recommend running FTP from the DOS prompt or using Internet Explorer.

1050 Specific database changes need a reset to take effect

When you change the CDR password or IP address, the Tenor requires a reset in order for the changes to take effect.

1134 Disconnect Supervision works only for option '2' (Tenor AX/AS only)

The Disconnect Supervision Options (# of on/off intervals per cadence cycle) works only when option "2" is selected. An entry of "4" will still false answer if the ringback is followed by a busy tone. The workaround is to set it to option 2. (Note: The default value changed to 2.)

1862 When receiving a malformed SIP message, Tenor does not return message

When the Tenor receives any SIP message that cannot be decoded, it does not send back the "400 Bad Request" message.

1973 Pass Through Caller ID does not work

Pass Through Caller ID does not work. As a work around, disable progress tones in the LCRG.

1987 ToneBasedSupervision not working on transferred call

On a transferred call, the tones are not heard on the second call.

2214 MaxForward may produce unexpected results

When using the MaxForward feature, unexpected results may happen. For example, when a Tenor is being called, it may not use its own Max Forward configuration for returning messages. Instead, it uses the Max Forward configured in the calling Tenor.

2247 UserAgent parameters do not accept blank value

To un-configure any of the UserAgent parameters, the change command with a blank value does not work. As a work around, put an empty string character in single quotes following the command, using the following format: change 1 PrimaryPassWord ''.

2341 Remote NAT does not work on SIP calls

The RemoteNAT feature does not work on SIP calls.

2354 Memory mapping error may occur after reboot (Tenor DX only)

Rarely, when a Tenor reboots, a PCI memory mapping error causes an exception. When this happens, the Tenor resets a second time and comes up properly. This applies to Tenor DX4120 and Tenor DX8120 only.

3334 Tenor Migration between platforms not working as expected

After loading a Tenor S with a version of Tenor P (or vice versa), there was a problem with port usage. As a workaround, when migrating from a Tenor S to a Tenor P (or vice versa), do a setfactory command on the Tenor and then configure the unit manually.

3790 In IPRG "RejCallNoANI" does not work

The following scenarios are working opposite of what is expected:

  • When "RejCallNoANI" is enabled, and when when there is no entry in the DN channel map from the source Tenor, the call should not go through. The opposite happens in the Tenor, and the call does go through.
  • When there is an entry in the DN channel map and RelayANI is disabled, the Tenor will not send out any ANI to the destination. As a result, the call should fail because "RejCallNoANI" is enabled in the destination Tenor. The opposite happens and the call goes through.

4724 With new MultiPath routing, mixed wildcard usage should not be allowed

For the new MultiPath routing, mixed wildcard usage should not be allowed in the Number table (i.e., Incoming Pattern = 1732267* and Outgoing Pattern = 1732267....). The Tenor should not allow this to be configured. The incoming number will not be translated correctly. As a work around, ensure the incoming and outgoing patters use the same wildcards.

4728 Switching to Routing Table does not remove Forced Routing Number

When the new Routing Table is enabled (through the UseRoutingTable option), if a Forced Routing number was previously configured in a TCRG (Trunk Circuit Routing Group), the system will retain the Forced Routing Number, even though it is not displayed in the Tenor Configuration Manager or CLI. As a work around, prior to enabling the UseRoutingTable option, you must remove all Forced Routing Numbers from all TCRGs.

Certain Tenor units may reboot twice

For Tenor AXT and AXG, upon the initial startup, if the static IP option is selected and static IP address is typed, the Tenor will reboot itself twice.