Summary: | ASTERISK-28262: Custom device state losing - (dash) | ||||
Reporter: | Leandro Dardini (ldardini) | Labels: | |||
Date Opened: | 2019-01-24 12:47:12.000-0600 | Date Closed: | 2019-01-24 13:18:58.000-0600 | ||
Priority: | Minor | Regression? | No | ||
Status: | Closed/Complete | Components: | Applications/General | ||
Versions: | 13.23.1 13.24.1 | Frequency of Occurrence | Occasional | ||
Related Issues: |
| ||||
Environment: | CentOS 7 - 64bit | Attachments: | |||
Description: | From time to time, with no apparent reason, in any version I have tried in the 13 branch, every custom device state, usually in the form of 100-DEVEL, loses the dash. So for example, a pbx with over 300 custom device states, changes from:
{quote} 21-gkm@authenticate: Custom:221-gkm State:Idle Presence:not_set Watchers 4 103-phoenix@authenti: Custom:103-phoenix State:Idle Presence:not_set Watchers 1 20-itrs@authenticate: Custom:20-itrs State:Idle Presence:not_set Watchers 0 25-saveur@authentica: Custom:25-saveur State:InUse Presence:not_set Watchers 0 205-tti@authenticate: Custom:205-tti State:Idle Presence:not_set Watchers 2 24-itrs@authenticate: Custom:24-itrs State:Idle Presence:not_set Watchers 0 {quote} To {quote} 21gkm@authenticate: Custom:221gkm State:Idle Presence:not_set Watchers 4 103phoenix@authenti: Custom:103phoenix State:Idle Presence:not_set Watchers 1 20itrs@authenticate: Custom:20itrs State:Idle Presence:not_set Watchers 0 25saveur@authentica: Custom:25saveur State:InUse Presence:not_set Watchers 0 205tti@authenticate: Custom:205tti State:Idle Presence:not_set Watchers 2 24itrs@authenticate: Custom:24itrs State:Idle Presence:not_set Watchers 0 {quote} Obviously the BLF used for the custom device state stops working. The weird thing is only "-" is lost... if there is a custom device state like: {quote} 12_idcam@authenticat: Custom:12_idcam State:Idle Presence:not_set Watchers 4 {quote} it remains correct | ||||
Comments: | By: Asterisk Team (asteriskteam) 2019-01-24 12:47:13.211-0600 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. 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. |