12 Nov
2007
12 Nov
'07
9:15 a.m.
Hi,
I came accros one Nokia-S60 Guideline regarding SIP setting in the
NAT/Firewall traversal section which say:"It is recommended to use TCP
as the transport instead of UDP since even doubled battery life can be
achieved with a UI always connected to a SIP service".
I need OPenSER users to comment on this since what i know is that UDP is
more reliable transportation.
WBR
lu.
12 Nov
12 Nov
9:41 a.m.
I encountered few problems using Nokia's UDP implementation when there are
NATs around so I would recommend you to use TCP. Maybe recent versions have
solved this issue but you can find older implementations on the field...
Regarding reliability and batery life I would say TCP is more reliable by
itself and you will avoid UDP's retransmissions which can safe some batery
if the server does not respond fast or there's a problem in the link.
hope it helps,
sam
2007/11/12, lu <luzango.mfupe(a)tuune.mobi>bi>:
Hi,
I came accros one Nokia-S60 Guideline regarding SIP setting in the
NAT/Firewall traversal section which say:"It is recommended to use TCP
as the transport instead of UDP since even doubled battery life can be
achieved with a UI always connected to a SIP service".
I need OPenSER users to comment on this since what i know is that UDP is
more reliable transportation.
WBR
lu.
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
10:20 a.m.
I came accros one Nokia-S60 Guideline regarding SIP
setting in the
NAT/Firewall traversal section which say:"It is recommended to use TCP
as the transport instead of UDP since even doubled battery life can be
achieved with a UI always connected to a SIP service".
I cannt comment on the battery life issue, but the problem is with IP
fragmentation. In case a message is fragmented because it exceeds the MTU
size there is a good chance that the fragmented packets cannot traverse
the firewall. This is because the port information is not repeated in
fragmented packets.
regards
Franz
2:43 p.m.
Well -- this kind of surprises me. I would explain that of myself as the
handset guys were worried about UDP timers in firewalls being set more
aggressively, and addressed that by more frequent keep-alives for UDP
which consume more power, that's still guessing though.
-jiri
At 13:20 12/11/2007, franz.edler(a)inode.at wrote:
--
Jiri Kuthan http://iptel.org/~jiri/
I came accros
one Nokia-S60 Guideline regarding SIP setting in the
NAT/Firewall traversal section which say:"It is recommended to use TCP
as the transport instead of UDP since even doubled battery life can be
achieved with a UI always connected to a SIP service".
I cannt comment on the battery life issue, but the problem is with IP
fragmentation. In case a message is fragmented because it exceeds the MTU
size there is a good chance that the fragmented packets cannot traverse
the firewall. This is because the port information is not repeated in
fragmented packets.
regards
Franz
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users 
9:11 p.m.
franz.edler(a)inode.at writes:
I cannt comment on the battery life issue, but the
problem is with IP
fragmentation.
tcp's better battery life may be related to the fact that if the phone
is behind nat, the phone itself will keepthe nat binding open by sending
every 20 MINUTES or so a keepalive message to the proxy. if you use
udp, proxy must nat ping the phone from the proxy once at about 20
SECONDS.
-- juha
13 Nov
13 Nov
5:43 a.m.
Juha Heinanen schrieb:
franz.edler(a)inode.at writes:
Does NAT devices keep TCP bindings open for 20 minutes if there is no
traffic?
regards
klaus
I cannt comment on the battery life issue, but
the problem is with IP
fragmentation.
tcp's better battery life may be related to the fact that if the phone
is behind nat, the phone itself will keepthe nat binding open by sending
every 20 MINUTES or so a keepalive message to the proxy. if you use
udp, proxy must nat ping the phone from the proxy once at about 20
SECONDS.
-- juha
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
6:05 a.m.
Hi,
* Juha Heinanen <jh(a)tutpro.com> [071113 08:51]:
Klaus Darilion writes:
... and there are also some routers and sysadmins without mentioning
names that keep TCP timers to less then 30 seconds before they kill the
tcp connection if it's idle.
- Atle
(who has bad experience with tcp keepalive above 30 seconds...)
Does NAT devices keep TCP bindings open for 20
minutes if there is no
traffic?
yes, most nats have much longer tcp timeouts than udp timeouts.
6155
days inactive
6156
days old
7 comments
7 participants
participants (7)
-
Atle Samuelsen -
franz.edler＠inode.at -
jh＠tutpro.com -
Jiri Kuthan -
Klaus Darilion -
lu -
samuel