[OpenSIPS-Users] RTP Proxy problem

[Răzvan Crainea]

Hi, Wesley!

How exactly have you used the E/I flags? Have you tried to combine them 
rtpproxy("ie") or rtpproxy("ei")? Taking a look in the Rtpproxy code, 
it's kind of awkward how these flags are handled.

Best regards,

Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 12/14/2012 01:59 PM, Wesley Volcov wrote:
> Hey Guys,
>
> Some ideas?
>
> Regards,
>
> Wesley Volcov
>
> On 11 December 2012 11:35, Wesley Volcov <wesleyvolcov at gmail.com 
> <mailto:wesleyvolcov at gmail.com>> wrote:
>
>     Dear all,
>
>     I could fix the rtpproxy problem, it was a compilation problem.
>
>     But now, I'm having a audio problem.
>
>     Let me explain:
>
>     I have a Opensips with 2 IP addres, a public one (200.0.0.1) and a
>     private one (10.0.0.1).
>
>     The orignation endppint is in the private network (IP TEL), the
>     PSTN gateway is in the public network.
>
>     I receive a call from the IP TEL and send it to the gateway.
>
>     In the INVITE that the Opensips sends to the PSTN gateway, I see
>     the Public IP in the CIN parameter, but in the 200 OK that the
>     Opensips sends to the TEL IP I see the public IP to, and call goes
>     to one way audio.
>     The Opensips should send the private IP in the 200OK to the IP TEL.
>
>     RTPPROXY run command: /usr/local/bin/rtpproxy -l 200.0.0.1
>     10.0.0.1 -s udp:127.0.0.1 7890 <tel:127.0.0.1%207890> -F -m 10000
>     -M 20000 -d DBUG
>
>     Opensips:
>     if (is_method("INVITE")){
>                     rtpproxy_offer("","200.0.0.1");
>             }
>
>     onreply_route [ONREPLY] {
>
>             rtpproxy_answer("","10.0.0.1");
>     }
>
>     I've tried some parametes in the rtpproxy like FW, I, E, but I had
>     the same result.
>
>     I'am missing some thing?
>
>     Please, help me guys.
>
>     Thanks a lot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20121214/be1291a2/attachment-0001.htm>