Hello
you may try to cast $var(y) to int using this transformation:
http://www.kamailio.org/wiki/cookbooks/4.0.x/transformations#sint
Regards
Javi
On 04/09/2013 12:17 AM, julian arsanches wrote:
thanks for all support from the forum before hand.
i am having an issue with my setup, i am tryi
hello. I am tring to SUBSCRIBE for presence status of a user on my kamailio
server using the sipMl5 (over websockets) but kamailio failes. (more
exactly the handle_subscribe failes.)
I was told previusly by peter dunkly that it is not a bug, just a
configuration problem. I am quoting his answer:
thanks for all support from the forum before hand.
i am having an issue with my setup, i am trying to make the dispatcher
dynamic by asigning a value from a variable, that variable is define on my
dispatcher.lst but i am getting an error, if anyone can help thanks.
my config on the relay route
fi
Hello,
We noticed an issue with a bunch of stale entries in the
mysql location table recently - all for the same user. It turns out that if
you install linphone 2.0.2 on an iOS device (other versions/platforms might
also be affected) with the transport mode set to TCP and the '
Andreas Granig writes:
> Do you have use_received=1 from path module enabled on p2? It registers
> a call-back to rr and sets $du accordingly if a received param is found
> in the first (own) Route header.
thanks, use_received=1 in p2 did it.
-- juha
__
Hi,
What was the result of this? I'm seeing what looks like a leak of pkg mem
in kamailio-3.3.4.
On Thu, Nov 8, 2012 at 7:42 AM, Daniel-Constantin Mierla
wrote:
> Hello,
>
>
> On 11/7/12 11:53 AM, Jon Bonilla (Manwe) wrote:
>
>> El Tue, 6 Nov 2012 12:09:31 +0100
>> Jon Bonilla (Manwe) escribió
I'm running kamailio 3.X with the following patch for years, works fine to me
with distributed servers and replication:
diff --git a/modules_k/usrloc/udomain.c b/modules_k/usrloc/udomain.c
index b52bb76..e457cc5 100644
--- a/modules_k/usrloc/udomain.c
+++ b/modules_k/usrloc/udomain.c
@@ -318,6 +3
As far as I can tell (when db_mode=3) the timer function calls
synchronize_all_udomains(), which calls get_act_time() and then
db_timer_udomain() in a loop, and db_timer_udomain() just does a
database delete.
Regards,
Peter
On 08/04/13 10:27, Alex Balashov wrote:
On 04/08/2013 04:58 AM, Pet
Hi,
On 04/08/2013 11:50 AM, Juha Heinanen wrote:
i would expect that loose_route() would set $du to received parameter
value, but it does not, because i get to syslog:
Apr 8 12:44:54 wheezy1 /usr/sbin/sip-proxy[5723]: INFO: Trying to relay to du
<> or ru
how can i tell p2 to set $du to rece
in my test, proxy p2 receives initial request from proxy p1, that has
this kind of R-URI and Route header:
INVITE sip:47089231@192.98.102.10:41073;transport=tcp SIP/2.0.
Route:
route header is result of calling lookup in p1 on record:
AOR:: j...@test.fi
Contact:: sip:47089231@192.98.102.10:410
On 04/08/2013 05:30 AM, Juha Heinanen wrote:
Alex Balashov writes:
In practice, we have found that they seem to get deleted a little before
expiration, and so there is a gap between their being deleted and
re-registration on the part of the UAC.
it is a bug if records are deleted before they
On 04/08/2013 05:30 AM, Juha Heinanen wrote:
Alex Balashov writes:
In practice, we have found that they seem to get deleted a little before
expiration, and so there is a gap between their being deleted and
re-registration on the part of the UAC.
it is a bug if records are deleted before they
Alex Balashov writes:
> In practice, we have found that they seem to get deleted a little before
> expiration, and so there is a gap between their being deleted and
> re-registration on the part of the UAC.
it is a bug if records are deleted before they expire. there should be
a safe margin af
On 04/08/2013 04:58 AM, Peter Dunkley wrote:
Hi,
The timer to delete records only runs if the timer_interval modparam is
> 0.
This means you can have multiple active registrars off the same database
table and use some external process to manage deletion of records (for
example, a stored proce
On 04/08/2013 05:21 AM, Juha Heinanen wrote:
Alex Balashov writes:
The problem is that endpoints register to both registrars simultaneously
in this setup. There is no question that one Kamailio instance
periodically deletes the other's contacts. This has been observed.
in db_mode=3, what d
Alex Balashov writes:
> The problem is that endpoints register to both registrars simultaneously
> in this setup. There is no question that one Kamailio instance
> periodically deletes the other's contacts. This has been observed.
in db_mode=3, what does it matter that a proxy deletes other p
On 04/08/2013 05:01 AM, Juha Heinanen wrote:
have you tried with db_mode=3? i have not noticed problems with it, but
my case be different from yours.
I have, and unfortunately there are still these problems.
The problem is that endpoints register to both registrars simultaneously
in this se
On 04/08/2013 04:58 AM, Peter Dunkley wrote:
This means you can have multiple active registrars off the same database
table and use some external process to manage deletion of records (for
example, a stored procedure triggered from a cron job).
Ah, so! I hadn't thought of that. Good suggesti
Alex Balashov writes:
> The 'location' table is also replicated this way. We know that 'usrloc'
> doesn't work so well with this: one instance of Kamailio will
> periodically delete the other's contacts, even if they have a nonlocal
> SIP domain.
> Is there any db_mode that can be used (other
Hi,
The timer to delete records only runs if the timer_interval modparam is > 0.
This means you can have multiple active registrars off the same database
table and use some external process to manage deletion of records (for
example, a stored procedure triggered from a cron job).
Regards,
P
I know I'm revisiting a problem that has been discussed in multiple
threads from various angles, so I might be rightly accused of laziness
in neglecting to research them all. All the same:
I have proxy1 and proxy2 writing to database A and database B,
respectively. Database A and database B
Daniel-Constantin Mierla writes:
> Perhaps the functions should be moved to corex module and add support
> for all kind of combinations, including pv parameters.
sounds like a good plan to move forward functions to core. in the
meantime, i'll update the wiki page and only document the $du/forwa
Daniel-Constantin Mierla writes:
> After analysis the best solution seems to be to match on ruid for
> database operations, because matching on path will be very inefficient
> (contact or contact+callid should still be quite ok).
makes sense to use ruid for that. since this would again be db
o
Hello,
I expect is the old SER parameter format, where it actually requires
host and port as different parameter:
forward("1.2.3.4", 5060);
The wiki content looks like documenting the openser style of parameter,
but then we got the core from ser for v3.0 and perhaps nobody spotted
the diffe
Hello,
On 4/8/13 10:13 AM, Juha Heinanen wrote:
Juha Heinanen writes:
i'm not sure if it is related, but today i noticed too that there is an
old record in my location table which has expired couple of hours ago.
the record does not show up with ul_dump command, so it has been removed
from mem
i tested kamailio 4.0 xcap server with sipclients and got crash.
should i add a tracker entry?
-- juha
(gdb) where
#0 0x7fa35ab47764 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7fa3547ff9e2 in check_match_header (body=..., etag=0x7fff50162170)
at xcap_server.c:1625
#2 0x
Juha Heinanen writes:
> i'm not sure if it is related, but today i noticed too that there is an
> old record in my location table which has expired couple of hours ago.
> the record does not show up with ul_dump command, so it has been removed
> from memory. usrloc db_mode=1.
after restart of ka
i have seen emails about expired records not removed from database,
but i could not find the thread.
i'm not sure if it is related, but today i noticed too that there is an
old record in my location table which has expired couple of hours ago.
the record does not show up with ul_dump command, so i
28 matches
Mail list logo
