September 19, 2018
Fixed
The option to override all groups was still available when Single-Number Override setting was turned off for the account.
September 12, 2018
Improved
Updated internal components.
Fixed
In the web UI, the Time Zone field could not be edited after the number was created.
July 30, 2018
Fixed
Entering an incorrect group number using the IVR resulted in a system error.
CDRs that were not fully synchronized occasionally caused errors in the web UI.
Call plans could not be populated with switch point code criteria.
July 23, 2018
Fixed
The routing engine was incorrectly looking for the “custom criteria” variable and not finding it.
CDRs were attempting to retrieve data from the incorrect location.
July 18, 2018
Improved
The IVR customer service redirection now uses a Refer flow.
General improvements to autofill field sorting.
New
Added a Single Number Override context menu in the Supergroup and Group table pages.
Improved
Moved up/down arrow click boxes in number fields for easier manipulation.
Minor graphical and caching improvements.
Added additional checks for internal component synchronicity.
Fixed
The
clear-web-cachecommand incorrectly destroyed user sessions.Supergroups could sometimes not be edited after being created.
Group call plan activation was not successful after turning on the Single-Number Override setting.
Using single-number override of a supergroup could have potentially created a race condition when more than one group in that supergroup contained the same number.
A user had to wait the required period (7 days by default) before requesting an additional password reset after an initial reset request. Unlimited reset requests are now allowed and only the most recent reset token will work.
Purging records was not supported by the database.
Using the IVR, there was no reported difference between no option and option 0.
Requesting the status of all groups when there are no groups in that key would cause the IVR to not work properly.
New
Added a global
install-logocommand, which moves a .png file into the appropriate folder and sets SELinux context for use in a branding configuration.
Improved
Authentication now performs a “heartbeat” with each page load. If a user has lost their session at any time, they will be sent back to the login screen. This prevents a user from being able to continue browsing on a cached web context and have all of their API calls fail due to an expired token.
Branding configuration now supports a “label” in addition to all other configuration categories. This will change what appears in the title of the page.
Added some robustness to the API, including default values and object inference.
Fixed
The
clear-web-cachecommand did not clear out cached processed CSS and images.There was an issue causing initial registration of a secondary NIU as a standby database cluster to be unsuccessful.
Privilege separation of statistics viewing caused users to not be able to see any statistics at all.
New
Added a global
clear-web-cachecommand, which takes arguments of the application name to clear the cache of. This wipes out all users’ sessions and any cached data.
Improved
Caching and session variables now check if a users’ session was built on a previous version of the application. If so, it wipes it clean and logs them out.
Session variables now use a database table rather than signed cookies. This is more secure and easier to manage.
Fixed
Clustered installations did not work properly.
Altering the database during installation affected nodes other than the primary NIU.