Solved Recordings stay on Yealink T58A, not saved in 3CX

[apitsos]

Hi there!

I have the following problem. When someone records a call on a Yealink T58 device, the recording is saved locally on the device and not on 3CX, under "Recordings". Is it possible the recordings to be saved on 3CX instead of the local storage of the Yealink IP phone?

Thanks a lot in advance for your help!

 

[JohnS_3CX]

Hi,

Sounds like you are using the built in record function of the phone which is not related to the PBX (it's an independent device based recording).

To have recordings on the extension (so a PBX-stored recording) you will need to enable it under the extension's options - available for professional and enterprise licence systems.

 

[apitsos]

Hi John!

Thanks a lot for the hint. One more question, please. As soon as we want to save that on a remote location, but immediately and not based ona schedule (daily, weekly, etc), Under "Archive Schedule Policy" should we just select "Turn Off"? Because then I see the files not to be saved on the remote SMB location.

 

[JohnS_3CX]

Yes you can turn it off and it will only archive them when you select the recordings and press the "Archive" button.

Once archived, a little book icon will appear next to the recording

 

[apitsos]

I see. I thought that turning that off will save the recording to the remote location. So the only option I see there is to archive them once per day. Can't do it sooner or immediately. Right?

 

[JohnS_3CX]

If you want the recordings to ALWAYS be saved on a remote location, you can mount a remote drive to your 3CX instance machine, and point the Local Recordings Folder to that drive.

Note that we only support block-level devices like SAN (or iSCSI). So don't mount a regular NAS/SMB or other file-level storage system. The data integrity of the recordings cannot be guaranteed and you may encounter unrecoverable file corruption.

Otherwise you can simply do daily archiving which provides more flexibility in terms of storage location types like FTP/S, SMB, Google Buckets (Avoid Google Drive - support for it is being deprecated)

 

[apitsos]

HI John,

Once again, I would like to thank you for your kind support. According to my understanding it would be better to have a Windows installation instead of a Debian on a working environment with Windows systems, especially when we have such complicated requests, that require some kind of customization on an OS level. Then I could just make a map drive in Windows and save the recordings in F:\3CX-Recordings or whatever...

Please consider this thread as solved. Wishing you all the best!

 

[JohnS_3CX]

Ah, simply mapping a drive is still SMB though, that's file-level access and you run the risk of incomplete/corrupted recordings. You either need a physical drive, or a SAN type remote drive that provides block-level access.

So the challenge remains the same regardless of OS, and using Windows would just make the VM use more resources unnecessarily in this case.

 

[apitsos]

But setting up an iSCSI connection to a Windows Server (as soon as we enable iSCSI host role on it) isn't much more easier to do it on a Windows 3CX machine, instead of a Debian? At least I have no knowledge of how to connect a Debian OS to an iSCSI host.

 

[JohnS_3CX]

Oh in that case no problem, I thought you meant mount a simple SMB location when you said to map a drive.

 

[apitsos]

That was what I meant initially. But I didn’t realize that it was also a problem. Anyway… thanks for everything! I really appreciate that great support you provide here.

 

[JohnS_3CX]

You're welcome! Once you setup your iSCSI Windows Server host, try googling how to connect a debian client to it and mounting the drive. Might not be too bad once you learn how to do it, and it means you can have the flexibility to deploy both types of OS in the future for your clients.

Note that Debian supports an additional feature that you might find useful if managing multiple PBX deployments, this may interest you in the future: https://www.3cx.com/docs/manual/pbx-management/#h.qfash562493e/

 

[apitsos]

You're welcome! Once you setup your iSCSI Windows Server host, try googling how to connect a debian client to it and mounting the drive. Might not be too bad once you learn how to do it, and it means you can have the flexibility to deploy both types of OS in the future for your clients.

Sounds a good idea. I will give a try as soon as I can. Thanks a lot!

Note that Debian supports an additional feature that you might find useful if managing multiple PBX deployments, this may interest you in the future: https://www.3cx.com/docs/manual/pbx-management/#h.qfash562493e/

I was aware of that, but for sure is a good option. I will do that for all of our installations.