Hi David,
You can refer to the following drafts and RFC's to support UDP keep-alive
mechanism in NAT.
1> draft-ietf-sip-outbound-01.txt - Section 3.5
2> RFC 3489 (STUN)
Regards,
--Vikram.
David Stuart
<[EMAIL PROTECTED]
m> To
Sent by: [email protected]
sip-implementors- cc
[EMAIL PROTECTED]
ia.edu Subject
[Sip-implementors] Question about
NAT/FW and UDP
12/01/2005 05:30
AM
Hello,
I have noticed that some SIP User Agents are sending UDP keep-alive
packets in order to keep the pinhole on the NAT from closing.
But because of the fact that most of these NATs are either port
restricted cone or, in the worst case, symmetric, it means you need to
send the packets to their intended destination (including the port
number).
So, I worry about these packets because I think that maybe the
implementation of the receiving side might not account for packets which
are essentially "garbage" (for instance, a phone might interpret this as
a lost packet and do silence suppression, or a video codec may try to
conceal packet loss etc)..
Therefore I am wondering if any standards (or even best practices) exist
for the sending of such packets.
Dave
--
David Stuart, SIPquest
Email: dave (at) sipquest (dot) com
Phone: 254-8886 x234 Web: http://www.sipquest.com/
Address: 300 - 350 Terry Fox Drive, Kanata Ontario, K2K 2P5
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
