I'm involved in setting up a Kamailio instance and was hoping to make use of the auth_ephemeral module for authentication. But the module documentation doesn't quite make clear how exactly the module is to be employed or the web service set up. Does anyone have a working example?
Regards,
Hemanshu Vadehra
hemanshu.v(a)directi.com
Hi all,
I'm switching my development environment from Linux to Mac.
Is there any tutorial on how to setup Kamailio on this OS? It may be an
Unix flavor, but it's still quite different from Linux :).
Thanks,
--
Carlos
http://caruizdiaz.comhttp://ngvoice.com
+52 55 3048 3303
Hello,
I’m attempting to deploy a homer sip capture server on SPARC and I’m seeing some strange date related errors:
ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Incorrect datetime value: '2052-06-12 16:21:06' for column 'date' at row 1 (1292)
Is there some sore of endianness issue?
Thanks for any assistance!
Regards,
Spencer
Hi
Im trying to remove my Asterisk s= line on SDP but when doing:
sdp_remove_line_by_prefix("s=Asterisk");
Nothing happens.
Loaded sdpops.so module as well.
Is there any additional needed?
BR
Hi fellow kamailio users,
I'm playing actually with t_on_branch_failure, in a simultaneous forking
scenario ( lookup("location") returns multiple contacts ).
Any idea on how to get those "on_branch_failure" working ?
Thanks in Advance !
* Test by putting failure_exec_mode:
- at 1 => no branch failure being called, never.
- at 0 => t_relay does not fail if a single branch answers the
transaction, even if all other branches are failing.
* Test by moving the t_on_branch_failure("manage_branch_failure"); line
before or after the lookup("location") or on a _on_branch route to set
it per branch.
- The on_route branch are executed, but never the failure one.
- tried also with failure_exec_mode = 0 or 1.
* Using set_forward_no_connect, I can see in the logs a "Sending to
branch X failed" but no failure route being executed. Without it,
nothing in the logs indicating that the branch has timeout.
* Config extract:
# auto-discard branches from previous serial forking leg
modparam("tm", "failure_reply_mode", 3) # 3 by default
# default retransmission timeout: 30sec
modparam("tm", "fr_timer", 30000)
# default invite retransmission timeout after 1xx: 120sec
modparam("tm", "fr_inv_timer", 120000)
modparam("tm", "reparse_on_dns_failover", 0)
# 1: Allow branches to have a per branch failure route
# 0: t_relay should fail if a branch fail
modparam("tm", "failure_exec_mode", 1)
# Allow locally generated 408 to be forgotten in case a reply is received.
#modparam("tm", "faked_reply_prio", 2000)
# USER location service
route[LOCATION] {
t_on_branch_failure("manage_branch_failure");
if (!lookup("location")) {
....
}
# Let's get back after 2.5s if no 100/Trying received.
t_set_fr(0, 2500);
# set_forward_no_connect();
#t_on_branch("SET_BRANCH_FAILURE");
route(RELAY);
exit;
}
route[RELAY] {
....
if (!t_relay()) {
xlog("L_WARN","$rm|$ci|$fu|$tu|RELAY_FAILED");
sl_reply_error();
}
exit();
}
# set failure route per branch
branch_route[SET_BRANCH_FAILURE] {
xlog("L_WARN","$rm|$ci|$fu|$tu|SETTING_BrANCH_FAILURE_ROUTE");
t_on_branch_failure("manage_branch_failure");
}
# manage failure routing cases per branch
event_route[tm:branch-failure:manage_branch_failure] {
xlog("L_WARN","$rm|$ci|$fu|$tu[$avp(dest_to)]|MANAGE_BRANCH_FAILURE");
}
Hi all,
I am having some issues using get_redirects() from the UAC_Redirect module
in conjunction with t_next_contacts from the TM Module. I've searched
Google and the list but the only references I can find are several years
old.
I am attempting to configure Kamailio so it if receives a 3XX redirect
message, it will store the Contacts it contains, and attempt them in 'Q'
parameter order.
So for the Contact below-
Contact: <sip:10.0.97.21:5060>;q=0.2,<sip:5.29.13.139:5060>;q=0.5.
I want Kamailio to try 5.29.13.139, and if that times out, or is rejected
in someway, try 10.0.97.21.
If I use t_relay rather than t_next_contacts, kamailio branches the calls
and relays them in parallel regardless of Q value - this is not what I want.
If I use t_next_contacts, it attempts 5.29.13.139 which is rejected with a
401, but it doesn't attempt 5.29.13.139 and responds "408", "Request
Timeout MH 2"
Relevant script section is below, has anyone been able to get this working?
failure_route[302] {
if (t_check_status("302")){
xlog("L_ALERT","Failure Route: 302\n$mb");
get_redirects("*");
if (!t_load_contacts()) {
send_reply("500", "Server Internal Error - Cannot load contacts
MH");
exit;
};
if (!t_next_contacts()) {
t_reply("408", "Request Timeout MH");
} else {
t_on_failure("302");
t_relay();
exit;
};
} else if (t_check_status("[456][0-9][0-9]")){
if (!t_next_contacts()) {
t_reply("408", "Request Timeout MH 2");
} else {
t_on_failure("302");
t_relay();
exit;
}
}
}
Thanks,
Matthew
Hi All,
I'd like to use the Dispatcher Module along with 30X redirects, to monitor
gateway availability with SIP options and to provide redundancy / fail
over.
Some sources online suggest it's as easy as -
if ( method=="INVITE" ) {
dst_select_domain("1","4");
sl_send_reply("300","Redirect");
exit;
}
However when the 30X reply is sent, it contains no contact header.
Please could someone advise if it's possible to use the Dispatcher module
with 302 redirects, and what they syntax is?
Thanks,
Matthew
Hello everyone,
I'm trying to use BLF with the config here (except with SQlite):
http://kb.asipto.com/kamailio:presence:k43-blf
BLF seems to work perfectly except after the call is ended I get
"sqlite commit failed: database is locked" error messages as seen
here:
http://pastebin.com/xVijj98H
BLF is then broken at this point.
kamailio -v
version: kamailio 4.3.5 (x86_64/linux) 950657
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS,
USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM,
SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX,
FAST_LOCK-ADAPTIVE_WAIT, USE_PTHREAD_MUTEX, 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.
id: 950657
compiled on 01:33:01 Mar 29 2016 with x86_64-openwrt-linux-gnu-gcc 4.8.3
Has anyone ever seen this before?
Thanks!
--
Kristian Kielhofner
Happy New Year!
I've just upgraded my Kamailio (build from master@c7e411e) instance to Fedora
23 from Fedora 22. I've built the packages specifically for Fedora 23 with
the following current sources:
openssl-1.0.2e-3.fc23.x86_64
openssl-libs-1.0.2e-3.fc23.x86_64
openssl version reports...
OpenSSL 1.0.2e-fips 3 Dec 2015
Even so, the following error occurs. It seems like Kamailio having trouble
detecting that I'm using running with the same version that I have installed,
and the same version that I have compiled against.
tls [tls_init.c:557]: init_tls_h(): ERROR: tls: init_tls_h: installed openssl
library version is too different from the library the Kamailio tls module was
compiled with: installed "OpenSSL 1.0.0-fips 29 Mar 2010" (0x10000003),
compiled "OpenSSL 1.0.2d-fips 9 Jul 2015" (0x1000204f).
Please make sure a
compatible version is used (tls_force_run in kamailio.cfg will override this
check)
CRITICAL: <core> [main.c:2558]: main(): could not initialize tls, exiting...
Any pointers? -A
--
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
