[asterisk-users] visdn, misdn and the hell

[Massimo Nuvoli]

I am at the end of a long way... i try to work with a number of isdn
boards (BRI not PRI) and i found only a lot of problems.

First, the bristuff that is "near" working, but not so perfect ISDN
designed interface. This is not bad but in a production environment
this solution is not usable.

Second visdn, i am cryng because i see a lot of people sayng "yes is
very attractive" but the developer and who pay him is doing a bad bad
bad bad work, they work on a closed source way, very bad.

And last misnd, working now (thnks to Digium), i am happy, but not at
100%, a lot of problems are here, some kernel fault even, some problem
in the "diagnostic" part.

I think the ISDN part of asterisk is very important, in Italy there is
a lot of equipments that are ISDN and not ANALOGIC or PRI, and with no
ISDN stable support it is impossibile to port asterisk on the real world.

Wath i see now is that a lot of integrators are doing this: using
external box to avoid at 100% the isdn problem in asterisk. Very bad,
we go to use proprietary designed hardware and software, external
components, more complexity, more point of failure.

This is, for me, the hell.

I am the only one searching a solution to the ISDN problem?
Why develop a lot separate ISDN systems and not to concentrate all
efforts on one or two?

Why there is NOT a native isdn support on asterisk? why i must add a
separate visdn misdn bristuff or capi component?

Ciao.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20070306/78a6dd2a/signature-0001.pgp