I have a very high speed LCR App for FreeSwitch (when I say very high speed it can be deployed on the order of 10 to 15 CW/Asterisk boxes to 1 LCR Platform (and its ok if those boxes are autodialing) the LCR can handle call rates in excess of 600 Call/sec... Drop me a list if anyone is interested in it... (sorry its not open source, but it is a very high speed, highly configurable platform... Under extreme loads (600+ CPS) INVITE in to INVITE our times are still less than 140ms on avg
K > From: Kristijan Vrban <[EMAIL PROTECTED]> > Reply-To: Users Mailing List - Non-Commercial Discussion > <[email protected]> > Date: Wed, 04 Jun 2008 11:42:39 +0200 > To: Users Mailing List - Non-Commercial Discussion > <[email protected]> > Subject: Re: [Callweaver-users] chan_lcr for CW? > > Hi roy, > > i wrote to the developer of chan_lcr, he said he heard the first time > about callweaver :) But he was > quite interested to make a CW version for chan_lcr and asked me if i can > name him a developer > who can give him some hints for the differences between the asterisk and > CW channel-api. > Sure a job for you? > > His email: [EMAIL PROTECTED] > > Kristijan > > Roy Sigurd Karlsbakk schrieb: >> Hi >> >> By looking at it, it seems to me chan_lcr is reinventing a few wheels >> (local dialtones etc). Perhaps it'd be better to just get the >> functionality out of the app and replace it by a function and some >> dialplan logic? I've done some LCD with dialplan logic and db queries, >> and that worked, but I don't know if it scales as well as a dedicated >> app. >> >> roy >> >> On 3. juni. 2008, at 18.53, Kristijan Vrban wrote: >> >>> 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 >>> >>> >>> -- >>> Kristijan >>> >>> _______________________________________________ >>> 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 >> >> >> > _______________________________________________ > 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
