RE: Congestion in M3UA/SUA and the use of the SCON

Brian,

Perhaps you were not aware, but additional GTT can also take place at an
endpoint.  Many STPs will do GTT and they can allow further GTT to take
place at the final destination (the signalling end point).  In this
case, it will arrive at an SG with a GTT in the called and calling
address.  The SG is not required to (and probably shouldn't) convert the
called address to a PC/SSN.  So a CLDT may arrive at the ASP with JUST a
GT in the called address.  

And you may have designed your architecture so the ASPs have no need to
know their point code (a much simpler configuration).  This is nothing
NEW or outside the spec.

Regards,
Lincoln 

-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]] 
Sent: Monday, October 10, 2005 1:26 PM
To: Haresign Lincoln
Cc: Tolga Asveren; [email protected]
Subject: Re: [Sigtran] Congestion in M3UA/SUA and the use of the SCON

Haresign,

Haresign Lincoln wrote:
(Mon, 10 Oct 2005 09:02:26)
> Brian,
> 
> If I'm reading the SUA RFC correctly (section 3.10.2), there is no 
> requirement to put the DPC in the address when using GT.  There are a 
> variety of other scenarios also where no PC is required.

You will not see a requirement for the protocol to be useful either.

To be useful for SS7 SCCP, final GTT must be performed before a message
reaches its endpoint.  SUA permits relay nodes, that either have final
GTT performed ahead of them (MTP3 Relay) or perform GTT themselves (SCCP
Relay).  This is how SS7 SCCP works.  Were you not aware?

SUA is used to transparently transport SS7 SCCP, not to invent a brand
new protocol, addressing scheme, network manangement, or configuration.

--brian

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