[Serusers] SIP Contact header field issue incase of NAT

[samuel]

In your config file, for REGISTER requests use fix_nated_register();
instead of fix_nated_contact();
This will make the 200 answer to contain the original Contact while
solving the NAT "issues".

SAmuel.


2006/9/1, Abdul Qadir <ablqadir at yahoo.com>:
> Hi All,
>
>   I have problem connecting Nokia Phone with SER. The problem is When SER
> receives the registration request from the Nokia phone. The registration
> request contain the phone's private IP (192.xxx.xx.xx), since we use wifi
> for connection. Our proxy detects that since this is a private IP handles
> the NAT translation and determines the phone public IP address (e.g.,
> 202.xxx.xx.xx, port xx). Our SIP proxy informs the phone that registration
> is successful but the contact information is changed from
> userid at 192.xxx.xxx.xx to userid at 202.xxx.xxx.xx, port xx.  On recieving this
> changed contact info the Phone rejects 200 Ok.
>
>      We tried to contact nokia people and they said that its part of RFC3261
> to reject such contacts. After this I have also gone through RFC 3261
> section "10.2.4" and it seems that phone is doing rite.  Can any body tell
> me why SER is changing the contact address in case of NAT. It would be higly
> appreciated if you can give me some reference from some RFC or other
> document which I can show to nokia people.
>
>
>
> Best Regards,
> Abdul Qadir
>
>
>  ________________________________
> How low will we go? Check out Yahoo! Messenger's low PC-to-Phone call rates.
> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
>
>