5 Jan
2009
5 Jan
'09
12:14 a.m.
2009/1/4 Aymeric Moizard <jack(a)atosc.org>rg>:
Yeah, but does some UA implement it? is this technique defined in some
RFC/draft?
So what you mean is that, with "outbound" draft, the UA registers the
public URI (after discovering it using STUN), is it? (I must re-read
the draft XD).
Best regards.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
On Sun, 4 Jan 2009, Iñaki Baz Castillo wrote:
Yes, but there are some workarounds. For example nathelper module in
Kamailio adds a SDP line:
"a=nortpproxy"
when it enables RtpProxy, so if other proxy in the patch tries to add
its own RtpProxy it won't do it due to the presence of that SDP line.
And AFAIK, MediaProxy doesn't suffer of this issue.
* what about case where you have several proxy?
Yes, good point. But it's really difficult an
scenario in which two
users behind the same NAT connect to different proxies.
In this case the media proxy would be enabled even if not necessary.
Not all relay work if several media proxy are used because some RTP
relay wait for RTP data before relaying and RTP is received on the
other relay.... What I really
like is the idea of non-replacing the "Contact" header
in the proxy (described in "outbound" proxy AFAIK).
UA can have correct contact even if not using outbound:
send OPTIONS
check received= and rport= parameter in answer.
send REGISTER with correct contact binding!
easy....