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" <ali...@gmail.com> wrote:
> 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 instead of replacing the external IP, it adds the internal IP to > the end of connection line in the SDP. I'm using opensips version 1.11.5. > It works with most clients but this happens time to time. > > > Has anyone experienced this problem? How can I fix it? > > > Regards, > Ali Pey > > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users