Question regarding Vendor Config File

[Dan Morphis]

I can shed some light. The vendor config file is the configuration file you
upload to the CPE usually through the GUI on the CPE. The format of the
file will be specific to the CPE vendor. The config file for SmartRG (and
other Broadcom based CPEs) is an XML representation of the TR069 object
model of the device. While the older Thomson's its in ini file format.

Currently, you have to manually tell the CPE to download the configuration
file. Be aware though, when the CPE applies the config file, it will be
factory defaulted. So if you send the config file to any CPE's that have
customers assigned to it, you will need to set the pppoe credentials and
other settings specific to your environment.

On Tue, Jul 21, 2015 at 2:05 AM, Prashant Upadhyaya <praupadhyaya at gmail.com>
wrote:

> Hi,
>
> I have a few questions regarding the concept of Vendor Config File in
> TR-069.
> What does it exactly represent for ACS ?
> Is it a snapshot of _all_ the parameters of a CPE at a single place (the
> root model supported by CPE as well as vendor specific extensions) ?
> How is the lifecycle of this config file managed.
> Eg. if the version at CPE and ACS mismatch, then ACS should ask CPE to
> download it.
> But how would the version typically change at the ACS itself ? Eg. should
> the ACS bump up the version everytime the operator changes some CPE
> parameter at ACS or is there some different scenario.
> Can the version change at CPE automatically and in that case, should the
> CPE ask the ACS to upload it.
>
> Basically, if somebody can shed more light on this concept in TR-069 from
> their practical experience, that will be great.
>
> Regards
> -Prashant
>
>
> _______________________________________________
> Users mailing list
> Users at lists.genieacs.com
> http://lists.genieacs.com/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genieacs.com/pipermail/users/attachments/20150721/742ae8b0/attachment.html>