Hello,
On 2/22/12 8:38 AM, Uri Shacked wrote:
Hi,
I need to add a parameter to the contact header. suppose to look like:
Contact:
How do I add the parameters?
Should i concatenate the $ct with the parameters?
Or is there a better way?
$ct is not writtable. You can remove existing header and add
Hi,
I am newly experiencing kamailio 3.2. I have installed kamailio and MySQL
and tried the test call from 1 PC(x-lite) to another PC(x-lite) and ended
successfully.
Now moving further, I have configured dynamic routing module and applied
needed parameters and scripts to finally be able to
Also, with some kernels, it is disabled for non-root users, so might be
better to run as root when trying to reproduce.
Private memory stats are available starting with 3.2, via 'sercmd
pkg.stats'.
For older versions, you would have to walk the private memory with gdb:
http://www.kamailio.org
On 2/22/12 10:26 AM, Sven Knoblich wrote:
Ah, ok. thanks. This explains the behaviour. But it isn't explicit
mentioned in the documentation what /g stands for.
But next time, i will also have a further look at the sources.
But now you can enhance the docs, just commit some more details there
Hello,
On 2/22/12 7:50 PM, Ric Marques wrote:
Daniel -
Thank you for your assistance..
first, here's the sections of my routing where I'm calling
fix_nated_sdp, and subsequent call:
# Routing to foreign domains
route[SIPOUT] {
xlog("-- checking of outb
Hello,
I am not using mediaproxy at all (but nathelper/rtpproxy), neither the
call control module, but making an option (module parameter or function
parameter) for call control to bind to another module like media proxy,
should not be big deal if it is all you are looking for -- I can look
o
First, I am posting about the wrong behavior of CallControl (or most
probably Kamailio modules) which leaves no option. I should be the only one
deciding about how to handle timeouts. If I decide to take some risk, no
module should oblige me to do otherwise.
Mediaproxy detects ONLY RTP timeouts fr
Reda-
> It's clear but not necessary. It can look at radius records fixed by
> mediaproxy on RTP timeout to debit the correct balance as well. And why
> also force it on postpaid calls which it doesn't control at all ?
I don't understand how you plan to tear down Kamailio calls that suffer RTP
t
It's clear but not necessary. It can look at radius records fixed by
mediaproxy on RTP timeout to debit the correct balance as well. And why
also force it on postpaid calls which it doesn't control at all ?
What happens is cost and performance issues for additional calls passing
through my mediapr
Reading from the module docs its clear why it needs to engage media/rtp
proxy to start,stop billing or timer of a call. so what happens when it
engages mediaproxy on unwanted calls !? audio-issues?
On Thu, Feb 23, 2012 at 1:21 PM, Reda Aouad wrote:
> Thanks Sammy. I didn't get any reply yet.
>
>
Usually (on Debian) the core file will be activated in
/etc/default/kamailio and the location of the core file is specified in
/etc/init.d/kamailio.
regards
klaus
On 22.02.2012 23:45, Fabian Borot wrote:
How can I make sure that a core file is created after a situation like this?
Where will
Thanks Sammy. I didn't get any reply yet.
CallControl is an application used with CDRTool for prepaid calls. It
calculates the maximum call duration based on the user's balance. Once the
call's duration limit is reached, it sends BYE to both calling parties,
terminating the call. At the end of a p
12 matches
Mail list logo
