[Freeswitch-dev] rtp-timer-name set to none
djbinter at gmail.com
Fri Mar 7 02:12:06 MSK 2014
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
On Wed, Mar 5, 2014 at 9:06 PM, George Halpert <george at thesoniccloud.com>wrote:
> What are the disadvantages and risks of setting rtp-timer-name to none?
> What problems can it lead to?
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> Official FreeSWITCH Sites
> FreeSWITCH-dev mailing list
> FreeSWITCH-dev at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2013 Aug 6-8, 2013
More information about the FreeSWITCH-dev