Now that a #partisipate client is at least started on @Codeberg at least two more things will be needed for 2024; a #troll gateway controller, and a #cardaver integration/collaboration server. Then everyone can be #beswitched with #switchcraft living on a pi-like device, which would kind of bring us back to what I originally had wanted to do with #sipcraft#voip #telephony last decade.

The curious thing about #sipcraft is that the backend data config model is being built directly from the dynamic config files of other components like #coventry rather than in a database.

I did turn around a fast 0.2.1 release of #coventry mostly to support 3 digit dialing plans to help cover what were #sipcraft use cases.

I am going to support compile time dialplans in coventry and eliminate the small diversity that now exists between #sipcraft and #coventry, consolidating on coventry development going forward.

@parlehaakon #coventry is a modern and lighter weight #sipwitch replacement focused on residential voip gateway uses, whereas #sipcraft is a more enterprise friendly modern and more complete sipwitch replacement with web/database driven dynamic provisioning over mqtt.

I might complete message delivery and basic messaging milestone before doing a new #coventry release, maybe even next week. #sipcraft has also come along nicely.

I have conveged #sipcraft and #coventry development, which will help speed up both. Principle differences include sipcraft will receive dynamic provisioning updates and heartbeat a provisioning server thru #mqtt

While in #sipcraft I had been experimenting with direct database access in the call server, I have considered switching to message queues so I could push provisioning configs when they change rather than catching them on infrequent database queries, as well as eliminate potential blocking operations in the call server.

I am happy to have completed migrating #coventry to @codeberg so I am going to finish #bordeaux and #sipcraft next. #codeberg is nice because its #gitea and there is community help. This is how I think #foss should generally work.

Maybe it is time to talk about what I think about for 21st century #telephony. #Bordeaux is for delivering containerized and device resident voice applications.

#Coventry will re-imagine residential phone services and home automation. #Sipcraft will do the same for small offices and facility automation. Both focus on messaging first communications and sip inter-operation. #Calypso will provide secure collaboration built on #zmq. All will use Bordeaux.