Re: Multiple SUA SGs, sending for SSP from SGs

Ilie Glib <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <[email protected]>
Brian, Tolga

thank you very much indeed for your answers.

I think it is not possible to have multiple SGs without them playing
the role of STPs.
Therefore "multiple SG as STP scenario" is equivalent to "multiple SGs
scenario".
That is STP is always part of SG in this case and in case of SUA the
SG deals with (owns) capability (alias) pointcodes.

Is my understanding correct?

Does it apply to both SUA and M3UA?

By the way capability (alias) pointcodes is not an ITU-T term, is the
function of mimicking capability (alias) pointcodes an implementation
issue for the SG?

Thank you in advance

Ilie

On 1/11/06, Brian F. G. Bidulock <[email protected]> wrote:
> Tolga,
>
> I disagree. An instance of MTP is identified by a point code and the
> point code resides at the ASPs in the multiple SG as STP scenario.  The
> point code is not local to the MTP stack at the SG in the SS7 sense when
> RK is at PC granularity or above.  This is a necessary situation to properly
> support the multiple SG as STP scenario.
>
> --brian
>
> Tolga Asveren wrote:                            (Tue, 10 Jan 2006 17:35:12)
> > Brian,
> >
> > You also know as much as I do that SCCP (and MTP3 for M3UA) is hosted on
> > SGs, the interface between SG and ASP mimics SCCP/SCCP-User (MTP3/MTP3-User
> > interface for M3UA) interface. It is true that for multiple SG scenario ASPs
> > have a small portion of MTP3 functionality, but this does not mean that MTP3
> > is actually not hosted on SG, e.g. it is still SG generating management
> > messages for SCCP/MTP3.
> >
> >    Tolga
> >
>
> --
> Brian F. G. Bidulock
> [email protected]
> http://www.openss7.org/
>
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/sigtran
>


--
Ilie
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.