We took have the same problem after an upgrade to CM 5.2
Ticket number 15548791 is opened with Avaya and after an MST trace, it has been esculated to Tier 4.
According to Tier 3, they were ot able to reproduce the issue with CM 5.2 patch 17250; they were able to recreate it with patch levels 17436 and 17534.