[SR-Users] Re: Roadmap to next major Kamailio release series v5.8.x
Hello, with still some docs to be updated for v5.8.0, the plan is to get the new version out tomorrow, March 7, 2024. Cheers, Daniel On 27.02.24 16:49, Daniel-Constantin Mierla wrote: > Hello, > > I propose to aim to get out 5.8.0 next week on Wednesday or Thursday > (March 6 or 7, 2024). I haven't seen much activity around issues in the > new features/modules. If time allows to build the pages for what-is-new > and how-to-upgrade (which I think it should be rather minimal), then I > think it should be no other major task. Overall it will be almost two > weeks since the 5.8 branch was created. > > Cheers, > Daniel > > On 23.02.24 12:11, Daniel-Constantin Mierla wrote: >> Hello, >> >> quick note that later today I will create the branch 5.8, notification >> emails will be sent once done. >> >> Cheers, >> Daniel >> >> On 16.02.24 08:01, Daniel-Constantin Mierla wrote: >>> Hello, >>> >>> hopefully the devel version is now more stabilized after the freezing, >>> the new components being adjusted enough not to need many more changes. >>> Therefore I consider to branch 5.8 out of devel version next week on >>> Friday, February 23, 2024, sometime around noon UTC. >>> >>> After that the master branch becomes open for new features, and branch >>> 5.8 has to be hammered further to build the 5.8.x series. >>> >>> Cheers, >>> Daniel >>> >>> On 10.01.24 10:11, Daniel-Constantin Mierla wrote: Hello, discussed a bit during the online Kamailio devel meeting, it is time to set the milestones towards the next major Kamailio release series v5.8.x. If no other suggestions that suit more developers, I would propose to freeze by end of this month or early February, then test for about 4 weeks as usual and release by end of February or during March. If anyone wants to add new features/modules, they have to be published till freezing date, either pushed in the git repository or proposed as pull request. Cheers, Daniel >>> -- >>> Daniel-Constantin Mierla (@ asipto.com) >>> twitter.com/miconda -- linkedin.com/in/miconda >>> Kamailio Consultancy, Training and Development Services -- asipto.com >>> Kamailio Advanced Training, February 20-22, 2024 -- asipto.com >>> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com >>> >> -- >> Daniel-Constantin Mierla (@ asipto.com) >> twitter.com/miconda -- linkedin.com/in/miconda >> Kamailio Consultancy, Training and Development Services -- asipto.com >> Kamailio Advanced Training, February 20-22, 2024 -- asipto.com >> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com >> > -- > Daniel-Constantin Mierla (@ asipto.com) > twitter.com/miconda -- linkedin.com/in/miconda > Kamailio Consultancy, Training and Development Services -- asipto.com > Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com > -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: SSL key logger for Diffie-Hellman cipher
Hi Calvin, Thanks for the tip on capturing on LO interface, I'm sure you just saved me some headaches ;) Interestingly when I check the environ I do see the env vars being set, but in the maps I don't see the keylogger: root@csbc03:~# cat /proc/2216899/environ LANG=en_US.UTF-8PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binPIDFILE=/run/kamailio/kamailio.pidHOME=/run/kamailioLOGNAME=kamailioUSER=kamailioINVOCATION_ID=fb5d2818a5434319ab2381262737dcffJOURNAL_STREAM=8:1642042024RUNTIME_DIRECTORY=/run/kamailioCFGFILE=/etc/kamailio/csbc.cfgSHM_MEMORY=512PKG_MEMORY=32SSLKEYLOG_UDP=10.2.1.19:1234LD_PRELOAD=/opt/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so /usr/lib/x86_64-linux-gnu/libssl.so.1.1RUN_KAMAILIO=yesGROUP=kamailioDUMP_CORE=yes root@csbc03:~# root@csbc03:~# fgrep ssl /proc/2216899/maps 7f1ceef99000-7f1ceefb6000 r--p 08:06 266231 /usr/lib/x86_64-linux-gnu/libssl.so.1.1 7f1ceefb6000-7f1cef004000 r-xp 0001d000 08:06 266231 /usr/lib/x86_64-linux-gnu/libssl.so.1.1 7f1cef004000-7f1cef01e000 r--p 0006b000 08:06 266231 /usr/lib/x86_64-linux-gnu/libssl.so.1.1 7f1cef01e000-7f1cef01f000 ---p 00085000 08:06 266231 /usr/lib/x86_64-linux-gnu/libssl.so.1.1 7f1cef01f000-7f1cef028000 r--p 00085000 08:06 266231 /usr/lib/x86_64-linux-gnu/libssl.so.1.1 7f1cef028000-7f1cef02c000 rw-p 0008e000 08:06 266231 /usr/lib/x86_64-linux-gnu/libssl.so.1.1 root@csbc03:~# This is on a debian 10 box. I have another box for testing on debian12, I set the exact same config as you and I still don't see the keylogger being loaded: root@csbc01:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm root@csbc01:~# root@csbc01:~# cat /etc/default/kamailio.d/voipmonitor # ANSIBLE_MANAGED_FILE - Do NOT edit this file as it is auto-generated by Ansible. SSLKEYLOG_UDP='127.0.0.1:1234' LD_PRELOAD="/usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so /usr/lib/x86_64-linux-gnu/libssl.so.3" root@csbc01:~# root@csbc01:~# file /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=f1a884cad7648cc38a579b1d00a9ad523297b78c, with debug_info, not stripped root@csbc01:~# root@csbc01:~# file /usr/lib/x86_64-linux-gnu/libssl.so.3 /usr/lib/x86_64-linux-gnu/libssl.so.3: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=dd6b0615fc5d03f9c698d6d0c9d2da1b1e8f2d24, stripped root@csbc01:~# root@csbc01:~# cat /proc/181454/environ LANG=en_US.UTF-8PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binPIDFILE=/run/kamailio/kamailio.pidHOME=/run/kamailioLOGNAME=kamailioUSER=kamailioINVOCATION_ID=059a5e15f1bb4e2bae17c0b5ec9c731eJOURNAL_STREAM=8:2661302RUNTIME_DIRECTORY=/run/kamailioSYSTEMD_EXEC_PID=181394CFGFILE=/etc/kamailio/csbc.cfgSHM_MEMORY=512PKG_MEMORY=32RUN_KAMAILIO=yesGROUP=kamailioDUMP_CORE=yesSSLKEYLOG_UDP=127.0.0.1:1234LD_PRELOAD=/usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so /usr/lib/x86_64-linux-gnu/libssl.so.3 root@csbc01:~# root@csbc01:~# fgrep ssl /proc/181454/maps 7f0c537b6000-7f0c537d5000 r--p 08:01 3674382 /usr/lib/x86_64-linux-gnu/libssl.so.3 7f0c537d5000-7f0c53833000 r-xp 0001f000 08:01 3674382 /usr/lib/x86_64-linux-gnu/libssl.so.3 7f0c53833000-7f0c53852000 r--p 0007d000 08:01 3674382 /usr/lib/x86_64-linux-gnu/libssl.so.3 7f0c53852000-7f0c5385c000 r--p 0009c000 08:01 3674382 /usr/lib/x86_64-linux-gnu/libssl.so.3 7f0c5385c000-7f0c5386 rw-p 000a6000 08:01 3674382 /usr/lib/x86_64-linux-gnu/libssl.so.3 root@csbc01:~# Any other ideas of what I can be missing? On Tue, Mar 5, 2024 at 2:30 PM Calvin E. wrote: > Make sure you are preloading the correct OpenSSL library. On my Debian > 12 box it is libssl.so.3 not libssl.so.1.1. You can confirm which is > loaded by checking the "maps" of a running proc: > > $ sudo fgrep ssl /proc/2951676/maps > 7f26647a4000-7f26647c3000 r--p 08:01 131274 > /usr/lib/x86_64-linux-gnu/libssl.so.3 > 7f26647c3000-7f2664821000 r-xp 0001f000 08:01 131274 > /usr/lib/x86_64-linux-gnu/libssl.so.3 > 7f2664821000-7f266484 r--p 0007d000 08:01 131274 > /usr/lib/x86_64-linux-gnu/libssl.so.3 > 7f266484-7f266484a000 r--p 0009c000 08:01 131274 > /usr/lib/x86_64-linux-gnu/libssl.so.3 > 7f266484a000-7f266484e000 rw-p 000a6000 08:01 131274 > /usr/lib/x86_64-linux-gnu/libssl.so.3 > 7f266484e000-7f266484f000 r--p 08:01 154916 > /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so > 7f266484f000-7f266485 r-xp 1000 08:01 154916 > /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so > 7f266485-7f2664851000 r--p 2000 08:01 154916 > /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so > 7f2664851000-7f2664852000 r--p 2000 08:01 154916 >
[SR-Users] Re: Add XML to INVITE
Thanks for replying!
thanks for this, it worked perfectly. I'm still wondering why
set_body_multipart
and append_body_part don't work together...
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Tue, 5 Mar 2024 at 20:25, Valentin Christoph <
christoph.valen...@kontron.com> wrote:
> Hi David,
>
>
>
> I am always very cautious when using msg_apply_changes() – e.g. there are
> some implications with Record-Route, afaik
>
>
>
> I do it this way:
>
>
>
> set_body("--outer\r\nContent-Type:application/sdp\r\n\r\n$rb" +
>
>
> "\r\n--outer\r\nContent-Type:application/vnd.3gpp.mcptt-info+xml\r\n\r\n"
> +
>
> "\r\n"
> +
>
>
>
> "\t\r\n" +
>
> "\r\n--outer--\r\n",
>
> "multipart/mixed;boundary=\"outer\"");
>
>
>
> Hope this helps, and sorry for slow reaction. I am scanning the mailing
> list in rather low frequency.
>
>
>
> Kr
>
>
>
> *From:* David Villasmil via sr-users
> *Sent:* Tuesday, March 5, 2024 7:08 PM
> *To:* Kamailio (SER) - Users Mailing List
> *Cc:* David Villasmil
> *Subject:* [SR-Users] Re: Add XML to INVITE
>
>
>
> Hello guys,
>
>
>
> Anyone on this?
>
>
> Regards,
>
>
>
> David Villasmil
>
> email: david.villasmil.w...@gmail.com
>
> phone: +34669448337
>
>
>
>
>
> On Sun, Mar 3, 2024 at 4:01 AM David Villasmil <
> david.villasmil.w...@gmail.com> wrote:
>
> Hello guys,
>
>
>
> I'm trying to add an xml with a boundary to an outgoing INVITE. But if i
> do:
>
>
>
> set_body_multipart("$rb", "application/sdp", "delimiter");
> msg_apply_changes();
> append_body_part("$var(something)", "application/pidf+xml");
> msg_apply_changes();
>
>
>
> but kamailio adds the SDP, but NOT the second $var(something). If i switch
> them and add firs the var, and then the SDP. kamailio adds the contents of
> $var(something) but NOT the SDP point is it doesn't add the second
> append
>
>
>
>
>
> Thanks!!!
>
>
>
>
>
> Regards,
>
>
>
> David Villasmil
>
> email: david.villasmil.w...@gmail.com
>
> phone: +34669448337
>
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: SSL key logger for Diffie-Hellman cipher
Make sure you are preloading the correct OpenSSL library. On my Debian 12 box it is libssl.so.3 not libssl.so.1.1. You can confirm which is loaded by checking the "maps" of a running proc: $ sudo fgrep ssl /proc/2951676/maps 7f26647a4000-7f26647c3000 r--p 08:01 131274 /usr/lib/x86_64-linux-gnu/libssl.so.3 7f26647c3000-7f2664821000 r-xp 0001f000 08:01 131274 /usr/lib/x86_64-linux-gnu/libssl.so.3 7f2664821000-7f266484 r--p 0007d000 08:01 131274 /usr/lib/x86_64-linux-gnu/libssl.so.3 7f266484-7f266484a000 r--p 0009c000 08:01 131274 /usr/lib/x86_64-linux-gnu/libssl.so.3 7f266484a000-7f266484e000 rw-p 000a6000 08:01 131274 /usr/lib/x86_64-linux-gnu/libssl.so.3 7f266484e000-7f266484f000 r--p 08:01 154916 /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so 7f266484f000-7f266485 r-xp 1000 08:01 154916 /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so 7f266485-7f2664851000 r--p 2000 08:01 154916 /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so 7f2664851000-7f2664852000 r--p 2000 08:01 154916 /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so 7f2664852000-7f2664853000 rw-p 3000 08:01 154916 /usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so My systemd /lib/systemd/system/kamailio.service has a line "EnvironmentFile=-/etc/default/kamailio.d/*" so I dropped a file there: $ cat /etc/default/kamailio.d/voipmonitor SSLKEYLOG_UDP='127.0.0.1:1234' LD_PRELOAD="/usr/local/src/voipmonitor-git/tools/ssl_keylogger/sslkeylog.so /usr/lib/x86_64-linux-gnu/libssl.so.3" In my environment we're using "packetbuffer_sender = yes" to copy all packets to a central processor. I'm sending the keys to localhost so they can get picked up by the sniffer instead of sending them separately to the central processor. For this to work, the sniffer also must capture the "lo" interface. __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: SSL key logger for Diffie-Hellman cipher
Ok so for whatever reason Kamailio is not sending keys, but if I try on the same machine with openssl binary directly I do see keys being sent to the voipmonitor-sniffer. I will report here what I find for anyone else that runs into this. On Tue, Mar 5, 2024 at 1:43 PM Joel Serrano wrote: > Hey Calvin, > > Did you have to do anything special with OpenSSL and/or Kamailio to > get LD_PRELOAD to work and send the keys to voipmonitor? > > I can see the env vars are loaded correctly, but I don't see any keys > being sent to the sniffer on port 1234 udp. > > root@csbc03:~# ps -fe | grep kamailio > kamailio 2209068 1 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209069 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209070 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209071 2209068 0 16:33 ?00:00:02 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209072 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209073 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209074 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209075 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209076 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209077 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209078 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209080 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209082 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209083 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209084 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209086 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209087 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209088 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209089 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209090 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209091 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209092 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209093 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209094 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209095 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209096 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209097 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 > --atexit=no > kamailio 2209098 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P > /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg
[SR-Users] Re: SSL key logger for Diffie-Hellman cipher
Hey Calvin, Did you have to do anything special with OpenSSL and/or Kamailio to get LD_PRELOAD to work and send the keys to voipmonitor? I can see the env vars are loaded correctly, but I don't see any keys being sent to the sniffer on port 1234 udp. root@csbc03:~# ps -fe | grep kamailio kamailio 2209068 1 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209069 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209070 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209071 2209068 0 16:33 ?00:00:02 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209072 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209073 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209074 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209075 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209076 2209068 0 16:33 ?00:00:03 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209077 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209078 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209080 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209082 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209083 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209084 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209086 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209087 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209088 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209089 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209090 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209091 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209092 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209093 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209094 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209095 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209096 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209097 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209098 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209099 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209100 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32 --atexit=no kamailio 2209101 2209068 0 16:33 ?00:00:00 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/csbc.cfg -m 512 -M 32
[SR-Users] Re: Add XML to INVITE
Hi David,
I am always very cautious when using msg_apply_changes() – e.g. there are some
implications with Record-Route, afaik
I do it this way:
set_body("--outer\r\nContent-Type:application/sdp\r\n\r\n$rb" +
"\r\n--outer\r\nContent-Type:application/vnd.3gpp.mcptt-info+xml\r\n\r\n" +
"\r\n" +
"\t\r\n" +
"\r\n--outer--\r\n",
"multipart/mixed;boundary=\"outer\"");
Hope this helps, and sorry for slow reaction. I am scanning the mailing list in
rather low frequency.
Kr
From: David Villasmil via sr-users
Sent: Tuesday, March 5, 2024 7:08 PM
To: Kamailio (SER) - Users Mailing List
Cc: David Villasmil
Subject: [SR-Users] Re: Add XML to INVITE
Hello guys,
Anyone on this?
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Sun, Mar 3, 2024 at 4:01 AM David Villasmil
mailto:david.villasmil.w...@gmail.com>> wrote:
Hello guys,
I'm trying to add an xml with a boundary to an outgoing INVITE. But if i do:
set_body_multipart("$rb", "application/sdp", "delimiter");
msg_apply_changes();
append_body_part("$var(something)", "application/pidf+xml");
msg_apply_changes();
but kamailio adds the SDP, but NOT the second $var(something). If i switch them
and add firs the var, and then the SDP. kamailio adds the contents of
$var(something) but NOT the SDP point is it doesn't add the second append
Thanks!!!
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: dispatcher - sip options per gw
And use the flag 8, according
Optionally, these fields can be followed by:
flags - control the mode of using the destination address and sending
keepalives. It is a bitwise value that can be built using the following flags:
1 (bit at index 0 - 1 <<0) - inactive destination
2 (bit at index 1 - 1 <<1) - temporary trying destination (in the way to become
inactive if it does not reply to keepalives - there is a module parameter to
set the threshold of failures)
4 (bit at index 2 - 1 <<2) - admin disabled destination
8 (bit at index 3 - 1 <<3) - probing destination (sending keep alives);
16 (bit at index 4 - 1 <<4) - skip DNS A/ resolve at startup, useful when
the hostname of the destination address is a NAPTR or SRV record only. Such
addresses cannot be matched anymore with ds_is_from_list(...).
-Original Message-
From: Valentin Christoph
Sent: Tuesday, March 5, 2024 7:04 PM
To: Kamailio (SER) - Users Mailing List
Cc: marek
Subject: RE: [SR-Users] dispatcher - sip options per gw
You must set the module parameter
## probing mode 3 is necessary, if you want to selectively disable OPTIONS
#!define DS_PROBING_MODE 3
# Actively query the gateways:
modparam("dispatcher", "ds_probing_mode", DS_PROBING_MODE)
Kr,
Christoph
-Original Message-
From: marek via sr-users
Sent: Tuesday, March 5, 2024 2:10 PM
To: Kamailio (SER) - Users Mailing List
Cc: marek
Subject: [SR-Users] dispatcher - sip options per gw
hi,
i have kamailio gw (5.6.x) for voxbone. dispatcher module
voxbone has separated inbound/outboud and prohibit sip options to "inbound" IP
#traffic from voxbone
20 sip:81.201.82.45:5060;transport=udp 1 0 duid=abc;socket=udp:x.x.x.x:5060
#traffic TO voxbone
30 sip:81.201.89.110:5060;transport=udp 0 0 duid=abc;socket=udp:x.x.x.x:5060
is it possible send sip options per GW with dispatcher module?
i tried flag "1 (bit at index 0 - 1 <<0) - inactive destination"
https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#idm1059
Marek
__
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send
an email to sr-users-le...@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-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: Add XML to INVITE
Hello guys,
Anyone on this?
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Sun, Mar 3, 2024 at 4:01 AM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> Hello guys,
>
> I'm trying to add an xml with a boundary to an outgoing INVITE. But if i
> do:
>
> set_body_multipart("$rb", "application/sdp", "delimiter");
> msg_apply_changes();
> append_body_part("$var(something)", "application/pidf+xml");
> msg_apply_changes();
>
> but kamailio adds the SDP, but NOT the second $var(something). If i switch
> them and add firs the var, and then the SDP. kamailio adds the contents of
> $var(something) but NOT the SDP point is it doesn't add the second
> append
>
>
> Thanks!!!
>
>
> Regards,
>
> David Villasmil
> email: david.villasmil.w...@gmail.com
> phone: +34669448337
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] Re: dispatcher - sip options per gw
You must set the module parameter
## probing mode 3 is necessary, if you want to selectively disable OPTIONS
#!define DS_PROBING_MODE 3
# Actively query the gateways:
modparam("dispatcher", "ds_probing_mode", DS_PROBING_MODE)
Kr,
Christoph
-Original Message-
From: marek via sr-users
Sent: Tuesday, March 5, 2024 2:10 PM
To: Kamailio (SER) - Users Mailing List
Cc: marek
Subject: [SR-Users] dispatcher - sip options per gw
hi,
i have kamailio gw (5.6.x) for voxbone. dispatcher module
voxbone has separated inbound/outboud and prohibit sip options to "inbound" IP
#traffic from voxbone
20 sip:81.201.82.45:5060;transport=udp 1 0 duid=abc;socket=udp:x.x.x.x:5060
#traffic TO voxbone
30 sip:81.201.89.110:5060;transport=udp 0 0 duid=abc;socket=udp:x.x.x.x:5060
is it possible send sip options per GW with dispatcher module?
i tried flag "1 (bit at index 0 - 1 <<0) - inactive destination"
https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#idm1059
Marek
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@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-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the
sender!
Edit mailing list options or unsubscribe:
[SR-Users] dispatcher - sip options per gw
hi, i have kamailio gw (5.6.x) for voxbone. dispatcher module voxbone has separated inbound/outboud and prohibit sip options to "inbound" IP #traffic from voxbone 20 sip:81.201.82.45:5060;transport=udp 1 0 duid=abc;socket=udp:x.x.x.x:5060 #traffic TO voxbone 30 sip:81.201.89.110:5060;transport=udp 0 0 duid=abc;socket=udp:x.x.x.x:5060 is it possible send sip options per GW with dispatcher module? i tried flag "1 (bit at index 0 - 1 <<0) - inactive destination" https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#idm1059 Marek __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] direct media between UACs
Hi all! got a weird behavior that I cannot understand the reason for... In our LAB environment, we have 2 Asterisk instances (version 13.38.3 and chan_sip) and 1 Kamailio 5.7 in between. All servers are in the same network, so, there is no NAT involved. No RTPEngine either. Network is 10.20.0.0/24 and Asterisk #1 has IP .1 Asterisk #2 has IP .3 and Kamailio has IP .5 The Asterisk servers are used only for testing, nothing serious. However, Kamailio is setup to use RTJson requesting routes to a Routing Server on the same network. And it works fine. Both Asterisk servers have the same dialplan, which only Answers the call and plays MOH on both ends so that RTP audio streams both ways. When making a call on Asterisk Server #1 via command line to go directly to Asterisk Server #2 without using Kamailio (CLI> channel originate SIP/123@10.20.0.3 application MusicOnHold() ) the Asterisk #2 receives the call, answers and plays MOH too and I can see RTP streams coming from both ends correctly. However, if I use Kamailio to proxy the call generated from Asterisk #1 to Asterisk #2, using similar command line instruction (CLI> channel originate SIP/123@10.20.0.5 application MusicOnHold() ), the call is indeed received on Kamailio who then sends it to Asterisk #2, who answers the call and plays MOH, *but* despite the audio stream being sent to Asterisk #1 it is never received, however audio from Asterisk #1 is received by Asterisk #2, which configures a typical One Way Audio issue due to NAT. This is where it gets strange, because there is no NAT, SDP on INVITE and SIP 200 messages seem OK, as far as I understand it. Also, Asterisk servers have SIP configuration with directmedia enabled and NAT disabled to make sure that media is direct. But I have also tried with directmedia disabled and NAT enabled and get identical results. I am most probably missing some tiny detail, but I have no clue and I bet it is simple and stupid Could another pair of eyes help me with this? What is wrong? Do I really need RTPEngine even when the network has no NAT? I am sure it would work that way, but it doesn't make sense... Here are some screenshots: Call Scenario #1 - direct call from Asterisk #1 to Asterisk #2 without Kamailio in between: Invite from Asterisk #1 to Asterisk #2 with direct media between both ends: https://drive.google.com/file/d/1eLjT3nr_Rc-UBaf4QhIgZ95bjETOVvxo/view?usp=drive_link Replies from Asterisk #2 to Asterisk #1 with direct media between both ends: https://drive.google.com/file/d/11lLcB-V8rWGSrVqWiit-q9WX2FfqB6BZ/view?usp=drive_link Call Scenario #2 - call from Asterisk #1 using Kamailio to relay call to Asterisk #2, with one way audio Invite from Asterisk #1 to Asterisk #2 via Kamailio with SDP details: https://drive.google.com/file/d/1Cp9xrGcwNmQ9Ks36N_oD1Dj7lxfu-tbH/view?usp=drive_link Invite from Kamailio relayed to Asterisk #2 with SDP details from Asterisk #1 identical to above: https://drive.google.com/file/d/1mi3FCNjM3luXfENEp-0088XLgcyfXRK6/view?usp=drive_link Reply from Asterisk #2 to Kamailio with SDP details: https://drive.google.com/file/d/1TpMGe2tvpX_5SIpSbm2b3Zro9EuYwcO-/view?usp=drive_link Reply from Kamailio to Asterisk #2 with SDP details from Asterisk #2 identical to above: https://drive.google.com/file/d/12jq5APfFwVVPc0vJ3RkcXyN1hBE51fnQ/view?usp=drive_link As we can see, SDP details seem OK, but if I check call flow on Asterisk #1, I can only find 1 RTP channel with audio coming from Asterisk #2 https://drive.google.com/file/d/1iEfvkylZVbthHM5kxkurWh-GAYCYLytl/view?usp=drive_link and the same on Asterisk #2 : https://drive.google.com/file/d/12rvf9Lrwp-MNZvGCwlXEEBsBRmfcinph/view?usp=drive_link My Kamailio.cfg is as follows: #!KAMAILIO # # config file for SIPProxy # - load balancing of VoIP calls # - no TPC listening # # Kamailio (OpenSER) SIP Server v3.2 # - web: http://www.kamailio.org # - git: http://sip-router.org # # # Refer to the Core CookBook at http://www.kamailio.org/dokuwiki/doku.php # for an explanation of possible statements, functions and parameters. # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # #!define WITH_DEBUG ###!define WITH_NAT #!define WITH_PSTN /* enables Accounting Log functions */ #!define FLT_ACC 1 /* enable Accounting of missed or failed calls */ #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 /* defines DB connection string */ #!ifndef DBURL #!define DBURL "mysql://kamailio:kamailio@10.20.0.1:3306/kamailio" #!endif # - the value for 'use_domain' parameters #!define MULTIDOMAIN 1 ### Global Parameters # #!ifdef WITH_DEBUG debug=4 log_stderror=no #!else debug=2 log_stderror=no #!endif #!define FLT_DISPATCH_SETID 1 #!define FLT_FS 10 #!define FLT_NATS 5 #!define FLB_NATB 6 #!define FLB_NATSIPPING 7 #!define FLT_SRC_ALLOWED 8 #!define FLT_DST_INTERNAL_IP 9 #!define FLT_SRC_INTERNAL_IP 10 #!substdef
