| Message ID | e140e827103cd893938e0c113bc38b2c1f4f28b0.1739480113.git.gerickson@nuovations.com (mailing list archive) |
|---|---|
| State | Accepted, archived |
| Headers | show |
| Series | data: AT&T 'data device' public APN. | expand |
diff --git a/data/provision.json b/data/provision.json index 50319cf33a51..0cb6b8c3dffc 100644 --- a/data/provision.json +++ b/data/provision.json @@ -14183,6 +14183,15 @@ "mmsproxy": "proxy.mobile.att.net:80", "tags": "5g" }, + { + "name": "AT&T MVNO IoT/M2M (Public)", + "apn": "broadband", + "type": [ + "internet", + "ia" + ], + "tags": "kore-public" + }, { "name": "AT&T M2M", "apn": "m2m005246.attz",
Per AT&T documentation at <https://www.att.com/support/article/wireless/KM1062162/>, AT&T currently has three "public" APNs: 1. 'ENHANCEDPHONE' - For 5G smart phone devices. 2. 'NXTGENPHONE' - For 4G / LTE smart phone devices. 3. '[Bb]roadband' - For "data devices" such as Wi-Fi hotspots or IoT/M2M devices. The first two are already in the provisioning database; this adds the third under the tag `kore-public` since the AT&T mobile virtual network operator (MVNO) KORE Wireless recommends this AT&T public APN for users of its issued "AT&T Business" SIMs and since there is already a generic 'm2m'-tagged entry with the same types. --- data/provision.json | 9 +++++++++ 1 file changed, 9 insertions(+)