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
On Wed, 1 Sep 2004, Helge Waastad wrote:
Hello,
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?
You can use a different port than 5060 for your SIP proxy. This way ALGs should not modify the packets.
Saludos JesusR.
------------------------------- Jesus Rodriguez VozTelecom Sistemas, S.L. jesusr@voztele.com http://www.voztele.com Tel. 902360305 -------------------------------
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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Helge Waastad -
Jan Janak -
Jesus Rodriguez