[OpenSIPS-Users] - INVITE (SDP) includes Originators IP info

Bogdan-Andrei Iancu bogdan at opensips.org
Wed Oct 19 06:20:18 UTC 2022


Hi there,

Actually you do not need the B2B, you can achieve the same kind of 
privacy (at SIP level) with dialog module and topology_hiding module 
together.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Bootcamp 5-16 Dec 2022, online
   https://www.opensips.org/training/OpenSIPS_eBootcamp_2022/

On 10/19/22 1:23 AM, Abdul Basit wrote:
> Nitesh,
>
> You need a B2BUA function 
> <https://www.tutorialspoint.com/session_initiation_protocol/session_initiation_protocol_b2bua.htm> with 
> the help of a topo-hiding module with opensips as Bela shared in his 
> email.
> Also, install the RTP proxy on the same opensips box (not necessary if 
> you need separate signaling and media boxes).
>
> Far end party will not be able to see the A-party information.
> https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2
> <https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2>
>
> I hope this will help.
>
> --
> regards,
>
> abdul basit
>
> On Wed, 19 Oct 2022 at 03:14, Bela H <hobe69 at hotmail.com 
> <mailto:hobe69 at hotmail.com>> wrote:
>
>     Hi Nitesh,
>
>      1. Check the topology hiding function:
>         https://opensips.org/docs/modules/3.2.x/topology_hiding.html
>         <https://opensips.org/docs/modules/3.2.x/topology_hiding.html>
>      2. Use e.g. rtpproxy:
>
>     https://opensips.org/docs/modules/3.2.x/rtpproxy.html#func_rtpproxy_offer
>     <https://opensips.org/docs/modules/3.2.x/rtpproxy.html#func_rtpproxy_offer>
>
>     http://opensips.com.br/wiki/index.php?title=Oopensips_Nat_script_with_RTPPROXY_-_English
>     <http://opensips.com.br/wiki/index.php?title=Oopensips_Nat_script_with_RTPPROXY_-_English>
>
>     https://github.com/sippy/rtpproxy <https://github.com/sippy/rtpproxy>
>
>     I hope these help!
>
>     Cheers,
>
>     Bela
>
>     *From: *Nitesh Divecha <mailto:aviator.nitesh.d at gmail.com>
>     *Sent: *Wednesday, 19 October 2022 04:26
>     *To: *OpenSIPS users mailling list <mailto:users at lists.opensips.org>
>     *Subject: *[OpenSIPS-Users] - INVITE (SDP) includes Originators IP
>     info
>
>     Hello All,
>
>     This is my first OpenSIPS project so I'm a newbie!
>
>     After going back and forth with "uac_replace_from()", I was
>     successfully able to make a call from my ATA -> OpenSIPS ->
>     Outbound Provider -> CellPhone. All worked fine with two-way audio
>     except few issues:
>
>     1) Outbound Provider was able to see my ATA (Originator's
>     IP/User-Agent/etc) in SIP INVITE (SDP) which kinda raised some
>     eyebrows with Outbound provider. How can I block or strip all the
>     Originator's contact info in SIP INVITE (SDP) and only send
>     OpenSIPS info? Meaning I want to protect my Originators and don't
>     want to show anything to the Outbound Provider. Outbound providers
>     should only communicate to the OpenSIPS server.
>
>     2) When the call was up I failed to capture any media/RTP on the
>     OpenSIPS server. I want to involve OpenSIPS in media/RTP between
>     ATA and outbound providers. How can I force media/RTP to pass-thru
>     OpenSIPS IP so I'm not exposing Originator's IP.
>
>     Any insights will be highly appreciated.
>
>     Cheers,
>
>     Nitesh
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>     <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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20221019/b65c38ac/attachment.html>


More information about the Users mailing list