sr-users October 2013

sr-users@lists.kamailio.org

78 participants
153 discussions

Start a nNew thread

alyaseen98@yahoo.com
by mohammed alyaseen 13 Oct '13

13 Oct '13

alyaseen98(a)yahoo.com

1 0

UAC Module fail to refresh REGISTER
by Rene Montilva 11 Oct '13

11 Oct '13

Hi list i'm testing uac module with a did provider, apparently it works the first register, when it's going to refresh the session the register packed don't send the proxy-authorization header. My kamailio is 4.0, the debian wheezy repository *this is my parameter config:* #!ifdef WITH_UAC #---------- uac params ----------# modparam("uac", "reg_db_url",DBURL) modparam("uac", "reg_timer_interval",60) modparam("uac", "reg_retry_interval",120) modparam("uac", "reg_db_table", "uacreg") modparam("uac","credential","username:domain:password") modparam("uac","auth_realm_avp","$avp(i:10)") modparam("uac","auth_username_avp","$avp(i:11)") modparam("uac","auth_password_avp","$avp(i:12)") modparam("uac","restore_mode","auto") modparam("uac", "reg_contact_addr", "xx.xx.xx:5060") #!endif *this is the route block:* if(uac_reg_request_to("$fU", 1)) { xlog("L_NOTICE", "Found remote user [$rU] on [$rd] via [$du]"); t_on_failure("REMOTE_AUTH"); t_relay(); } * inside route[LOCATION] at the end:* #!ifdef WITH_UAC if(uac_reg_lookup("$rU", "$ru")) { xlog("request from a remote SIP provider [$ou => $ru]\n"); } lookup("location"); #!endif failure_route[REMOTE_AUTH] { if ($T_reply_code == 401 or $T_reply_code == 407) { xlog("L_NOTICE", "Remote asked for authentication"); uac_auth(); } } *this is the error log by syslog* ct 11 13:52:47 rene /usr/sbin/kamailio[7413]: INFO: <script>: Routing locally generated REGISTER to<sip:ippbx.xxxxx.com> Oct 11 13:52:47 rene /usr/sbin/kamailio[7400]: ERROR: uac [uac_reg.c:537]: uac_reg_tm_callback(): authentication failed for <2127207679> *this is sip trace with first register:* Frame 209: 671 bytes on wire (5368 bits), 671 bytes captured (5368 bits) on interface 0 Ethernet II, Src: Hewlett-_6b:6e:49 (10:1f:74:6b:6e:49), Dst: Cisco_7f:1e:69 (00:13:1a:7f:1e:69) Internet Protocol Version 4, Src: 10.20.8.45 (10.20.8.45), Dst: xx.xx.xx.xx (xx.xx.xx.xx) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:ippbx.xxxxx.com SIP/2.0 Message Header Via: SIP/2.0/UDP 10.20.8.45;branch=z9hG4bKb278.906502e4.0 To: sip:5201341115@ippbx.xxxxx.com From: sip:5201341115@ippbx.xxxxx.com ;tag=533cb9e91f4b999cf76861cbb9ed54ed-4cad CSeq: 11 REGISTER Call-ID: 2e81fffd-7628(a)127.0.0.1 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (4.0.3 (i386/linux)) Contact: <sip:01133212720@xxx.xxx.xxx:5060> Expires: 60 Proxy-Authorization: Digest username="1341115", realm="xxxxx", nonce="5DB4B614FCD76AD44FFFC3BEAECBDA9B", uri="sip:ippbx.xxxxx.com", response="d7d38055e339a2554cf2bb7e79e9b6f4", algorithm=MD5 *this is sip trace with the second register:* Frame 681: 468 bytes on wire (3744 bits), 468 bytes captured (3744 bits) on interface 0 Ethernet II, Src: Hewlett-_6b:6e:49 (10:1f:74:6b:6e:49), Dst: Cisco_7f:1e:69 (00:13:1a:7f:1e:69) Internet Protocol Version 4, Src: 10.20.8.45 (10.20.8.45), Dst: xx.xx.xx.xx (66.33.146.52) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:ippbx.xxxxx.com SIP/2.0 Message Header Via: SIP/2.0/UDP 10.20.8.45;branch=z9hG4bKb278.a06502e4.0 To: sip:5201341115@ippbx.xxxxx.com From: sip:5201341115@ippbx.xxxxx.com ;tag=533cb9e91f4b999cf76861cbb9ed54ed-4d45 CSeq: 10 REGISTER Call-ID: 2e81fffe-7628(a)127.0.0.1 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (4.0.3 (i386/linux)) Contact: <sip:01133212720@xxx.xxx.xxx:5060> Expires: 60 there isn't proxy-authorization Header Any help i don't know what it's wrong Best Regards Rene Montilva

3 5

ZRTP
by Jonathan Brown 11 Oct '13

11 Oct '13

Hi, Does Kamailio support ZRTP end point to end point encryption? If so how is this configured? Sincerely, Jonathan Brown IT Manager [Signature Email] (P) 318-698-1252 (F) 318-459-2935

2 2

Kamailio 4.0.4 won't start
by Igor Potjevlesch 11 Oct '13

11 Oct '13

Hello, I don't figure out why Kamailio can't connect to MySQL DB. DBURL is set : # *** Value defines - IDs used later in config #!ifdef WITH_MYSQL # - database URL - used to connect to database server by modules such # as: auth_db, acc, usrloc, a.s.o. #!define DBURL "mysql://kamailio:PASSWORD@192.168.2.6/kamailio" #!endif Each module refer to DBURL, like acc : # ----- acc params ----- /* what special events should be accounted ? */ modparam("acc", "early_media", 0) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1) /* by default ww do not adjust the direct of the sequential requests. if you enable this parameter, be sure the enable "append_fromtag" in "rr" module */ modparam("acc", "detect_direction", 0) /* account triggers (flags) */ modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) /* enhanced DB accounting */ #!ifdef WITH_ACCDB modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_url", DBURL) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") #!endif When I try a connection from MySQL CLI with the same login and password, it works. Here are the output from /var/log/messages (note that public IP address appears as A.B.C.X) : Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: rr [../outbound/api.h:49]: ob_load_api(): Failed to import bind_ob Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: rr [rr_mod.c:159]: mod_init(): outbound module not available Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 512 Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: auth [auth_mod.c:350]: mod_init(): auth: qop set, but nonce-count (nc_enabled) support disabled Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: <core> [udp_server.c:179]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is initially 229376 Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: <core> [udp_server.c:230]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is finally 262142 Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: <core> [udp_server.c:179]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is initially 229376 Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: <core> [udp_server.c:230]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is finally 262142 Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: rtpproxy [rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found, support for it enabled Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10301]: INFO: rtpproxy [rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found, support for it enabled Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10302]: INFO: rtpproxy [rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found, support for it enabled Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.2.6' (4) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.2.6' (4) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: acc [acc.c:359]: acc_db_init_child(): unable to connect to the database Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: acc [acc.c:359]: acc_db_init_child(): unable to connect to the database Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: acc [acc_mod.c:689]: child_init(): could not open database connection Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: acc [acc_mod.c:689]: child_init(): could not open database connection Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: <core> [sr_module.c:896]: init_mod_child(): init_mod_child(): Error while initializing module acc (/usr/local/lib64/kamailio/modules/acc.so) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: <core> [sr_module.c:896]: init_mod_child(): init_mod_child(): Error while initializing module acc (/usr/local/lib64/kamailio/modules/acc.so) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: <core> [pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for process 3, pid 10303, "udp receiver child=2 sock=A.B.C.4:5060" Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: <core> [pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for process 6, pid 10306, "udp receiver child=5 sock=A.B.C.4:5060" Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: : <core> [main.c:1630]: main_loop(): main_loop: Cannot fork Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: : <core> [main.c:1630]: main_loop(): main_loop: Cannot fork Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.2.6' (4) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: acc [acc.c:359]: acc_db_init_child(): unable to connect to the database Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: acc [acc_mod.c:689]: child_init(): could not open database connection Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: <core> [sr_module.c:896]: init_mod_child(): init_mod_child(): Error while initializing module acc (/usr/local/lib64/kamailio/modules/acc.so) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: <core> [pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for process 4, pid 10304, "udp receiver child=3 sock=A.B.C.4:5060" Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: : <core> [main.c:1630]: main_loop(): main_loop: Cannot fork Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.2.6' (4) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: acc [acc.c:359]: acc_db_init_child(): unable to connect to the database Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: acc [acc_mod.c:689]: child_init(): could not open database connection Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: <core> [sr_module.c:896]: init_mod_child(): init_mod_child(): Error while initializing module acc (/usr/local/lib64/kamailio/modules/acc.so) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: <core> [pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for process 5, pid 10305, "udp receiver child=4 sock=A.B.C.4:5060" Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: : <core> [main.c:1630]: main_loop(): main_loop: Cannot fork Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.2.6' (4) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: acc [acc.c:359]: acc_db_init_child(): unable to connect to the database Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: acc [acc_mod.c:689]: child_init(): could not open database connection Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: <core> [sr_module.c:896]: init_mod_child(): init_mod_child(): Error while initializing module acc (/usr/local/lib64/kamailio/modules/acc.so) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: <core> [pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for process 9, pid 10309, "udp receiver child=8 sock=A.B.C.4:5060" Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: : <core> [main.c:1630]: main_loop(): main_loop: Cannot fork Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.2.6' (4) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10308]: ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.2.6' (4) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: usrloc [ul_mod.c:437]: child_init(): child(0): failed to connect to database Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10308]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: <core> [sr_module.c:896]: init_mod_child(): init_mod_child(): Error while initializing module usrloc (/usr/local/lib64/kamailio/modules/usrloc.so) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10308]: ERROR: acc [acc.c:359]: acc_db_init_child(): unable to connect to the database Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10308]: ERROR: acc [acc_mod.c:689]: child_init(): could not open database connection Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: <core> [main.c:1716]: main_loop(): ERROR: main: error in init_child Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10307]: ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.2.6' (4) Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10307]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10330]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 received [...] Many thanks for your help. Regards, Igor.

1 0

Kamailio.cfg help
by Owais ul Haq 11 Oct '13

11 Oct '13

Hello, I am new to VOIP world. I want to learn about the message processing in kamailio server. Can some one point out some good online source. Thanks Secondly when I connect soft phone to kamailio server. I find some error messages generated by Kamailio Server (I found out these messages using WireShark). I want to know which part of kamailio.cfg generated those messages. Thanks. Any help for this newbie will be appreciated. Best Regards

2 1

SipCapture & SipTrace modules performance
by Grant Bagdasarian 11 Oct '13

11 Oct '13

Hello, Have these modules ever been tested under heavy load? For instance at 20+ CPS? Any idea what the maximum performance is for these modules?

1 0

Error kamailio and sems, help me please!!
by Camilo Bozo 10 Oct '13

10 Oct '13

Hello!! In /var/log/message show me is: Galileo sems [13817] : error: [28c96d80] findSessionFactory (AmplugIn.cpp:850) : AmplugIn::findSessionFactory: appliccation ocupado not found ¿What´s it? Please help me!! Thanks -- Camilo Bozo Torres Mirje Soluciones INF Fono 81338638/2520108 Camilo.bozo(a)mirje.net <mailto:Camilo.bozo@mirje.net> Pto Williams 136 Pto Montt X Región

1 0

PUBLISH handling
by Piyush.Bansal＠relianceada.com 10 Oct '13

10 Oct '13

Hi, I've an observation regarding PUBLISH message handling. on receiving of PUBLISH message, SER is sending NOTIFY with presence information of all the buddies available in the buddy list while it should be sending that only for the buddy updating his/her presence information. Because of this the size of every NOTIFY message traversing on the network is quite high. Please help if there is any change I'll have to do to achieve the desired. Thanks and Regards, --Piyush Bansal The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

2 2

PUBLISH handling
by Piyush.Bansal＠relianceada.com 10 Oct '13

10 Oct '13

1 0

Fw: query regarding SER
by Piyush.Bansal＠relianceada.com 10 Oct '13

10 Oct '13

please help ----- Forwarded by Piyush Bansal/RCOM/RelianceADA on 10/10/2013 10:52 AM ----- From: Piyush Bansal/RCOM/RelianceADA To: serusers(a)lists.iptel.org, serdev(a)lists.iptel.org Date: 10/09/2013 11:00 AM Subject: Fw: query regarding SER HI there, I have few queries regarding data deletion from database tables- 1. Once the timer of REGISTER expires, the entry for that user is not getting deleted from "location" table. 2. Same thing is happening with SUBSCRIBER timer expiry. The entries from presence tables are not getting deleted. Please suggest how to debug this issue?? Thanks and Regards, --Piyush Bansal The information contained in this electronic message (email) and any attachments to this email are intended for the exclusive use of the addressee(s) and access to this email by any one else is unauthorised. The email may contain proprietary, confidential or privileged information or information relating to Reliance Group. If you are not the intended recipient, please notify the sender by telephone, fax, or return email and delete this communication and any attachments thereto, immediately from your computer. Any dissemination, distribution, or copying of this communication and the attachments thereto (in whole or part), in any manner, is strictly prohibited and actionable at law. The recipient acknowledges that emails are susceptible to alteration and their integrity can not be guaranteed and that Company does not guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.

1 0

← Newer
1
...
8
9
10
11
12
13
14
15
16
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 October 2013