Re: FW: RFC 4666 M3UA

Josh,

The situation is no different for SUA.  Just how did you think that there was
a difference?  Under M3UA or SUA (or TUA for that matter), in the "multiple SG
as STP" configuration, where there are AS that can originate messages with the
point code for which a TFC arrives with that point code in the DPC, the SG
needs to perform the procedures of Q.704/13.6, Q.704/13.7 or Q.704/13.8 as
appropriate, which may include running timer T15 for the OPC/DPC (of the TFC)
and generating RCT messages to the OPC (of the TFC) as required as required.

But this is SS7 and outside the scope of the RFCs.

--brian

Tuel, Josh wrote:                               (Wed, 19 Sep 2007 21:48:17)
> 
>    The  placing  of  the  ITP  point  code  in  the OPC of an  RCT is the
>    vendor's implementation.  It is not defined in the RFC how this should
>    work.  It was done this way to make M3UA and SUA work the same in this
>    case  (SUA  would  have  to have the RCT OPC=ITP since the AS does not
>    have MTP3 equivalent).
> 
>    For  M3UA the  ITP's job is to front end these management messages and
>    translate  them to the appropriate ASP/AS management message.  So when
>    the 240-0-0  is congested, for example, the ITP will terminate the TFC
>    and  send a SCON to 1-1-1.  One can argue we should place 1-1-1 in the
>    OPC of the RCT (since we know the DPC of the TFC) and one can argue it
>    should be the ITP OPC (since the ITP is supposed to front end SSNM for
>    SS7 for the ASP).
> 
>    Josh


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