Hosted (pbxexpress) failing SIP ALG and Full Cone test

[newark]

Any ideas what would cause this? We have one pbxexpress installation on ovh that is suffering from an inability to make or receive calls on any extension - calls connect but are silent.

Checking the firewall checker (which has an alert icon on the dashboard) shows a bunch of failures:

resolving 'stun-eu.3cx.com'... failed (How to resolve?)
resolving 'stun2.3cx.com'... done
resolving 'stun3.3cx.com'... done
resolving 'sip-alg-detector.3cx.com'... done
testing 3CX SIP Server... failed (How to resolve?)
stopping service... done
detecting SIP ALG... failed (How to resolve?)
testing port 5060... full cone test failed (How to resolve?)
starting service... done
testing 3CX Tunneling Proxy... done
stopping service... done
testing port 5090... done
starting service... done
testing 3CX Media Server... failed (How to resolve?)
stopping service... done
testing ports [9000..9255]... failed (How to resolve?)
testing port 9000... done
testing port 9001... done
testing port 9002... done
testing port 9003... done
testing port 9004... done
testing port 9005... done
testing port 9006... done
testing port 9007... done
testing port 9008... done
testing port 9009... done
testing port 9010... done
testing port 9011... done
testing port 9012... done
testing port 9013... done
testing port 9014... done
testing port 9015... done
testing port 9016... full cone test failed (How to resolve?)
testing port 9017... done
testing port 9018... done
testing port 9019... done
testing port 9020... full cone test failed (How to resolve?)
testing port 9021... done
testing port 9022... done
testing port 9023... done
testing port 9024... not reachable (How to resolve?)
testing port 9025... done
testing port 9026... full cone test failed (How to resolve?)
testing port 9027... not reachable (How to resolve?)
testing port 9028... full cone test failed (How to resolve?)
testing port 9029... done
testing port 9030... done
testing port 9031... done
testing port 9032... done
testing port 9033... not reachable (How to resolve?)
testing port 9034... done
testing port 9035... done
testing port 9036... done
testing port 9037... done
testing port 9038... done
testing port 9039... full cone test failed (How to resolve?)
testing port 9040... done
testing port 9041... done
testing port 9042... full cone test failed (How to resolve?)
testing port 9043... full cone test failed (How to resolve?)
testing port 9044... done
testing port 9045... done
testing port 9046... done
testing port 9047... full cone test failed (How to resolve?)
testing port 9048... done
testing port 9049... done
testing port 9050... full cone test failed (How to resolve?)
testing port 9051... full cone test failed (How to resolve?)
testing port 9052... done
testing port 9053... full cone test failed (How to resolve?)
testing port 9054... full cone test failed (How to resolve?)
testing port 9055... done
testing port 9056... not reachable (How to resolve?)
testing port 9057... done
testing port 9058... done
testing port 9059... full cone test failed (How to resolve?)
testing port 9060... done
testing port 9061... done
testing port 9062... full cone test failed (How to resolve?)
testing port 9063... done
testing port 9064... done
testing port 9065... done
testing port 9066... done
...and so on

 

[eddv123]

I use AWS for hosting and you have a basic set of ACL's called security groups to configure from the actual platform.

This is for standard port forwarding. There is nothing in regards to SIP ALG required on the platform - SIP ALG is more for actual hardware routers and firewalls so it is strange that you are seeing this. I don't use PBX Express however so not sure how much flexibility you have.

I would however expect a system based on OVH to be no different as a platform provider.

 

[newark]

Well that's the thing, we have multiple pbxexpress installs on OVH and this is the only problem one.

My concern is that there's something 'broken' about this one - either networking or with the VM's OS, but I don't really know what to even look for

 

[YiannisH_3CX]

You can check the ip tables of the instance and compare them to a working one. Also try running the checker again as there was an issue with the SIP ALG checker that has now been resolved.

 

[newark]

Scratch that, I'll ssh instead it'll be easier

 

[YiannisH_3CX]

Let us know what you find