Callflow Post Installation
After installation of Composer, you need to perform some post-installation configuration tasks. Note: If you plan to use IIS as your web server for testing and deployment, you will also need to configure IIS preferences in Composer so that your applications can be auto-deployed to IIS from within the workbench. Composer can work only with IIS installed on the local machine. You can work with both Tomcat and IIS from the same installation of Composer. Also see: Context Services Preferences.
- Select Window > Preferences, then expand Composer and select Tomcat. Starting with 8.1.420.14, Composer supports Tomcat 7. Composer installation adds the role for manager-gui to Tomcat configuration for callflows and workflows. The default username and password for the bundled Tomcat is admin. The username and password for manager-gui is tomcat.
- Provide the same port number that you specified during installation. The default user name and password for the bundled Tomcat is admin.
- To start Tomcat, click the button on the main toolbar.
If you already have Java Composer Projects in the workspace and did not perform the Tomcat configuration earlier, perform the following steps to deploy the project on Tomcat:
- From the Project Explorer, right-click on the Java Composer Project and select Properties.
- Select Tomcat Deployment and click the Deploy button.
Note: This also needs to be done if a Java Composer Project is imported.
- Select Window > Preferences, then expand Composer and select IIS/.NET.
- Provide the IIS website port number where you want to deploy your .NET Composer Project. The IIS Default Website Site port number is 80.
- If you plan to use .NET Composer Project builder to compile the server-side files (.aspx) in your .NET Composer Project, you will need to configure the location of the aspnet_compiler.exe file in the Microsoft .NET Installed Path field.
Note: The typical location of the ASP.NET compiler is:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe.
- Specify the Web Services Enhancement (WSE) path. This must be specified before Composer .NET Projects can work.
If you already have .NET Composer Projects in the workspace and did not perform the IIS configuration earlier, perform the following steps to deploy the project on IIS:
- From the Project Explorer, right-click on the .NET Composer Project and select Properties.
- Select IIS Deployment and click the Deploy button.
Note: This also needs to be done if a .NET Composer Project is imported or renamed as well.
- Select Window > Preferences, then expand Composer and select Debugging.
- Specify the following settings:
- Network Interface. Composer debugging uses this setting to make the socket connection for the Debugger control channel. Select the interface that is applicable to your scenario. The debugging server (GVP or ORS) must be able to access the Tomcat server, bundled as part of Composer, for fetching the Voice or Routing application pages. If you have multiple NIC cards of multiple networks (such as Wireless and LAN) select the interface on which GVP or ORS will communicate to your desktop. In case you are connected over VPN, select the VPN interface (such as PPP if connected via a Windows VPN connection).
- Client Port Range. Enter a port range to be used for connection to ORS for SCXML debugging sessions.
- Select GVP Debugger and specify:
- SIP Phone User Name. This is the user name or phone number of your SIP Phone.
- SIP Phone Hostname/IP . This is the IP address on which your SIP phone is running. It is possible to send the call to a SIP Phone located on some other machine, but it is generally advisable to have the SIP Phone locally for ease of access. If you have multiple NIC cards or interfaces, make sure you specify the same IP address as corresponds to the Network Interface selected above.
- SIP Phone Port. This is the port on which your SIP phone is running.
- Platform IP. This is the IP address of your GVP Server. Note: Composer 8.1 is compatible with GVP 8.1. Operation with GVP 8.0 is not supported.
- Platform Port. Typically, this will be the default port 5060 or the port that you configured for the Resource Manager (RM) or Media Control Platform (MCP) on your GVP Server. You can make direct calls to MCP from the debugger. However, if using pre-provisioned DNIS, then you will need to make test calls to the RM.
- Use Secure Connection. See Debugging TLS Support.
Composer may display a prompt asking if you wish to propagate these settings to an existing launch configurations.
MIME (Multipurpose Internet Mail Extensions) refers to a common method for transmitting non-text files via Internet e-mail. By default the SCXML MIME type is already configured in the Tomcat server bundled with Composer. If you are using the Internet Information Services (IIS) Application Server to deploy ASP.NET projects, add the following MIME type extensions through the IIS Manager of your webserver:
This preference enables diagram validation warnings where prompt audio resources no longer exist in the given file path. If the audio file is no longer present, the diagram block will show a warning icon.
- Select Window > Preferences.
- Select Composer > Composer Diagram.
- Select the option Enable Validation for Prompt Resources. By default the preference is not enabled.
GVP 8.1 provides a debugger interface to allow Composer to make direct calls. By default it is turned off and you will have to enable it to allow GVP to accept calls from the debugger interface.
- Outside of Composer, locate your Media Control Platform (MCP) Application. For example, you can open your MCP Application object in Configuration Manager or in Genesys Administrator for the Configuration environment that is serving the MCP platform.
- Under the vxmli section of the MCP, look for a setting called debug.enabled. By default, it is set to false. Change the value to true and restart your MCP.
If you have a local firewall on your machine, open up the following ports:
- Tomcat port (generally, this is set to port 8080). If you installed Tomcat on a different port, open its corresponding port in the firewall.
- IIS port (generally, this is set to port 80). If you installed IIS on a different port, open its corresponding port in the firewall.
- The UDP port on which your SIP phone is running (by default, this will be either 5060 or 5070). Check your SIP phone settings for the exact port number.
- RTP ports on which your SIP phone will get the audio stream. Check your SIP phone Help file for details on this. Some SIP phones will autoconfigure this during installation.
If you continue to run into problems with the firewall and calls are not coming through successfully, consult your network administrator.