[Asterisk-Users] New ISDN architecture available for asterisk

Matteo Brancaleoni mbrancaleoni at espia.it
Thu Oct 20 11:25:57 MST 2005


Hi. see my comments inline.

On Thu, 2005-10-20 at 11:41 +0200, Tzafrir Cohen wrote:
> > 
> > vISDN is not based on Zaptel, libpri, chan_zap, zaphfc, qozap, etc...
> > but has been designed from scratch to be a standard compliant EuroISDN
> > implementation plus a channel crossconnector, plus protocol analisys
> > support thru Ethereal, plus a ppp terminator, plus other stuff :)
> 
> Ironically, the bristuff patch has currently (AFAIK, and not including
> vISDN which I haven't yet read much about) the best eauroisdn support
> and supports hfc hardware as well.
yes the "best" that is "available". but please compare it to ETSI specs.
and in zaptel based... which means broken frames under load (and not
only...)

> > 
> > - Open, modular, flexible and versatile architecture
> > - Fully GPLed
> 
> What are the plans about commiting code to asterisk? openbpx support?
with openpbx the support is coming.
With asterisk only if digium will accept non disclaimed code, which I
don't expect to happens. But if they want, they can add it.

> 
> > - Full support for PRI and BRI
> > - Full support for Network and Terminal Equipment role
> > - Traffic analisys with (patched) Ethereal
> > - E-channel sniffing
> > - D-channel sharing between applications (in TE-multipoint mode)
> > - Good integration with latest 2.6 kernels and extensive usage of their
> > newer features (e.g.: sysfs)
> 
> With which versions of 2.6 should it work? With which versions was it
> tested?
tested with 2.6.8-13 both vanilla and suse 9.3 patched and centos 4.1/2
patched.
currently is developed and tested under suse 9.3 and centos 4.1.
AFAIK has been tested also under fedora core 4.

> 
> > - Protocol stacks are implemented following the finite-state-machine
> > models described in the ETSI specification for better
> > compliance/debuggability.
> > - Termination of PPP connections without exiting from the kernel
> > - Takes advantage from HFC's framer for HDLC traffic
> > - Preliminary/experimental support for hardware PCM bus
> > - Preliminary support for hardware channel bridging
> > - Support for dynamic (optionally automatic) activation/deactivation of
> > layer2 (DLC connection)
> > - Unintrusive with respect to the Linux kernel and Asterisk (no patches 
> > needed)
> 
> Requires extra kernel modules? Extra asterisk channel modules?
> Oh well, I'm already building an extra zaptel-modules package...
kernel modules like zaptel... the drivers :)
for asterisk there's a new channel driver, which doesn't require
any asterisk patching

Greetings, Matteo.




More information about the asterisk-users mailing list