PRODUCT_LINE: BCM ============================================ TITLE ===== BCM.R400.274-CDR ======================== Release: 4.0 Issue: N/A Category: GEN Superceded By: NONE Release Date: 20090324 Patch Conflict(s): N/A Special Instructions: YES Patch Version: N/A ======================== Software Update Name: BCM.R400.274-CDR Applicable H/W Platforms: BCM200, BCM400, BCM1000 Applicable S/W Platforms: BCM4.0 Category: GEN Installation Recommendations: This update should be applied to all new installations of BCM 4.0. 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. It is necessary to remove the CDR client from the host computer and re-install the CDR client from the BCM after the update is applied to the system. Component & Version: cdr 41.11.13.10 cdr-provider 41.11.09.10 cdr-client 41.11.12.10 Dependencies: Required Updates: None Product Dependencies: None Size: 7.7MB System Impact: Time to apply approximately 2 minutes Does update application force reboot: No Other Impacts: None Limitations: Updating Prefix list will not take effect until the Report Filter type is changed. Workaround: When user updates the Prefix list, the Prefix Filter Type must be updated for the change in the Prefix list to take effect. This issue will be addressed with the future software update. Q01983902-01 Update Removable: No Description: ------------ The following issues are addressed. 1. No CDR data when using a prefix filter without account codes When using CDR and selecting a filter type of "prefix" only calls using account codes (F900) are appearing in CDR data. Call that match the "prefix filter" that do not use account codes (F900) are not captured by CDR. This issue is due to mismatch between the values of filter types in the mof file and CDR code. This update resolves the issue by making the value mapping of different filter types same in both mof file and CDR code. Q01943234-01 This update includes the content of the following superseded updates: BCM.R400.260-CDR ----------------- 1. CDR push failures after FTP server is rebooted This update resolves the CDR push failure if the ftp server is rebooted. Q01892101-03 BCM.R400.246-CDR ---------------- 1. CDR stream displays strange characters in CDR live client When multiple transfers happen for a call in the BCM, the amount of data sent to the CDR live client exceeds the maximum buffer size. This results in a buffer overflow and strange characters appear in the CDR live client. This update resolves the issue by increasing the size of the buffer. Q01912410 BCM.R400.225-CDR ---------------- 1. CDR service is going down unexpectedly When an application other than a CDR client connects to the BCM on the Port reserved for CDR, the CDR Service goes down. This update resolves the issue by removing the error handling which causes CDR to go down. Q01884976 BCM.R400.204-CDR ---------------- 1. CDR reports incorrect records for Hunt groups when Manual DND (Feature 85) is programmed on the sets of HG members. This Patch resolves this issue of reporting records in CDR correctly by changing CDR to support manual DND being programmed on HG members. Q01877898 BCM.R400.188-CDR ---------------- 1. CDR shows incorrect records for Hunt group scenario when DND on Busy is enabled. This Patch resolves this issue of reporting records in CDR correctly by changing the CDR design to support when DND on Busy is enabled. Q01841781 BCM.R400.161-CDR ---------------- 1. CDR reports the CLID for incoming calls Intermittently due to active registration of CLID by the other software or equipment. This Patch resolves the issue of recording CLID Intermittently by changing the CDR design to support both active and Passive registration of CLID. Q01738969 BCM.R400.127-CDR ---------------- 1. CDR live client cannot connect to BCM if LAN1 IP address is changed to 192.168.254.x This Patch resolves the issue of CDR live client connecting to the different IP addresses Q01682090 Q01586134 2. Incorrect time display in CDRPullClient which displays transfer time as "24:10" instead of 12:10pm. This patch resolves the improper display of transfer time in CDR pull client. Q01686295-02 BCM.R400.099-CDR ---------------- 1. CDR shows incorrect call duration for some calls. This patch resolves incorrect call durations in CDR records for both Norstar and SL-1 report formats. Q01511761-02 Q01646099 BCM.R400.066-CDR ---------------- 1. CDR multi-party conference records are incorrect most of the time. This patch resolves the issue of incorrect CDR multi-party conference records under various multi-party conference call scenarios. Q01467648 2. CDR DN number is incorrect for the SL1 record format for variable DN length. This patch resolves the incorrect DN number issue seen in SL1 record format for variable-length DNs. Q01512744. 3. CDR Pull Client will only work to default destination folder. This patch resolves the issue of installing CDR Client in different paths and different drives on a Client system. Q01529733-02 4. CDR Stops working after a few language changes like German and Dutch. This path resolves the crashing of CDR service when languages like German and Dutch are selected in Element Manager for CDR Norstar report format. Q01508526-02 5. CDR Multi-Party Conference Record - Trunk Call missing CALL RELEASED entry This patch adds the CALL RELEASE line which 3rd party applications rely on to identify the end of each line in Ad-hoc conferences. Q01529318-02 6. Element Manager disconnects when clicking on CDR. This patch resolves the issue of EM closing when the CDR option is selected in Element Manager. Q01486203 7. CDR Transfer not properly closing sockets. This patch resolves the issue with sockets not properly closing after CDR record transfer. Q01408588 Limitations: Updating Prefix list will not take effect until the Report Filter type is changed. Workaround: When user updates the Prefix list, the Prefix Filter Type must be updated for the change in the Prefix list to take effect. This issue will be addressed with the future software update.