All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Re-activating a context.
Date: Wed, 29 Aug 2012 18:56:50 -0500	[thread overview]
Message-ID: <503EAC42.3070104@gmail.com> (raw)
In-Reply-To: <1646126421.203726.1346265651893.JavaMail.root@mail.hale>

[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]

Hi Christopher,

<snip>

> I now know why I receive '+CGEV: ME DEACT IP, , 1\r\n'.
> According to Telit support this happens because the context does not get deactivated
> and ofono is trying to request a new IP address although the previous one is still valid.
>
> After the antenna gets disconnected, the modem sends '+CREG: 2' and '+CGREG: 2'.
> In consequence drivers/atmodem/gprs-context.c:telit_gprs_detach_shutdown() is called to end ppp connection and
> 'AT+CGATT=0' is sent.
> 'AT+CGATT=0' should normally deactivate all active contexts, but it returns '+CME ERROR: 30'.

That sounds like a firmware bug, we should be able to tell the modem to 
abort the attach procedure or detach at any time.

> When I try to deactivate the context with +CGACT like ifx does in
> drivers/ifxmodem/gprs-context.c:ifx_gprs_deactivate_primary(), then I get '+CME ERROR: 0' (phone failure).
>

Does sending 'AT+CGACT=0' per 3GPP 27.007 10.1.10 work?

> Furthermore I thought that when I receive 'NO CARRIER' at least then all context should be deactivated.
>  From a Cinterion manual (as the Telit manual is very poor):
> "If the TE wants to close the LCP link the MT may perform an LCP termination request procedure on PPP level.
> After this LCP termination procedure the MT deactivates the PDP context automatically and the MT returns to
> V.250 command mode and issues the final result code NO CARRIER."

Yes, that is the expected behavior, NO CARRIER means context is 
deactivated.  We've had problems with Huawei modems that try to keep the 
PPP link alive when network registration is lost.  We then had to 
force-deactivate them by sending the relevant LCP close procedure.  But 
that doesn't seem to be the issue here...

>
> I don't know if this is a firmware or ofono issue as I don't know how this should be handled correctly.
>

Sounds like firmware is at fault, or maybe the Telit modem has to be 
driven 'differently', but I do not see how.

Regards,
-Denis

      reply	other threads:[~2012-08-29 23:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 14:50 Re-activating a context Christopher Vogl
2012-07-12 20:49 ` Denis Kenzior
2012-07-13 10:12   ` Christopher Vogl
2012-07-13 13:39     ` Guillaume Zajac
2012-07-16 12:31       ` Christopher Vogl
2012-08-29 18:40       ` Chrisopher Vogl
2012-08-29 23:56         ` Denis Kenzior [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=503EAC42.3070104@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.