Clearspan s OpEasy Release Notes Current GA load: Version

Transcription

1 Clearspan s OpEasy Release Notes Current GA load: Version Internet Blvd Frisco, Texas Tel Lobby Tel ACTS Page 1

2 Table of Contents 1 Supported Environments Upgrade Information Enhancements and Changes EIR s... 8 Page 2

3 1 Supported Environments Windows 7 Windows XP Internet Explorer Versions 8.0 & 9.0 Phones set up using DMS License Manager Version 5 Spreadsheet Versions: Basic Import: B219 Advanced Import: A215 Enterprise Import: E213 Advanced Export: A215 Enterprise Export: E213 Service Rate Import: SR220 2 Upgrade Information Upgrade part number: Schedule upgrades with ACTS at least 48 hours in advance Upgrade will be performed by ACTS personnel. Installation, upgrade and test plan documents are available through Customer Operations Manager and ACTS. Document includes Enhancements/Changes from OpEasy to Enhancements and Changes Provisioning Licensing for Polycom and Users for Enterprises - Add the ability to license a count of Polycom phone devices that are allowed to be managed via OpEasy. Track which devices are added or modified and disallow any others once the limit is reached. Apply this also to User Licensing added in V3.10. Provision AINs (Locations) in OpEasy for Reporting - Revised the Enterprise and/or Group Settings to provision AINs for the enterprise and groups (AINs are current stored in Remedy). Add new elements to the XML report (and others?) to provide the Page 3

4 enterprise AIN and the AIN associated with each group so that billing can occur properly by location. Import Advanced & Import Basic - Prevent all admin levels except Super Users from building devices that have a device type that is not supported by OpEasy User Edit: Fixed an issue where the admin cannot select a trunk group on the trunk group device edit page when the User Profile does not specify a trunk group. Corrected an error when deleting a primary device that is a trunk when in user add mode. System Removed System Import - Remove the decommissioned System Import from OpEasy completely Remove System Import privilege Remove the Clearspan System Import Template file Remove both Import & Export from Provisioning (and Reporting library) Important Note Administrators may need to remove a physical phone from its associated Clearspan device but retain that Clearspan device for future use by another phone. The physical phone that was removed from a Clearspan device can then be associated with a different Clearspan device. When an Aastra phone is removed from a Clearspan device and associated with another Clearspan device (with an Auto Install Device Id), booting the phone causes the Auto Install screen to be displayed so the user can select the new Clearspan device using the Auto Install Device Id. The actions to complete the disassociation are different for Aastra and Polycom phones and different when performed via OpEasy or the Broadsoft Web Interface. To disassociate a physical Aastra phone from its Clearspan device using the OpEasy GUI, the administrator must: Either clear the MAC Address field of the Clearspan device or change that MAC Address field to a new Auto Install Device Id (to replace the MAC address of the Aastra phone being dis-associated). Page 4

5 To dis-associate a physical Aastra phone from its Clearspan device using the Broadsoft Web Interface, the administrator must: Either clear the MAC Address field of the Clearspan device or change that MAC Address field to a new Auto Install Device Id (to replace the MAC address of the Aastra phone being dis-associated). Change the Device Access User Name and Device Access Password fields under Use Custom Credentials of the Authentication section of the Clearspan device. The Device Access User Name MUST be changed so that is does NOT contain a MAC address, even when User Custom Credentials is not enabled. Therefore, it must be set to a value that is not a MAC address but is unique across all devices of the same Device Type. If needed, select Use Custom Credentials so the Device Access User Name can be changed to remove a MAC address from the User Name. When changing the User Name, an associated Device Access Password must be entered. Use any acceptable password. To disassociate a physical Polycom phone from its Clearspan device using the OpEasy GUI, the administrator must: Clear the MAC Address field of the Clearspan device (to remove the MAC address of the Polycom phone being disassociated). Change the User Name and Password fields under Device Access of the Device Configuration section of the Clearspan device. The User Name MUST be changed so that is does NOT contain a value related to the removed phone (such as the phone s MAC address). This change lets the administrator use that phone-specific value when later assigning the physical Polycom phone to another Clearspan device. Therefore, the User Name must be set to a value that is not a MAC address or other phone-specific value but the new value must be unique across all devices of the same Device Type. When changing the User Name, an associated Password must be entered. Use any acceptable password. Page 5

6 To disassociate a physical Polycom phone from its Clearspan device using the Broadsoft Web Interface, the administrator must: Clear the MAC Address field of the Clearspan device (to remove the MAC address of the Polycom phone being disassociated). Changes Change the Device Access User Name and Device Access Password fields under Use Custom Credentials of the Authentication section of the Clearspan device. The Device Access User Name MUST be changed so that is does NOT contain a value related to the removed phone (such as the phone s MAC address), even when User Custom Credentials is not enabled. This change lets the administrator use that phone-specific value when later assigning the physical Polycom phone to another Clearspan device. Therefore, the Device Access User Name must be set to a value that is not a MAC address or phone-specific value but the new value must be unique across all devices of the same Device Type. If needed, select Use Custom Credentials so the Device Access User Name can be changed to remove a MAC address from the User Name. When changing the User Name, an associated Device Access Password must be entered. Use any acceptable password. Only use the special chars "-" and "_" in passwords. AutoInstall - Always create device credentials if the MAC address is correct. System Report - Change "EnterpriseLicensed" tag to "EnterpriseDisabled" to clarify the meaning of the value. Administrative Tools / Remedy AIN Definitions page - Cleaned up page display when Enterprise changed. Administrative Tools / OpEasy License Allocation page - Displayed "Saved" when the Apply button is pressed and the allocations are saved. Reporting / System Report - Corrected System Report issue where 2 elements were both called <Enterprise> (one should have been <EnterpriseAIN>. Page 6

7 OpEasy Licensing: Default enterprises to Manual mode with 10 allocated users and Polycom phones. Clarified OpEasy license warning text. Added License Id audit. System Report - OpEasy Licensing: Always output licensing fields even when they do not apply (just leave them empty). Renamed <ClearspanCurrent> element to <Used> in the XML System Report and the xsd file, to clarify the value Updated xsd for XML System Report to include OpEasyManagedUser and OpEasyManagedDevice elements. Corrected type definitions Load Balancer: The web servers have been put into Primary/Secondary mode instead of Round Robin. This means that all administrators will be routed to EMS1 unless it is down (then they will route to EMS2). Auto Install - Remove 3 second delay before restarting the phone. Device Type Conversion: Remove Device Type To URL trailing slash if it exists as it should not be in the URL path Add Polycom Phone License only if the replaced device was licensed and add the license only if possible (add the new device regardless). Corrected the Load Balancer configuration to route users to EMS1 when using the management port Corrected the number of keys on the M685i expansion module Corrected OSS lookup of a phone number to read all phone numbers from the OSS server (instead of stopping after the first 100 numbers) Page 7

8 4 EIR s EIR OpEasy sent a message to the Application Server to reboot a station after the admin changed the voice portal password via OpEasy. It only happens the first time a user's password is changed, after the password is changed initially and the station is rebooted, it does not happen anymore. There must be something the admin sets or OpEasy automatically (formats) that changes the station and causes the reboot. These stations were built via the bulk provisioning tool. The admin changed the password via OpEasy / Provisioning / Users / Edit / Voice Portal Passcode parameter. Bug in the code resulted in phone reset even when none of device parameters were changed. Fixed the code EIR Provisioning --> User Profiles - When a VM Only is created from a VM Only User Profile, the New User has to be edited to select the "All Calls to VM" option. When a VM Only User is created from a VM Only User Profile can the "Send all Calls to VM" option be selected by default? Fixed code such that if a user is created from VM only user profile, by default all calls are redirected to VM. EIR When using an Import Advanced worksheet and specifying Modify User with the columns filled for User ID, Calling Line Phone ID and NCOS only, when the import runs the Department field is reverted back to 'None'. If fields are blank on an Import worksheet, the field should be left as is - rather than setting the field back to 'None'. Hopefully the Department column is the only column that is broken in this way, but please confirm this doesn't occur for any other columns. The OCI driver module (BWOCIClient.OCIUserModifyRequestXX) currently generates a "Department" object in the OCIUserModifyRequest and sets it nil. this deletes the Department from the user. EIR In order to avoid modifying the Department field, the OCI driver should not attach a Department object at all. The complete solution is to use a key value "NULL" to indicate the desire to delete the department from the user. Since this is just another data value to the import operation there is no impact to that code, but the modify command is also used by the Provisioning GUI and it will be necessary to verify that everywhere it is used will be compatible with the new interface. Changed OCI driver to accept "NULL" as a command to remove the department, empty leaves it alone. Changed template file and export to indicate "NULL to delete" on department. Modified UserHelper to change empty to "NULL since provisioning always fills it in (same action as before) Page 8

9 The voic tab of an Advanced Export has columns for 'Use Default Mailbox Limit' and 'Mailbox Limit'. The data for these columns are misleading / inaccurate. Example 1, a user uses the system default and the system sets the limit to 30 minutes, BUT the export shows values of 'True' and '10' for the columns respectively. This doesn't tell us if the Default uses the Group or System setting and doesn't retrieve the limit accurately. (Not sure where the value of 10 comes from.) Example 2, a user has a Mailbox Limit set to 60 at the user level. In this case, the export shows 'Undefined' for the 'Use Default Mailbox Limit' and '60' for the 'Mailbox Limit'. What does 'Undefined' mean? Shouldn't this column contain True or False? Anomaly in export system. If user has selected "Group Default Mailbox Limit", mailbox limit is displayed as blank in the voic worksheet EIR OpEasy: Changing the name on a template i1inb3 mw9 kyle. If you attempt to modify the name, all phones associated with that template, will lose that template and become <UserDefined> ================================================= I was able to reproduce this on Alphas OpEasy also. I modified the name of "Asseff - Standard 2 Line" to "Asseff - Standard 2 Line1". When I went back under Phone Management, my template was changed to <UserDefined> OpEasy did not verify whether a template was in use before renaming it and did not change the associated phones using that template, which caused the phones to be set to a User Defined template. Do not allow a template to be renamed if it is in use EIR When adding an Auto Attendant, adding a personal greeting fails. Either the greeting file is not loaded, or if selecting another menu after browsing for the greeting file for a menu (such as Business Hours Menu), the personal greeting file being browsed appears to load on the other menu, not the menu where the file was selected. File information stored in the wrong object. Store file information in the correct object. EIR When only modifying an Auto Attendant to load a newer version of the same audio file for a personal greeting or announcement, the change does not occur because the filename did not change so the code did not detect the change. The matchesmediafileresource() method in the MediaFileResource class was not performing the proper comparisons on the files. Correct the comparison of files in matchesmediafileresource EIR Page 9

10 Auto Attendant - Two related issues: (1) When adding an announcement file as a greeting or in a Play Announcement step, the entire filename, including the path, is sent to Broadsoft when saving the Auto Attendant configuration. The path should NOT be sent because it is the path to the file on the administrator's PC, which is unimportant. (2) The saved filename includes the extension (.WAV, etc.). However, Broadsoft also attaches an extension to the filename because of the file type (WAV, etc.), which means the filename displays as: <filename>.wav.wav. The file extension needs to be removed before sending it to Broadsoft and restored when reading the Auto Attendant configuration because OpEasy does not add the file extension like Broadsoft. Lack of understanding of how Broadworks handles the audio filenames. Remove the extension from the filename and set the media type when adding an audio or video file. EIR Auto Attendant - When changing menu items, errors are being logged. The Play Announcement was being added as the menu item but this issue may be occurring when adding other menu items as well. The menu objects were being overwritten with a new object each time the menu tab was entered. Check for null menu object before creating and assigning a new menu object. EIR Auto Attendant: Submenu Add page - When adding a Transfer to Submenu item to a submenu, the following is alarm is logged because the drop down value is not set correctly: "com.sun.webui.jsf.component.dropdown: The current value of component form1: layoutpanelkeyfour:dropdownkeyfoursubmenuid does not match any of the selections. Did you forget to reset the value after changing the options?" Did you forget to reset the value after changing the options?" The submenu drop down value was not being initialized correctly. Initialize the sub menu drop down value. EIR Auto Attendant: Submenu Add/Modify page - Do not show the Transfer to Submenu option unless at least one submenu exists. Today it shows an empty drop down box. EIR Auto Attendant - No validation occurs for the fields entered on the Menu tab. Similar to the Users pages, the validation should occur in AutoAttendantHelper before performing the add/modify. Validation of menus was not implemented initially. Implement validation of menus. Page 10

11 EIR In the failure case where EMS 2 cannot communicate with components in the primary data center, it will not be able to send notification s to maintenance personnel. The 'SMTP Server Address' was moved out of aastra.properties and into the synchronized database. The original design intent was for each EMS to target the SMTP server (Surg ) in its local data center when sending s. Move into database did not take into account two separate values for the definitions. Split "Site Name Reported", " FromAddress", "SMPTServer IP Address", and SMTPServerPort" into separate entries for primary and secondary servers. On SystemSettings page - duplicated " definitions box under "Primary Server" and "Secondary Server". Database retrofit sets the value for both servers to the same (existing) single setting. If left this way no change should be seen. Separate values can be entered to differentiate the two servers as desired. The "Site Name" and " From" fields will be used in SNMP trap and admin notification messages. EIR Customer has extension only phone built on OpEasy and when trying to assign the 1 line Standard nodnd (Group) template an error appears stating "[Details] Calling Party ID: Phone Number is invalid. Number must either be an international (E.164) number (beginning with +), or a telephone number (XXX- XXX-XXXX or 1-XXX-XXX-XXXX). Customer was able to assign the template using the Provisioning -> Phone Management menu in OpEasy version but should be able to assign the template from the Add users menu. The Extension was being validated a full E.164 number Removed requirement on CLID number to be full E.164 number EIR Customer is unable to add users to BLF list using OpEasy Existing BLF list BLF@tuup.sip.net.internet2.edu has monitored users in list and when the User search for Department "Study Abroad" is selected the Available users that are in list can be selected to add but when apply is pressed error shown is "[Details] Calling Party ID: Phone Number is invalid. Number must either be an international (E.164) number (beginning with +), or a telephone number (XXX-XXX-XXXX or 1-XXX-XXX-XXXX). User can be added via AS Root cause appears to be CLID number that is not full E.164 number. Removed requirement on CLID number to be full E.164 number EIR Service Packs - When assigning Service Pack(s) under User Profiles, Users, Auto Attendants, and Import (Basic, Advanced, and System), the list of available Service Packs for assignment must NOT include any Service Pack that is NOT available to be used (NOT marked "Available For Use"). These unavailable Service Packs are returned when obtaining the list of Service Packs and are currently being displayed in the list of available Service Packs but they cannot be assigned to users. Any attempt to assign them to a user causes an error that is not understandable to the administrator. Page 11

12 Lists of available service packs were not filtered to exclude service packs that were not marked "Available For Use". Modified the three routines in OCICommHelper that get the various lists of service packs to only include those that are marked "Available For Service". This corrected the lists for User and User Profile operations. Note that of the function listed in the problem description Auto Attendants use services - not service packs so they are not affected, Basic Import uses only the service packs already in the user profile - so they are covered there, and Advanced Import does not list the available service packs, the admin just has to know what to put in. (And system import is moribund). EIR Export - Admin wishes to run an export on only one export option but the export fails for all the options except Users and Media Packs. The error message returned is "Unable to open data file for read (/var/aastra/temp/exportadvanceddevices_<admin_xxx...dat>)" User information is gathered and filtered through disk files. The disk files would get out of sync if one of the steps (getting the device information) was not done. Also, information gathered for the "Media Pack Report" sheet was gathered whether the report was active on not. It failed looking for device information that had not been read because the "Media Pack Report" was not requested. Changed the User data file setup to use manage two files so a skipped filtering would not cause the export to fail. Changed "Media Pack Report" to only get data if the sheet is requested eliminating the failure reading device information. Added text to all the data file errors to identify what routine and what file were involved. EIR Customer has requirement for setting CLID to a 5 digit value. OpEasy requires that CLID numbers are the full 10 digits. CLID number was validated to the full e.164 number. Changed the CLID number validation to except an extension number as well. Added an option to the user profile rule for CLID number to use the extension number EIR On the Enterprise Import worksheet, EnterpriseVoiceVPNPolicy tab, the Digit Manipulation and corresponding Value columns input up to 8 digit manipulations in multiple rows of the spreadsheet. However, it would make it easier for the customer to fill out if the digit manipulations were in 8 sets of columns on the same row (instead of in a single column) because the customer could then easily cut and paste into the spreadsheet. Move the 8 digit manipulations from separate rows to one row with 8 sets of columns EIR Page 12

13 When assigning a Primary Trunk, the settings in the Primary Trunk section should be moved up one line so there is no blank line at the top of the section. Instead, the blank line should be at the bottom of that section to conform with all other section displays. Correct both the Edit and View mode (if there is a View mode). Adjusted text spacing for trunk information. EIR A device on Alpha (named Aastra6863iDMS _SCA4) has only an SCA line, no primary line. When I run an export (of Alpha enterprise) for Users and SCAs, the device does not appear on the users tab. I believe it should show up as a Device Row since there is no Primary Line associated with it. Attachment provides the export worksheet. Device Rows only show devices that have no lines assigned at all. Added a row called "SCA Only Row" that show devices that have SCA appearances but are not the primary device of any user. EIR Phone Templates --> Definitions - Select a System Template that is only used in a User Profile in another Enterprise. Attempt to delete the template and an error is returned, "Template <name> is in use and cannot be deleted..."the Profile name is given but not the Enterprise and Group. Changed format of error message to show user profile as Enterprise:Group:ProfileName". EIR Advance Export returns spreadsheet version A207. This spreadsheet can be used to run an import but the import spreadsheet version is A215. The Export spreadsheet, A207, does run but it would be less confusing if the Export spreadsheet version was the same as the Import version. Corrected version number in exported advanced spreadsheet (WorkbookAdvanced) did not match version number in import "Get Worksheet". EIR Ran a Basic spreadsheet to delete 500 Users & Devices. The Progress Messages top 2 lines displayed "- Processed 500 Users... Stopped processing after 40 minutes. (Believed the Request ID was 5107) Duplicating the problem with Request ID = has deleted all Users and Devices but waiting for the import page to finish so I can continue, waited 30 minutes so far. Still request was still "active" after 1 hour and 35 minutes. The import ran correctly. After the status message of - Processed 500 Users..." is displayed the import processing deletes the configuration files for all devices that had been deleted. This took about 6 minutes but there are no status messages displayed during this process. Add status messages during the deletion of the device configuration files. Page 13

14 EIR Enterprise Export - Ran an Enterprise Export and the exported spreadsheet was version E207. The Import Enterprise spreadsheet is E213. It would be less confusing if the 2 were the same version. The export and import spreadsheets have different versioning methods. Changed the Enterprise Export version to E213. EIR Inventory Report - The OpEasy Managed (OM) columns are now in the report. Column F is to the right of the User ID. The second OM column, column K, is between the Yahoo ID and the MAC Address which makes no sense. The report is attached. The Inventory Report has several device related columns but there was no Device Name column to identify the device that the other fields were for. Inventory Report - Added the Device Name column so the admin can see the name of the device that the other device fields are for. EIR Enhanced Inventory Report - The 2nd OpEasy Managed, OM, columns is very hard to see/understand. I have attached a report. The Device Name is longer than the space provided so it overruns the OM column. Providing more space for the Device Name should help. I have attached the report. The Device Name column was too short, causing most of the name to overlap into trailing columns. Enhanced Inventory Report - Expand the size of the Device Name column so that most of the name fits in the column. EIR Possibly an enhancement request. This is for when a new user takes over an existing phone number. Customer has the ability to delete voic messages by means other than OpEasy, however, they would like the ability to delete a users voic messages via the OpEasy application. Also, they would like to be able to "reset" the voic greeting message back to the system greeting via OpEasy as well. This is an enhancement request. OpEasy Enhancement request #455 was created for future consideration EIR Possibly an enhancement request. Customer would like the ability to change ring tones for a users individual phone (not per template) via OpEasy. They would also like to be able to turn the ringer off and on by specific line also. Page 14

15 This is an enhancement request. OpEasy Enhancement request #194 was updated for future consideration. EIR If an enterprise is set to 5 Allocated User Licenses and from the Users screen, an edit of an un-managed user is attempted, a warning message appears to say the limit has been exceeded but the edit is allowed. After the edit, the OpEasy License Allocation page shows a negative 1 Available balance and the Available count on the Users page shows "Over allocated by 1". Is OpEasy supposed to allow an edit after the allocation limit has been met? I thought preventing management after the limit had been met was the purpose of this feature... When a Super User adds or edits a user or Polycom phone, a license was added even if no licenses were available When a Super User adds or edits a user or Polycom phone and no licenses are available, do not add a license. Instead, simply allow the administrator to complete the add or edit. EIR When only modifying an Auto Attendant to load a newer version of the same audio file for a personal greeting or announcement, the change does not occur because the filename did not change so the code did not detect the change When no AIN exists for an enterprise, the text field was not getting cleared. Clear Enterprise AIN if no AIN exists for the current enterprise. EIR The "Call Log" and "Speed 100" keys do not work on Aastra 6867i stations. OpEasy builds the soft keys in the configuration file missing a quote from the beginning of the string. To work around this issue, we are adding the settings needed to the extra settings: The leading double quote was being removed when the soft key URI was updated for 'http' or 'https' access. Add the double quote to the text to be substituted back in. EIR Auto Install - When Auto Install is used and the Auto Install Device Id (pseudo MAC address) is entered and confirmed, Auto Install attempts to change the MAC address and device credentials of the selected device (having the matching Auto Install Device Id). However, this fails if the device credentials User Name of some other device is already using the MAC address of this phone. The failure occurs when an OCI 5668 error is returned indicating the User Name is already in use. This issue can occur if a phone is moved from one device to another device only by clearing out the MAC address and not also clearing out the User Name. To resolve this, Auto Install should automatically remove the phone's MAC address from the credentials (User Name) of the other device that is using it. In addition, Auto Install did not return an error when this failure occurred. Instead, it acted like the change occurred successfully. An error message should be returned if an OCI failure occurs Auto install does not check to see if other devices are using the same device credentials username as the device being installed. Check for OCI error code 5668 when an attempt is made to update the device credentials. When this error occurs, search the system for the device that is using Page 15

16 the username in question, and modify the username of that device so the new device can complete installation. EIR When a trunk user is built within OpEasy, it produces a line/port that is of a format similar to primary.tgrp1. The PBX where the calls originate truncate the trailing information and uses just the phone number. OpEasy should be adjusted so that when building a trunk user, the line/port does not append 'primary' and the trunk group name; rather the line/port should simply be the phone number. The rules for creating the line/port for a device were also being used when creating a line/port for a trunk. Use a different set of rules when creating a line/port for a trunk: - For a phone number, only use the phone number - For an extension, use: <Extension>.<CustomizedField>, the <CustomizedField> is typically the SiteId Page 16

17 Page 17