APN info for Straight Talk via AT&T

[Selene ToyKeeper]

In Ubuntu Touch, I'm trying to use a SIM from Straight Talk, configured to use AT&T's network. The APN data isn't user-configurable yet, and the entries are missing or inaccurate in /system/etc/apns-conf.xml , as of Utopic image 166. This issue prevents me from testing several features for RTM.

The info provided by Straight Talk is:

APN Name: Straight Talk
APN: tfdata
Port: 80
MMSC: http://mms­tf.net
MMS Proxy: mms3.tracfone.com
MMS Port: 80

Under "Settings -> Cellular", the carrier is listed as "AT&T", so I'm not sure if this will be automatically distinguishable from other AT&T-based carriers.

On one device, I see these two potentially-matching entries in apns-conf.xml:

  <apn carrier="ATT"
      mcc="310"
      mnc="410"
      apn="wap.cingular"
      <email address hidden>"
      password="CINGULAR1"
      server="cingulargprs.com"
      mmsc="http://mmsc.cingular.com/"
      mmsproxy="wireless.cingular.com"
   mmsport="80"
      type="default,supl,mms"
  />

  <apn carrier="StraightTalk ATT"
      mcc="310"
      mnc="410"
      apn="att.mvno"
      mmsc="http://mmsc.cingular.com"
      mmsproxy="66.209.11.33"
      mmsport="80"
   type="default,supl,mms"
  />

On another device, I see no matching entries at all.

[Tony Espy (awe)]

@Selene

Have you tried the same SIM in an Android or iOS device? If so, was it automatically provisioned?

Unfortunately, handling of MVNOs is tricky business.

The apn database does have a way of handling MVNOs, but utilizing this support may require technical assistance from StraightTalk and/or the carriers that they have agreements with.

Here's a quick re-cap of how things works... When we initially provision for GPRS/MMS, we call a plugin with the following pieces of information:

- Mobile Country Code ( MCC )

- Mobile Network Code ( MNC )

- Service Provider Name ( SPN )

- Subscriber Identity ( IMSI )

- Group ID ( GID )

All of the above values are read from the SIM and passed into the provisioning plugin. The first two attributes ( MCC/MNC ) are used for normal matching. The latter three are matched against MVNO-specific attributes in the apns-conf.xml file. So if we could determine whether or not Straightalk programs their SIMs with a valid SPN or GID, then we could potentially create records for Straightalk.

That said... Straightalk's own documentation is pretty clear that a user needs to update their phones settings manually in order for GPRS to work. They also are pretty clear that MMS might now work even after doing so...

http://www.straighttalkbyop.com/program.php

[Tony Espy (awe)]

@Selene

If you need help configuring your device manually for testing, you can do the following:

As root, on the device:

# stop network-manager
# stop ofono
# cd /var/lib/ofono/<IMSI>

edit the file 'gprs' and remove all existing contexts, then add:

[context1]
Name=Straight Talk
AccessPointName=tfdata
Username=
Password=
Type=internet
Protocol=ip
MessageProxy=mms3.tracfone.com:80
MessageCenter=http://mms­tf.net

# start ofono
# start network-manager

Not sure the MMS settings are 100% correct, so you'll need to give that a check, but this should make GPRS ( ie. mobile data ) work.

[Selene ToyKeeper (toykeeper)]

Hi, sorry for the delay. I finally got a chance to test it with both AT&T and T-Mobile (both via Straight Talk), and found that the info here works:
https://wiki.ubuntu.com/QATeam/TouchTesting/Tips#Straight_Talk_Sim_.28Walmart.29

Coverage in this area isn't very good for T-Mobile, but it does at least work at 2G speeds.

I think the branch with manual config settings for this was supposed to land by now, but I don't see it yet. Hopefully soon.

[jrose (jroesler)]

Hey folks, I'm having some trouble with this as well, so I thought I'd contribute to the report.

I have mobile data working, but not MMS.

I'm on a google nexus 4 (mako), using the devel-proposed channel.

My carrier is Straight Talk (ATT), and these are the settings they give me on their site (https://www.straighttalk.com/wps/portal/home/support/apn/!ut/p/a1/fc7JDoIwFIXhN-q9zHWJSBkiorgAuzFAsBKGGiQ2vL2auDLRs_uTb3GAQwF8LB-tKOdWjmX_bm6fNxgnxsEN9UxnPkaM6ZhEGQYBQg78i4SOhdE-9I6Bs0PTc_6DlOkfgD_mIsTA22ogqh4IEkqRGpplUo2ibVoryNfA1ZIqX7zuntyxMqgAPjWXZmomcpX3GQqlFBFSir4htRzg1nUZXbbuEyVB6Q8!/dl5/d5/L2dBISEvZ0FBIS9nQSEh/pw/Z7_D0JM3QAH2R2FE0IFF20MIR0GM3/act/id=0/p=javax.portlet.action=submit_searchApn_action/295453462234/=/#Z7_D0JM3QAH2R2FE0IFF20MIR0GM3) (I'm not sure if that url is stable:

APN att.mvno
MMSC http://mmsc.cingular.com
MMS PROXY 66.209.11.33
MMS PORT 80
MMS_APN att.mvno

I've tried entering the information in the "custom internet/mms apn" dialogues. While this got mobile data working, every time I try to send a picture mms, it fails, and the mobile data connection also drops.

Then, I found this post and tried switching the fs to r/w mode and updating the ofono config file (linked above). Now, MMS still fails, but at least the mobile data stays connected.

One thing I noticed when I opened the config file was that the "custom" entries had written the proxy as "66.209.11.33:80:undefined". Not sure what that's about, but maybe it's related to why mobile data was crashing.

Any ideas about how I can debug further? Does ofono write log files somewhere? I tried reading the ofono docs, but I couldn't find any that gave me the info I needed.