Dear list
Im quite new to Kamailio and i found something while trying to see the
failover behaviour in Kamailio. I have a kamailio v4.3.5 load balancing two
Asterisk boxes.
This happens just when i stop one of the asterisk and make a call that is
being load balanced to the same asterisk box that i stopped before, when
trying to go to failure_route and dispatch it to the other box then
Kamailio just crashes. I have debug=4 in the config file and it really
doesnt say much about the error. This is the relative logging i could found:
*Jul 18 16:30:13 kam2 /usr/sbin/kamailio[69548]: INFO: <script>: UBICAR:
Forwarding non-registrar requests to AsteriskJul 18 16:30:13 kam2
/usr/sbin/kamailio[69548]: INFO: <script>: UBICAR: Dispatching to Asterisk
Box sip:10.0.1.201:5060 <http://10.0.1.201:5060>Jul 18 16:30:13 kam2
/usr/sbin/kamailio[69550]: INFO: <script>: UBICAR: requestm=INVITE
reply=<null> SIP packet comes from the Asterisk Box
duid=PBX2;my=pbx2;maxload=10000
callid=4d52095c6f2ed1ab2de2d6c70340a126@10.0.1.201:5060
<http://4d52095c6f2ed1ab2de2d6c70340a126@10.0.1.201:5060>Jul 18 16:30:13
kam2 /usr/sbin/kamailio[69550]: INFO: <script>: UBICAR: requestm=INVITE
reply=<null> SIP packet comes from the Asterisk Box
duid=PBX2;my=pbx2;maxload=10000
callid=4d52095c6f2ed1ab2de2d6c70340a126@10.0.1.201:5060
<http://4d52095c6f2ed1ab2de2d6c70340a126@10.0.1.201:5060>Jul 18 16:30:18
kam2 /usr/sbin/kamailio[69547]: INFO: <script>: UBICAR: setting call load
requesturi=<null> callid=896175650(a)192.168.14.76
<896175650(a)192.168.14.76>Jul 18 16:30:20 kam2 /usr/sbin/kamailio[69550]:
INFO: <script>: UBICAR: delete call load
requesturi=sip:10005@10.0.1.201:5060 <http://sip:10005@10.0.1.201:5060>
callid=896175650(a)192.168.14.76 <896175650(a)192.168.14.76>Jul 18 16:30:38
kam2 /usr/sbin/kamailio[69548]: INFO: <script>: UBICAR: Forwarding
non-registrar requests to AsteriskJul 18 16:30:38 kam2
/usr/sbin/kamailio[69548]: INFO: <script>: UBICAR: Dispatching to Asterisk
Box sip:10.0.1.201:5060 <http://10.0.1.201:5060>Jul 18 16:30:42 kam2
/usr/sbin/kamailio[69559]: ALERT: <script>: UBICAR: Asterisk
sip:10.0.1.201:5060 <http://10.0.1.201:5060> failed to answer, selecting
other one!Jul 18 16:30:42 kam2 /usr/sbin/kamailio[69559]: INFO: <script>:
UBICAR: Dispatching to Asterisk Box sip:10.0.1.200:5060
<http://10.0.1.200:5060>Jul 18 16:30:43 kam2 /usr/sbin/kamailio[69546]:
ALERT: <core> [main.c:728]: handle_sigs(): child process 69559 exited by a
signal 11Jul 18 16:30:43 kam2 /usr/sbin/kamailio[69546]: ALERT: <core>
[main.c:731]: handle_sigs(): core was generatedJul 18 16:30:43 kam2
/usr/sbin/kamailio[69546]: INFO: <core> [main.c:743]: handle_sigs():
terminating due to SIGCHLDJul 18 16:30:43 kam2 /usr/sbin/kamailio[69563]:
INFO: <core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43
kam2 /usr/sbin/kamailio[69562]: INFO: <core> [main.c:798]: sig_usr():
signal 15 receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69561]: INFO:
<core> [main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2
/usr/sbin/kamailio[69558]: INFO: <core> [main.c:798]: sig_usr(): signal 15
receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69557]: INFO: <core>
[main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2
/usr/sbin/kamailio[69556]: INFO: <core> [main.c:798]: sig_usr(): signal 15
receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69555]: INFO: <core>
[main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2
/usr/sbin/kamailio[69554]: INFO: <core> [main.c:798]: sig_usr(): signal 15
receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69553]: INFO: <core>
[main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2
/usr/sbin/kamailio[69552]: INFO: <core> [main.c:798]: sig_usr(): signal 15
receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69551]: INFO: <core>
[main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2
/usr/sbin/kamailio[69548]: INFO: <core> [main.c:798]: sig_usr(): signal 15
receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69547]: INFO: <core>
[main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2
/usr/sbin/kamailio[69549]: INFO: <core> [main.c:798]: sig_usr(): signal 15
receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69550]: INFO: <core>
[main.c:798]: sig_usr(): signal 15 receivedJul 18 16:30:43 kam2
/usr/sbin/kamailio[69560]: INFO: <core> [main.c:798]: sig_usr(): signal 15
receivedJul 18 16:30:43 kam2 /usr/sbin/kamailio[69546]: INFO: <core>
[sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized*
My configuration when applying load balancing and failover is detailed here:
*# Send to Asteriskroute[TOASTERISK] {#!ifdef WITH_LOADBALANCE
xlog("L_INFO","UBICAR: Forwarding non-registrar requests to Asterisk
\n"); if(!ds_select_dst("0", "10")) {
sl_send_reply("500", "Service Unavailable");
xlog("L_ERROR","UBICAR: No destinations available for $rd
\n"); exit; } xlog("L_INFO","UBICAR:
Dispatching to Asterisk Box $du\n"); t_set_fr(0,4000);
t_on_failure("MANAGE_FAILURE"); route(RELAY); exit;#!endif*
*# manage failure routing casesfailure_route[MANAGE_FAILURE]
{ #xlog("L_ALERT","UBICAR: failure requestm=$rm requesturi=$ru
callid=$ci\n"); if (t_is_canceled()) { exit; }#!ifdef
WITH_LOADBALANCE xlog("L_ALERT","UBICAR: Asterisk $du failed to
answer, selecting other one!"); # next DST - only for 500 reply or
local timeout (set by t_set_fr()) if (t_check_status("500") ||
t_branch_timeout() || !t_branch_replied()) { #we mark
the destination Inactive and Probing
ds_mark_dst("ip"); #select the new
destination if(ds_next_dst())
{ t_set_fr(0,4000);
t_on_failure("MANAGE_FAILURE");
xlog("L_INFO","UBICAR: Dispatching to Asterisk Box
$du\n"); route(RELAY);
exit; }else{ #last available node
failed to reply, no other destinations available
send_reply("404", "No destination");
exit; }#!endif }}*
It may be a bug in that Kamailio version because i used Kamailio v4.2
before and i didnt have that inconvenient, still i had to upgrade to v4.3
because i needed the default_socket modparam that wasnt implemented in
Kamailio v4.2
Any hint about this issue would be appreciate it
Best Regards
Alejandro
Hello,
Are there any recommended modules for managing concurrent ports for different endpoints/customers/accounts/etc?
I believe the dialog and dialog_ng modules do exactly this, but how is the performance of these modules under high loads?
What is the release time of the ports?
Are there perhaps other modules?
Regards,
Grant
I have some problem with SSL+rtpproxy, kamailio successfully decodes SIP,
rtpproxy decodes SRTP frames, all is going to freeswitch unencrypted. FS
transfers the call back, the call is going unencrypted though kamailio,
kamailio encodes to SSL, but rtpproxy DOESN'T encodes RTP frames to SRTP.
Hence, endpoint SIP equipment rejects the call with 488 Not Acceptable Here
Scenario
1. Endpoint device -> SRTP -> kamailio -> RTP -> freeswitch
2. Freeswitch calls back
3. freeswitch -> RTP -> kamailio -> PROBLEM (SIP[TLS] + RTP (but not SRTP))
-> Endpoint device
4. Endpoint device -> 488 Not Acceptable Here -> Kamailio
Could somebody point me what's wrong here?
Thanks!
Hi,
Is it possible to check wether the trace_on for siptrace module is on or
off from within the config script, e.g inside routing logic,
thannks in advance
-Anand
Hi,
I don't really know if I'm writing to the right list, sorry if I don't. Has
someone been using crocodile-msrp library? I need to develop a webchat app
with Kamailio together and I found Crocodile, but I see it hasn't
documentation neither guides to developers. I also realize it hasn't active
community, last commit done to crocodile-msrp library by its developers was
2013. I need some information to know if I should use it or not.
Thank you and best regards,
Marcelo
Hello All,
We have a Kamailio proxy (P1) and a custom client (A).
Calls are working reliably with A communicating directly with P1. When A sends INVITE to P1, in some cases, we insert a custom header ‘X-Routing’ in the reply.
Now, testing with a new, additional proxy (P2) between these two: A -> P2 -> P1
A sends INVITE via P2 to P1, P1 replies include X-Routing header field (confirmed by logging message buffer received from P1 by P2).
However, the reply relayed from P2 to A does not contain the custom header. P2’s reply_route block only contains logging code and I’ve checked for calls to remove_hf.
I can’t find documentation or code to explain why the header is omitted. Is there a module config parameter that I can set to preserve custom headers?
Any suggestions welcome!
Regards,
Dave Wilson.
Hi,
I have installed Kamailio version 4.4.1. Everything works just fine. If
I connect a PCRF via Rx to the P-CSCF, the registration still runs
through as expected but the subsequent SUBSCRIBE is rejected with "403
Forbidden - You must register first with a S-CSCF" error cause or is
simply ignored (see attached wireshark traces).
And, if I disconnect Rx and restart the P-CSCF, the "forbidden" problem
still persists. (But I can work around this by cleaning up the P-CSCF
database.)
Any suggestions how I could get Rx working?
Thanks,
Kristian