Software Update Name: BCM050.SU.System.008-200806

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

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

Category: GEN

Installation Recommendations:
This update should be applied to all new installs of BCM50 R1 and SRG50 R1. 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: 
   backup-recovery              2.25.0
   backup-restore-provider      2.24.0
   bcmEMcartridge               BCM50.3.22
   bsp-dsp                      40.206.50.9-16
   bsp-fpga                     25-1
   bsp-u-boot                   2.04.02-6
   cdr                          40.1.08.10
   cdr-client                   40.1.08.10
   cdr-provider                 40.1.08.10
   cfs                          40.1.1.19-15
   configfs                     2.27.0-15
   core-telephony               40.02.45.8 
   (Internal Software version code: 30DfC43)
   core-telephony-provider      40.0.12.96
   cte                          7.0.1.04.a-15
   cti                          40.70.11.1
   dcm-provider                 40.0.7.85-15
   dialogger                    2.04.1-3
   dsp-firmware                 40.290.160.9
   feps                         40.380.1.33
   glibc                        2.3.2-50.7.9.6.1_2007k
   host-provider                1.27.0 
   hotdesking                   40.004.00.59-15
   inventory-provider           2.57.0-1
   iptelephony                  2.03.0-15
   iptelprovideragent           40.270.5.43
   jbsm                         40.30.7.56-15
   lan-cte-provider             7.0.1.04.a-15
   license-provider             40.0.7.95
   mgs                          40.140.3.3
   mgspdr                       40.10.23.57-15
   modemcc                      40.15.00.99-15
   monit                        4.4-9
   mps                          40.80.6.34-15
   mpsmi                        40.120.4.35
   msm                          40.3.0.26
   openssh                      4.4p1-50.7.9.6.1
   openssl                      0.9.7l-50.7.9.6.1
   openwbem                     2.83.0
   osa                          2.04.1-1
   psm                          4805.2.06.1
   scd                          40.1.06.10
   ras-provider                 3.1-15
   snmp-agent                   4.1.0.3.01
   snmp-provider                40.1.26
   software-managment           2.45.0
   software-managment-flag      1
   software-managment-provider  2.29.0
   srg                          40.50.60.51
   srg-remove                   1.0
   startup-profile              1.0-25
   system-provider              2.29.0-15
   timezonesetting-provider     2.72.0-3
   utps                         40.090.4.12
   voicemail                    10.01.00.22

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

  New updates for this SU:
  ---------------------------

   BCM050.192-DSP-FIRMWARE
   BCM050.189-SRG-REMOVE
   BCM050.188-CORE
   BCM050.187-GLIBC
   BCM050.185-FEPS

  Updates from previous SU:
  ------------------------------
   BCM050.183-FEPS
   BCM050.182-CORE
   BCM050.181-FEPS
   BCM050.179-VISTA 
   BCM050.178-SNMP
   BCM050.175-GLIBC
   BCM050.172-VOICEMAIL
   BCM050.171-CORE
   BCM050.155-OPENSSH-OPENSSL
   BCM050.168-CTI
   BCM050.167-CORE
   BCM050.161-MSM
   BCM050.162-CDR
   BCM050.154-SOFTWARE-MANAGEMENT
   BCM050.158-SU3
   BCM050.157-CTI
   BCM050.156-CORE
   BCM050.152-OAM
   BCM050.145-DSP-FIRMWARE
   BCM050.144-VOICEMAIL
   BCM050.101-INVENTORY-PROVIDER
   BCM050.099-SRG

Product Dependencies: None

Size: 52MB

Size of changed content since last Smart Update: 23MB

System Impact: 
   Time to apply approximately 15 minutes.

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

Other: 
   Installation of the update will cause all telephony services to cease 
   during this time. The services will restart automatically after the 
   update installs. Voicemail is shut down for the period when this update
   is being applied.
 
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 
daylight savings time to standard time in Australia. The time on the BCM and displayed 
on sets is correct at all times. 

Update Removable: No


Software Update BCM050.192-DSP-FIRMWARE Description:
---------------------------------------------------

- Voicemail message cuts off when in a noisy environment
  This update corrects the issue by updating the tones' definitions 
  exactly as per the dialtone specifications for the UK.
  Q01850128


Software Update BCM050.189-SRG-REMOVE Description:
-------------------------------------------------

- SRGP patch prevents successful upgrade to SRG50 3.0
  BCM50 R1 systems that were converted to SRG by applying the 
  SRGP-2.20-2.01 update cannot be upgraded to SRG50 R3. Before 
  starting to upgrade these systems, apply this update first to 
  prevent the upgrade from failing.
  Q01817371


Software Update BCM050.188-CORE Description:
-------------------------------------------

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

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

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

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

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


Software Update BCM050.187-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-01


Software Update BCM050.185-FEPS Description:
-------------------------------------------

- BCM H323 outbound calls to mobile phones in China did not get through 
  Connecting to a mobile phone in China can take up to 12 seconds. But the current 
  setting of response timeout value for Q931 SETUP messages was 5 seconds. Therefore, 
  BCM H323 outbound calls to mobile phones were released during setup by the Radvision 
  stack after the 5 second timeout. The solution is to increase the timeout value to
  15 seconds.
  Q01810385-01


Software Update BCM050.183-FEPS 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-02


Software Update BCM050.182-CORE Description:
--------------------------------------------

- BCM Delay in sending NAM on DPNSS Link
  Incoming DPNSS calls on Feature-Net Embark circuit rings
  the destination set immediately. However, the calling party
  hears ringback approximately three seconds later.
  Q01428057-02

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

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

- No CLID and Unexpected Callback on GATM8
  No calling line ID information is displayed for incoming analog calls on
  the GATM8 media bay module. After the answered call is released, the
  trunk starts alerting the set again even though no new incoming call
  has been made.
  Q01589063-03

- GATM2 rev F Lines show as "Not in Service" in AUS Dip Switch mode.
  When the new GATM2 hardware with Rev-F support is installed in DIP
  switch mode in the Australian market, the GATM2 MBM will not come
  up, and lines will show as "Not In Service"
  Q01624801-06

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

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

- Redirect information is incorrect after Blind Transfer when TRO is enabled
  An incoming PRI call is tandemed from a CS1000 via VoIP to a BCM where it is
  answered. The BCM transfers the call to a second CS1000 via VoIP trunk where
  the call is "forward all calls" back to Centralized Voice mail on the first
  CS1000. When TRO is invoked to optimize the VoIP trunks, the BCM sends incorrect
  redirection information to the first CS1000 so the transferred call lands in
  the general delivery mail box instead of the set mail box.
  Q01594717-01

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


Software Update BCM050.181-FEPS 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-03 

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

- User is unable to make adjustments to ringing volume via Feature *80. 
  After an active voice call involving IPSets, adjustment to the ringing 
  volume via Feature *80 was not possible.
  This patch ensures that the adjustments to ringing volume can be made. 
  Q01672005

- Failure to switch to T.38 mode in tandem scenario.
  The VoIP Gateway did not properly forward the T.38 capabilities of each
  endpoint involved in each leg of the tandem, and so caused the switch to
  T.38 to fail.
  Q00905442-02

- T.38 settings changes not picked up until VoIP Gateway restarted.
  Changes to the T.38 Fax Support were only detected by the VoIP Gateway during
  initialization instead of at call time.
  Q01487793-01

- The 'Force G.711 for 3.1KHz Audio' feature will only be activated if 'T.38 Fax Support' 
  is also activated.
  The 'Force G.711 for 3.1KHz Audio' feature should not require that the 'T.38 Fax Support'
  feature be enabled, as these two features are mutually exclusive.
  Q01491995-03

- GatekeeperRoutedNonRAS gatekeeper ping mechanism appears as security risk
  in some networks.
  When the VoIP Gateway is in a GatekeeperRoutedNonRAS mode, it sends ICMP pings
  to the configured gatekeeper. Some networks cannot support the receipt of such pings
  as this looks like a DOS attack and is blocked by some firewalls.
  Q01497975-01

- VoIP Gateway crash upon receiving gatekeeper admission confirmation after call release.
  When the VoIP Gateway is configured to use Gatekeeper call signaling, and
  the admission confirmation is received after the call is released, the VoIP Gateway
  would generate an exception.
  Q01524349-03

- No speech path upon retrieving parked call, or taking call off hold.
  The VoIP Gateway would fail to trigger codec renegotiation when switching to a 
  media path using a different payload size.
  Q01540598-01

- Intermittent no speech path for VoIP calls transferred by auto-attendant.
  Upon the auto-attendant redirecting the call, the VoIP Gateway sometimes would
  receive a NULL TerminalCapabilitySet at the same time that it sends an
  OpenLogicalChannel request, resulting in failure to re-establish media path.
  Q01542458-01

- In GatekeeperRoutedNonRAS mode, Element Manager displays a status of
  "Running ..." even if the gatekeeper is not accessible. If the gatekeeper becomes
  not accessible after VoIP Gateway startup, then the VoIP Gateway would display
  a status of "Running..." instead of "Attempting to discover the gatekeeper at ". 
  Note that in GatekeeperRoutedNonRas mode, 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.
  Q01570430-01
  Q01729819

- IP trunk hangs upon an incoming call with no codecs in common.
  After having rejected an incoming call due to a codec mismatch between the
  two H.323 endpoints, the VoIP Gateway would not properly release the IP Trunk.
  Q01589331-01

- FEPS crash upon receiving a GatekeeperReject with unspecified reject reason.
  The VoIP Gateway failed to check if the received GatekeeperReject reason was 
  within its expected range of values and so generated an exception upon receiving 
  an unexpected value.
  Q01592829-01

- VoIP Gateway displays incorrect status
  Upon changing the VoIP Gateway Call Signaling method, or Gatekeeper IP address,
  the VoIP Gateway status would continually display 'Shutting down' status when in
  GatekeeperRoutedNonRas mode, if no backup gatekeeper was configured.
  Q01612881-01

- Intermittent no voice path after BCM does a CFB and CFNA over VoIP to H323 
  Gateway that only provides fastStart in the CONNECT.
  Upon media path renegotiation on one leg of a tandem call, the BCM would sometimes
  fail to renegotiate media path on the second leg of the call, resulting in no speech path.
  Q01618839

- T.38 Fax calls cause MGS to generate critical alarm 53011.
  Media paths for T.38 fax calls have their rtp port set to 0, and this
  was causing MGS to generate alarm 53011 instead of ignoring it.
  Q01403054-01

- Intermittent VoIP Trunk lockup issue.
  In certain scenarios the VoIP Gateway does not get an H245 Connected event 
  from the Radvision stack. This puts the VoIP Gateway into a state in which it 
  does not properly clean up the IP trunk when the call is released, and hence 
  the IP trunk hangs.
  Q01677167

- VoIP Gateway not switching to G.711 when 'Force G.711 for 3.1 KHz Audio' is enabled
  As a result of the VoIP Gateway not correctly detecting the bearerCapability for 
  an outgoing VoIP call, it was not forcing G.711 as the preferred codec if the 
  'Force G.711 for 3.1 KHz Audio' feature was enabled.
  Q01718665


Software Update BCM050.179-VISTA Description:
---------------------------------------------

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

- 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 BCM050.178-SNMP Description:
-------------------------------------------

- Alarm 11202 Low Memory 
  When using Solar Wind to monitor SNMP traps, a memory leak can occur causing alarm 
  11202 low memory.  This patch corrects the memory leak. 
  Q01589266

- SNMP Agent times out.
  If Administrator Access and SNMP Trap Destinations both define the same 
  community string, SNMP v2 MIB browser queries will time out.
  Q01666376


Software Update BCM050.175-GLIBC Description:
--------------------------------------------

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


Software Update BCM050.172-VOICEMAIL Description:
------------------------------------------------

- Voicemail reboots due to abnormal termination of request to a Fax service.
  Symptom is that voicemail reboots continuously when the fax print request is 
  terminated abnormally or voicemail fails to add fax files to the send 
  list. Problem was due to the 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 a valid handle.
  Q01668702

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

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


Software Update BCM050.171-CORE Description:
-------------------------------------------

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

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

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

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


Software Update BCM050.155-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 BCM50 R1 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, so a subsequent patch may be required at that time if further 
  changes are made to the DST regimen.
  Q01502789


Software Update BCM050.168-CTI Description:
------------------------------------------

- Problems With Silent Monitor
  Intermittently, while silent monitoring the agent, the supervisor will lose
  voice path with the agent. This 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 the Release/Feature keys in the silent monitor
  initiation state.
  Q01650109


Software Update BCM050.167-CORE Description:
-------------------------------------------

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

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

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

- Redirected Calls Fwd on PRI to DMS DID trunks may not hear ringback.
  This solution corrects a PRI NI-2 specification compliance
  issue which may result in the calling party not hearing ringback
  on tandemed calls.
  Q01094224-05

- Cut & Paste button programming causes loss of intercom keys
  Intercom keys have been replaced by autodial keys when they have 
  been cut & pasted keys using Element Manager. When this happens,
  users are not able to make any calls.
  Q01521070-01

- Network billing is incorrect in tandem call forward scenario
  from BCM50 to an 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

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


Software Update BCM050.161-MSM Description:
------------------------------------------

- BCM Monitor unable to connect
  The BCM Monitor would intermittently display an "Unable to Connect - 
  Error 80011" error message and experience loss of functionality.
  Q01616854


Software Update BCM050.162-CDR Description:
------------------------------------------

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

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

- CDR Pull Client will only work to default destination folder.
This patch resolves the issue of installing the CDR Client to different
paths and different drives on a Client system.
Q01529733-03

- Improper reporting in Norstar record format for incoming PRI-NI calls
This patch resolves the issue of improper reporting of source or
destination information for incoming PRI-NI calls when the Norstar
record format is used.
Q01405973.


Software Update BCM050.154-SOFTWARE-MANAGEMENT Description:
----------------------------------------------------------

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

- 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

- More robust multi-package patches.
Allow a patch to be applied even if some component package of that patch is
superseded by the version of that component on the BCM. Previously this
condition would cause a patch to fail.

- Unable to apply patches via FTP
In some instances, patches being applied via an FTP server would fail. This
occurs when the FTP server is configured to perform reverse-DNS lookup on
incoming requests, and where the BCM being patched is not known to the domain
name server.
Q01203639


Software Update BCM050.158-SU3  Description:
----------------------------------------------------------

- Approximately 37 days after installation of a BCM50, if there is
no system reboot (continuous operation without power cycling), the customer
will observe the generation of a critical alarm on the BCM50. At this time,
the ability to manage changes to keycode settings will no longer work
correctly. All other system functionality is unaffected. This issue is caused
by an internal open file resource leak that results in running out of system
file resources for this process. The patch will correct that resource leak.

- This patch updates both the CDR Server and CDR Client components
to address an issue with backwards compatibility of the CDR Pull capability.

- Refer to Bulletin Number P-2005-0321-Global for Survivable Remote Gateway 
(SRG) BCM50 R1 Patch

- This patch includes changes to both server and client sides of
Lan Cte. As a result, client PCs will need to uninstall current versions of
Lan Cte Client software, download and reinstall it once this patch is
completed.

- In the France Profile it is not possible to program Destcodes via
Element Manager.
Q01229280

- This patch will enable an SNMP manager application or an SNMP MIB
browser to view ipAddrTable, ipRouteTable and ipNetToMediaTable (all from RFC
1213) which were previously not viewable.
Q01249896

- After a Level 1 reset, it is not possible to dial into the BCM50
soft modem. The modem answers but it does not complete the handshake and the
connection attempt always fails. The issue will only occur after a Level 1
reset because the recovery modem configuration files are incorrect. This
patch replaces the current modem configuration files if required and ensures
that any subsequent Level 1 reset will maintain the correct versions of the
modem configuration files.
Installation instructions:
Given the nature of this issue, if you are able to apply this patch over a
modem connection, the BCM has not had a Level 1 reset which is Case 2 below.
Case 1:
If the BCM has had a Level 1 reset, then the modem configuration files will be
replaced and modem settings will default. If you have customized the modem
settings, you will have to reprogram the settings after the patch is applied.
The modem is configured in the Element Manager under Configuration,
Administrator Access, Modem. After installation of this patch, it is
recommended that a back up of system be scheduled.
Case 2:
If the BCM has not had a Level 1 reset, the n the current modem configuration
files will not be replaced and your modem settings will be maintained.
Q01147853

- This patch introduces a new feature. It is now possible to route an
incoming call to the modem based on the calling number (CLID/ANI). Via the
Element Manager in the Modem Dial-In panel, a calling number can be
programmed. This field will accept a phone number up to 26 digits in length.
The BCM50 will redirect calls from this number to the Modem after the number
of rings specified in the 'Number of rings' field.
The system will redirect an incoming call to the Modem DN if either:
- The call is presented on the line specified by the 'Line' field. In this
case, the call will be redirected after the system has counted the number
of rings specified by the 'Number of Rings' field.
- The calling number (CLID/ANI) of the call matches the 'Calling Number' field
and the calling Number field is not blank. In this case the call will be
redirected after the system has counted the number of rings specified by the
'Number of Rings' field where the counting starts once the calling number has
been received. The calling number maybe received from the network at different
times depending on the type of trunks and/or the market.
The line that the modem call is on may "AppearOnly" or "Appear&Ring" or
"RingOnly" at one or more sets. These sets will ring (if "Appear&Ring" or
"RingOnly" is set) and will show the line in use (if "AppearOnly" or
"Appear&Ring" is set) after the call is redirected to the modem DN and the
modem answers the call.
If Auto-Attendant is configured to answer the line, the number of rings in the
CallPilot lines table should be set high enough such that Auto-Attendant will
not answer the call before it is redirected to the Modem.

- Call Pilot and Call Centre can stop working if a Hunt Group Call is being
bounced between one of those applications and the Hunt Group Queue. An
example would be an incoming call being answered by Auto-Attendant and
transferred to a Hunt Group which has no agents available to answer the call.
In this case, the call will bounce back to the Auto-Attendant and it can be
transferred back again to the Hunt Group.
Q01096293

- Lines are not automatically released when disconnected at the far end when
connected to a voice port or a Control DN. Voice Ports and Control DN are
under the control of Voice Mail and Call Centre. Certain types of lines will
not disconnect immediately when a caller disconnects the call. This feature
is to allow the far-end of the call to play a message to the caller (eg. Thank
you for calling us...). When a voice port or a Control DN is connected to
that type of lines, the call should be released immediately as there those
applications don't have the capability to play messages in such cases.
Q011 37108

- Alarm 391 cannot be generated for UTPS packet loss on IP terminal
Q01137772

- Time Service Event 6003 Inactive on BCM50 R1
Q01136800

- "B RIM is primary clock instead of DTM" alarm NOT reported when DTM-PRI is
used
Q01133248

- Grammar Error on GUI, SNMP text string for PSM Event 11409
Q01136341

- USB failure alarms need more detail in resolution field or in description
field
Q01139367

- AlarmID 17015 generated when enable or disable modem using SSBA
Q01158634

- SNMP strings/EM alarms for Local/Remote Temps not equal to Master Alarms
List
Q01132292

- Monit not generating recovery message when you killall CoreTel
Q01071084

- FES Router alarms on busy system
On busy systems the Fast Ethernet Switch may fail to respond to the periodic
queries from the Platform Status Monitor (PSM). This resulted in erroneous
alarms suggesting that the router (whether present or not) might be defective,
and that a LAN port has gone down. This patch corrects that behavior.
Q01386802

- H.450.2 Radvision resource leaks during H.450.2 transfers
A Radvision stack resource was leaked for each H.450.2 transfer that occurred.
Once these resources had all become exhausted (about 200 transfers), H.450.2
transfers began to fail.
Q01457336

- IP trunks may not release after a call.
A race condition exists between CoreTel and FEPS such that IP trunk release
messaging between the two components may not be sent or received correctly
thus the IP trunk would not be released.
Q01376136

- Gatekeeper deregistration problem
In the case in which the primary gatekeeper became unavailable, and the
discovery of a backup GK failed, the VoIP gateway would fail to switch back
to attempting to register with the primary gatekeeper. Also in this scenario,
the VoIP gateway would stop attempting to register with the backup gatekeeper
after 350 attempts due to a Radvision resource leak.
Q01404705-01

- FEPS intermittent crashes
Under certain timing scenarios, MPSMI was attempting to reference a media path
that had just been closed, and as a result could cause the VoIP components
MGS, UTPS, or FEPS to crash.
Q01452376

- BCM50R1 losing up to 14 minutes per day.
Resolves the BCM50 Time of Day Clock Slip as described in Nortel Technical
Bulletin 2006007430.
Q01475884

- The FS288 interface between a BCM50 main unit and a BCM50e expansion unit
may experience bit errors with some cable lengths within the allowed range of
0m to 10m. This can lead to system slowdowns and lockups of TDM phones. The
standard 1m shielded cable that is included with the BCM50e expansion unit is
not affected. Random errors that occur at all cable lengths due to noise may
also produce signaling and voice errors, although these are usually only
noticeable in the /var/log/messages log. The FPGA update allows the interface
to function correctly at all cable lengths from 0m to 10, as well as reducing
noise susceptibility.
Q01422219

- BCM50 system freezes after 248 days of continuous service
A bug in a low-level timer utility function caused BCM50s to freeze after 248
days of uninterrupted service. This patch corrects that error.
Q01501221

- BCM50 memory leak
A very minor memory leak in a low-level utility function is eliminated.
Q01409447-01


Software Update BCM050.157-CTI Description:
------------------------------------------

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

- Support for New Zealand Market Profile
This update contributes to providing support for the New Zealand Market
Profile introduced by BCM050.139-CORE.
Q01511603

Note: Although not strict dependencies, in order to fully support the
New Zealand Market Profile, this patch must be applied
together with the following other patches:
  - BCM050.152-OAM or later
  - BCM050.156-CORE or later
  - BCM050.144- VOICEMAIL or later
  - BCM050.145-DSP-FIRMWARE or later

- DTMF Tones not recognized by BCM50 CallPilot:
BCM50 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 BCM50 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 in the
Element Manager.
Q01445406

- Mailboxes with outbound notification cannot respond to message DTMF
An external caller leaves a message in a mailbox that has been configured
with off-premise message notification (OPMN) to an external number. If a
call is placed to the external number when a new message is received, the
user receives the call, and then tries to log into the mailbox but it does
not respond to DTMF tones.
Q01401361-02

- When using the park and page feature, the recorded voice prompt is played
at a very low volume and it cannot be increased
The loss plan used earlier had the same volume gain for both sets and the
external speakers resulting in a low volume for the external paging. This
update corrects the problem by adjusting the loss plan only to PAGING using
EXTERNAL SPEAKER by a gain value of 4 to boost the volume. Volume gain is
not applicable to the set or to the set+speaker combination.
Q01427954

- OPMN Reply to external number from external location not working:
An external caller leaves a message at a mail box that has been configured
with off-premise message notification (OPMN) to an external number. A call
is placed to the external number when a new message is received. User
receives the call, logs into the mailbox and listens to the message. When
pressing 9 to Reply by calling the message sender, the OPMN call is put on
hold and a few seconds later the user hears "The Routing information for
this call is not valid" and mailbox options are replayed. The External
call goes through but after one ring, the call drops.
Q01325674-01

- Call Pilot and Call Centre can stop working if a Hunt Group Call is
being bounced between one of those applications and the Hunt Group Queue.
An example would be an incoming call being answered by Auto-Attendant and
transferred to a Hunt Group which has no agents available to answer the call.
In this case, the call will bounce back to the Auto-Attendant and it can
be transferred back again to the Hunt Group.
Q01096293

- Lines are not automatically released when disconnected at the far end when
connected to a voice port or a Control DN. Voice Ports and Control DN are
under the control of Voice Mail and Call Centre. Certain types of lines
will not disconnect immediately when a caller disconnects the call.
This feature is to allow the far-end of the call to play a message to the
caller (e.g. Thank you for calling us...). When a voice port or a Control
DN is connected to that type of line, the call should be released
immediately as there those applications don't have the capability to play
messages in such cases.
Q01137108

- Voice Mail and Call Centre can stop working when the far end of a call
connected to those applications via a digital line disconnects at the
same time as the application. An example of when this problem is most
likely to happen is when a fax transmission is completed between a fax
machine and Voice Mail.
Q01197815

- Transferring manually a call to the modem can fail. If the incoming call
that was answered came in on a line that was programmed to be answered by
the Auto-Attendant, it cannot be manually transferred to the modem for
about 30 to 45 seconds.
Q01259566

- The System can crash or severely misbehave after a long period of use if
the Modem or Auto-Attendant were programmed to answer after one ring or more.
A component is leaking memory every time there is a ring to be counted for
Auto-Attendant or the Modem (but not Call Centre). Eventually, the system
will run low on available memory and it will cause alarms to be raised and
possibly failure on some system features or potentially a system crash. If
the system is restarted (power outage or soft reset), the memory will be
recovered.
Q01279912-01

- Calls on Target Lines using only Private Received Digits don't work in a
Centralized Voice Mail system. If a customer programs only Private Received
digits for the Target Line to be answered by Voice Mail for Centralized
Voice Mail (the received digits having to match the Voice Mail DN),
Voice Mail will answer the call with the Centralized Auto-Attendant service
instead of the Centralized Voice Mail service. This problem doesn't occur
of the Public Received Digits are also programmed for that same Target Line.
Q01295164-01


Software Update BCM050.156-CORE Description:
-------------------------------------------

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

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

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

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

- 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

- Enbloc sending on BRI after Core Patch BCM050.139-CORE-3.3-1.1
Outgoing ETSI BRI calls cannot be configured as overlap sending.
All outgoing calls are using enbloc dialing.
Q01523153

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

- Not able to dial out on 2nd PRI if both spans are in one line pool
The customer is not able to dial out on 2nd ETSI PRI if both PRIs are 
in the same pool. The CBC throttling feature was unintentionally affecting 
the ETSI Euro trunks.
Q01301542-01

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

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

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

- 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

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

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

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

- Cannot make conference calls
Attempts to set up a 3 party conference may occasionally result in
'conference busy' being displayed on the customer's set.
Q01411102-02

- ISDN clocking, event, & alarms incorrectly generated
When layer 1 alarms are raised for Primary rate interface connection 
the message parameters do not indicate the bus number of the offending 
digital trunk module.
Q01465611-02

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

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

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

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

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

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

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

- Calls over 2 T1 E&M trunks have 1-way speech
Incoming calls on T1 E&M which tandem over a T1 E&M trunk to a destination
switch receives 1 way speech path when the calls are answered
Q01317384-03

- Logevent 247 message has no parameters
This solution introduces additional diagnostic code allowing the design
team to better diagnose possible hardware errors reported from the field.
Q01328192

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

- Line and set restrictions bypassed (Fraud)
This solution makes the F**OPTION feature available in the Element Manager. 
This feature was previously only available through set based UI. F**OPTION 
allows the user to activate additional toll fraud protection at problematic
customer sites.
Q01318719-03

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

- Core Hunt Group Metrics incorrect in reroute scenario
The Hunt Group metrics on the core are incorrectly counting the number of calls 
and abandoned calls in the scenario involving a call transfer
Q01328892-01

- BCM with supervised ROI lines drop out on answer in Australia profile
New functionality is added to support reversal on seize for analog trunks in 
the Australian market.
Q0117 6599

- BCM - ETSI Euro PRI will not connect to New Zealand ISDN
This adds a New Zealand market profile to the BCM50 Release 1. It also allows 
the users in that market to select the B-channel for outgoing calls if required. 
The ETSI Euro PRI protocol normally does not support B-channel selection by the 
PBX for outgoing calls, rather the PSTN decides which B-channel should be used. 
This change is specific to the New Zealand market.
Q01308779-05

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

- Call cutoffs: 310 errors
This change was made to minimize occurrence of an error which was being
seen at a central office. When an outgoing call is made and the CO does
not respond, we now send a release to the PSTN. The NI-2 specification
does not require the PBX to send a release to the network. This change
was implemented because in this scenario, a particular CO was locking
up the trunks and not releasing PRI call references.
Q01244275

- Intermittent call drop
The MCDN protocol is not able to handle PRI layer 3 messages where the location 
information element has a value other than 0. This results in a dropped call on 
tandems with the NI-2 PRI links where these other location IE values are supported.
Q01383499

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

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

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

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

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

- GATM line Tuning fails
The GATM fails to complete Line tuning when initialized.
This can result in improper loss levels, and possible echo
on analog trunk calls.
Q01444242-03

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

- Problem with incoming calls on PRI trunk
Incoming calls over PRI trunk to a BCM at site A that tandem out via T1 E&M
to a BCM at site B drop if it's not answered within 2 rings and the phone
display shows: Invalid num 28Problem with incoming calls on PRI
Q01392178-03

- Using digit zero for network PSTN access does not work
In the German market the digit 0 is used to access the public
network. When 2 BCMs are networked together and a tandem call
attempt is made to the public network, the tandem does not complete.
The call rings to the prime set of the tandem node.
Q01410932-03

- BCM - ETSI Euro PRI will not connect to New Zealand ISDN
Currently the ISDN protocol used in New Zealand does not request a B-channel
when outgoing calls are made. The CO indicates which B-channel to use when it
responds to the seize request. The New Zealand market is introducing a new
product that requires the B-channel to be specified when a line to the network
is seized. This enhancement implements the functionality. New prompts for the
B-channel sequence are now visible for ETSI EURO PRI protocol.
Options are: None, Ascending and Descending.
Q01308779

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

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

- VoIP lines go busy. This resolves an issue where outgoing calls which were
released before the far end answers causes a VoIP trunk to lock up and become
unusable. The root cause lies with the VoIP trunk release protocol. The
following patch is also required as part of this solution:
- BCM050.065-VOIPGATEWAY-IPTELPROVI DERAGENT-1.1-1.0 or higher
Q01120093-03

- Q01247102 GASM8+MBM will not boot
- Q01101726 Cannot call out on idle T1 EAM, auto answer channel.
- Q01222053 BRI terminal gets incorrect call treatment when T1 lines are unavailable.
- Q01178926 Tandem call MCDN to PSTN and disconnects if the call goes to VM.
- Update to MCDN protocol to accept a PROGRESS message in a Call Delivered state.
- Q01229855 Daily schedules are not activated correctly. This is caused by the day of 
the week not being reset correctly when system.
- Q01273213 No CONNECT PI Out
- Q01184612 Hunt group overflow call is returning to AA after 1 ring.
- Q01200546 Protect against potential system crash due to uninitialized variable. 
Caused when MSM goes down as the system is booting.
- Q01019869 Hunt group set not ringing. After a specific call transfer
scenario, a hunt group set may no longer alert for hunt group calls.
- Q01229855 Reset day of the week when updating system time
- Q01247102 Stop-shipping Issue for GASM: ASM8+ will not boot [also Q01180514 Q01165379]
- Q01175385 Allow the transmission of DTMF tones on the BCM50 paging speaker
- Q01121305 Resolves a call disconnect issue when making a PRI/BRI 911 call to a
Lucent 5ESS switch having both PSAP (911) equipment installed and also supplying 
the end user's PRI/BRI service.
- Q01165773 Resolves an intermittent call disconnect issue with MCDN to PSTN calls
tandemed through an M1.
- Q01126447 UK GATM driver: Adds support for Algo dongle.
- Q01072877 Resolves intermittent ASM8+ port lock ups when connected to 3rd party
devices.
- Q01107104 Resolves tandem PRI-IP calls being dropped under heavy loads because of
a race condition during call release.
- Q01125596 Protect RADAR flow control against zero-length messages
- Q01121305 Add support for AT&T Call Queued cause value on BRI/PRI NI2 trunks
- Q01122222 Allow programming of CAP buttons without TCMI keycodes
- Q01120248 Make sure feature option gets defaulted on button change
- Q01129644 Fixing the gain control for GATIs to enable MOH.
- Q01133734 Correct the initialization order of srg_config to fix SRG IC keys
- Q01111249 Protect against a set Paste without a preceding Copy
- Q01112394 Reduce cache-out time from 30 min. to 5 min. to reduce data loss
- Q01113038 Handsfree & headset failed with prime line set for line pool [also Q01110207]
- Q01113326 Restore the SRG mode after switching market profiles
- Q01115435 Prevent fatal log 115 when checking the BRI loop clock source
- Q01100985 Fix SetPoolAccess to consider Bloc line pools 


Software Update BCM050.152-OAM Description:
------------------------------------------

- The Call By Call(CBC) Limits are visible in UK market for ETSI PRI.
This patch masked the CBC Limit prompt in Element Manager.
Q01544942

- For M7310 sets button programming through Element Manager
(configuration-> Telephony -> sets -> active sets -> Capabilities and 
preferences -> button programming ) does not work properly. EM shows 
labeling for "dual memory" buttons from 12 onwards instead of 11 for 
this type of set. It creates a mismatch between set based OAM and EM 
button count. Labeling for the buttons are corrected through this patch.
Q01453352

- Openwbem log file escapes logrotate control
When under stress conditions (dozens of logins per second, for many hours 
in a row), the openwbem server's log file can grow without limit. This 
causes other processes on the system to fail logging.
Q01386802

- Daylight Saving Time changes effective 2007
Legislated changes to the start and stop dates for Daylight Saving Time come
into effect in a number of jurisdictions starting in 2007. This patch updates
DST data on the BCM so that future transitions continue to be performed
automatically. Also, errors in some Asian time zones are corrected.
Q01248734

- Ignore in-band DTMF in RTP
On the "IP Trunk Settings" tab in the Element Manager, new option "Ignore
in-band DTMF in RTP" will appear. When selected, this will cause Voice CTI
applications including Voice Mail, IVR and Call Center, to ignore any in-band
tones received over a VoIP trunk call that are encoded in the RTP. This
setting is useful i.e. should be checked on when the far end is Call Server
2000 & Packet Voice Gateway (PVG) combination where the PVG is
provisioned for OOBDTMFSupp=FullSupport resulting in the PVG + CS2000 sending
out of band as well as in-band DTMF tones at the same time to the BCM. The
PVG MAY not send both tone notifications depending on whether the call is
using G711 and depending on what the SN0 version is. 
Q01376707-02

- Call forwarded over VOIP trunk is shown as connected when the far end hears
ring back tones.
An incoming call from the central office via the ETSI BRI trunk is forwarded
via BCM1 to BCM2 over VOIP trunk. In the protocol trace the call is shown as
being connected when the far end hears ring back tones. The above problem is
addressed in the above mentioned Core patch. This update provides a
configurable option in Element Manager to select the protocol type.
(Configuration->Telephony- > Loops; If the protocol is Euro, there will be a
Protocol Type "S-T user / "T-T user ) 
Q01296708-02

- Added Gateway Type "Other" In IP Trunks Routing Table
In the routing table the "GW Type" drop down list now allows the user to
select "Other". This can be used when the far end does not match any of the
existing listed types. However this should never be used if the far end is a BCM.
Q01325828


Software Update BCM050.145-DSP-FIRMWARE Description:
----------------------------------------------------

- Adding support for new market profile
When the new market profile for New Zealand was implemented by patch BCM050.139-CORE, 
some additional changes to the DSP were required. 
Q01308779-07

- BCM - ETSI Euro PRI will not connect to New Zealand ISDN
This adds DSP support for a New Zealand market profile to the BCM50 Release 1. In 
conjunction with BCM050.139-CORE and BCM050.138-OAM, it allows the users in that 
market to select the B-channel for outgoing calls if required. The ETSI Euro PRI 
protocol normally does not support B-channel selection by the PBX for outgoing calls, 
rather the PSTN decides which B-channel should be used. This change is specific to 
the New Zealand market.
Q01308779-05

- Clicking noise when seizing outside line.
Some CO lines experience a surge on batteries or line reversal significantly late in 
the off-hook state, causing an audible "click" on going off-hook.
Q01463425

- Voicemail messages cut out after 10 seconds
This intermittent problem is caused by false detection of call progress tones in the 
Spanish market profile. The problem is addressed by tightening the detection parameters 
of the Spanish overflow tone.
Q01419082-02

- Echo on Analog Trunks
This change will improve echo canceller performance on analog trunks with low echo 
return loss.
This change modifies the thresholds used for the echo canceller's doubletalk detection 
to tolerate gain added by the lossplan on analog trunks. The improvements in ECAN 
performance are in the following two areas:
1) Echo canceller training over trunks with poor echo return loss will be improved. 
This will result in less echo during doubletalk conditions.
2) The echo canceller's Non-Linear Processor (NLP) will transition from singletalk to 
doubletalk at higher energy levels from the remote speaker. This change prevents echo 
that persists during singletalk conditions.
Q01414710

- T.38 Interop with CS1000
This patch addresses an interop issue with the CS1000 in which the timing between T.30 
control frame DCS and the modulation training check TCF for V.27ter can exceed the T.30 spec. 
This issue has been seen to cause problems on T.38 sessions which are tandemmed through 
Passport fax relay. When this problem occurs the Passport will fail to transmit the fax 
training check at 4800 or 2400 bps to the answering fax machine, and the fax session will 
fail. This issue has not been observed to cause problems for fax machines directly connected 
to the BCM or CS1000. According to T.38 the timing of the DCS and TCF should be recreated by 
the offramp CS1000 in this scenario. In this problem the timing is not being recreated by the 
CS1000; CR Q01344419 has been raised to track this issue with the CS1000. As a work-around to 
this problem this change is being made to the BCM to improve the performance.
Q01344419

- GATI: 800 Ohm DC termination while ringing
This change has been made to provide additional protection to analog trunk circuits when exposed 
to excessive ring trip current. The GATI ports will maintain an 800 ohm termination for the first 
300 milliseconds when they are placed off-hook. Following the 300 millisecond delay, the 
impedance is switched to 50 ohms.
Q01242182

- Tolerance to simultaneous reception of T.38 and RTP streams
In some cases the CS1000 continues to send RTP Voice frames following the set up of a T.38 session. 
If the RTP packets are received by the T.38 gateway on BCM, then the T.38 session will fail. In this 
patch additional checking is added to the T.38 endpoint to filter these RTP packets out.

- T.38 Tandemmed Sessions
On T.38 sessions which are tandemmed through Passport 6480 fax relay, NSF frames sent through the 
PP6480 are changed to V.21 preamble by the PP6480. This results in a preamble which exceeds the 
BCM's preamble timer. The most common symptom of the preamble timer expiry is the failure to 
establish any fax session through T.38. In this patch the preamble timer is extended to permit the 
extended preamble.

- Super G3 Compatibility
Super G3 (or V.34) fax is not supported over T.38, and an attempt to establish a V.34 fax session 
over T.38 will fail. In most cases, Super G3 will back off to use G3 fax if negotiation with another 
Super G3 fax machine fails. It is this back-off mechanism which is used by T.38 gateways to support 
Super G3 fax machines. In the case addressed by this patch the Super G3 fax machine uses the type of 
answer tone presented by the answering fax machine to determine if it will use V.34 fax or one of 
the Group 3 fax modulations.
To prevent originating Super G3 fax machines from attempting to use V.34 fax, the answer tone (either 
CED or ANSam) is blocked from being passed through the speech path. In the place of the answer tone 
generated by the answering fax machine, the VoIP task will pass a cons tant 2100Hz tone (CED). This 
change has the effect that the originating fax machine sees only the characteristics of a Group 3 fax 
machine, even if it is connected to a Super Group 3 fax machine.

- Westell T.38 Gateway Compatibility
The Westell T.38 gateway sends out multiple (15-20) PREAMBLE INDICATOR Packets to indicate the start 
of a T.30 v.21 handshaking signal. Normally in this situation a transmitting gateway will repeatedly
send a packet (for reliability), but the packet sequence number will not change. In the Westell case, 
the 15-20 repeated packets all have unique sequence numbers and are treated as the start of a new 
T.30 signal. This causes the BCM's T.38 fax session to fail. The fix for this condition was to ignore 
subsequent PREAMBLE INDICATORS until the current T.30 frame has ended. This change has no impact 
except in the specific failure case in which multiple preamble indicator packets are sent by the 
remote gateway.
Q01290071

- Echo on VoIP call IP Set progressively worse as the call went on.
This patch addresses problems with echo canceller performance including:
1) Excessive "Clipping" of the returned speech path.
2) Continuously audible echo. Both these problems are dependent on the CoreTel Lossplan, and are both 
errors in detecting doubletalk conditions.

The following changes have been made to address these problems:
1) Due to lossplan changes the ECAN's doubletalk detection can be relaxed. This change will reduce the 
amount of muting the ECAN's NLP introduces.
2) An additional test for doubletalk will prevent the NLP from muting the return echo path if the signal 
in the return path pre-existed the signal in the forward direction (the echo source). This reduces the 
likelihood of the NLP muting the return path while there's active speech in the path.
Q01136753


Software Update BCM050.144-VOICEMAIL Description:
------------------------------------------------

- Support for New Zealand Market Profile
This update contributes to providing support for the New Zealand Market Profile by core telephony.
Q01508815

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

- 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 the number to be dialed on the AMIS network is proper.
Q01440775

- Message delivery fails if the AMIS networking message is composed to 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 it to other recipients in the TO address list. The issue 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

- 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 resending AMIS message as per the number of retries configured in the AMIS retry page for cases 
where the Trunk drops the call in middle of an AMIS negotiation.
Q01448471

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

- Once all intercom paths are in use, no subsequent calls go to personal voicemail.
Once all intercom paths are in use, call placed on a target line cannot ring on the set & the call gets diverted 
to prime set. If the prime set is voicemail DN, general delivery mailbox answers the call rather the personal 
mailbox associated with the set.
Q01229950-04

- Auto Attendant stopped working on restore
Resolves a race condition, which causes a Voicemail port to become locked up when a paging is just started and at 
the same time as the far end disconnects the call. Symptom is that Voicemail service is running, but Voicemail 
(Auto Attendant in particular) is inaccessible. The Voice port can only be unlocked by a reboot or stopping/starting
the Voicemail service.
Q01326556

- Voicemail process restart causes resource leak
On the Voicemail restart, CFeature Status (CFS) cleanup is not called. This resulted in leaking one semaphore.
Q01119341

- MyPhone can no longer record greetings
Ability to record greetings ceases while using MyPhone. Symptoms is that if a DN is entered in voice window, Dial or 
Record or Play button is pressed, the DN does not ring.
Q01268892-01

Enhancement for Simultaneous ringing and continuous announcement at the attendant set. In addition, this patch 
introduces a new feature found in other Call Pilot products called "Service Directory Numbers" SDN's can be used 
to assign a variety of services, such as express messaging, name dialing, Auto Attendant and greeting tables, to 
a Directory Number. When a caller dials this DN, they connect to the various services that can be setup in the 
Service DN Table. Documentation for this new feature can be found through www.nortel.com/Support. On the support 
page, a search for the title "Call Pilot Setup and Operation Guide" will find the correct document. A new chapter, 
Chapter 11, has been added to provide feature details.

Q01267240 - Simultaneous Ring and Continuous Announcement
Q01105802-02 - Multiple fax pages sent to internal fax machine
Q01160532-01 - CallPilot Manager inaccessible
Q01220393-02 - Fax Overflow gives multiple blank


Software Update BCM050.101-INVENTORY-PROVIDER Description:
---------------------------------------------------------

- SRG systems with Cumulative Patch 1 applied display incorrect ID
  On SRG systems with CP1 applied, the Element Manager will display 
  "BCM50" rather than "SRG50" under Configuration>System>Identification> 
    Description, and General>Hardware Inventory>Model. 
  Q01362569


Software Update BCM050.099-SRG Description:
------------------------------------------

- SRG50 Support for IP sets 1120E, 1140E, i2212 (WLAN) and i2033 (Conference Phone). 
  The C1E firmware binary file named x24 is provided for 1120E set.
  The C1E firmware binary file named x25 is provided for the 1140E set.

- Upgraded firmware for i20xx sets.
  The D9H firmware binary file named x02.fw is provided for i20xx sets.

Issue Resolution Fixes:

- Fix for SRG sets staying in local mode after WAN outage, Main Office upgrade or reboot.
  This SRG patch solves the issue where sets remained in local mode after a WAN outage, 
  Main Office upgrade or reboot.  It also lessens the likelihood of SRG systems in a 
  large configuration flooding the NCS with messages during this scenario.
Q01164987, Q01306625

BCM050.090-SRG-1.1-1.0
----------------------
This patch allows an SRG50 IP Set redirected to the Main Office to receive a 
download of the recommended firmware from the Main Office.  With this patch 
an IP set will have the  recommended firmware from the SRG50 when it first 
registers to SRG.  It will then have the recommended firmware from the Main 
Office after the umsUpgradeAll command is manually requested at the Main Office.
After a umsUpgradeAll is requested, the recommended firmware from SRG50 is the 
recommended firmware from the Main Office. This patch does not allow an IP set 
to have a newer version of firmware than the SRG / Main Office.

(Please Note: umsUpgradeAll is a command invoked manually at the Main Office.  
This patch does not require the Main Office administrator to issue the command, 
it just provides SRG50 support should the Main Office administrator invoke the 
command.  Before this patch, the SRG50 did not support this download of 
firmware from the Main Office).
Q01335312

BCM050.038-SRG-1.0-1.0
----------------------
This patch is to include D9C Firmware binary in the SRG50 system. The file has 
been renamed as x02.fw and will come as part of the patch.


This update includes the content of the following superseded Smart Updates:
BCM050.SU.System.006-200801


