sms segment fault with 160 char

sms segment fault with 160 char

[Li, Zhigang]

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

Hi,
There was segment fault during send 160 char sms.
The content is 160 char like: abcdefghijklmnopqrstuvwxyz0123456789][=+..........

ofonod[12988]: Response line: +CSCA: "+8613800210500",145
ofonod[12988]: csca_query_cb: 8613800210500, 145
ofonod[12988]: Got 1 recipients
ofonod[12988]: ref: 1, offset: 3
ofonod[12988]: pdu_len: 155, tpdu_len: 154
ofonod[12988]: pdu_len: 36, tpdu_len: 35
ofonod[12988]: tx_next: 0x82660f0
ofonod[12988]: at_cmgs_cb got result: 1
ofonod[12988]: Final response: OK
ofonod[12988]: Response line: +CMGS: 31
ofonod[12988]: Got MR: 31
ofonod[12988]: tx_finished
ofonod[12988]: Peeking in the queue
ofonod[12988]: Scheduling next
Segmentation fault

Basically the "[ ]' will be encoded as UCS2, but it is 7bit according message head in fact.
So there were two problem:
1, tpdu_len was wrong: the problem was in sms encode
2, send more segment had issue.
 
Thanks
Zhigang

Re: sms segment fault with 160 char

[Denis Kenzior]

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

Hi,

> Basically the "[ ]' will be encoded as UCS2, but it is 7bit according
> message head in fact. So there were two problem:
> 1, tpdu_len was wrong: the problem was in sms encode

You're wrong.  '[' and ']' are defined in GSM extension table.  And can thus 
still be encoded in GSM 7bit alphabet.

> 2, send more segment had issue.

Please fetch the latest version, this was fixed earlier today.

Regards,
-Denis

RE: sms segment fault with 160 char

[Li, Zhigang]

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

Hi Denis,
Great, the segment fault was solved in latest version.
But there was problem for more recipients
Please see the log of phonesim:
 AT+CMGS=18 : 
> 
0011000B815128010272F40000A70461F1980C : 
+CMGS: 0
OK
AT+CMGS=18 : 
> 
0011000B813118567873F20000A704B2D88C06 : 
+CMGS: 0
OK
The content is different, and it should be abcd

In real network:
Because I use phone as modem so maybe something wrong in at response.
Whatever it was wrong behavior:
The number1 target device received two message:
 1, content: abcd
 2, content: number1

ofonod[21782]: csca_query_cb: 8613800210500, 145
ofonod[21782]: Got 2 recipients
ofonod[21782]: ref: 1, offset: 0
ofonod[21782]: pdu_len: 20, tpdu_len: 19
ofonod[21782]: ref: 2, offset: 0
ofonod[21782]: pdu_len: 20, tpdu_len: 19
ofonod[21782]: tx_next: 0x8c1eac0
ofonod[21782]: Got 1 recipients
ofonod[21782]: ref: 3, offset: 0
ofonod[21782]: pdu_len: 25, tpdu_len: 24
ofonod[21782]: at_cmgs_cb got result: 1
ofonod[21782]: Final response: OK
ofonod[21782]: Response line: +CMGS: 81
ofonod[21782]: Got MR: 81
ofonod[21782]: tx_finished
ofonod[21782]: Peeking in the queue
ofonod[21782]: Scheduling next
ofonod[21782]: tx_next: 0x8c1ebf8
ofonod[21782]: at_cmgs_cb got result: 0
ofonod[21782]: Final response: +CMS ERROR: 500
ofonod[21782]: tx_finished
ofonod[21782]: Sending failed, retrying in 5 seconds...
ofonod[21782]: tx_next: 0x8c1ebf8
ofonod[21782]: at_cmgs_cb got result: 1
ofonod[21782]: Final response: OK
ofonod[21782]: Response line: +CMGS: 83
ofonod[21782]: Got MR: 83
ofonod[21782]: tx_finished
ofonod[21782]: Peeking in the queue
ofonod[21782]: Scheduling next
ofonod[21782]: tx_next: 0x8c1ecb8
ofonod[21782]: at_cmgs_cb got result: 1
ofonod[21782]: Final response: OK
ofonod[21782]: Response line: +CMGS: 84
ofonod[21782]: Got MR: 84
ofonod[21782]: tx_finished
ofonod[21782]: Peeking in the queue

Thanks
Zhigang
>-----Original Message-----
>From: ofono-bounces(a)ofono.org [mailto:ofono-bounces(a)ofono.org] On Behalf Of
>Denis Kenzior
>Sent: 2009年7月30日 12:06
>To: ofono(a)ofono.org
>Subject: Re: sms segment fault with 160 char
>
>Hi,
>
>> Basically the "[ ]' will be encoded as UCS2, but it is 7bit according
>> message head in fact. So there were two problem:
>> 1, tpdu_len was wrong: the problem was in sms encode
>
>You're wrong.  '[' and ']' are defined in GSM extension table.  And can thus
>still be encoded in GSM 7bit alphabet.
>
>> 2, send more segment had issue.
>
>Please fetch the latest version, this was fixed earlier today.
>
>Regards,
>-Denis
>_______________________________________________
>ofono mailing list
>ofono(a)ofono.org
>http://lists.ofono.org/listinfo/ofono

Re: sms segment fault with 160 char

[Denis Kenzior]

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

Hi,

> Please see the log of phonesim:
>  AT+CMGS=18 :
>
> 0011000B815128010272F40000A70461F1980C :
> +CMGS: 0
> OK

Destination: 158210202..
Content: abcd

> AT+CMGS=18 :
>
> 0011000B813118567873F20000A704B2D88C06 :
> +CMGS: 0
> OK
> The content is different, and it should be abcd

Destination: 138165873..
Content: 2134

So I don't understand, you're physically sending two different SMSs here.

>
> In real network:
> Because I use phone as modem so maybe something wrong in at response.
> Whatever it was wrong behavior:
> The number1 target device received two message:
>  1, content: abcd
>  2, content: number1

Again, you're sending two SMSes according to the log.  First with 2 
recipients, and second with a single one.  This means three SMSes are sent, 
and presumably one of the recipients will get 2 of them.  All three get sent 
eventually.  What is the problem?

Regards,
-Denis

RE: sms segment fault with 160 char

[Li, Zhigang]

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

Hi,
Great! More than one recipients and more segment work fine after I reinstall the python package 
Thanks

>-----Original Message-----
>From: ofono-bounces(a)ofono.org [mailto:ofono-bounces(a)ofono.org] On Behalf Of
>Denis Kenzior
>Sent: 2009年7月30日 23:28
>To: ofono(a)ofono.org
>Subject: Re: sms segment fault with 160 char
>
>Hi,
>
>> Please see the log of phonesim:
>>  AT+CMGS=18 :
>>
>> 0011000B815128010272F40000A70461F1980C :
>> +CMGS: 0
>> OK
>
>Destination: 158210202..
>Content: abcd
>
>> AT+CMGS=18 :
>>
>> 0011000B813118567873F20000A704B2D88C06 :
>> +CMGS: 0
>> OK
>> The content is different, and it should be abcd
>
>Destination: 138165873..
>Content: 2134
>
>So I don't understand, you're physically sending two different SMSs here.
>
>>
>> In real network:
>> Because I use phone as modem so maybe something wrong in at response.
>> Whatever it was wrong behavior:
>> The number1 target device received two message:
>>  1, content: abcd
>>  2, content: number1
>
>Again, you're sending two SMSes according to the log.  First with 2
>recipients, and second with a single one.  This means three SMSes are sent,
>and presumably one of the recipients will get 2 of them.  All three get sent
>eventually.  What is the problem?
>
>Regards,
>-Denis
>_______________________________________________
>ofono mailing list
>ofono(a)ofono.org
>http://lists.ofono.org/listinfo/ofono