PRODUCT_LINE: BCM ============================================  Software Update Name: BCM360.317-FEPS 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 Recommendation: This patch should be applied to all new installs of BCM 3.6 and SRG 1.0 based on 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: FEPS 37.220.0.33 Dependencies: Required patches BCM_360.275_CORE.08.0625 or later The core does not need to be applied before this patch, but the core must be applied for this patch to work correctly Product Dependencies: None Size: 2 Mb System Impact: Time to apply - approximately 20 minutes Does patch application force reboot: Yes, 2 reboots Other impacts: None. Limitations: None Patch Removable: No Description: ----------- The following issues are addressed: 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. CR 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 *** NOTE: The content of superseded patches continues on "Special Information" field *** *** Patch Content continues *** This patch includes the content of the following superseded patches: BCM360.299-FEPS --------------- 1. Incorrect Release Reasons and Tones Calls to CS1000 sets that are busy can result in the caller receiving an undecipherable release reason displayed on their set, for example "Unknown 17", which should be "user busy". There will be no busy tone. The BCM Monitor UIP trace for MCDN over IP will show a NOTIFY message being received from the CS1000 side immediately before the DISCONNECT. CR Q01316141 2. Intermittent Fax Failure on calls with CS1000 and BCM 4.0 Fax calls can fail intermittently due to T38 channels not being opened. The T38 channels are not opened because the BCM does not always advertise the T38 capability in its capability set. One scenario in which this can commonly occur is if the first VoIP call after a BCM reboot is a fax attempt. The issue has been resolved by ensuring that the T38 capability is not erroneously omitted from the capability set. CR Q01379032 BCM_360.289_FEPS.33.372000 -------------------------- 1. Issue Fixed: Intermittent VoIP Trunk Lockup VoIP trunks can lockup intermittently when communicating with CS1000. On the call that results in a locked up trunk, a one way voice path will also be detected. No further calls can be made on the locked up trunk. CR Q01232655 2. Issue Fixed: Unscheduled VoIP Gateway Restart VoIP Gateway restarts when using a GateKeeper. This is an extremely rare event. CR Q01336145 3. Issue Fixed: Rare VoIP Trunk Lockup One way voice path will be detected on the call that results in a locked up trunk. No further calls can be made on the locked up trunk. CR Q01232655-02 4. Issue Fixed: Voice Path Problems on Call Transfer Involving BCM 2.5 Various call transfer scenarios where a BCM 2.5 and a BCM 3.7 or BCM 3.6 are involved, result in one or no way voice path. This includes blind and supervised call transfers where the BCM 2.5 system acts as the transferring party. CR Q01305973 BCM_360.282_FEPS.33.371900 -------------------------- 1. Issue Fixed: Intermittent VoIP calls will drop soon after initiation. Intermittent VoIP calls will drop from the user's perspective for no reason. These calls will drop soon after initiation. This is an extremely rare problem. If however a BCM suffers from this problem the symptoms can occur regularly. CR Q01286946 2. Issue Fixed: Intermittent Inbound Trunk Lockup On rare occasions when an inbound VoIP trunk call is answered, a trunk can lockup. This can occur on sites with a small number of VoIP trunks, i.e. on trunks that will be used for both inbound and outbound calls. When the trunk locks up the first inbound call will fail and so will the next outbound call. No further calls can be made on this trunk. CR Q01232655, Q01282054 3. Issue Fixed: Overloaded GateKeeper Current BCM timeout for GateKeeper requests is 2 seconds, the H225 standard (a part of the H323 standard family) recommends 3 seconds so the BCM timeout has been extended. This helps alleviate congestion at the GateKeeper when many BCMs send registration requests that may timeout. CR Q01291957 4. Issue Fixed: Intermittent VoIP Trunk Lockup VoIP trunks can lockup. MCDN must be enabled for problem to occur, problem has been found where outbound calls of the following type exist: BCM---VOIP--->Meridian/Succession---PRI--->PSTN. No further calls can be made on the locked up trunks. CR Q01282054, Q01281447, Q01120093, Q01290752 NOTE: For a complete list of issues addressed by this patch, please refer to release notes attached to the patch