8 Sep
2004
8 Sep
'04
2:55 p.m.
Yes, I think this solves the problem.
I've done som testing and it seems to work fine.
I should probably check cisco if this is a bug in my sw version.
best regards
hw
-----Original Message-----
From: Jan Janak [mailto:jan@iptel.org]
Sent: Sun 9/5/2004 5:36 PM
To: Helge Waastad
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] NAT and protocol aware firewalls
If you are the fixup functions of the Cisco box then it should obey the
expires interval returned by registrar in 200 OK to REGISTER. If it does
not work then you can either disable the functionality or you can set
modparam("registrar", "max_expires", 1800) in your ser.cfg
Jan.
On 01-09 22:06, Helge Waastad wrote:
Hi,
I just want to dwell around a couple of things.
Several vendors have "application awareness" for instance Cisco has
<fixup protocol sip...>
Hence the ser will not se the client as nat'ed and will not send
nat-ping to the clients.
If the client does not support some kind of keep-alives, I guess you
will loose connectivity with the clients when standard register expiry
is 3600 sec. (off course until the next register message is sent)
The Cisco PIX, for instance, have a standard (however configurable) sip
inactivity timer = 1800sec.
What would actually be the best way of dealing with this?
Best regards,
hw
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers