Then the gateway is either not set to register with the correct FQDN / IP, cannot resolve the FQDN (DNS issue), or is being blocked (blacklisted?) at the 3CX end. you might want to use Wireshark, or if available, any logging, within the gateway, to help troubleshoot.
Thank you for the prompt reply, I used Wireshark and got the following captured (3CX server IP: 185.137.246.52, GS FXO Gateway IP: 185.137.246.51)
3174 74.882732 185.137.246.51 185.137.246.52 TCP 60 4097 → 5000 [SYN] Seq=0 Win=8192 Len=0 MSS=1452
3175 74.882797 185.137.246.52 185.137.246.51 TCP 58 5000 → 4097 [SYN, ACK] Seq=0 Ack=1 Win=65340 Len=0 MSS=1460
3177 74.885051 185.137.246.52 185.137.246.51 HTTP 359 HTTP/1.1 403 Forbidden (text/html)
3178 74.885074 185.137.246.52 185.137.246.51 TCP 54 5000 → 4097 [FIN, ACK] Seq=306 Ack=169 Win=65172 Len=0
3285 77.104801 185.137.246.51 185.137.246.52 TCP 60 [TCP Retransmission] 4097 → 5000 [FIN, ACK] Seq=169 Ack=307 Win=8191 Len=0
3287 77.107009 185.137.246.51 185.137.246.52 TCP 60 [TCP Dup ACK 3180#1] 4097 → 5000 [ACK] Seq=170 Ack=307 Win=8191 Len=0
------------------------------------------------------------------------------------------------------------------------------------
It seems 3CX is getting HTTP 403 error from gateway, does that ring any bell?
3CX and gateway configuration attached :
Im not using FQDN but using the IP, also I replaced the FQDN with IP in the provisioning link