How to send and receive SMS via AT-Command with nokia E63 ?

dongtrien wrote:

I do not know why when I type the left arrow "" and the right arrow ""
This page is not displayed.

I do not follow your meaning. I do not understand.

case 2: messages of more than 160 characters
when I send a message more than 160 characters, I've split the message
into multiple messages children, each message children smaller than or
equal to 160 characters before sending, the receiving device know how
that "message is concatenated" ?, in HyperTerminal you can perform at
command syntax to send messages longer than 160 characters like ?

What is the problem here? If the total message text length is 100
characters, and you are splitting it into two messages, does the receiving
device receive both messages OK?

Is the problem just that you want the receiving device to automatically join
the two messages back into a single message?

case 3:
AT+CSMP?
+CSMP: 17,167,0,0
OK

I'll work through those four values.

Your PDU-type octet is set to 17 decimal. That's 11 hex, and 00010001
binary. This is normal for an ordinary SMS with no User Data Header.

Your Validity Period is set to 167 decimal That's A7 hex and means 24
hours.

If the message centre which accepts your messages for delivery is unable to
deliver those messages within 24 hours, they will be deleted and no further
delivery attempts will be made.

You might want to increase that value. Or even reduce it.

Your PID (Protocol ID) is zero. This is a normal value for an SMS to be
sent.

Finally, your DCS (Data Coding Scheme) value is also zero. This means that
you'll be using the SMS 7-bit default alphabet. So if you use

AT+CSCS="HEX"

your hex data will be converted by the sending device into SMS 7-bit
characters before sending.

This is clearly not what you want. You want to send 16-bit unicode
characters.

So before you send the message, set your DCS to 8 (eight). Issue the
command:

AT+CSMP=17,167,0,8

If you want to increase the Validity Period from 24 hours to 7 days, use:

AT+CSMP=17,173,0,8

instead.

Don't forget to change the DCS back to zero before you try to send a 7-bit
message again.

John

I do not know DCS and DCS values I set correctly for 16-bit characters
like ? How i must set the PDU-type UDHI bit octet ? you can perform
syntax at via HyperTerminal ?

This site does not support the strange (wild) characters and other
features should I attach files this content
http://www.mediafire.com/view/0e3mco.../case2and3.txt

dongtrien wrote:

case 3:
I did not send the message unicode characters when after receiving a
message full of wild characters:

Code:
--------------------

0 Message3 less than or equal 70 // the string less than or equal 70
characters

AT
OK

AT + CMGF = 1
OK

AT + CSCS = "Hex"
OK

AT + CMGS = "0196704xxxx"
* MessageUnicode = (Hex)Message3 + (control + z)

--------------------

On further reading,

AT+CSCS="HEX"

might not work for 16-bit. If your device supports it,

AT+CSCS="UCS2"

might be required instead.

The DCS value should still be 8.

You can list your supported values with:

AT+CSCS=?

John

What is the problem here? If the total message text length is 100
characters, and you are splitting it into two messages, does the receiving
device receive both messages OK?

Is the problem just that you want the receiving device to automatically join
the two messages back into a single message?

--------------------

I divide the message into several messages while the total length greater than 160 characters, suppose I have a message 195 characters I spent a 2 message, the first message 160 characters 2nd message with 35 characters remaining, sending just first message is received not received 2nd message I do not know why ?

According to your instructions above, I sent a message unicode Okay, the reason is I do not know the declaration, now I've got it

Now I figure one another questions you can answer to help me? as I know there are two ways to send messages unicode, 1 you have guided me then, and a 2 code at the bottom, I do not see the recipient's phone and do not understand AT + CMGS = 34 it to do what? if I send this form AT + CSCS declaration = "HEX" or AT + CSCS = "UCS2" ?

AT+CMGF=0 
OK 
AT+CMGS=34 
0011000B912309157821xxx0008AA1400680065006C006C006F00680065006C006C006F

dongtrien wrote:

I divide the message into several messages while the total length
greater than 160 characters, suppose I have a message 195 characters I
spent a 2 message, the first message 160 characters 2nd message with 35
characters remaining, sending just first message is received not
received 2nd message I do not know why ?

When you send a message using AT commands, you are given a message reference
number for each message sent. Like:

+CMGS: 23

Did you get two message reference numbers? One for each message?

These numbers tell you that the message has been sent successfully.

According to your instructions above, I sent a message unicode Okay, the
reason is I do not know the declaration, now I've got it

Now I figure one another questions you can answer to help me? as I know
there are two ways to send messages unicode, 1 you have guided me then,
and a 2 code at the bottom, I do not see the recipient's phone and do
not understand AT + CMGS = 34 it to do what? if I send this form AT +
CSCS declaration = "HEX" or AT + CSCS = "UCS2" ?

Code:
--------------------

AT+CMGF=0
OK
AT+CMGS=34
0011000B912309157821xxx0008AA1400680065006C006C006 F00680065006C006C006F

The AT+CMGF=0 command puts the device into PDU-mode, not text-mode.

In PDU-mode the "34" argument for the send command is the number of octets
in the PDU. This is the number of octets without the SMSC (message centre)
information. In the case of your message, the first byte "00" is the SMSC
information. So the count doesn't include this.

Your PDU has a PDU-type of 11 hex. It's addressed to +3290518712xxx (but a
fill digit "F" is also missing).

PID is 00. DCS is 08. Validity period AA means 4 days.

There are 14 hex (20 decimal) octets of user data:

00680065006C006C006F00680065006C006C006F

It's 16-bit data, so the octets are decoded in pairs:

0068 h
0065 e
006C l
006C i
006F o
0068 h
0065 e
006C l
006C l
006F o

Is this what you wanted to know?

John

thank you for answer

Have you got use the DCOM 3G modern E173Eu-1 to send a message ? I read the document says this device is sent, but when I mount this device to a computer can not be used with HyperTerminal.

Hi John Henderson[_2_].
Are you John Henderson[_2_] here ? I want to ask you one problems command AT.

I write programs that run scripts at after active sim, I do not get the results returned via the command at + CMGL = "ALL", I run 70 sim returns the same results, you know why ? I sent you the file active 70 sim status.
the status file active sim, see you attach file: http://www.mediafire.com/download/25...MSLog_2016.txt

70 sim returns the same results:

at+cmgl="ALL"
+CMGL: 1,"REC READ","127",,"16/07/05,16:18:35+28"
Ma bi mat da duoc doi thanh cong. Ma giao dich 114612745.
+CMGL: 2,"REC READ","128",,"16/07/05,16:19:33+28"
Ban da dang ki su dung SHT  01867081033 thanh cong. Ma giao dich 62302820
+CMGL: 3,"REC READ","128",,"16/07/18,18:59:59+28"
Mat khau khong hop le.
+CMGL: 4,"REC READ","128",,"16/07/18,19:00:22+28"
Mat khau khong hop le.
+CMGL: 5,"REC READ","127",,"16/07/18,19:38:28+28"
Ban nhan duoc 10000000 dong tu thue bao 01867018798 ngay 18/07/2016 19:38:29. Ma giao dich 114806508.
+CMGL: 6,"REC READ","128",,"16/07/18,20:18:05+28"
Mat khau khong hop le.
+CMGL: 7,"REC READ","128",,"16/07/18,20:18:30+28"
Mat khau khong hop le.
+CMGL: 8,"REC READ","128",,"16/07/18,20:18:54+28"
Mat khau khong hop le.
+CMGL: 9,"REC READ","128",,"16/07/18,20:19:19+28"
Mat khau khong hop le.
+CMGL: 10,"REC READ","128",,"16/07/18,20:19:44+28"
Mat khau khong hop le.
+CMGL: 11,"REC READ","128",,"16/07/18,20:20:10+28"
Mat khau khong hop le.
+CMGL: 12,"REC READ","128",,"16/07/18,20:20:36+28"
Mat khau khong hop le.
+CMGL: 13,"REC READ","128",,"16/07/18,20:21:01+28"
Mat khau khong hop le.
+CMGL: 14,"REC READ","128",,"16/07/18,20:21:27+28"
Mat khau khong hop le.
+CMGL: 15,"REC READ","128",,"16/07/18,20:21:54+28"
Mat khau khong hop le.
+CMGL: 16,"REC READ","128",,"16/07/18,20:22:21+28"
Mat khau khong hop le.
+CMGL: 17,"REC READ","128",,"16/07/18,20:22:48+28"
Mat khau khong hop le.
+CMGL: 18,"REC READ","128",,"16/07/18,20:23:15+28"
Mat khau khong hop le.
+CMGL: 19,"REC READ","128",,"16/07/18,20:26:40+28"
Mat khau khong hop le.
+CMGL: 20,"REC READ","128",,"16/07/18,20:27:08+28"
Mat khau khong hop le.
+CMGL: 21,"REC READ","127",,"16/07/18,20:28:53+28"
Ma bi mat khong dung. Vui long nhap lai.Tai khoan ETOPUP se bi khoa sau 5 lan nhap sai ma PIN lien tiep. Ma giao dich 114807221.
+CMGL: 22,"REC READ","127",,"16/07/18,20:29:21+28"
Ma bi mat khong dung. Vui long nhap lai.Tai khoan ETOPUP se bi khoa sau 5 lan nhap sai ma PIN lien tiep. Ma giao dich 114807226.
+CMGL: 23,"REC READ","127",,"16/07/18,20:29:50+28"
Ban con 10.000.000 dong trong tai khoan. Ma giao dich 114807232.
+CMGL: 24,"REC READ","128",,"16/07/18,20:31:15+28"
Ban da dang ky thong tin cho so thue bao 0924132131 thanh cong. Ma giao dich 62479062
+CMGL: 25,"REC READ","128",,"16/07/18,20:31:44+28"
Ban da dang ky thong tin cho so thue bao 0924132134 thanh cong. Ma giao dich 62479076
+CMGL: 26,"REC READ","128",,"16/07/18,20:32:13+28"
Ban da dang ky thong tin cho so thue bao 0924132136 thanh cong. Ma giao dich 62479092
+CMGL: 27,"REC READ","128",,"16/07/18,20:32:43+28"
Ban da dang ky thong tin cho so thue bao 0924132137 thanh cong. Ma giao dich 62479104
+CMGL: 28,"REC READ","128",,"16/07/18,20:33:13+28"
Ban da dang ky thong tin cho so thue bao 0924132140 thanh cong. Ma giao dich 62479123
+CMGL: 29,"REC READ","128",,"16/07/18,20:33:43+28"
Ban da dang ky thong tin cho so thue bao 0924132141 thanh cong. Ma giao dich 62479139
+CMGL: 30,"REC READ","128",,"16/07/18,20:34:14+28"
Ban da dang ky thong tin cho so thue bao 0924132143 thanh cong. Ma giao dich 62479154
+CMGL: 31,"REC READ","128",,"16/07/18,20:34:45+28"
Ban da dang ky thong tin cho so thue bao 0924132144 thanh cong. Ma giao dich 62479171
+CMGL: 32,"REC READ","128",,"16/07/18,20:35:16+28"
Ban da dang ky thong tin cho so thue bao 0924132145 thanh cong. Ma giao dich 62479186
+CMGL: 33,"REC READ","128",,"16/07/18,20:35:47+28"
Ban da dang ky thong tin cho so thue bao 0924132146 thanh cong. Ma giao dich 62479203
+CMGL: 34,"REC READ","128",,"16/07/18,20:36:18+28"
Ban da dang ky thong tin cho so thue bao 0924132148 thanh cong. Ma giao dich 62479220
+CMGL: 35,"REC READ","128",,"16/07/18,20:36:50+28"
Ban da dang ky thong tin cho so thue bao 0924132153 thanh cong. Ma giao dich 62479234
+CMGL: 36,"REC READ","128",,"16/07/18,20:37:22+28"
Ban da dang ky thong tin cho so thue bao 0924132154 thanh cong. Ma giao dich 62479249
+CMGL: 37,"REC READ","128",,"16/07/18,20:37:54+28"
Ban da dang ky thong tin cho so thue bao 0924132155 thanh cong. Ma giao dich 62479265
+CMGL: 38,"REC READ","128",,"16/07/18,20:38:27+28"
Ban da dang ky thong tin cho so thue bao 0924132156 thanh cong. Ma giao dich 62479278
+CMGL: 39,"REC READ","128",,"16/07/18,20:38:59+28"
Ban da dang ky thong tin cho so thue bao 0924132157 thanh cong. Ma giao dich 62479296
+CMGL: 40,"REC READ","128",,"16/07/18,20:39:32+28"
Ban da dang ky thong tin cho so thue bao 0924132166 thanh cong. Ma giao dich 62479314