Hi there,
While trying to add a "route" dynamically after a normal boot sequence performed by "s7-mgt", we figured out that it's required to "deactivate" and then "activate" all the links in all the linksets involved in that regarding "route", in order to make that route functional. In other words, just sending the message "MTP_MSG_CNF_ROUTE" with it's parameters is not sufficient and the regarding links have to get "MTP_MSG_DEACT_SL" and then "MTP_MSG_ACT_SL".
The same thing is true for adding or deleting a linkset, i.e., for deleting a linkset, all the links in the regarding linkset have to be deactivated which is of course reasonable but things get a bit messy for adding a linkset:
1. All the links in that linkset must be deleted
2. All the routes in that linkset must be deleted
3. The linkset itself must be added
4. All the routes must be added
5. All the links must be added and activated
Does it really have to be in this way or we're just trapped in a wrong scenario?
Best Regards,
Leila
Hi When you add a new route to a remote destination, you also need to inform level 4 of this change. Here is an extract from the MTP3 manual. MTP_MSG_UPDATE_L4 – Update Level 4 Request MTP_MSG_UPDATE_L4 (0x731f ) This message is sent to the MTP3 module to request that all user parts are notified of the current route status for the given destination using the normal MTP PAUSE, MTP RESUME and MTP STATUS primitives. The message is intended for use after new routes have been configured or following additional user part configuration on a live system (for example, the addition of a new ISUP circuit group). It allows the user to ensure that the user part is updated with the current accessibility of the destination. Can you provide more information on what you are trying to achieve and post your configurations? Ukernie
Hi
When you add a new route to a remote destination, you also need to inform level 4 of this change.
Here is an extract from the MTP3 manual.
MTP_MSG_UPDATE_L4 – Update Level 4 Request
MTP_MSG_UPDATE_L4 (0x731f )
This message is sent to the MTP3 module to request that all user parts are notified of the current route status for the given destination using the normal MTP PAUSE, MTP RESUME and MTP STATUS primitives. The message is intended for use after new routes have been configured or following additional user part configuration on a live system (for example, the addition of a new ISUP circuit group). It allows the user to ensure that the user part is updated with the current accessibility of the destination.
Can you provide more information on what you are trying to achieve and post your configurations?
Ukernie
Dear Ukernie,
Thanks for your reply.
We tried out the "MTP_MSG_UPDATE_L4" message after adding a route, and we got the message
SCP_MSG_MAINT_IND (0x0761) with Maintenance event code 3 (SCPEV_RTF_NET_FAIL) from SCCP
S7L:I0000 SCCP Maintenance event : SCPEV_RTF_NET_FAIL
Of course, if we deactivate and then active all the regarding links, the route actually will get into operation.
This is our config.txt. We have a remote pointcode 120 to which we have a route, after boot sequence, while we are exchanging sms between the local PC(23) and the remote PC(120), we delete this route. The SMS stream wil be interrupted. Then we add the route again, and send the "MTP_MSG_UPDATE_L4", but the sms stream won't flow again unlesss we deactivate and activate all the regarding links.
SS7_BOARD 0 SS7HDE 0x0043 ss7.dc4 MTP
LIU_CONFIG 0 1 5 1 1 1LIU_CONFIG 0 2 5 1 1 1LIU_CONFIG 0 3 5 1 1 1
MTP_CONFIG 0 0 0x00000000
MTP_LINKSET 1 120 8 0x0000 23 0x08
* Define signaling links:* MTP_LINK <link_id> <linkset_id> <link_ref> <slc> <board_id> <blink>* <stream> <timeslot> <flags> MTP_LINK 4 1 0 0 0 0-2 1 1 0x0006MTP_LINK 5 1 1 1 0 0-3 1 2 0x0006MTP_LINK 6 1 2 2 0 0-4 1 3 0x0006MTP_LINK 7 1 3 3 0 0-5 1 4 0x0006MTP_LINK 8 1 4 4 0 1-2 2 1 0x0006MTP_LINK 9 1 5 5 0 1-3 2 2 0x0006MTP_LINK 10 1 6 6 0 1-4 2 3 0x0006MTP_LINK 11 1 7 7 0 1-5 2 4 0x0006
* Define a route for each remote signaling point:* MTP_ROUTE <dpc> <linkset_id> <user_part_mask>
MTP_ROUTE 120 1 0x0008
* SCCP Parameters:* SCCP_CONFIG <local_spc> <ssf> <options> [<send_uis>]SCCP_CONFIG 23 0x8 0x0103 1 * the last 1 added by LMA to force SCCP * to automatically activate local SSN*
* Define Local Sub-Systems:* SCCP_SSR <ssr_id> LSS <local_ssn> <module_id> <flags> <protocol>SCCP_SSR 2 LSS 0x08 0x2d 0 MAP** Define Remote Sub-Systems:* SCCP_SSR <ssr_id> RSS <remote_spc> <remote_ssn> <flags>SCCP_SSR 4 RSP 120 0 0x0000SCCP_SSR 5 RSS 120 0x08 0
* TCAP Parameters:* TCAP_CONFIG <base_ogdlg_id> <nog_dialogues> <base_icdlg_id>* <nic_dialogues> <options> <dlg_hunt> [<addr_format>]TCAP_CONFIG 0x0 8192 0x8000 8192 0x0000 2 0
* MAP_CONFIG <options>MAP_CONFIG 0x0
Thanks for your care,