CDR search criteria not honoring date range

Customer with OEM system and version 15.0.17.22 of the module reported an issue when using complex query with the CDR

CDR version: 15.0.17.22

If the user enters two numbers on the outbound callerID number field, for example 5146138244,4372922436 and then a date range on the Call date field

CDR will return results without honoring the date range.

According to the hint icon info, the field should allow to search for a set of numbers separated by a comma, it seems it's breaking on the outbound callerID number field when it uses comma.