Incoming calls to ring group fail - 3CX V18 locally hosted on Window 10

[compute1]

Dear Colleagues,

We started experiencing this issue recently. Incoming calls to any ring group fail and the call goes to Destination if no answer. The ring group works if called locally from another extension.


The following is in the regular logs:

04/25/2022 12:34:48 PM - [CM503003]: Call(C:354): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5483

04/25/2022 12:34:48 PM - [CM503003]: Call(C:354): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.202:5060

04/25/2022 12:34:48 PM - [CM503003]: Call(C:354): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.239:5060

04/25/2022 12:34:48 PM - [CM503003]: Call(C:354): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.204:5060

04/25/2022 12:34:48 PM - [CM503003]: Call(C:354): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.201:5060

So far I tried everything I found here but no luck.

Your help is highly appreciated.

Ara

 

[leejor]

Who is your VoIP trunk provider? It would seem to be something to do with them, or a 3CX trunk setting that has changed . Have there been any updates, of any sort, about the time this began failing?
Are the sets and 3CX all hosted locally?

 

[compute1]

The VoIP provider is Vitelity.net. Yes the phones and the 3CX are hosted locally. possible it happened after upgrading to V18.

The following are the trunk settings. This was running for 3 year without any problems