Solved 3CX Ring Time issue

[vtxdigital]

Hello,
I have had a strange issue since restoring a backup of my 3CX system from a Raspberry Pi to a Debian Hyper-V VM so that it could be included into my veeam backups.
The system works in every way except that unless the ring time on extensions / the ring group before forwarding to voicemail is set in the hundreds it will ring twice and go to voicemail.
I have tried incrementally increasing the ring time upwards from the ideal 20s all the way up to 200s which the soft phones will finally ring.

When looking at the activity log I just keep getting the below for the times that I have called in (Internal and external)

06/04/2021 22:49:20 - [CM503003]: Call(C:19): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

I have also tried placing an IVR in front of the ring group to see if that makes a difference but still just stops after two rings (Which show up on the softphone receiving the calls) and goes to the extensions voicemail.

Any help would be massively appreciated as I have been scrounging around the forums for 2 weeks now

 

[VasilisV_3CX]

Hi @vtxdigital,

Can you create a completely new extension, with default settings. Only log in to the extension using the Web Client (not Windows Client), and make a test call to it. Does it exhibit the same behaviour?

Also please ensure that you've followed our guide, as it can cause problems if NTP is not correctly set up: https://www.3cx.com/docs/installing-microsoft-hyper-v/#h.cjj20zk71lns

 

[vtxdigital]

Hi @vtxdigital,

Can you create a completely new extension, with default settings. Only log in to the extension using the Web Client (not Windows Client), and make a test call to it. Does it exhibit the same behaviour?

Also please ensure that you've followed our guide, as it can cause problems if NTP is not correctly set up: https://www.3cx.com/docs/installing-microsoft-hyper-v/#h.cjj20zk71lns

Hi Vasilis,
Sorry for the late reply
I have done as requested and that sorted it. Looks like NTP wasnt installed on my Debian installation but after installing and rebooting the VM the call time acts as it should do

 

[VasilisV_3CX]

Hi @vtxdigital,

Great to hear that you that you've solved the issue! Feel free to open another thread if you require any further assistance.