×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Automatically configure SPA504G

Unanswered Question
Nov 5th, 2012
User Badges:

Hi


First, sorry for my english . i have five SPA504G and always, i have always set for web http://ipx.x.x.x. Now I have 30 phones and I need to set it automatically, without doing it by web. Is there any application or way to do it?


I searched forums but can not find anything


thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Steven Howes Thu, 11/08/2012 - 09:11
User Badges:

Cisco cant really provide a provisioning system, because the config depends on your call control system. Making an XML config delivered over HTTP is probably a few dozen lines of PHP at best - it's been quite commonly done if you look online. Plenty for the 9xx series of phones (which share the format). There's plenty of free provisioning examples out there (but we chose to write our own to interact with a backend SQL database that also produces the call control config).


S

andrewhotlab Thu, 11/08/2012 - 09:05
User Badges:

I've posted about this topic more than a year ago, but it seems that Cisco has no interest to make available a provisioning system targeted at this type of market (after all, these phones are targeted to "small businesses", that is, to environments with few devices, thus this decision is somewhat understandable).


So we only have tools such the SPC (SIP Profile Compiler) or vi/notepad to play with for this job.


I hope to be helpful by describing my case. I needed to provision and manage about 40 SPA phones distributed in several locations (and for different companies) around my nation. After some design consideration, I've choosen to make an XML file named spa$PSN.cfg available via TFTP at each location (the TFTP server IP address is provided as DHCP option to the phones), which provides the following fields:


 

 

    http://provision.mypublicdomain.com/companyname/spa$PSN.cfg

 

 

    http://provision.mypublicdomain.com/companyname/$SN.cfg

 


On the other and, the web server http://provision.mypublicdomain.com publishes all configuration files compiled and encrypted with the command "spc --scramble [sharedkey] filename.txt filename.cfg"


The file spa$PSN.cfg contains all common settings I whish to define for the specific company (timezone, language, firmware version, dictionary files, interval time for configuration resync, etc.). firmware and dictionary files are also provided via HTTP by the same web server.


The file $SN.cfg contains user-specific configurations (SIP account username and password, BLFs, speed dials, etc.).


Al text files are in the "proprietary plain-text" format described at page 37 in the document "Cisco Small Business IP Telephony Provisioning Guide", and their "change management" is maintained by using the good old RCS (Revisions Control System) method on the same unix server.


That implementation fits pretty well for me and several customers I have deployed the same "provisioning system" for, the biggest of whom is operating about 100 SIP phones.