Re: Call recording using ARI

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

the “recording” directory was missing, and creating it in "/var/spool/asterisk/recording” did solve the issue, thanks.

Still not sure if this is the correct behaviour. I have tried it before giving absolute path like “/tmp/test”, expecting it would try to create the file in “/tmp”, not in "/var/spool/asterisk/recording/tmp”.

So right now, passing “/tmp/test” (absolute) and “tmp/test” (relative) paths have the same effect. 

     Jan Svoboda
     Software Architect

On Monday 22 September 2014 at 21:44, Jakub Wietrzyk wrote:

Date: Mon, 22 Sep 2014 14:29:18 +0200 Jan Svoboda <jan@xxxxxxx> wrote:

Hello,

I have tested recording through ARI and can confirm the same error:

ARI returns Internal Server Error - 500 and Asterisk console the following:

[Sep 22 12:10:52] WARNING[30362]: ari/resource_bridges.c:739 ast_ari_bridges_record: Unrecognized recording error: No such file or directory

I have tried different recording locations with the same result.

I am using Asterisk 12.5.0 on CentOS Linux 6.5, installed using RPM packages from http://packages.asterisk.org/.

Hello Jan,

I compared directory structure between 12.6-rc1 and 12.50:

I have an idea: check if adding:

/var/spool/asterisk/recording

with appropriate permissions is solving your problem.

--
Jakub Wietrzyk

_______________________________________________
asterisk-app-dev mailing list

_______________________________________________
asterisk-app-dev mailing list
asterisk-app-dev@xxxxxxxxxxxxxxxx
http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev

[Index of Archives]     [Asterisk SS7]     [Asterisk Announcements]     [Asterisk Users]     [PJ SIP]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Linux API]

  Powered by Linux