sr-users

sr-users@lists.kamailio.org

8 participants
37523 discussions

Module RTPPROXY param Timeout_Socket not Working
by Hamid Hashmi 24 Sep '18

24 Sep '18

Kamailio didn't start listening on IP mentioned in Module RTPPROXY parameter Timeout_Socket<https://kamailio.org/docs/modules/5.1.x/modules/rtpproxy.html#rtpproxy.p.ti…>. Below is my configuration file. loadmodule "rtpproxy.so" modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") modparam("rtpproxy", "rtpproxy_tout", 1) modparam("rtpproxy", "rtpproxy_retr", 2) modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:8000/RPC2") loadmodule "xmlrpc.so" modparam("xmlrpc", "route", "XMLRPC"); modparam("xmlrpc", "mode", 1) modparam("xmlrpc", "url_match", "^/RPC2") when I type a command $ netstat -nlp it only shows SIP listening ports. Kamailio should also start listening on 127.0.0.1:8000. Below are the RTPproxy logs, RTPproxy is also unable to bridge the media DBUG:get_command:GLOBAL: received command "19083_4 Uc120,101 9a1060af660d4202976c419ab5300470 58.65.176.42 4000 1ea06d1eb0a8443697a08e568045598c;1" INFO:rtpp_command_ul_handle:GLOBAL: new session 9a1060af660d4202976c419ab5300470, tag 1ea06d1eb0a8443697a08e568045598c;1 requested, type strong INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a port 35012 created, tag 1ea06d1eb0a8443697a08e568045598c;1 INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling caller's address with 58.65.176.42:4000 DBUG:rtpc_doreply:GLOBAL: sending reply "35012 51.38.201.3 " DBUG:get_command:GLOBAL: received command "19083_5 Uc120,101 9a1060af660d4202976c419ab5300470 58.65.176.42 4022 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 1ea06d1eb0a8443697a08e568045598c;1 xmlrpc:http://127.0.0.1:8000/RPC2" INFO:rtpp_command_ul_handle:GLOBAL: new session 9a1060af660d4202976c419ab5300470, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 requested, type strong INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: new session on a port 35014 created, tag 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq;1 ERR:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: invalid socket name 1ea06d1eb0a8443697a08e568045598c;1 INFO:rtpp_command_ul_handle:9a1060af660d4202976c419ab5300470: pre-filling caller's address with 58.65.176.42:4022 DBUG:rtpc_doreply:GLOBAL: sending reply "35014 51.38.201.3 " DBUG:get_command:GLOBAL: received command "19086_4 D 9a1060af660d4202976c419ab5300470 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq 1ea06d1eb0a8443697a08e568045598c" INFO:handle_delete:9a1060af660d4202976c419ab5300470: forcefully deleting session 1 on ports 35012/0 INFO:remove_session:9a1060af660d4202976c419ab5300470: RTP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped INFO:remove_session:9a1060af660d4202976c419ab5300470: RTCP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped INFO:remove_session:9a1060af660d4202976c419ab5300470: session on ports 35012/0 is cleaned up INFO:handle_delete:9a1060af660d4202976c419ab5300470: forcefully deleting session 1 on ports 35014/0 INFO:remove_session:9a1060af660d4202976c419ab5300470: RTP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped INFO:remove_session:9a1060af660d4202976c419ab5300470: RTCP stats: 0 in from callee, 0 in from caller, 0 relayed, 0 dropped INFO:remove_session:9a1060af660d4202976c419ab5300470: session on ports 35014/0 is cleaned up DBUG:rtpc_doreply:GLOBAL: sending reply "0 " DBUG:get_command:GLOBAL: received command "19086_5 D 9a1060af660d4202976c419ab5300470 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq 1ea06d1eb0a8443697a08e568045598c" INFO:handle_command:GLOBAL: delete request failed: session 9a1060af660d4202976c419ab5300470, tags 9RPsEBbcZSA23MmWAw0hfXzJ-bG1GYDq/1ea06d1eb0a8443697a08e568045598c not found DBUG:rtpc_doreply:GLOBAL: sending reply "E50 But if I comment out the param "Timeout_Socket" then there is no issue in bridging the media. Regards Hamid R. Hashmi

3 6

uac usage
by David Villasmil 21 Sep '18

21 Sep '18

Hello guys On my working config, i enabled uac like so: loadmodule "uac.so" ... modparam("uac", "reg_db_url", DBURL) modparam("uac", "reg_db_table", "uacreg") modparam("uac", "reg_contact_addr", "test-proxy.singlecomm.com") ... And i added a user to the uacreg table: id,l_uuid,l_username,l_domain,r_username,r_domain,realm,auth_username,auth_password,auth_ha1,auth_proxy,expires,flags,reg_delay 1,10001,myuser,test-proxy.test.com,myuser,myprovider.com,myprovider.com ,myuser,mypass,,sip:myprovider.com,300,0,0 But it's not trying to register, and when i do: #> kamcmd uac.reg_info l_uuid 10001 I get: error: 404 - Record not found What am I doing wrong? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 2

Jsonrpc_exec does not get body of request
by Denys Pozniak 21 Sep '18

21 Sep '18

Hello! I need to get some data via RPC to Kamailio inside by external event. But it seems long values of body brakes something: loadmodule "xhttp.so" loadmodule "jsonrpcs.so" modparam("jsonrpcs", "transport", 0) 1) event_route[xhttp:request] { ... jsonrpc_exec('{"jsonrpc": "2.0", "method": "core.psx", "id": 1}'); xlog("L_ERR","RPC code: $jsonrpl(code) \n"); xlog("L_ERR","RPC text: $jsonrpl(text) \n"); xlog("L_ERR","RPC body: $jsonrpl(body) \n"); return; } But in result I do not have body: Sep 21 14:27:55 /usr/sbin/kamailio[16140]: ERROR: <script>: RPC code: 200 Sep 21 14:27:55 /usr/sbin/kamailio[16140]: ERROR: <script>: RPC text: OK 2) If I request core.uptime I have something in body: event_route[xhttp:request] { ... jsonrpc_exec('{"jsonrpc": "2.0", "method": "core.uptime", "id": 1}'); xlog("L_ERR","RPC code: $jsonrpl(code) \n"); xlog("L_ERR","RPC text: $jsonrpl(text) \n"); xlog("L_ERR","RPC body: $jsonrpl(body) \n"); return; } Sep 21 14:37:17 /usr/sbin/kamailio[22683]: ERROR: <script>: RPC code: 200 Sep 21 14:37:17 /usr/sbin/kamailio[22683]: ERROR: <script>: RPC text: OK Sep 21 14:37:17 /usr/sbin/kamailio[22683]: ERROR: <script>: RPC body: {"jsonrpc":"2.0","result":{"now":"Fri Sep 21 14:37:17 2018","up_since":"Fri Sep 21 14:37:16 2018","uptime":1},"id":1} [root@kamailio]# kamailio -v version: kamailio 5.1.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. -- BR, Denys Pozniak

1 0

Include parameters in replies
by Duarte Rocha 21 Sep '18

21 Sep '18

Greetings, I need to to include some routing information (Two Id's, example "id_in=10;id_out=72") to be read later by Kamailio in every Request (Except the first one and in every Reply. For the requests, i'm including this info as parameters in the Record-Route and i'm reading it later in the Route Headers. For replies i thought about using the Via header. I'm using subst_hf() and i'm having success adding the parameter to Via in the requests. However, it does not seem the best idea since i breake the routing when i add the parameter. I wanted to avoid using custom headers for this since i can't really be sure that they won't be erased by any client's CPE or endpoint. Any ideas on this ? Thanks Cheers, Duarte Rocha

1 0

usr location
by volga629＠networklab.ca 21 Sep '18

21 Sep '18

Hello Everyone, User location lookup looks like can't handle long $rU like 10102-ce72256df4945bc472ed9c27a1037f46. It always return -3 404 not found. here relevant log Sep 19 23:37:26 canlvprx01 /usr/sbin/kamailio[29217]: INFO: <script>: [INVITE] Call going from LAN SourceIP <10.18.130.50> to WAN. Sep 19 23:37:26 canlvprx01 /usr/sbin/kamailio[29217]: INFO: <script>: Looking user --> 10102-ce72256df4945bc472ed9c27a1037f46 in db Sep 19 23:37:26 canlvprx01 /usr/sbin/kamailio[29217]: INFO: <script>: Got [INVITE] and status <null> route[LOCATION] { $avp(oexten) = $rU; xlog("L_INFO", "Looking user --> $rU in db\n"); if (!lookup("location")) { $var(rc) = $rc; t_newtran(); switch ($var(rc)) { case -1: case -3: route(MSG_STORE); # Meaning SMS has being stored for offline delivery if(!t_check_status("202")) { xlog("L_INFO", "Got [$rm] and status [$rs]\n"); # For rest traffic proceed as normal send_reply("404", "Not Found"); } exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } } kamailio-5.1.3-1.gitf0dce0c99.fc27.x86_64 volga629

4 3

Re: [SR-Users] Daemon won't start
by Henning Westerholt 20 Sep '18

20 Sep '18

Am Samstag, 15. September 2018, 20:00:39 CEST schrieb hexhaxtron: > I can't make it work... > > It seems to have created the databases without any problem. > [pastebin cfg and logs] Hi Hexatron, please keep the list in CC. you should investigate why this error happens: Sep 14 06:52:07 thunix.org mysqld[1943]: 2018-09-14 6:52:07 140187532334848 [Warning] Access denied for user 'kamailio'@'localhost' (using password: YES) Sep 14 06:52:07 thunix.org /usr/sbin/kamailio[4254]: ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Access denied for user 'kamailio'@'localhost' (using password: YES) Can you login with a mysql client on a shell to the database with the same credentials? Best regards, Henning -- Henning Westerholt https://skalatan.de/blog/

1 0

Kamailio On Tap – Social Event In Dusseldorf, Sep 27, 2018
by Daniel-Constantin Mierla 20 Sep '18

20 Sep '18

Hello, we are organizing an open social networking event in the evening of Sep 27, 2018, in Dusseldorf, at the end of the first day of Kamailio Developers meeting. Anyone in the area that wants to enjoy beer, pizza and chat about Kamailio, VoIP/RTC is welcome to join us. More details at: * https://www.kamailio.org/w/2018/09/kamailio-on-tap-social-event-in-dusseldo… Note that participation is free, but you have to announce your participation until Sep 26 in order to plan properly the event. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

1 0

usr location
by volga629＠networklab.ca 20 Sep '18

20 Sep '18

1 0

re- double record route
by Wilkins, Steve 19 Sep '18

19 Sep '18

Hi Henning, Yes I do have that enabled. What is happening is that one of the providers on IOS is sending a double record route on the INVITE, but it is getting lost somewhere so when I send a 'BYE', I get a "404 not here". When I look at the SIP message I see only one of the record routes from the INVITE, therefore my assumption is, this is what is causing the 404, because everything else looks good.

3 8

occasional processing delay and UAC remote registration
by Dmitri Savolainen 19 Sep '18

19 Sep '18

Hi all. i encountered in my 4.1.5 kamailio server some inconstant issue. I have 2 listen address: addr1 for incoming SIP requests and as source addr for remote registration (via UAC module) addr2 for incoming SIP requests only uac config for regs: modparam("uac", "reg_keep_callid", 1) modparam("uac", "reg_random_delay", 120) modparam("uac", "reg_retry_interval", 300) modparam("uac", "reg_timer_interval", 40) i have response time checking tool, that send OPTIONS every second, which immedeately replied by sl_send_reply("200") without any processing. Usualy respose time <1ms. Sometimes (2-3 per day) addr1 stop to response for these OPTIONS (timeout >5sec), while addr2 continue responding with time <1ms. In kamailio.log at this moment bunch of messages like ERROR: uac [uac_reg.c:1034]: uac_reg_tm_callback(): got sip response 403 > while registering ERROR: uac [uac_reg.c:1034]: uac_reg_tm_callback(): got sip response 408 > while registering That is normal: some remotes are broken. The problem is: 1. usually these messages appearing is not the reason of problem, but all problems are while these messages in log 2. it may be on OFF peak / ON peak day period 3. in my test installation i have much more remote failure registration (X 10), and the problem is not manifested more often (but i can catch it 2-3 per day) I think adding more workers for addr1 may help (now 8 worker and 16 CPUs). But it is interesting to understand the source of this issue -- Savolainen Dmitri

1 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