5 thoughts on - ControlPlayback Can Not Replay Complicated File Names

• This doesn’t fix the issue, but a work around might be to try using file names without the any : in them

  —–Original Message—

• Seems ‘bug-worthy’ to me.

  Here’s some more confusion using Asterisk 11.8.1:

  Play a file with colons in the file name:

  — Executing [*@default:3] ControlPlayback(“IAX2/6002-1095”, “/tmp/2014-04-10-13:31:03”) in new stack
  — Playing ‘/tmp/2014-04-10-13:31:03.slin’ (language ‘en’)
  — ControlPlayback seek to offset 0 from end

  1) There is no ‘slin’ file, only a ‘wav.’

  2) I didn’t specify any offset. Note that ‘core show application controlplayback’ does not mention anything about seek from end.

  3) No audio is played.

  Play a file with quoted colons:

  — Executing [*@default:3] ControlPlayback(“IAX2/6002-106”, “/tmp/2014-04-10-13\:31\:03”) in new stack
  — Playing ‘/tmp/2014-04-10-13:31:03.slin’ (language ‘en’)
  — ControlPlayback seek to offset 0 from end

  1) No slin file.

  2) No offset.

  3) No audio.

  4) No quotes in ‘Playing’ message.

  — Executing [*@default:3] ControlPlayback(“IAX2/6002-461”, “/tmp/foo”) in new stack
  — Playing ‘/tmp/foo.slin’ (language ‘en’)

  1) Still no slin file.

  2) /tmp/foo.wav is played, audio is heard.

  So…

  1) You should report it as a bug.

  2) Eric’s right — you should not use colons in file names. Even if controlplayback() allowed them, they always seem to cause problems somewhere.

• Many thanks for the testing. I have raised a bug report and we will see if it gains any support.

  The file name as you can imagine is generated from a set of variables, the idea is to make life simple but if the replay tool doesn’t support it the reverse.

  Interesting that Playback() supports complicated file names.

  Regards

  J

  —–Original Message—

• The colon freaks it out, this may be some parsing problem, I bet.

  Jonathan White wrote:

• Yes I changed the format of a variable I use to – which names the file during recording and adds an entry to a database. Luck would have it that the database accepts the format without error and converts it back to :

  —–Original Message—