Files
fusionpbx/app
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
..
2020-01-17 16:19:46 -07:00
2020-01-13 08:18:16 -07:00
2020-01-26 15:39:48 -07:00
2020-01-21 14:21:34 -07:00
2020-01-08 20:38:00 -07:00
2019-05-15 20:04:39 -04:00
2020-01-29 11:49:49 -07:00
2019-11-28 02:15:47 -07:00
2020-01-22 22:08:42 -05:00
2020-01-06 11:45:14 -07:00
2018-02-26 15:15:36 -05:00
2020-01-06 12:07:05 -07:00
2020-01-08 20:42:30 -07:00
2019-12-14 08:18:32 -07:00
2020-01-21 16:53:13 -07:00
2020-01-08 20:50:21 -07:00
2019-12-04 16:26:58 -07:00
2019-12-31 14:40:16 -07:00
2019-12-31 11:46:34 -07:00
2020-01-28 21:33:10 -07:00
2020-01-06 12:33:56 -07:00
2019-12-04 13:49:02 -07:00
2020-01-08 20:47:44 -07:00
2019-12-28 12:16:34 -07:00
2020-01-08 20:46:45 -07:00
2020-01-15 13:41:20 -07:00