GVP is composed of the following software components:

 
Voice Portal Manager (VPM) or Element Management Provisioning System (EMPS) - Provides centralized configuration of VCS/IPCS and application configuration. It is a web based interface accessible via Internet Explorer. The VPM/EMPS configuration enables the VCS/IPCS to correctly identify the desired voice application using the DNIS of the incoming call. The primary voice application configuration features of the VPM/EMPS allow authorized administrators to:

• Add, modify, and delete voice applications
• Configure the voice application URL
• Assign specific external telephone numbers to a voice application
• Enable ASR capture (when ASR is enabled)
• Configure a fail over voice application URL upon failure of the primary URL and configure failover transfer numbers.

Genesys Studio - Genesys Studio is a Windows-based GUI tool that can be used to build and test voice applications using a “drag and drop” paradigm.

Voice Application Reporter (VAR) - A browser-based reporting program that runs on a separate server, and provides reporting on both JSP and ASP applications. Studio applications store call information on a web server, and VAR can report on call statistics by application summarizing calls by time of day, application, and outcome.

Voice Communication Server (VCS) - Handles calls through TDM using Dialogic telephony boards. The VCS parses, interprets and executes tags contained in VoiceXML documents, as well as terminates and processes voice calls. The VCS integrates with text-to-speech (TTS) and automatic speech recognition (ASR) through MRCP standard.

Internet Protocol Communication Server (IPCS) - Handles calls through Voice Over IP (VoIP). The IPCS parses, interprets and executes tags contained in VoiceXML documents, as well communicates with Media Gateways. Like the VCS, IPCS also integrates with text-to-speech (TTS) and automatic speech recognition (ASR) through MRCP standard.

IP Call Manager (IPCM) - Consists of a set of components that coordinates and assigns the resources needed to process a VoIP call using Session Initialization Protocol (SIP). Includes SIP/H.323 Session Manager and Resource Manager.

Resource Manager - Maintains resource states for IPCS and Media Gateway resources. The Resource Manager maintains dynamic status of each resource whether it is in use or available. The Resource Manager can perform load balancing of the IPCS resources using a round-robin algorithm. It can also select the IPCS resource based on specific feature requirements. Resource Manager checks the health of each resource periodically and marks the resource as healthy/not healthy.

SIP Session Manager - Acts as a SIP Proxy to relay SIP messages between a Media Gateway or Signaling Gateway and IPCS. When a new call arrives at the SIP Session Manager, it fetches the application profile from the VPM based on the dialed number or URI. With the help of the Resource Manager, the SIP Session Manager routes the call to an IPCS based on the application profile requirement. When the call is disconnected, it informs the Resource Manager to free up the IPCS resource.

H.323 Session Manager - Acts as an H.323 Proxy. It processes H.323 messages received from Media Gateway or Signaling Gateway, and forwards equivalent SIP messages to IP Communication Server. When a new call arrives at the H.323 Session Manager, the H.323 Session Manager, with the help of the Resource Manager routes the call to an IPCS, based on the application profile requirement. When the call is disconnected, it informs the Resource Manager to free up the IPCS resource.

Web Server – A customer-provided server where the VoiceXML (2.0 or 2.1) application resides. Any HTTP 1.1 compliant web server can be used. When an inbound call arrives the DNIS is mapped to a URL, as provisioned in the VPM/EMPS and the VoiceXML application is retrieved from the web server.

<< Prev - Next >>