Originally when the problem was occurring?  Yes, I was using the default conference profile from the vanilla conf.

To recap, the problem happened on Windows 7, CentOS 5.9, Debian 6 but it worked fine on Debian 7.




On Mon, Jun 16, 2014 at 2:03 PM, Brian West <brian@freeswitch.org> wrote:
That sir is the Mystery, So you're doing WebRTC into an 8k CONF right?

--
Brian West


Twitter: @FreeSWITCH , @briankwest














On Jun 16, 2014, at 3:55 PM, Oleg Stolyar <olegstolyar@gmail.com> wrote:

Ah, but that's completely consistent with what I am seeing.  This explains why 11999 still exhibited the problem - it simply kept using 8000.

The question for me is why did the problem go away at 12000.  


On Mon, Jun 16, 2014 at 1:25 PM, Brian West <brian@freeswitch.org> wrote:
What you're saying is IMPOSSIBLE to have happened.  The rates are checked, the only values accepted are 8000/12000/16000/24000/32000/48000, Had you set it to 11999 it would have defaulted to the 8000.

So don't stop looking because you've yet to find the real problem.

--
Brian West


_________________________________________________________________________
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