Define the following configurations for the MTP 3 layer:
The following illustration shows MTP 3 configurable entities:
General configuration parameters define and control the general operation of the signaling point (SP) implemented by the SS7 software. General configuration parameters include the type of signaling point being constructed (SP or STP), the point code assigned to the signaling point, the values for various SP-level timers, and the maximum number of other configurable elements (SAPs, links, linksets, routes) to control memory allocation. General parameters are configured once at board download time, before the other entities are configured. After the general configuration is performed, only the restart required attribute, timers, and routing masks can be reconfigured using Mtp3SetGenCfg. The board must be downloaded again to change any of the other general configuration parameters.
Service access points (SAPs) define the SS7 applications that use MTP 3. The configurable attributes of SAPs include the:
Protocol variant.
Point code length supported by the application associated with the SAP.
Maximum number of application messages to be queued at each of the four possible message priority levels when flow control between MTP 3 and the application is in effect.
SAPs can be defined any time after the general configuration parameters are defined, up to the maximum number of SAPs allowed by the general configuration parameters definition. After the SAP is defined, all parameters can be changed by calling the SAP configuration function, Mtp3SetNSapCfg.
Links define physical signaling links between the TX board and the adjacent signaling points. The configurable attributes of a link include:
The point code of the adjacent signaling point.
The protocol variant employed on the link.
The point code length.
The maximum packet length.
Various timer values.
Membership in a linkset.
Links can be defined any time after the general configuration parameters are defined, up to the maximum number of links allowed by the general configuration parameters definition. After a link is defined, some of its attributes can be changed by calling the link configuration request, Mtp3SetLinkCfg. Links can also be deleted with the remove link control request.
Linksets are groups of 1 to 32 links that directly connect two signaling points. The configurable attributes of a linkset include:
The point code of the adjacent signaling point.
The number of links to attempt to keep active.
Linksets can be defined any time after the general configuration parameters are defined, up to the maximum number of linksets allowed by the general configuration parameters definition. After a linkset is defined, the target number of active links and the defined combined linksets can be changed by calling the linkset configuration request, Mtp3SetLinkSetCfg. The board must be downloaded again to change any of the other linkset configuration parameters.
Routes specify the destination signaling points (subnetworks or clusters) accessible from the node being configured. Each route is assigned a direction, either up or down. Up routes are used to identify incoming messages to be routed up to the applications. One down route is required for each remote signaling point/network/cluster that is to be accessible from the SP being configured. Down routes route outgoing messages across the appropriate signaling links.
Other configurable attributes of routes include the destination point code and the protocol variant in use at the destination SP/cluster/network. Routes can be defined any time after the general configuration parameters are defined, up to the maximum number of routes allowed by the general configuration parameters definition. After a route is defined, some of its attributes can be changed by calling the route configuration request, Mtp3SetRouteCfg.
