Software Update Name: BCM050.198-CORE

Applicable H/W Platforms: BCM50, BCM50a, BCM50e, SRG50

Applicable S/W Platforms: 1.00.2.04g, 1.00.2.04j, SRG50

Category: GEN 

Installation Recommendations: 
   This update should be applied to all new installs of BCM50 R1 and SRG50. 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: 
    core-telephony   40.02.48.8  
    (internal software version code: 30DfC48)

Dependencies: 
   Required Updates: 
   BCM050.SU.System.002 or later
   The Smart Update should be applied first.

   Product Dependencies: None

Size: 4.5MB

System Impact: 
   Time to apply: approximately 2 minutes

   Does update application force reboot: Yes

   Other Impacts: Installation of the update will cause all telephony services to cease during this
                  time. The services will restart automatically after the update installs.

Limitations: None

Update Removable: No

Description:
------------
The following issues are addressed:

1. Market Profile GATM4 failure 
   Intermittently, the GATM2 will not recover after a soft reset.
   A soft reset includes any of the following actions:
   * Disable/Enable,
   * Change of Trunk Mode
   * Change of Market Profile
   This problem is not present on GATM V1 firmware
   Q01679650-03

2. Tandem Call from PSTN rings at the control set
   All tandem calls from the PSTN to the remote site ring 
   at the control set rather than the correct extension number.
   Q01822669-03

3. SRG50 - Hunt Group calls do not connect caller when answered in local mode
   An incoming call attempts to tandems via SRG to the main office.
   The VOIP trunk is down so the call falls back to the prime set
   for the physical line. The prime set does not answer and the call is
   forwarded to a hunt group.  When the hunt group member answers,
   the calling party continues to hear ring back tone.
   Q01881651

This update includes the content of the following superseded updates:

BCM050.191-CORE
---------------
1.  Tandem calls disconnected after placed on hold when TAT feature is enabled.
    Problem: 
    - An Incoming analog line call is tandemed 
      from one BCM to another over VoIP where 
      it is answered. 
    - The call is transferred back to the tandem BCM  
      where it is answered. Trunk anti-tromboning takes
      place on answer (TAT).
    - That set which answered the call has an
      appearance of the incoming analog trunk. 
    - If answered call is placed on hold then
      picked up on another set, (transfer via
      hold) the call is cut off.
    Q01747421

2. Line number information is not displayed until call is answered.
   If CLID information is withheld on an incoming call,
   line number information is not displayed until
   after the call is answered.
   Q01801594-01

BCM050.188-CORE
---------------

1. CFNA calls to CS1000 are dropping after SU3 was applied
   A cell phone call is made from BCM50 R1 (With SU3 patch applied) 
   over an analog line. The call is answered by AA, and the user dials 0 
   for an operator. The operator does not answer and the call is call 
   forwards no answer to a CS1000 over VoIP trunks. At this point the 
   call is dropped.
   Q01798685

2. DPNSS call cut off.
   Intermittent call cut offs are experienced when connected to a
   Central Office and the DPNSS protocol is used.
   Q00970904-01

3. DPNSS call cut off
   When a tandem call is answered at a destination node and transferred
   back to the tandem node via a DPNSS link, the call is dropped after 
   about 2 minutes and the set is left in a locked up state until one 
   presses the intercom key and then the release key. 
   Q01688511-04

4. Unanswered calls disconnect after just 6 minutes
   Incoming trunk calls which are unanswered for 6 minutes are
   force disconnected by the BCM.
   Q01785007-02

5. Hunt group metrics not working.
   An external incoming call is answered by Auto Attendant and then
   transferred to Hunt Group. If the call is abandoned before the Hunt
   Group member answers, the Hunt Group metric for abandoned calls can
   be incorrectly decremented. This can result in large negative
   numbers in the abandoned call metric. 
   Q01825303

BCM050.184-CORE
---------------

1. VoIP TAT not working
   The TAT feature does not work when a tandem call is made from BCM 
   "A" to BCM "C" through BCM "B" and then transferred back along the 
   same route to BCM "A."
   Q01006402-02

2. BCM50 VoIP trunk lock up 
   After a few days of operation, VoIP trunks lock up and never release. 
   BCM Monitor shows the trunk as idle, but no calls can be made.  
   A reboot of the BCM is required to free the trunks.
   Q01662662

3. Call Diversion (Partial Rerouting) not Working on T-T User on BRI/M 
   ETSI Call Diversion (partial re-routing) does not work when the T-T 
   user setting is configured on a BRI module. It works correctly when the 
   S-T user setting is configured.
   Q01788089-03

4. Night service does not turn off on Mondays
   If the night ringing service is set up such that the start and stop times 
   change over the weekend, on Monday, the night service doesn't turn off.
   Q01773120-02

5. Issue with VoIP trunks Locking Up
   After TRO happens on a VoIP trunk, there is a mismatch in the release 
   sequence for subsequent incoming calls on the same trunk. This results 
   in a VoIP trunk lock-up. 
   Q01685091-01

BCM050.182-CORE
---------------

1. 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 ringback approximately three seconds later.
   Q01428057-02

2. The SWCA call can be retrieved using park code(101) 
   The SWCA call can be retrieved using the park code. It should display error message
   "No call on :nnn" instead of retrieving the call.
   Q01675431

3. Redirection information is unknown in a particular scenario.
   If the CS1000 ACDN is network call forwarded to a BCM and this call in turn is 
   forwarded back to CS1000 and TRO is enabled, log event 202 is generated on CS1000
   due to unknown redirection reason.  
   Q01652360

4. 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-03

5. 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-06

6. Intermittently, the skill set agent does not get the Activity Code
   prompt after releasing a call.
   Q01675801-01

7. Background music is not retained for IP sets after a system reboot.
   Q01321800-04

8. Redirect information is incorrect after Blind Transfer when 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-01

9. Line Tuning For BCM 50 R1
   This update introduces the line tuning feature for the BCM 50 R1 product.
   Q01475421-05

BCM050.171-CORE
---------------

1. Trunk Module Metrics: BRIM Loops status is wrong
   The BRI firmware reports Layer 1 status as disabled even though the loop
   is enabled and the attached BRI Set is functioning normally. 
   Q01060334

2. SRG50: Calling Party Privacy is not working 
   When a set in Normal mode dials through VoIP to the SRG
   using the CS1000 presentation restricted feature (no calling
   party number provided), the SRG substitutes its main number 
   in the tandem call to the public network. In keeping with
   the presentation restricted feature, no calling party
   information should be provided.
   Q01538245

3. Night ringing service stops working
   Night service ringing will stop functioning if the night service 
   configuration end times are different for different weekdays.
   Q01621516-02

4. Unable to add Internal Autodial to Hunt Group member using Element Manager. 
   One can program an internal autodial of a Hunt Group DN by using
   Feature*2 on the set, but cannot do this in Element Manager. 
   An "invalid DN" error is raised in Element Manager. 
   Q01490178-01

5. Line Tuning For BCM 50 R1
   This update introduces the line tuning feature for the BCM 50 R1 product.
   Q01475421-05

BCM050.167-CORE
----------------

1. Auto Night Ringing Service Not working in a couple of scenarios
   AUTO Night Ringing  Service is getting Turned Off in the following scenarios:
   - Night ringing service is on and the physical line configuration 
     is changed (name, control set, etc.)
   - If a physically disconnected control set is plugged in while night	 
     service is active, the control set will show Nite Service ON once it 
     comes up. However, incoming calls are not extended to ringing group DNs.
   Q01658726

2. Problems Programming CAP Sets
   Programming changes made in Element Manager are not propagated to 
   the CAP of a 7324 set. 
   Q01534835

3. Issues with restrictions filters and Element Manager
   Element Manager does not display "1AAA" set restriction 
   override filters that were programmed through the set-based
   admin. Also, the user cannot add the restriction "1AAA" in
   element manager.
   Q01514355

4. 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-05

5. Cut & Paste button programming causes loss of intercom keys
   Customer has reported multiple sites whereby the intercom keys have been replaced 
   by an autodial key when they have cut & pasted keys using Element Manager. When
   this happens, users are not able to make any calls.
   Q01521070-01

6. Network billing is incorrect in tandem call forward scenario from BCM50 to external number. 
   An incoming PRI call which tandems back to the public network
   passes the original Calling Party Number instead of the forwarding
   number from the BCM.  This prevents the end customer from billing
   correctly to the forwarding number.
   Q01623271

7. Aux ringer problems on hunt groups
   Intermittently when a hunt group is configured with an aux
   ringer, the aux ringer appears to stick and the bell rings continuously.
   Q01579766-01

BCM050.165-CORE
----------------

1. Auto dial key busy state goes out even though monitored set is busy.
   The auto dial key on an 2004  set will occasionally go off 
   even though the set being monitored is still active on a call.
   Q01522683

2. SRG50 in normal mode: tandem calls to PSTN are dropped
   Outgoing tandem calls to a BRI interface through an SRG are 
   disconnected if the far end is busy. 
   Q01525727

3. On an SRG tandem trunk calls get "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-02

4. Core reset happens when a call is made over an analog trunk to an ISDN set
   The CoreTel process resets when a call is made over an analog trunk to an
   ISDN set and the "Auto Associate SWCA key to call" option is configured as 
   "Automatically - Life of Call".
   Q01491634-02

5. Incoming calls to DISA and AUTO DN do not work after a while
   After some period of time incoming BRI calls to DISA and auto DN numbers
   fail due to unavailable DTMF receivers. 
   Q01567184

6. IP set intercom key locks up, unable to receive incoming calls
   Different IP sets occasionally have a problem where the first (bottom)
   intercom key is locked up in use.  The intercom key is displayed as
   "in use."  The IP set cannot receive incoming calls.	Outgoing calls
   can be made on the second intercom key.
   Q01577064-01

BCM050.156-CORE
----------------

1. Core Stuck in infinite loop after significant numbers of Logevent 139
   Under certain conditions, CoreTel software may get stuck in
   an infinite loop when large numbers of logevent 139 errors occur.
   Q01463942-02

2. Lockups after IP call transfer.
   If an answered IP call is placed on hold and quickly transferred to an
   external number before an alerting message is received, CoreTel will reset 
   Q01413796

BCM050.153-CORE 
---------------

1. Retrieving parked call issue
   When retrieving a parked call, audio is heard from both the handset
   and the set speaker.
   Q01521857

2. SRG50: No speechpath in Survival Mode
   An incoming call to a hunt group on an SRG 50 which is in survival mode
   receives no speech path when the call is answered. 
   Q01496626

3. Analogue Exchange Lines (GATM) Locking-up
   In the UK market, loop guarded analog lines may lock up
   intermittently, preventing customers from making or receiving calls.
   Q01403818
	
4. Enbloc sending on BRI after Core Patch BCM050.139-CORE-3.3-1.1
   Outgoing ETSI BRI calls cannot be configured as overlap sending.
   All outgoing calls are using enbloc dialing.
   Q01523153

5. No traceback on fatal Logevent 115
   Upon the fatal Logevent 115, the component resets without providing a 
   core dump, which makes debugging difficult.  This software change provides
   sufficient information in the logevent 115 to allow more accurate debugging.
   Q01413796-02

6. Not able to dial out on 2nd PRI if 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-01

BCM050.139-CORE
---------------

1.  ENBLOC over VoIP does not function under certain conditions
    An incoming PSTN call over ETSI BRI line is forwarded from
    BCM1 to BCM2 via VoIP trunk. The call is incorrectly answered at BCM1 
    while the far end hears ring back tones from BCM2.
    Q01296708

2.  Delay on speechpath when call tandems through SRG50 to a Main Office Set.
    A five second delay for speech path cut through is experienced when an
    incoming PSTN call to an SRG tandems via VoIP trunk to the CS 1000 and
    is answered by an ACD agent.
    Q01407395-03

3.  Incoming calls with a leading digit 0 are not routed to prime.
    In the German market any incoming call with 0 as the first digit should
    automatically route to the prime set. This was not happening.
    Q01484418-01.

4.  No Voice path in BRI to PRI Tandem Scenario.
    When a tandem call is made between a BRI and PRI trunks, no speech path
    is present on call answer.
    Q01472015 

5.  CoreTel not responding after applying patch
    Multiple VoIP calls between a BCM and CS 1000 can result in a CoreTel freeze.
    Q01472822

6.  VoIP trunk lockups on BCM 50 Core Patch BCM050.111-CORE-3.0-1.0
    When 2 VoIP consecutive calls are made over the same trunk the trunk
    locks up and cannot be accessed.
    Q01453438

7.  Incoming Calls cutting off
    The 2 Main numbers on  a customer's PRI link experience cut-offs  
    during high call volumes. 'Normal Call Clearing' on display when
    they press to answer call or during a call.  This was due to a 
    race condition occurring between call release and the start of the 
    next call, where the line is released but the B-channel remains 
    allocated. 
    Q01376136

8.  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-02

9.  ISDN clocking, event, & 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-02

10. No Drop Back/rerouting when calling out via SRG50 CO trunks which are down
    The VoIP drop back rerouting feature on the CS 1K is not activated
    because the SRG 50 is sending the incorrect release reasons when a VOIP
    tandem call encounters congestion on the public network.  
    Q01414470

BCM050.113-CORE
---------------

1.  MWI and fallback routing
    BCM 3.7 serves BCM50s as a centralized VM.  When fallback
    routing to analog trunks is used, MWI does not work.
    Q01280952-03

2.  Music on hold will not play
    When dialing a DID, if the end user puts the phone on hold, no
    music is heard. This occurs only if target line is set to "private."
    Q01279357-01

3.  No speech path on incoming PRI call to IP set private subnet
    Incoming call to IP set via PRI trunk resulted in no speech path.
    Q01246753-03

4.  QSIG and ISDN connection problem
    Using the UK profile, program PRI ETSI Euro trunk with 
    "Overlap receiving = Y" then change the protocol variant to ETSI QSIG.
    The "Overlap receiving" prompt disappears but the overlap reception
    functionality keeps working which is confusing, and it makes the
    trunk appear as if it is not functioning properly
    Q01266644-03

5.  Incorrect trunk status on BCM maintenance set
    On a T1 digital trunk interface: if all channels are active on calls, 
    and they are taken out of service due to a Layer 1 failure, 
    the maintenance status shows as "0 busy." When Layer 1 
    recovers, the status should once again be "24 lines busy."
    The maintenance status incorrectly shows "20 lines busy." 
    Q01222057-02

6.  Telset does not display the prefix 0 of the CLID
    In the Swedish market a leading prefix (digit 0) is used in the
    calling line ID. This information was not being displayed as part
    of the CLID number.
    Q01122824-02

7.  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 receives 1 way speech path when the calls are answered
    Q01317384-03

8.  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

9.  Feature 2 (Later) not working
    Ring again feature is not working when the "later" soft key is 
    pressed after attempting an outgoing call.
    Q01338760

10. 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 at problematic
    customer sites.
    Q01318719-03

11. Reduced receive levels for echo patch control
    LP Changes have been implemented to the loss plan for GATM cards 
    to correct low volume, echo, and broken conversations 
    Q01303269

12. 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-01

13. 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

14. BCM - ETSI Euro PRI will not connect to New Zealand ISDN
    This adds a New Zealand market profile to the BCM50 Release 1. 
    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-05

15. Agent Monitor intermittently gives "supervise failed" message
    Intermittently an ACD supervisor is unable to monitor a target agent.
    Q01302731-01

16. 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

17. 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

18. LAN CTE application unavailable
    When the clock ticks counter on the core rolls over from a large
    negative value to a positive value (once every 248 days) this 
    can disrupt active timers, occasionally resulting in a telephony
    core reset. 
    Q01189301-03

19. BCM 50: echo on external calls (one side)
    BCM50 IP set users experience echo on calls over analog lines from the
    PSTN.
    Q1246874

20. SWCA does not work as expected on T24 KIM
    SWCA appears to work as expected on keys on a T7316E, however
    behavior changes when on a KIM. This solution adds new code to 
    the call park feature for support of SWCA and Enhanced SWCA
    features on EKIM/ECAP.
    Q01363103

21. Call will not be associated to SWCA key after transferring the call.
    If a call retrieved from SWCA is transferred to another set, the SWCA
    call association is lost. SWCA call association should be for the life
    of the entire call. 
    Q01417270

22. 3-WAY CONF with AA will not release initial DTMF tone
    Occasionally, if digit keys are pressed while in an established
    conference call, a tone is heard from the set and speech
    connection with all conference members is lost.
    Q01414831

23. GATM line 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-03

24. Need to include G4x16 in BCM50 R1 EM
    The original 4x16 was Manufacture Discontinued since
    the components used to manufacture the box are End Of Life.
    As part of BCM50 R2 a new 4x16 module (G4x16 - NT8B42AAABE5)
    was introduced and the CoreTel changes need to be ported
    back from BCM50 R2 to BCM50 R1 so that customers can continue to
    procure G4x16 modules for their BCM50 R1 Expansions. 
    Q01442640

25. 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 28Problem with incoming calls on PRI
    Q01392178-03

26. 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-03

BCM050.084-CORE
---------------

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

BCM050.073-CORE
---------------

1. ATA/ASM recall timer incorrect for Austrian/German market
   The current switch hook flash timer duration is inadequate for the Austrian 
   German market. This solution changes the switch hook flash durations to 
   expected values. (100 ms +/-20 ms).
   Q01272743

2. North American Loss Plan update for echo issues.
   This solution implements loss plan adjustments for BCM50 IPset users who
   were experiencing echo on calls over analog lines from the PSTN. 
   Q01246874 Q01268840 Q00969258 Q01100714

3. VoIP lines go busy. 
   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:
   - BCM050.065-VOIPGATEWAY-IPTELPROVIDERAGENT-1.1-1.0 or higher
   Q01120093-03

BCM050.041-CORE
---------------

1. Q01247102 GASM8+MBM will not boot
2. Q01101726 Cannot call out on idle T1 EAM, auto answer channel. 
3. Q01222053 BRI terminal gets incorrect call treatment when T1 lines are unavailable. 
4. Q01178926 Tandem call MCDN to PSTN and disconnects if the call goes to VM. 
5. Update to MCDN protocol to accept a PROGRESS message in a Call Delivered state. 
6. Q01229855 Daily schedules are not activated correctly. 
   This is caused by the day of the week not being reset correctly when system. 
7. Q01273213 No CONNECT PI Out 

BCM050.023-CORE
---------------

1. Q01184612 Hunt group overflow call is returning to AA after 1 ring. 
2. Q01200546 Protect against potential system crash due to uninitialized variable. 
   Caused when MSM goes down as the system is booting. 
3. Q01019869 Hunt group set not ringing. After a specific call transfer scenario, 
   a hunt group set may no longer alert for hunt group calls. 
4. Q01229855 Reset day of the week when updating system time 
5. Q01247102 Stop-shipping Issue for GASM: ASM8+ will not boot [also Q01180514 Q01165379] 

BCM050.016-CORE
---------------

1. Q01175385 Allow the transmission of DTMF tones on the BCM50 paging speaker 
2. Q01121305 Resolves a call disconnect issue when making a PRI/BRI 911 call to
   a Lucent 5ESS switch having both PSAP (911) equipment installed and 
   also supplying the end user's PRI/BRI service. 
3. Q01165773 Resolves an intermittent call disconnect issue with MCDN to PSTN
   calls tandemed through an M1. 

BCM050.008-CORE
---------------

1. Q01126447 UK GATM driver: Adds support for Algo dongle. 
2. Q01072877 Resolves intermittent ASM8+ port lock ups when connected to 3rd party devices. 
3. Q01107104 Resolves tandem PRI-IP calls being dropped under heavy loads because of 
   a race condition during ca ll release. 
4. Q01125596 Protect RADAR flow control against zero-length messages 
5. Q01121305 Add support for AT&T Call Queued cause value on BRI/PRI NI2 trunks 
6. Q01122222 Allow programming of CAP buttons without TCMI keycodes 
7. Q01120248 Make sure feature option gets defaulted on button change 
8. Q01129644 Fixing the gain control for GATIs to enable MOH. 
9. Q01133734 Correct the initialization order of srg_config to fix SRG IC keys 
10. Q01111249 Protect against a set Paste without a preceding Copy 
11. Q01112394 Reduce cache-out time from 30 min.  to 5 min. to reduce data loss 
12. Q01113038 Handsfree & headset failed with prime line set for line pool [also Q01110207] 
13. Q01113326 Restore the SRG mode after switching market profiles 
14. Q01115435 Prevent fatal log 115 when checking the BRI loop clock source 
15. Q01100985 Fix SetPoolAccess to consider Bloc line pools 



