Iruwen Posted March 2, 2018 Report Share Posted March 2, 2018 https://vodia.com/doc/pnp_customization <?xml version="1.0" encoding="utf-8"?> <setting-files> <file url="{http-url}/snom_3xx_fw.xml?model=snom360" /> <file url="{https-url}/snom_3xx_phone.xml?model=snom360" /> <file url="{https-url}/snom_3xx_fkeys.xml?model=snom360" /> <file url="{https-url}/snom_web_lang.xml?model=snom360" /> <file url="{https-url}/snom_gui_lang.xml?model=snom360" /> <file url="{https-url tftp}/snom_360_custom.xml" /> </setting-files> What does the "model=snom360" parameter actually do here? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 2, 2018 Report Share Posted March 2, 2018 This was in the old way of doing it before 60.0. The new way is to detect the model using the various HTTP headers. If you can I would suggest to move on to 60.0. Quote Link to comment Share on other sites More sharing options...
Iruwen Posted March 2, 2018 Author Report Share Posted March 2, 2018 Thanks for the reply, this leads to two other questions: which headers, and is this the wrong documentation to look at? Quote Link to comment Share on other sites More sharing options...
ahennis@voicespring.net Posted March 2, 2018 Report Share Posted March 2, 2018 The "model=snom360" tells the system what model the phone is. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.