Verifying outcalls and application launching with the Application Interface web service

About this task

Use this procedure to verify outcalls and the launching of Avaya Experience Portal with the Application Interface web service.

Note:

If FIPS is enabled on the system where VPAppIntfClient.sh is being launched, you need to specify the following additional command line arguments:

-K <Java Truststore>: The Java truststore file name including the path which contains all the trusted certificates. If the command is running on Primary EPM, the Primary EPM truststore can be specified using the value EPM_TRUSTSTORE.
-O <Java Truststore password>: The password for the Java truststore file. If the command is running on Primary EPM, the Primary EPM truststore password can be specified using the value EPM_TRUSTSTORE_PASS

Before you begin

Ensure that you configure Avaya Experience Portal for the Application Interface test client as described in the Configuring Avaya Experience Portal for the Application Interface test client topic in the Implementing Avaya Experience Portal on multiple servers.

Procedure

Log on to Linux on the Experience Portal server.
If you are an Avaya Services representative, and use the Avaya Enterprise Linux or if the Avaya Service accounts are installed on this server:
- Log in to the local Linux console as sroot.
- Or log in remotely as a non-root user and then change the user to sroot by entering the su - sroot command.
Otherwise, log in to Linux locally as root, or log in remotely as a non-root user and then change the user to root by entering the su - command.
Navigate to the Application Interface test client directory by entering the cd $AVAYA_HOME/Support/OutCallTest/VPAppIntfClient command.

Use the following examples to show calling Application Interface test client using different authentication schemes

Password Authentication
Enter the ./VPAppIntfClient.sh —R 1 —A <application name> —T <number-to-dial> —n <outcall-username> —p <outcall password> command to initiate an outcall and launch the Experience Portal test application, where:
- <application–name> is the same test application name as it was entered on the application page.
- <number-to-dial> is the phone number to place the outcall to.
- <outcall-username> is an Experience Portal user configured from EPM Web interface.
- <outcall password> is the password for <outcall-username> that is configured from the EPM Web interface .
Note:

The user must have the Web Services user role.

Certificate Authentication

Enter the ./VPAppIntfClient.sh —R 1 —A <application name> —T <number-to-dial> -y certificate -k <Java Keystore> —o <Java Keystore password> command to initiate an outcall and launch the Experience Portal test application, where:

<application–name> is the same test application name as it was entered on the application page.
<number-to-dial> is the phone number to place the outcall to.
-y: <certificate> the authentication type is certificate.
-k: <Java Keystore> the Java keystore file name including the path. The Java keystore should contain the User identity certificate including the private key.
-o: <Java Keystore password> the password for the Java keystore file.

Note:

Import the User identity certificate to the EPM and ensure that the certificate is assigned to a user of Certificate type.

The user must have the Web Services user role.

Password and Certificate Authentication

Enter the ./VPAppIntfClient.sh —R 1 —A <application name> —T <number-to-dial> -n <outcall-username> -p <outcall password> -y password+certificate -k <Java Keystore> —o <Java Keystore password> command to initiate an outcall and launch the Experience Portal test application, where:

<application–name> is the same test application name as it was entered on the application page.
<number-to-dial> is the phone number to place the outcall to.
<outcall-username> is an Experience Portaluser configured on the Users page of the EPM web interface..
<outcall password> is the password for <outcall-username> that is configured on the Users page of the EPM web interface..
-y: <password+certificate> the authentication type is password + certificate.
-k: <Java Keystore> the Java keystore file name including the path. The Java keystore should contain the User identity certificate including the private key.
-o: <Java Keystore password> the password for the Java keystore file.

Note:

Import the User identity certificate to the EPM and ensure that the certificate is assigned to the <outcall-username> and the user authentication type is Password and Certificate.

The user must have the Web Services user role.

Verify that the dialed phone number rings.
Answer the phone and verify that the Experience Portal test application is handling the call.

Note:

The application handles the call in the same way as when an actual user calls into the system.
Verify that the Application Interface test client displays:
- A response that shows the result of the LaunchVXML operation.
- The total ports and the unused ports available for outcalls.
Fri Oct 17 15:24:58 PDT 2008: VPAppIntfServiceClient: launchVXML succeeded, SessionID = sys-mpp-2008291222458-2, TotalRes = 24, UnusedH323 = 12, UnusedSIP = 12

Fri Oct 17 15:24:58 PDT 2008: VPAppIntfServiceClient: exiting.

	Note:
	The application handles the call in the same way as when an actual user calls into the system.