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

 

Overview

This section describes the eZuce uniteme and reachme 16.08 software release, including:

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

Software Enhancements

eZuce is pleased to announce the General Availability Release of uniteme and reachme 16.08. With this release we’re getting back on schedule after being thrown off a bit earlier in the year.

We’re continuing to focus more on fixes and minor improvements in uniteme 16.08 as work ramps up on the next generation of code. For those who watch the code repositories you should start to see some new projects appear.

reachme however sees major enhancements as part of 16.08. After introducing the new reporting capabilities in 16.04, 16.08 follows that up with a slew of new standard reports. Additionally with feedback from customers we continue to adjust the Agent and Supervisor widgets to get at the data that those users want to have available.

Also as always, thanks to the Dev & QA team at eZuce for their excellent work on this release.

In all 90 issues (enhancements / fixes) are addressed for uniteme and reachme in this release.

The next uniteme and reachme release will be 16.12.


Highlights

uniteme New Features

  • Unite Web and Lite (new user portal) get Call History

  • Unite Web Referential URL on Logout

uniteme Improvements

  • Unite Web and Lite gain ability to add speed dials to non numeric users and SIP addresses

  • Polycom support added for new 301, 311, 401, 411, 501 and 601 phones

  • Polycom firmware 5.x and later adjust default line labels

  • Moved several dangerous Polycom settings to Advanced pages

  • Expose TCP option for sipXbridge

  • Add option to pass p-asserted-identity

  • Add new ring types for Yealink phones

  • Adjust MP3 bitrate and frequency

reachme New Features

  • New set of Standard Reports

    • CDR Report with Wrap up, Agent Node, Original Skills and Final Skills

    • Weekly Report with:

      • Total # of inbound vs. outbound calls / agent

      • Total # of minutes/hours

      • Total raw # of calls

      • Total # of transferred calls

      • Total # of completed calls

      • Ability to filter out Inbound & Outbound

    • Daily Report with:

      • Total # of minutes/hours in the given date/time range

      • Total raw # of calls

      • Total # of transferred calls

      • Total # of completed calls

      • Average hold time

      • Ability to filter out Inbound & Outbound

    • Client Traffic Detail Report (similar to Queue Traffic Detail Report)

    • Client Traffic Overview Report (similar to Queue Traffic Overview Report)

    • Agent Activity Report

    • Agent Group Activity Report (similar to Agent Activity but rolled up for agent groups)

    • Outbound Overview by Client Report

    • Line Traffic Detail Report (similar to Queue Traffic Detail Report)

    • Line Traffic Overview Report (similar to Queue Traffic Overview Report)

Screenshots of a couple of of the new ReachMe reports:

AgentActivityByGroup-Output.PNG

ClientTrafficDetail-Outputs.PNG

reachme Improvements

  • Existing reports improvements

    • Add inactive queues/lines/clients to Queue/Line/Client Overview Reports

    • Add the following columns to the Queue/Line/Client Traffic Detail Reports:

      • Sent to voicemail

      • Transfer out

      • Total Abandon

      • SLA

    • Queue Traffic Detail Report to show periods with no activity

    • Agent and Agent Group Productivity Reports to show values or percentages

  • Improve Recordings Archiving so that Archived messages can be played from GUI.

  • In Session Manager added an enhancement to be able to see the call status of an outbound conference.

  • End user improvements in the outbound widget when making a call.

  • Allow a Reachme agent to change Release Reason while in Released mode.

  • Added an enhancement for Advanced Login  to disable the continue button once there is a valid entry in the sip uri field.

  • Added a configuration parameter to set an interval for statistics being generated to minimize database accesses and improve performance.

  • Added an enhancement to better validate data entered by users in the phone number field of the Transfer / Conference list.

  • Enhanced the Agent Manager Agent Section to show that an Agent is on an outbound call and not just in session.

  • Enhancement to update the agent group section of the agent manager widget to show in session count for inbound and for outbound.

  • Enhancement to update the in session counts in the Agent manager group section.

Important Notes

None.

Software Release History

We're currently running on a 4 month release cycle.

  • April release for 2015 is 15.04
  • May release for 2015 is 15.05
  • June release for 2015 is 15.06
  • August release for 2015 is 15.08
  • October release for 2015 is 15.10
  • December release for 2015 is 15.12
  • February release for 2016 is 16.02
  • April release for 2016 is 16.04
  • August release for 2016 is 16.08

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
  • 15.04 - April 29, 2015
  • 15.05 - May 27, 2015
  • 15.06 - June 30, 2015
  • 15.08 - August 31, 2015
  • 15.10.1 - December 9, 2015
  • 15.12 - January 6, 2015
  • 16.02 - March 14, 2016
  • 16.04 - May 31, 2016
  • 16.08 - August XX, 2016

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)

Notes:

  • uniteme 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).
  • reachme requires more memory, processor and disk space. Please consult with eZuce SA team for your specific installation.

Operating System

CentOS/RHEL 6 x86_64 with latest updates is required.

Devices

Phones

  • Polycom VVX Devices with firmware 5.2.5 (split) are recommended for new installations
  • Polycom SoundPoint IP Devices should run firmware 4.0.7 (split)

Gateways

  • AudioCodes Gateways are recommended for PSTN connectivity

SBCs

  • Frafos, 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 uniteme - "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. Additionally sipXbridge does not work in a HA 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 uniteme 16.08 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 uniteme 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 64000
mongodb hard nproc 64000
mongodb soft nofile 64000
mongodb hard nofile 64000

Special Patch Note

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.

Installing from ISO image

Download uniteme ISO

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

Install uniteme

  • Boot from the DVD created with the uniteme ISO image.
  • Press Enter at the boot screen below to begin the uniteme 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 uniteme.

Installing from Repository

uniteme can be installed using the following 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 uniteme 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 uniteme from the eZuce software repository.

Upgrade from previous versions

Modify the repo file in /etc/yum.repos.d and replace the baseurl= with the location of the repository you'd like to upgrade to.

Identify any existing 'rpmnew' or 'rpmsave' files on the system with:

find / -print | egrep "rpmnew$|rpmsave$"

As root, execute the following commands:

yum clean all
yum update

Note any additional 'rpmnew' or 'rpmsave' files that may have been created by running find command again:

find / -print | egrep "rpmnew$|rpmsave$"

If there are any files that didn't get overwritten by yum, please see 'Modified Files Upgrade Note' information below.

A system reboot after the update has completed is recommended.

SEC Service Upgrade Note

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

  • 1. Upgrade from 4.6 Update 11 or 14.4.3 to 15.06.
  • 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.

Modified Files Upgrade Note

If you have manually modified any system related files or some files are not as yum would expect them to be, the yum update process may not overwrite them. It will instead create 'rpmnew' or 'rpmsave' files and not overwrite the files. The adminsitrator may have previously modified the files knowingly or as part of a patch supplied by TAC.

To check your upgrade.log and search for *.rpmnew *.rpmsave on your system check the upgrade log:

You will be responsible for merging any changes from the old file to the new or contacting Technical Support if you require assistance.

 

Support Tips and Contact Information

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

 

Issues Sorted by Issue Number

 JIRA nameRN ContentEnhancement/Fix/Known IssueKey words
SIPX-389Cannot access HTML reportsFixed an issue that cropped up in 15.10 that caused HTML reports in Call Detail Records > Reports to not work.

PDF, CSV, and XLS files were accessed without problems.

HTTP ERROR 500

Problem accessing /sipxconfig/reportsService.svc. Reason:

Server Error
FixConfig
SIPX-401DID in FAX, Hunt Groups Voicemail, etc., are not indexedFixed an issue where the DID fields added for huntgroups, voicemail service, fax did, etc. are not indexed or searchable by the system. It acknowledges they are there by not allowing a duplicate.FixConfig
SIPX-404P-Preferred-Identity of Proxy - gui workCreate a jira with a check box in proxy setup to pass p-asserted-identity (default should be to not pass (as it operates now)): GUI change.EnhancementConfig
SIPX-481Add support for Polycom 301, 311, 401, 411, 501, 601Polycom has added some new phones. The phones are technically the same as the 300, 310, 400, 410, 500 and 600 from a configuration standpoint. The phones have upgraded processor and memory.

According to Polycom Support:

NOTICE: UCS 5.4.1.14510 should not be used for VVX 501 and VVX 601 phones. A Bluetooth headset issue has been fixed in 5.4.1.16215 for VVX 501 and 601 phones. For all the other phone models UCS 5.4.1.14510 is the supported GA release.

NOTICE: The issues that required UCS 5.4.2 to be withdrawn from the Polycom Support web site have now been resolved and the new build is now available for download. Polycom recommends that any customers who have already downloaded UCS 5.4.2 should download UCS 5.4.2 Rev D and use that release going forward. If you have any questions, please contact your Polycom Global Support representative.

So, 5.4.1 is the earliest firmware rev for these phones, 5.4.2 will not exist and 5.4.3 is also now available.
EnhancementPolycom
SIPX-482Can't remove a Phone Group from Intercom, Groups field can't be emptyFixed an issue where the Intercom Groups field can't be empty.

Steps to reproduce:
1.Create a phone group
2.Go to Intercom, here by default the Groups field is empty
3.Add the phone group to Intercom->Groups, Apply
4.Remove the phone group from Intercom->Group, Apply

Issue: You are prompted "You must enter a value for Groups.".

So you cannot leave the field empty.

You have to make another phone group , add it to this Groups field, and deleted the other one you want to delete...
FixConfig
SIPX-484Slow Mongo queries due to instrument field not indexed in registration dbThere are bunch of slow queries in mongo logs like

Sun Mar 9 01:03:45.779 [conn33033] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f245d6b5", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4381 keyUpdates:0 numYields: 34 locks(micros) r:40511 nreturned:1 reslen:431 583ms
Sun Mar 9 01:03:45.784 [conn33636] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23ec1d5", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4386 keyUpdates:0 numYields: 34 locks(micros) r:34357 nreturned:2 reslen:848 587ms
Sun Mar 9 01:03:45.785 [conn31556] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23e2026", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4382 keyUpdates:0 numYields: 34 locks(micros) r:39891 nreturned:0 reslen:20 583ms
Sun Mar 9 01:03:45.788 [conn32804] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f246046c", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4380 keyUpdates:0 numYields: 34 locks(micros) r:41638 nreturned:3 reslen:1262 590ms
Sun Mar 9 01:03:45.794 [conn32517] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2ae5678", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4378 keyUpdates:0 numYields: 34 locks(micros) r:38242 nreturned:2 reslen:844 593ms
Sun Mar 9 01:03:45.800 [conn32940] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23e849c", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4377 keyUpdates:0 numYields: 34 locks(micros) r:31570 nreturned:7 reslen:2918 612ms
Sun Mar 9 01:03:45.826 [conn33283] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23a25f1", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4375 keyUpdates:0 numYields: 34 locks(micros) r:40170 nreturned:2 reslen:846 606ms
Sun Mar 9 01:03:45.828 [conn33285] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2ae5676", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4376 keyUpdates:0 numYields: 34 locks(micros) r:51343 nreturned:1 reslen:434 609ms
Sun Mar 9 01:03:45.833 [conn33281] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2ab6e3c", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4375 keyUpdates:0 numYields: 34 locks(micros) r:51153 nreturned:2 reslen:844 620ms
Sun Mar 9 01:03:45.867 [conn33301] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23bc053", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4375 keyUpdates:0 numYields: 34 locks(micros) r:44507 nreturned:7 reslen:2904 116ms
Sun Mar 9 01:03:45.868 [conn33300] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2b217a9", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4375 keyUpdates:0 numYields: 34 locks(micros) r:43480 nreturned:2 reslen:844 125ms
Sun Mar 9 01:03:45.901 [conn33012] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2ae75b0", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:8744 keyUpdates:0 numYields: 68 locks(micros) r:71578 nreturned:1 reslen:432 133ms
Sun Mar 9 01:03:45.903 [conn33317] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2b217a9", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:8744 keyUpdates:0 numYields: 68 locks(micros) r:67004 nreturned:2 reslen:844 125ms
Sun Mar 9 01:03:45.920 [conn33315] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2f60fcf", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:8745 keyUpdates:0 numYields: 68 locks(micros) r:71890 nreturned:3 reslen:1262 138ms

sipxecs:PRIMARY> db.system.indexes.find()
{ "v" : 1, "key" : { "_id" : 1 }, "ns" : "node.registrar", "name" : "_id_" }
{ "v" : 1, "key" : { "identity" : 1 }, "ns" : "node.registrar", "name" : "identity_1" }
{ "v" : 1, "key" : { "expirationTime" : 1 }, "ns" : "node.registrar", "name" : "expirationTime_1" }
{ "v" : 1, "key" : { "_id" : 1 }, "ns" : "node.subscription", "name" : "_id_" }
{ "v" : 1, "key" : { "expires" : 1 }, "ns" : "node.subscription", "name" : "expires_1" }
{ "v" : 1, "key" : { "key" : 1 }, "ns" : "node.subscription", "name" : "key_1" }
{ "v" : 1, "key" : { "toUri" : 1 }, "ns" : "node.subscription", "name" : "toUri_1" }
{ "v" : 1, "key" : { "shardId" : 1 }, "ns" : "node.subscription", "name" : "shardId_1" }

My call would be to use sparse indexes as there could be null instruments
http://docs.mongodb.org/manual/core/index-sparse/
FixConfig
SIPX-485Move some Polycom Configuration Items to AdvancedEnhancement to move some Polycom settings that cause problems for the system to the Advanced tab.

In all Polycom Phones & Phone Groups:

SIP Tab:

This entire section -> Server Feature Control

Server Based Call Forwarding (Default: unchecked)
Enable or disable server-based call forwarding.
Server Based Call Forwarding Local Processing (Default: checked)
Enable or disable local call forwarding behavior when server-based call forwarding is enabled.
Server Based Do Not Disturb (Default: unchecked)
Enable or disable server-based DND.
Server Based DNo Not Disturb Local Processing (Default: checked)
Enable or disable local DND behavior when server-based enabled.

In the
Device -> Phone -> Line -> Call Handling page move:

Missed Calls (Default: unchecked)
If set to 0, all missed-call events will increment the counter If set to 1, only missed-call events sent by the server will increment the counter.

On all items add a message: "Warning: Changing these values can cause server instability."
EnhancementConfig
SIPX-493Configuration Generation Error after upgrade from 16.02 to 16.04Fixed an issue that caused a Configuration Generation Error after the upgrade from 16.02 to 16.04.

Configuration generation 5/21/16 11:38 AM 5/21/16 11:38 AM Failed Internal Error null

Service not running: Voicemail/AutoAttendant/IVR/MoH (sipxivr)
FixConfig
SIPX-494Yealink ring typesEnhancement to add new Ring types according to Yealink configuration parameters in V8.

Examples:
account.1.ringtone.ring_type = Ring3.wav

It means configuring Ring3.wav for account1.

account.1.ringtone.ring_type = Common
It means account1 will use the ring tone selected for the IP phone configured by the parameter "phone_setting.ring_type".
EnhancementYealink
SIPX-496Allow MP3 bitrate setting in IVR UIAn enhancement to allow the adjustment of the MP3 recording rates. The MP3 bitrate defaults chosen by mod_shout work out to 16 kbps 8000 Hz recordings and 32 kbps for 16000 Hz recordings. These can cause significant warble/distortion/tinniness. Suitable defaults to be double each of these values, or 32 kbps @ 8000 or 64 kbps @ 16000.

Recording at 8Khz however bumps into an issue in Freeswitch that can cause FS to fail.

Variable recording settings that are safe are now located in System -> Media Services -> Settings.
EnhancementMedia Services
SIPX-501With a valid/signed certificate, connecting over HTTPS will prompt you to accept an invalid cert localhost.localdomainFixed an issue where with a valid signed certificate, connecting over HTTPS will prompt the user to accept an invalid certificate for localhost.localdomain

Steps to reproduce:
1.Created a new VM to test UC-3592 - set it up with fqdn "pr.ezuce.com"
2.Imported a valid certificate(the one provided for *ezuce.com) by going to :
System->Certificates->Web Certificate->Certificate File:"STAR_ezuce_com.crt",Key File :"server.key",Certificate Chain File:"STAR_ezuce_com.ca-bundle"
3.Verified certificate was correctly applied by logging into Admin Portal again

Issue: tried in multiple ways to make it load the valid certificate but it did not.

Server kept sending invalid/old localhost.localdomain certificate.

Server send profiles,reboot, trying different brwsers etc did not work.
FixConfig
SIPX-504Audiocodes template missing CallerIdFixed an issue where the board.ini files generated by sipX for version 6.0 of Audiocodes FXS devices does not include the caller-id name fields. These should be picked up by the line settings for the user name. These could be set manually in an ATAs web UI but they are lost whenever upload the ini file.

Here is an example of what the device needs.
;
; *** TABLE CallerDisplayInfo ***
;
;

[ CallerDisplayInfo ]
FORMAT CallerDisplayInfo_Index = CallerDisplayInfo_DisplayString, CallerDisplayInfo_IsCidRestricted;
CallerDisplayInfo 0 = "Irradiation Svc MRB", 0;
CallerDisplayInfo 1 = "AZ ELEV", 0;

[ \CallerDisplayInfo ]
FixAudioCodes
SIPX-507Callqueue doesnt show queue's name as calleridFix an issue with a package that was missing from the install: freeswitch-lua.

This file was missing from sipxcom RPM spec file https://github.com/sipXcom/sipxecs/blob/release-16.04/sipXcom/sipxcom.spec.in
FixConfig
SIPX-511Certificate issue with openfire/IM after fresh installResolved an issue where a freshly installed server was unable to login into Unite Web with IM.
This was a localised issue in openfire and probably introduced through jira SIPX-3.
FixUnite Web / Unite Lite
SIPX-512Live Attendant -> "Extension will ring for" option initialized with 0Fixed an illogical default value when a new live attendant was created.The "Extension will ring for" option was set to "0" seconds by default.
This means the extension setup as a live attendant extension would not ring at all until that value was changed to a proper time.

Set to default value of 20 seconds.
FixConfig
UC-1726Increase max value for voice mail importsFixed an issue that would now allow larger voicemail backups to be restored. Previously this value is set to maxSize=1073741824.

Steps to reproduce:
1. Attempt to upload a voicemail backup that is larger than 1073741824 bytes.

Error seen:
"Unable to decode multipart encoded request: the request was rejected because its size (1436454790) exceeds the configured maximum (1073741824)"
FixConfig Backup/Restore
UC-1743Investigate DST updates in schedules, voicemails, cdrs, etc.Fixed an issue that caused Auto Attendant and IVR schedules to not be updated with DST change.

Workaround is to send server profiles.
FixConfig
UC-3503Allow speedials for User IDs consisting of numbers/lettersAn administrator would like to allow letters in the user ID along with numbers.

Currently it isn't possible to change the speed dial lists via the new user web portal when a user without a number is listed; for instance, when the user ID consists of letters instead of numbers. This is used also for ACD, when the user registers in order to make/receive calls. In this case the "save" and "save and update" fields are not selectable, so that a user cannot make any changes. As soon as the user with no user ID is removed, changes can be made and it works just as desired.

There are customers that have letters instead of numbers for their user ID, so this feature would be blocked for them.
EnhancementConfig
UC-3587Cannot upload config backups larger than 1 GB (or 1073741824) multipart encoded errorFixed an issue trying to upload and restore large backup files.

Tried to upload a customer config backup (to recreate a setup) which has a size of 1.5 GB.
Upload fails with error :

"2015-03-04T16:28:31.259000Z":63:JAVA:WARNING:one.ctradu-legacy.ezuce.ro:P2-18:0 0000000:sipXconfig-web:"/sipxconfig/backup/RestorePage,$backup$RestoreUpload.upl oad.sdirect: "org.apache.hivemind.ApplicationRuntimeException: Unable to decode multipart encoded request: the request was rejected because its size (1647324186) exceeds the configured maximum (1073741824)
FixConfig Backup/Restore
UC-3592Problems with SSL certificate if Reachme is not running on primaryFixed an issue where if Reachme is enabled on a node other than the primary then "cowboy" collection will read just root web certificate and will ignore certificate chain (intermediary certificate).

As an additional (and important) note: To run Reachme on other node you need to use wildcard certificate
FixReachme
UC-3655Conference call does not end when an agent makes outbound call, invites "number" into conference, and then agent ends conf by clicking X in the dashboardFixed an issue where conference calls do not end properly when an agent makes an outbound call, invites a "number" into conference, and the agent then tries to end the conference by clicking on the X in the dashboard.

Steps to reproduce:
1.Agent makes outbound call
2.Customer answers
3.Call flow continues with the Agent creating a conf call by choosing Transfer/Conf - "Number" and inviting a 3rd participant
4.3rd participant joins and all can hear each other
5.Agent drops the call by clicking "X" in the dashboard

Issue : conference call does not end.

If the initiator of the call ,ends the call, then conf call should end.

In this case Agent is the one who initiated the calls, but when he drops, conf call continues between the customer and the invited "number"

This issue only happens if the agent ends the call by clicking X. DOes not happen if he ends call from deskphone.
FixReachme
UC-3825Reach Outbound - Update Agent Manager Group SectionEnhancement to update the in session counts in the Agent manager group section. Previously the agent that is on an outbound is still counted as an agent that is in released rather than in session.EnhancementReachme
UC-3826Reach Outbound - Update Agent ManagerEnhancement to update the agent group section of the agent manager widget to show in session count for inbound and for outbound.

Column for In Session make
In Session ... then under it
in/Out

Then show counts of agents in session for inbound and outbound separately. So if there are 20 agents in session on inbounds and 3 in session for outbounds show 20/3

In addition, an agent that is in the process of making an outbound call and is in the ringing state during the outbound call processing should be counted as such under the ringing count in the agent manager.
EnhancementReachme
UC-3827Update Icon for "in session" identifying inbound vs. outbound, fix view of long customer name, fix agent manager unable to see outbound call status after page refreshEnhance the Agent Manager Agent Section to show that an Agent is on an outbound call and not just in session.

This will be specified by a different icon representing an outbound call.

Whatever icon we use there should also then be used in the session manager for the agent when an outbound call has been made and is in session.
EnhancementReachme
UC-3841Multiple calls getClient to backend causes errors in browser consoleFixed an issue with multiple calls of getClient to backend was causing errors in browser console.FixReachme
UC-3870CDR csv export repeats page headers within rowsFixed an issue with CSV export in Call Detail Records that interspersed column header information with data.

Steps to reproduce:
1) Diagnostics -> Call Detail Records -> Reports -> "Call History" -> <Apply>
2) Download CSV
3) Open CSV

You will see that interspersed with your useful data is repeated header/footer/pagination records, making it very difficult to work with the exported data:

This also is done for Excel, but in that case it might be considered intentional in order to make a pretty printout. But then CSV is relied upon as the only pure data dump for post processing, but this header/footer data ruins that.
FixConfig
UC-3880Move Network Packet Capture Service to Diagnostic TabLogically the Network Packet Capture Service should go under the Diagnostics tab. It should be moved for continuity.FixConfig
UC-3887Agent caller id shown twice in session manager widgetFixed an issue where the Agent's CallerID was displayed twice in the Agent Session Manager.

Steps to reproduce:
Agent : Mary Jane with extension 302
Client : Ezuce ,to reach this client the number is 309
1.Agent logs in and makes an outbound call to client Ezuce by dialing 309.

Issue : in the session manager widget ,next to the customer avatar , you can see : Ezuce 302 302 309

So we have client name , agent caller Id , agent caller Id again and then the dialed number to reach the client.
FixReachme
UC-3903Improvement for default line labels in Polycom 5.xMake the default line labels for Polycom Phones with firmware 5.x and higher display extension numbers vs. names.

Features in Polycom 5.x firmware are starting to make it more desirable for production (for example, the ability to set default transfer type). The big problem moving from 4.x firmware is that the phones change to display the name of the user instead of the extension. Most users prefer to continue seeing the extension number as they do now.

While it can be manually adjusted under the line options of each phone, having 1,000+ phones to fix would be a very manual process.
EnhancementPolycom
UC-3964Queue Group Traffic reports should take their data from the Queue Group Traffic with SLAThe Queue Group Traffic reports need to take their data from the Queue Group Traffic with SLA.FixReachme Reports
UC-3968Expose transport setting for sipXbridge in configEnhancement to expose a way through which sipXbridge can be set to use TCP or UDP transport.

The core functionality which allowed TCP or UDP usage was already implemented however it was not configurable from portal.
EnhancementsipXbridge
UC-3976Validate data entries when an agent makes a transfer / conference to a numberAn agent is allowed to transfer a call to an external number or to make a conference with a third party. When selecting 'Number' from the 'Transfer / Conference' drop down list, he is asked to input a number.

Data entered in that text field was not validated and the agent can insert bad characters, like %.

We added an enhancement to validate the input strip any special, but allowed characters.

Note that there is a small difference in the way the validation should work for a transfer versus a conference. For a conference, there is an origination command being issued in the backed, while for a transfer there is a uuid_transfer FS call.
EnhancementReachme
UC-3989Make Reachme statistics generation configurableAdded a configuration parameter to set an interval for statistics being generated. At present statistics are generated in real time and this can create a lot of database traffic.

By making this happen at specified intervals we can optimize and minimize database queries.
EnhancementReachme
UC-3990Reachme call recording ends when a call conferenced and then handed off to another AgentFixed an issue where a call recording would stop at the point where Agent 1 drops out of a call he or she conferenced in Agent 2 to handle.

Steps to recreate:
1. Call into a Reachme line that has a client associated with it that has call recording turned on.
2. Answer the call with agent1
3. Agent1 does a conference to queue, selects the queue and hits the conference button.
4. Agent1 awaits another agent to answer the call out of the queue (agent2)
5. Agent2 answers the conference request out of the queue.
6. Agent1 now drops out of the call via hitting the X button. This leaves the caller and agent2 talking.

The issue is that in this call flow the call recording file stops at the point that agent1 hits the X button to drop out of the call.

This also occurs if agent1 uses the same conference hand off function to another agent.

This does NOT occur if agent1 blind transfers the caller to another queue or agent via using the transfer button rather than the conference button.
FixReachme
UC-3994Disable "Continue" button during Reachme advanced login when URI is enteredDuring the advanced login process for a reach agent, the agent sees 2 buttons (Continue and Use Advanced Login). At first, the Continue button is enabled and the Advanced login button is disabled. When the user puts in valid characters in the sip uri field the Advanced Login button is enabled.

However, the continue button is also still enabled and can be pushed. If an agent does this, they are logged in via their normal sip phone. This can be confusing to users who entered a sip uri (phone number) and are expecting to receive calls there.

This enhancement request is to disable the continue button once there is a valid entry in the sip uri field.

In short, have only one of the 2 buttons enabled at any given time. The Continue button is enabled before valid characters are in the sip uri and the advance login button is enabled once there are valid characters in the sip uri field but BOTH buttons are never enabled at the same time.
EnhancementReachme
UC-3998Allow a Reachme Agent to change Release Reason while in the release modeCurrently, if a Reach agent is in the release mode but they want to select a different release reason, the only way that they can do that is to go available (idle) and then go back to the release mode with a different reason code from the drop down.

This enhancement request is to allow the agent to select a new release reason from the list while they are already in the release mode.

We must ensure that we keep event data associated with reporting of how much time was spent in each release reason when implementing this enhancement.
EnhancementReachme
UC-4002Proxy should add "transport=tcp" into Record-Route of responses (180, 200) in case TCP usage- SIP sidePer RFC https://tools.ietf.org/html/rfc5658 , proxy should put "transport=tcp" into Record-Route of responses (180, 200) in case TCP is required for this call leg. By default (when no transport specified) UDP should be used. So in this case Polycom behavior is valid. This is proxy bug.

Grandstream is not compliant with RFC strictly, it just ignores absence of transport.

This Jira was created to make sure TCP protocol is kept between Proxy and internal user, when set, and not flip-flop to UDP.

It only involves SIP Core side work (no config).
FixProxy
UC-4005Add Reachme CDR report that contains the Wrap up, Node, Agent Node, Original Skills and Final Skills columnsCreate a new version of the CDR report that includes the following fields since those fields were available in previous releases.

Wrap up, Node, Agent Node, Original Skills and Final Skills columns
New FeatureReachme Reports
UC-4013Agent cannot end the call from dashboard during outbound precall - missing X buttonFixed an issue in recent versions of Reach where the Agent could not end an outbound call during the outbound precall (the X button was missing).

Steps to reproduce:
1. Agent selects client he wishes to call outbound to,
2. Agent answers the incoming reach call, and he then decides to no longer enter the caller number but rather wants to end the call.

The "x" is missing in the newer versions of Reach whereas there was an X available in 15.10 to end the pre-call.
FixReachme
UC-4014Transfer/conference from dashboard not working during a held outbound callFixed an issue where transfer or conference from Agent dashboard was not working during a held outbound call.

Steps to reproduce:
1. Make otubound call and place the call on hold.
2. Transfer/conference selector box is available when you hold the outbound call from dashboard.
3. Next, when you choose the option to transf/conf, you get to option for "Number"; try to complete it, and nothing happens.

In previous release the widget looked rather different, and you would not be able to use the transf/conf section while on hold

It's valid to place a call on hold and then conference in another party. For a call that is originally connected via outbound should look just like a call that was originally connected via inbound. Thus, hold then trans/conf should indeed work and it should work in the same way that a normal inbound call can be placed on hold and then trans/conf.
FixReachme
UC-4015Customer is left alone in call after an agent makes outbound call,invites "number" into conference,"number" drops and then agent ends conf by clicking X in the dashboardFixed an issue where if a caller is left alone in call after an agent makes outbound call, invites "number" into conference, "number" drops and then agent ends conf by clicking X in the dashboard the caller is not dropped but starts hearing queue MoH.

Steps to reproduce:
1. Agent makes outbound call
2. Callee answers
3. Call flow continues with the Agent creating a conf call by choosing Transfer/Conf - "Number" and inviting a 3rd participant
4. 3rd participant joins and all can hear each other
5. 3rd participant drops while Agent and callee are still on conf call ok
6. Agent drops the call by clicking "X" in the dashboard

Issue: Callee is not dropped from call, and starts hearing queue MoH

In release 15.10 in this last step, the callee would be dropped from call.
FixReachme
UC-4016Bria devices are exhausting Unite Mobile LicensesFixed an issue with Unite Mobile licensing which was causing the licensing to detect Bria as Unite Mobile.FixUnite Mobile
UC-4019Call park name extension creates a duplicate entry in mongo dbFixed an issue where if an administrator added a new call park with name=1200 and extension=1200 it will create 2 identical entries in mongodb. This in turn will answer with a 302 Redirect having the same contact twice.
This confused SSS and also FS as follows:

sipxecs:PRIMARY> db.entity.find({"ident":"1200@ezuce.ro"}).pretty()
{
"_id" : "ParkOrbit2",
"ident" : "1200@ezuce.ro",
"locations" : [ ],
"ent" : "parkorbit",
"als" : [
{
"id" : "1200",
"cnt" : "sip:1200@10.0.0.23:15060",
"rln" : "orbit"
},
{
"id" : "1200",
"cnt" : "sip:1200@10.0.0.23:15060",
"rln" : "orbit"
},
{
"id" : "*41200",
"cnt" : "sip:*41200@10.0.0.23:15060",
"rln" : "unpark"
},
{
"id" : "*781200",
"cnt" : "sip:*781200@10.0.0.23:15060",
"rln" : "unpark"
}
]
}
FixPark
UC-4021Reach: Calls Stuck in Queue, Not Being Offered to AgentsWhen a reach vqueue is abnormally terminated, all it's registered calls are not offered to an agent anymore, they are essentially lost.

In most cases the reason that a vqueue gets terminated abnormally is a timeout to a disconnected phone.

The QUEUE_TIMEOUT is 1 minute, so if the connection to a call in queue drops, after 1 minute all the calls registered on that queue will not be offered anymore.

With this JIRA we created a fail-safe mechanism that moves all the calls in an abnormally terminated vqueue to another vqueue.
FixReachme
UC-4025SOAP api bug - duplicate entriesFixed an issue with SOAP API to add a line to a phone. When adding a line to a phone via SOAP API the line gets duplicated.FixConfig
UC-4030If a user puts call queue extension in speed dial and subscribes to presence SSS has problemsThis enhancement will block users or administrators from configuring speed dials and enable presence for extensions that are Call Queue extensions. Call Queue extensions are not monitorable.

Steps to reproduce:
1. PSTN---> call DID---> call queue 120
2. 120 is monitored on both phones that are agents
3. Call answered on 201 (agent 2)
4. Presence for 201 and 120 was shown on 200 (agent 1) speed dial buttons
5. Call is parked on 1100 (presence was not seen for this extension)
6. presence for 120 is stuck untll the call is picked up with *781100 from call park and hung up
FixConfig
UC-4034Improve usability of Reach OutboundCurrently, when the agent begins the process of an outbound call, they select a client from the Outbound Call drop down. The system then rings their phone. Once they answer the call they get a text box to enter the phone number that they would like to call.

Part 1 of this enhancement:
When the agent answers the call, place the cursor in the phone number text box automatically so that they don't have to click into the text box to begin entering the phone number that they want to call.

Part 2 of this enhancement:
If the agent hits enter/return, the outbound call should be launched as if they clicked on the call button. This return to call and the click to call button should only be allowed if the phone number entered is valid based upon current checks for that content. In other words, if the agent enters a character like 'a', then hits return, it would not launch the call since the content of the outbound number text box is invalid. The same should be true of clicking the call button.
EnhancementReachme
UC-4046Add new Daily and Weekly ReportsA weekly report on:

- Total number of inbound vs outbound calls per agent
- Total number of minutes/hours
- Total raw number of calls (ex. 500 calls from 4/24 – 4/29)
- Total transferred
- Total completed
- The option to filter out Inbound & Outbound

Automatically total up each column at the bottom.


A daily report on:

- Total number of minutes/hours in the given date/time range
- Total raw number of calls (ex. 500 calls from 9am – 12pm on 4/28/16)
- Total transferred
- Total completed
- Average hold time
- The option to filter out by Inbound & Outbound

Automatically total up each column at the bottom.

(They don’t need to see every leg of every calls. The idea is, they’re sales reps and they’re supposed to make x amount of calls per day so around lunch they usually pull their stats to see how much they need to ramp up in the afternoon. )
New FeatureReachme Reports
UC-4049New Report Agent Activity by GroupA new report called "Agent Activity by Group"

Report definition is as follows:

Inputs: Date/Time Start, Date/Time End, Multiselect Drop down for selection of one or more agent groups
Default would be all agent groups selected in the multiselect drop down
Default Date/Time Start = Date of 7 days ago; time of midnight (start of day)
Default Date/Time End = The current day and time of end of the day.
The date/time defaults are intended to provide a 1 week default including today's activity.

Output:
Agent, Total Inbound calls, Total Inbound Minutes, Total Inbound Completed, Total Inbound Transferred, Total Outbound calls, Total Outbound Minutes, Total Combined In/Out Calls, Total In/Out Minutes

Additional Output (totals row at bottom of report)
Totals Row at bottom. This row will be a total of each of the other columns of the report. Obviously we can't total the Agents column but all other columns should be totaled up.

It would be preferred that the report headings are grouped In sections of Inbound, Outbound and Total, then have each column as a subheading (e.g. the column of Total Inbound Calls would just say Total Calls but be under a report header of Inbound). However, care must be taken to ensure that when exporting the report to CSV, these headers don't mess up a standard CSV import to Excel or some other spreadsheet.

Measurement definition clarifications:
Total Inbound Completed is defined as an inbound call that an agent answered that was never transferred to another user/queue/number.

Total Inbound Transferred is defined as an inbound call that an agent answered that was ultimately transferred somewhere else.
New FeatureReachme Reports
UC-4050New Report Agent Activity IndividualA new report called "Agent Activity Individual"

Report definition is as follows:

Inputs: Date/Time Start, Date/Time End, Agent ID drop down or textual input
If a drop down with all reach agent ID's in the system can be populated that would be best. That drop down select would be a single select drop down meaning that you can only select a single user. It would be preferred that the user could start typing into the selection portion of the drop down to "find" a specific user and/or just manually enter the ID of choice.

Default would be no agent ID selected
Default Date/Time Start = beginning of the current day
Default Date/Time End = end of the current day
The date/time defaults are intended to provide activity for today thus far

Output:
Agent, Total Inbound calls, Total Inbound Minutes, Total Inbound Completed, Total Inbound Transferred, Total Outbound calls, Average Hold Time, Total Outbound Minutes, Total Combined In/Out Calls, Total In/Out Minutes

Note that this is the same output as the agent group activity report defined in uc-4049 with the addition of the "average hold time" field.

It would be preferred that the report headings are grouped In sections of Inbound, Outbound and Total, then have each column as a subheading (e.g. the column of Total Inbound Calls would just say Total Calls but be under a report header of Inbound). The average hold time field would be grouped with the Inbound measurements. Care must be taken to ensure that when exporting the report to CSV, these headers don't mess up a standard CSV import to Excel or some other spreadsheet.

Measurement definition clarifications:
Average Hold Time is relevant to inbound calls and is defined as the average amount of time spent in queue and in ringing for all calls that the selected agent answered.

Total Inbound Completed is defined as an inbound call that an agent answered that was never transferred to another user/queue/number.

Total Inbound Transferred is defined as an inbound call that an agent answered that was ultimately transferred somewhere else.
New FeatureReachme Reports
UC-4054Reach CDR report has incorrect "Offered To Reach" timestampThe Reachme Call Detail Report had an incorrect "Offered To Reach" timestamp.

Steps to reproduce:
Place calls into reach and keeping manual timing of calls while doing so. Run the CDR report afterwards and check the offered to reach timestamp.

The thing that seemed to trigger this issue was having a call in queue for a long time before answering it with an agent. Example, place a call that is allowed to queue for over 2 minutes and another that is allowed to queue for over 4 minutes. Both had incorrect "offered to reach" times.

This was negatively effecting measurements on reports for average hold or in queue times.
FixReachme Reports
UC-4055Persistent tcp keepalive reductionImplemented Mongo recommendations regarding keepalives:

https://docs.mongodb.org/v2.6/faq/diagnostics/#does-tcp-keepalive-time-affect-sharded-clusters-and-replica-sets

"A common keep alive period is 7200 seconds (2 hours); however, different distributions and OS X may have different settings. For MongoDB, you will have better experiences with shorter keepalive periods, on the order of 300 seconds (five minutes)."

In order to make that persistent you will need to edit /etc/sysctl.conf and append net.ipv4.tcp_keepalive_time = 300
After that you will need to run " sysctl -p " to have the new values reloaded. You can check this new value with cat /proc/sys/net/ipv4/tcp_keepalive_time
FixConfig
UC-4060Enhance the Reach productivity reports to show values or percentagesFor the following 4 reports that exist in Reach today:
Agent Productivity
Agent Productivity Compact
Agent Group Productivity
Agent Group Productivity Compact

Do the following:
Add an radial dial input control that allows the user to select either % or raw numbers. Only one of the two may be selected. The Input should be called "Ouput Data In"

In short, the user would be identifying whether the output of the report should be provided in percentages or numbers.

The output would then follow the selection of the radial dial when the report is executed.
EnhancementReachme Reports
UC-4066Supervisor sees agent in Idle mode but agent is in Released mode after outbound callThe agent shows idle in the agent manager widget while showing released in the agent's UI.

To reproduce:
have an agent in the idle state
select a client to begin the process of making an outbound call
the agent's phone begins ringing
while the phone is still ringing, hit the release button on the agent UI
answer the phone
hang up the phone without putting in a phone number and making an outbound call

UI now shows release while the Agent Manager widget shows the agent as being idle.

If you place a call into the queue now the agent will not be offered the call even though they show as being idle in the Agent Manager. If you go idle in the agent portal now, the call will be delivered (gets back in sync between the Agent Manager and agent UI).
FixReachme
UC-4069Change Queue Traffic Detail Reach report to show periods with no activityThe current traffic detail report will not show a row of data for any period of time that had not activity. Example, if the interval selected to run the report for is every 60 minutes and the date/time range was for one full day, there is not 24 rows returned (some being 0 call activity). Instead, only the hour intervals that had call activity are shown.

This request is to show all intervals regardless of whether or not they had activity. For such a row with no call activity, simply show 0 in all columns of the row.

In addition, mirror the Queue Traffic with SLA report columns in the output of this new traffic detail report.
EnhancementReachme Reports
UC-4074Add Reach Client Detail ReportAdd a report that is very similar to the current Queue Traffic Detail Report.

This new report will be a client based report and that is the major difference in this report in comparison to the Queue Traffic Detail Report.

Additional columns for Outbound activity for the client are also added.

The input parameters of queue group and queue should be replaced with a single multiple select client drop down (with all/none/inverse options).

When the user selects one or more clients from the drop down, a from date/time, To date/time and an interval, the report will execute and output the results as identified in the attached screen shot.
New FeatureReachme Reports
UC-4075Add Client Traffic Overview Reach ReportAdd a report very similar to the Queue Traffic Overview Report.

This new report will be a client based report and that is the major difference in this report in comparison to the Queue Traffic Overview Report.

The input parameters will be the same (From Date/Time and To Date/Time)

Once the user selects a date time range and executes the report, the output will be as shown in the attached screen shot.
New FeatureReachme Reports
UC-4078Need to remove/hide/add a danger tag message for Security Classification parameter

If an administrator enables Security Classification under Devices--> Phones-->{Phone}---> SIP, it will cause 1000+ Sip messages in less than 1 minute
Subscribing for event:as-feature-event which will eventually consume server resources and bring the server down.

This JIRA is to move this setting to Advanced page and put a warning on this setting.

For these Subscribes server responds with:
SIP/2.0 482 Loop Detected
Via: SIP/2.0/UDP 172.31.1.8;branch=z9hG4bK-XX-0f8b58jLXg1IDnWhjj9Eje2rJg~06cDismVVIpdr`rHxNEPbQ
Via: SIP/2.0/TCP 192.168.1.164;branch=z9hG4bKe4606e0e5C28F81;received=5.2.152.210;rport=30065
From: \"Mihai - backup Costache\" <sip:2049@ezuce.com>;tag=679010C6-DE4E4609
To: <sip:2049@ezuce.com>;tag=B5A9A0F1-4F43A0E6
Cseq: 1 SUBSCRIBE
Call-Id: 53bcdfd6-2ecb3079-48caae1e@192.168.1.164
Record-Route: <sip:107.23.34.40:5060;lr;transport=tcp;sipXecs-rs=%2Aauth%7E.%2Afrom%7ENjc5MDEwQzYtREU0RTQ2MDk%60.900_ntap%2ACeT%7ENS4yLjE1Mi4yMTA6MzAwNjU7dHJhbnNwb3J0

PXRjcA%60%60.900_ntap%2ACrT%7ENS4yLjE1Mi4yMTA6MzAwNjU7dHJhbnNwb3J0PXRjcA%60%60%2102eddc0b252d06f61fccb2de07fdf2d5>

Event: as-feature-event
User-Agent: PolycomVVX-VVX_400-UA/5.2.5.0639
Accept-Language: en
Content-Length: 0
Date: Mon, 16 May 2016 07:45:04 GMT

EnhancementConfig
UC-4079Fix ASA calculation on All Reach ReportsASA is not calculated correctly on any of the Reach reports.

Correct it to be (Total time for all calls answered) / # of calls answered.
FixReachme Reports
UC-4082Deploy additional Custom Reach Report as a standard reportEnsure that other new Custom reports are part of the deployed report package.New FeatureReachme Reports
UC-4083Deploy new custom reach Agent Activity report as a standard reportEnsure that the new agent activity custom reports are delivered as a standard report.New FeatureReachme Reports
UC-4085Decrease number of DB queries by openuc-customcallerid pluginThe openuc-customcallerid makes mongo query for every single packet of call.FixCustom CallerID
UC-4086After server Send Profiles, SSS stops working properlyAfter a send server profiles SSS stops working properly.

Steps to reproduce:
1. send server profiles - wait for Job Status to show complete.
2. Check for BLF on outbound or inbound PSTN call or internal calls - broken.
3. restart either phones or restart SSS
4. BLF now works on outbound or inbound PSTN call and internal calls

After server profiles re sent, at the same time in sipxsss.log
"2016-05-19T06:23:45.901811Z":23409:SIP:INFO:openuc.ezuce.com::7fbd3a78a700:sipxsss:"SetRefresherBase::mongoOpLogCallBackInsert::0x7ffd41a55250 "

Then within the next few seconds RLS lists are actively updated/removed/inserted.
FixSSS
UC-4088Create a reach reports "redeployment package"Create a method of uninstalling all "old standard reports" and deploy all most recent versions of standard reports.

This cannot remove any custom reports that might already exist in the server.
EnhancementReachme Reports
UC-4090Reach agent status in Agent Manager widget out of sync for outbound callsIn supervisor Agent Manager widget the agent's state shows that he's still on call although the call is terminated.

Steps to reproduce :
1. Agent selects a client and starts a pre-ring call for outbound call.
2. The agents's phone begins ringing.
3. Answers the phone and enters an external number to start an outbound call.
4. Call with external number is answered and then ended.

Workaround : refresh the supervisor web page.
FixReachme
UC-4093Add Agent Group Activity Reach ReportThis will be a custom report "Agent Group Activity" report but with rolled up stats based on agent group instead of agent by agent data.

Inputs:
From Date/Time
To Date/Time

Outputs:
Column Headers of Group, Inbound Activity, Outbound Activity, Total Activity
Columns under Group Header (Agent Group)
Columns under Inbound Activity Header (Total Calls, total time, completed calls, transferred calls, avg. hold time)
Columns under Outbound Activity Header (Total Calls, Total Time)
Columns under Total Activity (Total Calls, Total Time)

Note that this is exactly the same output as the existing report. Same look and feel. Just grouped by agent group.
New FeatureReachme Reports
UC-4096Add "Outbound Overview by Client" Reach reportAdd a reach report that shows an overview of outbound call activity by client.

Inputs:
Start date/time
End date/time
No Customer (checkbox)
Checkbox labeled "Hide Inactive" (default of checked)

If No Customer checkbox is checked, the output will contain a No Customer Entry that looks just like a normal client entry even though "No Customer" is in fact not a client.
For each client built in the system there will be a row in the output.

Outputs:
Client, Started, Sent, Answered, %Complete, Average Talk Time, Total Talk Time
A "totals" row at the bottom showing the totals for the columns (note that %Complete must be a weighted average rather than an average or sum of all of the column data).
The values of the outputs will be as follows:

Started - count of time that the agent selected a client from the drop down box to begin the process or making an outbound call. This is independent of whether or not they answered their phone when it rings.

Sent - how many outbound calls were sent (this would NOT include cases where an agent started the outbound call process but did not ultimately put in a number to call and send the call.

Answered - calls that were sent and answered by the called party.

%Complete - Answered / Attempts

Average Talk Time - Total Talk Time / number of completed

Total Talk Time - Total days/hours/minutes/seconds of all call talk time for all answered calls

If "hide inactive" is checked, clients with no outbound call activity for the start/end date/time are not shown. If "hide inactive" is not checked, clients with no outbound call activity for the start/end date/time will be shown with 0s for counts and NA for measurements such as %Complete.
New FeatureReachme Reports
UC-4097Add Reach Line Traffic Detail ReportAdd a report that is very similar to the current Queue Traffic Detail Report.

This new report will be a Line based report and that is the major difference in this report in comparison to the Queue Traffic Detail Report.

The input parameters of queue group and queue should be replaced with a single multiple select Line drop down (with all/none/inverse options).

When the user selects one or more lines from the drop down, a from date/time, To date/time and an interval, the report will execute and output the same information as is in the queue traffic details report except that the report title information at the top will show what lines were selected rather than what queue group and queue were selected and that the header row should read Line Activity instead of queue activity.
Screen shot of queue traffic detail report is attached for reference.
New FeatureReachme Reports
UC-4098Add "Line Traffic Overview" Reach ReportAdd a report very similar to the Queue Traffic Overview Report.

This new report will be a Line based report and that is the major difference in this report in comparison to the Queue Traffic Overview Report.

The input parameters will be the same (From Date/Time and To Date/Time)

Once the user selects a date time range and executes the report, the output will be as shown in the attached screen shot.
New FeatureReachme Reports
UC-4101Block the ability to do a conference when on holdIn Agent Widget disable the ability to start a conference call when a call is on hold. This is a bit of a workaround to deal with the following workflow not working.

Steps to reproduce:
1.Agent A makes outbound call to customer,and customer answers
2.Agent A places this outbound call on hold from dashboard.
Result : call is on hold,customer can hear Moh
3.Agent A selects Transfer/Conference->Number->Enters "the number of the invited party"->Conference
Result : the invited party is being alerted by the incoming conf call while
Customer is still on hold and hears Moh
4.The invited party answers the call
Issue: Customer and the invited party are hearing MoH and can also hear eachother.
The agent who initiated this call still has the call on hold,as expected, however when he unholds the call from the dashboard,the call is not retrieved.
He must click Hold again and then again unhold the call - after he does this operation , MoH stops and all 3 can hear eachother.

This issue does not appear if at Step 2 , the agent does not hold the call.

UC-4140 will track fixing this workflow.
FixReachme
UC-4103Review/Improve Reach archiving scriptReview and improve the Reachme archiving script /usr/bin/reach-recordings-clean.pyFixReachme
UC-4104Mongo C++ driver fix for tcp connection issueMongo C++ driver is creating large number of tcp connections on secondary database servers.FixProxy
UC-4107Capture Agent Events for Reports UseCapture events with date/time stamps and agent login, agent name and agent group for the following:

login
logout
go release (with release reason)
go idle/available
Answer call
Missed call (e.g. was offered a call but didn't answer it)
End call (with direction or inbound or outbound)
start wrap
end wrap
In outbound setup (triggers when client is selected from drop down)
Ringing outbound (triggers when they launch the call to the outbound #)
On Outbound (triggers when far end outbound # answers)

Each record needs to be written immediately upon entry into one of the states above.
Each record should include at least the following:
Start Date/Time
State being entered
End Date/Time

Since an entry is written immediately upon entry into a new state, when a transition is made from one state to another, the previous state entry must be updated with the End Date/Time stamp and of course the new entry would need to be created for the state being newly entered into. When creating a new entry, the End Date/Time stamp will be initially null. It will later be updated to the date/time that the user enters another sate.

Care should be given to ensuring that that multiple entries with a null end date/time do not exist in the data table (e.g. Reach or DB crash the leaves entries with no end Date/Time).

This data is required to be able to produce an agent session report.

This data can be captured in the events collection and then processed and moved to some other collection like the other data in that collection is done. However, the end result must be that a collection like the call_segment_facts collection is created with the identified data above.
New FeatureReachme Reports
UC-4108Reach: Inefficient method ouc_agents:get_online_agents/0Supervisors are not seeing some agents that are logged into acd and Idle state.

On agent screen they show Idle but when we go to supervisor account that agent doesn't show up. Its like dead session but shows as Idle.
FixReachme
UC-4112Add columns to the Queue/Line/Client Traffic Detail reportsAdd the following columns to all 3 of the traffic detail reports:
Sent to voicemail
Transfer out
Total abandon
SLA

They are the same columns as the traffic overview reports currently have.

This means that a SLA input parameter will need to be added to these traffic detail reports as well. It should be the same as the SLA input on the overview reports.
EnhancementReachme Reports
UC-4113Add inactive queues/lines/clients to Queue/Line/Client Overview Reach ReportsCurrently, if you run the queue traffic overview report for a data/time range that does not have any activity for a specific queue, this queue will not show up on the report at all. This is true for the Line and Client overview reports as well.

This enhancement request is to show all queueus/lines/clients on the output of that report regardless of whether or not they had activity.

However, this should be done based on an input parameter. The new input parameter will be a check box. The checkbox will be checked by default and the label of the checkbox will be "Hide Inactive".

If checked, the report output will have rows for ONLY those lines/clients/queues that have activity. If unchecked the report will show a row for all lines/clients/queues configured in the system even if they do not have activity for the date/time range selected. In this case, the inactive lines will just show 0 for counts and NA for other measurements such as CPT.
EnhancementReachme Reports
UC-4114Deleting Voicemails from link in eMail doesn't notify MWIThere are hyperlinks included in eMails sent as part of the Voicemail to eMail feature. If a user clicks on the Delete hyperlink the Voicemail is deleted but the Message Waiting Indicator service is not updated.

Setup and steps to reproduce:
1. Unified Messaging on the individual user, "E-mail format" set to Full.
2. Voicemail created, open email and use the delete button.
3. This takes you to the GUI log in, login, GUI page is blank, can only close the tab.
4. Voicemail does get deleted, but does not show up in the deleted folder and the MWI light remains blinking.
5. Play and manage voicemails buttons work as expected.

Expected behavior:
Upon delete move voicemail to deleted folder and NOTIFY MWI
FixVoicemail
UC-4115Add Outbound Detail by Client Reach ReportAdd a reach report for detailed outbound call activity. This will be much like the outbound overview report by grouped the the time interval entered by the user.New FeatureReachme Reports
UC-4121Update icons for agent OutboundRelated to UC-3827. Update the outbound icons to allow users to better identify call direction.EnhancementReachme
UC-4126Call Status of Outbound Conference is not Updated.In the Reachme Session Manager Widget, only in session call status is visible for outbound call conference. Add enhancement to also be able to see the call status of an outbound conference.EnhancementReachme
UC-4137Deploy Custom JasperServer extensionsFor the Reachme Standard Report Package we need a custom extension for JasperServer allowing us to use a custom Interval Data Source. This will allow for deployment of such extensions to new releases and also be able to backport them if needed.

Interval Data Source is not a "real" datasource (no data is actually read from DB). It must create successive time intervals defined by timestamps entered to "From" and "To" input controls and value of interval length entered to "Interval" input control. Each interval is then defined by its own start and end timestamps, first interval must start at "From" timestamp, last interval must end at "To" timestamp, even if it will be shorter than requested Interval length value.
EnhancementReachme
UC-4147Read reach recordings from archive pathCurrently Reachme recordings are read only from GridFS, so when the recording is archived, Reachme does not files from archive location. This enhancement allows Reachme to read from Mongo's GridFS as well as the Archive path.EnhancementReachme
UC-4149Add Reachme Report called Agent State HistoryAdd a report called Agent State History.

Report should be placed in the Agent subcategory of reports and should be as follows:

Inputs:
Agent ID (single select list of all agents in the system)
Start Date/time
End Date/time

Output Title to include date/time range and Agent ID input

Text Prior to table formatted Data:

Total Time Logged In
Total Time Logged Out
Total Time In Released
Total Time Available for Calls

Note: these totals will not include time outside of the date/time range input. Example; if the agent logged in prior to 9am but the report is executed for a 9am start time, the total logged in time will not take into account time in logged in state prior to 9am.

Output Columns:
State Entered (Log In, Log Off, Idle, Release)
Reason (if state entered is release, this will show the release reason)
State Begin Date/Time of State change
State End Date/Time that this state was exited (into one of the other reported states of login, logoff, idle or released)
Duration (Total Time spent in this state before next State Change; State End Date Time - State Begin Date/Time)


Notes:
State changes other than login, logout, release and idle will not be shown. Example, ringing, in session, prering, etc are states that will not be shown on this report.
Duration will show in the format of w days, x hours, y minutes, z seconds
Duration will be calculated via start datetime or enddatetime if necesaary (e.g. State End Date/Time is not populated due to it being outside of the date/time input range.

If there is no activity for the agent ID selected, simply display 0 for all of the totals and display no table formatted data.
EnhancementReachme Reports
UC-4154Show archived recordings in the call recording widgets differently than non archived recordingsThis is a companion issue for UC-4147. Enhancement to display Archived recordings in recoding widget and highlight them with a different color so the Administrator knows they are in Archive.EnhancementReachme
UC-4155Collation of reports in alphabetical orderCurrently the reports dropdown select tool is showing Outbound Reports positioned in between the Traffic - Line Traffic Overview and Traffic - Queue Group Traffic Overview.
We could use a alphabetical sort order or collate them each in their own category to be more eye pleasing.
Also there is one item which i think is a leftover from previous releases and should not be there : Queue Traffic Reports - Queue Group Traffic.
EnhancementReachme Reports
UC-4156Freeswitch restarts when clients or queues are added/edited - result is all reach calls dropFixed an issue where if an Administrator adds a new Reachme Client or configures a new queue or edits existing queues/clients in CallQueue then the freeswitch service will restart.

Freeswitch restart will drop all calls anchored in Reachme.

Changed freeswitch operation to reload instead of restart.
FixConfig
UC-4161When generating Agent Answer Performance by Group the output won't mention selected groupsAdded an enhancement so that when generating Agent Answer Performance by Group you didn't see additional info about what group you've selected as you see in Agent Activity by Group reportEnhancementReachme Reports
UC-4165Report selected time frame is not mentioned in some types of exported reportThe selected time frame is shown when you generate the report - however this time frame is not mentioned when you export a report of type : Excel, DOCX, ODT, ODS, XLSX
Works for other formats.
EnhancementReachme Reports
UC-4170Reports exported in ODS format missing part of the first rowWhen you export reports in ODS format,part(or all) of the first row is missing. The first row is the one that includes the Column names.
I think all reports have two rows with column names.
The firsts one will not be visible or only part of it will be, the right-most part.
FixReachme Reports
UC-4171Inconsistent value for nothing : null, n/a, NA, 0, 0:00Fixed inconsistencies where in the same report(Agent Group activity) we are showing 3 different things for the case where we should maybe just show 0 and 0:00
Also in a different report (Agent activity by group) we have a different view.
FixReachme Reports
UC-4174Totals row and Average Hold Time incorrectFixed an issue such that when an Agent Group Activity report (or Agent Activity by Group) is generated, the Totals row will compute some value but the value is wrong.FixReachme Reports
UC-4175Change default start/end date time for Agent Answer Performance by Group/Agent Group Productivity/Agent ProductivityAgent Answer Performance by Group report

Currently defaults to a start date of 5/26.
Currently defaults to a end date of "now"
Change to have a default start date/time to 1 week prior to today and a default end date of the start of the day tomorrow
(same as agent activity by group)

Agent Group Productivity report

Currently defaults to a start date of 5/26.
Currently defaults to a end date of "now".
Change to have a default start date/time to 1 week prior to today and a default end date of the start of the day tomorrow
(same as agent activity by group)

Agent Productivity report

Currently defaults to a start date of 5/26.
Currently defaults to a end date of "now"
Change to have a default start date/time to 1 week prior to today and a default end date of the start of the day tomorrow
(same as agent activity by group)
EnhancementReachme Reports
UC-4176Change default start/end date time for CDR/CDR Brief/CDR Extended/CDR CompactCDR/CDR Brief/CDR Extended/CDR Compact (ensure that all cdr versions have the same start/end defaults as described below; basically current day)
Currently defaults to a start date of 5/26.
Currently defaults to a end date of "now"
Change to default to today; start of today until start of tomorrow so all day today included
(same as Agent Activity Individual)
EnhancementReachme Reports
UC-4177Change default start/end date time for Client Traffic Overview/Outbound Overview by Client/Queue Group Traffic Overview/Queue Traffic Overview/Line Traffic OverviewClient Traffic Overview

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)

Line Traffic Overview

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)

Outbound Overview by Client

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)
(same as Client Traffic Overview)

Queue Group Traffic Overview

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)
(same as Client Traffic Overview)

Queue Traffic Overview

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)
(same as Client Traffic Overview)
EnhancementReachme Reports
UC-4179Total Outbound time computation different across similar agent reportsFixed a problem with incosistent data in similar reports.

Agent Group Activity will display under Outbound Activity-Total Time the value of outbound CPT , which is the time starting with the customer answering the call until it ends

Agent Activity by Group and Agent Activity Individual will display under Outbound Activity-Total Time the value of outbound CPT+Time In Queue/Precall, which is the time starting after the agent clicks the Outbound call widget and select a customer until the end of the call.

Having different outputs in different reports for the same column could be confusing for customers.
I don't know which one we want to keep either.
FixReachme Reports
UC-4187Cannot end callback call from dashboardFixed an issue that didn't allow the Reachme Agent to end a callback from the dashboard

Steps to reproduce:
1.While no agent is Idle, drop a voicemail in queue
2.Go idle and receive the voicemail
3.Listen to it, then click callback button
Call is placed back to client, you can hear ring back
4.Answer the callback from the other end
There is voice path
5.Try ending the call from dashboard
Issue: you can't
6.Try ending it from phone
Works
7.Now after the call is ended you will be placed in Wrap-up
Issue: once you click Done on the wrap-up, you are back at callback screen
FixReachme
UC-4188For a callback either a CDR entry is missing or Last Segment is wrongFixed an issue with callback calls that were missing information in reports.

Steps to reproduce
1.Login with an agent in dashboard don't go available yet; call into queue and drop a voicemail by pressing * button
2.Go available and receive the incoming voicemail call, then click the callback button, answer it from the other side and end it after a while(can't end it from dashb UC-4187, but you can end it from phone)
3.Generate report

Issue:
THere are two call entries : one corresponds to voicemail being left in queue
The second one has disposition : callback and last segment N
So either a cdr entry is missing or the last segment value is wrong
FixReachme Reports
UC-4194Help button redirects to wrong pageFixed an issue with the Admin portal where the help button redirected to the wrong web page.FixConfig
UC-4208Enabling/Disabling live attendant from TUI restarts proxy and registrarFixed an issue that caused the proxy and registrar to restart when the live attendant was enabled or disabled through the TUI.FixConfig
UW-310Call History in Unite Web and Unite LiteUsers would like to have the ability to see their call history in Unite Web and Unite Lite.New FeatureUnite Web / Unite Lite
UW-320Referential URL for LogoutThis feature request is to make this URL upon logout configurable such that a customer could use a proxy and have their users returned to something like userportal.ezuce.com

The other option is to make the URL used for logout referential to the current URL such that it just goes back as many layers as it needs to get back to the original proxy URL.
New FeatureUnite Web
UW-328Warn browser user before closing UniteWebAn administrator would like to issue a warning about closing Unite Web.EnhancementUnite Web
UW-331Unite Web will send 20 GET requests for a conference room if it's not activeSteps to reproduce:
1. A user is configured as a conference room owner.
2. User logs in Unite Web.

Issue: if you look under the browser dev tools you can see that 20 GET requests are sent to the server for that conference room and server replies with 406 Conf found but not active.
If you go to the Conference section in UW, 20 more GET messages are sent
Each time 20 more messages are sent

It does not cause any apparent issues, but there will be a large load generated if many users are logged in.
FixUnite Web
UW-334Inconsistencies across browsers when downloading voicemails from portalVoicemail file names are not consistent across different web browsers.

Steps to reproduce:
1.From Admin portal System->Voicemail type is set to .wav
2.Login to UW->Voicemails
3.In inbox voice messages are named like : "Voice Message 100000004",
4.Open a voice mail and click download.

In Firefox and Chrome : file downloaded is named : "voicemail.mp3" though the file format is actually .wav
In Safari : voicemail is named "100000004" with no extension
In IE : voicemail is named "100000004.wav"

Safari, Firefox and Chrome are clearly wrong.
FixUnite Web / Unite Lite
UW-338Unite Web should allow sip address under speeddial menuUnite Web and Lite user Web Portal does not allow for non-numeric characters in speeddial field.EnhancementUnite Web / Unite Lite
UW-342Upgrade Angular VersionDue call history feature update angular to the latest version.EnhancementUnite Web / Unite Lite
UW-343Lowercase Only Search for UniteWeb LiteUsing the UniteWeb Lite UI you are only able to search users using lowercase. Anything other than lowercase will not produce any results.FixUnite Lite
UW-344Unable to Expand Contact Information for User Search in UniteWeb LiteUpon locating a user using the search functionality you are unable to expand the contact information of the user by click on the avatar as you can in UniteWeb standard.FixUnite Lite
UW-345Conference Bridge Users DuplicatingIn the user's conference bridge internal participants are duplicating in the window.FixUnite Web / Unite Lite
UW-346Uniteme Web, make sound notification setting persist in cache per browser/userUniteme web, make sound notification setting persist in cache per browser/user, and make option enabled by defaultFixUnite Web
UW-348On contacts tab, when user trys to hide/unhide the list, it doesn't workFixed an issue where after loging to unite web page with a normal user with IM access, goes to the contacts page and try to hide/unhide it. After several attempts to hide it, it doesn't work. It works only if the user press on hide arrow, goes to activity list and returns back to contacts.FixUnite Web / Unite Lite

 

Issues Sorted by Issue Keyword

 JIRA nameRN ContentEnhancement/Fix/Known IssueKey words
SIPX-504Audiocodes template missing CallerIdFixed an issue where the board.ini files generated by sipX for version 6.0 of Audiocodes FXS devices does not include the caller-id name fields. These should be picked up by the line settings for the user name. These could be set manually in an ATAs web UI but they are lost whenever upload the ini file.

Here is an example of what the device needs.
;
; *** TABLE CallerDisplayInfo ***
;
;

[ CallerDisplayInfo ]
FORMAT CallerDisplayInfo_Index = CallerDisplayInfo_DisplayString, CallerDisplayInfo_IsCidRestricted;
CallerDisplayInfo 0 = "Irradiation Svc MRB", 0;
CallerDisplayInfo 1 = "AZ ELEV", 0;

[ \CallerDisplayInfo ]
FixAudioCodes
SIPX-404P-Preferred-Identity of Proxy - gui workCreate a jira with a check box in proxy setup to pass p-asserted-identity (default should be to not pass (as it operates now)): GUI change.EnhancementConfig
SIPX-485Move some Polycom Configuration Items to AdvancedEnhancement to move some Polycom settings that cause problems for the system to the Advanced tab.

In all Polycom Phones & Phone Groups:

SIP Tab:

This entire section -> Server Feature Control

Server Based Call Forwarding (Default: unchecked)
Enable or disable server-based call forwarding.
Server Based Call Forwarding Local Processing (Default: checked)
Enable or disable local call forwarding behavior when server-based call forwarding is enabled.
Server Based Do Not Disturb (Default: unchecked)
Enable or disable server-based DND.
Server Based DNo Not Disturb Local Processing (Default: checked)
Enable or disable local DND behavior when server-based enabled.

In the
Device -> Phone -> Line -> Call Handling page move:

Missed Calls (Default: unchecked)
If set to 0, all missed-call events will increment the counter If set to 1, only missed-call events sent by the server will increment the counter.

On all items add a message: "Warning: Changing these values can cause server instability."
EnhancementConfig
UC-3503Allow speedials for User IDs consisting of numbers/lettersAn administrator would like to allow letters in the user ID along with numbers.

Currently it isn't possible to change the speed dial lists via the new user web portal when a user without a number is listed; for instance, when the user ID consists of letters instead of numbers. This is used also for ACD, when the user registers in order to make/receive calls. In this case the "save" and "save and update" fields are not selectable, so that a user cannot make any changes. As soon as the user with no user ID is removed, changes can be made and it works just as desired.

There are customers that have letters instead of numbers for their user ID, so this feature would be blocked for them.
EnhancementConfig
UC-4078Need to remove/hide/add a danger tag message for Security Classification parameter

If an administrator enables Security Classification under Devices--> Phones-->{Phone}---> SIP, it will cause 1000+ Sip messages in less than 1 minute
Subscribing for event:as-feature-event which will eventually consume server resources and bring the server down.

This JIRA is to move this setting to Advanced page and put a warning on this setting.

For these Subscribes server responds with:
SIP/2.0 482 Loop Detected
Via: SIP/2.0/UDP 172.31.1.8;branch=z9hG4bK-XX-0f8b58jLXg1IDnWhjj9Eje2rJg~06cDismVVIpdr`rHxNEPbQ
Via: SIP/2.0/TCP 192.168.1.164;branch=z9hG4bKe4606e0e5C28F81;received=5.2.152.210;rport=30065
From: \"Mihai - backup Costache\" <sip:2049@ezuce.com>;tag=679010C6-DE4E4609
To: <sip:2049@ezuce.com>;tag=B5A9A0F1-4F43A0E6
Cseq: 1 SUBSCRIBE
Call-Id: 53bcdfd6-2ecb3079-48caae1e@192.168.1.164
Record-Route: <sip:107.23.34.40:5060;lr;transport=tcp;sipXecs-rs=%2Aauth%7E.%2Afrom%7ENjc5MDEwQzYtREU0RTQ2MDk%60.900_ntap%2ACeT%7ENS4yLjE1Mi4yMTA6MzAwNjU7dHJhbnNwb3J0

PXRjcA%60%60.900_ntap%2ACrT%7ENS4yLjE1Mi4yMTA6MzAwNjU7dHJhbnNwb3J0PXRjcA%60%60%2102eddc0b252d06f61fccb2de07fdf2d5>
Event: as-feature-event
User-Agent: PolycomVVX-VVX_400-UA/5.2.5.0639
Accept-Language: en
Content-Length: 0
Date: Mon, 16 May 2016 07:45:04 GMT

EnhancementConfig
SIPX-389Cannot access HTML reportsFixed an issue that cropped up in 15.10 that caused HTML reports in Call Detail Records > Reports to not work.

PDF, CSV, and XLS files were accessed without problems.

HTTP ERROR 500

Problem accessing /sipxconfig/reportsService.svc. Reason:

Server Error
FixConfig
SIPX-401DID in FAX, Hunt Groups Voicemail, etc., are not indexedFixed an issue where the DID fields added for huntgroups, voicemail service, fax did, etc. are not indexed or searchable by the system. It acknowledges they are there by not allowing a duplicate.FixConfig
SIPX-482Can't remove a Phone Group from Intercom, Groups field can't be emptyFixed an issue where the Intercom Groups field can't be empty.

Steps to reproduce:
1.Create a phone group
2.Go to Intercom, here by default the Groups field is empty
3.Add the phone group to Intercom->Groups, Apply
4.Remove the phone group from Intercom->Group, Apply

Issue: You are prompted "You must enter a value for Groups.".

So you cannot leave the field empty.

You have to make another phone group , add it to this Groups field, and deleted the other one you want to delete...
FixConfig
SIPX-484Slow Mongo queries due to instrument field not indexed in registration dbThere are bunch of slow queries in mongo logs like

Sun Mar 9 01:03:45.779 [conn33033] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f245d6b5", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4381 keyUpdates:0 numYields: 34 locks(micros) r:40511 nreturned:1 reslen:431 583ms
Sun Mar 9 01:03:45.784 [conn33636] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23ec1d5", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4386 keyUpdates:0 numYields: 34 locks(micros) r:34357 nreturned:2 reslen:848 587ms
Sun Mar 9 01:03:45.785 [conn31556] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23e2026", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4382 keyUpdates:0 numYields: 34 locks(micros) r:39891 nreturned:0 reslen:20 583ms
Sun Mar 9 01:03:45.788 [conn32804] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f246046c", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4380 keyUpdates:0 numYields: 34 locks(micros) r:41638 nreturned:3 reslen:1262 590ms
Sun Mar 9 01:03:45.794 [conn32517] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2ae5678", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4378 keyUpdates:0 numYields: 34 locks(micros) r:38242 nreturned:2 reslen:844 593ms
Sun Mar 9 01:03:45.800 [conn32940] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23e849c", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4377 keyUpdates:0 numYields: 34 locks(micros) r:31570 nreturned:7 reslen:2918 612ms
Sun Mar 9 01:03:45.826 [conn33283] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23a25f1", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4375 keyUpdates:0 numYields: 34 locks(micros) r:40170 nreturned:2 reslen:846 606ms
Sun Mar 9 01:03:45.828 [conn33285] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2ae5676", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4376 keyUpdates:0 numYields: 34 locks(micros) r:51343 nreturned:1 reslen:434 609ms
Sun Mar 9 01:03:45.833 [conn33281] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2ab6e3c", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4375 keyUpdates:0 numYields: 34 locks(micros) r:51153 nreturned:2 reslen:844 620ms
Sun Mar 9 01:03:45.867 [conn33301] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f23bc053", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4375 keyUpdates:0 numYields: 34 locks(micros) r:44507 nreturned:7 reslen:2904 116ms
Sun Mar 9 01:03:45.868 [conn33300] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2b217a9", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:4375 keyUpdates:0 numYields: 34 locks(micros) r:43480 nreturned:2 reslen:844 125ms
Sun Mar 9 01:03:45.901 [conn33012] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2ae75b0", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:8744 keyUpdates:0 numYields: 68 locks(micros) r:71578 nreturned:1 reslen:432 133ms
Sun Mar 9 01:03:45.903 [conn33317] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2b217a9", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:8744 keyUpdates:0 numYields: 68 locks(micros) r:67004 nreturned:2 reslen:844 125ms
Sun Mar 9 01:03:45.920 [conn33315] query node.registrar query: { $readPreference: { mode: "primaryPreferred" }, query: { instrument: "0004f2f60fcf", expirationTime: { $gt: 0 } } } ntoreturn:0 ntoskip:0 nscanned:8745 keyUpdates:0 numYields: 68 locks(micros) r:71890 nreturned:3 reslen:1262 138ms

sipxecs:PRIMARY> db.system.indexes.find()
{ "v" : 1, "key" : { "_id" : 1 }, "ns" : "node.registrar", "name" : "_id_" }
{ "v" : 1, "key" : { "identity" : 1 }, "ns" : "node.registrar", "name" : "identity_1" }
{ "v" : 1, "key" : { "expirationTime" : 1 }, "ns" : "node.registrar", "name" : "expirationTime_1" }
{ "v" : 1, "key" : { "_id" : 1 }, "ns" : "node.subscription", "name" : "_id_" }
{ "v" : 1, "key" : { "expires" : 1 }, "ns" : "node.subscription", "name" : "expires_1" }
{ "v" : 1, "key" : { "key" : 1 }, "ns" : "node.subscription", "name" : "key_1" }
{ "v" : 1, "key" : { "toUri" : 1 }, "ns" : "node.subscription", "name" : "toUri_1" }
{ "v" : 1, "key" : { "shardId" : 1 }, "ns" : "node.subscription", "name" : "shardId_1" }

My call would be to use sparse indexes as there could be null instruments
http://docs.mongodb.org/manual/core/index-sparse/
FixConfig
SIPX-493Configuration Generation Error after upgrade from 16.02 to 16.04Fixed an issue that caused a Configuration Generation Error after the upgrade from 16.02 to 16.04.

Configuration generation 5/21/16 11:38 AM 5/21/16 11:38 AM Failed Internal Error null

Service not running: Voicemail/AutoAttendant/IVR/MoH (sipxivr)
FixConfig
SIPX-501With a valid/signed certificate, connecting over HTTPS will prompt you to accept an invalid cert localhost.localdomainFixed an issue where with a valid signed certificate, connecting over HTTPS will prompt the user to accept an invalid certificate for localhost.localdomain

Steps to reproduce:
1.Created a new VM to test UC-3592 - set it up with fqdn "pr.ezuce.com"
2.Imported a valid certificate(the one provided for *ezuce.com) by going to :
System->Certificates->Web Certificate->Certificate File:"STAR_ezuce_com.crt",Key File :"server.key",Certificate Chain File:"STAR_ezuce_com.ca-bundle"
3.Verified certificate was correctly applied by logging into Admin Portal again

Issue: tried in multiple ways to make it load the valid certificate but it did not.

Server kept sending invalid/old localhost.localdomain certificate.

Server send profiles,reboot, trying different brwsers etc did not work.
FixConfig
SIPX-507Callqueue doesnt show queue's name as calleridFix an issue with a package that was missing from the install: freeswitch-lua.

This file was missing from sipxcom RPM spec file https://github.com/sipXcom/sipxecs/blob/release-16.04/sipXcom/sipxcom.spec.in
FixConfig
SIPX-512Live Attendant -> "Extension will ring for" option initialized with 0Fixed an illogical default value when a new live attendant was created.The "Extension will ring for" option was set to "0" seconds by default.
This means the extension setup as a live attendant extension would not ring at all until that value was changed to a proper time.

Set to default value of 20 seconds.
FixConfig
UC-1743Investigate DST updates in schedules, voicemails, cdrs, etc.Fixed an issue that caused Auto Attendant and IVR schedules to not be updated with DST change.

Workaround is to send server profiles.
FixConfig
UC-3870CDR csv export repeats page headers within rowsFixed an issue with CSV export in Call Detail Records that interspersed column header information with data.

Steps to reproduce:
1) Diagnostics -> Call Detail Records -> Reports -> "Call History" -> <Apply>
2) Download CSV
3) Open CSV

You will see that interspersed with your useful data is repeated header/footer/pagination records, making it very difficult to work with the exported data:

This also is done for Excel, but in that case it might be considered intentional in order to make a pretty printout. But then CSV is relied upon as the only pure data dump for post processing, but this header/footer data ruins that.
FixConfig
UC-3880Move Network Packet Capture Service to Diagnostic TabLogically the Network Packet Capture Service should go under the Diagnostics tab. It should be moved for continuity.FixConfig
UC-4025SOAP api bug - duplicate entriesFixed an issue with SOAP API to add a line to a phone. When adding a line to a phone via SOAP API the line gets duplicated.FixConfig
UC-4030If a user puts call queue extension in speed dial and subscribes to presence SSS has problemsThis enhancement will block users or administrators from configuring speed dials and enable presence for extensions that are Call Queue extensions. Call Queue extensions are not monitorable.

Steps to reproduce:
1. PSTN---> call DID---> call queue 120
2. 120 is monitored on both phones that are agents
3. Call answered on 201 (agent 2)
4. Presence for 201 and 120 was shown on 200 (agent 1) speed dial buttons
5. Call is parked on 1100 (presence was not seen for this extension)
6. presence for 120 is stuck untll the call is picked up with *781100 from call park and hung up
FixConfig
UC-4055Persistent tcp keepalive reductionImplemented Mongo recommendations regarding keepalives:

https://docs.mongodb.org/v2.6/faq/diagnostics/#does-tcp-keepalive-time-affect-sharded-clusters-and-replica-sets

"A common keep alive period is 7200 seconds (2 hours); however, different distributions and OS X may have different settings. For MongoDB, you will have better experiences with shorter keepalive periods, on the order of 300 seconds (five minutes)."

In order to make that persistent you will need to edit /etc/sysctl.conf and append net.ipv4.tcp_keepalive_time = 300
After that you will need to run " sysctl -p " to have the new values reloaded. You can check this new value with cat /proc/sys/net/ipv4/tcp_keepalive_time
FixConfig
UC-4156Freeswitch restarts when clients or queues are added/edited - result is all reach calls dropFixed an issue where if an Administrator adds a new Reachme Client or configures a new queue or edits existing queues/clients in CallQueue then the freeswitch service will restart.

Freeswitch restart will drop all calls anchored in Reachme.

Changed freeswitch operation to reload instead of restart.
FixConfig
UC-4194Help button redirects to wrong pageFixed an issue with the Admin portal where the help button redirected to the wrong web page.FixConfig
UC-4208Enabling/Disabling live attendant from TUI restarts proxy and registrarFixed an issue that caused the proxy and registrar to restart when the live attendant was enabled or disabled through the TUI.FixConfig
UC-1726Increase max value for voice mail importsFixed an issue that would now allow larger voicemail backups to be restored. Previously this value is set to maxSize=1073741824.

Steps to reproduce:
1. Attempt to upload a voicemail backup that is larger than 1073741824 bytes.

Error seen:
"Unable to decode multipart encoded request: the request was rejected because its size (1436454790) exceeds the configured maximum (1073741824)"
FixConfig Backup/Restore
UC-3587Cannot upload config backups larger than 1 GB (or 1073741824) multipart encoded errorFixed an issue trying to upload and restore large backup files.

Tried to upload a customer config backup (to recreate a setup) which has a size of 1.5 GB.
Upload fails with error :

"2015-03-04T16:28:31.259000Z":63:JAVA:WARNING:one.ctradu-legacy.ezuce.ro:P2-18:0 0000000:sipXconfig-web:"/sipxconfig/backup/RestorePage,$backup$RestoreUpload.upl oad.sdirect: "org.apache.hivemind.ApplicationRuntimeException: Unable to decode multipart encoded request: the request was rejected because its size (1647324186) exceeds the configured maximum (1073741824)
FixConfig Backup/Restore
UC-4085Decrease number of DB queries by openuc-customcallerid pluginThe openuc-customcallerid makes mongo query for every single packet of call.FixCustom CallerID
SIPX-496Allow MP3 bitrate setting in IVR UIAn enhancement to allow the adjustment of the MP3 recording rates. The MP3 bitrate defaults chosen by mod_shout work out to 16 kbps 8000 Hz recordings and 32 kbps for 16000 Hz recordings. These can cause significant warble/distortion/tinniness. Suitable defaults to be double each of these values, or 32 kbps @ 8000 or 64 kbps @ 16000.

Recording at 8Khz however bumps into an issue in Freeswitch that can cause FS to fail.

Variable recording settings that are safe are now located in System -> Media Services -> Settings.
EnhancementMedia Services
UC-4019Call park name extension creates a duplicate entry in mongo dbFixed an issue where if an administrator added a new call park with name=1200 and extension=1200 it will create 2 identical entries in mongodb. This in turn will answer with a 302 Redirect having the same contact twice.
This confused SSS and also FS as follows:

sipxecs:PRIMARY> db.entity.find({"ident":"1200@ezuce.ro"}).pretty()
{
"_id" : "ParkOrbit2",
"ident" : "1200@ezuce.ro",
"locations" : [ ],
"ent" : "parkorbit",
"als" : [
{
"id" : "1200",
"cnt" : "sip:1200@10.0.0.23:15060",
"rln" : "orbit"
},
{
"id" : "1200",
"cnt" : "sip:1200@10.0.0.23:15060",
"rln" : "orbit"
},
{
"id" : "*41200",
"cnt" : "sip:*41200@10.0.0.23:15060",
"rln" : "unpark"
},
{
"id" : "*781200",
"cnt" : "sip:*781200@10.0.0.23:15060",
"rln" : "unpark"
}
]
}
FixPark
SIPX-481Add support for Polycom 301, 311, 401, 411, 501, 601Polycom has added some new phones. The phones are technically the same as the 300, 310, 400, 410, 500 and 600 from a configuration standpoint. The phones have upgraded processor and memory.

According to Polycom Support:

NOTICE: UCS 5.4.1.14510 should not be used for VVX 501 and VVX 601 phones. A Bluetooth headset issue has been fixed in 5.4.1.16215 for VVX 501 and 601 phones. For all the other phone models UCS 5.4.1.14510 is the supported GA release.

NOTICE: The issues that required UCS 5.4.2 to be withdrawn from the Polycom Support web site have now been resolved and the new build is now available for download. Polycom recommends that any customers who have already downloaded UCS 5.4.2 should download UCS 5.4.2 Rev D and use that release going forward. If you have any questions, please contact your Polycom Global Support representative.

So, 5.4.1 is the earliest firmware rev for these phones, 5.4.2 will not exist and 5.4.3 is also now available.
EnhancementPolycom
UC-3903Improvement for default line labels in Polycom 5.xMake the default line labels for Polycom Phones with firmware 5.x and higher display extension numbers vs. names.

Features in Polycom 5.x firmware are starting to make it more desirable for production (for example, the ability to set default transfer type). The big problem moving from 4.x firmware is that the phones change to display the name of the user instead of the extension. Most users prefer to continue seeing the extension number as they do now.

While it can be manually adjusted under the line options of each phone, having 1,000+ phones to fix would be a very manual process.
EnhancementPolycom
UC-4002Proxy should add "transport=tcp" into Record-Route of responses (180, 200) in case TCP usage- SIP sidePer RFC https://tools.ietf.org/html/rfc5658 , proxy should put "transport=tcp" into Record-Route of responses (180, 200) in case TCP is required for this call leg. By default (when no transport specified) UDP should be used. So in this case Polycom behavior is valid. This is proxy bug.

Grandstream is not compliant with RFC strictly, it just ignores absence of transport.

This Jira was created to make sure TCP protocol is kept between Proxy and internal user, when set, and not flip-flop to UDP.

It only involves SIP Core side work (no config).
FixProxy
UC-4104Mongo C++ driver fix for tcp connection issueMongo C++ driver is creating large number of tcp connections on secondary database servers.FixProxy
UC-3825Reach Outbound - Update Agent Manager Group SectionEnhancement to update the in session counts in the Agent manager group section. Previously the agent that is on an outbound is still counted as an agent that is in released rather than in session.EnhancementReachme
UC-3826Reach Outbound - Update Agent ManagerEnhancement to update the agent group section of the agent manager widget to show in session count for inbound and for outbound.

Column for In Session make
In Session ... then under it
in/Out

Then show counts of agents in session for inbound and outbound separately. So if there are 20 agents in session on inbounds and 3 in session for outbounds show 20/3

In addition, an agent that is in the process of making an outbound call and is in the ringing state during the outbound call processing should be counted as such under the ringing count in the agent manager.
EnhancementReachme
UC-3827Update Icon for "in session" identifying inbound vs. outbound, fix view of long customer name, fix agent manager unable to see outbound call status after page refreshEnhance the Agent Manager Agent Section to show that an Agent is on an outbound call and not just in session.

This will be specified by a different icon representing an outbound call.

Whatever icon we use there should also then be used in the session manager for the agent when an outbound call has been made and is in session.
EnhancementReachme
UC-3976Validate data entries when an agent makes a transfer / conference to a numberAn agent is allowed to transfer a call to an external number or to make a conference with a third party. When selecting 'Number' from the 'Transfer / Conference' drop down list, he is asked to input a number.

Data entered in that text field was not validated and the agent can insert bad characters, like %.

We added an enhancement to validate the input strip any special, but allowed characters.

Note that there is a small difference in the way the validation should work for a transfer versus a conference. For a conference, there is an origination command being issued in the backed, while for a transfer there is a uuid_transfer FS call.
EnhancementReachme
UC-3989Make Reachme statistics generation configurableAdded a configuration parameter to set an interval for statistics being generated. At present statistics are generated in real time and this can create a lot of database traffic.

By making this happen at specified intervals we can optimize and minimize database queries.
EnhancementReachme
UC-3994Disable "Continue" button during Reachme advanced login when URI is enteredDuring the advanced login process for a reach agent, the agent sees 2 buttons (Continue and Use Advanced Login). At first, the Continue button is enabled and the Advanced login button is disabled. When the user puts in valid characters in the sip uri field the Advanced Login button is enabled.

However, the continue button is also still enabled and can be pushed. If an agent does this, they are logged in via their normal sip phone. This can be confusing to users who entered a sip uri (phone number) and are expecting to receive calls there.

This enhancement request is to disable the continue button once there is a valid entry in the sip uri field.

In short, have only one of the 2 buttons enabled at any given time. The Continue button is enabled before valid characters are in the sip uri and the advance login button is enabled once there are valid characters in the sip uri field but BOTH buttons are never enabled at the same time.
EnhancementReachme
UC-3998Allow a Reachme Agent to change Release Reason while in the release modeCurrently, if a Reach agent is in the release mode but they want to select a different release reason, the only way that they can do that is to go available (idle) and then go back to the release mode with a different reason code from the drop down.

This enhancement request is to allow the agent to select a new release reason from the list while they are already in the release mode.

We must ensure that we keep event data associated with reporting of how much time was spent in each release reason when implementing this enhancement.
EnhancementReachme
UC-4034Improve usability of Reach OutboundCurrently, when the agent begins the process of an outbound call, they select a client from the Outbound Call drop down. The system then rings their phone. Once they answer the call they get a text box to enter the phone number that they would like to call.

Part 1 of this enhancement:
When the agent answers the call, place the cursor in the phone number text box automatically so that they don't have to click into the text box to begin entering the phone number that they want to call.

Part 2 of this enhancement:
If the agent hits enter/return, the outbound call should be launched as if they clicked on the call button. This return to call and the click to call button should only be allowed if the phone number entered is valid based upon current checks for that content. In other words, if the agent enters a character like 'a', then hits return, it would not launch the call since the content of the outbound number text box is invalid. The same should be true of clicking the call button.
EnhancementReachme
UC-4121Update icons for agent OutboundRelated to UC-3827. Update the outbound icons to allow users to better identify call direction.EnhancementReachme
UC-4126Call Status of Outbound Conference is not Updated.In the Reachme Session Manager Widget, only in session call status is visible for outbound call conference. Add enhancement to also be able to see the call status of an outbound conference.EnhancementReachme
UC-4137Deploy Custom JasperServer extensionsFor the Reachme Standard Report Package we need a custom extension for JasperServer allowing us to use a custom Interval Data Source. This will allow for deployment of such extensions to new releases and also be able to backport them if needed.

Interval Data Source is not a "real" datasource (no data is actually read from DB). It must create successive time intervals defined by timestamps entered to "From" and "To" input controls and value of interval length entered to "Interval" input control. Each interval is then defined by its own start and end timestamps, first interval must start at "From" timestamp, last interval must end at "To" timestamp, even if it will be shorter than requested Interval length value.
EnhancementReachme
UC-4147Read reach recordings from archive pathCurrently Reachme recordings are read only from GridFS, so when the recording is archived, Reachme does not files from archive location. This enhancement allows Reachme to read from Mongo's GridFS as well as the Archive path.EnhancementReachme
UC-4154Show archived recordings in the call recording widgets differently than non archived recordingsThis is a companion issue for UC-4147. Enhancement to display Archived recordings in recoding widget and highlight them with a different color so the Administrator knows they are in Archive.EnhancementReachme
UC-3592Problems with SSL certificate if Reachme is not running on primaryFixed an issue where if Reachme is enabled on a node other than the primary then "cowboy" collection will read just root web certificate and will ignore certificate chain (intermediary certificate).

As an additional (and important) note: To run Reachme on other node you need to use wildcard certificate
FixReachme
UC-3655Conference call does not end when an agent makes outbound call, invites "number" into conference, and then agent ends conf by clicking X in the dashboardFixed an issue where conference calls do not end properly when an agent makes an outbound call, invites a "number" into conference, and the agent then tries to end the conference by clicking on the X in the dashboard.

Steps to reproduce:
1.Agent makes outbound call
2.Customer answers
3.Call flow continues with the Agent creating a conf call by choosing Transfer/Conf - "Number" and inviting a 3rd participant
4.3rd participant joins and all can hear each other
5.Agent drops the call by clicking "X" in the dashboard

Issue : conference call does not end.

If the initiator of the call ,ends the call, then conf call should end.

In this case Agent is the one who initiated the calls, but when he drops, conf call continues between the customer and the invited "number"

This issue only happens if the agent ends the call by clicking X. DOes not happen if he ends call from deskphone.
FixReachme
UC-3841Multiple calls getClient to backend causes errors in browser consoleFixed an issue with multiple calls of getClient to backend was causing errors in browser console.FixReachme
UC-3887Agent caller id shown twice in session manager widgetFixed an issue where the Agent's CallerID was displayed twice in the Agent Session Manager.

Steps to reproduce:
Agent : Mary Jane with extension 302
Client : Ezuce ,to reach this client the number is 309
1.Agent logs in and makes an outbound call to client Ezuce by dialing 309.

Issue : in the session manager widget ,next to the customer avatar , you can see : Ezuce 302 302 309

So we have client name , agent caller Id , agent caller Id again and then the dialed number to reach the client.
FixReachme
UC-3990Reachme call recording ends when a call conferenced and then handed off to another AgentFixed an issue where a call recording would stop at the point where Agent 1 drops out of a call he or she conferenced in Agent 2 to handle.

Steps to recreate:
1. Call into a Reachme line that has a client associated with it that has call recording turned on.
2. Answer the call with agent1
3. Agent1 does a conference to queue, selects the queue and hits the conference button.
4. Agent1 awaits another agent to answer the call out of the queue (agent2)
5. Agent2 answers the conference request out of the queue.
6. Agent1 now drops out of the call via hitting the X button. This leaves the caller and agent2 talking.

The issue is that in this call flow the call recording file stops at the point that agent1 hits the X button to drop out of the call.

This also occurs if agent1 uses the same conference hand off function to another agent.

This does NOT occur if agent1 blind transfers the caller to another queue or agent via using the transfer button rather than the conference button.
FixReachme
UC-4013Agent cannot end the call from dashboard during outbound precall - missing X buttonFixed an issue in recent versions of Reach where the Agent could not end an outbound call during the outbound precall (the X button was missing).

Steps to reproduce:
1. Agent selects client he wishes to call outbound to,
2. Agent answers the incoming reach call, and he then decides to no longer enter the caller number but rather wants to end the call.

The "x" is missing in the newer versions of Reach whereas there was an X available in 15.10 to end the pre-call.
FixReachme
UC-4014Transfer/conference from dashboard not working during a held outbound callFixed an issue where transfer or conference from Agent dashboard was not working during a held outbound call.

Steps to reproduce:
1. Make otubound call and place the call on hold.
2. Transfer/conference selector box is available when you hold the outbound call from dashboard.
3. Next, when you choose the option to transf/conf, you get to option for "Number"; try to complete it, and nothing happens.

In previous release the widget looked rather different, and you would not be able to use the transf/conf section while on hold

It's valid to place a call on hold and then conference in another party. For a call that is originally connected via outbound should look just like a call that was originally connected via inbound. Thus, hold then trans/conf should indeed work and it should work in the same way that a normal inbound call can be placed on hold and then trans/conf.
FixReachme
UC-4015Customer is left alone in call after an agent makes outbound call,invites "number" into conference,"number" drops and then agent ends conf by clicking X in the dashboardFixed an issue where if a caller is left alone in call after an agent makes outbound call, invites "number" into conference, "number" drops and then agent ends conf by clicking X in the dashboard the caller is not dropped but starts hearing queue MoH.

Steps to reproduce:
1. Agent makes outbound call
2. Callee answers
3. Call flow continues with the Agent creating a conf call by choosing Transfer/Conf - "Number" and inviting a 3rd participant
4. 3rd participant joins and all can hear each other
5. 3rd participant drops while Agent and callee are still on conf call ok
6. Agent drops the call by clicking "X" in the dashboard

Issue: Callee is not dropped from call, and starts hearing queue MoH

In release 15.10 in this last step, the callee would be dropped from call.
FixReachme
UC-4021Reach: Calls Stuck in Queue, Not Being Offered to AgentsWhen a reach vqueue is abnormally terminated, all it's registered calls are not offered to an agent anymore, they are essentially lost.

In most cases the reason that a vqueue gets terminated abnormally is a timeout to a disconnected phone.

The QUEUE_TIMEOUT is 1 minute, so if the connection to a call in queue drops, after 1 minute all the calls registered on that queue will not be offered anymore.

With this JIRA we created a fail-safe mechanism that moves all the calls in an abnormally terminated vqueue to another vqueue.
FixReachme
UC-4066Supervisor sees agent in Idle mode but agent is in Released mode after outbound callThe agent shows idle in the agent manager widget while showing released in the agent's UI.

To reproduce:
have an agent in the idle state
select a client to begin the process of making an outbound call
the agent's phone begins ringing
while the phone is still ringing, hit the release button on the agent UI
answer the phone
hang up the phone without putting in a phone number and making an outbound call

UI now shows release while the Agent Manager widget shows the agent as being idle.

If you place a call into the queue now the agent will not be offered the call even though they show as being idle in the Agent Manager. If you go idle in the agent portal now, the call will be delivered (gets back in sync between the Agent Manager and agent UI).
FixReachme
UC-4090Reach agent status in Agent Manager widget out of sync for outbound callsIn supervisor Agent Manager widget the agent's state shows that he's still on call although the call is terminated.

Steps to reproduce :
1. Agent selects a client and starts a pre-ring call for outbound call.
2. The agents's phone begins ringing.
3. Answers the phone and enters an external number to start an outbound call.
4. Call with external number is answered and then ended.

Workaround : refresh the supervisor web page.
FixReachme
UC-4101Block the ability to do a conference when on holdIn Agent Widget disable the ability to start a conference call when a call is on hold. This is a bit of a workaround to deal with the following workflow not working.

Steps to reproduce:
1.Agent A makes outbound call to customer,and customer answers
2.Agent A places this outbound call on hold from dashboard.
Result : call is on hold,customer can hear Moh
3.Agent A selects Transfer/Conference->Number->Enters "the number of the invited party"->Conference
Result : the invited party is being alerted by the incoming conf call while
Customer is still on hold and hears Moh
4.The invited party answers the call
Issue: Customer and the invited party are hearing MoH and can also hear eachother.
The agent who initiated this call still has the call on hold,as expected, however when he unholds the call from the dashboard,the call is not retrieved.
He must click Hold again and then again unhold the call - after he does this operation , MoH stops and all 3 can hear eachother.

This issue does not appear if at Step 2 , the agent does not hold the call.

UC-4140 will track fixing this workflow.
FixReachme
UC-4103Review/Improve Reach archiving scriptReview and improve the Reachme archiving script /usr/bin/reach-recordings-clean.pyFixReachme
UC-4108Reach: Inefficient method ouc_agents:get_online_agents/0Supervisors are not seeing some agents that are logged into acd and Idle state.

On agent screen they show Idle but when we go to supervisor account that agent doesn't show up. Its like dead session but shows as Idle.
FixReachme
UC-4187Cannot end callback call from dashboardFixed an issue that didn't allow the Reachme Agent to end a callback from the dashboard

Steps to reproduce:
1.While no agent is Idle, drop a voicemail in queue
2.Go idle and receive the voicemail
3.Listen to it, then click callback button
Call is placed back to client, you can hear ring back
4.Answer the callback from the other end
There is voice path
5.Try ending the call from dashboard
Issue: you can't
6.Try ending it from phone
Works
7.Now after the call is ended you will be placed in Wrap-up
Issue: once you click Done on the wrap-up, you are back at callback screen
FixReachme
UC-4060Enhance the Reach productivity reports to show values or percentagesFor the following 4 reports that exist in Reach today:
Agent Productivity
Agent Productivity Compact
Agent Group Productivity
Agent Group Productivity Compact

Do the following:
Add an radial dial input control that allows the user to select either % or raw numbers. Only one of the two may be selected. The Input should be called "Ouput Data In"

In short, the user would be identifying whether the output of the report should be provided in percentages or numbers.

The output would then follow the selection of the radial dial when the report is executed.
EnhancementReachme Reports
UC-4069Change Queue Traffic Detail Reach report to show periods with no activityThe current traffic detail report will not show a row of data for any period of time that had not activity. Example, if the interval selected to run the report for is every 60 minutes and the date/time range was for one full day, there is not 24 rows returned (some being 0 call activity). Instead, only the hour intervals that had call activity are shown.

This request is to show all intervals regardless of whether or not they had activity. For such a row with no call activity, simply show 0 in all columns of the row.

In addition, mirror the Queue Traffic with SLA report columns in the output of this new traffic detail report.
EnhancementReachme Reports
UC-4088Create a reach reports "redeployment package"Create a method of uninstalling all "old standard reports" and deploy all most recent versions of standard reports.

This cannot remove any custom reports that might already exist in the server.
EnhancementReachme Reports
UC-4112Add columns to the Queue/Line/Client Traffic Detail reportsAdd the following columns to all 3 of the traffic detail reports:
Sent to voicemail
Transfer out
Total abandon
SLA

They are the same columns as the traffic overview reports currently have.

This means that a SLA input parameter will need to be added to these traffic detail reports as well. It should be the same as the SLA input on the overview reports.
EnhancementReachme Reports
UC-4113Add inactive queues/lines/clients to Queue/Line/Client Overview Reach ReportsCurrently, if you run the queue traffic overview report for a data/time range that does not have any activity for a specific queue, this queue will not show up on the report at all. This is true for the Line and Client overview reports as well.

This enhancement request is to show all queueus/lines/clients on the output of that report regardless of whether or not they had activity.

However, this should be done based on an input parameter. The new input parameter will be a check box. The checkbox will be checked by default and the label of the checkbox will be "Hide Inactive".

If checked, the report output will have rows for ONLY those lines/clients/queues that have activity. If unchecked the report will show a row for all lines/clients/queues configured in the system even if they do not have activity for the date/time range selected. In this case, the inactive lines will just show 0 for counts and NA for other measurements such as CPT.
EnhancementReachme Reports
UC-4149Add Reachme Report called Agent State HistoryAdd a report called Agent State History.

Report should be placed in the Agent subcategory of reports and should be as follows:

Inputs:
Agent ID (single select list of all agents in the system)
Start Date/time
End Date/time

Output Title to include date/time range and Agent ID input

Text Prior to table formatted Data:

Total Time Logged In
Total Time Logged Out
Total Time In Released
Total Time Available for Calls

Note: these totals will not include time outside of the date/time range input. Example; if the agent logged in prior to 9am but the report is executed for a 9am start time, the total logged in time will not take into account time in logged in state prior to 9am.

Output Columns:
State Entered (Log In, Log Off, Idle, Release)
Reason (if state entered is release, this will show the release reason)
State Begin Date/Time of State change
State End Date/Time that this state was exited (into one of the other reported states of login, logoff, idle or released)
Duration (Total Time spent in this state before next State Change; State End Date Time - State Begin Date/Time)


Notes:
State changes other than login, logout, release and idle will not be shown. Example, ringing, in session, prering, etc are states that will not be shown on this report.
Duration will show in the format of w days, x hours, y minutes, z seconds
Duration will be calculated via start datetime or enddatetime if necesaary (e.g. State End Date/Time is not populated due to it being outside of the date/time input range.

If there is no activity for the agent ID selected, simply display 0 for all of the totals and display no table formatted data.
EnhancementReachme Reports
UC-4155Collation of reports in alphabetical orderCurrently the reports dropdown select tool is showing Outbound Reports positioned in between the Traffic - Line Traffic Overview and Traffic - Queue Group Traffic Overview.
We could use a alphabetical sort order or collate them each in their own category to be more eye pleasing.
Also there is one item which i think is a leftover from previous releases and should not be there : Queue Traffic Reports - Queue Group Traffic.
EnhancementReachme Reports
UC-4161When generating Agent Answer Performance by Group the output won't mention selected groupsAdded an enhancement so that when generating Agent Answer Performance by Group you didn't see additional info about what group you've selected as you see in Agent Activity by Group reportEnhancementReachme Reports
UC-4165Report selected time frame is not mentioned in some types of exported reportThe selected time frame is shown when you generate the report - however this time frame is not mentioned when you export a report of type : Excel, DOCX, ODT, ODS, XLSX
Works for other formats.
EnhancementReachme Reports
UC-4175Change default start/end date time for Agent Answer Performance by Group/Agent Group Productivity/Agent ProductivityAgent Answer Performance by Group report

Currently defaults to a start date of 5/26.
Currently defaults to a end date of "now"
Change to have a default start date/time to 1 week prior to today and a default end date of the start of the day tomorrow
(same as agent activity by group)

Agent Group Productivity report

Currently defaults to a start date of 5/26.
Currently defaults to a end date of "now".
Change to have a default start date/time to 1 week prior to today and a default end date of the start of the day tomorrow
(same as agent activity by group)

Agent Productivity report

Currently defaults to a start date of 5/26.
Currently defaults to a end date of "now"
Change to have a default start date/time to 1 week prior to today and a default end date of the start of the day tomorrow
(same as agent activity by group)
EnhancementReachme Reports
UC-4176Change default start/end date time for CDR/CDR Brief/CDR Extended/CDR CompactCDR/CDR Brief/CDR Extended/CDR Compact (ensure that all cdr versions have the same start/end defaults as described below; basically current day)
Currently defaults to a start date of 5/26.
Currently defaults to a end date of "now"
Change to default to today; start of today until start of tomorrow so all day today included
(same as Agent Activity Individual)
EnhancementReachme Reports
UC-4177Change default start/end date time for Client Traffic Overview/Outbound Overview by Client/Queue Group Traffic Overview/Queue Traffic Overview/Line Traffic OverviewClient Traffic Overview

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)

Line Traffic Overview

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)

Outbound Overview by Client

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)
(same as Client Traffic Overview)

Queue Group Traffic Overview

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)
(same as Client Traffic Overview)

Queue Traffic Overview

Currently defaults to a start date of 5/26
Currently defaults to an end date of 'Now'.
Change to default to today (start of today until start of tomorrow so all day today included)
(same as Client Traffic Overview)
EnhancementReachme Reports
UC-3964Queue Group Traffic reports should take their data from the Queue Group Traffic with SLAThe Queue Group Traffic reports need to take their data from the Queue Group Traffic with SLA.FixReachme Reports
UC-4054Reach CDR report has incorrect "Offered To Reach" timestampThe Reachme Call Detail Report had an incorrect "Offered To Reach" timestamp.

Steps to reproduce:
Place calls into reach and keeping manual timing of calls while doing so. Run the CDR report afterwards and check the offered to reach timestamp.

The thing that seemed to trigger this issue was having a call in queue for a long time before answering it with an agent. Example, place a call that is allowed to queue for over 2 minutes and another that is allowed to queue for over 4 minutes. Both had incorrect "offered to reach" times.

This was negatively effecting measurements on reports for average hold or in queue times.
FixReachme Reports
UC-4079Fix ASA calculation on All Reach ReportsASA is not calculated correctly on any of the Reach reports.

Correct it to be (Total time for all calls answered) / # of calls answered.
FixReachme Reports
UC-4170Reports exported in ODS format missing part of the first rowWhen you export reports in ODS format,part(or all) of the first row is missing. The first row is the one that includes the Column names.
I think all reports have two rows with column names.
The firsts one will not be visible or only part of it will be, the right-most part.
FixReachme Reports
UC-4171Inconsistent value for nothing : null, n/a, NA, 0, 0:00Fixed inconsistencies where in the same report(Agent Group activity) we are showing 3 different things for the case where we should maybe just show 0 and 0:00
Also in a different report (Agent activity by group) we have a different view.
FixReachme Reports
UC-4174Totals row and Average Hold Time incorrectFixed an issue such that when an Agent Group Activity report (or Agent Activity by Group) is generated, the Totals row will compute some value but the value is wrong.FixReachme Reports
UC-4179Total Outbound time computation different across similar agent reportsFixed a problem with incosistent data in similar reports.

Agent Group Activity will display under Outbound Activity-Total Time the value of outbound CPT , which is the time starting with the customer answering the call until it ends

Agent Activity by Group and Agent Activity Individual will display under Outbound Activity-Total Time the value of outbound CPT+Time In Queue/Precall, which is the time starting after the agent clicks the Outbound call widget and select a customer until the end of the call.

Having different outputs in different reports for the same column could be confusing for customers.
I don't know which one we want to keep either.
FixReachme Reports
UC-4188For a callback either a CDR entry is missing or Last Segment is wrongFixed an issue with callback calls that were missing information in reports.

Steps to reproduce
1.Login with an agent in dashboard don't go available yet; call into queue and drop a voicemail by pressing * button
2.Go available and receive the incoming voicemail call, then click the callback button, answer it from the other side and end it after a while(can't end it from dashb UC-4187, but you can end it from phone)
3.Generate report

Issue:
THere are two call entries : one corresponds to voicemail being left in queue
The second one has disposition : callback and last segment N
So either a cdr entry is missing or the last segment value is wrong
FixReachme Reports
UC-4005Add Reachme CDR report that contains the Wrap up, Node, Agent Node, Original Skills and Final Skills columnsCreate a new version of the CDR report that includes the following fields since those fields were available in previous releases.

Wrap up, Node, Agent Node, Original Skills and Final Skills columns
New FeatureReachme Reports
UC-4046Add new Daily and Weekly ReportsA weekly report on:

- Total number of inbound vs outbound calls per agent
- Total number of minutes/hours
- Total raw number of calls (ex. 500 calls from 4/24 – 4/29)
- Total transferred
- Total completed
- The option to filter out Inbound & Outbound

Automatically total up each column at the bottom.


A daily report on:

- Total number of minutes/hours in the given date/time range
- Total raw number of calls (ex. 500 calls from 9am – 12pm on 4/28/16)
- Total transferred
- Total completed
- Average hold time
- The option to filter out by Inbound & Outbound

Automatically total up each column at the bottom.

(They don’t need to see every leg of every calls. The idea is, they’re sales reps and they’re supposed to make x amount of calls per day so around lunch they usually pull their stats to see how much they need to ramp up in the afternoon. )
New FeatureReachme Reports
UC-4049New Report Agent Activity by GroupA new report called "Agent Activity by Group"

Report definition is as follows:

Inputs: Date/Time Start, Date/Time End, Multiselect Drop down for selection of one or more agent groups
Default would be all agent groups selected in the multiselect drop down
Default Date/Time Start = Date of 7 days ago; time of midnight (start of day)
Default Date/Time End = The current day and time of end of the day.
The date/time defaults are intended to provide a 1 week default including today's activity.

Output:
Agent, Total Inbound calls, Total Inbound Minutes, Total Inbound Completed, Total Inbound Transferred, Total Outbound calls, Total Outbound Minutes, Total Combined In/Out Calls, Total In/Out Minutes

Additional Output (totals row at bottom of report)
Totals Row at bottom. This row will be a total of each of the other columns of the report. Obviously we can't total the Agents column but all other columns should be totaled up.

It would be preferred that the report headings are grouped In sections of Inbound, Outbound and Total, then have each column as a subheading (e.g. the column of Total Inbound Calls would just say Total Calls but be under a report header of Inbound). However, care must be taken to ensure that when exporting the report to CSV, these headers don't mess up a standard CSV import to Excel or some other spreadsheet.

Measurement definition clarifications:
Total Inbound Completed is defined as an inbound call that an agent answered that was never transferred to another user/queue/number.

Total Inbound Transferred is defined as an inbound call that an agent answered that was ultimately transferred somewhere else.
New FeatureReachme Reports
UC-4050New Report Agent Activity IndividualA new report called "Agent Activity Individual"

Report definition is as follows:

Inputs: Date/Time Start, Date/Time End, Agent ID drop down or textual input
If a drop down with all reach agent ID's in the system can be populated that would be best. That drop down select would be a single select drop down meaning that you can only select a single user. It would be preferred that the user could start typing into the selection portion of the drop down to "find" a specific user and/or just manually enter the ID of choice.

Default would be no agent ID selected
Default Date/Time Start = beginning of the current day
Default Date/Time End = end of the current day
The date/time defaults are intended to provide activity for today thus far

Output:
Agent, Total Inbound calls, Total Inbound Minutes, Total Inbound Completed, Total Inbound Transferred, Total Outbound calls, Average Hold Time, Total Outbound Minutes, Total Combined In/Out Calls, Total In/Out Minutes

Note that this is the same output as the agent group activity report defined in uc-4049 with the addition of the "average hold time" field.

It would be preferred that the report headings are grouped In sections of Inbound, Outbound and Total, then have each column as a subheading (e.g. the column of Total Inbound Calls would just say Total Calls but be under a report header of Inbound). The average hold time field would be grouped with the Inbound measurements. Care must be taken to ensure that when exporting the report to CSV, these headers don't mess up a standard CSV import to Excel or some other spreadsheet.

Measurement definition clarifications:
Average Hold Time is relevant to inbound calls and is defined as the average amount of time spent in queue and in ringing for all calls that the selected agent answered.

Total Inbound Completed is defined as an inbound call that an agent answered that was never transferred to another user/queue/number.

Total Inbound Transferred is defined as an inbound call that an agent answered that was ultimately transferred somewhere else.
New FeatureReachme Reports
UC-4074Add Reach Client Detail ReportAdd a report that is very similar to the current Queue Traffic Detail Report.

This new report will be a client based report and that is the major difference in this report in comparison to the Queue Traffic Detail Report.

Additional columns for Outbound activity for the client are also added.

The input parameters of queue group and queue should be replaced with a single multiple select client drop down (with all/none/inverse options).

When the user selects one or more clients from the drop down, a from date/time, To date/time and an interval, the report will execute and output the results as identified in the attached screen shot.
New FeatureReachme Reports
UC-4075Add Client Traffic Overview Reach ReportAdd a report very similar to the Queue Traffic Overview Report.

This new report will be a client based report and that is the major difference in this report in comparison to the Queue Traffic Overview Report.

The input parameters will be the same (From Date/Time and To Date/Time)

Once the user selects a date time range and executes the report, the output will be as shown in the attached screen shot.
New FeatureReachme Reports
UC-4082Deploy additional Custom Reach Report as a standard reportEnsure that other new Custom reports are part of the deployed report package.New FeatureReachme Reports
UC-4083Deploy new custom reach Agent Activity report as a standard reportEnsure that the new agent activity custom reports are delivered as a standard report.New FeatureReachme Reports
UC-4093Add Agent Group Activity Reach ReportThis will be a custom report "Agent Group Activity" report but with rolled up stats based on agent group instead of agent by agent data.

Inputs:
From Date/Time
To Date/Time

Outputs:
Column Headers of Group, Inbound Activity, Outbound Activity, Total Activity
Columns under Group Header (Agent Group)
Columns under Inbound Activity Header (Total Calls, total time, completed calls, transferred calls, avg. hold time)
Columns under Outbound Activity Header (Total Calls, Total Time)
Columns under Total Activity (Total Calls, Total Time)

Note that this is exactly the same output as the existing report. Same look and feel. Just grouped by agent group.
New FeatureReachme Reports
UC-4096Add "Outbound Overview by Client" Reach reportAdd a reach report that shows an overview of outbound call activity by client.

Inputs:
Start date/time
End date/time
No Customer (checkbox)
Checkbox labeled "Hide Inactive" (default of checked)

If No Customer checkbox is checked, the output will contain a No Customer Entry that looks just like a normal client entry even though "No Customer" is in fact not a client.
For each client built in the system there will be a row in the output.

Outputs:
Client, Started, Sent, Answered, %Complete, Average Talk Time, Total Talk Time
A "totals" row at the bottom showing the totals for the columns (note that %Complete must be a weighted average rather than an average or sum of all of the column data).
The values of the outputs will be as follows:

Started - count of time that the agent selected a client from the drop down box to begin the process or making an outbound call. This is independent of whether or not they answered their phone when it rings.

Sent - how many outbound calls were sent (this would NOT include cases where an agent started the outbound call process but did not ultimately put in a number to call and send the call.

Answered - calls that were sent and answered by the called party.

%Complete - Answered / Attempts

Average Talk Time - Total Talk Time / number of completed

Total Talk Time - Total days/hours/minutes/seconds of all call talk time for all answered calls

If "hide inactive" is checked, clients with no outbound call activity for the start/end date/time are not shown. If "hide inactive" is not checked, clients with no outbound call activity for the start/end date/time will be shown with 0s for counts and NA for measurements such as %Complete.
New FeatureReachme Reports
UC-4097Add Reach Line Traffic Detail ReportAdd a report that is very similar to the current Queue Traffic Detail Report.

This new report will be a Line based report and that is the major difference in this report in comparison to the Queue Traffic Detail Report.

The input parameters of queue group and queue should be replaced with a single multiple select Line drop down (with all/none/inverse options).

When the user selects one or more lines from the drop down, a from date/time, To date/time and an interval, the report will execute and output the same information as is in the queue traffic details report except that the report title information at the top will show what lines were selected rather than what queue group and queue were selected and that the header row should read Line Activity instead of queue activity.
Screen shot of queue traffic detail report is attached for reference.
New FeatureReachme Reports
UC-4098Add "Line Traffic Overview" Reach ReportAdd a report very similar to the Queue Traffic Overview Report.

This new report will be a Line based report and that is the major difference in this report in comparison to the Queue Traffic Overview Report.

The input parameters will be the same (From Date/Time and To Date/Time)

Once the user selects a date time range and executes the report, the output will be as shown in the attached screen shot.
New FeatureReachme Reports
UC-4107Capture Agent Events for Reports UseCapture events with date/time stamps and agent login, agent name and agent group for the following:

login
logout
go release (with release reason)
go idle/available
Answer call
Missed call (e.g. was offered a call but didn't answer it)
End call (with direction or inbound or outbound)
start wrap
end wrap
In outbound setup (triggers when client is selected from drop down)
Ringing outbound (triggers when they launch the call to the outbound #)
On Outbound (triggers when far end outbound # answers)

Each record needs to be written immediately upon entry into one of the states above.
Each record should include at least the following:
Start Date/Time
State being entered
End Date/Time

Since an entry is written immediately upon entry into a new state, when a transition is made from one state to another, the previous state entry must be updated with the End Date/Time stamp and of course the new entry would need to be created for the state being newly entered into. When creating a new entry, the End Date/Time stamp will be initially null. It will later be updated to the date/time that the user enters another sate.

Care should be given to ensuring that that multiple entries with a null end date/time do not exist in the data table (e.g. Reach or DB crash the leaves entries with no end Date/Time).

This data is required to be able to produce an agent session report.

This data can be captured in the events collection and then processed and moved to some other collection like the other data in that collection is done. However, the end result must be that a collection like the call_segment_facts collection is created with the identified data above.
New FeatureReachme Reports
UC-4115Add Outbound Detail by Client Reach ReportAdd a reach report for detailed outbound call activity. This will be much like the outbound overview report by grouped the the time interval entered by the user.New FeatureReachme Reports
UC-3968Expose transport setting for sipXbridge in configEnhancement to expose a way through which sipXbridge can be set to use TCP or UDP transport.

The core functionality which allowed TCP or UDP usage was already implemented however it was not configurable from portal.
EnhancementsipXbridge
UC-4086After server Send Profiles, SSS stops working properlyAfter a send server profiles SSS stops working properly.

Steps to reproduce:
1. send server profiles - wait for Job Status to show complete.
2. Check for BLF on outbound or inbound PSTN call or internal calls - broken.
3. restart either phones or restart SSS
4. BLF now works on outbound or inbound PSTN call and internal calls

After server profiles re sent, at the same time in sipxsss.log
"2016-05-19T06:23:45.901811Z":23409:SIP:INFO:openuc.ezuce.com::7fbd3a78a700:sipxsss:"SetRefresherBase::mongoOpLogCallBackInsert::0x7ffd41a55250 "

Then within the next few seconds RLS lists are actively updated/removed/inserted.
FixSSS
UW-343Lowercase Only Search for UniteWeb LiteUsing the UniteWeb Lite UI you are only able to search users using lowercase. Anything other than lowercase will not produce any results.FixUnite Lite
UW-344Unable to Expand Contact Information for User Search in UniteWeb LiteUpon locating a user using the search functionality you are unable to expand the contact information of the user by click on the avatar as you can in UniteWeb standard.FixUnite Lite
UC-4016Bria devices are exhausting Unite Mobile LicensesFixed an issue with Unite Mobile licensing which was causing the licensing to detect Bria as Unite Mobile.FixUnite Mobile
UW-328Warn browser user before closing UniteWebAn administrator would like to issue a warning about closing Unite Web.EnhancementUnite Web
UW-331Unite Web will send 20 GET requests for a conference room if it's not activeSteps to reproduce:
1. A user is configured as a conference room owner.
2. User logs in Unite Web.

Issue: if you look under the browser dev tools you can see that 20 GET requests are sent to the server for that conference room and server replies with 406 Conf found but not active.
If you go to the Conference section in UW, 20 more GET messages are sent
Each time 20 more messages are sent

It does not cause any apparent issues, but there will be a large load generated if many users are logged in.
FixUnite Web
UW-346Uniteme Web, make sound notification setting persist in cache per browser/userUniteme web, make sound notification setting persist in cache per browser/user, and make option enabled by defaultFixUnite Web
UW-320Referential URL for LogoutThis feature request is to make this URL upon logout configurable such that a customer could use a proxy and have their users returned to something like userportal.ezuce.com

The other option is to make the URL used for logout referential to the current URL such that it just goes back as many layers as it needs to get back to the original proxy URL.
New FeatureUnite Web
UW-338Unite Web should allow sip address under speeddial menuUnite Web and Lite user Web Portal does not allow for non-numeric characters in speeddial field.EnhancementUnite Web / Unite Lite
UW-342Upgrade Angular VersionDue call history feature update angular to the latest version.EnhancementUnite Web / Unite Lite
SIPX-511Certificate issue with openfire/IM after fresh installResolved an issue where a freshly installed server was unable to login into Unite Web with IM.
This was a localised issue in openfire and probably introduced through jira SIPX-3.
FixUnite Web / Unite Lite
UW-334Inconsistencies across browsers when downloading voicemails from portalVoicemail file names are not consistent across different web browsers.

Steps to reproduce:
1.From Admin portal System->Voicemail type is set to .wav
2.Login to UW->Voicemails
3.In inbox voice messages are named like : "Voice Message 100000004",
4.Open a voice mail and click download.

In Firefox and Chrome : file downloaded is named : "voicemail.mp3" though the file format is actually .wav
In Safari : voicemail is named "100000004" with no extension
In IE : voicemail is named "100000004.wav"

Safari, Firefox and Chrome are clearly wrong.
FixUnite Web / Unite Lite
UW-345Conference Bridge Users DuplicatingIn the user's conference bridge internal participants are duplicating in the window.FixUnite Web / Unite Lite
UW-348On contacts tab, when user trys to hide/unhide the list, it doesn't workFixed an issue where after loging to unite web page with a normal user with IM access, goes to the contacts page and try to hide/unhide it. After several attempts to hide it, it doesn't work. It works only if the user press on hide arrow, goes to activity list and returns back to contacts.FixUnite Web / Unite Lite
UW-310Call History in Unite Web and Unite LiteUsers would like to have the ability to see their call history in Unite Web and Unite Lite.New FeatureUnite Web / Unite Lite
UC-4114Deleting Voicemails from link in eMail doesn't notify MWIThere are hyperlinks included in eMails sent as part of the Voicemail to eMail feature. If a user clicks on the Delete hyperlink the Voicemail is deleted but the Message Waiting Indicator service is not updated.

Setup and steps to reproduce:
1. Unified Messaging on the individual user, "E-mail format" set to Full.
2. Voicemail created, open email and use the delete button.
3. This takes you to the GUI log in, login, GUI page is blank, can only close the tab.
4. Voicemail does get deleted, but does not show up in the deleted folder and the MWI light remains blinking.
5. Play and manage voicemails buttons work as expected.

Expected behavior:
Upon delete move voicemail to deleted folder and NOTIFY MWI
FixVoicemail
SIPX-494Yealink ring typesEnhancement to add new Ring types according to Yealink configuration parameters in V8.

Examples:
account.1.ringtone.ring_type = Ring3.wav

It means configuring Ring3.wav for account1.

account.1.ringtone.ring_type = Common
It means account1 will use the ring tone selected for the IP phone configured by the parameter "phone_setting.ring_type".
EnhancementYealink
  • No labels