28 Apr
2014
28 Apr
'14
8:41 p.m.
On 28/04/14 04:21 PM, Ovidiu Sas wrote:
I can't remember all the details, but after an ICE negotiation, during the UPDATE that confirms the negotiated parameters, the c line shouldn't be touched (if touched, it breakes the ICE negotiation). Maybe the new rtpproxyengine handles this by default ...
I wasn't aware of this, is there an RFC which specifies this? All the ICE negotiations I've seen so far were done entirely outside of signalling (apart from the initial offers and answers). I believe rtpproxy would also be guilty of this then, as it also always modifies m= and c=.
cheers