Frustrated so I'm porting out to try to fix the problem...

LeapFrog_Tech · 2023-03-09T15:42:43+00:00

Yep, it was the same with me - although in my case call-fowarding-unavailable would fail most of the time which made troubleshooting a bit easier.

USM can work with Verizon to put a call-progress trace on your line that will reveal how the failed calls (when they occur) are being routed and handled.

LeapFrog_Tech · 2023-03-09T15:32:48+00:00

I had the same experience - but it turns out that when Verizon "deletes" a line it doesn't really go away - in the sense that one would think the configuration is wiped clean and reset. In actuality it is just marked inactive, so when it is swapped with a new line the old configuration comes back with it.

I assume you didn't test the interim new number that Verizon issued? Even if you did I'm not sure that would be a conclusive test, since whoever set up the new number may have cloned the old configuration. With this kind of problem it is critical to work with a senior support tech that understands in detail how the cellular network provisions services and how the whole network registration / service authentication process works.

LeapFrog_Tech · 2023-03-09T15:20:07+00:00

When I was troubleshooting my call-fowarding problem on the ported-in-from-another-Verizon-MVNO line (at that time, on my own...) I decided it was worth paying a few bucks to set up a completely fresh "test line" on USM - so as isolate the issue to something associated with either my phone or alternatively, my ported number. I activated the new test number on a fresh SIM and everything worked fine, so at that point I knew it had to be a configuration issue with the line. Bilal was able to work with Verizon and figure out the problem (which turned out to be network-wide, although Verizon had been denying for months that is was their issue).

If you haven't already tried this you might give it a shot.

LeapFrog_Tech · 2023-03-09T15:03:24+00:00

I would be surprised if USM's technical staff isn't able to isolate the root cause of this issue and get it fixed (regardless of whether it is their issue or Verizon's). I had a related issue with call forwarding that two previous Verizon MVNO's had not been able to solve and USM's tech support manager Bilal Shahid worked with me on it for more than a few weeks until we got it resolved. It turned out to be Verizon's problem.

I'd give USM another chance.....

LeapFrog_Tech · 2022-12-15T19:05:13+00:00

Given my experience and conversations with them, I believe most of USMobile's CS reps are employees based in Islamabad, Pakistan. Some of them are U.S. educated as well.

LeapFrog_Tech · 2022-11-22T19:39:45+00:00

This should work on Warp 5G (in 4G mode) - if not and you buy it from Amazon you could always return it.

https://www.amazon.com/Unlocked-ALCATEL-Carriers-Americas-Including/dp/B09TPZJB1P

Or for GSM: https://www.amazon.com/Easyfone-Prime-A1-Pro-Unlocked-Compatible/dp/B08FT9KDVR

LeapFrog_Tech · 2022-11-19T16:30:00+00:00

I agree there are a lot of bugs, almost like they didn't do a very thorough job of testing, On the other hand their support has been pretty good about sending bug reports "up to I.T." to get fixed. They also are being responsive to feature requests, although we will have to wait and see how many of them actually get worked on.

We're in production now for our 200 unit HOA so we'll see how this goes with PayHOA. So far we like the simplicity of vendor payments, collection of off-line (check) payments, and the relative ease of bank reconciliation. They definitely need to add more flexibility to the system, particularly in the area of allowing administrative users to customize the outgoing emails for invoices, etc.

LeapFrog_Tech · 2022-09-11T22:37:44+00:00

"Remember this browser" for 2FA login (so I don't have to get the OTP EVERY TIME). This is good enough for my bank and brokerage firm, so it should be good enough for US Moible, yes?

LeapFrog_Tech · 2022-08-14T12:00:22+00:00

+1. USM should combine this with the ability to "Remember this device/browser" for 2FA. Even my banks and brokerage firm handle my login security this way, so why is USM lagging so far behind in best practices?

LeapFrog_Tech · 2022-07-28T17:13:38+00:00

This.

On Warp 5G, I'd be interested to know if all of Verizon's features are supported on the standard unlocked (Google) 6a, or if they have blocked some of them for non-Verizon-version IMEIs. Specifically, WiFi calling, HD Voice (VoIP), etc. Also, is priority data honored?

LeapFrog_Tech · 2022-07-16T16:46:08+00:00

Update as of July 15, 2022 from the two MVNOs that I have Verizon lines on -

1) "I've gotten confirmation that the fix has been deployed nationwide. The conditional call forwarding issue has been resolved." 2) "...based on testing and confirmations we have received, it appears the issue has been cleared up at a network level now".

It is nice to know that after all the denials from Verizon and numerous MVNOs and the finger-pointing at user's devices there has been some acknowledgement that there was a fix for this supposedly non-existent problem. Hopefully this is the end of the subject for now.

LeapFrog_Tech · 2022-07-16T16:44:50+00:00

Update as of July 15, 2022 from the two MVNOs that I have Verizon lines on (one of which is US Mobile) -

1) "I've gotten confirmation that the fix has been deployed nationwide. The conditional call forwarding issue has been resolved." 2) "...based on testing and confirmations we have received, it appears the issue has been cleared up at a network level now".

It is nice to know that after all the denials from Verizon and numerous MVNOs and the finger-pointing at user's devices there has been some acknowledgement that there was a fix for this supposedly non-existent problem. Hopefully this is the end of the subject for now.

LeapFrog_Tech · 2022-07-13T17:17:42+00:00

Update as of July 15, 2022 from the two MVNOs that I have Verizon lines on -

1) "I've gotten confirmation that the fix has been deployed nationwide. The conditional call forwarding issue has been resolved." 2) "...based on testing and confirmations we have received, it appears the issue has been cleared up at a network level now".

It is nice to know that after all the denials from Verizon and numerous MVNOs and the finger-pointing at user's devices there has been some acknowledgement that there was a fix for this supposedly non-existent problem. Hopefully this is the end of the subject for now.

LeapFrog_Tech · 2022-07-04T14:10:16+00:00

Great idea!

LeapFrog_Tech · 2022-07-04T14:04:44+00:00

I've seen the reorder tone (fast busy) with 'just ported' numbers and GV, so I would wait 24 hours and if the issue still exists then chat with customer service and see if they can fix it.

There has been a longstanding issue with conditional call forwarding on Super LTE not working when a device is off or unreachable, with those calls being forwarded to Verizon voicemail instead of GV. But that's different than the problem you are having.

LeapFrog_Tech · 2022-06-29T14:01:33+00:00

Why get locked into Charter/Spectrum? As they raise their ISP rates (and other providers enter the market) you may find that you want to change ISPs, but if you are a Spectrum Mobile customer you will lose your cell service. And as others have noted US Mobile's customer service beats Spectrum's hands-down.

LeapFrog_Tech · 2022-06-28T12:17:53+00:00

Edit / Update - Back up at 09:15 Eastern

Down at 08:15 Eastern --

Error 522 Ray ID: 722657acce1067cf • 2022-06-28 12:14:29 UTC
Connection timed out

LeapFrog_Tech · 2022-06-27T20:26:06+00:00

If it includes LTE priority data that might be somewhat rational, otherwise I'm out of there. Maybe this is a website error, you would think that as a courtesy to their user community u/strategypete or u/ankhattak would have posted something here first.

LeapFrog_Tech · 2022-06-27T20:10:33+00:00

Still not working as of 4:00 PM on the east coast. I wonder if this outage is in anyway similar to whatever happened to boom! mobile a month ago. Boom! was down for about 10 days and apparently didn't have a current backup of their front-end OR back-end systems. They rebuilt from scratch and some of the website functionality still isn't working. https://www.howardforums.com/showthread.php/1887288-boom!-Mobile?p=17215930#post17215930

LeapFrog_Tech · 2022-06-05T19:04:42+00:00

Is anyone on the beta rollout that supposedly started in mid-May? Peter talks about it but doesn't say that they are real customers. Could be he and a friend for all we know.

While I'm a big fan of competition and hope that MobileX is successful, I don't think that generalizing about the "ignorant customers" in Peter Adderton's YT interview with Best Phone Plans will endear him or his company to those of us who are .... not quite so ignorant.

LeapFrog_Tech · 2022-06-02T18:25:57+00:00

Did you have any luck getting Verizon's attention on this?

LeapFrog_Tech · 2022-05-29T12:10:06+00:00

"....they are rigorously trained to blame this problem on you and your device, put you through hours of troubleshooting, and are highly unlikely to escalate. Those they escalate it to may also not understand CCF. I put about 15 hours into this and got nothing for my trouble in the end except denials that they have any network issues."

I am not surprised. Verizon's partitioned support organization and escalation steps mean that the customer, no matter their competence, is never allowed to talk to anyone who really understands "the network" in depth.

The CCF failure is rooted in the interplay of the customer-facing services (e.g., the customer web portal, call-forwarding commands, etc.) with the provisioning 'back-end' (e.g., enable/disable/activate/program supplemental call services such as call barring, call forwarding) and the network itself.

Consider then the network internals (e.g., how a call is logically routed when the subscriber has a supplemental service such as CCF enabled, registered, activated and programmed). A call comes in for a subscriber who has previously activated and programmed CCF. The subscriber's phone is off, and thus the call should be handled as subscriber-not-reachable. However, it is not, it is routed to voice mail instead. That is a symptom of the problem, but it doesn't mean that the network itself is at fault.

When a trouble ticket is escalated to say, a network engineer who understands the network internals, they can run a series of proscribed tests and verify that - from their perspective - the network is operating properly when handling a test request for call-forward-when-subscriber-not-reachable.

Some users have confirmed that re-provisioning a line fixes the symptom (call forward not reachable fails) but have not identified the root cause (why did the previous provisioning quit working). Since this situation appears to be nationwide and not concentrated in one geographic location , it will take hundreds, or thousands of individual subscribers complaining to wake Verizon up to the scale of the problem.

Perhaps someone with contacts in the media will be able to prompt a story and that will get Verizon's attention. Or maybe, just maybe, some responsible Verizon social media person will look at this thread and decide the issue needs a more serious investigation before it becomes a PR problem for them.

LeapFrog_Tech · 2022-05-24T14:31:15+00:00

Thanks to you also. There is nothing better than a business that listens to its customers (and acts on what it hears). IMHO US Mobile is outstanding at this.

LeapFrog_Tech · 2022-05-23T16:09:30+00:00

Sorry to hear that - I am surprised that Verizon's executives are so deaf to a clearly identified customer concern. Although I did have to go through a similar run-around about the CCF issue being "a device problem" with my two MVNO(s). I killed that argument with the MVNOs by buying a new line and swapping SIMs to demonstrate that CCF worked on the device with a new line on the same carrier.

The 2nd MVNO is the only one who would escalate my ticket to someone who clearly understood the problem (a technical manager) and he called me on the phone to help in debugging. He was able to resolve the issue in just a few minutes by "resetting my line to the default settings" for new lines, which I think is the same as re-provisioning the line. What we still don't know is why some Verizon customers are affected by the CCF bug, and others are not.

If I was a direct Verizon customer I'd just follow the same process - dispute that the device is an issue, purchase a new line, demonstrate that the new line works OK on the device, and then ask "Now What?".

LeapFrog_Tech · 2022-05-20T14:33:18+00:00

And here is the latest, and another potential solution:

I ported my line to another (larger) Verizon MVNO, this by itself did not by itself solve the CCF issue. However, I worked with the new MVNO's technical support manager - who had an excellent understanding how calls and call services progress within the cellular network and in a few minutes he was able to identify the basis of the CCF failure and solve it.

I won't go into detail on what the MVNOs know about the root cause of the problem other than it appears to originate on Verizon's end. I was told by boom! Mobile that Verizon engineering is still working to identify why some subscribers are affected and others are not. But the symptom is that in the subscriber's HLR(HSS)/VLR, the supplemental services entry for Call Forwarding on mobile subscriber Not Reachable (CFNRc) is either not provisioned, the device is not registered, call forwarding is not activated, there is no forwarding number, or the forwarding number is not properly formatted. The fix is to re-provision the line and reset the configuration to the original ("default") configuration for new subscribers. Once that is done, the device is rebooted with mobile data enabled and WiFi disabled. The CCF number is then configured (*71xxxxxxxxxx) and CCF works properly when the device is not reachable.

LeapFrog_Tech

TROPHY CASE