Hi Jerome,
Jerome Martin wrote:
Hello Ovidiu and Bogdan,
Thanks a lot for both of your answers. I should have be more carefull
with that issue, as I'm afraid I should have solved this myself,
especially because it has already been specifically addressed both here
and in the v1.1 nathelper module.
The thing is I did read about the "c" option in force_rtp_proxy
documentation, I just got confused by session/media description in SDP.
Now that I've just read the RFC2327 (which I already went through, but
not carefully enough), everything is clear as crystal :-)
So, if I have a message for people like me reading this : RTFR(FCs) !!!
(this is sooo much compatible with the Fu****g word than the plain old
RTFM.).
Bogdan wrote:
this is a topic that was debated couple of times. according to the
SDP
RFC, the connection information (c=) can exists both in session
description (s= section ) and in media description (m= section). This
because a session may contain several media description and if the c=
in
media is not specify, the one from session is used.
Now that I've read it, I'm gonna be bitchy about it : ain't the session
description delimited by "v=" and not "s=", according to RFC2327 ? ;-p
yes, that is correct - it is v= and not s= - mea culpa :)
regards,
bogdan
Thanks again,
I was really amazed by such a fast answer (first time I post here).
Best Regards,
Jerome Martin
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
