Re: [OpenSIPS-Users] Problem NAT RTPproxy

2012-04-03 Thread Bogdan-Andrei Iancu
The relevant one should be INVITE leaving you opensips - to see if RTPproxy was inserted in the SDP. Regards, Bogdan On 04/02/2012 11:41 PM, magnusadil...@gmail.com wrote: In ngrep traffic check no active rdp-session-id but do not know how to solve # U +3.135110 IP-ASTERISK:5060 -

Re: [OpenSIPS-Users] Problem NAT RTPproxy

2012-04-02 Thread Bogdan-Andrei Iancu
Hi Magnus, attaching cfg files is useless, as no one will debug the script, but we will help you to debug your script. So, for the non-working case (PSTN to SIP) does your script force RTPproxy in INVITE and 200 OK ? Regards, Bogdan On 03/29/2012 01:52 AM, magnusadil...@gmail.com wrote: I

Re: [OpenSIPS-Users] Problem NAT RTPproxy

2012-04-02 Thread magnusadil...@gmail.com
hi, yes, rtpproxy is active in invite 200 onreply_route[3] { if ((isflagset(5) || isbflagset(0)) status =~ "(183)|(2[0-9][0-9])" has_body("application/sdp")) { if (rtpproxy_answer()) { log("L_INFO: rtpproxy_answer NAT"); } } if

Re: [OpenSIPS-Users] Problem NAT RTPproxy

2012-04-02 Thread Bogdan-Andrei Iancu
Well, you know, one is what we want to do , another we actually get. I was rather asking if, making a sip capture (with ngrep) you see in your call the RTPproxy insertion - check it in traffic, not in script. Regards, Bogdan On 04/02/2012 10:05 PM, magnusadil...@gmail.com wrote: hi, yes,

Re: [OpenSIPS-Users] Problem NAT RTPproxy

2012-04-02 Thread magnusadil...@gmail.com
In ngrep traffic check no active rdp-session-id but do not know how to solve # U +3.135110 IP-ASTERISK:5060 - IP_OPENSIPS:5060 INVITE sip:100@ IP_OPENSIPS SIP/2.0 Via: SIP/2.0/UDP IP-ASTERISK:5060;branch=z9hG4bK3e684698;rport Max-Forwards: 70

[OpenSIPS-Users] Problem NAT RTPproxy

2012-03-28 Thread magnusadil...@gmail.com
I have phones (some behind NAT) connecting to Opensips server an Asterisk and an rtpproxy as seen below: rtpproxy started with ps -aux | grep rtpproxy root 15666 0.0 0.0 14472 920 ? Ssl Mar23 0:05 ./rtpproxy -F -l 189.254.2.19 -s udp:* 7890 -d DBUG LOG_LOCAL3