[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Flexisip behind NAT
From: |
Aram M. |
Subject: |
Re: Flexisip behind NAT |
Date: |
Fri, 8 Nov 2019 20:17:30 +0400 |
cap_config.zip
Description: Zip archive
> On Nov 8, 2019, at 8:16 PM, Aram M. <address@hidden> wrote:
>
> Hi Nicolas,
>
> Thanks a lot for your reply.
>
> Both properties are configured in the config. Path header is set with FQDN as
> well as VIA header in register sent to the SIP server but the Contact header
> still has AWS private/local IP. According to the captures you can see in the
> attachment, the SIP server is trying to route the INVITE message to the
> destination set in the Contact header.
>
> I am also attaching the config file if could have a look.
>
> Any help would be greatly appreciated.
>
> Best Regards,
> Aram.
>
>> On Nov 8, 2019, at 6:04 PM, Nicolas Michon <address@hidden> wrote:
>>
>> Hello,
>>
>>
>> Does the 'transports' parameter include the fqdn or public IP of your server
>> ?
>>
>> Please read the 'aliases' and 'transports' properties for more details about
>> the syntax here :
>> https://wiki.linphone.org/xwiki/wiki/public/view/Flexisip/Modules%20Reference%20Guide/master/global
>>
>>
>> Regards,
>>
>> Nicolas
>>
>> On 07/11/2019 08:57, Aram M. wrote:
>>> Hello Dear Flexisip Developers and Community.
>>>
>>> We have been using Flexisip as a proxy server for many years without any
>>> issue.
>>>
>>> When we moved our server into AWS instances the proxy functionality stopped
>>> to be working.
>>>
>>> The issue is that when proxy changes the Contact header or adds Path it
>>> inserts the AWS instance private/local IP which the original SIP server
>>> can’t find while making INVITE.
>>>
>>> So is there any configuration for Flexisip to make aware of it’s NAT
>>> address or put the instance hostname in Path or Contact headers.
>>>
>>>
>>> Any help would be greatly appreciated.
>>>
>>>
>>> Thanks,
>>> Aram.
>>
>> --
>> Nicolas Michon, Software Engineer
>> Belledonne Communications
>> http://www.belledonne-communications.com
>>
>