Wazo Platform: build carrier-grade programmable IP communication infrastructures

[onesmallcoin]

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.

[mathias44]

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.

[ignoramous]

Does Wazo compete with 2600hz's Kazoo [0] / Telestax's RestComm [1] or with OpenCORD [2] implementations? If not, I'm having trouble understanding what it really is... Can someone pls explain?

[0] https://github.com/2600hz/kazoo

[1] https://github.com/RestComm

[2] https://opencord.org

[JeromeP]

The whole idea behind Wazo Platform is to bring to the community a programmable platform for communication which is at the same time open & hybrid. Open: it uses the most standard programming language (Python vs. Erlang for Kazoo) to aim for the largest interoperability and to make it most accessible to anyone. Hybrid: the programmability are delivered neither as a service (Twilio), nor on a cloud-based platform (Restcomm) but as a product, so that you can use it from any kind of infrastructure (public or private clouds, bare metal) so as to keep the control on what you are building. The communication platform is made of open source components only, which are fully api-centric and cloud centric, so as to be in a position to manage every single component. The team behind Wazo is made of 15 developers from both open source Telecom and open source IT orchestration, as well as a strong community. Any feedback/contribution is welcome to make of Wazo Platform the missing open source communication stack for communication!

[taf2]

This looks more like open source twilio or plivo... Plivo originally being the open source twilio... of course this looks pretty early and I could not tell from http://www.wazo-platform.org/documentation/overview/webhook.... whether it supports xml tags like twilio / Plivo

But I was able to find 404 links which leaves me feeling this isn’t ready for prime time... regardless of being based on sound tech

[Hayku]

Hi, I'm new and I'm installing and testing the Wazo Platform UC use case, based on:

http://www.wazo-platform.org/install

But I get a couple of errors.

where is the best place to search for help?