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

eZuce openUC Beta 14.10 Release Notes

Overview

This section describes the eZuce openUC 14.10 software release, including:

  • Software Enhancements
  • Application, Hardware, and Documentation Requirements
  • Installation & Upgrade Instructions
  • Two attachments (PDF files) containing Fixes for internally-reported issues and for customer-reported issues

Software Release History

Starting with the April 2014 release, OpenUC will have a regular release cycle for new features and a new versioning schema which incorporates the Year and Month of release.

  • April release for 2014 is 14.04
  • December release for 2014 is 14.10 (delayed for 14.04.3)
  • April release for 2015 is 15.04

Release Level History

  • 14.04   - April 30, 2014
  • 14.04.1 - June 01, 2014
  • 14.04.2 - July 11, 2014
  • 14.04.3 - October 24, 2014
  • 14.10 - February 5, 2015

System Requirements

For a reasonably performing system we recommend the following configuration.

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

Note: OpenUC supports an unlimited number of voice-mail boxes,the total number of hours of recorded messages is determined by the size of the hard-disk. 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).

  • Operating System:

CentOS/RHEL 6 x86_64 with latest updates is required.An i386 version is also provided as is (without any support).

  • Devices:
    • Phones
      • Polycom VVX Devices with firmware 4.1.6 or later are recommended for new installations
    • Gateways
      • AudioCodes Gateways are recommended for PSTN connectivity
    • SBCs
      • Sangoma, AudioCodes, Acme Packet and Ingate SBC's are recommended for SIP Trunking and Remote Worker connectivity (commonly referred to as sipXbridge and MediaRelay services respectively).
      • NOTE: The eZuce openUC - "Use built-in SIP Trunk SBC" found in Gateway Details for use with Trunking or Remote Worker solutions should be used only for lab purposes. The openUC "Built-In SIP Trunk SBC" (sipXbridge) will not be supported in any production or live environment.

Documentation

Technical Reference Manuals, User Guides, Reach Reference Manuals, and other technical and user information can be found under the following link:Documentation Page

Installation and Upgrade Notes

  • Installation note

After OpenUC 14.10 is downloaded and installed,the clusterId read tag is unique (same as locationId). Follow these steps to propagate the new read tags to the MongoDB replica set:

  1. In the OpenUC menu, click System>Database.
  2. Click the Add query metadata button.
  3. To verify that the MongoDB replica contains the unique read tags, run in the command line:
mongo rs.config();
  • Special MongoDB note

Please be aware of this Mongodb requirementshttp://docs.mongodb.org/manual/reference/ulimit/“Note: Both the “hard” and the “soft” ulimit affect MongoDB’s performance. The “hard” ulimit refers to the maximum number of processes that a user can have active at any time. This is the ceiling: no non-root process can increase the “hard” ulimit. In contrast, the “soft” ulimit is the limit that is actually enforced for a session or process, but any process can increase it up to “hard” ulimit maximum.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.If you limit virtual or resident memory size on a system running MongoDB the operating system will refuse to honor additional allocation requests.After every install/upgrade please check that "cat /proc/$pid_of_mongo/limits" have the recommended value of 655350. To make this value permanent you need to create this file /etc/security/limits.d/99-mongodb-nproc.conf and add the following lines:mongodb soft nproc 64000mongodb hard nproc 64000mongodb soft nofile 64000mongodb hard nofile 64000 .

If you have a patch installed to your system a new patch may be required. Please contact sa@ezuce.com if think you may have a patch applied as that may be replaced during the update.

  • Special Reach note

Please be aware of this Reach Call Recordings Requirement

There is an issue with Reach recordings when upgrading from 14.04 to 14.10.

In 14.04 we allowed customers to manually create directories on disk and to specify path in Reach client, whereas in 14.10 we're recording to a certain path and then uploading files into MongoDB.

The problem is that these old paths are not upgraded in the database, so Reach will try to record in the 14.04 defined paths (that are deleted during migration).

When upgrading from 14.04 to 14.10 execute the following:

psql -U postgres SIPXCONFIGupdate openacd_client SET recording_location='/var/sipxdata/reach/recordings';

Then send profiles to server.

 

Installing from ISO image

Download openUC ISO

Download the ISO image corresponding to your hardware and write the image to a DVD.

Install openUC

  • Boot from the DVD created with the openUC ISO image.
  • Press Enter at the boot screen below to begin the openUC installation.
  • Select Manual Configuration under Enable IPv4 support and select OK.
  • Set a static IPv4 address with the corresponding networking information and click OK.
  • In certain situations an warning of the use of indicated storage devices will be displayed.
  • Select the language to be used during the installation.
  • Select the keyboard layout to be used.
  • Select the timezone to be used.
  • Set a root password.
  • Login to the system as root with the password you provided earlier and continue on to the Configure of openUC.

Installing from Repository

OpenUC can be installed using the below procedure

  • Download and install CentOS 6.x minimal ISO
  • Run the following command:
yum update && reboot
  • Run the following commands to retrieve and run the eZuce openUC installer:
curl https://download.ezuce.com/openuc-setup > /usr/bin/openuc-setup
chmod +x /usr/bin/openuc-setup
openuc-setup

This utility will guide you through the process of installing openUC from the eZuce software repository.

Upgrade from previous versions

When upgrading OpenUC from 4.6 Update 11 or 14.4.3 to 14.10 follow these steps to ensure the SEC service is correctly running:

  • 1. Upgrade from 4.6 Update 11 or 14.4.3 to 14.10.
  • 2. After the upgrade is complete, perform the usual restart.
  • 3. Once possible, connect via CLI and monitor processes using top. Notice that the SEC process is using a lot of CPU memory.
  • 4. Perform another restart OR restart only the Sipxlogwatcher service.

Support Tips and Contact Information

Please see the Getting Support section for support tips and support contact information.

Enhancements, Fixes and Known Issues

Click the following for initial release issues:

14.10 Release Notes

14.10.1 Issues Addressed

UC-3438 - Create Proxy plugin to solve MoH / Ringing overlap for poorly behaving SBCs

The plugin will do the following

1. Check if the sipfrag of a notify is a 180 Ringing 2. Convert to sipfrag 100 Trying before sending to Polycom

End result: Polycom will only send BYE upon receipt of sipfrag 200 Ok. The intention is to let MoH play the entire alerting phase.

In the old use case where call goes to a mobile phone, sipfrag will be 183 Session Progress. This will not be changed by the plugin. This would result to MoH stopping to avoid the media overlap.

1. Disabled by default 2. Will affect only notifies for event refer 3. Will not have any effect on routing, but would effect when polycom tears down MoH.

XX-11584 - Write race on the same TCP socket descriptor

Fixed an issue whereby the socket::send operations are not thread safe and there is the possibility of missing some TCP packets if two threads try to grab the same socket at the same time.

The race condition applies only to TCP and the involved functions are SipClient::isWritable() and SipClientWriteBuffer::writeMore() since they are run in distinct threads.

XX-11585 - TCP failover support

Fixed an issue that was caused when a write operation fails, the TCP transport does not look for an alternative flow (or create a new one). This functionality brings this ability to sipXtackLib.

XX-11586 - Park fails to ringback on key pressed / timeout through SBC

Fixed an issue with calls from external numbers that are parked, on timeout or on transfer key pressed the original caller should ring back but when using an SBC the call fails.

XX-11595 - Upgrade to 14.10 changes working time attendant schedules

Fixed an issue that caused working time attendant to change to UTC.

In 14.04.2 Working time attendant Select attendant to be used during working hours. Working hours can be specified once attendant is selected. Monday From: 9:00 AM To: 06:00 PM

After upgrade in 14.10 Working time attendant Select attendant to be used during working hours. Working hours can be specified once attendant is selected. Monday From: 02:00 PM To: 11:00 PM

UC-3476 - Specifying a SIP endpoint for a Reach Agent has no effect

Fixed an issue that caused a problem when an agent logged in and specified an SIP endpoint for a phone.

Go to the login url with the agent: https://one.ctradu-ha.ezuce.ro/reach/portal/login

Fill in the following details: Username: 3000 Password: <pass> Advanced options: sip:2013@openuc.ezuce.com

Press login.

UC-3508 - When the agents phone is DND a call is offered over-and-over

Fixed an issue with Reach that was caused by Agents putting their phone on DND.

Assume we have a Reach agent called John.

John sets his Reach status as `Available`. After a while he puts his deskphone on DND.

If a call is routed by Reach to this agent while in DND the call is offered again and again to this user, even if the phone returns 486 BUSY.

  • No labels