[asterisk-bugs] [JIRA] (ASTERISK-18286) [patch] 'Silence' is truncated in Record()

[Kevin Harwell (JIRA)]

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

Kevin Harwell updated ASTERISK-18286:
-------------------------------------

    Target Release Version/s:     (was: 13.4.0)

> [patch] 'Silence' is truncated in Record()
> ------------------------------------------
>
>                 Key: ASTERISK-18286
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18286
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_record
>    Affects Versions: 1.8.6.0
>         Environment: Debian 6.0.4, kernel 2.6.32-5-686, dahdi-tools-2.6.0, dahdi-linux-2.6.0, libpri-1.4.12
>            Reporter: var
>            Severity: Minor
>      Target Release: 13.15.0, 14.4.0
>
>         Attachments: app_record-1.8.6.0.diff, app_record-1.8.6.0-doc.diff, app_record-1.8.6.0-final.diff, app_record-1.8.6.0-final.diff, app_record-1.8.7.1.diff, app_record.diff
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> When using Record with the silence detection feature, the stream is written out to the given file. However, if only 'silence' is detected, this file is then truncated to the first second of the recording (8016 bytes for alaw e1).
> This causes a problem for IVR applications, even if only silence is detected it can still be of use in data collection as silence may not really be all silence (e.g. someone talking quietly) or this data is utilised for other verification reasons. Silence detection should not have right to remove any recorded data, at the very least it should be a configuration or argument option.
> See ticket ASTERISK-17522 for pre-dated 1.6.2.x issue, this ticket contains 1.8.5.0 patch instead of the 1.6.2.17 patch.



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