- sr-users - kamailio.org

pua.publish using RPC
by Alex Balashov 12 Dec '17

12 Dec '17

Hello, Is pua.publish strictly an MI function, or is it possible nowadays to call it via the RPC channel, and specifically, using jsonrpc_exec()? Thanks! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 (direct) / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 5

Re: [SR-Users] Kamailio does not add port number to addresses in Via, Record-Route headers
by George Diamantopoulos 12 Dec '17

12 Dec '17

Hello again, Indeed this issue does not manifest at all. I'm awfully sorry for the false alarm, and on release day no less! The problem was there was a lingering DNAT rule in iptables, which would translate port 5066 to port 5060. The deployment script injected this as it was carried over from our legacy platform. Of course, I kept banging my head against the wall here because sngrep wouldn't show the DNAT's effect as it captures traffic from the NIC directly: it would show a REGISTER arriving on 5066, but the dport was masqueraded before being handed over to kamailio. Similarly for the outgoing INVITE. NAT is wrong in so many ways... :-) BR, George On 11 December 2017 at 18:17, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote: > Hello, > > I did a quick test and all looks fine, ports are set in via and > record-route, in my config I have: > > record_route(); > > $fs="udp:127.0.0.1:5080"; > $du = "sip:127.0.0.1:9"; > t_relay(); > exit; > > Then sending an OPTIONS resulted in the trace shown below. > > Cheers, > Daniel > > U 2017/12/11 17:14:47.108430 127.0.0.1:56729 -> 127.0.0.1:5060 > OPTIONS sip:test@127.0.0.1 SIP/2.0. > Via: SIP/2.0/UDP 192.168.178.84:62516;branch=z9hG4bK.3aaddf68;rport;alias. > From: sip:sipsak@192.168.178.84:62516;tag=16d1c24. > To: sip:test@127.0.0.1. > Call-ID: 23927844(a)192.168.178.84. > CSeq: 1 OPTIONS. > Contact: sip:sipsak@192.168.178.84:62516. > Content-Length: 0. > Max-Forwards: 70. > User-Agent: sipsak 0.9.7pre. > Accept: text/plain. > . > > > U 2017/12/11 17:14:51.010251 127.0.0.1:5080 -> 127.0.0.1:9 > OPTIONS sip:test@127.0.0.1 SIP/2.0. > Record-Route: <sip:127.0.0.1:5080;r2=on;lr>. > Record-Route: <sip:127.0.0.1;r2=on;lr>. > Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK61bd. > b2882fea15c488761489f8ef588efbe1.0. > Via: SIP/2.0/UDP 192.168.178.84:62516;received=127.0.0.1;branch=z9hG4bK. > 3aaddf68;rport=56729;alias. > From: sip:sipsak@192.168.178.84:62516;tag=16d1c24. > To: sip:test@127.0.0.1. > Call-ID: 23927844(a)192.168.178.84. > CSeq: 1 OPTIONS. > Contact: sip:sipsak@192.168.178.84:62516. > Content-Length: 0. > Max-Forwards: 69. > User-Agent: sipsak 0.9.7pre. > Accept: text/plain. > . > > On 11.12.17 16:37, George Diamantopoulos wrote: > > Hello all, > > I have the following issue in my configuration, tested with 5.2.0-rc1 so > far: > > At some point, I set the $fs pseudovariable to force a request to be > relayed through a specific socket. Although this is honoured by kamailio > (i.e. the request does indeed leave the kamailio host from the respective > socket), the port number is not added to the Via and RR headers. As a > result, all replies to the request, as well as all subsequent requests from > the other SIP UA are relayed to the default port, 5060. Here's an example: > > SIP UAC to kamailio: > INVITE 192.168.1.1:5060 ---> 192.168.1.254:5060 > Kamailio to UAS ($fs is set): > INVITE 2.2.2.2:5066 ---> 3.3.3.3:5060 > Topmost Via in request relayed by kamailio is: > SIP/2.0/UDP 2.2.2.2;branch=aaaaaaaaaaaaaa <- port 5066 is not added > Topmost RR in request relayed by kamailio is: > <sip:2.2.2.2;r2=on;lr;did=bbbbbbb;nat=yes> <- port 5066 is not added > RESULT: Reply from UAS is sent to 2.2.2.2:5060 > > Is this behaviour valid? Am I missing anything? Kamailio is configured to > listen on both sockets on IP 2.2.2.2, namely: a) udp:2.2.2.2:5060 and b) > 2.2.2.2:5066. Thanks. > > BR, > George > > > _______________________________________________ > Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > -- > Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - www.asipto.com > Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com > >

2 1

Change Calling Number
by Duarte Rocha 11 Dec '17

11 Dec '17

Hey I'm trying to do some normalization on my Calling Number after Kamailio chooses the Gateway in which it will deliver the request. So, i'm trying to do the operation in the DISPATCH route. However, in this route, msg_apply_changes() doesn't work and returns (-1). I've tried to do this on a Branch route but Kamailio doesn't allow me to use msg_apply_changes() there and otherwise changes won't be persistent. Is there a way to modify $fU at this stage? Cheers

2 1

Kamailio v5.1.0 Released - new major version is out
by Daniel-Constantin Mierla 11 Dec '17

11 Dec '17

Kamailio v5.1.0 is out – it comes with 9 new modules and a significant set of improvements touching more than 90 existing modules. You can read detailed release notes at: * https://www.kamailio.org/w/kamailio-v5-1-0-release-notes/ Many thanks to all developers and community members that made possible this release. A consistent effort was directed to export most of the config functions to the KEMI framework, allowing to write SIP routing logic in other scripting languages executed by the embedded interpreters for Lua, JavaScript, Python or Squirrel, with the option to reload the routing script without restarting Kamailio. Enjoy Kamailio v5.1.0! Thank you for flying Kamailio! Daniel -- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference 2018 - http://www.kamailioworld.com

1 0

Kamailio does not add port number to addresses in Via, Record-Route headers
by George Diamantopoulos 11 Dec '17

11 Dec '17

Hello all, I have the following issue in my configuration, tested with 5.2.0-rc1 so far: At some point, I set the $fs pseudovariable to force a request to be relayed through a specific socket. Although this is honoured by kamailio (i.e. the request does indeed leave the kamailio host from the respective socket), the port number is not added to the Via and RR headers. As a result, all replies to the request, as well as all subsequent requests from the other SIP UA are relayed to the default port, 5060. Here's an example: SIP UAC to kamailio: INVITE 192.168.1.1:5060 ---> 192.168.1.254:5060 Kamailio to UAS ($fs is set): INVITE 2.2.2.2:5066 ---> 3.3.3.3:5060 Topmost Via in request relayed by kamailio is: SIP/2.0/UDP 2.2.2.2;branch=aaaaaaaaaaaaaa <- port 5066 is not added Topmost RR in request relayed by kamailio is: <sip:2.2.2.2;r2=on;lr;did=bbbbbbb;nat=yes> <- port 5066 is not added RESULT: Reply from UAS is sent to 2.2.2.2:5060 Is this behaviour valid? Am I missing anything? Kamailio is configured to listen on both sockets on IP 2.2.2.2, namely: a) udp:2.2.2.2:5060 and b) 2.2.2.2:5066. Thanks. BR, George

2 1

Re: [SR-Users] Failed to find command http_client_query
by Alexandru Covalschi 11 Dec '17

11 Dec '17

Hello, Wanted to ask if you found something ________________________________ Alexandru Covalschi VoIP Engineer and System Administrator tel: +373 673 98 493 > 24 нояб. 2017 г., в 22:19, Alexandru Covalschi <568691(a)gmail.com> написал(а): > > Hello, sharing whole config except vars.cfg file, where values like API_PROTO, DBURL etc. are defined. > > <kamailio_504.cfg> > > > ________________________________ > Alexandru Covalschi > VoIP Engineer and System Administrator > tel: +373 673 98 493 > >> 24 нояб. 2017 г., в 13:21, Daniel-Constantin Mierla <miconda(a)gmail.com <mailto:miconda@gmail.com>> написал(а): >> >> Hello, >> >> can you provide here all the http_client_query(...) you have in your config and list in which route block are they used (like request_route, failure_route, ...)? You can replace IP addresses, usernames, passwords with other strings, but if you use any kamailio variables (e.g. $rU), let them in place. >> Cheers, >> Daniel >> >> On 23.11.17 20:54, Alexandru Covalschi wrote: >>> sip:172.21.0.14:5060 <sip:172.21.0.14:5060> is the local address of the server, it seems like a bug in http_client, as I don't have such http_query call anywhere :/ >>> just re-checked >>> Also the fact that it works perfectly on 4.4.6 tells that it's not a configuration issue >>> >>> ________________________________ >>> Alexandru Covalschi >>> VoIP Engineer and System Administrator >>> tel: +373 673 98 493 >>> >>>> 23 нояб. 2017 г., в 16:59, Daniel-Constantin Mierla <miconda(a)gmail.com <mailto:miconda@gmail.com>> написал(а): >>>> >>>> There was a mistake in the exports structure, the name of the function with 4 parameter was http_query instead of http_client_query. I pushed a patch to fix it. >>>> Then, related to the issue with cannot resolve the host, the debug messages show an invalid http url being used: >>>> >>>> Nov 21 04:18:20 ast1 /usr/sbin/kamailio[20804]: DEBUG: http_client [functions.c:146]: curL_query_url(): ****** ##### CURL URL [sip:172.21.0.14:5060 <sip:172.21.0.14:5060>] >>>> >>>> The it fails to do the dns stuff with it... >>>> >>>> Cheers, >>>> Daniel >>>> >>>> On 22.11.17 22:38, Alexandru Covalschi wrote: >>>>> Just wanted to ask if you need my help to test/check/etc. >>>>> >>>>> ________________________________ >>>>> Alexandru Covalschi >>>>> VoIP Engineer and System Administrator >>>>> tel: +373 673 98 493 >>>>> >>>>>> 21 нояб. 2017 г., в 11:58, Alexandru Covalschi <568691(a)gmail.com <mailto:568691@gmail.com>> написал(а): >>>>>> >>>>>> Kamailio is actually starting, please take a look at that debug=4 log file: https://filebin.net/r54y3jkmzdyk9zak/syslog_http_client_query_failed.txt <https://filebin.net/r54y3jkmzdyk9zak/syslog_http_client_query_failed.txt> >>>>>> at line 1042 http_client module is successfully loading, but at line 12785 it fails to load http_client_query >>>>>> >>>>>> Also please check line 50385 in https://filebin.net/352vff41fwx7uowg/syslog_http_query_curl_6.txt <https://filebin.net/352vff41fwx7uowg/syslog_http_query_curl_6.txt> >>>>>> I'm using http_query here with 5.0.4 http_client, you can see that http_client makes a request, but afterwards it returns curl error 6, but the weirdest thing is - at line 19887 I request token from the very same IP address, only url is changed, and it actually works fine. >>>>>> ________________________________ >>>>>> Alexandru Covalschi >>>>>> VoIP Engineer and System Administrator >>>>>> tel: +373 673 98 493 >>>>>> >>>>>>> 21 нояб. 2017 г., в 10:44, Daniel-Constantin Mierla <miconda(a)gmail.com <mailto:miconda@gmail.com>> написал(а): >>>>>>> >>>>>>> But then kamailio is not starting, or? >>>>>>> >>>>>>> Can you provide all the error message as they are printed in syslog file? File, line and other details are part of the logs message, allowing to identify the location in the source code where that happens ... >>>>>>> >>>>>>> Cheers, >>>>>>> Daniel >>>>>>> >>>>>>> On 21.11.17 09:38, Alexandru Covalschi wrote: >>>>>>>> It is still one of the issues >>>>>>>> >>>>>>>> ________________________________ >>>>>>>> Alexandru Covalschi >>>>>>>> VoIP Engineer and System Administrator >>>>>>>> tel: +373 673 98 493 >>>>>>>> >>>>>>>>> 21 нояб. 2017 г., в 9:40, Daniel-Constantin Mierla <miconda(a)gmail.com <mailto:miconda@gmail.com>> написал(а): >>>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> in your email in this thread, you said: >>>>>>>>> >>>>>>>>> > When I try to change http_query to http_client_query it fails to load with error "failed to find command http_client_query". >>>>>>>>> >>>>>>>>> Is it still the case, or that was sorted out? >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Daniel >>>>>>>>> >>>>>>>>> On 20.11.17 22:43, Alexandru Covalschi wrote: >>>>>>>>>> Works ok on 4.4.6. So I suppose it's a weird 5.0.4 + my environment bug. I'm rolling back to 4.4.6 right now, will keep one 5.0.4 machine for testing (on debian 9) >>>>>>>>>> Let me know if I can provide any dumps/cores etc. >>>>>>>>>> >>>>>>>>>> ________________________________ >>>>>>>>>> Alexandru Covalschi >>>>>>>>>> VoIP Engineer and System Administrator >>>>>>>>>> tel: +373 673 98 493 >>>>>>>>>> >>>>>>>>>>> 20 нояб. 2017 г., в 23:29, Alexandru Covalschi <568691(a)gmail.com <mailto:568691@gmail.com>> написал(а): >>>>>>>>>>> >>>>>>>>>>> So the weirdest thing is Kamailio actually sends the request, but it returns curl error 6 in the answer variable. I have a plenty of clonned servers and same behaviour is on all of them, also just now tried on a fresh debian 9 - same result. I'm inside a virtual machine (vmware), but not sure it matters... >>>>>>>>>>> >>>>>>>>>>> ________________________________ >>>>>>>>>>> Alexandru Covalschi >>>>>>>>>>> VoIP Engineer and System Administrator >>>>>>>>>>> tel: +373 673 98 493 >>>>>>>>>>> >>>>>>>>>>>> 20 нояб. 2017 г., в 22:37, Alexandru Covalschi <568691(a)gmail.com <mailto:568691@gmail.com>> написал(а): >>>>>>>>>>>> >>>>>>>>>>>> I often get WARNING: http_client [functions.c:281]: curL_query_url(): Couldn't resolve host, while I don't even use hostnames. >>>>>>>>>>>> After I changed IP address to hostname (which I've added into /etc/hosts) nothing changed. It seems like a weird bug, but I've no idea - is it CURL or kamailio, but when I execute curl from shell it is working fine. I have google dns in resolve.conf and nslookup is also working ok. >>>>>>>>>>>> Can anyone help me with that? >>>>>>>>>>>> >>>>>>>>>>>> ________________________________ >>>>>>>>>>>> Alexandru Covalschi >>>>>>>>>>>> VoIP Engineer and System Administrator >>>>>>>>>>>> tel: +373 673 98 493 >>>>>>>>>>>> >>>>>>>>>>>>> 20 нояб. 2017 г., в 22:06, Alexandru Covalschi <568691(a)gmail.com <mailto:568691@gmail.com>> написал(а): >>>>>>>>>>>>> >>>>>>>>>>>>> t >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>> sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> >>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Daniel-Constantin Mierla >>>>>>>>> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> >>>>>>>>> Kamailio Advanced Training - www.asipto.com <http://www.asipto.com/> >>>>>>>>> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com <http://www.kamailioworld.com/> >>>>>>> >>>>>>> -- >>>>>>> Daniel-Constantin Mierla >>>>>>> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> >>>>>>> Kamailio Advanced Training - www.asipto.com <http://www.asipto.com/> >>>>>>> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com <http://www.kamailioworld.com/> >>>>> >>>> >>>> -- >>>> Daniel-Constantin Mierla >>>> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> >>>> Kamailio Advanced Training - www.asipto.com <http://www.asipto.com/> >>>> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com <http://www.kamailioworld.com/> >> >> -- >> Daniel-Constantin Mierla >> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> >> Kamailio Advanced Training - www.asipto.com <http://www.asipto.com/> >> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com <http://www.kamailioworld.com/>

2 2

can kamailio send 183 to caller
by 赵国杰 11 Dec '17

11 Dec '17

Hello guys, Is it possible for kamailio to initiate a 183 to caller? Thanks

3 6

Releasing Kamailio v5.1.0
by Daniel-Constantin Mierla 11 Dec '17

11 Dec '17

Hello, with no relevant new bugs reported lately, it is time to fix the date for releasing next major version, respectively Kamailio v5.1.0. I am proposing Monday, December 11, 2018, as the release date for v5.1.0, with a fallback option to next day, if a bit of time is still needed. Currently there are ongoing efforts to make rpm packaging a first class citizen via docker and obs, credits to Sergey Safarov for it, and get (auto-generated) reference list of Kemi functions, credits to Samuel Förnes for it. In the next two weeks, they can get in good shape and also do a bit more testing as well as update relevant tutorials. Regarding Kemi exports, if you are using a module, check the master branch version to see if it has any sr_kemi_t exports, if not, report it in the case you want to try using the new config framework that allows reloading routing logic script without restart (you will have to use Lua, JavaScript or Squirrel scripting). And of course, if you are aware of any problem not yet reported to the bug tracker, open an issue as soon as possible to allow time to try to fix it before the release: * https://github.com/kamailio/kamailio/issues Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 2

Exec - call python script with arguments
by Daniel W. Graham 10 Dec '17

10 Dec '17

Trying to call a python script using exec_msg and haven't had any luck. The following works: exec_msg("echo 'TEST' > /usr/local/etc/kamailio/test.txt"); The following works from shell: /usr/local/etc/kamailio/script.py arg1 arg2 arg3 The following does not work from kamailio: exec_msg("/usr/local/etc/kamailio/script.py arg1 arg2 arg3"); (The arguments are just strings for test purposes) Kamailio is running as kamailio user Permissions: 755 script.py Any idea what could be going wrong? -dan

2 2

TOPOS - record timeouts
by Daniel W. Graham 10 Dec '17

10 Dec '17

Looking for clarification on how the timers work, such as 'dialog_expire'. Are these hard-set timeouts meaning if a dialog lasts longer than 'dialog_expire' there could be risk of the dialog not completing successfully? If yes, any plans to integrate with DIALOG module to keep topos records up-to-date per active dialogs? Thanks, -dan

2 2

Need help troubleshooting messages that never made it to the client
by Andrew Chen 09 Dec '17

09 Dec '17

Hi all, So for a while now I've been working with our engineering team to troubleshoot these random events where the UPDATE message sent from the server never made it to the client side. Here is the the topology: Server -(tcp)-> kamailio -(tls)-> client So looks pretty straight forward and I have logging messages stating t_relay() was successful in sending the message. The question is how do we know t_relay really successfully sent it? Does it actually monitor the physical interface as it goes out? Please advise. Thanks. -- Andy Chen -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 6

cfg_get in async_worker causes segfault (v4.4)
by Malcolm O'Hare 09 Dec '17

09 Dec '17

I want to experiment with using the async module. I added the module and updated my request_route to call async_task_route() and put all the existing routing logic in a new route. Unfortunately my kamailio is crashing looking up a cfg_get variable. The exact same route logic works fine in the normal child process, its only when its run in a async_worker that it fails. Is this a known issue? I can see in the core file that there is no group handle in the cfg_group_t (its 0x0), but I know nothing about how that gets set and where. Thanks in advance for any help Malcolm

2 1

Forwarding Registration to Asterisk
by Wilkins, Steve 07 Dec '17

07 Dec '17

Hello All, Problem: My main issue is that when I "REGISTER" a client via Kamailio, and I attempt to "Dial" a different endpoint within an Asterisk Dial Plan, Asterisk throws an error stating that the endpoint (the number I am dialing via "Dial") is not registered or reachable. However, commands like "Playback" do work correctly for the client I "REGISTERED" via Kamailio. E.g. I register client 10001 in Kamailio, I then register another client 10002 in Kamalio; both 10001 and 10002 can exercise an Asterisk Dial Plan which will play videos/audio (No Problem). But, now I want 10001 to Call (Dial) 10002; it is at this point that Asterisk throws the error "10002 is not registered or reachable". I have tried many of the suggestion on many different help boards (several times) but I am still unable to forward a registration from Kamailio to Asterisk. With my current Kamailio configuration (I do use dispatching), I see , via tcpdump, Asterisk receiving a "REGISTER" request, and Asterisk sends back the "unauthorized" as expected, however, Kamailio does not re-send the "REGISTER" as is customary. I am not sure of the next step to take, but I feel I have a couple of options. * I can continue to try and figure out why Kamailio is not sending the second "REGISTER" (I have not yet been able to figure this out). * Tell Asterisk to not require authentication. (I am using pjsip and do not know how to not require authentication in Asterisk when the request is from Kamailio). I have put a lot of time into this one, and I am at a sticking point. Any help or suggestions would be very much appreciated. Thank you,

5 12

400 Bad From URI reply from kamalio
by Konstantin Tumalevich 07 Dec '17

07 Dec '17

One of our clients expiriences strange error. Their system sends BYE with different from address (which IP is presented in Contact header of initial INVITE) and Kamailio immediately responded with "400 Bad From URI". In which module can be generated this response? We use 4.3 version. -- Skype: konstantin.tumalevich

2 2

Question about parsing a jsonrpc_exec result with a colon in object name with jansson_get
by jenus＠cyberchaos.nl 07 Dec '17

07 Dec '17

Hi all, I'm trying to parse the result of a json rpc call to get the register statistics. # Get registrar stats jsonrpc_exec('{"jsonrpc": "2.0", "method": "stats.get_statistics", "params": ["accepted_regs"], "id": 1}'); jansson_get("result[0]", $jsonrpl(body), "$var(registrar_accepted)"); xlog("LOG_LOCAL3","L_WARN","$jsonrpl(body)\n"); The $jsonrpl(body) var contains: {"jsonrpc":"2.0","result":["registrar:accepted_regs = 2"],"id":1} With this code the result stored in $var(registrar_accepted) is : "AcceptedRegistrations":"registrar:accepted_regs = 1" I'm trying to get only the value. I have tried: jansson_get("result[0].registrar:accepted_regs", $jsonrpl(body), "$var(registrar_accepted)"); jansson_get("result[0].['registrar:accepted_regs']", $jsonrpl(body), "$var(registrar_accepted)"); jansson_get("result[0]['registrar:accepted_regs']", $jsonrpl(body), "$var(registrar_accepted)"); But this does not work. Do i need to escape the colon in the object name "registrar:accepted_regs" ? Thanks, Jan

1 1

Doing a quick test with http_async_client module from master branch
by Daniel-Constantin Mierla 07 Dec '17

07 Dec '17

Hello, anyone around here that can do a quick test with http_async_module? I don't have a testbed for it right now and I would spend the time on other resources if someone here can run some tests with http_async_client module from master branch. I did a bit of internal refactoring in order to be able to export the function to kemi interface -- nothing radical, but it would be good to know it didn't break anything. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 3

IMS with online Charging system
by Amar Tinawi 06 Dec '17

06 Dec '17

Hello all Is there any open souce ocs can be integrated with kamailio IMS ? Is it possible to integrate with CGrates ?

2 1

t_set_fr behaviour
by Kelvin Chua 06 Dec '17

06 Dec '17

hi guys, has anyone of you tried playing around with a scenario similar to this? A. invite -> t_set_fr() 2 seconds - if "100 trying" not received in 2 seconds, timeout. works fine. B. after receiving "100 trying" received, t_set_fr() 30 seconds - if 18x not received in 30 seconds, timeout. works fine C. after receiving the first 180, t_set_fr() 10 seconds - if "200 ok" not received in 10 seconds, it will not timeout, but instead it will timeout 30 seconds after B. i noticed this behavior recently and noticed that when a previous t_set_fr() is bigger than the new one, it will be ignored. so if i did 2 -> 10 -> 30, it works (swapping timeout values of B and C) my question is, is this an expected behavior? Kelvin Chua

2 2

load testing ims_charging
by Kelvin Chua 06 Dec '17

06 Dec '17

i am trying to load test the ims_charging module and notice some issues whenever i send test calls one by one, it's perfect. but when i use sipp and generate a bunch of calls, i would get this intermittently CRITICAL: ims_charging [ro_timer.c:122]: insert_ro_timer(): Trying to insert a bogus ro tl=0x7f207e91c2d0 tl->next=0x7f207e8b57b8 tl->prev=0x7f207e97c398 if i continue to hammer the server, it would end up failing all calls. When this issue happens, Ro_CCR will not return any value and will also not trigger the async route, looks like it just sits there frozen. during this time, sip client will receive a 408. also notice cdp complaining of latency usually around 1 second, using packet capture i am sure diameter server is responding properly. i think there is a choke point somewhere. i tried playing around with async_workers, no improvement. any pointers? Kelvin Chua

1 0

Re: [SR-Users] Kamailio Multi IP
by Duarte Rocha 06 Dec '17

06 Dec '17

Thnaks for the reply. I don't need mhomed since i do the socket forcing by myself after the the DISPATCH selects the Gateway. What i need is something that modifies the SIP Request in order to use the outbound IP in the R-URI, To-Header, etc. I'm doing that using the $td and $rd pseudo-variables, but i'm not sure if that is the safest approach. The TOPOS module is really usefull for this, thanks for mentioning. However, the dialog_expires parameter is really confusing, since it imposes a maximum time allowed for a dialog to exist (After the records are deleted, routing no longer works). I could work with a very long timer for this if the ended dialogs would get removed from the table automatically, but that doesn't happen. Cheers

1 0

redis via haproxy
by Aidar Kamalov 06 Dec '17

06 Dec '17

Hello, Kamailio after restart(or start) sometimes can't connect to redis (via haproxy) with logs: Dec 6 07:29:30 siptest /usr/sbin/kamailio[47291]: NOTICE: <script>: ROOT: KDMQ usrloc [764c076919c73540-39925(a)192.168.150.225] Dec 6 07:29:31 siptest /usr/sbin/kamailio[47263]: NOTICE: <script>: ROOT: OPTIONS <null> [0b4dc11225a6fc77294de97578061844@192.168.150.231:5060] Dec 6 07:29:31 siptest /usr/sbin/kamailio[47269]: ERROR: ndb_redis [redis_client.c:130]: redisc_init(): error communicating with redis server [redis] (127.0.0.1:6380/0): Resource temporarily unavailable Dec 6 07:29:31 siptest /usr/sbin/kamailio[47269]: ERROR: ndb_redis [ndb_redis_mod.c:122]: child_init(): failed to initialize redis connections Dec 6 07:29:31 siptest /usr/sbin/kamailio[47269]: ERROR: <core> [core/sr_module.c:923]: init_mod_child(): Error while initializing module ndb_redis (/usr/lib64/kamailio/modules/ndb_redis.so) Dec 6 07:29:31 siptest /usr/sbin/kamailio[47269]: ERROR: <core> [core/pt.c:334]: fork_process(): init_child failed for process 5, pid 47269, "udp receiver child=4 sock=192.168.8.213:5060" Dec 6 07:29:31 siptest /usr/sbin/kamailio[47269]: CRITICAL: <core> [main.c:1611]: main_loop(): Cannot fork Dec 6 07:29:31 siptest /usr/sbin/kamailio[47252]: ALERT: <core> [main.c:740]: handle_sigs(): child process 47269 exited normally, status=255 Dec 6 07:29:31 siptest /usr/sbin/kamailio[47362]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 13 Redis and haproxy working fine (I test it by many attepts - echo ping|ncat localhost 6380) At tcpdump all attemps from kamailio have: *1 $4 PING +PONG *2 $6 SELECT $1 0 +OK my kamailio 5.0.4 config: modparam("ndb_redis", "server", "name=redis;addr=127.0.0.1;port=6380") my haproxy 1.5 config: backend bk_redis mode tcp option tcp-check tcp-check connect tcp-check send PING\r\n tcp-check expect string +PONG tcp-check send QUIT\r\n tcp-check expect string +OK server sipkazan 192.168.107.195:6379 check inter 1s server local 127.0.0.1:6379 check inter 1s backup -- Aydar A. Kamalov

2 2

Re: [SR-Users] using bcrypt passwd hashing
by Walter Martín Villalba 05 Dec '17

05 Dec '17

Hello everyone, and thanks very much for your feedback. Some responses and further questions below. Daniel> Latest kamailio versions support also SHA256 algorithm Martín> SHA256 is also a bad choice for storing passwords. See details here: https://crackstation.net/hashing-security.htm Daniel> However, the main blocker in suing a different hashing algorithm are the sip client devices (mainly hardphones), which implement only MD5. If you implement your own client app, then you can extend kamailio to support whatever hashing you do in the client. Then, of course you can use client side tls certificates for authentication, which should be better than any hashing algorithm. Martín> I do implement my own client app, even though I use a third party SIP stack, which currently doesn't support any other auth methods besides basic and MD5 (standard ones). I am planning to send username and passwd as custom SIP headers in the REGISTER message, probably encrypted, and this will travel on top of TLS. Then Kamailio can extract these custom headers and call a custom python script to decrypt the values and do the authentication (bcrypt password and compare with the one in database). Client certificates are good but only in certain situations (e.g. not if you want a zero footprint client such as a web-based client), and in most cases a pain to manage when your user base grows. Alex> Do you know of any mainstream SIP UACs which support anything other than standard MD5 digest auth? Martín> I don't, but haven't really worked much at all with 3rd party SIP clients. I doubt there's any support for newer passwd hashing schemes, unfortunately. ---------- Now the details.... I'm looking at sipcomm.cfg and see it calls www_authenticate (defined in modules/auth_db/authorize.c). I believe I would need to create a similar function, e.g. bcrypt_authenticate, and call this instead, with the username and passwd values I get in my custom headers (as explained above). The routine would decrypt the values, look up the user in the database, bcrypt the passwd extracted from the custom header, and compare with the one in the database. Doesn't sound too hard, but I do have some concerns related to other functions that www_authenticate may be doing, that I would also need to do in my bcrypt_authenticate function in order to keep Kamailio functioning properly. For example, www_authenticate could be changing some values in the database and/or other temporary storage. I took a quick look at the implementation and tried to follow the calls inside it. I see calls to mark_authorized_cred, check_auth_hr (or auth_check_hdr_md5), and generate_avps, and that some of these functions are indeed changing some values here and there. So, before spending more time looking into these details, I wanted to see if any of you have any suggestions about how to handle this situation, i.e. maybe all I need to do in bcrypt_authenticate is to check the credentials and then set one flag in the database for the user that was just authenticated? Does the explanation above make sense to you? Please let me know any suggestions or further guidance you may have. Thanks a lot, Martín. On Mon, Nov 13, 2017 at 3:00 AM, <sr-users-request(a)lists.kamailio.org> wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.kamailio.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > or, via email, send a message with subject or body 'help' to > sr-users-request(a)lists.kamailio.org > > You can reach the person managing the list at > sr-users-owner(a)lists.kamailio.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > > Today's Topics: > > 1. Branch 5.1 created (Daniel-Constantin Mierla) > 2. Development open in master branch (to be v5.2.x) > (Daniel-Constantin Mierla) > 3. Re: using bcrypt passwd hashing (Daniel-Constantin Mierla) > 4. Re: t_set_fr behaviour (Daniel-Constantin Mierla) > 5. Re: t_set_fr behaviour (Daniel-Constantin Mierla) > 6. Re: AVPOPS: is_avp_set/avp_check "name" parameter as > variable. (Daniel-Constantin Mierla) > 7. Re: strange --dialog in delete state is too old-- log line > managing dialog hashes (Daniel-Constantin Mierla) > 8. Re: 183 acc records even if early_media equals to 0 > (Marco Capetta) > 9. Re: Kamailio issue (Daniel-Constantin Mierla) > 10. Re: using bcrypt passwd hashing (Yuriy Gorlichenko) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 12 Nov 2017 14:42:35 +0100 > From: Daniel-Constantin Mierla <miconda(a)gmail.com> > To: "Kamailio (SER) - Devel Mailing List" <sr-dev(a)lists.kamailio.org>, > "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org > > > Subject: [SR-Users] Branch 5.1 created > Message-ID: <dca81faa-dec2-4e12-704f-b382d23493d7(a)gmail.com> > Content-Type: text/plain; charset=utf-8 > > Hello, > > the GIT branch 5.1 has just been created, it will host the release > series 5.1.x. To get this branch from GIT, you can use: > > > git clone https://github.com/kamailio/kamailio.git kamailio > cd kamailio > git checkout -b 5.1 origin/5.1 > > > Hopefully in two-three weeks time frame the full release of 5.1.0 will > be out. > > >From now on, any corresponding fix has to be pushed first to master > branch and then cherry-picked to branch 5.1. No new features can get in > branch 5.1. Enhancements to documentation or helping tools, as well as > kemi exports are still allowed. If you are not sure about doing or not a > backport, ask on sr-dev mailing list. > > Cheers, > Daniel > > > -- > Daniel-Constantin Mierla > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - www.asipto.com > Kamailio World Conference - www.kamailioworld.com > > > > ------------------------------ > > Message: 2 > Date: Sun, 12 Nov 2017 14:50:45 +0100 > From: Daniel-Constantin Mierla <miconda(a)gmail.com> > To: "Kamailio (SER) - Devel Mailing List" <sr-dev(a)lists.kamailio.org>, > "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org > > > Subject: [SR-Users] Development open in master branch (to be v5.2.x) > Message-ID: <07baf03f-0d1b-30f6-45d2-cacfc3dfec99(a)gmail.com> > Content-Type: text/plain; charset=utf-8 > > Hello, > > git branch 5.1 was just created (to host the release series v5.1.x), > therefore new features can now be pushed again in master branch. They > will be part of the next future release, likely to be numbered 5.2.x. > > Any fixes that affect existing code in branches 5.1 or older version > have to be backported - push first to master and then cherry pick -- see > the contributing guidelines at: > > - > https://www.kamailio.org/wiki/devel/git-commit-guidelines# > backporting_commits > > Many thanks to all contributors so far! Testing of branch 5.1 and giving > feedback for it is very appreciated! > > Cheers, > Daniel > > -- > Daniel-Constantin Mierla > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - www.asipto.com > Kamailio World Conference - www.kamailioworld.com > > > > > ------------------------------ > > Message: 3 > Date: Mon, 13 Nov 2017 09:22:17 +0100 > From: Daniel-Constantin Mierla <miconda(a)gmail.com> > To: "Kamailio (SER) - Users Mailing List" > <sr-users(a)lists.kamailio.org>, Yuriy Gorlichenko < > ovoshlook(a)gmail.com> > Subject: Re: [SR-Users] using bcrypt passwd hashing > Message-ID: <c7bb57e5-16dd-f5c2-f4ac-e3060f3b45bb(a)gmail.com> > Content-Type: text/plain; charset="utf-8" > > > > On 12.11.17 10:33, Yuriy Gorlichenko wrote: > > You can realize any of auth methods by yourself and include it via > > config file/kemi on lua/by adding module > > > > forexample I added SSO auth without any troubles instead of basid MD5 > > for some projects. > Out of curiosity, what do you refer by SSO? > > Cheers, > Daniel > > > > 2017-11-11 18:49 GMT+03:00 Alex Balashov <abalashov(a)evaristesys.com > > <mailto:abalashov@evaristesys.com>>: > > > > Do you know of any mainstream SIP UACs which support anything > > other than standard MD5 digest auth? > > > > On November 10, 2017 7:11:26 PM EST, "Walter Martín Villalba" > > <wvillalba(a)gmail.com <mailto:wvillalba@gmail.com>> wrote: > > >Hello, > > > > > >I did some searches online and talked to some colleagues and it > seems > > >Kamailio only supports the traditional HTTP digest authentication, > > >which > > >uses MD5. I would like to know if any of you has been successful in > > >using > > >bcrypt/scrypt/pbkdf2 passwd hashing, instead of MD5, which has been > > >deemed > > >as obsolete and insecure a long time ago. Perhaps you've written > your > > >own > > >auth module, or just modified the config script to call some other > > >credential checking routine using a custom python/perl script (I'm > > >thinking > > >of doing the latter, of nothing better is available). > > > > > >If any of you have done something like this, using bcrypt or any > > other > > >current and secure hashing algorithm, I would appreciate some > > guidance. > > > If > > >you haven't, aren't you concerned about storing MD5 password > > hashes in > > >your > > >database? > > > > > >Note: if I can't find a good answer using this list, I will try the > > >developer's list next. > > > > > >Thanks in advance, > > > > > >Martín. > > > > > > -- Alex > > > > -- > > Sent via mobile, please forgive typos and brevity. > > > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> > > > > > > > > > > _______________________________________________ > > 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.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com > Kamailio World Conference - www.kamailioworld.com > >

1 0

Kamailio Multi IP
by Duarte Rocha 05 Dec '17

05 Dec '17

Greetings, I have a Kamailio that is hosted on multiple IP's. Each client connects to an IP and there is another IP that communicates with the PSTN. The problem is that I don't want any client "seeing" any IP besides his. If the client (connected to kamailio's IP 1.1.1.1) receives an request coming from the PSTN (connected to Kamailio's IP 2.2.2.2) , it will have 2.2.2.2 on the R-URI, To Header,etc. Is there a method to ensure kamailio will manipulate the packet and use the correct IP ? Currently i'm directly changing the R-URI and To Header, but I don't if it's the correct approach to this. I would also like to know the best way to do those changes right before the packet leaves Kamailio. I know that OnSend route doesn't allow changes in the buffer. I tried Branch routes but not every request goes through that. Thanks for the help. Cheers.

2 1

how to escape asterisk in pattern matching
by voipspace voipspace 05 Dec '17

05 Dec '17

how to escape asterisk in pattern matching if($rU=~"\d+*") regards

2 1

How to change To header URI from Kamailio?
by Arun NV 05 Dec '17

05 Dec '17

Hi, I am using *Kamailio 4.4*. I would like to forward the request to a different port number of my endpoint. I have changed the destination *URI *and the *INVITE *correctly reached to the new port. But the *To header *in the *INVITE *request has the old port. so the endpoint is not responding to the request. Then I tried to remove and replace *To header* using *remove_hf("To")* and* insert_hf("To: $var(modified_to_header) \r\n");* functions. But the to header not changed. So, is there any way to change the *To header URI*.

2 1

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