Re: RFC 4666 M3UA - Reg Request Message

Lincoln,

Well, to begin with, an SG does not lose connectivity to an AS, it loses
connectivity to one or more ASPs.  In the case where an SG loses
connectivity to all ASPs serving an AS, the SG does what it normally
does: the AS moves to state AS-PENDING and a notification is sent to any
ASPs in the ASP-INACTIVE state for the AS (maybe none) and informs
management.  Eventually the SG moves the AS to the AS-INACTIVE state and
takes action with regard to the SS7 network.  Because there is no AS in
the AS-ACTIVE or AS-PENDING state corresponding to messages received
from the SS7 network, the SG performs implementation dependent treatment
toward the SS7 network.

This, according to the RFC, can include sending the messages to a
default ASP (possibly and internal one), rerouting messages to the
alternate STP in an STP pair using C-links if the route toward the
alternate STP is not prohibited, or sending UPU Inaccessible toward the
originating SP (in the case that the SG is an SEP and "owns" the point
code), or sending TFP (if the SG is an STP and the route to the paired
STP is prohibited).

In the non-STP case, sending UPU Inaccessible is appropriate and is
properly interpreted by ISUP at the originating SEP.

--brian

Haresign Lincoln wrote:                       (Mon, 06 Nov 2006 16:45:16)
> Brian,
> 
> So in the case that we loose completely connectivity to an AS, what
> would the SG do?  
> 
> Regards,
> Lincoln
> 

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/