Software Update Name: BCM.R400.SU.System.005-200711

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.

Components & Versions: 
  apcupsd                 3.14.01
  backup-recovery         41.2.25.10
  backup-recover-provider 41.2.23.91
  bcmEMcartridge-BCM200   2.67
  BCM_DOORPHONE           41.2.4.127
  callpilot-provider      41.10.24.09
  CCRSAppServer           41.2.07.16
  cdr                     41.11.06.10
  cdr-provider            41.11.05.10
  cfs                     41.10.24.19
  core-telephony          41.02.10.8
  core-telephony-provider 41.00.30.96
  cte                     7.11.05A
  cteapps-obt             41.00.07.98
  cti                     41.30.00.1
  dataservices            41.0.440.70
  dialogger               41.20.03.15
  dsp-firmware            37.70.110.9
  ems                     40.02.101.26
  feps                    41.500.0.33
  glibc                   2.3.2-80.10.12.1.0
  inventory-provider      41.20.01.115
  ipsecprovider           41.0.29.71
  iptelprovideragent      41.130.1.43
  ivrprovider             41.00.2044.113
  lan-cte-provider        7.11.05A
  lan-provider            41.10.50.82
  mgs                     41.60.0.3
  MMCC                    41.2.06.28
  mof-db                  2.67
  mscdriverservice        41.30.02.20
  mtt                     41.10.34.37
  ntp                     41.0.4.25
  openssh                 4.4p1-80.10.07.1.0
  openssl                 0.9.7l-80.10.07.1.0
  periase                 41.00.27.2
  peribim                 41.00.27.2
  periglobl               41.00.28.2
  psm                     41.20.202.11
  qos-monitor             41.0.0.165
  scd                     41.33.0.50
  software-management     41.20.001.158
  startup-profile         41.20.07.117
  utps                    41.280.0.12
  voicemail               41.02.53.22
  voicemail-turkish       41.02.06.23

Constituent Updates:
  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.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.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 Patches
   - BCM.R400.046-SoftwareManagement or later must be applied before this update to prevent a premature "Update Complete" message

   Product Dependencies: None

Size: ME >

System Impact: 
   Time to apply approximately 5 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: None

Limitations: 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


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 patch is being installed.
- The DiaLogger and SysLogListener applications will also be restarted. Some alarms 
  may be missed while the patch is applied

Patch Removable: No


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

This patch 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 patch includes fixes to make the Element Manager Vista compatible.

The following issues are addressed.

- Critical alarms appear when APPP patch is installed and BCM rebooted.
  The following alarms appear on every reboot of the BCM after the patch 
  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 patch 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 patch 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 patch 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 patch 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 patch 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.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.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.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.104-QOS Description:
--------------------------------------------

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


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 patch to have more IVR alarms available, there is
  a requirement to reboot the system. This is no longer necessary.
  Q01645481


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 patch may be required at that time if further 
  changes are made to the DST regimen.
  Q01502789-02


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 patch 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.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.099-CDR Description:
--------------------------------------------

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


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 patch 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.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 patch 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 patch 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 patch 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 patch 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 begin ning 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 patch 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 patch 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 patch 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 patch 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 patch fixes the issue by sending the proper location parameter in the
  progress message.
  Q01440544-02

- ADID image need to be picked up.
  This patch 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.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.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.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 patch 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 patch also fixes the QoS logging to the file qmon.log found in the BCM 4.0 logs.
  Without this patch the BCM 4.0 would incorrectly log the QoS statistics as perceived by the
  far end. It would log them as zero. After this patch 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 patch 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.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 patch resolves the issue of disk
  space exhaustion.
  Q01529404-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 patch applied will 
        revert the ownership of the files. A new backup should be taken 
        after applying this patch.
  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 patch applied will 
        revert the ownership of the folders. A new backup should be taken 
        after applying this patch.
  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 patch applied will 
        revert the permissions of the folders. A new backup should be taken 
        after applying this patch.
  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 patch.
  Q01475874

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.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 patch.
  Q01475874

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.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 patch corrects the problem adding the 
  NONE option to Element Manger. 
  Q01500035 & Q01531731


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 


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

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

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


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


BCM.R400.032-PSM-1.0-1.0
------------------------
1. Duplicate Files
  Fix file inconsistency and file(s) overwritten by duplicate tar files.
  Q01403599-05.

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

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

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

BCM.R400.033-SMG-1.0-1.3
------------------------
1. 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 patch 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 patch.
Q01224647, Q01301100

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

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

4 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

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

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

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

8. 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.034-IPTEL-1.1-1.0
--------------------------
1. 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

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

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

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

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

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


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

BCM.R400.035-CTI-1.1-1.2
------------------------

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


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.066-CDR Description:
---------------------------------------------

- CDR multi-party conference records are incorrect most of the time.
  This patch 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 patch 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 patch 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 patch resolves the issue of EM closing when the CDR option is selected in 
   Element Manager.
  Q01486203

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


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


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

BCM.R400.SU.System.004-200710





