- sr-users - kamailio.org

Parmas in lcr_gw
by Ashutosh chaubey 28 Aug '18

28 Aug '18

Hi, How to give username and password for the gateway in params column in lcr_gw? Regards, Ashutosh

2 1

regular expression in kamailio
by Wilkins, Steve 25 Aug '18

25 Aug '18

Hi All, I am trying get the 10digit number called in on using the following $var(caller) = $(fu{re.subst,[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]}); I thought I could use a regular expression for the expression in re.subst,expression Thank you, -Steve

2 8

Listner problems
by Wilkins, Steve 25 Aug '18

25 Aug '18

Hi Joel, Actually, I have a strange issue. If I have a single UDP IP:Port listening, most Providers/Phones have two-way Audio/Video, however, with some Providers/Phones, I need to have two UDP IP:Port listners in order to get two-way Audio/Video. Here is the strange thing. If I enable two, the Providers/Phones that worked when I had a single listener only have one-way Audi/Video. I use Kamailio 5.1 and Asterisk 15.3 (pjsip). This behavior is so strange, Thank you, -Steve

2 2

add listen dynamically
by Wilkins, Steve 24 Aug '18

24 Aug '18

Hi All, Is it possible to add or remove "listen" dynamically? Thank you, -Steve

2 2

Struggling with RTPEngine
by Wilkins, Steve 24 Aug '18

24 Aug '18

Hi Florian, Thank you for your response. I checked and direct-media is off. Just as a recap, here is where I am I just can't get rtpengine to work. I have tried multiple configurations, but to no avail. Note that calls work good if rtpengine is disabled. Here is my setup => Public IP: 20.20.20.20 Private IP 10.10.10.10 flow => webrtc client <-> kamailio+rtpengine <-> asterisk <-> kamailio <-> legacy sip phone rtpenngine startup (I have tried a few different startups) => rtpengine --interface=int/10.10.10.10 --interface=ext/10.10.10.10\!20.20.20.20 --listen-ng=127.0.0.1:12221 --pidfile=/var/run/rtpengine --dtls-passive -f -m 10000 -M 20000 -E kamailio => Invites: rtpengine_manage("trust-address replace-origin replace-session-connection direction=ext direction=int ICE=remove RTP/AVP"); Reply's: rtpengine_manage("trust-address replace-origin replace-session-connection ICE=force RTP/SAVPF"); I have tried direction ext ext; and many other combinations, each producing its own incorrect behavior. Thanks again, Steve

1 0

Struggling with RTPProxy and RTPEngine
by Wilkins, Steve 24 Aug '18

24 Aug '18

Hello all, I can't seem to get either RTPProxy or RTPEngine to work correctly. I have decided to concentrate on RTPEngine because I have read that it works the best. I am using Asterisk with Kamailio in front. When I make calls, I see RTPEngine being hit but I continually get the error "Call-ID not found", calls work but media traffic doesn't go through RTPEngine. I have tried many combination of the flags but I seem to always get the same error. When I look at the tcpdump log, I see that the media offer is not on the RTPEngine port. Is there a common mis-configuration error that can cause this? I know I can send all my logs and configurations but I really want to try and resolve this as a learning experience. Thanks all, -Steve

8 17

Send a BYE for the call
by Nicolas Breuer 23 Aug '18

23 Aug '18

Hello, Any ideas how to cut a call in progress ? How to send a forced "BYE" to all parties ? Thanks

2 2

Kamailio 5.1.4 crashes
by Abdulaziz Alghosh 23 Aug '18

23 Aug '18

Hi Everyone, I am trying to start kamailio 5.1.4 with two own modules. After /etc/init.d/kamailio start , I am getting one error of the dispatcher module and bunch of warrnings because of missed reply and failure routes. The first error before crashing is: ERROR: dispatcher [dispatcher.c:814]: ds_warn_fixup(): failover functions used, but required AVP parameters are NULL -- feature disabled Later on, when I am trying to register a user (from a soft phone) i am getting the following: ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) Aug 22 10:02:52 sgw1a /sbin/kamailio[6960]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 20 Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: ALERT: <core> [main.c:746]: handle_sigs(): child process 6942 exited by a signal 11 Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: ALERT: <core> [main.c:749]: handle_sigs(): core was not generated Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: INFO: <core> [main.c:771]: handle_sigs(): terminating due to SIGCHLD Aug 22 10:02:52 sgw1a /sbin/kamailio[6959]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6958]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6957]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6956]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6955]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6954]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6953]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6950]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6941]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6944]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6948]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6951]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6946]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6952]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6943]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6949]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6947]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6938]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6937]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6940]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6939]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a kernel: [296301.271457] kamailio[6942]: segfault at 0 ip (null) sp 00007fffb3ddf368 error 14 in kamailio[400000+442000] Aug 22 10:02:52 sgw1a /sbin/kamailio[6945]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6960]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6936]: INFO: <core> [main.c:826]: sig_usr(): signal 15 received Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: ERROR: jsonrpcs [jsonrpcs_fifo.c:594]: jsonrpc_fifo_destroy(): cannot delete the fifo (/tmp/kamailio_jsonrpc.fifo): Operation not permitted Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: ERROR: jsonrpcs [jsonrpcs_sock.c:511]: jsonrpc_dgram_destroy(): cannot delete the socket (/tmp/kamailio_rpc.sock): Operation not permitted Aug 22 10:02:52 sgw1a /sbin/kamailio[6935]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Regarding to the first error of the dispatcher module i could not find out which calibration i can follow with its parameters to get rid of this error. Regarding the jasonrpcs and the last two erros, here are my configuration in kamailio.cfg: #/* set the path to RPC fifo control file */ modparam("jsonrpcs", "fifo_name", "/tmp/kamailio_jsonrpc.fifo") modparam("jsonrpcs", "fifo_mode", 0755) modparam("jsonrpcs", "fifo_group", "kamailio") modparam("jsonrpcs", "fifo_user", "kamailio") #/* set the path to RPC unix socket control file */ modparam("jsonrpcs", "dgram_socket", "/tmp/kamailio_rpc.sock") modparam("jsonrpcs", "dgram_mode", 0755) modparam("jsonrpcs", "dgram_user", "kamailio") modparam("jsonrpcs", "dgram_group", "kamailio") I think the root cause is even beyond the dispatcher and jsonrpcs modules setting. Please check the attached where you can find my complete log file after starting Kamailio. Best regards Abdulaziz

2 4

Dispatcher - Force one end point active
by Marrold 23 Aug '18

23 Aug '18

Hi, We are currently using the dispatcher module and probing end points with OPTIONS, and making them active / inactive depending on the response: modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=3;code=404") modparam("dispatcher", "ds_ping_from", "[REDACTED]") modparam("dispatcher", "ds_ping_interval", 20) modparam("dispatcher", "ds_probing_threshold", 1) modparam("dispatcher", "ds_probing_mode", 1) One of our suppliers endpoints doesn't respond to SIP OPTIONS, is it possible to force a single endpoint as active, but continue probing the rest? I've tried various settings - both globally and flags for the individual end point, but I couldn't seem to find the correct combination. Thanks Matthew

2 2

Re: [SR-Users] Fail to reload htable
by Henning Westerholt 23 Aug '18

23 Aug '18

Am Montag, 20. August 2018, 20:58:43 CEST schrieb Soltanici Ilie: > In the logs, I see these errors: > > ERROR: <core> [db.c:463]: db_use_table(): invalid parameter value > Aug 20 19:56:41 kamailio[12716]: ERROR: <core> [db.c:463]: db_use_table(): > invalid parameter value Aug 20 19:56:41 kamailio[12716]: ERROR: htable > [ht_db.c:211]: ht_db_load_table(): failed to use_table Hi, please keep the list in CC. This error is related to a database issue. Please double check if there are any issues during startup in the log. Do you see any other error there? A similar (not 100% identical) issue was discussed recently here: https://lists.kamailio.org/pipermail/sr-users/2018-August/102393.html Maybe this helps you as well. Best regards, Henning -- Henning Westerholt https://skalatan.de/blog/

4 7

Re: [SR-Users] Struggling with RTPProxy and RTPEngine
by Wilkins, Steve 23 Aug '18

23 Aug '18

Good morning Daniel, If RTPEngine is on the same server as Kamailio (Asterisk being on another server), and RTP traffic is sent to and from RTPEngine, then the provider only needs to whitelist one IP-Address. I thought with RTPEngine that all RTP traffic would go through it and then it would pass it on to the correct destination. Is this correct? Thank you -----Original Message----- From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Daniel Tryba Sent: Thursday, August 23, 2018 4:36 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] Struggling with RTPProxy and RTPEngine MITRE WARNING: Do not open unexpected password-protected attachments. >>>Email originates from a non-MITRE system. Use caution.<<< On Wed, Aug 22, 2018 at 05:05:02PM +0000, Wilkins, Steve wrote: > The SIP traffic is working this way for me but I still see RTP traffic going directly from Asterisk to the UAC, which means they need to whitelist asterisk IP. Am I missing something? In what sense do they need whitelisting? In a common NATed solution where is no white/blacklist needed. UA gets RTP endpoints from SDP, starts sending packets to ip/port and the destination will send back packets to the source ip/port, the router/firewall will just send this to the actual UA. I have yet to find an UA that cares about where the RTP stream is coming from with regards to the SIP traffic.

2 1

SIP and RTP Proxy for multiple Servers
by sewlist＠gmail.com 23 Aug '18

23 Aug '18

Im very new to kamailio, we have some ptime issues which causes one way audio due to varies PBX vendors connecting to our class 5 softswitches I would like to use Kamailio as the SIP/RTP proxy in front of our class 5 soft switches I followed the example of freeswitch and kamailio. However the config is still hard for me below setup works, however RTP not being proxied, Looks like its its not, because im not using NAT, so RTP goes direct https://freeswitch.org/confluence/display/FREESWITCH/Kamailio+basic+setup+a… I would like to to ensure RTP proxy is always used(possible re-framing ptime) and we have multiple soft switches Is it possible to setup kamailio.cfg so my customers can point the endpoint to kamailio and domain names contains the server we want to use to register with? eg, softswitch 1 = 1.1.1.2 softswitch 2 = 1.1.1.3 softswitch 3 = 1.1.1.4 etc etc my current config #!KAMAILIO #!define IPADDRESS "1.1.1.1" #!define SWITCH_IPADDRESS "1.1.1.2" #!define FLAG_FROM_SWITCH 1 #!define FLAG_FROM_USER 2 # ------------------ module loading ---------------------------------- loadmodule "tm.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "sl.so" loadmodule "maxfwd.so" loadmodule "nathelper.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "path.so" loadmodule "rtpproxy.so" # ----------------- setting module-specific parameters --------------- modparam("nathelper|registrar", "received_avp", "$avp(s:rcv)") # ------------------------- request routing logic ------------------- #!ifdef WITH_NAT # ----- rtpproxy params ----- modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") # ----- nathelper params ----- modparam("nathelper", "natping_interval", 30) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "sipping_bflag", FLB_NATSIPPING) modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") # params needed for NAT traversal in other modules modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") modparam("usrloc", "nat_bflag", FLB_NATB) #!endif # main routing logic route { # per request initial checks route(SANITY_CHECK); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { t_relay(); } exit; } route(CHECK_SOURCE_IP); ################################## ### HANDLE SEQUENTIAL REQUESTS ### route(WITHINDLG); ############################### ### HANDLE INITIAL REQUESTS ### t_check_trans(); if (is_method("INVITE|REFER")) { record_route(); } if (is_method("REGISTER")) { add_path(); } if (isflagset(FLAG_FROM_SWITCH)) { # don't send INVITE from SWITCH back to SWITCH, set reply route to handle NAT and forward them along t_on_reply("EXTERNAL_REPLY"); } else { # set destination to your SWITCH $du = "sip:1.1.1.2:5060"; } route(RELAY); } route[SANITY_CHECK] { if (!sanity_check()) { #xlog("L_WARN", "$ci|end|message is insane"); exit; } if (!mf_process_maxfwd_header("10")) { #xlog("L_WARN", "$ci|end|too much hops, not enough barley"); send_reply("483", "Too Many Hops"); exit; } if ($ua == "friendly-scanner" || $ua == "sundayddr" || $ua =~ "sipcli" ) { #xlog("L_WARN", "$ci|end|dropping message with user-agent $ua"); exit; } if ($si == IPADDRESS) { #xlog("L_WARN", "$ci|end|dropping message"); exit; } } route[CHECK_SOURCE_IP] { if ($si == SWITCH_IPADDRESS) { setflag(FLAG_FROM_SWITCH); } else { setflag(FLAG_FROM_USER); } } # Handle requests within SIP dialogs route[WITHINDLG] { if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { route(RELAY); } else { if (is_method("NOTIFY")) { route(RELAY); } if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests exit; } if (is_method("ACK")) { if (t_check_trans()) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server t_relay(); exit; } else { # ACK without matching transaction ... ignore and discard #xlog("ACK without matching transaction ... ignore and discard"); exit; } } sl_send_reply("404","Not here"); } exit; } } onreply_route[EXTERNAL_REPLY] { route(NAT_TEST_AND_CORRECT); } route[NAT_TEST_AND_CORRECT] { if (nat_uac_test("3")) { if (is_method("REGISTER")) { fix_nated_register(); } else { fix_nated_contact(); } force_rport(); } if (has_body("application/sdp") && nat_uac_test("8")) { fix_nated_sdp("10"); } } route[RELAY] { #!ifdef WITH_NAT if (check_route_param("nat=yes")) { #setbflag(FLB_NATB); route(RTPPROXY); } if (isflagset(FLT_NATS) || isbflagset(FLB_NATB)) { route(RTPPROXY); } #!endif route(RTPPROXY); /* example how to enable some additional event routes */ if (is_method("INVITE")) { #t_on_branch("BRANCH_ONE"); t_on_reply("REPLY_ONE"); t_on_failure("FAIL_ONE"); } if (!t_relay()) { sl_reply_error(); } exit; # if (!t_relay()) { # sl_reply_error(); # } # exit; } # RTPProxy control route[RTPPROXY] { #!ifdef WITH_NAT if (is_method("BYE")) { #unforce_rtp_proxy(); force_rtp_proxy(); } else if (is_method("INVITE")){ force_rtp_proxy(); } if (!has_totag()) add_rr_param(";nat=yes"); #!endif return; }

2 1

RTPEngine wow's
by Wilkins, Steve 22 Aug '18

22 Aug '18

Hello all, I am still trying to get RTPEngine to work. At this point, when I make a call, I do see the offer in the rtpengine log, I also see the update of the SDP (c) changing it to 20.20.20.20. However, after that, there are no logs other than a bunch of "timer run time = 0.nnnnnnn sec", and the delete when I hang up the call. There is no RTP traffic what so ever in the rtpengine log (however, the call is completely successful, other than the RTP traffic not going through RTPEngine). Here is a breakdown of my configs (I borrowed this format from Maxim Fedorov because I thought it was very concise) Starting rtpengine => rtpengine --interface=internal/21.21.21.21--interface=external/21.21.21.21\!20.20.20.20 --listen-ng=127.0.0.1:12221 --dtls-passive -f -m 10000 -M 20000 -E -L 7 --log-facility=local1 RTPEngine Public IP: 20.20.20.20 RTPEngine Private IP: 21.21.21.21 kamailio.cfg modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:12221") listen=tcp: 21.21.21.21:5060 advertise 20.20.20.20:5060 listen=udp: 21.21.21.21:5060 advertise 20.20.20.20:5060 rtpengine_manage call rtpengine_manage("trust-address replace-origin replace-session-connection external external media-address=20.20.20.20"); (I have placed this rtpengine_manage call at the beginning of all routes). I have tried many variations of rtpengine_manage parameters, and placement of the call itself, but I never see RTP traffic in the rtpengine log. Thank you to all who have looked at this, -Steve

1 0

Error at startup
by Nicolas Breuer 22 Aug '18

22 Aug '18

Hello, How can i clear this error ? Aug 22 13:05:56 proxy1 kamailio: ERROR: <core> [core/pvapi.c:228]: pv_table_add(): pvar [rtpstat] already exists Aug 22 13:05:56 proxy1 kamailio: ERROR: <core> [core/pvapi.c:513]: register_pvars_mod(): failed to register pseudo-variable <rtpstat> for module rtpproxy

2 2

Releasing Kamailio v5.1.5
by Daniel-Constantin Mierla 22 Aug '18

22 Aug '18

Hello, with the summer holidays in the northern hemisphere approaching the end, I am considering to release v5.1.5 out of Kamailio git branch 5.1 -- there were several fixes done since 5.1.4 and it is time to package another minor release. The propose date is next week on Wednesday, August 22, or slightly after in case there are unexpected events delays it. Should there be any issues you are aware of and not yet reported on the bug tracker, do it asap in order to have a chance to be fixed: - https://github.com/kamailio/kamailio/issues Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com

1 2

Encoding mechanism in UAC Module
by Duarte Rocha 21 Aug '18

21 Aug '18

Greetings, Is there a way to choose the encoding algorithm that builds the vsf and vst parameters in the Record-Route? What is the default method that Kamailio uses for this ? Thanks in advance, Duarte Rocha

2 1

invalid version 8 for table aliases found, expected 9
by Abdulaziz Alghosh 21 Aug '18

21 Aug '18

Hi everyone, i am trying to start kamailio 5.1.4 after the migration from Kamailio 3.0.3 but getting newly the following error: ERROR: <core> [db.c:450]: db_check_table_version(): invalid version 8 for table aliases found, expected 9 (check table structure and table "version") Allegedlly, this error is because of a wrong version of "aliases" table. I followed the Upgrade process starting from 3.0.3 till 5.1.x and I altered the structure of my aliase table accordinglly. The last new version of aliases is 8 as it is described at the upgrade from 4.2.x to 4.3.0 Even though, the error here says that the newest version is 9: May someone help me to find out if the aliases table's structure was renewed in between ?? Is there any modification in the data types? Thanks in advance Abdulaziz

3 4

ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed
by Abdulaziz Alghosh 21 Aug '18

21 Aug '18

Greetings, i am at the final stages of emigrating from kamailio 3.0.3 to 5.1.0 including our own module. Unluckily, after writing the command " kamctl start", the following error is popping up: * PID file /var/run/kamailio.pid does not exist -- Kamailio start failed* Thus, I used the command " kamailio -M 8 -E -e -dd " to get more debugging Info and the output is detailing the following: 0(10334) ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.168.1.207' (4) 0(10334) ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool 0(10334) ERROR: ABDUL_functions [ABDUL_chk.c:1069]: init_db(): failed to connect database URL=mysql://ABDUL:ABDUL@192.168.1.207/ABDUL 0(10334) ERROR: ABDUL_functions [ABDUL_functions_mod.c:296]: mod_init(): Module ABDUL_functions not correktly initialized, pid[10334] 0(10334) ERROR: <core> [core/sr_module.c:991]: init_mod(): Error while initializing module ABDUL_functions (//lib64/kamailio/modules/ABDUL_functions.so) Seemingly the error relates to old databases url ( "URL=mysql:// ABDUL:ABDUL@192.168.1.207/ABDUL" ) inside an old Kamailio.cfg file from my 3.0.3 package which I put under another different directory. This old Kamailio.cfg file #includes my own module, so he is exporting this url. Consequently, my module is trying to connect again to this databases. I do not know why both kamailio.cfg (new: /etc/kamailio/kamailio.cfg and old one out of /etc/kamailio) are both seen for kamctl or (/sbin/kamailio). I know that my new url inside the new /etc/kamailio/kamailio.cfg is read and connected but again not sure why my hidden old kamailio.cfg is still being read as well. the attached shows my init file for "SUSE Linux Enterprise Server 11 (x86_64)" and my used kamailio *default *file under /etc/default. Thanks in advance and best regards Abdulaziz

2 2

help
by Pravin . 21 Aug '18

21 Aug '18

Hello Team, I want to install Kamailio SIP server on centOS server...do we need to download kamailio ISO file and install on server..pls provide the installation procedure/guidelines. Regards Pravin

6 14

Dialplan priority
by igor.potjevlesch＠gmail.com 21 Aug '18

21 Aug '18

Hello, I'm not sure to understand in which situation "pr" value is used. For example: if I have two identical rules except pr value: 1 with 1 and the second with 2, then the rule with pr 2 is never used. Someone can help me to understand? Thank you. The finality I'd like to accomplish is having some kind of load balacing between two values into "repl_exp" with the same inputs conditions. Thank you. Regards, Igor.

2 2

Call Transfer Scenario Using Freeswitch
by Sunil More 21 Aug '18

21 Aug '18

Hi All, I am using kamailio and freeswitch in my setup. While all users are registered on Kamailio, calls are routed to Freeswitch back to kamailio and then upstream providers. I can make user to user calls but in cases of transfer I am stuck. I am using a Polycom IP phone to test this scenario. While I initiate a attended transfer and click on transfer all the legs hangup. When I register all users on Freeswitch this works well. I am missing something on Kamailio side. Please point me in the right direction. Thanking You, Sunil More Ph : 9503338275

2 1

Enabling tcp_write_buf
by Gholamreza Sabery 21 Aug '18

21 Aug '18

Hi, In the documentation of "tcp_wq_max" option it is written that : > It has no effect if *tcp_write_buf *is not enabled. > > The interesting fact is that, there is not description of what it is and how one can enable it. There is even a question about it in the mailing lists: https://lists.kamailio.org//pipermail/sr-dev/2011-June/011521.html It seems that it is an inaccuracy in the documentation. If there is such an option how to enable it? Can anyone tell? Regards

3 2

Best practice/routing block for TCP connection errors to UAC?
by Anthony Alba 21 Aug '18

21 Aug '18

HI SR-Users Scenario: clients registered by TCP/TLS dropping off the network, kamailio stil thinks the client is registered and relays the INTIVE. The error occurs at the TCP layer so no failure route is called. ERROR: <core> [core/tcp_main.c:2690]: tcpconn_1st_send(): connect 127.0.0.1:48338 failed (RST) Connection refused ERROR: <core> [core/tcp_main.c:2700]: tcpconn_1st_send(): 127.0.0.1:48338: connect & send for 0x7f5494e906c0 failed: Connection refused (111) ERROR: tm [../../core/forward.h:251]: msg_send_buffer(): tcp_send failed WARNING: tm [t_fwd.c:1567]: t_send_branch(): sending request on branch 0 failed ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) I want to send the caller instead a graceful failure route type message as if the callee is not registered (404/486/603/408 type) but don't understand how to hook a routing block for TCP errors. Anthony

1 0

Fail to reload htable
by Soltanici Ilie 20 Aug '18

20 Aug '18

I'm trying to reload a hash table but receiving an error: error: 500 - Mtree reload failed [root@kamailio]# /usr/local/sbin/kamcmd htable.listTables { name: auth dbtable: dbmode: 0 expire: 0 updateexpire: 1 size: 256 dmqreplicate: 0 } [root@kamailio]# /usr/local/sbin/kamcmd htable.dump auth { entry: 69 size: 1 slot: { { name: username::8.8.8.8 value: 0 type: int } } } [root@kamailio]# /usr/local/sbin/kamcmd htable.reload auth error: 500 - Mtree reload failed [root@kamailio]# /usr/local/sbin/kamailio -v version: kamailio 5.1.4 (x86_64/linux) e8b2bf

2 1

Kamailio 5.1 Nathelper sipping on different transport protocols.
by Володимир Іванець 20 Aug '18

20 Aug '18

Hello everyone! I have system with Kamailio v5.1 which needs to send OPTIONS packets to all active clients. Here is full Nathelper module configuration: *modparam("nathelper", "received_avp", "$avp(s:received)")* *modparam("nathelper", "natping_interval", 30)* *modparam("nathelper", "ping_nated_only", 0)* *modparam("nathelper", "sipping_bflag", FLB_SIPPING)* *modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org <sip%3Apinger(a)kamailio.org>")* It works fine if client is connected over UDP. But as soon as I will switch to TCP or register with client that uses WS, Kamailio stops generating OPTIONS. Does anyone know if it is correct behavior or something is wrong? Thanks a lot!

3 3

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