chrispopp

Looked at both of these, and neither one provides the SIP password.

Problem is that we want to generate the password automatically and randomly. Otherwise generating all extensions with the same password, may pose a security risk. Also, changing the password randomly on the fly, will take the deskphones offline... which is not an option.

In the process of building a softphone, and would like to provision my softphone. How would I retrieve the SIP pass via the REST api? Or is there another way?

Do you plan on incorporating this?

Do you plan on offering an integration with https://letsencrypt.org/? This would be great, as we can offer properly encrypted traffic, without needing to use self-signed...

Any luck on getting this to provision with Vodia? We are seeing increased demand for this product. Thanks

No, because there are other bugs that prevent the rest of the buttons from working on the new one, after the update. Was hoping to use the old firmwares...

I have a Snom 320 version 8.4.35 and Vodia 5.5 we are testing. The phone has using_server_managed_dnd enabled. Problem is that the server does not switch to DND. How can we resolve this problem, so that the DND button syncs with the server? This is what the Snom firmware says: If this setting is "on" the server will be responsible for handling the DND(DO NOT DISTURB) functionality. From the call perspective the phone will act as if no dnd was set (all is managed by the server). The phone user will see the value from dnd_mode (in FW versions < 8.7.3:server_managed_dnd_state) as the current DND state, and this value can be changed at anytime by the server. This setting does not specify how the server changes the value of dnd_mode (in FW versions < 8.7.3:server_managed_dnd_state) nor how the phone updates them (it may be done via TR69).

We are working with vodia 5.5 and using a snom 320 - 8.4.35. The feature using_server_managed_dnd1!: on The server does not set the DND flag. Any options?

Can it be changed for all domains at once?

Any advancements on this? Would like to test a few phones out for a deployment.

How can this be used?

I did add that to the config file. That seems to be the correct value. Without adding the CAN-5, the timezone is simply USA and the value on the phone is the following: Adding CAN-5 gives you the following: . The automated generated file by Vodia seems to have an incorrect value, thus defaulting to Unused. See Snom wiki. http://wiki.snom.com/wiki/index.php/Settings/timezone At least that's what I understood from reading and dealing with this issue for the last month.

This is the setting shown in the settings file... dst!: 3600 3.2.7 2:0:0 11.1.7 2:0:0 timezone!: CAN-5

Mar 8 14:45:08 [ERROR ] PHN: TPL: Socket Error: 317/50/connected, Tls error, closing Mar 8 14:45:08 [NOTICE] CFG: read_xml_settings: found firmware-settings XML header Mar 8 14:45:08 [NOTICE] CFG: read_xml_settings: found one byte encoding: 1 Mar 8 15:45:09 [NOTICE] PHN: DST start 03.02.2016 02:00:00 end 06.11.2016 02:00:00 offset 3600 Mar 8 15:45:09 [NOTICE] CFG: Std-Settings stored Mar 8 15:47:07 [NOTICE] PHN: Executing timer driven automatic settings refresh Mar 8 15:47:07 [NOTICE] PHN: Setting automatic settings refresh timer with 120 seconds Mar 8 15:47:07 [NOTICE] PHN: Setting server prio 1, type redirection, url: > Mar 8 15:47:07 [NOTICE] PHN: Fetching URL: Mar 8 15:47:07 [NOTICE] CFG: read_xml_settings: found setting-files XML header Mar 8 15:47:07 [NOTICE] CFG: read_xml_settings: found one byte encoding: 1 So it seems the DST is causing the issues. As you can see, as soon as the DST starts, it ruins the time and jumps it ahead an hour. Any ideas? The DHCP option 42 did not help...

I was looking at this: Currently playing around with the DHCP option 42. This is a screenshot of my Snom 720. Moved the option 42 from ON to OFF. Whereas the Snom 370 has only these settings. I rebooted the phone and awaiting to see if this fixes the issue. Waiting for the NTP timer. Also considering issues with DST... I just can't find any settings relating to DST on these phones. The problem happened since the DST change here in Canada...

Fixed it on the Cisco, but the Snom's are still picking up the incorrect time. They boot up, pick up the right time. After the refresh (one hour), they go one hour ahead. Any fixes for this? The log and the SIP trace both show the incorrect time. Changed the NTP server, didn't help. Changed the DNS, also didn't help. The time on the server and PBX is showing the correct time.

Programmed some Cisco SPA509 and SPA525G and they are also one hour ahead. Used different NTP servers, and on different networks. <Set_Local_Date__mm_dd_ ua="na"> </Set_Local_Date__mm_dd_> <Set_Local_Time__HH_mm_ ua="na"> </Set_Local_Time__HH_mm_> <Time_Zone ua="na"> GMT-04:00 </Time_Zone> <Time_Offset__HH_mm_ ua="na"> </Time_Offset__HH_mm_> <Daylight_Saving_Time_Rule ua="na"> start=3/2/7/2:0;end=11/1/7/2:0;save=1 </Daylight_Saving_Time_Rule>

Even after using CAN-5 (as a constant in the file)... the phones go back to the incorrect time.

No I did not. But seems to be a constant in the pnp xml files.... This is from the server wide snom_760_phone.xml file... what is the variable that this should be switch to? Edit: The same seems to be in all the other xml files. Edit 2: Checked another old server on version 4.5 and it has the same USA as the value...

I can confirm that changing the template file to USA-5 works and fixes the time.

Running a few phones snom760-SIP 8.7.5.35 with version on Vodia 5.2.5a. This is what is generated for the auto-provision: <timezone perm="RW">USA</timezone>^ <utc_offset perm="RW">-18000</utc_offset>^ <dst perm="RW">3600 3.2.7 2:0:0 11.1.7 2:0:0</dst>^ I believe the time zone value is incorrect, as depicted in this page: In my case, it should be (USA-5) http://wiki.snom.com/wiki/index.php/Settings/timezone

SPA509G: 5067AE SPA525: 1CDEA7

That's the version I'm testing with. very simple setup as well before I can test in the full environment. Can you run a quick test and confirm that it works on your end?

Would this be considered a bug?