Jump to content

updating phones


mikec
 Share

Recommended Posts

hi all

 

we have hadour Snom one system installed by someone else and are trying to get our head around it! we have 760 handsets are are failing to be able to make changes on these from the snomOne admin console.

 

As far as a know these are connected via PnP - is there a way to check!?

 

i want to update the firmware for all 760's , so i go into admin > settings > PnP and change the url to point to new Firmware url ....reboot phones but no udates.

 

I also tried creating a new button profile for the 760's , assign a few of the buttons for BLF and apply these to the domain buttons setting , or even under an extention, again phone doesnt update....

 

not sure if im missing a fundimental bit here ?!.......

 

looking on the phone log (level 5) shows lots of the following which doesnt look good (?)

 

16/connected, poll data_cb -> No such file or directory (2)

8/10/2012 21:05:59 [ERROR ] PHN: TPL: Socket Error: 201/19/connected, poll data_cb -> No such file or directory (2)

8/10/2012 21:05:59 [ERROR ] PHN: TPL: Socket Error: 202/20/connected, poll data_cb -> No such file or directory (2)

8/10/2012 21:05:59 [ERROR ] PHN: TPL: Socket Error: 203/21/connected, poll data_cb -> No such file or directory (2)

8/10/2012 21:05:59 [ERROR ] PHN: TPL: Socket Error: 204/22/connected, poll data_cb -> No such file or directory (2)

8/10/2012 21:05:59 [ERROR ] PHN: TPL: Socket Error: 205/23/connected, poll data_cb -> No such file or directory (2)

8/10/2012 21:06:02 [NOTICE] PHN: TPL: Socket 210 idle/connect timeout

8/10/2012 21:06:02 [NOTICE] PHN: TPL: Socket 211 idle/connect timeout

8/10/2012 21:06:02 [NOTICE] PHN: TPL: Socket 206 idle/connect timeout

8/10/2012 21:06:02 [NOTICE] PHN: TPL: Socket 207 idle/connect timeout

8/10/2012 21:06:02 [NOTICE] PHN: TPL: Socket 208 idle/connect timeout

8/10/2012 21:06:02 [NOTICE] PHN: TPL: Socket 209 idle/connect timeout

 

 

help please!! thanks

Link to comment
Share on other sites

To check if the phones were automatically provisioned, you can check on the file system the "generated" folder. There you find all files that have been generated during the PnP process (unless this feature was disabled).

 

If you can actually log in to the phones without any password, chances are that those phones were not automatically provisioned. If you are in the LAN, it is actually not that difficult to provision them. Just copy & paste the MAC address into the PBX extension settings (registration tab), and enter the IP address of the PBX into the settings server setting of the phone (hidden under advanced/update/settings server in the phone web interface). The long version is on http://wiki.snomone.com/index.php?title=Plug_and_Play with all kinds of scenarios, even videos about it are available.

Link to comment
Share on other sites

many thanks.

 

Ok the phones are PnP (they have generated files). but the update setting on the phone (advance,update...)was http://provisioning.snom.com/snom760/snom760.php?mac={mac}.

 

Ive changed this to http://192.168.4.100/snom760/snom760.php?mac={mac} (our server), rebooted the phone but the unit still doesnt apply any of the changes i make on the snomONE admin (new firmware, button assignmets etc)

 

i must be missing something!?!... :(

 

many thanks for your help

Link to comment
Share on other sites

Getting closer... Just set it to "192.168.4.100" (don't copy the quotes). The PBX will then do the rest.

 

 

thanks that worked a treat! firmware updates have been been applied now and button profiles have been updated (even though it says provision server says buttons failed?)

 

one more if thats ok - after the button profile has been applied if its changed under each user on the SnomOne extensions, it doesnt update the ext. is this normal?

Link to comment
Share on other sites

Not 100 % sure about the updating of buttons. I remember that it *should* automatically apply the button settings, meaning that it sends a request to the phone to reload its configuration. It also might take some activity to set the buttons into action. Of course a complete phone reboot should make sure that the buttons are properly configured.

Link to comment
Share on other sites

Well, it is a long story and it started with Cisco and the usage of option 66 of DHCP. The default protocol was and is TFTP. Unfortunately, TFTP is not very NAT friendly and not secure either, but it works in the LAN and the MAC on layer 2 of the packet is a (weak) token of authenticity The phone fetches via TFTP essentially the real location, which is then https-encoded. So when you are in the LAN, the IP address of the PBX is okay. If you are outside of the LAN, things get more complicated; then you have to enter the whole URL and a username/password.

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...