Software Update Name: BCM.R400.SU.System.014-200809

Applicable H/W Platforms: BCM200, BCM400, BCM1000, SRG200 1.5, SRG400 1.5

Applicable S/W Platforms: BCM 4.0, SRG 1.5 based on BCM 4.0

Category: GEN

Installation Recommendations:
This update should be applied to all new installs of BCM 4.0 and SRG 1.5 based on 
BCM 4.0. 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.
The latest Desktop Smart Update should be applied with this update if the affected 
desktop applications are used.


NOTE: 
If the current version of Element Manager you are currently using is not 2.05 or 
greater, you must first apply BCM.R400.SU.Desktop.005-200801 or later. 
Then, install the new EM from the BCM on your PC before you can install 
this [ BCM.R400.SU.System.014-200809 ] update or any other updates.
If BCM.R400.SU.Desktop.005-200801 or later has already been applied to the 
BCM and your current version of EM is 2.05 or greater you can proceed with 
normal update application.


Components & Versions: 
   apache                     2.0.63
   apcupsd                    3.14.01
   backup-recovery            41.2.28.10
   backup-restore-provider    41.2.26.91
   BCM_DataComponentsProvider 41.10.56.149
   bcmEMcartridge             BCM200.3.75
   BCM_DOORPHONE              41.2.6.127
   bind                       9.4.1-P1
   btrace                     42.1.57.6
   callpilot-provider         41.10.24.09
   cdr                        41.11.10.10
   cdr-client                 41.11.09.10
   cdr-provider               41.11.09.10
   cfs                        41.10.24.19
   core-telephony             41.02.23.8
   core-telephony-provider    41.00.31.96
   cte                        7.11.08A
   cteapps-obt                41.00.07.98
   cti                        41.33.02.1
   dataservices               41.0.450.70
   dhcp-provider              41.80.100.84
   dialogger                  41.20.05.15
   dsp-firmware               37.70.120.9
   ems                        40.02.101.26
   feps                       41.590.0.33
   gap                        42.1.58.6
   glibc                      2.3.2-80.10.12.1.0_2007k
   inventory-provider         41.20.01.115
   ipsecprovider              41.0.29.71
   ipsetfirmware              41.4.03.0
   iptelprovideragent         41.140.8.43
   isdn                       41.10.300.116
   ivr-reenable               41.0.0.200
   ivrprovider                41.00.2046.113
   kernel-modules             2.4.22-10.wk12.1
   lan-cte-provider           7.11.05A
   lan-provider               41.10.50.82
   mgs                        41.80.0.3
   mof-db                     2.76
   mps                        41.50.3.34
   mscdriverservice           41.30.06.20
   mtt                        41.10.36.37
   ncglkernel                 2.4.22-80.10.12.2.2
   ntp                        41.0.4.25
   openssh                    4.4p1-80.10.07.1.0
   openssl                    0.9.7l-80.10.07.1.0
   openwbem                   41.1.31.135
   periase                    41.0.28.2
   peribim                    41.0.29.2
   periglobl                  41.0.28.2
   psm                        41.20.202.11
   qos-monitor                41.0.0.165
   scd                        41.38.13.50
   security-provider          42.1.42.6
   software-management        41.20.003.158
   startup-profile            41.20.07.117
   utps                       41.320.0.12
   voicemail                  41.02.59.22
   voicemail-turkish          41.02.06.23

Constituent Updates:
====================

New updates for this SU:
------------------------
   BCM.R400.212-CTI
   BCM.R400.211-APACHE

Updates from previous SU:
-------------------------
   BCM.R400.215-CORE
   BCM.R400.208-IVR
   BCM.R400.207-IPTEL
   BCM.R400.205-ISDN
   BCM.R400.204-CDR
   BCM.R400.203-UTPS
   BCM.R400.202-SCD
   BCM.R400.201-CTI
   BCM.R400.199-VOICEMAIL
   BCM.R400.198-OAM
   BCM.R400.195-DHCP-PROVIDER
   BCM.R400.193-IVR-RE-ENABLE
   BCM.R400.192-CTI
   BCM.R400.191-UTPS
   BCM.R400.190-DOORPHONE
   BCM.R400.189-VOICEMAIL
   BCM.R400.188-CDR
   BCM.R400.187-IVR
   BCM.R400.186-IPTEL
   BCM.R400.180-Dialogger
   BCM.R400.179-CTE
   BCM.R400.177-CTI
   BCM.R400.175-GLIBC
   BCM.R400.174-MSC 
   BCM.R400.171-IVR
   BCM.R400.170-RECOVERY
   BCM.R400.169-VOICEMAIL
   BCM.R400.168-UTPS
   BCM.R400.167-NCGLKERNEL
   BCM.R400.166-SCD
   BCM.R400.165-CORE
   BCM.R400.163-QOS
   BCM.R400.161-CDR
   BCM.R400.160-SoftwareManagement 
   BCM.R400.159-VOICEMAIL
   BCM.R400.158-CORE
   BCM.R400.153-BTRACE
   BCM.R400.150-GAP
   BCM.R400.149-DSPFIRMWARE
   BCM.R400.148-CORE
   BCM.R400.147-CTI
   BCM.R400.146-BIND 
   BCM.R400.144-OPENWBEM
   BCM.R400.143-CORE
   BCM.R400.141-VOICEMAIL
   BCM.R400.138-IPTEL
   BCM.R400.137-APPP
   BCM.R400.136-VISTA
   BCM.R400.135-QOS
   BCM.R400.127-CDR
   BCM.R400.126-DOORPHONE
   BCM.R400.125-UTPS
   BCM.R400.124-VOICEMAIL
   BCM.R400.123-CTI
   BCM.R400.121-GLIBC
   BCM.R400.120-ISDN
   BCM.R400.116-SCD
   BCM.R400.115-RECOVERY
   BCM.R400.110-VOICEMAIL
   BCM.R400.109-CORE
   BCM.R400.108-TurkishPrompts
   BCM.R400.107-CTI
   BCM.R400.105-IPSecProvider
   BCM.R400.104-QOS
   BCM.R400.099-CDR
   BCM.R400.097-UTPS
   BCM.R400.096-VOICEMAIL
   BCM.R400.095-DSPFIRMWARE
   BCM.R400.089-IVR
   BCM.R400.085-IPTEL
   BCM.R400.084-QOSMON
   BCM.R400.083-QOS
   BCM.R400.081-CORE
   BCM.R400.080-SCD
   BCM.R400.076-InventoryProvider
   BCM.R400.078-CTE
   BCM.R400.073-OPENSSH_OPENSSL
   BCM.R400.069-IVR
   BCM.R400.066-CDR
   BCM.R400.064-LANDriver
   BCM.R400.063-CTI
   BCM.R400.061-OAM
   BCM.R400.050-SU1
   BCM.R400.046-SoftwareManagement
   BCM.R400.044-VOICEMAIL

Dependencies: 
   Required Updates
   BCM.R400.160-SoftwareManagement or later must be applied before this update

   Product Dependencies: None

Size: 149MB

Size of changed content since last Smart Update: 2.1MB

System Impact:
    Time to apply approximately 20 minutes.

    Please note that the CTE Server and the following applications may have to be 
    shut down and restarted after the update is applied:
   1. BCM Monitor - Line Monitor Service.
   2. Doorphone
   3. Hunt Group Metrics Reporter

Does update application force reboot: Yes
   Over last Cumulative Smart Update: Yes
   Over default content: Yes

Other Impacts: 
   The IVR Engine will be restarted. This will prevent the IVR applications 
   from running while the update is being installed.

   The IVR Provider will be restarted. This will prevent the administration
   of IVR via Element Manager during that time.

   DHCP Server on BCM will be temporarily disabled while the update is being installed.

   Voicemail application will be down while the update is being applied

   VoIP Trunks will be unusable during the application of  the update.
   
   IPSets will go offline during the system reboot.
   
   If it is suspected that a UDP attack has already occurred on the BCM, 
   then the BCM should be rebooted prior to applying this update in order 
   for the update to apply properly.
   

Limitations: 
  
   Restoring a 'backup' taken from a BCM prior to CoreTel version 2.03 (BCM.R400.SU.System.002-200708) 
   to a system greater than version 2.03 is not supported.
   Restores have been confirmed to work if it's taken from the BCM with BCM.R400.SU.System.002-200708 
   or 'later releases' applied.
   Note: "Bulletin 023997 - Business Communication Manager (BCM) 4.0 Backup and Restore" has been 
   issued to provide further information.

   Due to a suspected flaw in Java, the Element Manager may display an 
   incorrect time during a two-hour window surrounding the time transition from 
   NZDT to NZST. The time on the BCM and displayed on sets is correct at all times. 
   Note: Do not manually correct the Element Manager's time setting during this 
   two-hour window as it may result in incorrect times on the BCM.

   Dect sets will not be able to identify incoming calls during One Button Text (OBT) Sessions
   When the DECT set is in an OBT session, it will not be able to identify an incoming call.
   The user can check the Call Log to find any missed calls during the OBT session.
   Workaround: None.
   Q01716365

   Element Manager fails to auto refresh an OBT feature code entry if the destination DN 
   field is not modified.  If the user adds or modifies only the text message field of the OBT,
   then the entry will not be refreshed automatically. 
   Workaround: Do a manual refresh.
   Q01741732

   The static IP address pool in Element Manager under 
   Configuration->Resources->Network Interfaces-> Dial-in parameters ->Static IP address pool 
   needs to be re-assigned after applying the update (BCM.R400.120-ISDN). Before 
   applying the update, ISDN interfaces need to be deleted and then created after applying 
   the update.

Other:
- The ModemCC will be restarted. If the update is applied via the modem, the modem
  will disconnect. Voice Mail, Contact Centre and System Set Based Administration (F9*8)
  will also be restarted.
- If the Soft Modem is failing to properly answer and connect to a call that is involved in
  TAT scenario, the latest ModemCC update is also required (with this one) to properly work.
- The ModemCC will be restarted. If the update is applied via the modem, the modem
  will disconnect.
- The IVRProviderAgent will be restarted. If the Element Manager is opened to the IVR 
  Advanced Configuration or IVR Advance Commands panel, switching to another panel 
  and coming back to the IVR Advanced Configuration or IVR Advanced Commands panel 
  will show the fixes.
- The IVR Engine will also be restarted. This will prevent the IVR applications from 
  running while the update is being installed.
- The DiaLogger and SysLogListener applications will also be restarted. Some alarms 
  may be missed while the update is applied

Update Removable: No


Software Update BCM.R400.215-CORE Description:
----------------------------------------------

- Can't restore backup since core update 184 installed
  After application of update 184, a coretel backup taken from an earlier 
  BCM 4.0 release cannot be successfully restored.
  Q01884362

- Echo on analog DID trunks (ADID4)
  Echo can be heard during the first 10 seconds of a call for analog DID trunks 
  on some Central Office exchanges. This issue is addressed in this update.
  Q01760892-02

- Calls with no CLID cannot connect to BCM50 via H323
  When a person with no CLID feature (e.g. a cell phone) calls the BCM, this call 
  does not tandem via H.323 to a second BCM. Incoming calls with CLID tandem
  successfully.
  Q01883856, Q01879253, Q01886058, Q01886077

- Calls using the SIP Trunks not reverting to the Prime Set when WAN Link fails
  Calls that route across the Virtual Trunk using SIP, are not being redirected to the 
  Prime Set when the WLAN link is down.
  Q01833351-02


Software Update BCM.R400.212-CTI Description:
------------------------------------------------
- during a special TAT scenario when a user hangs up, the CTI Tracker 
  instance was not getting killed. This tracker instance was interfering
  in other calls/features, due to which Voicemail was becoming unresponsive.
  This update corrects the problem by making CTI process the release 
  message sent by the Core, which leads to the killing of the Tracker instance.
  Q01840996


Software Update BCM.R400.211-APACHE Description:
------------------------------------------------
- Cross Site Scripting (XSS) or Denial of Service (DoS) vulnerabilities in Apache
  Security Vulnerabilities in the Apache 1.3 and 2.0 Web Server Daemon and "mod_status" 
  Module May Lead to Cross Site Scripting (XSS) or Denial of Service (DoS). 
  More Info: http://securitytracker.com/alerts/2008/Jan/1019154.html
  Q01814487-03


Software Update BCM.R400.208-IVR Description:
---------------------------------------------

- Uploading a prompt file appeared to fail
  This occurred when there were already many prompts installed on a system.
  Q01858093


Software Update BCM.R400.207-IPTEL Description:
-----------------------------------------------

- Redirecting H323 calls with no CLID do not complete 
  The issue has been that the VoIP Gateway does not look at the RGN number once the 
  calling number is empty, regardless of whether the "Redirect OLI" setting is enabled or 
  not. In this case if the destination network requires a CallingPartyNumber, then the call 
  will not complete successfully.
  Q01827221-01

- Intermittent no speech path on H323 calls from a BCM set that Forward No Answer to a CS1K CallPilot 
  It was found that the MGS was queuing open media path requests too long, so that if the 
  CS1K initiated a quick media path redirect while the original request was still being 
  processed, a transport mismatch error could occur, resulting in no speech path.
  Q01774840


Software Update BCM.R400.205-ISDN Description:
----------------------------------------------

- Kernel crashes when the system goes for an auto-reboot after applying
  the BCM.R400.SU.System.006 update. Problem occurred due to improper termination 
  of ipppd processes while applying the ISDN Bundling update (BCM.R400.120-ISDN). 
  This update resolves the issue.
  Q01814627


Software Update BCM.R400.204-CDR Description:
---------------------------------------------

- CDR reports incorrect records for Hunt groups when Manual DND 
  (Feature 85) is programmed on the sets of HG members.
  This update resolves this issue by changing CDR to support manual
  DND being programmed on HG members.
  Q01877898


Software Update BCM.R400.203-UTPS Description:
----------------------------------------------

- The LCD on the KEM modules going blank intermittently
  The following latest firmware is being included in the BCM 4.0 build which 
  fixes the 1110 series expansion module's issues.
  0623C4L.bin - for 1110 (Next Gen) IP Phone
  0624C4L.bin - for 1120 (Next Gen) IP Phone
  0625C4L.bin - for 1140 (Next Gen) IP Phone
  Q01877250


Software Update BCM.R400.202-SCD Description:
---------------------------------------------

- The CallHistory.YYYYMM.txt files are filling up with errors at the rate 
  of 8 lines per second and consuming on average 1GB of disk space per month. 
  This happens on systems with IVR config Data loaded on them, that are not
  actively using/running the IVR application.  This fix addresses the issue.
  Q01788956


Software Update BCM.R400.201-CTI Description:
---------------------------------------------

- The IVR CallHistory.YYYYMM.txt files fill up with errors at the rate 
  of 8 lines per second, consuming on average 1GB of disk space per month. 
  This happens on systems with IVR config data loaded on them but which lack
  an IVR keycode.  
  This fix, in conjunction with BCM.R400.202-SCD, will resolve this issue. 
  Installing this update without BCM.R400.202-SCD creates no side effect. 
  Installing BCM.R400.202-SCD without installing this update will cause 
  backups to fail for systems without an IVR key code. 
  Q01788956


Software Update BCM.R400.199-VOICEMAIL Description:
---------------------------------------------------

- Voicemail crashes with event error codes 10002 and 10230
  Two agents are on two different calls. One of them transfers their call to the other 
  agent. Now the agent who has two calls holds one of them,  disconnects the other 
  and invokes F906 (supervisor help), which leads to a voicemail crash. This update 
  resolves the issue by checking for this particular scenario and display a message 
  on the set.
  Q01848085

- Auto Park & Page feature does not work when customers call in.
  The customer is not able to connect to any of the departments using Auto
  Park & Page feature. During system boot up, the Auto Park & Page feature
  from Call Pilot Manager was not getting registered, resulting in the user
  getting the response "inactive feature" when invoking Auto Park & Page.
  This update resolves the issue by increasing retry attempts in registration
  of the Auto Park & Page feature with the voicemail application.
  Q01833389


Software Update BCM.R400.198-OAM Description:
---------------------------------------------

- Remote Scope Read Only
  At the Configuration -> Data Services-> DHCP Server -> Subnets -> Add button, 
  the "Subnet Mask" field was Read Only.
  Q01868897

- Help link is wrong for 'ignore in-band DTMF in RTP' 
  At the Configuration -> Resources -> Telephony Resources -> IP Trunk Setting,
  when hovering over the "Ignore in-band DTMF in RTP" option, the help text was 
  displayed with the wrong messaging. The message is corrected.
  Q01831506

- EM Version inconsistency
  Different EM releases follow different version naming rules such that an 
  EM version from one release is not comparable with the version number of 
  another release, even though the frameworks are the same. To resolve the 
  issue, a new version naming is defined and is being applied for all 
  releases such that the EM version for different releases become comparable. 
  Consequently, the Help screen is updated to show the EM version.
  Q01814447


Software Update BCM.R400.195-DHCP-PROVIDER Description:
-------------------------------------------------------

- DHCP lease information is not displaying in Element Manager on BCM 4.0.
  This fix addresses the issue.
  Q01852586


Software Update BCM.R400.187-IVR Description:
---------------------------------------------

- Trying to create the VASDBlist using dbman from the Advanced Command
  IVR panel fails.
  Q01849935


Software Update BCM.R400.193-IVR-RE-ENABLE Description:
-------------------------------------------------------

- Unable to perform Backups after applying BCM.R400.SU.System.010-200804
  Systems that have applied SU.System.010, and which do not have IVR
  keycodes installed, will be unable to perform backups. The backup
  processes attempts to stop and re-start IVR; this would fail because
  the SU disabled IVR processes on systems without keycodes. This update enables
  these processes to restart. 
  Q01864658


Software Update BCM.R400.192-CTI Description:
---------------------------------------------

- CTIServer crashes in a TAT call scenario
  CTIServer crashes if two simultaneous TAT requests are sent by Core to CTI 
  for the same trunks in TAT-enabled tandem systems. This update corrects the 
  problem by rejecting one of the TAT request if already one TAT is in process
  Q01847192


Software Update BCM.R400.191-UTPS Description:
----------------------------------------------

- Single IP Phone locks up after reboot
  Due to a port mismatch the DN of the IP set gets assigned to Co-loop.
  During restart of an IP set, UTPS was using LAD and STNX  information 
  received from Core through the "query PDN Response" FUMP without 
  checking for hardware ID and Set Type. This is now fixed by verifying 
  the hardware ID and the Set type in the FUMP message.
  This is validated against the expected Hardware ID and the Set type. 
  Q01801665


Software Update BCM.R400.190-DOORPHONE Description:
---------------------------------------------------

- Call from doorphone only rings once when one of the Hunt Group sets is busy or uses DND
  If a Hunt Group is called, a reject event may occur if ANY of the target 
  phones that are being rung are busy. This causes the call from a doorphone 
  to be abandoned, and hence none of the other phones in the hunt group get 
  an opportunity to answer it. To correct this, only disconnect the call 
  attempt when it reaches the timeout period i.e. only allow this disconnect 
  shortcut to paging if the user is dialing a single phone.
  Q01779415


Software Update BCM.R400.189-VOICEMAIL Description:
---------------------------------------------------

- Unable to service Doorphone call when the call is routed to VM
  When a doorphone call goes to voicemail, the doorphone hears greetings, 
  and is solicited to record a message or provide key input, neither of which are 
  useable functions by doorphone. The acquire action of VM prevents the 
  doorphone software from disconnecting in this situation. This update 
  resolves the issue by disconnecting the call when a doorphone call goes to 
  voicemail.
  Q01845653

- Mis-routing of Calls in CallPilot using CCR & Call Center
  Despite the user pressing correct digits, Auto Attendant transfers an external call 
  to skillset different  from the expected one.
  This update corrects the problem by resolving a timing issue.
  Q01826967

- Feature F970 should be registered only if APPP keycode is applied.
  F970 feature code gets registered with the core irrespective of the APPP keycode 
  status. This update puts a check to see whether an APPP 
  keycode is present before F970 is registered.
  Q01816244-02

- Changes for APPP and Intelligent Contact Center (ICC) Keycode issue
  When the APPPack keycodes are enabled, the Contact Center Functionalities 
  may not work as designed. This update addresses this anomaly.
  Q01815622-02 

- RCC 2.5 cannot connect to DB and invalid XML
  Call Center received a line ID in place of a DN from the middleware. This caused
  the XML validation against the schema to fail, since DNs are specified in the 
  schema to be numerical, whereas the line ID is alphanumeric. Now this is
  detected and a numerical value is assigned to the DN.
  Q01786289-02

- APPP symbol kiosk URL allows paging for null station name
  Symbol kiosk allows paging even when the URL specifies a null station name.
  This update corrects the problem by introducing an extra check for the 
  null station name.
  Q01829664-01

- Localization of the message "Please Wait" for OBP fails.
  In the One Button Page feature, when the primary language is changed to other than
  English, the "Please Wait" prompt fails to appear in the respective language 
  selected in the CallPilot Manager. This update corrects the issue by displaying 
  the prompts for all selected languages.
  Q01830142-01


Software Update BCM.R400.188-CDR Description:
---------------------------------------------

- CDR shows incorrect records for Hunt group scenario when DND on Busy is enabled.
  This update resolves this issue of reporting records in CDR correctly by changing 
  the CDR design to support when DND on Busy is enabled.
  Q01841781 


Software Update BCM.R400.186-IPTEL Description:
-----------------------------------------------

- SIP Call from CS2000 to BCM cannot be forwarded to CallPilot on CS1000 5.0
  In this scenario, it was found that the BCM could not handle receiving a 
  SIP 183 followed by a SIP UPDATE, both with media parameters specified, 
  and so did not handle the media redirect promptly.
  Q01779930

- SIP Call failure from BCM50 (UDP) to CS1000 (TCP/TLS)
  SIP Calls from the BCM to the CS1K were failing when the CS1K was 
  configured to use TCP/TLS.  This was found to be a result of the BCM 
  failing to send a SIP PRACK out in response to CS1K's SIP 180 (100rel) 
  message.
  Q01778047-01

- Extra diagnostics around MPS initialization
  Additional logging was added around the MPS initialization procedures in 
  order to show in the logs if these procedures had completed correctly.
  Q01661706

- No Speech Path for BCM H323 CFNA from CS1000 5.0 set to a CS1000 Call Pilot
  It was found that there was an intermittent no speech path issue for 
  H323 calls to a CS1000 5.0 set that was CFNA to a CS1000 Call Pilot.  
  This was a result of the BCM not resuming speech path once the CS1000 
  attempted to redirect the media path to the Call Pilot.
  Q01833478

- BCM did not support SIP Re-INVITE with no SDP
  SIP Re-INVITE with no SDP would be rejected by BCM with SIP 415 
  Unsupported Media. Therefore, SIP calls between BCM and CS1000 
  dropped when CS1000 attempted to redirect the calls. Changes were 
  made to allow BCM to support the Re-INVITE with no SDP.
  Q01833443


Software Update BCM.R400.180-Dialogger Description:
---------------------------------------------------

- Alarm/event 247 has been modified to be more specific. 
  This is a request to have event/alarm 247 include more specific 
  information on the trouble being reported. This will have 
  additional parameters that could isolate the trouble and allow 
  customers to troubleshoot and clear the issue themselves.
  Q01801837


Software Update BCM.R400.179-CTE Description:
---------------------------------------------

- Telephony applications reacting to and/or controlling incorrect devices 
  CTE Applications that monitor or control BCM devices are receiving  
  inconsistent call progress events for different devices. This update
  will resolve the problem.  
  Q01824811


Software Update BCM.R400.177-CTI Description:
---------------------------------------------

- Callpilot locks up Intermittently and drops the calls directed to AA/call centre 
  Callcenter freezes intermittently. Auto Attendant get dropped 
  when the incoming calls are directed toward the callcenter.  
  At this time, voicemail features like "open", "transfer", and 
  "leave message" are still active. The Callcenter agents who have
  already logged in would be active. The calls in the queue stay 
  in the queue, however new calls don't get through.
  This update corrects the memory leak issue that's causing this problem.
  Q01773886-01 


Software Update BCM.R400.175-GLIBC Description:
-----------------------------------------------

- Changes to Australian Daylight Saving April 2008
  Australian Eastern (New South Wales, Victoria, Australia Capital 
  Territory and Tasmania) and Central (South Australia) time zones 
  will extend daylight saving and also harmonise start and end times 
  commencing April 2008. From April 2008, daylight saving will end 
  on the first Sunday in April and recommence on the first Sunday in
  October in all states.
  Argentina adopted DST on Dec 30, 2007. This update has DST ending 
  the third Sunday of March, and then beginning again the first 
  Sunday in October.
  Q01817208


Software Update BCM.R400.174-MSC Description:
---------------------------------------------

- MT_RTP Crash fix
  IP trunks were failing because the BCM was rebooting intermittently. 
  The system was rebooting due to a crash in media transport driver. 
  This fix avoids such crashes.
  Q01790489

- MSC Lockup Fix
  VoIP calls were failing intermittently as one of the threads in MscService 
  was getting locked up. This was because of a race condition between 
  MscService and DSP while the Voice DSP task was being configured. 
  This fix corrects this problem.
  Q01580636-02

- ISDN PRI back-to-back connection on BCM4.0 systems was failing intermittently. 
  When a bundled ISDN call was connected and disconnected repeatedly, the 
  call was failing intermittently. This was due to two reasons, the first was 
  due to a task context mismatch in the MSC, the LCP packets were not 
  reaching the correct destination; and the second was the WAN task creation 
  was failing. The fix corrects these issues.
  Q01651355
  Q01651355-01

- Modifying the ds30 log statements in BCM4.0
  Some of the newly added log messages in Msc were not in line with ds30 
  logging practices. These messages are used in manufacturing while 
  conducting the sanity tests on the MSC cards. The fix modifies the log 
  statements as per the ds30 standard. 
  Q01743627 


Software Update BCM.R400.171-IVR Description:
---------------------------------------------

- IVR lines may fail to answer calls after a caller hangs up with prompts playing.
  If a caller hangs up while the IVR is speaking prompts, the IVR 
  application may fail to answer any subsequent incoming calls. 
  The problem occurs when the application has two or more Speak 
  blocks in succession without the wait boxes checked (or a Speak 
  block and a Select block with a prompt). If the prompts are 
  still playing when the caller hangs up, and the application is 
  written to go directly to an Answer block for the next call
  without recycling, then the line may fail to receive any more 
  incoming calls. The bim line status will show the line is not 
  put in ready (rdy) state to take another call. This is only for
  applications that do not recycle before returning to the Answer 
  block. In the more typical scenario, an application will run to 
  the end and recycle after a caller hangs up. The unplayed prompts
  (i.e. the Speak blocks) are aborted when the application restarts.  
  This update causes the unplayed prompts to be aborted at the time 
  the caller hangs up, which readies the line to execute another 
  Answer block.
  Q01809036


Software Update BCM.R400.170-RECOVERY Description:
--------------------------------------------------

- In rare circumstances, the Backup or Restore operations may encounter inadequate 
  disk space. When this condition occurs, any transient files created by an 
  interrupted Backup or Restore are removed from the disk.
  Q01802537

- Backup file does not contain installed update history.
  The tar files produced by backups do not contain the history of
  updates that were applied to the system from the initial power up.
  This updates makes the history file available in the log file
  so that support personnel can easily identify the state of systems
  they are supporting.
  The "softwareupdates.log" can be obtained from the Log File by 
  navigating to 'systemInformation.tar.gz'. 
  Q01479103


Software Update BCM.R400.169-VOICEMAIL Description:
---------------------------------------------------

- Agents stop receiving calls after wrap time
  This has been fixed by clearing all the agent shared data if an activity 
  code feature is activated for that agent.
  Q01449845-01

- Unread Skillset Message appearing in RT (Real Time) after listening 
  to VM (VoiceMail)
  The problem is that Contact Center is not updating the skillset message
  counter when the message has been read and expunged. This has been
  fixed by updating the message counter in Contact Center once voicemail
  sends the expunge message.
  Q01693848

- CallCenter: XML does not show F905 when there is a F906 Notified status
  Due to limitations in the reporting architecture, we may only report on one 
  active agent state at a time.  There is an issue where a Supervisor misses a
  (F906) Supervisor Help request, then releases the notification on the telset
  without checking the messages.  This creates a constant F906 notification
  flag for that supervisor until they manually enter F906 and clear all 
  notifications.  This is the feature intent, however when the supervisor is 
  in the state with a notification pending and enters (F905) Silent 
  Monitoring, the XML will report the Supervisor as handling a F906 request, 
  NOT doing a F905 Silent Monitor session. The fix for this CR is to suppress
  the F906 status when the supervisor enters F905, thus the XML will properly
  display the supervisor's active state.
  Q01384700
   
- The Symbol Kiosk output is not customer friendly.
  This issue has been fixed by displaying only the text messages 
  "Help Requested" or "Help Cancelled", when the user requests 
  the help page from Internet Explorer.
  Q01757155-01


Software Update BCM.R400.168-UTPS Description:
----------------------------------------------

- Issues found during Designer Testing of the Expansion Module for 
  IP Phone 1100 series Hardware.
  Issues were found while testing with the Expansion Module for 
  IP Phone 1100 series hardware. There was a mismatch in the Expansion 
  Module for IP Phone 1100 series type. Also, issues with the misalignment
  of the KEM labels are fixed. 
  Expansion Module for IP Phone 1100 series is now supported with BCM4.0
  Q01578700-03

- Support for IP Phone 1110 Sets in BCM4.0
  A new firmware file was added in the BCM4.0 build to support IP Phone 1110.
  Q01764255

- Inclusion of new firmware files for 1110, 1120e, 1140e, 2007, 
  2002 and 2004 Phase 2 IP sets.
  Added the latest versions of firmware files for 1110 (0623C4D),
  1120e(0624C3G), 1140e(0625C3G), 2007(0621C3N), 2002 and 2004
  Phase 2 Sets (0604DAX). LLDP is supported on 0604DAX.
  Q01779467


Software Update BCM.R400.166-SCD Description:
---------------------------------------------

- NTP daemon's log file "filegen" is not currently managed by log rotate and
  the file could grow indefinitely. When managed by logrotate, a size limit 
  is enforced.
  Q01449728-02

- Unable to apply updates due to Disk space exhaustion.
  The /var/log partition gets filled up completely due to kernel crashes and 
  other large files. This partition will be cleaned up as necessary.
  This fix addresses the issue.
  Q01722625

- The One Button Text "feature inactive"
  SCD failed to start the One Button Text process because of some missing 
  startup scripts. 
  Q01794340

- Unable to apply updates due to Disk space exhaustion.
  Binary files in /var/log are removed now when free disk space becomes low.
  Q01803712
   
   
Software Update BCM.R400.165-CORE Description:
----------------------------------------------

- Telephone set time did not change on DST change.
  After applying the update the telephone set time will reflect
  the change in DST.
  Q01776352

- Unable to make any H.323 calls to the BCM or Tandem through the BCM
  Tandem calls between PRI and IP fail with "Unallocated Number."
  Q01798621

- No dial tone for second call on i2033 when interacting with LNR         
  When you lift the handset of basic set and do F5 and then put the 
  call on hold then you will get dial tone. But when you do F5 without
  lifting the handset and then put the call on hold then dial tone
  won't be given.
  Q01803622

- Cannot release the call when receiving the call while KEM is booting
  If a set receives a call while its KEM is booting up, that call cannot be
  released after KEM boot up is complete.
  Q01745049-01

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

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

- Call not clearing after handsfree call from i2001
  On an i2001, when a call is initiated in handsfree mode, once
  the called party has answered, the caller then lifts the handset
  to speak. After the call is completed, the caller replaces the handset
  back in the cradle, but the call is not clearing. The display
  is shows the called party number, for both
  internal and external calls. To clear the call, the caller has
  to press the release key.
  Q01796293-01

- Call Diversion (Partial Rerouting) not Working on T-T User on BRIM 
  ETSI Call Diversion (partial rerouting) does not work when the T-T 
  user setting is configured on a BRI module. It works fine when the 
  S-T user setting is configured.
  Q01788089-02

- Noticeable Stuttered ring Tone on 1200 series on intercom calls 
  while doing a transfer.
  Stuttered ringback tone is heard on 1100 and 1200 series
  IP sets during call transfers.
  Q01742086-01
 
  
Software Update BCM.R400.SU.System.008-200802 Description:
----------------------------------------------------------

- Element Manager cannot access BCM from user PCs - gets MOF error from Java
  If an EM is freshly installed from a BCM that was updated by 
  BCM.R400.SU.System.006 and BCM.R400.SU.Desktop.004, 
  the EM is unable to connect to the BCM. After downloading 
  the cartridge, it displays an error message about not be able 
  to open MOF directory.
  Q01824960


Software Update BCM.R400.167-NCGLKERNEL Description:
----------------------------------------------------

- BCM 4.0 software does not supports multiple USB
  flash storage (thumb) drives to be mounted without
  rebooting the system. There is no issue found when
  the same USB drive is used, however if a different
  one is used then the system fails to correctly
  mount this USB drive, and a reboot is required to
  mount the drive as expected.  

  This kernel update addresses this issue and allows
  mounting a USB drive, then unmounting it and 
  mounting another without rebooting.
  Q01773831


Software Update BCM.R400.163-QOS Description:
---------------------------------------------

- /var/log is at 100% capacity
  BCM_DataInterfacesProviderAgent.log file is not rotated properly, as a
  result it can grow until it takes up all free space on the /var/log partition. 
  This update fixes the issue.
  Q01765748


Software Update BCM.R400.161-CDR Description:
---------------------------------------------

- CDR reports the CLID for incoming calls Intermittently due to active registration
  of CLID by the other software or equipment. 
  This update resolves the issue of recording CLID Intermittently by changing the CDR
  design to support both active and Passive registration of CLID.  
  Q01738969
   
   
Software Update BCM.R400.160-SoftwareManagement Description:
------------------------------------------------------------

- The transfer of software is optimized when "My Computer" retrieval 
  option is used from Element Manager. Only the necessary software 
  packages in the update will be downloaded to the BCM instead of all 
  the software packages.
  Q01791291-01

- Automatic backup and restore of RPM Database
  The RPM database on BCM 4.0 can become corrupted, preventing users from
  logging in with Element Manager or applying updates. This update delivers
  enhancements for RPM Database robustness.
  Q01592770-01
   
   
Software Update BCM.R400.159-VOICEMAIL Description:
---------------------------------------------------

- High CPU spikes
  If a Desktop Messaging client is configured for Auto Send/Receive, and a new
  fax or voice message is delivered to that client's mailbox, resulting in more 
  than 500 messages in that mailbox, CPU usage spikes to 100%.
  This update will resolve the problem.
  Q01762747
 
- Call Sender shows corrupted CLID for German profile
  This update increases the Local Number Length from 7 digits to 15 digits for 
  German profile so that CallPilot can correctly determine the dialable DN for 
  Call Sender feature.
  Q01789495


Software Update BCM.R400.158-CORE Description:
----------------------------------------------

- Element Manager shows incorrect OLI digit length
  When one increased the received digit length, the OLI field length did not increase.
  Q01772589

- Lamp indication for M7324 is lost at keys display
  After entering into SBA (Set Base Administration), navigation icons on an M7324 are not 
  displayed. Programming features on the same set with F*3 will not show icons on
  the set when feature is used.
  Incoming call line appearances on the set won't show BLF icons on the set.
  Q01762357

- 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

- E&M T1 stops accepting calls
  Under high traffic conditions, T1 E&M trunks may stop accepting
  calls from the network. The root cause was identified as an error
  in the coretel DSP code which prevents detection of DTMF digits.
  Q01759578
  Q01743932

- Feature **option is unavailable
  This update allows a single TDM set to boot up on SRG systems to allow
  access to F **OPTION. Access to F **OPTION allows the
  technician to select cadences and disconnect supervision options for
  various markets.
  Q01782786

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

   
Software Update BCM.R400.153-BTRACE Description:
------------------------------------------------

- Changes were applied to the BTRACE application setup which will change the 
  security policies when the BTRACE keycode is active.
  Q01458934.

- btraceserver will not start
  Q01781603 


Software Update BCM.R400.150-GAP Description:
---------------------------------------------

- This update adds a privilege to the BCM called SetProgramming. The
  SetProgramming privilege will have access to the following Element
  Manager Screens:
     Welcome
     Current User
     Active Sets: Line Access, Capabilities and Preferences, Restrictions
     Active Applications DN: Line Access, Capabilities and Preferences, Restrictions
     Inactive DNs: Line Access, Capabilities and Preferences, Restrictions
     All DNs: Line Access, Capabilities and Preferences, Restrictions
  Q01788687-01

- IP Set type 1110 support in Element Manager
  Q01764255-01

- Issue with Element Manager installed on a French-enabled PC
  When starting the EM installed on a French-enabled PC (regional settings
  set to French Canada or any other French language region), some incorrect
  text is displayed ("Panneau de navigation d&#65533;&#65533;?l&#65533;&#65533;ment").
  This update ensures that French text will be properly presented in the EM.
  Q01535611

- Button mapping is incorrect for M7310 graphical representation
  When programming buttons on an M7310 set with the Element Manager,
  the buttons were incorrectly numbered. The button #11 was missing and
  there was a non-functional button numbered 35. This update adds button
  #11 and deletes button #35.
  Q01725188


Software Update BCM.R400.149-DSPFIRMWARE Description:
-----------------------------------------------------

- Short "beeps" on IP sets coming from the BCM
  The CED's signal power and signal-to-noise ratio (talk-off) were increased to prevent 
  misdetections of CED.  
  Q01640437

- T.38 Fax Interoperation with Xerox WorkCenterPro added
  Added support for interoperation with fax machines requiring echo protect tone for 
  both CallPilot and T.38. 
  Q01658598


Software Update BCM.R400.148-CORE Description:
----------------------------------------------

- GATI: Auto Calibration issue with 800 ohms Transition feature
  This update implements an 800 ohm impedance transition 
  between the onhook (high impedance) and offhook (50 ohms impedance) 
  states for 300 ms on analog trunk calls. This extra transition 
  protects the analog front end circuitry from shorting under
  improper ring trip conditions.
  Q01644162-02

- Australia Profile - ROI call drop issue.
  In ROI mode, calls are getting dropped intermittently in some sites
  in Australia. This issue is fixed in both GATM-Ver1 and GATM-Ver2
  firmwares.
  Q01663473-01
  Q01470485-01
        
- Adaptive Line Tuning Support for GATM-Ver2.
  Adaptive Line Tuning support is added in GATM-Ver2 firmware. This is to
  resolve the echo issues reported in multiple sites in different markets.
  This new line tuning algorithm calculates the Filter Hybrid coefficients
  dynamically during boot-up based on the CO line conditions.
  GATM Adaptive Line tuning will only be supported on GATMv2 hardware and 
  later vintages of GATM and combinations modules, which include the 
  following top level codes:
  Gx16 MBMs (NT5B42AAABE5/NT5B42AAACE5) & 
  GATM 4/8 (NT5B44BAABE5/NT5BAAABE5).
  Q01755111-02 
  Q01644162-02

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


Software Update BCM.R400.147-CTI Description:
---------------------------------------------

- Busy CCR Tree intermittently quits taking calls
  Incoming calls to a CCR Tree stop being answered. The calling party
  sometimes receives an audible message "Can't continue. Please try
  again later" or the call simply quits without any message. When this
  occurs, the administrator who is recording in the same mailbox is
  terminated with the error message "Cannot continue" on the set display,
  and the mailbox becomes inaccessible. This is caused by the voice
  file of a mailbox being deleted when it is simultaneously being accessed
  for both read and write operations. This update prevents the deleting of
  the voice file when it is being accessed for both read and write access.
  Q01687919


Software Update BCM.R400.146-BIND Description:
----------------------------------------------

- BCM 4.0 uses BIND version 9.3.1 as a proxy DNS cache and therefore is 
  potentially vulnerable to the CVE-2007-2926.
  This update includes BIND version 9.4.1-P1 to fix the issue.
  Q01750968


Software Update BCM.R400.144-OPENWBEM Description:
--------------------------------------------------

- Cannot access system with Element Manager 
  Unable to login to Element Manager. Logins get stuck at "resolving cartridge identifier"
  Webpage, Ping, and SSH accesses work.
  Q01751044
   
   
Software Update BCM.R400.143-CORE Description:
----------------------------------------------

- LEDs inoperative on M7324 after applying Core update
  LCDs on M7324 sets will not illuminate for active calls. 
  Q01769222

BCM.R400.134-CORE
------------------

- After applying the CoreTel update BCM.R400.109-CORE, set time 
is five minutes behind system time, even when Date and Time 
Source in Element Manager is set to either Manual or Trunk .
Q01723283

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

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

- CoreTel restarts when faxes a re sent at a very high rate. This 
issue is observed when a third party ISDN FAX card is used.
Q01471821-01

- In the German market profile, if a supervisor invokes the JOIN soft key 
in a silent monitor session, the supervisor will not get voice path. This issue is 
observed if the silent monitor setting is No.
Q01672789

- In a particular multi-party conference scenario, CoreTel restarts.
If a three-party conference is established due to Call recording feature
(F989) and this three-party conference converts into a multi-party conference,
CoreTel restarts.
Q01731350

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

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

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

- 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-04

BCM.R400.122-CORE
-----------------

- Copy and Paste of Analog Trunk data not happening thru EM
When analog trunk data is copied to a different trunk using Element
Manager, the required information is not copied.
Q01637740

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

- Night ringing service stops working
Night service ringing will stop functioning if night service 
configuration end time is different for different weekdays.
Q01621516-01

- Silent monitor does not function in UK market profile.
A loud tone is heard on the Agent supervisor set when the silent
monitor feature code is invoked. When the supervisor presses the 
"join" soft key, the monitored parties also hear the tone. This
occurs only in the UK market profile.
Q01618502

- Autodial lights do not work with i2004 phones
On i2004 phones, the Autodial icon does not illuminate when
the target set is off hook
Q01530111

- Pulse Dialing does not work for the Brazil Market profile.
Pulse Dialing on analog trunks does not work for the Brazil Market
profile with a GATM1 module.
Q01612145

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


Software Update BCM.R400.141-VOICEMAIL Description:
---------------------------------------------------

- Voicemail features unavailable
  Symptom:  Access to the voicemail features such as F981, F983 etc. indicates
  "exiting the system, good bye" and the CallPilot Manager shows the Available
  Subscriber Mailboxes as negative when trying to add a mailbox. The problem
  was due to voicemail being unable to get licenses from the CFS Server.
  Q01757636
  Q01678118


Software Update BCM.R400.138-IPTEL Description:
-----------------------------------------------

- FEPS UDP thread corruption upon receiving non-MCDN packets on port 15000
  The thread that processes UDP packets received by FEPS made the assumption that any packets
  received on port 15000 contained MCDN data.  Upon receiving non-MCDN packets on this port,
  memory corruption would then occur causing a core file to be generated by that thread.
  Q01753800-01


Software Update BCM.R400.137-APPP Description:
----------------------------------------------

This update introduces the following new feature.
 
- Advanced Paging Productivity Pack (APPP)
  The APPP provides the following four capabilities

  One button page - an extension of the existing one button park and page.
  This feature will perform a page when a pre-programmed feature key is 
  pressed even if no active call is present at the set. An example would be 
  "Cashier in Aisle 1 needs change").

  One button Text Message  - Allows a text message to be sent 
  (and acknowledged) to a fixed or wireless (Dect or Spectralink) phone. 
  An example would be "Angry customer at Aisle 1"). 

  Customer Assistance Box - This feature allows a retail end customer to 
  walk up to a customer assistance device in a store and press a large 
  "Please help" button. The system will then perform a periodic page 
  such as "Customer in electronics requires help".  When a sales assistant 
  arrives he/she presses a different button to cancel any further pages. 
  The assistance request and the required time to answer the page is 
  recorded in a CSV file for later reporting by a custom CDR application.

  Scheduled Paging - system will provide a scheduled specific page 
  (eg. "the store is about to close").

  Administration of the above is performed via Element Manager or NCM. 
  All four features are enabled by a single binary third party keycode.

- Vista compatibility for Element Manager
  This update includes fixes to make the Element Manager Vista compatible.

The following issues are addressed.

- Critical alarms appear when APPP update is installed and BCM rebooted.
  The following alarms appear on every reboot of the BCM after the update 
  BCM.R400.128.APPP-1.6-1.1 is installed - Alarm ID:31079 and Alarm ID:31079.
  These alarms are false. They are log info messages and mistakenly tagged as 
  alarms. This update addresses the issue of false alarms.
  Q01750933


Software Update BCM.R400.136-VISTA Description:
-----------------------------------------------

- Service Manager table unordered in Vista
  This release includes an update to display the table in alphabetical order by service name.
  Q01620584-01

- DN Type of route no longer refreshed automatically
  When adding a route and setting the Pool to blocA, the DN type did not change automatically 
  to Private (from the default Public). 
  Q01716483 

- HW Inventory shows Retrieving for nonexistent MBMs
  With no expansion modules in the BCM, in the Hardware Inventory screen, for the MBM and MBM 
  Asset ID fields for the Expansion modules, EM showed "Retrieving..." instead of "N/A". 
  Q01721238 

- Scheduled Service Screen is slow to display with no progress bar
  When selecting the Scheduled Services screen in Telephony, the progress does not remain 
  until the data is displayed.
  Q01721248 

- Assign BlocF to VoIP Line001 Failed on Initial Attempt
  Configuring the QoS resulted in a condition where the attempt to set BlocF to active VoIP 
  Line001 failed. 
  Q01689671
 
- Tab SNMP Access Point is not present.
  The SNMP Access Point tab was not present in EM.
  Q01740068


Software Update BCM.R400.135-QOS Description:
---------------------------------------------

- BCM receives alarm 74004 intermittently
  This update closes an open socket to fix the issue.
  Q01734992


Software Update BCM.R400.127-CDR Description:
---------------------------------------------

- CDR live client cannot connect to BCM if LAN1 IP address is changed to 192.168.254.x
  This update resolves the issue of CDR live client connecting to the different
  IP addresses
  Q01682090 
  Q01586134

- Incorrect time display in CDRPullClient which displays transfer time as "24:10" 
  instead of 12:10pm.
  This update resolves the improper display of transfer time in CDR pull client.
  Q01686295-02


Software Update BCM.R400.126-DOORPHONE Description:
---------------------------------------------------

- Doorphones fail to operate after power cycle of the system
  This update addresses a timing issue where after a system reboot, the Doorphones 
  would not operate.
  Q01687897


Software Update BCM.R400.125-UTPS Description:
----------------------------------------------

- Spoofed Brute-Force UNISTIM message attack puts IP set in surveillance mode.
  This vulnerability is removed by using 30 bits for the initial reliable UDP 
  sequence number seeding, and good randomization in the phone and the BCM.
  Q01693925-02

- Spoofed UNISTIM reauthentication messages cause Denial-of-Service to IP Clients
  When there is an illegitimate request coming in from an unknown/fake (spoofed) 
  set which has the same IP address as that of an IP set which has already booted 
  up and is running, we send a NACK with the NextRxSequenceNumber. This will 
  ensure that there is no disruption to the connection of the legitimate IP set.
  Q01693840-02


Software Update BCM.R400.124-VOICEMAIL Description:
---------------------------------------------------

- SMTP Server down when recipient address length exceeds 64 characters
  In a scenario where a user is trying to send fax messages to multiple 
  recipients, if by mistake "," (comma) is used to separate recipients, the 
  SMTP server treats comma as PAUSE. As a result, if the recipient address 
  length exceeds 64 characters the SMTP server will crash. Changes have been made 
  in the SMTP server to check the recipient address length. A length
  of more than the 64 characters is handled gracefully such that 
  SMTP server is not shut down.
  Q01679753

- Voicemail reboots due to abnormal termination of request to a Fax service.
  Voicemail reboots continuously when the fax print request is terminated 
  abnormally or voicemail fails to add the fax files to the send list. 
  Problem was due to fax clean up routine being called a second time 
  with an invalid handle. This update corrects the problem by calling the fax 
  clean up routine only once with the valid handle.
  Q01668702-01

- VoiceMail doesn't handle all TAT scenarios.
  In some particular scenario during a TAT call, TAT request occurs just 
  before Voicemail is about to query the call data for the first call after
  answering the call. Since the original call is gone and new call is 
  already setup due to the TAT so query call for the first call fails and 
  voicemail terminates the call.
  Q01547678-02

- New error messages have been added to XML to aid in debugging.
  CallCenter erroneously reports failed database connections when the 
  connection to the database is intact.  The Call Center was unable to 
  determine the difference between no connection and no data in the 
  database.  CallCenter now returns more intelligent error messages when
  the database is empty.
  Q01574109

- Caller transferred to skillset via operator fails
  Under the following circumstances, when an operator transfers a caller
  to a skillset, it erroneously goes to the skillset mailbox.
  Details:  A caller calls Skillset X, there are no agents and an
            overflow rule exists which transfers to Skillset X's mailbox.
            Once in the mailbox, the caller presses "0" to reach the
            operator.  The Operator receives the call and transfers the 
            Caller to skillset Y which has all agents busy.  Instead of
            getting queued, the caller returns to Skillset X's mailbox
            where they again press "0" to reach the operator.  On the
            second attempt with the same circumstances, the call will 
            successfully queue in Skillset Y.
  The above scenario has been resolved so that the transfer from operator
  into Skillset Y will succeed on the first attempt regardless of all
  agents being busy or available.
  Q01679216


Software Update BCM.R400.123-CTI Description:
---------------------------------------------

- Voicemail terminates TAT calls in certain CVM scenarios.
  Callers who reach the Mailbox via CVM will receive dead air in some instances.
  In a particular scenario during a TAT call, the TAT request occurs just before 
  Voicemail queries the call data for the original call after it's answered. Since the 
  original call was terminated and the new call is already setup due to TAT, the 
  query for the original call fails and voicemail terminates the call altogether.
  Q01547678-05


Software Update BCM.R400.121-GLIBC Description:
-----------------------------------------------

- Daylight Saving Time for New Zealand
  On April 20, 2007, daylight saving time was introduced to New Zealand. 
  This fix allows BCM4.0 systems set to this time zone to correctly adjust 
  the system clock for DST. 
  Q01666356-03


Software Update BCM.R400.120-ISDN Description:
----------------------------------------------

- ISDN Bundling is not supported for Dial-In data calls over ISDN PRI/BRI.
  Q01394460

- Interfaces and Global Settings tabs are not shown in Element Manager under 
  NetworkInterfaces when ISDN or Modem interface is configured for auto
  dial out route and the interface is disabled. 
  Q01451325

- The ISDN interface is getting disconnected when there is no traffic and the 
  the connection is left over night. 
  Q01576640-01 

- Not able to connect ISDN interface intermittently. 
  Q01500749-01 

- Intermittently observed system reboot while trying to connect ISDN interface.
  Q01576640 

- Intermittent error when interface name is subset of other interface name
  Q01670571

- Several log files have been found to be in "deleted" state, but still taking
  up space on the logging partition. This can result in alarm 11201 "Hard 
  Drive near Capacity". This update resolves the issue of disk
  space exhaustion.
  Q01529404 
  Q01529404-02
 
- MSC FRU Replacement Fix
  autoCoreUpload failed to upload the appropriate core load after an MSC FRU
  was installed on the BCM. 
  Q01567391 
  Q01567391-01

- autoCoreUpload is enhanced to address the following issues
  a) During the system boot up, create the /nn/etc/core_var file if it doesn't
  exist and populate it with the appropriate core variant.
  b) Upload the core only if the core version running on MSC card is lower 
  than the DAT files version.
  Q01619917

- Halt script not updated for location of apccontrol directory
  The file /etc/rc.d/init.d/halt does not properly list the location of 
  apccontrol. It is located in /opt/etc/apcupsd/apccontrol and not 
  /etc/apcupsd/apccontrol. 
  Q01595933
  Q01595933-01

- autoCoreUpload is enhanced to support the uploading of core with 
  version "lablodx".
  Q01654779

- Increase monit configuration retries for securityservice application
  In BCM4.0, securityservice application is being monitored by monit.
  Monit will stop monitoring the securityservice if it fails 2 times in 3 
  retries. This needs to be increased to 40 times in 41 retry cycles.
  This is needed to ensure securityservice application is running 
  continuously even if application crashes. Monit will restart at this 
  point of time. 
  Q01689286

- Unable to connect to the BCM through Element Manager or Putty after 
  making multiple bundling calls from the PC due to authentication failure.
  Q01678221-01


Software Update BCM.R400.116-SCD Description:
---------------------------------------------

- Several log files have been found to be in "deleted" state, but still taking
  up space on the logging partition. This can result in alarm 11201 "Hard 
  Drive near Capacity" in the site. This update resolves the issue of disk
  space exhaustion.
  Q01529404-02
 
- MSC FRU Replacement Fix
  autoCoreUpload failed to upload the appropriate core load after an MSC FRU
  was installed on the BCM. This update corrects the problem.
  Q01567391-01

- autoCoreUpload is enhanced to address the following issues
   If a customer is running BCM 3.6 or 3.7 and has to replace their hard drive
   with a BCM 4.0 HD (for example because a new BCM 3.6 HD is no longer 
   available), the following changes ensure that the coretel executable will be
   automatically uploaded to the MSC:
  a) During the system boot up, create the /nn/etc/core_var file if it does not
     exist and populate it with the appropriate core variant.
     Note: If the core version on MSC is older than BCM 3.6, then the
     core_var file will be defaulted to "Auto".
  b) Upload the core only if the core version running on MSC card is lower 
     than the DAT files version.  Note: "Lower core versions" 
       refer to BCM 3.6 or BCM 3.7 core variants.  I.E. If a BCM 3.6 or
       BCM 3.7 hard drive is replaced with a 4.0 hard drive, the MSC
       Core will be automatically uploaded. 
  Q01619917

- Controlled shutdown initiated by UPS fails
  The BCM 4.0 system would not shut down gracefully under control of the UPS. 
  Instead, the BCM would remain running until the UPS power ran down. At this 
  point the BCM would shut down without stopping all the services. This fix 
  addresses this issue.
  Q01643300

- Halt script not updated for location of apccontrol directory
  The file /etc/rc.d/init.d/halt does not properly list the location of 
  apccontrol. It is located in /opt/etc/apcupsd/apccontrol and not 
  /etc/apcupsd/apccontrol. The fix addresses this issue.
  Q01595933-01

- NTP daemon's log file "filegen" is not currently managed by log rotate.
  This file could grow indefinitely. When managed by logrotate, a size limit 
  is enforced.
  Q01449728

- autoCoreUpload is enhanced to support the uploading of core with 
  version "lablodx".
  Q01654779


Software Update BCM.R400.115-RECOVERY Description:
--------------------------------------------------

- Backup and Restore impacts IVR
  When a restore operation is performed with only "CallPilot Configuration" selected, 
  the IVR service will never restart after the operation is completed.  
  Q01653193, Q01653944, Q01642270, Q01675889


Software Update BCM.R400.110-VOICEMAIL Description:
---------------------------------------------------

- Contact Center: Version Update
  Synopsis: Version update for the Contact Center component. 42.02.06.16
  Q01664526

  41.02.05.16
  ===========

- XML: Incorrect Data in Agent Capacity Report.
  Synopsis: If a single agent is logged into multiple skillsets in the contact
  center, a zero length interval can occur. This is not an error as for
  the fraction of a second the agent is unavailable to take calls in
  both skillsets while logging in. This does however skew the reports.
  New logic was introduced to mask zero length intervals from affecting
  reporting statistics.
  Q01237114-01

- Contact Center: Version Update
  Synopsis: Version update for the Contact Center component. 42.02.05.16
  Q01663455

  41.02.04.16
  ===========

- XML: Invalid Data Segments in data cause Contact Center to stop sending XML
  Synopsis: Due to invalid data segments, which can be spawned by numerous and
  rapid XML requests, the Contact Center stops sending data. The end user
  will experience the lack of updates in Reporting for Contact Center.
  Data is still being buffered into the Contact Center and if the update is
  applied soon enough, no data loss should occur. In addition to this,
  enhancements have been made to prevent the issue from occurring.
  Q01644599

- Contact Center: Version Update
  Synopsis: Version update for the Contact Center component. 42.02.04.16
  Q01657173

  41.02.03.16
  ===========

- Contact Center: Agents not being presented calls.
  Synopsis: An obscure race condition existed where Contact Center agents are
  available yet calls are not being triaged to them. This has been
  fixed in this version of Contact Center.
  Q01414570-01

- XML: XML stops sending when too many connections are open
  Synopsis: If there are too many connections to the Contact Center, XML
  requests start to time out. Degradation in system performance may also
  occur in this scenario. The solution was to implement prioritization
  where only the first reporting application to connect would receive XML.
  Q01416932

- XML: Real-Time XML reports agent status incorrectly while under heavy load
  Synopsis: In situations of extreme load exceeding the recommended capacities
  for Contact Center, the Real-Time XML becomes inaccurate. Robustness
  tweaks have been made to the XML enabling the BCM to run at maximum load
  with some additional room for activity spikes.
  Q01434749-01

- XML: Wallboards show calls in queue that have been answered
  Synopsis: Events can be received from CTI out of order, previously this
  confused the Contact Center and although the call would be triaged and
  answered, the XML would be wrong. Robustness tweaks have been made to
  accommodate for this sort of scenario.
  Q01436350-01

- Contact Center: Enable DNIS display on Telset UI
  Synopsis: The Call Center now supports DNIS display on the Telset UI.
  This feature is enabled via Call Pilot Manager on the Call
  Center General Properties page, under the existing CLID display
  options. The administrator may now enable DNIS to follow the
  CLID Display when a call is presented - when DNIS information
  is available from the CO.
  Q01501067-01

- Contact Center: Version Update
  Synopsis: Version update for the Contact Center component. 42.02.03.16
  Q01587796

  41.02.02.16
  ===========

- XML: Skillset missing in XML output
  Synopsis: If a programmed CDN starts to conflict with another device, it can
  disappear from the XML for both historically and moving forward. Fixes
  have been put in place to ensure data consistency and availability.
  Q01172370-03

- Contact Center: Calls not presenting to Agents
  Synopsis: Due to various issues in the core and CTI, the system can enter a
  state where calls are not being presented to agents. This has been fixed
  but relies on CTI version 41.28.02.1.
  Q01398473-02

- XML: Call Real Time screens not updating for Phone and Browser calls
  Synopsis: Not all of the Phone and Browser Calls status were being updated
  reliably in Realtime XML. This has been fixed and both Real Time and
  Wallboard statistics for MMCC calls are accurate.
  Q01405458

- MMCC: Updated MMCC Signing Certificate
  Synopsis: The previous MMCC Certificate used to sign MMCC Java applets,
  which would be presented to callers placing MMCC Calls, Was only good
  up until March 1st, 2007. We have updated the certificates to be
  valid until March 2009.
  Q01657322 

- MMCC: Block Caller does not work in the MMCC Agent interface
  Synopsis: The MMCC Agent interface enables a MMCC Agent to block the
  current caller from using the system again based on their IP. This
  functionality did not work in some obscure scenarios but has been
  fixed in this release.
  Q01383687-01

- MMCC: Incorrect Error message when MMCC Server is down.
  Synopsis: When the MMCC Server is down and a user calls, erroneous messages
  are displayed. The Contact Center now shows a generic out of service
  message in this scenario.
  Q01389692

- MMCC: Cannot log back in as a MMCC Agent after being forced off
  Synopsis: A bug existed where a Contact Center supervisor forces a MMCC agent
  off the system and the agent could not log back in without restarting
  the MMCC agent application. This is no longer necessary.
  Q01405190 

- MMCC: MMCC caller must click link to launch caller applet
  Synopsis: To by-pass popup blockers in most modern browsers, MMCC Callers are
  now forced to click a HTML link to launch the browser applet.
  Q01395147-02

- MMCC: Cannot log back in as a MMCC Agent after being forced off
  Synopsis: A bug existed where a Contact Center supervisor forces a MMCC agent
  off the system and the agent could not log back in without restarting
  the MMCC agent application. This is no longer necessary.
  Q01405190 


Software Update BCM.R400.109-CORE Description:
----------------------------------------------

- Date and Time Change Automatically
  Even when auto time and date settings are configured as manual or NTP in 
  Element Manager, an incoming trunk call with time and date information in 
  the CLID will update time and date on all sets.
  Q01574908

- ACD Monitor Call Error - No Voice Path at Supervisor DN
  Agent A, Agent B, and an incoming line are connected in a conference via 
  privacy control. Supervisor C tries to monitor Set A just as set A is 
  placing the conference on hold. When these two activities occur simultaneously, 
  voice path is lost for the supervisor.
  Q01591782

- Getting Alarm 50 on Power Cycle
  If a BCM is configured for a 3/5 split and the unit is power cycled, the BCM 
  will issue a 50-1 critical alarm and the power LED will turn red.
  Q01643254

- Ring Group Control Set or Line Changes Require a Power Cycle
  If the Ring Group control set is changed from default to another set, the new 
  control set sees "Denied in Admin" when pressing F871. The originally-assigned 
  control set is still able to control the service. This can only be corrected 
  by a power cycle of the BCM.
  Q01548012

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

- Aux Ringer Problems on Hunt Groups
  Intermittently when a hunt group is configured with an Aux ringer, the Aux ringer 
  appears to stick and bell rings continuously.
  Q01579766-02

- Network Billing is Incorrect in Tandem Call Forward Scenario from BCM 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-01

BCM.R400.091-CORE
-----------------

- 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
  Q01577064

- ADID MBM has difficulty connecting to the CO through a very long loop
  Incoming calls on the ADID cards were being released by the
  firmware two seconds after the line was seized, resulting in dropped calls.
  Q01574087-01

BCM.R400.081-CORE
------------------

- Cannot make outgoing calls on VoIP trunks
  If an outgoing VoIP trunk call is released before the far end
  answers, or is released by the originator after the near end answers,
  the VoIP trunk locks up and cannot be accessed.
  Q01586244

- Unable to answer the call on overflow DN off of the Hunt Group
  Incoming Hunt Group calls will drop if a non-hunt group set with an Answer DN
  picks up the call.
  Q01573970

- 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

- Call charge info is missing
  After a call to the public network is disconnected, the call
  charge information provided by the central office cannot be
  displayed on the calling set.
  Q01503686-02

- Button 18 on KIM + T7316e causes Call Pilot failure
  When the button 18 on the KIM is programmed for an external autodial
  and this button is pressed, or F*0 (key enquiry) is
  performed on the button, voice mail on the system stops.
  Q01525570

- No audio on calls from phones in Skillset
  When a call centre agent is logged in to the call center, speech path
  is lost when the supervisor monitors the call. If the Agent places
  the call on hold and goes back to the call, speechpath is present.
  Q015292 28

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

- Line Tuning For BCM 4.0
  This update introduces the line tuning feature for the BCM 4.0 product.
  Q01475421, Q01475421-02

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

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

- Conference Resources are getting locked up in one particular silent
  monitor scenario.
  If an ACD agent supervisor monitors an agent while the agent is
  making an outgoing call, a conference resource will become locked
  up. After 20 calls, no conference resources will be available and the
  users will be unable to set up any conferences.
  Q01536124

- No conference resources
  When a user tries to establish a multi-party conference using a target
  line key defined on a KIM, the system responds with "no conference
  resources available."
  Q01524534

- No Drop Back/rerouting when calling out via SRG50 CO trunks which are down
  The VoIP drop back rerouting feature on the CS 1000 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-05

- 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

BCM.R400.048-CORE
-----------------

- No ring back tone through IP trunk to PSTN
  SRG BCM4.0 does not send a ring back when the set starts a call out to PSTN.
  The call can complete because it rings at the far end, but the caller does not
  hear any ring back. The caller only hears silence until the call is answered.
  After the call is answered they can talk normally. This update corrects the
  issue by sending the Alert message.
  Q01487044

- Upgrade caused the public OLI digits to change
  The 10 digit configured public OLI in BCM4.0 that is upgraded from BCM3.x
  displayed only 4 digits in Element Manager after the upgrade, But 10 digits
  are displayed in set based administration. This update fixed the issue by checking
  the length of the public OLI while sending the digits to Element Manager for
  display. This issue is only applicable to the Australian market.
  Q01410902

- Alarm is not showing the proper Media Bay Module bus number
  Whenever alarms 40 through 47 are raised they do not show the proper bus
  number. This update fixes the issue by changing the alarm parameter from
  maintenance index of the DTI to bus number.
  Q01465611-03

- DN type International can not dial 16 digit number
  Calls can not complete that exceed 16 digits length for the International DN
  type. CS2000 requires the International NPI/TON in order to route
  international calls. A DN type of Public or national does not work. This update fixes the
  issue by changing the constant value from 15 to 24 for the International DN type.
  Q01502219

- Delay in voice path during the start of 3-party conference in the Poland
  market There is around a 5 second delay in voice path at the beginning of the 3-party
  conference. The Poland market conference tone cadence is 100msec tone and
  4900msec no tone. Due to conference tone gain the level is so low that the
  100msec tone is not audible and the 4900msec no tone causes a 5 second delay
  in voice path. This update fixes the issue by increasing the conference tone gain
  level and removing the 4900msec no tone cadence.
  Q01410057

- Low speech on analog trunk calls and IP phone
  On calls established over GATM trunks users can observe low volume when they
  are making outgoing calls. The transmit low volume is seen on TDM as well as
  IP sets. This update fixes the issue by Gain level offsets in GATM Analog to
  Digital converter and Digital to Analog converter.
  Q01513090-01

- Unable to program a Hunt Group DN as an internal auto dial
  Able to program an internal autodial of a Hunt Group DN by using Feature*2 on
  the set, but can not do this in Element Manager. This gives an error saying
  that it is an invalid DN. This update fixes the issue by adding the Hunt Group
  DNs in the list of allowed DNs for internal autodial.
  Q01490178

- Diagnostic error message not displayed when background music fails to play
  When no Shared Media Gateway is available, background music fails and no
  diagnostic error message appears on the requesting IP client. This update fixes
  the issue by sending the NACK message if there are no media gateway resources.
  Q01403665

- Feature Enhancement for BRI EURO Protocol to work in both S-T and T-T user
  mode.
  Q01296708-05

- Unable to dial Faxes from ATA extensions
  Calls from ATA to DASS2 destinations would not connect and CO warns "This
  service is not compatible with the call". This issue is due to a progress
  indicator message that was not sent with a proper parameter for the location.
  This update fixes the issue by sending the proper location parameter in the
  progress message.
  Q01440544-02

- ADID image need to be picked up.
  This update include the ADID image wi12.00
  Q01434997-04

 BCM.R400.043-CORE 
-----------------

- Calls on BCM with supervised ROI lines drop when answered using Australia
  profile New functionality is added to support reversal on seize for analog trunks in
  the Australian market.
  Q01176599

- Problem with incoming calls on PRI
  An incoming PRI call to site A (BCM) which tandems to site B (BCM) via a T1
  E&M interface rings twice at the destination node, but then is dropped. The
  release reason displayed on the set is "Invalid num" (28) An internal call from
  BCM A to BCM B works okay.
  Q01392178-02


Software Update BCM.R400.108-TurkishPrompts Description:
--------------------------------------------------------

- Issues with CallPilot Turkish prompts and labels 
  CallPilot plays incorrect Turkish voice prompts. This update corrects this issue.
  Q01445561


Software Update BCM.R400.107-CTI Description:
---------------------------------------------

- F905 Agent monitor (OBS) fails intermittently
  Symptom is that intermittently while silent monitoring an agent, the
  supervisor will not have voice path with the agent. The problem was
  due to improper handling of the Release/Feature keys in the silent monitor
  initiation state. This update corrects the problem by properly handling 
  the events generated by Release/Feature keys in the silent monitor 
  initiation state.
  Q01622584

- Silent Monitor feature gets the "Observation Cancelled" when used with the
  second dialtone feature.
  Symptom is that when supervisor starts monitoring an agent who dials the
  access code for which the second dial tone is enabled and doesn't dial any
  further digits, after a few seconds the supervisor gets the "Observation cancelled"
  display and the silent monitoring session stops. The problem was due to the Silent
  Monitor feature timing out because of the delay introduced by the second
  dialtone feature. This update corrects the issue by increasing the Silent Monitor 
  time out value.
  Q01529228-01


Software Update BCM.R400.105-IPSecProvider Description:
-------------------------------------------------------

- It was found that the IPSecProviderAgent would crash when VPN clients connected to it.
  This occurred most frequently when the VPN clients were running behind NAT.
  Q01525442, Q01415054

- When 20 IP Address pools are added (which is the maximum), no more IP Address pools
  can be added even if IP Address pools are subsequently deleted. Only restarting the
  IPSecProviderAgent would fix this.
  Q01470729

- BCM 4.0 cannot initiate a Branch Office tunnel with BCM50R2 when AES128 Encryption
  and Diffie-Hellman Group 5 is used.
  Q01575785

- Error codes rather than error text being displayed by IPSecProviderAgent.
  Q01614308


Software Update BCM.R400.104-QOS Description:
---------------------------------------------

- Paging over IP sets has bad audio quality.
This update has changes to the egress queue length to fix this issue.
Q01617220


Software Update BCM.R400.099-CDR Description:
---------------------------------------------

- CDR shows incorrect call duration for some calls.
  This update resolves incorrect call durations in CDR records for both Norstar and SL-1 
  report formats.
  Q01511761-02
  Q01646099


Software Update BCM.R400.097-UTPS Description:
----------------------------------------------

- UTPS crash when an IP set attached to a KEM module resets.
  When an IP set attached to a KEM module with line appearances is reset due to loss 
  of power, or is rebooted, the UTPS service will stop functioning. This will cause 
  all IP sets connected to the BCM to go down. A reboot of the BCM is required to restore 
  UTPS service. UTPS was fixed to handle this situation without crashing.
  Q01546584-02


Software Update BCM.R400.096-VOICEMAIL Description:
---------------------------------------------------

- CCR tree home menus and submenu prompts are repeated twice.
  When the CallPilot UI style is selected, CCR tree home menus and submenu
  prompts are repeated twice instead of repeating only once. This update corrects
  the problem by handling the timer plans properly.
  Q01515756

- Voicemail wrongly generates the subject text.
  Unified Messaging Client users on French-enabled PCs see wrong subject text
  in a voice message when they receive a call with no CLID and Name display.
  This update corrects the problem by properly parsing the control characters
  seen in the French language.
  Q01535615

- Increase Local Number Length from 7 digits to 9 digits for Spanish profile
  This update increases the Local Number Length from 7 digits to 9 digits for
  Spanish profile
  Q01511592

- WAV file exported from BCM fails to load on sound recorder
  When a company greeting recorded using a Telset is exported as a .wav file and
  then loaded on sound recorder, it fails with an error message stating the file
  is corrupted and can not be opened. Problem occurred due to a two-byte
  difference in the header & was not compliant with the RIFF format
  specification.This update corrects the problem by eliminating the two byte
  difference.
  Q01513115-02

- CCR Tree Menu repeats when the user doesn't select any option number
  BCM 4.0 Voicemail has a hard-coded implementation to repeat the CCR tree
  menu, if the user didn't select any option number. This update corrects the
  issue by providing a configurable setting called "Repeat CCR Menu Prompts"
  to the system administrator in the "Auto-Attendant Properties" page. Using
  this option, the administrator can now control the CCR Tree Menu repeat
  behavior. By default the CCR Tree Menu repeat will be enabled.
  Q01585128

- Voicemail slowly leaks file descriptors
  Whenever the user creates a One Button Park and Page, the voicemail application
  opens a file descriptor for each feature code. This open file descriptor is not
  closed properly and file descriptor is leaked. If the number of open file
  descriptor count is more than 1024, there is a chance that voicemail
  application will stop working. The frequency of the problem is intermittent
  and the leakage happens only when an open file is called which does not have a
  subsequent closed file. This update resolves the problem by closing the open
  file descriptor properly.
  Q01601357-02

- BCM 4.0 system CPU spike reboot required to recover.
  Memory usage spikes up while downloading the Voice messages using Unified
  Messaging and reaches its threshold. Which intern kills the application.
  System restart is required to resume the normal operation.
  The fix is provided to avoid the increase of memory usage reaching to
  its threshold.
  Q01534490


Software Update BCM.R400.095-DSPFIRMWARE Description:
-----------------------------------------------------

- T.38 - Inbound faxes disconnect in mid transmission; communication error  
  (interoperation with CS1000)
  During interoperation with CS1000, some inbound faxes were failing during the transmission 
  of a page. BCM can now handle the long scanlines and continuous streams of 0s during the 
  page data.
  Q01594838

- T.38 - CRP replacing EOP, Short DCS tail and Collisions cause fax to fail
  (CRP = Command Repeat, EOP = End of Procedure, DCS = Digital Command Signal)
  Some fax machines have different signal timing characteristics that when traversing T.38 
  would cause the fax session to fail. Changes have been made to the BCM's T.38 codec to:
  - not interfere with a fax session's EOP signaling
  - avoid a race condition internal to T.38 when receiving DCS message with 1 tail flag 
    (normally there are 3 or more)
  - lengthen the time that T.38 will listen for a response from a local fax machine before 
    disabling the receiver
  Q01648220

- IP Set - "beeps" on IP sets coming from the BCM
  People on IP sets were hearing "beeps" due to the fax CED detector being too sensitive. 
  The sensitivity of the CED detector was reduced from -40db to -25db. Changes were also 
  made to allow CED to be detected for 250msec before initiating the CED replacement code.
  Q01640437


Software Update BCM.R400.089-IVR Description:
---------------------------------------------

- Removing vocabs raises Alarm on BCM.
  When removing prompts via the Element Manager or via the Advanced 
  Commands panel with vfsrm, an Alarm was generated (43006). This
  fix will resolve this issue as no alarms should be generated
  Q01591518

- Missing IVR Alarms.
  5 new alarms for IVR will be reported (bim 10003, 10004 and 10006,
  srp 12013 and all vengines alarms will be reported as a single 
  generic one). Also, a missing COMMGR alarms was not logged properly.
  Q01492872-02

- No checks done of file extension for prompt upload.
  The Element Manager was not checking that the prompts to upload 
  have at least the mmi and mmd extension. Now it does and reports
  an error if the files to upload don't have that extension.
  Q01568949 

- Argument list not cleared for Element Manager Advanced Commands
  The argument list will have to be erased by the administrator 
  every time they change command. Previously, the field was 
  automatically cleared but the argument was still applied to a 
  command and the arguments would reappear.
  Q01568962

- dbman not working properly from Element Manager
  The dbman command should be running as peri so that applications 
  can use the output created by dbman. Also dbman (and other commands)
  can create output files. The path where those files should be 
  created is limited but not indicated anywhere. A new warning on
  the Advanced Command panel will inform the user about the path
  where files can be created. 
  Q01559337 

- It is not possible to delete IVR configuration files
  The Element Manager IVR Advanced Configuration screen will now have
  a third button associated with the configurations files. As well as
  being able to upload and download the files, a new button will be 
  added to allow the administrator to delete files.
  Q01439408

- It is not possible to upload or download files with spaces in the 
  name. A file name that contains spaces will now be uploadable on 
  the BCM via the IVR Advanced Configuration screen.
  Q01568981

- Reboot is required to recover alarm generation
  After applying the update to have more IVR alarms available, there is
  a requirement to reboot the system. This is no longer necessary.
  Q01645481

BCM.R400.054-IVR
---------------

- If a file name with more than 32 characters exists in one of the folders
  that can have files uploaded or downloaded for IVR via the IVR Advanced
  Configuration tab, then the Element Manager IVR windows will display
  errors and IVR cannot be administered. This fix will allow file names of
  up to 256 characters (including the path name).
  Q01506212

BCM.R400.027-IVR
----------------

- Element Manager prevents file uploads and downloads from some IVR
  directo ries IVR Applications may need to access files in the
  /var/nn/ivr/data, /var/nn/ivr/fax or /var/nn/ivr/mmf folders. The files
  in those folders may be configuration files that need to be updated
  periodically. The Element Manager does not allow files to be uploaded to
  downloaded from those folders. This fix will allow the upload or download
  of files from those folders via the Element manager IVR Advanced
  Configuration panel.
  Q01439405

- Text file format incompatibility with Windows
  There are three configuration files that may need to be updated to be
  able to configure data base access for certain type of IVR applications.
  The GEN.CFG, ASE.CFG and VOS.CFG files can be downloaded from a BCM to a
  PC using the Element Manager IVR Advanced Configuration panel, edited to
  configure database access and uploaded back to the BCM via the same panel.
  There was a problem uploading a file and an error was displayed in the
  Element Manager stating that the file was invalid. The fix resolves this
  issue.
  Q01454586


Software Update BCM.R400.085-IPTEL Description:
-----------------------------------------------

- VoIP Trunk Lockup
  The VoIP Gateway would not properly release the VoIP trunk after having 
  rejected an incoming VoIP call due to a codec negotiation failure.
  Q01589331

- VoIP Gateway exception
  The VoIP Gateway would crash when trying to discover and register with 
  a BCM 3.6 acting as an H.323 gatekeeper.
  Q01592829 

- VoIP Gateway displays incorrect status 
  The VoIP Gateway status would incorrectly display a status of 'Shutting down' 
  when set to GatekeeperRoutedNonRas and no backup gatekeeper was configured.  
  Note that if in GatekeeperRoutedNonRas mode, then the Backup Gatekeeper 
  Address must also be populated for the VoIP Gateway to display the correct 
  status.  If there is no backup gatekeeper in the network then the primary 
  gatekeeper address may also be used to fill this field.
  Q01612881
  Q01729819-02

- MGS generating alarm 53011
  When switching to a T38 fax call, the MGS would sometimes generate the 
  critical alarm 53011
  Q01403054

BCM.R400.075-IPTEL
----------------

- Failure to switch to T.38 mode in tandem scenario
  Attempts to switch from a voice call to a T.38 fax call would fail in a tandem scenario in 
  which the BCM was the tandem node.
  Q00905442

- VoIP Gateway does not use T.38 Fax Support settings correctly
  Changes to the T.38 Fax Support setting do not get used by the VoIP Gateway until the 
  VoIP Gateway is restarted.
  Q01487793 

- Not able to make VoIP calls when VoIP Gateway in Gatekeeper Non RAS mode
  When the VoIP Gateway is configured to use GatekeeperRoutedNonRAS mode, outgoing
  VoIP calls are not able to complete.
  Q01488883-01

- Force G711 for 3.1kHz Audio feature does not function correctly
  The Force G.711 for 3.1KHz Audio feature will only be activated if T.38 Fax Support is also 
  activated. 
  Q01491995-01

- VoIP Gateway crash
  The VoIP Gateway will generate an exception upon attempting a VoIP call when in 
  GatekeeperRoutedNonRas mode and a matching entry exists in the Address book.
  Q01493744-01

- GatekeeperRoutedNonRAS ping mechanism
  The VoIP Gateway GatekeeperRoutedNonRAS gatekeeper ping mechanism appears 
  as security risk in some networks..
  Q01497975

- Gatekeeper IP address does not change in GatekeeperRoutedNonRAS mode.
  Changing the gatekeeper IP address while in GatekeeperRoutedNonRas mode did not 
  get used by the VoIP Gateway.
  Q01502353

- VoIP Gateway crash
  VoIP Gateway crash upon receiving gatekeeper admission confirmation after call 
  release.
  Q01524349-01

- Intermittent no speech path for VoIP calls transferred by auto-attendant.
  VoIP calls transferred by the auto-attendant on one BCM to a second BCM experience 
  intermittent loss of speech path.
  Q01542458

- VoIP Gateway status in Element Manager not updated correctly in 
  GatekeeperRoutedNonRas mode When the VoIP Gateway is in GatekeeperRoutedNonRAS 
  mode, Element Manager shows status of "Running ..." when gatekeeper is not available.
  Q01570430


Software Update BCM.R400.084-QOSMON Description:
------------------------------------------------

- For IPT and BCM 4.0 QoS interop, if the IPT is configured to perform QoS on a link
  with a BCM 4.0, the IPT card will remain in fallback on that link. This update resolves
  that issue and allows the IPT link to stay out of fallback. This is of course if the 
  actual network quality of service is greater than the configured threshold on the IPT.
  This update also fixes the QoS logging to the file qmon.log found in the BCM 4.0 logs.
  Without this update the BCM 4.0 would incorrectly log the QoS statistics as perceived by the
  far end. It would log them as zero. After this update the qmon.log file will correctly 
  log the far end QoS statistics.
  Q01574347


Software Update BCM.R400.083-QOS Description:
---------------------------------------------

- More than 40 remotely registered IP Sets could crash the BCM
  When a BCM has more than 40 IP Sets remotely registered, there is a high probability of 
  seeing a kernel crash, followed by a system reboot. When this occurs, it 
  is likely to repeat frequently. "Remotely registered" IP Sets 
  means that the set's IP address does not fall in the same IP subnet as any of the 
  BCM interfaces. For example, for a BCM configured with published 
  IP address 192.168.1.1 netmask 255.255.255.0, an IP set configured with address 
  192.168.2.1 netmask 255.255.255.0 that registers with the BCM would be considered 
  "remotely registered." Another IP set configured with address 192.168.1.10 netmask 
  255.255.255.0 that registers with the BCM would be considered "locally registered."
  Q01572030

- QoS Queuing changes not applied immediately
  When a user changes the bandwidth allocation for any of the seven queues in the 
  Element Manager under Configuration -> Data Services -> QoS Queuing,
  the changes are not applied immediately. The changes are applied the next time another 
  change is made in the same area.
  Q01541195

- Minimum bandwidth allocation of 0% does not work
  When a user sets the "minimum bandwidth" percentage to zero in the Element Manager 
  (under Configuration -> Data Services -> QoS Queuing), the QoS queuing functionality of 
  the interface parameters will be disabled. The minimum value that could be used was one. 
  With this update a value of zero is accepted.
  Note: When a guaranteed bandwidth value of 0% is entered, it is important to clarify 
        a limitation in the queuing behavior. This is best explained with two cases:
        Case 1: Minimum guaranteed value is 0% and maximum guaranteed value is 0% for 
                a given QoS queue. The egress traffic will not be 100% dropped. There
                will be a maximum of one packet per second that will be forwarded and
                tracked under the packets within guarantee metrics. To achieve 100%
                 packet drop for a given QoS queue it is suggested to configure an
                outbound IP Policy Filter rule to block all traffic matching 
                the DiffServ Code Point (DSCP) values of that QoS queue.
        Case 2: Minimum guaranteed value is 0% and maximum guaranteed value is greater
                than 0% for a given QoS queue. The egress queuing metrics will show a 
                maximum of one packet per second that will be forwarded and tracked 
                under the packets within guarantee metrics. The other egress traffic
                metrics for that QoS queue in excess of one packet per second will be
                tracked as expected either under the "packets over guarantee" or "packets
                dropped" metrics.
  Q01541195

- QoS metrics for "packets over guarantee" do not show per queue
  When a user monitors the "packets over guarantee" metrics under the 
  "Administration -> System Status -> QoS Metric" panel, the metrics will
  show 0 for the per-queue metrics. However, the summary "packets over guarantee" 
  metrics worked fine. Now the per-queue metrics work properly.
  Q01541195

- Early traffic shaping for WAN1 and WAN2 interfaces 
  Traffic shaping over the "WAN1" and "WAN2" interfaces shaped some traffic at the 
  layer 3 level (IP stack queuing) when traffic for a particular QoS queue was forwarded
  exactly at the limit of the minimum guaranteed bandwidth for that queue. The 
  expectation was that no traffic should be shaped unless there is excess traffic
  forwarded above the minimum guaranteed bandwidth for that queue.
  Q01541195

- Malformed H.323 messages could crash the BCM 
  When H.323 messages are decoded in ASN.1 format, if an error occurs in the decoding
  where the message contains incorrect data, there is a possibility that a kernel 
  crash can be seen while attempting to record information about the malformed message.
  Q01580636

- Support NAT and Firewall for multiple dialin connections with the same account name
  When an account name is used to dial in to the BCM, and if there are NAT and/or Firewall
  rules configured against the account name, they may not get applied properly. This issue
  is only applicable to dialin connections. In addition, this issue is only visible when
  NAT or Firewall, or both NAT and Firewall on account names are enabled.
  Q01530410


Software Update BCM.R400.081-CORE Description:
----------------------------------------------

- Cannot make outgoing calls on VoIP trunks
  If an outgoing VoIP trunk call is released before the far end
  answers, or is released by the originator after the near end answers,
  the VoIP trunk locks up and cannot be accessed.
  Q01586244

- Unable to answer the call on overflow DN off of the Hunt Group
  Incoming Hunt Group calls will drop if a non-hunt group set with an Answer DN
  picks up the call.
  Q01573970

- 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

- Call charge info is missing
  After a call to the public network is disconnected, the call
  charge information provided by the central office cannot be
  displayed on the calling set.
  Q01503686-02

- Button 18 on KIM + T7316e causes Call Pilot failure
  When the button 18 on the KIM is programmed for an external autodial
  and this button is pressed, or F*0 (key enquiry) is
  performed on the button, voice mail on the system stops.
  Q01525570

- No audio on calls from phones in Skillset
  When a call centre agent is logged in to the call center, speech path
  is lost when the supervisor monitors the call. If the Agent places
  the call on hold and goes back to the call, speechpath is present.
  Q015292 28

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

- Line Tuning For BCM 4.0
  This update introduces the line tuning feature for the BCM 4.0 product.
  Q01475421, Q01475421-02

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

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

- Conference Resources are getting locked up in one particular silent
  monitor scenario.
  If an ACD agent supervisor monitors an agent while the agent is
  making an outgoing call, a conference resource will become locked
  up. After 20 calls, no conference resources will be available and the
  users will be unable to set up any conferences.
  Q01536124

- No conference resources
  When a user tries to establish a multi-party conference using a target
  line key defined on a KIM, the system responds with "no conference
  resources available."
  Q01524534

- No Drop Back/rerouting when calling out via SRG50 CO trunks which are down
  The VoIP drop back rerouting feature on the CS 1000 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-05

- 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


Software Update BCM.R400.080-SCD Description:
---------------------------------------------

- Several log files have been found to be in "deleted" state, but still taking
  up space on the logging partition. This can result in alarm 11201 "Hard 
  Drive near Capacity" in the site. This update resolves the issue of disk
  space exhaustion.
  Q01529404-02


Software Update BCM.R400-078-CTE Description:
---------------------------------------------

- VoIP Lines not monitored; do not present call info to console.net
  LAN CTE appears not to be monitoring all of the VoIP trunks.  Trunks that
  are not being monitored are also not being presented. This update corrects
  this issue.
  Q01588113, Q01502372-01

- CTE - TransmitDigits API Correction
  When the CTE API TransmitDigits is used to send a string of more than 1
  digit, it returns a SUCCESS immediately after dispatching the first digit in
  the string. Since any of the subsequent digit transmission could result in a
  failure, ideally the API should return SUCCESS only after transmitting the 
  entire string of digits. This update corrects this issue.
  Q01449385-01

- Client Installer removes old versions of LAN CTE files that conflict with 
  new versions.
  Q01404399 

- System events not being processed by system event handler.
  Q01408365

- Application shutdown can cause a crash during cleanup.
  Q01404466

- Translation of accelerator keys in Windows message loop.
  Q01403876

- CTE Crashes on target line calls with 10 digits.
  On systems configured with Target Line DN's greater than 7 digits CTE can crash. 
  Theses additional symptoms will also  occur.
   - The CPU shows 100% use and is affecting IP sets and AA. It lasts about 10 mins 
     then everything works again.
   - IP sets - cutting in and out, long delays.
   - AA - voice is scratchy
   - Line monitor doesn't work on this BCM from any PC but does work on other BCM's.
  Q01420757

- CTI reports only 8 DNIS digits when the CO sends 10.
  Although the CO is sending 10 digits, CTI and CTE are only reporting the leading 8 
  to applications. Contact Center configured with the "DNIS Routing sub-feature" will 
  not function correctly if the DNIS is more than 8  digits.
  Q01423730

- CTE reports only 8 DNIS digits when the C O sends 10
  Although the CO is sending 10 digits, CTI and CTE are only reporting the leading 8 to
  applications. Client side applications that depend on DNIS information will not 
  function correctly if DNIS is configured for more than 8  digits.
  Q01423730-01


Software Update BCM.R400.076-InventoryProvider Description:
-----------------------------------------------------------

- New WAN520 card is not displayed in hardware inventory. 
  This update corrects the problem by adding vendor id and device id
  information for WAN520 Card to the Inventory Provider Component.
  Q01582143


Software Update BCM.R400.073-OPENSSH_OPENSSL Description:
---------------------------------------------------------

- OpenSSL security issues addressed are as described in http://www.openssl.org/ 
  and http://www.openssl.org/news/secadv_20060928.txt

- OpenSSh security issues addressed are as described in http://www.openssh.org/ 
  and http://www.openssh.org/txt/release-4.4

- Daylight Saving Time for Western Australia
  On December 3, 2006 daylight saving time was introduced into Western Australia. 
  This fix allows BCM4.0 systems set to this Time Zone to correctly adjust the 
  system clock for DST. A referendum in 2009 will determine whether to continue 
  to apply DST, to a subsequent update may be required at that time if further 
  changes are made to the DST regimen.
  Q01502789-02


Software Update BCM.R400.069-IVR Description:
---------------------------------------------

- IVR Alarms are not reported.
  IVR alarms are not reported at all. With this fix, 4 alarms will be 
  reported (bim 10001, bim 10005, srp 12002 and srp 12003). All
  are major or critical alarms that will report SNMP traps and turn 
  the system status LED red.
  Q01492872 

- Files uploaded in folders via the Element Manager IVR Advanced 
  Configuration panel have the wrong ownership.
  IVR applications do not have enough permissions to access those files. 
  This fix will allow both IVR applications and internal processes to 
  have the appropriate permissions to read and/or write to those 
  uploaded files.
  NOTE: Backups taken on systems prior of having this update applied will 
        revert the ownership of the files. A new backup should be taken 
        after applying this update.
  Q01559335

- IVR Applications cannot create files. 
  A list of folders with enough permissions need to be available to IVR 
  application so they can create files (stats, logs, etc...). This fix 
  will provide IVR applications with a list of folders that can be used 
  to create files, namely: /var/nn/ivr/data and /var/nn/ivr/fax. Those 
  2 folders will be added to the list of folders already available for 
  file creation to IVR Applications.
  NOTE: Backups taken on systems prior of having this update applied will 
        revert the ownership of the folders. A new backup should be taken 
        after applying this update.
  Q01559336

- IVR Applications cannot save CDR Records. 
  IVR Applications may want to copy their stats in the /var/nn/CDRDataFiles
  folder so that they can be picked up by the CDR Pull capability of the BCM.
  That folder needs enough permissions for IVR applications to be able to
   move their stats records.
  NOTE: Backups taken on systems prior of having this update applied will 
        revert the permissions of the folders. A new backup should be taken 
        after applying this update.
  Q01578144

- If a file name with more than 32 characters exists in one of the folders 
  that can have files uploaded or downloaded for IVR via the IVR Advanced 
  Configuration tab, then the Element Manager IVR windows will display 
  errors and IVR cannot be administered. This fix will allow file names of 
  up to 256 characters (including the path name).
  Q01506212

- An extra command is available via the Element Manager IVR Advanced Commands panel.
  The "vfsrm" will now show in the list of commands that can be executed. This 
  command can be used to remove IVR vocabulary  files from the system.
  Q01474722

- Applications using DISAM files experienced abnormal termination and errors 
  reading, locking, and deleting DISAM files.
  The peri user lacked permissions for manipulation of temporary files created during 
  DISAM file processing, because the  DISAM library was built with an incorrect build 
  option. Build options have been corrected, the library has been rebuilt,  and 
  executables incorporating the rebuilt static DISAM libraries are included in this update.
  Q01475874


Software Update BCM.R400.066-CDR Description:
---------------------------------------------

- CDR multi-party conference records are incorrect most of the time.
  This update resolves the issue of incorrect CDR multi-party conference records 
  under various multi-party conference call  scenarios.
  Q01467648

- CDR DN number is incorrect for the SL1 record format for variable DN length.
  This update resolves the incorrect DN number issue seen in SL1 record format for 
  variable-length DNs.
  Q01512744.

- CDR Stops working after a few language changes like German and Dutch.
  This path resolves the crashing of CDR service when languages like German and 
  Dutch are selected in Element Manager for  CDR Norstar report format.
  Q01508526-02

- CDR Multi-Party Conference Record - Trunk Call missing CALL RELEASED entry
  This update adds the CALL RELEASE line which 3rd party applications rely on to 
  identify the end of each line in Ad-hoc  conferences.
  Q01529318-02

- Element Manager disconnects when clicking on CDR.
  This update resolves the issue of EM closing when the CDR option is selected in 
  Element Manager.
  Q01486203

- CDR Transfer not properly closing sockets.
  This update resolves the issue with sockets not properly closing after CDR record 
  transfer.
  Q01408588 


Software Update BCM.R400.064-LANDriver Description:
---------------------------------------------------
- LAN Connection type settings configured through Element Manager are not retained
  on reboot.
  This update corrects this problem in the LAN Provider component by storing the 
  connection type information in PDR when  the configuration is changed.
  Q01566403


Software Update BCM.R400.063-CTI Description:
---------------------------------------------

- Unable to record/leave a Voicemail over VoIP with Trunk Anti-Tromboning (TAT) enabled.
  Symptom is that a blank voicemail is played back when a user leaves a voice 
  message from Centralized voicemail over VoIP (both H.323 and SIP) when TAT is 
  enabled. User leaving a message will hear "Please speak louder or speak directly 
  into the telephone to ensure clear recording" and then "Exiting the system, Good Bye"
  Problem occurred due to Voice CTI being  unable to get the correct media path 
  support, which resulted in one-way voice path between voicemail and the caller. 
  This update corrects the media path issue so that a user can record/leave a VM 
  over VoIP with TAT enabled.
  Q01410162

- Voicemail is delivered to the wrong mailbox
  Problem occurred due to improper handling of the voice files at the Voice CTI level. 
  This update corrects the problem by  properly handling the voice files opened in 
  read/write mode.
  Q01534532-01


Software Update BCM.R400.061-OAM Description:
---------------------------------------------

- Line Tuning For BCM 4.0
  This update introduces the line tuning feature for the BCM 4.0 product.
  Q01475421

- Feature Enhancement for BRI EURO Protocol to work in both S-T and T-T user mode.
  Q01296708-05

- After upgrade to BCM4.0 WAN PPP link does not come up. The problem is due to no option 
  provided to configure NONE Authentication. This update corrects the problem adding the 
  NONE option to Element Manger. 
  Q01500035 & Q01531731


Software Update BCM.R400.050-SU1 Description:
---------------------------------------------

- This update is comprised of the following updates which are described below
  BCM.R400.039-IVR
  BCM.R400.035-CTI
  BCM.R400.034-IPTEL
  BCM.R400.033-SMG
  BCM.R400.032-PSM

BCM.R400.039-IVR
---------------

- An extra command is available via the Element Manager IVR Advanced Commands
  panel.
  The "vfsrm" will now show in the list of commands that can be
  executed. This command can be used to remove IVR vocabulary files from the
  system.
  Q01474722

- Applications using DISAM files experienced abnormal termination and errors
  reading, locking, and deleting DISAM files.
  The peri user lacked permissions for manipulation of temporary files created
  during DISAM file processing, because the DISAM library was built with an
  incorrect build option. Build options have been corrected, the library has
  been rebuilt, and executables incorporating the rebuilt static DISAM libraries
  are included in this update.
  Q01475874

BCM.R400.035-CTI 
-----------------

- CTI backs up IVR configuration as part of data backup
  The /var/nn/ivr/data folder is being picked up as part of the IVR data backup;
  it should be picked up as part of the configuration part of the 
  IVR backup. That will allow applications to be distributed to all BCMs via 
  backup and restore (as it was done in BCM3.X) without having to also restore 
  VoiceMail Data and Configuration. Customers running IVR should check with 
  their application developer to make sure that their IVR backup will not grow 
  too big if their data folder is backed up as part of the configuration of IVR.
 
  IVR Configuration will now include the content of the following files:
  /opt/vps/common/etc/*
  /opt/vps/mps*/apps/*
  /opt/vps/mps*/apps/lib/*
  /opt/vps/mps*/etc/*
  /opt/vps/mps*/stats/*sh
  /opt/vps/packages/pdp2.10/etc/*
  /opt/vps/packages/plic1.2.0/etc/*
  /opt/vps/packages/hostp2.1.0/etc/*
  /opt/vps/packages/ase5.0.0/etc/*
  /var/nn/ivr/data/*
  and all vocabulary used by the vex applications.
 
  IVR Data will now include all CMR recordings and the content of the 
  /var/nn/ivr/fax
 
  IVR Data is transient data that should only be restored to the same BCM from 
  which it was taken. Examples of transient data are faxes and recorded messages
  (like voicemail messages).
  Q01454973

- Mailboxes with outbound notification cannot respond to DTMF 
  If an application uses pauses after dialing the destination code and the 
  trunk returns dial tone, the DSP used by the dialing voice port will 
  detect it and the dial tone will be translated into a character recognized 
  internally to indicate that an internal call is in progress. That information
  makes Voice CTI disable in-band DTMF detection. The fix is to make the 
  character indicating an internal call different from any other characters 
  that Call Progress Tones could change into.
  Q01401361

- CTI reports only 8 DNIS digits when the CO sends 10
  Although the CO sends 10 digits, CTI and CTE only reports 
  the leading 8 to applications.
  Contact Center configured with the "DNIS Routing sub-feature" will not
  function correctly if the DNIS is more than 8 digits.
  Q01423730

- DTMF Tones not recognized by BCM Call Pilot
  BCM is receiving both in-band and out of band DTMF digits over VoIP into VM/AA
  Symptom is that when a VoIP call is received by BCM CallPilot across a network, 
  the calling party receives a CCR menu as required, however on entering a digit
  to select the CCR tree, the CCR tree is not followed. This update corrects the
  problem by monitoring incoming VoIP trunk calls to ignore the in-band DTMF 
  digits based on the configuration setting on the Element Manager.
  Q01314181-05

  Further information related to Q01314181-05: DTMF Tones not 
  recognized by BCM Call Pilot.
  The following notes apply specifically to the change in DTMF handling for VoIP 
  applications in response to the above CR.

  Background
  Typical CS2000 networks involve multiple Nortel and non-Nortel VoIP products 
  at both the customer premises and carrier locations.  These include BCM, 
  CS1000, and Centrex IP Call Manager (CICM) as well as third party CPE gateways
  and the CS2K Passport Voice Gateway (PVG).  For VoIP calls, each of these 
  gateway devices uses call control signaling directly with the CS2000 Gateway
  Controller (GWC), while the media from each of these devices is connected 
  directly between the two endpoints involved in a call.  The GWC supports 
  multiple protocols for signaling, including H.323 for communicating to devices
  such as BCM and CS1000.  Each of these signaling protocols uses different 
  methods for signaling mid-call DTMF.

  In H.323 networking configurations, BCM is designed to respond to incoming
  in-band DTMF tones (embedded in the media stream as audio) or an out-of-band
  H.245 DTMF message.  When DTMF is received while the far end is connected to
  a BCM application such as Auto Attendant or Voicemail, the BCM application 
  collects the digits and follows the appropriate actions in response.  While 
  the expected behavior is to only receive mid-call DTMF via one method or 
  the other, in some CS2000 based networking scenarios the BCM will receive 
  both methods simultaneously.  Both of the DTMF messages are passed to the 
  BCM application(s), causing unexpected, customer impacting behavior. 

  This BCM software component release provides a method for controlling whether
  BCM will 'listen' for in-band DTMF.  The ability to ignore the in-band DTMF 
  will resolve some, but not all, of the interworking scenarios that can result 
  in this duplicate DTMF reception.  

  Supported scenarios
  The current H.323 VoIP behavior for BCM to/from BCM and BCM to/from CS1000 
  calls with or without a CS2000 gatekeeper uses only out-of-band H.245 based 
  DTMF, with no in-band messages.  Activating the 'Ignore In-band DTMF' 
  functionality will have no effect on these calls.  

  The Nortel PVG used in the CS2000 environment has the ability to squelch 
  (remove) the in-band DTMF for a subset of endpoints on particular incoming 
  TDM based connections.  If networks are configured to use this squelching 
  mechanism for BCM-destined calls, then activating the 'Ignore In-band DTMF'
  functionality will have no effect on these calls.  
  (The configuration mechanism and network design implications for the PVG and 
  CS2000 is beyond the scope of these BCM release notes).

  However, when the PVG is not configured to use the squelching mechanism for 
  BCM-destined calls, the activation of the 'Ignore In-band DTMF' functionality 
  will stop the duplicate in-band DTMF messages reaching the BCM applications, 
  and the BCM applications will process the single DTMF message as expected.

  Unsupported scenarios
  The 'Ignore In-band DTMF' functionality will result in no in-band DTMF messages 
  from H.323 trunks from reaching the BCM applications.  Therefore, any network 
  scenario to/from and endpoint that results in only in-band DTMF transmission 
  to the BCM on an H.323 call will not work when this functionality is activated.
  Currently, this is the behavior for DTMF transmission to the BCM from certain 
  third party VoIP gateways (such as the Mediatrix Gateway) and the Centrex IP 
  Call Manager (CICM). Therefore, CS2K based networks that result in calls 
  between these devices and BCM cannot rely on the 'Ignore In-band DTMF' 
  functionality on the BCM to resolve the duplicate DTMF message scenario on 
  BCM to/from PVG calls.  Other endpoint devices supported by the CS2000 may 
  also exhibit this behavior.  If the BCM is expected to receive mid-call DTMF 
  from these endpoints, the 'Ignore In-band DTMF' functionality cannot be active
  on the BCM.

  These scenarios can be supported using other methods.  
  *  As noted earlier, the CS2000 network can be configured to squelch the 
  in-band DTMF between the PVG and BCM.  A CS2000 network configured this way 
  will result in only out-of band DTMF for BCM calls involving other BCM, 
  CS1000, or PVG endpoints and only in-band DTMF for BCM calls involving 
  Mediatrix and CICM endpoints.
  *  Consideration is being given to a method of optionally modifying the GWC's 
  profile for the BCM to block the sending of out-of-band DTMF.  This scenario
  would result in only out-of band DTMF for BCM calls involving other BCM, 
  CS1000 endpoints and only in-band DTMF for BCM calls involving Mediatrix, 
  CICM, and PVG endpoints. Timing of the availability of this modified GWC 
  behavior is still to be determined.

  Note that the reliability of in-band DTMF detection is a function of both 
  the media stream codec and the network quality that carries the media.  
  A G.711 based media stream will provide higher reliability of detection 
  than a G.729 because of the compression/decompression process. 
  The reliability is also greater on a well engineered IP network compared 
  to one that suffers from both jitter and packet loss.  The impact of jitter 
  and packet loss is also greater when compression is used.

BCM.R400.034-IPTEL 
------------------

- Inability to Open H245 Channel, CS2000 Interop
  Call scenario: CS2000->BCM(Call Forward Busy)->CS2000. Incoming CS2000 call is
  forwarded by the BCM to another CS2000, as  the forwarding set is busy, and call 
  forward busy is provisioned. An H245 channel cannot be opened on the inbound call 
  leg  to the BCM. This can have a number of user visible impacts such as: the inability 
  to establish a voice path on an IP set,  inability to send/receive DTMF, inability to 
  perform any voice path manipulation such as call transfer or hold. In  general, the 
  symptom is usually no voice path.
  Q01274497-01

- Gatekeeper Deregistration Problem
  Upon losing connectivity to the primary gatekeeper, t he 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  failed 
  attempts and instead attempts to try to register with the backup. After 350 such 
  attempts, the VoIP Gateway (FEPS)  runs out of RAS transaction resources, and 
  must be restarted. This issue has been resolved by forcing the VoIP Gateway to  
  try to switch between the primary and backup in an alternating fashion. The 350 RAS 
  transaction limit will not be reached  and no restart of the VoIP Gateway is required 
  unless of course there is a user invoked configuration change requiring a  gateway 
  restart.
  Q01404705-01

- 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.
  Q01232655-04

- 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 H.323 
  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.
  Q01379114-02

- T.38 Fax Rate Incorrectly limited to 200bps,
  Inbound VoIP SIP trunk calls to the BCM's fax machine result in a fax rate that is 
  limited to 200bps. This can be verified by inspecting the BCM Monitor RTP Sessions 
  tab. The resolution was to allow the fax machines to negotiate a higher rate such as 
  14,400 bps
  Q01403020-01

- Services Failing and Alarm 52005 and Alarm 11204
  If Voice Mail is hosted on the BCM and a message waiting indicator is sent to a Voice
  Mail client system over SIP it is  possible that Alarm 52005 and 11204 will be generated
  on the Voice Mail host BCM. Some services my go down or restart.
  Q01438316

BCM.R400.033-SMG 
---------------

- Delayed Paging
  The first part of a page can be cut off on some IP sets when a large number of IP sets
  is paged at the same time. This is  due to delayed VoIP paging setup. The fix included
  in this update will reduce the paging setup time for IP sets to enable  paging to a 
  greater number of IP sets than would be practical without this update.
  Q01224647, Q01301100

- Missing voice path for call answer via off-hook handset when hotdesking
  When a desktop phone (e.g. 2004) is used to 'Hot Desk' a softphone (e.g. 2050), that 
  Handsfree and Headset modes on the  desktop phone became unusable. With this 
  fix, a user using a desktop phone to Hot Desk a softphone will be able to make use 
  of the Handsfree and Headset capabilities of the desktop phone when making or 
  receiving calls.
  Q01416055-01

- Infrequent no-way speech path call when using IP phone
  Every time an IP phone made or received a call there was a very small probability that
  this call would not have audio  (user does not hear and is not heard by far-end). This 
  fix resolves the issue.
  Q01404093

- Listening R metric is reported against desktop clients for i2050 P2 softphones
  When 2050 softphones detect PVQM violations, these violations are reported against 
  'desktop phones' in the PVQM management  panel of Element Manager when they 
  should have been reported against 'softphone'. This fix resolves the issue.
  Q01327461-01

- PVQM Alarm description as mentioned in the FD is not shown in EM
  When PVQM violations are detected, an alarm is raised. This fix enhances the 
  PVQM information carried in the text of the  alarm to allow tools such as Net6 servers 
  to perform advanced processing on the PVQM data.
  Q01410941-01

- Alarm 50503 generated when called from an i2050 set
  Sometimes the 2050v2 softphone generated PVQM alarms reporting 0% packet loss 
  in error. This fix eliminates these  erroneous alarms.
  Q01407702

- On i2004 set, need to hold button down to see what is programmed on to it.
  When entering the button inquiry feature via 'Feature*0' to query key programming 
  information, sometimes IP phones would  only display the key programming 
  information for a very brief period of time making it hard to read. This fix addresses  
  the issue
  Q01357516-02

- IP Set's DN not retained during upgrade
  When upgrading from a BCM3.x to BCM4.0, some IP phones may lose their DN 
  programming as a result therefore requiring the  need to reprogram the DN on the 
  phone. This fix addresses the issue.
  Q01449571

BCM.R400.032-PSM 
-----------------

- Duplicate Files
  Fix file inconsistency and file(s) overwritten by duplicate tar files.
  Q01403599-05.

- Incorrect available memory
  Fix "available memory" value presented by psmtest.
  Q01406877

- psmtest gives inaccurate readings for CPU
  CPU utilization was over-reported by psmtest (CPU appeared busier than 
  it really was).
  Q01413735

- "Physical memory near or on its capacity" alarm appears after archlog 
  transfers to FTP server Fix memory alarm by increasing memory threshold.
  Q01413147 


Software Update BCM.R400.046-SoftwareManagement Description:
------------------------------------------------------------

- "Scheduled" update fails to perform required reboot
  A "scheduled" update that requests a reboot would fail to perform that reboot.
  Q01503795-02, Q01411128

- Updates report "Success" before update application is complete
  The update process previously would report "Success" as soon as their constituent 
  RPMs were installed. Some updates can perform significant operations after 
  installing their RPMs which, if interrupted by a power cycle, could cause the update to
  fail and in the worst case disable the BCM completely. This update causes future 
  update processes to wait until all post-processing is complete before reporting update
  completion status.
  Q01511412-01


Software Update BCM.R400.044-VOICEMAIL Description:
---------------------------------------------------

- BCM CallPilot fails to reply to an AMIS networking message.
  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-04

- Message delivery fails if the AMIS networking message is composed of multiple recipients. 
  Symptom is that BCM CallPilot delivers the AMIS networking message only to the first 
  recipient in the TO address list and  fails to deliver the AMIS networking message to 
  the other recipients in the TO address list. This occurred due to VoiceCTI  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 does not use the same trunk LAD.
  Q01446965-04

- Rare delivery failure for AMIS.
  When sending an AMIS networking message to multiple sites, occasionally the 
  sender's mailbox will receive a 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 re-sending the  AMIS message as per the number 
  of retries configured in the AMIS retry page for cases where Trunk drops the call in 
  the  middle of an AMIS negotiation.
  Q01448471-04

- CallPilot is not properly sending the read receipt for messages sent with the 
  "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 the sending of duplicate read receipts to the same  mailbox 
  user instead of sending to each mailbox user. This update corrects the problem by 
  generating the unique message  IDs for each read receipt sent by the system.
  Q01414600-04

- Auto Attendant is not working due to a locked VM port.
  This update resolves a race condition, which causes a Voicemail port to become 
  locked up when a page retry starts at the  same time the far end disconnects the call. 
  The symptom is that the Voicemail service is running, but Voicemail 
  (Auto attendant in particular) is not accessible. The Voice port can only be unlocked 
  by a reboot or stopping/starting the  Voicemail service.
  Q01497428 


This update includes the content of the following superseded Smart Updates:

BCM.R400.SU.System.013-200808

