[OpenSIPS-Users] Opensips 1.9.1 and NAT

[Ali Pey]

Hello,

The question is not quite clear. In your opensips.cfg you call
"fix_nated_contact()"
on both route and reply route. that's why it changes the route.

There is no such a thing as direction in opensips unless it's implemented
in your logic. A message goes through your route or reply route scripts
when it reaches opensips.

Regards,
Ali


On Fri, Nov 22, 2013 at 1:10 AM, dpa <denis7979 at mail.ru> wrote:

> Hello
>
>
>
> I have a one question about nat processing of Opensips.
>
>
>
> There is such scheme
>
>
>
> UAC1 (softphone behind nat) à Opensips -> UAC2 (another softswitch), i.e.
> UAC1 initiates a call to Opensips and a signaling port = 5068.
>
>
>
> So UAC2 becomes “ringing” by sending 183 message.
>
>
>
> In attachment 183 message from UAC2 and some parts of opensips.cfg
>
>
>
> After 183 processing by Opensips port in Contact header of 183 (and later
> 200 OK) messages become 5060, i.e. Opensips detects NAT and changes Contact
> header.
>
>
>
> So my question is, Why does Opensips changes Contact header?
>
> Once Opensips detects nat transaction (setting setflag(21)) is it check
> all reply messages (and doesn`t matter from which UAC they have been
> received) or Opensips can detect direction and makes decision about nat
> process?
>
>
>
> Thank you  for any help.
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> 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/20131122/15b186c8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 906 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20131122/15b186c8/attachment.gif>