Jump to content

PNP Provisioning


hosted
 Share

Recommended Posts

ok I am going to go from 3023 to 3177 on 1 hosted box. The PNP completely different.

 

Is there a way to pull all these tftp files out of the 3023 box for snom and polycom phones so i can just put them in the tftp directory after i upgrade to 3177?

It would suck to have to go to each site and update the phone itself.

Link to comment
Share on other sites

ok I am going to go from 3023 to 3177 on 1 hosted box. The PNP completely different.

 

Is there a way to pull all these tftp files out of the 3023 box for snom and polycom phones so i can just put them in the tftp directory after i upgrade to 3177?

It would suck to have to go to each site and update the phone itself.

 

Well, the key point here is that the phone must authenticate themselves. The PBX no longer trusts the MAC address mentioned in the provisioning request. That has some very obvious security features; however it also requires that the endpoints now must have the username and password for provisioning before the provisioning can take place.

 

There is a workaround for this. You can generate the MAC-based files and put them into the tftp directory. For details, ask support@pbxnsip.com.

Link to comment
Share on other sites

  • 2 weeks later...

Would it be possible for you to write up the best practices method for provisioning snom phones using pbxnsip?

 

I have a box of brand new snom phones and a cs410 and am getting a little frustrated with the amount of time its taking to run simple software upgrades. snom is advising logging into each phone and pasting a URL into the phone. This upgrades but it's silly and very time consuming to have to do each one by hand - and it sticks at the end and requires a manual re-boot of the phone!

 

I would *love it* if you had an article which told me:

 

- WHERE on the PBX to drop the snom software and default settings file; and

- WHAT settings I need to change on the PBX

 

So that all I have to do is know the MAC address of a new phone. (It's printed on the box and on a sticker. )

 

I put that in a PBXnSIP account record, plug in the phone, it boots, upgrades to the latest firmware, loads its settings and I'm done.

 

A cheat sheet with the basic steps to make this happen would be gold - especially if you continually updated it as the steps change. We would always know where to look.

 

Can this be done or am I blind and you will point me to a page I have missed?

 

Thanks,

 

Alex

Link to comment
Share on other sites

Would it be possible for you to write up the best practices method for provisioning snom phones using pbxnsip?

 

I have a box of brand new snom phones and a cs410 and am getting a little frustrated with the amount of time its taking to run simple software upgrades. snom is advising logging into each phone and pasting a URL into the phone. This upgrades but it's silly and very time consuming to have to do each one by hand - and it sticks at the end and requires a manual re-boot of the phone!

 

I would *love it* if you had an article which told me:

 

- WHERE on the PBX to drop the snom software and default settings file; and

- WHAT settings I need to change on the PBX

 

So that all I have to do is know the MAC address of a new phone. (It's printed on the box and on a sticker. )

 

I put that in a PBXnSIP account record, plug in the phone, it boots, upgrades to the latest firmware, loads its settings and I'm done.

 

A cheat sheet with the basic steps to make this happen would be gold - especially if you continually updated it as the steps change. We would always know where to look.

 

Can this be done or am I blind and you will point me to a page I have missed?

 

Thanks,

 

Alex

 

pbxnsip can do this with the snom phones but they need to be running firmware version 7.x first before any auto provisioning works. You also have to put the right bin file in the directory so when the snom phone looks for it, it sees that their is a newer version and downloads, installs and reboots if needed. I'm running pbxnsip version 3.1.2.3120 so if you have a newer release it might be different.

Link to comment
Share on other sites

  • 2 months later...
Would it be possible for you to write up the best practices method for provisioning snom phones using pbxnsip?

 

I have a box of brand new snom phones and a cs410 and am getting a little frustrated with the amount of time its taking to run simple software upgrades. snom is advising logging into each phone and pasting a URL into the phone. This upgrades but it's silly and very time consuming to have to do each one by hand - and it sticks at the end and requires a manual re-boot of the phone!

 

I would *love it* if you had an article which told me:

 

- WHERE on the PBX to drop the snom software and default settings file; and

- WHAT settings I need to change on the PBX

 

So that all I have to do is know the MAC address of a new phone. (It's printed on the box and on a sticker. )

 

I put that in a PBXnSIP account record, plug in the phone, it boots, upgrades to the latest firmware, loads its settings and I'm done.

 

A cheat sheet with the basic steps to make this happen would be gold - especially if you continually updated it as the steps change. We would always know where to look.

 

Can this be done or am I blind and you will point me to a page I have missed?

 

Thanks,

 

Alex

 

I agree with this post.

But I think these issues can be fixed...

 

matt

Link to comment
Share on other sites

I agree with this post.

But I think these issues can be fixed...

 

matt

 

Well there is a process (tested on 3.4 version) and it works for snom phones. The precondition is that the phones must already have the settings URL as http://<pbx ip>/provisioning/snom320-<mac address>.htm.

 

Then the following steps have to be followed (note: References to 320 on the filename should be replaced with the appropriate phone model. 300, 320, 360, etc. But references to 3xx should be kept as is).

  • Create the 'provisioning' folder under the working directory
  • Create/Copy the snom320-mac address.htm file to the 'provisioning' folder.
  • Create snom_3xx_phone_<mac address>.xml. Note that this file should contain the http client user name and password
  • Reboot the phone
  • After the reboot the phone will receive the snom320-mac address.htm file and then snom_3xx_phone_<mac address>.xml (without authentication)
  • At the end of the reboot cycle, the phone will be provisioned with the http_client_user and http_client_pass. Also the settings URL will be changed so that it will be consistent with the future releases of the PBX.

 

Once the phone is rebooted, you can move 'provisioning' folder away. From the next reboot onwards, phone will contact the PBX with the authentication information and the PBX will properly generate the config files.

 

Sample content of snom320-mac address.htm.

<?xml version="1.0" encoding="utf-8"?>

<setting-files>

<file url="https://10.1.10.10/provisioning/snom_3xx_phone_000413271234.xml?model=snom320" />

</setting-files>

 

Sample content of the snom_3xx_phone_<mac address>.xml

<?xml version="1.0" encoding="utf-8"?>

<phone-settings>

<user_active idx="1" perm="RW">on</user_active>

<http_client_user perm="RW">100@mycompany.com</http_client_user>

<http_client_pass perm="RW">secret</http_client_pass>

<setting_server perm="RW">http://10.1.10.10/provisioning/snom320.htm</setting_server>

</phone-settings>

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