2.5 TOBR Enhancement to perform "Operation Code Tag " based routing
TCAP Opcode Based Routing provides additional capability to EAGLE to route the
message based on Operation Code Tag. This routing enables the EAGLE to prevent the
“Global Tag Abuse” security issue. To perform global title translation on ITU messages,
EAGLE considers the following information contained in the TCAP portion of the
message:
- Message Type / Package Type
- Application Context Name
- Operation Code
- Operation Code Tag
For the Operation Code Tag based routing, the key for ITU opcode translations is the ITU opcode, the ITU TCAP Package Type, the Application Context Name (ACN), and the OpCodeTag. The values in ITU OpCode Tag can be "local", "global", "any" and "none". The value "none" in the OpCode Tag indicates that the TOBR is not able to decode the OpCodeTag in the incoming MSU message.
For the Operation Code Tag based routing, TOBR matches the translation based on OpCodeTag
with the OpCodeTag of the incoming MSU. Table 2-1 shows the search order for OpCodeTag Translation.
Table 2-1 OpCodetag Translation Searching Order
| Priority | OpCode Tag | TCAP Package Type | Opcode ( ANSI) | ACN |
|---|---|---|---|---|
| 1 | Exact (value) | Exact (value) | Exact (none or number) | Exact (none or number) |
| 2 | Exact | Exact | Exact | Any |
| 3 | Exact | Exact | Any | Exact |
| 4 | Exact | Exact | Any | Any |
| 5 | Exact | Any | Exact | Exact |
| 6 | Exact | Any | Exact | Any |
| 7 | Exact | Any | Any | Exact |
| 8 | Exact | Any | Any | Any |
| 9 | Any | Exact (value) | Exact (none or number) | Exact (none or number) |
| 10 | Any | Exact | Exact | Any |
| 11 | Any | Exact | Any | Exact |
| 12 | Any | Exact | Any | Any |
| 13 | Any | Any | Exact | Exact |
| 14 | Any | Any | Exact | Any |
| 15 | Any | Any | Any | Exact |
| 16 | Any | Any | Any | Any |
For more information, refer to Database Administration - GTT User's Guide.