Tag: How-To Fix

Fix for T-Mobile MMS not working with Wifi [Calling] connected. (Group and Picture texts)

I like to buy my own phones and bring them to my plan. Sometimes this results in not having the full config to make the phone work 100% on a carrier. I recently fixed issues where I could not receive MMS messages if I had an active wifi connection. When my phone is on wifi, it chooses to send and receive messages and calls over wifi instead of the cellular service. Unfortunately, I was missing this in my APN config!

APN settings: (Changes I made to my settings in brackets. Full quote is from source)
Name: T-Mobile US LTE
APN: fast.t-mobile.com
Proxy: Not set
Port: Not set
Username: Not set
Password: Not set
Server: Not set
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc [ADDED THIS]
Multimedia message proxy: Not set
Multimedia message port: 80 [ADDED THIS]
MCC: 310
MNC: 260
Authentication type: None
APN type: default,mms,supl [ADDED mms to my existing list]
APN protocol: IPv6
APN roaming protocol: IPv4
Enable/disable APN: APN enabled
Bearer: Unspecified
Mobile virtual network operator type: None
Mobile virtual network operator value: Not set

Source: https://support.t-mobile.com/message/626402#626402

T-Mobile Wifi Calling – ER081 Firewall Port Summary

Open the following ports on your firewall:

  • TCP 5060-5061
  • UDP 4500 (aka IKE Traversal)  –  Note: This is the port the call data goes through

Additionally, you may need to let IKE Key Exchange traffic through.

  • UDP 500

Other errors:

REG99 – Go to my.t-mobile.com and update your E911 address (even if you previously have)

Fixing Cisco Wireless Client Association Failure ReasonCode: 102

Have you seen this error in your Cisco WLC logs?

Client Association Failure: MACAddress:xx:xx:xx:xx:xx:xx Base Radio MAC:xx:xx:xx:xx:xx:xx Slot: 0 User Name:UNKNOWN IP Addr: unknown Reason:Unknown ReasonCode: 102

There is one link on the internet mentioning this error on the Cisco Support Forums, but I found it might have an alternative solution.

Reboot the AP with the Base Radio MAC that is triggering this error.

I highly doubt this is a silver bullet for this error, but when there’s little other documentation on this error online, I figure I’d share what my fix was.