[OpenSIPS-Users] Topology hiding - B2B_LOGIC

[Ovidiu Sas]

Please open a bug report and provide the version of opensips:
opensips -V

Also, please provide the platform details for your server (OS and hardware).


Regards,
Ovidiu Sas

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