sr-users

sr-users@lists.kamailio.org

21 participants
37532 discussions

Re: [SR-Users] Kamailio not processing SIP TCP
by JR Richardson 17 Jan '17

17 Jan '17

> On Mon, Jan 16, 2017 at 10:29:39AM -0600, JR Richardson wrote: >> Yes, I'm familiar with the methods sipcapture uses, I don't use HEP, >> using raw socket capture, I think this may be a sipcapture issue, >> debuging kamailio shows normal startup and processing of UDP SIP >> packets, but does not show any activity with TCP packets. > > I never used HOMER sofar but when I saw your first message my thoughts > was that this can't work in a simple way since for … [View More]

2 1

Using the auth_ephemeral module
by Hemanshu Vadehra 17 Jan '17

17 Jan '17

I'm involved in setting up a Kamailio instance and was hoping to make use of the auth_ephemeral module for authentication. But the module documentation doesn't quite make clear how exactly the module is to be employed or the web service set up. Does anyone have a working example? Regards, Hemanshu Vadehra hemanshu.v(a)directi.com

5 8

usrloc module with dbmode=2 does not insert records to database
by Vik Killa 17 Jan '17

17 Jan '17

Hello, we've noticed that the usrloc module does not "sync" all the records from memory into the database. I use a bash script to generate in-memory AoRs ( http://paste.debian.net/plain/908521) then i perform kamcmd ul.flush and no records are inserted. We have tried various usrloc parameters but none seem to work Here is our basic setup # ----- usrloc params ----- modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", 1) modparam("usrloc", "… [View More]

2 11

Info: github template for reporting issues
by Daniel-Constantin Mierla 17 Jan '17

17 Jan '17

Hello, yesterday I added a template for opening new issues on github.com bug tracker. You can see it in action at: - https://github.com/kamailio/kamailio/issues/new Its bare text can be seen at: - https://raw.githubusercontent.com/kamailio/kamailio/master/.github/ISSUE_TE… More about the issue templates for github can be found at: - https://help.github.com/articles/creating-an-issue-template-for-your-reposi… Beside informing about this addition, I would like to get also … [View More]

1 0

LCR module dont_strip_or_tag_flag
by Annus Fictus 17 Jan '17

17 Jan '17

Hello, I'm trying LCR module and dont_strip_or_tag_flag parameter. If I use this line in the module configuration: modparam("lcr", "dont_strip_or_tag_flag", 10) and then restart kamailio, i receive this error: ERROR: <core> [modparam.c:141]: set_mod_param_regex(): parameter <dont_strip_or_tag_flag> of type <2> not found in module <lcr> I'm using 4.4.4 version Any hint? Thank you Regards

3 3

Re: [SR-Users] Kamailio not processing SIP TCP
by JR Richardson 16 Jan '17

16 Jan '17

Hey Daniel, Yes, I'm familiar with the methods sipcapture uses, I don't use HEP, using raw socket capture, I think this may be a sipcapture issue, debuging kamailio shows normal startup and processing of UDP SIP packets, but does not show any activity with TCP packets. I have enabled/disabled the different capture methods and no TCP SIP packets are processed. Also, I didn't mention before I'm testing on 2 different instances, one is a Homer 3.5 (Kamailio 4.1.2) and another is Homer 5.0 (… [View More]Kamailio 4.4.0). I'll post to the Homer list and see what they say. Thanks. JR > is it this about a sipcature node? If yes, then it receives the packets > over HEP, meaning that is not going to the normal processing path. > Kamailio detects it is not a SIP packet, executes some callbacks for > non-sip packets registered by modules (in this case sipcapture). The > module detecting it's a packet for it, can execute the request_route > once it builds a local sip packet. > > To troubleshoot further, run with debug=3 in kamailio.cfg and see what > you get in the logs. > > Cheers, > Daniel > > On 13/01/2017 16:33, JR Richardson wrote: >> Iptables is not blocking, but it was worth a check. >> >> Thanks. >> >> JR >> >> >> I assume you have ruled out firewall? It's something that can nab even >> experienced people: >> >> # iptables -Ln >> >> -- Alex >> >> On Thu, Jan 12, 2017 at 03:25:27PM -0600, JR Richardson wrote: >> >>> Hi All, >>> >>> Just enabled SIP TCP on a homer capture server, I can see the SIP TCP >>> Sessions on the server with ngrep, just like all the UDP traffic. I >>> have Kamailio listening on TCP ports but its not capturing any TCP >>> traffic. >>> >>> kamailio.cfg: >>> >>> #disable_tcp=yes >>> listen=tcp:10.99.99.99:5060 #monitor port >>> listen=udp:10.99.99.99:5060 #monitor port >>> >>> loadmodule "pv.so" >>> loadmodule "db_mysql.so" >>> loadmodule "sipcapture.so" >>> loadmodule "textops.so" >>> loadmodule "rtimer.so" >>> loadmodule "xlog.so" >>> loadmodule "sqlops.so" >>> loadmodule "htable.so" >>> loadmodule "sl.so" >>> loadmodule "siputils.so" >>> >>> >>> modparam("sipcapture", "capture_on", 1) >>> modparam("sipcapture", "hep_capture_on", 0) >>> modparam("sipcapture", "raw_socket_listen", "10.99.99.99:5060-5070") >>> modparam("sipcapture", "raw_interface", "eth1") >>> modparam("sipcapture", "raw_ipip_capture_on", 0) >>> modparam("sipcapture", "table_name", "sip_capture") >>> modparam("sipcapture", "raw_sock_children", 4) >>> modparam("sipcapture", "db_insert_mode", 0) >>> modparam("sipcapture", "raw_moni_capture_on", 1) >>> modparam("sipcapture", "promiscious_on", 1) >>> modparam("sipcapture", "raw_moni_bpf_on", 1) >>> modparam("sipcapture", "capture_node", "homer02") >>> modparam("sipcapture", "authorization_column", "authorization") >>> >>> >>> ## logging all INVITES top of the [route] block >>> if (is_method("INVITE|REGISTER")) { >>> xlog("L_INFO", "Received INVITE \"$fU\" to \"$rU\" >>> from \"$si\"\n"); >>> >>> Logging reports all SIP UDP traffic to logs fine, but no TCP traffic. >>> >>> root@homer02:~# netstat -al >>> Active Internet connections (servers and established) >>> Proto Recv-Q Send-Q Local Address Foreign Address State >>> tcp 0 0 homer02.me.com:sip *:* LISTEN >>> >>> >>> I don't think this is a homer issue because logging invites is prior >>> to any homer processing. I'm thinking this is something simple I'm >>> overlooking, any help is much appreciated. >>> [View Less]

2 1

Remove/Append headers in 200 canceling and 200 ok to BYE
by Diego Nadares 16 Jan '17

16 Jan '17

Hi List, I'm trying to add and remove some headers in 200 canceling and 200 ok to BYEs with no success. I don't know in which route to add my remove_hf and append_hf. It seems that I can't catch it on reply either on request route. I tried adding it in event_route[tm:local-response] { xlog("L_ERR", "TM LOCAL REPONSE!"); route(MANAGE_HEADERS); } This is my route to manage hdrs: route[MANAGE_HEADERS]{ xlog("L_ERR", "MANAGE HDRS !"); keep_hf("TH"); # for … [View More]

3 9

Re: [SR-Users] Kamailio not processing SIP TCP
by JR Richardson 16 Jan '17

16 Jan '17

Iptables is not blocking, but it was worth a check. Thanks. JR I assume you have ruled out firewall? It's something that can nab even experienced people: # iptables -Ln -- Alex On Thu, Jan 12, 2017 at 03:25:27PM -0600, JR Richardson wrote: > Hi All, > > Just enabled SIP TCP on a homer capture server, I can see the SIP TCP > Sessions on the server with ngrep, just like all the UDP traffic. I > have Kamailio listening on TCP ports but its not capturing any TCP > traffic.… [View More] > > kamailio.cfg: > > #disable_tcp=yes > listen=tcp:10.99.99.99:5060 #monitor port > listen=udp:10.99.99.99:5060 #monitor port > > loadmodule "pv.so" > loadmodule "db_mysql.so" > loadmodule "sipcapture.so" > loadmodule "textops.so" > loadmodule "rtimer.so" > loadmodule "xlog.so" > loadmodule "sqlops.so" > loadmodule "htable.so" > loadmodule "sl.so" > loadmodule "siputils.so" > > > modparam("sipcapture", "capture_on", 1) > modparam("sipcapture", "hep_capture_on", 0) > modparam("sipcapture", "raw_socket_listen", "10.99.99.99:5060-5070") > modparam("sipcapture", "raw_interface", "eth1") > modparam("sipcapture", "raw_ipip_capture_on", 0) > modparam("sipcapture", "table_name", "sip_capture") > modparam("sipcapture", "raw_sock_children", 4) > modparam("sipcapture", "db_insert_mode", 0) > modparam("sipcapture", "raw_moni_capture_on", 1) > modparam("sipcapture", "promiscious_on", 1) > modparam("sipcapture", "raw_moni_bpf_on", 1) > modparam("sipcapture", "capture_node", "homer02") > modparam("sipcapture", "authorization_column", "authorization") > > > ## logging all INVITES top of the [route] block > if (is_method("INVITE|REGISTER")) { > xlog("L_INFO", "Received INVITE \"$fU\" to \"$rU\" > from \"$si\"\n"); > > Logging reports all SIP UDP traffic to logs fine, but no TCP traffic. > > root@homer02:~# netstat -al > Active Internet connections (servers and established) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 homer02.me.com:sip *:* LISTEN > > > I don't think this is a homer issue because logging invites is prior > to any homer processing. I'm thinking this is something simple I'm > overlooking, any help is much appreciated. > > Thanks. > > JR > -- > JR Richardson > Engineering for the Masses > Chasing the Azeotrope > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users [View Less]

3 2

Kamailio segfault on TM module
by José Seabra 16 Jan '17

16 Jan '17

Hi there, I have noticed a segfault on my kamailio server but as i have coredumps disabled and i don't know how i can reproduce it, i can't provide that kind of information. Anyway i don't know if anyone of you can help with the following information: segfault at 600 ip 00007f5cb97af1ea sp 00007ffed96b8d60 error 6 in tm.so[7f5cb9718000+11d000] ERROR: tm [t_reply.c:533]: _reply_light(): ERROR: _reply_light: can't generate 404 reply when a final 200 was sent out ERROR: sl [sl.c:269]: send_reply(… [View More]): failed to reply stateful (tm) WARNING: db_postgres [km_dbase.c:281]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] ALERT: <core> [main.c:739]: handle_sigs(): child process 2048 exited by a signal 11 CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 14 ALERT: <core> [main.c:742]: handle_sigs(): core was not generated INFO: <core> [main.c:754]: handle_sigs(): terminating due to SIGCHLD INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received INFO: <core> [main.c:809]: sig_usr(): signal 15 received Database server was down during this segfault, but the segfault was on TM module not on database module. Thank you Regards José Seabra [View Less]

2 1

dbtext module issue
by Satish Patel 16 Jan '17

16 Jan '17

I am trying use dbtext module instead of mysql and following is my configuration. We are using old SER version because of custom written module. Do you think following config looks good. # -- permissions params -- modparam("permissions", "db_url", "dbtext:///etc/ser/dbtext") modparam("permissions", "db_mode", 0) modparam("permissions", "trusted_table", "trusted") In function if ( !allow_trusted() && !search ("^User-Agent:.*Some Perl client.*") ) { xlog("… [View More]

2 2

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