Jump to content

snom 870


hosted
 Share

Recommended Posts

  • 3 weeks later...
Not yet. But it should be easy to add PnP if the software behaves like the other snom phones. We added MeetingPoint and that was very easy.

 

Really? How? This isn't explained anywhere. I have both the MeetingPoint and an 870 and am manually creating an xml file by downloading the settings from from the phone and putting it in the pbx/html/tftp folder where it does get picked up - but this requires a manual xml file for each phone. How are you doing it?

 

AK

Link to comment
Share on other sites

Really? How? This isn't explained anywhere. I have both the MeetingPoint and an 870 and am manually creating an xml file by downloading the settings from from the phone and putting it in the pbx/html/tftp folder where it does get picked up - but this requires a manual xml file for each phone. How are you doing it?

 

Currently this is only a 4.0 feature. After getting this stable lets see if we can port this back to version 3.

Link to comment
Share on other sites

  • 2 months later...
Not yet. But it should be easy to add PnP if the software behaves like the other snom phones. We added MeetingPoint and that was very easy.

 

I have been struggling trying to get the SNOM870 working complete with phone book support and 'park orbit'. But till now it does not work.

 

If it is not supported it would be a huge disappointment for my customers who purchased a few SNOM870 as 'TOP-MODEL' :( . According to following document it is fully supported :angry: !!!!

http://www.pbxnsip.com/sales/pbxnsip-and-s...phones-v1.1.pdf

 

When will the full support be available ? As you can understand the management will not accept half-functional phones on their desk. So I have a bunch of useless phones at this moment !

 

Thanks for any news on this....

Link to comment
Share on other sites

When will the full support be available ? As you can understand the management will not accept half-functional phones on their desk. So I have a bunch of useless phones at this moment !

 

We will come out with a version 3.5. I think there we can include the 870 config file. I attach the files that you can throw into the html directory. Don't forget to remove them when you upgrade later.

pnp.xml

snom_3xx_fw.xml

snom_870.xml

Link to comment
Share on other sites

  • 4 weeks later...
It should work. Just make sure that you need to remove these files when you upgrade the version to something that includes the PnP files for snom 870. (All version older than today do support this).

Does not work for me, I do have snom_3xx_fs and snom_3xx_fw in the genrated/extension folder, my 820 phones have 8 files in their extension folder.

I get a 404 if I try browsing to http://srv.server.com/provisioning/snom870.htm where as if I try http://srv.server.com/provisioning/snom820.htm I get logon and see the xml

 

snom log

5]24/12/2001 00:00:31: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml

[5]24/12/2001 00:00:36: Using WEB language English from: /snom/snomlang/web_lang_EN.xml

[5]24/12/2001 00:00:36: read_xml_settings: found dial-plan XML header

[5]24/12/2001 00:00:36: read_xml_settings: found one byte encoding: 0

[0]24/12/2001 00:00:46: phone::vlan_onoff: cannot open switch-api

[0]24/12/2001 00:00:46: phone::vlan_table_reset: cannot open switch-api

[5]24/12/2001 00:00:46: Opening TCP socket on port 843

[5]24/12/2001 00:00:51: Setting server was already set: http://srv.server.com/provisioning/snom870.htm

[5]24/12/2001 00:00:51: Fetching URL: http://srv.server.com/provisioning/snom870.htm

[0]24/12/2001 00:00:52: Webclient: Could not resolve host during provisioning srv.server.com:80

[5]24/12/2001 00:00:52: Conf setup: return code 400; requeueing >http://srv.server.com:80/provisioning/snom870.htm<; attempt: 1, state: 38

[5]24/12/2001 00:00:55: Fetching URL: http://srv.server.com:80/provisioning/snom870.htm

[1]24/12/2001 00:00:55: Conf setup: code: 404, host: srv.server.com:80, file: /provisioning/snom870.htm

[5]24/12/2001 00:00:55: Fetching URL: http://srv.server.com/provisioning/snom870-000414410B3B.htm

[1]24/12/2001 00:00:55: Conf setup: code: 404, host: srv.server.com:80, file: /provisioning/snom870-000413410B3B.htm

[5]24/12/2001 00:00:55: Fetching URL: http://127.0.0.1/dummy.htm

[1]24/12/2001 00:00:55: Conf setup: code: 500, host: 127.0.0.1:80, file: /dummy.htm

[5]24/12/2001 00:00:55: Fetching FW URL: http://srv.server.com/snom870/snom870-firmware.htm

[5]24/12/2001 00:00:55: Fetching URL: http://srv.server.com/snom870/snom870-firmware.htm

[2]23/12/2001 19:00:55: start_dst(984276000) end_dst(1004839200) offset_dst(3600) offset_utc(-18000)

[2]23/12/2001 19:00:55: start DST: 03/11/2001 02:00:00 (984276000)

[2]23/12/2001 19:00:55: end DST: 11/04/2001 02:00:00 (1004839200)

[5]23/12/2001 19:00:55: read_xml_settings: found phone-book XML header

[5]23/12/2001 19:00:55: read_xml_settings: found one byte encoding: 0

[5]23/12/2001 19:00:58: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml

[5]23/12/2001 19:01:03: Using WEB language English from: /snom/snomlang/web_lang_EN.xml

[5]23/12/2001 19:01:03: Opening TCP socket on port 80

[5]23/12/2001 19:01:03: Opening TCP socket on port 443

[2]3/12/2009 19:32:32: start_dst(1236477600) end_dst(1257040800) offset_dst(3600) offset_utc(-18000)

[2]3/12/2009 19:32:32: start DST: 03/08/2009 02:00:00 (1236477600)

[2]3/12/2009 19:32:32: end DST: 11/01/2009 02:00:00 (1257040800)

Link to comment
Share on other sites

FYI.. After copying the pnp.xml to html folder, you need to restart PBX service or this file needs to be uploaded through Admin->Settings->Configuration page.

 

Also, the log line "[0]24/12/2001 00:00:52: Webclient: Could not resolve host during provisioning srv.server.com:80", is a suspect.

 

 

Does not work for me, I do have snom_3xx_fs and snom_3xx_fw in the genrated/extension folder, my 820 phones have 8 files in their extension folder.

I get a 404 if I try browsing to http://srv.server.com/provisioning/snom870.htm where as if I try http://srv.server.com/provisioning/snom820.htm I get logon and see the xml

 

snom log

5]24/12/2001 00:00:31: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml

[5]24/12/2001 00:00:36: Using WEB language English from: /snom/snomlang/web_lang_EN.xml

[5]24/12/2001 00:00:36: read_xml_settings: found dial-plan XML header

[5]24/12/2001 00:00:36: read_xml_settings: found one byte encoding: 0

[0]24/12/2001 00:00:46: phone::vlan_onoff: cannot open switch-api

[0]24/12/2001 00:00:46: phone::vlan_table_reset: cannot open switch-api

[5]24/12/2001 00:00:46: Opening TCP socket on port 843

[5]24/12/2001 00:00:51: Setting server was already set: http://srv.server.com/provisioning/snom870.htm

[5]24/12/2001 00:00:51: Fetching URL: http://srv.server.com/provisioning/snom870.htm

[0]24/12/2001 00:00:52: Webclient: Could not resolve host during provisioning srv.server.com:80

[5]24/12/2001 00:00:52: Conf setup: return code 400; requeueing >http://srv.server.com:80/provisioning/snom870.htm<; attempt: 1, state: 38

[5]24/12/2001 00:00:55: Fetching URL: http://srv.server.com:80/provisioning/snom870.htm

[1]24/12/2001 00:00:55: Conf setup: code: 404, host: srv.server.com:80, file: /provisioning/snom870.htm

[5]24/12/2001 00:00:55: Fetching URL: http://srv.server.com/provisioning/snom870-000414410B3B.htm

[1]24/12/2001 00:00:55: Conf setup: code: 404, host: srv.server.com:80, file: /provisioning/snom870-000413410B3B.htm

[5]24/12/2001 00:00:55: Fetching URL: http://127.0.0.1/dummy.htm

[1]24/12/2001 00:00:55: Conf setup: code: 500, host: 127.0.0.1:80, file: /dummy.htm

[5]24/12/2001 00:00:55: Fetching FW URL: http://srv.server.com/snom870/snom870-firmware.htm

[5]24/12/2001 00:00:55: Fetching URL: http://srv.server.com/snom870/snom870-firmware.htm

[2]23/12/2001 19:00:55: start_dst(984276000) end_dst(1004839200) offset_dst(3600) offset_utc(-18000)

[2]23/12/2001 19:00:55: start DST: 03/11/2001 02:00:00 (984276000)

[2]23/12/2001 19:00:55: end DST: 11/04/2001 02:00:00 (1004839200)

[5]23/12/2001 19:00:55: read_xml_settings: found phone-book XML header

[5]23/12/2001 19:00:55: read_xml_settings: found one byte encoding: 0

[5]23/12/2001 19:00:58: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml

[5]23/12/2001 19:01:03: Using WEB language English from: /snom/snomlang/web_lang_EN.xml

[5]23/12/2001 19:01:03: Opening TCP socket on port 80

[5]23/12/2001 19:01:03: Opening TCP socket on port 443

[2]3/12/2009 19:32:32: start_dst(1236477600) end_dst(1257040800) offset_dst(3600) offset_utc(-18000)

[2]3/12/2009 19:32:32: start DST: 03/08/2009 02:00:00 (1236477600)

[2]3/12/2009 19:32:32: end DST: 11/01/2009 02:00:00 (1257040800)

Link to comment
Share on other sites

FYI.. After copying the pnp.xml to html folder, you need to restart PBX service or this file needs to be uploaded through Admin->Settings->Configuration page.

 

Also, the log line "[0]24/12/2001 00:00:52: Webclient: Could not resolve host during provisioning srv.server.com:80", is a suspect.

 

Sorry, I forgot about that, I reloaded the pnp.xml, I get further however it seems to be getting an error 500, and it tries to re log in, from my desktop, the url's pull up fine, using same user name and password set in the client setting of the phone.

 

here is the snom 870 log

 

5]24/12/2001 00:00:27: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml

[5]24/12/2001 00:00:32: Using WEB language English from: /snom/snomlang/web_lang_EN.xml

[5]24/12/2001 00:00:32: read_xml_settings: found dial-plan XML header

[5]24/12/2001 00:00:32: read_xml_settings: found one byte encoding: 0

[0]24/12/2001 00:00:41: phone::vlan_onoff: cannot open switch-api

[0]24/12/2001 00:00:41: phone::vlan_table_reset: cannot open switch-api

[5]24/12/2001 00:00:41: Opening TCP socket on port 843

[5]24/12/2001 00:00:46: Setting server was already set: http://server.server.com/provisioning/snom870.htm

[5]24/12/2001 00:00:46: Fetching URL: http://server.server.com/provisioning/snom870.htm

[5]24/12/2001 00:00:55: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:00:55: webclient::handle_challenge: resending request !

[5]24/12/2001 00:00:59: read_xml_settings: found setting-files XML header

[5]24/12/2001 00:00:59: read_xml_settings: found one byte encoding: 1

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: http://55.77.142.3:80/provisioning/snom_3x...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_w...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_g...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/tftp/snom_870_custom.xml

[5]24/12/2001 00:00:59: Conf setup: found xml style settings

[5]24/12/2001 00:00:59: Fetching URL: http://server.server.com/provisioning/snom...00414410B3B.htm

[1]24/12/2001 00:00:59: Conf setup: code: 404, host: server.server.com:80, file: /provisioning/snom870-000414410B3B.htm

[5]24/12/2001 00:00:59: Fetching URL: http://55.77.142.3:80/provisioning/snom_3x...l?model=snom870

[5]24/12/2001 00:01:07: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:01:07: webclient::handle_challenge: resending request !

[5]24/12/2001 00:01:10: read_xml_settings: found phone-settings XML header

[5]24/12/2001 00:01:10: read_xml_settings: found one byte encoding: 1

[5]24/12/2001 00:01:10: Conf setup: found xml style settings

[5]24/12/2001 00:01:10: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:01:19: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:01:19: webclient::handle_challenge: resending request !

[5]24/12/2001 00:01:49: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 1, state: 38

[5]24/12/2001 00:01:52: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:02:00: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:02:00: webclient::handle_challenge: resending request !

[5]24/12/2001 00:02:30: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 2, state: 38

[5]24/12/2001 00:02:33: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:02:42: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:02:42: webclient::handle_challenge: resending request !

[5]24/12/2001 00:03:12: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 3, state: 38

[5]24/12/2001 00:03:15: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:03:23: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:03:23: webclient::handle_challenge: resending request !

[5]24/12/2001 00:03:54: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 4, state: 38

[5]24/12/2001 00:03:57: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:04:05: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:04:05: webclient::handle_challenge: resending request !

[5]24/12/2001 00:04:35: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 5, state: 38

[5]24/12/2001 00:04:38: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:04:47: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:04:47: webclient::handle_challenge: resending request !

[5]24/12/2001 00:05:17: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 6, state: 38

[5]24/12/2001 00:05:20: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:05:28: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:05:28: webclient::handle_challenge: resending request !

[5]24/12/2001 00:05:58: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 7, state: 38

[5]24/12/2001 00:06:01: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:06:10: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:06:10: webclient::handle_challenge: resending request !

[5]24/12/2001 00:06:40: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 8, state: 38

[5]24/12/2001 00:06:43: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:06:51: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:06:51: webclient::handle_challenge: resending request !

[5]24/12/2001 00:07:22: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 9, state: 38

[5]24/12/2001 00:07:25: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:07:33: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:07:33: webclient::handle_challenge: resending request !

[5]24/12/2001 00:08:03: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 10, state: 38

[5]24/12/2001 00:08:06: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:08:15: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:08:15: webclient::handle_challenge: resending request !

[5]24/12/2001 00:08:45: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 11, state: 38

[5]24/12/2001 00:08:48: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:09:18: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 12, state: 38

[5]24/12/2001 00:09:21: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:09:52: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 13, state: 38

[5]24/12/2001 00:09:55: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:10:03: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:10:03: webclient::handle_challenge: resending request !

[5]24/12/2001 00:10:33: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 14, state: 38

[5]24/12/2001 00:10:36: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:10:45: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:10:45: webclient::handle_challenge: resending request !

[5]24/12/2001 00:11:15: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 15, state: 38

[5]24/12/2001 00:11:18: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:11:26: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:11:26: webclient::handle_challenge: resending request !

[5]24/12/2001 00:11:56: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 16, state: 38

[5]24/12/2001 00:11:59: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:12:08: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:12:08: webclient::handle_challenge: resending request !

[5]24/12/2001 00:12:38: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 17, state: 38

[5]24/12/2001 00:12:41: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:12:49: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:12:49: webclient::handle_challenge: resending request !

[5]24/12/2001 00:13:19: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 18, state: 38

[5]24/12/2001 00:13:22: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:13:31: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:13:31: webclient::handle_challenge: resending request !

[5]24/12/2001 00:14:01: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 19, state: 38

[5]24/12/2001 00:14:04: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:14:12: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:14:12: webclient::handle_challenge: resending request !

[5]24/12/2001 00:14:43: Conf setup: return code 500; requeueing >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<;'>https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<; attempt: 20, state: 38

[5]24/12/2001 00:14:46: Fetching URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:14:54: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:14:54: webclient::handle_challenge: resending request !

[5]24/12/2001 00:15:24: Conf setup: return code 500; giving up on >https://55.77.142.3:443/provisioning/snom_3xx_phone.xml?model=snom870<

[5]24/12/2001 00:15:24: read_xml_settings: found phone-book XML header

[5]24/12/2001 00:15:24: read_xml_settings: found one byte encoding: 0

[5]24/12/2001 00:15:27: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml

[5]24/12/2001 00:15:32: Using WEB language English from: /snom/snomlang/web_lang_EN.xml

[5]24/12/2001 00:15:32: Opening TCP socket on port 80

[5]24/12/2001 00:15:32: Opening TCP socket on port 443

Link to comment
Share on other sites

Ok. definitely this is a user name password issue. Try using username@domain if it is multi-domain system.

 

Sorry, I forgot about that, I reloaded the pnp.xml, I get further however it seems to be getting an error 500, and it tries to re log in, from my desktop, the url's pull up fine, using same user name and password set in the client setting of the phone.

 

here is the snom 870 log

 

5]24/12/2001 00:00:27: Using GUI language English from: /snom/snomlang/gui_lang_EN.xml

[5]24/12/2001 00:00:32: Using WEB language English from: /snom/snomlang/web_lang_EN.xml

[5]24/12/2001 00:00:32: read_xml_settings: found dial-plan XML header

[5]24/12/2001 00:00:32: read_xml_settings: found one byte encoding: 0

[0]24/12/2001 00:00:41: phone::vlan_onoff: cannot open switch-api

[0]24/12/2001 00:00:41: phone::vlan_table_reset: cannot open switch-api

[5]24/12/2001 00:00:41: Opening TCP socket on port 843

[5]24/12/2001 00:00:46: Setting server was already set: http://server.server.com/provisioning/snom870.htm

[5]24/12/2001 00:00:46: Fetching URL: http://server.server.com/provisioning/snom870.htm

[5]24/12/2001 00:00:55: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:00:55: webclient::handle_challenge: resending request !

[5]24/12/2001 00:00:59: read_xml_settings: found setting-files XML header

[5]24/12/2001 00:00:59: read_xml_settings: found one byte encoding: 1

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: http://55.77.142.3:80/provisioning/snom_3x...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_3...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_w...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/provisioning/snom_g...l?model=snom870

[5]24/12/2001 00:00:59: read_setting_file_list: added URL: https://55.77.142.3:443/tftp/snom_870_custom.xml

[5]24/12/2001 00:00:59: Conf setup: found xml style settings

[5]24/12/2001 00:00:59: Fetching URL: http://server.server.com/provisioning/snom...00414410B3B.htm

[1]24/12/2001 00:00:59: Conf setup: code: 404, host: server.server.com:80, file: /provisioning/snom870-000414410B3B.htm

[5]24/12/2001 00:00:59: Fetching URL: http://55.77.142.3:80/provisioning/snom_3x...l?model=snom870

[5]24/12/2001 00:01:07: webclient::handle_challenge: http server is asking for credentials!

[5]24/12/2001 00:01:07: webclient::handle_challenge: resending request !

Link to comment
Share on other sites

Ok. definitely this is a user name password issue. Try using username@domain if it is multi-domain system.

Definetly not a user name and password issue, as my web browser accepts that same login, it has the full username@domain, the Snom 820 accepted the same password too. I beleive I would get a 400 response not a 500 for a bad password.

Link to comment
Share on other sites

We've made that.

 

Everything is Ok, provided files helps a lot.

 

FW version is 8.3.2, 8.3.3 and 8.3.5

 

Can you tell me in a few short words which of the procedures above worked for you ?

I tried using the pxp.xml in the manual way but nothing happened.

 

B.T.W. Where did you find the 8.3.3 FW ?

Link to comment
Share on other sites

  • 3 weeks later...
Can you tell me in a few short words which of the procedures above worked for you ?

I tried using the pxp.xml in the manual way but nothing happened.

 

B.T.W. Where did you find the 8.3.3 FW ?

Yes. It isn't exactly clear is it?

 

Here goes. To make the 870 and 820 work with PBXnSIP in its current release you must do the following:

  • Download the three files above. Ensure they are all named properly (pnp.xml, snom870.xml and snom_3xx_fw.xml).
  • Using SSH or some other method, put the three files you downloaded into the pbx/html directory on your PBX server or CS410 unit.
  • Reboot the PBX
  • Reboot your 870 phone(s)

Your 870/820 should pick it up right away using PnP and you can then adjust buttons using PBXnSIP's web interface, the directory will work, etc.

 

Note that this is a PATCH! You must remember later: When and if you decide to upgrade your PBX software to a (as yet unreleased) version that supports the 8xx series out of the box, YOU MUST REMOVE the three files you just uploaded as they will always override any new files in a new PBX version if you forget to do this.

 

Customization

 

Additionally, if you wish to further customize the behavior of all your 8xx phones (e.g. stuff that isn't controlled by PBXnSIP) you can log into an 8xx phone web interface, set it up the way you want and download an xml settings file with all your little customizations.

 

Using a text editor, inspect this xml file and remove anything you don't want. Name the xml file snom_870_custom.xml or snom_820_custom.xml depending on your model and create a directory called tftp in pbx/html - so your path is pbx/html/tftp and put these xml files in it.

 

All of your 8xx phones will use these files as the settings default so you can do something like turn off that extremely confusing "dial tone on hold feature" or make all the phones ring like crickets. But again, be careful as they will even override the settings PBXnSIP generates for each phone. Remove ANY individual phone specific settings from your custom xml files or you will have cloned phones and get very confused. If you get totally lost, just remove the files and reboot. If it's bad, wipe your phones as these settings stay there until they are specifically changed or the phone is reset.

 

Firmware upgrade

 

Unfortunately these phones still have some major bugs in the release software. The most annoying: No Sidetone!! (You can't hear yourself). You can download the beta version of the next update here at snom.com, but remember you may have other issues as it is still in beta. Otherwise the phones seem to work fine. I'm still testing and haven't rolled it, but it's a very cool looking phone and for many executive types that's enough.

 

Note: I DO NOT work for PBXnSIP or Snom (but maybe should? ;)) these are my own observations. Use these suggestions at your own risk.

 

Alex

Link to comment
Share on other sites

Note: I DO NOT work for PBXnSIP or Snom (but maybe should? ;) ) these are my own observations. Use these suggestions at your own risk.

 

Thanks, the description is very useful! We are working on 3.5 with some smaller improvements, including a 870 PnP. Those who would like to get a 3.5 image, send a PM or email to support@pbxnsip.com.

Link to comment
Share on other sites

  • 2 months later...

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.

Loading...
 Share

×
×
  • Create New...