Solved Problems provisioning SNOM PA1

[ASC Admin]

We just set up our 3CX system in the Azure cloud using the PBX Express w/ an SBC running locally.

So far everything has been going swimmingly with one exception.

Our SNOM PA1 does indeed show up on the 'phones' section, but any attempts to assign it to an extension seem to have no effect. The device still shows up as 'new' after we go through the procedure.

We have factory reset the device multiple times, as well as loaded the correct recommended firmware (8.7.5.75).

We need the device to function to facilitate paging through our PA system, so the current state of affairs has us a bit nervous.

All of our Grandstream phones are provisioning just fine through the SBC.

My concern is that there are two different versions of the SNOM PA1 manufactured, and the template is only compatible with the first model.

There are several forum posts detailing similar issues:
here, here, and here, but no resolutions.

I've attempted to put the provision link into the SNOM manually (https://XXXXX.my3cx.us/provisioning/uh1blahblahblahpg/cfg{mac}), to no effect.

The error logs detail several entries hinting at 500 errors:

Mar 15 21:57:35.390 [INFO ] PHN: Config setup: code: 500, uri:

https://XXX.my3cx.us:443/provisioning/uh14blahblahblah3pg/cfg00041blahblah28E7
Mar 15 21:57:35.393 [NOTICE] PHN: Config setup: return code 500; requeueing >https://XXX.my3cx.us:443/provisioning/uh14blahblahblah3pg/cfg000blahblah8D28E7<; attempt: 28, state: 24, duration: 61/68

Is it possible that it is having trouble accessing the https page?

edit:
I managed to load the config file manually. I'm not a huge fan of this option, as it would limit our maleability when it comes to changing SBCs, re-provisioning, or any changes made to our central server. We were hoping to use the SNOM as a multicast relay, but that seems impossible behind an SBC. Am I overthinking it? Is the manual config file fine for a 'set it and forget it' approach?

 

[craigreilly]

If doing solely multicast with this unit - then does it even need to register? Not sure what you are doing with the SNOM.
My SNOM only has Multicast address in it for paging to the Warehouse Bullhorns - and it not registered to my PBX. Hands off approach.

 

[ASC Admin]

That would be great, except multicast configuration for all of the phones (which also need to be included in the page group) is disabled when using an SBC.

 

[craigreilly]

ah yes, that does seem silly doesn't it.

 

[ASC Admin]

As long as the manual config file persists I think we'll be alright. I just need to take rigorous notes in case we need to change ip addresses for the SBC or manipulate the extensions in any way. It sure is a shame. I can't for the life of me figure out why the thing won't provision.

 

[YiannisH_3CX]

Hello @ASC Admin

Can you please navigate to Settings / Security and disable the SSL ciphers setting? Then reset the device and try to auto provision it through PnP.



Let us know if that works for you

 

[ASC Admin]

Wow. That actually worked. I could have sworn that I tried that before to no effect. Thank you kind stranger!

Should I just leave this off? Is there any danger?

 

[cobaltit]

Should I just leave this off? Is there any danger?

Yes, you are in danger of not being PCI compliant if you leave that off.

 

[YiannisH_3CX]

Wow. That actually worked. I could have sworn that I tried that before to no effect. Thank you kind stranger!

Should I just leave this off? Is there any danger?

Glad to see the issue has been resolved. As mentioned, by leaving that option enabled you will not be PCI complaint as that will also enable TLSv1.1 tha older devices need. It is up to you if you want it enabled or disabled.