Skip to end of metadata
Go to start of metadata


When you submit a policy request, the status is reported in the status display panel at the bottom of the screen. See the section "Main Window" on page 1-3 for the location of the status display panel.

SuccessfulRequest

A successful request is indicated by the following lines in the status display panel:
SSREQ Client sent Request Sent Register Request to PSX Registration for <gateway> succeeded
Received port <port no.> for sending requests
Sent Policy Request to PSX
SSREQ Client received Policy Response Script returned <script name> Routes returned <no. of routes>
SSREQ Client received Call Trace
Sent Trigger Request to PSX
SSREQ Client received Trigger Response <trigger response no.> Script returned <script name>
Routes returned <no. of routes> SSREQ Client received Call Trace
Sent Download Request to PSX
Script returned <script name> Sent Unregister Request to PSX
The script and routes returned information also appears if there is no script or if there are no routes configured. The information indicates 0.
The routes folder under policy/trigger response appears when the number of routes returned is more than zero. The routes are indexed by trunk group and gateway. By expanding the routes folder, per-route fields can be viewed.

UnsuccessfulRequest

A request that does not result in a response will be indicated by one of the following lines in the status display:
Error: SSREQ Server not responding
Error: Unknown PSX Hostname or IP Address <hostname/IP Address> Error: Unable to connect to TCP socket at <server>:<port>
Error: Unable to read message from TCP socket connected to
<server>:<port>
Error: Unable to send message over UDP to <server>:<port> Error: Registration for <gateway> failed


Error: Registration attempt from unknown gateway <gateway> Error: Failed decoding the Request
Error: SSREQ Server and Client version incompatible - Server: <X> Client: <Y>
Error: Invalid Port Number - <port number> Error: Invalid Timeout - <timeout>
For details on these status messages, refer to Ta ble 1 8, "Common Problems and Error Messages Generated by SSREQ".

  • No labels