<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nRF9160 AT&amp;amp;T Test SIMs</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46280/nrf9160-at-t-test-sims</link><description>Hey, 
 
 So I recently got some test SIMs from AT&amp;amp;T to use for our development. I&amp;#39;m trying to get them working with my nRF9160 dev kit but can&amp;#39;t seem to get a connection to LTE. 
 AT&amp;amp;T requires me to configure my APN to &amp;quot;m2m.com.attz&amp;quot;. So I&amp;#39;m running</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Apr 2019 13:04:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46280/nrf9160-at-t-test-sims" /><item><title>RE: nRF9160 AT&amp;T Test SIMs</title><link>https://devzone.nordicsemi.com/thread/183488?ContentTypeID=1</link><pubDate>Wed, 24 Apr 2019 13:04:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b68f347-aed8-48e5-a22d-61b9dc685a02</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Jack,&lt;/p&gt;
&lt;p&gt;&lt;em&gt;There is also something that you should be aware of.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;If you are trying to configure the&amp;nbsp;&lt;em&gt;default PDN connection&lt;/em&gt; then you should set the &lt;strong&gt;CID 0&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Because you have configured the context #1 (CID1), but I think you should rather configure the CID 0.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;Instead of:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;AT+CGDCONT=1,&amp;quot;IPV4V6&amp;quot;,&amp;quot;m2m.com.attz&amp;quot; &lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fref_at_commands%2FREF%2Fat_commands%2Fpacket_domain%2Fcgdcont_set.html&amp;amp;resultof=%22cgdcont%22%20" rel="noopener noreferrer" target="_blank"&gt;use the following:&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;&lt;pre class="ui-code" data-mode="text"&gt;AT+CGDCONT=0,&amp;quot;IPV4V6&amp;quot;,&amp;quot;m2m.com.attz&amp;quot; &lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 AT&amp;T Test SIMs</title><link>https://devzone.nordicsemi.com/thread/183487?ContentTypeID=1</link><pubDate>Wed, 24 Apr 2019 13:04:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77487518-ce76-4f32-abc2-e59595970b9f</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Jack,&lt;/p&gt;
&lt;p&gt;&lt;em&gt;There is also something that you should be aware of.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;If you are trying to configure the&amp;nbsp;&lt;em&gt;default PDN connection&lt;/em&gt; then you should set the &lt;strong&gt;CID 0&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Because you have configured the context #1 (CID1), but I think you should rather configure the CID 0.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;Instead of:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;AT+CGDCONT=1,&amp;quot;IPV4V6&amp;quot;,&amp;quot;m2m.com.attz&amp;quot; &lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fref_at_commands%2FREF%2Fat_commands%2Fpacket_domain%2Fcgdcont_set.html&amp;amp;resultof=%22cgdcont%22%20" rel="noopener noreferrer" target="_blank"&gt;use the following:&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;&lt;pre class="ui-code" data-mode="text"&gt;AT+CGDCONT=0,&amp;quot;IPV4V6&amp;quot;,&amp;quot;m2m.com.attz&amp;quot; &lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 AT&amp;T Test SIMs</title><link>https://devzone.nordicsemi.com/thread/183444?ContentTypeID=1</link><pubDate>Wed, 24 Apr 2019 12:22:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de6ce87e-c016-4af0-8f0d-4f1a958e36a2</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Which modem firmware are you running?&lt;br /&gt;Could you try to update to t&lt;a href="https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs" rel="noopener noreferrer" target="_blank"&gt;he 0.6.8-131&amp;nbsp;&lt;/a&gt;version to see if there are any improvements?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 AT&amp;T Test SIMs</title><link>https://devzone.nordicsemi.com/thread/182691?ContentTypeID=1</link><pubDate>Thu, 18 Apr 2019 00:43:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de4a2f9b-5a0c-4428-9d05-a2b1dd4e3f20</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;AT&amp;amp;T uses bands 4 and 12 in the USA and Canada; band 12 is not (yet) approved or available for the nRF9160, which means you must use band 4. You can lock to band 4 with the following steps to avoid locking to Verizon&amp;#39;s band 13:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;The AT host sample started
AT+CGDCONT=1,&amp;quot;IPV6&amp;quot;,&amp;quot;m2m.com.attz&amp;quot;
OK
AT+CGDCONT?
+CGDCONT: 1,&amp;quot;IPV6&amp;quot;,&amp;quot;m2m.com.attz&amp;quot;,&amp;quot;&amp;quot;,0,0
OK
AT%XBANDLOCK=1,&amp;quot;1000&amp;quot;
OK
AT%XCBAND=?
%XCBAND: (4)
OK
AT+CFUN?
+CFUN: 4
OK
AT+CFUN=1
OK&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;However .. we have not (so far) been able to connect to the AT&amp;amp;T network on band 4 even though some smartphones can connect to AT&amp;amp;T on band 4.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>