History: ss7box M3UASource of version: 7 (current)!ss7box M3UA
--- !!SNM --- The M3UA plug-in has a separate processing section for signal network management messages. !!ISUP --- The M3UA plug-in has a separate processing section for ISUP messages. !!! DPC/XID to SMG IP address A new section is needed in ss7box.conf to list associations between point-code/CIC pairs and SMG IP-addresses. The M3UA ISUP plug-in will assume responsibility for final routing of ISUP MSUs to an SMG by selecting the appropriate IP address from the point-code/CIC/IP-address table. For ISUP MSUs sent from SMG, the ISUP M3UA will not need to do anything extra to the MTP3 routing section since ss7boost will have already filled in the appropriate values in the M3UA header. !!! Automatic ISUP REL generated for downed SMG Notes on implementing a method for routing traffic away from a downed SMG: If the ss7box, the SS7 link, or the E1 is down, then the SS7 link is down and re-routing occurs without further action necessary. If ss7boost is down, then generating an REL with release cause is not possible - there is no ISUP engine running. One suggestion is to ensure ss7boost is not down so that it can generate the desired REL if it cannot reach the other parts of SMG. We cannot guarantee that ss7boost is not down or that the IP link between ss7box and ss7boost is not down. The problem gets more complex as we look forward to a time when ss7box supports clusters of media gateways that all share the same point code. If one of the m/g in the cluster is lost, the remaining clusters must continue operating without interruption. One solution is for the M3UA plug-in, on the ss7box side that connects to the various ss7boost entities, to take action on behalf of an ss7boost entity that is not responding. The action can be to automatically respond to an IAM inbound to the downed SMG with a REL with cause code 34. This will prevent the call from going through and will not hinder ss7box and other working SMG to continue their normal operations. This approach implies that the M3UA plug-in will finish the job of routing to SMG. The ss7box concept of routing is evolving. !!SCCP --- The M3UA plug-in has a separate processing section for SCCP messages. !!! DPC/XID to IP address A new section is needed in ss7box.conf to list associations between point-code/transaction-id pairs and SMG IP-addresses. The M3UA SCCP plug-in will assume responsibility for final routing of SCCP MSUs to an SMG by selecting the appropriate IP address from the point-code/transaction-ip/IP-address table. For SCCP MSUs sent from SMG, the SCCP M3UA will not need to do anything extra to the MTP3 routing section since ss7boost will have already filled in the appropriate values in the M3UA header. |
Login |