Hi We use a multi-step process. First we use DHCP to pass the phone the tftp server IP address (option 150). Then the phone (by default) requests the file spa$psn.cfg (the phone replaces $psn with the model number, so for a 942 it will request spa942.cfg). This file is built on our TFTP server but is just used as a pointer file to fill in provisioning rules A and B which point to http urls to the system and device configuration files. So the system copies and loads this pointer file, reboots and upon reboot follows the provisioning rules it just loaded and requests via http the system and device files. If we are not in control of the DHCP process we web into the phone and set the provisioning rule manually to point to the tftp server's .cfg file. Adam Baird Telesphere Networks -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Carlos Alvarez Sent: Friday, July 01, 2011 8:43 AM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Cisco linksys spa 942 and tftp Ujjval Karihaloo wrote:
Hi
Anyone figured out the easiest way to have spa942 pull config files from a tftp server- file name conventions ..etc , that are known to work.
We use https since we pull configs over the wild internet, but the process *should* be the same for TFTP I would think. You can always go with http also. The easiest way to get started is to manually configure a phone through its web interface. Get everything set exactly as you want it. Then browse to: http://<phone ip>/admin/spacfg.xml You now have a good working file that you can modify as needed for your deployment.
Broadsoft partner config guide states to use .cfg extentions, but the phone seems to only like .xml. , butvstill doesnt pull all files - system file as well as MAC. xml
There are two config files for a typical setup, and both are .cfg extension. The first, defaults.cfg (or any name really) is where you set up, obviously, default settings for the organization, such as the server name, etc. It's easy to set them up departmentally, or by location, or whatever. defaults.eastcoast.cfg and defaults.westcoast.cfg for example. Any items from the above XML output can go in either this or the phone-specific file. The other is for individual phones, and again you can call it anything. You will specify this when you configure a phone. If you want full automation (DHCP option 66) then use the MAC address and have DHCP issue the URLs with the {MAC} variable in them. Otherwise go to a phone's web interface, and fill in the profile rule paths to the files. You will typically just use A and B profile rule lines. -- Carlos Alvarez TelEvolve 602-889-3003 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops