[asterisk-bugs] [JIRA] (ASTERISK-19802) Fails to set WRITE mode correctly, skips first file to be played when format is ULAW.

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-19802:
-----------------------------------

    Affects Version/s: 13.18.4

> Fails to set WRITE mode correctly, skips first file to be played when format is ULAW.
> -------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19802
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19802
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_meetme
>    Affects Versions: 1.8.11.1, 13.18.4
>         Environment: No hardware. Just Centos, Asterisk, Dahdi & Tools
>            Reporter: alexr1
>            Severity: Minor
>         Attachments: fail.txt, success.txt, weird.txt
>
>
> I have noticed an issue with MEETME (realtime/Dynamic conferences) on Asterisk 1.8 - I allow ULAW and ALAW only.
> Under certain conditions, Asterisk fails to set the channel WRITE mode correctly resulting in the failure to play the FIRST sound file using play_and_record. Subsequent sound files are OK. If the channel WRITE mode is set in advance by another application before MEETME, then the problem does not exist.
> If a call comes in on ALAW. Everything works OK as per success.txt. If the call comes in on ULAW, something goes wrong and Asterisk SKIPS the vm-rec-name.gsm and plays beep.gsm instead and begins recording as per fail.txt
> I just restricted the codecs to ALAW only, and now I actually hear the first fraction of a second of audio before the beep "At<beep>". I have attached it as weird.txt



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