Hi Benny, I find opensips server modify the c line to server public address, so mismatch. Will pjsips release an official patch for this issue ? It seems a serious problem. BRs, bo On Fri, Sep 23, 2011 at 7:59 PM, Benny Prijono <bennylp at teluu.com> wrote: > On Fri, Sep 23, 2011 at 2:48 PM, Sa?l Ibarra Corretg? > <saul at ag-projects.com> wrote: > >> Yeah, that could be a good idea actually. It'll make the protocol > >> tries harder in finding a connectivity. Rather than just disabling the > >> check, I'm thinking that we could add the default address as one of > >> the remote candidate, so it gets checked as well. > >> > > > > Looks to me that this can only work if both ends implement this > workaround. > > > > Benny, even if you add your own address as a candidate chances are the > server replaced the c line with some relay server IP address, which you > don't know in advance. > > > > I mean if callee receives an INVITE with mismatched c= line, it can > just add this c= address as a new *remote* candidate. Caller doesn't > need to be aware of it, as this will be handled by the triggered check > . > > But you're right, the 200/OK response may be mangled by the server > too, which would upset the caller, so for best results, both agents > need to implement this workaround. > > Benny > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120216/afea465c/attachment.html>
