Sonexis' next software update, version 12.1 is on its way! After our last major software release of the ConferenceManager2, version 12.0, this new minor update will offer customers a software refresh as well as added features and functionality. All customers currently running ConferenceManager2 v12.0 will be eligible for this release of new software, expected summer 2019! If you are still running an older version of ConferenceManager2, it's never too late to upgrade. Check out the updates below to see what's new!
New Caller Modes
This new feature allows hosts and operators to identify callers who join conference based on the called and calling numbers and joins them in one of the following modes:
- Listen/Talk - This mode allows the caller to both talk and listen throughout the conference.
- Listen only, unlocked - In this mode, the caller is automatically muted when they enter the conference but has the ability to un-mute themselves by using the *2 DTMF command.
- Listen only, locked - This mode automatically enters the caller as a muted participant, only allowing the host or operator the ability to un-mute them.
This new feature is great for hosts and operators hoping to simplify call management. With ANI Look-up Ability to control the names of callers as they appear in conferences on the ConferenceManager2 based on caller ID.
Guest Only Passcode Entry
This change offers yet another layer of security for account owners and their individual conference ID #. Guest Only Passcode Entry allows participants to be joined into the conference with an ID # separate from the account owner or host’s individual Conference ID. This way, each account owner’s Conference ID can remain known only to them.
These modifications have updated the platform security baseline to align with the DoD configuration standards of our JITC-certified version. Following the Security Technical Implementation Guides (STIGs), the system is able to lock down information systems/software that might otherwise be vulnerable to malicious computer attacks. Changes include some of the following:
- Require the use of FIPS-compliant algorithms for encryption, hashing and signing
- Disable legacy protocols vulnerable to attack such as SMB-v1 and TLS 1.0
- Removal of unnecessary roles and services that increase the attack surface of the system
- Prevent access to sensitive system and application resources from non-privileged accounts
- Maintain an audit trail of system activity to troubleshoot service disruptions, analyze compromises and detect attacks