PRODUCT_LINE: BCM50
============================================

TITLE
=====

BCM050.R200.SU.System.015-200907

========================
Release: 2.0 Issue: N/A
Category: GEN
Superceded By: NONE
Release Date: 20090713
Patch Conflict(s): N/A
Special Instructions: YES
Patch Version: N/A
========================

Software Update Name: BCM050.R200.SU.System.015-200907

Applicable H/W Platforms: BCM50, BCM50a, BCM50e, BCM50b, BCM50ba, BCM50be, SRG50

Applicable S/W Platforms: 2.00.2.05e, SRG50 R2

Category: GEN

Installation Recommendations:
This update should be applied to all new installs of BCM50 R2 and SRG50 2.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:

   apache 2.0.63
   backup-recovery 42.2.28.10
   backup-restore-provider 42.2.1.91
   bcmEMcartridge BCM50.3.55
   bsp-fpga 42.1.26.136
   bsp-mtd 42.1.26.138
   btrace 42.2.6.14
   callpilot-provider 40.0.3.09
   cdr 41.2.07.10
   cdr-client 41.2.04.10
   cdr-provider 41.2.04.10
   cfs 42.1.21.19
   core-telephony 42.05.01.8
   core-telephony-provider 42.00.05.96
   cte 7.12.01.A
   cteapps-obt 42.00.04.98
   cti 42.07.06.1
   doorphone 42.2.6.127
   dsp-firmware 41.110.50.9
   feps 42.191.0.33
   gap 42.13.8.6
   glibc 2.3.2
   host-provider 40.1.27.0
   ipmusic 42.1.15.102
   iptelprovideragent 42.20.7.43
   lan-cte-provider 7.12.01.A
   mgs 42.60.7.3
   modemcc 42.02.01.142
   mof-db 2.60
   mpsmi 42.30.7.35
   nnu 42.1.10.15
   nnu-pdrd 42.1.10.15
   openssh 4.4p1
   openssl 0.9.7l
   scd 42.2.04.50
   security-provider 42.1.31.93
   snmp-agent 42.10.13.118
   snmp-provider 42.10.13.97
   software-management 42.00.05.158
   software-management-provider 42.2.00.162
   srg 42.00.06.51
   srg-remove 1.0
   utps 42.70.2.12
   voicemail 42.02.32.22
   voicemail-auenglish 42.00.43.23
   voicemail-turkish 42.00.44.23

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

New updates for this SU:
------------------------
BCM050.R200.147-CORE
BCM050.R200.144-CDR


Updates from previous SU:
-------------------------
BCM050.R200.145-VOICEMAIL
BCM050.R200.141-SOFTWARE-MANAGEMENT-PROVIDER
BCM050.R200.140-CORE
BCM050.R200.139-SRG
BCM050.R200.138-IPMUSIC
BCM050.R200.137-IPTEL
BCM050.R200.136-BSP
BCM050.R200.135-BACKUP-RECOVERY
BCM050.R200.134-CORE
BCM050.R200.131-CDR
BCM050.R200.130-APACHE
BCM050.R200.127-BSP
BCM050.R200.126-IPTEL
BCM050.R200.124-VOICEMAIL
BCM050.R200.123-DOORPHONE
BCM050.R200.121-CORE
BCM050.R200.120-DSPFIRMWARE 
BCM050.R200.117-OAM
BCM050.R200.116-GLIBC
BCM050.R200.114-SRG-REMOVE 
BCM050.R200.112-CORE
BCM050.R200.109-GAP
BCM050.R200.108-DSPFIRMWARE
BCM050.R200.105-CORE
BCM050.R200.104-OAM
BCM050.R200.103-SoftwareManagement
BCM050.R200.102-CORE
BCM050.R200.101-VOICEMAIL
BCM050.R200.098-DOORPHONE
BCM050.R200.095-IPTEL
BCM050.R200.094-APPP
BCM050.R200.092-BACKUP-RECOVERY
BCM050.R200.090-SRG
BCM050.R200.088-NNU
BCM050.R200.087-CDR
BCM050.R200.086-VISTA
BCM050.R200.085-IPTEL
BCM050.R200.080-SNMP
BCM050.R200.079-UTPS
BCM050.R200.077-VOICEMAIL
BCM050.R200.075-DSPFIRMWARE
BCM050.R200.074-CORE
BCM050.R200.073-GLIBC
BCM050.R200.067-CORE
BCM050.R200.066-BTRACE
BCM050.R200.065-DSPFIRMWARE
BCM050.R200.058-UTPS
BCM050.R200.057-CTI
BCM050.R200.055-TurkishPrompts
BCM050.R200.051-SRG
BCM050.R200.046-AustralianPrompts
BCM050.R200.045-BSP
BCM050.R200.044-CORE
BCM050.R200.041-IPM USIC
BCM050.R200.039-VOICEMAIL
BCM050.R200.037-UTPS
BCM050.R200.035-OAM
BCM050.R200.032-OPENSSH_OPENSSL
BCM050.R200.027-CTI
BCM050.R200.024-MODEMCC
BCM050.R200.021-CTE

Dependencies:
Required Updates: 
BCM050.R200.103-SoftwareManagement should be applied before this update

Product Dependencies: None

Size: 111.65 MB

Size of changed content since last Smart Update: 11MB

System Impact:
Time to apply approximately 15 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 this update force reboot:
Over last Cumulative Smart Update: Yes
Over default content: Yes
NOTE: this update will reboot in all cases.

Other Impacts: 
Doorphones will not be operational during update process.
VoiceMail will be shut down while the update is applied.
VoIP Trunks will be unusable during the application of the update.
IP Sets will reset during the application of the update.
If it is suspected that a UDP attack has already occurred on the BCM, 
then the BCM should be rebooted prior to applying this update in order 
for the update to apply properly.

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

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

3. This update DOES NOT remove CCR Tree 100. Update allows Telset user
to delete the CCR tree 100 after application. Removal of CCR Tree 100 is
manually performed after applying the update as follows:

1. Using f983, login with Telset user ID and Telset password to access
CallPilot Admin
2. Once accessed to Admin menu, select the "OTHR" (Other) Soft Key
3. Soft Keys should update and display "CCR" (Custom Call Routing)
Soft key, select the CCR Soft Key
4. While accessing CCR Admin, select the "ADMIN" (Administration)
Soft Key
5. When display shows "CCR tree:", enter 100 on Telset dial pad
6. Telset display should show; "Tree:100", if so depress the digit 8
on the dial pad. 
7. Display update should show; "Delete tree 100?", and Soft Keys
marked "YES" and "NO"
8. Select the "YES" Soft key to delete CCR tree 100

Mailboxes previously referencing CCR Tree 100 in error can now be deleted
via CallPilot Manager GUI or Telset. 


Update Removable: No


Software Update BCM050.R200.147-CORE  Description:
------------------------------------------------------

- Intermittent fast/busy on incoming PRI calls
Incoming DID calls on the PRI trunk may result in unexpected busy signals.
Sites with a PRI trunk may experience increased ISDN call processing error
with event id 799.
Q02007774

- B-channels go into lockout on PSTN facing PRI when using BCM or SRG as Network Edge Device 
Problem with B channels going into lockout on PRI. The problem is triggered by incoming calls. 
There are no reported issues when making outgoing calls. Disable of TAT (Anti-Trunk Tromboning) 
and reboot of the BCM resolves the condition. This corrective content addresses TAT/PRI interaction
Q02007774


BCM050.R200.146-CORE
--------------------

- Phantom outgoing calls ring at both far end and prime set
On an SRG system if far end does not send an alerting event in time, the call
will be disconnected and fall back to the prime set. If the prime set is
externally call forwarded this could result in a phantom call ringing at
the far end.
Q01979330

- Fallback to PSTN does not work using VOIP trunk
PSTN fallback does not work when using VOIP trunk.
Q01954315-04


Software Update BCM050.R200.145-VOICEMAIL Description:
------------------------------------------------------

- Cannot delete a mailbox from CCR tree numbered greater than 99
User logged in as an admin, unable to delete a mailbox from CCR tree 100.
CallPilot Manager GUI doesn't recognize 100 as CCR Tree value and Telset admin
will not accept the third digit for CCR Tree value. This update allows CallPilot 
administrator to enter a third digit for the CCR Tree value when using Telset interface
to remove temporary CCR Tree 100.
Q01886226


Software Update BCM050.R200.144-CDR  Description:
------------------------------------------------------

- CDR push failures after FTP server is rebooted
This patch resolves the CDR push failure if the ftp server 
is rebooted.
Q01892101-04


Software Update BCM050.R200.141-SOFTWAR E-MANAGEMENT-PROVIDER Description:
-------------------------------------------------------------------------

- user id and password stored in cleartext within log file during software updates
The SoftwareUpdateProviderAgent.log records the user id and password in 
cleartext when retrieving patches from remote locations. Exposure of this 
information is an issue because this log file is included in the Log Collection 
utility and then shipped off the BCM for browsing. Anyone looking at this file on 
their PC will be able to see the user id and password.
Q01927648-03


Software Update BCM050.R200.140-CORE Description:
-------------------------------------------------

- Incoming PSTN Calls that tandem over VOIP Trunks goes to Prime Set
If the Calling Line ID is suppressed on an incoming Call from a Cell phone, 
the Call goes to the Prime Set rather than tandeming to the CS1K.
Q01936952

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


Software Update BCM050.R200.139-SRG Description:
------------------------------------------------

- IP set 1120 E is not registering to SRG 
Inclusion of new firmware files for 1120e, 1140e, 2007, 2002 and 2004 Phase 2 IP sets.
The following firmware is being included in the BCM50 2.0 build for 1120e (0624C4N), 
1140e (0625C4N), 2007(0621C4V), 2002 and 2004 Phase 2 (0604DBP) IP Sets.
Q01834934


Software Update BCM050.R200.138-IPMUSIC Description:
----------------------------------------------------

- NCM cannot backup / restore Music Manager files
After the application of BCM050.R200.041-IPMUSIC or BCM050.R200.SU.System.009-200803
Music Manager files fail to be able to be backed up or restored using NCM.
Q01900042


Software Update BCM050.R200.137-IPTEL Description:
--------------------------------------------------

- SIP MWI Notify not redirected
BCM was configured to run the centralized voice mail. After a voice message was recorded
for a remote subscriber, BCM sent a SIP MWI Notify message to the SIP proxy server, but 
BCM ignored the SIP 302 response from the proxy server. As a result, MWI Notify was not 
redirected.
Q01882153


Software Update BCM050.R200.136-BSP Description:
------------------------------------------------

- Incoming T.38 faxes via SIP fail
Call originates from a fax machine off a CS1K system and routes across a SIP VOIP 
trunk to a SRG50 release 2.0, terminating at a fax machine on the SRG. Whenever T.38 
is enabled, the incoming fax calls to the SRG fax always fails after approximately 
30-40 seconds. If T.38 is disabled, fax calls work in both directions. Outgoing fax 
from the SRG50 R2 to the CS1K (with T.38 enabled) works without any problem. Note: 
where T.38 fax crosses a network, such as PSTN Fax->Central Office->PABX->QSIG link to 
CS1K->VOIP trunk->SRG, then the incoming fax will always fail when T.38 is enabled 
(across the VOIP trunk). The fault was proven between CS1K & SRG50 R2 by installing 
FAX on FALC (Flexible Analogue Line Card) howe ver this demonstrated problem will be 
observed whenever T.38 is used in part of a network solution.
Q01909229


Software Update BCM050.R200.135-BACKUP-RECOVERY Description:
------------------------------------------------------------

- Restore Warning - Software Level Report - incompatibility detected
The warning is incorrect and should never be displayed.
Q01832302


Software Update BCM050.R200.134-CORE Description:
------------------------------------------------

- CLID through GATM8 is broken
CLID is not working on GATM trunks in UK profile. 
The solution for this issue applies to both GATM-Ver1 and
GATM-Ver2 hardware. This problem is not present for GATI trunks.
Q01890281

- Tandem Call from PSTN rings at the control set
All tandem calls from the PSTN to the remote site ring 
at the control set instead of the correct extension number.
Q01822669-04

- Tandem calls on copper CO trunks fail across the VOIP
When a person with no CLID feature (e.g. a cell phone) calls
the SRG using analog PSTN lines, this call does not 
tandem to the CS1K, whereas calls with CLID tandem
successfully.
Q01881178

- SRG50R2 - one way speech to prime set
An incoming call tandems via SRG to the main office.
The digits dialed do not match any target line, so the call 
is rerouted to the prime set for the physical line. The prime 
set is in normal mode so the call tandems back to the main office.
On answer, the calling party can hear the person on the prime set,
but the called party (prime set) cannot hear the originator.
Q01881623

- No speech path to prime set
An incoming call tandems via SRG to the main office.
The digits dialed do not match any target line, so the call 
falls back to the p rime set for the physical line which is in 
local mode. When the prime set answers, the calling party 
continues to hear ring back tone.
Q01899096


Software Update BCM050.R200.131-CDR Description:
------------------------------------------------

- CDR shows incorrect data for Hunt group scenario when DND on Busy is enabled
CDR has been re-designed to correctly support hunt groups with DND on busy .
Q01888843


Software Update BCM050.R200.130-APACHE Description:
---------------------------------------------------

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


Software Update BCM050.R200.127-BSP Description:
------------------------------------------------

- RTP driver
All IP network connectivity is eventually lost from the BCM/SRG when using IP 
phones and IP trunks. This issue will affect all IP-based phones, IP trunks, 
and applications, however TDM phones will not be affected. This loss of IP 
connectivity typically occurs after several months of uptime. The BCM must be 
manually power cycled to restore service.
Q01884157


Software Update BCM050.R200.126-IPTEL Description:
--------------------------------------------------

- SIP T.38 fax calls from BCM to CS1000 intermittently fail
T.38 fax calls from BCM to CS1000 and then out on a PRI trunk to a fax machine
were failing intermittently. The cause was found to be that the BCM was not 
properly setting the InBandTone flag sent to the CORE upon detecting a 200 AC K
with SDP. As a result media path would be torn down in order to provide local
ringback. If a request came in from CS1K to switch to T.38 while this media 
path was being re-established, the BCM would end up rejecting this request, and
the fax would fail.
Q01854306

- BCM takes 15 secs to fallback to PSTN for each call while SIP Proxy Server is
unavailable PSTN calls arriving into the BCM via analog trunks and being 
redirected out over SIP to another SIP Gateway would take 15 seconds to 
fallback to PSTN if the IP network was down and hence the SIP Proxy Server 
became unavailable. The solution was to add a SIP OPTION ping on a regular 
basis (default setting is 15 seconds) to poll the proxy sever so as to determine
its availability. Once BCM has discovered that the proxy server is unreachable,
subsequent calls will fallback to PSTN with no delay, until the proxy is back alive.
Q01855035 

- No speech path when SIP calls forwarded from BCM to CS1K 5.0 CallPilot
In this call scenario, the BCM was not able to properly handle receiving a SIP
183 message with one media type, followed by a SIP update with a different media
type. As a result the BCM would not respond correctly with a SIP 200 ACK, 
subsequently resulting in a speech path issue.
Q01779930-01

- SIP calls from BCM50R2 to BCM4.0 drop after being answered
SIP outbound calls were made from BCM50R2 to BCM4.0 where centralized voice mail
was installed. The calls were accepted and answered by BCM4.0 but no speech path
was established properly. The issue was caused by BCM50R2 incorrectly handling 
the media disconnection based on the received SIP 180-no-SDP messages.
Q01878161


Software Update BCM050.R200.124-VOICEMAIL Description:
- -----------------------------------------------------

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

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

- High CPU spikes
If the BCM has more than 800 mailboxes, CPU usage spikes to 100%
while generating All Mailbox activity report. This update will resolve the
problem.
Q01826914-01

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

- Feature F970 should be registered only if APPP keycode is applied.
When the APPPack keycodes are not enabled, F970 gets registered but does not
work as designed. This update addresses this anomaly.
Q01816244-01 

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

- Call Sender shows corrupted CLID for German profile
This update increases the Local Number Length from 7 digits to 15 digits 
for German profile so that CallPilot can correctly determine the dialable 
DN for Call Sender feature.
Q01789495-01 

- High CPU spikes
If a Desktop Messaging client is configured for Auto Send/Receive, and 
a new fax or voice message is delivered to that client's mailbox, resulting 
in more than 500 messages in that mailbox, CPU usage spikes to 100%.
This update will resolve the problem.
Q01762747-01

- Voice quality is deteriorating
If the BCM has more than 800 mailboxes, voice quality 
deteriorates while accessing CallPilot manager and All Mailbox activity
report. This update will resolve the problem.
Q01691889-03

- 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 the
SMTP server is not shut down.
Q01679753-02

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

- RCC 2.5 cannotconnecttoDB and invalid XML
CallCenter receives a line ID as DN number from the middleware. This causes
the XML validation against the schema to fail, since the DN is defined as
numerical in the schema, whereas the line ID is alphanumeric. Now this will
be detected and a numerical value will be assigned to the DN.
Q01786289-01


Software Update BCM050.R200.123-DOORPHONE Description:
------------------------------------------------------

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


Software Update BCM050.R200.121-CORE Description:
------------------------------------------------

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

- SRG 50: Call forwarding fails.
An outside caller calls in to an SRG in normal mode and is tandemed to the CS1000 over VoIP.
The destination CS1000 set is CFAC to a PSTN number so the call is routed back to the SRG
and the public network. The forwarded call is dropped by the PSTN with the error 
"missing IE content." 
Q01831907

- Error in keycode allocation
This solution corrects an error in the number of keycodes allocated for digital set usage.
Q01842559

- UK market: CLID is presented after call answer rather than while ringing.
When a set is configured in 'Cap's n Pref's' to First Display 'Line', and the CLID 
is withheld on an incoming call, the line number only shows up after the call is answered, 
instead of while the call is ringing. 
Q01801594-02


Software Update BCM050.R200.120-DSPFIRMWARE Description:
-------------------------------------------------------

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

- Auto attendant does not recognize "0" or "#"
This issue is caused due to a conflict with the SIT (Special Information Tone) tone previously 
added in DSP. This problem is fixed in this update.
Q01845714-01


Software Update BCM050.R200.117-OAM Description:
-----------------------------------------------

- No data is showing for ADID module in Telephony Resource
DID related data is not displayed in 
configuration->Resources->Telephony Resources.
In MBMOD.vml, a DID parameter has been added to solve this issue.
Q01811104


Software Update BCM050.R200.116-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-02


Software Update BCM050.R200.114-SRG-REMOVE Description:
---- --------------------------------------------------

- SRGP update 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. This applies to SRG50 R2 systems that 
were upgraded from SRG50 R1 systems. Before starting to upgrade these systems, 
apply this update first to prevent the upgrade from failing.
Q01817371


Software Update BCM050.R200.112-CORE Description:
------------------------------------------------

- Partial loss of Telephony Programming post Power cut
Loss of recently configured core telephony data may occur following 
a coretel restart.
Q01685795

- Incoming VoIP Trunk calls receive fast busy
Incoming calls can only be answered by the prime set. Attempts to answer the 
trunk on a target line appearance gives fast busy to the caller.
Q01804851

- Echo on analog DID trunks (ADID4)
Echo can be heard during the first 10 seconds of a call for analog DID trunks.
Q01760892

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


Software Update BCM050.R200.109-GAP Description:
-----------------------------------------------

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

All DNs: Line Access, Capabilities and Preferences, Restrictions
Q01788687-02


Software Update BCM050.R200.108-DSPFIRMWARE Description:
-------------------------------------------------------

- Call is answered but ring tone continues on analogue GATI
For an incoming call, even though the call is answered, ring tone 
is heard on analogue GATI trunks. This is a race condition which occurs
intermittently. This update corrects the issue by blocking the detection
of ringing once the call is answered for that particular trunk.
Q01796100

- Australia ROI Fix for GATI: 
Incoming calls were getting dropped when call was answered for ROI trunks.
The existing ROI solution is not robust and is failing intermittently
(once in 4 days) at some sites in Australia. This is addressed in this update.
Q01774129-01

- South Africa Pulse Dialing Fix for GATI:
Pulse Dialing sometimes fails in the South Africa profile. This is fixed in
this update by disabling RZ bit (Ringer Impedance) during Pulse Dialing.
Q01730670-01


Software Update BCM050.R200.105-CORE Description:
------------------------------------------------

- Supervised ROI trunks drop when AA answers in Australia.
Incoming calls are getting dropped when answered for ROI
supervised mode in the Australia profile. This is an intermittent
issue. This issue is addressed for the required Analog Trunk
Interfaces GATM-Ver2,GATM-Ver1 and GATI.
Q01663473-02

- Addition of new Disconnect OSI Timer values for the New Zealand
Market Profile.
This change adds 800, 900, 1000 and 1100 Disconnect OSI
timer values for NZ market profile.
Q01724774-01

- Proper updating of GATM2 parameters is not happening while warm starting.
When market profile optio ns are changed under F** Option, GATM2 parameter
values not updated.
Q01662170-02

- Trunk Module Metrics: BRIM Loops status wrong
The BRI Layer-1 status is not updated properly in 
Element Manager under 
"Administration -> Telephony Metrics -> Trunk Module Metrics".
Q01060334-02

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

- Supervised ROI trunks drop when Auto Attendant answers the call in 
Australian market
Q01470485-02

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

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

- Night service does not turn off on Mondays
The customer has night ringing service set up where 
the start and stop times change over the weekend. 
On Mondays, the night service doesn't turn off.
Q01781334

- 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 un til you
press the intercom key and then release
Q01688511-01


Software Update BCM050.R200.104-OAM Description:
-----------------------------------------------

- Adding new Disconnect OSI Timer value in New Zealand Market Profile for EM. 
Q01724774-01

- When programming phone set buttons through Element Manager, 
the buttons for keys 6 and 7 on the image of IP phone 1120E were mis-labeled; 
the buttons for keys 8 and 9 on the image of IP phone 1140E were mis-labeled.
Q01639020


Software Update BCM050.R200.103-SoftwareManagement Description:
--------------------------------------------------------------

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


Software Update BCM050.R200.102-CORE Description:
------------------------------------------------

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

- The Hunt Group Matrix is Reporting Incorrectly
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.
Q01672357

- Cut & Paste button programming causes l oss 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-03

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


Software Update BCM050.R200.101-VOICEMAIL Description:
------------------------------------------------------

- CallCenter: Agent Audit Report shows inaccurate statistics for Break Time
A condition exists where the Contact Center Reporting Server database makes
an error when recording the break time duration. This appears in the 
Agent Audit report as erroneous break times.
Q01474739-01

- CallCenter: Connection between CCRS and RCC lost on co-resident PC
The problem is that a site was experiencing disconnection between CC 
and CCRS which lead to the connection between CCRS and RCC being lost. 
The fix was to close and re-open sockets to clean the old socket objects.
Q01598508 

- CallCenter: Server busy error message occurs in Real Time XML Stream
Server Busy error message occurs in Real Time screens intermittently. 
Restarting the web server was a workaround to resolve the issue. The fix 
introduced a timer to abort real time or historical processing when stuck.
Q01661415

- CallCenter: XML does not show F905 when there is a F906 Notified status
Due to limitations in the reporting architecture, we may only report on one 
active agent state at a time. There is an issue where a Supervisor misses a
(F906) Supervisor Help req uest, then releases the notification on the telset
without checking the messages. This creates a constant F906 notification
flag for that supervisor until they manually enter F906 and clear all 
notifications. This is the feature intent, however when the supervisor is 
in the state with a notification pending and enters (F905) Silent 
Monitoring, the XML will report the Supervisor as handling a F906 request, 
NOT doing a F905 Silent Monitor session. The fix for this issue is to suppress
the F906 status when the supervisor enters F905, thus the XML will properly
display the supervisor's active state.
Q01384700-01

- CallCenter: Enable DNIS display on Telset UI
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-02

- CallCenter: CCRSAppServer config contains 'histrorical' spelling mistake
Corrected a spelling error.
Q01574957

- CallCenter: Constant use of feature codes could lead to failure
Additional logging was added to help diagnose issues on several sites. It 
turns out that the main issue was a Voicemail issue where small amounts of 
memory were leaked every time a feature code was activated. The issue has
been solved under CR ID Q01601357-01.
Q01575347

- CallCenter: Reverting changes for CR Q01575347
The changes for Q01575347 (item above) are no longer needed and bloat the 
logs. The additional logging information introduced has now been removed.
Q01612871

- CallCenter: XML should not say " CannotConnectToDB" when Data Base is empty
When the Contact Center database is empty, test utilities will report 
"CannotConnectToDB". This information is false and the report should indicate
"NoCCData" when the database is empty. This update addresses the issue.
Q01414859-01

- CallCenter: The XML Stream enters an erroneously System Busy state during
normal operation. Problems with socket management eventually cause all sockets
to be full and as a result, XML queries fail. This error has been fixed. 
Q01506324

- CallCenter: Multiple users accessing configuration causes unpredictable results
When a user submits modifications to the Contact Center via Call Pilot 
Manager, the system automatically locks and unlocks the files to prevent
race conditions where two elements access the same file. An error in the 
system causes the Contact Center to lock the wrong portion of the 
configuration file, so if two users are managing the system in tandem, 
undesirable entries could be made. This has been fixed.
Q01612550

- CallCenter: Max calls in queue should be 30 but 48 is possible
The contact center software for BCM 50 Release 2.0 has been designed to 
operate at sustained maximum call limit of 30 simultaneous calls. Due to 
errors in the code it is possible to inject more than 30 calls and possibly
cause undesirable system performance if left unchecked. A fix has
been implemented which enforces the 30 call maximum, promoting stable call 
routing and system performance.
Q01546688

- CallCenter: Upgrade CCRS Database from MSDE to MSSQL
Microsoft is discontinuing support for the MSDE SQL database. MSDE also has 
no plan for support on the Windows Vista platform. To address these issues,
the Cont act Center Reporting Server, which uses MSDE will be upgraded to the
latest MSSQL database engine providing wider support and Vista compatibility
Q01538395

- CallCenter: Unread Skillset Message appearing in RT after listening to VM
Real Time report still shows new voicemail messages in the Skillset mailbox 
after the messages have been read. When a Skillset mailbox user composes
a new message or forwards an existing message to another mailbox, Voicemail 
will save a copy of the message temporarily, and will delete it once the
message has been delivered. But voicemail fails to send the "Delete" event
to update its counter. Changes were made to have the skillset mailbox
counter's information get altered. 
Q01693848-01

- Voicemail: ctiserver states Resource limits exceeded.
Voicemail reboots due to abnormal termination of a 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-03


Software Update BCM050.R200.098-DOORPHONE Description:
------------------------------------------------------

- Doorphones fail to operate after system reboot
This update addresses a timing issue where four or more doorphones
would not operate after a system reboot.
Q01760133


Software Update BCM050.R200.095-IPTEL Description:
--------------------------------------------------

- FEPS UDP thread corruption upon receiving non MCDN packets on port 15000
The thread that processes UDP packets received by F EPS 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


Software Update BCM050.R200.094-APPP Description:
--------------------------------------------------

This update introduces the following new feature.

- Advanced Paging Productivity Pack (APPP)
The APPP provides the following four capabilities

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

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

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

Scheduled Paging - system will provide a scheduled specific page 
(e.g. "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 updat e includes fixes to make the Element Manager Vista compatible. 


The following issues are addressed.

- OBT feature code registrations fail if there is a feature code starting with a 
blank.
Element Manager allows the addition of a feature code starting with a 
blank. After a reboot, the OBT fails to read any of the feature codes from the
PDR (Persistent Data Registry), and hence does not register any feature code.
The issue has been resolved by restricting the entry of blank spaces and 
special characters in the feature code.
Q01740178

- Element Manager throws error if a smaller OBT feature code is added after a 
larger one.
This is due to the fact that table is refreshed when the user tabs out after 
entering the OBT text message. Since the DN has not yet been entered, its
validation will throw an error. 
This issue has been fixed by ensuring that refresh will happen only after 
entering the full details of the feature code.
Q01739826

- On tabbing out of the OBT text message field in the Element Manager, the 
cursor is not placed in the destination DN field.
This is due to the fact that table is refreshed when the user tabs out after 
entering the OBT text message. After a refresh the cursor will not be placed
at the next tab stop. 
This issue has been fixed by ensuring that refresh will happen only after 
entering the full details of the feature code.
Q01739831


Software Update BCM050.R200.092-BACKUP-RECOVERY Description:
-----------------------------------------------------------

- Backup file contains installed update history
When Backup operation is performed on BCM the resulting tar 
file does not contain the history of updates that were 
applied to the system from th e initial power up.

This updates makes the history file available in the backup 
tar file so that support personnel can easily identify the 
state of a system they are supporting.
Q01479103-02


Software Update BCM050.R200.090-SRG Description:
-----------------------------------------------

- Element Manager disconnection due to PDR entries corruption
If any of the SRG data stored in PDR gets corrupted with control
characters, attempting to display this data would result in the
Element Manager disconnecting. Now all string data stored in 
the PDR will be checked for control character by the SRG provider 
before being sent to the EM.
Q01676165

- IP Address configuration problem in SRG tree node
Unable to configure the primary and alternate NCS IP addresses in 
EM with one of the octet values as 255. The test to check for 
valid IP addresses has been modified to support octet values of 255.
Q01590705


Software Update BCM050.R200.088-NNU Description:
-----------------------------------------------

- Partial loss of programming possible due to database and client synchronization. 
It is possible that the Database sends a database response to the wrong Database
Client. This can lead to incorrect programming records or invalid programming 
records.
Q01685795


Software Update BCM050.R200.087-CDR Description:
------------------------------------------------

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

- After applying update BCM050.R200.056-CDR no longer able to display push 
settings in Element Manager.
This update resolves the imp roper display of push settings in the Element 
Manager
Q01739659

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

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

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

- CDR Pull Client will only work with the default destination folder.
This update resolves the issue of installing CDR Client in different 
paths and different drives on a Client system.
Q01529733-01.

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

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


Software Update BCM050.R200.086-VISTA Description:
-------------------------------------------------

- 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 

- 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.R200.085-IPTEL Description:
-------------------------------------------------

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

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

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

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

- Changing the gatekeeper IP address while in GatekeeperRoutedNonRas mode
does not get picked up by the VoIP Gateway.
It was found that the VoIP Gateway did not change the Gatekeeper IP address it 
was using, if it was in GatekeeperRoutedNonRas mode, and if this was changed 
while it was already running. A restart of the VoIP Gateway service would 
result in the use of the configured IP address.
Q01502353-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-02 

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

- In GatekeeperRoutedNonRAS Element Manager shows status of 
"Running ..." even if gatekeeper not accessible.
If the gatekeeper becomes not accessible after VoIP Gateway startup, then 
the VoIP Gateway would display the status of "Running..." instead of 
"Attempting to discover the gatekeeper at ".
Q01570430-02

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

- FEPS crash upon receiving a Gatekeep erReject 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-02 

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

- H.323 to SIP Tandem fails to forward Progress Message on SIP leg
A Progress message received on the H.323 leg of a H323-SIP tandem through 
the BCM does not get passed through to the SIP leg of the call resulting 
in the call not completing. 
Q01637562-02

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

- Unnecessary codec renegotiation at beginning of VoIP Call.
Upon the init ial TerminalCapabilitySet exchange, the received max payload 
size was found to be smaller than expected, renegotiation would be triggered. 
When this happened unnecessarily at the beginning of the call, it could 
result in interruption of ringback, or delay of speech path setup.
Q01677775-04

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

- GatekeeperRoutedNonRas status not updated correctly
When in GatekeeperRoutedNonRas mode, the status field would not be updated
correctly in the event the gatekeeper became non reachable.
Q01729819-01

- Intermittent dead-air on outbound sip calls
With MCDN enabled it was found that under certain conditions SIP trunks 
could misinterpret the call Release as an Alerting. This would result 
in subsequent outgoing calls on those trunks experiencing dead air. A 
reboot of the BCM was required to resolve the issue.
Q01735697


Software Update BCM050.R200.080-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 update corrects the memory leak. 
Q01589266-01

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


Software Update BCM050.R200.079-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 

- 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


Software Update BCM050.R200.077-VOICEMAIL Description:
-----------------------------------------------------

- CPU usage is high
Memory usage spikes up while downloading the Voice messages using Unified 
Messaging and reaches its threshold which in turn 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-01

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

- CCR Tree Menu repeats when the user does not select any option number 
BCM50 2.0 Voicemail has a hard-coded implementation to repeat the CCR tree 
menu, if the user does not 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 Prop erties" 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.
Q01664396


Software Update BCM050.R200.075-DSPFIRMWARE Description:
-------------------------------------------------------

- GASI ASM+ Message Support
GASI receives market related parameters from the Core through ASM+ message.
Default hard coded market parameters are taken only when there is no ASM+
message support from the CoreTel.
Q01591658-01

- GASI New Market Profile Support
Support has been added for UK, Australia and Poland profiles in GASI. This
includes basic call processing, CLID and Message Waiting Indication.
Q01591658-01

- GATI New Market Profile Support
GATI support has been added for New Zealand, Russia and South Africa Profile.
This includes Normal Call Processing, Disconnect supervision and CLID.
Q01676857-01, Q01567968-02, Q01531574-03, Q01531440-01


Software Update BCM050.R200.074-CORE Description:
------------------------------------------------

- New Zealand profile addition in BCM50R2 PostGA
This code adds the New Zealand market profile to the BCM50 Release 2
product. It provides market-specific support for analog trunking.
Q01567968-02

- Russia Market profile addition in BCM50R2
This code adds the Russia market profile to the BCM50 Release 2
product. It provides market-specific support for analog trunking.
Q01531574-03

- South Africa Market profile addition in BCM50R2
This code adds the South Africa market profile to the BCM50 
Release 2 product.
Q01531440-01

- GASI globalization for AUS, NA, POL and UK in R2 Post GA.
This code provides analog station functionality for the following markets:
Australia, North America, Poland, United Kingdom
Q01591658-01

- The Hunt Group Metrics are Reporting Incorrectly
The Hunt Group Metrics are incorrectly reporting the total number
of abandoned calls.
Q01672357

- GATM2: South Africa Analog Trunk Support in R2
This code provides market-specific analog trunk
support for South Africa
Q01676863-01

- GASM: Issue with Rigning and Onhook voltage.
Ringing and onhook voltage settings for the GASM and GASM 8+
modules are incorrect for the UK market profile. 
Q01545887-03


Software Update BCM050.R200.073-GLIBC Description:
-------------------------------------------------

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


Software Update BCM050.R200.067-CORE Description:
------------------------------------------------

- Spain profil e addition in BCM50R2
This code adds the Spanish market profile to the BCM50 Release 2
product. It also corrects the omission of loss plan table entries
for analog trunks (which would result in 995 errors)
Q01541051

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

- One Conference resource is not freed up in Silent Monitor Sessions
When a silent monitor session is released by the supervisor, not
all conference resources are freed up.
Q01588756-02

- 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 such calls, no conference resources will be available
and users will be unable to set up any conferences.
Q01536124-01

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

- 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 fea ture, no calling party
information should be provided.
Q01538245-01

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

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

- BRI target line calls drop at ATA
Incoming calls on BRI trunks which terminate on target lines assigned to
analog sets connected to ATAs may occasionally be dropped on call answer.
Q01672544 


Software Update BCM050.R200.066-BTRACE Description:
--------------------------------------------------

- The "BCM IP Address" field in a user's account was not used for analogue 
modem Dial-In connections
The address field in the user's account was not being used when dial-up 
occurred over the analogue modem but was used for incoming ISDN connections. 
The fix ensures that this IP address is used for both ISDN and analogue 
modem incoming connections.
Q01546211-01.


Software Update BCM050.R200.065-DSPFIRMWARE Description:
--------------------------------------------------------

- Adaptive Line Tuning Support for GATI.
Echo Return Loss (ERL) is coming down when loop length (beyond 3000 feet )
is increased. This update resolve the issue.
Q01687332

- UK Call Diversion fix
This will resolve the issue observed in UK Market with GATI.
Customer is not able to cancel the Network Diversion Feature.
Dial tone definitions for GATI are modified to fix this issue.
Q01647592

- T.38 compatibility with Brother Tel/Fax mode
When a Brother Intellifax Machine is inTel/Fax Mode, it can
enter a state where it produces an 1800Hz tone. This change
fixes a problem in which the 1800Hz tone is mi s-detected
as a fax V.21 tone and causes T.38 to enter a state in which
the fax cannot proceed.
Q01559274-01

- Adaptive Line Tuning Support for GATI.
New Adaptive Line Tuning Algorithm is implemented for GATI. Hybrid
coefficients will be calculated dynamically using this new algorithm
This will resolve the echo issues observed in several customer locations.
Q01565372

- GATI: Pulse Dialing not working for Brazil Market profile.
When the digits are dialed out in Pulse Dialing Mode, GATI lines were
being released. This was due to the interaction with the overload protection
feature in Brazil. This issue is addressed.
Q01645024

- GATI: Auto Calibration issue with 800 ohms Transition feature
DAA chip was being calibrated to 800 ohms instead of the required 50 ohms.
This resulted in the DC offset issues, resulting in poor voice quality in
some cases. This is resolved by disabling automatic calibration
and by invoking manual calibration as per the recommendations from
Silicon Labs.
Q01620548

- Cache Tuning Changes and Optimizations
The DSP capacity is increased approximately 10% by tuning memory placement to
reduce the impact of external memory accesses. These changes have no functional
impact apart from increasing the system capacity.
Q01583044-01


Software Update BCM050.R200.058-UTPS Description:
------------------------------------------------

- Voice Path During Transfer or Call Park Scenarios
When parking or transferring a call that was originally placed from a BCM50 
R2 to CS1000, intermittent one-way speech was detected. This update resolves 
this issue.
Q01664346


Software Update BCM050.R200.057-CTI Description:
-----------------------------------------------

- F905 Agent monitor (OBS) fails intermittently on IP sets.
If the supervisor presses the Release key/Feature key immediately after
starting F905 i.e. when the F905 is initiating, the state machine 
doesn't handle these events and the state machine enters to a state from where
supervi sor times out and later cannot initiate the silent monitor once again.
Q01622584-01

- No audio on calls from phones in Skill set
As a fix to the CR Q01529228, core delays the silent monitor "session started"
message to the CTI. When the silent monitor feature is started, the supervisor 
cannot monitor the agent when the agent dials the access code for which a second
dial tone is enabled. The silent monitor feature was timing out and the feature
would be cancelled, until the second dial tone gets the disconnect, as the
time out period for the CTI was hard-coded to 7 seconds.
Q01529228-05 

- Support for New Zealand Market Profile
Symptom is that when BCM50R2 core's market profile is changed to New Zealand,
CallPilot fails to take the default country settings for New Zealand.
This update corrects the issue by adding the country-specific default data
so that CallPilot takes the defaults when the core's market profile
is changed to New Zealand. 
Q01511603-01


Software Update BCM050.R200.055-TurkishPrompts Description:
----------------------------------------------------------

- Issues with CallPilot Turkish prompts and labels 
CallPilot plays incorrect Turkish voice prompts. 
Q01445561-01


Software Update BCM050.R200.051 -SRG Description:
-----------------------------------------------

- SRG50 R2 : CS2100 Handle Quit Key is not Working
Q01595347 

- SE09.1:SRG Fails to detect the CS2100 CICM heart beat after the link comes back.
The sets that got connected in local mode upon WAN failure were not redirected
to Main office in Normal mode . This condition was solved by this update.
Q01579211


Software Update BCM050.R200.046-AustralianPrompts Description:
-------------------------------------------------------------

- Volume not normalized for Australian English 
This update normalizes the volume level for voicemail voice prompts for 
Australian English (including New Zealand) to a higher volume which 
will cause the voice prompts to be in the expected volume range.
Q01639253


Software Update BCM050.R200.045-BSP Description:
-----------------------------------------------

- RTP driver
The RTP driver does not send packets to IP sets with correct TOS field. This causes 
voice quality issues.
Q01612605

- The RTP driver causes high CPU usage
Q01513300 and Q01352584

- FPGA Release 10 for CSC2.0 
The FPGA Release 9 for CSC2.0 provided the work-around for FS288 expansion 
cable length issue. The FPGA release 10 implements the preferred solution.
Q01223267


Software Update BCM050.R200.044-CORE Description:
------------------------------------------------

- GASI 3dB Loss
The coretel software incorrectly assigned the off site mode setting to all GASI 
and GASM instead of on site mode. This results in improper loss plan settings 
between analog sets and analog trunks.
Q01387366

- ADID8 not showing programming parameters
Incoming calls on the ADID cards were being released by the firmware 2 seconds 
after line seize, resulting in dropped calls. 
Q01574087

- Incoming BRI calls without called party number are dropped.
Incoming BRI calls where the called party number is not provided are dropped by 
the public network due to lack of timely response from the BCM. This problem is 
specific to the Austrian market.
Q01502947

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

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

- 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

- No conference resources
This solution corrects a resource leak where the CoreTel software runs out of 
conference resources and conference calls can no longer be made.
Q01524534-01

- Hunt Group Configuration Issue
Incoming Hunt Group calls will drop if a non hunt group set with an Answer DN 
picks up the call.
Q01573918

- In the German or Austrian market any incoming call with 0 as the first digit 
should automatically route to the prime set. This was not happening.
Q01564034

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

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

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

- Button 18 on KIM + T7316e causes CallPilot 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, Voicemail 
on the system stops.
Q01525570-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-03

- Core programming is lost after first reboot.
On a freshly cloned system, CoreTel configuration data is lost after a warm restart 
of the CoreTel process.
Q01524191-01

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

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

- Cannot configure overlap sending on BRI after application of Core update 139 
Outgoing ETSI BRI calls cannot be configured as overlap signaling. All outgoing 
calls are using enbloc dialing.
Q01523153-01

- FAR_RELEASE is interpreted as FAR_RINGBACK
When an incoming VoIP trunk call is unable to connect to ringback because no media 
gateway is available, and the originator abandons the call before it is answered, 
the call continues to ring on the destination system.
Q00284073-03

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

- ENBLOC over VoIP does not work in special conditions
A incoming call from the central office via t he ETSI BRI trunk is forwarded from 
BCM1 to BCM2 via VOIP. In the protocol trace, the call is shown as being connected 
when the far end hears ring back tones. The call should only be connected when the 
destination answers the call.
Q01296708-07

- No DTMF tones on Page Output
When paging via an external device is invoked, DTMF tones cannot be sent. 
Q01578145


Software Update BCM050.R200.041-IPMUSIC Description:
---------------------------------------------------

- BcmAmp audio files are now volume leveled at upload time.
Uploaded audio files of .wav or .au types were being changed in volume to the 
point of being too loud. This update provides a configurable baseline value 
for the volume.
Q01506358-01


Software Update BCM050.R200.039-VOICEMAIL Description:
-----------------------------------------------------

- 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.
Q01596914, Q01601357-01

- 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 pa ssing the control character seen in 
the French language.
Q01535615-02

- WAV file exported from BCM fails to load on sound recorder.
The .wav file generated by exporting a company greeting that was recorded on a 
telset does not conform to the RIFF format specification. This update corrects 
this format error.
Q01513115-03


Software Update BCM050.R200.037-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


Software Update BCM050.R200.035-OAM Description:
-----------------------------------------------

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


Software Update BCM050.R200.032-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 R2 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 subse quent update may be required at that time if further 
changes are made to the DST regimen.
Q01502789-01


Software Update BCM050.R200.027-CTI Description:
------------------------------------------------

- Recordings are mixed up.
The wrong recordings may be played. Messages in the wrong mailboxes, greetings 
played as messages or vice-versa or empty messages. Any type of recordings are 
affected. This problem occurs only on systems with Unified Messaging users.
Q01534532-02

- If a Voice Port answers a call (Voice Mail, Contact Centre or Soft Modem) and TAT 
(Trunk Anti Tromboning) is invoked, the call could end up being disconnected immediately 
or having a one-way voice path if the voice port answered an incoming IP trunk call before 
TAT was invoked.
Q01410162-02


Software Update BCM050.R200.024-MODEMCC Description:
----------------------------------------------------

- When the Soft Modem answered a call that was at the far end of a TAT (Trunk Anti 
Tromboning) call, the modem was disconnecting the call instead of reconnecting to 
the near end of the TAT call.
Q01544270


Software Update BCM050.R200.021-CTE Description:
------------------------------------------------

- LAN CTE Client does not properly support Domain/Username Configuration
Some installations of the LAN CTE Client (TAPI and/or CTE) may not provide the full 
list of devices accessible to the user if that user is configured in Element Manager as 
using Domain/Username.
Q01493696

- Device Monitoring fails with ME_ALREADY_MONITORED when it is not being monitored
In some scenarios, a TAPI or CTE application attempting to monitor a device may fail 
with ME_ALREADY_MONITORED even though it has not been monitored by this app lication. 
This can occur if another application has attempted to monitor the same device and
reached a timeout limit before a response could be given. Check with your application 
provider if this update affects you.
Q01502372-02


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

BCM050.R200.SU.System.014-200903



Limitations: 

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

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

3. This update DOES NOT remove CCR Tree 100. Update allows Telset user
to delete the CCR tree 100 after application. Removal of CCR Tree 100 is
manually performed after applying the update as follows:

1. Using f983, login with Telset user ID and Telset password to access
CallPilot Admin
2. Once accessed to Admin menu, select the "OTHR" (Other) Soft Key
3. Soft Keys should update and display "CCR" (Custom Call Routing)
Soft key, select the CCR Soft Key
4. While accessing CCR Admin, select the "ADMIN" (Administration)
Soft Key
5. When display shows "CCR tree:", enter 100 on Telset dial pad
6. Telset display should show; "Tree:100", if so depress the digit 8
on the dial pad. 
7. Display update should show; "Delete tree 100?", and Soft Keys
marked "YES" and "NO"
8. Select the "YES" Soft key to delete CCR tree 100

Mailboxes previously referencing CCR Tree 100 in error can now be deleted
via CallPilot Manager GUI or Telset.