ok, chan_lcr does load now. To test it, catch the patch here: http://www.callweaver.org/ticket/440
Kristijan Kristijan Vrban schrieb: > Ok, i tried to port chan_lcr, i renamed all ast to cw, and just tried it: > > http://callweaver.pastebin.com/m7f884f6c > > So, the most erros are doable for me, but i dont know how to eliminate this > strings.h:221/stdlib.h:196 erros? > > any hints? > > Kristijan > > > Kristijan Vrban schrieb: > >> hi, chan_lcr for callweaver? Because then more BRI-ISDN stuff is in LCR >> and is independent from CW. >> >> So it could be more easier to maintain BRI-ISDN in CW, then with chan_misdn. >> >> this was on the the misdn-list: >> >> dear list members, >> >> the mISDN socket API is almost complete and can be tested. >> - it features robustness, modules can be removed without crash. >> - no module parameters are required in most cases, NT-mode / TE-mode is >> selected by application and can be changed at runtime. >> - layer 3 stack is in user space. >> >> the linux-call-router is also ported to new mISDN API. >> - interfaces are configured via interface.conf (NT / TE / PTP / PTMP >> /...) >> - Asterisk channel interface for using linux-call-router as ISDN >> frontend. (replacement of chan_mISDN) >> >> download lates source and a little howto at: >> >> http://www.linux-call-router.de/download/lcr-1.0/ >> >> ask, if you have problem. >> >> best regards, >> >> andreas >> >> >> >> > _______________________________________________ > Callweaver-users mailing list > [email protected] > http://lists.callweaver.org/mailman/listinfo/callweaver-users > > > _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
