[Home]

Summary:ASTERISK-30116: Asterisk cel DB table issues
Reporter:Dalius Mockevicius (Daliusm)Labels:
Date Opened:2022-06-23 02:53:44Date Closed:2022-07-07 12:00:01
Priority:MinorRegression?
Status:Closed/CompleteComponents:CEL/cel_odbc
Versions:18.12.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Attachments:
Description:Hello,

I need information, whether is it bug, or undocumented feature.

Curently I have Asterisk writing something CEL log to MySQL table. Table is created using these examples: https://wiki.asterisk.org/wiki/display/AST/CEL+Configuration+Examples

There column `peer` has type varchar(80).

Now I have these messages in Asterisk full log, e.g.:
{code}
[Jun 19 10:43:55] WARNING[16877] res_odbc.c: SQL Execute returned an error: HY000: [MySQL][ODBC 8.0(w) Driver][mysqld-5.7.37-40]Data too long for column 'peer' at row 1
[Jun 19 10:43:55] WARNING[16877] res_odbc.c: SQL Execute error -1!
[Jun 19 10:43:55] WARNING[16877] cel_odbc.c: Insert failed on 'asterisk-odbc:realtime_cel'.  CEL failed: INSERT INTO realtime_cel (eventtype, eventtime, userdeftype, cid_name, cid_num, cid_ani, cid_rdnis, cid_dnid, exten, context, channame, appname, appdata, amaflags, accountcode, peeraccount, uniqueid, linkedid, userfield, peer, extra) VALUES ('BRIDGE_EXIT', {ts '2022-06-19 10:43:55.747193'}, '', 'xxxxxxx', '000000000', '00000000', '', '000000000', 's', 'conference', 'SIP/sitea-vims-vln-in-000000f3', 'ConfBridge', '1234,conference,user_unmuted', 3, '', '', '1655620856.1543', '1655620856.1543', '', 'CBAnn/1234-00000016;2,SIP/sitea-vims-vln-in-000000f5,SIP/sitea-vims-vln-in-000000f6,SIP/sitea-vims-vln-in-000000f9', '{"bridge_id":"94ec9b5a-d85d-443f-84b6-5e792884cde6","bridge_technology":"softmix"}')
{code}
This is because peer value is 115 chars long. Longer than its is allowed by table schema.

And my question is did I miss some DB migration? Or Asterisk writes something longer, than is expected?

Comments:By: Asterisk Team (asteriskteam) 2022-06-23 02:53:45.669-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
By: Joshua C. Colp (jcolp) 2022-06-23 03:56:19.218-0500

Asterisk is writing something longer than it would have in the past when such a schema was created. You can extend the size further to meet your needs. Does that work? If so, for your usage what did you extend it to? Over all the CEL schema isn't managed using our current Alembic based system as noone has moved it there.
By: Asterisk Team (asteriskteam) 2022-07-07 12:00:01.228-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines