No subject

This stuff is hdd-bounded, not cpu-bounded. With only 02 hdd your server is
handicapped

On Tue, Jul 21, 2009 at 11:31 AM, Do Tien Dung <dungdt at elcom.com.vn> wrote:

>  I have read the feature and performance of Rtpproxy and found that It ca=
n
> be handle thousands calls concurrently but no where said It can be handle
> how many concurrent call if using recording.
>
>
>
> Actually when I test using recording, Connected call never reached 100
> calls.
>
>
>
> My testing server has 2 Quardcore Xeon 3.0Ghz. 8GB RAM, 2x146Gb SCSI HDD.
> And when running I check by =93top=94 command. It show that rtpproxy not =
using
> many CPU ( never more than 0.1%). So I thing that It can be problem of
> RTpproxy.
>
>
>
> Please help me or show me a solution for my situation. My system must to
> handle about 240 call and recording all of theme.
>
>
>
>
>
> Br,
>
>
>
> *From:* DangVinh Nguyen [mailto:dangvinh.nguyen at gmail.com]
> *Sent:* Tuesday, July 21, 2009 11:14 AM
> *To:* Do Tien Dung
> *Subject:* Re: [OpenSIPS-Users] RTPProxy recording problem
>
>
>
> I think you already know the answer: No more than 100 calls per rtpproxy
> box with call recording.
>
> Check out for a multi-box rtpproxy solution. Or buy a big box with decent
> storage: Memory -> RAM Disk -> RAID ->Tape/Optical
>
> On Tue, Jul 21, 2009 at 10:58 AM, Do Tien Dung <dungdt at elcom.com.vn>
> wrote:
>
> Hi all.
>
>
>
> I=92m newbee in Opensips.  When I=92m intergrated Opensips with RtpProxy =
with
> recording all call option of Rtpproxy, everything ok if the concurrent ca=
ll
> and call setup per second is not many, But when I=92m calling about 120ca=
lls
> it setup call too slowly, sometime INVITE timeout. But If I not using
> recording option,  the system seting up about 240 calls quickly.
>
>
>
> So what is my problem, please help me.
>
> Br,
>
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>

--00504502c74882e186046f302603
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable