APEX VOICE COMMUNICATIONS ADDS
MULTI-USER INTERFACE TO OMNIVOX® AES
- New Interface Increases Security and Control Through OmniView® OAM&P -
WOODLAND HILLS, CA, January 11, 2006 - APEX Voice Communications, a leading supplier of multi-service platforms for enhanced services and real-time billing solutions to telecommunications carriers, service providers, developers and enterprises worldwide, today announced that it has added a Multi-User Interface to its OmniVox AES multi-service platform for enhanced services solutions. Key features include enhanced account administration, new object control functions, and the greater use of permissions for various account actions.
The new OmniView Operation, Administration, Management and Provisioning (OAM&P) module of OmniVox AES gives systems administrators the ability to create Domains, Groups and Users. For example, Domains are used to partition systems when services are being "sub-leased" to third-parties. Each Domain in return has its own domain administrator that can create User and Group accounts and assign them various permissions and object access capabilities. Groups are used to define a specific set of permissions that can be applied to Users. Also, password storage and verification now uses 160-bit encryption for increased security.
"We have had extremely positive feedback from our customers who have started to implement the new multi-user interface of OmniVox AES," said Elhum Vahdat, executive vice president of APEX Voice Communications. "The new multi-user interface, along with the added security features, continues to keep OmniVox AES at the forefront of multi-service platforms."
One of the functions of the object controls is similar to that of a source control facility. Objects, such as applications, devices, voice prompts/libraries, must now be "checked-out" before they can be modified and "checked-in" to have the modifications saved. While an object is checked-out, others may view the contents of the object, however, they will not be able to make any modifications to it. Additionally, objects are now assigned access rights for particular accounts, which are controlled by permissions. Every account can be assigned permissions which either allow or deny actions such as creating, modifying, reading/writing or deleting of switches, applications, devices, configurations, etc.