Filter
Top Products
147
Dialogic
®
DSI SS7MD Programmer’s Manual Issue 3
7.7.2 SCCP_SSR – SCCP Sub-System Resource
Synopsis
The SCCP_SSR command supplies the global configuration parameters for the SCCP.
Syntax
SCCP_SSR <ssr_id> RSP <remote_spc> <flags> <pc_mask>
SCCP_SSR <ssr_id> LSS <local_ssn> <module_id> <flags> <protocol>
SCCP_SSR <ssr_id> RSS <remote_spc> <remote_ssn> <flags>
Example
SCCP_SSR 1 RSP 1236 0
SCCP_SSR 2 LSS 0x07 0x0d 1 TCAP
SCCP_SSR 3 RSS 1236 0x67 0
Parameters
The SCCP_SSR command includes the following parameters:
• <ssr_id>
Unique ID for the SSR.
• <remote_spc>
The point code of the remote signaling point, which may be either an STP or an SCP.
Note: For correct operation, <remote_spc> must always have its own RSP entry in addition to any
RSS entries. There must also be an MTP_ROUTE defined for this signaling point.
• <local_ssn>
The local sub-system number as defined by the SCCP protocol.
• <flags>
A 16-bit value, where each bit enables or disables additional features of the RSP, RSS, or LSS. The
meaning for each bit is as defined for the options parameter described in the Configure Sub-System
Resource Request section of the SCCP Programmer’s Manual.
• <module_id>
The module identifier of the user application on the host computer that implements the local sub-system.
This must be in the range 0x0d, 0x1d, 0x2d to 0xfd.
• <remote_ssn>
The remote sub-system number as defined by the SCCP protocol.
• <pc_mask>
A 32-bit value specifying the part of a destination point code that must match the <remote_spc> value
for a SCCP transmit message to be sent down to this destination sub-system. Bits set to 0 indicate that
the corresponding bit position in the transmit message destination point code must match the bit
position of the <remote_spc>, bits set to 1 indicate bit positions in the message destination point code
that do not need to match the <remote_spc> set for this RSP. This allows configuration of default
destination sub-systems (for example, to a gateway SCP).
• <protocol>
Should be set to SCCP, TCAP, MAP, INAP or IS41 according to the layer of the protocol stack to which the
user application interfaces.
Note: There can be at most one LSS for each of the MAP, INAP and IS41 protocols.