PRODUCT_LINE: BCM ============================================ TITLE ===== BCM370.250-DSPFW ======================== Release: 3.7 Issue: N/A Category: GEN Superceded By: NONE Release Date: 20080729 Patch Conflict(s): N/A Special Instructions: NO Patch Version: N/A ======================== Software Update Name: BCM370.250-DSPFW Applicable H/W Platforms: BCM200, BCM400, BCM1000, SRG200 1.0, SRG400 1.0 Applicable S/W Platforms: BCM 3.7, SRG 1.0 based on BCM 3.7 Category: GEN Installation Recommendations: This update should be applied to all new installs of BCM 3.7 and SRG 1.0 based on BCM 3.7. Existing installations should have this update applied if they are experiencing any of the issues that are corrected. There is no need to schedule specific maintenance to apply this upgrade if there are no reported issues. In those cases, systems should be updated at the next regular service opportunity. Component & Version: Voice Firmware 37.70.120.9 Dependencies: Required Updates - None Product Dependencies - None Size: ~2.2 MB System Impact: time to apply approximately 20 minutes. Does update application force reboot: yes Other Impacts: None Limitations: None Update Removable: no Description: ----------- The following issues are addressed: 1. T.38 Fax Interoperation with Xerox WorkCenterPro added Added support for interoperation with fax machines requiring echo protect tone for both CallPilot and T.38. Q01658598 This update includes the content of the following superseded updates: BCM370.235-DSPFW --------------------------- 1. T.38 - Inbound faxes disconnect in mid transmission; communication error (Interoperation with CS1K) During interoperation with CS1K, some inbound faxes were failing during the transmission of a page. BCM can now handle the long scanlines and continuous streams of 0s during the page data. Q01594838 2. T.38 - CRP replacing EOP, Short DCS tail and Collisions cause fax to fail (CRP = Command Repeat, EOP = End of Procedure, DCS = Digital Command Signal) Some fax machines have different signal timing characteristics that when traversing T.38 would cause the fax session to fail. Changes have been made to the BCM's T.38 codec to: - not interfere with a fax session's EOP signaling - avoid a race condition internal to T .38 when receiving DCS message with 1 tail flag (normally there are 3 or more) - lengthen the time that T.38 will listen for a response from a local fax machine before disabling the receiver Q01648220 3. IP Set - "beeps" on IP sets coming from the BCM People on IP sets were hearing 'beeps' due to the fax CED detector being too sensitive. The sensitivity of the CED detector was reduced from -40db to -25db. Changes were also made to allow CED to be detected for 250msec before initiating the CED replacement code (already implemented). Q01640437 BCM370.166-DSPFW ----------------------- 1. Spurious reset; IP sets down, Voice Mail down, Send event to DSP error The master DSP was sensitive to corrupted messages from the coreDSP on the D channel. It was previously possible for messages with a corrupted length field to cause corruption of MDSP memory, which in turn could result in a crash of the MDSP. The bug fix introduced by this change prevents the MDSP crash, but does not address the corruption of the D channel message in the coreDSP. Q01350969 2. First couple of words on a call echoed quite loud. The echo canceller's non-linear processor (NLP) doubletalk threshold has been raised by 6dB to account for gain in the echo path introduced in the lossplan. This change will allow the ECAN's NLP to mute residual echo in the time period before the ECAN has converged. Q01331717 3. Some fax machines emit a long CED tone causing Fax machines not to handshake. This change delays the reporting of the CED tone until the end of the CED tone. Q01330782-01 BCM370.102-FW ---------- 1. Fax - High rate of fax failures to CallPilot due to echo in VoIP Gateway Fax would fail in some environments where extreme delay and echo were present. The BCM fax task could sometimes misinterpret an echo of it's own transmitted signal as a remote fax signal, causing the BCM fax to exit 'receive' mode. The fax controller will now re-enter 'receive mode' on the loss of any signal in order to be able to continue to look for a remote fax machines signal after being miss-triggered by it's own echo. Q01183673 BCM_370.099_DSPFW.09.5124 ---------- 1. T.38 - Faxing from Brother 2800 fax machines often fails The end of the page was not detected by BCM's T.38 task due to the Brother 2800 not providing ample silence at the end of the page data. The BCM's T.38 datapump was adjusted to be able to properly detect the short durations of silence at the end of the page. Q00996277 2. T.38 - 70% of the time (at a particular site) fax over IP will not switch to T.38 If a fax machine's answer tone (CED) signal level is lower than the originating fax machine's tone (CNG), it is possible that the BCM's echo canceller mutes a portion of the CED tone, thinking that it is echo. This muting (caused by the non-linear processing - NLP) prevents the BCM's tone detector from detecting CED tone and thus a switch to T.38 never occurs. BCM will now disable the echo cancellor's NLP when it begins detecting CED tone. Q01089594 3. T.38 - UDP Redundancy in high-speed data causes multi-page faxes to fail. UDP Redundancy, used during high-speed data transmission (page data) from some gateways, was causing BCM's T38 connection to fail . The BCM DSP Firmware was changed to allow for the reception of longer packets (due to redundancy). Q01105648