Hi Emmanuel, In theory this will be nice and correct, but practically speaking it is too difficult to do , as the SIP part needs to be aware of the transport layer and vice versa .
Like you need to "know" that a SIP URI points behind a NAT, store the info with the RURI and pass it to the transport level when it tries to send the message out. The 2.0 design will solve this problem as the async model will not be affected by the blocking to a natted destination. Regards, Bogdan Emmanuel BUU wrote: > Hello, > > Is there a way in the TM module to prevent opensips to open an outbound > TCP connection in case the destination is nated? > > Emmanuel > > _______________________________________________ > Devel mailing list > Devel@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/devel > > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
