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 <[email protected]> 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 > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
