Local 3CX V20 not functional outside the network

[RechDevi001]

Good morning,

I installed a 3CX Debian server locally.
The firewall test is successful, and provisioning the 3CX Windows application on the same network works perfectly.

However, as soon as I leave the local network, provisioning via QR code for the mobile application does not work. The 3CX web server appears to be either unreachable or inaccessible from the outside.
The problem is the same for:

the Windows application,
IP phones (Yealink T42S and Yealink T53), which also fail to provision.
If anyone has any thoughts or, better yet, a solution to offer me, I would be very grateful.

Thank you in advance and have a nice day.

 

[Alphabetic]

Have you made any restrictions on your port forwarding and does the FQDN externally resolve to your WAN Address.

 

[RechDevi001]

Thank you for your attention, it’s very nice of you.

I don't think I made any particular restrictions regarding port forwarding. I simply followed the procedure in the manual (3cx)

Regarding FQDN externally resolve to my WAN Address, I'm not sure I understood the question correctly.
The firewall correctly resolves the names outside the network and from outside the network an nslookup to the 3cx server works, I obtain is public IP address.

 

[Alphabetic]

Can you perform the firewall test again? Do you have any errors in event log?

 

[AWS2P]

Did you install a split dns as required for on premise install?
if so a Nslookup FQDN should resolve on local IP when on LAN and public Ip when on WAN is it what you get ?

 

[RechDevi001]

to respond to Alphabetic, I did a firewall test just now.
all is ok.
in the event log no error. :/

Aws2p, thanks for your attention,
Yes I installed a split DNS as indicated in the 3CX documentation.
I have a result with nslookup in the network and outside the network with 3CX FQDN.

 

[AWS2P]

is it a fresh V20 PBX or was it in V18 and upgraded to V20 ?

 

[RechDevi001]

a fresh V20,
a fresh debian who is used with the 3cx ISO to be precise