sr-users February 2015

sr-users@lists.kamailio.org

95 participants
131 discussions

Issues after Ubuntu Server Update and WebRTC
by Manuel Camargo Lominchar 13 Feb '15

13 Feb '15

>* Is the SIP signaling still going fine via websocket? Do you get callee *>* ringing? *>>* Cheers, *>* Daniel* Hello Daniel Actually SIP signalling goes perfect, and i can see in RTP asterisk log that RTP packets are being sent, so I suppose there is something stuck somewhere in RTP maybe related with RTP Engine >Hi, > >If you are using rtpengine for the rtp you might have to upgrade to a >newer version. > >On my system crypto negotiation in rtpengine started failing after a >openssl update in January. Recompiling a newer version from git fixed that. > >regards > >M I updated to latest version through git but still stuck there. Now I can see that the config file (ngcp-rtpengine in etc default) has changed so I'm not sure how should this impact (not ADDRESS neither ADV ADDRESS now I see an Interfaces parameter) I also find for some reason very possible that somehow rtp traffic is not getting through. ICE candidates are being negotiated, so I feel that the route is clear, so maybe there might be some crypto issues as you point out, but update has not been enough :( Any other ideas? *Manuel Camargo* Teléfono: 638000836 eMail: sir.louen(a)gmail.com <https://twitter.com/SirLouen> [image: Ver el perfil de Manuel Camargo Lominchar en LinkedIn] <http://es.linkedin.com/in/louen>

1 1

change_reply_status() 415 -> 200 change
by Juha Heinanen 13 Feb '15

13 Feb '15

i tried to use change_reply_status() to change 415 to 200, but got: ERROR: textopsx [textopsx.c:283]: change_reply_status_f(): ERROR: textops: the class of provisional or positive final replies cannot be changed textopsx/README does not mention anything about what can or cannot be changed. why is it that the above change cannot be made? -- juha

2 1

Issues after Ubuntu Server Update and WebRTC
by Manuel Camargo Lominchar 13 Feb '15

13 Feb '15

This might be a weird question I've been operating for some months with my kam + asterisk + webrtc sipml5 based system inside an Ubuntu Server Today I had the idea to apt-get upgrade my system and... now the whole system webrtc communication service is dead Here is the VAST list of packages updated... But I cannot figure out who is the "destroyer" package. No prompts appeared during the update so I believe no config files have been updated I'm trying to debug but I cant find a solution The handshake is done, and in Wireshark the only thing I find is that no UDP (RTP) packages are being processed, but in the SIP log I can see ICE candidates and all process is done I tried to do a direct SIP connection without WebRTC, and it worked pretty fine, so this have something to do with maybe crypt libs, or something to do with kamailio and imcompatibilities with one of this packages. Kamailio Version: # kamailio -v version: kamailio 4.1.5 (x86_64/linux) 2b3d4b flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 2b3d4b compiled on 14:39:42 Aug 28 2014 with gcc 4.8.2 Any ideas of where to start digging? Start-Date: 2015-02-12 14:40:19 Install: linux-image-extra-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), linux-image-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), linux-headers-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), linux-headers-3.13.0-45:amd64 (3.13.0-45.74, automatic) Upgrade: bind9-host:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), python3-problem-report:amd64 (2.14.1-0ubuntu3.5, 2.14.1-0ubuntu3.6), mime-support:amd64 (3.54ubuntu1, 3.54ubuntu1.1), liblwres90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), apt:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), libevent-2.0-5:amd64 (2.0.21-stable-1ubuntu1, 2.0.21-stable-1ubuntu1.14.04.1), libsystemd-login0:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), linux-headers-generic:amd64 (3.13.0.37.44, 3.13.0.45.52), mysql-server-core-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), ppp:amd64 (2.4.5-5.1ubuntu2, 2.4.5-5.1ubuntu2.1), mysql-server-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), multiarch-support:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libdns100:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), krb5-multidev:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), mysql-client-core-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), libisccfg90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), systemd-services:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), apt-transport-https:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), procps:amd64 (3.3.9-1ubuntu2, 3.3.9-1ubuntu2.2), libbind9-90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), tcpdump:amd64 (4.5.1-2ubuntu1, 4.5.1-2ubuntu1.1), dbus:amd64 (1.6.18-0ubuntu4.2, 1.6.18-0ubuntu4.3), libgssapi-krb5-2:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libapache2-mod-php5:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), php5-mysql:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), python-urllib3:amd64 (1.7.1-1build1, 1.7.1-1ubuntu0.1), dkms:amd64 (2.2.0.3-1.1ubuntu5, 2.2.0.3-1.1ubuntu5.14.04), php5-common:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), coreutils:amd64 (8.21-1ubuntu5, 8.21-1ubuntu5.1), libkrb5-3:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), apt-utils:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), cpio:amd64 (2.11+dfsg-1ubuntu1, 2.11+dfsg-1ubuntu1.1), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu17, 0.8.8-0ubuntu17.1), python3-software-properties:amd64 (0.92.37.1, 0.92.37.3), libkadm5clnt-mit9:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), mount:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), libsystemd-daemon0:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), python-apt:amd64 (0.9.3.5, 0.9.3.5ubuntu1), libc-dev-bin:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libcgmanager0:amd64 (0.24-0ubuntu7, 0.24-0ubuntu7.2), file:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3), libapparmor1:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), libkrb5-dev:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libmagic1:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3), libpam-systemd:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), libc-bin:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libc6:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libglib2.0-0:amd64 (2.40.0-2, 2.40.2-0ubuntu1), php5-readline:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), libprocps3:amd64 (3.3.9-1ubuntu2, 3.3.9-1ubuntu2.2), libsepol1:amd64 (2.2-1, 2.2-1ubuntu0.1), libglib2.0-dev:amd64 (2.40.0-2, 2.40.2-0ubuntu1), libapt-inst1.5:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), libuuid1:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), libmount1:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), dnsutils:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), libdbus-1-3:amd64 (1.6.18-0ubuntu4.2, 1.6.18-0ubuntu4.3), udev:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), curl:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), update-notifier-common:amd64 (0.154.1, 0.154.1ubuntu1), plymouth:amd64 (0.8.8-0ubuntu17, 0.8.8-0ubuntu17.1), libglib2.0-data:amd64 (2.40.0-2, 2.40.2-0ubuntu1), mysql-client-5.5:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), krb5-locales:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libxml2:amd64 (2.9.1+dfsg1-3ubuntu4.3, 2.9.1+dfsg1-3ubuntu4.4), ntp:amd64 (4.2.6.p5+dfsg-3ubuntu2, 4.2.6.p5+dfsg-3ubuntu2.14.04.2), libudev1:amd64 (204-5ubuntu20.7, 204-5ubuntu20.9), binutils:amd64 (2.24-5ubuntu3, 2.24-5ubuntu3.1), bsdutils:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), libxml2-dev:amd64 (2.9.1+dfsg1-3ubuntu4.3, 2.9.1+dfsg1-3ubuntu4.4), libapparmor-perl:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), lshw:amd64 (02.16-2ubuntu1, 02.16-2ubuntu1.2), libssl-dev:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), wget:amd64 (1.15-1ubuntu1, 1.15-1ubuntu1.14.04.1), libapt-pkg4.12:amd64 (1.0.1ubuntu2.5, 1.0.1ubuntu2.6), uuid-runtime:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), python3-apt:amd64 (0.9.3.5, 0.9.3.5ubuntu1), mysql-common:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), php5-cli:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), libmysqlclient18:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), git-man:amd64 (1.9.1-1, 1.9.1-1ubuntu0.1), libplymouth2:amd64 (0.8.8-0ubuntu17, 0.8.8-0ubuntu17.1), libmysqlclient-dev:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), git:amd64 (1.9.1-1, 1.9.1-1ubuntu0.1), python3-distupgrade:amd64 (0.220.5, 0.220.7), libcurl3:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), apport:amd64 (2.14.1-0ubuntu3.5, 2.14.1-0ubuntu3.6), linux-firmware:amd64 (1.127.7, 1.127.11), libssl-doc:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), libcurl4-gnutls-dev:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), landscape-common:amd64 (14.01-0ubuntu3, 14.12-0ubuntu0.14.04), libblkid1:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), python3-apport:amd64 (2.14.1-0ubuntu3.5, 2.14.1-0ubuntu3.6), apparmor:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), tzdata:amd64 (2014e-0ubuntu0.14.04, 2015a-0ubuntu0.14.04), mysql-server:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), software-properties-common:amd64 (0.92.37.1, 0.92.37.3), openssl:amd64 (1.0.1f-1ubuntu2.7, 1.0.1f-1ubuntu2.8), libelf1:amd64 (0.158-0ubuntu5.1, 0.158-0ubuntu5.2), libglib2.0-bin:amd64 (2.40.0-2, 2.40.2-0ubuntu1), libkdb5-7:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), ubuntu-release-upgrader-core:amd64 (0.220.5, 0.220.7), linux-libc-dev:amd64 (3.13.0-37.64, 3.13.0-45.74), util-linux:amd64 (2.20.1-5.1ubuntu20.2, 2.20.1-5.1ubuntu20.3), python-apt-common:amd64 (0.9.3.5, 0.9.3.5ubuntu1), php5-gd:amd64 (5.5.9+dfsg-1ubuntu4.4, 5.5.9+dfsg-1ubuntu4.5), libgssrpc4:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libdrm2:amd64 (2.4.52-1, 2.4.56-1~ubuntu1), language-pack-en:amd64 (14.04+20140707, 14.04+20141110), libmysqld-dev:amd64 (5.5.40-0ubuntu0.14.04.1, 5.5.41-0ubuntu0.14.04.1), linux-image-generic:amd64 (3.13.0.37.44, 3.13.0.45.52), libkadm5srv-mit9:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libkrb5support0:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libk5crypto3:amd64 (1.12+dfsg-2ubuntu4.2, 1.12+dfsg-2ubuntu5.1), libisccc90:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), dh-apparmor:amd64 (2.8.95~2430-0ubuntu5, 2.8.95~2430-0ubuntu5.1), libc6-dev:amd64 (2.19-0ubuntu6.3, 2.19-0ubuntu6.5), libisc95:amd64 (9.9.5.dfsg-3, 9.9.5.dfsg-3ubuntu0.1), libcurl3-gnutls:amd64 (7.35.0-1ubuntu2.1, 7.35.0-1ubuntu2.3), rsyslog:amd64 (7.4.4-1ubuntu2.3, 7.4.4-1ubuntu2.5), ntpdate:amd64 (4.2.6.p5+dfsg-3ubuntu2, 4.2.6.p5+dfsg-3ubuntu2.14.04.2), linux-generic:amd64 (3.13.0.37.44, 3.13.0.45.52) End-Date: 2015-02-12 14:43:37 Kind regards, *Manuel Camargo* Teléfono: 638000836 eMail: sir.louen(a)gmail.com <https://twitter.com/SirLouen> [image: Ver el perfil de Manuel Camargo Lominchar en LinkedIn] <http://es.linkedin.com/in/louen>

4 3

Unable to route outbound with multiple VRRP IP's
by mark＠brightvoip.co.uk 13 Feb '15

13 Feb '15

Hi, I am trying to install a Kamailio server in a HA configuration, with IP's for 3 attached networks. I am using Keepalived/VRRP to manage the VIP's. I have tested v 4.1.6 and latest 4.2.2 I have 3 x listen entries, one for each network and mhomed=1. Also, for info, we have net.ipv4.ip_nonlocal_bind = 1 in sysctl.conf listen=udp:my.public.net.46:5060 listen=udp:192.168.106.46:5060 listen=udp:192.168.116.46:5060 mhomed=1 I have dispatcher set up to load balance over two seperate groups of Asterisk servers, one on each private network. Dispatcher does probing to know which Asterisks are 'alive'. When I ran the system, Kamailio/Dispatcher was not able to send any probing OPTIONS to any Asterisk (normal PINGS work fine in all networks in/out of Asterisk/Kamailio) Looking at the log, I see these entries for all 3 networks: Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: <core> [forward.c:218]: get_out_socket(): no socket found Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: <core> [forward.c:220]: get_out_socket(): no corresponding socket found for(u dp:192.168.116.38:5060) Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: tm [ut.h:345]: uri2dst2(): no corresponding socket found for "192.168.116.38" af 2 (udp:192.168.116.38:5060) Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: tm [uac.c:307]: t_uac_prepare(): t_uac: no socket found Feb 12 17:28:19 app-srv-dev-1-01 /usr/local/sbin/kamailio[2992]: ERROR: dispatcher [dispatch.c:2564]: ds_check_timer(): unable to ping [sip:192.168.1 16.38:5060] I notice from other logging that Kamailio is receiving and processing incoming OPTIONS messages, and sending appropriate replies. Now, this might not be a Kamailio issue, as when I run the same config with 3 IP's, but NOT using VRRP/Keepalived/Aliased IP's, everything works normally. However, I do need to run this setup in HA, so would welcome any suggestions as to how I might resolve this issue. Kind regards, Mark Hall --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com

2 2

Possible memory leak dealing with presence in kamailio
by Nuno Reis 12 Feb '15

12 Feb '15

Hello all. I'm consistently watching a memory increase in kamailio when dealing with PRESENCE events, namely SIP PUBLISH events. The system eventually hangs running out of memory. This behavior is seen at least in kamailio 4.1 and 4.2. I'm currently using the latest stable 4.2.2. If I disable the SIP PUBLISH handling in kamailio i don't observe the issue anymore but as a side effect I don't have presence (name BLFs) also. What do you think can be the right approach here? Should I open an issue in github for this? Should I run kamailio under valgrind for some time? Are there any other possible debug hints here? Please find attached a code snippet with the presence related parts I'm using right now. Looking forward to hear from you. Best Regards, -- *Nuno Miguel Reis* | *Unified Communication** Systems* M. +351 913907481 | nreis(a)wavecom.pt WAVECOM-Soluções Rádio, S.A. Cacia Park | Rua do Progresso, Lote 15 3800-639 AVEIRO | Portugal T. +351 309 700 225 | F. +351 234 919 191 *GPS <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* [image: Description: Description: WavecomSignature] <http://www.wavecom.pt/pt/wavecom/premios.php> [image: Publicity] <http://www.wavecom.pt/pt/mail_eventos.php>

4 13

Roadmap to next major release 4.3.0
by Daniel-Constantin Mierla 12 Feb '15

12 Feb '15

Hello, being discussed yesterday during the IRC devel meeting, the proposed planning for next major release (v4.3.0) is: - freeze the development sometime in April - after mid of March decide the exact date when the development is going to be frozen - testing during last part of April and May - based on testing results, release in the time frame: end of May till mid of June >From git activity, there are already several new modules and plenty of new features -- don't forget to add them to: - http://www.kamailio.org/wiki/features/new-in-devel Also, any detail that is relevant for upgrading has to added to: - https://www.kamailio.org/wiki/install/upgrade/stable-to-devel Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

1 0

Using MariaDB with sqlops sql_query_async
by davy van de moere 12 Feb '15

12 Feb '15

Does anyone know if the async queries of kamailio work with mariadb? I'm on kamailio 4.2.3, and I can't get the async way of querying to work. I don't get any errors, but I don't see the queries to be executed. the relevant part of my config is: loadmodule "db_mysql.so" loadmodule "sqlops.so" modparam("sqlops","sqlcon","ca=>mysql://kamailio:kamailiorw@localhost /kamailio") sql_query_async("ca", "insert into cdr_events (callid) values ('$ci') "); When just replace sql_query_async with sql_query, I do see inserts passing by. Do I just bluntly miss something? Or does someone have some good pointers? Thx! Davy

2 3

long l_uuid in uac_reg
by kovarik＠odorik.cz 11 Feb '15

11 Feb '15

Hello, rpc funcions: reg_info,reg_enable,reg_disable not work if l_uuid is number and size > than 10, for 1234567890 is O.K. and for 12345678901 try to find 18446744073170328629. kamcmd uac.reg_enable l_uuid 1234567890 -- found kamcmd uac.reg_enable l_uuid 12345678901 -- not found and if number start with zero then zero is cut. kamcmd uac.reg_enable l_uuid 0034567890 -- 34567890 I add debug to uac_reg.c 1615 LM_ERR("START %.*s,%.*s\n", attr.len,attr.s,val.len, val.s); Thaks

2 1

Trouble with DB APIs
by Davidson, Erik 11 Feb '15

11 Feb '15

Hey Everyone! I'm currently working on a database module and I've come across some issues/confusion that I was hoping someone could clear up for me. I've been looking at the existing modules and the docs online for help but I can't find a definitive answer for them. 1. I see there are 2 DB APIs (srdb1 and srdb2) and I gather that srdb2 is the newer version? Should I aim to use srdb2 exclusively or should I also use srdb1? 2. It looks like srdb2 provides a db_uri command that can be used to implement custom URI parsing but I can't figure out how to hook into it. I added it to my exported commands but it was never called. When I looked through the code I saw the only place that ever really uses it is db_ctx, which itself looks to be used in the child_init of modules. I'm developing a database module that I want to be a drop-in replacement for others, but it needs multiple hosts specified in the connection uri (similar to the URI example here http://docs.mongodb.org/manual/reference/connection-string/) and I can't figure out the best place to do it. Should I be doing it in db_func_t.init because it has the full string version of the uri and parse it there? Do I then have to reimplement everything that db_do_init would be doing? 3. Do I need to implement multiple database interfaces to get full module coverage in Kamailio? I was looking at db_berkeley as a reference and it looks like it has the KAMAILIO_MOD_INTERFACE as well as the SER_MOD_INTERFACE implemented. 4. Is there a preferred way to handle the API binding (such as db_ commands vs db_bind_api)? Thanks for any help or direction you can give me! - Erik Davidson ----------------------------------------- CONFIDENTIALITY NOTICE: The information contained in this e-mail message and any attachments is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient and have received this communication in error, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.

2 1

Next IRC development meeting
by Daniel-Constantin Mierla 11 Feb '15

11 Feb '15

Hello, I thought to propose organizing the next IRC meeting to discuss and sync each other about Kamailio development and surrounding ecosystem. First date proposal is next week, Wednesday, 15:00GMT, Feb 11, 2015, on the usual #kamailio channel at freenode.net. The date can be changed, based on feedback from the people that want to attends. I made a wiki page for the event at: - http://www.kamailio.org/wiki/devel/irc-meetings/2015a Feel free to propose topics to the agenda and/or new date. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

3 4

← Newer
1
...
6
7
8
9
10
11
12
13
14
Older →

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 February 2015