sr-users May 2011

sr-users@lists.kamailio.org

78 participants
129 discussions

by Klaus Darilion

Hi! I just read the Siremis installation howto. One of the task of the installer is: "Update SIP Database - this updates the structure of Kamailio database for accounting and charts modules" I wonder what siremis exactly does to the DB. Is greped over the siremis source file but couldn't find the changes. Are they somewhere documented? (e.g. .sql file with the statemens). Anyway, I wonder changes are needed at all. IMO, if possible, the Kamailio DB should not be changed by an external too - otherwise this may cause problems with updates to the Kamailio DB structure. Thanks Klaus

13 years, 1 month

kamailio debian package bug report : 3.1.3+lenny2

by Philippe HENSEL

Hi developpers and packagers, The file "/usr/lib64/kamailio/libsrdb2.so.1.0" seems to be included in both "kamailio_3.1.3+lenny2_amd64.deb" and "kamailio-mysql-modules_3.1.3 +lenny2_amd64.deb". So it is not possible to install "kamailio-mysql-modules". Thanks for help

13 years, 1 month

Multidomains - quick question

by Lucas Alvarez

Hi, if I want to register clients from outside of my local network, do I have to enable the domain module and add the external IP as a new domain? Thanks in advance, Lucas Alvarez

13 years, 1 month

acc Locks

by Borin

Hi all, Recently I met the following problem with kamailio acc table. We are using kamailio for calls dispatching to a couple of rtp gateways and for call statistics acc is used (with mysql). I tried to delete some old entries from acc table and for this time mysql "show processes" showed a lot of entries like " kamailio | Query | 0 | System lock | insert into acc (method,from_tag,to_tag,callid,sip_code,sip_reason,start_time,src_addr,dst_addr,src_ |". I think that meant that kamailio could not write to the acc table for the time the data were being deleted. And it also did not forward INVITE requests further. Does that mean that if kamailio does not manage to write acc record for any reason it does not forward that INVITE/200ok? Best Regards, Kate

13 years, 1 month

Green VoIP - energy efficiency and performaces of v3.0

by Daniel-Constantin Mierla

Hello, Jan Janak conducted a very interesting research project regarding energy efficiency of VoIP systems during 2010, a collaboration between iptel.org and Columbia University. The team used the source code from sip-router.org GIT repository from January 2010, which corresponds to Kamailio (former OpenSER) and SER v3.0. The latest stable series v3.1 shares the same internal architecture with v3.0. As part of the research work, Jan could also gather some figures about capacity and performances of v3.0 with a quite complex configuration file: etc/sip-router-oob.cfg (involving authentication and NAT traversal as well). You can read the paper about energy efficiency at: - Green VoIP Article: http://asipto.com/u/2j The draft notes about capacity and performances of v3.0 are available at: - Performances and Capacity for v3.0 Wiki page: http://asipto.com/u/2k Some interesting results: - one instance of SIP server with 500 000 online users (mixed users – behind and not NAT routers) – consumed energy 210W - one instance of SIP server with 1 000 000 online users (no NAT involved) – consumed energy 190W - on a 32-bit machine with 4GB of memory and with 2.5GB reserved for SIP server, the server could support 43 000 simultaneous TLS connections – consumed energy 203W - one SIP server instance with 80 000 permanent TCP connections, the SIP server could still handle at least 1000 requests per second and a connection arrival rate of 1000 new connections per second, done for 20 000 new connections. CPU load generated by the SIP server was from 6% to 8%. I added a new section to the draft notes to list the enhancements done for the latest stable release (v3.1.x) that contribute to performance improvements, like asynchronous TLS, fine tuning of memory for TLS connections and raw UDP sockets. Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda

13 years, 1 month

Late parallel branch (without canceling previous pending branches)

by Iñaki Baz Castillo

Hi, just wondering whether the following scenario (which it's not possible in kamailio 1.5) is possible in 3.X: 1) Alice calls a PSTN number. 2) Proxy receives the call and routes it to a media server which plays an early-announcement (30 seconds long). 3) After N seconds (maybe 10 seconds) proxy starts a new parallel branch to the PSTN gateway *without* cancelling the previous branch with the media server. 4) Let's suppose the PSTN phone rings and proxy gets 183 with SDP (ringing in real audio). Proxy converts such 183 into a 180 with no SDP (already possible in Kamailio). 5) After 30 seconds media server rejects the call with 480. PSTN branch remains ringing as usual. I just would like to know if Kamailio 3.X allows point 3. I think it's hard but maybe I miss some feature. Thanks a lot. -- Iñaki Baz Castillo <ibc(a)aliax.net>

13 years, 1 month

Dispatcher variables

by Lee Archer

Hi all, I am using dispatcher and on a failure I would like to log the server that has failed. I am using $dd but this only ever returns the address of the first server that was tried and not any subsequent servers that were tried and also failed. What should I be using to display the IP address of the server dispatcher is about to use? Thanks Lee

13 years, 1 month

Fw: Load capacity of SER??

by Piyush.Bansal＠relianceada.com

Dear All, I'm using SER as a SIP proxy server for quite a long time. I'm not been able to find its load bearing capacity. If you can help me get a figure in terms of BHCA, that'll be quite helpful. Thanks and Regards, --Piyush Bansal The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

13 years, 1 month

IMC module doesn't save data to mysql database

by Ozren Lapcevic

Hi all, I'm trying to configure IMC module and get it to work properly but I've run into problems with saving IMC module data to mysql database. I'm using following code provided in IMC module documentation: modparam("imc", "db_url", DBURL) ## route block ### if(is_method("MESSAGE") && (uri=~ "sip:chat-[0-9]+@") || (uri=~ "sip:chat-manager@")) { xlog("L_INFO", "going to imc: F [$fu] T [$tu] B [$rb]\n"); if(imc_manager()) sl_send_reply("200", "ok - imc_manager()"); else sl_send_reply("500", "command error"); exit; } I am creating chat room with following message sent to chat-manager(a)abc.hr: "#create chat-111" DEBUG log returns following: May 30 18:01:23 ser-test /usr/local/kamailio-ozren/sbin/kamailio[13225]: INFO: <script>: going to imc: F [sip:oz@abc.hr] T [sip:chat-manager@abc.hr] B [#create chat-111] May 30 18:01:23 ser-test /usr/local/kamailio-ozren/sbin/kamailio[13225]: DEBUG: imc [imc.c:525]: found command May 30 18:01:23 ser-test /usr/local/kamailio-ozren/sbin/kamailio[13225]: DEBUG: imc [imc_cmd.c:146]: command: [create] May 30 18:01:23 ser-test /usr/local/kamailio-ozren/sbin/kamailio[13225]: DEBUG: imc [imc_cmd.c:151]: parameter 0=[chat-111] May 30 18:01:23 ser-test /usr/local/kamailio-ozren/sbin/kamailio[13225]: DEBUG: imc [imc_cmd.c:171]: new room [chat-111] May 30 18:01:23 ser-test /usr/local/kamailio-ozren/sbin/kamailio[13225]: DEBUG: imc [imc_cmd.c:186]: added room uri= sip:chat-111@abc.hr May 30 18:01:23 ser-test /usr/local/kamailio-ozren/sbin/kamailio[13225]: DEBUG: imc [imc_mng.c:322]: [uri]= sip:oz@abc.hr May 30 18:01:23 ser-test /usr/local/kamailio-ozren/sbin/kamailio[13225]: DEBUG: imc [imc_mng.c:326]: [user]= oz May 30 18:01:23 ser-test /usr/local/kamailio-ozren/sbin/kamailio[13225]: DEBUG: imc [imc_cmd.c:196]: added the owner as the first member [ sip:oz@abc.hr] "./kamctl fifo imc_list_rooms" returns following: ROOM:: URI=sip:chat-111@abc.hr MEMBERS=0 OWNER=sip:oz@abc.hr "./kamctl fifo imc_list_members sip:chat-111@abc.hr" returns following: ROOM:: sip:chat-111@abc.hr NR_OF_MEMBERS=1 MEMBER:: sip:oz@abc.hr However, that data is not persisted/saved in the imc_rooms and imc_members tables in the database. Any clues what might be the problem here? Any help is greatly appreciated. Best regards, Ozren Lapcevic PS I'm runing Kamailio 3.1.4 with default cfg file with enabled mysql, multidomain, usrlocdb, auth and NAT. I can register clients, establish calls, send IMs, etc. imc_rooms and imc_members tables were created when kamailio was installed. I've also checked imc-create.sql script and tables are correctly created. The same DBURL used for imc is also used for auth_db, domain and usrloc modules and I haven't experienced any problems with those modules and database connection/persistence. domain, location, version and subscriber tables are correctly populated. I'm not getting any errors from imc_manager(), it returns 200 OK. I can't trace any errors in DEBUG related to problems with mysql database.

13 years, 1 month

Kamailio service not starting on reboot when using mysql database

by Rick Aldred

I have set up kamailio 3.1.2 on an install of Debian Squeeze, using the default config but with the following defines enabled: WITH_MYSQLWITH_AUTHWITH_USRLOCDBWITH_NAT Everything works as expected when starting Kamailio from a terminal, e.g.service kamailio start But after a reboot, the service fails to start and all SIP requests are dropped with a ICMP port unreachable error. The following is an extract of /var/log/syslog when this problem occurs. It looks like Kamailio is failing to access the mysql socket, as the mysql service has not yet started? Apr 12 10:08:31 SIPServer /usr/sbin/kamailio[1347]: ERROR: db_mysql [km_my_con.c:109]: driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)Apr 12 10:08:31 SIPServer /usr/sbin/kamailio[1347]: ERROR: <core> [db.c:289]: could not add connection to the poolApr 12 10:08:31 SIPServer /usr/sbin/kamailio[1347]: ERROR: usrloc [dlist.c:486]: failed to open database connectionApr 12 10:08:31 SIPServer /usr/sbin/kamailio[1347]: ERROR: registrar [reg_mod.c:396]: failed to register domainApr 12 10:08:31 SIPServer /usr/sbin/kamailio[1347]: ERROR: <core> [route.c:1161]: fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:569Apr 12 10:08:31 SIPServer /usr/sbin/kamailio[1347]: ERROR: <core> [route.c:1161]: fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:572Apr 12 10:08:31 SIPServer /usr/sbin/kamailio[1347]: ERROR: <core> [route.c:1161]: fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:574Apr 12 10:08:34 SIPServer mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysqlApr 12 10:08:34 SIPServer mysqld: 110412 10:08:34 [Note] Plugin 'FEDERATED' is disabled.Apr 12 10:08:36 SIPServer mysqld: 110412 10:08:36 InnoDB: Started; log sequence number 0 44233Apr 12 10:08:36 SIPServer mysqld: 110412 10:08:36 [Note] Event Scheduler: Loaded 0 eventsApr 12 10:08:36 SIPServer mysqld: 110412 10:08:36 [Note] /usr/sbin/mysqld: ready for connections.Apr 12 10:08:36 SIPServer mysqld: Version: '5.1.49-3' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian) Both the Kamailio and mysql services start with priority 18 on run levels 2345. I tried adjusting the Kamailio service to priority 19, but the problem still occurs. I am relatively new to Kamailio and mysql as well as Linux / Debian administration, so I'm not really sure how to solve this problem. Any ideas would be greatly appreciated. Regards,Rick Aldred

13 years, 1 month

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 May 2011