Hi, all,
Here's a background:
I have a self-hosted 4SC Pro Version 20.0 Update 5 (Build 551 Release) system in Google Cloud Platform running Debian 12.
It was created October 2024 from the Google Cloud marketplace using the deployment that the 3CX team has there.
It has 3 Yealink T46S desk phones connected through an SBC to the 3CX phone system. The SBC is running Windows 11 Pro.
I'm using Flowroute as a VoIP provider.
It has 3 Outbound Rules (keep in mind this is for the US):
One when redialing a phone number that comes with a + sign, a second to dial phone numbers by adding 1 as required by the VoIP provider, and the third to dial a phone number the "regular" way (a 10-digit phone number starting with the 3-digit area code).
Now the issue:
The last Outbound Rule has been working since the beginning, but starting last Friday, May 30, 2025, it stops working.
When dialing a phone number as 201-xxx-xxxx, it shows "No Route Exists" on the 3CX side and "603: Network Blocked" on the VoIP provider side.
I've deleted all the Outbound Rules and the VoIP provider and started from scratch, but no clue as to why it stops working.
I've made some test calls from another self-hosted 3CX phone system I have access to.
This other 3CX instance has the same version and operating system, and it has similar outbound rules.
Calls on this second 3CX instance went through.
Any thoughts,
Thank you!
Here's a background:
I have a self-hosted 4SC Pro Version 20.0 Update 5 (Build 551 Release) system in Google Cloud Platform running Debian 12.
It was created October 2024 from the Google Cloud marketplace using the deployment that the 3CX team has there.
It has 3 Yealink T46S desk phones connected through an SBC to the 3CX phone system. The SBC is running Windows 11 Pro.
I'm using Flowroute as a VoIP provider.
It has 3 Outbound Rules (keep in mind this is for the US):
One when redialing a phone number that comes with a + sign, a second to dial phone numbers by adding 1 as required by the VoIP provider, and the third to dial a phone number the "regular" way (a 10-digit phone number starting with the 3-digit area code).
Now the issue:
The last Outbound Rule has been working since the beginning, but starting last Friday, May 30, 2025, it stops working.
When dialing a phone number as 201-xxx-xxxx, it shows "No Route Exists" on the 3CX side and "603: Network Blocked" on the VoIP provider side.
I've deleted all the Outbound Rules and the VoIP provider and started from scratch, but no clue as to why it stops working.
I've made some test calls from another self-hosted 3CX phone system I have access to.
This other 3CX instance has the same version and operating system, and it has similar outbound rules.
Calls on this second 3CX instance went through.
Any thoughts,
Thank you!
