Re: SS7 UPU FROM ASP

Emmanuel,

At the ASP, M3UA is envisioned by the RFC as presenting an MTP to MTP-User
service primitive interface an MTP-User.  As Barry notes, how availability
of the MTP user is detected across the MTP/MTP-User interface is
implementation dependent for SS7 MTP (see Q.701 for example).  As such, this
must be an implementation dependent mechanism.

For example, if the MTP/MTP-User interface is implemented as pseudo-device
driver and service primitives passed using, say, getpmsg(2) and putpmsg(2)
system calls, unavalability of the local MTP-User might be signalled across
the interface by closing the file description associated with the pseudo-
device driver.  Of couse, other representations and implementations are
possible.

So if closing a file descriptor signals the unavaibility of an equipped MTP
User, the M3UA implementation should deactivate for the associated AS.  At
the SGP, the SGP is responsible for determining if the entire AS is
unavailable and, if so, should generated UPU messages toward originators
sending messags to the unavailable User Part.

Sending a UPU message directly from the ASP would consists of packaging a
normal SS7 UPU message in an M3UA DATA message and sending it to the SGP.
However, beware that the ASP needs to known the availability of all ASPs for
the AS with all SGP, and that some NIF at the SG might reject the message out
of hand.

It is better and fully in fitting with th RFC to indicate unavailability to
the SGP, only using ASPTM.


--brian


emmanuel mavrommatis wrote:                    (Thu, 31 May 2007 18:38:43)
> 
>    Hi Barry,
>    Thanks for the responce.
>    I  understand that ASP at the AS does not have MTP3 layer (just M3UA).
>    As so when you say M3UA implementation-dependent primitive to the MTP3
>    layer, do you mean a M3UA implementation-dependent message to the MTP3
>    layer at the SG?
>    Thanks,
>    Emmanuel
> 


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