[VoiceOps] Cisco linksys spa 942 and tftp

[Ujjval Karihaloo]

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>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110701/f5fb35bd/attachment.html>