[SR-Users] rtpengine returns 0.0.0.0 even with sendrecv in offer

[Juha Heinanen]

Richard Fuchs writes:

> I don't see how it would make a difference. If Firefox sends 0.0.0.0 and
> rtpengine replaces it with its own address, then the receiving client
> can send media to rtpengine, but rtpengine would have nowhere to forward
> it to. After the answer, ICE processing may commence and determine an IP
> address, after which I expect Firefox to send an updated offer with the
> address filled in. At this point, media should start to flow no matter what.
> 
> I'm not sure how much of a valid use-case this is, or if it'd be just a
> Firefox-specific workaround, but my all means, give it a try and see if
> it makes a difference.

i found this on jssip mailing list:

  Just a side note; FF34 does offer the value '0.0.0.0' as the media
  connectiom address, and the value 9 as the media port. This way it
  announces the support for ICE Trickle. 

  Media servers not aware of this will take it as a 'hold' request and
  wont send media to the peer.

-- juha