Jump to: navigation, search

Custom Applications

This chapter describes how to install and configure your custom built applications to run in a Genesys environment. There are many ways to customize your Genesys environment to meet your business needs. Below are a few examples of how to install and configure your Interaction SDK custom built applications.

Configuring TLS

In 7.6.6, AIL integrates the PSDK Application Template Application Block, which provides TLS support. Before you can use and test your AIL application, you must configure secured ports as detailed in the Deployment Guide.

For further details, you should read Platform SDK Implementation of TLS chapter which give all details about TLS in Platform SDK.

Setting up VoIP Support

To allow your call center to use VoIP technology by creating and configuring a DN on the IPMX (Genesys IP Media eXchange) switch.

  • You must have your Interaction SDK component installed. For detailed information on how to install Interaction SDK components, see Installing and Configuring Interaction SDK Components.
  • To handle VoIP calls, Agent Interaction (Java API) uses H323 (Microsoft NetMeeting) or SIP (Windows Messenger) applications. For a full description of VoIP, see the Genesys IP Media eXchange Reference Guide.


  1. General Tab
  2. Type: ACDPosition
    Number: any

  3. Advanced Tab
  4. Alias and/or Use-Override (must be selected if used): Enter the IP address on which the agent’s VoIP application is launched, preceded by the @ symbol and followed by the /VR option.
    For example: @
    This option allows a Connected mode between IPMX and a VoIP application. For standard use, Genesys recommends setting the agent’s NetMeeting to autoresponse .

    Agents can receive VoIP sessions when logged into an IPMX DN. The connection between VoIP applications and IPMX is established only after the agent accepts the call, and the connection remains on until the agent logs out.

Next Steps

Setting up your SIP Communication Server

To allow your call center to use SIP communication technology. Agent Interaction (Java API) supports SIP Communication Server. For a full description of this server, see the Framework SIP Communication Server Deployment Guide.
You configure endpoints (SIP phones) as DN objects of type Extension in the Genesys Configuration Layer. For DN objects, you must configure the Configuration Manager fields listed in the following subsections.



  1. General Tab
    Type: Extension
    Number: The username part of the endpoint’s Address of Record (AOR). Contains a numeric-only DN number that can be dialed directly from a phone.
    You must not use an @ sign or a domain name when configuring the number.
  2. Annex Tab
    Annex TServer/contact: Contains the contact URI. This field is used to specify the endpoint IP address if this is a fixed address. This object is necessary only for a stand-alone configuration, and only if the endpoint does not register itself in the Communication Server registry.
    The URI format is:
    • sip is an optional prefix.
    • number is the DN number. The current version of SIP Communication Server ignores this value.
    • hostport is a <host>:<port> pair, where <host> is either a dotted IP address or a DNS-resolvable hostname for the endpoint.
    • transport=tcp or transport=udp is used to select the network transport.
    The realm for password authentication is configured globally. There is one realm per Communication Server.

Next Steps

Configuring for your Specific Switch

To configure your specific switch.


  1. For full support of your specific switch, configure the Place that the agent will log into. The Place configuration must not be changed while an agent is logged in.
  2. Check with your switch to determine the kind of DN support you have. Then configure it accordingly. See, Switch-Specific Support Configuration for details.
    In some of the switches, the agent cannot see all the DNs in the Place configuration. In these cases, only one DN is visible, and this DN includes the features of all other DNs.

Next Steps

Running MIL and QIL on the Same JVM

To configure MIL and QIL to run on the same JVM.


    In order to run QIL and MIL on the same JVM with the same application in Configuration Manager, no special configuration is needed, because QIL options are a subset of the MIL options.
    Genesys advises you to use the MIL template and complete it with the applicable QIL options.

Next Steps

Starting MIL in Server Mode

To start MIL in server mode.


  1. Launch startMediaServer.cmd from the installation directory. The Class used to start MIL in server mode (located in the MIL.jar) is com.genesyslab.omsdk.mil.MILBootstrapper.
  2. In the Command window, add to startMediaServer.cmd the following mandatory parameters:
    • host <config server host>
    • port <config server port>
    • app <application name>

    • Command line: startMediaServer -host <config server host> -port <config server port> -app <application name>

  3. You can add non-mandatory parameters for OMSDKConnector initialization:
    • backupHost <backup configuration server host name>
    • backupPort <backup configuration server port>
    • reconnectionPeriod <period between reconnection attempts in milliseconds>
    • reconnectionAttempts <number of reconnection attempts>
  4. You can also add the non-mandatory parameter for MIL initialization: ext <comma-separated list of preloaded extensions (FQN)>.
    To correctly start MIL in server mode, the Java class path should include all the following .jars:
    1. Genesys libraries:
      • Java Config Library (cfglib.jar)
      • Java Common Library (commonLib.jar)
      • Java TKVList library (tkv.jar)
      • Java XKVList library (xkv.jar)
      • Java Management Layer Library (gml.jar)
      • License library used by Java Config Library (license.jar)
    2. Multimedia libraries:
      • ESP Protocol Library Java (_3rd_party_protocol.jar)
      • Interaction Server API Java (_workflow_engine_protocol.jar)
    3. MIL libraries:
      • OMSDK MIL library (mil.jar)
      • om_commons library (om_commons.jar)
      • UCS OMAPI library (omapi.jar)
    4. Java common libraries:
      • commons-lang-2.0.jar
      • concurrent.jar
      • log4j-1.2.8.jar
      • mail.jar
      • .jar files that contain necessary extensions (if any).

Next Steps

Configuring External Service Protocol Request


To define generic blocks in a strategy on which you want to make an External Service Protocol request.



To make requests on Open Media interactions related to your custom media server, you can define generic blocks in your strategy through IRD (Interactive Routing Designer). For further details on Genesys IRD strategies, see the Genesys Multimedia 7.6 User’s Guide. Define the External Service block in a strategy for the Open Media interactions on which you want to make an External Service Protocol (ESP) request. (See External Service Properties Window as a guide to the following instructions.)

  1. Application type: Select ThirdPartyServer.
  2. Application name: Specify the application (server) name. If you want to use load-balancing of ESP requests, the Universal Routing Server has to call ESP server by type, and the server name should not be specified.
  3. Service: Specify the Fully Qualified Class Name (FQCN) of the extension class to be used to handle requests.
  4. Method: Specify the method name to be invoked in the extension class.
  5. Specify the parameters to be put into request parameters attached to ESP requests.
  6. Important
    You can create any key/value pair.


    External Service Properties Window

  7. Default timeout: Specify the timeout for waiting response to ESP request.
  8. Important
    You can choose the default value.
  9. Click OK to save your data.
  10. Important
    In order to invoke ESP requests on MIL server, the link to the MIL application should be added to the Connections tab in the IxnServer application in Configuration Manager.

Next Steps

This page was last edited on January 23, 2014, at 15:12.
blog comments powered by Disqus