Welltech SPCI2S Intel NetStructure SS7 Boards - Manual (Page 46)

SS7 Programmer’s Manual for SPCI2, SPCI4 and CPM8 Issue 2 Page 46
5.2.4 MTP Route Configuration Request
Synopsis:
Message sent to MTP3 to add a route to the MTP routing table.
Message Format:
MESSAGE HEADER
FIELD NAME MEANING
type MTP_MSG_CNF_ROUTE (0x7312)
id 0
src Sending module_id
dst MTP_TASK_ID
rsp_req
used to request a confirmation
hclass 0
status 0
err_info 0
len 32
PARAMETER AREA
OFFSET SIZE NAME
0 4 dpc - Destination point code.
4 1 norm_ls - linkset_id of normal link set.
5 1 second_ls - linkset_id of optional link set.
6
2 Reserved for future use, must be set to zero.
8 2 flags - run time options (see below)
10 2 up_enable - User part enable mask
12 20 Reserved for future use, must be set to zero.
Description:
This message is used by the application to add routes to the MTP routing table.
Each route consists of a destination point code and the linkset_id of one or two
link sets over which traffic to the destination should be routed. When two link
sets are supplied the user can elect to load share traffic or to treat the link sets
as a primary link set and a secondary link set.
When the board is configured (using the Board Configure Request) the routing
table is (by default) initialised so that the adjacent signalling point is the only
accessible destination for the link set. If this is the only destination point code
required then there is no need to use this message.
If it is necessary to provide routing over more than a single link set to a
destination then bit 9 in the flags field of the Board Configure Request should
be set to one and the user should send in MTP_MSG_CNF_ROUTE messages
for each destination (including all adjacent signalling points)