Hello,
Reaching out for some assistance with debugging, I am not seeing any xlog messages in my log file. If there is any other info I didn't include that would be helpful please let me know.
Any ideas are appreciated.
Using Kamailio 3.3.2 & Cent OS 6
Rsyslog.conf
--------------------
*.info;mail.none;authpriv.none;cron.none;local0.none /var/log/messages
# Kamailio
local0.* -/var/log/kamailio
Kamailio CFG
------------------------------
#!define WITH_DEBUG
#!ifdef WITH_DEBUG
debug=4
log_stderror=yes
#!else
debug=2
log_stderror=no
#!endif
log_facility=LOG_LOCAL0
loadmodule "xlog.so"
Example xlog-
xlog("L_INFO", "No more gateways \n");
Thanks,
Dan-
Hi,
I have a kamailio proxy server that´s controlling the limit of calls that
clients can make with profile grouping. In other side I also limit clients
call duration base on users credit ( DATABASE) and *timeout *feature .
Before the calls get answer I calculate how much time the client has left
for this call and set the timeout variable. When the time is reached the
proxy sends BYEs two both sides of this call.
I want when the call timeout, as before explain, all other calls in the
same profile end too, because the client has expired his credit.
Is there a way to achieve this?
Regards,
Camila
*Camila Troncoso **|* Ingeniero de Desarrollo
RedVoiss *|*ctroncoso(a)redvoiss.net
Santiago - Chile *|* +56 2 2408535
www.redvoiss.net
Hi,
Kamailio is running fine, but when I try run again by command line without
killing the previous, the kamailio_fifo is removed and functions fifo in
kamctl doen't work anymore. Why when I try running kamailio when already
exist one, it remove de file kamailio_fifo?
I can't find the part of source code that file kamailio_fifo is removed...
Someone knows?
Best Regards
Hi
I'm trying to integrate a (K) front end cluster with an Asterisk back end cluster and Asterisk RT (legacy system)
I've followed the recipe at http://kb.asipto.com/asterisk:realtime:kamailio-3.3.x-asterisk-10.7.0-astdb
(with one minor exception …)
if (from_uri!=myself && uri!=myself)
became
if (uri!=myself)
as with the original line in place we were able to spoof traffic from 3rd party sites and route out onto the PSTN (which I thought was bad) …
anyway …
The problem I'm seeing currently is that when a call is passed down a SIP trunk to an end user on the (K) platform we're losing the DNID
Asterisk delivers the call to SIP/account/DNID
(K) however just tries to deliver the call to DNID@domain which comes back as not found.
I've had limited success hand coding aliases into the alias_db however we're still missing the DNID info and having to scrape it from the SIP To field (with a) limited success and b) fears of a support nightmare if we try and move existing customers onto the new platform). If we were to do this for real I'd either have to modify usrloc or try some perl_exec magic I'm guessing … (although it might be possible with a view on the existing sql database … but I'd rather not have to do that if there is a simpler way)
I confess I'm struggling to get my head around the config and docs and hoped someone could point me in the right direction?
For legacy reasons Asterisk needs to be in the critical path on this particular build … what I'm looking for is a simple recipe and some helpful pointers on how to implement it that will allow enable me to swing (K) into the path between our end user SIP devices and the existing asterisk back ends without losing the ability to deliver hundreds of numbers down a single SIP trunk to a subscriber, and that doesn't require them to make any changes on their end as they will still see the equivalent of SIP:${DNID}@example.com arriving on their PBX
This should be simple, but I'm obviously missing something :)
Help and pointers gratefully received
--
Jon Morby
FidoNet - the internet made simple!
10 - 16 Tiller Road, London, E14 8PX
tel: 0845 004 3050 / fax: 0845 004 3051
As I posted here before, Ubuntu has moved to Upstart as the main
engine to start daemons. As a result, Kamailio will fail to start on boot time because
it starts before MySQL that has already been moved to the new Upstart daemon
starting fashion. I am struggling to get some help from the Ubuntu community
explaining how we can match the previous init script behavior when using
Upstart but I got no success till now. Anyway, I have created an Upstart script
for Kamailio that does most everything that the old script use to do. However,
in this script I am making sure MySQL starts before Kamailio. If you have another SQL engine
you must change the script to match your SQL engine by changing the “start on
started” statement on the script. To use it you have to: A – Create a kamailio.conf file at “/etc/init/” with the
contents of the kamailio.conf script in attach, that is the new Upstart stile
init script. Please notice that I just adapted the existing script, no news… B – Create a symbolic link at /etc/init.d/ pointing to this
kamailio.conf at /etc/init/. C – If you want, you can still have a /etc/default/kamailio
file like it used to be and the script will behave like it used to behave when using
the default file. Hopefully someone more “influent” at the Ubuntu community
may get some help on how to adapt their “start on started” Upstart stanza to
behave like we need for multiple possible SQL engines. Cheers! Moacir
Hi,
I am using app_lua to frequently store some data in htable and avp
entries, using sr.pv.sets. When I read the values using sr.pv.get
immediately after writing them, they seem correct. However, when I read
them later from Lua, I have noticed that sometimes the value is
incorrect or nil. Am I doing something wrong?
The following code uses rtimer to duplicate the problem on startup,
printing the errors to syslog.
Tested on version: kamailio 3.3.1 (i386/linux) 2d0f6f
###############
# kamailio.cfg
###############
loadmodule "pv.so"
loadmodule "xlog.so"
loadmodule "htable.so"
loadmodule "rtimer.so"
loadmodule "app_lua"
modparam("htable", "htable", "status=>size=14;autoexpire=0;")
modparam("rtimer", "timer", "name=ta;interval=10;mode=1")
modparam("rtimer", "exec", "timer=ta;route=LUA_TEST")
# the following path may need to change depending on filesystem setup
modparam("app_lua", "load", "/etc/kamailio/kamailio.lua")
route
{
route(LUA_TEST);
}
route[LUA_TEST] {
$var(lua_test_key) = $(pp{s.toupper}) + "::";
lua_runstring("htable_test([[status=>$var(lua_test_key)]])");
lua_runstring("avp_test([[status=>$var(lua_test_key)]])");
}
----------------
-- kamailio.lua
----------------
-- Test of sr.pv operations in Lua
function htable_test (namekey)
local pvar_prefix = "$sht("..namekey
pvar_test(pvar_prefix)
end
function avp_test ( name )
local pvar_prefix = "$avp("..name
pvar_test(pvar_prefix)
end
function pvar_test ( pvar_prefix )
for value = 10000, 10050 do
local pvar = pvar_prefix..value..")"
--sr.log("info", "Lua attempting to set '"..pvar.."' to value
'"..value.."'")
sr.pv.sets(pvar, value)
end
for value = 10000, 10050 do
-- now we check what was stored
local pvar = pvar_prefix..value..")"
local checkvar = sr.pv.get(pvar)
if ( tostring(checkvar) ~= tostring(value) ) then
sr.err(string.format("CHECK: Lua checking pvar '%s' and got value
'%s' which is NOT '%s'",
tostring(pvar),
tostring(checkvar),
tostring(value)
))
end
end
end
-- end of kamailio.lua
Thanks,
-Andrew
I am looking for a way to integrate Java business logic with Kamailio to
influence routing decisions, add/remove/modify headers, record
accounting-related information, etc. A while back there was a project named
WeSIP, but it doesn't appear to active anymore.
Is anyone doing something like this now, or any ideas or suggestions?
Thanks,
Ron