23 Dec
2004
23 Dec
'04
11:06 p.m.
Hello list.
Does someone knows which are the best or most common timers for :
- REGISTER Expire? How often i send the REGISTER message to SER.
- If i'm behind a NAT and i am sending NOTIFY messages to mantain
the bind open, which is the optimal timer for this NOTIFY messages?
-
in a production enviroment?
Thank in advance.
Ricardo Martinez
23 Dec
23 Dec
11:16 p.m.
New subject: [Serusers] Question about general SIP timers in production enviroments.
Ricardo Martinez wrote:
Hello list.
Does someone knows which are the best or most common timers for :
- REGISTER Expire? How often i send the REGISTER message to SER.
I have no clue, but I guess that should be decided based on the size of
your user base and what type of customers you have ie how often do they
re-register from a new IP etc.
- If i'm behind a NAT and i am sending NOTIFY
messages to mantain
the bind open, which is the optimal timer for this NOTIFY messages?
-
This varies with the NAT implementation and also if you use TCP or UDP
on the UAC/UAS, I guess. TCP usually got a higher timeout value in the
NAT devices than UDP, the devices I have worked with, have used 180
seconds for UDP timeout in the NAT table, so less than that atleast if
you use NAT and ZyNOS based devices.
Pedro
--
With kind regards
Jan Pedro Tumusok - ZyXEL Communications AS
Nils Hansens vei 13 - N-0667 - Norway
Tel (+47)22 80 61 80 - Telefax (+47)22 80 61 81
Did you check http://www.zyxel.no today?
24 Dec
24 Dec
10:48 a.m.
New subject: [Serusers] Question about general SIP timers in productionenviroments.
This is dependent on the type of deployment and your preferences. If you
have a deployment scenario with fixed line replacement, you probably have
users who don't move around a lot. Then 3,600 seconds is a typical number.
Sending NOTIFY as a way to keep the NAT open is something you should
avoid. I don't know who started this, but sending an empty UDP is more than
enough and does not require ser to do any processing of the incoming packet.
Of course, if NOTIFY is used for communicating something, it's a different
thing...
The minimum ping time configurable in UAs is often 20 seconds.
Normally, you could ping every minute or so and everything would be fine.
The problem is that you will not know which UAs that are behind NATs with
low expiry time. Also, if the NAT mapping table starts getting full, the
expiry time will often be reduced.
g-)
Ricardo Martinez wrote:
Hello list.
Does someone knows which are the best or most common timers for :
- REGISTER Expire? How often i send the REGISTER message to SER.
- If i'm behind a NAT and i am sending NOTIFY messages to mantain
the bind open, which is the optimal timer for this NOTIFY messages?
-
in a production enviroment?
Thank in advance.
Ricardo Martinez
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
27 Dec
27 Dec
12:13 p.m.
New subject: [Serusers] Question about general SIP timers in productionenviroments.
At 08:48 AM 12/24/2004, Greger V. Teigre wrote:
This is dependent on the type of deployment and your
preferences. If you have a deployment scenario with fixed line replacement, you probably
have users who don't move around a lot. Then 3,600 seconds is a typical number.
We typically set lower than that -- NATs, rebooted devices and other surprise
cause sometimes for invalid bindings and 10 minutes seems a reasonable compromise
between robustness of bindings and too heavy traffic. There is no computational
justification though -- it is just a value we "decided" some day back ago to be
ok :)
Sending NOTIFY as a way to keep the NAT open is
something you should avoid. I don't know who started this, but sending an empty UDP is
more than enough and does not require ser to do any processing of the incoming packet. Of
course, if NOTIFY is used for communicating something, it's a different thing...
The minimum ping time configurable in UAs is often 20 seconds. Normally, you could ping
every minute or so and everything would be fine. The problem is that you will not know
which UAs that are behind NATs with low expiry time. Also, if the NAT mapping table starts
getting full, the expiry time will often be reduced.
I would tend to leave it at 20 seconds. I think some *BSD NATs have sub-1-minute timing
expiration time.
-jiri
7261
days inactive
7261
days old
3 comments
4 participants
participants (4)
-
Greger V. Teigre -
Jiri Kuthan -
Ricardo Martinez -
ZyXEL - Jan Pedro Tumusok