Hi,
I am tasked to make use of blacklist module for about 4 to 6 million
numbers. I am thinking of using Cassandra for the purpose but reading
through the documentatiom of module and recent mailing list discussion made
me a bit hesitant.
I am looking for advise on this whether this is going to perform as
expected or is not even going to work with the BlackListing module !
I am using Cassandra 33x and Kamailio 4.4 over Ubuntu 14.04.
Looking for suggestions here.
Regards,
Sammy
Hi,
I'm running 4.4.0:ea2033 and am seeing a crash when using
route_if_exists() on a nonexistent route:
Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid
-m 512 -M 8 -u evaristesys -g'.
Program terminated with signal 11, Segmentation fault.
#0 0x0000000000456751 in do_action (h=0x7ffcce5bc4c0, a=0xf0f0f0f0,
msg=0x7fba440abc80) at action.c:337
337 switch ((unsigned char)a->type){
gdb) print a
$1 = (struct action *) 0xf0f0f0f0
(gdb) print a->type
Cannot access memory at address 0xf0f0f108
The invocation looks like this:
if(check_route_exists("AUX_RTPENGINE_OFFER_INBOUND"))
route_if_exists("AUX_RTPENGINE_OFFER_INBOUND");
else {
set_rtpengine_set("1");
rtpengine_offer("replace-origin replace-session-connection
ICE=remove");
}
#route[AUX_RTPENGINE_OFFER_INBOUND] {
# xlog("L_INFO", 'action=R-AUX-RTPENGINE-OFFER-INBOUND');
#}
Uncommenting the nonexistent route has another curious effect: script
execution appears to break after route[AUX_RTPENGINE_OFFER_INBOUND]
executes, and nothing further happens.
Changing
route_if_exists("AUX_RTPENGINE_OFFER_INBOUND");
to
route(AUX_RTPENGINE_OFFER_INBOUND);
resolves both issues (the crash and the script execution halting). But,
of course, if the route is commented out - its normal state - then
Kamailio won't start since it won't allow a nonexistent identifier to be
passed to route().
--
Alex Balashov | Principal | Evariste Systems LLC
1447 Peachtree Street NE, Suite 700
Atlanta, GA 30309
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Hello,
I installed Homer with kamailio as capture agent in order to capture sip
packets.
The first test I did was using the default kamailio.cfg config located in
homer-docker directory , where all Register and Invite packets were saved in
the database and I was able to monitor them from web homer.
After that , I tried to enable registration using the save(location)
function in registrar module , yet I'm getting the below error in the log :
2016-05-11T18:48:36.443231+03:00 ubuntu /usr/sbin/kamailio[4759]: ERROR:
<core> [udp_server.c:550]: udp_send():
sendto(sock,0x7f64702b1d98,767,0,192.168.26.3:3806,16): Bad file
descriptor(9)
2016-05-11T18:48:36.443239+03:00 ubuntu /usr/sbin/kamailio[4759]: ERROR: sl
[../../forward.h:201]: msg_send_buffer(): udp_send failed
2016-05-11T18:48:36.443247+03:00 ubuntu /usr/sbin/kamailio[4759]: ERROR:
registrar [reply.c:734]: reg_send_reply(): failed to send 200 OK
Can you please help with resolving this issue , noting that the registration
works good if I remove the routing logic set for sipcapture.
Any hint would be appreciated.
Cheers,
Ali Taher
Hi guys,
i have a kamailio running on the wan (my central kamailio) and i have phones on a private network range 172.20.0.0/16 behind a NAT.
i also run another kamailio locally to collect all sip phones on my network and this one use the DB of the remote central kamailio.
the local kamailio does t_relay_to() the ip of the central kamailio
route {
if (uri==myself) {
if (method=="REGISTER") {
route(2);
exit;
};
route[2] {
rewritehost("public_remote_kamailio");
if(!t_relay_to("udp:public_remote_kamailio:5060")) {
sl_reply_error();
};
exit;
}
the bad thing is once the phones get registered with non-routable ip (like in the attached picture) trying to INVITE them directly by requesting public_kamailio_ip result in non-working situation.
how should I rewrite my dst_domain when registring in a way INVITE triggers to the local kamailio.
My local kamailio runs with the listen udp:private_local_kamailio advertise udp:public_local_kamailio
I try to be explicit but my understanding is not perfect, it would be nice you could give me a hand.
I put my local kamailio.cfg attached.
thx
debian jessie c compiler complains about these in kamailio 4.4:
CC (gcc) [sip-proxy] mem/tlsf_malloc.o
mem/tlsf_malloc.c: In function 'tlsf_malloc_init_pkg_manager':
mem/tlsf_malloc.c:1353:16: warning: assignment from incompatible pointer type
ma.xmalloc = tlsf_malloc;
^
mem/tlsf_malloc.c:1355:16: warning: assignment from incompatible pointer type
ma.xrealloc = tlsf_realloc;
^
mem/tlsf_malloc.c:1358:16: warning: assignment from incompatible pointer type
ma.xavailable = tlsf_available;
^
mem/tlsf_malloc.c: In function 'tlsf_malloc_init_shm_manager':
mem/tlsf_malloc.c:1501:20: warning: assignment from incompatible pointer type
ma.xmalloc_unsafe = tlsf_malloc;
^
it would be highly appreciated to get rid of them.
-- juha
Hello everybody,
I have a kamailio running on debian, and it works well with a little
modification of the kamailio-advanced file.
I would like to have some speed dial short numbers for all local users,
because I used a random generator script and usernames and password are 25
digits (not only numbers) long.
My problem is with the ownership of a every speeddial number.
Example:
SIP accounts: 5001,5002,5003
SIP domain: mydomain.com
add a speeddial number:
kamctl speeddial add 5002(a)mydomain.com 51(a)mydomain.com sip:5001@mydomain.com
I can call from user 5002 to user 5001 typing 51 correctly.
what I would like to do is that sd-id 51(a)mydomain.com could be called from
every user registered at mydomain.com.
I read the module documentation, kamctl help but I'm not able to find an
answer.
Could you please help me?
Thank you in advance
