 |
| |||||||||||||
|
|
| |||||||||||||
|
|
Release Notes for P105 Patch ReleasesTenor Gateways and Call RelaysThese patch release notes apply to the following products;
A software patch is a release of software that has been created by Quintum to resolve an inconsistency or 'bug' that has been identified within a previous release of Generally Available (GA) software or patch. They may also add features. Patch software does not go through any testing from Quintum, but has been verified by the customer that the identified the bug is resolved with this patch. Patches (for Second Generation Tenors) can be identified by the 3rd set of digits in the release name as PX-Y-Z. Where the Z is the patch number. All patches will be built on top of the latest GA release of software. For example, P102-11-00 is the latest GA software, then the first patch for this software will be P102-11-01. If additional patches are required for a specific GA release, each new patch will contain all previous patch fixes. For example, the patch P100-11-02 will include all patches from P100-11-01. On a scheduled basis, Quintum will release a full GA version that will include all previous patches and will have been put through our full system tests. We hope that this process will aid our customers by providing fixes in a more rapid manner. CMS COMPATIBILITY NOTE: P101 and LATER CODE ON CMS ONLY SUPPORTS SERIES 2 CONTROLLER AND PERIPHERAL CARDS! See this document for more details: http://www.quintum.com/support/products/2G/cms/sysdoc/CMS_series2_notice.pdf
Known Open Inconstancies and AnomaliesNoneResolved Issues and Feature EnhancementsP105-19-123499 Corrected inconstant two stage dialing operation
3590 Added authentication based upon DNIS in IVR type 9
3708 Autoswitch number not recognized when prefixed with long distance prefix
3717 IVR interdigit timeout incorrectly forced to 3 seconds when ivrCardLength is not 255
3723 Added optional PSTN call termination indication tone configurable by CallTerminationINDication in LCRG/TCRG
3739 FXO channels may remain off-hook when PassThrough is set to "Enabled Block of Channels"
3742 Added ability to perform DNIS-based authentication after normalization
3748 Tenor Analog DSP's may become unavailable when used with Reverse Battery Caller ID
3772 Reset may result in some cases if ARP resolution fails
3779 When performing a factory default, 'teltrail.log' is now cleared
3794 Added 'h323-ivr-out' to RADIUS authentication to enhance PortaBilling Interoperability
3818 Changed ISDN cause value 88 to generate an alternate SIP Response code to enhance Microsoft OCS interoperability
3836 Allow SelectNet for IP Trunking Calls from TCRG
3851 Added support for 'ResourcesAvailableIndicate' (RAI) in H.323
3867 Added indication that a reboot is required after performing a factory default
3880 Under rare situations the Call Relay SP setup calls with one-way audio transport
3881 Call Relay incorrectly passing GSM codec in SIP SDP in a Reinvite Message
3882 Call Relay SP reboot after long period of full load operation
3895 Multiple FIPD attachment causes system reset
3900 SIP 'Refer' not working if 'Bye' received immediately after '202 Accepted' sent
3904 HND translated event log entry reinstated
3910 Security Enhancements for Telnet/FTP
3913 Playout appropriate prompt when RADIUS return code 7 is received
3914 Incorrect conversion of H.245 DTMF digits to SIP RFC2833 message insertion
3948 EPAD SourceCallSignalAddress Security Problem
3959 Added Call Throttling Origination IP Address to event log
3962 Generate ringback tone in slow-start H.323 call setup procedure
3974 Remote Party ID Privacy value always set to "full"
3975 Incorrect calculation of Gatekeeper port usage versus license
3984 Callers Hearing Busy Tone Before Connect
3986 SIP Notify Message Could Cause Memory Leak
3987 Call Relay 60 data alignment problem with media loopback causing reset
3990 Incorrect data displayed on active 'call' output
P105-19-113569 Received RTP Packet Validation Algorithm
3591 Allow 'replaces' tag in 'Supported' and 'Required' SIP headers
3592 Improper global call pickup handling
3638 Unable to delete configuration parameters contains a space character via the CLI
3641 Description field under Radius Servers discards strings ending in a space character
3767 Improper music on hold handling
3817 SSG events cause reset of Tenor AXT series
3819 Allow Japan NAVI dial (0570-0xxxxxx) calls
3822 Improper handling of Channel Group names containing spaces
3822 Improper handling of Channel Group names containing spaces
3835 RPID not being passed on H323 to SIP calls on Call Relay series products
3859 Enhanced Tenor GUI Reset log message
3860 RADIUS does not report new Tenor IP acquired by PPPOE mechanism
3860 RADIUS does not report new Tenor IP acquired by PPPOE mechanism
3862 FSK based Caller ID detection fails if received after 2nd ring
3865 A HND object containing a space character looses its configuration
3875 Unconfigured Tenor yields '(tNetTask): arptnew failed on 7f000001' console messages
3878 Modified SIP restricted caller ID handling for better OCS Interoperability
P105-19-103796 Tenor DXi Manufacturing Test EnhancementAdded support for proper LED handling to reflect the pass/fail status of the Tenor DXi Manufacturing test including the PCIe bus test. Also enabled test operation using the Tenor DXi in a manufacturing test fixture instead of a PC environment. 3863 Improper Memory Management For Certain SIP Response MessagesResolved an issue whereby receive SIP response message processing may result in the improper deallocation of memory buffers. In particular, reception of a response message containing code 181 (Call is being forwarded), caused this condition. P105-19-093852 Improper SIP TCP Socket Management In Certain Error CasesResolved an issue whereby the Tenor gateways would improperly deallocate network sockets when certain error cases in the normal call flow occurred. This would eventually result in the depletion of network sockets, and the inability of Tenor to process new calls. 3853 Buffer Leak When Using TCP SIP AuthenticationResolved an issue whereby the Tenor gateways would deplete 1K memory buffer pools when SIP authentications would take place using TCP transport. Certain 1K memory buffers allocated to receive SIP message processing were improperly being deallocated. P105-19-083636 Facility Message Resets Digital Tenors Using IVRResolved an issue whereby the Digital Tenors DX and Tenor CMS gateways would reset if an ISDN Facility Message were received by the Tenor for a call which is currently being handled by the built-in Tenor IVR function. 3718 Modified H.245 Terminal Capabilities Set EncodingModified 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 resolves certain interoperability issues which could result in improper media stream setup. 3839 SIP Cancel Message Processing Causing Hanging CallsResolved hanging SIP calls cause 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 InteroperabilityResolved an issue whereby the Tenor gateways would reset when using the Tenor Monitor to monitor the gateway. This was caused by incorrect handling of the query for active alarms that the Tenor gateways received from the Tenor Monitor. 3845 TCP SIP Bye Transaction Timeout Socket LeakResolved a problem related to a SIP Bye transaction processing using TCP transport. If a timeout were to occur while waiting for the transaction to complete, a TCP socket leak occur when the Tenor attempts to resend the message. P105-19-072526 Call Routing Server SIP CallsWhen originating SIP call with the Call Routing Server, the Tenor will look up its configured SIPSG's for a IP Address matching the Call Routing Server response in order to determine the applicable SIP parameters to use for the call. 3645 ISDN cause code '44' SIP MappingMapping of ISDN cause code '44' (Requested channel/circuit not available) to a SIP failure code has changed. In prior releases, cause code '44' mapped to a SIP '601 Busy' response. Tenor now maps this cause code to a SIP '503 Service Unavailable' response. 3721 QOS/DiffServ tagging for Call SignalingAll H.323 and SIP signaling packets are now tagged with a configured ToS/Diffserv value. Previously only media packets were tagged and not signaling. The Tos/DiffServ value used to tag signaling and media packets is now configured in the MediaQOSValue attribute in the default IPRG. A gateway reset is required for the new setting to take effect. 3763 New FXS/FXO hardware revision identificationManufacturing test has been modified to be aware of new revisions of FXS/FXO hardware, and respond appropriately. 3791 Random CallRelay 60 ResetsRandom resets occasionally seen in the CallRelay 60 product in certain environments have been resolved. 3796 Manufacturing test support has been added for the Tenor DXiSupport for a new product, the Tenor DXi PCIe Adapter, has been added to Quintum's manufacturing test routines. 3813 Random Tenor CallRelay 60 H.245 ResetsRandom resets related to reception processing of H.245 packets has been resolved. 3816 Network Buffer Resource DepletionPackets sent to unallocated Tenor UDP/RTP ports, would cause eventual Tenor network buffer resource depletion. Over time, this would cause the Tenor not to be able to generate or receive network traffic, and thus appear to hang. This problem has been revolved. 3818 ISDN Cause Code '88' to SIP mapping (Microsoft Interoperability)A modification has been made to the ISDN cause code to SIP message mapping to enhance interoperability with Microsoft Office Communication Server 2007 (OCS). ISDN cause code '88' now maps to a SIP response '400 Bad Request', instead of '503 Service Unavailable' in previous releases. 3821 Tenor CMS and Call Relay SP Web Server (port 8080)In certain circumstances, the Tenor web server would incorrectly close network sockets in a Tenor CMS or Call Relay SP resulting occasionally in a system reset. This problem has been resolved. 3826 Tenor DX failure to bootTenor DX would fail to boot if a configuration database were manually loaded onto the DX which results in a mismatch of the database versus actual DS1 hardware installed in the product. This problem has been resolved. 3827 Single DS1 Span License for Tenor DXiThe product feature license mechanism has been extended to allow for the licensing of a single DS1 span. This is required to support the new Tenor DXi PCIe Adapter product. 3828 CNG Fax Tone Detection When Using G.711 (Microsoft Interoperability)To enhance interoperability with Microsoft Office Communications Server 2007 (OCS), CNG Fax tone detection is enabled when using the G.711 codec. This is in addition to the existing CNG tone detection which currently exists for when using low bit-rate codecs such as G.729 and G.723. 3838 Call Routing Server and IVR Multisession IncompatibilityWhen using IVR Multisession with the Quintum Call Routing server, the second call, if any, would fail. The CMS sends stop accounting to the Call Routing Server after the first call, which causes the Call Routing Server to reject any additional Route requests for that session. This problem has been resolved. P105-19-063423 Multipath Call Failure to FXO Configured For BusyoutResolved Multipath call failure in the case of a fallback to an FXO port which is configured for Busyout. Previously, Multipath calls would not complete when outbound call attempts on a FXO port which was in a Busyout state was attempted. 3423 Tenor DXi PCIe Adapter SupportSupport has been added to the Tenor software to recognize and support the new Tenor DXi PCIe Adapter product line. 3665 Expanded 'show -v' version number fieldThe format of the 'show -v' CLI command output has been changes to allow for longer version numbers. 3713 Normalized Number Printing in Nortel Call FlowNormalized 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 not print correctly. 3714 Increased SIP Stack Size for Tenor AS/AF/AX/DX/BXThe size of the SIP task stack has been increased for Tenor Enterprise Gateways (Tenor AS/AF/AX/DX/BX), and CallRelay 60 product lines. 3759 Remove '+' from Incoming DNIS (Microsoft Interoperability)To enhance interoperability with Microsoft Office Communication Server 2007 (OCS), the Tenor will strip off the leading '+' character in the DNIS number received in incoming SIP INVITE messages from OCS. 3731 Outbound Caller ID Translation ProblemCorrected a malformed Caller ID Information Element which may occur when no Outbound Caller ID Translation is configured in a 'CallerIDXlationDirectory' attached to a 'TCRG' or 'LCRG'. The outbound Caller ID is now correctly formed regardless of the Outbound Caller ID Translation Directory configuration. 3760 Multiple Transactions with TCP SIP SignalingCorrectly supports multiple SIP transactions which may occur over a single TCP connection. Previously the TCP socket was erroneously closed prematurely. 3762 DS1 E1 Transmit Pulse Template AdjustmentAdjusted hardware parameters to meet E1 Transmit Pulse Templates when using newer revision DS1 Framer / LIU. 3766 Changed Default SIP Failure ResponseTo 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 OptimizationThe amount of memory required for internal Caller ID Translation structures has been optimized. 3780 BRI Q.SIG Facility IE ResetResolved an intermittent problem whereby the Tenor BX could reset upon receiving a Q.SIG message which contains a Facility Information Element (IE). 3782 DNS Library OptimizationModified the DNS library to use mutual exclusion methods which have less impact on system performance. 3788 CallRelay SP with H.323 ResetIn certain traffic conditions, the CallRelay SP may reset when processing H.323 calls. The buffer pools that the Memory Manager uses have been optimized to eliminate the condition which causes a reset.
|
