NDLB-connectile-dysfunction adding expires to Contact header?
It seems that when using NDLB-connectile-dysfunction this adds ";expires=30" to my Contact headers irrespective of what Expiry is requested by the client or is set in the Sofia profile. Is this the intended behaviour ? Ross
Yes it forces the expires down which is perfectly valid. /b On Sep 28, 2010, at 4:30 PM, Ross McKillop wrote:
It seems that when using NDLB-connectile-dysfunction this adds ";expires=30" to my Contact headers irrespective of what Expiry is requested by the client or is set in the Sofia profile.
Is this the intended behaviour ?
Ross
On 28 Sep 2010, at 22:39, Brian West wrote:
Yes it forces the expires down which is perfectly valid.
Ah right, is there any way to override this behaviour on a per user basis ? Thanks for the quick response Regards, Ross
Honestly your device is broken if it can't overcome nat on its own. Your device is responsible for knowing its network topology and registering correctly and using keep alives and such to keep nat mappings open on its own. The connectile-dysfunction option shouldn't be used but for extreme cases of evil evil nat. check for sip-force-expires on the wiki for more info but I think the NDLB option will override that to 30. /b On Sep 28, 2010, at 5:21 PM, Ross McKillop wrote:
On 28 Sep 2010, at 22:39, Brian West wrote:
Yes it forces the expires down which is perfectly valid.
Ah right, is there any way to override this behaviour on a per user basis ?
Thanks for the quick response
Regards, Ross
On 28 Sep 2010, at 23:48, Brian West wrote:
Honestly your device is broken if it can't overcome nat on its own. Your device is responsible for knowing its network topology and registering correctly and using keep alives and such to keep nat mappings open on its own.The connectile-dysfunction option shouldn't be used but for extreme cases of evil evil nat.
I agree entirely - unfortunately as a service provider I don't get to pick the devices my customers use to connect... but try my best to accommodate them, this option made their service work :)
check for sip-force-expires on the wiki for more info but I think the NDLB option will override that to 30.
It does. It doesn't affect me in 99% of cases so it's not a big problem - I just wasn't sure if it was a bug or not. Thanks again for your advice Best Regards, Ross
participants (2)
-
Brian West
-
Ross McKillop