If rtpproxy is behind NAT, you usually have to instruct Kamailio to
write the public rtpproxy IP address into the SDP, instead of the local
one (which is sent from rtpproxy to kamailio).
e.g: rtpproxy_manage("co","your.public.ip.address");
regards
Klaus
On 20.12.2013 17:07, Benjamin Trent wro
Hugh,
Thank you for the response, however, now neither the callee or the caller
are getting a feed. I am not sure if the nat requires symmetric RTP. If
there is a way to determine that, please let me know.
Summery, even with Hugh's possible solution, this still does not work.
Thank you again,
b
Hey all,
I have kamailio set up behind a nat(port restricted, with firewall rules to
allow sip transactions and allowing rtpproxy packet handling if needed) on
Amazon EC2. I can register and calls complete, however, the Caller(the one
initiating the transaction) receives no rtp media feed. I am ru
Hi Ben,
Some NATs require symmetric RTP, so that source and destination ports
are the same for incoming and outgoing media streams. This can be
configured using the 'w' flag to rtpproxy_manage in the NATDETECT route.
rtpproxy_manage("cow");
Regards,
Hugh
On 20/12/2013 16:13, Benjamin Trent
Hey all,
**I apologize if this is a duplicate, I received a bounce back on my first
email.
I have kamailio set up behind a nat(port restricted, with firewall rules to
allow sip transactions and allowing rtpproxy packet handling if needed) on
Amazon EC2. I can register and calls complete, however,