PRODUCT_LINE: BCM ============================================ TITLE ===== BCM370.249-CORE ======================== Release: 3.7 Issue: N/A Category: GEN Superceded By: NONE Release Date: 20080108 Patch Conflict(s): N/A Special Instructions: NO Patch Version: N/A ======================== Software Update Name: BCM370.249-CORE Applicable Platform: 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 patch 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 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.7 core wi07.23 Dependencies: Required patches: When using PRI, DASS2, DPNSS or T1 trunks, the Alarm Monitor patch BCM_370.097_ALRMMON.46.11 or later or BCM370.213-SU3 or later should be installed. When using Voice over IP trunks, the FEPS patch BCM370.241-FEPS patch 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. Line redirecting to incorrect number at times When two calls come in at the same time to different target lines, both calls redirect to the same destination. Q01755373 2. Loss of Voice Path When TAT is enabled and a set makes an outgoing call which tandems back to the originating node, the destination set hears no speechpath on answer if a wireless set is configured as an answer DN for the destination set. Q01741954 3. Night service does not turn off on Mondays The customer has night ringing service set up where the start and stop times change over the weekend. On Mondays, the night service doesn't turn off. Q01773120 This patch includes the content of the following superseded patches BCM370.244-CORE --------------- 1. Supervised ROI trunks drop when Auto Attendant answers the call in Australian market Q01470485, Q01663473 2. Event 380 is not seen for ROA Line tuning in Australia The line tuning feature is non functional in the Australian market. This could result in incorrect volume levels for analog trunk calls. Q01653010-02 BCM370.239-CORE --------------- 1. Line Tuning For BCM 3.7 This update introduces the line tuning feature for the BCM 3.7 product. Q01475421-03 2. Night ringing service stops working Night service ringing will stop functioning if night service configuration end time is different for different weekdays. Q01621516 3. Pulse Dialing not working for Brazil Market profile. The Pulse Dialing mode did not work for Brazil Market profile with a GATM1 module. The customer was unable to establish outgoing calls on analog lines when the "Dial Mode" was changed from "Tone" to "Pulse" Q01612145-02 4. Redirecting information is incorrect after Blind Transfer if TRO is enabled An incoming PRI call is tandemed from a CS1000 via VoIP to a BCM where it is answered. The BCM transfers the call to a second CS1000 via VoIP trunk where the call is "forward all calls" back to Centralized Voice mail on the first CS1000. When TRO is invoked to optimize the VoIP trunks, the BCM sends incorrect redirection information to the first CS1000 so the transferred call lands in the general delivery mail box instead of the set mail box. Q01594717 BCM370.231-CORE --------------- 1. NEP Low speech on analog trunk call and IP phones The end user is complaining of low speech volume when they make out going calls via the GATM. The transmit low volume issue is seen on TDM as well as IP Sets. Q01513090 2. 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-01 3. Delayed voice cut through occurs on calls to voice mail which dial "0" An incoming call to site A which tandems to site B is forwarded to the user's mailbox back on site A. When the calling party dials "0" to reach the main number at site B, ringback is not heard, and there is a 3 second delay in speech cut through. Q01620937 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-04 BCM_370.208_CORE.08.0716 ------------------------ 1. SRG, Trunk out of service When a single PSTN line is assigned to more than 40 sets on an SRG system, call attempts to the PSTN fail showing "Out of Service". Q01297447 2. The ftxDialDigits feature does not always dial all digits requested The ftxDialDigits Xfeature allows an application the ability to dial out digits on an active call. On the very first attempt after system start up on a device that an ftxDialDigits is requested, only the last digit in the request is actually sent out. Subsequent calls to ftxDialDigits on that device dial out all digits requested. Q01449836-01 3. Incoming calls with a 0 at the end of the main number are not routed to prime set In the German market, callers dialing into a BCM should be routed to the prime set if they use 0 at the end of the Main number. This feature was not working. An incoming SETUP message on a BRI Loop with dialed number "0" results in a reject message sent from the BCM. Q01484418 4. Core Hunt Group Metrics incorrect during forward scenario The Hunt Group metrics are incorrectly incremented when a call which was answered by a particular hunt group is transferred to a set outside the group which is itself call forward all calls to the same hunt group. Q0136203 BCM_370.202_CORE.08.0715 ------------------------ 1. ENBLOC OVER VOIP DOES NOT WORK IN SPECIAL CONDITIONS A incoming call from the central office via the ETSI BRI trunk is forwarded via BCM1 to BCM2 via VOIP. In the protocol trace, the call is shown as being connected when the far end hears ring back tones. The call should only be connected when the destination answers the call. Q01296708-01 2. BCM Delay in sending NAM on DPNSS Link Incoming DPNSS calls on Feature-Net Embark circuit rings the destination set immediately. However the calling party hears ring tone approx. 3 seconds later. Q01428057 3. UNABLE TO DIAL FAXES FROM ATA EXTNS Fax calls from ATA2 to DASS2 destinations would not connect. The CO warns "This service is not compatible with the call". The problem is specific to the DASS2 interface. Faxing to the same number via Unified Messaging, or using a PRI Euro interface is successful. Q01440544 4. 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 5. Problem with incoming calls on PRI An incoming PRI call to site A which tandems to site B via T1 E&M, are dropped if the call is not answered within 2 rings. Internal calls from BCM A to BCM B are successful. Q01392178-01 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.177_CORE.08.0712 ------------------------ 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 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 3. BCM400 3.7 - Feature 2 (Later) not working Ring again feature is not working when the "later" soft key is pressed after attempting an outgoing call. Q01338760 4. Line and Set Restrictions Bypassed (Fraud) This solution makes the F**OPTION feature available in the Unified manager. This feature was previously only available through set based UI. F**OPTION allows the user to activate additional toll fraud protection in problematic customer sites. Q01318719 5. Reduced receive levels for echo patch control IP Changes have been implemented to the loss plan for GATM cards to correct low volume, echo, and broken conversations Q01303269 6. Core Hunt Group Metrics incorrect in reroute scenario The Hunt Group metrics on the core are incorrectly counting the number of calls and abandoned calls in the scenario involving a call transfer Q01328892 7. 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 8. BCM 400 - Agent Monitor intermittently gives "supervise failed" message Intermittently an ACD supervisor is unable to monitor a target agent. Q01302731 9. 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 is 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 references. Q01244275 10. 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 11. Core DSP: 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. BCM370.124_CORE.08.0710 ----------------------- 1. BCM - ETSI Euro PRI will not connect to New Zealand ISDN Currently the ISDN protocol used in New Zealand does not request a B-channel when outgoing calls are made. The CO indicates which B-channel to use when it responds to the seize request. The New Zealand market is introducing a new product that requires the B-channel to be specified when a line to the network is seized. This enhancement implements the functionality. New prompts for the B-channel sequence are now visible for ETSI EURO PRI protocol. Options are: None, Ascending and Descending. Q01308779 2. When VoIP trunks are in night mode MWI for centralized voice mail does not work The customer has VOIP trunks configured between BCM50 and BCM 3.X. The 3.X BCM provides centralized voice mail for the BCM50s. If the VoIP trunks fail, fallback is to analog lines. When the System is in Night mode and a message is left in a mailbox for a BCM50 user the Message Waiting Indicator does not light on the BCM50 user's set. Q01280952 BCM_370.117_CORE.08.0709 ------------------------ 1. Calls in Analog trunk get frozen This solution makes **OPTION UI for busy tone disconnect supervision visible in Unified manager. This is necessary for SRG users since they do not have access to set base administration. Without access to set base administration, disconnect supervision is not provided and the trunks lock up. Q01282366 2. Porting of IP Paging Delay feature This enhancement changes the way the paging feature works when multiple IP sets are present in the system Paging to large numbers of IP sets imposes a performance penalty. If the person paging starts to speak immediately parts of the speech may be cut off. This enhancement provides a programmable delay prompt to indicate to the person initiating the page to proceed with the page. The prompt is intended to allow sufficient time for IP sets to be connected to the paging server. Q01024914-01 3. 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 4. Music on Hold will not play When dialing a DID, if the end user puts the phone on hold, no music is heard. Q01279357 5. Redirected Calls Fwd on PRI to DMS DID trunks may not hear ringback. This solution corrects a PRI NI-2 specification compliance issue which may result in the calling party not hearing ringback on tandemed calls. Q01094224-02. 6. QSIG - Overlap Receive prompt display in UM The prompt for overlap receiving is not present when the QSIG PRI protocol is selected. It should be visible. Q01289436 7. Fix for No voice path and crosstalk. Incoming call to IP set via PRI trunk can occasionally result in no speech path. Q1246753-02 BCM_370.105_CORE.08.0708 ------------------------ Q01216314 Progress Indicator Additions Q01120093 VoIP line go to busy state Q01222065 Maintenance terminal does not report clearing of alarm condition Q01289436 QSIG - Overlap Receiving prompt display Q01222057-01 Incorrect trunk status on BCM maintenance set BCM_370.098_CORE.08.0707 ------------------------ Q01104297-01: Hidden programming of QSIG overlap dialing issue Q01096719-01: Porting of karum.386 - Reset on transfer of CO call to ISDN set. Q01189546: "Port from BCM36 - Cannot tandem call from T1 over VoIP" Q01181453: SRG1.0: EURO E1 PRI: No Ring Back or Speech Path: Local Mode Q01036297-01: F*82 on IP set cause core reset Q01215733: Problem with T7316e revision 4 sets with BCM3.7 Q01258165: MCDN TAT fails via H323 trunk Q01100714 Q00969258 Q01140577 Q01128198 Q01096653: Lossplan Changes for Echo and clipping Q01273213: No CONNECT PI Out (When a PRI call is made from a BCM 3.7, system into the BCM50 Call Centre, the call is dropped, just as the call is answered by the Call Centre.) Q01178926: Handle MCDN PROGRESS message in state U4=Call Delivered BCM_370.086_CORE.08.0706 ------------------------ Q01189301 Port from BCM36 for CR Q01189301: core reset Q01189301 Port from BCM36 for CR Q01189301: core reset Q01126529-01 Core Reset on BRI line selection as BRI loop boots Q01247102 Stop shipping Issue for GASM BCM_370.075_CORE.08.0705 ------------------------ Q01219218 SWCA: Not able to make call and shown blank in one particular sc Q01219221 SWCA: "Oldest SWCA" F*537 function is not proper in one scenario BCM_370.059_CORE.08.0703 ------------------------ Q00971020 No sequence checking for unrecognized IEs Q01087165 Update UI-Frame handling Q01121305 Allow receipt of STATUS msg after 911 call to 5ESS switch Q01179463 BCM37-HG calls drop if AnserDN Answers. Q01026566 Update PRI Makefile to allow creation of D64 files Q00971043 Missing Channel ID in RESTART message exception handler Q01033464 Ignore unrecognized IEs in sequence checking Q01165773 Add MCDN Progress Indicator to the CONNECT message Q01101726 Cannot call out on idle channel Q01200784 Dsaint.1609 not ported to BCM 3.7, BCM 3.5 and BCM 3.6 Q01210192 Add F**OPTION administration for GATM disconnect tone Q01209020 Update SWCA so SWCA controlled park codes cannot be dialed dire Q01184612 Port dsaint.1620. Fix extra IM ring messages after trunk connect Q01185678 handsfree issue when taking a held call during all call page Q01170412 SM functionality with DECT as AnsDN BCM_370.056_CORE.08.0208 ------------------------ Q00968360 Link feature and Pulse dialing for Poland market do not work. Q01018341 Porting of Some CRs from MAIN stream to BCM3.7 stream. Q01042490 BCM 3.6 call routing counts F78 as 3 digits towards 24 digit max Q01121345 To correct race conditions on RELEASE Q01150579 voice path lost when held privacy control Q01178579 Paging on speaker from DMC portable is not transmitting DTMF Q01028145 Unable to send digits from slave when master puts Conference on hold Q01152682 Invoking F*81 in DECT set allowing that feature Q01018341 THE CROSSTALK ON IP PHONES. Q01019869 Hunt group DNs not ringing Q00970904 DPNSS calls cut off Q01082560 Invalid information element in disconnecting calls. Q01113443 BCM 3.6 Hunt Group Overflow phone rings solid Q01121305 Mics 6.1 dials 911 but call gets rejected Q01122824 Tultra Telset Doesn't Display the Prefix 0 of the CLID Q01120010 Sweden market fails to add leading "0" to National calls Q01103606 BCM 4003.5 Randomly rebooting Q01126447 UK GATM driver: Need to change RZ bit to support Algo dongle solution Q01113767 BCM 1000, 3.6: Call Logs not showing Calling Number Priority BCM_370.037_CORE.08.0207 ------------------------ Q01107104 To fix load test related issues (Q01088920, Q00932969) Q01148302 DECT will get a ringing splash being an answer DN for supervisor Q01107778 Upgrade from BCM3.0 to BCM3.6 for T7316E sets BCM 3.7 MSC Core wi02.06 Update ------------------------------- Q01099625 Juniper T7316 to boot up in Taiwan Profile. Q01123638 Fixing the problem of DMC portable not getting VOLUME UPDATE Core version codes: (30DgH23) CT2P : NorthAm, Carribean, HongKong, Taiwan (30DhH23) E1 CALA (CT2P): CALA, Global, Australia, PRChina (30DiH23) Etiquette: NorthAm, Carribean, HongKong, Taiwan (30DjH23) E1 Euro: UK, Sweden, Denmark, Holland, Norway, Italy, Germany, Spain, Switzerland, France (30DkH23) E1 Global (Etiquette): CALA, Global, Australia, PRChina, Poland