- sr-users - kamailio.org

Re: [SR-Users] Call limit through shared database
by Olli Attila 04 Oct '19

04 Oct '19

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

1 0

Record-Route management
by Duarte Rocha 03 Oct '19

03 Oct '19

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

2 2

string manipulation
by David Villasmil 03 Oct '19

03 Oct '19

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

2 2

Get destination out of _dsdst_
by David Villasmil 03 Oct '19

03 Oct '19

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

2 2

Development is open for future release of v5.4.x series
by Daniel-Constantin Mierla 03 Oct '19

03 Oct '19

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

1 0

Branch 5.3 has been created
by Daniel-Constantin Mierla 03 Oct '19

03 Oct '19

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

1 0

Branching 5.3
by Daniel-Constantin Mierla 02 Oct '19

02 Oct '19

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

1 1

Unresolvable destination for new added users...
by Zhan Bazarov 02 Oct '19

02 Oct '19

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

3 5

BLF 'NOTIFY' not working
by Petarr Jones 02 Oct '19

02 Oct '19

Hi I am using Kamailio 5.2 with the following PRESENCE modules and parameters: loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "presence_reginfo.so" modparam("presence", "db_url", DBURL) modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) modparam("presence_xml", "disable_bla", 0) modparam("presence_xml", "integrated_xcap_server", 1) I have a Yealink T28P phone which has two lines/extensions successfully registered with Kamailio 5.2. When I setup the BLF light to monitor one of the extensions, I get the correct SUBSCRIBE record but the NOTIFY record is sent over and over again until it fails. ----------------------------------------------------------------------------------------------------------- NOTIFY sip:101@192.168.1.123:5062 SIP/2.0 Via: SIP/2.0/UDP 45.45.45.45;branch=z9hG4bKd16c.03b5bc97000000000000000000000000.0 To: <sip:101@45.45.45.45>;tag=1366853594 From: <sip:104@45.45.45.45>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-e6c3 CSeq: 2 NOTIFY Call-ID: 594386350(a)192.168.1.123 Content-Length: 0 User-Agent: kamailio (5.2.4 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:45.45.45.45:5060;transport=udp> ----------------------------------------------------------------------------------------------------------- When I register the phone with Freeswitch instead and run the same test, the NOTIFY works and I get a much longer NOTIFY message ----------------------------------------------------------------------------------------------------------- NOTIFY sip:100@192.168.1.123:5064 SIP/2.0 Via: SIP/2.0/UDP 66.66.66.66;rport;branch=z9hG4bK1mXej9r2605UB Route: <sip:55.55.55.55:5064>;transport=udp Max-Forwards: 70 From: <sip:102@66.66.66.66>;tag=xUoVghM5syHc To: "100" <sip:100@66.66.66.66>;tag=1720892352 Call-ID: 2583553127(a)192.168.1.123 CSeq: 1178415701 NOTIFY Contact: <sip:102@66.66.66.66:5060> User-Agent: FreeSWITCH-mod_sofia/1.10.1-release-12-f9990221e6~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Event: dialog Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Subscription-State: active;expires=1800 Content-Type: application/dialog-info+xml Content-Length: 149 xml version="1.0"?> dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:102@66.66.66.66"> dialog-info> ----------------------------------------------------------------------------------------------------------- Should the message coming from Kamailio contain more data or is that not the issue. Should I be including other modules also? All guidance would be appreciated.

2 4

Call limit through shared database
by Olli Attila 01 Oct '19

01 Oct '19

Hello, I have 2 kam instances using one shared database and both kam servers running the same routing logic code. Kamailio servers are configured to use the same database as dialog backend. I am limiting the concurrent dialogs in the following way but it seems that kamailio is using its own memory to read profile size rather than the db. Second kam is not aware of the dialog profiles that the first kam wrote to the shared db. Is there a way to get multiple kam instances to read profile size from the same database when calling the get_profile_size function? modparam("dialog", "profiles_with_value", "concurrent_calls") modparam("dialog", "dlg_flag", 4) modparam("dialog", "db_url", DBURL) modparam("dialog", "db_mode", 1) route[LIMIT_CALLS] { if (!dlg_isflagset("1")) { # $td – gateways, $fu - user if (get_profile_size("concurrent_calls", "$fu", "$avp(calls)")) { if ($avp(calls) >= 3) { xlog("L_INFO", "Concurrent calls $fu at limit"); send_reply("503", "Calls limit reached"); exit; } else { dlg_manage(); dlg_setflag("1"); set_dlg_profile("concurrent_calls", "$fu"); } } } } Cheers, Olli

5 8

Kamailio Charging
by Jack R 01 Oct '19

01 Oct '19

Hi, Does Kamailio provide some charging functionality? If yes, then how do we go about setting it up? like what module/configuration? and Database tables to see/touch? I see these links: https://www.kamailio.org/docs/modules/4.2.x/modules/ims_charging.html https://www.kamailio.org/w/2013/07/documentation-on-charging-in-ims/ Or Do we need separate software like example cgrates for charging? (also a side question do we have any other open-source like cgrates) Any information would be helpful. Thanks and Regards, Jack.

3 3

Relay Request
by Maryam Baghdadi 29 Sep '19

29 Sep '19

Hello everyone, Is it possible to relay INVITE request to another server after receiving "180 Ringing" response ??? I would like to activate CRBT(ring back tone) service and according to my research after receiving 180 ringing media playing request should be sent to a media server .

3 2

Re: [SR-Users] Relay Request
by Mojtaba 29 Sep '19

29 Sep '19

Would you please keep "Users Mailing List" <sr-users(a)lists.kamailio.org> in tracking. :) That is straight froward. There is no change in sending the request from Kamailio to Asterisk. In Asterisk you could use Progress command to support Media-Relay. In additional use Dial command (with r or m option for supporting CRBT ). With Best Regards On Sun, Sep 29, 2019 at 8:52 AM Maryam Baghdadi <maryam.baghdadi(a)gmail.com> wrote: > Hello Mojtaba, > I chose asterisk as media server and some services like voice mail > provided ... about CRBT I know asterisk have this service but I don't know > how to send this request from kamailio to asterisk.. > do you know kamailio can provide this service itself or not??? > could you pls explain more > > thanks > > > On Sat, Sep 28, 2019, 1:48 PM Mojtaba <mespio(a)gmail.com wrote: > >> Hello, Some consideration would be needed: >> 1) SS7 for PSTN subscriber to support media-relay >> 2)Progress capability for SIP subscriber. >> 3) Media server to support ring-back VAS service >> You should check enabling this service or not during MO procedure. >> With Best Regards. >> >> On Sat, Sep 28, 2019 at 1:19 PM Maryam Baghdadi < >> maryam.baghdadi(a)gmail.com> wrote: >> >>> Hello everyone, >>> >>> Is it possible to relay INVITE request to another server after receiving >>> "180 Ringing" response ??? >>> I would like to activate CRBT(ring back tone) service and according to >>> my research after receiving 180 ringing media playing request should be >>> sent to a media server . >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> sr-users(a)lists.kamailio.org >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >> >> >> -- >> --Mojtaba Esfandiari.S >> > -- --Mojtaba Esfandiari.S

1 0

tcp_accept_haproxy questions
by Grant Bagdasarian 27 Sep '19

27 Sep '19

Hello, The docs mention regular TCP connections not being accepted anymore once this is enabled. I assume UDP is unaffected and both proxyprotocol and udp may live side by side? Also, does this play nicely with WebSockets? Taking into account the Websocket connection being setup through a proxy protocol supporting proxy. Regards, Grant

1 0

wiki on $sht(htable=>key)
by Juha Heinanen 27 Sep '19

27 Sep '19

Kamailio wiki does not tell what result $sht(htable=>key) gives if the key is not found in htable. It would be nice if it did. -- Juha

1 0

KEMI dialplan dp_replace returns not implemented yet
by Grant Bagdasarian 26 Sep '19

26 Sep '19

Hello, The dp_replace KEMI function is returning the message "not implemented yet". Function call: _.dialplan.dp_replace(1, _.pv.get("$rU"), "$var(dpr)") app_python3 ¡apy_kemi.c:872¿: sr_apy_kemi_f_pv_get_mode(): pv get: $rU <core> ¡core/pvapi.c:398¿: pv_cache_lookup(): pvar ¡$rU¿ found in cache app_python3 ¡apy_kemi.c:193¿: sr_apy_kemi_exec_func_ex(): execution of method: dp_replace app_python3 ¡apy_kemi.c:338¿: sr_apy_kemi_exec_func_ex(): not implemented yet app_python3 ¡apy_kemi.c:872¿: sr_apy_kemi_f_pv_get_mode(): pv get: $var(dpr) <core> ¡core/pvapi.c:371¿: pv_cache_add(): pvar ¡$var(dpr)¿ added in cache Using Kamailio 5.2.4 Docker image. version: kamailio 5.2.4 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 6.3.0 Regards, Grant

2 4

Kamailio Rasberry Pi benchmark results
by Henning Westerholt 26 Sep '19

26 Sep '19

Hello, as promised here the report on my Rasberry Pi benchmarks. The numbers were quite impressive! - 3000 registration requests per second (in-memory usrloc) - 300 calls per second for a p2p call (default cfg, only SIP traffic) - about 18 MBit/s incoming and 16 MBit/s outgoing SIP peak traffic could be processed All the details about the test setup and more numbers in the blog post: https://skalatan.de/blog/kamailio-rpi-benchmark Cheers, Henning -- Kamailio Merchandising - https://skalatan.de/merchandising/ Kamailio services - https://skalatan.de/services Henning Westerholt - https://skalatan.de/blog/

1 0

Kamailio v5.1.9 Released
by Daniel-Constantin Mierla 26 Sep '19

26 Sep '19

Hello, Kamailio SIP Server v5.1.9 stable release is out. This is a maintenance release of the previous stable branch, 5.1, that includes fixes since the release of v5.1.8. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.9 or to v5.2.x series. For more details about version 5.1.9 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/09/kamailio-v5-1-9-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the branch 5.1 is the previous stable branch. The latest stable branch is 5.2, at this time with v5.2.4 being released out of it. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020 -- www.kamailioworld.com

2 1

ims_ipsec_pcscf: maybe core dump due to maximum count of connections
by Valentin Christoph 26 Sep '19

26 Sep '19

Hi, Doing some tests with the module ims_ipsec_pcscf, we encountered a core dump during startup of Kamailio and would like to understand the correct behavior. We assume the ipsec_max_connections parameter was the root cause --> how many max connections have been actually tested? Can it be that ipsec_client-port and ipsec_server_port were too close together (some overlapping)? Thx Christoph

2 1

install with kazoo
by Benoit Chesneau 26 Sep '19

26 Sep '19

Hi all, Can anyone share a simple configuration to use with kazoo or a link to it? I'm struggle in having it setup without using the defaults packages. Ideally it should dispatch messages to freeswitch. Any help is welcome :) Benoît

3 2

Planning the release of v5.1.9
by Daniel-Constantin Mierla 26 Sep '19

26 Sep '19

Hello, I am considering to release v5.1.9 out of the branch 5.1 during the next week, on Tuesday (Sep 24) or Thursday (Sep 26). As usual, if you are aware of issues not reported on tracker or commits that should be backported to branch 5.1, do report them asap in order to get them a chance to be sorted out. 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

1 2

Kamailio ARM support improved, tests
by Henning Westerholt 25 Sep '19

25 Sep '19

Hello, as part of the testing for 5.3.0 I looked into the ARM support in Kamailio. Previously the core used some deprecated assembler functions for atomic operations (locking etc..). There was also no native support for the ARM v7 architecture available. After several fixes and extensions both topics should be now much improved. I did today a lot of tests on Rasberry Pi and also some benchmarking (will send another e-mail when the report is ready). If you use Kamailio on another embedded ARM (>= v6) system it would be great if you also give it a try. Use git master revision ccc0eb6d12a1d (or newer) for your tests. Please report eventual issues to the sr-dev list. Cheers, Henning -- Kamailio Merchandising - https://skalatan.de/merchandising/ Kamailio services - https://skalatan.de/services Henning Westerholt - https://skalatan.de/blog/

1 0

Development for v5.3.x is frozen
by Daniel-Constantin Mierla 25 Sep '19

25 Sep '19

Hello, the formal notification that the development for the next major version 5.3.0 is now frozen. The focus has to be on testing the master branch. Also, the master branch should not get commits with new features till the branch 5.3 is created, expected to happen in 2-4 weeks, a matter of how testing goes on. Meanwhile, the commits with new features in the C code can be pushed to personal branches, pull requests can still be done, but they will be merged after branching 5.3. Can still be done commits with documentation improvements, enhancements to related tool (e.g., kamctl, kamcmd) and exporting missing KEMI functions to the modules already exporting most of the other functions (done for previous releases, because likely that was a fail to notice, all functions should be exported for a module at the same time). Once the branch 5.3 is created, new features can be pushed again to master branch as usual. From that moment, the v5.3.0 should be out very soon, time used for further testing but also preparing the release of packages. If someone is not sure if a commit brings a new feature, just make a pull request and it can be discussed there on github portal or via sr-dev mailing list. A summary of what is new in upcoming 5.3 is collected at: * https://www.kamailio.org/wiki/features/new-in-5.3.x Upgrade guidelines will be collected at: * https://www.kamailio.org/wiki/install/upgrade/5.1.x-to-5.3.0 Everyone is more than welcome to contribute to the above wiki pages, especially to the upgrade guidelines, to help everyone else during the migration process from v5.2.x to 5.3.x. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 8

Extract user from AOR
by Grant Bagdasarian 25 Sep '19

25 Sep '19

Hello, I've been trying to extract the user part from an AoR using transformations in Python (KEMI), but without success. The reg_fetch_contacts function has been called successfully before trying to access the AoR. None of the below statements work for me. They all return None. user = _.pv.get("$(ulc(profile=>aor){uri.user})") user = _.pv.get("$(ulc(profile=>aor){tobody.user})") or _.pv.sets("$var(aor)", _.pv.get("$(ulc(profile=>aor))")) user = _.pv.get("$(var(aor){tobody.user})") user = _.pv.get("$(var(aor){uri.user})") I'm not sure what's causing the None result. Could it be the curly braces being used for string interpolation in Python? Or are these transformations not able to extract the value since the AoR has the following format: user@domain? If the same can be accomplished in another way, please let me know. Regards, Grant

2 1

Question
by Shahdee Nelson 25 Sep '19

25 Sep '19

With your software would I be able to create, and modify VOIP lines? As in saying would I be able to provide VOIP numbers that can make outbound calls to USA from USA?

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