I wouldn't recommend running RTPProxy on Amazon AWS due to the large data transfer pricing.
We moved out RTP to a flat rate bandwidth provider and it has worked out much better. Sent from my iPhone > On 20 Apr 2015, at 3:30 pm, Hamid Hashmi <[email protected]> wrote: > > > RTPproxy replaces 'o' and 'c' in SDP with private IP in case of > rtpproxy_offer("OCNFWIE") while in case of rtpproxy_offer("OCNFWEI") it gives > an error > > ERROR:rtpproxy:unforce_rtp_proxy_f: no available proxies. > > > UAC ---------------> Amazon Firewall -------------> Opensips/RTPproxy > (AWS.Public.IP.1) > (AWS.Private.IP.1) > > > opensips: > > auto_aliases=no > listen=udp:AWS.Private.IP.1:5060 > advertised_address="AWS.Public.IP.1" > advertised_port=5060 > alias="AWS.Public.IP.1" > port=5060 > > > RTPproxy > > /usr/local/bin/rtpproxy -p /var/run/rtpproxy.pid -u root -F -s > udp:127.0.0.1:22222 -l AWS.Public.IP.1/AWS.Private.IP.1 -m 11000 -M 62000 -n > tcp:127.0.0.1:22222 -i 30 -T 50 -W 50 -2 -d DBUG local0 > > > > My questions are: > > 1. When to use "EI" flag and When to use "IE" flag? > 2. Can RTPproxy listen on one interface in bridge mood? > 3. How to change "200 OK" SDP ? > > > Regards > Hamid R. Hashmi > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
