recording file name

Status
Not open for further replies.

vitor

Customer
Joined
Jan 3, 2019
Messages
21
Reaction score
0
hello

i need a help
when generating recording calls (for incoming calls) the 3cx creates a file with this name - [01133333%3AMESA%3AMESA]_01133333-8001_20190321130552(203).wav
BUT when I try to do a backup with my FTP server - files with the syntax "%3A" are not uploaded.

its possible to avoid this syntax to be generated at the recording files name?

thanks
Vitor
 
%#A is a HEX Encoding for : which could be problematic with some file systems - especially Windows.

Perhaps the FTP server is trying to convert this to :
 
hello

i need a help
when generating recording calls (for incoming calls) the 3cx creates a file with this name - [01133333%3AMESA%3AMESA]_01133333-8001_20190321130552(203).wav
BUT when I try to do a backup with my FTP server - files with the syntax "%3A" are not uploaded.

its possible to avoid this syntax to be generated at the recording files name?

thanks
Vitor

Hi Vitor,
As @craigreilly said this is the : symbol encoding. Could be that you have this in the name or just from an inbound rule.
Can you please specify the build version of your PBX? And are you referring to the new archive functionality or are you trying manually to upload to your ftp server.
Also please let us know what ftp server you are using and the OS that is running on.
 
Im running 3cx on Windows.
I made a script tô upoad The recording...
The FTP Server is running filezilla server
 
If you wrote a script for this, you'll need to take this into account and properly escape filenames before uploading to ftp.
However, in V16, there is a recording archiving functionality where you can use your ftp server and let the PBX do this for you.
Check this link for more info on this https://www.3cx.com/docs/manual/pbx-management/#h.regwb5464gsv
 
Status
Not open for further replies.

Forum statistics

Threads
111,916
Messages
589,723
Members
164,787
Latest member
IWalter