[asterisk-bugs] [JIRA] (ASTERISK-27774) res_musiconhold: Music on hold restarts after every announcement

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-27774:
-----------------------------------

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

Have you only seen this under realtime music on hold or also with file based?

> res_musiconhold: Music on hold restarts after every announcement
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-27774
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27774
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_musiconhold
>    Affects Versions: 15.3.0
>            Reporter: lvl
>            Assignee: lvl
>
> The fix for ASTERISK-24329 is causing a regression during "regular" music on hold behavior.
> Imagine a simple musiconhold setup, configured via realtime.
> {code}
> +--------+-------+------------------------+-------+
> | name   | mode  | directory              | sort  |
> +--------+-------+------------------------+-------+
> | 82497  | files | /ext/moh/82497         | alpha |
> {code}
> In /ext/moh/82497 are one or more audio files with a length of around 3 minutes. If a queue is configured with a periodic announcement every 30 seconds, the following will occur:
> * Caller hears music on hold file #1, playing from the beginning
> * After 30 seconds, the caller will hear the announcement
> * Caller hears music on hold file #1, playing from the beginning
> * After 30 seconds, the caller will hear the announcement
> * ...
> E.g., if the periodic announcement is made every 30 seconds the caller will only ever hear the first 30 seconds of music on hold over and over again.
> I don't fully understand the issue reported in ASTERISK-24329, but if this new behavior is indeed desirable in some cases I think it should be made configurable with the default behavior reverted back to how it was in 15.2.



--
This message was sent by Atlassian JIRA
(v6.2#6252)