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