Hello Matt, > Anywayz, while we're at it, chan_lcr is licensed under GPL, which means > it's unlikely to get included in main stream Asterisk, which means that > support for it may fail at some time.
That's a problem of Asterisk, not of GPL software. > I've noticed a few changes going in to libpri (or maybe it was Dahdi) to > support BRI over the past couple of days (albeit in trunk), which makes > me think that long term the best bet is going to be native support. DAHDI support for ISDN/BRI would be great. No more worries about mISDN and such. But: do you think, that people start writing kernel drivers for various BRI cards or do you think, they will use mISDN V2 code from kernel >= 2.6.27 and just write an interface to that? Writing all drivers again from scratch for all available cards sounds like a nice task..... > Which makes me think that maybe we should stick with chan_misdn for the > moment and then later move to native libpri/dahdi support once the > project moves to 1.6/trunk. Yes, we stick with chan_misdn for now. That's the easiest for the community. regards, Ingmar ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
