Note

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.


The SoftSwitch Request (SSReq) tool is a simulated call tracing tool used to verify the provisioning and routes selected by simulating requests (policy, trigger, download, DIAMETER, etc.). SSReq provides the ability to specify all of the parameters in a request, and display the response received from the SBC and the call trace. The simulated call is handled in the same manner as any live call.

Triggers, such as an Authcode validation service or toll-free number translation service, are used to request a service from the SBC allowing for the emulation of two-stage calls. Download requests are used to retrieve the script data from the SBC.

Requests and responses can be saved in files for future use.

A configurable ACL Rule allows SSReq to receive packets on ports 3090 and 3091.

  • Port 3090 is used by SSReq Server to receive XML requests over UDP from a SSReq Client.
  • Port 3091 is used by SSReq Server to receive XML requests over TCP from a SSReq Client.

The SSReq applet is launched in a separate browser window, and prompts the user to select the SBC mode of operation:

  • ERE – If ERE is used for routing, limited SSReq functionality.
  • PSX – If external PSX is used for routing, full SSReq functionality is available.

You cannot launch the SSReq tool from EMA for use with a stand-alone PSX.

Prior to launching the SSREQ application, refer to the perquisites mentioned in Using SSReq page.

On SBC main screen, go to Troubleshooting > Troubleshooting Tools >  Policy Analysis - SSREQ.

Figure 1: Troubleshooting - Policy Analysis - SSREQ

For more information, refer to Using the SSReq Tool.

  • No labels