Page tree
Skip to end of metadata
Go to start of metadata

eZuce openUC Release Notes

Release 4.6.0 Update 11


This Release Note describes the eZuce openUC 4.6.0 Update 11 software release, including:

  • Hardware Enhancements
  • Software Enhancements
  • Application, Hardware, and Documentation Requirements
  • Installation & Upgrade Instructions
  • Fixes for customer-reported problems

Software Release History

Release Level

Rel 4.6.0    

Rel 4.6.0 Update 1    Feb 5, 2013

Rel 4.6.0 Update 2    Feb 6, 2013

Rel 4.6.0 Update 3    March 12, 2013

Rel 4.6.0 Update 4    March 27, 2013

Rel 4.6.0 Update 5    March 26, 2013

Rel 4.6.0 Update 6    May 20, 2013

Rel 4.6.0 Update 7    Sept 9, 2013

Rel 4.6.0 Update 8    Oct 14, 2013

Rel 4.6.0 Update 9    Dec 13, 2013

Rel 4.6.0 Update 10  Jan 30, 2014

Rel 4.6.0 Update 11  March 5, 2014

Product Enhancements

Feature Enhancements in Release 4.6.0 Update 11

No Feature Enhancements included in this Update.

Feature Enhancements in Release 4.6.0 Update 10

No Feature Enhancements included in this Update.


Feature Enhancements in Release 4.6.0 Update 9

New Products:

openUC Reach - Contact Center Solution

  • A new breed of open standards based Contact Center.
  • Web Based Supervisor and Agent Portals
  • Reporting
  • Call Recording

Unite Mobile

  • Clients for iPhone, iPad, Android Phones and Android Tablets.
  • Can be provisioned directly from openUC Admin Portal.  User simply logs in with their openUC extension and system password.

Feature Enhancements in openUC


Provide new levels of redundancy to individual sites.

openUC IVR

Upload customized IVR scripts and prompts to the system.  Pass values to openUC Reach.

openUC License Services

Control the number of users on a system with licenses.

Music on Hold

Music on Hold can now be set for a group of users.  As well, Music on Hold can now run on multiple servers and run as Highly Available.

Phantom Users

Create users that can not have phones registered to them but can be used for call routing duties.

Enable and disable voicemail

In User Portal, user can enable or disable ability of callers to leave voicemail.

Polycom 5.0 firmware support

Polycom’s latest firmware versions are now supported.

Finer grained control over Polycom versions

Ability to distinguish between multiple versions of same firmware.  For example 4.1.2, 4.1.3, etc can all be active and used for different groups of phones.

Increase open files limit in Operating System

Larger systems were running out of tcp connections on server.

Dial by name directory improvements

Allow for dial by name directory listings by group of users.

Block Subscriptions to External Phone Numbers

Users were trying to subscribe to presence for Speed Dials that were associated with external phone numbers.  This was causing RLS services to create floods of SUBSCRIBE messages.

Feature Enhancements in Release 4.6.0 Update 8

Licensing Services

Some basic licensing capabilities will be integrated to openUC.  Some of our OEM customers need to have this capability.  The goal with this product will be to just limit the number of concurrent registrations.

Feature Enhancements in Release 4.6.0 Update 7

Multi-Level Administration

This is a key feature required by MSPs and large companies.  Initial pass at multiple administrator levels. This will block out entire menu items only.

Multi-Time Zones

Support for users being in multiple time zones. Allow users to see their call history, modify call forwarding schedules and hear their voicemail stamps in their own time zones.

High Availability Instant Messaging Services

Allow for multiple IM servers in a cluster.  This will allow larger scale and higher reliability of IM services for large organizations.  openfire 3.8.1 will be implemented which will offers this HA capability.

Call Queuing

Basic call queuing. This will offer similar functionality to the queuing that was available in openUC 4.4 but be more reliable and more robust.  This will not include any sort of Agent or Supervisor portals or reporting.

Radius Authentication

Implement Radius Authentication in support of. Server side work is complete with the Spring security module already implemented.

CAS Authentication

Implement CAS Authentication in support of. Server side work is complete with the Spring security module already implemented. (experimental / no gui support yet)

LDAP ImprovementsImplement

LDAP improvements. eg. Administrative changes in LDAP would be passed through and made in openUC.

oauth for authentication

Implement the ability to use oauth for authentication. Server side work is complete with the Spring security module already implemented.  (experimental / no gui support yet)

SAML authentication

Implement the ability to use SAML for authentication. Server side work is complete with the Spring security module already implemented. (experimental / no gui support yet)

Polycom Phones

Add support for VVX 300 & 400 series phones to the already supported VVX 500, 600 & 1500.  Support video on the phones that also support it.

Emergency ServicesChanges

Create a new proxy plugin that can pass out a user’s ELIN.  Assign Emergency Location information to users / user groups

Polycom Hoteling

Support new Polycom Hoteling feature in firmware versions 4.0 and later.Internal Caller ID Mask / ModifyAbility to change a user's callerID when calling internally on the system.

Feature Enhancements in Release 4.6.0 Update 6

Make Default Polycom Firmware Configurable

Setup support for SIP domain different than Server domain

Enhanced LDAP Sync to block PIN on LDAP Re-Sync

Feature Enhancements in Release 4.6.0 Update 5

Bria mobile provisioning addedAdded support for Polycom 300/310 and 400/410

Configure Time Zone for Users in a Group

Feature Enhancements in Release 4.6.0 Update 4

Allow Call Forwarding Rules to follow a user's Time Zone

New API to query active calls for a particular user

Virtualization of openUC

Feature Enhancements in Release 4.6.0 Update 3

Improved Grandstream Phone Support

Firewalling Improvements

Denial of Service Attack Prevention

Make Relaying of Non-Local SIP Domain Messages Configurable

Allow for Polycom Multicast PTT and Multicast Paging support

Feature Enhancements in Release 4.6.0 Update 2

There were no feature enhancements in Update 2.

Feature Enhancements in Release 4.6.0 Update 1

Polycom VVX support for 500 & 600

Multiple Polycom Firmware Version support

Improved CSV Import Functionality

Firewall Blocking of IP addresses

Hardware Requirements

For a reasonably performing system we recommend the following configuration. This is a rough guide line for a production system.  Media server performance profits from a dual / quad CPU system (dual / quad core CPUs) and lots of memory (2GB - 4GB).

Production systems are not recommended to run on Virtual Servers due to the manner in which the CPU is shared. Timing is critical to voice codecs and virtualization creates problems in production systems.

  • Pentium 4 or Xeon processor @ 2.0 GHz Core 64bit or higher
  • CentOS/RHEL 6
  • Minimum of 4 GB of RAM with sufficient swap space
  • 80 GB disk recommended (75 users depending on usage patterns)

The openUC supports an unlimited number of voicemail boxes, and the total number of hours of recorded messages is determined by the size of the harddisk.  As a rule, for every minute of recorded messages you will need 1 MB of disk space (About 3 hours per 10 GB of disk space).


eZuce Customer Portal

Interested in becoming an eZuce customer?  Want to find out more about our open virtualized communications solutions? Contact us and we will get in touch with you quickly. 

If you'd simply like to join our mailing list and gain access to our exclusive educational content, you can create a user account and get access right away.

Existing customer?  Our eZuce Customer Portal will provide support, user manuals for you to print and share with end users, and a customer forum to connect with open communications users around the world. This is also the place to find our documentation, including the wiki and printable PDFs. Log in here to access your exclusive customer portal.  Also available is access to the Customer Support Portal for direct communication with eZuce Technical Support.

eZuce Technical Documentation

  • eZuce openUC 4.6
  • eZuce Reach (Contact Center)
  • Unite for Salesforce Beta
  • Unite for Zimbra Beta

eZuce Release Documentation

  • eZuce openUC Release Notes
  • eZuce openUC Release Process
  • eZuce Unite for openUC Release Notes
  • eZuce Unite Outlook Add-in for openUC Release Notes

Children Pages

  • eZuce openUC 4.6 Technical Documentation
  • eZuce openUC Release Notes
  • eZuce Unite for openUC Release Notes
  • eZuce Unite Outlook Add-in for openUC Release Notes
  • eZuce Voicemail Integration in Zimbra
  • Integration Toolkit
  • openUC Reach Documentation
  • Unite for Salesforce Documentation
  • Unite for Zimbra Documentation
  • Zimbra Web Unite

Installation and Upgrade Notes

Updating openUC

An update is a newer version of code within the same version (for example: 4.6.0 Update 6 to 4.6.0 Update 9).  Applying updates to openUC 4.6.0 is an easy to do procedure with yum.  It is required that your system have access to download from the Internet.

To update eZuce openUC 4.6:

  1. Perform a backup of the entire system.
  2. Download backup from the server.
  3. SSH to the server and login as root (if you don't have root to the server, login with your non-root account and enter sudo -s).
  4. Run the command yum clean all.  When that completes, run the command yum update.  As long as your openUC instance has access to the Internet, your system should download and upgrade all necessary updates.  (see NOTE)
  5. When the update completes, it's safest to reboot in case there were important operating system updates.  To reboot the server use the reboot command.
  6. If there were no operating system related update you can just restart openUC services issue the command sipxagent -d restart_sipxecs
  7. Send all server profiles after upgrade / reboot.  Login to Admin GUI, click on System -> Servers, Select all servers and click 'Send Profiles' button.

Special NOTE:  The "pymongo" package in our openUC repository is outdated and should be replaced with the differently named but newer version "python-pymongo" package from the EPEL repository. This allows pymongo to upgrade along with other OS packages from the upstream provider (EPEL) rather than eZuce openUC repository.  Not all Updates previous to Update 8 have “pymongo” installed.If upon running yum update you encounter a message similar to:


  • Error: Package: pymongo-2.4.2-1.el6.x86_64 (@openuc)
  •     Requires: python-bson = 2.4.2-1.el6          
  •     Removing: python-bson-2.4.2-1.el6.x86_64 (@openuc)              
  •        python-bson = 2.4.2-1.el6          
  •     Updated By: python-bson-2.5.2-3.el6.x86_64 (epel)              
  •        python-bson = 2.5.2-3.el6          
  •     Available: python-bson-2.1.1-1.el6.x86_64 (epel)              
  •        python-bson = 2.1.1-1.el6
  • You could try using --skip-broken to work around the problem


DO NOT run yum update --skip-broken to proceed.

As mentioned, the "pymongo" package in our openUC repository is outdated and should be replaced with the differently named but newer version "python-pymongo" package from the EPEL repository. This allows pymongo to upgrade along with other OS packages from the upstream provider (EPEL) rather than eZuce openUC repository.To do so, follow these steps:

  1.         $ rpm -e --nodeps pymongo              # Removes the outdated pymongo from the openUC repo.
  2.         $ yum install python-pymongo -y      # Installs newer 2.5 version of pymongo from the EPEL repo.
  3.         $ yum clean all                                     # This will clear any cached repository data. 

At this point you should be able to run 'yum update -y' without issue.


 Review and Set Resource Limits of MongoDB

A very Important configuration of MongoDB.  eZuce openUC installations at customer sites could be expired registration or call completion issues in various scenarios, as openuc components as registrar cannot create mongo connections. 

    Recommended Settings for ulimit

Every deployment may have unique requirements and settings; however, the following thresholds and settings are particularly important for mongod and mongos deployments:

$ ulimit –a

-f (file size): unlimited

-t (cpu time): unlimited

-v (virtual memory): unlimited

-n (open files): 64000

-m (memory size): unlimited

-u (processes/threads): 32000

Always remember to restart your mongod and mongos instances after changing the ulimit settings to make sure that the settings change takes effect.   Note:  If you limit virtual or resident memory size on a system running MongoDB the operating system will refuse to honor additional allocation requests.

For complete description of the requirement, please open and execute the instructions found in the Knowledge Base Article found here.



Disable IPv6

Current releases of eZuce openUC are not IPv6 compliant, so to minimize the exposure of potential issues it is best to disable IPv6.  By default IPv6 interfaces will remain active on CentOS installations even though the interface was not configured. If the IPv6 interface has not been explicitly disabled, services will attempt to bind to them.  To disable the interfaces system-wide, edit /etc/sysctl.conf and append:

    net.ipv6.conf.all.disable_ipv6 = 1   

net.ipv6.conf.default.disable_ipv6 = 1

Save, then reboot the server. This should be applied to all openUC servers within a cluster.

Installation of Reach

Ensuring Contact Center is Licensed

Contact eZuce to obtain a license for Contact Center.

Upload the license via the System --> Licensing page in the admin portal.Ensuring Contact Center is Installed

The openUC Reach contact center is a fully integrated part of the openUC environment.  Therefore, once licensed as discussed above, it is only necessary to do the following:   

  • Login to openUC admin console as superadmin.   
  • Navigate to System -> Servers -> Contact Center   
  • Click on the Check box for Contact Center on the Config Server only (only install on Config server at the current time).

Systems will need to be on openUC 4.6 Update 7 or greater in order to install it.

Starting the Service

In the OpenUC admin UI navigate to:  System --> Servers --> Servers

Select the Server that has the openUC Reach service installed on it

From the links list on the left, select the Services link.

Ensure that the Contact Center service is running.  If it is not, put a check mark in the check box to the left of the service and start/restart the service.  Ensure that the service has a Status of “running”.

Contact Center Service

If the service is not running, check the installation information to ensure that the correct installation has occurred.  If you feel that the installation has taken place as it should have, contact support for guidance.

Distributed openUC

The openUC can be installed as a distributed system spanning several servers that do not have to be geographically co-located.  The openUC management system centrally manages the entire cluster.  Scalability or redundancy can be achieved by running different components, such as redundant call control, voicemail services, conferencing service, call center ACD service or the SIP trunking service on dedicated hardware.

Installation of an additional server starts by creating the new server in the openUC Web admin console.  A specific role for that new server can be assigned upon creation.  A password is created for the new server.  Then the same installation CD is used to install the additional server. When running the installation wizard (sipxecs-setup-system script), it will ask you whether this is the first or an additional server.  For additional servers the password generated by the master is required so that the new server can contact the master and download its configuration.  This will dedicate it into the chosen server role and make the new server part of the openUC distributed but centrally managed system.

Known Issues

Known Issues in 4.6.0 Update 11

  • UC-2386   Update from 10 to 11 will keep the Update 10 version.  After update the Admin Portal still displays that the version is: openUC ( 2014-02-27EST08:02:32 localhost.localdomain) update 10    Workaround:  Manually uninstall sipxrelease rpm version 020140130001433 and then install the correct one 3728.aa570 (rpm -e --nodeps sipxrelease && yum install sipxrelease)
  • UC-2237: SAA service not working in HA setup with 1 node down
  • UC-2275: SAA service not working with Polycom VVX600.  SAA won't work for a period of time for a phone registered / subscribed to SAA using a node that goes unavailable. Service should be again available after phone reregisters / subscribes to a different node
  • UC-2303: Paging group not working when default region is partitioned.  Paging group intermittently won't work if nodes goes down. (To send out SIP messages for phones, page service makes a DNS lookup that could return node in partitioned region)
  • UC-2302: 10 seconds delay when leaving or retrieving a VM, with a partitioned region.  When a region gets separated from main region users will experience delay of seconds between time when voicemail recorded and record confirmation prompt (since service within that region will try to send out MWI notifications to all other regions). The delay varies and depends on number of regions configured with voicemail / MWI services
  • UC-2305: GUI crash in a regions partitioned setup (intermitent).  If new primary elected in global replica set then intermittently UI will show internal error (that is until a new primary is elected)
  • UC-2306: Delay when trying to place calls after server reboot/shutdown in a partitioned region.   Limitation of current architecture in region setup - when node rebooted proxy and registrar will try to make connections to entire global and local replica set. Since region partitioned it will timeout and reattempt max retries on each unreachable node, hence the delay
  • UC-2323: VMs received from other regions won't be updated in a partitioned region.  For a configured region voicemails are left in local database and then synced to global replica set. When retrieving voicemail for an user inside a region both local and global replica set are queried. In case region gets separated voicemails from global replica set can be read (retrieved from local node within global replica set) but they cannot be deleted / updated (since primary node within global replica set cannot be contacted).  For user experience this means he will be able to listen all voicemails but won't be able to delete / mark as read voicemails that were read from global replica set
  • UC-2343: When default region is partitioned,calls between other regions will only work until registrations expire.  This problem will manifest itself if a majority of global database servers is not visible.  For example consider: 3 global database servers with voting rights are available in the US, 1 global database server with voting rights in EU and 1 in APAC. EU and APAC servers are configured as separate Regions with their own local databases.
    Problem scenario: For some reason the US WAN becomes segmented from EU and APAC and there is no redundant IP route.  Result: EU and APAC will be able to call between phones only until remote registrations time out. At that point EU will only be able to call within EU and APAC within APAC.
    Global database layout needs to consider customer's network infrastructure.
  • UC-2344: Delay when accessing VM for the first time after an ivr service restart.  On startup, ivr service on a partitioned region will try to reconnect to replica set nodes and will timeout on unreachable nodes. This behavior could be tuned up.  Under System > Voicemail -> Show advanced -> Database Connection timeout(Default: 5000)Timeout (in milliseconds) for global database connection.  Database Socket timeout(Default: 5000)Timeout (in milliseconds) for global database socket.
  • UC-2355: 500 Error returned ,with no other explanation, when configuring databases (intermitent)  (introduced with db rework and migrating to Dart)
    Can be seen when configuring databases
  • UC-2400: Error after upgrading from Update 10 to Update 11 , and after each reboot.  On each reboot config will show failed job status. This happens due to sipxconfig starting before supervisor. This is Benign.

Known Issues in 4.6.0 Update 10

  • UC-1919    During a conference, if the forward agent puts the call on hold (from UI or phone), both the initial agent and the client will hear MoH.  This issue is related to UC-1807 and is only an issue with some Polycom phones.  In addition to improperly playing the MOH over the top of the conference call, the conference status (in session, on hold) is missing for the invited agent and the conference status is not updated when agent goes on hold.UC-1925   Audio cut through significantly delayed for Reach agent using PSTN.  This may or may not be occurring in the most recent release but we have not fixed it and therefore would expect it to occur in some environments.
  • UC-470    Blind transfer to internal or external number from agent has significant audio delay.  This may or may not be occurring in the most recent release but we have not fixed it and therefore would expect it to occur in some environments.
  • UC-2061   Caller and Agent incorrectly hear MOH during conference setup.  This is related to UC-1807 and only occurs on some Polycom phones.  The specific issue is that when an agent conferences in a second agent, the caller and second agent hear MOH and can talk to one another, while the initial agent is not in the conference.  The expectation is that the 2 agents would be able to communicate and the caller should be hearing MOH.  In this scenario, the original agent can take themselves back off of hold and all parties will be in a conference call and properly communicating.
  • UC-1807  Retrieve the call from On Hold is not working properly.  This is phone specific and does not occur on soft phones that we have tested.  It appears to be specific to some polycom phones.  There is a known work around for this bug.  The work around is to remove musicOnHold.uri from the Devices --> Phone --> Lines --> Registration for the phones that Reach agents are using.  In should be noted that this will result in not playing MOH from that phone on a regular extension call that arrives there.
  • UC-1923   Reach Xfer to extension; Call Dropped transferred too party transfers again.  If phones are NAT'd, the following bug can be exposed.  Here is the scenario: Reach agent is in a call with a customer.  Agent transfers the call to an external number (OpenUC extension).  The external number answers the call and makes a blind transfer to another OpenUC extension.  As soon as the first extension presses dial to finish the blind transfer, the call is dropped.  Hold via PSTN connected Reach agent is likely an issue.  Need to test and write this one up.  I've asked the QA team to do this once they have a proper PSTN environment to test it in.  This is likely to not happen until they upgrade
  • UC-2154   Reach: Occasionally, when the agent hang ups a call from the physical phone the dashboard does'nt clear, it still appears to be on call.  The agent can click the end call button on the UI to clear their state and continue processing calls.
  • No Jira Ticket:  Hold from the UI while using a PSTN line for media connection to a Reach agent will be selectable but will not do anything (you can click it but it won't put the caller on hold or take them off hold).
  • UC-2146   When a call is transferred by a Reach agent to another Reach queue, that call does not hear the configured announcements for the queue that they are waiting in.
  • UC-2153   A Reach queue voicemail is not placed in the queue if the user/caller presses while in the middle of recording their message.
  • UC-2172   Client defined URL popup for a Reach agent doesn't display if the agent portal has been accessed via https.
  • UC-2182   If the My Stats widget is not loaded by default when a Reach agent logs in, their session will reconnect over and over.
  • UC-2181   The last drop down item in many of the agent/supervisor Reach portal widgets are not selectable via the mouse when using a Chrome version that is not up to date (e.g. 32.0.1700.76 m).

Known Issues in 4.6.0 Update 9

Reach (Contact Center)

There are a number of known issues outstanding within the Reach call center application.  Here is a list identifying these issues.  All of these issues are scheduled to be resolved in 4.6 Update 10.

  • UC-1965    Skills set on the agent group are currently NOT inherited by the agents in the group
  • UC-1937    Agent name is not displayed in agent state gadget
  • UC-1933    Disable transfer/conference when calling back for a voicemail    
  • UC-1925    Audio cut through significantly delayed for Reach agent using PSTN    
  • UC-1924    New skills do not show up on agents
  • UC-1923    Reach Xfer to extension; Call Dropped when placing a caller on hold    
  • UC-1922    Wait time is inaccurate in Session Manager for Reach conference/transfer
  • UC-1921    Caller hears silence during attended transfer from Reach to openUC
  • UC-1920    Blind Transfer from phone does not work for Reach Agent
  • UC-1919    Reach Agent conferenced in does not have a hold button
  • UC-1918    Reach Agent is left on line when Transfer to another agent
  • UC-1917    Reach Agent conferenced in is disconnected upon transfer
  • UC-1916    Reach Agent conferenced in cannot Conf/Transfer
  • UC-1857    Statistics - Occupy parameter not updated
  • UC-1807    Retrieve the call from on hold is not working properly
  • UC-1770    Double hold the call from dashboard and phone
  • UC-1583    Openacd-the voicemail tracker pause button not showing the play symbol
  • UC-1564    Getting hold music when transferring call to voicemail

Known Issues in 4.6.0 Update 7

DHCP Service

DHCP Service may not add default route to DHCP configuration.  See for workaround.  A patch is forthcoming in update 8.

Forked Calls

Large numbers of forked calls that are cancelled shortly after the INVITE is received may cause the sipXproxy service to consume system resources.  We’ve discovered an issue with sipXproxy such that when forked calls are canceled not all legs of the call are closed out properly.  This is not a problem during normal operation but could be an issue with call spammers hitting a system.  What was noticed in one particular attack was that the spammers would tend to send INVITES with rapid CANCELS.  A patch is forthcoming in Update 8.

Group Firmware not honored for Imported Phones

The Group Firmware setting was not being honored for imported phones.  The workaround is to send phone profiles for any phones that were imported. Internal issue # UC-1368. A patch is forthcoming in Update 8.

Multi-Level Administration

Administrative user accounts that are not the 'superadmin' account will not be able to see any menu's in the Admin GUI until the user 'superadmin' logs in, creates an Administrative Group, Adds Users to the group and then Adds permissions to the Administrative Group.  See Admin Roles in Users menu for configuring this.

openUC Call Queue

To enable the new openUC Call Queue feature, after ‘yum update’ to openUC 4.6 update 7 is complete, run ‘yum install sipxcallqueue’.  Once this is complete, restart services ‘service sipxecs restart’.

Known Issues in 4.6.0 Update 5

The text here will be integrated to release notes for updates / releases. This file to be pre-pended to list of closed items. This list is for known PT items that may cause user problems.Workarounds for each item will be documented if known.

User Portal

GMail Contact Import - GMail’s certificates seem to have changed and this is causing an issue with users being able to import contacts in their user portal. Workaround: None.Internet Explorer 9 & 10 - Voicemail playback functionality is broken in UI using IE10 or IE9. Workaround: Using the user agent switcher (hit F12 for development tools within browser 9 or newer) and switching to IE8 this works. Commenting out html5 within sipxconfig.war fixes the issue.


  • Admin Portal - Problems with translation to German in Admin Portal. A number of words are wrong on various pages. Workaround: None.
  • Admin Portal - Disabling Firewall also disables Intercom function. Workaround: Re-enable Intercom check box.
  • Admin Portal - When IM service enabled, it should also enable the dependent services. If using IM and wish to monitor the phone status of users in IM, the Network Queue and Network Queue DB services need to be enabled. Workaround: If using IM, enable Network Queue and Network Queue DB services.
  • Admin Portal - If an Auto Attendant is created without a valid prompt or if all prompts are deleted, the config server will throw an exception and the auto attendant.xml file will not be produced. The exception is:

"2013-01-17T14:09:58.045000Z""Exception in background task." java.lang.NullPointerExceptionat<init>( at org.sipfoundry.sipxconfig.admin.dialplan.AutoAttendant.getPromptFile( at org.sipfoundry.sipxconfig.admin.dialplan.attendant.AutoAttendantsConfig.generateAttendants( 

Workaround: Ensure that Auto Attendants have valid prompt WAV files.

  • Admin Portal - MongoVCardProvider reads vcards from profiles' s gridfs storageIf user uses an external image for avatar, nothing is saved there, and the default avatar is used. Workaround: Do not use external Avatar images.
  • Admin Portal - Some German translations of Admin portal are not correct. Workaround: None.
  • Backup / Restore - Backup / Restore does not handle custom AA prompts. Workaround: Copy AA prompts from old server to new server manually, set owner / group to sipx:sipx for all files after copy.
  • Backup / Restore - During the restore of a 4.4 VM backup into a new 4.6 system, the voicemail records made by users are not loaded into gridFS. The system defaults are played after the restore is complete. Workaround: A patch is available through support for this issue (called openuc-ivr-gridfs.jar). Apply the patch as directed and from your voicemail backup, restore the personal greeting files (standard.wav) back on the server into the same directory as before (var/sipxdata/mediaserver/data/mailstore<user ID> and change ownership to sipx:sipx. Then restart voicemail. When it restarts, the file should load into the mongo database and then play.
  • Backup / Restore - On restore of 4.4 data to 4.6 system, device cleaner should not block if zip files are not present in backup. Workaround: Remove device files from 4.4 before backup as a workaround.
  • Backup / Restore - The settings for Enable NAT Traversal and Server behind NAT are not updated by the restore of a 4.4 backup to a 4.6 install. After the restore, these settings are set to enabled even if they were set to disabled on the 4.4 system. Workaround: Manually reset NAT settings in Admin GUI.
  • Backup / Restore - If incorrect credentials/path are input to the FTP backup routine it will succeed on backup, but not transfer. This results in no cleanup routine following backup limit parameter. The disc space can quickly become consumed with backups that should've been cleaned up. Workaround: Make sure to use proper FTP credentials and check to see that backup runs as scheduled.
  • Backup / Restore - Openfire properties not replicated to postgres when backup restore. Workaround: Send Server profiles, restart Instant Messaging services.•    Backup / Restore - Wrong owner on “Unmanaged TFTP” Files upload directory after 4.4 restore to 4.6 system. If there are uploaded device files as “Unmanaged TFTP” entry in a 4.4 backup that you restore on a 4.6 system, the owner of the directory is wrong after restore. The net is that it will not allow you to add a new file as part of that set of files. For example, a customer attempted to attach another file of German dial tones to an existing entry that existed in 4.4. When the customer attempted to same the entry after uploading the file, they received the following exception: "2013-04-22T13:34:32.650000Z""Unable to process client request: Could not upload file german_tones.cfg" org.apache.hivemind.ApplicationRuntimeException: Could not upload file german_tones.cfg [context:/WEB-INF/upload/, line 3, column 80].... Caused by: /var/sipxdata/upload/5/german_tones.cfg (Permission denied). Checking the ownership of the directory that the file is uploaded to (/var/sipxdata/upload/5 in this example) shows that it was owned by root. Workaround: Changed it to sipx:sipx (chown sipx:sipx /var/sipxdata/upload/5) and the file could then be uploaded.
  • CDR - On an HA system, after a reboot, the following can be seen in the logs of the primary:"Loss of connection to database•    <struct DatabaseUrl database=\"SIPXCDR\", port=5432, host=\"\", adapter=\"postgresql\", username=\"postgres\"> - retrying to connect after sleep". Workaround: "/etc/init.d/sipxcdr restart" fixes this (until the next reboot).
  • External Aliases - External aliases feature from openUC 4.4 is not present in 4.6. Workaround: None.
  • G.729 Codec - If a customer installs G.729 licenses on the system, we are starting the license manager with the user sipx. According to freeswitch, the licensing server needs to be started by root. The result is that the licensing server does not start and you can not use the codec. Workaround: Manually start licensing server as root by logging in to the server as root and issuing /usr/sbin/freeswitch_license_server
  • Import / Export - You get this error in sipxconfig log for each user imported. "2012-10-17T15:11:39.114000Z""TransactionSynchronization.beforeCompletion threw exception". Workaround: Benign, user imports successfully.
  • LDAP - When LDAP authentication is implemented, there is a long delay in the login process for those users such as superadmin that are not authenticated. Workaround: None.
  • Postgres Database - The remote database server can be accessed without a password. It is possible to connect to the remote PostgreSQL database server using an unpassworded account. This may allow an attacker to launch further attacks against the database. Workaround: Leave firewall (iptables) rules enabled. iptables limits access to postgres ports from cluster member servers only.
  • Setup - When resetting the config using "sipxecs-setup --reset-all", all config should be wiped out. The phone profiles from /var/sipxdata/configserver/phone/profile/tftproot are not deleted with this command. Workaround: Remove all files in /var/sipxdata/configserver/phone/profile/tftproot
  • SIP Capture - Packets may be missing from Homer SIP Capture due to a timing issue with message queuing mechanism (SQA) that sends SIP packet info to database. Workaround: None.
  • SIP Capture - The pcap file that is generated from the call flow after clicking on a call-ID after a search in Homer only contains the first 100 messages and not the full list of messages associated with the call. Workaround: None.
  • SIP Capture - Requesting searches of time spans of more than 15 minutes takes a long time / times out. Workaround: Specify smaller time spans to get around the problem.
  • SIP Capture - SIP Capture database using large amounts of disk space. Workaround: If SIP Capture is enabled, ensure lots of disk space is available. You could also periodically drop the database.
  • SIP Capture - When using either the session-ID, From User, or T User in the PCAP Factory on the Toolbox page, the resulting pcap file is empty. The call-ID used in the Match value was taken directly from the results of a Search as was the To and From values. Workaround: Download PCAPs from Message Flow.
  • SIP Proxy - Attempting to move SIP proxy from 5060/5061 to 8560/8561. The proxy moved fine, but the managed DNS did not update. Re-sending profiles didn't help. Customer verified it wasn't a cache problem by looking at the zone file directly. It stayed at 5060 there. Workaround: Set DNS to manual and adjust manually or do not change proxy ports.
  • Voicemail - If your disk fills, voicemail stops working. Workaround: Monitor disk space on all servers and allocate more if needed.•    Voicemail - If a user tries to add comments to a forwarded voicemail and the system is set for MP3 voicemail, the comment is not added to the forwarded message. Workaround: If this is an important feature, set voicemail at system level to WAV.
  • Voicemail to eMail - The links to the user portal embedded in the voicemail email notification display as a picture, not as a link when displayed in mail on the iPhone, iPad, or Mac mail. Workaround: Attach WAV or MP3 and don’t use message links.
  • Devices
  • Autoprovision - Rebooting an auto provisioned Polycom phone which has not had its profiles sent will cause an error in sipxconfig.log:"Failed to add phone - duplicated serial number."$DuplicateSerialNumberException: &error.duplicateSerialNumberException at at sun.reflect.GeneratedMethodAccessor222.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke(

Note that this error is benign, however, having such a phone in an infinite loop will fill sipXconfig log with such errors and more harmful, DB queries. Workaround: when having a phone in an infinite loop, turn it off until its problem can be solved. Selecting correct firmware version for this phone and sending profiles will also solve the issue.

  • Autoprovision: a non-provisioned phone with 3.2.X firmware version will go into infinite loop. That is because default firmware in 0000000000.cfg is 4.0.X so a phone with 3.2 will be served 4.0 profiles, and that it would not be able to interpret. Workarounds: for a reasonable number of phones, setting the firmware to 3.2 and sending profiles will fix the issue. For a large number of phones:

- find 000000000000.cfg.vm (/etc/sipxpbx/polycom/000000000000.cfg.vm) and open for editing- find:#set( $default_fw = "${cfg.DefaultFirmware}" )#macro( ModelSpecificAttributes $fw )#if($fw == "3.1.X")#ModelSpecificAttributes31( "")#elseif($fw == "4.0.X")#ModelSpecificAttributes4( "", "4.0.X")#elseif($fw == "4.1.X")#ModelSpecificAttributes4( "", "4.1.X")#elseif ($fw == "2.0")#ModelSpecificAttributes20("")#end#endreplace with:#set( $default_fw = "3.2.X" )#macro( ModelSpecificAttributes $fw )#if($fw == "3.1.X")#ModelSpecificAttributes31( "")#elseif($fw == "3.2.X")#ModelSpecificAttributes32( "")#elseif($fw == "4.0.X")#ModelSpecificAttributes4( "", "4.0.X")#elseif($fw == "4.1.X")#ModelSpecificAttributes4( "", "4.1.X")#elseif ($fw == "2.0")#ModelSpecificAttributes20("")#end#endThis would basically make the default firmware to 3.2 and serve the phone 3.2 profiles.

  • Bria - Counterpath has changed the name of the DTMF parameter in their .ini file. We need to change our provisioning template accordingly. Workaround: Manually configure Bria if required settings are not working.
  • Polycom 670 - Appears in auto provisioning as Polycom 650. Workaround: Manually change model from phone’s identification page in admin portal to Polycom 670.•    Polycom VVX1500 - Does not select eZuce background image. Workaround: Manually select logo from phone.
  • Polycom SoundStation - Codecs for SoundStation 6000/7000 not set when in phone group type of SoundPoint. If you have Polycom SoundStation IP 6000/7000s in a group of phones with other SoundPoint models and you attempt to set the codecs for the whole group and use a SoundPoint model (i.e. 450, 650, 670), the generated configuration files for the SoundStations to not contain the applied codec list. Workaround: To set the code list for the SoundStations, have all IP 6000/7000 in the same group and select SoundStation IP 6000/7000 as the phone model or set the codec for the individual phones.

Resolved Customer Reported Problems

Problems Resolved in 4.6.0 Update 11

            JIRA #                       Summary   

  • UC-2200     Registrar responds 200 OK without DB write confirmation
  • UC-2301     Cannot leave VM when default region is partitioned.  Voicemail write concerned was set as MAJORITY, so in a replica set with 8 nodes it would wait for 5 to consider success. However in case when only 3 nodes available (voiting priority off on other) write operation won't complete even there's a primary. Use vm write concern of SAFE, that is Write operations that use this write concern will wait for acknowledgement from the primary server before returning (if vm written to primary consider good to go)
  • UC-2327     Inconsistent standard and name .wav file replication across nodes.  Made sure there is only one greeting recorded in system
  • UC-2345     openuc-ivr-gridfs pointing to old mongo driver

Problems Resolved in 4.6.0 Update 10

            JIRA #                       Summary   

  • UC-1804    Login page https to http redirect problem   
  • UC-1777    Blind transfer out of call queue fails

Problems Resolved in 4.6.0 Update 9

            JIRA #                       Summary   

  • UC-1472    Proxy should forward statelessly multiple 2xx responses to INVITE requests   
  • UC-1401    LDAP: XMPP presence not working when Openfire integrated with LDAP   
  • UC-1398    Order of gateways in dialplan not being followed correctly   
  • UC-1368    Group Firmware not being honored when phone is imported.   
  • UC-1303    SF2457 / Zen 555: sipxrelay doesn't restart reliably   
  • UC-500    SIP proxy port change doesn't update DNS   
  • UC-498    Unable to send voicemail-to-email   
  • UC-268    When adding user check if permitted by license.   
  • UC-145    Licensing Alarms   
  • UC-134    Block subscription to presence to numeric values that are not openUC userIDs   
  • UC-75     Set time on Holiday AA

Problems Resolved in 4.6.0 Update 8

  No Bug Fixes were delivered in Update 8.  Only New Features.

Problems Resolved in 4.6.0 Update 7

               Jira #                         Summary

  • UC-1499    ZENDESK 521: HTML5 tags: Chrome cannot compute mp3 duration
  • UC-1459    DNS port not added in firewall when DNS unmanaged
  • UC-1393    Firewall Entries missing in OpenUC
  • UC-1211    Resolve MWI for Aliased Domains
  • UC-1166    Improper Call Routing when transffering PSTN call on system configured with multiple branches and gateways at a branch
  • UC-1132    Paging does not work to NAT'ed phones
  • UC-790    Login page displays invalid username/password error if not connected to DB
  • UC-756    Option to receive only unheared messages via IVR
  • UC-690    HTML5 tags/checks in voicemail playback
  • UC-646    Setting the wrong port option for RTP in iptables
  • UC-578    Device Files management allows two instances of the same firmware to be activated at the same time.
  • UC-507    Counterpath configuration parameters names have been changed for Bria 3.x
  • UC-467    Voicemail Email Notification malformed
  • UC-309    Expose Radius Configuration in GUI
  • UC-306    Add Radius to Spring Authentication
  • UC-301    Allow administrators to select Radius or LDAP as authentication protocol
  • UC-282    open DNS port in iptables if DNS is enabled
  • UC-240    Add mongodb providers for Openfire
  • UC-228    Unite and XMPP authentication with Radius
  • UC-8    Click to Dial call does not utilize Location   = Problems Resolved in 4.6.0 Update 6 =                    Jira                      Summary
  • UC-1128    Calls hold/pickup fails in a HA setup with two servers and shared lines
  • UC-739    Ticket 384: IVR Transfer Failures
  • UC-724    Change Login Page to use Password not PIN
  • UC-710    inconsistency in Polycom phone groups profiles selection
  • UC-680    Internal error when creating Firewall group, click apply then ok button
  • UC-670    Backup/restore does not handle AA prompts , closed the issue.
  • UC-632    When deleting user, the user's conference bridge is not deleted.
  • UC-631    Change default for Missed call Tracking to Disabled for a phone group
  • UC-614    Voicemail Notification email malformed for iPad, Mac Mail
  • UC-597    Too many AA, cannot delete them
  • UC-521    Useless warning messages in config log related to polycom profiles
  • UC-499    "On the phone" is not displayed when call initiated from Unite client
  • UC-428    Bria cmcprov and LDAP authentication
  • UC-422    Voicemail permission not replicated when vm role enabled
  • UC-245    Make the default Polycom Firmware version configurable
  • UC-234    Have profiles for autoprovisioned phones generated on disk even before "send profiles"
  • UC-224    support installations with sip domain different than network domain
  • UC-216    A user should be able to know what update they have installed
  • UC-123    Change default for Everyone parameter for phonebooks
  • UC-120    Fix sipxconfig_archive.rb script
  • UC-56    Allow media upload for media announce step on openacd
  • UC-53    Provide ability to block updating voicemail PIN during LDAP sync
  • UC-23    4.6.0 Update 6

Problems Resolved in 4.6.0 Update 5

                   Jira                    Summary

  • UC-1191    4.6.0 update 5
  • UC-1111    Continuous increase of memory usage in sipXproxy related to Homer
  • UC-744    IM Messages not being logged
  • UC-732    Homer login fails if local mongo instance is in SECONDARY state
  • UC-726    Freeswitch conference config is wrong if you disable DTMF
  • UC-705    Remove ACD Agent Supervisor tab in edit user page
  • UC-703    deleting and re-adding same user problem with IM ID
  • UC-686    mongo replica set config should be captured in snapshot
  • UC-671    iptables blocks tftpd
  • UC-642    User in group with IM enabled not found in resource-lists
  • UC-634    No warning/error is shown when RLS is enabled on multiple servers
  • UC-604    sipxbridge startup sequencing problem
  • UC-566    Can't change speed dial entries after upgrade from 4.4 to 4.6.
  • UC-562    mysql start exercised on every configuration replication
  • UC-559    Voicemail Inbox-Unread messages should be played first
  • UC-522    Line protocol is not being updated
  • UC-474    OpenACD init script is symlinked to missing file
  • UC-465    Call waiting beep not being played due to configuration file problem
  • UC-461    Polycom 4.1.3 firmware unzip
  • UC-434    Polycom 670 wrong model in provision servlet
  • UC-417    SoundStation IP 7000 missing supported firmware
  • UC-260    Add back support agent dial strings in openacd
  • UC-215    Add Bria Mobile provisioning option - featured
  • UC-200    Add emergency response location information to user record
  • UC-126    User call detail time zone
  • UC-124    Add support for Polycom VVX 300, 310, 400 and 410
  • UC-115    Configure time zones for users, groups
  • UC-71    Admin should be able to set agent call disposition options
  • UC-26    4.6.0 Update 5

Problems Resolved in 4.6.0 Update 4

               Jira                                 Summary

  • UC-1265    SBC - Create stand-alone RTP Proxy.
  • UC-1255    SBC - Update sipXsbc code to proxy media for NAT/Remote worker calls
  • UC-1239    SBC - Create client server RPC API for RTP proxy
  • UC-1233    Finalize sipXsbc package to be ready for colab
  • UC-1229    Get familiar with sipXsbc
  • UC-1227    SBC - Port Karoo Bridge RTP Proxy to a reusable class in OSS CORE
  • UC-1213    OsTimerQueue improvement - add ids to timers
  • UC-1202    SBC - Support transaction forking (parallel) in OSS Core SIP stack
  • UC-1192    4.6.0 Update 4
  • UC-1148    High memory usage for sipxregristrar
  • UC-748    PTT and paging groups: Change address field name to Multicast Address
  • UC-719    circular dependency in openacd beans
  • UC-708    HTTP/HTTPS auto-provisioning does not seem to work
  • UC-702    Clustermachine-when yum updated to latest stable build, found that replica set under Databases is displayed as "Unconfigured" for all the servers
  • UC-699    Polycoms should not "useDirectoryNames" by default.
  • UC-606    Internal exception while adding DID number to Line in Contact Center
  • UC-596    Error when adding polycom phone
  • UC-584    service mongod stop shuts down arbiter too
  • UC-259    Configure Branch in a Time Zone
  • UC-250    Voicemail timestamps should be in the time zone a user is in
  • UC-237    User call forwarding rules should follow time zone
  • UC-229    Grandstream Plugin Fixes
  • UC-130    Create API to query active calls only for a particular user
  • UC-63    Admin should be able to add add 'transfer outband' as a recipe action in openacd
  • UC-28    4.6.0 Update 4

Problems Resolved in 4.6.0 Update 3

                Jira                                 Summary

  • XX-10137    Create plugin for Polycom VVX500 phone
  • UC-1256    make relaying of none local domain SIP messages configurable.
  • UC-1244    Add functionality to allow proxy to stick to TCP if dialog started using TCP transport (Add transport=tcp in record-route)
  • UC-1240    OsTimer improvement: set _isRunning value to false early within the onTimerFire callback to avoid race conditions when other thread calls isRunning() method.
  • UC-1234    Safer timers creation in stacklib and other sip components
  • UC-1224    Safer SIP transaction timers handling by usage of the OsTimerQueue
  • UC-1218    Log and assert in case objects receive invalid data
  • UC-1210    If mongo is unavailable, SAA and RLS service should send 500 error instead of shutting down
  • UC-1203    Support inbound aliases of users and domains processed in one pass.
  • UC-1193    4.6.0 Update 3
  • UC-1170    sipXproxy uses mongodb port
  • UC-1169    Race in resources deallocation from OsTimer
  • UC-1168    Proxy wrongfully modifies registrations containing two contacts
  • UC-1163    Small changes in OsTimer implementation to make it safer
  • UC-1152    Sometimes sipXsaa consumes most of the CPU
  • UC-1150    Sometimes registrar does not accept reg subscriptions from SAA
  • UC-1141    Memory leak under call load in sipXproxy
  • UC-1127    When the user does not answer the call it does not get transferred to the voicemail
  • UC-1125    When a user defined sip header is removed from a sip message, getSipHeaderValue() returns an empty string instead of NULL.
  • UC-1122    Random crashes of sipXhomer in sqa client code
  • UC-1117    When SQA server is down, proxy plugin takes 3 seconds to queue a message. This is due to a reconnect attempt to recover a lost connection. If a connection to SQA is severed, calls to send AndReceive must return false right away until the next time k...
  • UC-1108    sipXhomer leaking memory
  • UC-1106    sipXsaa duplicates restarted reg subscriptions
  • UC-1087    Create fix for sipxregistrar leaks reported by valgrind and other leak detection tools
  • UC-1086    Callpark - The call is not connecting to call park extension
  • UC-723    Unable to receive email notification for PROXY_EMERG_NUMBER_DIALED alarm
  • UC-704    Add german translation for GWT components
  • UC-661    system related alarms are not sent via email
  • UC-624    Adding 2 or more mongo service at same time doesn't work
  • UC-615    ivr alarms are not triggered
  • UC-585    On send profiles, resource-lists.xml might have incomplete data
  • UC-518    Restore fails if no avatar db present
  • UC-478    group.version tab shown on phone page if firmware not 4.0
  • UC-315    Add new Proxy option SIPX_PROXY_RELAY_ALLOWED to control relay behavior
  • UC-288    Polycom secure provision
  • UC-281    PTT and group paging params
  • UC-276    Enable iptables Logging
  • UC-226    Document Polycom 4.0.x Firmware Settings
  • UC-197    Unitialized servers should not be shown in services page
  • UC-185    Grandstream Provisioning Improvements
  • UC-177    Document new firmware upload page changes
  • UC-176    Add flag to turn off account creation notifications during restore
  • UC-175    Admin should be able to set additional openacd client options
  • UC-160    Raise alarms when issues with Mongo
  • UC-152    Enable video capabilities of freeswitch mod_conference
  • UC-99    Add new config param SIPX_PROXY_ENSURE_TCP_LIFETIME
  • UC-87    Add fail2ban as sipXecs core service
  • UC-79    Add the ability to easily block ranges of IP addresses right in the GUI
  • UC-73    Investigate the possibility of an automated migration from 4.6 to 47 for polycom phones
  • UC-60    Database page: add option to specify voting / non-voting replica set members
  • UC-55    Review / commit Domenico's patch for SNOMs
  • UC-27    4.6.0 Update 3

Problems Resolved in 4.6.0 Update 2

Revert "PT-42880563 : When timer C fires and an INVITE transaction is already within or beyond the COMPLET

Problems Resolved in 4.6.0 Update 1

                  Jira                        Summary

  • XX-7151    Allow change of user MOH source without restarting the phone
  • UC-1268    Redesign of RLS subscription termination to phone
  • sUC-1252    Modify ResourceListSet to use shared pointers for resource list documents to get rid of locks
  • UC-1223    Modify SipSubscriptionClient class to use boost::shared_ptr and standard containers to get rid of locks
  • UC-1222    Add a utility class in portlib to maintain a queue of timers
  • UC-1216    Modify SAA AppearanceGroupSet to use shared pointers to get rid of locks
  • UC-1215    Modify subscription user agent classes to use boost::shared_ptr and stadard containers to get rid of locks
  • UC-1201    RLS: find a workaround to split large notifies to smaller segments.
  • UC-1199    Redesign of SAA subscription termination to phones
  • UC-1190    4.6.0 Update 1
  • UC-1161    sipXsaa deadlocks during a 10 cps test harness run
  • UC-1145    NTAP: Modify session level connection address when rewriting SDP.
  • UC-1098    sipXproxy useragent queue deadlocks after 20 K calls
  • UC-683    EFK does not seem to work
  • UC-626    Add back removed features from config files
  • UC-600    license does not get uploaded where it should
  • UC-557    on group firmware change phones fw can be changed to unsupported version
  • UC-546    cfnew appended to web portal configuration backup
  • UC-541    autoprovision line does not display correct label
  • UC-538    Restore fails if no avatar db present
  • UC-529    add option to disable XMPP presence
  • UC-502    Disable Forward softkey from models supporting it
  • UC-488    LDAP import: user gets modified if duplicated username
  • UC-308    Validate config files against schema provided by Polycom
  • UC-291    XX-10492 - Add Max Sessions option value validation in Park Server Settings
  • UC-264    split bean definitions of Phone models defined as polycom XXX/YYY. Remove unsupported phones on upgrade.
  • UC-251    document 4.0 upgrade
  • UC-242    Add more validations in order to prevent failures if the CSV file has wrong values
  • UC-231    Calendar integration for VVX 600
  • UC-211    Field validation of Server Group IP addresses
  • UC-199    new codecs for Polycom VVX500UC-183    XX-10448 - Alphabetize Services List
  • UC-181    Display port or port range in admin gui
  • UC-180    add back support for 300 and 500UC-178    Firewall should be able to block all traffic from specific IP addresses or range of addresses
  • UC-142    evaluate a smaller eZuce logo for Polycoms that support background image
  • UC-131    Enhance Import tool capabilities
  • UC-111    add calendar feature for vvx 500 and 1500 running 4.0.1 fw
  • UC-110    XX-10449 - If a user specifies https://serveriporname and login as superadmin, redirect is to http and doesn't work
  • UC-92    XX-10414 - Re-organize server roles menus
  • UC-91    Review / improve all labels and descriptions in polycom plugin settings
  • UC-83    Merge Polycom code from master to 4.6-updates
  • UC-78    Improve help text on Restore page
  • UC-25    4.6.0 Update 1
  • UC-16    Support backup / restore with Polycom phones from 4.4 to 4.6
  • No labels