Bryon Davis
Forum Replies Created
-
AuthorPosts
-
Bryon Davis
ModeratorHi Luis,
Does the Cisco router allow you to lock the Ethernet port going to the SF100 to 100Mb? This may solve the problem. Another work around may be to put a simple 100Mb switch between the Gigabit switch and the SF100.When you Telnet to port 2222, you start a Linux shell. So many of the common Linux commands will be available.
I’m not sure what commands will get the SF100 ports 80 and 81 working again. Both of these ports are handled by the boa process. You could try entering a “ps” command, finding the “/bin/boa” process, and then enter “kill <pid>” where the <pid> is the number in the far left column of the ps list. The SF100 will respawn a new boa process, and may then work.
We will look into this problem and do some testing.
Regards,
BryonModeratorHi Thomas,
If you are using ASCII 7 bit, the important setting for special characters is in the SMS Settings menu, change the ASCII 7 bit character set to “3GPP 23.038″ and click save. Using PDU mode may also help.What did the non-polling message show as the encoding type? If the encoding type is 8 bit Extended ASCII, there may be a difference in the character set used.
If you send from the iSMS back to itself, does it look correct? If you’re sending 7 bit it should ensure that you receive 7 bit, which should work with the “3GPP 23.038″ character set setting.
Regards,
BryonModeratorHi Steven,
The log files, inbox, and outbox are managed so they won’t grow too large and run out of space. You shouldn’t need to do any disk management manually.Regards,
BryonModeratorIn my testing, I do not receive a message back when sending to my land line.
ModeratorHi Steven,
I think the results will vary depending on the recipient’s carrier, and may not be a dependable indicator that a recipient has sms capabilities. Although receiving that response message would definitely indicate that recipient does not have sms capabilities.Regards,
BryonModeratorHi Steven,
The Invalid Number message must have been generated by your carrier, or the carrier of the recipient number. Which number are you referring to? The from number 112-161-1611 is the number from the automated system that sent the error response. I’m not sure where the 1972xxxxxxx came from, is this the number you sent it to? it could possibly the sms center number assigned to the SIM.Regards,
BryonModeratorHi Laurent,
Unfortunately we are treating incoming data as text, so any value that isn’t a displayable ASCII character is set to 20. The only way to get raw binary data from the modem is to control the modem directly by doing telnet to the iSMS on port 5000 (for modem 1) to 5007 (for modem 8), but then you would have to manage all modem functions yourself. The iSMS won’t send or receive anything from the modem while a telnet to a modem is connected.Regards,
BryonModeratorHi Gustavo,
We are currently looking into adding the feature of tracking whether the message was delivered, but we currently don’t have an estimate on when this will be added.If the iSMS loses power while sending messages, the iSMS will have the pending messages saved and will continue sending those messages, but any messages that were in the process of being sent by the modem will get lost.
Currently there isn’t a way to pause sending. You can cancel messages in the queue, but not pause sending them.
Regards,
BryonModeratorHi Erwin,
Another option would be to your server/program track it’s own groups. When people send a message and it is delivered to your server/program, it can add the person to it’s own local group list and maintain it as needed. When sending, the program would pull the phone numbers from it’s own local group and submit a message with that phone number. This way you can create your own custom features to fit your needs.Regards,
BryonModeratorHi Steven,
When sending the sendmsg request, HTTP or TCP, the text’s carriage returns should be encoded as %0D and the the linefeeds encoded as “%0A”.Regards,
BryonModeratorHi Steven,
In my testing the API still sends a maximum of 1232 7-bit ASCII characters in PDU. It allows me to submit a longer messages, but the message will be truncated to 1232 characters.Regards,
BryonModeratorHi Laurent,
Are you using 7 bit ASCII?
By default the iSMS using PCCP437 7-bit character set, which doesn’t support many special characters. If an unsupported character is in a message, the iSMS replaces that character with a space (20).
It may help if you update to the v1.51.14 firmware which has support for 3GPP 23.038 character set. This character set supports many more special characters. This firmware also has support for PDU mode which may also help with sending special characters.
The settings for the Character Set and PDU mode are in the SMS Settings menu.
You can find the v1.51.14 firmware on our FTP site at:
SF100:
SF400 and SF800:
Regards,
Bryon
ModeratorHi Steven,
We currently don’t have a release date planned for v1.51.x. We will be adding release notes soon to the v1.51.14 ftp folder to show the changes.
The 1.50.7 and 1.51.14 do support multi-part messages. When sending a request for a long message, just include the entire message string for the text, the iSMS will automatically split up the message and send them.
Regards,
Bryon
ModeratorHi,
Sending a multi-part message with the API is the same as sending a regular message, just with a longer text string. The iSMS will automatically split up long messages into multi-parts and send them.
See the User Guide’s Appendix A (page 76) for more information on the API.
User Guide:
http://www.multitech.com/en_US/DOCUMENTS/Collateral/manuals/S000461E.pdf
Regards,
Bryon
ModeratorHi Steven,
The C# examples for the iSMS API are at the link below:
https://webfiles.multitech.com/engineering/sample-code/sms-finder/c-sharp/
Regards,
Bryon
May 31, 2013 at 5:40 pm in reply to: Non Polling Receive – Multiple calls to page for same message #4452ModeratorHi Todd,
Please try the v1.51.14 firmware. There is a known issue in 1.50.7 where successful Non-polling HTTP deliveries are sometimes detected as failures, so they get resent.
SF100 v1.51.14:
SF400 and SF800 v1.51.14:
Regards,
Bryon
ModeratorHi Thomas,
The new v1.51.14 firmware supports the 3GPP 23.038 character set, which is a 7 bit characters set. All of those character are supported in this set. Below are the link to the v1.51.14 firmware.
To get support for the special characters change the following settings after you upgrade:
1. In SMS Settings menu, check “Enable PDU Mode” and click save.
2. In SMS Settings menu, change the ASCII 7 bit character set to “3GPP 23.038” and click save.
3. In SMS Settings menu, make sure Unicode and Extended ASCII are disabled, unless you plan to specify ASCII 7 bit encoding during the send.
SF100:
SF400-800:
Regards,
Bryon
ModeratorHi Fabian,
The iSMS will often send a AT+CSMP command to set the modem in the correct mode before a send, which would overwrite the initialization string. We currently don’t support flash SMS.
Regards,
Bryon
ModeratorHi Brian,
When connected through telnet port 5000, you are directly connected to the modem and can issue your own AT commands and receive the +CMT messages and other modem responses.
While the telnet session is connected, the iSMS manager does nothing with the modem. It doesn’t handle the incoming or send any outgoing messages to the modem.
If you disable “Modem Status” in the Network Setup->Cellular Modem menu, the iSMS manager won’t do anything with the modem even if telnet gets disconnected. This option isn’t available in the current SF100 firmware, but a special firmware can be offered to add this option.
If you want to use telnet to ports 5000-5007 to control the modem directly with your program, we recommend disabling “Modem Status” so the iSMS manage doesn’t process incoming messages if the telnet session gets disconnected. We also recommend setting up the modem to require manual incoming message ACKs, or store the incoming messages, so no messages are lost in the event of a telnet disconnect.
This type of access would give you complete control over the modem, and wouldn’t require you to deal with the source code.
We are still discussing what is GPL licensed in the code and how to make it available. If you still require the GPL section of the source code, please make a portal case on our support site (support.multitech.com) and we will be able to work more directly with you there.
Regards,
Bryon
ModeratorHi Brian,
We don’t really support modifying the firmware on the iSMS. You may be interested in using the MultiConnect OCG (Cellular Development Platform). This product is designed to allow the developer to make their own firmware. It has many tools to help the developer and we provide help and support for these type of projects. It comes with a single modem, but you could also support other multiple modem through the USB port.
Another option may be to control the iSMS directly through a telnet connection. By connecting to port 5000 (modem 1) to 5007 (modem 8), you take direct control over the modem and bypass the iSMS firmware.
Regards,
Bryon
ModeratorHi Dan,
Kirk is correct. The ModemNumber field will only contain the phone number if the SIM Number is configured in the Network Setup->Cellular Modem menus. There is a tab at the top to select each modem and set them individually.
Regards,
Bryon
ModeratorWith a 255.255.255.0 network mask, the 192.168.0.88 IP address and 192.168.2.1 IP address are on different networks, and the can’t talk to each other without some sort of router.
You could change the network mask on the iSMS and computer 2 to be 255.255.0.0, and they should then be able to see each other. Depending on you network set up, and reason for having two networks 192.168.2.x and 192.168.0.x, this could possible cause other problems on computer 2 though.
The other alternative is to change computer 2 to be on 192.168.2.x network.
ModeratorHi Brad,
The Inbox and Outbox are limited in size, around 8 gig each, so the number of messages varies depending on how large they are. If either gets too large, the older entries are automatically deleted.
Regards,
Bryon
ModeratorHi Marco,
I recommend that you create a case in our tech support portal.
Regards,
Bryon
ModeratorHi Dan,
Sorry for the delay. There isn’t a way to query the iSMS to find out this information. This currently must be statically defined or retrieved from received messages.
Regards,
Bryon
ModeratorHi Harry,
If the Statistics&Logs->SMS Statistics page never shows your SIM becoming Enabled, then first try powering off the iSMS for a minute and try powering it on again. Also make sure you have a SIM and service that supports 2G. Currently the iSMS only supports 2G.
If the problem still persists, telnet to the iSMS on the modem port (5000-5007 depending on which modem) and enter the following AT commands:
AT+CPIN? – Should respond +CPIN: READY
AT+CREG? – a response of 0,0 usually means no SIM, 0,1=registered successfully, 0,2=no signal
AT+CSQ – A response of +CSQ: 99,99 means no signal.
AT+WMBS? – Make sure the response matches the proper band for their region. US should respond 4,0.
If all of the AT commands respond correctly, check if you can send a sms message through the telnet using AT commands.
Sometimes the SIM fills up with messages and prevents the modem from becoming enabled. While connected the the modem via telnet, enter the command AT+CMGD=1,4
This should clear any stored messages on the SIM.
If it still fails, then we recommend creating a case with our tech support.
Regards,
Bryon
ModeratorHi Arron,
You shouldn’t need to add any additional initialization strings for normal operation. The iSMS has a set of initialization strings it performs on its own to prepare it for normal operation. The option to add additional initialization strings is only used in special circumstances.
Regards,
Bryon
January 10, 2013 at 4:24 pm in reply to: Non Polling Receive – Multiple calls to page for same message #4449ModeratorHi Todd,
Glad you were able to fix the problem. If the Non-polling Receive API message wasn’t sent successfully then the iSMS will resend it repeatedly. Clearing the Inbox should’ve cleared this though.
Regards,
Bryon
ModeratorHi Kirk,
I haven’t heard of a bug like this. Most likely the year was a problem from where you were getting the date/time information, whether it was from a SNTP or from the time stamp sms message.
Regards,
Bryon
ModeratorHi Hien,
The MultiModem® iSMS User Guide for Administrators for Models SF100/400/800 should describe what features are available for this.
You can find the manual at the link below:
http://www.multitech.com/en_US/DOCUMENTS/Collateral/manuals/S000461E.pdf
Regards,
Bryon
-
AuthorPosts