Dear Klaus,<br><br><div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Between Openser and rtpproxy is no media traffic, just the proprietary
<br>rtpproxy protocol which is used by nathelper module to control the rtpproxy.</blockquote><div><br>thank you for the clarification. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
1. Use ngrep to inspect the SIP message:<br> - look if the IP address in the c line in the SDP is replaced with the<br>rtpproxy's IP address and the port number is replaced with the port<br>number allocated by rtpproxy
</blockquote><div><br>Using debug=7 I think I saw in the openser log that the c line was not replaced.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2. use tcpdump/wireshark/.... to verify if there are RTP packets sent to<br>your server. MAybe there is a firewall which blocks RTP packets.</blockquote><div><br>I opened all ports so it shouldn't have been a problem.
<br><br>Very fortunately I started on this trace you suggested. I tried to merge the nathelper.cfg file (shipped with openser as a factory documentation) with my openser.cfg. And voilá, it seems to work smoothly! :-D<br></div>
</div><br>Thank you for your kind help!<br><br>Best regards, Zoltan<br>