Hello,
Trying to understand why CDR rows are sometimes not written to v_xml_cdr for calls, I added some logging to database.php and found the error:
SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'pdd_ms' at row 1
(It's MySQL).
The value 1264 in the error is weird, it's a smallint and for other rows there are values smaller and larger. So the message is maybe inaccurate (MySQL issue?) yet the problem is there. Any idea what may cause out-of-range pdd_ms? Maybe the SIP provider's behavior or FreeSWITCH issue?
FusionPBX 4.4.3, FreeSWITCH 1.8.5.
I guess altering the column to be int will work, but does it make sense?
Thanks
ADDED: similar issue with
SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'json' at row 1
(looks that 1406 is not the field size yet the problem is there).
Trying to understand why CDR rows are sometimes not written to v_xml_cdr for calls, I added some logging to database.php and found the error:
SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'pdd_ms' at row 1
(It's MySQL).
The value 1264 in the error is weird, it's a smallint and for other rows there are values smaller and larger. So the message is maybe inaccurate (MySQL issue?) yet the problem is there. Any idea what may cause out-of-range pdd_ms? Maybe the SIP provider's behavior or FreeSWITCH issue?
FusionPBX 4.4.3, FreeSWITCH 1.8.5.
I guess altering the column to be int will work, but does it make sense?
Thanks
ADDED: similar issue with
SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'json' at row 1
(looks that 1406 is not the field size yet the problem is there).