Bypass media succeeds from extension to gateway but fails from extension to extension
I'm not sure if this is a bug or just a NAT-related configurational problem. If it's truly a bug, let me know and I'll be happy to file a Jira. I'm trying to get bypass media to work with extension to extension calls. Both endpoint extensions are behind NAT in two different locations. This looks like a possible bug because FS sends the internal IP address of one of the endpoints to the other for media, but when making a call from the same extension to an external gateway for PSTN termination, it sends the phone's external IP address as it should, and the call succeeds. Everything works fine, of course, when "proxy media" is used. The SIP traffic for the failed call is here, look for the word "WRONG!" to see the incorrect address being passed in the SDP: http://pastebin.freeswitch.org/19003 Regards, Phil Quesinberry Q Systems Engineering, Inc. Electronic Controls and Embedded Systems Development (410) 969-8002 http://www.qsystemsengineering.com
On Mon, May 7, 2012 at 9:54 AM, Phil Quesinberry <philq@qsystemsengineering.com> wrote:
I’m trying to get bypass media to work with extension to extension calls. Both endpoint extensions are behind NAT in two different locations. This looks like a possible bug because FS sends the internal IP address of one of the endpoints to the other for media, but when making a call from the same extension to an external gateway for PSTN termination, it sends the phone’s external IP address as it should, and the call succeeds.
My guess is that this is not a bug. The NAT stuff has been gone over and over and used in many different configurations. Usually, in my experience, NAT issues are cause by config errors or a broken device. What do you have for your sofia configs? Gabe
This is not a bug in FreeSWITCH... Bypass Media is a special mode to allow us to act as a psuedo proxy. Other then possibly filtering some codecs the rest of the SDPs are simply copied across the bridge. That means if your sip devices are sending RFC1918 IPs in their SDPs then FreeSWITCH will forward an RFC1918 SDP. Why is that? Because FreeSWITCH has no way to know where the media is actually coming from since FreeSWITCH is not in the media path. K On 5/7/12 8:34 PM, "Gabriel Gunderson" <gabe@gundy.org> wrote:
On Mon, May 7, 2012 at 9:54 AM, Phil Quesinberry <philq@qsystemsengineering.com> wrote:
I¹m trying to get bypass media to work with extension to extension calls. Both endpoint extensions are behind NAT in two different locations. This looks like a possible bug because FS sends the internal IP address of one of the endpoints to the other for media, but when making a call from the same extension to an external gateway for PSTN termination, it sends the phone¹s external IP address as it should, and the call succeeds.
My guess is that this is not a bug. The NAT stuff has been gone over and over and used in many different configurations. Usually, in my experience, NAT issues are cause by config errors or a broken device.
What do you have for your sofia configs?
Gabe
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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 (3)
-
Gabriel Gunderson
-
Ken Rice
-
Phil Quesinberry