sr-users October 2019

sr-users@lists.kamailio.org

59 participants
83 discussions

by David Villasmil

Hello guys, I'm storing some data in an htable, like so: $var(http_query) = "/default/en_US/send.html?u=user&p=pass&l=$var(next_channel)&n=$var(to)&m=$var(message)"; then i need to store it: $sht(http_requests=>$http_req_id) = $var(http_query); But what's stored is the actual vars, not the the values, it's stored like: sh store: /default/en_US/send.html?u=user&p=pass&l=$var(next_channel)&n=$var(to)&m=$var(message) Why is that? shouldn't the vars be parsed? Thanks Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

5 years, 1 month

Re: [SR-Users] Call limit through shared database

by Olli Attila

Hello Henning, I tried the dialog profile sharing with dmq&dialog modules and now the syncing works between the two kam nodes. Thank you! Is there a way to keep the dialog profiles persistent (load from db if kam restarts)? I was thinking a scenario where kam1 has already the call limit maxed out and kam2 suddenly reboots and after reboot, kam2 should be aware of dialogs on kam1 to be able to limit calls again correctly. Cheers, Olli

5 years, 1 month

Re: [SR-Users] Call limit through shared database

by Olli Attila

Hello, I had the following enabled in db_mode param and now it is actually working: *1 - REALTIME* - any dialog information changes will be reflected into the database immediately. Restarting either of the kam1 or kam2 proxies "on the fly" will result in retrieving dialog profiles correctly from database. Cheers, Olli

5 years, 1 month

Record-Route management

by Duarte Rocha

Greetings, I have multiple IPs in my Kamailio. In some scenarios, the caller and the called connect to different IPs and in others, they use the same IP. Currently i'm running with the RR's module "enable_double_rr" parameter set so i can have one Record-Route for each IP used on the call. However, in the scenario that both caller and called have the same IP, i would like to only have on Record-Route in order to save on the pactet's size. Is this possible to have those two scenarios on the same Kamailio ? Best Regards

5 years, 1 month

string manipulation

by David Villasmil

Hello guys, I'm receiving an http request via xhttp, something like: http://ip.com/request?value1=123&value2=2313&value3... Is it possible to get those values somehow? I also have a suri coming from a ds_select in _dsdst_, I need to get the host from that _dsdst_ Any way of doing this? Thanks all Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

5 years, 1 month

Get destination out of _dsdst_

by David Villasmil

Hello guys, I've never used "ds_select" as opposed to "ds_select_dst", and i would like to get the actual destination out of _dsdst_ I've got modparam("dispatcher", "xavp_dst", "_dsdst_") and then i'm trying to do: if(!ds_select("100", "4")) { send_reply("404", "No destination"); exit; }else{ xlog("L_ERR", "[XHTTP]: The next destination for SMS is: [$xavp(_dsdst_)]\n"); ds_mark_dst("d"); } But that's coming up with The next destination for SMS is: [<<xavp:0x7fbe87acdbf0>>] I need to get the actual ip address out of the struct. Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

5 years, 1 month

Development is open for future release of v5.4.x series

by Daniel-Constantin Mierla

Hello, the branch 5.3 was created late last evening, therefore the master branch is open for adding new features, to be part of future release series v5.4.x. Any bug fix committed to master that applies to 5.3.x or older stable branches should be backported as usual with "git cherry-pick -x ..." to appropriate branches like 5.3 or 5.2. Expect that v5.3.0 will be released in a few weeks from now. Based on the workflow used during the past years, the next future release v5.4.0 should be out after another 8-10 months of development, plus 1-2 months of testing, so sometime in close to the end of spring 2020 or afterwards. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

5 years, 1 month

Branch 5.3 has been created

by Daniel-Constantin Mierla

Hello, the branch 5.3 has been created, to be used for releasing v5.3.x series. To check out this branch, the following commands can be used: git clone https://github.com/kamailio/kamailio kamailio-5.3 cd kamailio-5.3 git checkout -b 5.3 origin/5.3 Pushing commits in this branch: git push origin 5.3:5.3 Note that 5.3 is an official stable branch, so only bug fixes, missing kemi exports (discuss on sr-dev if not sure) or improvements to documentation or helper tools can be pushed to this branch. You may notice a bit of more activity on tls (some issue is under work) and siptrace (a bit of cleanup for coherence might be done) modules, but over all no new features will be pushed there. As usual, if there is a bug fixed, commit and push first to master branch and then cherry pick to 5.2 branch: git cherry-pick -x COMMITID In few weeks, the first release from branch 5.3 will be out, respectively Kamailio v5.3.0. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

5 years, 1 month

Branching 5.3

by Daniel-Constantin Mierla

Hello, if there are no strong opinions against, then it is time to branch 5.3 on git repository. I am considering to do it by the end of the day on Wednesday, October 2, 2019. After that, the master will be again open for new features, while 5.3 branch will continue to get the only fixes and improvements to documentation and tools. 2-3 weeks later we should release v5.3.0, the first stable version in 5.3.x series. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

5 years, 1 month

Unresolvable destination for new added users...

by Zhan Bazarov

I can't make call through kamailio between new added users. I get 478 ... But it works for older users (who was added couple weeks ago e.g.) SIP flow, location and subscriber table the same in both cases. Could you please shed any light on this issue? *2019/10/02 11:11:20.719834 10.2.1.198:5068 <http://10.2.1.198:5068> -> 10.4.1.14:50600 <http://10.4.1.14:50600>* SIP/2.0 *478* Unresolvable destination (478/SL) Via: SIP/2.0/UDP asterisk_ip:asterisk_port;branch=z9hG4bK18626d14;rport=50600;received=10.4.1.14 From: "Admin Admin" <sip:some_user@asterisk_ip:asterisk_port>;tag=as09b1f1f3 To: <sip:some_user@kamailio_ip :kamailio_port>;tag=a1384aaeda4d71b5edb13882669b943e.8468 Call-ID: *20e023254f1b3c942a61e47d63badfd6@10.4.1.14:50600 <http://20e023254f1b3c942a61e47d63badfd6@10.4.1.14:50600>* CSeq: 102 INVITE Server: MS Lync Content-Length: 0

5 years, 1 month

← Newer
1
2
3
4
5
6
7
8
9
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 October 2019