[openss7] Re: Fwd: Re: Fwd: Returned mail: User unknown "bidulock@openss7.org"

["Brian F. G. Bidulock" <bidulock@dallas.net>]

David,

Sorry for taking so long to get back to you, but I was vacationing in
Colorado for a while...

On Fri, 29 Sep 2000, David Sugar wrote:
> 
> There is some misunderstanding here.  I mean to integrate SS7 signalling
> events as states in the core Bayonne state engine, and a Bayonne DSO stack to
> talk to the SS7 session and your kernel module, but not your "stack" itself.
> 

No, I didn't think that you would move the stack into Bayonne...  Perhaps
a diagram would help here:

             +--------------------------+
             |                          |
             |      Call Framework      |
             |                          |
             +--------------------------+
                   |              |
             +-----------+  +-----------+
             |           |  |           |
             |   ISUP    |  |   TCAP    |
             |           |  |           |
             +-----------+  +-----------+
                   |              |
          ========Socket==Interface==========
                   |              |
             +-----------+  +-----------+
             |           |  |           |
             |    MTP    |  |   SCCP    |
             |           |  |           |
             +-----------+  +-----------+
                   |              |
                   +--------------+
                   |
             +-----------+
             |           |
             |   Links   |
             |           |
             +-----------+
                   |
             +-----------+
             |           |
             |  Hardware |
             |           |
             +-----------+

I would think that Bayonne sits at the Call Framework level.  The initial
OpenSS7 work addresses below the socket interface on the diagram.  Later it
will address ISUP and TCAP.

> 
> We would like to use SS7 as a means to signal and control states of calls
> activily switched between Bayonne nodes on the public network.  Bayonne really
> is a different kind of switching application for it will look at one side to
> the telephone network, will look to the other side to the data network,
> and Bayonne will eventually switch calls in both environments
> transparently, as well as provide an "application environment" for building
> telephony services such as IVR, messaging, PBX services, conferencing, etc. 
> In the broadest sense Bayonne is being developed as a "telephony server".
> 

Were you looking for an interface above the ISUP/TCAP layer?

--Brian

-- 
Brian F. G. Bidulock
bidulock@openswitch.org