[asterisk-bugs] [JIRA] (ASTERISK-16578) Record audio channels gets out of sync

[xxot-alex (JIRA)]

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

xxot-alex commented on ASTERISK-16578:
--------------------------------------

We have this issue on asterisk 1.8.7.1. It is only SIP, no dahdi. What I noticed, that if I use option "r" in Dial() the unsynchronization is much more worse than without this option. All calls are recorded to wav. Can it somehow be connected with codecs?
                
> Record audio channels gets out of sync
> --------------------------------------
>
>                 Key: ASTERISK-16578
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-16578
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Applications/app_mixmonitor
>            Reporter: Marco Aurelio
>            Severity: Minor
>      Target Release: 1.8.5.0
>
>         Attachments: 620.WAV, configs.txt, scenario.jpg
>
>
> When recording with mixmonitor, some record files channels gets out of sync.
> The scenario was:
> - Medium call traffic: More than 60 and less than 120 concurrent calls.
> - All calls are recorded
> - Codec: Alaw
> - Record File format: WAV GSM
> - Processor load: Never more than 50%
> - Asterisk Version: 1.6.2.10 (also happened in older versions, since 1.4.19)
> - SO Debian 5.0.3 - 2.6.26-2-686
> ****** ADDITIONAL INFORMATION ******
> - The call channels gets out of sync. The customer answers before the agent´s question.
> - The same issue can be reproduced using chanspy. After sometime monitoring one agent, the channels gets ou of sync.
> - Not tryed the same scenario recording WAV format.
> - Not tryed recording WAV GSM format with no call trafic.
> - Also realized the same problem at another customers, with different hardware and Asterisk version (older than 1.4.19)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira