Re: [SR-Users] Kamailio 5.0.X RPM packages/repo broken

Thank you Sergey!! Installation was successful now!! Cheers! Patrick Wakano On 10 July 2018 at 14:24, Sergey Safarov wrote: > I was trigered rpm rebuild. > Please check after 40 min. > > вт, 10 июля 2018 г., 6:57 Patrick Wakano : > >> Hello list, >> Hope you all doing fine! >> >> I've been

Re: [SR-Users] Kamailio 5.0.X RPM packages/repo broken

I was trigered rpm rebuild. Please check after 40 min. вт, 10 июля 2018 г., 6:57 Patrick Wakano : > Hello list, > Hope you all doing fine! > > I've been trying to install Kamailio packages from the opensuse repo (as > per https://www.kamailio.org/wiki/packages/rpms) but the installation is >

[SR-Users] Kamailio 5.0.X RPM packages/repo broken

Hello list, Hope you all doing fine! I've been trying to install Kamailio packages from the opensuse repo (as per https://www.kamailio.org/wiki/packages/rpms) but the installation is failing with this message: Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed.

Re: [SR-Users] CPS

Figured it out eventually, thanks for the tip Alex. Cheers --Sergiu On Mon, Jul 9, 2018 at 4:14 PM Sergiu Pojoga wrote: > I have not until now that you recommended it, looks much simpler indeed, > thanks. > > Although, so far I can't seem to hit a pipe limit. If I watch pl.stats, no > matter

Re: [SR-Users] CPS

I have not until now that you recommended it, looks much simpler indeed, thanks. Although, so far I can't seem to hit a pipe limit. If I watch pl.stats, no matter what *timer_interval* I set, the counter increases to 1 upon a call then back to 0 the next second. root@proxy:/# watch -n 1 -d

Re: [SR-Users] CPS

Have you considered using pipelimit for this? It's as simple as: if(!pl_check("$avp(customer_id)", "TAILDROP", "$avp(cps_limit)")) { pl_drop(); exit; } There was a time when that wasn't possible because pipes couldn't easily be created dynamically for a given customer ID or

[SR-Users] CPS

Hi folks, Trying to implement CPS throttling based on this article, having some trouble. modparam("htable", "htable", "rhs=>size=32;initval=0;autoexpire=300;" modparam("htable", "htable",

[SR-Users] Communication between Kamailio Proxy and Registrar Server

Hi All, As per our requirement, we want to configure one Kamailio as a " Kamailio PROXY" and 2nd Kamailio as a " Kamailio REGISTRAR". Whenever any INVITE request come at " Kamailio PROXY" we want to get the UA information from " Kamailio REGISTRAR " and send INVITE to particular UA. Could

Re: [SR-Users] Delay in 100 Trying response for INVITE when the load is 70 INVITE's per sec

Hello, just as hint to troubleshoot which actions take too long to execute, see benchmark module as well as *latency* related core parameters. Cheers, Daniel On 09.07.18 14:03, Federico Cabiddu wrote: > Hi, > Kamailio doesn't delay sending of 100 trying after calling t_relay().  > You probably

Re: [SR-Users] Delay in 100 Trying response for INVITE when the load is 70 INVITE's per sec

Hi, Kamailio doesn't delay sending of 100 trying after calling t_relay(). You probably have something blocking in your script: a SQL operation, a Http query or some long operation. Check your routing script for the presence of such operations. Regards, Federico On Mon, 9 Jul 2018, 13:51

[SR-Users] Delay in 100 Trying response for INVITE when the load is 70 INVITE's per sec

Hi All, When we are using the kamailio to handle around 70 INVITE's per second, kamailio is sending 100 Trying with the delay of around 3-4sec for few INVITE's. How can I reduce the delay in 100 Trying? Also, I tried increasing the number of threads for SIP routing processes.

Re: [SR-Users] RTPEngine-Recording-daemon

I underestand your meaning. Thank you. On Mon, Jul 9, 2018 at 1:54 PM, Pawel Kuzak wrote: > Hi, > > You can. For every new call a new connection is established using the UNIX > socket. So different connections means different calls. > > Regards, > Paul > > > > Am 09.07.2018 um 10:43 schrieb

Re: [SR-Users] RTPEngine-Recording-daemon

Hi, You can. For every new call a new connection is established using the UNIX socket. So different connections means different calls. Regards, Paul Am 09.07.2018 um 10:43 schrieb Mojtaba: Hello, In RTPEngine recording-daemon, I enabled "forward-to" option to unix_socket. All things work

Re: [SR-Users] ul.add | path & socket not correctly set

Hello, few things for your version 5.0.x:   - rpc ul.add command doesn't have the last two parameters: received and socket -- those were added in 5.1 -- so socket is not going to be set no matter parameter you give   - path parameter was expecting "0" (s:0) in order not to set it -- for

[SR-Users] RTPEngine-Recording-daemon

Hello, In RTPEngine recording-daemon, I enabled "forward-to" option to unix_socket. All things work right, I got metadata at first, then media packets (RTP-UDP-IP). The metadata for each calls is received just at first packet, but i want to know, if i have more than one concurrent active call in

Re: [SR-Users] ul.add | path & socket not correctly set

Hello, I will check it -- reminders are good, somehow first message was not noticed... Cheers, Daniel On 08.07.18 13:15, Laurent Schweizer wrote: > > Dear all, > >   > > Any idea how to solve it ? > >   > > BR > >   > > Laurent > >   > > *De :*sr-users