Re: [SR-Users] A "success_route" as counterpart to "failure_route" available?

_route. I tried it, and as said: then the location from the external registrar server is saved. Not the contact from the requesting UA. > On October 2, 2017 6:33:31 AM EDT, Kristijan Vrban <vrban.l...@gmail.com> > wrote: > >Hello, > > > >i need a "succ

[SR-Users] Best variant to share variables between two dialogs?

Hi, based on Daniels example from: http://blog.miconda.eu/2010/01/best-of-new-in-kamailio-300-19-htable.html ... modparam("htable", "htable", "acalls=>size=8;") ... route { ... if(is_method("INVITE") && !has_totag()) { # a new call if($shtcv(ht=>^$fU$)>=3) {

[SR-Users] Register on kamailio.org wiki page not working

Hi, https://www.kamailio.org/wiki/start?do=register Is not working. You get a empty page here. Kristijan ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Upgrade issue with old Kamailio 3.0.3 in table rls_presentity

ing Westerholt : > Am Dienstag, 29. Mai 2018, 16:39:22 CEST schrieb Kristijan Vrban: > > > Hmm, for me it looks like it is the wrong table. Should be " > rls_watchers" > > > not " rls_presentity" So it is a error on the SQ upgrade commands from > > > http

[SR-Users] Upgrade issue with old Kamailio 3.0.3 in table rls_presentity

Hi, i try a upgrade from old 3.0.3 Kamailio mysql db. Got stuck with update the structure : ALTER TABLE rls_presentity MODIFY callid VARCHAR(255) NOT NULL;ALTER TABLE rls_presentity MODIFY contact VARCHAR(128) NOT NULL; found on: https://www.kamailio.org/wiki/install/upgrade/3.1.x-to-3.2.0 But

Re: [SR-Users] Upgrade issue with old Kamailio 3.0.3 in table rls_presentity

Hmm, for me it looks like it is the wrong table. Should be " rls_watchers" not " rls_presentity" So it is a error on the SQ upgrade commands from https://www.kamailio.org/wiki/install/upgrade/3.1.x-to-3.2.0 2018-05-29 16:19 GMT+02:00 Kristijan Vrban : > Hi, > > i

Re: [SR-Users] fix_nated_contact and IPv6

fix_contact from NAT Traversal Module has the same issue. 2015-01-23 10:24 GMT+01:00 Sebastian Damm : > Hi Daniel, Hi Klaus, > > On Thu, Jan 22, 2015 at 10:48 PM, Daniel-Constantin Mierla < > mico...@gmail.com> wrote: > >> 1) I guess the initial author know there is no nat in

[SR-Users] Await to INVITE after REGISTER for mobile device which get awake via android/iOS notification messages

Hi, now that many SIP endpoints are mobile devices which usually deep-sleep, and only get awake after Android/iOS own notification messages awake them, what are the best practices to await a a pending INVITE to such a mobile device until it REGISTER after the awake? I currently use a Asterisk a do

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

test with tools such as sipp, or was this happening > after a while, with usual phones registering? > > Can you list the tcp connections and see if they are listed? > > kamctl tcp core.tcp_list > > Cheers, > Daniel > > On 25.03.19 08:03, Kristijan Vrban wrote: > >> The sol

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

> Just curious, did you get to compile with OpenSSL 1.0 and test? Just compiled with OpenSSL 1.0 . Gone test now. Am Di., 26. März 2019 um 15:40 Uhr schrieb Joel Serrano : > > Just curious, did you get to compile with OpenSSL 1.0 and test? > > On Tue, Mar 26, 2019 at 06:12 Kristij

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

it > first in request_route block. I think this would be a good addition to > the default configuration file as well, IMO, the sip server should not > connect for sending replies and should do it also for requests that go > behind nat. > > Cheers, > Daniel > > On 19.03.19 1

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

Hi Andrew, yes, with openssl 1.0.2 Kamailio is now up and running since five days. Looks good so far. Kristijan Am Do., 28. März 2019 um 11:09 Uhr schrieb Andrew Pogrebennyk : > > On 3/26/19 3:52 PM, Kristijan Vrban wrote: > >> Just curious, did you get to compile with OpenS

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

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 incoming SIP traffic via TCP. The > incoming TCP network packages get TCP-ACK from the OS (Debian 9, > 4.18.0-

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

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

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

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

[SR-Users] Regex issue with subst_body

Hi, in a sdp i need to rewrite a a=sendrecv to a=sendonly but onyl for the for the video stream. I made a regex like this: (?<=m=video)(?s)(.*)(a=sendrecv) Full version here: https://regex101.com/r/rovecJ/1 But if have problems to translate this into kamailio config via subst_body function. I

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

worker, i do not see any activity. Just: futex(0x7fdaeca92f8c, FUTEX_WAIT_PRIVATE, 1, NULL and nothing, even when i see the main tcp process choose this worker process. Kristijan Am Mi., 27. Feb. 2019 um 15:14 Uhr schrieb Kristijan Vrban : > > first of all thanks for the feedback. i prepar

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

) at core/tcp_read.c:1974 #18 0x556ead4c8e24 in tcp_init_children () at core/tcp_main.c:4853 #19 0x556ead3c352a in main_loop () at main.c:1735 #20 0x556ead3ca5f8 in main (argc=13, argv=0x7e2c3828) at main.c:2675 Am Do., 14. März 2019 um 13:41 Uhr schrieb Kristijan Vrban : > &