[Freeswitch-users] Internal Profile sends RTP to external IP when using two network interfaces
Alberto Escudero-Pascual (lists)
aep.lists at it46.se
Wed Aug 26 11:25:22 PDT 2009
Yes, I did fix the internal IP in the internal profile overwritting the
local_ipv4 var in sip-ip and rtp-ip. When the internal clients
>sofia status profile internet
User: 1000 at 188.8.131.52
<sip:1000 at 10.0.46.51;user=phone;fs_nat=yes;fs_path=sip%3A1000%4010.0.46.51%3A5060%3Buser%3Dphone>
Agent: Grandstream BT110 184.108.40.206
Status: Registered(UDP-NAT)(unknown) EXP(2009-08-26 22:22:32)
User: 1000 at 10.0.46.51
I can see SIP/SDP messages announcing the external IP and port 5060 in the
It is a very old phone... will try with different gadgets tomorrow.
Stopping junk mailers is good for the environment
> Well actually you do have issues you're going to have to specify the
> rtp-ip and sip-ip on BOTH profiles yourself because you're config is
> currently putting your external IP into the internal's settings.
> Please correct that and I'm sure it'll work then.
> On Aug 26, 2009, at 9:18 AM, Alberto Escudero-Pascual (lists) wrote:
>> ASCII art follows
>> voip-phones..... 10.0.46.1 [ FS ] 220.127.116.11 ----> Internet
>> I have two profiles binded to two different IPs
>> internal is binded to 10.0.46.1 port 5060 /24 network
>> external is binded to 18.104.22.168 port 5080
>> My IP phones are in the 10.0.46.X range and they register @
>> 10.0.46.1 IP
>> When I place a call between the two phones in the 10.0.46.0/24 network
>> the phones register but audio RTP is sent to 22.214.171.124 instead of
>> 10.0.46.1 (FS)
>> In this scenario i have FS without any NAT configuration.
>> The way that i solved was to run both profiles (internal and
>> external) in
>> the public IP (local_ipv4) and force the phones to register with
>> 126.96.36.199 instead of 10.0.46.1
>> Thanks looong time!
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
More information about the FreeSWITCH-users