Solved

LineLink drops calls with 3 beeps


Just set up my LineLink a few days ago.

It regularly drops both incoming and outgoing calls after a variable amount of time, always preceded by 3 beeps.

I've checked my connection speed and quality and it meets the T-Mobile standards.

Tech Support doesn't know what's wrong.

Anyone else had this problem?  What was the solution?

icon

Best answer by tmo_amanda 2 May 2017, 17:23

View original

70 replies

Userlevel 1
Badge +2

Interesting, I may have to call TMO and have them disable VM for LineLink and just use the VM on the phone system.  LineLink is still NOT a better solution than the old TMobile@Home.  My caller ID has never come back... 😠

I figured out why Link Link occasionally drops calls with 3 beeps.

It has to do with voice mails left on LineLink. For some reason if the LineLink system has unread voice mails then it keeps acting-up like this, dropping call etc.

I have tried doing a call forward and it worked for a long time until occasionally one or two VMs go into LinkLink# and boom it again drops calls.

I'd say try the above approach or call T-Mobile and disable VM on LinkLink# (if that is an option for you

I figured out why Link Link occasionally drops calls with 3 beeps.

It has to with voice mails left on LineLink. For some reason if the LineLink system has unread voice mails then it keeps acting-up like this, dropping call etc.

I have tried doing a call forward and it worked for a long time until occasionally one or two VMs go into LinkLink# and boom it again drops calls.

I'd say try the above approach or call T-Mobile and disable VM on LinkLink# (if that is an option for you

I figured out why Link Link occasionally drops calls with 3 beeps.

It has to with voice mails left on LineLink. For some reason if the LineLink system has unread voice mails then it keeps acting-up like this, dropping call etc.

I have tried doing a call forward and it worked for a long time until occasionally one or two VMs go into LinkLink# and boom it again drops calls.

I'd say try the above approach or call T-Mobile and disable VM on LinkLink# (if that is an option for you).

Userlevel 1
Badge +2

But LineLink is so much better and more sophisticated than the old @Home... *Sarcasm.  Mine hasn't dropped in awhile, but that's probably because I don't use it as much as I used to for outbound calls/voicemails/etc. because I can't have calls dropping when using as my business line.  Also, my call waiting, caller ID (phone number only) has never come back on LL, whereas it worked on @Home. Very frustrating to not see the number calling in when I'm already on a call.  Guess, still a fail on TMO's part with this.  😥

Scratch that -- it's still identically broken.

There seems to have been a firmware update this week or other backend change. I received a call from T-Mobile support to say they had fixed something and (in limited testing) the problem seems to have gone away. Other people in this thread who have not yet cancelled service may want to test.

Userlevel 1
Badge +2

Yeah, LineLink is nowhere near as reliable as the old @Home router, unfortunately.  I don't get the 3 beeps and dropped calls anymore...just dropped calls.  I will say the dropped calls have gotten less, but still there and any important calls I make (LL is a second office line for me), I use my normal house phone.  Also, call waiting, caller ID no longer works for me and it definitely is the LL system.  I've tried multiple phones hooked up to LL and put in a tech ticket with TMO about 9 months ago, but nothing.  The call waiting, caller ID worked on the @Home router with no problem and it's very frustrating it now doesn't work.  I wish TMO would fix this darn thing, it's a hassle to switch to another provider like Ooma, but I ultimately may have to do it at some point.  What a pain!  TMO, fix LL, please!

Just wanted to bump this thread. I've gone through the hassle and cost of replacing my Linelink device.  Of course it didn't make any difference.

Phone calls still drop, mostly outgoing and longer than a couple of minutes.

PLEASE FIX !!!

Today is February 26, 2018.  After almost a year of continually dropped calls, I've given up.  I cancelled my LineLink today. Good luck to the rest of you. If you still would like to be able to have a "home phone" give a try to Panasonic's Link2Cell.  It uses your cellphone to connect its traditional wireless handsets to a cell tower.  It'll use your cellphone minutes, but you can talk at home with a traditional wireless handset.

Userlevel 1
Badge +2

Well, this fix DIDN'T work.  Ok, I don't get 3 beeps anymore, BUT the call still DROPS.  Amanda:  Any other suggestions?  This is really frustrating and there has to be an answer to this as the old @Home service never did this.  LineLink is supposed to be a "newer", "better" technology and it drops calls at times it should not.

My Scenario:  I returned a call of a client and went to their voicemail.  Their voicemail message started and about halfway through (before the "beep" to leave a message) the call just dropped.  There were no 3 beeps, but that's really insignificant to this issue of dropped calls.  I will now have to call the client back again on another phone and leave a message.

Userlevel 1
Badge +2

I assume we need to "restart" the LL device...ie. unplug, to take this new update?  Based on above, doesn't sound promising for a fix, but we'll see.  Thanks!

It might be *slightly* more reliable now, but I am still experiencing the same call drops with the same numbers with which I previously had problems. The only qualitative difference is that, instead of hearing three beeps, it goes straight to the busy signal that previously followed the three beeps. So I guess, in that extremely limited sense, the problem has been fixed...

Is there any better, more direct way to get in touch with the engineering department than calling 611? I don't even have any new examples, since the problems are with exactly the same numbers as before, with the same symptoms aside from the missing beeps.

If the fix was to get rid of the 3 beeps, then yes, they've succeeded, but that doesn't resolve the main disconnect issue: OUTBOUND CALLS ARE STILL RANDOMLY DROPPED!!!!

Frankly how can  TMO engineering pretend they are fixing anything when they don't even take the time to talk and figure out what exactly is happending here ??? Two of us ( @9900dude​ ) have even offered to provide network traces to them!.....But nothing!

In the end you're suggesting to call tech care department, but those guys are powerless and totally unable to get engineering's attention. It's just a mailbox that goes nowhere.  So, no way I'm going to waste my time and their time. 

Userlevel 4

Hello All,

I wanted to post an update on this thread. Yesterday an update was rolled out (1.01.42) that should fix the three beeps drop call issue. I'm sorry it has taken this long to be resolved but this should do the trick. If for some reason you're still experiencing this, please call into our Tech Care department as our Engineers will need new examples of this happening.

Userlevel 1
Badge +2

Adding my comments to this thread, as well.  I had created another thread (2-8-18) because when I used the Support site search, I didn't find anything.  This newer Support site is awful compared to the prior one...kinda sounds like LineLink vs the old @Home service.  😊    Fix this TMO!!

I use LineLink as a second/office line and have run into two, what I consider, major issues:

1.  LineLink will not stay connected to certain conference call lines.  I use an 800 conference call line service for my job and I'm able to call into the line for calls, but after a certain period of time, the line beeps like 3 times or so and then drops the call.  I can re-dial back into the line, but it ultimately does the same thing.

2.  When leaving a voicemail for certain clients/prospects, the call will beep like mentioned above and then drop the call.  This just happened today when I called a prospect and was ready to leave them a VM.  The assistant transferred me to the person's VM and it started the VM message and within a couple seconds I got 3 or so beeps and then disconnected.

I've reset the device, the router, and re-started my computer, with no luck.  Any resolution or though to this as it's basically an unworkable solution for me as an office line and I'll probably have to port-out if this keeps happening.  I never had any of these issues with the old TMO@Home service and LL is supposed to be a "superior" service.  😠

It's kind of hard to see by my snapshot, but I did a Wireshark trace.  The ESP (encapsulated/encrypted) voice packets seem to go fine for a while, then the VPN tunnel is dropped.  The Line Link then starts up the negotiation with IPSEC and such to get this VPN tunnel back up and running again to T-Mobile.

I've given this Wireshark snapshot and trace to T-Force on Facebook.  I hope they can get it to the engineers.

That is an interesting question!  I have a new in the box @Home router as I posted.  I think I may call Support and inquire.  I'm not sure if I could use the same sim card.

Joe P

Has anyone tried to use the old @home router? Honestly I never had the issue until T-Mobile made me change devices.

Just fyi, not a good solution, but maybe a possible short term solution to be able to use your landline.  If you are on a TMobile ONE plan, you linelink number is also a DIGITs number.  If you have the DIGITS app (or a high end phone that supports it natively) you can answer and make calls with your landline number on your cell phone.  Of course, sometimes DIGITS has it's own issues (like how the DIGITS app on my Win 10 laptop didn't recognize the call I just got), but usally it works well.

Same issue here.

I also recently noticed this degradation of service and I've had to go through a complete reboot of the Linelink every day for the past week or so to clear this problem.

Unbelievable!

Hi all. I'm glad this thread is here. I started using LineLink in December (a little over a month ago). I have regularly observed this "three beeps and drop" problem as well. Tech Support was no help, but I was able to point them to this thread, so they could know it wasn't just me having this problem. This morning LineLink was stuck in a new fault state: any outgoing call would go through, but drop immediately (the receiving end would see the incoming call with Caller ID, then "call failed" after a second, before the call could be answered). Incoming calls would go directly to voicemail. Rebooting the LineLink seems to clear that condition. At this point, the service is not reliable enough, obviously. Looking for other solutions for VoIP.

Not for me. Supposedly I have an open ticket about this, but am just getting endless runaround about checking parameters of my network connection. If any T-Mobile engineer happens to read this message, the issue is almost perfectly reproducible by calling any line provided by UberConference (which lines work perfectly on any non-LineLink telephone service). I'm giving this one more week and then cancelling.

Is there any resolution to this?  My wife has been bugging me about dropped calls just like this.  As recent as today.  We’ve tried the Internet connection (both AT&T and Comcast), and even swapping out to a Google WiFi router.  It’s frankly really irritating, especially if you’re on hold for a while and your call drops.

Back in October, as you can read in the conversation with Amanda, I was contacted directly to figure this out directly with engineering. 

After few days of investigation engineering apparently checked into this issue and apparently found the reasons for the call drops. Though not sure it was the one we experienced they claimed to have a fix for this issue and would roll out a new firmware to our units during the November roll out.

Unfortunately two months have passed since then and like you guys, I am still experiencing the exact same issue you guys are.

I've ping'ed Amanda twice these past couple of weeks but she has gone completely MIA.

Conclusion; no still no fix.

I keep using this unit for incoming calls and/or toll-free calls which for some reasons, works flawlessly in this particular case.  I just can't have a reliable outbound call to anyone outside of TMO (which is 99.9% of my contacts). I use my cell phone for those calls.

Reply