In the large enterprise and service provider markets, the Microsoft OCS and Cisco hybrid architecture may face a number of deployment blockers, increasingly so in multi-location, multi-country, multi-vendor situations.
These will be greater still for a service provider supporting multiple enterprise environments or (shared) multi-tenant platforms.
Within such hybrid environments, we see a range of potential service management challenges which VOSS is able to address:
- Dial plan configuration: Pool assignment, default profiles, location profiles, normalization rules, phone usage records, phone usage policies, gateway routes
- Configuration of multiple mediation server/media gateway break-out points; or,
- Centralized integration with IP-PBX architecture and provisioning of gateway routing via IP-PBX elements (and local breakout points)
- Support for call-routing to internal IP-PBX and TDM-PBX extensions (i.e. where there is no E164 number mapping)
- Workflow management of end-users with combinations of OCS and IP/TDM-PBX phones
- Allocation of E164 numbers between OCS and IPPBX and TDM-PBX phones
- Integrated configuration of RCC-controlled desk-phones (both OCS & PBX elements)
- Integrated configuration of voicemail and UM servers (both OCS & PBX elements)
- 2-way synchronization of PBX and active directory telephone directories.
- Configuration of presence settings and (corporate) buddy lists, where multiple presence servers exist (CUPS and OCS)
- Secure, delegated administration of enterprise/location features with mix of phone types, including partitioned access to active directory as well as to PBX elements