Hi,
I'm trying to implement a "callquota" based on destination domains.
The idea is following:
every destation domain has a limit of, say 50 calls.
As the sip clients are registered with the "destination domains", i've extracted
the domain using "$fd" because it results as same value as destination domain.
Problem is, i wanted to have separate quota for each domains. But it seems,
that the quota is reached "as total" not as per domain basis.
Another thing is, the number of calls reported by it is also unusually
large than
actual calls.
This is implemenated as bellow:
#!ifdef WITH_CALL_LIMIT
modparam("dialog","enable_stats",1)
modparam("dialog","dlg_flag", DLG_FLAG)
modparam("dialog","hash_size", 4096)
modparam("dialog", "profiles_with_value","callquota")
modparam("dialog", "default_timeout", 300)
modparam("dialog", "dlg_match_mode", 2)
modparam("dialog", "detect_spirals", 1)
modparam("dialog", "db_mode", 0)
#!endif
#!ifdef WITH_CALL_LIMIT
if (is_method("INVITE")) {
dlg_manage();
$var(100) = 0;
get_profile_size("callquota", "$fd", "$var(100)");
if ($var(100) >= 50 ) {
xdbg("DEBUG: Simultaneous calls limit reached");
sl_send_reply("503","Simultaneous calls
limit reached");
exit;
}
set_dlg_profile("callquota","$fd");
if (get_profile_size("callquota","$fd", "$var(100)")) {
xdbg("DEBUG: there are $var(100) total calls
for $fd");
}
}
#!endif
Thanks in advance.
--
-aft
Greetings.
I try to make iOS voip application with presence information.
iOS does not let too frequent network updates from server side when
runs in background mode.
So I cannot rely on plain PUBLISH / SUBSCRIBE scheme - it leads to
restart of application by iOS in many cases.
Please see this post for details:
https://devforums.apple.com/message/565667#565667
The question.
Can Kamailio provide way to reduce the number of NOTIFYs?
I see it as
1) iOS application creates & uploads RLS via XCAP
2) iOS application asks server about changes in presence information
once per 10 minutes or when application goes to foreground state. The
best way is to receive single batch'd NOTIFY answer for all watched
peers.
Is it possible to implement with kamailio?
Thank you :)
Hi,
On a Gentoo Linux system I'm getting the following compile-time warnings (kamailio-3.3.1 ebuild):
* python_msgobj.c:529:5: warning: dereferencing type-punned pointer will break strict-aliasing rules
* ld_con.c:241:4: warning: implicit declaration of function 'ldap_simple_bind_s'
* perl.c:340:2: warning: null argument where non-null required (argument 2)
* perl.c:340:2: warning: null argument where non-null required (argument 1)
Hopefully I can just ignore these messages.
Thanks,
Vieri
is Homer Capture Agent 4 hep protocol incompatible with Kamalio 3.3
sipcapture module? in captagent.xml i set core_hep.conf version to 2,
but looks like kamailio is not able to parse the messages:
Oct 5 12:40:18 siika sip-proxy[6779]: INFO: <core> [parser/parse_fline.c:145]: ERROR:parse_first_line: method not followed by SP
Oct 5 12:40:18 siika sip-proxy[6779]: INFO: <core> [parser/parse_fline.c:242]: ERROR:parse_first_line: bad message
Oct 5 12:40:18 siika sip-proxy[6779]: ERROR: <core> [parser/msg_parser.c:705]: ERROR: parse_msg: message=<#002#020#002#006#023ij��bg#012�bg#012#002�nP#037#035#010>
Oct 5 12:40:18 siika sip-proxy[6779]: ERROR: <core> [receive.c:146]: ERROR: receive_msg: parse_msg failed
in kamailio config i have
modparam("sipcapture", "capture_on", 1)
modparam("sipcapture", "hep_capture_on", 1)
-- juha
Hi,
I have Kamailio 3.3.1 working fine with TLS 1.0, running on CentOS 6.3
However, now I want to use some ECDHE ciphersuites, for instance: ECDHE-ECDSA-AES128-SHA
I have built an appropriate OpenSSL (1.0.0j) in CentOS to support this, and have generated the appropriate certs:
openssl ecparam -out ca-privkey.pem -name secp256r1 -genkey -outform pem
openssl req -x509 -new -key ca-privkey.pem -out ca_cert.pem -outform PEM -days 3650
openssl ecparam -out privkey.pem -name secp256r1 -genkey -outform pem
openssl req -new -nodes -key privkey.pem -outform pem -out cert_req.pem
openssl ca -keyfile ca-privkey.pem -cert ca_cert.pem -in cert_req.pem -out cert.pem
However, when I try to connect from my phone I am always getting:
Oct 3 20:27:54 /usr/sbin/kamailio[2905]: ERROR: tls [tls_server.c:1190]: TLS accept:error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher
Oct 3 20:27:54 /usr/sbin/kamailio[2905]: ERROR: <core> [tcp_read.c:1127]: ERROR: tcp_read_req: error reading
If I use the OpenSSL s_server test-tool, I can connect from my phone just fine with these certs:
openssl s_server -accept 8888 -cert cert.pem -key key.pem -pass stdin -CAfile calist.pem -cipher ECDHE-ECDSA-AES128-SHA
Does Kamailio support ECDHE ciphersuites?
If so, what am I doing wrong?
Thanks!
AJ
Hi!
I am a student at Oslo and Akershus University college of applied sciences.
I'm working on a project where I am supposed to setup a kamailio server.
Up until now I have been able to install kamailio and add a user.
When I use a sip-client I am able to register and authenticate this user.
And I am able to make calls between different users, as long as they
both are registered on the same server.
But when I try to make a call between users that are registered on
different servers/proxies I fail to establish the call.
When I look at the sip-messages in wireshark, I see that there is a
message "407 proxy authentication required".
I thought that enabling "multidomain" in kamailio.cfg would fix this
problem, but it doesn't.
What I have written in the kamailio.cfg-file is:
#!define WITH_MYSQL
#!define WITH_AUTH
#!define WITH_USRLOCDB
#!define WITH_MULTIDOMAIN
#!define WITH_ALIASDB
#!define WITH_DEBUG
yours
Jostein Aardal
Oslo and Akershus University College of Applied Sciences
Hello All,
I am trying to use Kamailio 3.3 configured as a presence server and
rls server with integrated XCAP.
I am trying to test the presence and rls functionality with clients
such as Jitsi (doesn't seem to support rls and doesn't let me specify
presence rules per contact) and Boghe (doesn't seem to be behaving as
expected!). Anyone recommend other clients that work for the
functionality I described above.
Thanks,
Sangeeta
--
Sangeeta Shah
Dears,
Am able to route call using LCR module from anywhere. I need to use certain
option in the lcr tables in order to specify the ip of which calls is
generated.
I suppose that the From_uri column in LCR module meets my requirement, yet
am not able to make it work and confused after reading several docs.
My question is in what form should the from_uri column be? Is the ip
enough?
Are the Load params used below missing?
modparam("lcr", "db_url","mysql://openser:openserrw@localhost/openser")
modparam("lcr","lcr_gw_table","lcr_gw")
modparam("lcr","from_uri_column","from_uri")
modparam("lcr","priority_column","priority")
modparam("lcr","gw_uri_avp", "$avp(i:709)")
modparam("lcr","ruri_user_avp", "$avp(i:500)")
modparam("lcr", "flags_avp", "$avp(i:712)")
modparam("lcr","lcr_id_avp","$avp(s:lcr_id_avp)")
What should I change in the routing script to consider the from_uri?
if (!load_gws("1")) {
sl_send_reply("503", "Unable To lOad GatEwAyS");
exit;}
if(!next_gw()){
sl_send_reply("503", "Unable To fInD a gateWaY");
exit;}
Thanks in advance,
F Chahrour
after adding a few module params
modparam("sipcapture", "db_url", "MYSQL_SIP_PROXY_USAGE_URL")
modparam("sipcapture", "table_name", "sip_capture")
modparam("sipcapture", "hep_capture_on", 1)
modparam("sipcapture", "capture_node", "EXTERNAL_HOSTNAME")
i restarted my sip proxy and started to get these kind of errors to
syslog:
Oct 4 18:09:02 siika /usr/sbin/sip-proxy[22914]: ERROR: sipcapture [sipcapture.c:733]: ERROR: sipcapture:hep_msg_received: unsupported family [71]
why they appear and how to turn them off?
-- juha
