[asterisk-bugs] [JIRA] (ASTERISK-28240) Unexpected unhold when Asterisk cannot find the moh-files
Sean Bright (JIRA)
noreply at issues.asterisk.org
Tue Jan 15 11:19:47 CST 2019
[ https://issues.asterisk.org/jira/browse/ASTERISK-28240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245974#comment-245974 ]
Sean Bright commented on ASTERISK-28240:
----------------------------------------
While I haven't tested it, I believe this is similar to the behavior one would see if there was a music class defined with no files at all. What do you feel the behavior should be when this occurs?
> Unexpected unhold when Asterisk cannot find the moh-files
> ---------------------------------------------------------
>
> Key: ASTERISK-28240
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28240
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: . I did not set the category correctly.
> Affects Versions: 13.16.0, 13.20.0
> Reporter: Martin Nyström
> Severity: Minor
>
> Given the following scenario
> 1) Customer calls Agent A
> 2) Agent A holds customer
> 3) Agent A calls an external party
> If Asterisk cannot find the MusicOnHold files, asterisk will stop MusicOnHold and the Customer will barge into the call between Agent A and the external party (3).
> [2019-01-11 15:06:55] VERBOSE[2510][C-00006428] res_musiconhold.c: Started music on hold, class 'default', on channel 'SIP/trunk-0000a992'
> [2019-01-11 15:06:55] WARNING[2510][C-00006428] file.c: File /var/lib/asterisk/moh/reno_project-system does not exist in any format
> [2019-01-11 15:06:55] WARNING[2510][C-00006428] res_musiconhold.c: Unable to open file '/var/lib/asterisk/moh/reno_project-system': No such file or directory
> [2019-01-11 15:06:55] VERBOSE[2510][C-00006428] res_musiconhold.c: Stopped music on hold on SIP/trunk-0000a992
> This issue can be replicated by simply setting musiconhold on a queue, then moving the moh-file away from /var/lib/asterisk/moh without performing an CLI moh reload.
> This has been tested and replicated in Asterisk 13.16 and Asterisk 13.20.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list