Newly added numbers don't work with T-Mobile!

[xinerevelle]

I finally got a local number for my MJ and my dad's (after months of "coming soon"...). The numbers can dial out, but cannot accept calls.

After hours and hours and hours on chat with tech support, and FINALLY being escalated to a higher level of tech support, we figured out that it was only T-Mobile cell phone numbers that could not call in to our MJ numbers.

I asked whether I should switch to the other newly available exchange in my area, and was told that I could if I liked. I asked whether it would work with T-Mobile... no response. I asked if I'd have to pay the $10 change fee for each line, and was told I was free to change if I wanted (not a real response)... sigh.

I was told repeatedly that they would fix it as soon as they could, but could not tell me if they've had this problem before, if they expect it to take awhile, or even whether they own all the numbers in a certain exchange since I have a friend in the same exchange that I can call with no problems (don't know if she's got mj though).

I told them I was very unhappy because now I have two unusable MJs, since most of my friends and family are on T-Mobile and they cannot call me. I would have thought they would've offered me some sort of compensation, and even hinted at it, but was offered nothing but an apology and a vague promise to work on it as quickly as possible. I'm not believing it. sigh.

I hope I can get this resolved soon, since I've just done some cost calculations on my landline ($20/month) vs. my time of use meter from the electric co., which was the only reason we were keeping a landline anyway. If I didn't go with MJ I would've gone with T-Mobile @home, but MJ was cheaper.

[az2008]

After hours and hours and hours on chat with tech support, and FINALLY being escalated to a higher level of tech support, we figured out that it was only T-Mobile cell phone numbers that could not call in to our MJ numbers.

It's been reported by others that new area codes/prefixes in MJ can be problematic because it takes awhile for other CLECs(?) to make the changes in their systems to recognize how to route a call to that number.

It will probably clear up in 2-3 weeks.

Mark

[xinerevelle]

While I've had that experience with new area code overlays in POTS, I expected that the "higher level" tech I was chatting with could have told me that and said, "Oh, we've had that problem before and it usually takes XX days to resolve at most." THAT would have been more helpful.

[aaronwt]

Your problem is not with MagicJack but with T-Mobile. You should be calling T-Mobile to find out why they are taking so long to update their system with the proper prefixes.
Why should MJ give you compensation for something that is T_Mobiles fault? To expect MJ to do that makes absolutely no sense.

I finally got a local number for my MJ and my dad's (after months of "coming soon"...). The numbers can dial out, but cannot accept calls.

After hours and hours and hours on chat with tech support, and FINALLY being escalated to a higher level of tech support, we figured out that it was only T-Mobile cell phone numbers that could not call in to our MJ numbers.

I asked whether I should switch to the other newly available exchange in my area, and was told that I could if I liked. I asked whether it would work with T-Mobile... no response. I asked if I'd have to pay the $10 change fee for each line, and was told I was free to change if I wanted (not a real response)... sigh.

I was told repeatedly that they would fix it as soon as they could, but could not tell me if they've had this problem before, if they expect it to take awhile, or even whether they own all the numbers in a certain exchange since I have a friend in the same exchange that I can call with no problems (don't know if she's got mj though).

I told them I was very unhappy because now I have two unusable MJs, since most of my friends and family are on T-Mobile and they cannot call me. I would have thought they would've offered me some sort of compensation, and even hinted at it, but was offered nothing but an apology and a vague promise to work on it as quickly as possible. I'm not believing it. sigh.

I hope I can get this resolved soon, since I've just done some cost calculations on my landline ($20/month) vs. my time of use meter from the electric co., which was the only reason we were keeping a landline anyway. If I didn't go with MJ I would've gone with T-Mobile @home, but MJ was cheaper.

[az2008]

Why should MJ give you compensation for something that is T_Mobiles fault? To expect MJ to do that makes absolutely no sense.

True. But, MJ should make it clearer when someone purchases a newly-available area-code or prefix that these problems may occur, and the process to fix them. The problem with MJ is that they don't disclose this at the time of purchase, and chat support doesn't seem to know anything about it either.

This ties into what I've said a million times: Most of MJ's problems with negative customer feedback is *self inflicted*. MJ seems to be *oblivious* to how it's behaviors will be construed from a customer perspective. This stuff is low-hanging fruit. It doesn't take much money or time just to mature the business processes and make it easy for customers to be *informed* and know what to do.

Having said that, MJ's still a great bargain at $1.66 a month. I'd be willing to pay $1.70 for a little better business conduct from Dan.

Mark

[mberlant]

This one is definitely in T-Mobile's court and not MJ's(YMAX's).

I can almost guarantee that YMAX distributes the proper MAC notification to all other carriers each time they assign and energize a number group on a CO switch. The evidence of YMAX having done this properly is that other phone companies (like Verizon) process received MAC notifications very quickly and calls from these phone companies go through within hours of activation.

T-Mobile is notoriously slow in processing received MACs, second only to the Sprint half of Sprint/Nextel.

[Vulture1340]

I finally got a local number for my MJ and my dad's (after months of "coming soon"...). The numbers can dial out, but cannot accept calls.

After hours and hours and hours on chat with tech support, and FINALLY being escalated to a higher level of tech support, we figured out that it was only T-Mobile cell phone numbers that could not call in to our MJ numbers.

I asked whether I should switch to the other newly available exchange in my area, and was told that I could if I liked. I asked whether it would work with T-Mobile... no response. I asked if I'd have to pay the $10 change fee for each line, and was told I was free to change if I wanted (not a real response)... sigh.

I was told repeatedly that they would fix it as soon as they could, but could not tell me if they've had this problem before, if they expect it to take awhile, or even whether they own all the numbers in a certain exchange since I have a friend in the same exchange that I can call with no problems (don't know if she's got mj though).

I told them I was very unhappy because now I have two unusable MJs, since most of my friends and family are on T-Mobile and they cannot call me. I would have thought they would've offered me some sort of compensation, and even hinted at it, but was offered nothing but an apology and a vague promise to work on it as quickly as possible. I'm not believing it. sigh.

I hope I can get this resolved soon, since I've just done some cost calculations on my landline ($20/month) vs. my time of use meter from the electric co., which was the only reason we were keeping a landline anyway. If I didn't go with MJ I would've gone with T-Mobile @home, but MJ was cheaper.

I had the same issue with Verizon Wireless. It took them a couple of days to fix. What surprised me was the fact that they called me personally on my MJ to inform me that the issue was resolved.

[freekshow]

I've got Alltel and had the same issue when I changed my MJ number. It took a week or so but it works fine now.

[xinerevelle]

OP here...

Well, it's now been over 3 weeks, and I'm still waiting for a fix. The sad part is that the ONLY way for me inquire about the problem's resolution is to get on the stupid chat system, try to explain to a CSR what's going on, ask for an update, explain AGAIN that I don't want to run the upgrade (LOL!), wait to get passed to a higher level tech, go through it all again, wait for him/her to read the notes, then find out that nothing has been done yet. Sigh. This is getting old. It takes me over 30 minutes just to inquire.

[mberlant]

Have you read and heeded the advice I gave you almost two weeks ago in this thread (not to mention the discussions in the other threads here with the identical problem)?

The problem is not in MJ, and MJ have no capacity to correct a problem that is 100% inside T-Mobile. Your only option is to call T-Mobile and tell them that you cannot reach a particular known working number. T-Mobile will ask for that number (your MJ number) and for the number of a telephone that is able to reach the number that cannot be reached from T-Mobile. They will then forward that information to the folks in T-Mobile who are responsible for implementing MACs, who will implement the one that had gotten overlooked.