PRODUCT_LINE: BCM ============================================ TITLE ===== BCM360.350-CORE ======================== Release: 3.6 Issue: N/A Category: GEN Superceded By: NONE Release Date: 20071211 Patch Conflict(s): N/A Special Instructions: NO Patch Version: N/A ======================== Software Update Name: BCM360.350-CORE Applicable H/W Platform: 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: Non-critical. This patch should be applied to all new installs of BCM 3.6 and SRG 1.0 based on BCM 3.6. Existing installations should have this patch 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: 3.6 core wi06.31 Dependencies: Required patches: When using PRI, DASS2, DPNSS or T1 trunks, the latest alarm monitor patch BCM_360.264_ALRMMON or later OR BCM360.346-SU4 or later should be installed. When using Voice Over IP trunks, the latest FEPS patch BCM360.317-FEPS or later OR BCM360.346-SU4 or later must be installed. Product Dependencies - None Size: ~16 MB System Impact: time to apply approximately 25 minutes. Does patch application force reboot: Yes, 2 reboots Other impacts: None Limitations: None Patch Removable: No Description: ============ The following issues are addressed: 1. No CLID and Unexpected Callback on GATM8 No calling line ID information is displayed for incoming analog calls on the GATM8 media bay module. After the answered call is released, the trunk starts alerting the set again even though no new incoming call has been made. Q01589063-02 2. GATM2 rev F Lines show as "Not in Service" in AUS Dip Switch mode When the new GATM2 Hardware with Rev-F support is installed in DIP switch mode in the Australian market, the GATM2 MBM will not come up and Lines will show as "Not In Service". Q01624801-05 This patch includes the content of the following superseded patches: 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 4. Analogue Exchange Lines (GATM) Locking-up In the UK market, loop guarded analogue lines may lock up intermittently, preventing customers from making or receiving calls. Q01403818-05 5. ISDN clocking, event, and alarms incorrectly generated When layer 1 alarms are raised for Primary rate interface connection the message parameters do not indicate the bus number of the offending digital trunk module. Q01465611-01 6. Line Tuning For BCM 3.6 This update introduces the line tuning feature for the BCM 3.6 product. Q01475421-04 7. Cannot make conference calls Attempts to set up a 3-party conference may occasionally result in 'conference busy' being displayed on the customer's set. Q01411102 8. Build failure in bcm_etq_36 (wi06.29). A typographical error in the sbcs_rom_mri_mak.mak make file was causing a compilation failure. This error has been corrected. Q01716348 BCM_360.313_CORE.08.0627 ---------------------------- 1. Calls over 2 T1 E&M Trunks have 1-way speech Incoming calls on T1 E&M which tandem over a T1 E&M trunk to a destination switch receive 1 way speechpath when the call is answered Q01317384-01 2. Logevent 247 message has no parameters This solution introduces additional diagnostic code allowing the design team to better diagnose possible hardware errors reported from the field. Q01328192-01 3. DMS100 protocol, incorrect release reasons If the BCM user terminates a DMS 100 PRI call first, the calling party hears a Telco recording "The number you have reached is not in service, please hand up and try again". Disconnect release cause is "Unallocated number". The BCM was sending the incorrect release reason resulting in a recorder announcement being played. Q01326694 4. BCM with supervised ROI lines drop out on answer in Australia profile New functionality is added to support reversal on seize for analog trunks in the Australian market. Q01176599 5. MICS 7.0: Call Cutoffs: 310 errors This change was made to minimize occurrence of an error which was being seen at a central office. When an outgoing call was made and the CO does not respond, we now send a release to the PSTN. The NI-2 specification does not require the PBX to send a release to the network. This change was implemented because in this scenario, a particular CO was locking up the trunks and not releasing PRI call refs. Q01244275 6. intermittent call drop The MCDN protocol is not able to handle PRI layer 3 messages where the location information element has a value other than 0. This results in a dropped call on tandems with the NI-2 PRI links where these other location IE values are supported. Q01383499 7. CoreDSP: Possible FUMP message corruption. The Core DSP firmware may send messages which have an incorrect message length, or the message length is set to a value greater than the allowed maximum. This can result in core Telephony resets, loss of communication with Windows NT and possibly Windows NT lock ups. Q01375239. BCM_360.275_CORE.08.0625 ------------------------ 1. Porting BCM 4.0 Fix (mathi.86) for no voice path and crosstalk. Incoming call to IP set via PRI trunk can occasionally result in no speech path Q1246753-01 2. QSIG -- Overlap receiving prompt display The prompt for overlap receiving is not present when the QSIG PRI protocol is selected. It should be visible. Q01287657 3. MICS6.1:Ext. Call Fwd on PRI to DID This solution corrects a PRI NI-2 specification compliance issue which may result in the calling party not hearing ringback on tandemed calls. Q01094224-03. 4. BCM 400 Loss of Speech path. When privacy control is turned off and set B tries to pick up a held call from set A, speechpath on set A's active call can be lost. Q01284456-01 5. VoIP lines go to busy state This resolves an issue where outgoing calls which were released before the far end answers causes a VoIP trunk to lock up and become unusable . The root cause lies with the VoIP trunk release protocol. The following patch is also required as part of this solution: FEPS patch BCM_360.236_FEPS.33.371600 or higher Q01120093 MSC Core WI 06.24 Q01215733-01: Problem with T7316e Revision 4 sets MSC Core WI 06.23 Q01266644: CoreTel allows hidden programming of QSIG overlap dialing Q01273213: No CONNECT PI Out (When a PRI call is made from a BCM 3.7, build 2.4f system into the M50 Call Centre, the call is dropped, just as the call is answered by the Call Centre.) MSC Core WI 06.22 Q01189546 BCM 400 3.6..cannot tandem call from T1 over VoIP Q01222065 Maintenance terminal does not report clearing of PRI or T1 layer 1 alarm condition MSC Core wi06.21 Q01247102 GASM8+ MBM will not boot. Q01101726 Cannot call out on idle T1 EAM, auto answer channel. Q01222053 BRI terminal gets incorrect call treatment when T1 lines are unavailable. Q01178926 Tandem call MCDN to PSTN and disconnects if the call goes to VM. Update to MCDN protocol to accept a PROGRESS message in a Call Delivered state. Q01222057 Incorrect T1 trunk status on BCM maintenance set (TDR36004) MSC Core wi06.20 Q01227690: MSC Core wi06.19: BCM Update Wizard: Continuous BCM re-boot MSC Core wi06.19 Q01189301 LAN CTE application unavailable Q01167598 BCM1000 MSC resets when a page is made MSC Core wi06.18 Q01100714 Q00969258 Q00572724 Q0110577 Q01187986 Q01128198 Loss_plan_changes_for_IP_telephony_issues Q01200784 Dsaint.1609 is not ported to BCM3.7,BCM 3.5 and BCM3.6 Q01121345 Load test - low pass rate on case 3 benchmark - agents busy and core errors Q01184612 BCM 50 Huntgroup overflow call is returning to AA after 1 ring Q01181453 SRG in local no ring back and speech path Q01185678 handsfree issue when taking a held call during all call page MSC Core wi06.17 Q00971020 No sequence checking for unrecognized IEs Q01087165 Update UI-Frame handling Q01121305 Allow receipt of STATUS msg after 911 call to 5ESS switch Q01179729 Loss of Forceauto/spd dial over ic/conf functionality Q01101726 Fix for Q01101726 (Cannot call out on idle channel) Q01165773 Add MCDN Progress Indicator to the CONNECT message Q01026566 Update PRI Makefile to allow creation of D64 files Q00971043 Missing Channel ID in RESTART message exception handler Q00884059 Support for logging Logevent 310 when sending or receiving STATUS Q01033464 Ignore unrecognized IEs in sequence checking Q01121305 Allow receipt of STATUS msg after 911 call to 5ESS switch MSC Core wi06.16 Q01155829 Link Transfer drops when Supervised Q01106980 BCM rebooting MSC Core WI 2.04 to wi06.15 Q01028145 Unable to send digits from slave when master puts Conference on Q01150579 Voice Path Lost When Held Conference Created Q01142073 BCM3.6 400 VoIP trunks dropping Q00992293 BCM fails to provide appropriate call treatment during busy/vaca Q01113767 BCM 1000, 3.6: Call Logs not showing Ca Increase DS30_TX_UQUEUE QUEUE_SIZE to 60 Includes the new busy tone library DTMF and FSK CLID fix for Taiwan Q01010005 Taiwan Busy tone detection. F4839 Poland MP port to BCM 3.6 Q01103606 BCM 400 3.5 Randomly Rebooting Q01113443 BCM 3.6 Huntgroup overflow rings solid switch to DTD servers, old syntax. Q01121305 Add support for AT&T Call Queued cause value on BRI trunks Q10394937 To resolve the expiration of T310 issue Q01121305 Add support for AT&T Call Queued cause value on PRI trunks Q01111855 Creating tones file for Spain Q01126447 UK GATM driver : Need to change RZ bit to support Algo dongle Q01122824 Telset Doesn't Display the Prefix 0 of the CLID. Q01107778: Needs upgrade from BCM3.0 to BCM3.6 for T7316E sets Q00992293: BCM fails to provide appropriate call treatment during busy/vacan Q01087386: BCM36 speakerphone and handset active Q00970904: DPNSS call cut-off's No Number ConferIII CR Fix and 1KHz tone CR fix Q01024914: IP Page Delay Feature Enhancement Q01024914 Hunt group DN's not ringing Q01018341: BCM Crosstalk on IP Phones Q00869882: Transfer to External Autodialer Drops Call Q01045609: Transfer to External Autodialer Drops Call Q00992293: BCM fails to provide appropriate call treatment during busy/vaca Q01036100: Originate Privacy doesn't properly send Release FUMP under Rejec Q01048696: Move Line Fails When Swapping Line or HG keys on CAP or KIM Q01036111: Fump Translator Fix Q00931160: One way speech path between 2 ISDN terminals connected via a T1 block nvram id's for IP page delay feature 0000000000 Q01035344: Hidden Calls should not be allowed to be put on auto-hold. Q00931157: Modify T1 EAM state machine for JTIC T1 EAM link disconnect test Q01035765: core resets during silent monitor session Q01005820: MWI (lamp)status lost once BCM is Powered On/Off Q01028145: Unable to send digits from slave when master puts Conference on Q00923512: PRI202 message appears before notify message is sent by BCM Q01035344: Hidden Calls should not be allowed to be put on auto-hold Q00974036 - Poland Market option cannot be selected from UM Q00832363 - Silent Monitor : Call Does not release from Supervisor set after Q00987479 - M50: "Copy in Use" lockup Q00971830 - BCM 3.6 hunt group overflow Q00864456 - calls dropping on Timer Recovery Q00957346 - Pause durati on in Poland MP is too short Q00880226 - PRI209 message is printed out each time a call is answered by Q00901554 - Porting - DAI does not allow for clearing the Hunt Group Metri Q00925630: UK CLID does not work in ASM8+ Q00968360: Pulse dialing of Digit 1 has a conflict with Link (Flash) in Poland market Q00898869: Three way Conference introduces static and degraded voice quality for CALA load Q00964733: False polarity reversal detection for the incoming calls. Q00964720: Release handshake is not happening properly. Event 263 Q00895534: ASM8+ not supported in double density mode Q00975071: CLID and DS needs to be disabled in BCM 3.6.1 release in ASM8+ Australia profile Q00933352: One way speech path on externally forwarded I/C calls Q00929748: BRI issue: fallback to Prime CFWD to External Call is dropped/rejected Q00908910: BCM 3.5: Multiple customers: Programmed values change wh Q00908629: Q00908629 Load test: release trunk driver on path failure Q00934039: Cross talk issue Q00919551: Range Indexing Errors in Hunt Group Code Q00906477: BCM3.01/Hunt Group pick-up 0 calling/Phone Lockup/ Set tin/ [also Q00881236 (P3/CSR)] Q00863025: Incoming DPNSS Embark calls fail Q00910620: Populate the Redirecting Number with the pub/priv digits Q00901481: No speech path after TRO in PRI to Voip tandem. Q00864395: Reset due to corruption of Timer Call Retention Timer Q00862133: Network Callback Timer Field missing in the UM in UK Profile Q00901714: Remove check for cause in tandem of PROGRESS message (Also Q00823209) Q00910620: Allow the Redirecting Number to be sent to FEPS CORE Version Codes: MSC Core wi06.30 (Build date: August 23, 2007) 30DcG31 - EE-ETQ-3.6 (T1) 30DdG31 - EE-ETQ-3.6 (E1-Europe) 30DeG31 - EE-ETQ-3.6 (E1-Globa l) 30DaG31 - EE-CT2P-3.6 (T1) 30DbG31 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.28 (Build date: September 1, 2006) 30DcG28 - EE-ETQ-3.6 (T1) 30DdG28 - EE-ETQ-3.6 (E1-Europe) 30DeG28 - EE-ETQ-3.6 (E1-Globa l) 30DaG28 - EE-CT2P-3.6 (T1) 30DbG28 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.27 (Build date: June 27, 2006) 30DcG27 - EE-ETQ-3.6 (T1) 30DdG27 - EE-ETQ-3.6 (E1-Europe) 30DeG27 - EE-ETQ-3.6 (E1-Global) 30DaG27 - EE-CT2P-3.6 (T1) 30DbG27 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.25 (Build date: February 14, 2006) 30DcG25 - EE-ETQ-3.6 (T1) 30DdG25 - EE-ETQ-3.6 (E1-Europe) 30DeG25 - EE-ETQ-3.6 (E1-Global) 30DaG25 - EE-CT2P-3.6 (T1) 30DbG25 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.24 (Build date: January 3, 2006) 30DcG24 - EE-ETQ-3.6 (T1) 30DdG24 - EE-ETQ-3.6 (E1-Europe) 30DeG24 - EE-ETQ-3.6 (E1-Global) 30DaG24 - EE-CT2P-3.6 (T1) 30DbG24 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.23 (Build date: December 21, 2005) 30DcG23 - EE-ETQ-3.6 (T1) 30DdG23 - EE-ETQ-3.6 (E1-Europe) 30DeG23 - EE-ETQ-3.6 (E1-Global) 30DaG23 - EE-CT2P-3.6 (T1) 30DbG23 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.22 (Build date: November 21, 2005) 30DcG22 - EE-ETQ-3.6 (T1) 30DdG22 - EE-ETQ-3.6 (E1-Europe) 30DeG22 - EE-ETQ-3.6 (E1-Global) 30DaG22 - EE-CT2P-3.6 (T1) 30DbG22 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.21 (Build date: November 9, 2005) 30DcG21 - EE-ETQ-3.6 (T1) 30DdG21 - EE-ETQ-3.6 (E1-Europe) 30DeG21 - EE-ETQ-3.6 (E1-Global) 30DaG21 - EE-CT2P-3.6 (T1) 30DbG21 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.20 (Build date: October 7, 2005) 30DcG20 - EE-ETQ-3.6 (T1) 30DdG20 - EE-ETQ-3.6 (E1-Europe) 30DeG20 - EE-ETQ-3.6 (E1-Global) 30DaG20 - EE-CT2P-3.6 (T1) 30DbG20 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.19 (Build date: October 5, 2005) 30DcG19 - EE-ETQ-3.6 (T1) 30DdG19 - EE-ETQ-3.6 (E1-Europe) 30DeG19 - EE-ETQ-3.6 (E1-Global) 30DaG19 - EE-CT2P-3.6 (T1) 30DbG19 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.18 (Build date: Sep tember 16, 2005) 30DcG18 - EE-ETQ-3.6 (T1) 30DdG18 - EE-ETQ-3.6 (E1-Europe) 30DeG18 - EE-ETQ-3.6 (E1-Global) 30DaG18 - EE-CT2P-3.6 (T1) 30DbG18 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.17 (Build date: August 10, 2005) 30DcG17 - EE-ETQ-3.6 (T1) 30DdG17 - EE-ETQ-3.6 (E1-Europe) 30DeG17 - EE-ETQ-3.6 (E1-Global) 30DaG17 - EE-CT2P-3.6 (T1) 30DbG17 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.16 (Build date: July 10, 2005) 30DcG16 - EE-ETQ-3.6 (T1) 30DdG16 - EE-ETQ-3.6 (E1-Europe) 30DeG16 - EE-ETQ-3.6 (E1-Global) 30DaG16 - EE-CT2P-3.6 (T1) 30DbG16 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.15 (Build date: June 20, 2005) 30DcG15 - EE-ETQ-3.6 (T1) 30DdG15 - EE-ETQ-3.6 (E1-Europe) 30DeG15 - EE-ETQ-3.6 (E1-Global) 30DaG15 - EE-CT2P-3.6 (T1) MSC Core wi06.14 (Build date: June 6, 2005) 30DcG14 - EE-ETQ-3.6 (T1) 30DdG14 - EE-ETQ-3.6 (E1-Europe) 30DeG14 - EE-ETQ-3.6 (E1-Global) 30DaG14 - EE-CT2P-3.6 (T1) 30DbG14 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.13 (Build date: May 9, 2005) 30DcG13 - EE-ETQ-3.6 (T1) 30DdG13 - EE-ETQ-3.6 (E1-Europe) 30DeG13 - EE-ETQ-3.6 (E1-Global) 30DaG13 - EE-CT2P-3.6 (T1) 30DbG13 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.12 (Build date: April 20, 2005) 30DcG12 - EE-ETQ-3.6 (T1) 30DdG12 - EE-ETQ-3.6 (E1-Europe) 30DeG12 - EE-ETQ-3.6 (E1-Global) 30DaG12 - EE-CT2P-3.6 (T1) 30DbG12 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.11 (Build date: March 14, 2005) 30DcG11 - EE-ETQ-3.6 (T1) 30DdG11 - EE-ETQ-3.6 (E1-Europe) 30DeG11 - EE-ETQ-3.6 (E1-Global) 30DaG11 - EE-CT2P-3.6 (T1) 30DbG11 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.10 (Build date: March 11, 2005) 30DcG10 - EE-ETQ-3.6 (T1) 30DdG10 - EE-ETQ-3.6 (E1-Europe) 30DeG10 - EE-ETQ-3.6 (E1-Global) 30DaG10 - EE-CT2P-3.6 (T1) 30Db G10 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.09 (Build date: February 28, 2005) 30DcG09 - EE-ETQ-3.6 (T1) 30DdG09 - EE-ETQ-3.6 (E1-Europe) 30DeG09 - EE-ETQ-3.6 (E1-Global) 30DaG09 - EE-CT2P-3.6 (T1) 30DbG09 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.08 (Build date: February 11, 2005) 30DcG08 - EE-ETQ-3.6 (T1) 30DdG08 - EE-ETQ-3.6 (E1-Europe) 30DeG08 - EE-ETQ-3.6 (E1-Global) 30DaG08 - EE-CT2P-3.6 (T1) 30DbG08 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.07 (Build date: January 26, 2005) 30DcG07 - EE-ETQ-3.6 (T1) 30DdG07 - EE-ETQ-3.6 (E1-Europe) 30DeG07 - EE-ETQ-3.6 (E1-Global) 30DaG07 - EE-CT2P-3.6 (T1) 30DbG07 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.06 (Build date: December 10 , 2004) 30DcG06 - EE-ETQ-3.6 (T1) 30DdG06 - EE-ETQ-3.6 (E1-Europe) 30DeG06 - EE-ETQ-3.6 (E1-Global) 30DaG06 - EE-CT2P-3.6 (T1) 30DbG06 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.05 (Build date: October 25 , 2004) 30DcG05 - EE-ETQ-3.6 (T1) 30DdG05 - EE-ETQ-3.6 (E1-Europe) 30DeG05 - EE-ETQ-3.6 (E1-Global) 30DaG05 - EE-CT2P-3.6 (T1) 30DbG05 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.04 (Build date: September 2, 2004) 30DcG04 - EE-ETQ-3.6 (T1) 30DdG04 - EE-ETQ-3.6 (E1-Europe) 30DeG04 - EE-ETQ-3.6 (E1-Global) 30DaG04 - EE-CT2P-3.6 (T1) 30DbG04 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.03 (Build date: July 26, 2004) 30DcG03 - EE-ETQ-3.6 (T1) 30DdG03 - EE-ETQ-3.6 (E1-Europe) 30DeG03 - EE-ETQ-3.6 (E1-Global) 30DaG03 - EE-CT2P-3.6 (T1) 30DbG03 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.02 (Build date: July 20, 2004) 30DcG02 - EE-ETQ-3.6 (T1) 30DdG02 - EE-ETQ-3.6 (E1-Europe) 30DeG02 - EE-ETQ-3.6 (E1-Global) 30DaG02 - EE-CT2P-3.6 (T1) 30DbG02 - EE-ETQ-3.6 (E1-CALA) MSC Core wi06.00 (Build date: June 1, 2004) 30DcG00 - EE-ETQ-3.6 (T1) 30DdG00 - EE-ETQ-3.6 (E1-Europe) 30DeG00 - EE-ETQ-3.6 (E1-Global) 30DaG00 - EE-CT2P-3.6 (T1) 30DbG00 - EE-ETQ-3.6 (E1-CALA) MSC Core wi02.04 (Build Date: April 26, 2004) 30DcC04 - EE-ETQ-3.6 (T1) 30DdC04 - EE-ETQ-3.6 (E1-Europe) 30DeC04 - EE-ETQ-3.6 (E1-Global) 30DaC04 - EE-CT2P-3.6 (T1) 30DbC04 - EE-ETQ-3.6 (E1-CALA)