Hi, I was wondering if anyone could answer a couple of questions how this application interfaces with CPEs and how it compares to existing tools (TR-064/TR-069). So I understand messages are passed over http
1. how does the cpe then know where to get and set the relevant configuration data? Is this done automaticly or do I have to write additional code to interface with the specific device implementation from here?
(how posix compatible is this?)
2. How does this library scale? How many devices are you able to concurrently manage and how beefy of a machine\internet connection does it require?
Looks like a cool project I'm currently writing my own TR-064\TR-069 libary with plans on an ACS in python. I'll have to have a bit more of a read but some more flowcharts would be awesome, I love flowcharts for big picture stuff like this.
Hi,
The phone provisionning is not done using TR-06x as it is not relevant for these endpoints. We use https based provisionning to be closest to vendor specifications.
Documentation is here : http://www.wazo-platform.org/documentation/overview/provisio...
Regarding your 1st question : you can pass the provisionning server throw DHCP (it is explained on the doc link)
Regarding your second question : as the process is to deliver a flat file to a phone, it scales easily.
1. how does the cpe then know where to get and set the relevant configuration data? Is this done automaticly or do I have to write additional code to interface with the specific device implementation from here? (how posix compatible is this?)
2. How does this library scale? How many devices are you able to concurrently manage and how beefy of a machine\internet connection does it require?
Looks like a cool project I'm currently writing my own TR-064\TR-069 libary with plans on an ACS in python. I'll have to have a bit more of a read but some more flowcharts would be awesome, I love flowcharts for big picture stuff like this.