Please try to keep the mailing list in loop so that it helps others as well
facing this issue.
I believe this was resolved in 5.3.3 branch not sure why you are facing
this issue. Anyways, make sure that modules loaded in kamailio.cfg of PCSCF
is in following order
loadmodule "ims_dialog"
Hello,
I do not work with IMS modules, but if you find some inconsitency
between the code and the documentation, just make a PR to fix the
documentation.
Cheers,
Daniel
On 17.06.20 14:46, Martin W Woscek wrote:
>
> Hello,
>
>
>
> I’m revisiting some initial issues I had with P-CSCF. I could
Very good idea with rpc command or json module, never mind about it.
For the moment I will try with that, but any way will be good to have a
function in the dialog module for that.
Thanks.
În mie., 24 iun. 2020 la 09:45, Daniel-Constantin Mierla
a scris:
> Hello,
>
> if there is a rpc command
Hi Supreeth,
I have registered the user bob .. and it is already stored in hss database
also . Registration is successful with that user .
When i make a call from alice to bob .. in call establishment , it is
throwing this error.
In scscf logs , I am able to see registered user not found. But
There is no other IPSec configuration needed apart from running Kamailio
P-CSCF and UE sending a SIP Register with Security-Client information for
IPSec creation. Kamailio IMS IPSec module creates IPSec tunnels using
Netlink library.
Best Regards,
Supreeth
On Wed, 24 Jun 2020 at 13:29, Pavithra
Hi ,
Could you please tell how to configure ipsec (general configuration not
related to kamailio).
Thanks,
Pavithra
On Wed, Jun 24, 2020 at 2:12 PM supreeth herle
wrote:
> reason=404 (Not Found - destination user not found on this S-CSCF)]
>>
>
> Please check your IMPU for the IMS user in the
On Wednesday 24 June 2020 at 13:29:37, Pavithra Mohanraja wrote:
> Hi ,
>
> Could you please tell how to configure ipsec (general configuration not
> related to kamailio).
Surely this question is better asked on a Freeswan / Strongswan (or whatever
name your operating system uses for its IPsec
Hi,
I am not sure if this issue comes in 5.3.4 version .
The below error i am facing in pcscf .
0(4152) ERROR:
Hello Daniel,
Thank you for the reply. Sure, I'll send one to your private email address.
Thanks!
BR,
George
On Wed, 24 Jun 2020 at 12:06, Daniel-Constantin Mierla
wrote:
> Hello,
>
> can you send a pcap with a call reproducing such case? I can check it with
> the c code and see if something
Hi
Reusing of TLS ok only in the case if you have the wildcard certificate and
all your domains are subdomains.
Otherwise it will not work. MS checks if RR FQDN matches your TLS
certificate.
ср, 24 июн. 2020 г. в 11:14, Daniel-Constantin Mierla :
> Hello,
>
> MS Teams uses the Record-Route
This means the HSS had answered the user is not known in this domain
(lir_term_user_unknown), but then the DNS server insists this telephone number
should be handled by our domain ($rd == NETWORKNAME).
Just enter the user to the HSS database - if it shall be handled by this domain
-
Or
>
> reason=404 (Not Found - destination user not found on this S-CSCF)]
>
Please check your IMPU for the IMS user in the IMS HSS (e.g. FHoSS or any
other HSS you are using to enter IMS user details). SCSCF is not able to
find a registered user with that IMPU (i am assuming that you are getting
Hello,
if there is a rpc command for it, then maybe you can leverage the
jsonrpc_exec() from jsonrpcs module and walk through json using jansson.
If not, then such feature has to be added within the c code and exported
as function to config.
Cheers,
Daniel
On 18.06.20 13:44, Ilie Soltanici
Hello,
MS Teams uses the Record-Route header to match the PBX/group domain. In
my experience testing with MS Teams so far, reusing the TLS connection
is ok when having multiple domains.
Cheers,
Daniel
On 12.06.20 22:28, Leanderson Correia wrote:
> I'm testing here to use multiple domains with
Hello,
I suggest to run kamailio with debug=3 in kamailio.cfg to see if the
ringing state is published by dialog/pua_dialoginfo during the call setup.
On the other hand, the dialoginfo is a different event than user/device
presence state, so the endpoints have to subscribe for both dialog info
Hello,
I never faced it myself, the functionality was added based on a report
from the community more for troubleshooting purposes to see if the
transactions can still be freed after timer was elapsed and they were no
longer cleaned.
IIRC, the report said that there was no activity reported in
Hello,
I haven't cross compiled myself, but there is a makefile flag
CROSS_COMPILE that you can set in such cases -- the Makefile of the
modules sets the path to includes and libs based on it. You may need to
set other Makefile variables to get it done, look in the
src/Makefile.defs to see most
Hello,
can you send a pcap with a call reproducing such case? I can check it
with the c code and see if something is mismatched.
Cheers,
Daniel
On 09.06.20 13:00, George Diamantopoulos wrote:
> Hello again,
>
> This might turn out to be a bug, but I'm posting here first because my
> config is
Hi,
I am facing below error in kamailio-ims 5.3.4 version.
reason=404 (Not Found - destination user not found on this S-CSCF)]
could you please help me how should i proceed with and where the
registration details will be stored in kamailio ims.
It fails at this line in kamailio.cfg file in
Hello,
is Kamailio listening on other sockets towards UE other than the IPSec
tunnel?
Cheers,
Daniel
On 17.06.20 04:49, BALL SUN wrote:
> Hi
>
> We have setup UE with Kamailio IMS, and after the registration is
> successful. The 2nd SIP REGISTER is sent from UE to P-CSCF through
> IPSEC tunnel.
Hello,
Kamailio is agnostic of the media content type. If both endpoints
support video, then the call just works. The rtpproxy or rtpengine is
needed if you have to deal with nat traversal.
For voice conferencing you need sip media servers such as asterisk,
freeswitch or sems (to list a few from
Hello,
for the records, jsonrpc command panel has to be installed/configured:
- http://kb.asipto.com/siremis:install53x:jsonrpc-commands
Cheers,
Daniel
On 12.06.20 21:32, Henning Westerholt wrote:
> Hello,
>
> look for the option in the GUI to execute arbitrary RPC commands. You might
>
Hello,
the code seems to have it. Can you provide the full log messages printed
in such case?
Cheers,
Daniel
On 19.06.20 15:46, Martin W Woscek wrote:
>
> Hello all,
>
>
>
> Im trying to call t_relay() with host and port as documented in:
>
>
Hello,
Kamailio is not generating the 200ok for INVITE (calls), it just sends
out what it received from end point, after consuming own Via header (of
course, other headers can be changed based on config rules, but Kamailio
is not in charge of setting To-tag).
Cheers,
Daniel
On 19.06.20 21:19,
Hi,
The issue is the P should be sending to the UE not back to the I like the
failed flow:
Asterisk16-[phone] --->ICSCF--->S-CSCF--->P-CSCF--->I-CSCF ---> [604 HSS user
unknown] to Asterisk16[phone]
The successful call should look like:
Asterisk16-[phone]
Greetings,
I'm trying to clean a SQL result using "sql_result_free()" but i'm not
having success.
Can you please verify if i'm doing anything wrong here?
This is my code :
xerr("Pre clean [0] = Iterator 0 =
$xavp(Cli_PICKER_Default_Search_Result[0]=>Code)");
I haven't cross compiled in a long time ...
For proper cross-compilation, the CROSS_COMPILE flag must be set to
something, then the LOCALBASE and SYSBASE should point to the staging
directory where the toolchain and all the libraries and include files
for the target platform are present.
Extra
thank you. I'll check soon.
Regards
---
I'm SoCIaL, MayBe
On 24/06/20 3:57, Daniel-Constantin Mierla wrote:
Hello,
for the records, jsonrpc command panel has to be installed/configured:
- http://kb.asipto.com/siremis:install53x:jsonrpc-commands
Cheers,
Daniel
On 12.06.20 21:32, Henning
Just to clarify what we are seeing, here is a packet from the INVITE from the
S-CSCF (6060) to the P-CSCF(4060). I have eliminated the S-CSCF as this packet
looks correct.
The P-CSCF is not handling the request URI correctly, and simply sends it back
to the I-CSCF where I-CSCF cannot find the
yes. when the HSS profile is not found, it did not route to DNS/ENUM
to check, which portion of configuration should I check?
On Wed, Jun 24, 2020 at 5:31 PM Valentin Christoph
wrote:
>
> This means the HSS had answered the user is not known in this domain
> (lir_term_user_unknown), but then
Hi
I can see that it is not in the IPSEC tunnel. below is the SIP OPTIONS
from two UEs with P-CSCF.
10:43:04.072360 IP 192.168.11.66.5060 > 192.168.10.42.9701: SIP:
OPTIONS sip:45400237@192.168.10.42:9700 SIP/2.0
10:43:04.072592 IP 192.168.11.66.5060 > 192.168.10.44.6602: SIP:
OPTIONS
Hi
can I simply change all of the t_relay to t_relay_to_tcp in P-CSCF,
I-CSCF and S-CSCF?
how I can make sure it will not affect "SIP client <-> P-CSCF (either
UDP or TCP, based on the transport tag) "?
On Sun, Jun 7, 2020 at 6:21 PM Henning Westerholt wrote:
>
> Hello,
>
> there is not a
I don't know your DNS server nor your addressing plan. Probably to modify / add
some zone files
You must be sure to forward the ranges of telephone numbers that you want to
forward to the other domain.
Actually, it DID the request to the DNS/ENUM, but the result was "keep the
domain as it is"
HI
We noticed an issue here, not sure is it related to HSS profile.
the setting is like this
Caller: MSISDN-A, IMSI-A
Called: MSISDN-B, IMSI-B
Both UEs can be registered based on IMSI number. Also the
corresponding tel:MSISDN is added to the corresponding IMPU.
now, when we make a call from
Hello
I may not describe the problem clearly. When a UE call a number to the
Kamailio IMS core, says, the number is 12345678, the R-URI in the SIP
INVITE is
"sip:12345678;phone-context=ims.mnc001.mcc001.3gppnetwork@ims.mnc001.mcc001.3gppnetwork.org;user=phone",
Kamailio P-CSCF pass to INVITE
Hi Supreeth,
I have followed your guide to build kamailio IMS
https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/
services are running fine .
when i try to make a call . registration fails with 478 unresolvable
destination
93(25632) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route
36 matches
Mail list logo
