[openss7] Defining CAPI-extension to support MTP2...

[Tobias Erichsen <erichsen@te-systems.de>]

Hi there,

I don´t know if any of you guys have heard of CAPI.
This is an api which has been defined for manufacturer
independent usage of ISDN-boards.  Both signaling and
data-transfer are supported by this interface.  There
have even been some extensions to also support GSM and
ATM (Q.2931/UNI 4.0).  Up to now there has not been
an integration of SS7 into this API.  As some of our
customers require SS7 instead of Q.931 signaling, we
are trying to get manufacturers to support this stuff.

To not burden them with implementing the full protocol
stack (with ISUP & TCAP) I thought about proposing them
to first implement MTP2 (or perhaps even MTP2) within
the driver and let the application do the ISUP part.

So right now I´m looking for the options which have to
be defined for MTP2 and MTP3 to be configurable at run-
time and those to be configured at installation-time.

For MTP2 I really only see two options: 
a.) Emergency Alignment / Normal Alignment
b.) Basic Method / PCR Method

I have not looked into the MTP3-part that much - but
I think as this setup will only be a signaling-end-
point, the parts to be configured should be pretty
small.  

Do you see any stuff I have left out for MTP2 and do
you have some good suggestions for MTP3?

One further point I´d like to point to is the isdn4linux
project. This is accompanied by capi4linux which is
developing a open-source-CAPI for linux.  It could be
a cool thing to also have ISUP signaling based on your
project as an additional option to the Q.931 based stuff
which is in use right now...

Any suggestions and/or comments highly welcome ;-)

Best regards,
Tobias
--
TE-SYSTEMS GmbH - competence in e-communications.
Max-von-Laue-Weg 19 - 38446 Wolfsburg  -  Germany
TEL: +49 (0)5361 895-0 - FAX: +49 (0)5361 895-999
PGP-KEY: DB519487D8B620F8141551F31E68A993167535D4