SVI-STP SSME
Squire Technologies - Confidential Document
Page
43
of
57
6
API Server
6.1
Overview
The STP SSME is capable of routing messages to an external API for examination and routing decision
based on the XML configuration. (See section 9 for details of the Python SDK)
The attribute
apiserver
in the <route> element will inform the STP to route the message internally to
an API server function. The API server is connected to the STP via TCP and is documented in the
relevant API user guides.
In the <linkset> element the
apiserver
attribute is used to inform the STP SSME engine that the
message was received from an external application.
The API server name must match a API resource configured in the STP main configuration (if not
configured then the configuration will not accepted by the SVI-STP)
For Example
The configuration of this could be that based on the SCCP called party a message received from STP 1
could be routed to either:
API Server 1
API Server 2
STP 2
If a message is routed to API Server 1 then this application could either change some of the incoming
parameters for example the SCCP Called Party Address and then resubmit to the SVI-STP for re-
routing.
The following XML example works on the following method:
Messages are received from Linkset LS-ETSI-OPC-8000-DPC-7100
o
If the incoming message is a MAP operation “Send Routing Info” then forward the
message to the API server.