Re: [SR-Users] rtpengine_offer() with ICE not updating o= and m= IP addresses

2019-04-22 Thread Richard Fuchs
`replace-origin` and `replace-session-connection` are optional for normal operation and are preempted by `ICE=force-relay`. If you want c= and o= (and m=) lines updated, you should use `ICE=force` instead. Cheers On 19/04/2019 05.25, David Dean wrote: Sorry, not sure I understand. The

Re: [SR-Users] rtpengine_offer() with ICE not updating o= and m= IP addresses

2019-04-19 Thread David Dean
Sorry, not sure I understand. The documentation says these options will update c= and m= but in my case they aren't applying and I don't know why. Are you saying c= and m= won't be updated if ICE is being forced?

Re: [SR-Users] rtpengine_offer() with ICE not updating o= and m= IP addresses

2019-04-19 Thread Daniel Tryba
On Fri, Apr 19, 2019 at 08:52:30AM +, David Dean wrote: > I'm using the following rtpengine_offer() to force the use of ICE relay and > also replace o= and m= > ?? ??rtpengine_offer("replace-origin replace-session-connection > ICE=force-relay RTP"); > > The SDP is being updated to include

[SR-Users] rtpengine_offer() with ICE not updating o= and m= IP addresses

2019-04-19 Thread David Dean
I'm using the following rtpengine_offer() to force the use of ICE relay and also replace o= and m=    rtpengine_offer("replace-origin replace-session-connection ICE=force-relay RTP"); The SDP is being updated to include an ICE relay candidate, but the IP addresses in the o= and m= lines are