Hi Michael, After your mail, I did several test and looked into the packets, but the phones doesn't insert any reference to the NAT_ADDRESS. Freeswitch adds the parameter "received=NAT_ADDRESS" in the via header (for the aggressive-nat-detection) and sometimes changes the SDP connect information to the NAT_ADDRESS instead of the PHONE_PRIVATE_ADDRESS. Could the bypass_media_after_bridge fail in some calls? Regards, Il 23/07/13 15.50, Michael Jerris ha scritto:
in bypass media, we pass along the sdp the other side sends. If they are sending the wrong address, we will happily send that along. If the other end can't figure it out with its own nat fixing, it won't work.
On Jul 23, 2013, at 7:38 AM, Carlo Dimaggio <jaasmailing@gmail.com <mailto:jaasmailing@gmail.com>> wrote:
Hi all,
I have an installation with several phones (yealink) behind NAT and freeswitch withaggressive-nat-detection=true in internal SIP Profile. In dialplan I set bypass_media_after_bridgein order to eliminate on-way audio problems (and use less bandwidth), but I'm encountering a strange issue. When I call two extensions, sometimes freeswitch bypassthe media between them (so the SDP sent by freeswitch have the private IP) and sometimes freeswitch send the SDP with the NAT IP(in this case there is no audio).
What could be the problem? Is this a bug or my misconfiguration?
_________________________________________________________________________ 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