Hi Rodrigo,
If opensips is behind NAT, you should not use the nat related modules
(as the incoming traffic is correct from nat perspective, as originating
from public network). What you need to do is to be sure the traffic sent
out by opensips has the public IP and not the local private one. For
this, look at :
advertise_address
advertise_port
(http://www.opensips.org/Documentation/Script-CoreParameters-2-1#toc25)
And be sure you have do port fwd of the SIP port from the public address
of the NAT to the private IP of your opensips.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 07.01.2016 13:30, Rodrigo Pimenta Carvalho wrote:
Hi.
I have read the entire OpenSIPS' documentation about how to deal with
NATs.
I found ways of dealing with messages from client that is behind NAT.
OpenSIPS can fix Contact headers fields and registers, when SIP
messages comes from clients and cross NATs before reaching this proxy.
However, my OpenSIPS and callee is behind NAT, not the client. That
is, if a client (caller) calls the callee, how could OpenSIPS with its
functions fixes Contact header fields in responses that go from callee
to caller, so that the client will be able to send ACKs? It is still
obscure to me.
Any idea?
Best regards.
RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
_______________________________________________
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
