RE: Multiple SUA SGs, sending for SSP from SGs

Brian,

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:[email protected]]
> Sent: Tuesday, January 10, 2006 7:56 PM
> To: Tolga Asveren
> Cc: [email protected]
> Subject: Re: [Sigtran] Multiple SUA SGs, sending for SSP from SGs
>
>
> 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.
[TOLGA]Even for PC granularity RKs, it is SG which controls/creates the
unique view of the signaling enitity to the network, so one has to have
necessary MTP3 procedures to support that.

BTW, I wouldn't call hosting MTP3 logic in SG as "a PC in MTP3 stack in SG",
it is just providing necessary procedures to have the unique view of the
signaling enitity and generating corresponding network messages -and it is
the multiple clones of the same unique view on different SGs, which are not
synchronized, which may create issues for multiple-SG scenarios-.
>
> --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/
>