sr-users February 2020

sr-users@lists.kamailio.org

57 participants
71 discussions

by Sergey Safarov

Hi At present time kamailio config file packaged with kamailio binaries. So projects that use kamailio cannot simple package "/etc/kamailio/kamailio.cfg" file. This leads to packages conflict on RPM dists. As options we can separate "kamailio default config" and "kamailio binaries" to packages. 1) kamailio-cfg-default 2) kamailio-base This allow not install "kamailio-default" config when project provide own config file. For backward compatibility we create "kamailio" empty package that have two dependencies "kamailio-cfg-default" and "kamailio-base". What you think?

4 years, 2 months

How to implement simple presence in kamailio active-active cluster.

by Zhan Bazarov

Hello! We have next setup, which I've desribed in: http://sip-router.1086192.n5.nabble.com/Bad-request-when-INVITE-relayed-to-… Presence works fine in setup with single kamailio, without any loaded presence modules... So, I want to something wtih SUBSCRIBE and NOTIFY methods... But when I making a relay on second kamailio instance I receive 407 proxy auth required from this instance... So, its how I'm trying to implement this: part of code from route[LOCATION] case -2: if (is_method("SUBSCRIBE|NOTIFY")) { $ru = "sip:" + $tU + "@" + "ip_of_second_kam:5078"; t_relay("ip_of_second_kam", 5078); exit; } else { send_reply("405", "Method Not Allowed"); exit; } Any ideas how I can do that? Thanks. -- Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

4 years, 2 months

Re: [SR-Users] P-CSCF not starting- Kamailio 5.3

by Henning Westerholt

Hi Lanvin, (please keep the sr-users list in CC) the modules works on my machine: henning@linux:~/repositories/kamailio> killall kamailio ; ./src/kamailio -f etc/kamailio.cfg -L src/modules/ -Y /tmp -a no -E -e -d Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 192.168.188.25 [192.168.188.25]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 tcp: 192.168.188.25 [192.168.188.25]:5060 Aliases: henning@linux:~/repositories/kamailio> ps aux |grep kamailio henning 15948 0.1 0.1 166776 14900 ? S 15:33 0:00 ./src/kamailio -f etc/kamailio.cfg -L src/modules/ -Y /tmp -a no -E -e -d henning 15949 0.0 0.0 166776 4224 ? S 15:33 0:00 ./src/kamailio -f etc/kamailio.cfg -L src/modules/ -Y /tmp -a no -E -e -d [...] Here the diff to the default cfg in git master: diff --git a/etc/kamailio.cfg b/etc/kamailio.cfg index c0e618719..dbc911fb0 100644 --- a/etc/kamailio.cfg +++ b/etc/kamailio.cfg @@ -309,6 +309,14 @@ loadmodule "pike.so" loadmodule "debugger.so" #!endif + +loadmodule "ims_dialog" +loadmodule "ims_usrloc_pcscf" +loadmodule "ims_ipsec_pcscf" +loadmodule "ims_registrar_pcscf" +modparam("ims_dialog", "dlg_flag", 4) + + Cheers, Henning Am 04.02.20 um 11:55 schrieb Lanvin ADON: > > > loadmodule "ims_dialog" > loadmodule "ims_usrloc_pcscf" > #loadmodule "ims_registrar_pcscf" > #!ifdef WITH_IPSEC > loadmodule "ims_ipsec_pcscf" > #!endif > loadmodule "ims_registrar_pcscf" > > > > > Feb 4 11:53:27 pcscf kamailio[17616]: 0(17618) ERROR: > ims_registrar_pcscf [ims_registrar_pcscf_mod.c:268]: mod_init(): can't > bind ims_ipsec_pcscf > Feb 4 11:53:27 pcscf kamailio[17616]: 0(17618) ERROR: <core> > [core/sr_module.c:849]: init_mod(): Error while initializing module > ims_registrar_pcscf > (/opt/pcscf/lib64/kamailio/modules/ims_registrar_pcscf.so) > Feb 4 11:53:27 pcscf kamailio[17616]: ERROR: error while initializing > modules > Feb 4 11:53:28 pcscf kamailio[17620]: 0(17622) ERROR: > ims_registrar_pcscf [ims_registrar_pcscf_mod.c:268]: mod_init(): can't > bind ims_ipsec_pcscf > Feb 4 11:53:28 pcscf kamailio[17620]: 0(17622) ERROR: <core> > [core/sr_module.c:849]: init_mod(): Error while initializing module > ims_registrar_pcscf > (/opt/pcscf/lib64/kamailio/modules/ims_registrar_pcscf.so) > Feb 4 11:53:28 pcscf kamailio[17620]: ERROR: error while initializing > modules > Feb 4 11:53:28 pcscf kamailio[17623]: 0(17625) ERROR: > ims_registrar_pcscf [ims_registrar_pcscf_mod.c:268]: mod_init(): can't > bind ims_ipsec_pcscf > Feb 4 11:53:28 pcscf kamailio[17623]: 0(17625) ERROR: <core> > [core/sr_module.c:849]: init_mod(): Error while initializing module > ims_registrar_pcscf > (/opt/pcscf/lib64/kamailio/modules/ims_registrar_pcscf.so) > Feb 4 11:53:28 pcscf kamailio[17623]: ERROR: error while initializing > modules > Feb 4 11:53:29 pcscf kamailio[17626]: 0(17628) ERROR: > ims_registrar_pcscf [ims_registrar_pcscf_mod.c:268]: mod_init(): can't > bind ims_ipsec_pcscf > Feb 4 11:53:29 pcscf kamailio[17626]: 0(17628) ERROR: <core> > [core/sr_module.c:849]: init_mod(): Error while initializing module > ims_registrar_pcscf > (/opt/pcscf/lib64/kamailio/modules/ims_registrar_pcscf.so) > Feb 4 11:53:29 pcscf kamailio[17626]: ERROR: error while initializing > modules > Feb 4 11:53:29 pcscf kamailio[17629]: 0(17631) ERROR: > ims_registrar_pcscf [ims_registrar_pcscf_mod.c:268]: mod_init(): can't > bind ims_ipsec_pcscf > Feb 4 11:53:29 pcscf kamailio[17629]: 0(17631) ERROR: <core> > [core/sr_module.c:849]: init_mod(): Error while initializing module > ims_registrar_pcscf > (/opt/pcscf/lib64/kamailio/modules/ims_registrar_pcscf.so) > Feb 4 11:53:29 pcscf kamailio[17629]: ERROR: error while initializing > modules > > > > > > > > > On Tue, Feb 4, 2020 at 11:46 AM Henning Westerholt <hw(a)skalatan.de > <mailto:hw@skalatan.de>> wrote: > > Hello Lanvin, > > try to load it before and see if it starts then. > > Cheers, > > Henning > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com <https://gilawa.com/> > > *From:* Lanvin ADON <lanvin.adon(a)gmail.com > <mailto:lanvin.adon@gmail.com>> > *Sent:* Tuesday, February 4, 2020 11:45 AM > *To:* Henning Westerholt <hw(a)skalatan.de <mailto:hw@skalatan.de>> > *Subject:* Re: [SR-Users] P-CSCF not starting- Kamailio 5.3 > > Hello Henning > > ims_ipsec_pcscf is loaded after. > > loadmodule "ims_dialog" > loadmodule "ims_usrloc_pcscf" > loadmodule "ims_registrar_pcscf" > #!ifdef WITH_IPSEC > loadmodule "ims_ipsec_pcscf" > #!endif > > Thanks > > Lanvin ADON > > On Tue, Feb 4, 2020 at 11:06 AM Henning Westerholt <hw(a)skalatan.de > <mailto:hw@skalatan.de>> wrote: > > Hello, > > just a guess, but do you load the ims_ipsec_pcscf module > before the ims_registrar_pcscf module? > > Cheers, > > Henning > > -- > > Henning Westerholt – https://skalatan.de/blog/ > > Kamailio services – https://gilawa.com <https://gilawa.com/> > > *From:* sr-users <sr-users-bounces(a)lists.kamailio.org > <mailto:sr-users-bounces@lists.kamailio.org>> *On Behalf Of > *Lanvin ADON > *Sent:* Tuesday, February 4, 2020 8:54 AM > *To:* sr-users(a)lists.kamailio.org > <mailto:sr-users@lists.kamailio.org> > *Subject:* [SR-Users] P-CSCF not starting- Kamailio 5.3 > > Hi All, > > I'm installing an IMS core with Kamailio 5.3 release. The > P-CSCF is not starting with the following error message. > > Feb 4 07:01:32 pcscf kamailio[13878]: 0(13880) DEBUG: <core> > [core/sr_module.c:638]: find_mod_export_record(): export of > <bind_ims_ipsec_pcscf> not found (flags 0) > Feb 4 07:01:32 pcscf kamailio[13878]: 0(13880) ERROR: > ims_registrar_pcscf [ims_registrar_pcscf_mod.c:268]: > mod_init(): can't bind ims_ipsec_pcscf > Feb 4 07:01:32 pcscf kamailio[13878]: 0(13880) ERROR: <core> > [core/sr_module.c:849]: init_mod(): Error while initializing > module ims_registrar_pcscf > (/opt/pcscf/lib64/kamailio/modules/ims_registrar_pcscf.so) > Feb 4 07:01:32 pcscf kamailio[13878]: ERROR: error while > initializing modules > > For the configuration file, I'm using the example files in the > source. > > > > -- > > Regards > > Lanvin ADON > > > > -- > > Cordialement, > > Lanvin ADON > > > > -- > > */ > /* > > Cordialement, > > Lanvin ADON -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com Kamailio Merchandising - https://skalatan.de/merchandising/

4 years, 2 months

Re: [SR-Users] P-CSCF not starting- Kamailio 5.3

by Henning Westerholt

Hello Lanvin, try to load it before and see if it starts then. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Lanvin ADON <lanvin.adon(a)gmail.com> Sent: Tuesday, February 4, 2020 11:45 AM To: Henning Westerholt <hw(a)skalatan.de> Subject: Re: [SR-Users] P-CSCF not starting- Kamailio 5.3 Hello Henning ims_ipsec_pcscf is loaded after. loadmodule "ims_dialog" loadmodule "ims_usrloc_pcscf" loadmodule "ims_registrar_pcscf" #!ifdef WITH_IPSEC loadmodule "ims_ipsec_pcscf" #!endif Thanks Lanvin ADON On Tue, Feb 4, 2020 at 11:06 AM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote: Hello, just a guess, but do you load the ims_ipsec_pcscf module before the ims_registrar_pcscf module? Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Lanvin ADON Sent: Tuesday, February 4, 2020 8:54 AM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] P-CSCF not starting- Kamailio 5.3 Hi All, I'm installing an IMS core with Kamailio 5.3 release. The P-CSCF is not starting with the following error message. Feb 4 07:01:32 pcscf kamailio[13878]: 0(13880) DEBUG: <core> [core/sr_module.c:638]: find_mod_export_record(): export of <bind_ims_ipsec_pcscf> not found (flags 0) Feb 4 07:01:32 pcscf kamailio[13878]: 0(13880) ERROR: ims_registrar_pcscf [ims_registrar_pcscf_mod.c:268]: mod_init(): can't bind ims_ipsec_pcscf Feb 4 07:01:32 pcscf kamailio[13878]: 0(13880) ERROR: <core> [core/sr_module.c:849]: init_mod(): Error while initializing module ims_registrar_pcscf (/opt/pcscf/lib64/kamailio/modules/ims_registrar_pcscf.so) Feb 4 07:01:32 pcscf kamailio[13878]: ERROR: error while initializing modules For the configuration file, I'm using the example files in the source. -- Regards Lanvin ADON -- Cordialement, Lanvin ADON

4 years, 2 months

P-CSCF not starting- Kamailio 5.3

by Lanvin ADON

Hi All, I'm installing an IMS core with Kamailio 5.3 release. The P-CSCF is not starting with the following error message. Feb 4 07:01:32 pcscf kamailio[13878]: 0(13880) DEBUG: <core> [core/sr_module.c:638]: find_mod_export_record(): export of <bind_ims_ipsec_pcscf> not found (flags 0) Feb 4 07:01:32 pcscf kamailio[13878]: 0(13880) ERROR: ims_registrar_pcscf [ims_registrar_pcscf_mod.c:268]: mod_init(): can't bind ims_ipsec_pcscf Feb 4 07:01:32 pcscf kamailio[13878]: 0(13880) ERROR: <core> [core/sr_module.c:849]: init_mod(): Error while initializing module ims_registrar_pcscf (/opt/pcscf/lib64/kamailio/modules/ims_registrar_pcscf.so) Feb 4 07:01:32 pcscf kamailio[13878]: ERROR: error while initializing modules For the configuration file, I'm using the example files in the source. -- Regards Lanvin ADON

4 years, 2 months

parallel forking in combination with rtpengine

by michael.willow＠web.de

Hi everbody, I encountered an issue with my Kamailio in combination with Rtpengine. I wondered if anybody got a solution or a hint as this issue is only in combination with special parallel forked calls. I sent a call from my SIP gateway via a Kamailio to another SIP provider. The other SIP provider or the B-user seems to use a parallel forking as I receive 183 Session Progress and 180 Ringing with different to-tags. My kamailio is using a Rtpengine to relay the media from my SIP gateway to the other SIP provider. As Kamailio receives two different to-tags that include a SDP body rtpengine_manage makes Rtpengine to change RTP port. Some short example (cut down to the important messages): a-gateway kamailio b-provider | INVITE Port 16890 | INVITE Port 20400 | | ------------------------> | --------------------------> | | | | | 180 to-tag 1 / no SDP | 180 to-tag 1 / no SDP | | <------------------------ | <------------------------- | | | | | 183 to-tag 2 / Port 20408 | 183 to-tag 2 / Port 46298 | | <------------------------ | <------------------------- | | | | | | | | RTP | RTP | | Port 16890 <---- Port 20408 | Port 20400 <---- Port 46298 | | | | | | | | RTP | RTP | | Port 16890 ----> Port 20408 | Port 20400 ----> Port 46298 | | | | | | | | 180 to-tag 2 / Port 20408 | 180 to-tag 0 / Port 46298 | | <------------------------ | <------------------------- | | | | | | | | 200 OK to-tag 1 / Port 20408 | 200 OK to-tag 1 / Port 46298 | | <------------------------ | <------------------------- | | | | | | | | RTP | RTP | | Port 16890 <---- Port 20408 | Port 20400 <---- Port 46298 | | | | | | | | RTP | RTP | | Port 16890 ----> Port 20408 | Port 20418 ----> Port 46298 | Kamailio receives INVITE from a-gateway with rtp port 16890 and rtpengine rewrites it with port 20400 to b-provider. b-provider sends 180 ringing from to-tag 1 and no SDP which is just passed through kamailio to a-gateway. b-provider sends 183 progress from to-tag 2 and SDP with port 46298 to kamailio. rtpengines rewrites the sdp port to 20408 which is passed to a-gateway. b-provider start sending RTP via the negotiated ports which is passed correctly to a-gateway. b-provider sends 180 ringing from to-tag 2 with the same SDP. Rewritten and passed to a-gateway. b-provider sends 200 OK on Invite. This 200 Ok is from to-tag 1 but including the same SDP endpoint as to-tag 2 used before. Media from b-provider via rtpengine to a-gateway is passed the same way as before. Media from a-gateway to rtpengine is passed the same way as before. Media from rtpengine is passed with a different source port to b-provider. As this port was not announced in the callflow b-provider blocks the traffic. Any ideas how to fix this issue or force rtpengine to stay on the same port? Thanks Michael

4 years, 2 months

P-CSCF not starting- Kamailio 5.3

by Lanvin ADON

4 years, 2 months

Call merging issues on cellular network

by Gaurav Bmotra

Hi I m using kamailio 5.3 I m trying to merge the call on cellular network but is not working. As on WiFi it is working fine . Any one can help me Thank you

4 years, 2 months

Kamailio TLS server hello without any client certificate request

by Patrick Murphy

Hey guys - I'm using the following settings on my Kamailio config: modparam("tls", "low_mem_threshold2", 1024) modparam("tls", "tls_force_run", 1) modparam("tls", "tls_disable_compression", 1) modparam("tls", "ssl_max_send_fragment", 4096) modparam("tls", "renegotiation", 0) modparam("tls", "low_mem_threshold1", 2048) modparam("tls", "require_certificate", 1) When a client attempts to connect to Kamailio, the server hello it receives does *not* contain the client certificate request. And I've noticed that kamailio starts with: tls [tls_domain.c:694]: set_verification(): TLSs<default>: No client certificate required and no checks performed tls [tls_domain.c:320]: fill_missing(): TLSs<default>: require_certificate=0 Complete version output: kamailio 5.1.1 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, 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_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. Any hints?

4 years, 2 months

Dialog module - default_timeout behavior

by Gholamreza Sabery

Hi, According to the documentation default_timeout is "The default dialog timeout (in seconds), in the absence of a custom value provided in an AVP". There is also a "send_bye" option which can automatically send a BYE message on dialog timeout. Suppose that a user sends an INVITE and the call is successful (200). He talks more than default_timeout seconds (so there is not BYE for more than default_timeout seconds). This means that when the user actually sends BYE, the dialog is already terminated by the dialog module? Regards

4 years, 2 months

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 February 2020