Jump to content

Snom 821 Provisioning on SnomONE


participant
 Share

Recommended Posts

  • 1 month later...

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  • 2 weeks later...

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

Link to comment
Share on other sites

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" />

Link to comment
Share on other sites

  • 3 weeks later...

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...