[asterisk-bugs] [JIRA] (ASTERISK-22191) wrong timing for periodic announcement in queue

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-22191:
------------------------------------

    Assignee: c0rnoTa
      Status: Waiting for Feedback  (was: Triage)

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}
                
> wrong timing for periodic announcement in queue
> -----------------------------------------------
>
>                 Key: ASTERISK-22191
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22191
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 1.8.22.0
>         Environment: OS Linux Gentoo x86_64 on hardware server DL180
> Realtime SIP agents in queue with strategy ringall.
>            Reporter: c0rnoTa
>            Assignee: c0rnoTa
>            Severity: Minor
>         Attachments: verbose_queue
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira