sr-users September 2018

sr-users@lists.kamailio.org

72 participants
123 discussions

KAMAILIO 5.1 : How to enable and subscribe to all of the SIP events and kamailio server through tcp, json

by yboujraf＠by-systems.be

Dear All, I am currently working to control from third party system Kamailio I have there are several way to interact with Kamailio but not sure I could make what I am expecting My question is : * I would like to get from my third party system subscribe to all of the sip events and status of the kamailio server My best way is TCP, JSON, scrambled if possible It will be great if anybody could route me to the correct direction. Best Regards, Youssef --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

6 years, 4 months

KAMAILIO 5.1 - how to make a full redundancy of two kamailio Proxy server ?

by yboujraf＠by-systems.be

Dear All, I am currently thinking to use TWO (2) Kamailio Proxy server in redundancy. The system is : * I have one (1) public address * Two (2) Kamailio Servers with two different IP address My questions are : * What I need to add in front of the two Kamailio servers to be sure sip phone will be connected through the public ip address to one of the kamailio server at time. I have seen we could enable "cluster module" to sync the dabase of the two (2) kamailio server at the same time but not for the request. * Script to add to be sure the kamailio servers are correctly configured. Best Regards, Youssef --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

6 years, 4 months

kamailio not forwarding 407

by David Villasmil

Hello guys, I have an almost default config, the box behind kamailio sends out the register, it is forwarded to the provider, which replies with 401, this gets forwarded back to the box which sends out the REGISTER with credentials and all works well. BUT when calling out, INVITE is sent to kamailio which is properly forwarded to the provider. The provider replies with a 407 and this 407 is NOT forwarded back to the box. Any ideas why? I can't figure it out! Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

6 years, 4 months

Dispatcher's Probing

by Duarte Rocha

Hey, I've been using the Dispatcher module with great results. But now, i want to be able to have some gateways to belong to more than one group set. To achieve that, i'm duplicating the Gateway in the Dispatcher's table and give it a different group set. However, if i do this, Dispatcher will do repeated probing to this gateways. Is there any way to avoid this or to achieve the same result in a different way? Best Regards

6 years, 4 months

No dispatcher failover

by Gertjan Wolzak

Hello Kamailions, I want to send traffic to an Asterisk box but when that box fails traffic should be routed to the second Asterisk box. The dispatcher params are as follows: # ----- Dispatcher params ------ modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_ping_interval", 20) modparam("dispatcher", "ds_ping_reply_codes", "class=2;class=3;class=4") modparam("dispatcher", "ds_inactive_threshold", 4) modparam("dispatcher", "ds_ping_latency_stats", 1) modparam("dispatcher", "ds_probing_threshold", 1) My dispatcher.list is: #DBBS PBX # SBC's 1 sip:ip_address_sbc:5060 0 0 weight=100 #PBX 2 sip:ip_pbx_01:5060 0 10 weight=100 2 sip:ip_pbx_02:5060 0 5 weight=100 Verry simple request route: request_route { if (is_method("OPTIONS")) { sl_send_reply("200", "OK"); exit; } #Call from SBC to PBX #Get gateway from dispatcher list if($si=="ip_address_sbc1" |$si=="ip_address_sbc2" ) { ds_select_dst("2", "8"); $var(new_uri) = "sip:" + $tU + "@" + $dd + ":5060"; $ru=($var(new_uri)); route(RELAY); exit; } # Call from pbx to SBC # Get sbc ip from dispatcher list ds_select_dst("1","4"); $var(new_uri) = "sip:" + $tU + "@" + $dd + ":5060"; $ru=($var(new_uri)); route(RELAY); } When I send a call to the kamailio its routed correctly to the first pbx. But when I kill the asterisk process on the first pbx, an invite is still send by Kamailio to the first pbx. Maybe I am assuming incorrectly that when the dispatcher does not react to the ds_ping it will be set to "inactive" and not be selected by the ds_select_dst command... Or am I thinking to easy and do I need to configure some actions in the failure route? Pretty sure I'm doing something wrong, but cant see where and have not been able to find the information. Tips are appreciated. Rgds, Gertjan Wolzak

6 years, 4 months

onsend_route showing wrong answer after forking

by Aymeric Moizard

Hi, I'm experimenting "onsend_route" with "onsend_route_reply=yes" to improve my logs. I was surprised to see that "onsend_route" doesn't always display the "forwarded" answer after negative final answers. The documentation seems to indicate that this route will execute only if "the received reply is sent out". -as I'm forking, the final 6xx answer is not "forwarded" immediatly... and I guess this is the reason it doesn't show. Here comes a real strange use-case: With forking enabled, only the last answer will appear in the "onsend_route", however, in some case, this is NOT the answer being forwarded. Example: 1/ receive 603 decline from branch1 2/ a CANCEL is sent on branch2 3/ a 487 Request Terminated is received on branch2 What happens: 1/ onsend_route is showing "487 Request Terminated" 2/ 603 Decline is forwarded (as expected) The documenation say: "If set to 1 (yes, on), onsend_route block is executed for received replies that are sent out. Default is 0." This doesn't look to be correct. (either the doc, or the code?) Is there any possibility to install a log in the script that would log ALL *exact* replies being sent: 1/ the real forwarded ones 2/ and also the ones sent by kamailio directly. May be this is possible with some "event_route"? Tks a lot! Aymeric -- Antisip - http://www.antisip.com

6 years, 4 months

kamailio 5.0.6 | segfault bad msg or missing FROM header

by Laurent Schweizer

Dear all, I have setup few weeks ago a kamailio 5.0.6, was working correctly till last night where 2 time he stop with a segfault error : Sep 25 23:36:19 ch0012 kamailio[18696]: ERROR: <core> [core/parser/parse_from.c:53]: parse_from_header(): bad msg or missing FROM header Sep 25 23:36:19 ch0012 kernel: kamailio[18696]: segfault at 0 ip 00000000004d7c4f sp 00007fff16135130 error 4 in kamailio[400000+42b000] Sep 25 23:36:19 ch0012 kernel: kamailio[18682]: segfault at 0 ip 00000000004d7c4f sp 00007fff16135130 error 4 in kamailio[400000+42b000] Sep 25 23:36:19 ch0012 kamailio[18696]: ERROR: siptrace [siptrace.c:535]: sip_trace_prepare(): cannot parse FROM header Sep 25 23:36:19 ch0012 kamailio[18682]: ERROR: <core> [core/parser/parse_from.c:53]: parse_from_header(): bad msg or missing FROM header Sep 25 23:36:19 ch0012 kamailio[18682]: ERROR: siptrace [siptrace.c:535]: sip_trace_prepare(): cannot parse FROM header Sep 25 23:36:19 ch0012 abrt-hook-ccpp: Process 18696 (kamailio) of user 0 killed by SIGSEGV - ignoring (repeated crash) Sep 25 23:36:19 ch0012 abrt-hook-ccpp: Process 18682 (kamailio) of user 0 killed by SIGSEGV - dumping core Sep 25 23:36:20 ch0012 abrt-hook-ccpp: Saved core dump of pid 18696 to core.18696 at / (2294079488 bytes) Sep 25 23:36:20 ch0012 kamailio[18759]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 31 Sep 25 23:36:20 ch0012 kamailio[18679]: ALERT: <core> [main.c:743]: handle_sigs(): child process 18696 exited by a signal 11 Sep 25 23:36:20 ch0012 kamailio[18679]: ALERT: <core> [main.c:746]: handle_sigs(): core was generated Sep 25 23:36:20 ch0012 kamailio[18679]: INFO: <core> [main.c:768]: handle_sigs(): terminating due to SIGCHLD Sep 25 23:36:20 ch0012 kamailio[18759]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18754]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18758]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18757]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18753]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18752]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18756]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18751]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18746]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18747]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Sep 25 23:36:20 ch0012 kamailio[18750]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received I have exported from the core file some info (file is attached), any idea ? BR Laurent

6 years, 4 months

Dispatcher Questions

by Duarte Rocha

Greetings, I have some questions about Dispatcher0s modules general behaviours. Can Dispatcher use two tables to read values from? If I can't use two tables, is it possible to read them from a Mysql View? I want to be able to have a Gateway belonging to more than one Gateway Set. By doing so, in the table, the gateway will be repeated but with different groups. How will the probing work in this scenario? Will the Gateway be probed multiple times? Thanks for your help. Cheers

6 years, 4 months

TM Module timing question

by Igor Olhovskiy

Hi! A bit lost in timers for TM module Idea is following I want to have dial timeout for 30 seconds, but only if I received 100 Trying in reply to INVITE. If no 100 Trying is received - I want timeout to be like 2 seconds. 100 Trying is indicator for me, that other side is alive. As I got, fr_timer and fr_inv_timer is not what I’m looking for. Regards, Igor

6 years, 4 months

htable event routes behavior

by Володимир Іванець

Hello all, I have following configuration: 1. Htable which loads from MySQL DB and has autoexpire setting. *modparam("htable", "htable", "tl_connect_users=>size=4;autoexpire=120;dbtable=some_htable")* 2. Regular *route[SOME_ROUTE]* with sole logic. 3. *event_route[htable:mod-init]* 4. *event_route[htable:expired: some_htable]* I use while loop in *event_route[htable:mod-init]* to extract stored values from htable, assign them to *$var(some_variable)* and call *SOME_ROUTE* to perform some action for all of them on Kamailio start up. *SOME_ROUTE* has *$sht(some_htable =>$var(some_variable)) = "enabled"* line to add expired value back to the htable. The pboblem is when* event_route[htable:expired: some_htable]* triggers *SOME_ROUTE*. Values are not being added to htable. Hovewer if I will try to manipulate values for key_name or key_value by adding some character new item will be insert to the htable. Does anybody know if behavior is correct when exactly same value can not be inserted back to htable on it's expired event? Thanks a lot!

6 years, 4 months

← Newer
1
2
3
4
5
6
7
8
...
13
Older →

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 September 2018