gnokii - Bugs: bug #33007, Concatenated messages - Reference...
You are not allowed to post comments on this tracker with your current authentication level.
bug #33007: Concatenated messages - Reference numbers
Submitter: | Sebastijan V <sv7874> | ||
Submitted: | Wed 06 Apr 2011 01:16:51 PM UTC | ||
Category: | gnokii | Severity: | 3 - Normal |
Item Group: | minor malfunction | Status: | Need Info |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open |
Thu 07 Apr 2011 11:45:20 AM UTC, comment #3: |
Pawel Kot <pkot>![]() |
Thu 07 Apr 2011 07:35:43 AM UTC, comment #2: When SMS is longer than 160 characters, it is send in multiple parts.
|
Sebastijan V <sv7874> |
Wed 06 Apr 2011 02:13:28 PM UTC, comment #1: We are not able to help you unless you provide some basic information described in http://git.savannah.gnu.org/cgit/gnokii.git/plain/Docs/Bugs |
Pawel Kot <pkot>![]() |
Wed 06 Apr 2011 01:16:51 PM UTC, original submission:
Hi
|
Sebastijan V <sv7874> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
The -1 you refer to is not TP-Message-Reference but concatenated short message reference number. And it has the be the same for all concatenated messages. Actually in your log it is set to 88 but for some reason incorrectly propagated up.
TP-Message-Reference we do not set. Or rather we set it to 0. It is the task of the device to increase the sequence value. We are not able to trace the sequence in between the consecutive gnokii runs. So it does not make sense to set it in EPC. And quite frankly this is the first that kind report, so I would blame the device for that. Can you please try some other device (other manufacturer)? If the other would not work I would guess that most of the operators are ignoring TP-Message-Reference and that why we didn't have any bug report so far.
If it is the device fault, let's think about the workaround.