Re: Re : Query regarding reachability STATUS of Signaling Point Code

Xiangsong,

Thank you for pointing this out.

I was originally wondering if SGW does send DAVA for routing context X only then how should AS/ASP interpret the same.

At this moment I am not sure if this (SGW sending DAVA with routing context X only) can happen in a real life network.

And whether it is possible that a route for an SS7 destination is available for one AS and not available for second AS through the same SGW (given that both AS(s) are in Active state).

I would request others to comment on the following two points:

1. Whether it is possible that a route for an SS7 destination is available for one AS (AS-1) and not available for second AS (AS-2) through the same SGW (given that both AS(s) are in Active state),
When a "common ASP" is serving both AS-1 and AS-2 (given the common ASP is active for both AS-1 and AS-2)

2. Whether it is possible that a route for an SS7 destination is available for one AS (AS-1) and not available for second AS (AS-2) through the same SGW (given that both AS(s) are in Active state),
When "two mutually exclusive" ASP(s), say ASP-1 and ASP-2 are serving AS-1 and AS-2 respectively (given the ASP-1 is active for AS-1 and ASP-2 is active for and AS-2)

Regards

Rajesh

-----Original Message-----
From: Xiangsong Cui [mailto:[email protected]]
Sent: Friday, March 19, 2010 7:32 PM
To: Rajesh Makhija
Cc: [email protected]; Rajat2 Gupta; Amit Jain
Subject: Re :[Sigtran] Query regarding reachability STATUS of Signaling Point Code

> 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)

But why does the SGW send NAVA only for routing context X?

Xiangsong

----- 原邮件 -----
发件人: Rajesh Makhija <[email protected]>
日期: 星期五, 三月 19日, 2010 下午6:59
主题: [Sigtran] Query regarding reachability STATUS of Signaling Point    Code
收件人: "[email protected]" <[email protected]>
抄送: Rajat2 Gupta <[email protected]>, Amit Jain <[email protected]>

> Hello,
>
>
>
> We would like to understand how the STATUS of Signaling Point Code
> (that uniquely 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?
>
> Regards
>
> Rajesh
>
>
>
>
> ________________________________
> "DISCLAIMER: This message is proprietary to Aricent and is
> intended solely for the use of the individual to whom it is
> addressed. It may contain privileged or confidential information
> and should not be circulated or used for any purpose other than
> for what it is intended. If you have received this message in
> error, please notify the originator immediately. If you are not
> the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the
> contents of this message. Aricent accepts no responsibility for
> loss or damage arising from the use of the information transmitted
> by this email including damage from virus."
>

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
_______________________________________________
Sigtran mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sigtran