Open Source Telephony
 help / color / mirror / Atom feed
From: Viallard Anthony <viallard@syscom-instruments.com>
To: ofono@ofono.org
Subject: Re: Randomly SMS sent passes or fails
Date: Thu, 28 Mar 2013 15:29:38 +0100	[thread overview]
Message-ID: <515453D2.9040404@syscom-instruments.com> (raw)
In-Reply-To: <5154070A.9040108@syscom-instruments.com>

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

On 28. 03. 13 10:02, Viallard Anthony wrote:
> On 05. 03. 13 21:43, Denis Kenzior wrote:
>>>
>>> [...]
>>>
>>> Provisioning failed
>>> -------------------------------
>>
>> This should not affect anything, unless your operator requires SMS to be
>> sent over GPRS.
>>
>
> Hi,
>
> I try to find how i can fix the "provisioning failed" message.
>
> Actually, I have always troubles with T-Mobile. I think I need to fix
> this provisioning issue. How can I do this ? I tried to see where this
> provisioning in the source code but I was quickly lost.
>

I think I've found where the issue is. The MCC and MNC can't be 
retrieve. And the cause is the mnc length can't be retrieve in this 
callback:

static void sim_ad_read_cb(int ok, int length, int record,
				const unsigned char *data,
				int record_length, void *userdata)

The call returns at the test "if (!ok)". So, mnt_length stay at 0 and 
next, on IMSI callback, as it doesn't know mnc_length, it doesn't 
extract MCC and MNC.

I don't know why ofono call the callback with ok=0. In the log, I see 
the command was successful:

---------------
Mar 28 13:50:05 mr3000 ofonod[6859]: Data: > AT+CRSM=192,28589\r
Mar 28 13:50:05 mr3000 ofonod[6859]: Data: < \r\n+CRSM: 
144,0,""\r\n\r\nOK\r\n
---------------

Maybe a clue on my problem... Why ofono says the command failed ?

Regards,
Anthony.

  parent reply	other threads:[~2013-03-28 14:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 15:27 Randomly SMS sent passes or fails Viallard Anthony
2013-03-05 20:43 ` Denis Kenzior
2013-03-06  9:23   ` Viallard Anthony
2013-03-11 14:53     ` Viallard Anthony
2013-03-12 18:13       ` Denis Kenzior
2013-03-13 16:11         ` Viallard Anthony
2013-03-28  9:02   ` Viallard Anthony
2013-03-28 14:24     ` Denis Kenzior
2013-04-12 13:08       ` Viallard Anthony
2013-05-02 16:40         ` Viallard Anthony
2013-05-02 18:36           ` Denis Kenzior
2013-05-21 14:20             ` Viallard Anthony
2013-03-28 14:29     ` Viallard Anthony [this message]
2013-03-28 14:42       ` Denis Kenzior
2013-03-28 16:29         ` Viallard Anthony
2013-03-28 18:05           ` Denis Kenzior
2013-04-02 13:49             ` Viallard Anthony
2013-04-02 15:08               ` Denis Kenzior
2013-04-02 15:25                 ` Viallard Anthony

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=515453D2.9040404@syscom-instruments.com \
    --to=viallard@syscom-instruments.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox