On 20/06/14 05:31 AM, Alex Balashov wrote:
Thanks for this clarification, Richard. I really appreciate it.
By "asymmetric flag", which flag do you mean precisely? I assume 'r'?
It would be the "a" flag, however I should mention that I was describing
things from an rtpengine perspective, whic
On 06/08/2014 09:00 AM, Richard Fuchs wrote:
On 06/07/14 12:39, Alex Balashov wrote:
Hello,
I'm invoking mediaproxy-ng with rtpproxy_offer/answer("ow") and am
getting a scenario where:
INVITE is forwarded to signalling gateway xxx.xxx.xxx.xxx, which returns
an SDP answer of yyy.yyy.yyy.yyy:519
On 06/07/14 12:39, Alex Balashov wrote:
> Hello,
>
> I'm invoking mediaproxy-ng with rtpproxy_offer/answer("ow") and am
> getting a scenario where:
>
> INVITE is forwarded to signalling gateway xxx.xxx.xxx.xxx, which returns
> an SDP answer of yyy.yyy.yyy.yyy:51964. rtpproxy is invoked in both
>
I think I might have just answered my own question:
From
http://kamailio.org/docs/modules/4.1.x/modules/rtpproxy-ng.html#rtpproxy-ng.f.rtpproxy_offer:
---
r - flags that IP address in SDP should be trusted. Without this flag,
rtpproxy ignores address in the SDP and uses source address of the
Hello,
I'm invoking mediaproxy-ng with rtpproxy_offer/answer("ow") and am
getting a scenario where:
INVITE is forwarded to signalling gateway xxx.xxx.xxx.xxx, which returns
an SDP answer of yyy.yyy.yyy.yyy:51964. rtpproxy is invoked in both
directions. However, media forwarded from media end
