[Osip] the eXosip_masquerade_contact issue

[Gemi Tsai 蔡國泰]

Hi Aymeric and all,

I'm sorry.
I found that is not the OpenIMScore issue, too.
Because the P-CSCF acts the outbound proxy, so we didn't need to use
the eXosip_masquerade_contact function in the IMS.

It means that we don't do anything for SIP Signaling, and UAs can
traverse the NAT.
But, the SDP is must handled by ourselves.

Thanks.
Gemi


2009/7/17 Gemi Tsai 蔡國泰 <gemi.tsai at gmail.com>:
> Hi Aymeric and all,
>
> I tested with OpenIMSCore, and found this Via issue. (maybe it caused
> by OpenIMSCore)
>
> Please see attached files, when I didn't modify the Via header field
> and originated a call, the UA received the 403 error response.
>
> When I originate a call, I found the log of OpenIMSCore, the
> originating contact that it got is private_addr:public_port
> (192.168.180.63:3410).
> So the OpenIMSCore can't look for this account, and return 403.
>
> After you replied, I think that it is maybe an OpenIMSCore issue, do you agree?
>
> Thanks for your response.
>
> Gemi
>
>
> 2009/7/16 Aymeric Moizard <jack at atosc.org>:
>>
>>
>> On Thu, 16 Jul 2009, Gemi Tsai ½²°ê®õ wrote:
>>
>>> Hi all and Aymeric,
>>>
>>> I tried to use the eXosip_masquerade_contact function, and input the
>>> public address and port. (got by stun server)
>>>
>>> But I found that eXosip only modify the Contact header of SIP Messages
>>> to public address and port.
>>> Why the Via header doesn't be modified?
>>
>> There is no reason to modify the Via IP and port. They are not
>> used for SIP routing. ("received" parameter is used by rfc3261 and "rport"
>> extension is mandatory for deployment behind NAT)
>>
>> Aymeric
>>
>>> The packet is attached.
>>> Thanks very much!
>>>
>>> Gemi
>>
>> _______________________________________________
>> Osip mailing list
>> Osip at atosc.org
>> http://www.atosc.org/mailinglist/listinfo/osip
>>
>>
>