'port forced close' after failed ppp

[Colin Helliwell]

> On 07 March 2017 at 14:55 Aleksander Morgado <aleksander at aleksander.es> wrote:
> 
> On Tue, Mar 7, 2017 at 3:46 PM, Colin Helliwell
> 
> <colin.helliwell at ln-systems.com> wrote:
> 
> > Yes, I see what you mean. Now, [my] confusion is: the PDP is (I believe) being activated on ttyMux1 - the virtual port which is set as the PPP port. But the connectivity check is being done on ttyMux0 - the primary port.
> > So, is MM expecting to be able to check the connectivity of the PPP port via the primary? That would make sense, I guess - but I'm wondering (to myself) how the modem's multiplexer deals with this i.e. whether it sees a distinction between which port the AT+CGACT? is done on.
> 
> I see your concern; but if the modem is a single one and it just has
> multiple AT ports, I would assume that there isn't a list of PDP
> contexts per TTY, that wouldn't make much sense, would it?. Another
> thing would be able to activate different PDP contexts on different
> TTYs, but that is unrelated, the actual list and state of PDP contexts
> should be the same for all TTYs. At least that is what I would expect!
> 

Yep, I agree. I'll need to try to find out just how the Muxer works.

> ...
> > Surely ought to be possible - otherwise what's the point in having the query command if it won't fetch you the answer for the other port?! Might be something I need to dig into at the modem Mux's end of things. If I'm understanding things right, that is. e.g. Is there a difference between a 'PDP [#1] context activation' and the 'ATD*99***1##' ?
> 
> The 1 in ATD*99***1## refers to PDP context #1 (i.e. starts data
> connection in PDP context 1). Not sure if that's what you mean.
> 

Sort of. Just wanted to understand whether 'a data connection started in PDP context 1' (by the ATD) is the same as 'PDP context 1 being activated' (indicated by the AT+CGACT), or is one a subset/follow-on of the other.