simfree

Having to retype the search phrase is just a plain old ux bug

ICM on a Saturday and Connections Museum on a Sunday is a delightful pairing! Close to the airport too if your just popping by on a layover, though plan on 2 to 4 hours for each

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.

Not really, I always have to choose an exit node for Tailscale to allow me internet access on Mac while connected to a Tailnet on cellular.

PCMU and PCMA voice frames are 20ms or 40ms, and no one is running with no jitter buffer, so your 30ms number doesn't make sense.

Even circuit switched networks are not often below 30ms, to hit that you'd need to make a local phone call on a fully analog circuit.

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.

Thank you for being honest and up front about your background. It is very meaningful that you do not try to hide it, and I feel it increases trust.

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.

Which vendor did you choose to partner with to provide the mobile core (IMS and such)?

I've talked to a few tangentially and it seems like an interesting space.

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.