Files
fusionpbx/app/xml_cdr
Andy-Seattle cfd70dcf4e E.164 Inbound caller ID fix (#5138)
When an inbound call has E.164 caller ID format (eg Skyetel), the + is being stripped from the caller_id_number variable before storing in the v_xml_cdr database table. If we then try and block this CDR in the Call Block application it adds the number BUT without the + so it never matches future calls.
This proposed change ensures that the + is not stripped for INBOUND calls when written to v_xml_cdr and therefore when blocking the CDR it works correctly (i.e. it includes the + which then matches the call next time and blocks it).
2020-01-31 15:37:46 -07:00
..
2019-12-23 11:20:43 -07:00
2019-12-24 14:31:04 -07:00
2017-01-13 00:24:29 -07:00
2020-01-06 10:56:27 -07:00
2019-09-06 11:05:01 -06:00
2019-09-03 08:29:44 -06:00
2020-01-28 17:28:01 -07:00
2020-01-28 17:27:23 -07:00
2020-01-06 10:56:27 -07:00
2020-01-06 10:56:27 -07:00
2020-01-28 18:43:04 -07:00