sr-users October 2018

sr-users@lists.kamailio.org

81 participants
125 discussions

Forcing outbound transport to TCP
by Ivan Ribakov 02 Oct '18

02 Oct '18

I’m new to Kamailio and currently evaluating it’s capabilities. One of the things I would like to be able to do is to change outbound message transport based on some dynamic logic. Kamailio setup: I’m running on a setup from this guide - http://kamailio.org/docs/tutorials/5.1.x/kamailio-install-guide-git/ <http://kamailio.org/docs/tutorials/5.1.x/kamailio-install-guide-git/> and using default configuration file. In a basic scenario of one2one call, I was able to make Kamailio to forward INVITE to callee over TCP by issuing a REGISTER request with “transport=tcp” parameter. Although it worked, as far as I understand that means all communication with the callee will be happening over TCP. I would like to be able to change transport dynamically so looking for a way to do that from config file. I tried modifying $ru/$du in the following manner, but it didn’t seem to work. # default config content if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting # added to try to force TCP transport $du = $du + ";transport=tcp"; } Any pointers as to how can I modify the outbound message transport? Do I need to use some extra modules or can it be achieved with a basic setup? Thanks in advance, Ivan

4 5

Registrar Module
by Dan Quinney 01 Oct '18

01 Oct '18

Hi, So, route[REGISTRAR_1] will, when the max_contacts is reached, reply to the endpoint with a 503 error containing a "P-Registrar-Error: Too many registered contacts" header - this seems wrong to me so I've tried to work around it with route[REGISTRAR_2] which returns the right response, but, also writes "INFO: registrar [save.c:615]: test_max_contacts(): too many contacts for AOR" to the log file, which is messy. Does anyone have any pointers for doing this better? Thanks, Dan route[REGISTRAR_1] { if ( is_method("REGISTER") ) { if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); setbflag(FLB_NATSIPPING); } if ($avp(maximum_contacts) != $null) { $xavp(reg=>max_contacts) = $avp(maximum_contacts); } save("location"); } return; } route[REGISTRAR_2] { if ( is_method("REGISTER") ) { if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); setbflag(FLB_NATSIPPING); } if ($avp(maximum_contacts) != $null) { $xavp(reg=>max_contacts) = $avp(maximum_contacts); } save("location", "0x02"); switch ($retcode) { case -1: sl_send_reply("500", "Server Internal Error"); exit; case -2: sl_send_reply("403", "Forbidden"); exit; }; sl_send_reply("200", "OK"); } return; }

2 1

RTPEngine Question
by Wilkins, Steve 01 Oct '18

01 Oct '18

Hello All, I have an issue where Kamailio-RTPEngine-Asterisk calls work good when a softphone UAC on an IOS phone makes an Inbound call to a WebRTC client. However, if the softphone UAC is on Windows, it does not work (No Audio/Video). I noticed in the Wireshark trace that when using IOS I see STUN packets, but when using Windows I see no STUN packets. I believe this may be my issue, but I am not sure why the IOS would create STUN packets but when using Windows I get no STUN packets. Does anyone have any thoughts on what could be causing this? Thank you,

1 0

Re: [SR-Users] Problem with replicating dialogs using DMQ
by Charles Chance 01 Oct '18

01 Oct '18

Hi Jan, Setting multi_notify parameter should fix. Cheers, Charles On Mon, 1 Oct 2018 at 08:26, <jenus(a)cyberchaos.nl> wrote: > Charles, > > I have the follwing parameters configured: > > # ----- dmq params ----- > modparam("dmq", "server_address", "sip:10.10.10.1:5060") > modparam("dmq", "num_workers", 4) > modparam("dmq", "ping_interval", 90) > modparam("dmq", "notification_address", > "sip:sip04.voip.domain.test:5060") > > And the output of dmq.list_nodes is: > > { > host: 10.10.10.2 > port: 5060 > resolved_ip: 10.10.10.2 > status: active > last_notification: 0 > local: 0 > } > { > host: sip03.voip.domain.test > port: 5060 > resolved_ip: 10.10.10.1 > status: active > last_notification: 0 > local: 0 > } > { > host: sip04.voip.domain.test > port: 5060 > resolved_ip: 10.10.10.2 > status: active > last_notification: 0 > local: 0 > } > { > host: 10.10.10.1 > port: 5060 > resolved_ip: 10.10.10.1 > status: active > last_notification: 0 > local: 1 > } > > > As you can see the nodes are listed twice, one time with the ip and one > time with the hostname. If i change the notification_address to a ip > address the duplicate entry's are gone. > > Thanks, > > Jan > > Charles Chance schreef op 2018-09-28 20:54: > > Hello, > > > > Can you share your dmq config (modparams) and the output of > > dmq.list_nodes? > > > > Cheers, > > > > Charles > > > > On Thu, 27 Sep 2018 at 12:51, Jan Hazenberg <jenus321(a)gmail.com> > > wrote: > > > >> In the output of "kamcmd dmq.list_nodes" i see nodes twice. One with > >> ip address of the host and one with the hostname of the host. > >> > >> Jan > >> > >> On Thu, Sep 27, 2018 at 12:47 PM Jan Hazenberg <jenus321(a)gmail.com> > >> wrote: > >> > >> Daniel, > >> > >> It indeed sends duplicate DMQ messages, one to the ip of the other > >> node and one to the hostname of the other node. > >> > >> Unknown request: KDMQ sip:dialog@sip04.voip.domain.acc:5060 | > >> (application/json) > >> Unknown request: KDMQ sip:dialog@10.10.10.12:5060 [5] | > >> (application/json) > >> > >> Is there any way to disable this? > >> > >> Thanks, > >> > >> Jan > >> > >> On Thu, Sep 27, 2018 at 11:50 AM Daniel-Constantin Mierla > >> <miconda(a)gmail.com> wrote: > >> > >> Hello, > >> > >> the log message says that the dialog was already added to the timer. > >> Do you see retransmissions of the DMQ requests on the network with > >> ngrep/wireshark/...? > >> Cheers, > >> Daniel > >> > >> On 27.09.18 10:40, Jan Hazenberg wrote: > >> > >> Hello, > >> > >> I'm trying to replicate active dialogs using the DMQ module. I see > >> the dialogs on the other nodes but it generates a error message in > >> the logs on all the nodes: > >> > >> Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog > >> [dlg_timer.c:130]: insert_dlg_timer(): Trying to insert a bogus dlg > >> tl=0x7efdca1bebf8 tl->next=0x7efdca14cb80 tl->prev=0x7efdca14cb80 > >> Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog > >> [dlg_dmq.c:309]: dlg_dmq_handle_msg(): Unable to insert dlg timer > >> 0x7efdca1beb98 [2643:3725] > >> > >> Even with the timeout_avp option disabled i still see the error > >> messages. I tested this on kamailio 5.0.3 and 5.1.3 with the same > >> results. > >> > >> With debug enabled i see the correct data is replicated to the other > >> nodes: > >> > >> dlg_dmq_replicate_action(): sending serialized data > >> > > > {"action":2,"h_entry":1328,"h_id":409,"state":4,"start_ts":1538036606,"lifetime":7200,"tag1":"1635359980","tag2":"as2d80799c","cseq1":"21","cseq2":"0","route_set1":"","route_set2":"","contact1":" > sip:sipuser@10.10.10.10:1057;alias=10.10.10.10~1055~1","contact2":" > sip:+31101234567@10.10.10.10:5060 > >> [6]"} > >> > >> "lifetime":7200 is in the serialized data, and when i check on the > >> other node with "kamcmd dlg.list" i see that the lifetime data is > >> not updated. > >> > >> Thanks, > >> > >> Jan > >> > >> _______________________________________________ > >> Kamailio (SER) - Users Mailing List > >> sr-users(a)lists.kamailio.org > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >> > >> -- > >> Daniel-Constantin Mierla -- www.asipto.com [1] > >> www.twitter.com/miconda [2] -- www.linkedin.com/in/miconda [3] > >> Kamailio World Conference -- www.kamailioworld.com [4] > >> Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- > >> www.asipto.com [1] > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > > > > CHARLES CHANCE > > Managing Director > > > > t. 0330 120 1200 m. 07932 063 891 > > Sipcentric Ltd. Company registered in England & Wales no. 7365592. > > Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt > > Street, Birmingham Science Park, Birmingham B7 4BB. > > > > Links: > > ------ > > [1] http://www.asipto.com > > [2] http://www.twitter.com/miconda > > [3] http://www.linkedin.com/in/miconda > > [4] http://www.kamailioworld.com > > [5] http://sip:dialog@10.10.10.12:5060 > > [6] http://sip:+31101234567@10.10.10.10:5060 > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- *Charles Chance* Managing Director t. 0330 120 1200 m. 07932 063 891 -- Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.

2 1

Problem with replicating dialogs using DMQ
by Jan Hazenberg 01 Oct '18

01 Oct '18

Hello, I'm trying to replicate active dialogs using the DMQ module. I see the dialogs on the other nodes but it generates a error message in the logs on all the nodes: Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog [dlg_timer.c:130]: insert_dlg_timer(): Trying to insert a bogus dlg tl=0x7efdca1bebf8 tl->next=0x7efdca14cb80 tl->prev=0x7efdca14cb80 Sep 27 10:17:31 sip04 /usr/sbin/kamailio[27367]: CRITICAL: dialog [dlg_dmq.c:309]: dlg_dmq_handle_msg(): Unable to insert dlg timer 0x7efdca1beb98 [2643:3725] Even with the timeout_avp option disabled i still see the error messages. I tested this on kamailio 5.0.3 and 5.1.3 with the same results. With debug enabled i see the correct data is replicated to the other nodes: dlg_dmq_replicate_action(): sending serialized data {"action":2,"h_entry":1328,"h_id":409,"state":4,"start_ts":1538036606,"lifetime":7200,"tag1":"1635359980","tag2":"as2d80799c","cseq1":"21","cseq2":"0","route_set1":"","route_set2":"","contact1":"sip:sipuser@10.10.10.10:1057 ;alias=10.10.10.10~1055~1","contact2":"sip:+31101234567@10.10.10.10:5060"} "lifetime":7200 is in the serialized data, and when i check on the other node with "kamcmd dlg.list" i see that the lifetime data is not updated. Thanks, Jan

4 5

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users October 2018