inline.
Rahul Gulati wrote:
Hi,
I am investigating into how RTP can be addressed through NATs and firewalls.
Some of the solutions mention using bi-directional RTP.
I think perhaps you mean what has been called "symmetric RTP", where one
side sends media to the source IP/port where it received media from the
other side.
These need extensions to SDP, or using STUN/TURN where STUN clients
residing in SIP-end equipment will need to send a request to the STUN
server to get UDP NAT-bindings for RTP.
The usage of STUN is orthogonal to symmetric RTP. If you use symmetric
RTP, and both sides are behind NAT, only one side needs to use STUN.
With regular RTP its both.
I had a few questions:
1) Is it possible to use uni-directional RTP in any of the above approaches?
If you define "uni-directional RTP" as RTP where each side sends RTP to
the IP/port advertised by the other side in SDP, then you can use that
RTP along with stun of course.
2) If yes How?, Are there any sample call flows/drafts which I can refer
for the same?
The current repository of SIP/nat related flows is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-nat-scenarios-00.txt
its a bit out of date, but should prove a good start.
-Jonathan R.
--
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
