[asterisk-bugs] [JIRA] (ASTERISK-18077) When in queue on g722 with interruptions, music on hold can get stuck and no longer play

[Joshua Colp (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-18077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238313#comment-238313 ] 

Joshua Colp commented on ASTERISK-18077:
----------------------------------------

[~sesom42] Please file a new issue with details instead of commenting on this.

> When in queue on g722 with interruptions, music on hold can get stuck and no longer play
> ----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-18077
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18077
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue, Codecs/codec_g722, Formats/format_pcm, Resources/res_musiconhold
>         Environment: Ubuntu 10.04 32 bit
>            Reporter: Jonathan Rose
>            Assignee: Kinsey Moore
>            Severity: Minor
>         Attachments: extensions.conf, jrose_Jun30_2011_g722_moh_patch.diff, queuemohstop.diff, queuemohstop.diff, queues.conf, sip.conf
>
>
> With a g722 call connected to the queue in the attached file, after listening up to the end of the second song, the music on hold will be interrupted by a generic Allison message about representatives being busy and once the message concludes, the following error will show up:
> WARNING[16606]: format_pcm.c:140 pcm_seek: offset too large 2303040, truncating to 2232088
> and at this point, the music will not resume and interruptions will continue as normal.  That message will continue to play with those same values after each interruption.
> I'm including a patch which fixes the issue, but I don't really believe this is necessarily the correct approach.  I think it would probably be more prudent to detect when the file is being started at the end and begin at the beginning of the next file instead.



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