Re: Sending SMS in PDU mode fails.

2017-08-09 Thread Aleksander Morgado 
 >>> As far as I know this happens only for Verizon customization that uses
 >>> SMS over IMS with 3GPP2 pdu.
 >>>
  Isn't this actually a bit weird, given that
  the LE866-SV1 is actually LTE-only (i.e. 3GPP-only, not 3GPP2)?
 >>>
 >>> Looks like a carrier requirement for SMS

 Or maybe we can let each plugin take care of this: for Telit modems
 probably we can think of checking some substring in the model name
 (e.g. -SV or -NV). Maybe other modems have a similar rule or some
 custom AT command that can be checked for that.

>>>
>>> I am not following all the technical details of the thread, but if we
>>> assume3GPP2 for the Telit LE866-SV modem, would that be a correct
>>> patch for ModemManager ?
>>>
>>
>> Not really, no. LTE is 3GPP, so the LE866-SV is 3GPP, regardless of
>> operator, we cannot change that or it wouldn't work in MM. What we
>> need is a way to "switch to 3GPP2 SMS messaging" in 3GPP-only modems,
>> either automagically (maybe flagging this specific modem to do so via
>> a udev tag) or via a user-requested option when creating the SMS.
>>
>>> It is my understanding that this modem can only be used with Verizon SIM 
>>> cards.
>>
>> Is the modem locked to Verizon in any way?
>>
>
> Yes, the SV will work properly only on Verizon.
>

I realize that a udev tag wouldn't work in this case, as this module
may be integrated via RS232 (so there's no reliable vid:pid to
associate). If we need a quirk for SMS messaging in this module, we
probably need to hardcode it based on the AT-queried device model.

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-08 Thread José 
On Tue, Aug 8, 2017 at 4:40 PM, Aleksander Morgado
 wrote:
> Not really, no. LTE is 3GPP, so the LE866-SV is 3GPP, regardless of
> operator, we cannot change that or it wouldn't work in MM. What we
> need is a way to "switch to 3GPP2 SMS messaging" in 3GPP-only modems,
> either automagically (maybe flagging this specific modem to do so via
> a udev tag) or via a user-requested option when creating the SMS.
>

Umh, a udev tag will also work for us.

>> It is my understanding that this modem can only be used with Verizon SIM 
>> cards.
>
> Is the modem locked to Verizon in any way?
>

I am not sure, my mate in US was telling me that. I also found that
they list 'Verizon' as the only provider in some documents, like
second page of this PDF:

http://www.telit.com/fileadmin/user_upload/media/products/cellular/4_G/LE866/Telit_LE866_Datasheet_AG.pdf
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-07 Thread Daniele Palmas 
2017-08-07 11:04 GMT+02:00 Aleksander Morgado :
>>> I can confirm that LE866-SV1 uses Telit custom 3GPP2 PDU format: there
>>> should be a PDU example in the AT commands user guide (see +CMGS
>>> 3GPP2), while EU variants use 3GPP.
>>
>> Thanks for the information. Then it is expected that the USA version (the
>> one I reported) does not work with ModemManager because it uses 3GPP2 PDU
>> format? Or is this format also supported in ModemManager?
>>
>
> My understanding is that it is currently not supported in ModemManager.
>

 But... 
 https://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/mm-sms-part-cdma.c

 The issue here is that the message isn't formatted as 3GPP2/CDMA
 because the modem is actually an LTE modem (i.e. 3GPP). As soon as a
 modem is 3GPP, we use the 3GPP format, see:
 https://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/mm-base-sms.c#n311

 The question now would be, is this something that happens to all
 US-version Telit modems?
>>>
>>> As far as I know this happens only for Verizon customization that uses
>>> SMS over IMS with 3GPP2 pdu.
>>>
 Isn't this actually a bit weird, given that
 the LE866-SV1 is actually LTE-only (i.e. 3GPP-only, not 3GPP2)?
>>>
>>> Looks like a carrier requirement for SMS.
>>>
>>
>> See also Reinhard's comment about this:
>>
>> https://lists.freedesktop.org/archives/modemmanager-devel/2016-January/002468.html
>>
>
> Interesting... I now wonder how we can setup all this to work
> automatically, if at all possible. We don't have any carrier-specific
> customization right now anywhere. Maybe some user specified parameter
> asking for a specific type of PDU to generate?
>

For this specific scenario would it be a too ugly hack blindly
re-trying with 3GPP2 if 3GPP fails and then storing the setting if
successful?

Unfortunately the result code is not helpful here (CMS ERROR: 41 that
is temporary failure), but this could be something Telit specific...

Or maybe we can let each plugin take care of this: for Telit modems
probably we can think of checking some substring in the model name
(e.g. -SV or -NV). Maybe other modems have a similar rule or some
custom AT command that can be checked for that.

Just throwing some ideas, not sure how much they make sense..

However a more generic way to address carrier customization issues
could be helpful for other scenarios.

Daniele

> --
> Aleksander
> https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-07 Thread Aleksander Morgado 
>> I can confirm that LE866-SV1 uses Telit custom 3GPP2 PDU format: there
>> should be a PDU example in the AT commands user guide (see +CMGS
>> 3GPP2), while EU variants use 3GPP.
>
> Thanks for the information. Then it is expected that the USA version (the
> one I reported) does not work with ModemManager because it uses 3GPP2 PDU
> format? Or is this format also supported in ModemManager?
>

 My understanding is that it is currently not supported in ModemManager.

>>>
>>> But... 
>>> https://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/mm-sms-part-cdma.c
>>>
>>> The issue here is that the message isn't formatted as 3GPP2/CDMA
>>> because the modem is actually an LTE modem (i.e. 3GPP). As soon as a
>>> modem is 3GPP, we use the 3GPP format, see:
>>> https://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/mm-base-sms.c#n311
>>>
>>> The question now would be, is this something that happens to all
>>> US-version Telit modems?
>>
>> As far as I know this happens only for Verizon customization that uses
>> SMS over IMS with 3GPP2 pdu.
>>
>>> Isn't this actually a bit weird, given that
>>> the LE866-SV1 is actually LTE-only (i.e. 3GPP-only, not 3GPP2)?
>>
>> Looks like a carrier requirement for SMS.
>>
>
> See also Reinhard's comment about this:
>
> https://lists.freedesktop.org/archives/modemmanager-devel/2016-January/002468.html
>

Interesting... I now wonder how we can setup all this to work
automatically, if at all possible. We don't have any carrier-specific
customization right now anywhere. Maybe some user specified parameter
asking for a specific type of PDU to generate?

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-07 Thread Daniele Palmas 
2017-08-07 10:39 GMT+02:00 Daniele Palmas :
> 2017-08-07 10:24 GMT+02:00 Aleksander Morgado :
> I can confirm that LE866-SV1 uses Telit custom 3GPP2 PDU format: there
> should be a PDU example in the AT commands user guide (see +CMGS
> 3GPP2), while EU variants use 3GPP.

 Thanks for the information. Then it is expected that the USA version (the
 one I reported) does not work with ModemManager because it uses 3GPP2 PDU
 format? Or is this format also supported in ModemManager?

>>>
>>> My understanding is that it is currently not supported in ModemManager.
>>>
>>
>> But... 
>> https://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/mm-sms-part-cdma.c
>>
>> The issue here is that the message isn't formatted as 3GPP2/CDMA
>> because the modem is actually an LTE modem (i.e. 3GPP). As soon as a
>> modem is 3GPP, we use the 3GPP format, see:
>> https://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/mm-base-sms.c#n311
>>
>> The question now would be, is this something that happens to all
>> US-version Telit modems?
>
> As far as I know this happens only for Verizon customization that uses
> SMS over IMS with 3GPP2 pdu.
>
>> Isn't this actually a bit weird, given that
>> the LE866-SV1 is actually LTE-only (i.e. 3GPP-only, not 3GPP2)?
>
> Looks like a carrier requirement for SMS.
>

See also Reinhard's comment about this:

https://lists.freedesktop.org/archives/modemmanager-devel/2016-January/002468.html

Daniele

> Regards,
> Daniele
>
>>
>> --
>> Aleksander
>> https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-07 Thread Aleksander Morgado 
>>> I can confirm that LE866-SV1 uses Telit custom 3GPP2 PDU format: there
>>> should be a PDU example in the AT commands user guide (see +CMGS
>>> 3GPP2), while EU variants use 3GPP.
>>
>> Thanks for the information. Then it is expected that the USA version (the
>> one I reported) does not work with ModemManager because it uses 3GPP2 PDU
>> format? Or is this format also supported in ModemManager?
>>
>
> My understanding is that it is currently not supported in ModemManager.
>

But... 
https://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/mm-sms-part-cdma.c

The issue here is that the message isn't formatted as 3GPP2/CDMA
because the modem is actually an LTE modem (i.e. 3GPP). As soon as a
modem is 3GPP, we use the 3GPP format, see:
https://cgit.freedesktop.org/ModemManager/ModemManager/tree/src/mm-base-sms.c#n311

The question now would be, is this something that happens to all
US-version Telit modems? Isn't this actually a bit weird, given that
the LE866-SV1 is actually LTE-only (i.e. 3GPP-only, not 3GPP2)?

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-07 Thread Daniele Palmas 
2017-08-07 9:50 GMT+02:00 José :
>
> On Mon, Aug 7, 2017 at 9:46 AM, Daniele Palmas  wrote:
>> I can confirm that LE866-SV1 uses Telit custom 3GPP2 PDU format: there
>> should be a PDU example in the AT commands user guide (see +CMGS
>> 3GPP2), while EU variants use 3GPP.
>
> Thanks for the information. Then it is expected that the USA version (the
> one I reported) does not work with ModemManager because it uses 3GPP2 PDU
> format? Or is this format also supported in ModemManager?
>

My understanding is that it is currently not supported in ModemManager.

Regards,
Daniele
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-07 Thread Daniele Palmas 
Hi Josè,

2017-08-04 16:18 GMT+02:00 José :
> On Fri, Aug 4, 2017 at 4:14 PM, Daniele Palmas  wrote:
>>
>> as far as I remember 3GPP pdu should be supported, but maybe this
>> could depend on firmware customizations.
>>
> Just in case, this is the information for the Modem I am using:
>
>   -
>   Hardware |   manufacturer: 'Telit'
>|  model: 'LE866-SV1'

I can confirm that LE866-SV1 uses Telit custom 3GPP2 PDU format: there
should be a PDU example in the AT commands user guide (see +CMGS
3GPP2), while EU variants use 3GPP.

Regards,
Daniele

>|   revision: '23.00.002 (M0A.00020)'
>|  supported: 'lte'
>|current: 'lte'
>|   equipment id: '352613070097419'
>   -
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-04 Thread José 
On Fri, Aug 4, 2017 at 4:14 PM, Daniele Palmas  wrote:
>
> as far as I remember 3GPP pdu should be supported, but maybe this
> could depend on firmware customizations.
>
Just in case, this is the information for the Modem I am using:

  -
  Hardware |   manufacturer: 'Telit'
   |  model: 'LE866-SV1'
   |   revision: '23.00.002 (M0A.00020)'
   |  supported: 'lte'
   |current: 'lte'
   |   equipment id: '352613070097419'
  -
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-04 Thread Daniele Palmas 
Hi Aleksander and José,

2017-08-04 15:24 GMT+02:00 Aleksander Morgado :
> Hey José, Carlo & Daniele
>
> On Fri, Aug 4, 2017 at 10:27 AM, José  wrote:
>> I am trying the same thing with the Telit LE866. With that modem I am
>> able to send SMSs in Text mode using AT commands, but no in PDU mode.
>>
>
> Hum I totally believe I did send SMS in PDU mode with the Telit
> LE866 a while back... What is the error you're getting, and which is
> the actual PDU you're trying to send?
>
>> I have been told that "Telit's PDU mode doesn't use the standard GSM
>> PDUs" but I am checking the AT Reference sheet and this is not clear
>> to me. Does anyone know about this? Would it be possible to make the
>> Telit plugin from ModemManager to use Text mode for the LE866-SV1?
>>
>
> Carlo, Daniele, do you have any comment on that statement regarding
> Telit's PDU mode?
>

as far as I remember 3GPP pdu should be supported, but maybe this
could depend on firmware customizations.

I'm checking this internally, but since it is vacation time it could
not be immediate.

Regards,
Daniele

> --
> Aleksander
> https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-04 Thread José 
On Fri, Aug 4, 2017 at 3:24 PM, Aleksander Morgado
 wrote:
> Hum I totally believe I did send SMS in PDU mode with the Telit
> LE866 a while back... What is the error you're getting, and which is
> the actual PDU you're trying to send?
>

Sorry, I forgot to include that. Here are the commands I tried and the output:

root@ccimx6ulsbc:~# mmcli -m 0 --messaging-create-sms="text='Hello
world',number='+197'"
Successfully created new SMS:
/org/freedesktop/ModemManager1/SMS/3 (unknown)

 [1501854124.113201] [../../git/src/mm-iface-modem.c:1206]
update_signal_quality(): Modem /org/freedesktop/ModemManager1/Modem/0:
signal quality updated (6)

root@ccimx6ulsbc:~# mmcli -s 3 --send
error: couldn't send the SMS:
'GDBus.Error:org.freedesktop.ModemManager1.Error.Message.Unknown:
Unknown error'

 [1501854251.236624] [../../git/src/mm-base-sms.c:178]
generate_3gpp_submit_pdus():   Processing chunk '0' of text with '11'
bytes
 [1501854251.238542] [../../git/src/mm-base-sms.c:208]
generate_3gpp_submit_pdus(): Created SMS part for singlepart SMS
 [1501854251.241746] [../../git/src/mm-sms-part-3gpp.c:805]
mm_sms_part_3gpp_get_submit_pdu(): Creating PDU for part...
 [1501854251.243373] [../../git/src/mm-sms-part-3gpp.c:892]
mm_sms_part_3gpp_get_submit_pdu():   using GSM7 encoding...
 [1501854251.244973] [../../git/src/mm-sms-part-3gpp.c:957]
mm_sms_part_3gpp_get_submit_pdu():   user data length is '11' septets
(without UDH)
 [1501854251.246756] [../../git/src/mm-port-serial.c:1250]
mm_port_serial_open(): (ttymxc1) device open count is 2 (open)
 [1501854251.248551] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc1): --> 'AT+CMGS=23'
 [1501854251.262761] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc1): <-- 'AT'
 [1501854251.274812] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc1): <-- '+CMGS=23'
 [1501854251.284741] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc1): <-- '> '
 [1501854251.286704] [../../git/src/mm-port-serial.c:1250]
mm_port_serial_open(): (ttymxc1) device open count is 3 (open)
 [1501854251.288503] [../../git/src/mm-port-serial.c:1307]
_close_internal(): (ttymxc1) device open count is 2 (close)
 [1501854251.290317] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc1): -->
'0001000B91910700F00BC8329BFD06DDDF723619\26'
 [1501854251.345394] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc1): <-- '0'
 [1501854251.370661] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc1): <-- '+CMS ERROR: 41'
 [1501854251.373089] [../../git/src/mm-error-helpers.c:218]
mm_message_error_for_code(): Invalid message error code: 41
 [1501854251.374966] [../../git/src/mm-serial-parsers.c:364]
mm_serial_parser_v1_parse(): Got failure code 500: Unknown error
 [1501854251.376918] [../../git/src/mm-port-serial.c:1307]
_close_internal(): (ttymxc1) device open count is 1 (close)


Same setup if I use microcom to send the SMS using text mode, it works fine.

>> I have been told that "Telit's PDU mode doesn't use the standard GSM
>> PDUs" but I am checking the AT Reference sheet and this is not clear
>> to me. Does anyone know about this? Would it be possible to make the
>> Telit plugin from ModemManager to use Text mode for the LE866-SV1?
>>
>
> Carlo, Daniele, do you have any comment on that statement regarding
> Telit's PDU mode?
>

Some extra information:

One thing that’s not described in the PDF is that encoding value 0x09
indicates GSM 7-bit (i.e. what you’d normally put into a PDU), and
that while “7-bit ASCII” and “GSM 7-bit” septets are packed into
octets differently. I don’t remember off the top of my head which
encoding leads to which packing order, but it’s easy enough to figure
out if you send the module an SMS and just look at the bits.


I also got this example: http://i.imgur.com/WJYRFiv.png
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-04 Thread José 
I am trying the same thing with the Telit LE866. With that modem I am
able to send SMSs in Text mode using AT commands, but no in PDU mode.

I have been told that "Telit's PDU mode doesn't use the standard GSM
PDUs" but I am checking the AT Reference sheet and this is not clear
to me. Does anyone know about this? Would it be possible to make the
Telit plugin from ModemManager to use Text mode for the LE866-SV1?

On Thu, Aug 3, 2017 at 6:53 PM, José  wrote:
> I was not register in the network : (
>
> Working now, thanks!
>
> I think I have a different problem with the XBee US version, but I
> will let you know if I cannot solve that.
>
> On Thu, Aug 3, 2017 at 1:13 PM, Aleksander Morgado
>  wrote:
>> On 03/08/17 11:04, José  wrote:
>>> I am using the 3G XBee Cellular (uses U-Blox SARA-U200 modem) and
>>> ModemManager from master (d41d717112e6a183a0df510c210e80a86fc11060).
>>>
>>> I am trying to send an SMS with the following commands:
>>>
>>> $ mmcli -m 0 --messaging-create-sms="text='Hello world',number='+627XX"
>>> Successfully created new SMS:
>>> /org/freedesktop/ModemManager1/SMS/10 (unknown)
>>>
>>> $ mmcli -s 10 --send
>>> error: couldn't send the SMS:
>>> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Message.Unknown:
>>> Unknown error'
>>>
>>>
>>> The log shows:
>>>
>>>  [1501676070.461276]
>>> [../../git/src/mm-iface-modem-messaging.c:511] sms_added(): Added
>>> local SMS at '/org/freedesktop/ModemManager1/SMS/8'
>>>  [1501676078.360084] [../../git/src/mm-base-sms.c:178]
>>> generate_3gpp_submit_pdus():   Processing chunk '0' of text with '11'
>>> bytes
>>>  [1501676078.371070] [../../git/src/mm-base-sms.c:208]
>>> generate_3gpp_submit_pdus(): Created SMS part for singlepart SMS
>>>  [1501676078.374057] [../../git/src/mm-sms-part-3gpp.c:805]
>>> mm_sms_part_3gpp_get_submit_pdu(): Creating PDU for part...
>>>  [1501676078.377048] [../../git/src/mm-sms-part-3gpp.c:892]
>>> mm_sms_part_3gpp_get_submit_pdu():   using GSM7 encoding...
>>>  [1501676078.379982] [../../git/src/mm-sms-part-3gpp.c:957]
>>> mm_sms_part_3gpp_get_submit_pdu():   user data length is '11' septets
>>> (without UDH)
>>>  [1501676078.382961] [../../git/src/mm-port-serial.c:1250]
>>> mm_port_serial_open(): (ttymxc4) device open count is 2 (open)
>>>  [1501676078.386006] [../../git/src/mm-port-serial-at.c:459]
>>> debug_log(): (ttymxc4): --> 'AT+CMGS=22'
>>>  [1501676078.431257] [../../git/src/mm-port-serial-at.c:459]
>>> debug_log(): (ttymxc4): <-- '> '
>>>  [1501676078.435569] [../../git/src/mm-port-serial.c:1250]
>>> mm_port_serial_open(): (ttymxc4) device open count is 3 (open)
>>>  [1501676078.438554] [../../git/src/mm-port-serial.c:1307]
>>> _close_internal(): (ttymxc4) device open count is 2 (close)
>>>  [1501676078.441551] [../../git/src/mm-port-serial-at.c:459]
>>> debug_log(): (ttymxc4): -->
>>> '00010009912637F10BC8329BFD06DDDF723619\26'
>>>  [1501676078.573891] [../../git/src/mm-port-serial-at.c:459]
>>> debug_log(): (ttymxc4): <-- '+CMS ERROR: 38'
>>>  [1501676078.597195] [../../git/src/mm-error-helpers.c:218]
>>> mm_message_error_for_code(): Invalid message error code: 38
>>>  [1501676078.600884] [../../git/src/mm-serial-parsers.c:364]
>>> mm_serial_parser_v1_parse(): Got failure code 500: Unknown error
>>>  [1501676078.604622] [../../git/src/mm-port-serial.c:1307]
>>> _close_internal(): (ttymxc4) device open count is 1 (close)
>>>
>>> However if I use a serial console and the following AT commands, the
>>> SMS is properly sent:
>>>
>>> ATZ
>>> OK
>>> AT+CMGF=1
>>> OK
>>> AT+CMGS="+627XX"
 Hello world
>>> +CMGS: 193
>>>
>>> OK
>>>
>>>
>>> a) Could you give any information about why is PDU mode failing?
>>> According to U-Blox documentation (1) it should be working
>>>
>>
>> I'm assuming that if you send the PDU manually using a serial console it 
>> also doesn't work, did you try that?
>> +CMS error 38 is "Network out of order", but I'm not sure why text mode 
>> would work without error while PDU mode gives error 38.
>>
>>> b) Is there a way to tell ModemManager to use text mode when sending SMSs?
>>
>> No; text mode is only used by default when PDU mode isn't supported. PDU 
>> mode is always preferred really.
>>
>> Also, which are your SMSC settings? E.g.:
>>   AT+CSCA?
>>
>> --
>> Aleksander
>> https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-03 Thread José 
I was not register in the network : (

Working now, thanks!

I think I have a different problem with the XBee US version, but I
will let you know if I cannot solve that.

On Thu, Aug 3, 2017 at 1:13 PM, Aleksander Morgado
 wrote:
> On 03/08/17 11:04, José  wrote:
>> I am using the 3G XBee Cellular (uses U-Blox SARA-U200 modem) and
>> ModemManager from master (d41d717112e6a183a0df510c210e80a86fc11060).
>>
>> I am trying to send an SMS with the following commands:
>>
>> $ mmcli -m 0 --messaging-create-sms="text='Hello world',number='+627XX"
>> Successfully created new SMS:
>> /org/freedesktop/ModemManager1/SMS/10 (unknown)
>>
>> $ mmcli -s 10 --send
>> error: couldn't send the SMS:
>> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Message.Unknown:
>> Unknown error'
>>
>>
>> The log shows:
>>
>>  [1501676070.461276]
>> [../../git/src/mm-iface-modem-messaging.c:511] sms_added(): Added
>> local SMS at '/org/freedesktop/ModemManager1/SMS/8'
>>  [1501676078.360084] [../../git/src/mm-base-sms.c:178]
>> generate_3gpp_submit_pdus():   Processing chunk '0' of text with '11'
>> bytes
>>  [1501676078.371070] [../../git/src/mm-base-sms.c:208]
>> generate_3gpp_submit_pdus(): Created SMS part for singlepart SMS
>>  [1501676078.374057] [../../git/src/mm-sms-part-3gpp.c:805]
>> mm_sms_part_3gpp_get_submit_pdu(): Creating PDU for part...
>>  [1501676078.377048] [../../git/src/mm-sms-part-3gpp.c:892]
>> mm_sms_part_3gpp_get_submit_pdu():   using GSM7 encoding...
>>  [1501676078.379982] [../../git/src/mm-sms-part-3gpp.c:957]
>> mm_sms_part_3gpp_get_submit_pdu():   user data length is '11' septets
>> (without UDH)
>>  [1501676078.382961] [../../git/src/mm-port-serial.c:1250]
>> mm_port_serial_open(): (ttymxc4) device open count is 2 (open)
>>  [1501676078.386006] [../../git/src/mm-port-serial-at.c:459]
>> debug_log(): (ttymxc4): --> 'AT+CMGS=22'
>>  [1501676078.431257] [../../git/src/mm-port-serial-at.c:459]
>> debug_log(): (ttymxc4): <-- '> '
>>  [1501676078.435569] [../../git/src/mm-port-serial.c:1250]
>> mm_port_serial_open(): (ttymxc4) device open count is 3 (open)
>>  [1501676078.438554] [../../git/src/mm-port-serial.c:1307]
>> _close_internal(): (ttymxc4) device open count is 2 (close)
>>  [1501676078.441551] [../../git/src/mm-port-serial-at.c:459]
>> debug_log(): (ttymxc4): -->
>> '00010009912637F10BC8329BFD06DDDF723619\26'
>>  [1501676078.573891] [../../git/src/mm-port-serial-at.c:459]
>> debug_log(): (ttymxc4): <-- '+CMS ERROR: 38'
>>  [1501676078.597195] [../../git/src/mm-error-helpers.c:218]
>> mm_message_error_for_code(): Invalid message error code: 38
>>  [1501676078.600884] [../../git/src/mm-serial-parsers.c:364]
>> mm_serial_parser_v1_parse(): Got failure code 500: Unknown error
>>  [1501676078.604622] [../../git/src/mm-port-serial.c:1307]
>> _close_internal(): (ttymxc4) device open count is 1 (close)
>>
>> However if I use a serial console and the following AT commands, the
>> SMS is properly sent:
>>
>> ATZ
>> OK
>> AT+CMGF=1
>> OK
>> AT+CMGS="+627XX"
>>> Hello world
>> +CMGS: 193
>>
>> OK
>>
>>
>> a) Could you give any information about why is PDU mode failing?
>> According to U-Blox documentation (1) it should be working
>>
>
> I'm assuming that if you send the PDU manually using a serial console it also 
> doesn't work, did you try that?
> +CMS error 38 is "Network out of order", but I'm not sure why text mode would 
> work without error while PDU mode gives error 38.
>
>> b) Is there a way to tell ModemManager to use text mode when sending SMSs?
>
> No; text mode is only used by default when PDU mode isn't supported. PDU mode 
> is always preferred really.
>
> Also, which are your SMSC settings? E.g.:
>   AT+CSCA?
>
> --
> Aleksander
> https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Re: Sending SMS in PDU mode fails.

2017-08-03 Thread Aleksander Morgado 
On 03/08/17 11:04, José  wrote:
> I am using the 3G XBee Cellular (uses U-Blox SARA-U200 modem) and
> ModemManager from master (d41d717112e6a183a0df510c210e80a86fc11060).
> 
> I am trying to send an SMS with the following commands:
> 
> $ mmcli -m 0 --messaging-create-sms="text='Hello world',number='+627XX"
> Successfully created new SMS:
> /org/freedesktop/ModemManager1/SMS/10 (unknown)
> 
> $ mmcli -s 10 --send
> error: couldn't send the SMS:
> 'GDBus.Error:org.freedesktop.ModemManager1.Error.Message.Unknown:
> Unknown error'
> 
> 
> The log shows:
> 
>  [1501676070.461276]
> [../../git/src/mm-iface-modem-messaging.c:511] sms_added(): Added
> local SMS at '/org/freedesktop/ModemManager1/SMS/8'
>  [1501676078.360084] [../../git/src/mm-base-sms.c:178]
> generate_3gpp_submit_pdus():   Processing chunk '0' of text with '11'
> bytes
>  [1501676078.371070] [../../git/src/mm-base-sms.c:208]
> generate_3gpp_submit_pdus(): Created SMS part for singlepart SMS
>  [1501676078.374057] [../../git/src/mm-sms-part-3gpp.c:805]
> mm_sms_part_3gpp_get_submit_pdu(): Creating PDU for part...
>  [1501676078.377048] [../../git/src/mm-sms-part-3gpp.c:892]
> mm_sms_part_3gpp_get_submit_pdu():   using GSM7 encoding...
>  [1501676078.379982] [../../git/src/mm-sms-part-3gpp.c:957]
> mm_sms_part_3gpp_get_submit_pdu():   user data length is '11' septets
> (without UDH)
>  [1501676078.382961] [../../git/src/mm-port-serial.c:1250]
> mm_port_serial_open(): (ttymxc4) device open count is 2 (open)
>  [1501676078.386006] [../../git/src/mm-port-serial-at.c:459]
> debug_log(): (ttymxc4): --> 'AT+CMGS=22'
>  [1501676078.431257] [../../git/src/mm-port-serial-at.c:459]
> debug_log(): (ttymxc4): <-- '> '
>  [1501676078.435569] [../../git/src/mm-port-serial.c:1250]
> mm_port_serial_open(): (ttymxc4) device open count is 3 (open)
>  [1501676078.438554] [../../git/src/mm-port-serial.c:1307]
> _close_internal(): (ttymxc4) device open count is 2 (close)
>  [1501676078.441551] [../../git/src/mm-port-serial-at.c:459]
> debug_log(): (ttymxc4): -->
> '00010009912637F10BC8329BFD06DDDF723619\26'
>  [1501676078.573891] [../../git/src/mm-port-serial-at.c:459]
> debug_log(): (ttymxc4): <-- '+CMS ERROR: 38'
>  [1501676078.597195] [../../git/src/mm-error-helpers.c:218]
> mm_message_error_for_code(): Invalid message error code: 38
>  [1501676078.600884] [../../git/src/mm-serial-parsers.c:364]
> mm_serial_parser_v1_parse(): Got failure code 500: Unknown error
>  [1501676078.604622] [../../git/src/mm-port-serial.c:1307]
> _close_internal(): (ttymxc4) device open count is 1 (close)
> 
> However if I use a serial console and the following AT commands, the
> SMS is properly sent:
> 
> ATZ
> OK
> AT+CMGF=1
> OK
> AT+CMGS="+627XX"
>> Hello world
> +CMGS: 193
> 
> OK
> 
> 
> a) Could you give any information about why is PDU mode failing?
> According to U-Blox documentation (1) it should be working
> 

I'm assuming that if you send the PDU manually using a serial console it also 
doesn't work, did you try that?
+CMS error 38 is "Network out of order", but I'm not sure why text mode would 
work without error while PDU mode gives error 38.

> b) Is there a way to tell ModemManager to use text mode when sending SMSs?

No; text mode is only used by default when PDU mode isn't supported. PDU mode 
is always preferred really.

Also, which are your SMSC settings? E.g.:
  AT+CSCA?

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Sending SMS in PDU mode fails.

2017-08-03 Thread José 
I am using the 3G XBee Cellular (uses U-Blox SARA-U200 modem) and
ModemManager from master (d41d717112e6a183a0df510c210e80a86fc11060).

I am trying to send an SMS with the following commands:

$ mmcli -m 0 --messaging-create-sms="text='Hello world',number='+627XX"
Successfully created new SMS:
/org/freedesktop/ModemManager1/SMS/10 (unknown)

$ mmcli -s 10 --send
error: couldn't send the SMS:
'GDBus.Error:org.freedesktop.ModemManager1.Error.Message.Unknown:
Unknown error'


The log shows:

 [1501676070.461276]
[../../git/src/mm-iface-modem-messaging.c:511] sms_added(): Added
local SMS at '/org/freedesktop/ModemManager1/SMS/8'
 [1501676078.360084] [../../git/src/mm-base-sms.c:178]
generate_3gpp_submit_pdus():   Processing chunk '0' of text with '11'
bytes
 [1501676078.371070] [../../git/src/mm-base-sms.c:208]
generate_3gpp_submit_pdus(): Created SMS part for singlepart SMS
 [1501676078.374057] [../../git/src/mm-sms-part-3gpp.c:805]
mm_sms_part_3gpp_get_submit_pdu(): Creating PDU for part...
 [1501676078.377048] [../../git/src/mm-sms-part-3gpp.c:892]
mm_sms_part_3gpp_get_submit_pdu():   using GSM7 encoding...
 [1501676078.379982] [../../git/src/mm-sms-part-3gpp.c:957]
mm_sms_part_3gpp_get_submit_pdu():   user data length is '11' septets
(without UDH)
 [1501676078.382961] [../../git/src/mm-port-serial.c:1250]
mm_port_serial_open(): (ttymxc4) device open count is 2 (open)
 [1501676078.386006] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc4): --> 'AT+CMGS=22'
 [1501676078.431257] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc4): <-- '> '
 [1501676078.435569] [../../git/src/mm-port-serial.c:1250]
mm_port_serial_open(): (ttymxc4) device open count is 3 (open)
 [1501676078.438554] [../../git/src/mm-port-serial.c:1307]
_close_internal(): (ttymxc4) device open count is 2 (close)
 [1501676078.441551] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc4): -->
'00010009912637F10BC8329BFD06DDDF723619\26'
 [1501676078.573891] [../../git/src/mm-port-serial-at.c:459]
debug_log(): (ttymxc4): <-- '+CMS ERROR: 38'
 [1501676078.597195] [../../git/src/mm-error-helpers.c:218]
mm_message_error_for_code(): Invalid message error code: 38
 [1501676078.600884] [../../git/src/mm-serial-parsers.c:364]
mm_serial_parser_v1_parse(): Got failure code 500: Unknown error
 [1501676078.604622] [../../git/src/mm-port-serial.c:1307]
_close_internal(): (ttymxc4) device open count is 1 (close)

However if I use a serial console and the following AT commands, the
SMS is properly sent:

ATZ
OK
AT+CMGF=1
OK
AT+CMGS="+627XX"
> Hello world
+CMGS: 193

OK


a) Could you give any information about why is PDU mode failing?
According to U-Blox documentation (1) it should be working

b) Is there a way to tell ModemManager to use text mode when sending SMSs?

Thanks


(1) 
https://www.u-blox.com/sites/default/files/u-blox-ATCommands_Manual_(UBX-13002752).pdf
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel