>  Way more handy and will be much more reliable too. Steve Underwood did a 
> great job implemeting it, but as far as I know the code isn't actively
> maintained anymore. Of course your implementation of MFC/R2 will take a while 
> to become stable, but hey -- it's a start.

Agreed.

>  Russel pointed some licensing stuff related to the Digivoice drivers. Please 
> listen to him on that, I had no idea of that kind of complication. If your
> implementation of MFC/R2 can't be integrated in Zaptel, then it's no much 
> better than Unicall.
You mean chan_zap/zapata (zaptel is the kernel code). I had already
discussed with Russell the licensing. He just got confused for a
second because he forgot LGPL code requires both license files (GPL
and LGPL).

>  I guess if you look at Digivoice's code to figure out how it works and then 
> write your own code, there will be no licensing issues. But that's just a 
> guess,
> Russel will need to clarify it.
I did not discussed that with Russell, but I will. In the meantime,
since I am aware of the licensing concerns I have not even looked at
that code :-)

I would like to test the BR variant the next week, I will contact you
off-list to see if we can meet via IM.

- Moisés Silva

-- 
"I do not agree with what you have to say, but I'll defend to the
death your right to say it." Voltaire

_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to