
141
Dialogic
®
DSI Signaling Server SGW Mode User Manual Issue 5
Figure 9 demonstrates example relationships between entities in the routing model. Relationships with full
lines indicate that there is an explicit relationship between the entities (that is, one entity selects the other).
Relationships with dotted lines indicate that the relationship is implicit, for example, if data arrives on a
SIGTRAN link over M3UA, it is implicitly coming from the SIGTRAN IP domain and similarly if data arrives on
an SS7 link set, it is implicitly arriving from the MTP domain.
Note: A message arriving from M2PA is considered as arriving from the MTP domain.
This example identifies two incoming routes, IR 1 from SIGTRAN IP and IR 2 from the MTP side. IR 1 and
IR 2 go to the Routing Key Table 1 for routing key analysis. If the analysis fails, or the destination found by
the analysis (Application Server AS1) is out of service, the Signaling Gateway discards messages from IR 1.
The Signaling Gateway however attempts to route messages from IR 2 to Destination 2 only discards those
messages if the SS7 route C7RT 1 is also out of service.
This example identifies two incoming routes, IR 1 from SIGTRAN IP and IR 2 from the MTP side. IR 1 goes to
Routing Key Table 1 for routing key analysis. IR 2 also goes to Routing Key Table 1 for analysis, however, if
analysis fails, or the destination found by analysis (either a MTP or SIGTRAN IP route or Application Server)
is out of service, it attempts to route to Destination 2.
The routing key table has one entry as follows:
• The entry that routes all SS7 messages with DPC 2 and CICs 1 to 128 to Destination 1.
There are two Destinations:
• Destination 1 routes to Application Server 1.
• Destination 2 routes all messages to the MTP side.
Example MML for the routing part of the above configuration is as follows:
Note: The Destinations Point are configured first, followed by the Routing Key Tables, and then finally
the Incoming Routes.
SGDPI:DEST=1,RTPRI=NONE,RAS=1;
SGDPI:DEST=2,RTPRI=MTP;
SGRKI:RKI=1,RKTAB=1,DPC=2,BCIC=1,RANGE=128,NC=1,DEST=1;
SGIRI:IR=1,NC=1,DOMAIN=IP,RKTAB=1;
SGIRI:IR=2,NC=1,DOMAIN=MTP,RKTAB=1,DEST=2;
7.4 Management and Operations
Entities such as boards, SS7 links, SIGTRAN links and Application Servers after configuration are considered
to be in the “blocked” state. The configuration exists in the system for these entities, but these entities are
not considered to be active. To activate an entity, the MNBLI command should be used. To temporally
deactivate an entity, the MNBLE command should be used.
The status of entities such as boards, SS7 links, SIGTRAN links and Application Servers can be examined
using the STxxx set of commands.
Alarms that occur on the Signaling Gateway can be view using the ALLOP and ALLIP commands.
7.5 Default Routing
The Signaling Gateway offers a Default Routing service. This service allows the Signaling Gateway to onward
route MTP Message Signal Units (MSUs) with unknown Destination Point Codes (DPCs). It also provides a
mechanism for Signaling Network Management messages to be generated for unknown Point Codes.
Figure 10 shows a typical system that uses Default Routing. The SPCs with Point Codes 1, 2 and 3 can each
communicate with many Point Codes within the MTP Network not all of which the Dialogic
®
DSI Signaling
Server has been configured to know about. The Signaling Server connects to two STPs that have been
explicitly configured to know about more Point Codes than the Signaling Server.
Kommentare zu diesen Handbüchern