Hello Alex,
Thank you for your answer, I still don't have sound but the behaviour is
now different.
Is it possible to configure this behaviour on a call by call basis with
flags on the rtpengine_manage() function? Or in alternative having it
consume the "direction=" attribute on the SDP?
Cheers
Hello Alex,
Thank you for your answer, I still don't have sound but the behaviour is
now different.
Is it possible to configure this behaviour on a call by call basis with
flags on the rtpengine_manage() function? Or in alternative having it
consume the "direction=" attribute on the SDP?
Cheers
Yes, what you are encountering is RTPEngine's "learning" behaviour, where it
waits for a single RTP frame from a (presumably NAT'd) endpoint and latches
onto its source IP:port in order to send RTP (symmetrically) back to it.
Check out the "endpoint learning" section here:
