Unable To Provision Snom PA1 - HTTPS problems?

Status
Not open for further replies.

Bernie Wright

Joined
Apr 16, 2018
Messages
4
Reaction score
0
Hello,

I am having a very similar issue like the post listed below, but I don't see where the other user found a solution.
https://www.3cx.com/community/threads/provisioning-snom-pa1-problem.58820/

I am trying to provision a Snom PA1 device. My server is remote so I'm trying to connect it via "Direct SIP - Stun Remote". The log file of the Snom device shows that it's not connecting, and I believe it has to do with the 3CX server needing HTTPS and the Snom can't communicate correctly with it.

I've already updated the firmware
I've already run a factory reset
I've ensured that I do not have "Enable PCI compliance SSL Transport and Ciphers" checked on the 3CX server.

These are what my log files look like with certain info masked for privacy.

Nov 27 10:07:28.051 [NOTICE] PHN: Fetching URL: https://companyname.bvoip.net:443/provisioning/blahblahblah

Nov 27 10:07:28.057 [WARN ] PHN: Could not resolve host >companyname.bvoip.net<

Nov 27 10:07:28.058 [WARN ] WEBCLIENT: Could not resolve host companyname.bvoip.net

Nov 27 10:07:28.060 [INFO ] PHN: Config setup: code: 400, uri: https://companyname.bvoip.net:443/provisioning/blahblahblah

Nov 27 10:07:28.063 [NOTICE] PHN: Config setup: return code 400; giving up on >https://companyname.bvoip.net:443/provisioning/blahblahblah<

Nov 27 10:07:28.064 [NOTICE] PHN: SetProvisioningDone

The device also isn't appearing in the phones listing on my 3CX server. I can see it under the extension, but not as a phone.

On the dashboard of the 3CX server, I am getting this message.

"3CX Phone System Management Console ID: 10018
RPS request for Snom PA1 IP Phone of Paging Address (###) delivered successfully"

Any ideas?

Thanks,
Bernie
 
Are you putting the 443 in the URL - or is that in a port field? I haven't programmed a Snom in a while. If in the URL - tried without as 443 is default?

Assuming manual provisioning?

Unfortunately I now only use the Snom for Multicast Broadcasting.
 
Thank you for your reply!

That 443 in the URL is not in my provisioning URL that I entered. I'm guessing it's being added from somewhere else. I forgot to mention that I couldn't install the firmware using https:// and I had to change it to http://

That's part of why I'm thinking that could be part of the issue.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,901
Messages
589,636
Members
164,768
Latest member
Eagle Man