sr-users

sr-users@lists.kamailio.org

42 participants
37518 discussions

Fwd: [CFP] FOSDEM 2020, RTC devroom, speakers, volunteers neeeded
by fosdem-rtc-admin＠freertc.org 28 Oct '19

28 Oct '19

FOSDEM - Real Time Communications devroom CfP ============================================= Overview -------- [FOSDEM](https://fosdem.org) is one of the world's premier meetings of free software developers, with over five thousand people attending each year. FOSDEM 2020 takes place 1-2 February 2020 in Brussels, Belgium. This document contains information about: - Real-Time Communications developer room (devroom) and lounge - speaking opportunities - volunteering in the devroom and lounge - social events (the legendary FOSDEM Beer Night and Saturday night dinners provide endless networking opportunities) - the Planet aggregation sites for RTC blogs **NEW:** Save yourself entering Free-RTC events and CFP deadlines into your calendar and task list, follow our iCalendar feed: https://freertc.org/events.ics Call for participation - Real Time Communications (RTC) ------------------------------------------------------- The Real-Time devroom and Real-Time lounge are about all things involving real-time communication, including: XMPP, SIP, WebRTC, telephony, mobile VoIP, codecs, peer-to-peer, privacy and encryption. **We are looking for speakers for the devroom and volunteers and participants for the tables in the Real-Time lounge.** The devroom is only on Sunday, 2nd of February 2020. The lounge will be present for both days. To discuss the devroom and lounge, please join the [Free-RTC mailing list](http://lists.freertc.org/mailman/listinfo/discuss). ### Speaking opportunities Note: if you used FOSDEM Pentabarf before, please use the same account/username Real-Time Communications devroom: deadline 23:59 UTC on 15th of December. Please use the [Pentabarf](https://penta.fosdem.org/submission/FOSDEM20/) system to submit a talk proposal for the devroom. On the "General" tab, please look for the "Track" option and choose "Real Time Communications devroom". Other devrooms and lightning talks: some speakers may find their topic is in the scope of more than one devroom. It is encouraged to apply to more than one devroom and also consider proposing a lightning talk, but please be kind enough to tell us if you do this by filling out the notes in the form. Here you can find the [full list of devrooms](https://www.fosdem.org/2020/schedule/tracks/) and here you can apply for a [lightning talk](https://fosdem.org/submit). ### First-time speaking? FOSDEM devrooms are a welcoming environment for people who have never given a talk before. Please feel free to contact the devroom administrators personally if you would like to ask any questions about it. ### Submission guidelines The Pentabarf system will ask for many of the essential details. Please remember to re-use your account from previous years if you have one. In the "Submission notes", please tell us about: - The purpose of your talk - Any other talk applications (devrooms, lightning talks, main track) - Availability constraints and special needs You can use HTML and links in your bio, abstract and description. If you maintain a blog, please consider providing us with the URL of a feed with posts tagged for your RTC-related work. We will be looking for relevance to the conference and devroom themes, presentations aimed at developers of free and open source software about RTC-related topics. Please feel free to suggest a duration between 20 minutes and 55 minutes but note that the final decision on talk durations will be made by the devroom administrators based on the number of received proposals. As the two previous devrooms have been combined into one, we may decide to give shorter slots than in previous years so that more speakers can participate. Please note FOSDEM aims to record and live-stream all talks. The CC-BY license is used. Volunteers needed ----------------- To make the devroom and lounge run successfully, we are looking for volunteers: - FOSDEM provides video recording equipment and live streaming, volunteers are needed to assist in this - Organizing one or more restaurant bookings (dependending upon number of participants) for the evening of Saturday, 1 February - Participation in the Real-Time lounge - Circulating this Call for Participation to other mailing lists Social events and dinners ------------------------- The traditional FOSDEM beer night occurs on Friday, 31st of January. On Saturday night, there are usually dinners associated with each of the devrooms. Most restaurants in Brussels are not so large so these dinners have space constraints and reservations are essential. Please subscribe to the [Free-RTC mailing list](http://lists.freertc.org/mailman/listinfo/discuss) for further details about the Saturday night dinner options and how you can register for a seat. Related events around FOSDEM ---------------------------- As per usual, the [XMPP Summit](https://wiki.xmpp.org/web/Conferences/Summit_24) is happening ahead of FOSDEM. This time it will take place on the 30th and 31st of January also in Brussels. All details are available on the [summit website](https://wiki.xmpp.org/web/Conferences/Summit_24). Spread the word and discuss --------------------------- If you know of any mailing lists where this CfP would be relevant, please forward this document. If this devroom excites you, please blog or microblog about it, especially if you are submitting a talk. If you regularly blog about RTC topics, please send details about your blog to the planet site administrators: - All projects https://planet.freertc.org planet(a)freertc.org - XMPP https://planet.jabber.org ralphm(a)ik.nu - SIP https://planet.sip5060.net planet(a)sip5060.net - (Español) https://planet.sip5060.net/es/ planet(a)sip5060.net Please also link to the Planet sites from your own blog or web site as this helps everybody in the free real-time communications community. Contact ------- For any private queries, contact us directly using the address **fosdem-rtc-admin(a)freertc.org** and for any other queries please ask on the [Free-RTC mailing list](http://lists.freertc.org/mailman/listinfo/discuss). The devroom administration team: - Saúl Ibarra Corretgé <s(a)saghul.net> - Ralph Meijer <ralphm(a)ik.nu> - Daniel-Constantin Mierla <miconda(a)gmail.com> - Daniel Pocock <daniel(a)pocock.pro> - Guus der Kinderen <guus.der.kinderen(a)gmail.com>

1 0

Rewrite contact address on 200 OK?
by Oded Arbel 28 Oct '19

28 Oct '19

Hi, we are having a problem with a network change use case. It goes on something like this: 1. Kamailio receives INVITE from caller. 2. Kamailio sends INVITE to callee MUA. 3. MUA response with 100, then 183. 4. MUA then loses network connectivity and re-establishes access with another IP address. 5. MUA sends 200 OK from the new IP address, but with `Contact` still set as the old address (which I think it should, because you aren't allowed to change contact in the middle of dialog?) 6. Kamailio forwards 200 OK to caller and receives ACK. 7. Kamailio sends ACK to old IP address of MUA. The last step is obviously a problem as the MUA will not be able to see the ACK. I'm trying to see how to resolve this issue. I can capture the "$si" and "$sp" of the new address in the reply route (I also tried to get the MUA to send OPTIONS immediately after reestablishing connectivity, and capture "$si"/"$sp" there, which also works), but I can't figure out how to update the destination of the ACK. I've tried running `fix_nated_contact()` as well as trying to write into various pseudo variables - in either the OPTIONS request handler or the 200 reply handler - which either errors or does nothing. Any suggestions? -- Oded Arbel

2 4

Kamailio to capture mirrored traffic
by Igor Olhovskiy 28 Oct '19

28 Oct '19

Hi! I'm trying to get Kamailio working as a traffic capture on a same machine with other PBX software installed. Actually, traffic is mirrored with iptables -A PREROUTING -t mangle -i eth0 -p udp --dport 5060 -j TEE --gateway 127.0.0.2 (https://link.getmailspring.com/link/AB5F9D36-533D-4A52-ADE3-FB76B813163C@ge…) iptables -t nat -A PREROUTING -d 127.0.0.2 -p udp --dport 5060 -j DNAT --to 127.0.0.1:5062 (https://link.getmailspring.com/link/AB5F9D36-533D-4A52-ADE3-FB76B813163C@ge…) Kamailio request route is super simple request_route { xlog("L_ALERT", "[SIP-PACKET] Got packet [F=$fu R=$ru D=$du M=$rm IP=($si:$sp $Ri:$Rp) ID=$ci]\n"); drop; } I was trying to get Kamailio just listen on interface 127.0.0.1:5062, but no luck listen=udp:127.0.0.1:5062 Next was to use sipcapture module with following parameters loadmodule "sipcapture.so" modparam("sipcapture", "db_url", "text:///tmp/") modparam("sipcapture", "raw_socket_listen", "127.0.0.1:5060-5062") modparam("sipcapture", "raw_interface", "lo") modparam("sipcapture", "promiscious_on", 1) Also no luck. Means Kamailio can't see packets, but I see em with wireshark on lo interface. What is best way to get it working? Or I'm missing something? Thanks!

5 7

Cancel / OK handling
by Oz Mortimer 26 Oct '19

26 Oct '19

Hi, I have an issue where a client is sending cancel after the call has been answered but before the client received the 200OK, I know they should then respond with a BYE based on the 200 final result, but they don’t (Meaning the call / billing stays up).. Is there a way I can timeout a call/force BYE if ACK is not received to the 200 OK? I know technically this is the clients issue but they can’t / won’t fix Thanks is advance Oz.

1 0

No audio after hold and unhold event
by arish haque 25 Oct '19

25 Oct '19

Hi all, No Audio flows between the two parties when one side resumes the call after putting on hold. Configuration - WebRTC <--> Kamailio <--> Asterisk Below is the warning I'm getting in asterisk console WARNING[32388]: chan_sip.c:10425 process_sdp: Declining non-primary audio stream: audio 10596 UDP/TLS/RTP/SAVPF 107 103 104 9 0 8 106 105 13 110 112 113 101 Is this a codec issue or something else. Thanks, Arish

1 0

Kamailio 3.3.7
by Brandon Armstead 24 Oct '19

24 Oct '19

Has anyone seen this error while compiling 3.3.7 raw_sock.c:431: undefined reference to `udpv4_vhdr_sum' system: Linux 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3 (2019-09-02) x86_64 GNU/Linux lsmod: Module Size Used by bonding 147456 0 intel_rapl 20480 0 x86_pkg_temp_thermal 16384 0 intel_powerclamp 16384 0 coretemp 16384 0 kvm_intel 200704 0 kvm 598016 1 kvm_intel irqbypass 16384 1 kvm ttm 98304 0 drm_kms_helper 155648 0 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 joydev 20480 0 evdev 24576 3 ghash_clmulni_intel 16384 0 drm 360448 2 ttm,drm_kms_helper i2c_algo_bit 16384 0 iTCO_wdt 16384 0 shpchp 36864 0 ipmi_si 57344 0 iTCO_vendor_support 16384 1 iTCO_wdt sg 32768 0 pcspkr 16384 0 mei_me 36864 0 ipmi_msghandler 49152 1 ipmi_si mei 102400 1 mei_me video 40960 0 button 16384 0 acpi_power_meter 20480 0 acpi_pad 24576 0 ib_iser 49152 0 rdma_cm 53248 1 ib_iser iw_cm 49152 1 rdma_cm ib_cm 45056 1 rdma_cm ib_core 208896 4 ib_iser,ib_cm,rdma_cm,iw_cm configfs 40960 2 rdma_cm iscsi_tcp 20480 0 libiscsi_tcp 24576 1 iscsi_tcp libiscsi 53248 3 ib_iser,libiscsi_tcp,iscsi_tcp scsi_transport_iscsi 102400 4 ib_iser,libiscsi,iscsi_tcp ip_tables 24576 0 x_tables 36864 1 ip_tables autofs4 40960 2 ext4 589824 2 crc16 16384 1 ext4 jbd2 106496 1 ext4 crc32c_generic 16384 0 fscrypto 28672 1 ext4 ecb 16384 0 mbcache 16384 3 ext4 sd_mod 49152 4 hid_generic 16384 0 usbhid 53248 0 hid 122880 2 hid_generic,usbhid crc32c_intel 24576 2 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel glue_helper 16384 1 aesni_intel lrw 16384 1 aesni_intel gf128mul 16384 1 lrw ablk_helper 16384 1 aesni_intel cryptd 24576 3 ablk_helper,ghash_clmulni_intel,aesni_intel ahci 40960 3 xhci_pci 16384 0 libahci 32768 1 ahci ixgbe 294912 0 xhci_hcd 188416 1 xhci_pci i2c_i801 24576 0 i2c_smbus 16384 1 i2c_i801 dca 16384 1 ixgbe ptp 20480 1 ixgbe libata 249856 2 ahci,libahci pps_core 16384 1 ptp mdio 16384 1 ixgbe usbcore 253952 3 usbhid,xhci_pci,xhci_hcd scsi_mod 225280 7 ib_iser,sd_mod,libiscsi,libata,scsi_transport_iscsi,iscsi_tcp,sg usb_common 16384 1 usbcore fan 16384 0 thermal 20480 0 I believe I've crossed this issue once before and it was a simple apt-get package to include compile options: make include_modules="mi_fifo db_mysql tm dialog sl tmx kex rr maxfwd textops textopsx nathelper acc avpops xlog uac alias_db siputils utils usrloc registrar pv regex htable sqlops sdpops topoh ctl db_mysql mysql" prefix="/usr/local" Thanks - Brandon

3 3

environmental variables in kamailio
by Gaurav Bmotra 24 Oct '19

24 Oct '19

hi i using kamailio 5.2 is it possible to use environmental variables value in kamailio.cfg like i want to use local ip and public ip in config file listen=udp:$(local_ip):5060 advertise $(public_ip):5060 if iti is possible then how i can use this thank you -- *Regards:* Gaurav Kumar

4 3

driver error: Can't connect to MySQL server with kamailio 5.3.x and mysql-config-groups
by Karsten Horsmann 23 Oct '19

23 Oct '19

Hi List, i updated one of my testing kamailios from 5.2.x to latest 5.3.x. After restarting the process, i got an mysql error that the server "kamailio" is not found. I use the config-feature of my.cnf config-group names within the kamailio.cfg I can start my kamailio 5.3.x installation with "normal username:password@host" definitions for DBURL. Did anyone have the same issue? 0(19625) ERROR: db_mysql [km_my_con.c:139]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'kamailio' (4) 0(19625) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool 0(19625) ERROR: dialplan [dp_db.c:179]: dp_connect_db(): unable to connect to the database 0(19625) ERROR: dialplan [dialplan.c:191]: mod_init(): could not initialize data 0(19625) ERROR: <core> [core/sr_module.c:850]: init_mod(): Error while initializing module dialplan (/usr/lib64/kamailio/modules/dialplan.so) ERROR: error while initializing modules from my kamailio.cfg i defined the DBURL like this: # Use /etc/my.cnf.d/kamailio.cnf to store credentials # within a mysql-db-group #!define DBURL "mysql://[kamailio]/kamailio" and special modules can use it like this (or via DBURL) modparam("sqlops", "sqlcon", "cb=>mysql://[kamailio]/kamailio") cat /etc/my.cnf.d/kamailio.cnf # MySQL configuration group for kamailio [kamailio] user=kamailio password="kamailiorw" host=172.20.100.22 rpm -qa | grep kam kamailio-dialplan-5.3.0-13.1.x86_64 kamailio-websocket-5.3.0-13.1.x86_64 kamailio-jansson-5.3.0-13.1.x86_64 kamailio-mysql-5.3.0-13.1.x86_64 kamailio-tls-5.3.0-13.1.x86_64 kamailio-ims-5.3.0-13.1.x86_64 kamailio-statsd-5.3.0-13.1.x86_64 kamailio-5.3.0-13.1.x86_64 kamailio-redis-5.3.0-13.1.x86_64 cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) -- Cheers *Karsten Horsmann*

3 7

MS Teams Direct routing with kamailio
by Karsten Horsmann 23 Oct '19

23 Oct '19

Hello List, i search for the right place in kamailio to manipulate the dispatcher OPTIONS packets to add an Contact header. For uac generated traffic i can use the event_route[tm:local-request] from the tm module. But how can i manipulate kamailio *self* generated OPTION pings from the dispatcher? OPTIONS request for MS Teams must contain the Contact header of such a format: Contact: <sip:SBC_FQDN:5061;transport=tls> I follow this guide (for opensips) and try to adapt that step by step to kamailio: https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/ CentOS 7 / kamailio 5.2.x (and maybe soon 5.3.x) / rtpengine -- Cheers *Karsten Horsmann*

2 2

Unable to use BLF
by Cehes (Free) 23 Oct '19

23 Oct '19

Hi all, This is many days we are trying many things and reading many threads :) We also re installed a simple brand new kamailio to be sure everything is ok. In fact, with sngrep we can see "subscribe" arriving on kamailio but on syslog we have a critical error : Oct 23 10:08:42 GTO-Temp01 kamailio[2004]: 20(2027) exec: {1 29 SUBSCRIBE 3135373137353930373733323337-joash9r9lnre} *** cfgtrace:request_route=[PRESENCE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=770 a=24 n=handle_subscribe Oct 23 10:08:42 GTO-Temp01 kamailio[2004]: 20(2027) CRITICAL: {1 29 SUBSCRIBE 3135373137353930373733323337-joash9r9lnre} <core> [core/mem/q_malloc.c:494]: qm_free(): *BUG: bad pointer 0xa (out of memory block!) *called from presence: *subscribe.c*: handle_subscribe(1040) - ignoring We tried to start kamailio with many more memory (x4) and this is the same. We tried with only "presenceXXX" plugins, and also with "puaXXX" plugins below is our config file : https://gist.github.com/Dyriolon/e894b9f2a67f9dfb7117421717ad6178 Any idea of what is wrong ? Thanks!

1 0

Jump to page:

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