Tenor(tm) VoIP MultiPath Switch/Gateway and Call Relay Products
P106-12-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 P106-12-00. These Release Notes also incorporate all resolved
issues and changes included in Maintenance
Releases P105-19-01 through P105-19-14.
The following sections are included:
Products Affected
The following products run software version P106-12-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 60
- Tenor Call Relay SP
- Tenor Gatekeeper+
Interoperability
The Tenor DX, Tenor AX, Tenor AS, Tenor AF, and Tenor BX running software version
P106-12-00 interoperate with Tenor Configuration Manager, CM106-18-00.
Tenor Monitor v2-0-2 interoperates with Tenor DX, AX, and AS.
See for all required files and firmware update instructions for each product.
Functionality Removed
AutoSwitch functionality has been removed from all Tenor products. All of the
configuration options available through TCRG and LCRG
have been removed from the Configuration Manager, as well as the CLI. AutoSwitch
will not be initiated if the IP link is down.
New Features/Enhancements
This sections includes new features/enhancements introduced in P106-12-00,
as well as any new features/enhancements introduced in Maintenance Releases
P105-19-01 through P105-19-14.
710 Support for RFC2833 DTMF relay when using H.323 protocol
Support for 2833 DTMF relay (using H.323) has been added to the Tenor. To enable
this feature, a new option has been added to the DigitRelayH323
parameter in IPRG. Configure 3 (RFC2833)
to enable RFC2833 DTMF relay.
For more information, see Command
Reference.
858 Syslog Feature
Previously, the event log from the Tenor went only to the local0 (facility
16) on the syslog server. As a result, the user could not easily separate the
Tenor event log from the rest of the syslog events normally appearing on local0
(i.e., various messages about packets rejected by the the host's firewall, PPPoE
connections, etc.).
A new Tenor syslog feature enables events logged by the syslogserver to be
collected on a separate facility (other than facility 16) and logged to a separate
file. Three new configuration options support this feature:
cmd evsyslog. Available through the CLI. Valid entry:
1 (sends the evlog to syslogserver-1) or 0 (does not
send evlog to syslogserver-1).
evsyslog. Available through the var_config.cfg
file. Valid entry: 1 (sends the evlog to syslogserver-1) or
0 (does not sent evlog to syslogserver-1).
evsyslogfacility. Available through var_config.cfg
file. Configures the facility code for where to send the evlog. Valid entry:
16 to 23 (number for the applicable facility). The
system sends the syslog to that configured facility.
See the Command
Reference for additional information about the var_config.cfg
file.
2526 Call Routing Server SIP Calls
For an originating SIP call with the Call Routing Server, the Tenor will now
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.
2830 New commands for port troubleshooting
Three new cmd commands (available through the CLI) have been
added to display information about available port ranges for troubleshooting
and maintenance: cmd showports, cmd displayports, and
cmd listports. Each of these commands displays the
list of available IP ports for the Tenor.
3317 Making test calls from CLI
The Tenor now has the ability to make test calls from the CLI. This capability
determines if a call can be routed successfully. Three new cmd
commands have been added as options for making a test call:
cmd testcall c 91442111. Makes a call to
a DNIS number (i.e., 91442111). Call is routed over IP to the destination Tenor.
cmd testcall e <callid>. Disconnects the call.
cmd testcall d. Displays the test call list.
3320 New conference capabilities
A new feature enables a conference call to be initiated on 3 party applications
from a phone connected to the Tenor. Once the conference is up, supplementary
services are available, such as receiving Call Waiting calls, initiating transfers,
and also adding users to the conference. To enable these features, four new
configuration options are available.
Through SIPSG, the following options are configurable:
ConferenceFactoryName. Name for the conference. Valid entry:
up 31 characters. Example: conference.
ConferenceFactoryServer. The server on which the conference
is running. Example: server.test.net
ConferenceFactoryPort. The port on which the conference is
running. Default entry: 5060.
Through the TCRG and LCRG, the following
option is configurable:
CallWaitToConfKeystroke. Keystroke used for an incoming Call
Waiting call to be added to the conference. Default value: 22.
3348 SNMP support for analog port monitoring (Analog only)
SNMP support has been added to the call status for individual FXO/FXS ports.
When you enter the st ds1 all command, the active in/out status
of each port will be displayed. In the display, the port number is listed with
the slot and interface under the Slot heading.
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).
3409 Auto provisioning
As Service Providers deploy gateways to their enterprise customers, they are
faced with the challenge of providing firmware and configuration data for each
system. The Service Providers business process involves an ordering and fulfillment
system typically referred to as the "back-office system" This system
is used to collect account information, assign services, and ship equipment.
Previously, the Service Provider initiated an FTP session to load the firmware
(such as a Tenor) and then use one of the configuration methods (GUI or CLI)
to configure the equipment. As a way to link the Service Providers' "back
office" system with the equipment (Tenor) in the field, the following AutoProvisioning
features are now supported in the Tenor: provisioning server discovery, firmware
updates, and configuration updates.
Several new options are now included in the Tenor to support and configure
AutoProvisioning, available through both the Tenor Configuration Manager and
CLI. Through the Tenor Configuration Manager, these fields are available under
the AutoProvisioning tabs (General, Auto
Configuration Retrieval, Auto Software Upgrade). Through
the CLI, these fields are available under AutoProvisioning-1.
Enabled. Enables communication with server to resync. Valid
entry: 0 (disabled) or 1 (enabled).
TFTPServer. Identifies TFTP server address which provides
initial AutoProvision settings in factory. No user input required.
ProvisionLog. Available logging output. Through Tenor Configuration
Manager, four options are available:
- Print connection details in RS-232 console
- Log the configuration file received from the provisioning server
- Log parsing result of the received configuration file
- Log execution result of the received configuration file
Through the CLI, valid entry: 1-15 (each block of numbers correlates to the
four options available through the Configuration Manager). Note: we recommend
configuring this option through the Configuration Manager. For more specific
information about these fields, see the Command
Reference.
ProvisionEnable. Identifies how the retrieved configuration
file is handled. Valid entries: 0 (AutoProvisioning is disabled;
ignore all other configuration), 1 (Set factory, apply retrieved
file, reset Tenor), 2 (Set factory, apply retrieved file, reset
Tenor only when necessary) or 3 (Apply retrieved file on top
of DB, reset Tenor if necessary).
ProvisionErrorPolicy. Identifies how to handle errors in the
configuration file. Valid entries: 1 (Allow no errors), 2
(Allow minimum errors), or 3 (Allow maximum errors).
ResyncOnReset. Defines whether the system should look for
a new configuration file at system reset. Valid entries: 0
(disable, do not look for new configuration at reset) or 1
(enable, look for new configuration at reset).
ResyncRandomDelay. Valid in seconds for how long to wait before
beginning the resync process. This field is used to minimize load on the provisioning
server. Valid entry: number of seconds. Default entry: 15 seconds.
ResyncPeriodic. Periodic timer (frequency) used to check provisioning
server for a new configuration. Valid entry: number of seconds. Default: 86400
seconds (1 day).
ResyncErrorRetryDelay. Period of delay time if there is an
error retrieving the configuration file. Valid entry: number of seconds. Default:
3600 seconds (1 hour).
ConnectTimeout. Length of time the Tenor waits to connect
to the provisioning server before timing out. Valid entry: number of seconds.
Default 300 seconds (5 minutes).
TransferTimeout. Length of time the Tenor waits while a file
is transferring to the provisioning server before timing out. Valid entry: Default
3600 seconds (1 hour).
ResyncAfterUpgradeAttempt. Forces the configuration to be
refreshed after a firmware upgrade. Valid values: 0 (disabled)
and 1 (enabled).
ForcedResyncDelay. Period of time the Tenor waits for calls
to clear before resetting the system. Valid entry: number of seconds. Default:
120 seconds (2 minutes).
ResyncNewCallsAllowed. Allow calls in Forced Resync Delay.
Valid entry: 0 (disabled) or 1 (enabled).
ProfileRule. URL of Tenor Configuration file location. Valid
entry: URL for configuration file.
UpgradeEnable. Enable auto-firmware update (if a Tenor software
update is available). Valid entry: 0 (disabled) or 1
(enabled).
UpgradeErrorRetryDelay. Delay time if there is an error retrieving
the firmware file. Value is in seconds. Valid entry: 3600 seconds (1 hour).
UpgradeRule. URL of the new Tenor software release.
UpgradeRelease. Release version of the firmware available
for download. This field is used to ensure the firmware version is the same
as the running firmware.
For more information, see Auto
Provisioning.
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.
3434 Access boot prompt via serial port by pressing "esc" key
A new feature enables access the boot prompt through the serial port as follows:
When you connect to the Tenor through the serial port, reboot the Tenor and
press the "esc" key, keeping it pressed while the system resets. A
prompt will appear, "WITHIN 4 SECONDS, PRESS 's' TO STOP BOOTING UP".
Follow the prompt to stop booting up and enter the boot code menu (or ignore
for a normal bootup).
3448 SNMP support for specific analog port monitoring
In addition to the Tenor supporting SNMP statistics for FXO and FXS ports as
a group, the Tenor now supports SNMP statistics for each individual analog port.
When you execute the st ds1 all command, statistics for the
individual ports are listed.
3470 Allow number of cycles for qualifying CNG Tone to be configurable
The configuration options for CNG tone detection for fax has been expanded
to include two new option cycles for validation. The var_config.cfg
command enableCNGdetection now enables more options
for validation cycles. Values include:
0 - disabled
1 - enabled with 1 cycle of validation (6 seconds)
2 - enabled with 2 cycles of validation (9 seconds)
3 - enabled with 3 cycles of validation (13 seconds)
See the Command
Reference for additional information about the var_config.cfg
file.
3482 Voicemail support for QSIG
Support for IP-based voicemail systems off legacy QSIG-based voicemail systems
is now supported in the Tenor. This new feature translates the information in
the SIP Invite to support QSIG-based voicemail. Voicemail support is for SIP
only (not H.323).
3488/3951/3847 P-Asserted-Id, P-Preferred-Id and Privacy header support
The Tenor now supports SIP implementation for P-Asserted-Identity and Privacy
header support. This header support provides a way for telephony services offered
via SIP to communicate the authenticated identity of subscribers over a trusted
network, but also withhold this information if a network is not trusted.
The P-Asserted-Identity header contains a URI and optionally a display name
defining the calling party information. P-Asserted-Identity can be added by
a user agent or a proxy. The P-Preferred-Identity header, when included, suggests
the identity that should be asserted by the proxy. P-Preferred-Identity can
only be sent by a user agent to a trusted proxy. If a user agent does not want
the asserted information to be forwarded to a non-trusted proxy or endpoint,
it will include the ‘Privacy: id’ header so that the proxy knows
to strip the P-Asserted-Identity header when sending to a non-trusted entity.
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), 3
(Q.1912.5 coded as sip uri), 4 (Ppreferred tel uri) and
5 (Ppreferred sip uri).
3553 Support for UPDATE added
Upon receipt of an UPDATE request, the Tenor was unable to send anything back.
Support for UPDATE has been added to the Tenor. Now, upon receipt of an UPDATE,
the Tenor responds and the call proceeds normally.
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.
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.
3589 Dial Tone Detection improved
The Tenor's dial tone detection algorithm has been improved to include configurable
detection parameters (using the var_config.cfg file). The following
parameters are available for configuration:
DialtoneDbLowThreshold. Valid entry: Between -38 and -20
dBm. Default: -30 dBm.
DialtoneDuration. Valid entry: Between 100 and 32767 msec.
Default: 500 msec.
DialtoneSNR. Valid entry: Between 25% and 87%. Default: 80
%.
DialtoneLowFrequency. Valid entry: Between 250 and 400 Hz.
Default: 325 Hz.
DialtoneHighFrequency. Valid entry: Between 500 and 700 Hz.
Default: 625 Hz.
To use the new defaults, leave the parameters as is. To change the parameters,
place an entry in the var_config.cfg file for each parameter
that needs to be changed. Following is an example of a valid var_config.cfg
file:
DialtoneSNR 85
DialtoneDbLowThreshold -25
DialtoneDuration 1000
DialtoneLowFrequency 350
DialtoneHighFrequency 550
In this example, the dial tone strength will need to be -25 dBm or greater
to be detected. It will have to be present for at least 1 second (1000 msec).
The dial tone frequency will need to be in the 350 to 550 Hz range. Also, the
signal energy in the 350 - 550 Hz range has to be at least 85% of the total
signal energy.
See the Command
Reference for additional information about the var_config.cfg
file.
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.
3608 Digest Authentication Nonce Count increment issue
The Tenor now increments the nounce count for each re-registration request.
The SIPIncrementNonceCount command is available through the
var_config.cfg file. Enter SIPIncrementNonceCount 1
to enable this feature.
See the Command
Reference for additional information about the var_config.cfg
file.
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.
3653 Busyout Feature (DX only)
In case of a proxy server down or a network down, the Tenor can now generate
an alarm on T1/E1 in the system to prevent subsequent incoming calls via T1/E1.
A new feature, GKBusyOut (available through the CLI and Configuration
Manager) has been implemented for you to enable/disable this feature.
The new command, GKBusyOut, is available through SIPSG
and H323SG. Valid values: 0, 1,
2,....10 (the number of times to try before
generating an alarm). Default value: 0.
See the Command
Reference for additional information about the configuration options.
3654 Tenor system information displayed on main page of Tenor Configuration
main window
In the Configuration Manager's main window, the Tenor's system information
and overall system status information is displayed. A sample is below:
Manufacture : Quintum Tech.
Product Name : Tenor DX
H/W Version : 2.0
S/W Version : 2.2.3
Port Info : 8:8
Protocol : SIP
Status : Registered
Network : Static 211.45.14.165
Total Call: 3 Call
3655 Support for SIP Static Route
The Tenor now supports SIP static routes. Each static route must be configured
to register with the Gatekeeper and it is set to a Border Element by default.
If there are duplicate DNs in the Static Routes, the Tenor will pick the first
match. When a static route is selected it assumes Port = 5060. The number pattern
can include wildcards.
The following fields are used to configure State Route:
DirectGWRouting (available under SIPSG).
This enables Static Route. Valid values: 0 (disabled) or 1
(enable). Default is 0. To enable Static Route, you must configure
this field as 1.
Registered (available under StaticRoute).
This configures the Static Route to register with the Gatekeeper. Valid values:
0 (sets Static Route with Border Element) or 1
(sets Static Route with Gatekeeper). Default value: 0. You must configure 1
to register with the Gatekeeper.
In addition, in the destination Tenor, configure AllowOnlyProxyCalls
(available under SIPSG) to 0 (disabled)
to allow calls from any Gateway. As an option, you can also configure the port
number of the Primary Server used to make outgoing SIP calls. This is available
through the PrimarySIPServerPort field (available under SIPSG).
3673 Call Log display now available
A new command cmd calllog is now available through the CLI
to display the current call history. Through this command, a call log (including
a call history) is displayed. In addition, call status is shown on the Tenor
Configuration Manager's main window.
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 LocalNxxRetry 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.
3695 Call Restriction added for specific number or prefix
In the Tenor, a new capability has been added to the InboundDNISXlation table.
When you configure a specific call pattern or prefix in this table, any incoming
calls that match this pattern will be rejected.
3719 Tenor now includes SIP registration with expiry = 0 on bootup
A new feature enables the Tenor on bootup to send a SIP Registration with Expiry
= 0, and then follow up with an RegisterExpiryTime which equals the configured
value from SIPSG.
A new command SIPRegisterOnBootup (available through SIPSG)
is used to configure SIP registration on bootup. Valid entries: 0
(disabled) or 1 (enabled). Default: 0. To enable this new feature,
enter SIPRegisterOnBootup 1.
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).
3732 Enhanced event log dump (ev d module)
A new feature now enables the Tenor to dump a specific individual module event
log. The command is ev d <modulename>. For example, ev
d ch will dump only the ch event log. For more information about event
log, see the Command
Reference.
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.
3793 PING request added
A new feature now enables the Tenor to send periodic ping messages to the server
to let the other end know that the Tenor is still alive. You can configure this
feature through the var_config.cfg file using the following
entries: SipPingInterval and SipPingName.
SipPingInterval. Determines whether PING requests will be
sent. Valid entry: 0 (disable, No Ping requests will be sent)
or a value (seconds between ping requests). For example: SipPingInterval
60.
SipPingName. Used as the name (number) part of Ping's Request
uri and To header. Valid entry: name/number to be used for
Request uri and To header. For example: SipPingName 17325550001.
See the Command
Reference for additional information about the var_config.cfg
file.
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.
3799 Microsoft Cause Code /Sip response configuration
The Tenor now has a new feature where PSTN cause codes are mapped to SIP cause
codes, and vice versa. For example, a cause code for SIP is mapped to the corresponding
cause code for PSTN. A new CLI command cmd sip map displays
the list the cause codes mapped.
For example, a mapping can occur from 17 to 503. If a 17 cause code is received
from the PSTN, it is converted to a 503 SIP response.
3802 Microsoft phone-context support
The Tenor now supports sending a phone-context parameter in the SIP URI for
inbound calls. A new Phone-context configuration parameter, SipPhoneContextText,
is now configurable on the Tenor through the var_config.cfg
file. This configuration parameter enables the ability to add phone-context
in the SIP URIs. The phone-context will be added if there is a valid string
in the SipPhoneContextText. Otherwise, if the SipPhoneContextText file is empty,
nothing will be added.
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).
3830 New default for DialPlanCountry
A new feature enables the default for DialPlanCountry (available
under DialPlan) to be 255 (No dial plan, none).
For more information about DialPlan, see the Command
Reference.
3851 Added support for 'ResourcesAvailableIndicate' (RAI) in H.323
A new features is supported on the Tenor to generate 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).
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.
3879 Command display expanded
The cmd support command has been expanded to include more
engineering support functions.
3890 Caller ID check improved on outbound calls
A new feature enables all inbound inbound calls to have their Caller ID replaced
with a default ANI configured. Configure the steps which follow to enable this
feature.
Step 1. Enter Default ANI
In the CallerIDXlationDirectory, an entry with a pattern value of a single
'*' will represent the default ANI specified by the value of the replacement
field.
For example, to specify a default inbound ANI of 7325551212, the following
CallerIDXlation Table needs to be specified.
index Pattern Replacement
----- ------------------------ ------------------------
1 * 7325551212
Step 2. Specify Table
You must specify a table to include the destination number pattern and minimum
Caller ID length. You can configure this table through the var_config.cfg
file. The following line will specify an entry in the table: CIDLenCheck
<destination pattern> <minimum length>. This line may be
repeated for multiple entries; up to 20 entries are supported.
For example, to enter minimum caller id length of 5 for calls to China ( country
code of 86), the following line is added to the var_config.cfg: CIDLenCheck
86 5. If an outgoing call matches the pattern and a caller id is not
present, or if the caller id length is less than the minimum specified, the
call is not sent out the outgoing trunk.
See the Command
Reference for additional information about the var_config.cfg
file.
Step 3. Enter RelayANI value
Configure RelayANI 4 (available through CASSG,
ISDNSG, and IPRG) to enable this feature on
corresponding outgoing LCRG/TCRG/IPRG.
3892 Wild card number matching
For IVR configuration, the ivr command (available through
the varconfig.cfg file) uses the accessnumber field to match
the incoming access number with exact number matching. As an enhancement, this
command will now accept * as a wild card for matching.
For example, ivr 1732460* will match any number starting
with 1732460.
See the Command
Reference for additional information about the var_config.cfg
file.
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.
3918 Dial Plan: Allow Routing of Unmatched (Bad Format) Numbers
A new Dial Plan feature allows a dialed number to be routed,
even if it does not fit the UPDP parameters.
When this new command, AllowUnmatchedNumbers (available through
DialPlan) is set to 1, any number not matching
the dial plan (UPDP or pre-programmed), will proceed with the dial plan with
an inter-digit timeout. After the inter-digit timeout, the call will proceed
with normal routing. These numbers will be set with a public number plan and
unknown number type. Valid values for AllowUnmatchedNumbers
are 0 (default, disabled) and 1 (enabled).
3950 User is now alerted on failed SIP registration
When a SIP agent registration fails, the user can pick up the phone on a non-registered
channel, and a fast busy tone will be provided on FXS ports when off-hook.
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.
4062 Microsoft: Send Progress to Disable T310 Timer
On an incoming SETUP message from the PRI, Tenor would return a CALL PROC and
route a call to the outbound leg. The incoming switch then started a T310 timer
(typically 10 seconds if the network side and 30 seconds if user side). If the
Tenor responded with a subsequent Progress, Alerting or Connect message before
T310 expired, the incoming switch tore down the call. T310 is typically the
time required to route to the destination. In cases where the outgoing takes
a long time to route a call, T310 expires and the call gets torn down. This
new feature will prevent the T310 timer from expiring.
Two new configuration parameters, available through the varconfig.cfg
file are added:
SendProgressToDisableT310. This is the number of seconds
that the Tenor will wait before sending the "false" PROGRESS message.
Valid ranges 0 - 179.
SendProgressToDisableT310PI. A progress message with the
progress indicator sent to disable the other side's T310. Valid ranges 1 - 8.
4149 Reject Video Call method configurable (ISND signaling only)
Currently, the Tenor does not route data calls (video is a data call) over
IP, but routes them over TDM. If no route is found, the Tenor will respond with
Call Proceeding followed by Disconnect with cause code 34. Now, the Tenor can
immediately send a Release Complete and the video call is rejected with cause
code 88.
To configure this new feature, a new parameter RejectVideoCall is
configurable through the var_config.cfg file. Valid entry:
0 (the video calls are immediately reject with the cause value
set to the value specified in RejectVideoCall.
This is applicable to ISDN signaling only.
Resolved Inconsistencies
This sections includes inconsistencies resolved in P106-12-00, as well as inconsistencies
resolved in Maintenance Releases P105-01-00 through P105-14-00.
2720 SNTPClient: Server returned invalid data is ambiguous
For SNTP, the server was returning ambiguous error messages (i.e., excp |01/01|
2006/03/06|16:42:48:700 |> TEL < SNTPClient: Server returned invalid data.).
These messages are now more clear.
3282 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. Multipath calls are now working
correctly.
3341 SIP modem call failed under certain condition (Analog only)
The SIP modem call failed when FMC was set to clear channel/16/24/32/40kbps.
This has been resolved.
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.
3396 FXO port is blocked sometimes
Occasionally, busyout FXO did not work correctly. This has been resolved.
3472/3840 DMT test results did not show errors
The DMT Manufacturing test did not report errors correctly. This has been resolved.
3499 Two stage dialing operating inconsistent
Through different configuration scenarios, Two Stage Dialing worked inconsistently.
3522 DHCP problem: Tenor never gets an IP address
After running a setfactory command and booting up the Tenor, it never received
an IP address, even though the login prompt appeared and login was successful.
An error message appeared on the screen: "0x95aeb730 (CH ): arpresolve:
can't allocate llinfo". This has been resolved.
3525 Empty OutboundPrimaryServer field does not take affect
In the SIPSG (through Configuration Manager or CLI), if the
field OutboundPrimaryServer was not configured with a valid
IP address, messages would still be sent to the OutboundPrimaryServer address
previously configured. This has been resolved.
3529 Incoming PRACK triggered second Call
An incoming PRACK launched a second call to the PBX side. This has been resolved.
3534 No alarm report generated when false login attempt is made from GUI
The Tenor did not generate an alarm report when a login was attempted with
an invalid username/password through the Configuration Manager. This has been
resolved.
3538 Error in Help for Connect Timer
In the Command Reference document, the values for Connect Timer values were
incorrect. The default setting was documented as 10 seconds, rather than 30.
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.
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). This configuration is now working.
3556 3rd Column help incorrect for PTE
The 3rd column help was incorrect for PTE. It has been corrected to the following:
2 Enabled, Try IP first
3 Enabled, Block of channels
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.
3572 Timing of Refer handling not working correctly
The 202 Accepted and BYE messages were being sent at the wrong time during
Refer. As a result of these issues, unattended call transfer did not work properly.
Unattended Call Transfer is now working correctly.
3585 Non-numeric digits are now supported
On outbound SIP calls, digits other than 0-9, *, # and + are now supported.
3613 User able to FTP when Allow Management Access was disabled
Using the Ethernet Interface parameter, (when AllowManagementAccess
option was disabled) the FTP port was working. In this case, both telnet and
FTP ports should not have been working at the same time. This has been resolved.
3614 Management Access did not work as expected
When the Management Access field was configured as disabled (disables access
to the management port for Telnet/FTP connections), and the change was submitted,
Telnet should have completed the current session. Instead, Telnet became unavailable
before the submit. This has been resolved.
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).
3636 Facility Message Resets Digital Tenors Using IVR
The Tenor reset if an ISDN Facility Message was received for a call which
was currently being handled by the built-in Tenor IVR function.
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. This has been resolved.
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. This has been resolved.
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.
3646 Certain IVR fields were not working correctly
The IVRCardNumLength and IVRAccountNumLength
fields (available under TrunkCircuitRoutingGroup, LineCircuitRoutingGroup
and IPRoutingGroup) were ignored and had no effect. This has
been resolved.
3650 SIP: ACK branch construction changes
For SIP calls, the branch in ACK should have been different for 200 OK, but
should be the same for failure (456XX) responses. This was not working correctly
in the Tenor. Now, for a successful SIP call, the INVITE and ACK has different
branch values in Via header.
3651 UDP ports not freed up
UDP ports were not freed up during certain transfer scenarios. As a result,
after a certain point, the system would not make anymore calls. This has been
resolved.
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.
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.
3668 In certain T.38 situations, calls were failing
When T.38 negotiations happened with multiple m= lines in SDP, calls were failing.
This has been resolved.
3670 Using certain Tenor port would cause the unit to crash
Using port 9001 would cause the Tenor to crash. Now, using port 9001 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.
3676 Alerting message with PI = 2 did not result in generating local Ringback
When the Tenor received an H.323 IP call and the Progress Indicator was equal
to 2, it generated a local ringback. A new command inbandprogind xx
can be configured in the var_config.cfg file to indicate
that when a progress indicator xx is received, the Tenor assumes that progress
messages will be provided inband from the far-end GW.
See the Command
Reference for additional information about the var_config.cfg
file.
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. This field is now populated correctly.
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. This has been resolved.
3694 DHCP error message appeared even after problem was resolved
When the Tenor had DHCP enabled, but the DHCP server was down, or not accessible,
the Tenor failed to get an IP address and the following error message was displayed,
"arpresolve: can't allocate llinfo". Even after the DHCP server was
started, the same error message was displayed. As a fix, the Tenor will now
reboot in this specific situation.
3702 3rd column help incorrect for RegisterExpiryTime field
The CLI"s 3rd column help for RegisterExpiryTime (available
under SIPSG) was listed as "never register" even
when the parameter was greater than 0. This has been resolved to include the
"number of second" next to the entry.
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.
3707 Status DS1 stopped Telnet session
When issuing st ds1 to Tenor CMS through Telnet, the Telnet
session stopped working. The screen output did not make sense. This has been
resolved.
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.
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. This has been resolved.
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.
3720 No CallerID for incoming H323 calls
Under certain circumstances using H323 calls, Caller ID was not working correctly
or being sent out the line side. CallerID is now working correctly.
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.
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.
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.
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.
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-based modem calls not working under specific configurations
In a few cases, SIP-based modem calls were not working under specific configurations.
Now, SIP modem calls are working correctly.
3748 Tenor DSPs became unavailable when used with Reverse Battery Caller ID
In certain situations, the Tenor's DSPs became unavailable when used with Reverse
Battery Caller ID. The DSPs got stuck in an "open" state. The only
way to recover would be to reset the Tenor.
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.
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.
3767 Music on-hold not set up correctly
The music to be played when a caller was "on hold" was not set up
correctly. This has been resolved.
3771 Unable to delete 2nd contact under SIP User Agent
When the 2nd contact field under SIP User Agent was configured and then deleted
through the Tenor Configuration Manager, when the changes were submitted, the
contact still remained. Also, once the fields under SIP User Agent were configured,
these fields were unable to be changed through the CLI. This has been resolved.
3772 Reset may have resulted if ARP resolution failed
A Tenor may have reset in some cases if an incoming IP call was made to a phone
connected to a FXS port and the incoming IP call was the first call after a
reset.
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.
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).
3791 Random CallRelay 60 Resets
Under a heavy load, random resets occurred occasionally with the CallRelay
60 product in certain environments. This issue has been resolved.
3810 Using SIP, decoding of Replace header did not support '&'
If a REFER request with a Replace header containing an '&'
was received by the Tenor, the decoding of the request failed. This has been
resolved.
3811 Fax parameters in Initial Invite caused DSP problems
The Tenor was allowing fax for the initial Invite, rather than entering audio
mode first and then changing media to T.38. This caused DSP problems, but has
been resolved.
3813 Random Tenor CallRelay 60 H.245 Resets
Under a heavy load, random resets related to reception processing of H.245
packets has been resolved.
3814 Digits dialed in INFO message with Sending Complete IE were ignored
When a setup message was sent out, followed by two INFO messages with Sending
Complete, only the digits in the first INFO message were acknowledged. The digits
in the second INFO message were ignored. This has been resolved to identify
the digits correctly.
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 to
be unable to generate or receive network traffic, and thus appear to hang. This
problem has been resolved.
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.
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.
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.
3826 Tenor DX failure to boot
Tenor DX would fail to boot if a configuration database with different number
of T1 spans 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.
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. This has been resolved.
3837 Tenor not properly decoding SIP message
The Tenor was not properly decoding the Contact header for a SIP Invite message
if it contained a * character. This has been resolved.
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.
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. This has been resolved.
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 happened when the Tenor attempted to resend the message.
3852 Improper SIP TCP Socket Management In Certain Error Cases
The Tenor improperly deallocated network sockets when certain unusual 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 depleted memory buffer pools when SIP authentications took place
using TCP transport. This has been resolved.
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. This has been resolved.
3862 Caller ID detection failed under rare condition
A rare problem appeared where Caller ID was not detected from the PSTN side.
Caller ID is now working correctly.
3863 Improper Memory Management For Certain SIP Response Messages
In the Tenor, at the reception of a response message containing code 181 (Call
is being forwarded), caused memory not to be deallocated. This has been resolved.
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 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.
3880 Under rare situations the Call Relay SP setup calls with one-way audio
transport (CR-SP only)
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 and running at full capacity,
rebooted after a long period of time.
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.
3895 Multiple FIPD attachment caused system reset
After adding multiple Filter IP Directories, attaching them and submitting,
the Tenor would reset. As a result, the entries would not re-appear. This has
been resolved.
3898 Handling of TCP sockets for SIP calls made more efficient
The handling of TCP sockets for SIP calls has been made more efficient. This
has been resolved.
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.
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. This has been resolved.
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.
3913 Played wrong prompt when RADIUS return code 7 was received
When Radius returned "Return Code 7" in the authentication response,
the Tenor played the "Account Expired" prompt. The same prompt was
used when Radius returned "Return Code 7" in authorization response.
The Tenor now plays the appropriate response.
3914 Incorrect conversion of H.245 DTMF digits to SIP RFC2833 message insertion
Some devices did not generate DTMF digits when RFC2833 packets were generated
by the Tenor. This happened when the Tenor converted DTMF digits received as
H.245 messages to RFC2833.
3915 Call Transfer failed
In the Tenor, it was possible that call transfer failed if the refer-to had
a DNS address as opposed to an IP address in the incoming Refer Method. It succeeded
most of the time, but some proxies would fail when the Tenor tried to contact
the new endpoint using the IP instead of DNS. Call Transfer now works correctly.
3922 Occasional static at the beginning of IP call (CMS only)
Occasionally, at random times, static could be heard at the beginning of IP
to circuit calls. This has been resolved to eliminate the static.
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.
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.
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.
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.
The Tenor now accepts these headers.
3592 Improper global call pickup handling
The global call pickup handling feature was not working correctly. This has
been resolved.
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.
3955 Private number dialed was being normalized as public at the destination
When a private IP call was made, the incoming number at the destination was
normalized as public and the call failed. This has been resolved.
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.
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. This has been resolved.
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. This has been resolved.
3964 "Proxy Fail-Over Behavior" options were being inter-changed
For ProxyFailOverBehavior (available through SIPSG),
the two options No Fail-Over (Always try the 1st Proxy) and
Fail-Over on Error Response were being inter-changed. This
has been resolved to work correctly.
3972 No ANI delivered when only private HuntLDN was configured
If there was no public HuntLDN configured, and only the private HuntLDN was
present, the private number dialed had a blank ANI. The ANI is now being delivered
correctly.
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. This has been resolved.
3986 SIP Notify Message may have caused Memory Leak
When the Tenor received a SIP notify message, it caused a memory leak. This
has been resolved.
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. The medial loopback problem as been resolved.
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.
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. Now, the configured entry stays in place.
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. Caller ID name is now working properly.
4003 Tenor loaded with saved database did not bootup with the loaded database
When a Tenor was loaded with a saved database, it did not boot up with the
loaded database after reset through the Tenor Configuration Manager. This has
been corrected so the saved database will load properly.
4007 Fax with redirect failed
When the Tenor initiated a call, the call was re-directed and came up. But
when the Tenor detected the fax and sent a re-invite, the re-invite also got
re-directed and did not work as expected. This has been resolved.
4009/4013 Lost CDR data in case of CDR buffer overflow
When the CDR buffer counter has reached its threshold, any overflow caused
all CDRs in the database to be lost (7801 CDRs is maximum stored). In order
to inform the user about CDR buffer overflow, there is a new configuration option
to generate an alarm. This new configuration field CdrAlarmThreshold
cdrcounter (where cdrcounter is the CDR counter left in the
CDR buffer, maximum entry is 7801) is available through the var_config.cfg
file.
For example, enter CdrAlarmThreshold 10. The following will
happen:
- Generate alarm when CDR is overwrote
- Clears alarm when CDR buffer has more than 10 call buffer.
See the Command
Reference for additional information about the var_config.cfg
file.
4015 LAN Redirect Issue for the gateway address
If the default gateway was set to an IP on the Tenor, and the network "LAN"
redirected the IP traffic to another IP gateway address, the Tenor built dynamic
host tables for these new destinations and the calls were successful. As a result,
when too many dynamic host tables were built, the Tenor was not accessible via
telnet, FTP, or until that system reboot. This has been resolved.
4016 Message decoding error with Microsoft Exchange
During fax testing with Microsoft Exchange, there was a problem where the Tenor
did not recognize the ACK message sent from Exchange. Now, the Tenor recognizes
the ACK messages.
4018 PRI Outbound DNIS was not working properly
The first digit in PRI setup message was being deleted. The Tenor now accepts
the first digit.
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.
4028 NI-2 User Side: Call Failed on "Fast Connect"
For the NI-2 (ISDN protocol) user side, when the network returned a Connect
message in response to an outgoing Setup message from the user side, the call
failed. This has been resolved for NI-2 to be accepted.
4029/4060 Enabling RPID reset unit
Enabling RPID caused the system to reset. This has been resolved.
4030 DSPs got stuck in closing state
Under some error conditions, DSPs got stuck in closing state. The DSP functionality
now works correctly.
4032 Channel created without FXS card
If a Tenor did not have an FXS card installed, it still made 0-FXS channel
registration on reboot. The database created an AnalogInterface-phone object
with no channel. The creation of AnalogInterface-phone was unnecessary since
there was no channel underneath. This has been resolved.
4042 Caller ID detection in Japan not working as expected
Caller ID detection in Japan (from NTT PSTN lines) has been inconsistent; the
PSTN started sending the Caller ID signal but then terminated it. This has been
resolved.
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.
4053 Call Transfer caused REFER to be rejected
The SIP INVITEs can be forked, and when call transfer is done, the Refer-To
header and Replaces should use the "tags" in the connected endpoint.
The "tags" used were from the endpoint which sent the first provisional
response. This caused the REFER to be rejected. Call Transfer now works correctly.
4063 MFG test did not catch DAA cards that caused reflections
If there was a faulty DAA card, it caused reflections. If one of these cards
was installed, and the MFG test was executed, the errors due to reflected digits
were not caught by the MFG software.
4064 Tenor AX Series not displayed correctly
The Tenor Configuration Manager was not correctly displaying the Tenor AX series
product line. This has been corrected.
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.
4071 DN registration was not working
When a DN was removed from Static Route, DN registration was not working correctly.
This has been fixed.
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 independently
Outbound CID translation did not work for outgoing IP calls if the Inbound
CID translation table was not used. These two tables should work independently.
This has been resolved.
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.
4085 Failure response not properly sent/received
When a 603 failure response was received, it was not used properly and a 601
failure response was used instead. This has been resolved to use the correct
response.
4092 FGD not working
When the Tenor routed a call with no DNIS, FGD (Feature Group D) did not work.
FGD is now working properly.
4097 Caller ID check for inbound SIP call fails
For an incoming SIP call without a caller ID, the call should have been rejected
if the configuration was set correctly. Now, the call will be rejected as configured.
4105 SIP Call waiting caused reset
Due to a SIP timer issue, under a specific circumstance, the SIP call waiting
feature caused the unit to reset. This has been resolved.
4112 Channel not put in service when RESTART received using NI2 protocol
If the PSTN switch sent a RESTART message to the Tenor, any channel, or all
channels of the entire DS1 interface, the applicable channels were not being
returned to service. This appeared when using NI2 protocol.
4115 Transfer failed for long phone number/DNS
If a transfer happened to a long (>32) phone number or DNS name, the transfer
would fail. As a fix, the Tenor can now support up to a 64 byte length phone
number/DNS name.
4117 SIP INVITE without SDP not processed correctly
When the Tenor received a SIP INVITE without SDP, the Tenor reported an encode
error when returning the Alerting/Progress/Connect responses with SDP.
4122 Radius StopAccounting message did not have overlap dialed digits
Tenor sent the wrong (partial) Called-Station-Id attribute, equal to the first
part of the DN received through Overlap Dialing. The Tenor now sends the complete
DN received.
4128 Heavily loaded system using SIP caused buffer pool depletion and reset
A heavily loaded CR-SP using SIP caused reset due to buffer depletion. The
problem has been resolved.
4129 SIP INVITE transaction not optimized
For SIP INVITE transactions, if a failure response was received, there was
no need to keep the transaction longer than the 4 seconds previously set. A
new configuration option enables you to set the SIP INVITE transaction to be
cleared after 500 msec. This allows the memory to be freed up sooner.
The new parameter, SIPCleanupTransactionsTimeout 4000 (in
msec), can be entered through the var_config.cfg file.
See the Command
Reference for additional information about the var_config.cfg
file.
4137 PRACK support changed
Previously, the Tenor enabled the PRACK message if both caller and called party
support PRACK. The Tenor now enables the PRACK message only if one side requires
it and the other side supports it.
4146 Provisional Msg Attached to Incoming Setup Msg caused reset
For H.323 calls, the Tenor reset upon receiving a provisional message along
with the incoming setup message (protocol violation).
4148 Tenor did not Respond to RESTART Message
Under a certain setup configuration, one Tenor sent a Restart message and the
receiving Tenor did not respond with a Restart-Ack message, leaving the channels
out of service at the PBX. This has been resolved.
4162 Call hold after call transfer caused reset
While attempting a call hold after call transfer, the Tenor reset. This was
due to an internal error and has been resolved.
4167 Dropped media packets caused bad voice quality
The Tenor dropped media packets under moderate/heavy jitter conditions, resulting
in bad voice quality. This has been resolved.
Other Changes
This sections includes other general changes (such as interoperability changes
and configuration option changes) in P106-12-00, as well as changes that occurred
in Maintenance Releases P105-01-00 through P105-14-00.
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.
3691 Language selection using IVRType 2 when pre-authentication fails
If pre-authentication fails, when IVRType is configured as
2 ( prepaid calling card),a message is now played for selecting
a language, followed by the prompt "enter PIN number" played in that
selected language.
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.
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.
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.
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.
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.
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.
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.
3846 Systemuptime command not working correctly
The systemuptime command (displays how much time has elapsed
since the last system reset) displays misleading data. The command output is
correct as long as the system up-time is less than 62 days, 3 hours and about
18.5 minutes. Otherwise, if the system has been up longer than this time period,
due to a wrap-around condition in the code, the system up-time also wraps around
and starts from 0 again. This gives the impression that the system has reset
on its own, even though it hasn't.
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.
4138 SIP Session Timer refresh time changed
To enhance the SIP feature, the session timer refresh mechanism has been changed
to optimize the number of SIP INVITES sent from the Tenor, while still maximizing
the benefit from using Session Timers.
Open Inconsistencies
This section includes open inconsistencies in Release P106-12-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.
538 G.726 codecs do not work
None of the ADPCM (G.726) Codecs work with the Tenor. This problem applies
to codecs for voice calls only, and not for FoIP and MoIP.
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/AF 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 Tenor S onto a unit running Tenor P software, there was a problem
with port usage. When migrating from a Tenor S to a Tenor P, or vice versa,
a setfactory command must be done on the Tenor, and then the
unit can be configured manually. The database will not get converted from one
to the other.
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.
| 
