Hello Aqs,
Yes, that was my problem. I didn't need fix_nated_sdp.
Thanks,
Ali
On Fri, Feb 26, 2016 at 4:23 PM, Aqs Younas wrote:
> Calling fix_nated_sdp() and rtpproxy_offer() after one another does not
> make sense since both do same things in some cases. Make sure you have just
> one in rou
Hello Alex,
Good to hear from you.
Yes, I did have fix_nated sdp and that was causing conflict. Copy and
paste issues:)
Thanks,
Ali
On Fri, Feb 26, 2016 at 3:39 PM, Alex Balashov
wrote:
> Ali,
>
> Is there any danger that you are calling rtpproxy_offer() twice, or using
> rtpproxy_offer() i
Calling fix_nated_sdp() and rtpproxy_offer() after one another does not
make sense since both do same things in some cases. Make sure you have just
one in route.
On 27-Feb-2016 1:39 am, "Alex Balashov" wrote:
> Ali,
>
> Is there any danger that you are calling rtpproxy_offer() twice, or using
> r
Ali,
Is there any danger that you are calling rtpproxy_offer() twice, or
using rtpproxy_offer() in combination with fix_nated_sdp()[1]?
-- Alex
[1] http://www.opensips.org/html/docs/modules/2.1.x/nathelper.html#id293899
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center
Hi,
This generally happens when rtpproxy function is called twice. So are you
sure such calls have a scenario different than others?
On 27 Feb 2016 1:31 am, "Ali Pey" wrote:
> Hello,
>
> Sometime with certain clients the connection IP in the SDP in the Invite
> message get's messed up (corrupted
Hello,
Sometime with certain clients the connection IP in the SDP in the Invite
message get's messed up (corrupted) after rtpproxy_offer:
Incoming Invite from public interface:
c=IN IP4 xx.xx.xx.xx
Outgoing Invite from opensips after rtpproxy_offer is:
c=IN IP4 xx.xx.xx.xxyy.yy.yy.yy
Basically
