Bryon Davis
Forum Replies Created
-
AuthorPosts
-
Bryon DavisModerator
Hi fleure,
Everything looks ok, but there shouldn’t be a %20 (space) between the / and sendmsg?Try:
/sendmsg?user=admin&passwd=mdp&cat=1&enc=1&priority=3&modem=0&to=%22xxxxxxxx%22&text=Hellow.
Regards,
BryonBryon DavisModeratorHi David,
Unfortunately there isn’t a way to add a description to an Address Book using the ADD command (or API, which uses ADD command).For adding address book entries and groups, please refer to the “Triggers > Action Triggers” and “Sending an Action Trigger Message” sections in the Administrator’s Guide.
There is a helpful table of the default Action Trigger Commands on page 60 (Table of Trigger Codes and Trigger Actions). This list the possible Action Triggers and their syntax.
Below are examples on how to send these Action Triggers with the API (Note: the examples are using default enc=0 encoding):
Sending an Action Trigger Message Generic Syntax:
http://192.168.2.1%5B:portnumber%5D/sendmsg?user=user1&passwd=user1&cat=3&text=messageAdd Address Book entry Joe Smith 7635554174:
http://192.168.2.1:81/sendmsg?user=admin&passwd=admin&cat=3&text=ADD;joe%20smith;7635554174Add Address Book Entry and add it to a Group (will create group if doesn’t exist):
http://192.168.2.1:81/sendmsg?user=admin&passwd=admin&cat=3&text=ADDG;MyGroup;Jane%20Doe;7635557474Regards,
BryonBryon DavisModeratorHi Brant,
The FF440 will allow you to schedule outbound faxes through emails. These options are in the “Store & Forward (T.37)” menu, which is in Fax Configuration. The “Enable T.37” must be enabled to allow this.When sending the emails, you would set the “To” address to “fax=<fax number>@<FaxFinder IP address or hostname>” and attach the files which you want to send in the fax. Note the FaxFinder currently only supports PDF, TXT, TIFF, and postscript file attachments.
An example an “To” address with an IP address would be “fax=215555123@192.168.2.1”. Your email server should then relay this to the FaxFinder, which will then fax the attachments to the phone number 215555123. Note that some email servers won’t relay to IP addresses and the email server would need to reach the IP address.
An example of a hostname was shown in Kelvin’s post “fax=215555123@fax.mydomain.com”. In order for the FaxFinder to except an email to a hostname, this hostname must be entered in either the System Configuration->Network menu’s Hostname OR (not both) the “Fax Configuration->Store & Forward (T.37)” menu’s Additional Hosts.
I’m not sure why Kelvin had an issue with the hostname he was using, it looks like a valid “To” address for scheduling faxes on the FaxFinder. It depends on what was giving the invalid address exception.
If you require more information on this, please see the Administrator’s Guide at the link below:
http://www.multitech.com/manuals/s000522_r_4_3_1_4.pdf
Regards,
BryonBryon DavisModeratorHi John,
Sorry there isn’t a built in feature to track replies to sent messages. You may be able to achieve this with the API and a software that tracks what was sent with what was received.Regards,
BryonBryon DavisModeratorHi Ashley,
This is a known issue with receiving multipart messages. We are looking into a better way to handle this. With the current receive API there isn’t a way to tell if a received message was part of one long multipart message. There is a feature request to resolve this issue, but I don’t currently have an estimate on when this will be available.Regards,
BryonBryon DavisModeratorHi Aaron,
During normal operation it is unusual to see this error. It would likely indicate that an error occurred on the last receive API delivery that caused the process to error out before creating the file or after deleting the file.I would suggest upgrading to the latest firmware and see if that resolves the problem. There have been a few bug fixes in the Receive API over recent firmware.
Here are links to the latest firmware below. I’m also including links to SF100:
SF400 and SF800 v1.51.28
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF400_SF800/1.51.28/SF400-800-u-v1.51.28-25Nov2014.zipRegards,
BryonDecember 11, 2014 at 12:36 pm in reply to: If using the http API the international '+' character of phone number is lost. M #6131Bryon DavisModeratorHi Arnd,
The + sign should be URL encoded as %2B in HTTP API requests.
Try:
http://192.168.2.1:81/sendmsg?user=admin&passwd=admin&cat=1&to=“%2B49175xxxxxxx”&text=”Test-Text”Regards,
BryonBryon DavisModeratorHi Ashley,
If you enable PDU mode and “Concatenate Multipart Outbound Messages” in the SMS Settings menu, then long messages sent from the iSMS should be received as one long concatenated message.Regards,
BryonBryon DavisModeratorHi Binh,
For multiple attachments, you should have an <attachment> element for each attachment.An example of multiple external attachments:
<attachment>
<location>external</location>
<url>http://Example.com/fax/report1.pdf</url>
</attachment>
<attachment>
<location>external</location>
<url>http://Example.com/fax/report2.pdf</url>
</attachment>Regards,
BryonBryon DavisModeratorHi Rob,
The iSMS shellshock fixes are available on the FTP site.SF400 and SF800 v1.51.27:
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF400_SF800/1.51.27/SF400-800-u-v1.51.27-10Nov2014.zipInstructions for upgrading are included in the readme file.
Regard,
BryonBryon DavisModeratorHi Gobier,
The modem on the iSMS will allow voice calls, but there isn’t any support for sending or receiving audio on the iSMS modems, so this mode would be limited.Regards,
BryonBryon DavisModeratorHi Sebastien,
Sorry, only the admin has access to the inbound messages. This is because there is no way to determine which user an incoming was meant for with any certainty.Regards,
BryonBryon DavisModeratorHi Gerben,
To create a support case go to http://support.multitech.com and select register to create a Multi-Tech ID. Afterwards you should be able to create a new case. The support portal is free.Regards,
BryonBryon DavisModeratorHi Gerben,
I would first verify that everything on the IP side is working. Do pings respond consistently? Do other devices on the same switch work reliably?Does rebooting temporarily clear the condition?
If the IP network looks good, but the iSMS is still slow to respond, there may be a problem with low disk space. I would then suggest to create a case in the tech support portal so we can troubleshoot the problem in more depth.
Normally disk space is managed so you don’t need to manually delete any files, but some of the older firmware had bugs that would let unmanaged files build up over time. Or it could be other related problems.
Regards,
BryonBryon DavisModeratorKirk,
Thanks for the update. It will help other people seeing the same issue.Regards,
BryonBryon DavisModeratorHi Justin,
You may be seeing a bug we found in the firmware. This bug was also in the previous firmware. Sometimes the resources will get depleted over time if something is port scanning or multiple connections are made to the same port in the port range 5000-5007. This can be avoided by disabling “TCP Connection” for all modems in the Cellular Modem menu. Note this only disables a feature that allows direct access to the modems, the TCP API is not effected.Please try disabling the “TCP Connection” option for each modem in the Cellular Modem menu, this can be found in the Network section. If using a SF100 please make sure to save, click on “Save & Restart” and then click on “Save to Flash memory” so the setting change will persist through a reboot.
If it continues to have problems, we recommend creating a case in the support portal (support.multitech.com) so we can better troubleshoot the problem.
Regards,
BryonBryon DavisModeratorHi Rob,
I’m thinking that the device that is sending the sms messages is using a special character, or possibly a PDU header variable that the iSMS modem doesn’t handle properly. The +CMT in the logs shows what is coming out of the modem. In text mode, the modem will translate the received PDU message to text.You can try sending you original message with only alpha numeric characters (no colon brackets ect..) and then add them back in one at a time and see if a certain character breaks it.
You can also try setting the iSMS into PDU mode, in the SMS Settings. This may handle the message better than the modem’s built in PDU to Text mode convertor.
In my testing with cel phones, I also noticed that a single carriage return or single linefeed is handled better than having both.
I’ll work with the tech working on your support case to help resolve this.
Regards,
BryonBryon DavisModeratorHi Rob,
I was able successfully to receive a sms message with 3 lines on my SF800. The sms message was the same simple 3 line message as before, but was received.The +CMT message shows all 3 lines:
May 15 13:39:23 txrx1-modem: livelog: [RECV] : +CMT: “+17637727561″,,”14/05/15,13:39:19-20″,145,4,0,0,”+16363848863”,145,17
line1
line2
line3You +CMT message shows the sms as already changed coming out of the modem. So either it wasn’t successfully sent with 3 lines, the modem didn’t like something about the message and changed, or the cellular network changed it.
I’m wondering if the message was originally sent correctly, or if there is a special character that is causing problems. Can you try sending a simple 3 line message similar to mine and see if that goes through successfully. You can also try sending your original message to a cel phone and see if it displays correctly.
Regards,
BryonMay 15, 2014 at 10:17 am in reply to: Non Polling Receive – Multiple calls to page for same message #5786Bryon DavisModeratorPlease use v1.51.25 instead of v1.51.14, it has the non-polling fix as well as other fixes. See the readme file for more information on the changes.
SF400 and SF800 v1.51.25
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF400_SF800/1.51.25/SF400-800-u-v1.51.25-13Jan2014.zipBryon DavisModeratorHi Rob,
To fix you non-polling receive API, please update to firmware version 1.51.25. See the links below.SF400 and SF800 v1.51.25
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF400_SF800/1.51.25/SF400-800-u-v1.51.25-13Jan2014.zipWhen using carriage returns and linefeeds with 7 bit ASCII, we recommend using ASCII 7-bit Character set “3GPP 23.038”, which can be set in the “SMS Settings” menu. When sending through the API using 7-bit ASCII, you should URL encode the carriage returns to %0D and linefeeds to %0A.
Here is an example of a 7-bit ASCII HTTP sendmsg request with carriage returns:
http://192.168.2.1:81/sendmsg?user=admin&passwd=admin&cat=1&enc=0&to=”17637773333″&text=line1line2line3With Unicode you don’t need to URL encode the carriage returns and linefeeds, they should be just included as their Unicode values 0D and 0A.
Here is an example of a Unicode HTTP sendmsg request with carriage returns:
http://192.168.2.1:81/sendmsg?user=admin&passwd=admin&cat=1&enc=2&to=”17637773333″&text=6c;69;6e;65;31;0d;6c;69;6e;65;32;0d;6c;69;6e;65;033I tested the above sendmsg requests and both successfully sent messages with 3 lines with no gaps between them.
Regards,
BryonBryon DavisModeratorHi Gustavo,
We discovered a potential problem which you may be seeing. The modem ports will sometimes become “Disabled” over time because of multiple connections to the TCP ports. This can happen from port scans on the network.You can prevent this problem by disabling the “TCP Connection” option on the SF800 (or SF100) in the Cellular Modem menu for each modem, this can be found in the Network section.
Regards,
BryonBryon DavisModeratorHi Kirk,
I haven’t seen this issue before. I would suggest creating a case in the support portal. They will be able to work with you in more detail in troubleshooting this issue.The support portal is at http://support.multitech.com/ and support is free.
Regards,
BryonBryon DavisModeratorHi Kirk,
I haven’t seen this issue before. I would suggest creating a case in the support portal. They will be able to work with you in more detail in troubleshooting this issue.The support portal is at http://support.multitech.com/ and support is free.
Regards,
BryonBryon DavisModeratorHi Kirk,
There was a bug in the v1.50.7 firmware where sometimes the HTTP 200 OK wasn’t recognized and the response was flagged as timing out. This has been fixed in the newer firmware.The latest firmware is v1.51.25, which can be found at the links below:
Regards,
BryonBryon DavisModeratorHi Gustavo,
In the APi text use %0D for carriage return and %0A for Linefeed.You should also have the ASCII 7-Bit Character Set configured as “3GPP 23.038” in the SMS Settings menu. There is currently a bug that prevents carriage returns and linefeeds from working in the PCCP437 character set.
Regards,
BryonBryon DavisModeratorThe only way to determine what groups an address book entry is part of is to view the individual groups.
I don’t have 7-zip installed, but Winrar seems to open my export file without errors.
Bryon DavisModeratorCurrently the only way to view Users, Groups, or group members are through the web interface.
April 8, 2014 at 4:12 pm in reply to: Bug found? When first modem has no SIM, the receive API doesn´t work. #5736Bryon DavisModeratorHi Gustavo,
I tried duplicating this problem, but it was working for me. On my SF800 I only had a SIM inserted on modem 2 and sent it messages. I was able to successfully retrieve messages using polling mode or non-polling mode.In the SMS API menu, is the “Non-Polling Receive API Status” enabled?
Are the received messages showing up in the Inbox for modem 2?
Does the “Receive API Live Log” show anything being delivered or failures?
Regards,
BryonBryon DavisModeratorHi Gerben,
Are you trying to send an action trigger? The cat=3 is for action triggers.In my testing, I was having problems getting enc=2 (hexadecimal) to work. Do you require hexadecimal?
I was able to get enc=0 (ASCII) to work with action triggers. An example of adding an address book entry would be:
Note: I added the port 81 to the “http://10.0.0.1:81” section. This port should be the same as the “HTTP Port” in the SMS API menu.
Regards,
BryonBryon DavisModeratorHi Franklin,
There isn’t any special settings on the modem that would effect this. Does the non-working SIM and provider support 2G? The iSMS currently only supports 2G.Does the non-working SIM have a pin code? The iSMS currently doesn’t support SIMs with pin codes.
You can do some AT commands to see the status of the modem. To do this telnet to the iSMS on port 5000 ( the port may vary depending on the modem which is having troubles. Modem 1 is port 5000, Modem 8 is port 5007). The telnet should connect but no login or prompt will be shown. The first command will not echo the typed keys.
Enter the following AT commands:
1. AT (Verify that you receive an OK response)2. AT+CPIN?
This should respond with Ready. If not, then the SIM has Pin code enabled.3. AT+CREG?
a response of 0,0 usually means no SIM, 0,1=registered successfully, 0,2=no signal4. AT+CSQ
A response of +CSQ: 99,99 means no signal.5. AT+WMBS?
Make sure the response matches the proper band for their region. US should respond 4,0.Regards,
Bryon -
AuthorPosts