Re: M3UA notify message

Tolga,

I prefer to read the RFC:

   In the example above, each signalling process (SGP, ASP or IPSP) is
   the end point to more than one SCTP association, leading to more than
   one other signalling processes.  To support this, a signalling
   process must be able to support distribution of M3UA messages to many
   simultaneous active associations.  This message distribution function
   is based on the status of provisioned Routing Keys, the status of the
   signalling routes to signalling points in the SS7 network, and the
   redundancy model (active-standby, load sharing, broadcast, n+k) of
   the remote signalling processes.

   For carrier grade networks, the failure or isolation of a particular
   signalling process should not cause stable calls or transactions to
   be lost.  This implies that signalling processes need, in some cases,
   to share the call/transaction state or be able to pass the call state
   information between each other.  In the case of ASPs performing call
   processing, coordination may also be required with the related Media
   Gateway to transfer the MGC control for a particular trunk
   termination. However, this sharing or communication of
   call/transaction state information is outside the scope of this
   document.

   This model serves as an example.  M3UA imposes no restrictions as to
   the exact layout of the network elements, the message distribution
   algorithms and the distribution of the signalling processes.
   Instead, it provides a framework and a set of messages that allow for
   a flexible and scalable signalling network architecture, aiming to
   provide reliability and performance.

--brian

Tolga Asveren wrote:                                                 (Fri, 24 Feb 2006 14:59:37)
> Brian,
> 
> Of course associations can fail. If they fail due to a host failure, there
> is no issue. Now, I assume you speak of premature failures.
> 
> Let's say, the probablity for an association to prematurely fail is p. If p
> is not satisfying the requirements for a carrier grade environment, the SCTP
> assocation is not fit to be used with M3UA -or one should be ready for bad
> suprises-. There is nothing like something *never* fails, there is always a
> probability for failure for anything, important is that it is under
> tolerable limits.
> 
> But, we discussed all this in this mailing list and put something to
> summarize the result:
> 
> http://www.ietf.org/internet-drafts/draft-asveren-sigtran-m3uacons-00.txt
> 
> Specifically Sections 2 and 3 in that draft.
> 
>    Thanks,
>    Tolga
> 

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