|
| Products > Avaya > Voice Portal > Voice Portal Management System
|
|
| Voice Portal Management System |
|
| The Voice Portal Management System (VPMS) provides a bridging role between the communications infrastructure of the media processing platform and the IT environment that manages that infrastructure. The VPMS is a Web Services-based management platform that runs on Red Hat Linux Enterprise 4.0 Certified Hardware Platforms provided either by the customer or orderable through Avaya as the ECAD X3250 COMMON SRVR RHS Server. |
|
| The Voice Portal Management System provides the following key functions: |
|
| Administers all MPPs for licensing, switch registration, speech resources, application resources, etc. |
|
| Provisions all MPPs with administration data and validates licenses through integration with the WebLM subsystem. |
|
| Actively monitors all MPPs, collecting errors, alarms, logs, call detail records, and session detail records. |
|
| Re-licenses and re-provisions network elements in case of hardware failures, thus providing fail-over and business continuity functions embedded within the solution. |
|
| Delivers SNMP v1,v2,v3 traps to customer-provided Network Management Systems. Also integrates to Avaya Services' INADS system via Secure Access and Control (SAC) VPN-based offerings. |
|
| Generates reports based on collected Call Detail Records (CDR), Session Detail Records (SDR), and Application Detail Records (ADR). Supports access to collected via schema and database access methods. |
|
| Allows multiple Voice Portals to share a common, external, customer-provided database for reporting purposes. |
|
| With Voice Portal 3.0.1 and later (including Voice Portal 4.0), the VPMS may be loaded on to a MPP server. The capacity of this single server is subject to the recommendations produced by the server sizing tool. Note: When installed on a single server, the high-availability feature for failover of media processing capability is not supported. |
|
| Disaster Recover licensing is provided as part of the overall solution by configuring Enterprise Wide Licensing (EWL) for Remote Feature Activation via a secondary WebLM server. Please see the connectivity guide available under sales collateral and tools -> job aids for help in understanding configurations involving the configuration of multiple Voice Portals sharing EWL licenses for Disaster Recovery purposes. |
|
| Note: For instances where the included, automated, high-availability, and manual disaster recovery processes through enterprise-wide licensing do not meet extremely critical customer requirements, reserve disaster recovery licenses are available for purchase. Please contact the ATAC for assistance with ordering these codes. |
|
| Applications can be written in any number of ways based on the standard VoiceXML 2.1 and CCXML 1.0 specifications. Developers can write applications by hand-coding VoiceXML and ECMA script, by using a VoiceXML certified environment to write static VoiceXML, or they can generate dynamic VoiceXML to drive the platform. |
|
| Dialog Designer 4.0 and other VoiceXML 2.1 certified environments are examples of dynamic VoiceXML 2.1 environments. Dialog Designer 4.0 application deployments are an included element of Voice Portal solutions, but do require a zero cost license to operate (SAP code 212570). Note: Voice Portal 4.0 supports applications built by Dialog Designer 3.1 (VoiceXML 2.0) and Dialog Designer 4.0 (VoiceXML 2.1).
|
|
| If a developer wishes to use Dialog Designer to build CCXML applications, Dialog Designer 4.0 is required. Note: CCXML 1.0 is not supported for external applications prior to Voice Portal 4.0.
|
| |
| |
