Hi David,
To begine with NAT does not normally differentiate between packets that different at level 4. If the packet is IP packet it is treated in the same way.
I am afraid that the incomming connection (SYN packet) may not be allowed through by all the NATs. Some mechanism needs to be devised to open NAT pinhole for the same.
regards
Rayees
[EMAIL PROTECTED] wrote: -----To begine with NAT does not normally differentiate between packets that different at level 4. If the packet is IP packet it is treated in the same way.
I am afraid that the incomming connection (SYN packet) may not be allowed through by all the NATs. Some mechanism needs to be devised to open NAT pinhole for the same.
regards
Rayees
To: [email protected]
From: David Stuart <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
Date: 12/01/2005 04:30PM
Subject: [Sip-implementors] NAT/FW and incoming TCP medias
Hello,
My impression from reading about STUN, TURN, ICE, etc. is that these
solutions will only work for the media path providing the media is
running over UDP as a transport (please correct me if I'm wrong).
Is there any methodologies out there to deal with the media path over
TCP? How can the NAT/FW be traversed by an incoming TCP connection?
Thanks for any pointers,
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
*****FSS-Private *****" DISCLAIMER: This message is proprietary to Flextronics Software Systems Limited (FSS) 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. FSS 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
