Using SSReq

This section details SSReq operating procedures.

Prerequisite

Make sure you have provisioned the PSX for any functionality that you want to test using SSReq.

Summary

The following is a summary of the steps for using SSReq. These steps are explained in detail in the following pages.

1. Launch SSReq.
2. Create a request.
3. Configure the server attributes (if changes required).
4. Save the request (optional, if you want to save the request without the response).
5. Submit the request.
6. View the status to confirm successful operation.
7. View the response.
8. View the call trace.
9. Save the request (optional, if you want to save the request with the response).

Steps 

Follow these steps to create and send a request. 

1. Login to EMA, and navigate to Troubleshoot > Policy Analysis - SSREQ, and from Policy Analysis window click Launch SSREQ.

   GUI example

    

    

   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.

    

   1. Select File | New from the menu bar. The request fields are populated with default values. 
   2. Modify the request fields as required.
      
      If a field does not have a Present check box, then it is mandatory and must be populated. For optional fields, select the Present box to have the field sent in the request.
      
      The following policy request fields are mandatory and must be populated with values or have an option selected:
      
      • Gateway
      • Source Trunk Group

      • Called Number (this is not mandatory for all scenarios. If it is mandatory and left blank, you will be prompted.

      
      For policy request field descriptions, refer to Policy Request Fields.

   3. If you want to send one or more trigger requests following the policy request, select the

      first trigger request from the navigation panel.

   4. Populate the trigger request fields in the details panel as required.
      For trigger request field descriptions, refer to Trigger Request Fields.

   5. Repeat steps a. through c. for each trigger request desired, up to 5.

2. 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.

   1. 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.

      Configure Server Attributes Values

      Field	Description
      PSX Hostname or IP Address	The PSX hostname or IP address of which to test the configuration. If the hostname is not resolved to the IP address, use the IP address instead or add an entry to the hosts file under the System32\Drivers\etc directory. NOTE:  An IPv4 address or an IPv6 address can be used.
      Port Number	The port number at which the SSReq server is listening for the SSReq request. The default port is 3090 for UDP or 3091 for TCP.
      Timeout (seconds)	Number of seconds that the SSReq client will wait for a response from the specified server. The default is 5 seconds.
      Transport	The transport protocol used to communicate with SSReq Server, either UDP or TCP can be used. The default is UDP.

   2. Click the Accept button to accept the settings.

3. Save the request (Optional, if you want to save the request without the response).

4. Submit the request.
   Click Submit to send the request to the SBC.

5. View the status to confirm successful operation. Refer to Status Display.

6. View the response. Refer to Viewing a Response.

7. 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.

8. 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. Sonus 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.