TCP transport issue (port in contact not same as the source/Via port) v1.8.10-trunk

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Am 10.12.2010 11:04, schrieb Benny Prijono:
> On Fri, Dec 10, 2010 at 2:47 PM, Anshuman S. Rawat<arawat at 3clogic.com>  wrote:
>>> That's not true. If the client is behind NAT, different IP would have
>>> been returned in the Via received parameter of the 200/OK, and PJSIP
>>> would re-register using that IP and the source TCP port in the
>>> Contact.
>>>
>>
>> I do not want to use the 'contact rewrite' option. I thought that it might
>> work without using this option.
>>
>>> In your current setup, there should not be any problem for the server
>>> to open a TCP connection to the client, as they are in the same LAN.
>>> Maybe there's a configuration in OpenSIPS that you need to tweak.
>>
>> I am now using the option suggested by Klaus Darilion. It seems to work so
>> far. Need more testing though.
>>
>
> Btw the newest feature to fix this is the SIP outbound extension (RFC
> 5626), just implemented in 1.8.10. Lets hope the open source server
> camps pick this up soon, as this would eliminate contact_rewrite or
> fix_nated_register() "hacks".

What do we need to implement in detail? :-)



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux