SNOM PA1 Not Provisioning

[contoured]

Hello there!

I have a SNOM PA1 that I cannot get to provision. I have 3cx v15.5 in google cloud and the SNOM behind a SBC. The PNP is not working. The SNOM does show up in the phones section but when I assign it to a extension it never reboots. I've tried putting in the provisioning link manually but that doesn't work either. I've ensured that the firmware is up today and i've factory reset it multiple times. I've also ensured that the firewall is not a factor either and am not filtering any traffic to or from the SNOM>

I've check the logs of the snom and get the following (url is x'd out):

PL: Socket Error: 11/25/connected, read -> Operation now in progress (150)
29/6/2018 00:32:42 [NOTICE] PHN: webclient:n_tcp_close conn_id:2
29/6/2018 00:32:42 [NOTICE] PHN: Config setup: return code 500; requeueing >https://xxxxxxxxxxxx<; attempt: 2, state: 26
29/6/2018 00:32:45 [NOTICE] PHN: Fetching URL: https://xxxxxxxxxx
29/6/2018 00:32:46 [ERROR ] PHN: TPL: Socket Error: 12/25/connected, read -> Operation now in progress (150)


When I go to the URL listed in the log I get a download for what appears to be the correct config file. Any ideas?

 

[phonemaster]

Hello there!

I have a SNOM PA1 that I cannot get to provision. I have 3cx v15.5 in google cloud and the SNOM behind a SBC. The PNP is not working. The SNOM does show up in the phones section but when I assign it to a extension it never reboots. I've tried putting in the provisioning link manually but that doesn't work either. I've ensured that the firmware is up today and i've factory reset it multiple times. I've also ensured that the firewall is not a factor either and am not filtering any traffic to or from the SNOM>

I've check the logs of the snom and get the following (url is x'd out):

PL: Socket Error: 11/25/connected, read -> Operation now in progress (150)
29/6/2018 00:32:42 [NOTICE] PHN: webclient:n_tcp_close conn_id:2
29/6/2018 00:32:42 [NOTICE] PHN: Config setup: return code 500; requeueing >https://xxxxxxxxxxxx<; attempt: 2, state: 26
29/6/2018 00:32:45 [NOTICE] PHN: Fetching URL: https://xxxxxxxxxx
29/6/2018 00:32:46 [ERROR ] PHN: TPL: Socket Error: 12/25/connected, read -> Operation now in progress (150)


When I go to the URL listed in the log I get a download for what appears to be the correct config file. Any ideas?

Hi,
As I know the Snom PA1 is the old model and doesn't have the TLS v1.2 support, so due that it's a remote server check if you have the "SSL Transport and Ciphers" enabled on 3CX PBX (Settings->Security page). If so, disable it and try again.

 

[contoured]

Thanks for the reply. I didn't see a setting for "SSL Transport and Ciphers" but I did see "Secure SIP/TLS" which I unchecked restarted services and attempted to provision the SNOM again. I'm still getting the same errors.

 

[phonemaster]

Thanks for the reply. I didn't see a setting for "SSL Transport and Ciphers" but I did see "Secure SIP/TLS" which I unchecked restarted services and attempted to provision the SNOM again. I'm still getting the same errors.

No, not the "Secure SIP/TLS". Enable it back.
What is the version of your PBX?
You need to find the "SSL Transport and Ciphers" in the Anti-Hacking tab of the Settings->Security page. Go to that page, scroll down and there you will see the "SSL Transport and Ciphers" feature.

Disable it and try to provision your SnomPA1.

 

[contoured]

I have Professional NFR 15.5.10244.4 and "SSL Transport and Ciphers" options are not there within the Anti-Hacking tab.

 

[phonemaster]

I have Professional NFR 15.5.10244.4 and "SSL Transport and Ciphers" options are not there within the Anti-Hacking tab.

Hi contoured,
I just saw that 3CX published a new version (8.7.5.75) and it has the Let's Encrypt support added.
https://www.3cx.com/support/phone-firmwares/

Update your PA1 to this version and try to provision it again.
BTW, I found the same version on the Snom website, so it's regular and not the 3CX specific version.
http://wiki.snom.com/Firmware/V8_7_5_75_MRU_PA1

Try it and please keep inform due that I'm planning to buy and use them.