MC55i-W problems sending SMS PDU with long phone number? | Thales IoT Developer Community
July 8, 2019 - 8:28am, 2560 views
Hi,
we are using the Cinterion MC55i-W to send SMS. This seems not to work when there is a 15 digit (without country code) destination pnone number. Other numbers are working fine. Also the SMS PDU we create seems to be OK. Nevertheless the modem reports an error after the PDU is sent to it. Is there any experience that specific nubers are not working with this module?
AT0
AT+CPIN?
AT+CPIN?+CPIN: READY
0
AT+CMGS=29
AT+CMGS=29
>
0011000F81101752xxxxxxxxF80F0000AA0DC672BD2C071DE570902C46FB<1A>
0011000F81101752xxxxxxxxF80F0000AA0DC672BD2C071DE570902C46FB<1A>4
(parts of the number was xxxxed out)
Denis
Hi Denis,
could you please send AT+CMEE=2 command to the module before sending PDU message? Thanks to it we will see enhanced error message from module instead of just "ERROR" after sending AT+CMGS command.
Many thanks,
Adam
Hi Adam,
Thank you for the hint. I have to do this on the customer side in the field.
But for my understanding... There is no problem in principle with such long phone numbers?
In the mean time I tried AT+CMEE=2 here in the office and it seems that the mc55i-W does not give any extra information about the error reason. I tried to use a wrong phone number and to use the modem without antenna (low CSQ value). Both resulted in error, but no further information about the reason from modem.
AT
0
AT+CPIN?
+CPIN: READY
0
AT+CMEE=2
0
AT+CMGS=45
>
0011000B81107******9F50000AA23AD560B34A5F3E575F719347C3641EB72DA5D062DDFED76DD9D5E87E9E9B7FB<1A>
4
AT+CMEE=0
0
AT
0
Hi Denis,
I think module does not give any additional message because you use numeric format **** (instead of error module returns 4. Could you please send ATV1 before the test?
I never heard about such issue. Unfortunately I don't have such long phone number to test with. Would it be possible for you to get from your customer this 15 digits phone number and test it in your office? You could also try to send SMS to the same phone number in text ****.
When I try to send PDU or text SMS to wrong phone number I get following error:
+CMS ERROR: Short message transfer rejected
Best regards,
Adam
Hi Adam,
I made the change on the customer side now and have a log with error message. Sorry for the long log but maybe the steps before the actual error are also important:
AT
0
ATZ
OK
ATE0
OK
AT+CPIN?
+CPIN: READY
ATV0&D2&C1S0=0
OK
0
AT+CMGF=0
0
AT+CREG?
+CREG: 0,1
0
AT+COPS?
+COPS: 0,0,"Telekom.de",0
0
AT+CPBS?
+CPBS: "SM",19,230
0
AT+CSCA=01710760000
+CME ERROR: invalid index
AT+CSCA=01710760000
+CME ERROR: invalid index
AT+CSCA=01710760000
+CME ERROR: invalid index
AT+CLIP=1
0
AT
0
AT
0
AT+CPIN?
+CPIN: READY
0
AT+CMEE=2
0
AT+CMGS=57
>
0011001091947121******4683100000AA2DC672BD2C07C962B2970C146C828E65312BC8025563A017A82A
341CBF2F9DB1D6697D3EE73D87DFE<1A>
+CMS ERROR: SMSC address unknown
Interresting here is that the error says unknown service center address while trying to set the CSCA results in error. This is always the same, even if we try to give the CSCA with country code or without giving a CSCA at all.
Hello,
Please try to read the current SCA with AT+CSCA? command. Please try the format +171... while configuring. Additionally you can specify the type of address <tosca> while configuring the number like below:
AT+CSCA=<sca>,<tosca>
You can set 145 for the international format with +.
In case of problems please also try to pass the number in quotation marks - I don't have the module to verify now but some module types may require quotation marks.
Please try with a text message first as it's easier. In case of PDU you SCA can also be encoded inside PDU - maybe there's a wrong service center number encoded in your PDU message.
Best regards,
Bartłomiej
Hello Bartłomiej,
Thank you for your tips. I hope I can try these things out on the customer side.