PRODUCT_LINE: BCM ============================================ Software Update Name: BCM370.213-SU3 Applicable H/W Platforms: BCM1000, BCM200, BCM400, 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: IPTelephony Voice Platform 37.03.03.41 Voice CTI 37.00.14.1 UTPS 37.171.80.12 SRG 37.110.2.51 Voicemail 37.01.09.22 CallCenter 37.01.09.16 RCC 2.4 - Build 344 IVR mps1.0.1 3.7 core wi07.14 WindowsNT4Server-KB921883-x86-ENU.exe WindowsNT4Server-KB920683-x86-ENU.exe FEPS 37.220.0.33 Unified Messaging 2.50.06.28 WindowsNT4Server-KB917159-x86-ENU.exe CteDp v. 0.17 DSP firmware version 37.70.90.9 Unified Manager 3.7.0.0.1.8 Unified Messaging 2.50.06.28 Italian and Spanish for Lotus Notes 6.x and Groupwise 6.x CTE 6.7 2.50.A PCM 1.2.129.0 SipUA 36.110.0.67 Hunt Group Metrics Reporter v. CTE 6.7 2.40.A i2001/2/4 Firmware version 0604D9H IPView 2.0.012 CDR 1.51.A Nothing visible in inventory for BCM_370_040_MSM Nothing visible in inventory for BCM_370_060_WANDVR Dependencies: Required patches - Please apply patch BCM370.194-OS2 prior to this service update patch to ensure that there is sufficient space available on the NNACTIVE (F:\) drive. Product Dependencies - Java 1.5.4 (included in RCC installation) MySQL 4.1.14 (included in RCC installation) Crystal Reports (included in RCC installation) IIS 5 (Not Included) BCM 3.7 - Voicemail 37.01.06.22 Size: ~306 MB System Impact: time to apply approximately 35 minutes Does update application force reboot: Yes, 2 reboots Other impacts: All services are unavailable during the patch process. Limitations: This patch has no effect on the operation of the BCM 3.7 main unit software. This patch updates the Unified Messaging client application file that is stored on the BCM 3.7 system hard drive and that file may be subsequently downloaded from the BCM 3.7 system to a PC. All email clients on client systems must be shut down while installing the new client and re-started once the installation completes. Danish, Norwegian, Brazilian Portuguese and Swedish languages are not supported in this patch. Applying this patch for Italian and Spanish permanently removes Brazilian Portuguese from the BCM. WARNING: You must ensure that the RCC client is not polling the BCM at the time you apply this patch. If you are applying an RCC patch as well, first uninstall the RCC Client from the Web Host PC, apply the patches to the BCM, then install the new RCC Client. If you are not applying an RCC patch, you must either stop the RCC Launcher Service on the Web Host PC or shut down the Web Host PC before applying the VM patch to the BCM. This patch will display an error message and terminate if the BCM does not have the MAINTOS drive. However, the likelihood of this scenario occurring is extremely rare. PLEASE NOTE: If you have a more recent core patch release installed than what is supplied with this service update you will receive a "Not Yet Started" status message when uploading the CORE with the patch wizard. There is no action required by the tec nician and the service update will continue on to the next action and complete successfully. Update Removable: No Description: ----------- This is the third Service Update patch created for BCM 3.7 (the first was called "Cumulative Patch 1"). The purpose of the Service Update is to bring a BCM 3.7 up to the latest software revision level as easily as possible by reducing the amount of tim it takes to install all current patches. The patches included in this Service Update are listed below. These are all globally applicable patches. If you are running a private or limited availability patch, please consult Nortel Technical Support befor applying this Service Update. The Service Update will not apply individual component patches if the component has already been patched, or has a later patch. All patches are applied if required. There is no ability to individually select the component to be patched. Included Patches: BCM 3.7 Cumulative Patch #1 constituent patches: BCM_370_033_VP_41_001 BCM00156 BCM 3.7 Maintenance Page Update BCM_370.039_SECURITY.00.896422 BCM00148/00159 BCM 3.7 Microsoft MS05-027 Security Update BCM_370.041_MSCSVC.20.372100 BCM00161 BCM 3.7 Voice MSC Service Update BCM_370_060_WANDVR_17_241 BCM00171 BCM 3.7 WAN Driver Update BCM_370.061_WIN.00.899588 BCM00147 BCM 3.7 MS05-039 and MS05-040 Security Updates BCM_370_062_NRU_16_1001 BCM00173 BCM 3.7 NRU Update BCM_370.097 (Not previously patched) BCM_370.148_OS.00.001 (Not previously patched) BCM 3.7 Service Update #2 constituent patches: BCM_370.114_QOS.70.3709 BCM370.114-QOS BCM 3.7 QoS v.3.7.0.9 BCM_370.116_IPSEC.71.3707 BCM370.116-VPN BCM 3.7 IPSec Patch BCM_370.127_BRU.10.020 BCM370.127-BRU BCM 3.7 BRU Patch BCM 3.7 Service Update #3 constituent patches: BCM_370_040_MSM_26_202 BCM00160 BCM 3.7 Resource Manager Update BCM_370.094_CDR.64.151 BCM370.094-CDR BCM 3.7 Call Detail Recording Upgrade BCM_370.130_IPVSB.62.012 BCM370.130 BCM370.130-IPview-Softboard BCM_370.132_SETFW.56.161 BCM370.132 BCM370.132-SETFW (D9H Upgrade) BCM_370.139_HGMR.148.240 BCM370.139 BCM370.139-Hunt-Group-Metrics-Reporter BCM_370.151_SIPUA.67.361100 BCM370.151 BCM370.151-SIPUA BCM_370.155_PCM.43.129 BCM370.155 BCM370.155-PCM BCM_370.157_CTE.40.251 BCM370.157 BCM370.157-CTE BCM_370.158_CPISB.22.2500628 BCM370.158 BCM370.158-CPISB BCM_370.159_WIN.00.911280 BCM370.159 BCM370.159-WIN BCM_370.161_UM3.39.002 BCM370.161 BCM370.161-UM3 BCM_370.166_DSPFW.09.5134 BCM370.166 BCM370.166-DSPFW BCM_370.169_DP.57.017 BCM370.169 BCM370.169-Doorphone BCM_370.171_WIN.00.917159 BCM370.171 BCM370.171-WIN BCM_370.174_CP.22.2500629 BCM370.174 BCM370.174-CP BCM_370.175_FEPS.33.372200 BCM370.175 BCM370.175-FEPS BCM_370.179_WIN.00.921883 BCM370.179 BCM370.179-WIN BCM_370.183_CORE.08.0714 BCM370.183 BCM370.183-CORE BCM_370.184_IVR.02.3509 BCM370.184 BCM370.184-IVR BCM_370.189_UTPS.12.17180 BCM370.189 BCM370.189-UTPS BCM_370.191_RCC.61.344 BCM370.191 BCM370.191-RCC BCM_370.192_VM.22.0109 BCM370.192 BCM370.192-Voicemail BCM_370.197_SRG.51-1103 BCM370.197 BCM370.197-SRG BCM_370.201_CTI.01.370141 BCM370.201 BCM370.201-CTI BCM_370.203_VP2.41.0303 BCM370.203 BCM370.203-VP2 BCM_370.080_MPS.34.003 BCM_370.080 BCM 3.7 Media Path Server update to disable Unidirectional Path feature Individual patch Release Notes: =============================== Patches included from Cumulative Patch #1: ------------------------------------------ BCM_370_033_VP_41_001 --------------------- Description: Fixes the issue with weekly scheduled restart. Please refer to Q01142938: BCM400v3.6 BCM_370.039_SECURITY.00.896422 ------------------------------ This BCM patch addresses the vulnerability described in Microsoft Security Bulletin MS05-027, Vulnerability in Server Message Block Could Allow Remote Code Execution (KB article 896422). A remote code execution vulnerability exists in Server Message Block (SMB) that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system. A workaround to not enable any drive shares. BCM_370.041_MSCSVC.20.372100 ---------------------------- The following CRs are resolved: Q01139597 - BCM 400 3.6 Voicemail not accessible Q01160314 - BCM System Crash when power is dropped from 110v to 90v BCM_370_060_WANDVR_17_241 ------------------------- Q00888200: IP routing slows down over time, reboot restores Q01090459: BCM 3.6:WAN Recovery BCM_370.061_WIN.00.899588 ------------------------- This BCM patch addresses the vulnerability described in Microsoft Security Bulletin MS05-039 "Vulnerability in Plug and Play Could Allow Remote Code Execution and Elevation of Privilege (KB Article 899588)" and MS05-040 "Vulnerability in Telephony Service Could Allow Remote Code Execution (KB Article 893756)". Either one of these vulnerabilities could allow an attacker, who successfully exploited one or both of these vulnerabilities, to take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. BCM_370_062_NRU_16_1001 ----------------------- This patch fixes a problem where Telephony OAM may become unavailable (without ca use) and does not recover. It affects the Telephony sections of Unified Manager, the Telephony option in the BRU Utility, and the daily scheduled NCM import. Q01135414 Patches included from Service Update #2: ---------------------------------------- BCM_370.114_QOS.70.3709 ----------------------- 1. BCM locks up when NAT and firewall is enabled and multiple Bittorrent sessions are active on client PC(s) on private side on BCM. Q01175114 & Q01279781 BCM_370.116_IPSEC.71.3707 ------------------------- 1. C221 contivity client disconnects with BCM 3.7. Contivity 221 147VPN Client148 connects to BCM 3.7 but is then disconnected after approx. 20 seconds. The problem is due to the fact that the Contivity 221 Client does not connect to the Quote Of The Day Server. This is different from how the Contivity VPN Client does it. This is treated as an error. BCM 3.x IPSecIKE code and the IPSec tunnel is deleted. This occurs after approx. 20 seconds. So the IPSec VPN client tunnel was staying up for approx. 20 seconds and then the BCM 3.x was deleting it. Q01203965 2. BCM does not send 3DES proposal. BCM3.x by default sends only DES proposal and does not send 3DES proposal. Branch Office Tunnel does not come up between BCM & BCM50a/BCM50e if BCM50a/BCM50a are configured to use 3DES encryption. CR - Q01240777 & Q01240777-01. 3DES proposal will be sent if in IPSec Global Settings any of the 3DES options are set AND both of the DES56 (MD5 and SHA) are un-selected. 3. Branch Office Tunnel does not come up between BCM50e and BCM 3.7 after its manually disconnected. It comes up only after BCM is rebooted or IPSecIKE service is restarted. Q01269701 BCM_370.127_BRU.10.020 ---------------------- 1. Unable to restore Telephony data backup when backup folder has been changed The BRU script has an issue where it fails to identify the proper Backup/Restore default path if it has been changed by the user through the UM. The BRU script now queries the registry to get the valid backup/restore default path and uses this during restore of fnvram.NEW Q01300537-01 ==================================================================================== Patches new to Service Update #3: --------------------------------- BCM_370_040_MSM_26_202 ---------------------- Q01109363 - BCM 400/3.6 Manager & voicemail to be inactive Q01100524 - BCM Monitor causes BCM voicemail to freeze Q01152435 - BSOD on netmeeting call to BCM 3.6 CP3 and 3.7 BCM_370.094_CDR.64.151 ---------------------- o Q01165458 The CDR record destination field (SL1 format) for incoming PRI NI calls is incorrectly displayed and o Q01234387 BCM 3.7/CDR showing info wrong when using authorization codes. BCM_370.130_IPVSB.62.012 ------------------------ 1. Several Instances of IPView Running Concurrently A single PC running several ipView SoftBoards which were each echoing to a number of non-operational ipView SoftBoards would eventually fail to make new socket connections. Although the order of closing the sockets should not be a consideration, Windows Sockets version 2.0 does not de-allocate a socket that has been duplicated if the Closesocket() function is called against the duplicated socket descriptor first, and then against the duplicate socket. Even after closing the socket at the program level, the socket provider may see a socket using that address. An overuse of socket resources may occur in the interim. A solution was implemented to avoid the issue by ensuring a new socket connection is not attempted to an ipView until the previous connection has been handled correctly or it has timed out, and sockets are now closed in the order they were opened. Note that newly booted ipViews which are being echoed to from another ipView will not receive data until the previous unsuccessful echo (that is, the last one the echoing ipView attempted before the echoed to ipView was booted up) has expired. This is a short duration of about 20 seconds or so. Q01328023 BCM_370.132_SETFW.56.161 ------------------------ 1. New IP Set Factory F/W IP client team is up-issuing the firmware that will be incorporated in each phase 2 phone coming out of the factory line. This patch provides this firmware so that it is available for all phase 2 phones. BCM_370.139_HGMR.148.240 ------------------------ 1.Q01314471- Hunt Group Metrics new file not being created at proper time New Hunt Group Metrics file not being created after a CDR Pull. The same file is appended to when the next interval occurs, as defined by the registry setting, instead of starting a new file. Depending on the settings in the registry a new file will either be created hourly or daily. If a CDR Transfer is successfully accomplished, the next gathering of HG stats should create a new file. Q01314471 BCM_370.151_SIPUA.67.361100 --------------------------- 1. SIP trunks locking up after Core Upgrade Issue Fixed: After upgrading Core Telephony to version 7.06 or later, any SIP VoIP trunk call that is released by the user on the BCM will cause a trunk to lockup. Every second call will fail. This patch resolves this issue. Q01344006 BCM_370.155_PCM.43.129 ---------------------- 1 Personal Call Manager inserts wrong country code for incoming international calls. When international caller dials in from Belgium to UK or from UK to Belgium, PCM inserts a +44 or +32 in front of the incoming number. So, when PCM compares the incoming number with its entry in the phone book, the number does not match and the name in the phonebook is not displayed. Q01341975 BCM_370.157_CTE.40.251 ---------------------- 1. LAN CTE position unable to answer When TSP receives a MADN Active message for a line, it increments the usage count for that Line. Under certain conditions, the TSP sees two MADN Active messages and the usage count is incremented to 2. This count will get decremented to 1 when the call goes to idle but never get decremented back down to 0. So when the next call comes in on that line, the count is incremented again but because the value 2 is greater than the number of appearances of that line on the set, the set is not allowed to answer the call. TSP was modified to handle such situation where two MADN active events are seen. Q01341307 2. Call transfer failure A timing issue in the BCM occurs when a Trunk hook flash is requested on a hidden call from the Secondary position while, at the same time, the Primary position releases the shared call. This issue has been corrected. Q01305364 BCM_370.158_CPISB.22.2500628 ---------------------------- 1. Cannot use Lotus Notes on PC running Italian OS Added support for Lotus Notes 6.x on Italian OS. Q01354305 BCM_370.159_WIN.00.911280 ------------------------- 1. Security vulnerability with RasMan The BCM / SRG GA products are impacted by MS vulnerability MS06-025. The Vulnerability is in Routing and Remote Access that Could Allow Remote Code Execution (911280). This patch delivers the necessary Microsoft operating system hotfix to address this vulnerability. Q01395193 BCM_370.161_UM3.39.002 ---------------------- 1. BCM - DTMF Tones not recognized by BCM Call Pilot This patch introduces a new drop down combo box on the page Services->IP Telephony->IP Trunks->H323 Trunks->Local Gateway IP Interface, with the label "Ignore in-band DTMF in RTP". The drop down combo box has two options, "Enabled" and "Disabled". Using this setting, Voice CTI decides to ignore or to consider the in-band DTMF digits received over a VoIP call. Q01314181-01 2. BCM400 - LAN2 DHCP problem This update resolves the problem of being unable to get an IP address from the DHCP server on LAN2 after installing Cumulative Patch 1 (BCM_370.110_CUMULATIVE.99.1) which was caused by the BCM 3.7 Unified Manager Patch BCM370.076_UM3.39.001 that disabled the ut1 (llnail) driver. The problem was due to the UT1 driver being disabled by a patch to resolve Q01220182 and DHCP server was bound to mspQoS virtual adapter over UT1 interface. The solution is to disable DHCP server bindings with mspQoS virtual adap ter over UT1. Q01368933 BCM_370.166_DSPFW.09.5134 ------------------------- 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 i n 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. T38 interop change Some fax machines emit longer CED tones that could be detected in both the VoIP channel and additionally in the T.38 channel (after switching to T.38). This causes an extra CED tone to be sent to the originating fax machine and a back-up of T.38 signaling - possibly causing contention. This change allows the CED detector to continue to replace the CED/ANSam tone with CED after a fixed 250msec, but will continue to detect CED in the VOIP channel for the entire duration of the CED tone. Reporting of the tone will be done when the tone ends. Q01330782-01 BCM_370.169_DP.57.017 --------------------- 1. Doorphone on a BCM 400, 3.7 does not function properly The doorphone was not working properly. It would either beep without unlocking the door or fail to beep completely. Reconfiguring the Doorphone from using a Phantom DN to a real DN also did not help. This issue has been corrected. Q01275958 BCM_370.171_WIN.00.917159 ------------------------- 1. BCM 200/400/1000 - Security vulnerability with MailSlot The BCM / SRG GA products are impacted by MS vulnerability MS06-035. The vulnerability is in Server Service that could allow remote code execution (917159). This patch delivers the necessary Microsoft operating system hotfix to address this vulnerability. See Nortel Security Bulletin "BCM and SRG Security Advisory Patch Update For MS06-035 Microsoft July Update". Q01417014 BCM_370.174_CP.22.2500629 ------------------------- 1. BCM_370.095_CP.22.2500628 patch does not have Mailbox & Operator Managers The Unified Messaging Client installer included in BCM_370.095_CP.22.2500628 is missing Mailbox or Operator Managers. These are usually included as a part of the Unified Messaging Client application. Q01399956 Q01411077 BCM_370.175_FEPS.33.372200 -------------------------- 1. Gatekeeper Deregistration Problem Upon losing connectivity to the primary gatekeeper, the BCM attempts to switch to the backup gatekeeper. In the case in which the BCM network configuration is not valid for the BCM to be able to register with the backup gatekeeper, the VoIP Gateway enters a state in which it continually attempts to discover the backup gatekeeper every 10 seconds, but with each attempt failing. At this point, two problems are exposed: 1) the VoIP gateway fails to switch back to the primary after 3 o f these type of failures, and 2) the VoIP Gateway fails to close the RAS transactions in each of these failure scenarios. As a result, after the Radvision configured max RAS out transactions (350), the VoIP Gateway runs out of RAS transaction resources, and must be restarted in order to recover. Q01404705 2. BCM VoIP Gateway memory leak When in direct call signaling mode, i.e. no gatekeeper, on every outbound VoIP trunk call, the VoIP Gateway service always allocates 8 bytes of memory to the GKACallback structure that it does not free. This wastes 8 bytes of system memory on each call of this type. The memory is only relinquished if the VoIP Gateway service is restarted, either manually or through a reboot. This patch resolves this issue by freeing the said 8 bytes on each call, preventing this waste of memory. Q01406115-01 3. Third Party H.323 Gateway Interop results in inability to send DTMF tones to IVR In this scenario a user on the BCM makes an outbound call to a third party H323 VoIP Gateway which is the interface to an IVR, and because this gateway sends back to the BCM a Progress H.225 message instead of an Alerting and does not connect the call, the BCM will not be able to send DTMF tones to the IVR. The Acme Packet Session Border Controller is an example of such a third party gateway with which this problem has been seen. Q01379114 BCM_370.179_WIN.00.921883 ------------------------- 1. BCM 200/400/1000 - Security vulnerability with RasMan The BCM / SRG GA products are impacted by MS vulnerabilities MS06-040 and MS06-041. MS06-040 relates to the vulnerability in Server service which could allow remote code execution (921883). MS06-041 relates to the vulnerability in DNS resolution that could allow remote code execution (920683). This patch delivers the necessary Microsoft operating system hotfixes to address these vulnerabilities. Q01434931 Q01434956 BCM_370.183_CORE.08.0714 ------------------------ 1. BCM - ETSI Euro PRI will not connect to New Zealand ISDN This adds a New Zealand market profile to the BCM 3.7 product. It also allows the users in that market to select the B-channel for outgoing calls if required. The ETSI Euro PRI protocol normally does not support B-channel selection by the PBX for outgoing calls, rather the PSTN decides which B-channel should be used. This change is specific to the New Zealand market. Q01308779-06 Q01422374 2. Not able to dial out on 2nd PRI if in both spans are in one line pool The customer is not able to dial out on 2nd ETSI PRI if both PRIs are in the same pool. The CBC throttling feature was unintentionally affecting the ETSI Euro trunks. Q01301542 3. Telephony Restore Fails Unless all MBMs are Removed Intermittently one is unable to complete a restore operation on a replaced MSC unless all media bay modules are removed. Q01143861 4. High attenuation in calls to the PSTN (BCM to PSTN) Adjustments in the loss plan levels for analog trunks in the CALA market. Reason for change: A-law attenuation factor not accounted for in TX/Rx Gain in market profile Q01326841 5. Core Hunt Group Metrics incorrect in Extend Callback Scenario When a call that was transferred to a hunt group recalls to the transferring set the Hunt Group Metrics are incorrectly incremented by 2 calls instead of one. Q01362041 6. GATM Tuning fails The GATM fails to complete Line tuning when initialized. This can result in improper loss levels, and possible echo on analog trunk calls. Q01444242 7. Using digit zero for network PSTN access does not work In the German market the digit 0 is used to access the public network. When 2 BCMs are networked together and a tandem call attempt is made to the public network, the tandem does not complete. The call rings to the prime set of the tandem node. Q01410932 BCM_370.184_IVR.02.3509 ----------------------- 1. Accumulated system and application statistics files older than seven days were not being automatically removed. The available file space on the BCM was being reduced. Q01273273 BCM_370.189-UTPS.12.17180 ------------------------- 1. User is unable to make adjustments to ringing volume via Feature *80. This patch ensures that the adjustments to ringing volume can be made. Q01379077 BCM_370.191_RCC.61.344 ---------------------- 1. RCC: System Configuration report in Canadian French overwrites value on screen When generating a System Configuration report in Canadian French, some values returned would be masked by the title which is too large for the column width. Q01459566 2. RCC: Print Schedule heading option change when using different language When viewing RCC in another language, menu options for daily print schedules are incorrect. Q01460361 3. RCC: The agent activity report shows incorrect data Negative values appear on the report due to a problem when handling Supervisor Monitoring time. Q01459098-01 4. RCC: SUOG change format of text to put more emphasis on the information Slight change to the SUOG "using the reports section" to emphasize important information. Q01455193 5. RCC: Error message when Submit selected in Company Details with no changes Entering information into the Company Details, submitting and then resubmitting a second time with no changes causes an error. Q01455041 6. RCC: Historical report issues Agent Average Report by Agent, when viewed on screen and printed, truncates Average Outgoing Call Time column. Q01442363-01 7. RCC: HP DeskJet 5400 cuts off edge of report when printed from View on Screen On the printer model above certain reports would truncate columns and report footers when viewed on screen and printed. Q01448639 8. RCC: "Get Latest CC Data" button fails with "Cannot establish a connection to CC" The error message would incorrectly lead the user into believing the connection between RCC and the Contact Center was not working. This is not the case and has been reworded to detail the correct status and what steps to take next. Q01449231 9. RCC: Agent Average Report By Agent and Agent Activity Report by Skillset do not generate and return "timeout error" For very large customer sites the Agent Average Report by Agent and Agent Activity Report by Skillset will not generate and will return an error containing the phrase \u201ctimeout\u201d. Q01444204 10. RCC: Insert generic information in RCC documentation on getting help from Nortel Information and help on raising technical support issues with Nortel has been added to each document within RCC, that includes the SUOG and Reports Explained. Q01441499 11. RCC: Printout of Agent Audit report missing data when printing on multiple pages Issue specific to HP DeskJet 5440 where the bottom few lines of the Agent Audit report would not be printed when viewed on screen and then printed. Q01435711 12. Call Center: Wallboard is not counting smoothly QT An update to the Troubleshooting Guide document to add a warning about possible problems with Microsoft Indexing service and Wallboard Updates if wallboard updates appear too slow. Q01437207 13. RCC: Print delay window should close when the reports have printed When printing a report from the Report Generation page and selecting a delay of more than 1 minute, the popup window would not close when the print time had passed. Q01398880 14. RCC: Suppress Incomplete XML warning When RCC detects Incomplete XML, warnings to the user are suppressed but still recorded in the database and log files. Q01438761-01 15. RCC: SUOG troubleshooting section needs enhancement Inclusion of a new document to the RCC library, Troubleshooting and Maintenance Guide. This guide should be consulted in the event of any issue occurring with RCC. Q01186881 16. RCC: Report status window sizing issue When generating a report, if the maximum number of concurrent report windows is exceeded the red warning text is cut off on the last line of the report status window. Window height has been adjusted to fit the message. Q01420391 17. RCC: error message appears along with activity codes report When trying to view the online help for any Activity Code Reports the message "no reports explained index is available" is displayed instead of the right help text. Q01407896 18. RCC: Correct Reports Explained Online Help for Summary Report Average GOS% Average GOS% field in the Reports Explained is incorrectly documented correct formula is: (Total Pre - Total AnCS - Total AbC) / Total Pre) * 100 Q01418408 19. RCC: CC Connection page Online Help compatibility across BCM platforms Online help now details what to enter for the various BCM platforms with which RCC 2.4 will operate. Q01409124 20. RCC: Should display CannotConnectToCC error message in Real Time Currently the error code CannotConnectToCC, CannotConnectToDB and CCRefusedConnection from the BCM are not reported to the real time screen if they occur. These have been added and a generic message has also been added should another error message be sent that RCC does not recognize. Q01396592 21. DOCS: Agent on Customer site can somehow avoid calls. Reports Explained Documentation now details how an agent may avoid being distributed calls by extending Break Time through prompted Activity Codes at the end of a call. Q01279027-01 BCM_370.192_VM.22.0109 ---------------------- 1. CallCenter: Port back RPT query time restriction from BCM4.0 to BCM3.7 Synopsis: Porting back a feature from BCM 4.0 which tightens the control on what CallCenter considers a valid XML Request. CallCenter will now reject queries where the data end time is before the data start time. For example, a request for data from 10:00 AM to 9:00 AM on the same day. Q01447132 2. VoiceMail: Rare delivery failure for AMIS Synopsis: When sending AMIS networking message to multiple sites, occasionally, sender's mailbox will receive Non-delivery notification (NDN) message, "The following message could not be delivered to phone number 'x' mailbox number 'y'. The destination telephone number does not appear to be a network site". This update corrects the problem by resending AMIS message as per the number of retries configured in AMIS retry page for cases where Trunk drops the call in middle of a AMIS negotiation. Q01448471 3. VoiceMail: BCM CallPilot fails to reply to a AMIS networking message Synopsis: Symptom is that BCM CallPilot fails to reply to a message received from an AMIS networked site located in the country other than the country where the local site is present. This update corrects the issue by not replacing the country code present in SAN with the country code configured in the AMIS networking properties so that number to be dialed on the AMIS network is proper. Q01440775 4. VoiceMail: Message delivery fails if the AMIS networking message is composed to multiple recipients Synopsis: Symptom is that BCM CallPilot delivers the AMIS networking message only to first recipient in the TO address list and fails to deliver the AMIS networking message to other recipients in the TO address list. Issue occurred due to Voice CTI grabbing the same Trunk LAD for consecutive make call requests. This update corrects the problem by adding a small delay between the consecutive make call requests so that VoiceCTI doesn't use same Trunk LAD. CQ01446965 5. Call Center: Small resource leak in a CC Routine Synopsis: A function was called to open the data file, but did not close the file before exiting. Q01390342-02 6. Call Center: Calls not presented to agents for 10mins Synopsis: The system state machine had a hole in which, very rarely, calls could get stuck and take ~10 minutes before successfully routing to an agent. Q01414570 7. VoiceMail: CallPilot Read Receipts missing Synopsis: CallPilot was not properly sending the read receipt for messages sent with Certified/Acknowledge delivery option. When two or more users read messages sent with Certified/Acknowledge delivery option at the same time, the message IDs generated for the read receipts were not unique. This resulted in sending the duplicate read receipt to same mailbox user instead of sending to corresponding mailbox users. This update corrects the problem by generating the unique message IDs for each read receipt send by the system. Q01414600 8. Call Center: Counter for time spent in a "Supervise" state resets on JOIN/MUTE Synopsis: When a user is using Supervisor Monitoring or Supervisor Help (Features 9 05 and 906) the Call Center tracks the total amount of time spent in each state. However, when the Supervisor presses the join/mute softkey to mute/unmute their voice path, this timer resets. This has been resolved so we track the entire F905/906 session. Q01019549 9. Call Center: XML schema port back from BCM 4.0 to BCM3.7 Synopsis: This is an enhancement which adds more robustness in the XML and increments the version so that the data stream is the same as a BCM 4.0 system. This requires RCC 2.4.330a or later version and makes previous versions of RCC incompatible. The benefits of this is that users on BCM 3.6/3.7 can utilize BCM 4.0's reporting for Contact Center package. Q01274838 10.Call Center: Reporting for Call Center fails to establish a connection Synopsis: The problem appears that RCC is unresponsive and does not connect to the BCM. After an abnormal patch application the MS SQL service (which manages the database) starts AFTER Voicemail. As a result Voicemail cannot reach the database to respond to the XML queries from RCC. This has been resolved. Voicemail will now try re-connecting to the MS SQL server every 5 minutes until a connection has been established. Q01334435 11.Call Center: Call Center gives up trying to connect to MS SQL Synopsis: Related to the above CR (Q01334435). After a certain point Call Center/Voicemail gives up trying to connect to the MS SQL service. This has been resolved so that we will always try every 5 minutes to connect until a connection has been established. Additional information about Database issues has also been added to the logs. Q01332863 12.Call Pilot Manager: Need notification in WUI if user disables CC via F982/WUI Synopsis: Users can use F982 or the Call Pilot Manager Web User interface to disable Auto-Attendant from answering lines. This affects Call Center as Call Center will also not answer lines. This Change is to have a noticeable banner appear when this setting has been toggled so that users can quickly find out if their Auto Attendant/Call Center has been disabled via the telset. Q01367288 BCM_370.197_SRG.51-1103 ------------------------------------- 1. SRG: IP sets caught in a loop while attempting firmware download. Q01437372 Q01345540 2. SRG: Application of patch BCM_370.131_UTPS-SRG caused set firmware downgrade. Q01428955 BCM_370.201_CTI.01.370141 ------------------------- 1. Possible System Lockup An issue was introduced in patch BCM370.163-CTI that can eventually cause a system lockup to occur. A possible symptom of this can be a failure to access the Unified Manager. This patch corrects this issue. Q01464062 BCM_370.203_VP2.41.0303 ----------------------- 1. WAN520 card is not shown in the PCI cards list The PCI cards list in the BCM initialization menu does not indicate the presence of the WAN520 card. This issue is corrected by adding the relevant registry key to the System Status Monitor. Q01482055 2. WAN520 card is not shown in inventory.xml The inventory service is unable to detect the WAN520 card. The inventory service is now modified to handle the new WAN520 card as well as the older WAN500 card. Q01482059 3. NCM is failing to import the WAN520 configurations NCM is unable to import WAN related configuration parameters from a BCM with a WAN520 card installed. This issue is addressed by modifying the NCM related scripts. Q01477735 BCM_370.080_MPS.34.003 ---------------------- o Q01232995: BCM 400 3.7, MVC paging problems o Q01103150: BCM 3.6 IP Sets No Speech Path after CP 2.0 Patch Applied