Cisco linksys spa 942 and tftp
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. 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 Any direction would help. Ujjval K
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
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
The Linksys SPA9xx series has some real quirks related to TFTP. I've had a lot more consistent behavior with HTTPS. And in general, it will only download files when the phone thinks it's time to do so. They've intentionally added random delays. The Linksys might reboot, then have default delays of 15 minutes before it downloads the configuration. It's possible that it will download the file you told it too in the Provisioning rule . . . eventually. The BroadSoft partner config guides can be a nice start, but (a) there are sometimes errors, and (b) vendors, like Cisco/Linksys, can change things faster than BroadSoft can update their documentation. mark at ecg.co | +1-229-316-0013 | http://ecg.co/lindsey On Jul 1, 2011, at 11:26 AM, 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.
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
Any direction would help.
Ujjval K _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Mark R Lindsey wrote:
The Linksys SPA9xx series has some real quirks related to TFTP. I've had a lot more consistent behavior with HTTPS.
Never tried TFTP, but will vouch for the reliability of HTTP provisioning.
And in general, it will only download files when the phone thinks it's time to do so. They've intentionally added random delays. The Linksys might reboot, then have default delays of 15 minutes before it downloads the configuration. It's possible that it will download the file you told it too in the Provisioning rule . . . eventually.
This is true, but you can force a resync: http://<address>/admin/resync?[--key <key>] https://<server>/<url>.cfg If you don't use HTTPS, you can omit the key stuff.
The BroadSoft partner config guides can be a nice start, but (a) there are sometimes errors, and (b) vendors, like Cisco/Linksys, can change things faster than BroadSoft can update their documentation.
The SPA series, with the exception of the SPA525G, has been stable and unchanged for many years. However it was ignored/maligned/ill supported by many vendors. I'm not sure why. Everyone here would rather work on those phones than any other, and all of us have them on our desks. We've deployed more SPA phones than any other. -- Carlos Alvarez TelEvolve 602-889-3003
Thx guys: The behaviour on the Profile rules seems to be little unpredictable when using Broadsoft Guide. Here is what we have tried:
From the Phone UI point it to tftp://a.b.c.d/spa952.xml
The above file has 2 rule entries like this? <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <flat-profile> <Resync_On_Reset>Yes</Resync_On_Reset> <Resync_Periodic>10</Resync_Periodic> <Transport_Protocol group="Provisioning/Configuration_Profile">tftp</Transport_Protocol> <Profile_Rule>tftp://1.1.1.1/942System.xml</Profile_Rule> <Profile_Rule_B ua="na">tftp://1.1.1.1/$MA.xml</Profile_Rule_B> </flat-profile> When we hand craft the 2 files with cherry picked configurations, Phone downloads first the system file and then the MAC.xml files..and comes up. However we we use the Broadsoft suggested templates, it downloads only the system file and not the mac.xml file and lines never register obviously I wanted help understanding what logic the phone uses to download each file and where does it look for pointers from one file to the other. Thx in advance... On Fri, Jul 1, 2011 at 10:35 AM, Carlos Alvarez <carlos at televolve.com>wrote:
Mark R Lindsey wrote:
The Linksys SPA9xx series has some real quirks related to TFTP. I've had a lot more consistent behavior with HTTPS.
Never tried TFTP, but will vouch for the reliability of HTTP provisioning.
And in general, it will only download files when the phone thinks it's time
to do so. They've intentionally added random delays. The Linksys might reboot, then have default delays of 15 minutes before it downloads the configuration. It's possible that it will download the file you told it too in the Provisioning rule . . . eventually.
This is true, but you can force a resync:
http://<address>/admin/resync?**[--key <key>] https://<server>/<url>.cfg
If you don't use HTTPS, you can omit the key stuff.
The BroadSoft partner config guides can be a nice start, but (a) there are
sometimes errors, and (b) vendors, like Cisco/Linksys, can change things faster than BroadSoft can update their documentation.
The SPA series, with the exception of the SPA525G, has been stable and unchanged for many years. However it was ignored/maligned/ill supported by many vendors. I'm not sure why. Everyone here would rather work on those phones than any other, and all of us have them on our desks. We've deployed more SPA phones than any other.
-- Carlos Alvarez TelEvolve 602-889-3003
______________________________**_________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/**mailman/listinfo/voiceops<https://puck.nether.net/mailman/listinfo/voiceops>
Ujjval Karihaloo wrote:
When we hand craft the 2 files with cherry picked configurations, Phone downloads first the system file and then the MAC.xml files..and comes up. However we we use the Broadsoft suggested templates, it downloads only the system file and not the mac.xml file and lines never register obviously I wanted help understanding what logic the phone uses to download each file and where does it look for pointers from one file to the other. Thx in advance...
I have no Broadsoft experience and never tried TFTP with these phones, so I can't give you a lot more than I have. However I will note that we use filename.cfg, not filename.xml, as do all the examples from Linksys. It may or may not matter, worth trying it the other way. I would also suggest trying HTTP configuration. -- Carlos Alvarez TelEvolve 602-889-3003
In case you don't have a copy, this document goes over the provisioning process in pretty good detail: http://www.cisco.com/en/US/docs/voice_ip_comm/csbpvga/ata/provisioning/guide... On Fri, Jul 1, 2011 at 1:01 PM, Ujjval Karihaloo <ujjval at simplesignal.com> wrote:
Thx guys:
The behaviour on the Profile rules seems to be little unpredictable when using Broadsoft Guide.
Here is what we have tried:
From the Phone UI point it to tftp://a.b.c.d/spa952.xml
The above file has 2 rule entries like this?
?<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <flat-profile> <Resync_On_Reset>Yes</Resync_On_Reset> <Resync_Periodic>10</Resync_Periodic> <Transport_Protocol group="Provisioning/Configuration_Profile">tftp</Transport_Protocol> <Profile_Rule>tftp://1.1.1.1/942System.xml</Profile_Rule> <Profile_Rule_B ua="na">tftp://1.1.1.1/$MA.xml</Profile_Rule_B> </flat-profile>
When we hand craft the 2 files with cherry picked configurations, Phone downloads first the system file and then the MAC.xml files..and comes up.
However we we use the Broadsoft suggested templates, it downloads only the system file and not the mac.xml file and lines never register obviously
?I wanted help understanding what logic the phone uses to download each file and where does it look for pointers from one file to the other.
Thx in advance...
On Fri, Jul 1, 2011 at 10:35 AM, Carlos Alvarez <carlos at televolve.com> wrote:
Mark R Lindsey wrote:
The Linksys SPA9xx series has some real quirks related to TFTP. I've had a lot more consistent behavior with HTTPS.
Never tried TFTP, but will vouch for the reliability of HTTP provisioning.
And in general, it will only download files when the phone thinks it's time to do so. They've intentionally added random delays. The Linksys might reboot, then have default delays of 15 minutes before it downloads the configuration. It's possible that it will download the file you told it too in the Provisioning rule . . . eventually.
This is true, but you can force a resync:
http://<address>/admin/resync?[--key <key>] https://<server>/<url>.cfg
If you don't use HTTPS, you can omit the key stuff.
The BroadSoft partner config guides can be a nice start, but (a) there are sometimes errors, and (b) vendors, like Cisco/Linksys, can change things faster than BroadSoft can update their documentation.
The SPA series, with the exception of the SPA525G, has been stable and unchanged for many years. ?However it was ignored/maligned/ill supported by many vendors. ?I'm not sure why. ?Everyone here would rather work on those phones than any other, and all of us have them on our desks. We've deployed more SPA phones than any other.
-- Carlos Alvarez TelEvolve 602-889-3003
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Thx a lot. -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Robert Johnson Sent: Friday, July 01, 2011 11:19 AM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Cisco linksys spa 942 and tftp In case you don't have a copy, this document goes over the provisioning process in pretty good detail: http://www.cisco.com/en/US/docs/voice_ip_comm/csbpvga/ata/provisioning/gui de/Cisco_Small_Business_IP_Telephony_Provisioning_Guide.pdf On Fri, Jul 1, 2011 at 1:01 PM, Ujjval Karihaloo <ujjval at simplesignal.com> wrote:
Thx guys:
The behaviour on the Profile rules seems to be little unpredictable when using Broadsoft Guide.
Here is what we have tried:
From the Phone UI point it to tftp://a.b.c.d/spa952.xml
The above file has 2 rule entries like this?
?<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <flat-profile> <Resync_On_Reset>Yes</Resync_On_Reset> <Resync_Periodic>10</Resync_Periodic> <Transport_Protocol group="Provisioning/Configuration_Profile">tftp</Transport_Protocol> <Profile_Rule>tftp://1.1.1.1/942System.xml</Profile_Rule> <Profile_Rule_B ua="na">tftp://1.1.1.1/$MA.xml</Profile_Rule_B> </flat-profile>
When we hand craft the 2 files with cherry picked configurations, Phone downloads first the system file and then the MAC.xml files..and comes up.
However we we use the Broadsoft suggested templates, it downloads only the system file and not the mac.xml file and lines never register obviously
?I wanted help understanding what logic the phone uses to download each file and where does it look for pointers from one file to the other.
Thx in advance...
On Fri, Jul 1, 2011 at 10:35 AM, Carlos Alvarez <carlos at televolve.com> wrote:
Mark R Lindsey wrote:
The Linksys SPA9xx series has some real quirks related to TFTP. I've
had
a lot more consistent behavior with HTTPS.
Never tried TFTP, but will vouch for the reliability of HTTP provisioning.
And in general, it will only download files when the phone thinks it's time to do so. They've intentionally added random delays. The Linksys might reboot, then have default delays of 15 minutes before it downloads the configuration. It's possible that it will download the file you told it too in the Provisioning rule . . . eventually.
This is true, but you can force a resync:
http://<address>/admin/resync?[--key <key>] https://<server>/<url>.cfg
If you don't use HTTPS, you can omit the key stuff.
The BroadSoft partner config guides can be a nice start, but (a) there are sometimes errors, and (b) vendors, like Cisco/Linksys, can change things faster than BroadSoft can update their documentation.
The SPA series, with the exception of the SPA525G, has been stable and unchanged for many years. ?However it was ignored/maligned/ill supported by many vendors. ?I'm not sure why. ?Everyone here would rather work on those phones than any other, and all of us have them on our desks. We've deployed more SPA phones than any other.
-- Carlos Alvarez TelEvolve 602-889-3003
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
There is some unpredictable behavior Ujjval K On Jul 1, 2011, at 10:37 AM, Carlos Alvarez <carlos at televolve.com> wrote:
Mark R Lindsey wrote:
The Linksys SPA9xx series has some real quirks related to TFTP. I've had a lot more consistent behavior with HTTPS.
Never tried TFTP, but will vouch for the reliability of HTTP provisioning.
And in general, it will only download files when the phone thinks it's time to do so. They've intentionally added random delays. The Linksys might reboot, then have default delays of 15 minutes before it downloads the configuration. It's possible that it will download the file you told it too in the Provisioning rule . . . eventually.
This is true, but you can force a resync:
http://<address>/admin/resync?[--key <key>] https://<server>/<url>.cfg
If you don't use HTTPS, you can omit the key stuff.
The BroadSoft partner config guides can be a nice start, but (a) there are sometimes errors, and (b) vendors, like Cisco/Linksys, can change things faster than BroadSoft can update their documentation.
The SPA series, with the exception of the SPA525G, has been stable and unchanged for many years. However it was ignored/maligned/ill supported by many vendors. I'm not sure why. Everyone here would rather work on those phones than any other, and all of us have them on our desks. We've deployed more SPA phones than any other.
-- Carlos Alvarez TelEvolve 602-889-3003
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (5)
-
abaird＠telesphere.com -
carlos＠televolve.com -
fasterfourier＠gmail.com -
lindsey＠e-c-group.com -
ujjval＠simplesignal.com