PRODUCT_LINE: BCM ============================================ Software Update Name: BCM360.346-SU4 Applicable H/W Platforms: BCM1000, BCM200, BCM400, SRG200 1.0, SRG400 1.0 Applicable S/W Platforms: BCM 3.6, SRG 1.0 based on BCM 3.6 Category: GEN Installation Recommendations: This update should be applied to all new installs of BCM3.6 and SRG 1.0 based upon BCM 3.6. 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: ntp 25.001 CallPilot Unified Messaging 22.2500621 MPS 34.002 MSC Driver 21.112251 MSC Driver 21.370021 MSM 26.202 MPS 34.003 DSPFW 09.5124 Alarm Monitor 36.1.1.46 DSP firmware version 37.70.40.9 IPSecIKE 3.6.0.8 mspQoS 3.6.0.21 BRU 36.00.20.10 i2001/2/4 Firmware version 0604D9H IPView 2.0.012 SipUA 36.110.0.67 CTE 6.6 2.40.A SSM 37.2.4f.12 SSMTest Utility 37.00.10.01 WindowsNT4Server-KB911280-x86-ENU.exe CteDp v. 0.17 WindowsNT4Server-KB917159-x86-ENU.exe FEPS 37.220.0.33 WindowsNT4Server-KB921883-x86-ENU.exe WindowsNT4Server-KB920683-x86-ENU.exe core wi06.28 Voicemail 37.01.09.22 CallCenter 37.01.09.16 RCC 2.4 - Build 344 Voice CTI 37.00.14.1 Unified Manager 3.6.0.0.2.1 CDR 64.140 Dependencies: Required patches - None. 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) Size: ~222 MB System Impact: time to apply approximately 40 minutes Does update application force reboot: Yes, two. Other impacts: All services are unavailable during the patch process. Limitations: The Voice Alarm Monitor service is stopped during the application patch BCM360.264-ALRM. Any alarms generated during this time will go unreported This patch (BCM360.280-QOS) resolves BCM lockup due to Bittorrent traffic (Q01175114 & Q01279781) when NAT & Firewall is enabled. The lock up problem may reappear if Bittorrent sends packets similar to unistim message. However chance of problem reappearing is negligible. Patch BCM360.318-CP has no effect on the operation of the BCM 3.6 system. This patch updates the Unified Messaging client Installer that is stored on the BCM 3.6 system hard drive and that may be subsequently downloaded and installed onto a client PC. All email clients on client systems must be shut down while installing the new client and re-started once the installation completes. Update Removable: No. Description: ----------- 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. IMPORTANT Please ensure you create a backup of your Reporting for Call Center Database prior to upgrading to this build. For information on backing up the database please refer to the Reporting for Call Center SUOG - The specific required chapter is titled "Backing up the MYSQL Database". For existing installations on client PCs: In Add/Remove Programs uninstall Reporting for Call Center. DO NOT uninstall Java or MySQL. Run the Reporting for Call Center install. For new installations on client PCs: DO NOT uninstall Java or MySQL. Run the Reporting for Call Center install. The installation process has changed, as a result of upgrading MySQL 3 to MySQL 4.1. You will need to supply a unique port number (default: 3309) for MySQL 4.1. If MySQL 3 is already installed on the Web Host PC, the MySQL Port Setter dialog box is displayed the first time you install Reporting for Call Center using the MySQL 4.1 Server. The port number to be used by MySQL 4 can be entered, or selected from the drop down list box, or left at the default port number of 3309. On first installation of Reporting for Call Center on a Web Host PC with MySQL 4 already installed, the MySQL Port Setter dialog box appears. Select the port number to be used by the MySQL 4.1 Server from the drop down list box, or enter a new port number, otherwise the port number is set to the defaulted value of 3309. It is recommended you select port 3309 (MySQL 3 by default would have been installed on port 3306). Port 3309 for MySQL 4.1 will be unique, as required. FOR MORE INFORMATION ON THIS CHANGE PLEASE CONSULT THE NEW FEATURES SECTION OF PATCH BCM_360.294_RCC.61.209b This is the fourth Service Update patch for BCM 3.6 (the first three were called "Cumulative Patch 1", "Cumulative Patch 2", and "Cumulative Patch 3"). The purpose of the Service Update is to bring a BCM 3.6 system up to the latest software revision level as easily as possible by reducing the amount of time 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 before 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 components to be patched. Included Patches: BCM 3.6 Cumulative Patch #2 constituent patches PATCH ID Title Patch File Name ------------ ------- ----------------------- BCM 3.6 Apache Configuration Update BCM_360.045 BCM 3.6 Cumulative Patch #3 constituent patches: PATCH ID Title Patch File Name ------------ ------- ----------------------- BCM00116 BCM 3.6 802.11 set support BCM_360.090_UM-UTPS-MSM.39-12-26.00.16050.205 BCM00082 BCM 3.6 Security Update for MS win. BCM_360_180_WIN_00_893066 BCM00084 BCM 3.6 WAN Driver Update BCM_360_198_WANDVR_17_250 BCM00089 BCM 3.6 Security Update KB896422 BCM_360_207_SECURITY_00_896422 BCM00096 BCM 3.6 Microsoft MS05-039 and MS05-040 BCM_360.228_WIN.00.899588 BCM00097 BCM 3.6 Default FTP-Root Folder Reset BCM_360.216_OS.50.002 BCM00101 BCM 3.6 Maintenance Page Update BCM_360.199_VP.41.001 BCM00109 BCM 3.6 UTPS version 37.170.60.12 BCM_360.140_UTPS.12.17060 BCM00113 BCM 3.6 CDR Push/Pull Upgrade Fix BCM_360.096_CDR2.64.0 BCM00117 BCM 3.6 Security Update MS04-011 for MS BCM_360.084_SECURITY.00.835732 BCM00118 BCM 3.6 SRG 36.10.11.51 BCM_360_075_SRG_51_1011 BCM 3.6 SDL Driver Debug Patch BCM_360.079 BCM00124 BCM 3.6 IVR Patch BCM_360_131_IVR_02_20165 BCM00134 BCM 3.6 Voice MSC Service and Driver Update BCM_360_212_MSCDVR_21_372100 BCM00144 BCM 3.6 NRU Update BCM_360_229_NRU_16_1001 BCM 3.6 Service Update #4 constituent patches: PATCH ID Title Patch File Name ------------- ------- ----------------------- BCM00102 BCM 3.6 NTP Client Update BCM_360.197_NTP.25.001 BCM00133 BCM 3.6 Resource Manager Update BCM_360_211_MSM_26_202 BCM00137 BCM 3.6 Media Path Server update to BCM_360_218_MPS_34_003 disable Unidirectional Path feature BCM360.264-ALRM BCM 3.6 Alarm Monitor Update BCM_360.264_ALRMMON.46.11 BCM360.274-FW BCM 3.6 DSP Firmware Patch BCM_360.274_DSPFW.09.5129 BCM360.279-VPN BCM 3.6 IPSecIKE Update BCM_360.279_IPSEC.71.3608 BCM360.280-QOS BCM 3.6 QoS v.3.6.0.21 BCM_360.280_QOS.70.36021 BCM360.284-BRU BCM 3.6 BRU Patch BCM_360.284_BRU.10.003 BCM360.286 BCM360.286-SETFW (D9H Upgrade) BCM_360.286_SETFW.56.161 BCM360.288 BCM360.288-IPview-Softboard BCM_360.288_IPVSB.62.012 BCM360.300 BCM360.300-SIPUA BCM_360.300_SIPUA.67.361100 BCM360.301 BCM360.301-CTE BCM_360.301_CTE.40.240 BCM360.302 BCM360.302-SSM BCM_360.302_SSM.11.370207 BCM360.307 BCM360.307-WIN BCM_360.307_WIN.00.911280 BCM360.314 BCM360.314-Doorphone BCM_360.314_DP.57.017 BCM360.315 BCM360.315-WIN BCM_360.315_WIN.00.917159 BCM360.317 BCM360.317-FEPS BCM_360.317_FEPS.33.372200 BCM360.318 BCM360.318-CP BCM_360.318_CP.22.2500629 BCM360.319 BCM360.319-WIN BCM_360.319_WIN.00.921883 BCM360.324 BCM360.324-CORE BCM_360.324_CORE.08.0628 BCM360.328 BCM360.328-Voicemail BCM_360.328_VM.22.0109 BCM360.329 BCM360.329-RCC BCM_360.329_RCC.61.344 BCM360.332 BCM360.332-CTI BCM_360.332_CTI.01.3700141 BCM360.345-UM BCM_360.345_UM.39.1012 BCM360.337 BCM360.337-VP3 BCM_360.337_VP3.41.001 BCM_360.251 BCM 3.6 CDR PRI NI Call Destination Patch BCM_360.251_CDR.64.140 BEFORE BEGINNING Please close any open Unified Manager or Putty sessions. If you have a personal firewall, such as CyberArmor, ensure you either turn it off, or enter the IP address and netmask of the Business Communications Manager in the file for allowed IP addresses. In CyberArmor, this is the Friends file. Individual Patch Release Notes: =============================== Patches included from Cumulative Patch #2: ----------------------------------------------------------- BCM_360.045 -------------------- BCM 3.6 Apache Configuration Update Patches included from Cumulative Patch #3: ----------------------------------------------------------- BCM_360.090_UM-UTPS-MSM.39-12-26.00.16050.205 ----------------------------------------------------------------------------- EMS does not handle IP set details correctly for spectralink sets. This patch adds support for 802.11 In order to support I2210/I2211 sets in DHCP mode two parameters are added under UM>>Services>>DHCP>>DHCP Global Options. UTPS and UM have been modified to recognize the I2210/I2211 sets Q00902671 BCM_360_180_WIN_00_893066 --------------------------------------------- BCM 3.6 Security Update for Microsoft Windows (MS05-19) This BCM patch addresses the vulnerability described in Microsoft Security Bulletin MS05-019, Vulnerabilities in TCP/IP Could Allow Remote Code Execution and Denial of Service (Article 893066). An attacker who successfully exploited the most severe of these vulnerabilities could take control of an affected system or cause the affected system to stop responding. There is no workaround that addresses all the vulnerabilities. BCM_360_198_WANDVR_17_250 ------------------------------------------------ The purpose of this patch is to update the current WAN Driver present on BCM 3.6 systems. 1. BCM 3.6:WAN Recovery Q01090459: 2. IP routing slows down over time, reboot restores Q00888200 BCM_360_207_SECURITY_00_896422 ----------------------------------------------------- Microsoft Security Update KB896422 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_360.228_WIN.00.899588 ------------------------------------------ Microsoft MS05-039 and MS05-040 Windows NT Security Update 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. BCM_360.216_OS.50.002 ------------------------------------ Default FTP-Root Folder Reset Default FTP Root folder stays at E:\ after upgrade/patch which affects NCM,CDR.(Default FTP root folder should be E:\ftproot) Q01095645 BCM_360.199_VP.41.001 ---------------------------------- Maintenance Page Update Fixes the issue with weekly scheduled restart BCM_360.140_UTPS.12.17060 ------------------------------------------ 1. Patch to update UTPS to version 37.170.60.12 Lowered transmit by 3db for phase 2 sets to reduce echo Q01025626 2. Increased f/w download time-out to 2.5 minutes to allow for terminals that are slow to reconnect. BCM_360.096_CDR2.64.0 -------------------------------------------------------------- Fixes the failed CDR Push/Pull functionality after the BCM 3.6 Upgrade process Q00948196 BCM_360.084_SECURITY.00.835732 --------------------------------------------------- Security Update MS04-011 for Microsoft Windows (835732) This is a cumulative patch addressing several newly-discovered Microsoft Windows vulnerabilities. An attacker who successfully exploited the most severe of these vulnerabilities could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts that have full privileges. This patch also contains an update to BCM software in order to establish compatibility between the fixes in MS04-011 and existing drivers on BCM 200/400 platforms. PAA-2004-0187-Global BCM/SRG Security Advisory Patch Update for MS04-011 BCM_360_075_SRG_51_1011 ------------------------------------------- This patch is required to enable an SRG 1.0 system to interoperate with the CS1000 Rls 4.0 Geographic Redundancy feature. SRG requires TPS Poll timeout to properly work with GR. Q00995699 BCM_360.079 -------------------- BCM 3.6 SDL Driver Debug Patch BCM_360_131_IVR_02_20165 ------------------------------------------- This patch includes the following IVR updates: mps1.0.1.51, mps1.0.1.52, globl2.0.1.43, hostp1.0.1.6 and hostp1.0.1.7 1. ANI/DNIS not propagated to the application. Applications are unable to obtain ANI/DNIS. Multiple upgrade issues after upgrading BCM from 3.5 to 3.6 Q00950753 2. IVR application crashes due to memory leak in psched. perisvc needs to support multiple service dependencies. Q00734287, Q00787523 3. BCM upgrades loose some configuration/data files. During upgrades config/data files are lost and causes system to function improperly. Q01005093 4. Host Protocols (vpstn3270) fails to get license on startup for BCM IVR. On BCM ivr, Even though valid licenses are available, host protocols fails to get license and goes to demo mode. Q00787523 5. Host Fail Problem on VPSTN3270 on MPS100 Bad parameter when attempting to disconnect from the host Q00866146 BCM_360_212_MSCDVR_21_372100 ---------------------------------------------------- Voice MSC Service and Driver Update 1. BCM 400 3.6 Voicemail not accessible Q01139597 2. BCM System Crash when power is dropped from 110v to 90v Q01160314 BCM_360_229_NRU_16_1001 ------------------------------------------- This patch fixes a problem where Telephony OAM may become unavailable (without cause) 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 new to Service Update #4: --------------------------------------------- BCM_360.197_NTP.25.001 ---------------------- CRs Resolved: Q01119132: BCM 3.5 200 - Date changed to 2020 after power cycle. Q01124822: BCM 1000 3.6 - Date changed to 2020. Q01127173: BCM 200 3.5 - Date changed to 2020. Q01130399: BCM 1000 3.5 - Date changed to 2020. Q01130416: BCM 200 3.6 - Date changed to 2020. Q01130457: BCM 200 3.6 - Date changed to 2020. Q01133045: BCM 200 3.6 - Date changed to 2020. Q01133120: BCM 200 3.6 - Date changed to 2020. Q01133286: BCM 200 3.5 - Date changed to 2020. BCM_360.211_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_360.218_MPS.34.003 ---------------------- IP Sets No Speech Path after CP 2.0 Patch Applied The enabling of the Unidirectional Paths feature in the Media Path Server has resulted in no speech path issues with IP sets. It appears that some customers are deploying IP sets behind third-party NAT devices such as Linksys WRT54G, even though this is not an officially supported configuration. The unidirectional streams feature breaks compatibility with a specific type of NAT devices, commonly called "port restricting" NATs. Such devices filter packets flowing from public into private domains and only allow packets form Y:y IP-address: port combination into the private domain destined to X:x internal address if it has seen recently (within 60 sec) at least one packet flowing from X:x to Y:y. Such a packet is said to create a pinhole in the NAT. With bi-directional streams, whenever an incoming IP set stream is setup by UTPS, the corresponding outgoing RTP stream is always set up by the UTPS on request from MPS. Both streams have matching IP addressing info. So, the first packet on an outgoing stream generates a pinhole in the NAT. With the introduction of unidirectional streams this is no longer the case, so whenever a unidirectional stream is setup the NAT filters the packets out in multiple scenarios. One such case is a case of a set going off hook. A unidirectional stream is opened to produce dial tone from BCM. The NAT does not let the dial tone through. In the case of an outgoing call, the ring back tones are also delivered via unidirectional streams. There are perhaps other examples of such issues with background music and music on hold that have not been seen in the field, but should exhibit similar behavior. Q01103150 BCM_360.264_ALRMMON.46.11 ------------------------- Addition of alarms 336 and 372 for DTI MBM BCM_360.274_DSPFW.09.5129 ------------------------- 1. Tolerance to simultaneous reception of T.38 and RTP streams In some cases the CS1000 continues to send RTP Voice frames following the setup of a T.38 session. If the RTP packets are received by the T.38 gateway on BCM, then the T.38 session will fail. In this patch additional checking is added to the T.38 endpoint to filter these RTP packets out. 2. T.38 Tandemmed Sessions On T.38 sessions which are tandemmed through Passport 6480 fax relay, NSF frames sent through the PP6480 are changed to V.21 preamble by the PP6480. This results in a preamble which exceeds the BCM's preamble timer. The most common symptom of the preamble timer expiry is the failure to establish any fax session through T.38. In this patch the preamble timer is extended to permit the extended preamble. 3. Super G3 Compatibility Super G3 (or V.34) fax is not supported over T.38, and an attempt to establish a V.34 fax session over T.38 will fail. In most cases, Super G3 will back off to use G3 fax if negotiation with another Super G3 fax machine fails. It is this back-off mechanism which is used by T.38 gateways to support Su per G3 fax machines. In the case addressed by this patch the Super G3 fax machine uses the type of answer tone presented by the answering fax machine to determine if it will use V.34 fax or one of the Group 3 fax modulations. To prevent originating Super G3 fax machines from attempting to use V.34 fax, the answer tone (either CED or ANSam) is blocked from being passed through the speech path. In the place of the answer tone generated by the answering fax machine, the VoIP task will pass a constant 2100Hz tone (CED). This change has the effect that the originating fax machine sees only the characteristics of a Group 3 fax machine, even if it is connected to a Super Group 3 fax machine. BCM_360.279_IPSEC.71.3608 ------------------------- 1. C221 contivity client disconnects with BCM3.6. Contivity 221 'VPN Client' connects to BCM 3.6 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 & M50a /M50e if M50a/M50a are configured to use 3DES encryption. Q01240777 & Q01240777-01 3. Branch Office Tunnel does not come up between M50e and BCM3.7 after it's manually disconnected. Branch Office Tunnel comes up only after BCM is rebooted or IPSecIKE service is restarted. Q01269701 BCM_360.280_QOS.70.36021 ------------------------ 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 2. OSIP & LZS code removal due to licensing issue. Q01242783 BCM_360.284_BRU.10.003 ---------------------- 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 BCM_360.286_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_360.288_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 2. IPView Could Stop Updating Its Display Overnight. Q01077534 BCM_360.300_SIPUA.67.361100 ------------------------------ 1. SIP trunks locking up after Core Upgrade After upgrading Core Telephony to version 6.18 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_360.301_CTE.40.240 ---------------------- 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_360.302_SSM.11.370207 ------------------------- 1. SSM intermittently logs false LAN 3 related warnings in Application Event log. Lan 3 related warnings will be of the following form, "(Event ID: 2005): Bytes Sent/sec LAN3 Recovered (Event ID: 2005): Bytes Received/sec LAN3 Recovered (Event ID: 1013): 8,Bytes Sent/sec greater than 50% of LAN3 speed (Event ID: 1013): 8,Bytes Received/sec greater than 50% of LAN3 speed" This can be verified by either examining SNMP trap monitor or Event Viewer. Q01305301 2. BIOS version information stored in System inventory and registry of BCM 200/400 does not necessarily reflect the real BIOS version. System inventory file is stored under "F:\Program Files\Nortel Networks\VoicePlatform\wwwroot\inventory.xml". BIOS version is stored in the registry under "Software\Nortel Networks\Platform Services\BIOS Version". Actual BIOS version can be verified by rebooting to CMOS and looking in "Advanced version information" under "Advanced" Tab. Q01340408 3. SSM intermittently logs Event id 3005 alarms in the Application Event log. Windows was not able to create a thread required for the SSM to perform sanity checking while initializing the SSM. The SSM.exe fix for 3005 application event failures is to terminate the SSM service immediately after event 3005 and let the ServiceMon restart SSM. Q01326419 BCM_360.307_WIN.00.911280 ------------------------- 1. BCM 200/400/1000 - 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-01 BCM_360.314_DP.57.017 --------------------- 1. Doorphone on a BCM 400, 3.6 does not function properly The doorphone was not working properly. It would either beep without unlocking the door or fail to beep completely. The previous use of that Doorphone resulted in the call being forwarded to a VoiceMail box. There was an interaction issue between the Doorphone and VoiceMail such that the call would never end (i.e. be torn down). Subsequent attempts to use the Doorphone after this would result in the issue as described above. This patch resolves the interaction such that the call between Voicemail and Doorphone would be terminated after a pre-determined timeout (i.e. 30 seconds). Q01275958 BCM_360.315_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-01 BCM_360.317_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 of 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_360.318_CP.22.2500629 ------------------------- 1. BCM_360.256_CP.22.2500628 patch does not have Mailbox & Operator Managers The Unified Messaging Client installer included in BCM_360.256_CP.22.2500628 is missing Mailbox and Operator Managers. These are usually included as a part of the Unified Messaging Client application. Q01425070 BCM_360.319_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-01, Q01434956-01 BCM_360.324_CORE.08.0628 ------------------------ 1. Problem with incoming calls on PRI trunk Incoming calls over PRI trunk to a BCM at site A that tandem out via T1 E&M to a BCM at site B drop if it's not answered within 2 rings and the phone display shows: Invalid num 28 Q01392178 2. GATM Tuning fails after Core Patch application After application of patch BCM_360.313_CORE.08.0627, the tuning on a GATM failed to take place. Q01444242-01 3. Telephony Restore Fails Unless all MBMs are Removed Unable to complete a telephony only restore. Q01143861-01 BCM_360.328_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 w ill 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. Q01446965 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 905 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_360.329_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 “timeout”. 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_360.332_CTI.01.3700141 -------------------------- 1. Possible System Lockup An issue was introduced in patch BCM360.325-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_360.345_UM.39.1012 ---------------------- 1. BCM400 - LAN2 DHCP problem This update resolves the problem of being unable to get an IP address from the DHCP server on LAN2. The problem was due 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 adapter over UT1. Q01368933-01 2. BCM 3.6 - DTMF Tones not recognized by BCM Call Pilot when simultaneously received both in-band and out-of-band 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" (default). Using this setting, Voice CTI decides to ignore or to consider the in-band DTMF digits received over a VoIP call. Q01314181-04 BCM_360.337_VP3.41.001 ------------------------------------ 1. Daylight Saving Time changes for North America effective March 2007. Legislated changes to the start and stop dates for Daylight Saving Time come into effect in a number of jurisdictions in North America starting in 2007. This patch updates DST data on the BCM so that future transitions continue to be performed automatically. DST now starts at 2:00 am on the second Sunday in March, and ends at 2:00 am on the first Sunday in November. Q01248734-07 BCM_360.251_CDR.64.140 ---------------------- This patch addresses an issue for incoming PRI NI calls where the destination field of the CDR record (Norstar format) was incorrectly displayed. CDR Record Lost under Call reject scenario Call Record split between 2 files if CDR Clip occurs. Corruption if more than 1000 files to transfer in Push/Pull.