1 Sep
2005
1 Sep
'05
4:29 p.m.
Exactly, but
this is not the UA, it's the NAT allocating the port (you
didn't answer whether you are solving the problem of two UAs behind same
NAT or behind different NATs).
I don't understand your question. I'm tring to solve the more general case as
possible.
Moreover, I'm tring to solve hairpin problems for UAs behind the same NAT
(and only one).
The general case is where you don't make any assumptions about where the UAs
are. If you are only talking about UAs you definitely know are behind the
same NAT, the scenario is different than what I assumed you were talking
about. If you know the UAs are behind the same NAt, why not put SER behind
the same NAT?
Or you can just use fix_nated_register and not do any mangling with SDP at
all (if the UAs don't use STUN and assuming the NAT does not have a SIP
ALG). As long as the private addresses are internally routable, you should
be fine.
All of this without proxing the RTP streams (just a
couple of packets).
?? A couple of packets?
The UA will probably use the same port, but a
reINVITE may even change
IP... The problem is the NAT allocating another port on the public
interface.
But the various kinds of "cone NATs" should allocate always the same port
(for the same internal IP/Port). This is the assumption on which STUN is
based!
Bye.
--
___________________________________________________
__
|- giannici(a)neomedia.it
|ederico Giannici http://www.neomedia.it
___________________________________________________