sr-users September 2024

sr-users@lists.kamailio.org

37 participants
46 discussions

Kamailio Developers Meeting, Nov 19-20, 2024, in Dusseldorf
by Daniel-Constantin Mierla 14 Nov '24

14 Nov '24

Hello, Kamailio SIP Server project is organizing another meeting of its developers and community members during November 19-20, 2024 (Tue-Wed), hosted again by sipgate.de in Dusseldorf, Germany. The event is intended to facilitate the interaction between Kamailio developers and contributors in order to offer a convenient environment for working together on several topics of high interest for the project, including writing code for Kamailio and its tools, improving documentation, or discuss about future development. Everyone from the community is welcome to join, developer or user interested in helping the project. Please note we have a limited capacity of seats in the meeting room, the main policy for accepting participants being first come first server. Also, very important to be aware that this is not an event to learn how to use Kamailio. More details about the event, the venue, how to register, are available at: * https://www.kamailio.org/w/developers-meeting/ Looking forward to those two intensive hacking Kamailio days in Dusseldorf! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

2 4

apt-key deprecation
by tom＠tomlynn.com 11 Nov '24

11 Nov '24

When I look at the debian repositories maintained by the project, there are instructions to import the public key of the repository for apt using this command: wget -O http://deb.kamailio.org/kamailiodebkey.gpg | sudo apt-key add - which results in: Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). gpg: no valid OpenPGP data found. Is there an alternate method that can be posted in the repository that will get better results? Thank you, TL

5 5

Getting the name of an already set onreply_route
by Denys Pozniak 14 Oct '24

14 Oct '24

Hello! Is it possible to find out the name of the onreply_route that was set before? Something like this: t_on_reply("MANAGE_REPLY"); ... if ( t_is_set("onreply_route") ) { get_onreply_route_name(); ... } -- BR, Denys Pozniak

3 5

TLS module crashes with FIPS OpenSSL
by Marat Gareev 08 Oct '24

08 Oct '24

Hello, I encountered a problem stopping Kamailio with FIPS OpenSSL: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3 Missing separate debuginfos, use: dnf debuginfo-install kamailio-5.7.3-4816.x86_64 (gdb) bt #0 0x00007ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3 #1 0x00007ff72914bf5b in conf_modules_finish_int () from /lib64/libcrypto.so.3 #2 0x00007ff72914c694 in CONF_modules_unload () from /lib64/libcrypto.so.3 #3 0x00007ff7291efff9 in OPENSSL_cleanup () from /lib64/libcrypto.so.3 #4 0x00007ff72954702b in ?? () #5 0x0000000100061c08 in ?? () #6 0x00007ff7190566c8 in ?? () #7 0x00007ffccf196a20 in ?? () #8 0x000000000071da8a in futex_release (lock=0x7ff729f08b50 <syslog>) at core/mem/../mem/../futexlock.h:134 #9 0x00000000006e9448 in destroy_tls () at core/tls_hooks.c:75 #10 0x000000000041f278 in cleanup (show_status=1) at main.c:594 #11 0x0000000000420af1 in shutdown_children (sig=15, show_status=1) at main.c:721 #12 0x0000000000421717 in handle_sigs () at main.c:752 #13 0x0000000000430c88 in main_loop () at main.c:1988 #14 0x0000000000439d13 in main (argc=14, argv=0x7ffccf1973f8) at main.c:3212 (gdb) Environment: Oracle Linux Server 9.3 Kamailio 5.7.3 yum list --installed | grep ssl openssl.x86_64 10:3.0.7-24.0.3.el9_fips @tools openssl-libs.x86_64 10:3.0.7-24.0.3.el9_fips @tools openssl-pkcs11.x86_64 0.4.11-7.el9 @anaconda xmlsec1-openssl.x86_64 1.2.29-9.el9 @AppStream What can I do for further investigation? Thanks

5 12

kamailio sending from udp non-listening port
by David Villasmil 04 Oct '24

04 Oct '24

Hello guys, i'm seeing something weird, and i'm working if you can let me know. I have a kamailio in AWS with a private IP listening on several sockets: Listening on udp: 10.1.2.36:5070 udp: 10.1.2.36:5080 udp: 10.1.2.36:5160 advertise 4.3.2.1:5160 udp: 0.0.0.0:5066 tls: 10.1.2.36:443 advertise sip.something.com:443 tls: 10.1.2.36:444 advertise sip.something.com:444 tls: 10.1.2.36:5061 When forwarding a udp invite received on 10.1.2.36:5080 to a public ip provider say on 8.8.8.8:5060, i'm forcing the outgoing socket with force_socket via 10.1.2.36:5160. But the outgoing invite does NOT use 5160, it uses some random port... Anybody knows why this might be? my problem is, that call goes to freeswitch... call is setup properly and connects fine. But 15 minutes later the end provider sends back a reINVITE, which freeswitch then sends TO THE RANDOM PORT kamailio used to send the INVITE... but by this time kamailio doesn't seem to even see the packet... help is greatly appreciated! David Regards, David Villasmil email: david.villasmil.work(a)gmail.com

4 9

Sync Suspended Transaction
by Knserbrave 30 Sep '24

30 Sep '24

Is it possible to sync a suspended transaction between two nodes using t_suspend() from the TMX module and DMQ (or similar module)? More specifically, can I suspend it on one node and resume the transaction on another in a cluster?

4 6

sys.exit() in app_python3s
by Denys Pozniak 26 Sep '24

26 Sep '24

Hello! I'm planning to rewrite a native Kamailio script in KEMI Python, and I want to understand the differences between app_python3 vs app_python3s in the context of using sys.exit(). My native script uses the exit function in deep nested route[] blocks quite a bit and would like to keep this logic in KEMI without using return codes on top (return -255) towards ksr_request_route() Using sys.exit() in app_python3s gives an error in syslog (although the interpreter does not crash and everything works correctly), in app_python3 no such error ERROR: app_python3s [apy3s_kemi.c:146]: apy3s_exec_func(): error exception occurred How safe is it to use sys.exit() in this case? -- BR, Denys Pozniak

1 0

Re: About error running PCSCF
by LUIS FELIPE RAMOS TORRES 25 Sep '24

25 Sep '24

Dear community: If someone runs this tutorial successfully for dockerized open5GS, please I appreciate it. Web page of OPEN 5GS: [image: image.png] The APNs were created in the docker_host:8080/docs [image: image.png] When i ran the command: docker compose -f srsenb.yaml up - d && docker container attach srsenb [image: image.png] [image: image.png] I created 2 APNs on the phones, but when I select one of them (internet), I have access to the Internet. About VOLTE, I don't know how to try or maybe I must change to the other APN (ims). [image: image.png] Please let me know, I only have the problem with VOLTE service and how to try it. Best wishes, Luis El mar, 24 sept 2024 a las 19:23, LUIS FELIPE RAMOS TORRES (< luis.ramost(a)pucp.edu.pe>) escribió: > > Sorry if I replied to you again. > > If you can explain to me why we need to create 2 APNs, 1 for the ims and > other for the internet. I created the subscriber on Open5GS. > > [image: image.png] > > > I also create the apns. I attached one of them to this email. > [image: image.png] > > I do everything that you put on github, but when I run the command for the > OTA, my cell phone registers to the network, and when I create manually the > 2 APNS, I select the "internet" and have access, but I don't know how to > configure VOLTE. The model is a Huawei p30 lite, and also I don't know if > it supports VOLTE. > > [image: image.png] > [image: image.png] > > Cellular connected to the network: > [image: image.png] > > > Also in this tutorial ( > https://open5gs.org/open5gs/docs/tutorial/03-VoLTE-dockerized/ ), I see > that you use an app called CoIMS for VoLTE. Is that enabled for that > service or what to do exactly? > > Sorry again for my replies and comments. > > Luis > > > El mar, 24 sept 2024 a las 17:04, LUIS FELIPE RAMOS TORRES (< > luis.ramost(a)pucp.edu.pe>) escribió: > >> Hi Supreeth: >> >> My question is if the MSISDN is necessary to add to the parameters, >> because when I configure the SIM card, I don't generate any for that value. >> Or maybe to make a call. >> >> And if I have an error in making the call for VOLTE, maybe it would be a >> problem of a configuration, or maybe the phones. How to know that? >> >> Luis >> >> El mar, 24 sept 2024 a las 2:48, Supreeth Herle (<herlesupreeth(a)gmail.com>) >> escribió: >> >>> Hi Luis, >>> >>> In the next screenshot, I don't know if the next command (docker compose >>>> -f srsenb-yaml up ...) must run in another terminal window or in the same >>>> as I run the first command. >>> >>> >>> In another terminal window. >>> >>> I will not use the RF simulated because it would be physical and I have >>>> the LIMESDR hardware. Also the UE with 4G sim cards. >>> >>> >>> Run only the one which says OTA (over-the-air) >>> >>> And next of the following steps, when I run the others and add the >>>> subscriber, the apn, the ims, and the SIM parameters. What is the next >>>> step? Try the solution by making a call? >>>> >>> >>> yes >>> >>> BR, >>> Supreeth >>> >>> >>> >>> On Tue, 24 Sept 2024 at 02:35, LUIS FELIPE RAMOS TORRES < >>> luis.ramost(a)pucp.edu.pe> wrote: >>> >>>> Hi Supreeth: >>>> >>>> I do nothing but finally it runs successfully. But I have a question. I >>>> am running now the command of the screenshot (docker compose -f >>>> 4g-volte-deploy.yaml up) and I have the next output: >>>> >>>> [image: image.png] >>>> >>>> >>>> In the next screenshot, I don't know if the next command (docker >>>> compose -f srsenb-yaml up ...) must run in another terminal window or in >>>> the same as I run the first command. >>>> >>>> [image: image.png] >>>> I will not use the RF simulated because it would be physical and I have >>>> the LIMESDR hardware. Also the UE with 4G sim cards. >>>> >>>> And next of the following steps, when I run the others and add the >>>> subscriber, the apn, the ims, and the SIM parameters. What is the next >>>> step? Try the solution by making a call? >>>> >>>> Please if you can help me. >>>> >>>> Best wishes, >>>> Luis >>>> >>>> >>>> El dom, 22 sept 2024 a las 1:46, Supreeth Herle (< >>>> herlesupreeth(a)gmail.com>) escribió: >>>> >>>>> Hi Luis, >>>>> >>>>> Please raise an issue in >>>>> https://github.com/herlesupreeth/docker_open5gs >>>>> <https://github.com/herlesupreeth/docker_open5gs/tree/master> repo. I >>>>> will try to resolve it. >>>>> >>>>> I just ran the same command (after removing the image built locally) >>>>> and that step passed. So I would suggest to check your network connection >>>>> or DNS settings of the machine on which docker_open5gs is cloned. >>>>> >>>>> WARN[0000] /home/sherle/docker_open5gs/4g-volte-deploy.yaml: the >>>>>> attribute `version` is obsolete, it will be ignored, please remove it to >>>>>> avoid potential confusion >>>>>> [+] Building 19.0s (8/8) FINISHED >>>>>> >>>>>> >>>>>> >>>>>> docker:default >>>>>> => [osmohlr internal] load build definition from Dockerfile >>>>>> >>>>>> >>>>>> >>>>>> 0.0s >>>>>> => => transferring dockerfile: 2.10kB >>>>>> >>>>>> >>>>>> >>>>>> 0.0s >>>>>> => WARN: JSONArgsRecommended: JSON arguments recommended for CMD to >>>>>> prevent unintended behavior related to OS signals (line 41) >>>>>> >>>>>> >>>>>> 0.0s >>>>>> => [osmohlr internal] load metadata for >>>>>> docker.io/library/debian:bullseye >>>>>> >>>>>> >>>>>> >>>>>> 0.0s >>>>>> => [osmohlr internal] load .dockerignore >>>>>> >>>>>> >>>>>> >>>>>> 0.0s >>>>>> => => transferring context: 2B >>>>>> >>>>>> >>>>>> >>>>>> 0.0s >>>>>> => CACHED [osmohlr 1/3] FROM docker.io/library/debian:bullseye >>>>>> >>>>>> >>>>>> >>>>>> 0.0s >>>>>> => [osmohlr 2/3] RUN apt-get update && apt-get -y install wget >>>>>> gnupg telnet >>>>>> >>>>>> >>>>>> 14.1s >>>>>> => [osmohlr 3/3] RUN wget >>>>>> https://downloads.osmocom.org/packages/osmocom:/latest/Debian_11/Release.key >>>>>> && mv Release.key /etc/apt/trusted.gpg.d/osmocom-latest.asc && echo >>>>>> "deb [signed-by=/etc/apt/trusted.gpg.d/osmocom-latest.asc] >>>>>> https://downloads.osmocom.org/packages/osmocom:/latest/Debian_11/ >>>>>> ./" > /etc/apt/sources.list.d/osmocom-latest.list && apt 4.5s >>>>>> => [osmohlr] exporting to image >>>>>> >>>>>> >>>>>> >>>>>> 0.2s >>>>>> => => exporting layers >>>>>> >>>>>> >>>>>> >>>>>> 0.2s >>>>>> => => writing image >>>>>> sha256:95227b65ff159ba4eab30f2caa460163b76895703c8cc73f41735d1ef4ef6dfc >>>>>> >>>>>> >>>>>> >>>>>> 0.0s >>>>>> => => naming to docker.io/library/docker_osmohlr >>>>>> >>>>>> >>>>>> >>>>>> 0.0s >>>>>> => [osmohlr] resolving provenance for metadata file >>>>> >>>>> >>>>> BR, >>>>> Supreeth >>>>> >>>>> On Sat, 21 Sept 2024 at 20:42, LUIS FELIPE RAMOS TORRES < >>>>> luis.ramost(a)pucp.edu.pe> wrote: >>>>> >>>>>> Hello: >>>>>> >>>>>> I don't know if somebody can successfully run this tutorial for a >>>>>> solution of open5gs with kamailio using docker. I have the next error after >>>>>> the command: >>>>>> >>>>>> docker compose -f 4g-volte-deploy.yaml build >>>>>> and the output is: >>>>>> [image: image.png] >>>>>> >>>>>> [image: image.png] >>>>>> >>>>>> [image: image.png] >>>>>> >>>>>> I am running on Ubuntu 22.04, I also don't know if it is the same as >>>>>> Debian 11 (in the link of the download). Or how can I solve it? >>>>>> >>>>>> Luis >>>>>> >>>>>> El mié, 18 sept 2024 a las 19:30, LUIS FELIPE RAMOS TORRES (< >>>>>> luis.ramost(a)pucp.edu.pe>) escribió: >>>>>> >>>>>>> Hello >>>>>>> >>>>>>> Sorry for writing again, I followed your repository on github: >>>>>>> https://github.com/herlesupreeth/docker_open5gs/tree/master, but I >>>>>>> don't know how to build srslte: >>>>>>> >>>>>>> I have the next error when I build the srslte: docker build >>>>>>> --no-cache --force-rm -t docker_srslte . >>>>>>> >>>>>>> I don't know if it is updated, maybe also I run it on a VM, and >>>>>>> specifically in the "git checkout ......" I had the error. >>>>>>> >>>>>>> [image: image.png] >>>>>>> Luis >>>>>>> >>>>>>> El mar, 17 sept 2024 a las 1:45, Supreeth Herle (< >>>>>>> herlesupreeth(a)gmail.com>) escribió: >>>>>>> >>>>>>>> Hello Luis, >>>>>>>> >>>>>>>> When I use the github of RTPEngine, the master branch, when I run >>>>>>>>> the command dpkg-checkbuildeps >>>>>>>> >>>>>>>> >>>>>>>> I would not recommend installing the master branch of RTPEngine, >>>>>>>> rather use the tag mr9.4.1 and install on Ubuntu 20.04. You can find all >>>>>>>> dependencies to install here - >>>>>>>> https://github.com/herlesupreeth/docker_open5gs/blob/master/rtpengine/Docke… >>>>>>>> >>>>>>>> If you just want a working setup of IMS + RTPEngine I would highly >>>>>>>> recommend using https://github.com/herlesupreeth/docker_open5gs >>>>>>>> repo. You can get the setup running with few steps. >>>>>>>> >>>>>>>> BR, >>>>>>>> Supreeth >>>>>>>> >>>>>>>> On Tue, 17 Sept 2024 at 03:06, LUIS FELIPE RAMOS TORRES < >>>>>>>> luis.ramost(a)pucp.edu.pe> wrote: >>>>>>>> >>>>>>>>> Hello Supreeth: >>>>>>>>> >>>>>>>>> Sorry if I reply to the message, but I am trying to install the >>>>>>>>> tutorials, but I've got the same error. When I use the github of RTPEngine, >>>>>>>>> the master branch, when I run the command dpkg-checkbuildeps, I get errors. >>>>>>>>> >>>>>>>>> If you would have an updated tutorial to run successfully and also >>>>>>>>> recommend the Ubuntu version to avoid more errors, please it would help me. >>>>>>>>> >>>>>>>>> Luis >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> El lun, 16 sept 2024 a las 10:32, Supreeth Herle (< >>>>>>>>> herlesupreeth(a)gmail.com>) escribió: >>>>>>>>> >>>>>>>>>> Hello Luis, >>>>>>>>>> >>>>>>>>>> I am the author of the tutorial here - >>>>>>>>>> https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/. That >>>>>>>>>> tutorial is also not up-to-date. However, you can use the latest master >>>>>>>>>> branch of kamailio, along with instructions here (installing dependencies >>>>>>>>>> etc) - >>>>>>>>>> https://github.com/herlesupreeth/docker_open5gs/blob/master/ims_base/Docker… >>>>>>>>>> and configuration files from master branch of this repo >>>>>>>>>> https://github.com/herlesupreeth/Kamailio_IMS_Config . >>>>>>>>>> >>>>>>>>>> As pointed out earlier, rtpproxy is not needed. It was a step I >>>>>>>>>> added to test out VoIP (not IMS) calling. All you need is RTPEngine to test >>>>>>>>>> out IMS. >>>>>>>>>> >>>>>>>>>> Hope it helps. >>>>>>>>>> >>>>>>>>>> BR, >>>>>>>>>> Supreeth >>>>>>>>>> >>>>>>>>>> On Mon, 16 Sept 2024 at 17:22, LUIS FELIPE RAMOS TORRES via >>>>>>>>>> sr-users <sr-users(a)lists.kamailio.org> wrote: >>>>>>>>>> >>>>>>>>>>> Hello Henning: >>>>>>>>>>> >>>>>>>>>>> Is this tutorial updated? >>>>>>>>>>> https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/ >>>>>>>>>>> >>>>>>>>>>> I don´t know about it. And also I guess that it is installed on >>>>>>>>>>> Ubuntu 18 version. >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Luis >>>>>>>>>>> >>>>>>>>>>> El lun, 16 sept 2024 a las 1:32, Henning Westerholt (< >>>>>>>>>>> hw(a)gilawa.com>) escribió: >>>>>>>>>>> >>>>>>>>>>>> Hello, >>>>>>>>>>>> >>>>>>>>>>>> the tutorial is using a Kamailio version that its long end of >>>>>>>>>>>> life (5.3.x). >>>>>>>>>>>> >>>>>>>>>>>> Some of the instructions given there are also a bit odd, like >>>>>>>>>>>> first installing rtpproxy, and then replacing it with rtpengine. >>>>>>>>>>>> >>>>>>>>>>>> Maybe you can reach out to the author of the tutorial. You need >>>>>>>>>>>> to understand how the individual components work together in the end to be >>>>>>>>>>>> able to debug it. Maybe somebody else figured out on this list how to do it >>>>>>>>>>>> for an updated Kamailio. >>>>>>>>>>>> >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Henning >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Henning Westerholt - https://skalatan.de/blog/ >>>>>>>>>>>> Kamailio services - https://gilawa.com >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> > -----Original Message----- >>>>>>>>>>>> > From: luis.ramost--- via sr-users < >>>>>>>>>>>> sr-users(a)lists.kamailio.org> >>>>>>>>>>>> > Sent: Montag, 16. September 2024 02:14 >>>>>>>>>>>> > To: sr-users(a)lists.kamailio.org >>>>>>>>>>>> > Cc: luis.ramost(a)pucp.edu.pe >>>>>>>>>>>> > Subject: [SR-Users] About error running PCSCF >>>>>>>>>>>> > >>>>>>>>>>>> > Hi community: >>>>>>>>>>>> > >>>>>>>>>>>> > I am trying to run the Kamailio IMS, but I have the next >>>>>>>>>>>> error in the module >>>>>>>>>>>> > PCSCF >>>>>>>>>>>> > >>>>>>>>>>>> > I installed the Kamailio on a VM Machine, with UBuntu 18.04 >>>>>>>>>>>> > >>>>>>>>>>>> > Commands: >>>>>>>>>>>> > $ sudo -i >>>>>>>>>>>> > # mkdir -p /var/run/kamailio_pcscf >>>>>>>>>>>> > #kamailio -f /etc/kamailio_pcscf/kamailio_pcscf.cfg -P >>>>>>>>>>>> /kamailio_pcscf.pid -DD >>>>>>>>>>>> > -E -e >>>>>>>>>>>> > >>>>>>>>>>>> > Output: >>>>>>>>>>>> > loading modules under config path: >>>>>>>>>>>> > >>>>>>>>>>>> /usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/:/usr/lib/kama >>>>>>>>>>>> > >>>>>>>>>>>> ilio/modules_k/:/usr/lib/kamailio/modules/:/usr/lib/x86_64-linux- >>>>>>>>>>>> > gnu/kamailio/modules/:/usr/local/lib64/kamailio/modules >>>>>>>>>>>> > 0(470) ERROR: <core> [core/modparam.c:164]: >>>>>>>>>>>> set_mod_param_regex(): >>>>>>>>>>>> > parameter <delete_delay> of type <2:int> not found in module >>>>>>>>>>>> > <ims_registrar_pcscf> >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/kamailio_pcscf.cfg, line 399, column >>>>>>>>>>>> 51: Can't set >>>>>>>>>>>> > module parameter >>>>>>>>>>>> > 0(470) ERROR: <core> [core/modparam.c:164]: >>>>>>>>>>>> set_mod_param_regex(): >>>>>>>>>>>> > parameter <ipsec_preferred_ealg> of type <1:string> not found >>>>>>>>>>>> in module >>>>>>>>>>>> > <ims_ipsec_pcscf> >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/kamailio_pcscf.cfg, line 417, column >>>>>>>>>>>> 59: Can't set >>>>>>>>>>>> > module parameter >>>>>>>>>>>> > 0(470) ERROR: <core> [core/modparam.c:164]: >>>>>>>>>>>> set_mod_param_regex(): >>>>>>>>>>>> > parameter <recv_mode> of type <2:int> not found in module >>>>>>>>>>>> <ims_qos> >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/kamailio_pcscf.cfg, line 435, column >>>>>>>>>>>> 35: Can't set >>>>>>>>>>>> > module parameter >>>>>>>>>>>> > 0(470) ERROR: <core> [core/modparam.c:164]: >>>>>>>>>>>> set_mod_param_regex(): >>>>>>>>>>>> > parameter <dialog_direction> of type <2:int> not found in >>>>>>>>>>>> module <ims_qos> >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/kamailio_pcscf.cfg, line 436, column >>>>>>>>>>>> 42: Can't set >>>>>>>>>>>> > module parameter >>>>>>>>>>>> > 0(470) INFO: pv [pv_shv.c:60]: shvar_init_locks(): locks >>>>>>>>>>>> array size 16 >>>>>>>>>>>> > 0(470) ERROR: <core> [core/cfg.y:3399]: yyparse(): cfg. >>>>>>>>>>>> parser: failed to find >>>>>>>>>>>> > command ipsec_forward (params 2) >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/route/register.cfg, line 260, column >>>>>>>>>>>> 42: unknown >>>>>>>>>>>> > command, missing loadmodule? >>>>>>>>>>>> > >>>>>>>>>>>> > 0(470) ERROR: <core> [core/cfg.y:3399]: yyparse(): cfg. >>>>>>>>>>>> parser: failed to find >>>>>>>>>>>> > command ipsec_create (params 2) >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/route/register.cfg, line 264, column >>>>>>>>>>>> 77: unknown >>>>>>>>>>>> > command, missing loadmodule? >>>>>>>>>>>> > >>>>>>>>>>>> > 0(470) ERROR: <core> [core/cfg.y:3399]: yyparse(): cfg. >>>>>>>>>>>> parser: failed to find >>>>>>>>>>>> > command ipsec_forward (params 2) >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/route/mo.cfg, line 114, column 31: >>>>>>>>>>>> unknown >>>>>>>>>>>> > command, missing loadmodule? >>>>>>>>>>>> > >>>>>>>>>>>> > 0(470) ERROR: <core> [core/cfg.y:3399]: yyparse(): cfg. >>>>>>>>>>>> parser: failed to find >>>>>>>>>>>> > command ipsec_forward (params 2) >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/route/mo.cfg, line 180, column 33: >>>>>>>>>>>> unknown >>>>>>>>>>>> > command, missing loadmodule? >>>>>>>>>>>> > >>>>>>>>>>>> > 0(470) ERROR: <core> [core/cfg.y:3399]: yyparse(): cfg. >>>>>>>>>>>> parser: failed to find >>>>>>>>>>>> > command ipsec_forward (params 2) >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/route/mt.cfg, line 11, column 34: >>>>>>>>>>>> unknown >>>>>>>>>>>> > command, missing loadmodule? >>>>>>>>>>>> > >>>>>>>>>>>> > 0(470) ERROR: <core> [core/cfg.y:3399]: yyparse(): cfg. >>>>>>>>>>>> parser: failed to find >>>>>>>>>>>> > command ipsec_forward (params 2) >>>>>>>>>>>> > 0(470) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): >>>>>>>>>>>> parse error in config >>>>>>>>>>>> > file /etc/kamailio_pcscf/route/mt.cfg, line 99, column 42: >>>>>>>>>>>> unknown >>>>>>>>>>>> > command, missing loadmodule? >>>>>>>>>>>> > >>>>>>>>>>>> > ERROR: bad config file (10 errors) >>>>>>>>>>>> > 0(470) WARNING: <core> [core/mem/q_malloc.c:487]: qm_free(): >>>>>>>>>>>> > WARNING: free(0) called from cdp_avp: cdp_avp_mod.c: >>>>>>>>>>>> > cdp_avp_destroy(226) >>>>>>>>>>>> > 0(470) INFO: cdp [cdp_mod.c:255]: cdp_exit(): CDiameterPeer >>>>>>>>>>>> child stopping >>>>>>>>>>>> > ... >>>>>>>>>>>> > 0(470) INFO: cdp [cdp_mod.c:257]: cdp_exit(): ... >>>>>>>>>>>> CDiameterPeer child >>>>>>>>>>>> > stopped >>>>>>>>>>>> > 0(470) ERROR: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:309]: >>>>>>>>>>>> > mod_destroy(): Error destroying spi generator >>>>>>>>>>>> > 0(470) ERROR: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:313]: >>>>>>>>>>>> > mod_destroy(): Error destroying port generator >>>>>>>>>>>> > >>>>>>>>>>>> > I guided form this tutorial: >>>>>>>>>>>> https://ryantheelder.github.io/blog/2023/VoLTE/ >>>>>>>>>>>> > >>>>>>>>>>>> > Please if somebody would help me, I appreciate it >>>>>>>>>>>> > >>>>>>>>>>>> > Finally my objective is to connect with srsRAN and open5GS to >>>>>>>>>>>> have VoLTE >>>>>>>>>>>> > service. >>>>>>>>>>>> > >>>>>>>>>>>> > Best wishes, >>>>>>>>>>>> > Luis >>>>>>>>>>>> > __________________________________________________________ >>>>>>>>>>>> > Kamailio - Users Mailing List - Non Commercial Discussions To >>>>>>>>>>>> unsubscribe >>>>>>>>>>>> > send an email to sr-users-leave(a)lists.kamailio.org >>>>>>>>>>>> > Important: keep the mailing list in the recipients, do not >>>>>>>>>>>> reply only to the >>>>>>>>>>>> > sender! >>>>>>>>>>>> > Edit mailing list options or unsubscribe: >>>>>>>>>>>> >>>>>>>>>>> __________________________________________________________ >>>>>>>>>>> Kamailio - Users Mailing List - Non Commercial Discussions >>>>>>>>>>> To unsubscribe send an email to >>>>>>>>>>> sr-users-leave(a)lists.kamailio.org >>>>>>>>>>> Important: keep the mailing list in the recipients, do not reply >>>>>>>>>>> only to the sender! >>>>>>>>>>> Edit mailing list options or unsubscribe: >>>>>>>>>>> >>>>>>>>>>

1 0

Re: [EXTERNAL] Re: SDP parsing fails when media stream is removed, there is no session-wide "c=" line and offending media stream omits all attributes
by Thomas Baumgartner 24 Sep '24

24 Sep '24

Hi Richard, thanks for your input. And i guess you are correct, when reading the sentence with the wording of the SDP RFC in mind attributes should only be "a=" lines. We will talk to the device vendor again with this new finding! Anyways, maybe it still makes sense to adjust the SDP parser for such scenarios, as it really doesn't make sense to require a "c=" line if the stream is being removed as you said. I will open an git issue aswell. Mit kommunikativen Grüßen I Best regards Thomas

2 1

SDP parsing fails when media stream is removed, there is no session-wide "c=" line and offending media stream omits all attributes
by Thomas Baumgartner 24 Sep '24

24 Sep '24

Hi, we have a problem with a device trying to send T.38 fax. During the T.38 ReInvite Kamailio fails to parse the SDP (via rtpengine_manage), and subsequently rtpengine is failing to do it's job. The problem seems to be that Kamailio is trying to find a media address, since there is no session-wide c= line present it goes to the media c= lines, but since the first media stream which was an audio stream is being removed (port 0) and can therefore omit all attributes (as per RFC 3264 8.2, or am i understanding this wrong?), the Kamailio SDP parser is failing, even if there is another c= line in the T.38 media stream. Here is the offending SDP from the ReInvite (IP changed): v=0 o=xmserver 1726638425 1726638427 IN IP4 169.254.1.1 s=xmserver t=0 0 m=audio 0 RTP/AVP 8 m=image 56002 udptl t38 c=IN IP4 169.254.1.1 a=sendrecv a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxFillBitRemoval:0 a=T38FaxTranscodingMMR:0 a=T38FaxTranscodingJBIG:0 a=T38FaxRateManagement:transferredTCF a=T38FaxMaxBuffer:200 a=T38FaxMaxDatagram:72 a=T38FaxUdpEC:t38UDPRedundancy And here is the corresponding log entry: <core> [core/parser/sdp/sdp.c:523]: parse_sdp_session(): can't find media IP in the message Can anyone confirm my findings? Is it possible to adjust the SDP parser for these kind of scenarios? Mit kommunikativen Grüßen I Best regards Thomas

3 3

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 September 2024