[asterisk-bugs] [JIRA] (ASTERISK-21035) features.conf in static realtime requires distinct cat_metric for each parking lot

Alex Epshteyn (JIRA) noreply at issues.asterisk.org
Sat Feb 2 00:20:58 CST 2013


     [ https://issues.asterisk.org/jira/browse/ASTERISK-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Epshteyn updated ASTERISK-21035:
-------------------------------------

    Attachment: static_db.sql
                cli

attaching 2 files
1) cli - error messages in cli
2) static realtime table that we use (id and tenantid are thirdlane specific columns, you can get rid of them) - i just left everything as is

as I mentioned before - a workaround would be to specify a cat_metric value (unique for each parking lot but the same for all rows of a parking lot), but i don't think that it should be required - if I understand the purpose of cat_metric correctly 
                
> features.conf in static realtime requires distinct cat_metric for each parking lot 
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21035
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21035
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/res_config_mysql
>    Affects Versions: 1.8.20.0
>         Environment: CentOS, res_config_mysql backend
>            Reporter: Alex Epshteyn
>            Assignee: Alex Epshteyn
>         Attachments: cli, static_db.sql
>
>
> when multiple parking lots are defined in static realtime even though each parking lot has a distinct category but cat_metric is the same for all parking lots produces errors during configuration load or "features reload". Making cat_metric unique for each parking lot seems  to solve the problem. It appears that the problem may be related to the order of loading of the configuration data (tested only using res_config_mysql)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list