[OpenSIPS-Users] OpenSIPS is behind a NAT, not the UAC. What to do?

[Johan De Clercq]

in the startup route, you should find  your pub ip using curl.
Put that in a var and then use that var in rtpproxy.

2016-07-27 15:07 GMT+02:00 Rodrigo Pimenta Carvalho <pimenta at inatel.br>:

> Dear OpenSIPS-users.
>
>
>
> The function nat_uac_test() (from module NATHELPER) works very well and
> tells me whether a cliente to my OpenSIPS is behind a NAT.
>
>
> But, for my specific network topology, is my OpenSIPS that is behind a
> NAT, from the client perspective. In this case I have to fix the SDP
> content that goes from OpenSIPS to the client, so that the client will be
> able to send its media to a public IP, when communicating to a peer in the
> same network domain of this SIP server.
>
>
> How can I be sure that for a client perspective the OpenSIPS is behind a
> NAT? In another words, is there a way to the OpenSIPS determine if its
> client is in the same network or in a remote network?
>
>
> --------------
>
>
> P.S. I suspect that OpenSIPS should be used in a node with public IP to
> simplify our solution. But our customer asked us to put OpenSIPS in a
> residential device that will be always behind a NAT for some smartphones
> perspective and not behind a NAT for another home devices perspective.
>
>
>
> ---------------
>
>
> Any hint will be very helpful!
>
>
> Best regards.
>
>
>
> RODRIGO PIMENTA CARVALHO
> Inatel Competence Center
> Software
> Ph: +55 35 3471 9200 RAMAL 979
>
> _______________________________________________
> 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/20160727/c06c1143/attachment.htm>