
Multi-Tech MultiModem iSMS SMS Server models SF100 SF400 and SF800 README

This document should be viewed with line wrap enabled within your text viewer/editor.

Document Outline
----------------
   - Before You Start the Firmware Upgrade
	Download new firmware from Multi-Tech.
	Stop Using the iSMS Server while it is to be upgraded.
	Save to Flash and then Reboot the iSMS Server.
	Back-up the unit's Configuration.
	Additional Important Notes.
   - Upgrade The Firmware
	Step by Step procedure.
   - Revision History (listing new features, changes, fixes & known issues)
	Version V1.47: Dated 18 NOV 2010. (Maintenance Release - Online only)
	Version V1.46: Dated 05 OCT 2010. (Maintenance Release - Online only)
	Version V1.44: Dated 26 AUG 2010. (Maintenance Release - Online only)
	Version V1.31: Dated August 21, 2009. (Production Release)
	Version V1.20: Dated July 14, 2008. (Production Release)
	Version V1.10: Dated March 4, 2008. (Production Release)
	Version V1.00: Dated January 29, 2008.(Production Release)
   - General Administrative Items, How To, etc (as of 1.47)
	SMS Delivery
	Save to Flash verses Save.
	Configuration Back-up.
	Reset Button.
	Managing the System, Log Traces menu (log files).
	Inbox and Outbox.
	Common Trouble Shooting Modem AT Commands.
   - Technical Support
   - Copyrights and Trademarks


BEFORE YOU START THE FIRMWARE UPGRADE
-------------------------------------

- Download new firmware from Multi-Tech. The upgrade file downloaded from multitech.com is a compressed (.zip) binary file. Download the file to a computer that has full IP access to your iSMS server. Unzip/extract the file into a directory of your choice.

** To upgrade the SF100 to version 1.47, download the file "SF100-u-v1.47-18Nov2010.zip". When unzipped/extracted, two files are created, this README text file and the binary upgrade file. The upgrade file is SF100-u-v1.47-18Nov2010.bin and is 6,186,016 bytes in size.
*** SF100 Users Please Note: The naming convention of the binary upgrade file has changed since version 1.31. This change has added an extra step to the upgrade progress if you are upgrading from version 1.31 or older (see SF100 note in the below Upgrade Firmware procedure).

** To upgrade the SF400 and SF800 models to version 1.47, download the file SF400-800-u-v1.47-18Nov2010.zip". When unzipped/extracted, two files are created, this REAME text file and the binary upgrade file. The upgrade file is SF400-800-u-v1.47-18Nov2010.bin and is 9,267,232 bytes in size.

- Stop Using the iSMS Server while it is to be upgraded. The upgrade process requires the Send API functions within the iSMS server be disabled. This also implies you should stop your application from making HTTP or TCP send requests and/or msg inquiries to the iSMS Server. Regarding the reception of SMS messages from the cell network to the iSMS server (during the firmware upgrade process), there is a period of time in which SMS messages received by the iSMS's cellular modems (from the cellular network) will not be handled by the Receive API process within the iSMS. These message will not be retained by the iSMS server nor delivered to your host application. This window of vulnerability exists if the modem's Status is enabled and a SIM card is installed.

- Save to Flash and then Reboot the iSMS Server. Most parameters (enabling, disabling, changes) take effect immediately and do not require a reboot. However, user defined parameters will be lost upon reboot if they have not been saved to the flash memory. Go to the Save and Restart menu, select "Save" (save to flash memory) and select "Restart" and confirm the server comes up normally. The importance of performing the Save to Flash is touched on in many locations within the Administration Guide, including Chapter 3 iSMS Basics and Setup Wizard. 

- Back-up the unit's Configuration via the Utilities > Backup menu. The purpose of doing a configuration back-up before upgrading the unit's firmware version is for possible future convenience. If, after upgrading, you choose to go back to the previous version (i.e. A unit in production goes from 1.31 to 1.47 and then back to 1.31), importing the original/previous configuration back-up will be an easy way to re-program the unit.  Downgrading a unit's firmware version requires the unit be defaulted after the older/previous version is loaded back in. MultiModem iSMS configuration back-up files are only to be applied to units running the same version of firmware that created the configuration back-up file.

- Additional Important Notes. Review the "Revision History" section within this document before upgrading. The following important items (among others) are discussed in more detail; root element change to the xml data posted by our Receive API and a change to the SF100 upgrade procedure.

***************************************************************************************************************
CAUTION: It is recommended that the firmware upgrade be done locally, invoked from a workstation on the same subnet and LAN that the iSMS is on. It can be helpful to watch the unit's STATUS LED and Ethernet LEDs during the upgrade process. Aspects of the upgrade progress may take longer than expected (i.e. network IP performance, workstation events, items beyond the control of the Java scripts, etc) which can lead to incorrect conclusions. Front Panel LED behavior is described in more detail in the following firmware upgrade procedure.
***************************************************************************************************************

************************************************************************
WARNING: DO NOT turn off the Multimodem iSMS during the upgrade process.
************************************************************************


UPGRADE THE FIRMWARE
--------------------

The following upgrade procedure assumes your MultiModem iSMS SMS Server is in a normal working state, previously configured and installed for use on your network.

**********************************
Upgrade Sequence Overview:
 - Save to Flash
 - Restart the unit
 - Create a Backup
 - Disable Send API
 - Invoke Upgrade
 - Review Settings
 - Save to Flash
 - Restart
 - Test Functionality of unit.
**********************************

Step by Step Upgrade Instructions

1) Review the 'Before You Start' recommendations, 'Caution' and 'Warning' statements found above.

2) Log into the unit's WEB Management menu system with admin credentials.

3) Check/Set the Web Interface Inactivity Timeout to 600 seconds or higher. Go to the Administration menu, then Admin Access menu. Change the value and use the Save button in this menu.

4) Copy all system settings to flash memory and restart the System. Go to the Save and Restart menu. First perform a "Save" to Flash Memory, then "Restart" the unit. Proceed to the next step (5) after the unit comes back up (Status LED continually blinks on and off - I'm alive heart beat).

5) Log into the unit's WEB Management menu system with admin credentials.

6) Go to Utilities menu, if you have already performed a configuration back up proceed to step 7. To perform a configuration back-up click on the "Export" button. Save the tar file (a back-up of the iSMS configuration) to your computer.

7) After performing the config back-up, start the Firmware Upgrade. Click the Firmware Upgrade option on the left side menu bar (when in the Utilities menu). If you previously disabled Send API as recommended above proceed to step 8. If you did not disable the Send API functionality proceed to Step 7a.

7a) If you have either method of Send API (HTTP Send or TCP Send) enabled when you click on the Upgrade Firmware link - the WEB Management system will automatically bring you to the Send API setup screen. Please uncheck HTTP Send & or TCP Send APIs (uncheck and save per menu option). After disabling Send API, navigate to the Firmware Upgrade menu. Click on the Utilities menu bar link and then click on the Firmware Upgrade option on the left side menu bar.

8) Click the Browse button and select the firmware .bin file you previously download and extracted (as described in the "Before You Start..." section of this document). *** Special Note / Extra Step if your unit is the SF100 ***

**** If the unit to be upgraded is an SF100, proceed to step 8a ****
**** If the unit to be upgraded is an SF400 or an SF800, proceed to step 9 ****

8a) If your SF100 unit (that is to be upgraded to 1.44 or higher) is running version 1.41 beta 7 or older, the binary file (for example the 1.47 .bin file) "SF100-u-v1.47-18Nov2010.bin" needs to be re-named to "SMSFinder-u-v1.47-18Nov2010.bin". Rename it and then perform steps 7, 8 & 9. If the upgrade file is not named appropriately for the version of firmware currently running, the upgrade will not proceed and an error message will be displayed regarding the use of the correct file.

9) Click the Upgrade button.

10) BE PATIENT, the upgrade process takes a minimum of 5 minutes.

Your Web browser will display "Uploading firmware file....Please Wait" (the unit's Ethernet link LED will flash as it receives the file and the unit's "Status" LED on the front panel will be flashing on/off normally).

Next (after the file transfer is complete,) the unit is restarted, and your Web browser will display "Upgrading Firmware and Restarting ....Do Not Power Off....will return to the Login screen shortly".

During this phase the unit's Status LED will be off for a short while, and then on solid for a short while, and then shortly after it starts flashing on and off normally, your browser will return to the unit's login page.

Warning: The upgrade may take a little longer than expected - when this happens, your browser will declare a timeout when it tries to return to the WEB Management Login screen (this does not mean the upgrade has failed). If this happens, wait about another minute and click the re-try button displayed on the page. You may want to re-start your browser and make a new connection to the iSMS Server (enter the unit's IP address in the address bar of your browser and press enter). If the Status LED is not flashing on/off, the unit will not provide a WEB Management Login screen.

11) When the WEB Management Login screen is displayed by your browser, login to the unit and check to see that the new firmware version is reflected on the main screen (Home menu). The version number is also reflected in the System Information menu of Statistics and Logs.

12) Verify the configuration settings are what you expect them to be.

12a) If you previously disabled the Send API feature (before starting the firmware upgrade), now you will need to enable the Send API feature.

13) Perform a Save to Flash after the new version is running.

14) Restart the Unit and now test the functionality of unit (test the new version).


REVISION HISTORY
----------------

Firmware Version V1.47: (Dated 18 NOV 2010) (Maintenance Release - Online only)
-------------------------------------------------------------------------------

Bug Fixes:
----------

- Carriage Return in body of submittied text message causing 3 truncated messages to be sent. Now the <cr> is replaced with a line feed (<ln> aka hex 0A) and so the message is not truncated and is sent only once.
- Address Book Debug now disabled. The debug output caused intermittent display problems for Address Book related menus, including Statisitics & Logs System Information and Import Export Address Book menus.

Firmware Version V1.46: (Dated 05 OCT 2010) (Maintenance Release - Online only)
-------------------------------------------------------------------------------

Changes:
--------

- Wireless Modem Initialization Sequence: The initialization sequence performed in versions 1.44 and older is insufficient in some screnarios (certain 64k SIM cards, SIM card configuruation, etc). The key to the modem being functional is to wait for a “+WIND:#” (1, 4 sometimes 9) status before issuing other commands. The time needed to wait for a +WIND response will vary depending on the SIM and/or network. Waiting a minute is usually sufficient, but up to 3 or 4 minutes may be required. “515” errors are an indication that commands were issued before +WIND 1/4 was reached.

The new logic is:
--1)Send AT+CFUN=0 (graceful shutdown).
--2)Wait for “OK”.
--3A)If no “OK” received within 15 seconds, do a hardware reset of the modem and proceed to step 4.
--3B)If “OK” received within 15 seconds send AT+CFUN=1 (soft reset of modem) and proceed to step 4.
--4)Wait for +WIND response before proceeding with remaing modem commands.
--5)Proceed with remaining hard coded AT commands used to setup text mode, character set and etc.
--6)Proceed with any User defined Initialization Strings defined on the Cellular Modem setup menu.

Bug Fixes:
----------

- Spanned SMS for the SF100: The handling (sending) of consecutive spanned messages would lock up the port.

Known Issues with 1.46
----------------------

- Spanned SMS for the SF400 and SF800: The handling (sending) of consecutive spanned messages through the same port will lock up the port.

- A Carriage Return (hex 0d aka \r) in the body of the message submitted for sending - causes the iSMS server to truncate the message after the <cr> and send the truncated mesage a total of 3 times. This issue was introduced in version 1.44.

- Address Book Debug left on - randomly causes a display problem for menus associated to the Address Book. This issue was introduced in version 1.44.

Firmware Version V1.44: (Dated 26 AUG 2010) (Maintenance Release - Online only)
-------------------------------------------------------------------------------

- Caution, the Root Element Tags in the XML data posted via Receive API have changed. See Changes section.

New Features:
-------------

- Unicode Support: Allows SMS messages to be sent in almost any language. Feature requires the message to be submitted in UTF16 format.

- Receive API Polling: Allows host application to retrieve SMS messages from the iSMS Server on-demand via HTTP GET.

- Automatic Re-registration: Ability to re-register the modem's presence with the carrier at a user-selected interval.

- SMS Priority: SMS messages can be assigned HIGH, NORMAL or LOW priority.

- SIM Card Status: Indicates presence of SIM card in the modem and whether the port is enabled or not.

- Added HTTP POST to send API: Allows sending SMS messages using HTTP POST method (earlier versions only supported HTTP GET).

- Load Balancing, across units: New to the SF400 and SF800 models. When the amount of pending messages within the Master unit reaches a system threshold, Slave units are polled by the Master for availability, and if so available, pending messages are off loaded to the slave(s) for sending (a dynamic distribution protocol across all defined slaves). This feature provides a single interface to multiple units when your throughput requirement is greater than what one unit can normally provide.

- Spanned SMS: Feature applies to sending SMS messages. This is a product specific implementation. When a submitted message contains more characters than the normal number allowed by the selected encoding type, it will be truncated into multiple messages - with a 6 character identification string prefixed to the message body of each SMS message generated. The 6 character id string counts towards the total number of characters for each message. For example, a message with a total of 462 characters has been submitted for sending via the Send API process and the specified encoding type is ASCCI, the message will be broken into 3 separate SMS messages, the first message will be prefixed with "1of3" (6 characters) with the first 154 characters of the original 462 put into the first SMS (for a total of 160 characters), the second SMS will start with "2of3" followed by the next 154 characters of the original message, the 3rd SMS will be prefixed "3of3" along with the remaining 154 characters of the original 462 character message. The receiving side mobile end point will receive 3 separate SMS messages, each with 160 ASCCI characters (480 characters total).

Changes:
--------

- API menu changes: In Versions 1.31 and older the API menu had separate sub menus for Send API and Receive API and there was only one method of Receive API (Receive API is how SMS messages received from the cellular network are passed to your application). Now, Send API and Receive API are in one menu (SMS API), plus there is now two methods of Receive API. In Version 1.44 the original method of Receive API is now called "Non-Polling Receive API". This method is where the iSMS Server performs an HTTP POST (containing the SMS and related details) to a WEB Server or capable application. When Non-Polling Receive API is disabled (unchecked) the new Receive API method is automatically on and is referred to as "Receive API Polling". It was given this name because the received SMS is stored in the unit's receive queue until you query (poll) the unit via an HTTP GET. The response to the GET is the same structured XML data as what the Non-Polling method would POST. Non Polling Receive API is disabled by a factory default.

- Receive API XML data structure change. The root element of the xml data we POST to your WEB Server/receiving application, has changed (the XML data contains the text/SMS message and receive details). With version 1.31 and older, <MessageNotification> was the root node/element. Now with version 1.44, <Response> is the root element, with <MessageNotification> being a sub element. This allows for multiple <MessageNotification> elements/tags within one POST.

- Address Book Enhancements: Address book can now be sorted and searched by name and phone number.

- SMS Statistics Enhancement: During active traffic, the number of SMS messages sent/received per minute is  displayed.

- SF100 Users Please Note: The name format of the SF100 firmware upgrade file has changed from SMSFinder-u-ddMMMYYYY.bin to SF100-u-ddMMMYYYY.bin. This name change has added one extra step to the upgrade progress (the extra step is re-naming the file back to the old format).

** SF100 units running firmware version 1.41 beta 7 and older (i.e. 1.41 beta 1, released version 1.31, released version 1.20, etc) require any upgrade file that is to be applied to an SF100, to include the word "SMSFinder" in the file name. This requirement of the older versions is ambiguous when considering the SF400 and SF800 units. SF100 units running versions "1.42 beta 11" and newer will accept "SF100" or "SMSFinder" in the upgrade file name. If the upgrade file is not named appropriately (for the currently installed/running version of firmware) the upgrade will not proceed and an error message will be displayed regarding the use of the correct file.

Bug Fixes:
----------

- Fixed remote root exploit in address book search.
- Fixed address book search not handling non-alpha/numeric input properly.
- Statistics and Logs. Log files were not being rotated and backed up correctly. If EMAIL Notification was enabled, once a log file became full, a notification email would to be generated and sent each time new event data was to be written to the log file). All log files are now handled consistently, regarding the displayed order of events, max size, and number of back-ups.
- Statistics & Logs. Removed visual display problem (causing need to scroll down to view contents).
- Memory leak.
- Misc. Code Cleanup.

Known Issues with 1.44
----------------------

- SMS Statistics: The per port counter "Sent SMS" always dispalys zero.

- Receive API logs are not available through the WEB Management interface when the Receive API Method is "Non-Polling". Receive API events are however written to the main kernel log (the messages file).

- TCP Connection: The purpose of the per modem port "TCP Connection" feature, is to be a trouble shooting tool. This feature gives direct AT Command access to the serial interface of each cellular modem within your iSMS Server. The system administrator can manually issue AT commands to the cellular modem to prove network registration, manually send an SMS, and etc. This helps the system administrator isolate / eliminate a specific layer / portion of the SMS communication path, etc. Use of this feature should be at the direction of Multi-Tech Technical Support. It is recommended this feature be disabled on all ports except when needed as described. The implementation of this feature does not restrict duplicate connections made to the same TCP port number. This can lead to duplicate and or forgotten connections, resulting in undesired behavior, problems  (duplicate /bin/txrx/dev/ttyMU1x processes). This holds true for all previous versions of MultiModem iSMS and legacy SMSFinder firmware. When the trouble shooting is finished, the TCP connection should be closed and the unit should be restarted.

Firmware Version V1.31: (Dated August 21, 2009) (Production Release)
--------------------------------------------------------------------

New Features and changes:
-------------------------

- Changed Product name from “SMSFinder” to “MultiModem iSMS”. Replaced SMSFinder product image with MultiModem iSMS image in the Home page of WEB Management.
- Added Load Balancing to the SF100, maximum of four slaves, this includes broadcast trigger jobs and API jobs.  Load is 3.25 KB. Minimum load to start load balancing is 3.25 KB. Maximum load is 1000.
- Added import/export back-up of load balancing configuration.
- Added help section for load balancing.
- Maximum of 20 multiple concurrent send SMS sessions are supported.
- System displays user's outbox.
- System displays outbox for all users for the Admin user.
- Non-admin user will not see the inbox.
- Number of pending jobs is displayed.
- Added support for "DEL::number" action trigger.  DEL:name:number will delete only if both name and number  match.
- sqlite is used for Outbox.
- Changed <Message Notification> to <MessageNotification> in Receive API from client.
- Added option to load custom image to display when access WEB GUI.
- Added validation for secondary DNS in Wizard setup and Network setup.
- The following special characters are not allowed in group name: `~!@#$%^&*()|\<>
- Default HTTP Admin Access Port is 80 and HTTP Send API Port is 81.  They can be set to be the same port.
- SIM phone number can be left blank.
- Changed the default WEB inactivity timeout from 120 seconds to 600 seconds. This is done to allow Import CSV to happen successfully without getting interrupted with inactivity timeout.
- Improved Address Book CSV File validation. Pop-up window with error is displayed and CSV is not imported if the following conditions are not met:
1) Every entry should have at least 1 comma 
2) Name and phone number fields cannot be empty or only spaces.

Firmware Version V1.20: (Dated July 14, 2008) (Production Release - SF100 only)
-------------------------------------------------------------------------------

New Features and changes:
-------------------------

- Added HTTP / TCP API support
- Added Extended characters support and conversion based on GSM 7bit and 8bit
- Changed receive SMS message without using the SIM card memory
- Added allow networks to restrict access for WEB Management, telnet and API.
- Added remote syslog server
- Added display of signal strength in “Statistics & Logs >> System Information” 
- Added Multi-Tech knowledge base URL link on the home page.
- Added options to empty out messages that are in the inbox and outbox.

Firmware Version V1.10: (Dated March 4, 2008) (Production Release - SF100 only)
-------------------------------------------------------------------------------

New Features and Changes:
-------------------------

- Import and export back-up file will include address book and groups
- Allow telnet to port 5000 regardless of signal strength on the GSM modem
- when submit sending SMS to multiple phone numbers, it will check and not allow duplicate phone number. This  will prevent sending the same SMS message to the same number multiple times. 
- When adding new number to the address book, the description field can be blank.
- Action trigger will accept both : or ; character. This will help some phones that can not enter the ;  character.
- Disable +WIND message from modem by issuing AT+WIND=0 during modem initialization.
- Improved paging display options in WEB Management interface for address book

Bug Fixes:
----------

- Fixed memory leaks problem with 20,000 addresses
- Fixed memory leaks problem when perform broadcast trigger continuously for a long period of time
- Fixed some import address book issues when using certain CSV files.
- Fixed problem with editing Broadcast trigger with preconfigured SMS to preconfigured group
- Fixed authentic User list so it shows properly when in Add or Edit Broadcast trigger

Firmware Version V1.00: (Dated January 29, 2008) (Production Release - SF100 only)
----------------------------------------------------------------------------------

- Initial Product Release. SF100 SMSFinder.


- GENERAL ADMINISTRATIVE ITEMS, HOW TO, etc (as of 1.47)
--------------------------------------------------------

- SMS Delivery: With regards to the sending role (send SMS) performed by the MultiModem iSMS, regardless of how the SMS was submitted (Send API, Send SMS menu or triggered broadcast), the various declarations of sent, finished, completed, successful, etc, pertain to our attempt at transmitting the message to the cellular network (success or failure between the MultiModem iSMS and the cellular network). SMS Status Report from the cellular network and Delivery Status Requests are not supported. This holds true for all previous versions of MultiModem iSMS and legacy SMSFinder firmware versions.

- Save to Flash verses Save: There are two types of save functions within the WEB Management menu system.
** 1) Save to Flash - This is a system wide save function. Upon system start up, system parameters are taken from what is stored in the unit's Flash Memory. After you have configured the unit for your needs, perform the "Save to Flash" function before the unit is to be restarted/rebooted (single or multi port unit). As changes are made to the Address Book, the User accounts, and Triggers (all living databases) the changes to them take effect immediately, but will be lost upon a reboot if the Save to Flash is not performed before the reboot.
** 2) Save - This is a 'per feature' (per menu) save button. Most features/parameters take effect upon invoking this 'Save' within the feature setup menu (but not all, some require a system restart). Without performing the "Save to Flash" process, the configuration settings you defined (the feature you just enabled) will be lost upon a reboot.

- Configuration Back-Up: Before performing the back-up, confirm what firmware version your MultiModem iSMS Server is running. The configuration back-up file is to be applied to a unit running the same version of firmware that created the configuration back-up file. The configuration back-up process creates a tar file. The naming convention of this file includes model type, date and time stamp of when it was created, i.e. 'SF400-800-27Jul2010-15-45-26.tar' (created July 27th 2010 at 3:46 and 26 seconds PM). When performing the back-up, you are prompted by your browser to save the .tar file - here is a good place for you to tweak the name of the tar file to include the version number of the iSMS Server creating the backup (i.e. save as SF400-800-ver1.47-27Jul2010-15-45-26.tar).

- Reset Button: The function of the reset button (found on the back of the unit) is to load factory defaults into the unit (which includes the deleting of any existing Address Book, User and SMS history databases). To invoke the default, hold in the reset pin until the Status LED turns off. More specifically - normally the Status LED flashes like a fast heartbeat (on/off/on/off/on/off...), use a paperclip and hold in the reset button, the Status LED immediately stops flashing and stays on solid, continue holding in until it turns off (hold in 8 to 10 seconds). After releasing, the unit will restart. If you don't hold it in long enough, nothing happens to the unit (no default, no restart). The Reset button is tied to a GPIO pin of the processor (not the hard rest pin of the processor).
** You can also default the unit through the "Factory Defaults" menu found in the Administration menu.

- Managing the System, Log Traces menu (log files): The various log file menus within the Statistics and Logs menu provides an accurate picture of how the system is working. Each log has it's own perspective (some are per modem port and some are a system as awhole). All the menus are snap shots of the current content. Refreshing the screen will update the info within it (if there has been a change). The newest (most recent) events are written to the end (bottom) of the log. When an individual log has become full, a new one is created. The new one starts out with the tail end of the old log file (depending on the log, it's about the last 3 lines of the old log). The old/full log file will be emailed to the administrator (if the Email Notification option found in the Administration menu is enable). Also - as each log file fills up, it is renamed and kept in the /var/log/ directory of the iSMS Server (3 backed up archives of each log are kept in the /var/log/ folder).
**Please Note: If our feature "Remote Syslog" is enabled, Log data is no longer written locally (/var/log/ is empty) nor displayed through the Statistics & Log, Log Traces menu.

- Inbox and Outbox: The MultiModem iSMS maintains a separate sql database file for each direction. The outbound data base is displayed as a single Outbox (per unit). However, the inbound database is displayed as an Inbox per Modem (SF100 = 1 Inbox, SF400 = 4 Inboxes, SF800 = 8 Inboxes). The newest (most recent) entry is displayed at the top of the first page of each database (with the oldest entry being listed at the bottom of the last page). The messages in either database can not be re-sent or re-delivered. If the model of MultiModem iSMS is an SF100, the Outbox and Inbox entries will be lost upon reboot, unless a Save to Flash is performed before rebooting. However, the Outbox and Inbox entries for the SF400 and SF800 models do not require a Save to Flash be performed.
** Outbox: A chronological listing of all SMS messages sent out to the cellular network. For each record, the time and date sent, the contents of the message, who submitted it and which iSMS unit (locally or slave) sent it is displayed.
** Inbox: A chronological listing of received messages. For each record, the time and date received, the contents of the message and the number of the sender (who from) is displayed.

- Common Trouble Shooting Modem AT Commands: You can establish command line access to the serial interface of each cellular modem in your MultiModem iSMS. The "TCP Connection" option for that port needs to be enabled (Network Setup > Cellular Modem Setup menu). Use Telnet (or a terminal program that can open user defined TCP Port numbers) and open a socket/connection on 500x to the MultiModem iSMS. When you have finished testing the modem's cellular connection, be sure to disable the TCP Connection option, Save to Flash and the Reboot the unit (see known issues section above).

syntax = at<command><cr>

Use the identify command to prove what model of modem you are communicating with.

ati<cr>

response is wavecom multiband.

Use the +creg command to determine if the modem is registered on the cellular network.

at+creg?<cr> 

0,0 means not registered.
0,1 means registered on the home network and good.
0,2 means the modem is hunting but has not found anything yet.
0,3 means registration denied.
0,4 means unknown.
0,5 means its connected to a local repeater and is in “roaming” mode.

Use the +csq command to determine signal strength.

at+csq<cr>

response is +CSQ:xx,yy

Where xx is signal level = 0 through 31 or 99 (0 is detected but weakest, 31 is strongest, 99 is not detectable/unknown).

Where yy is channel bit error rate signal quality = 0 through 7 or 99 (0 is best, 99 is not  detectable/unknown).

Use the +cpin command to determine if a SIM card is detected by the modem and if a security PIN code is needed to use the account/SIM card.

at+cpin?<cr>

The possible responses are:
+CPIN: READY		(desired response, card detected and not waiting for a password/PIN code).
+CPIN: SIM		(PIN CHV1 is required).
+CPIN: SIM		(PUK PUK1 is required).
+CPIN: SIM		(PIN2 CHV2 is required).
+CPIN: SIM		(PUK2 PUK2 is required).
+CPIN: PH-SIM PIN	(SIM lock, phone-to-SIM, is required).
+CPIN: PH-NET PIN	(Network personalization is required).	
+CME:Error 10		(SIM card no detected).

Use the +cmgs command to manually send a text message to your cell phone (if the modem is registered and ready).

at+cmgs=phonenumber<cr> (modem responds with > prompt).

From the > prompt type in the text message and end it with a <ctrl-Z> (aka Hex 1A). <ctrl-Z> indicates to the modem this is the end of the message, please send now.

>This is a test message. Please reply back when you receive it.<ctrl-Z>

There is a pause while the modem communicates with and transmits to the network. When the modem has successfully transmitted the message to the cellular network, it responds with

+CMGS: ###

OK

Where ### is an incrementing number from 1 to 255 generated by the modem.



TECHNICAL SUPPORT
-----------------

- Multi-Tech's main Internet Address: http://www.multitech.com

- Multi-Tech's Support page: http://www.multitech.com/en_US/SUPPORT/

- Search the Knowledge Base: http://www.multitech.com/en_US/SUPPORT/Help/Resolutions/

- Contact Support:

If you are in the U.S. or Canada: 800-972-2439
Answered Monday through Friday 8:00 AM to 5:00 PM Central Time (Daylight savings observed when in effect).
Email support@multitech.com

If you are in the EMEA region: +(44) 118 959 7774. Email support@multitech.co.uk.

Rest of World: +763-717-5863
Answered Monday through Friday 8:00 AM to 5:00 PM Central Time (Daylight savings observed when in effect).
Email support@multitech.com

For faster service, we suggest you create a support case through our Support Portal. Please review Multi-Tech's Support page: http://www.multitech.com/en_US/SUPPORT/ to create a Portal account.


COPYRIGHTS AND TRADEMARKS
-------------------------
© 1995-2010 by Multi-Tech Systems, Inc. All rights reserved. Other trademarks or trade names used herein are properties of the respective owners.