| Summary: | ASTERISK-22191: wrong timing for periodic announcement in queue | ||
| Reporter: | c0rnoTa (c0rnota) | Labels: | |
| Date Opened: | 2013-07-24 10:13:15 | Date Closed: | 2013-08-01 09:50:12 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | 1.8.22.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | OS Linux Gentoo x86_64 on hardware server DL180 Realtime SIP agents in queue with strategy ringall. | Attachments: | ( 0) verbose_queue |
| Description: | Was spotted an error in the calculation of the periods of periodic-announcement in the queues. It is not the difference in the calculation of the time when the operators are free or unavailable. I am talking about a point of reference when timer starts counting next period.
In my understanding, periodic notification should play after a specified period of time taking into account the duration of the playback file. Actually, the way it often happens. It calls to agents then comes the specified periodic-announce-frequency time, it playing a notification, and then starts timer to count next periodic-announce-frequency. Sometimes, for unknown reasons to me, the beginning of the reference period of announcement is the end of the previous period, and not the end of the played announcement. Is there a reason why the starting point of periodic-announce-frequency may change? The way it looks in verbose you can find in the attachment. periodic-announce-frequency=20 periodic announce duration is 15 secs. At Jul 16 18:18:17 periodic announcement starts, at Jul 16 18:18:31 it ends. At Jul 16 18:18:51 starts (after 20 seconds) - at Jul 16 18:19:05 it ends. At Jul 16 18:19:11 it starts (after 6 secons)- Jul 16 18:19:26 it ends. | ||
| Comments: | By: Rusty Newton (rnewton) 2013-07-26 17:23:16.863-0500 That does look strange. Please attach an Asterisk log again, but additionally with DEBUG turned up to 5 and "sip set debug on". I'm curious what is happening in between those two announcements at {noformat} [Jul 16 18:18:51] VERBOSE[4628] res_musiconhold.c: -- Stopped music on hold on SIP/audiotele-00023dfb [Jul 16 18:18:51] VERBOSE[4628] app_queue.c: -- Playing periodic announcement [Jul 16 18:18:51] VERBOSE[4628] file.c: -- <SIP/audiotele-00023dfb> Playing '365_periodic.slin' (language 'ru') [Jul 16 18:19:05] VERBOSE[4628] res_musiconhold.c: -- Started music on hold, class 'default', on SIP/audiotele-00023dfb [Jul 16 18:19:06] VERBOSE[4628] res_musiconhold.c: -- Stopped music on hold on SIP/audiotele-00023dfb [Jul 16 18:19:06] VERBOSE[4628] res_musiconhold.c: -- Started music on hold, class 'default', on SIP/audiotele-00023dfb [Jul 16 18:19:11] VERBOSE[4628] res_musiconhold.c: -- Stopped music on hold on SIP/audiotele-00023dfb [Jul 16 18:19:11] VERBOSE[4628] app_queue.c: -- Playing periodic announcement {noformat} By: c0rnoTa (c0rnota) 2013-08-01 06:49:44.057-0500 Excuse me, but I can not reproduce this issue. I don't know what can be wired with it. I think we can close this issue, because it coudn't be reproduced. But I'll tell you, if it's appear again. Thanks for your attention! By: c0rnoTa (c0rnota) 2013-08-01 06:51:12.399-0500 Excuse me, but I can not reproduce this issue. I don't know what can be wired with it. I think we can close this issue, because it coudn't be reproduced. But I'll tell you, if it's appear again. Thanks for your attention! By: Rusty Newton (rnewton) 2013-08-01 09:50:57.280-0500 Thanks. You can always ping a bug marshal in #asterisk-bugs (irc.freenode.net) as well. | ||