Recordings Download URL Changed

[Josh Smith]

So, I have put in a LOT of time integrating our CRM (SuiteCRM) and 3CX completely server side. I also have a CRON job setup to use LAME to convert all .wav recordings to MP3. All call logs, recording links, and event logs are managed in our CRM. Because of the MP3 conversion, our CRM must be used to download mp3 recordings since the original wav file gets converted and deleted. This has worked BEAUTIFULLY for over a year until something changed last week.

Now, when I go to the download the MP3 recording

https://pbx.pbxurl.com/#/download_record/nameofrecording.mp3

It will show this:

"...page can’t be found
No webpage was found for the web address:https://pbx.pbxurl.com/api/RecordingList/DownloadRecord?file=nameofrecording.mp3"

All integration is done with CRON jobs, shell scripts, and SQL scripts. It is extremely important for me to get this working as upper management is getting frustrated that they cannot download any recordings.

 

[edossantos]

Hello Josh Smith,

Create a new call details report, and go to the recording link. See how it has changed, and update your scripts accordingly.

Kind regards.

 

[Josh Smith]

The URLs have not changed in the reports. I already compared them to see if that changed. If I rename one of the MP3 files to .wav it will allow it to download. It seems the latest update added some type of extra security that isn’t allowing the MP3’s to be downloaded, only the original WAV files. The permissions on the MP3’s are set to phonesystem, it stopped after this last update.

 

[edossantos]

Yes, that's very possible... You should download the WAV file and convert it to MP3 once you have it in your server.

 

[Josh Smith]

Is there any way to find out what changed in 3CX so I can still store the recordings on the phone server?

The conversion and storage for the recordings has always been on the phone system and I would prefer to keep it that way. The URLs to the recordings is stored in our CRM.

 

[edossantos]

You can check the nginx configuration, and update it as you wish, at your own risk. Please note that this is not a supported procedure, we can't help you with that.