[OpenSIPS-Users] Opensips + rtpproxy issue

[Daniel Zanutti]

No special configuration, we just set IP's and ports.

Since CPU is not your problem, I believe you have some kind of bandwidth
limitation in your network.

I suggest you confirm:
1) You have enough max open files in your rtpproxy process ->
/proc/PID/limits
2) Where the bottleneck is: CPU, IO or bandwidth. You can record some
packets in wireshark inside RTPPROXY machine and confirm audio is
distorted before and after rtpproxy.

Regards


On Tue, May 5, 2020 at 10:35 AM Miha <miha at softnet.si> wrote:

> Hi,
>
> no CPU usage is around 1% to 5%, basically nothing.
> In sound there is big distortion it is impossibly to
> comunicate with each other.
>
> We have two cors deticated to it. Do you have any special
> thing set on it?
>
> tnx
> miha
>
> On Tue, 5 May 2020 10:27:22 -0300
>  Daniel Zanutti <daniel.zanutti at gmail.com> wrote:
> > Hi Miha
> >
> > Could you explaining how does it break? We use it in
> > virtual machines and
> > our safe limit is around 500 simultaneous calls, on
> > dedicated single core
> > VPS. Does CPU usage reach 100%?
> >
> >
> >
> > On Tue, May 5, 2020 at 10:11 AM Miha via Users
> > <users at lists.opensips.org>
> > wrote:
> >
> > > Hello
> > >
> > > we have virtualized opensips and rtpproxy running on
> > the same server which
> > > is virtualized in vmware infrastructure. Servers are
> > not old, also traffic
> > > is not so big (cca 50 simultaneous calls). when there
> > is a peak cca 80
> > > simultaneous calls RTP starts to break.
> > >
> > > is there any special setting/flag to be set, so that I
> > can optimze this?
> > > load on VM is very low.
> > >
> > > rtpproxy -version
> > > Basic version: 20040107
> > >
> > > Opensips is 2.1
> > >
> > >
> > > thank you for help.
> > > Miha
> > > _______________________________________________
> > > Users mailing list
> > > Users at lists.opensips.org
> > >
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> > >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200505/9dccb4dc/attachment.html>