# Tmobile Home Internet - getting voip.ms working **URL:** \ **Category:** Help & Support\ **Created:** [October 7, 2025, 3:16pm UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396 "2025-10-07T15:16:13Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![JMN10017](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JMN10017](https://community.voip.ms/u/JMN10017)\ **Post date:** [October 7, 2025, 3:16pm UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/1 "2025-10-07T15:16:13Z")
I am a new user configuring a Grandstream WP826 for an apartment in NYC (second home) where internet is via Tmobile Home Internet (TMHI). I have configured the phone and it works when connected via cell phone hotspot so I know the configuration is correct. It does not work via the TMHI router (4GAR). I have also attached to a second network (PC hotspot) that is tailscaled to my primary home and that hasn’t worked (yet). Does anyone have experience getting voip.ms line working through a TMHI 5G router? Any suggestions? ---
**Author:** ![jl66](https://avatars.discourse-cdn.com/v4/letter/j/ea5d25/32.png) [@jl66](https://community.voip.ms/u/jl66)\ **Post date:** [October 7, 2025, 9:24pm UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/2 "2025-10-07T21:24:58Z")
Have you tried setting the phone to the alternate port (5080)? T-Mobile may be blocking 5060. ---
**Author:** ![JMN10017](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JMN10017](https://community.voip.ms/u/JMN10017)\ **Post date:** [October 7, 2025, 11:20pm UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/3 "2025-10-07T23:20:52Z")
I’m away from that location for a couple of weeks. I did try 5080 and it didn’t work but I am going to try it again when I am back as I’m not sure I had everything set up correctly when I tried it. I’m back at my main home and everything works perfectly here. ---
**Author:** ![aleclerc](https://yyz2.discourse-cdn.com/flex012/user_avatar/community.voip.ms/aleclerc/32/65_2.png) [@aleclerc](https://community.voip.ms/u/aleclerc)\ **Post date:** [October 8, 2025, 12:55am UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/4 "2025-10-08T00:55:02Z")
Do you have a secure TLS connexion over TCP, or standard UPD connexion? Go TLS for your tests just to see. ---
**Author:** ![MurrayB](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@MurrayB](https://community.voip.ms/u/MurrayB)\ **Post date:** [October 8, 2025, 11:59am UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/5 "2025-10-08T11:59:11Z")
I experienced the same thing with T-Mobile Home internet. The connection will not work via T-Mobile Home Internet if set up as UDP. You have to reconfigure as an encrypted TLS connection. Good Luck! ---
**Author:** ![JMN10017](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JMN10017](https://community.voip.ms/u/JMN10017)\ **Post date:** [October 8, 2025, 12:36pm UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/6 "2025-10-08T12:36:51Z")
Thanks - I will try it when I am there next. Quick question - did you need to change any ports and/or reach out to TMHI to change/do anything? Or was it simply changing to encryption on the account (or subaccount) and then changing the client to use TLS and encryption/SRTP? ---
**Author:** ![aleclerc](https://yyz2.discourse-cdn.com/flex012/user_avatar/community.voip.ms/aleclerc/32/65_2.png) [@aleclerc](https://community.voip.ms/u/aleclerc)\ **Post date:** [October 8, 2025, 2:15pm UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/7 "2025-10-08T14:15:43Z")
Hello @JMN10017, What @MurrayB said just confirms my supposition. Properly setting up the TLS connection should make it work without any other changes. You will see that the TLS port is not the same anyway (5061). Check the wiki to be sure all the details are set (and check for your device if it is there). [https://wiki.voip.ms/article/Call\_Encryption\_-\_TLS/SRTP](https://wiki.voip.ms/article/Call_Encryption_-_TLS/SRTP) Kind regards. ---
**Author:** ![MurrayB](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@MurrayB](https://community.voip.ms/u/MurrayB)\ **Post date:** [October 8, 2025, 2:30pm UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/8 "2025-10-08T14:30:02Z")
Here is the way an Obi is set up. This was developed by Ozark Edge. Just adapt it to your ATA. I don’t see how to attach a file. Good Luck! **VoIP.ms POP server specification:** • Server _city#_.voip.ms • Port 5060, 5080, or 42872 for UDP or TCP transport • Port 5061, 5081, or 42873 for TCP transport with TLS/SRTP call encryption To use TLS, configure the VoIP.ms SIP account to encrypt SIP traffic. How TLS/SRTP call encryption looks for an OBi202: **Service Providers – ITSP Profile A – General** General::Name VoIP.ms POP1 General::DigitMap (Msp1) = ? ;VoIP.ms dialing. General::X\_SymmetricRTPEnable Checked ;for TLS/SRTP call encryption. **Service Providers – ITSP Profile A – SIP** SIP::ProxyServer washington1.voip.ms SIP::ProxyServerPort 5061 ;for TLS/SRTP call encryption. SIP::ProxyServerTransport TLS ;for TLS/SRTP call encryption. SIP::RegistrarServer ;leave blank to use SIP::ProxyServer. SIP::RegistrarServerPort 5061 ;same as SIP::ProxyServerPort. SIP::OutboundProxy ;leave blank to use SIP::ProxyServer. SIP::OutboundProxyPort 5061 ;same as SIP::ProxyServerPort. SIP::X\_OutboundProxyTransport Follow ProxyServerTransport ;same as SIP::ProxyServerTransport SIP::RegistrationPeriod 60 ;seconds registration period. SIP::RegisterExpires 3600 ;seconds registration expires advice to ITSP. A longer registration period has less network overhead and is tolerated if i) the User Agent WAN/ISP IP address is not changing frequently; and ii) using UDP transport with a keep-alive mechanism to keep-alive the router NAT session, or using TCP transport which keeps a TCP session open. **Voice Services – SP1 Service** SP1 Service::Enable Checked SP1 Service::X\_ServProvProfile A ;VoIP.ms POP1 server. SP1 Service::X\_InboundCallRoute ph1 ;PH1 PHONE1 Port L1. SP1 Service::X\_AcceptSipFromRegistrarOnly Checked ;prohibit anonymous SIP. SP1 Service::X\_NoRegNoCall Checked ;speed up trunk group failover. SP1 Service::X\_KeepAliveEnable Checked ;keep-alive router NAT session. SP1 Service::X\_KeepAliveExpires 30 ;seconds keep-alive period. SP1 Service::X\_KeepAliveServer ;leave blank to use SIP::ProxyServer. SP1 Service::X\_KeepAliveServerPort 5061 ;same as SIP::ProxyServerPort. SP1 Service::X\_UserAgentPort 6xx61 ;obscure, unassigned local network port. Use a non-standard User Agent port (not 5060; ports 49152 to 65535 are available) to avoid SIP ALG (Application-Level Gateway) interference with UDP transport and to hide from SIP scanners. The User Agent port is not used with TCP/TLS transport. Disable any router SIP ALG/SIP Passthrough. SIP Credentials::AuthUserName sip username ;VoIP.ms SIP account accountid. SIP Credentials::AuthPassword sip password ;12-characters minimum. SIP Credentials::X\_EnforceRequestUserID Checked ;prohibit anonymous SIP (supported by VoIP.ms). Calling Features::CallerIDName userid ;CallerID name. Calling Features::MWIEnable Enabled ;PH1 stutter tone message waiting indication. Calling Features::X\_VMWIEnable Enabled ;PH1 visual message waiting indication (LED flashes). Calling Features::X\_SRTP SRTP Only ;for TLS/SRTP call encryption. Calling Features::X\_SRTPCryptos AES\_CM\_128\_HMAC\_SHA1\_80 ;for TLS/SRTP call encryption (Poly fw only). **WARNING:** Configure the VoIP.ms SIP account CallerID number (or the VoIP.ms account global e911 Default CallerID number) to be the e911-enabled DID for the dialing location. Dial 555-555-0911 to confirm the VoIP.ms CallerID number and e911 configuration for trunk sp1. ---
**Author:** ![JMN10017](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JMN10017](https://community.voip.ms/u/JMN10017)\ **Post date:** [October 8, 2025, 2:58pm UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/9 "2025-10-08T14:58:36Z")
Thanks all. Not back there until week after next but will try it when I am back. ---
**Author:** ![urbnsr](https://avatars.discourse-cdn.com/v4/letter/u/df788c/32.png) [@urbnsr](https://community.voip.ms/u/urbnsr)\ **Post date:** [October 8, 2025, 9:20pm UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/10 "2025-10-08T21:20:13Z")
I wonder if your Tmobile Internet is using CGNAT for the data side of the connection. They used CGNAT here, but I didn’t have them for cell phone service so I couldn’t even try hot-spotting a connection. If that is being used, I would assume outgoing calls should be (more) successful, but incoming calls may have a hard time find the ATA. If this is the problem, I would look into getting a static IP address. If not - They wouldn’t even offer it to me when I asked, - I would look into possible working with IPv6. I don’t know if that is even an option. ---
**Author:** ![JMN10017](https://avatars.discourse-cdn.com/v4/letter/j/f4b2a3/32.png) [@JMN10017](https://community.voip.ms/u/JMN10017)\ **Post date:** [October 21, 2025, 11:15am UTC](https://community.voip.ms/t/tmobile-home-internet-getting-voip-ms-working/3396/11 "2025-10-21T11:15:53Z")
To close the loop. Got TLS working before I went back to the home with TMHI. Just got back yesterday, connected to my router and everything worked like a charm. Thanks all for the help.