Couldn't you fix your client to report the proper IP in the first place?  What you're proposing would prevent two FreeSWITCH systems from every talking because neither would send ANYTHING.

On Fri, Apr 24, 2015 at 12:40 PM, JP <jaykris@gmail.com> wrote:

I've observed that FreeSWITCH will initially transmit RTP to the remote party's private IP address until it has received at least 10 packets, at which time it will start sending to the remote party's NATed address.  Is there some way to suspend the transmission of RTP altogether until at least one packet has been received from the remote party?  It would be ideal if this could be controlled on a per call and/or per SIP profile basis.


Thanks,


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.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



--

Brian West
brian@freeswitch.org


Twitter: @FreeSWITCH , @briankwest
http://www.freeswitchbook.com
http://www.freeswitchcookbook.com

ClueCon 2015 Call for Speakers | Register TODAY! | Reddit: /r/freeswitch

T:+19184209001 | F:+19184209002 | M:+1918424WEST (9378)
iNUM:+883 5100 1420 9001 | ISN:410*543 | Skype:briankwest