Software Update Name: BCM450.R600.SU-2

Applicable H/W Platforms: BCM450

Applicable S/W Platforms: 10.0

Category: GEN

Installation Recommendations:
This update should be applied to all new installations of BCM450 Release 6.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.

Components and Versions:

   core-telephony 6.1.1.05.26
   cte 6.1.1.128
   cti 52.0.136
   dialogger 46.1.1.136
   dsp-firmware 56.10.40.9.5
   feps 6.1.4.134
   gap 6.0.7
   iptelprovideragent 6.1.4.132
   iptel-sas 6.1.4.126
   utps 6.1.4.135
   voicemail 60.1.3.132
   webpage 6.0.65

Dependencies: BCM Release 6.0 version R6.0 1.02

Product Dependencies: None

Size: 46.25 MB

System Impact:
Time to apply approximately 10 minutes

Does update application force reboot: Yes

Limitations: None

Other Impacts: None

Update Removable: No

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


1. Recording very long calls using F989 Silent may cause IP sets to deregister
   Under high load conditions, the IP sets may de-register when a 
   45 minute call is recorded using F989 that extension has a mailbox 
   with Message Forwarding enabled. The IP sets will quickly re-register.
   This issue also causes Virtual Terminals to de-register affecting
   Find Me/Follow Me meaning the Cte service must be restarted using
   the Element Manager Service Manager.
   BCMRELEASE-993

2. Call-leg transaction responses being ignored
   (a) Possible loss of voice path between transferee and transfer 
   target when attempting to blind transfer over SIP trunk during 
   an outbound call in the ringing state. 
   (b) Possible codec renegotiation failure during transfer operations 
   over SIP  trunks, resulting in loss of voice path.
   BCMRELEASE-1021 

3. Inbound ITSP association fails due to incorrectly statically provisioned DNS cache
   Failure to associate some inbound ITSP calls could result in failure 
   to connect or failure to establish voice path (e.g. if NAT 
   compensation is required)
   BCMRELEASE-1022

4. Connected identity feature is missing connected name on non-MCDN trunks
   If connected-identity feature is enabled on non-MCDN trunks, only
   connected number is delivered. Connected name is missing.
   BCMRELEASE-1029

5. FEPS SIP trunk user account PAI overrides do not work with connected identity feature
   If connected-identity feature is enabled on non-MCDN trunks and
   PAI CLID and Display name is used at the SIP trunk user account
   level the overrides do not take effect.
   BCMRELEASE-1030

6. Private SIP trunk user account status collides with public SIP trunk user account
   In case SIP trunk user account with the same SIP domain and CLID
   is configured in both private and public domains SIP registration 
   status of the accounts does not reflect the real status. Both 
   accounts use the same persistent storage location to report the 
   status and one may overwrite the other.
   BCMRELEASE-1031

7. Disable "maddr" contact parameter logic is reverse
   The logic of "Suppress maddr parameter" option in EM is reverse. 
   When the option is turned on in the EM it is in fact turned off 
   in the IP trunking component and vice versa.
   BCMRELEASE-1032

8. SIP accounts failed to register after upgrading BCM from 5.0 to 6.0
   During migration from BCM 5.0 to BCM 6.0 existing SIP trunk user 
   accounts are migrated. Some new attributes of the accounts introduced
   in BCM 6.0 are not initialized properly and are set at random. As 
   a result the operation of these accounts is unpredictable.
   BCMRELEASE-1044

9. Remote Worker: No dial tone
   One of remote IP set cannot get media. This is due to the wrong port sent 
   by UTPS in OpenAudioStream UNISTIM message.
   BCMRELEASE-1058

10. Call transfer to VM stops working randomly
   Call transfer to voicemail (feature 986) stops working on some phones, after
   entering the mailbox number. The call is not transferred and it stays on hold.
   Two lads were mistakenly using the same secondary station id, and as a
   result the F986 request was not handled properly by the CTI. This update
   resolves the issue.
   Q02091765-04

11. SIP trunk diversion header does not get the CLID override treatment
   The CLID will not be correct when using the CLID override as the SIP
   trunk diversion header is not set.
   BCMRELEASE-1057

12. SIP trunk call redirect fails when no transport param in contact
   The outgoing call may fail due to a 302 SIP response causing a missed redirect
   destination when the contact header gets ignored.
   BCMRELEASE-1054

13. VoiceMail Read Receipts Enhancement to include Original Body of the Message
   A VoiceMail Read Receipts Enhancement has to be made for the read receipt to include
   the original message bodies with the receipt. This gives the user the ability to request a
   read receipt from a person listening to a message and actually return the original message
   back to the sender to tell them which message they listened to.
   The voice or fax original message bodies are included in the read receipts and can be
   listened to or viewed by F981 or Unified Messaging. This enhancement does not apply
   to AMIS certified messages.
   Q02032711-03

14. No CLID transmission on transferred calls to CS1k over H.323 trunks
   When an incoming call to BCM transfers the active call
   to a CS1K set over h323 with f70 feature, the incoming 
   line identifiers (CLID Information) are not transferred to customer.
   Q02046221-05

15. Conference call is dropped
   An incoming and outgoing trunk are conferenced together
   through the BCM. When the set that joined teh tow parties 
   disconnects, the bridged call is dropped instead maintaining
   the connection.
   Q02115424-04

16. Remote sites don't not get Ringback tone
   No ringback tone is audible to caller for outgoing tandem calls from 
   BCM to PSTN on T1 E&M trunks to a BCM4.0 although call is 
   actually ringing at the far end.
   This update resolves the issue.
   Q02118568-04

17. Non-BCM stations are not able to call BCM station if BCM station 
   has enabled the Find-Me feature
   The problem occurs when a BCM station enables the Find Me in MM. The 
   call will fail unless another BCM station calls the BCM station with
   the Find Me feature, the call will not succeed. 
   BCMIPOINTEROP-26

18. Direct pickup fails on SCS when call is originated from BCM
   Attempts to pick up BCM calls by SCS over SIP trunk were blocked by
   BCM not allowing REFER in unanswered state.
   Q02102264-01

19. BCM <-> SCS interop: issue with Direct pickup on
   SCS when call is external to BCM 450r1
   An incoming PSTN call tandems via BCM over a SIP trunk to SCS
   where it rings at set A. If, while set A is ringing, SCS set B
   attempts direct call pickup, the call pickup will succeed but
   there will be no media path connection.
   Q02130340-03

20. Rotary Hunt Group not functioning correctly
   When an incoming call is blind transferred to a rotary hunt group,
   The first available set in the HG only gets a short ring blip, but
   on completion of the transfer, the call rolls to the next available set.
   Q02146813-01

21. Intermittent call drops when incoming calls are answered
   Intermittently, incoming calls on analog lines are disconnected when
   answered.
   Q02091670-02
22. BCM Faxes stop working after 3 Days
   Fax messages are failing due to a DSP lockup. This fix resolves
   the issue
   Q02111119-03

23. BCM Monitor cannot connect
   BCM Monitor cannot connect due to secure sockets waiting to be closed
   by other application.
   BCMRELEASE-1055

24. Remote worker POP up window is not in proper format
   The Remote Worker pop up window spacing is not correct.
   BCMRELEASE-1079

25. RFC2833 support for i2050v4
   RFC2833 defined DTMF tones are failing on i2050v4 with BCM.
   BCMRELEASE-1062

26. ICC Calls in queue will not present to agents
   ICC calls in queue are not presented to agents before being played 
   the Alternate message in the skillset mailbox.
   BCMRELEASE-1065

27. T38 missing EOLs in RTC Bug fix
   This change fixes the problem of missing EOLs in T38 on-ramp at the 
   end of Fax page transmission. There was a deficiency in T38 linker 
   layer which caused the number of EOLs (End of Line code) in RTC 
   (Return to Control) to be less than the standard number of 6. With 
   missed EOLs, some fax machines either reject the page or ask for 
   retransmission causing duplicate pages to be printed. By putting this 
   fix in place the number of EOLs in RTC in T38 on-ramp would be always 
   as same as the number of EOLs that the caller fax machine transmits. 
   Q02104860-02

28. BCM Monitor shows incorrect status of IP Trunks.
   When an external outgoing call is made, from a set, and released quickly
   before the far-end responds, then the trunk status under BCM Monitor is
   shown incorrectly as active. This update resolves the issues as the necessary
   code changes are made in CTE which updates the trunk status correctly.
   Q02137864-04


This update includes the content of the following superseded update:

BCM450.R600.CORE-TELEPHONY-1

1. This coretel update will prevent a NIL_TN destination timeslot 
   value from being passed to the kernel for a timeswitch connection. 
   Under heavy CPU load, the order of IP set shutdown messages received 
   from UTPS and MPS can create a scenario in which a NIL_TN value 
   may get used in a timeswitch connection. When the NIL destination 
   TN is passed to the kernel for a timeswitch connection, a system 
   error can occur. On the BCM450 platform, the error can cause a 
   CoreTel crash. On the BCM50 platform, the system does not crash, 
   but rather, writes into a random timeswitch location.
   BCMRELEASE-1046 

2. Call forward to Exchange UM fails with TRO on incoming call
   An incoming call to the SRG is forwarded to the users set in Normal
   mode on the main office. If TRO is active and the set actually has
   Call Forward All Calls setup on the main office to the Exchange UM
   server, the forwarded call will be disconnected.
   Q02091162-0
 
