Based on old posts from Anthony: You are basically turning off the feature that allows the remote end to stop sending audio but have FS still process the stream. The timer will allow the channel to read at the specified interval even when the other side stops sending audio. If the other end has a clock sync issue with FS or FS does not have a reliable timing source, it could cause your problem. When timer-name set to none, it does blocking reads on the audio vs timed ones. If the other end has a skew in clock freq with the FS then it will timeout erroneously. Having blocking reads ensures you only read audio when there is actually some there. Basically this timer-name set to none makes FS behave just like asterisk does by default. On Wed, Mar 5, 2014 at 9:06 PM, George Halpert <george@thesoniccloud.com>wrote:

Hi,

What are the disadvantages and risks of setting rtp-timer-name to none? What problems can it lead to?

Thanks, George

_________________________________________________________________________ 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-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org