Hi,
I am trying to use KEMI lua that needs kemix module (for KSR.kx.<...>).
I wonder if there is any pre-built Debian package that include the kemix
module, something like kamailio-<...>-modules, that I can install? Or do I
need to build from source with kemix in included_modules?
On a related question, for the kamailio-<...>-modules packages how do I
find out what modules are included in each of these package? E.g. things
like kamailio-lua-modules, kamailio-mysql-modules etc. are easy to guess,
while kamailio-nth, kamailio-utils-modules etc. are not so easy.
Thank you!
Yufei
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?
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
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
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
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
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
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