[Bryan Tran]

Hi JM,

1. -rw-r–r– 1 jm jm 78118912 2011-12-02 16:29 CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2

*Rename this file to: rootfs.jffs2 by typing:

mv CoreCDP-corecdp-full-image-eglibc-ipk-2.0.2-mtcdp.rootfs.jffs2 rootfs.jffs2.

2. -rw-r–r– 1 jm jm 1936596 2011-12-02 09:59 uImage-2.6.35-r4.corecdp5-mtcdp.bin

*Rename this file to: uImage.bin by typing:

mv Image-2.6.35-r4.corecdp5-mtcdp.bin uImage.bin

3. Then copy these two files to your SD card under the folder /flash-upgrade. Do the ls command on your SD card

to verify that:

a. uImage.bin is about roughly 1.85MB

b. rootfs.jffs2 is about roughly 74.5MB

Regards,

BT

[Bryan Tran]

Hi JM,

So you go into this folder on your development machine:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/corecdp-full-image-mtcdp.jffs2

and rename the file above to the rootfs.jffs2 ?

And this folder:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/uImage-mtcdp.bin

to uImage.bin and it is giving you a sym link ?

Can you go into the above folder do a command: ls -l and paste the output to this post so that I can see what they are.

Regards,

BT

[Bryan Tran]

Hi JM,

After you have downloaded the source code: you then cd into the folder: corecdp-2.0.2 and do as follow:

a. source env-oe.sh

b. bitbake corecdp-base-image or bitbake corecdp-full-image

The result file will be in:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/corecdp-full-image-mtcdp.jffs2

Note: Rename this file to: rootfs.jffs2

and:

/corecdp-2.0.2/build/tmp/deploy/eglibc/images/mtcdp/uImage-mtcdp.bin

Note: Rename this file to: uImage.bin

From the Development machine, you ssh into your CDP device with the SD card plugged in. Then do: cd /media/card.

a. Create a /flash-upgrade folder on your SD card.

b. Copy the rootfs.jffs2 and uImage.bin from your Development machine to /flash-upgrade folder on your SD card.

c. Do: cd /media/card/flash-upgrade and then ls to make sure the rootfs.jffs2, uImage.bin files are there.

d. Do: touch /var/volatile/do_flash_upgrade

e. Do: reboot.

When the CDP is rebooting back up, it will upgrade your CDP to the newest firmware CoreCDP-2.0.2.

Regards,

BT

[Bryan Tran]

Hi JM,

1. You should not have to worry about the TFTP server.

2. Here is how to flash upgrade your device with CoreCDP-2.0.2

Procedure for how to flash them to your CDP device:

a. Create a /flash-upgrade folder on your SD card.

b. Copy the rootfs.jffs2 and uImage.bin to /flash-upgrade folder.

c. Insert the SD card into the CDP device.

d. Do: cd /media/card/flash-upgrade and then ls to make sure the rootfs.jffs2, uImage.bin files are there.

e. Do: touch /var/volatile/do_flash_upgrade

f. Do: reboot.

Regards,

BT

[Bryan Tran]

Hi Aaron,

Try this sample code and see if it works for you: https://webfiles.multitech.com/engineering/sample-code/fax-finder/php/

Regards,

BT

[Bryan Tran]

Hi Mohammad,

1. I would try to send a couple sms from the cell phone to the iSMS device and look at both – sms live log and the inbox to verify that the sms messages that you have sent are coming in to the iSMS device.

2. Once you have confirming this, then you need to run a wire shark on the PC that had the script posted running. Then look at the wire shark capture and see if it gives you any clues…

Regards,

BT

[Bryan Tran]

Hi Noah,

Would you pls post your Email address here so that I can send you some of the documentations that regarding more additional steps that required to perform prior to use your SIM.

Regards,

BT

[Bryan Tran]

Noah,

I am currently working on your problem. I will let you know a solution as soon as I have found one.

Thanks,

BT

[Bryan Tran]

Hi Noah,

Can you take out the SIM and put it into your cell phone and see if you are able to send the sms message or not ?

Regards,

BT

[Bryan Tran]

Hi K,

Yes. It is in v1.47. http://www.multitech.com/en_US/SUPPORT/Families/MultiModemiSMS/firmware.aspx

Regards,

BT

[Bryan Tran]

Hi Noah,

Would you pls post the entire AT commands that you have sent to the modem that gives you the +CMS error: 500 ?

Regards,

BT

[Bryan Tran]

Hi Mohammad,

1. Can you check your SIM and see if it is inserted in ?

2. You can also telnet into the iSMS device on port 5000 and type in:

AT+CPIN? <–Check to see if the SIM is inserted correctly. If it is then you should get a +CPIN:Ready.

AT+CSQ <–Check the signal quality

AT+CREG? <–Check to see if it is registering to home or roam.

AT+CMGF=1 <–Turn on text mode.

AT+CMGS=”your_cell_number”[enter]

*After you hit Enter Key, you will get: ‘>’ prompt, then type in your sms message then to send it, you must do ctr+z.

For example,

>This is your message[ctr+z]

3. If it is still not working for you, I suggest take out the SIM and put it in your cell phone and try it out and verify it if you can send the sms message with that SIM. Or you can try to plug in a different SIM to the iSMS device and see if it helps.

Regards,

BT

[Bryan Tran]

Hi Mohammad,

Can you web into the device and go to Statistic&Logs -> live log and see what error you have got ? May be it will give you a clues.

Regards,

BT

[Bryan Tran]

Hi Mohammad,

1. It looks like the &password=admin param should be &passwd=admin instead.

2. Error 602 is a parse Error. http://www.multitech.com/en_US/DOCUMENTS/Families/MultiModemiSMS/manuals.aspx

3. Here is the link where you can take a look at our sample codes to get the message ID.

https://webfiles.multitech.com/engineering/sample-code/sms-finder/

Regards,

BT

[Bryan Tran]

Hi Noah,

Can you type: microcom /dev/ttyUSB3 to get into the microcom console. Type the following commands:

AT+CPIN? <–You should get response back with +CPIN: READY. Otherwise, check to see if SIM insert or not.

AT+CSQ[enter] <–Check signal.

AT+CREG?[enter] <–Check to see if register home or roam.

AT+CMGF=1[enter] <–Set to text mode.

AT+CMGS=”Your_SIM_number_here”[enter]

*After you hit Enter key, you will get a greater than sign, just type in your sms message and then hit ctr+z to send the sms message to your SIM. For example:

>This is your sms message [ctr+z]

Do: AT+CMGL=”ALL”[enter] <–List all of the messages received.

Regards,

BT

[Bryan Tran]

Hi Noah,

1. You can try to issue the command: microcom /dev/ttyUSB3 and then type:

AT[enter] and see if you are getting an OK back.

ATE1[enter] <–To turn echo on.

AT+CSQ[enter] <–Check signal.

AT+CREG?[enter] <–Check to see if register home or roam.

Ctrl + x [enter] <–Exit out the microcom.

2. Once you get the above commands to work, then you know that which /dev/ttyUSBx is talking to the wireless modem. You can then modify the .smsconfig and try it again.

3. If it is still not working for you, you can try:

sms –device /dev/ttyUSB3 send your_phone_number_here

or sms[enter] to list out a usage.

Regards,

BT

[Bryan Tran]

Hi Noah,

Would you pls give the model number and SN number of the product that you are currently having a problem with….

Regards,

BT

[Bryan Tran]

Hi John,

If you web into our iSMS device you will see there is an option called Utilities in the main menu. I am assuming this is what you are asking for.

If not pls, indicate what kind of sms-utils that you are looking for.

Regards,

BT

[Bryan Tran]

Hi Troy,

1. ffsend/ffstatus are unofficial commands and we do not support it.

2. However, we do support an official Web Service API with our newer product FFx30. Pls check out our user guide for the FFx30 starting on page 100 that talks about this Web Service API feature.

http://www.multitech.com/en_US/DOCUMENTS/Families/FaxFinder/manuals.aspx.

3. We also have several sample codes in many different programming languages that shows how to speak to our FFx30 product via Web Service API using HTTP request and response calls.

https://webfiles.multitech.com/engineering/sample-code/fax-finder/

Regards,

BT

[Bryan Tran]

Hi Brian,

1. You need to upgrade your isms device to 1.4x. Then go to SMS service -> SMS Settings -> Unicode Configuration -> Put a check mark on option ‘Unicode’ -> Click on Save button.

2. If you send a long message &text=”..your..message..here” in the sendmsg command. The isms device will break the message into 3 parts:

– (1of3) + ..your..message..here = 160 characters.

– (2of3) + ..your..message..here = 160 characters.

– (3of3) + ..your..message..here = 160 characters.

Total = 480 characters.

Note: The header (1of3) = 6 characters.

Your message = 154 characters.

Total for the first part will be = 160 characters.

Same for the 2 and 3rd part.

If you send message through web interface, it will only allowing you to have up to 462 characters only. This is because the header (1of3) took 6 bytes. And it has 3 headers. That 18 bytes. So the max is 462.

Regards,

BT

[Author]

Posts