Re: Query regarding reachability STATUS of Signaling Point Code

Rajesh,

Please see comments below:

Rajesh Makhija wrote:                        (Fri, 19 Mar 2010 16:29:08)
> 
> Hello,
>  
> We would like to understand how the STATUS of Signaling Point
> Code (that unique ly identifies an SS7 node) shall be
> interpreted by M3UA at ASP/AS side.
> 
> 
>    Entities Configured:
> 
> 
>    Let us consider an ASP is serving two Application servers,
>    say AS-1 and AS-2.  This ASP is connected (through SCTP
>    association) to an SGP.  This SGP is serving an SG.
> 
> 
>    The routing context of AS1 is X and routing context of AS2
>    is Y.
>  
> A route is configured for an SS7 destination (say with point
> code 101) through this SG.
> 
> 
>    This SS7 node with point code 101 is initially unavailable.
> 
> 
>    Now, a DAVA message (for SS7 point code 101) is sent by SGP
>    to ASP with routing context X (which is the routing context
>    corresponding to AS1)
> 
> 
>    There seem to be two possible interpretations:
> 
> 
>    1.       SS7 node with point code (101) is marked as
>    reachable for both the Application servers, AS1 and AS2.
> 
>    2.       SS7 point code (101) is marked as reachable for
>    AS-1 only (as determined by the RC in the DUNA message) and
>    remains unreachable for AS-2.
> 
> 
>    Which one of the above-mentioned interpretations is
>    correct?

Neither.  M3UA at the ASP simply identifies the MTP/MTP-User
interface (AS) associated with the RC and passes an MTP-RESUME
primitive to the MTP-User.  It is the MTP-User's responsibility
to track the state of remote signalling points.

--brian

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