Re: [SR-Users] Dispatcher problem $avp(dsattrs) is null

2019-02-27 Thread Denys Pozniak
Hello! Do you have as follows parameter? modparam("dispatcher", "attrs_avp", "$avp(dsattrs)") чт, 28 февр. 2019 г. в 05:21, jaflong jaflong : > > I am doing a ds_select_dst call. I think dispatcher did run because $du > gets updated > > > The problem is $(avp(dsattrs)) value is null. > > Any

[SR-Users] Dispatcher problem $avp(dsattrs) is null

2019-02-27 Thread jaflong jaflong
I am doing a ds_select_dst call. I think dispatcher did run because $du gets updated The problem is $(avp(dsattrs)) value is null. Any ideas why? ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org

Re: [SR-Users] TLS reload

2019-02-27 Thread Patrick Wakano
Thanks for the feedback guys! Much appreciated! Kamailio and Let's Encrypt with TLS reload, is the way to go then! Cheers! Patrick Wakano On Thu, 28 Feb 2019 at 08:58, Henning Westerholt wrote: > Am Mittwoch, 27. Februar 2019, 09:53:18 CET schrieb Joel Serrano: > > Been doing it like that too

Re: [SR-Users] TLS reload

2019-02-27 Thread Henning Westerholt
Am Mittwoch, 27. Februar 2019, 09:53:18 CET schrieb Joel Serrano: > Been doing it like that too (kamailio+tls+LE+auto-reload) for quite some > time now with 0 issues.. :) > [..] Hello, it looks that the warning in the module README is outdated. Maybe somebody could submit a pull request for an

Re: [SR-Users] auth_ephemeral too noisy

2019-02-27 Thread Juha Heinanen
Henning Westerholt writes: > > I did some tests with auth_ephemeral. When timestamp has expired, I get > > to syslog > > > > Feb 23 03:53:05 char /usr/bin/sip-proxy[31758]: WARNING: auth_ephemeral > > [authorize.c:205]: autheph_verify_timestamp(): username has expired Feb 23 > > 03:53:05 char

Re: [SR-Users] double_rr issues

2019-02-27 Thread Alex Balashov
Does Kamailio have listeners (listen= on both interfaces)? What is the value of the ‘mhomed’ setting? These nuances surely differ between the two hosts. — Sent from mobile, with due apologies for brevity and errors. > On Feb 27, 2019, at 4:14 PM, Roman Dissauer wrote: > > I’m experiencing

[SR-Users] double_rr issues

2019-02-27 Thread Roman Dissauer
I’m experiencing issues with kamailio 5.1 in multihomed config: two machines, latest debian stretch, latest kamailio 5.1, exactly same config (verified with diff) both machines have an internal and an external network interface. Only thing different is that they are in different datacenters.

[SR-Users] kamailio/asterisk no call with sound if use rtpproxy/rtpengine

2019-02-27 Thread PICCORO McKAY Lenz
i have setup asterisk/rtpproxy/kamailio following the guide in https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb and later NAT traversal with rtpproxy as i understand in simple we must have: phone/caller-->[-->rtpproxy->kamailio->asterisk->kamailio->rtpproxy

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Alex Balashov
On Wed, Feb 27, 2019 at 06:53:54PM +, Duarte Rocha wrote: > I use database for lots of configs. On any given first request i do around > 10 queries. > > A while ago i measured the processing time (using bm_timer) when i was > still using MySql and got times of around 6ms per first Invite and

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Duarte Rocha
I use database for lots of configs. On any given first request i do around 10 queries. A while ago i measured the processing time (using bm_timer) when i was still using MySql and got times of around 6ms per first Invite and around 2ms for other in-dialog requests. While i think those are big

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Alex Balashov
On Wed, Feb 27, 2019 at 01:43:02PM -0500, Ovidiu Sas wrote: > You can do hundreds of CPS with only two workers and the CPU will be > at 3% utilization on very old hardware. > There's something else in your config creating issues. +1 -- Alex Balashov | Principal | Evariste Systems LLC Tel:

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Ovidiu Sas
Do you use a lot of logging? Have you enabled asynchronous logging? If you are using the DB only for dispatcher, then you have other issues then the db. The dispatcher module is caching the data on memory. You can do hundreds of CPS with only two workers and the CPU will be at 3% utilization on

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Alex Balashov
I would say the first step is to gauge the total velocity of any given initial request through your config. One way to do that is: https://kamailio.org/docs/modules/5.2.x/modules/benchmark.html But I prefer this approach: route { $avp(proc_start) = $TV(Sn); ...

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Duarte Rocha
Ok, i reduced the number of processes and tried a few different values, but the performance hasn't changed a lot. How can i debug this and find the bottleneck in my system? A quarta, 27/02/2019, 17:56, Duarte Rocha escreveu: > Greetings Alex, > > At the moment i'm trying to debug some issues

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Alex Balashov
Okay, but at a paltry 20 CPS -- or even several multiples of that -- none of this should be an issue. There's something else going on. On Wed, Feb 27, 2019 at 10:28:54AM -0800, Julien Chavanton wrote: >

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Julien Chavanton
*https://www.kamailio.org/docs/modules/5.2.x/modules/db_sqlite.html#db_sqlite.p.db_set_journal_mode * On Wed, Feb 27, 2019 at 10:27 AM Julien Chavanton wrote: > > Hi, you can use the WAL mode, so

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Julien Chavanton
Hi, you can use the WAL mode, so that readers are never delayed. Just make sure all the connections to the DB are using the WAL mode. The downside is that the writers can be delayed sometimes, similar to Postgres read only replica On Wed, Feb 27, 2019 at 9:57 AM Duarte Rocha wrote: >

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Alex Balashov
Why do you have 100 processes for Kamailio?  Dial that down! http://www.evaristesys.com/blog/tuning-kamailio-for-high-throughput-and-performance/ — Sent from mobile, with due apologies for brevity and errors. > On Feb 27, 2019, at 12:56 PM, Duarte Rocha wrote: > > Greetings Alex, > > At the

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Duarte Rocha
Greetings Alex, At the moment i'm trying to debug some issues with the server and try some solutions to see the impact. With little load i'm getting some percentage of "503 Server Unavaliable" errors from Kamailio. I made some testing without using database for anything but Dispatcher and

Re: [SR-Users] SQlite in memory

2019-02-27 Thread Alex Balashov
What sort of insufficient read performance are you seeing from SQLite on modern storage which would lead you to this unnecessary ideation? Read performance on SQLite is insanely fast... — Sent from mobile, with due apologies for brevity and errors. > On Feb 27, 2019, at 12:23 PM, Duarte Rocha

[SR-Users] SQlite in memory

2019-02-27 Thread Duarte Rocha
Greetings, I'm trying to use SQlite as my engine in order to improve performance. I would like to have my Database stored in memory for faster access. I see that Kamailio can open the SQlite database as Read-Only, but i can't find a way to open it in memory. Is this possible using Kamailio?

Re: [SR-Users] Kamailio stop to process incoming SIP traffic via TCP.

2019-02-27 Thread Kristijan Vrban
first of all thanks for the feedback. i prepared our system now to run with debug=3 I hope to see more then then. Am Mi., 27. Feb. 2019 um 11:53 Uhr schrieb Kristijan Vrban : > > Hi kamailios, > > i have a creepy situation with v5.2.1 stable Kamilio. After a day or > so, Kamailio stop to process

Re: [SR-Users] Kamailio stop to process incoming SIP traffic via TCP.

2019-02-27 Thread Sergey Safarov
I think need to increase LimitNOFILE in systemd file https://www.freedesktop.org/software/systemd/man/systemd.exec.html [Service] LimitNOFILE=99 . Sergey ср, 27 февр. 2019 г., 14:27 Ivaylo Markov : > Hello, > > I believe this issue is related - >

Re: [SR-Users] Kamailio stop to process incoming SIP traffic via TCP.

2019-02-27 Thread Ivaylo Markov
Hello, I believe this issue is related - https://github.com/kamailio/kamailio/issues/1172. We encountered the problem before and the solution is to link kamailio-tls-modules with libssl1.0.X instead of libssl1.1. On 27/02/2019 13:23, Jurijs Ivolga wrote: > Hi, > > Just to add that in my case I

Re: [SR-Users] Kamailio stop to process incoming SIP traffic via TCP.

2019-02-27 Thread Jurijs Ivolga
Hi, Just to add that in my case I had a problem when after some period of time with a lot of TLS clients(100k+) I got a lot of TCP connections in CLOSE_WAIT state. When connections in CLOSE_WAIT state hit more then 1k, then kamailio stopped to receive traffic via TLS, nevertheless UDP at same

Re: [SR-Users] Kamailio stop to process incoming SIP traffic via TCP.

2019-02-27 Thread Kristijan Vrban
when is strace to the kamailio process that is attached to the tcp port. it get sporadic this: [], 46, 5000)= 0 epoll_wait(17, [{EPOLLIN, {u32=2692971064, u64=139924137540152}}], 46, 5000) = 1 accept(14, {sa_family=AF_INET, sin_port=htons(59766), sin_addr=inet_addr("xxx.xx.xxx.xxx")},

Re: [SR-Users] Kamailio stop to process incoming SIP traffic via TCP.

2019-02-27 Thread Jurijs Ivolga
Hi, I experienced something similar on Debian Stretch, nevertheless on Debian Jessie it worked fine. We use TLS and I was thinking that it is something to do with SSL libraries, but never had chance to find out. But maybe my problem was nothing to do with what you just described. Jurijs On

Re: [SR-Users] Kamailio behind NAT or With Public IP - Which one is highly recommended

2019-02-27 Thread Pintu Lohar
Hi Daniel, Thanks for you reply , Yes we indeed do use powerful hardware configuration server ,and we would tune to (centos) OS limits. There are many good blogs available on kamailio for high throughput and performance, we refer the same . One of them is

[SR-Users] Kamailio stop to process incoming SIP traffic via TCP.

2019-02-27 Thread Kristijan Vrban
Hi kamailios, i have a creepy situation with v5.2.1 stable Kamilio. After a day or so, Kamailio stop to process incoming SIP traffic via TCP. The incoming TCP network packages get TCP-ACK from the OS (Debian 9, 4.18.0-15-generic-Linux) but Kamailio does not show any processing for the SIP-Traffic

Re: [SR-Users] Kamailio behind NAT or With Public IP - Which one is highly recommended

2019-02-27 Thread Daniel-Constantin Mierla
Hello, there were companies that pushed hundred thousands of active tls connections to same kamailio and it went fine. You will have to do some tuning to kamailio params as well as to the operating system limits, but if you have powerful hardware, having such number of active tls connections

Re: [SR-Users] Kamailio behind NAT or With Public IP - Which one is highly recommended

2019-02-27 Thread Pintu Lohar
Hi Yasin, Not yet tested, My bad - it's 0.1 million with TLS but yes we are yet to test ), We need to distribute the users to different Kamailio cluster through API server. However, Would like to try Option 2 as well and test with it. Regards Pintu Lohar On Wed, Feb 27, 2019 at 7:16 PM YASIN

Re: [SR-Users] Kamailio behind NAT or With Public IP - Which one is highly recommended

2019-02-27 Thread YASIN CANER
Hello Pintu 1 million TLS user? Have u ever test with tester on Kamailio ?Because I remembered in sr-mails that an user tested on 1000 client on TLS transport , it consumes so much CPU etc . I guess 1 milliyonTLSUser make big impact your system for all registration/call. I tested option-2 for

Re: [SR-Users] Kamailio behind NAT or With Public IP - Which one is highly recommended

2019-02-27 Thread Pintu Lohar
Hi Yasin, Thanks indeed for your valuable input for the active-active cluster(Option-1) & Option-2 We definitely would like to try setting up an active-active cluster for the next phase if not in current phase. But In order to use Kamailio in the active-active cluster, I think we need to

Re: [SR-Users] TLS reload

2019-02-27 Thread Joel Serrano
Been doing it like that too (kamailio+tls+LE+auto-reload) for quite some time now with 0 issues.. :) On Tue, Feb 26, 2019 at 5:51 PM Patrick Wakano wrote: > Thanks Sergiu for your reply! > That's exactly what I am planning to do. But I just want to make sure the > reload would not cause me