[asterisk-bugs] [JIRA] (ASTERISK-30408) Conflicting filenames in media cache cause wrong prompts to play
Nathan Bruning (JIRA)
noreply at issues.asterisk.org
Fri Jan 27 08:20:03 CST 2023
[ https://issues.asterisk.org/jira/browse/ASTERISK-30408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bruning updated ASTERISK-30408:
--------------------------------------
Description:
We encountered a rare case in which asterisk would play a completely wrong audio file during {{Playback(http://)}}, but only for certain callers.
It turns out that the media cache can get into a situation where two files (from completely different http urls) are stored with the same basename, only differing in extension:
- {{/tmp/bucket-111111.wav}}
- {{/tmp/bucket-111111.wav16}}
Asterisk will then pick one of the two depending on the codec selection of the caller.
I'll provide a patch shortly that makes sure that each cache name (bucket-xxx) is unique for all extensions.
was:
We encountered a rare case in which asterisk would play a completely wrong audio file during `Playback(http://)`, but only for certain callers.
It turns out that the media cache can get into a situation where two files (from completely different http urls) are stored with the same basename, only differing in extension:
```
/tmp/bucket-111111.wav
/tmp/bucket-111111.wav16
```
Asterisk will then pick one of the two depending on the codec selection of the caller.
I'll provide a patch shortly that makes sure that each cache name (bucket-xxx) is unique for all extensions.
> Conflicting filenames in media cache cause wrong prompts to play
> ----------------------------------------------------------------
>
> Key: ASTERISK-30408
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-30408
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_playback, Core/HTTP
> Affects Versions: 20.1.0
> Reporter: Nathan Bruning
>
> We encountered a rare case in which asterisk would play a completely wrong audio file during {{Playback(http://)}}, but only for certain callers.
> It turns out that the media cache can get into a situation where two files (from completely different http urls) are stored with the same basename, only differing in extension:
> - {{/tmp/bucket-111111.wav}}
> - {{/tmp/bucket-111111.wav16}}
> Asterisk will then pick one of the two depending on the codec selection of the caller.
> I'll provide a patch shortly that makes sure that each cache name (bucket-xxx) is unique for all extensions.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list