<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">I agree with Matthew. Both, the simple and non-simple interface should allow to explicitly set the CID. Having this implemented, all these odd configurations
can be handled.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Von:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> matthew stanger [mailto:stangerm2@gmail.com]
<br>
<b>Gesendet:</b> Dienstag, 27. November 2018 19:29<br>
<b>An:</b> Aleksander Morgado<br>
<b>Cc:</b> Stelling2 Carsten; ModemManager (development)<br>
<b>Betreff:</b> Re: [review] LTE attach config and status<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal"> I don't think that CID=1 is always the one that the<br>
module expects to use as initial EPS bearer <o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal">I'd agree, but so far the small set of carriers we've seen requiring specific PDP's have all been #1. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Didn't Verizon require to use CID=4 for the same purpose in their<br>
modems? <o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal">Vzw is a little odd, they require their default APN in context #3, but apparently, and we've yet to make this work,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">they(Vzw) say that if you use context #1, which auto populates with 'vzwadmin' will, after the first attach the carrier,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> self provision the rest of the context's.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Docomo in Japan wouldn't do 4G without use of context #1 populated.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">SK Telecom in S. Korea wouldn't connect without using context #1, using blank context #1 populated other context's<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">I recall a patch were we allowed specifying the CID to use explicitly<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal">yes, and the non-simple interface. We still use it, and without it those cases above would not work. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">On Tue, Nov 27, 2018 at 9:37 AM Aleksander Morgado <<a href="mailto:aleksander@aleksander.es" target="_blank">aleksander@aleksander.es</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">> 4 In 4G the 1 context (where default EPS bearer is created) generally does not require an APN, APN is required on other context to set up data sessions instead . In any case the rules are made by network operator<br>
><br>
<br>
Unfortunately, I don't think that CID=1 is always the one that the<br>
module expects to use as initial EPS bearer, that may depend on the<br>
modem. So, if we were to add a logic that assumes "initial LTE bearer<br>
settings are those in CID=1" then that would need to be tied to a<br>
specific device.<br>
<br>
Didn't Verizon require to use CID=4 for the same purpose in their<br>
modems? (or something like that) @matthew stanger what was that about?<br>
I recall a patch were we allowed specifying the CID to use explicitly<br>
via Simple.Connect() for this very same purpose.<br>
<br>
-- <br>
Aleksander<br>
<a href="https://aleksander.es" target="_blank">https://aleksander.es</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>