Post a Reply
1796 views

FOP2 Won't Play Voicemail Files

  1. 13 years ago

    rx4change

    11 Aug 2011

    I am having an issue with FOP2 playing voicemail files. They show up properly in the interface, and I can see a 200/OK in the HTTPD logs when the voicemail file is clicked on:

    "GET /fop2/download.php?file=/var/spool/asterisk/voicemail/default/13/INBOX/msg0000.wav HTTP/1.1" 200 6 "http://www.mysite.com/fop2/wavplayer.swf?gui=none" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.124 Safari/534.30"

    I am running fop2 latest version, 2.21 and my php version is as follows:

    [root@server httpd]# php -v
    PHP 5.2.9 (cli) (built: Jul 19 2010 15:47:18)
    Copyright (c) 1997-2009 The PHP Group
    Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies

    Any ideas on how to resolve this?

    Thx in advance!

  2. admin

    11 Aug 2011 Administrator

    Do you have adobe flash installed and working?

  3. rx4change

    11 Aug 2011

    Yes. Flash is installed and working properly. The browser is Chrome 12, also tried with Firefox 4.

  4. admin

    11 Aug 2011 Administrator

    Perhaps your php sessions are broken.. you can debug by requesting the download.php?xxxxxx directly from your browser and look at the output. If the file starts to download, it must work. If it gives you an error, it will give you an idea of what is going on. If php sessions are broken, the download will fail.

  5. rx4change

    12 Aug 2011

    I was able to resolve an issue with sessions (and my default voicemail format). Now I can play the files properly, but I am still unable to delete them. Any ideas on how to resolve? I am using a NFS mounted directory, but I am able to delete them from the server manually.

    Thanks for all the help.

  6. admin

    12 Aug 2011 Administrator

    Start fop2_server in debug mode, level 511:

    service fop2 stop
cd /usr/local/fop2
script capture.log
./fop2_server -X 511
(try to delete a voicemail)
ctrl-C
exit

    Look at the log file for clues. It could be some restriction in the mailbox/context name (coded in fop2), or perhaps permission issues or nfs bugs/misconfigurations that will be kind of hard to debug.

or Sign Up to reply!