Forum Discussion

spacemanjosh's avatar
spacemanjosh
Newbie Caller
Hace 4 años

LineLink doesn't work with T-Mobile 5G home internet router

I was going to post my comment here:

https://community.t-mobile.com/tv-home-internet-7/linelink-not-working-with-nokia-router-34401

 

But comments are closed on that one, so I'm starting a new thread.  I'm having exactly the same issue described in the link above.  In short, after weeks of calling, each time promised a call back from an expert that never came (waiting on one right now), my LineLink home phone line will not connect.  I was told the same thing mentioned in the link above, that the 5G nokia router is not compatible with the LineLink device.  However, I've also been told several other things from different T-Mobile reps:

  1. Billing department says it should work fine… they forward me to tech support.
  2. LineLink tech support checked my sim card, device status lights, and said it should be working fine… forwarded me to the home internet tech support.
  3. Home internet tech support first didn't understand the problem.  They first said there was a tower upgrade in the area causing problems, which doesn't make sense because I'm getting internet just fine, only LineLink doesn't work.  They then put me on hold and said that there is an existing ticket in their system suggesting that the LineLink device is not compatible with their 5G internet router… said they'd call back in 3 business days to let me know the status (that was 9 days ago).
  4. Now I’ve been told that my sim card needs to be replaced… So now I need to wait for that.

All in all, I've been calling for over a month.  Honestly it feels like they are just throwing things around to see what sticks.  I have some ideas of my own in case someone from T-mobile actually reads these things.

Hypothesis #1: When I switched from comcast to T-mobile for my ISP, the device is now seen by T-Mobile as coming from a different IP address, which will make it appear that I have moved it to a new location.  I suspect that all that needs to happen is that they need to reset it on their end so that it's registered to the new IP.

Hypothesis #2: The T-mobile router is blocking some port that the LineLink needs to operate.

Hypothesis #3: Since according to their own page (https://www.t-mobile.com/support/coverage/t-mobile-linelink) LineLink is no longer sold by T-mobile, they have simply stopped caring about supporting it.

Could be any combination of those.

  • We are experiencing something similar with dialpad.com.  I'm wondering if T-Mobile is blocking ports intentionally so that one can't use another phone company.  Sounds fishy….  These are the ports we need to have open.

    Port and protocols used by Dialpad phones and applications residing in a private network are listed below. Outbound port configurations are needed on the firewall to allow traffic to the destination ports listed in the right-hand side column of the tables. Stateful firewalls are recommended for Dialpad deployments. For a stateful firewall, inbound port configurations are not needed as they are automatically opened as a reply to the outbound traffic.
     

    Desktop Native, Mobile, & Browser Applications

    Traffic Type Protocol (Protocolo) Domain (Dominio) Puerto
    Product features (images, social profiles etc) HTTPS (TCP)

    *.dialpad.com

    *.dialpadcdn.com

    443
    Mensajería HTTPS (TCP)
    WSS (TCP)
    *.dialpad.com
    *.ubervoip.net
    *.pusher.com
    443
    Call Signaling WSS (TCP)
    SIP/TLS (TCP)
    *.dialpad.com
    *.ubervoip.net
    443, 5061
    Call Media SRTP (UDP)   16384 a 32768
    STUN UDP stun.l.google.com 19301 a 19302
    TURN UDP and TCP turn.ubervoip.net 443
    Server Discovery DNS (SRV records)

    google-public-dns-a.google.com

    google-public-dns-b.google.com

    53

    For more details about Dialpad's Network set up recommendations, please visit our help center: https://help.dialpad.com/hc/en-us/articles/209954306-Network-Setup-Recommendations