Am 01.06.2010 22:08, schrieb Daniel-Constantin Mierla:
On 6/1/10 10:02 PM, Klaus Darilion wrote:
Daniel-Constantin Mierla wrote:
On 6/1/10 9:07 PM, Alex Balashov wrote:
No, it'll store the fixed one, in the proper contact column, not the received column. I do this all the time, even though it's not the "proper" way.
should be the original one with the last version, afaik. There were issues with phones accepting calls which had a different uri than the address they set in contact of register.
So, the contact details were brocken in:
- contact - the address from header
- received - built from source ip and port
- socket - local socket where the register was received
Note that there are two functions, fix_nated_contact() and fix_nated_registrar().
I know. I always use fix_nated_register. I just wonder why save() saves the fixed contact in case of fix_nated_contact(), because usually we have the problem that changes to the message are only visible when the message is forwarded (lumps are applied)
but are you sure the fixed contact is saved? I quick look in the registrar code seems to take the contact from headers, which are pointing inside original message.
I just tested with kamailio 3.0 and you are right. Yesterday I tested with ser 0.9.? and fix_nated_contact() seemed to save the rewritten contact header - strange.
Thanks klaus