sr-users September 2018

sr-users@lists.kamailio.org

72 participants
123 discussions

Kamailio On Tap – Social Event In Dusseldorf, Sep 27, 2018

by Daniel-Constantin Mierla

Hello, we are organizing an open social networking event in the evening of Sep 27, 2018, in Dusseldorf, at the end of the first day of Kamailio Developers meeting. Anyone in the area that wants to enjoy beer, pizza and chat about Kamailio, VoIP/RTC is welcome to join us. More details at: * https://www.kamailio.org/w/2018/09/kamailio-on-tap-social-event-in-dusseldo… Note that participation is free, but you have to announce your participation until Sep 26 in order to plan properly the event. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

6 years, 2 months

usr location

by volga629＠networklab.ca

Hello Everyone, User location lookup looks like can't handle long $rU like 10102-ce72256df4945bc472ed9c27a1037f46. It always return -3 404 not found. here relevant log Sep 19 23:37:26 canlvprx01 /usr/sbin/kamailio[29217]: INFO: <script>: [INVITE] Call going from LAN SourceIP <10.18.130.50> to WAN. Sep 19 23:37:26 canlvprx01 /usr/sbin/kamailio[29217]: INFO: <script>: Looking user --> 10102-ce72256df4945bc472ed9c27a1037f46 in db Sep 19 23:37:26 canlvprx01 /usr/sbin/kamailio[29217]: INFO: <script>: Got [INVITE] and status <null> route[LOCATION] { $avp(oexten) = $rU; xlog("L_INFO", "Looking user --> $rU in db\n"); if (!lookup("location")) { $var(rc) = $rc; t_newtran(); switch ($var(rc)) { case -1: case -3: route(MSG_STORE); # Meaning SMS has being stored for offline delivery if(!t_check_status("202")) { xlog("L_INFO", "Got [$rm] and status [$rs]\n"); # For rest traffic proceed as normal send_reply("404", "Not Found"); } exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } } kamailio-5.1.3-1.gitf0dce0c99.fc27.x86_64 volga629

6 years, 2 months

re- double record route

by Wilkins, Steve

Hi Henning, Yes I do have that enabled. What is happening is that one of the providers on IOS is sending a double record route on the INVITE, but it is getting lost somewhere so when I send a 'BYE', I get a "404 not here". When I look at the SIP message I see only one of the record routes from the INVITE, therefore my assumption is, this is what is causing the 404, because everything else looks good.

6 years, 2 months

occasional processing delay and UAC remote registration

by Dmitri Savolainen

Hi all. i encountered in my 4.1.5 kamailio server some inconstant issue. I have 2 listen address: addr1 for incoming SIP requests and as source addr for remote registration (via UAC module) addr2 for incoming SIP requests only uac config for regs: modparam("uac", "reg_keep_callid", 1) modparam("uac", "reg_random_delay", 120) modparam("uac", "reg_retry_interval", 300) modparam("uac", "reg_timer_interval", 40) i have response time checking tool, that send OPTIONS every second, which immedeately replied by sl_send_reply("200") without any processing. Usualy respose time <1ms. Sometimes (2-3 per day) addr1 stop to response for these OPTIONS (timeout >5sec), while addr2 continue responding with time <1ms. In kamailio.log at this moment bunch of messages like ERROR: uac [uac_reg.c:1034]: uac_reg_tm_callback(): got sip response 403 > while registering ERROR: uac [uac_reg.c:1034]: uac_reg_tm_callback(): got sip response 408 > while registering That is normal: some remotes are broken. The problem is: 1. usually these messages appearing is not the reason of problem, but all problems are while these messages in log 2. it may be on OFF peak / ON peak day period 3. in my test installation i have much more remote failure registration (X 10), and the problem is not manifested more often (but i can catch it 2-3 per day) I think adding more workers for addr1 may help (now 8 worker and 16 CPUs). But it is interesting to understand the source of this issue -- Savolainen Dmitri

6 years, 2 months

Where does location ruid come from?

by David Cunningham

Hello, We are debugging an issue with location records having duplicate "ruid" values, which aren't allowed by the table index. Can anyone tell us where the "ruid" value comes from? Is it a function of some other variable? Thanks in advance, -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

6 years, 2 months

Can't get from cache: $sqlrows(asg)

by David Villasmil

Hello guys, i've got this in my config: Module config: modparam("sqlops","sqlcon","asg=>mysql://DB_USER:DB_PASS@DB_HOST/kamailio") Route: sql_query("asg", "insert ignore dispatcher (id, setid, destination, flags, priority, attrs, description) values (NULL, $var(dispatcher_id), 'sip:$si:5080', 0, 0, 'weight=$var(new_weight);maxload=50', '$fU')"); xlog("L_ERR", "[ASG_ADD_TO_DISPATCHER] Affected rows: $sqlrows(asg)\n"); if ($sqlrows(asg)>0) { ds_reload(); } else { xlog("L_ERR", "[ASG_ADD_TO_DISPATCHER] COULD NOT ADD THE NEW GATEWAY WITH IP $si AND USERNAME $fU\n"); } and i'm getting: 0(3929) CRITICAL: <core> [core/cfg.y:3447]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 1261, column 20-32: Can't get from cache: $sqlrows(asg) I can't figure out where the problem might be. Can anyone help? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

6 years, 2 months

Await to INVITE after REGISTER for mobile device which get awake via android/iOS notification messages

by Kristijan Vrban

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 a simple loop, trying new INVITES every second, but this is not elegant. A nice solution would be a type of queue, where the pending INVITE get send to the new location triggered immediately by the fresh REGISTER from that device to avoid any delay during call setup Kristijan

6 years, 2 months

Incoming call on Kamailio WebRTC

by Adesh Pandey

Hi All, We are trying to setup WebRTC with Kamailio as sip registrar and dispatcher. We have succeed for outgoing calls but cannot attend incoming calls to the Kamailio. It would be a great help if someone can provide a sample config for webrtc + kamailio or blog for the same. Thanking you all -- Adesh Pandey Sr. Software Developer [image: phone] +91 92129 92129 Ext: 56 [image: moible] +91 8527384897 [image: Profile Pic] [image: Facebook] <https://www.facebook.com/VoiceTree?_rdr>[image: Twitter] <https://twitter.com/MyOperator>[image: Twitter] <https://www.youtube.com/user/MyOperatorCo>[image: Linkedin] <https://www.linkedin.com/company/voicetree-technologies>[image: Google+] <https://plus.google.com/+MyoperatorCo/posts> [image: Logo] <http://myoperator.co/>

6 years, 2 months

Re: [SR-Users] Record-Route Parameters

by Duarte Rocha

Hey, I need all of my kamailio's IPs in Record Routes and i can do that already. What i want to do is add different parameters to each Record-Route. Is that possible? A sexta, 14/09/2018, 17:54, Duarte Rocha <duarterocha91(a)gmail.com> escreveu: > Greetings, > > My Kamailio has 2 IP's and, as such, it will generate two Record-Routes > when the Request is relayed. > > I want to add one parameter to one of the Record Routes and another > parameter to the other Record-Route. However, if i use add_rr_param() it > will automatically add the parameters to the two Record-Route Headers. > > Is there a way to do what i want without me re-writing the headers > directly ? > > Cheers, > > Duarte Rocha >

6 years, 2 months

how to catch attacker using bad request line?

by Juha Heinanen

In order to be able to fail2ban an attacker that sends tons of SIP requests with malformed request lines, it would need to be possible to generate an appropriate syslog message from config file. I didn't find any sanity module param value that would turn on checking of request line syntax. Any other ideas? As an example, below is what comes to syslog when I send a request that has syntax error on request line. -- Juha Sep 17 14:46:39 char /usr/bin/sip-proxy[9458]: ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [(null)] Sep 17 14:46:39 char /usr/bin/sip-proxy[9458]: WARNING: <core> [core/receive.c:230]: receive_msg(): parsing relevant headers failed Sep 17 14:46:43 char /usr/bin/sip-proxy[9458]: ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [(null)] Sep 17 14:46:43 char /usr/bin/sip-proxy[9458]: WARNING: <core> [core/receive.c:230]: receive_msg(): parsing relevant headers failed

6 years, 2 months

← Newer
1
...
4
5
6
7
8
9
10
...
13
Older →

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 September 2018