Ok, I tried with the example. It looks like it is outdated as I faced some issues using it:<br><br>1) The "brake" command from the example gives errors.<br><br>2) The rtpproxy dies every time when the onreply_route hits to the rtpproxy_answer:<br>
<br>Feb 10 09:47:41 sms kernel: [7047428.249279] rtpproxy[1934]: segfault
at 0 ip 00000000004053e9 sp 00007fff5b36a060 error 4 in
rtpproxy[400000+e000]<br><br><br>The full log is:<br>Feb 10 09:47:41 sms /root/opensips-1.6.4-tls/opensips[2099]: DBG:core:parse_to: display={011359883327749}, ruri={<a href="mailto:sip%3A359883327749@69.25.128.234">sip:359883327749@69.25.128.234</a>}<br>
Feb 10 09:47:41 sms rtpproxy[2083]: DBUG:handle_command: received command "2099_5 UE <a href="mailto:649d55a2210e1409075b65c50fcef44d@69.25.128.234">649d55a2210e1409075b65c50fcef44d@69.25.128.234</a> 69.25.128.234 5652 as2facc0be;1"<br>
Feb 10 09:47:41 sms rtpproxy[2083]: INFO:handle_command: new session <a href="mailto:649d55a2210e1409075b65c50fcef44d@69.25.128.234">649d55a2210e1409075b65c50fcef44d@69.25.128.234</a>, tag as2facc0be;1 requested, type strong<br>
Feb 10 09:47:41 sms rtpproxy[2083]: INFO:handle_command: new session on a port 35540 created, tag as2facc0be;1<br>Feb 10 09:47:41 sms rtpproxy[2083]: INFO:handle_command: pre-filling caller's address with <a href="http://69.25.128.234:5652">69.25.128.234:5652</a><br>
Feb 10 09:47:41 sms rtpproxy[2083]: DBUG:doreply: sending reply "2099_5 35540 184.106.168.144#012"<br>Feb 10 09:47:41 sms /root/opensips-1.6.4-tls/opensips[2099]: DBG:nathelper:force_rtp_proxy_body: proxy reply: 35540 184.106.168.144#012<br>
...<br>...<br>Feb 10 09:47:41 sms /root/opensips-1.6.4-tls/opensips[2101]: ERROR:nathelper:force_rtp_proxy: Unable to parse body<br>Feb 10 09:47:41 sms /root/opensips-1.6.4-tls/opensips[2101]: [PROXY](INVITE - Trying) <br>
Feb 10 09:47:41 sms kernel: [7047428.249279] rtpproxy[1934]: segfault
at 0 ip 00000000004053e9 sp 00007fff5b36a060 error 4 in
rtpproxy[400000+e000]<br><br><br><br><br>Please advise.<br><br><br><br><br><br><br><div class="gmail_quote">On 10 February 2011 05:50, Ovidiu Sas <span dir="ltr"><<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">In the source tree, there are some examples on how to engage rtpproxy<br>
(using nathelper module):<br>
see "modules/nathelper/examples/alg.cfg".<br>
You need to run opensips in proxy mode (this is the server that will<br>
control the rtpproxy) on one server and on a separate server you need<br>
to tun opensips in b2b mode. You need to separate servers.<br>
Hope this heps.<br>
<br>
Regards,<br>
<font color="#888888">Ovidiu Sas<br>
</font><div><div></div><div class="h5"><br>
On Wed, Feb 9, 2011 at 7:26 PM, Kamen Petrov <<a href="mailto:kamen.petrov@gmail.com">kamen.petrov@gmail.com</a>> wrote:<br>
> Hi Ovidiu,<br>
><br>
> With that scenario, when exactly should I call rtpproxy_offer/answer/engage<br>
> ?<br>
> Is it on the b2b:<br>
> local_route {<br>
> if (is_method("INVITE")) {<br>
> engage_rtp_proxy();<br>
> }<br>
> }<br>
><br>
> Do I need anything else rtp related anywhere ?<br>
> The SIP goes ok with the scenario but the RTP does not and the audio is<br>
> missing.<br>
><br>
> Also, do I need anything special to enable the DTMF relay with the top<br>
> hiding ?<br>
><br>
> Thanks in advance.<br>
> --------------------------------------------<br>
> Kamen Petrov<br>
><br>
><br>
> On 6 February 2011 18:08, Ovidiu Sas <<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>> wrote:<br>
>><br>
>> For now, best thing to do is to separate functionality:<br>
>> - one server doing topology hiding;<br>
>> - one server doing routing, accounting, rtp proxy, etc.<br>
>><br>
>><br>
>> Regards,<br>
>> Ovidiu Sas<br>
>><br>
>> On Sun, Feb 6, 2011 at 9:23 AM, Maciej Bylica <<a href="mailto:mbsip@gazeta.pl">mbsip@gazeta.pl</a>> wrote:<br>
>> > Hi,<br>
>> ><br>
>> >> I am running Opensips 1.6.3 and trying to do topology hiding.<br>
>> >> This is my scenario: Operator_1 ------ > my Opensips ------><br>
>> >> Operator_2<br>
>> >> The goal is not to convey any information of Operator_2 to Operator_1<br>
>> >> like Contact, User-Agent headers and so on and to do rtp proxying.<br>
>> >> For rtp proxying i've installed rtpproxy and it works fine.<br>
>> >> But still the question is about signalization and SDP (o= part)<br>
>> >> I ran through a few posts and found out that the answer is B2B<br>
>> >> functionality here - so B2B_LOGIC.<br>
>> >><br>
>> >> Are there any other wayouts or this is the only way i may follow.<br>
>> ><br>
>> > One more question.<br>
>> > Should I place b2bua separately or could i combine that functionality<br>
>> > with my current Opensips installation?<br>
>> > I am asking because as i understand there might be some problems with<br>
>> > proper call accounting (no radius is used in my case).<br>
>> > If positive then my scenario will look like following:<br>
>> > Operator_1 ------ > my Opensips (billing) -- Opensips b2bua (top<br>
>> > hiding) -- OS RTP Proxy ------> Operator_2.<br>
>> > or it is wrong assumption.<br>
>> ><br>
>> > Thanks,<br>
>> > Maciej.<br>
>> ><br>
>> > _______________________________________________<br>
>> > Users mailing list<br>
>> > <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
>> > <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
>> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>