Re: Congestion in M3UA/SUA and the use of the SCON
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Haresign, Haresign Lincoln wrote: (Mon, 10 Oct 2005 14:38:13) > Brian, > > When talking about SUA, GTT can be performed in the SG. However, there > is no requirement to modify the called address to PC/SSN. In some > architectures, there is absolutely no need to know the PC/SSN if you are > working strictly with GTs. And in some architectures, this certainly > simplies the provisioning. Where does it say otherwise in any > requirement (SS7 or SIGTRAN)? > > There is no need to perform GTT in an ASP. > > I'm not sure where the disconnect is. I'm quoting from the RFCs. > > The RFC says: > > 1) An ASP can send an SCON to a SG. > > 2) When an ASP talks to an SG, it does not need to know it's point code. > It's not a required parameter in dynamic registration. It's not a > required parameter in the CL messages. An AS does not need to know its point code to receive messages. However, if SUA at th ASP is going to take responsibility for SCCP congestion procedures, it needs to know which SCCP it is signalling congestion for, and the instance of SCCP is identified by the MTP-SAP which includes the point code. This is nicely reflected in the fact that the Affected Point Code is mandatory in the SCON if it is sent from ASP to SG. Sending SCON is optional. If your ASP doesn't know its point code, simply don't send SCON from ASP to SG. --brian -- Brian F. G. Bidulock [email protected] http://www.openss7.org/