Beginning with release 10.1, the Java version in the SBC is upgraded to 11.0. After upgrading the SBC to this release, the SSReq application will not operate because the Java 11 environment in the client system/desktop does not include "javaws", which is required to run SSReq on the client system.
In this section:
This section details SSReq operating procedures.
Make sure you have provisioned the PSX for any functionality that you want to test using SSReq.
Use Java 8 or above in your system to work with the enhanced SSREQ GUI in EMA 6.0 onward. To avoid any problem related to execution of Java programs in your system, add your SBC IP Address to the list of trusted sites in the Java Control Panel.
To launch SSREQ application from SBC EMA, TLSv1.2 should be enabled in the Java Control Panel settings.
Execute the following steps to enable TLSv1.2:
On your computer, navigate to Start > Windows System > Control Panel. The Control Panel window is displayed.
Click Java or Java (32-bit). The Java Control Panel is displayed.
Select Use TLS 1.2 under Advanced Security Settings.
The following is a summary of the steps for using SSReq. These steps are explained in detail in the following pages.
The SSReq applet and server are automatically installed and enabled during the SBC software installation or update process.
Follow these steps to create and send a request.
Login to EMA, and navigate to Troubleshoot > Policy Analysis - SSREQ, and from Policy Analysis window click Launch SSREQ.
Create the request using the default file (recommended):
To create a Request using a previously saved file:
1. Select File | Open from the menu bar.
2. Enter the path/file name in the File name box or use the Browse window to locate the file and click Open.
Called Number (this is not mandatory for all scenarios. If it is mandatory and left blank, you will be prompted.
If you want to send one or more trigger requests following the policy request, select the
first trigger request from the navigation panel.
Populate the trigger request fields in the details panel as required.
For trigger request field descriptions, refer to Trigger Request Fields.
Repeat steps a. through c. for each trigger request desired, up to 5.
Configure the server attributes (if required).
The server attributes must be configured before you can run a simulated policy request. If they have been previously configured and the target PSX is the same, you do not need to re- configure them.
Select Configure | Server from the menu bar. The Configure Server Attributes dialog box appears.
Enter values in the fields as required. The fields are defined below.
Click the Accept button to accept the settings.
Save the request (Optional, if you want to save the request without the response).
Submit the request.
Click Submit to send the request to the SBC.
View the status to confirm successful operation. Refer to Status Display.
View the response. Refer to Viewing a Response.
View the call trace.
The call trace panel displays call trace information for the specific simulated call. Call tracing is enabled by default. You can disable it in the CallTrace field of the policy request. Each time a new call trace is received, the old trace is overwritten.
Call Trace information from the panel is saved in the same file as the policy request and response using the File, Save or Save As menu. You can copy and paste the contents of the call trace pane into another application (such as a word processing application) to create a log file for future reference, share the file, to find keywords, and for troubleshooting. Call trace information is not saved with the policy request and response information.
Save the SSReq file (Optional).
If you modified an existing file or created a new one, you may save it using the Save or Save As menu option. If you modify the default file and want to save it, you must save it using a different name. Ribbon recommends that you save the request for future reference. The server configuration is saved as well. If you save the file after the policy response has been received, the response is saved in the same file.