28 Aug
2012
28 Aug
'12
5:10 a.m.
On Sun, Aug 26, 2012 at 11:10 PM, R W <wingcomm@hotmail.com> wrote:
We fixed this by shutting of the "Passive Session Timer" in the "SIP Miscellaneous." However, I'm curious to know if anyone can explain why this happens on some NATs and not others? Is there s problem with disabling the "Passive Session Timer" on our clients?
I think you'll find it has less to do with NATing and more to do with the SIP user agent (UA) behind the NAT. If it *does* have to do with NATing, then it's likely the SIP 'helpers' getting in the way. Google ALG-based SIP-capable firewalls. Let us know what you find. Oh, and you'll want to check this at the SIP message level to get it figured out. Good luck! Best, Gabe