Skip to main content

Snom Provisioning

Posted by techsquared on Tue, 03/09/2010

I'm wondering about how to setup a Snom 320 phone to autoprovision. I understand the thirdlane part of the process and editing the templates before provisioning the phone.

Here is where I'm stuck. When you bring a new phone out of the box, you have to register the Snom phone with Snom to tell it where to point the phone when it boots up to get it's settings. I'm currently using a python script to register the phones to Snom and point them to me.

I see two files in the /unauthenticated/provisioning/ directory that seem relevant to my phone.

snom3xx.cfg and
snom3xx-MACADDRESS.cfg

The current registration with Snom points my phones to an mywebsite.com/prov/MACADDRESS.xml and all the settings are in the single file.

What URL do I register with Snom to have the phones provisioned from the thirdlane PBX manager?

I'm currently using HTTP to provision the phones. Is there a better way, and how do I get the phones to look to the thirdlane server. What URL do I use to pass to the Snom provisioning server.


Submitted by techsquared on Tue, 03/09/2010 Permalink

Here's how it works, in case others are interested.

Once registered, you send the snom3xx.cfg file URL to Snom for the phone, and the phone is built to then add -MACADDRESS and requests the snom3xx-MACADDRESS.cfg file next.

Register with the general settings file with Snom and the rest will work.

Submitted by voicedata on Tue, 03/09/2010 Permalink

I have noticed that Snom's do not normally register right away. I setup 3 demo phones with the auto provisioning and out of 3, one of them registered on the first reboot.

On the other 2, I had to mess around with the button settings in Tools --> Auto Provisioning and reboot the phones a few times to get them to work.

Now I am trying to help a client set his up and we are running into issues there as well. The phone is registering and showing the extension name but he can not dial out. Very weird...the linksys phones seem to be a lot more trouble-free when it comes to auto provisioning.

Submitted by diffen on Wed, 03/10/2010 Permalink

If you do any changes in the provisioning files (add blf button for example) does the snom reads it correctly when you reboot the phone? I cant manage to get the phone to accept new config files.

Submitted by eeman on Wed, 03/10/2010 Permalink

what manner of protocol is the snom using to retrieve its configs? if its tftp are you looking through the logs to verify that its actually retrieving the configs?

Submitted by voicedata on Thu, 03/11/2010 Permalink

I have set mine up with an http:// URL..precisely the URL that is given in System Settings --> Provisioning

It seems to work but it takes a couple reboots for me. In some instances, it works on the first reboot.

Submitted by jesperkjeldsen on Fri, 03/12/2010 Permalink

I had the problem that Snom phones didn't retrieved the config. It was like the system came up and running before the network interface! I was mostly on early 7.xx firmwares, with the newest firmwares I have no problem :-)

Regards
Jesper

Submitted by techsquared on Fri, 03/12/2010 Permalink

When I pull a Snom out of the box and plug it in, it dials home to Snom and Snom tells the phone where to go http://thirdlaneserver/unauthenticated/provisioning/snom3xx.cfg. i don't have to manually put this URL in the snom phone.

I don't have to program the Snom phones before deployment. I don't have to open the box.

What I discovered is that if i point the Snom website to the snom3xx.cfg it will also then point the phone to the snom3xx-MACADDRESS.cfg second. Quite cool.

http://wiki.snom.com/Features/Mass_Deployment

It's awesome and I have a phone register to the phone server within 10-20 seconds of completed boot. It's really quick.