SVI-STP SSME
Squire Technologies - Confidential Document
Page
39
of
57
If a point code is specified in the destination attribute then the SSME will automatically send to this
destination as long as the linkset is available.
The linkset must be a named destination.
It is possible to update the outbound message in the <Route> element using the og.mtp and
og.sccp.cdpn/og.sccp.cgpn attributes as per the MTPMatch element.
5.4
Route Selection
5.4.1
Routing from Routing Criteria
To select a route directly from the routing criteria then this should be set as follows:
Linkset – Only
<
Ep
name
=
"ETSI-ROUTING"
>
<
MTPMatch
dpc
=
"8887"
linkset
=
"STP0-STP-TST-1-ANSI"
/>
</
Ep
>
This would then be routed to linkset “STP0-STP-TST-1-ANSI” with the same incoming and outgoing
OPC and DPC
Destination – Only
<
Ep
name
=
"ETSI-ROUTING"
>
<
MTPMatch
dpc
=
"8887"
destination
=
"Destination-1"
/>
</
Ep
>
This would then be routed to destination “Destination-1” with the DPC set to “Destination-1”.
Destination-1 would need to be configured as SVI-STP resource Destination
This would then need to be configured in the MTP routing to give a linkset for the destination
<
Ep
name
=
"MTP-ROUTING"
>
<
MTPMatch
dpc
=
"Destination-1"
linkset
=
"Linkset-1"
/>
</
Ep
>
DPC – Only
<
Ep
name
=
"ETSI-ROUTING"
>
<
MTPMatch
dpc
=
"8887"
destination
=
"122"
/>
</
Ep
>
This would then be routed to destination “122” with the DPC set to “122”
Or
<
Ep
name
=
"ETSI-ROUTING"
>
<
MTPMatch
dpc
=
"8887"
destination
=
"1-3-3"
pc_format
=
"itu383"
/>
</
Ep
>