Snom 821 Provisioning on SnomONE

[participant]

Hello,

 

I got the Snom 821 today and tried to use auto provisioning with the SnomONE Free. It doesn't work.

I have also a Snom 370. Here the auto provisioning makes no problems.

 

Any idea?

 

Cheers,

Andreas

[Vodia PBX]

It could be that you got a old version. What is the version number (and OS)?

 

 

[Denis]

I have the same issue and need some help as well.

 

I am not able to provision any 8xx phones. Snom 3xx phones seem to work fine.

 

I am on SnomONE Blue and Free, windows and linux and get the same issue and downloaded the latest verion today and still have he same issue. Seems like the 8xx template files are not their or I can't find them. I can't find the 3xx templats in any of the directories so not sure what to add to get this working.

 

Is there a way to add custom files to make some changes to the base configuration files and where are they?

 

Any help will be appreaciated. Cutover this weekend is on the line.

Thanks for your help.

[Vodia PBX]

If you dont have the snom_821.xml file in the reg_texts.htm web page listed, create a html directory in the working directory of the PBX (where you also have audio_en, audio_moh and so on) and put the file snom_821.htm there with the following content:

 

<?xml version="1.0" encoding="utf-8"?>
<setting-files>
 <file url="{http-url}/snom_3xx_fw.xml?model=snom821" />
 <file url="{https-url}/snom_820_phone.xml?model=snom821" />
 <file url="{https-url}/snom_820_fkeys.xml?model=snom821" />
 <file url="{https-url}/snom_web_lang.xml?model=snom821" />
 <file url="{https-url}/snom_gui_lang.xml?model=snom821" />
</setting-files>

 

It could be that this file did not make it into the build, we have seen that in other places too.

[Denis]

If you dont have the snom_821.xml file in the reg_texts.htm web page listed, create a html directory in the working directory of the PBX (where you also have audio_en, audio_moh and so on) and put the file snom_821.htm there with the following content:

 

<?xml version="1.0" encoding="utf-8"?>
<setting-files>
 <file url="{http-url}/snom_3xx_fw.xml?model=snom821" />
 <file url="{https-url}/snom_820_phone.xml?model=snom821" />
 <file url="{https-url}/snom_820_fkeys.xml?model=snom821" />
 <file url="{https-url}/snom_web_lang.xml?model=snom821" />
 <file url="{https-url}/snom_gui_lang.xml?model=snom821" />
</setting-files>

 

It could be that this file did not make it into the build, we have seen that in other places too.

 

 

Thanks for your help.

I will give it a try.

[iActive]

Thanks for your help.

I will give it a try.

 

same problem here. we are not able to auto provision the snom821 but our Snom300's work just fine. Tried the mentioned solution and that does not work either. Can anyone help with this?

[Vodia PBX]

We will probably provide a new software build by the end of this week, which will include stuff like the missin 821 support.

 

 

[venom]

We will probably provide a new software build by the end of this week, which will include stuff like the missin 821 support.

We have had success auto provisioning 3xx, 821 and 870 phones with build .3969. The only issue we have noted is that the file snom821.htm that is generated seems like it is missing the last line to direct the phones to the tftp directory for the custom file. The 300 and 870 htm files have this line and they pick up their custom settings. Is it possible we missed a setting for the 821's?

 

TIA

[Vodia PBX]

Which file is missing? The 821 pretty much provisions like the 820, it should be only the first file that is missing the rest is like 820. Check out the generated directory which files are there.

[pbx support]

We have had success auto provisioning 3xx, 821 and 870 phones with build .3969. The only issue we have noted is that the file snom821.htm that is generated seems like it is missing the last line to direct the phones to the tftp directory for the custom file. The 300 and 870 htm files have this line and they pick up their custom settings. Is it possible we missed a setting for the 821's?

 

TIA

 

Oh, you mean the snom_821_custom.xml file? That is not really needed unless you are doing some customization for all the 821s. We will add that to the next version. But meanwhile if you need it, you can always update the snom_821.xml file that was mentioned in the couple of posts earlier to have the following line

<file url="{https-url tftp}/snom_821_custom.xml" />

[participant]

Hello,

 

is there any news on that? My 821 is not really gone to be auto provisioned. Or do you have some advice?

 

Regards,

Andreas

 

We will probably provide a new software build by the end of this week, which will include stuff like the missin 821 support.

[mattlandis]

http://wiki.snomone.com/index.php?title=Upgrades

[venom]

Oh, you mean the snom_821_custom.xml file? That is not really needed unless you are doing some customization for all the 821s. We will add that to the next version. But meanwhile if you need it, you can always update the snom_821.xml file that was mentioned in the couple of posts earlier to have the following line

<file url="{https-url tftp}/snom_821_custom.xml" />

 

I tried following the steps pbxnsip provided above to create /usr/local/snomONE/html/snom821.htm. I created a file that looks like this...

 

<?xml version="1.0" encoding="utf-8"?>
<setting-files>
 <file url="{http-url}/snom_3xx_fw.xml?model=snom821" />
 <file url="{https-url}/snom_820_phone.xml?model=snom821" />
 <file url="{https-url}/snom_820_fkeys.xml?model=snom821" />
 <file url="{https-url}/snom_web_lang.xml?model=snom821" />
 <file url="{https-url}/snom_gui_lang.xml?model=snom821" />
 <file url="{https-url tftp}/custom_snom_821.xml" />
</setting-files>

 

I also created /usr/local/snomONE/tftp/custom_snom_821.xml

 

<?xml version="1.0" encoding="utf-8"?>
<settings>
<phone-settings>
<!-- Test param -->
<auto_dial perm="RW">on</auto_dial>
</phone-settings>
</settings>

 

The snom821.htm file in the Generated folder does not contain the additional xml file node pointing to the custom file. Any guidance would be appreciated.

 

I'm using .3981 thanks to mattlandis. I've disconnected our test 821, deleted the extension's folder within Generated, restarted the PBX service and booted the phone.

[pbx support]

PBX will not generate any file based on your custom file. All it does is to send the your custom file (/usr/local/snomONE/tftp/custom_snom_821.xml) to phone during the phone reboot.

 

Not sure if that's what you are asking here.

[venom]

We're not asking the PBX to generate a custom file. As I mentioned above, I manually created both of those files. The ultimate goal here is to be able to have a custom config file for 821 phones that we can deploy on multiple snomONE systems.

 

For example, we want to adjust the idle screen brightness on every 821 we install.

 

EDIT: I just realized our file naming convention is different than pbxnsip's post above. Is that critical? My assumption was that I could use whatever name I wanted for the custom file.

[Vodia PBX]

Better dont put those files into the html directory, edit the files in the web interface instead. They override the file-based and built-in templates and that might cause the confusion.

[venom]

Better dont put those files into the html directory, edit the files in the web interface instead. They override the file-based and built-in templates and that might cause the confusion.

 

That was our first thought as well. However, there isn't a snom821.xml file in the web templates area. There is only a snom820.xml file which is similar but distinctly different xml declartions. Is it possible for us to add a base snom821.xml file to the web templates area?

[Vodia PBX]

Hmm. The 820 and 821 models have the same keys and the same functionality, thats why there is no differentiation between them. It should be okay to use the snom_820_custom.xml file to get this job done.