Summary: | ASTERISK-06249: can't get status device | ||
Reporter: | kent (kent) | Labels: | |
Date Opened: | 2006-02-03 06:40:14.000-0600 | Date Closed: | 2006-04-10 12:50:41 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Applications/app_queue |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) app_queue.c.patch | |
Description: | i'am upload file with changes, apply or commit it | ||
Comments: | By: kent (kent) 2006-02-04 09:55:00.000-0600 this bugg exist in 1.2.3 o may be in trunk version ;) By: Matt O'Gorman (mogorman) 2006-02-22 16:08:47.000-0600 are you sure this is a bug , i labbed it up with and without your line and got the same results when busy and unavail, as the variable was already correctly populated By: Olle Johansson (oej) 2006-04-04 08:39:11 No disclaimer, no ansewr from reporter. By: kent (kent) 2006-04-05 10:20:44 > mogorman yes it's bug i have't time to complaine. app_queues read status device once when load(reload), but devices change status within asterisk work....understand? By: Andrey S Pankov (casper) 2006-04-07 17:01:46 Isn't it updated within changethread? cur->status = sc->state; Moreover, as I understand it form your patch, you are not using latest SVN trunk. By: Andrey S Pankov (casper) 2006-04-10 12:08:59 Is it still an issue with latest SVN trunk? By: BJ Weschke (bweschke) 2006-04-10 12:49:48 There really shouldn't be a need for this patch so long as we are calling ast_device_state in all the spots were actions are being taken on the queue members (which is the intent). If that's not the case and we're still out of sync, then that is a bug that we need to fix. Closing for now. If it's still an issue, please let us know by reopening with more data. By: BJ Weschke (bweschke) 2006-04-10 12:50:40 cannot reproduce. need more info from the poster if it's still an issue in current 1.2.X or /trunk. |