Revision as of 23:33, November 11, 2014 by Sschlich (talk | contribs) (Procedure: Integrating Application Objects with Resource Manager)
Jump to: navigation, search

Configuring the GVP Components

Perform these advanced configuration procedures after GVP installation and basic configuration.

Integrating Application Objects

After the Media Control Platform and Call Control Platform Application objects are created and the components are installed, they are integrated with the Resource Manager which acts as a proxy server. SIP devices and VoiceXML or CCXML applications can then make use of media-centric services through the proxy, without having to know the actual location of these resources.

This procedure is optional and required only if you want the Resource Manager to act as a proxy server for outbound requests. To integrate these Application objects with the Resource Manager, you configure the Session Initiation Protocol (SIP) settings.

This procedure describes how to integrate Application objects with the Resource Manager by configuring SIP and secure SIP options.

Procedure: Integrating Application Objects with Resource Manager

Integrate an Application object with Resource Manager by configuring the Application parameters.

  1. verify that all GVP components are installed. See Procedure: Using the Deployment Wizard to Install GVP.
  2. Log in to Genesys Administrator.
  3. On the Provisioning tab, select Environment > Applications.
  4. Click the Application object that you want to configure for example, the Media Control Platform or Call Control Platform Application.
    The Configuration tab appears.
  5. Click the Options tab, and use the View drop-down list to select Show options in groups...
  6. In the sip section, find the routeset option.
  7. In the Value field, type the following:
    • sip:<IP_RM>:<SIPPort_RM>;lr to integrate the Media Control Platform with Resource Manager.
    • sip:<IP_RM>:<SIPPort_RM>:lr to integrate the Call Control Platform with Resource Manager. ...where IP_RM is the IP address of the Resource Manager, and SIPPort_RM is the SIP port of the Resource Manager typically, 5060.
      Tip
      You must include the angle brackets in the Value field in the sip.routeset and sip.securerouteset parameters.
  8. In the Value field of the securerouteset option, type the following:
    • sip:<IP_RM>:<SIPSecurePort_RM>;lr to integrate the Media Control Platform with Resources Manager.
    • sip:<IP_RM>:<SIPSecurePort_RM> to integrate the Call Control Platform with Resource Manager.
      In this case, IP_RM is the IP address of the Resource Manager, and SIPSecurePort_RM is the SIP secure port of the Resource Manager typically, 5061.
      Tip
      Although the GVP components support secure SIP capabilities, the external SIP Server does not.
  9. To use the Call Recording Solution through third-party recording servers: In the vrmrecorder section, configure the following options (pointing to the Resource Manager s IP address and SIP port, as shown in Steps 6 and 7):
    • sip.routeset
    • sip.securerouteset
  10. Save the configuration.
  11. Create the connections to the Message Server. See Procedure: Creating a Connection to a Server.

Creating a Connection to a Server

Use the procedure in this section to create connections to:

  • The Message Server—Create a connection in the Media Control Platform, Call Control Platform, Resource Manager, Supplementary Services Gateway, CTI Connector, PSTN Connector, MRCP Proxy, Reporting Server and Policy Server Applications to ensure that component log information reaches the Log database and can be viewed in the Solution Control Interface (SCI).
  • The Reporting Server—Create a connection in the Media Control Platform, Call Control Platform, Resource Manager, PSTN Connector, CTI Connector, Supplementary Services Gateway, and MRCP Proxy Applications to ensure that these components detect the Reporting Server to which they are sending reporting data. Genesys Administrator also requires a connection to Reporting Server to monitor GVP components.
  • SIP Server—Create a connection in the Resource Manager, Supplementary Services Gateway, and PSTN Connector Applications to manage the initiation of outbound calls.
  • MRCP Proxy—Create a connection in the Media Control Platform Application if you are planning to use the proxy to manage MRCPv1 RTSP traffic within the GVP deployment.
  • MRCP Server—Create a connection in the MRCP Proxy Application if you are planning to use the proxy to manage MRCPv1 RTSP traffic within the GVP deployment (in the Media Control Platform Application if you are not deploying the MRCP Proxy).
  • Cisco T-server—Create a connection in the UCM Connector Application to ensure the tenant DBID of the Cisco T-Server is included in Request URI in any SIP INVITE messages sent to the UCM Connector.
  • The SNMP Master Agent—Create a connection in the Media Control Platform, Call Control Platform, Resource Manager, Supplementary Services Gateway, CTI Connector, PSTN Connector, MRCP Proxy, and Reporting Server Applications if you want to capture alarm and trap information.

Procedure: Creating a Connection to a Server

[+] Purpose


[+] Prerequisites


[+] Steps


[+] Next

Provisioning the Speech Resources

The Media Resource Control Protocol (MRCP) speech resources are controlled by the Call Manager Application Program Interface (CMAPI), which opens and closes sessions, and provides the speech recognition and speech synthesis commands that the MRCP Server uses to carry out speech requests.

If the MRCP Proxy is deployed, the configurations in this procedure vary slightly. Therefore, the configurations are described with and without the MRCP Proxy. If you have installed the MRCP Proxy, see also Provisioning the MRCP Proxy on page 250.

Tip
The procedures in this section are required only if you are using Automatic Speech Recognition (ASR) and Text-to-Speech (TTS) speech resources, and have an MRCP Server or MRCP Proxy in your deployment.

This section contains two procedures that create the Speech Resource Applications and assign the MRCP Server or MRCP Proxy to the Media Control Platform.

Procedure: Provisioning Speech Resource Application Objects

[+] Purpose


[+] Summary


[+] Prerequisites


[+] Steps


[+] Next


Procedure: Assigning the MRCP Server to the Media Control Platform

[+] Purpose


[+] Summary


[+] Prerequisites


[+] Steps


[+] Next

Provisioning the MRCP Proxy

The MRCP Proxy is an optional component, but must be deployed if ASR and TTS usage reporting is required. You can deploy the MRCP Proxy in stand-alone or warm active standby HA mode. The procedures in this section describe the steps for each configuration.

Tip
By design, the MRCP Proxy supports only the NUANCE speech resource.

Procedure: Configuring the MRCP Proxy

[+] Purpose


[+] Prerequisites


[+] Steps


Procedure: Configuring the MRCP Proxy for HA

[+] Summary


[+] Purpose


[+] Prerequisites


[+] Steps


Procedure: Adding a Speech Server as Primary or Backup

[+] Purpose


[+] Steps


Comments or questions about this documentation? Contact us for support!