Release Notes for Software Patch Release Tenor AS/AX/DX/BX/CMS P102-11-09 and previous 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-00. 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. The notes below are cumulative since the last GA Release, P102-11-00. The most recent changes are in the top section, the history is similarly in most recent first order. We hope that this process will aid our customers by providing fixes in a more rapid manner. CMS COMPATIBILITY NOTE: P101 and P102 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 ------------------------------------------------------------------------- P102-11-09 The only change in this code is a small change to support recently manufactured AX models. If you are already running P102-11-08, there is no need to update to P102-11-09. If you have an AX with P103-08-00 on it from the factory, and wish to downgrade, you must use P102-11-09! Note: P102-11-09 does support all models of the AS, AX, and DX. BX users must use P103-08-00 or later if they wish to upgrade. ------------------------------------------------------------------------- P102-11-08 *** Bug 1874 Start Accounting packets do not contain correct call type In many cases Start Accounting packets had incorrect call type. This may also have caused a reset if a submit in P102-11-07 if made under certain conditions. This was resolved. *** Bug 1907 Add RtpVerify feature from Gen1 to Gen2 Lately we have seen a few issues w/LinkSys routers and D-Link ADSL modems changing the RTP ports in FastStart element of incoming Q931 messages. This caused the incorrect port to be used, resulting in one-way voice. To workaround this, we also added the capability to put the port number in non-standard data (quintum proprietary portion of the packet) to make sure the port number is properly communicated. This will only work in a Quintum to Quintum call. This is enabled by setting the rtpverify variable in var_config.cfg file. When enabled, the gateway will use the value in non-standard data if it differs from that received in negotiation. rtpverify 1 (enabled) default is disabled *** Bug 1928 display-ie is now disabled by default Recently we added the "Display IE" to allow for CallerID with name. We found some protocols will fail if this is sent. Now, by default, the Display IE will not be sent. *** Bug 1937 IP Translation not happening even though ExtIP is set In certain, fairly rare, circumstances NATAccess IP translation was not occurring. This situation has been resolved. *** Bug 1959 Credit time from previous call used on Customer Care redirect in multi-tenant IVR For those using the customer care redirect feature in multi-tenant IVR there were times where the card user's credit-time was being enforced. This did not make sense for a call to customer care. Customer care calls are no longer timed. *** Bug 1960 Need to protect agaInst, ## from dribbling an extra # and stopping prompt Under certain circumstances, often mobile calls, it was possible the second # in a multisession sequence might be interpreted as a 3rd #, disabling the destination number prompt. This was resolved by ignoing any # during the first 1 second of the destination prompt. *** Bug 1972 CDR formats 0, 100, 1 and 101 should be reenabled For backwards compatibility, the above CDR formats were reenabled in CMS. They had previously been disabled due to the fact they are missing slot information. ------------------------------------------------------------------------- P102-11-07 *** Bug 1645 Ivrmultisession supported in var_config.cfg This new feature allows you to enable/disable IVR multisession through the var_config.cfg file. If you are not familiar with the var_config.cfg mechanism, please go to Quintum's support site at http://www.quintum.com/support and enter the search word var_config.cfg in the search box. The following option is needed in the var_config.cfg file: ivr 2, 3 or 6 (ivrtype)