Answering my own question, it appears that rtpengine reverses the logic of
rtpproxy with regard
to the media source address. It trusts the "c" ( connection ) address that the
UA puts there. In
this case the UA had learned what its public address was. Rtpengine trusts this
instead using the
so
While configuring my script for rtpengine I got a rather confusing result. The
test involved
a UA tethered to a phone with only IPV4 availble. The test was a call to a UA
registered
with an IPV6 address. The call was answered successfully but there was no
media. A
sniffer at the rtpengine hos
