SVI-STP SSME
Squire Technologies - Confidential Document
Page
16
of
57
</
Match
>
In this case the OPC and DPC are not changed if DPC matches but the OPC fails to match
Example – match incoming DPC 9987 translate to DPC 1234, and if OPC matches “1234” change
to “2345” or if OPC matches “1235” change to “3456” otherwise leave the OPC is translated to
“999”
<
Match
ic.mtp.dpc
=
"9987"
og.mtp.dpc
=
"1234"
og.mtp.opc
=
"999"
/>
<
Match
ic.mtp.dpc
=
"1234"
og.mtp.opc
=
"2345"
/>
<
Match
ic.mtp.opc
=
"1235"
og.mtp.opc
=
"3456"
/>
</
Match
>
4.2.2
<MTPMatch>
The <MTPMatch> Element references all its attributes by the following
Attribute Type
Incoming
Outgoing
MTP
ic.mtp.<attr>
<attr>
og.mtp.<attr>
SCCP
ic.sccp.<attr>
og.sccp.<attr>
TCAP
tcap.operationCode
MAP
map.routing_expr
Examples
Incoming MTP DPC
dpc
Incoming SCCP Called Party Digits
ic.sccp.cdpn.digits
Outbound MTP OPC
og.mtp.opc
Outbound SCCP Calling Party Nature of Address
og.sccp.cgpa.noa
4.2.2.1
Matching
Example – match incoming DPC 9987
<MTP
Match
dpc
=
"9987"
/>
4.2.2.2
Translations
Example – match incoming DPC 9987 translate to DPC 1234
<
Match
dpc
=
"9987"
og.mtp.dpc
=
"1234"
/>