sr-users February 2016

sr-users@lists.kamailio.org

80 participants
133 discussions

Compile error with CNXCC on Debian 7 Wheezy
by Dirk Teurlings - SIGNET B.V. 03 Feb '16

03 Feb '16

Hi, While compiling Kamailio 4.3.4 from package sources for Debian 7 Wheezy (kamailio repository) I'm running into a problem. I've forked the CNXCC module which I was trying to keep up to date with upstream changes. But before I could do that, there is a dependency of redis added. Unfortunately, installing redis devel libs and libevent doesn't provide the correct version of redis. Also, I noticed on Debian 8 Jessie, it does compile correctly. How could Kamailio be compiled for Wheezy with these sources? I'm missing something obvious I feel. Attached is the compile log, this is with a completely unaltered sources. root@devhost:/usr/src/kamailio-4.3.4+wheezy# make -C modules/cnxcc make: Entering directory `/usr/src/kamailio-4.3.4+wheezy/modules/cnxcc' CC (gcc) [L libkmi.so.1.0] attr.o CC (gcc) [L libkmi.so.1.0] fmt.o CC (gcc) [L libkmi.so.1.0] mi.o CC (gcc) [L libkmi.so.1.0] tree.o LD (gcc) [L libkmi.so.1.0] libkmi.so.1.0 CC (gcc) [L libsrdb1.so.1.0] db.o CC (gcc) [L libsrdb1.so.1.0] db_id.o CC (gcc) [L libsrdb1.so.1.0] db_pool.o CC (gcc) [L libsrdb1.so.1.0] db_query.o CC (gcc) [L libsrdb1.so.1.0] db_res.o CC (gcc) [L libsrdb1.so.1.0] db_row.o CC (gcc) [L libsrdb1.so.1.0] db_ut.o CC (gcc) [L libsrdb1.so.1.0] db_val.o LD (gcc) [L libsrdb1.so.1.0] libsrdb1.so.1.0 CC (gcc) [L libkcore.so.1.0] cmpapi.o CC (gcc) [L libkcore.so.1.0] faked_msg.o CC (gcc) [L libkcore.so.1.0] kstats_wrapper.o CC (gcc) [L libkcore.so.1.0] parse_privacy.o CC (gcc) [L libkcore.so.1.0] parse_sst.o CC (gcc) [L libkcore.so.1.0] regexp.o CC (gcc) [L libkcore.so.1.0] statistics.o CC (gcc) [L libkcore.so.1.0] strcommon.o LD (gcc) [L libkcore.so.1.0] libkcore.so.1.0 LD (gcc) [M cnxcc.so] cnxcc.so cnxcc_mod.o: In function `redisLibeventReadEvent': /usr/include/hiredis/adapters/libevent.h:10: multiple definition of `redisLibeventReadEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:10: first defined here cnxcc_mod.o: In function `redisLibeventWriteEvent': /usr/include/hiredis/adapters/libevent.h:16: multiple definition of `redisLibeventWriteEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:16: first defined here cnxcc_mod.o: In function `redisLibeventAddRead': /usr/include/hiredis/adapters/libevent.h:22: multiple definition of `redisLibeventAddRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:22: first defined here cnxcc_mod.o: In function `redisLibeventDelRead': /usr/include/hiredis/adapters/libevent.h:27: multiple definition of `redisLibeventDelRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:27: first defined here cnxcc_mod.o: In function `redisLibeventAddWrite': /usr/include/hiredis/adapters/libevent.h:32: multiple definition of `redisLibeventAddWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:32: first defined here cnxcc_mod.o: In function `redisLibeventDelWrite': /usr/include/hiredis/adapters/libevent.h:37: multiple definition of `redisLibeventDelWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:37: first defined here cnxcc_mod.o: In function `redisLibeventCleanup': /usr/include/hiredis/adapters/libevent.h:42: multiple definition of `redisLibeventCleanup' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:42: first defined here cnxcc_mod.o: In function `redisLibeventAttach': /usr/include/hiredis/adapters/libevent.h:49: multiple definition of `redisLibeventAttach' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:49: first defined here cnxcc_redis.o: In function `redisLibeventReadEvent': /usr/include/hiredis/adapters/libevent.h:10: multiple definition of `redisLibeventReadEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:10: first defined here cnxcc_redis.o: In function `redisLibeventWriteEvent': /usr/include/hiredis/adapters/libevent.h:16: multiple definition of `redisLibeventWriteEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:16: first defined here cnxcc_redis.o: In function `redisLibeventAddRead': /usr/include/hiredis/adapters/libevent.h:22: multiple definition of `redisLibeventAddRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:22: first defined here cnxcc_redis.o: In function `redisLibeventDelRead': /usr/include/hiredis/adapters/libevent.h:27: multiple definition of `redisLibeventDelRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:27: first defined here cnxcc_redis.o: In function `redisLibeventAddWrite': /usr/include/hiredis/adapters/libevent.h:32: multiple definition of `redisLibeventAddWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:32: first defined here cnxcc_redis.o: In function `redisLibeventDelWrite': /usr/include/hiredis/adapters/libevent.h:37: multiple definition of `redisLibeventDelWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:37: first defined here cnxcc_redis.o: In function `redisLibeventCleanup': /usr/include/hiredis/adapters/libevent.h:42: multiple definition of `redisLibeventCleanup' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:42: first defined here cnxcc_redis.o: In function `redisLibeventAttach': /usr/include/hiredis/adapters/libevent.h:49: multiple definition of `redisLibeventAttach' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:49: first defined here collect2: error: ld returned 1 exit status make: *** [cnxcc.so] Error 1 make: Leaving directory `/usr/src/kamailio-4.3.4+wheezy/modules/cnxcc' Cheers, Dirk

3 3

Possible accidental merge to master.
by Cody Herzog 03 Feb '16

03 Feb '16

Hello. I feel like a total idiot. I was inspecting the various GitHub branches for Kamailio using a GitHub visual client, and I think I managed to accidentally merge a branch back into master. The branch I was inspecting was 'lazedo/presence_improvements'. I was inspecting diffs and branches, and was amazed that I was able to screw up so badly with one single click, but I guess that's the danger of a visual git client. Anyway, before trying to do anything more, I figured I'd asked for advice, because I don't want to screw up further. Hopefully there's a simple way to revert the accidental merge, but I first wanted to confirm that I actually did make that mistake, and that it's visible to others. Thanks.

2 2

issue with INVITE frame size
by Rene Montilva 03 Feb '16

03 Feb '16

Hi list I have problem with invite packet in some wifi networks because the invite packet is less than 1000bytes(frame size) and the access point not redirect to softphone, this scenario happen with incoming calls to my DID, the packets come from the provider to kamailio with a size more than 1000 and when kamailio redirect to softphone sometimes is less than 1000. how i could solve this issue?. thanks for any help.

3 7

Kamailio/How to send all requests ?
by alexandre.anconetti＠orange.com 02 Feb '16

02 Feb '16

Hello ! I'm using Kamailio for 2 months, and I have a problem with the routing logic. My aim is to use 2 Kamailio servers (in a cluster, so I have a primary and a backup server with a Virtual IP that can switch between the 2 servers) working with 2 medias servers (same as above, a primary and a backup). The Kamailio servers are here to handle failover, so all the requests go through them, and then are sent to the active media server. My question is : Which module(s) should I load to transmit all the requests (including registers) to my media server, through the Kamailio server ? Any particular parameters ? Then, what will be in the "request_route" ? I'm using Kamailio 4.3.4. Best regards, Alexandre _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 2

SIP register - memory size
by José Seabra 02 Feb '16

02 Feb '16

Hello there, Can anyone tell me what is the exactly memory size that kamailio use for one sip register saved on memory? How much memory i need allocate to kamailio in order to support 50.000 subscribers. Best Regards

2 4

Kamailio Social Event at Fosdem 2016
by Daniel-Constantin Mierla 02 Feb '16

02 Feb '16

Hello, only few days left, so we need to nail the location down for Kamailio dinner at Fosdem. One suggestion in walking distance is: - http://restaurant-italien-picotin-bruxelles.be/en I understood that it was used in the past also for Fosdem Speaker's Dinner, so it might be busy and we can't get the seats. So new suggestions are more than welcome in order to have some backups to try! If there is no strong preference for something else by end of today, tomorrow we should attempt to do the reservation at this place. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

5 9

Asterisk+Kamailio
by Вячеслав Завалко 02 Feb '16

02 Feb '16

The adjustment was carried out by a manual that http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb But the sharing screen is not working softphone on a given configuration. What can be done?

2 1

kamailio + asterisk
by Вячеслав Завалко 02 Feb '16

02 Feb '16

Is it possible to do a demonstration screen caller using Kamailio + Asterisk?

2 1

Kamailio 4.3 and Freeswitch 1.0 Stable Latest
by Barış Şekerciler 02 Feb '16

02 Feb '16

Hello everyone. I'm a student and I'm working on project which about SIP communication and PBXs with IP phones. So, my first test results were OK with JITSI. But I think I need Freeswitch for working with IP phones. In a word, I need configure an integration Kamailio and Freeswitch. First, I setup Debian 8.3 Jessie and installed Kamailio on this my local server, after that I installed another Debian 8.3 Jessie (from same image) as my second server and it was going to run Freeswitch on itself. Then I tried to send my communication requests to my Freeswitch server. I made some tests, my Jitsi accounts which are set in Kamailio server were done. I've read Kamailio 3.2 and Freeswitch integration from the Kamailio wiki and I applied exactly the same thing but I did not work. When I tried to reach another IP phone from my IP phone (I registered them) phone always say "NOT FOUND". I'm sure I did my configuration properly. So, how can I figure it out these things? How can I understand, does Kamailio routes to Freeswitch to my phones? Best regards. Thanks.

2 1

Critical issue: Kamailio throwing db errors
by Sharon Nathaniel 02 Feb '16

02 Feb '16

Hi, I am not sure, if its a kamailio issue or something else, but our Kamailio 4.2 server crashes everyday. Throwing out these logs: http://pastebin.com/z1MWdk7q. We have to restart the server to get this fixed. Please help us understand what is causing the issue. Thanks and Regards, Sharon Nathaniel The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and access to it by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken based on it, is strictly prohibited and may be unlawful.

2 1

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 2016