OP seems to want to route /64 or larger to each customer, but can only have 3000 total entries larger than /128 in the expensive routers his firm owns.
Essentially the hardware doesn't support scaling a /64 or /56 to each customer, leaving OP in a terrible position when it comes to proper IPv6 deployment.
When you look at Ziply Fiber, they seem to be ripping out these types of Enterprise grade routers left and right in favor of a simple Linux box doing routing. I think a large portion of why they're doing this is due to limitations like what OP is experiencing
Never mind the actual performance issues that I keep seeing in production deployments.
We have large networks that are essentially rolling on autopilot totally unmanaged, like Lumen'e recently sold Quantum Fiber asset that is now owned by AT&T holding company Forged Fiber 37 LLC
No native IPv6 still on this forgotten about network, 6RD keeps having weird routability issues, but if you just disable IPv6 everything works fine.
Scaleway is a huge abuse platform, the same IPs on their network continue day after day to blast out login and bruteforce attempts. Drop their ranges and suddenly your logs get a lot quieter with no user facing impacts.
VoIP.ms is hard to port into and out of, I've repeatedly seen them drop part of the account number when transferring a number, then drag their feet for days thereafter on resubmitting the port.
Always ask for the Port Order Number (PON) so you can follow up with the other carrier to see what they received from VoIP.ms
Google Voice is requiring ID verification now, and porting your phone number out is difficult as they charge an unlock fee and you get to deal with Bandwidth.com's port out shenanigans as they are the real underlying carrier for Google Voice.
What can be open sourced (GrapheneOS) already is, and the remainder is business logic that they have described for the MVNO that is likely carrier specific and tied to the oddball MVNO platform they are using.
Very hard to make the latter usable by anyone else IMO.
Mitigating SIP and TDM spoofing requires broad cooperation among every other Telecom provider. That doesn't exist today, you can't prevent people from spoofing your number.
There is a lot of money floating around major cities in the US. So many nonprofit entities are preserving some cultural niche thanks to their older patrons using their qualified minimum distribution to fund a long lasting endowment.
I feel like you see this less in other parts of the world where people don't have tens of thousands of dollars from their retirement savings that they have to take out each year, and they would rather give it tax free to their favorite nonprofit than take a haircut with taxes and then do nothing with the money
Teams is shovelware. Force bundled, with questionably reliable messaging, okay video calling (if your organization policies don't break it), and a fairly useless Phone System component that misbehaves often.
Great for organizations that believe these forms of communication should be an afterthought that has rough edges and inconsistent reliability.
The recent changes to end webhook support, kill Linux desktop support and do yet another rewrite are inane. Don't expect features you use today in Teams to work in 2 years...
What was the last successful French software project in the Telecom or Conferencing space?
This project has been forced into the hands of 40k users, but likely due to a plethora of bugs and user experience issues they are picking a date far in the future for broad deployment.
Belledonne Communications has been actively breaking Linphone, conference calling broke back in August 2023 for example and remains broken to this day.
If we look to Québécoise in Canada, SFLPhone would crash after 2 dozen calls, and Jami (formerly GNU Ring) is still a beta quality product with some neat DHT concepts that I'd love to see work.
The French sphere has a software delivery and quality problem. The user rejection factor will remain high until they choose to fix the bugs that cause users to run away.
All large organizations are political. Some employees choose to ignore the office politics, but that choice might find their management not ensuring they survive the next round of layoffs.
Essentially the hardware doesn't support scaling a /64 or /56 to each customer, leaving OP in a terrible position when it comes to proper IPv6 deployment.
When you look at Ziply Fiber, they seem to be ripping out these types of Enterprise grade routers left and right in favor of a simple Linux box doing routing. I think a large portion of why they're doing this is due to limitations like what OP is experiencing