Longer BEARER_CONNECTION_MONITOR_TIMEOUT?

[Colin Helliwell]

> On 14 May 2017 at 18:32 Aleksander Morgado <aleksander at aleksander.es> wrote:
> 
> On Fri, May 12, 2017 at 3:40 PM, <colin.helliwell at ln-systems.com> wrote:
> 
> > I've been finding today that I'm getting failed connection attempts - it
> > looks like MM is checking the PDP ("+CGDACT?") whilst ppp/modem are still in
> > the process of getting themselves together. So MM is getting back an
> > 'inactive' response and, I think ditching the attempt.
> > I've increased BEARER_CONNECTION_MONITOR_TIMEOUT and that seems to address
> > it.
> > Not sure if the time taken is down to the Operator or to signal quality
> > (which isn't great here), but wondered if it was a situation other people
> > encounter?
> 
> So, even if the ATD call succeeded, the PDP context status reported
> via AT+CGACT? still said disconnected, and we abort the connection
> attempt? 

Yes, 'CONNECT' comes back for the ATD, and pppd gets beyond at least the LCP netogiation.
 

> We should definitely increase that timeout, at least for the
> first time it is checked (e.g. 30s before the first check, then a
> check every 5s). What do you think?
> 

Sounds good to me