26 Aug
2014
26 Aug
'14
7:47 a.m.
if trust-address flag is not set in rtpengine_offer, "the RTP proxy
ignores address in the SDP and uses source address of the SIP message as
media address which is passed to the RTP proxy".
if there is another, e.g. a loadbalancer, proxy in front of the proxy,
source address of SIP message is not correct media address. it thus
looks to me that a new media-address= flag would be needed, where media
address is taken from if the flag is present.
any comments? it is ok if i try to add media-address= flag?
-- juha
26 Aug
26 Aug
3:43 p.m.
On 26/08/14 12:47 AM, Juha Heinanen wrote:
if trust-address flag is not set in rtpengine_offer,
"the RTP proxy
ignores address in the SDP and uses source address of the SIP message as
media address which is passed to the RTP proxy".
if there is another, e.g. a loadbalancer, proxy in front of the proxy,
source address of SIP message is not correct media address. it thus
looks to me that a new media-address= flag would be needed, where media
address is taken from if the flag is present.
It already exists. It's the replacement for what used to be the second
parameter to the _offer/_answer() etc functions. Did I forget to
document it?
cheers
9:05 p.m.
Richard Fuchs writes:
It already exists. It's the replacement for what
used to be the second
parameter to the _offer/_answer() etc functions. Did I forget to
document it?
my mistake in the name of the missing flag. i wrote the email in too
much hurry.
media-address parameter does exist, but it affects the media address in
sdp body. source-address parameter does not exist and that is what I'm
after:
if trust-address flag is not used, take source address from
source-address flag if it exists, otherwise take source address from sip
request.
-- juha
9:34 p.m.
On 26/08/14 02:05 PM, Juha Heinanen wrote:
Richard Fuchs writes:
Oh, I see. Sure, why not. Keep in mind though that (unless asymmetric
flag is given) rtpengine attempts to learn the source address from
incoming RTP packets, so in many cases this isn't needed.
cheers
It already exists. It's the replacement for
what used to be the second
parameter to the _offer/_answer() etc functions. Did I forget to
document it?
my mistake in the name of the missing flag. i wrote the email in too
much hurry.
media-address parameter does exist, but it affects the media address in
sdp body. source-address parameter does not exist and that is what I'm
after:
if trust-address flag is not used, take source address from
source-address flag if it exists, otherwise take source address from sip
request.
27 Aug
27 Aug
11:10 a.m.
Richard Fuchs writes:
Oh, I see. Sure, why not. Keep in mind though that
(unless asymmetric
flag is given) rtpengine attempts to learn the source address from
incoming RTP packets, so in many cases this isn't needed.
Thanks for the clarification. I did tests and noticed that media got
correctly proxied even when i did not use trust-address flag when it
would have been possible to trust media address in sdp and also when
source address of request didn't belong to caller.
So as you point out, it appears that, at least in common cases,
trust-address flag and the proposed new source-address flag are not
needed.
-- Juha
3743
days inactive
3744
days old
4 comments
2 participants
participants (2)
-
Juha Heinanen -
Richard Fuchs