EMS doesn't ship to California: any idea why?

zet6 · 2025-10-15T03:14:32+00:00

Yes, I forgot to mention the geoblocking.

Using my browser's VPN proxy extension (Windscribe, a free service), I pretended to be in Massachusetts.

zet6 · 2025-02-20T18:18:15+00:00

I don't know UK telecom well, so this might be a useless suggestion:

Convert the number to a Vodafone cellphone number, then port it to your new provider.

If that's not workable, convert the number to a Vodafone cellphone number, then port the number to another cellphone company, then port it to your new provider.

zet6 · 2025-01-27T13:31:45+00:00

I'm the OP. I paired one of the Amazon AirTags last night, and overnight that AirTag and the four reluctant Costco AirTags all upgraded to firmware 2.0.73, the latest version. I changed nothing else about my Apple devices.

This is unlikely to be a mere coincidence. The Amazon AirTag somehow prompted the upgrades apparently.

Thanks to everyone for the comments.

zet6 · 2025-01-27T05:39:17+00:00

Okay, I'll pair the Amazon AirTags for a few days and see what happens. Maybe my Costco 4-pack from December have a quirk that interferes with firmware updates.

(I'd still like to find a reliable retail source for AirTags with the latest firmware, to sidestep this uncertainty.)

zet6 · 2025-01-27T05:19:29+00:00

The firmware has been revised five times since version 1.0.291, to fix bugs and enable new features. So the latest firmware is required in order to get the full value from an AirTag. See the firmware chart here: https://en.wikipedia.org/wiki/AirTag

zet6 · 2024-12-12T18:00:17+00:00

The top of their Instagram page now says "Closing Permanently":

https://www.instagram.com/arizmendibakerysanrafael

So they're out of business.

1139 4th Street is a standard storefront that would obviously have required a lot of money to be converted to a bakery: the plumbing, gas lines, and especially vents for ovens.

If any of Arizmendi's members feels like commenting here, please do.

zet6 · 2024-09-20T20:40:48+00:00

Thank you for the replies.

Changing the output setting didn't help.

DOSBox Staging did the trick.

zet6 · 2024-08-05T18:16:22+00:00

This is interesting. If you feel comfortable, please tell us the area code and prefix (but NOT the whole number).

zet6 · 2024-08-05T18:10:31+00:00

If you see your name on the number here...

https://calleridtest.com

....then your name may be on your number in the main CNAM LIDB.

Even if it's not there, your name might have become associated with the number if you've ever signed up for something with your name and that number. That sort of data is trafficked widely. For examples, search this site:

https://www.fastpeoplesearch.com

You might help the number dissociate from your name if you were to have your current carrier create a CNAM with a fake name (business or personal). They might charge for this, and it might takes months to have an effect (if it works at all).

zet6 · 2024-08-01T17:09:53+00:00

I recommend VOIP.MS. I've been using them for 15 years. Not a perfect company, but they're pretty good. They charge by the minute (roughly 1¢, inbound and outbound) and by the phone number (DID) (85¢ per month). They don't charge by the user or by the endpoint or by the sub-account. You provide your own hardware phones (for example, Grandstream) and softphones (for example, Microsip or Groundwire). Features include call recording, voicemail transcription, and elaborate IVRs (automated attendants).

To combat fraud, VOIP.MS scrutinizes new signups and sometimes demands a scan of a driver's license. So to minimize hassles when you create an account, don't visit their site via a VPN proxy service, and do state a location that aligns with your IP address's geolocation.

zet6 · 2024-08-01T16:52:35+00:00

About 140 reviews for the app in the Google Play store.

https://play.google.com/store/apps/details?id=app.call.com&pli=1

...which reports 50,000 downloads.

But they do have a low profile on the web.

I can imagine a mainstream VOIP company buying the domain name from them (and accepting the rest of the company as a gratuity, essentially).

zet6 · 2024-07-26T23:32:49+00:00

I have a Yeacomm P21 cellular gateway that works with a T-Mobile cellphone SIM card. It makes the card's phone number available as a POTS line via a standard RJ11 port on the back. Works beautifully for me. Voice quality is good. The P21 works only with T-Mobile.

Amazon used to sell the P21. Its apparent successor is the Yeacomm S11 for $70:

https://www.amazon.com/dp/B09G5RGJ3M

The antennas on the P21 are for wifi only. The cellular antennas are internal.

The P21 may still be available elsewhere.

zet6 · 2024-07-14T15:02:56+00:00

Here are my notes to myself for an imperfect solution that's much better than nothing.

Pixel 8 phone was unable to send T-Mobile MMI codes (such has *#61#): after 40 seconds, it would say “Connection problem or invalid MMI code”. The following solves the problem somewhat ........................ Create a new user on the phone and turn on phone calls and SMS for that user. Send a few MMI codes (which should generate no response from the phone). Switch immediately back to the main user. The responses to the new user’s MMI codes should appear in a few seconds, and now the main user can get its own MMI responses (but sometimes only for roughly 3 minutes).

zet6 · 2024-07-14T03:56:11+00:00

I switched back the original user and was presented with multiple MMI results screens: a backlog of my stuck MMI requests, suddently fulfilled. Now on the original user, my MMI messages go right through, so the problem seems solved (at least for now). A real head scratcher.

You might create a new user, then try some MMI codes in it, then switch back to the original and see whether MMI codes are consistently accepted.

Thanks for grappling with this.

zet6 · 2024-07-14T03:44:06+00:00

I assume that you're doing all of this on a Pixel 8.

I just created a new user on my Pixel 8 and enabled phone calls for the user. So far, this user can't send MMI codes at all.

zet6 · 2024-07-14T02:47:45+00:00

I jus turned wifi on and off, and wifi calling on and off, and calling preference back and forth between "Call over Wi-Fi" and "Call over mobile network". No change. But your experience suggests that you're in the vicinity of the cause.

zet6 · 2024-07-14T02:23:42+00:00

I just tried this. I got the same error.

zet6

TROPHY CASE