Hi Daniel,
I re-tested with your latest commit and it works as expected with my
current configuration (with nat_bflag unset in my case).
Thanks!
On Thu, Feb 20, 2014 at 5:15 AM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> I removed the restriction on nat_bflag (in master and 4.1 branches).
>
Hello,
I removed the restriction on nat_bflag (in master and 4.1 branches).
Can anyone test to see if all goes fine even for non-natted contacts?
Cheers,
Daniel
On 20/02/14 01:23, Alex Balashov wrote:
Okay, so maybe someone who knows the usrloc code better can correct me
on this, but I get th
Okay, so maybe someone who knows the usrloc code better can correct me
on this, but I get the impression that the part of the code that ages
the contact out if a keepalive reply has not been received is dependent
on nat_bflag being set, regardless of the value of the 'ping_nated_only'
modparam.
On 02/19/2014 07:14 PM, Alex Balashov wrote:
On 02/19/2014 06:51 PM, Kristian Kielhofner wrote:
if((flags & POWPOW) != POWPOW)
printf("Problem?\n");
sasha@tambourine:~$ ./ns
Problem?
Are there other UL contact flags that could be in use here and breaking
this comparison in g
Hello Kristian,
On 02/19/2014 06:51 PM, Kristian Kielhofner wrote:
It seems that with modparam("nathelper", "ping_nated_only", 0) set my
configuration should work without always also setting nat_bflag (as
that is used in various other places currently).
Seemingly, yes. From nh_timer:
rva
I do, but only when endpoints are actually behind NAT :).
If I set my nat_bflag manually (in all cases) it behaves as expected.
It seems that with modparam("nathelper", "ping_nated_only", 0) set my
configuration should work without always also setting nat_bflag (as
that is used in various other p
I quickly checked the code and the condition is on nat_bflag, do you set
it as well? The config snipped you presented tells about sipping_bflag.
Otherwise I see the last-keepalive is updated. I assume the expire time
from the registration is higher than 180 sec.
If all above are ok in your co
Yes, before and after my client stops responding to OPTIONS. Both
Last-Keepalive and Last-Modified do not change:
Last-Keepalive:: 1392851434
Last-Modified:: 1392851424
On Wed, Feb 19, 2014 at 5:41 PM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> should be ok -- feature is not enabled for db-on
Hello,
should be ok -- feature is not enabled for db-only mode.
If you do:
kamctl ul show
is the Last-Keepalive set to a positive value?
Cheers,
Daniel
On 19/02/14 23:30, Kristian Kielhofner wrote:
Hi Daniel,
modparam("usrloc", "db_mode", 2)
On Wed, Feb 19, 2014 at 5:26 PM, Daniel-Cons
Hi Daniel,
modparam("usrloc", "db_mode", 2)
On Wed, Feb 19, 2014 at 5:26 PM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> quick check -- what is the db_mode for usrloc module?
>
> Cheers,
> Daniel
>
>
> On 19/02/14 23:03, Kristian Kielhofner wrote:
>>
>> Hello All,
>>
>>I'm trying to use k
Hello,
quick check -- what is the db_mode for usrloc module?
Cheers,
Daniel
On 19/02/14 23:03, Kristian Kielhofner wrote:
Hello All,
I'm trying to use keepalive_timeout with 4.1.1 as described here:
http://lists.sip-router.org/pipermail/sr-users/2012-August/074337.html
I believe I've
Hello All,
I'm trying to use keepalive_timeout with 4.1.1 as described here:
http://lists.sip-router.org/pipermail/sr-users/2012-August/074337.html
I believe I've followed these configuration steps and those defined
in the nathelper module.
Here are the relevant portions of my config:
modp
12 matches
Mail list logo
