Internal Profile sends RTP to external IP when using two network interfaces
Hi, I have a FS box with two physical network interfaces. The internal interface is hosting several internal phones. I have binded the internal profile SIP/RTP/IP to the private interface. Phones registered correctly but with User: 1000@external.ip.address in sofia status profile internal When I place a call between two internal phones, RTP traffic is send to the external IP address of the FS box instead of the internal. The SIP/SDP messages send from FS carry the external IP instead of the internal. The result is that no RTP media arrives to any of the phones. /aep -- Stopping junk mailers is good for the environment
First off you can't bind one profile to two interfaces you have to launch two sofia profiles, one for each IP. Secondly if you're doing things like this you'll have to refer to the in tree internal.xml. Third can you outline the network topology a little bit more? Is nat involved? /b On Aug 26, 2009, at 3:04 AM, Alberto Escudero-Pascual (lists) wrote:
Hi,
I have a FS box with two physical network interfaces. The internal interface is hosting several internal phones. I have binded the internal profile SIP/RTP/IP to the private interface. Phones registered correctly but with User: 1000@external.ip.address in sofia status profile internal
When I place a call between two internal phones, RTP traffic is send to the external IP address of the FS box instead of the internal.
The SIP/SDP messages send from FS carry the external IP instead of the internal.
The result is that no RTP media arrives to any of the phones.
/aep
ASCII art follows voip-phones..... 10.0.46.1 [ FS ] 216.82.231.69 ----> 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 216.82.231.69 port 5080 My IP phones are in the 10.0.46.X range and they register @ 10.0.46.1 IP address. 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 216.82.231.69 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 216.82.231.69 instead of 10.0.46.1 Thanks looong time! -- Stopping junk mailers is good for the environment
First off you can't bind one profile to two interfaces you have to launch two sofia profiles, one for each IP. Secondly if you're doing things like this you'll have to refer to the in tree internal.xml. Third can you outline the network topology a little bit more? Is nat involved?
/b
On Aug 26, 2009, at 3:04 AM, Alberto Escudero-Pascual (lists) wrote:
Hi,
I have a FS box with two physical network interfaces. The internal interface is hosting several internal phones. I have binded the internal profile SIP/RTP/IP to the private interface. Phones registered correctly but with User: 1000@external.ip.address in sofia status profile internal
When I place a call between two internal phones, RTP traffic is send to the external IP address of the FS box instead of the internal.
The SIP/SDP messages send from FS carry the external IP instead of the internal.
The result is that no RTP media arrives to any of the phones.
/aep
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
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. /b On Aug 26, 2009, at 9:18 AM, Alberto Escudero-Pascual (lists) wrote:
ASCII art follows
voip-phones..... 10.0.46.1 [ FS ] 216.82.231.69 ----> 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 216.82.231.69 port 5080
My IP phones are in the 10.0.46.X range and they register @ 10.0.46.1 IP address.
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 216.82.231.69 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 216.82.231.69 instead of 10.0.46.1
Thanks looong time!
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@216.82.231.69 Contact: "user" <sip:1000@10.0.46.51;user=phone;fs_nat=yes;fs_path=sip%3A1000%4010.0.46.51%3A5060%3Buser%3Dphone> Agent: Grandstream BT110 1.0.8.12 Status: Registered(UDP-NAT)(unknown) EXP(2009-08-26 22:22:32) Host: open46 IP: 10.0.46.51 Instead of User: 1000@10.0.46.51 I can see SIP/SDP messages announcing the external IP and port 5060 in the INVITE. It is a very old phone... will try with different gadgets tomorrow. /aep -- 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.
/b
On Aug 26, 2009, at 9:18 AM, Alberto Escudero-Pascual (lists) wrote:
ASCII art follows
voip-phones..... 10.0.46.1 [ FS ] 216.82.231.69 ----> 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 216.82.231.69 port 5080
My IP phones are in the 10.0.46.X range and they register @ 10.0.46.1 IP address.
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 216.82.231.69 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 216.82.231.69 instead of 10.0.46.1
Thanks looong time!
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (2)
-
Alberto Escudero-Pascual (lists)
-
Brian West