Product compatibility
This release is compatible with the Ensim Unify Platform 4.7.0 with Update 1.

Compatibility with third-party software
This release is compatible with the following third-party software.

Download
ftp://ftp.ensim.com/download/unify/broadworks/3.2.0/Unify_BW_3_2_0.iso

Fresh installation

• BroadWorks Release 14 SP9
• Microsoft Provisioning System (MPS) bundled with HMC 4.0 and 4.5
• Microsoft Windows Server® 2003 R2 operating system with Service Pack 2 (SP2)
• Microsoft SQL Server™ 2005 with Service Pack 2 (SP2)
• Microsoft .NET™ Framework 3.0 with Service Pack 1 (SP1)
• Web Services Enhancements (WSE) 3.0 for Microsoft .NET™ Framework 2.0
  Note: This release does not support upgrade from previous versions of Ensim Unify BroadWorks (R13) Service Manager.

What's new in this release
Ensim Unify BroadWorks 3.2.0 Service Manager introduces following new features in this release:

Support for Voice Messaging

You can now set all the required voice messaging settings from Unify and create a user with voice mail feature.

• User Provisioning / User Update – A new check box Use Exchange Mailbox at user provisioning level is added. This option helps you to set user's Exchange Email Address, Mail Account Username and Mail Account Password automatically to BroadWorks. Once you select this option you do not need to enter the mail account details manually.
• Voice Portal – Now, voice portal settings can also be set from the Organization Administrator panel for every group created.
• For setting Default “From Email address” for Voice mail:
  1. Create the following registry key at all PE servers:
     Key Path: -
     HKEY_LOCAL_MACHINE\SOFTWARE\Ensim\Ensim Unify\serviceComponents\BWComponent\backend
     String Key: - VoiceMessageEmailAddress
  2. Set the key value to a valid email address.
     Note: If the key is not created then, system default email address (set during installation of BroadWorks Server) will be used to send the voice mail.

Web services
Following new web services are introduced to provide additional functionalities in Ensim Unify BroadWorks 3.2.0 Service Manager:

• Organization group-voice portal web services:
  ? UpdateGroupVoicePortalData - Using this method you can update group voice portal data for the BroadWorks Group created at Organization Administrator level.
  ? GetGroupVoicePortalData - Using this method you can retrieve voice portal settings for every BroadWorks Group created at Organization Administrator level.
  For more information about these web services methods, refer Organizationgroupvoiceportalwebservices document.
• Web services methods for the single sign-on feature are now supported. ( 57103)
  For more information about these web service methods, refer Ensim Unify BroadWorks Web Services Help.

Resolved issues
This section describes the resolved issues of the Ensim Unify Broadworks 3.2.0 service. The numbers in parentheses indicate the Ensim problem report (PR) number.

• Resellers can now assign phone numbers to their organizations.(1081663)
• On the Add User page, the value entered for the Line/Port option is now validated when adding the user.(1083537)
• The user’s device information is now removed when you change the Device Category for the user to None. However, the device instance is not removed from the BroadWorks server.(57439 & 58223)
• If you create or have an organization with the Voice Mail Configuration option disabled but with a quota specified for the Voice Messaging User option, and if you provision a user on this organization with the Voice Messaging User option enabled, then changing user settings for this user no longer results in an error.(1083523)
• If you remove the group that the user template is using, the procedure no longer fails.(57091)
• For users that are assigned the Devices 3.2.0 service, changes to device instance settings such as MAC ID and STUN server are now updated in the BroadWorks Application Server.(58378 & 58068)
• While editing a user who has a device assigned, if you select the Add New IP Phone/ATA option then the earlier port can be now re-used.(58225)
• The "Add user", "Overview user", and "Trunk groups list" pages are now rendered faster.(1085223)
• Authentication password is not required to be re-entered while editing a trunk group.(1085268)

Known issues
This section describes the known issues of the Ensim Unify Broadworks 3.2.0 service. The numbers in parentheses indicate the Ensim problem report (PR) number.

BroadWorks-specific issues
The issues described in this section are specific to the BroadWorks service.

Trunk group issues

• You cannot remove a device instance that is used for a trunk group. This is because one port of the device instance is used by the auto-attendant user of the trunk group.(1084719)
• Organization administrators can set the trunk group user quota to a value less than the number of users created in the trunk group. Also they can add more users under the trunk group irrespective of the limit specified at the trunk group level. However, organization administrators cannot create trunk users more than the capacity set at the organization level.(1084936)
• While adding or changing a group, the actual limit available for the "Simultaneous Trunk Call Limit" option may be less than the available value. This happens because the displayed value is the quota allocated to the organization and not the limit available to the group.(63071)
• While adding or changing a trunk group, the actual limit available for the "Maximum Number of Active Calls" option may be less than the available value. This happens because the displayed value is the quota allocated to the group and not the limit available to the trunk group.(63072)
• To add/remove a trunk group or view the users in a trunk group, organization administrators must first select/locate the group to which the trunk group belongs. Also, organization administrators cannot move a trunk group from one group to another group. To do this, organization administrators must first remove the trunk group from the group to which it belongs and then add it to the required group.(63073)
• The history trail displayed for trunk group pages while navigating from group pages may not be correct.(63074)

Voice mail and voice messaging issues

• The Group Services > Voice Messaging configuration is not displayed in the BroadWorks interface until at least one Unify user is added to the organization and the Voice messaging user feature is assigned to that user.(56928)
  ? Solution: To resolve the issue:
  a Authorize the voice messaging group feature to the group, and
  b Assign the voice messaging user feature to a user and add the user to the group
• It is not possible to remove the Voice Messaging Group feature from the group.(1084924)
  ? Solution: To resolve the issue:
  ? Use the BroadWorks portal to unauthorize the Voice Messaging Group feature from the group.
• If you have a dual AD configuration for Unify and if you provision both Exchange 4.7.0 and Broadworks 3.2.0 service for a user, a warning message may be displayed in the action log User does not have Exchange mailbox defined. Email Address for the user cannot be set. However, provisioning is successful.(63070)
  Workaround: To set the email address - Select a user, go to Broadworks edit service page. In the User Features section, select the use exchange mailbox option OR Type the email address, mail account username and mail account password.

Time zone and state lists issues

• If the state or time zone description is changed on the BroadWorks server, the change in description is not reflected when you create a new organization in Unify.(57128)

Group and user issues

• The Add user functionality fails with an improper message Softswitch returned following error: [Error 4205] The user may not be added because the group user limit has been reached. Please ask your service provider to increase user limits for the group, if you add a user to a group when the maximum user limit of the group has been reached.(57408)
  ? Solution: To resolve the issue:
  ? Increase the settings for the maximum number of users allowed for the group.

Other issues

• The usage collection values for some BroadWorks resource types may not display correctly. You can view accurate usage information for such resource types from the BroadWorks portal.(1084506)

Devices integration-specific issues

The issues described in this section are specific to the Ensim Unify BroadWorks 3.2.0 when integrated with the Ensim Unify Devices 3.2.0 service.

Device configuration issues

• Removing a device instance through the organization control panel removes it from the Unify Devices service database, however, it is not removed from the BroadWorks Application Server.(58220)

Configuration file issues

• While adding a user having the Ensim Unify Devices 3.2.0 service, a configuration file is generated even if the add user operation fails. This configuration file does not contain any user information.(1083324)

User template issues

• If in the user template the Authentication and Voice Messaging User options are selected and the device category value is other than None, then creating a user with this template displays either or both the following errors on the Choose Service Option page: Type a new authentication password - Required field missing; Mail Account Password - Required field missing. You may observe similar behavior for other mandatory options on this page.(58132)
• When editing a user template, the device parameter information is not displayed. This is because the page is not automatically refreshed while editing the user template. Additionally, the device category is set to Add Device Type and not IP Phone/ATA.(58255)
  ? Solution: To display or change this information, you need to refresh the page as follows:
  • Select the template and click Edit on the action bar.
  • Click Next on the User Template Information page, then click Next on the Select Services page.
  • On the BroadWorks Service Edit page, under the Device Information section, choose Add New IP Phone/ATA (even though it may already be selected). The page is automatically refreshed and the Phone Name and Device Type fields are displayed.
  • In the Device Type field, click the arrow and select the option -Select a device type-. The page is automatically refreshed.
  • Again select the old device type whose information you want to change. The page is automatically refreshed and the device type parameters are displayed.
  • Change the values of the parameters as required and click Next, then click Finish to save the template.
• The "Shared" device type category is not supported for organizations that have both the BroadWorks 3.2.0 and Devices 3.2.0 service.(1084940)

Known limitations
This section describes the known limitations of the Ensim Unify Broadworks 3.2.0 service. The numbers in parentheses indicate the Ensim problem report (PR) number.

Browser support

• This release of BroadWorks 3.2.0 service does not support the FireFox and Mozilla browsers.(1082688)

Unify features not supported

• Moving the BroadWorks service from one server to another server is not supported.(56526)
• If you enable authentication at the trunk group level and the users under that trunk group have SIP authentication enabled but with a different user name and password, then such users fail to authenticate on the BroadWorks server. This is expected behavior of BroadWorks release 13. The workaround for this issue is not to enable authentication at the user level or if you enable the authentication then use the same user name and password given at the trunk group level.(1084938)

BroadWorks features not supported in this release

• Support for MGCP (Media Gateway Control Protocol) phone devices.(57404)
• Support for Broadsoft feature packages and feature bundles.(55876)
• Managing group-level administrators.
• Administrators cannot specify policies.

Features that must be accessed through the BroadWorks interface

• Configuration of voice VPN (Virtual Private Network).(56071)
• Provisioning and configuration of CPE (Customer Premise Equipment) devices.(56357)
• Defining the phone extension length when you create a group.(56073)
• Setting the Group Web Policy: User Profile setting to read-only. This prevents users from modifying their profiles.(56980) 
• System-level, Enterprise-level, and Group-level feature configurations.