Search Results for 'SMS API'

[fleure fleure]

Hello, i use the non polling mode to receive message ( using TCP socket) but i must answer the mutiModem isms and send an ok response for it stop to send me all the old messages.
can you give me the format of response to send to the Multimodem isms.
thank you.

[Bryon Davis]

fleure,
It looks like you are using Polling mode for the Receive API. Make sure that “Non Polling Receive API Status” is disabled in the SMS API menu. If using TCP, also select TCP as the Protocol and click save.

In my testing I would receive a “System Busy” error when sending a TCP recvmsg request if “Non Polling Receive API Status” was enabled. Once I disabled this, then I was able to successfully send the TCP recvmsg request.

The format of the recvmsg request is:

GET /recvmsg?user=admin&passwd=admin[&count=][&from][&fdate=][&tdate=][&ftime=][&ttime=][&text=]

An example of a simple TCP recvmsg request would be (requests all unread received sms messages):

/recvmsg?user=admin&passwd=admin

Note: that the above request must end with a carriage return and linefeed.

Bryon

[fleure fleure]

Hello and thank you for your return;
here is the My Test :
I send an SMS via my phone to number configured on the modem and I run a telnet recvmsg command to see what I recovers but I get an error (System Busy)

[Bryon Davis]

Hi fleure,
Which Receive API mode do you want to use, Polling or Non-Polling?

With Non-Polling, the iSMS will automatically deliver incoming messages to a server when they are received.

With Polling, your software would need to send a recvmsg request to get the unread incoming sms messages.

For more information see the MultiModem iSMS Administrator’s Guide’s “Appendix A – Application Programming Interface (API)” section. See link below.

http://www.multitech.com/manuals/s000461f.pdf

Regards,
Bryon

[fleure fleure]

Trevor, can you please give me, how you test the receive api . I try to catch the receive sms with socket tcp but i have always 609 error.
thank you.

[fleure fleure]

hollo , can you help me please to configure multimodem isms for Receive API ( with TCP) and how i can test this please.
thank you.

[fleure fleure]

hello, i try to catch the message sending by MultiModem isms with a java programme and i use socket ( Receive API) . i have a response ( error 609) . can you help me please for the configuration of the modem.

[fleure fleure]

hello, i try to catch the message sending by MultiModem isms with a java programme and i use socket ( Receive API) . i have a response ( error 609) . can you help me please for the configuration of the modem.

[Bryon Davis]

Hi Tim,
The built in action triggers currently don’t allow you add a number to a group without semicolons. It would need to be done through a custom software using API commands to communicate with the iSMS.

Through the Receive API, the software could receive the “Add groupname” sms message. That software could then issue a sendmsg command to add that sender to the group indicated.

An example of a HTTP sendmesg to add a number to a group would be:
http://192.168.2.1:81/sendmsg?user=user1&passwd=user1&cat=3&enc=0&text=ADDG;groupname;sendername;sendernumber

You could also maintain groups in your software, which would give you more flexibility.

Regards,
Bryon

[fleure fleure]

i have a response now with :
String sms=”/sendmsg?user=admin&passwd=mdp&cat=1&enc=1&priority=3&modem=0&to=%22xxxxxx%22&text=HellowviaCode\r\n”;

thank you frends for your help.

[fleure fleure]

i have Err:602 (parse Error).

[Bryon Davis]

Try changing the following line to end with “\r\n” (carriage return and linefeed):

socket.setSoTimeout(0); String sms=”sendmsg?user=admin&passwd=mdp&cat=1&enc=1&priority=3&modem=0&to=%22xxxxxxxx%22&text=HellowviaCode\r\n”;

[fleure fleure]

i have the same error.
this is the java code ( i get the first line of response):

Socket socket=new Socket(ipAdress,2040);
socket.setSoTimeout(0);
String sms=”sendmsg?user=admin&passwd=mdp&cat=1&enc=1&priority=3&modem=0&to=%22xxxxxxxx%22&text=HellowviaCode\n”;
BufferedReader br = new BufferedReader(new InputStreamReader(s.getInputStream()));
BufferedWriter bw = new BufferedWriter(new OutputStreamWriter(s.getOutputStream()));
bw.write(sms);
bw.flush();
String line;
StringBuffer Response = new StringBuffer();
int lineNumber=0;
while ((line = br.readLine()) != null) {
System.out.println( “Received line iSMS :”+ line);
if(line.equals(“”)){
System.out.println( “end Response “);
break;
}
if(lineNumber==0){
Response.append(line);
break;
}
else Response.append(line).append(“\n”);
}
String responseBody = Response.toString();
System.out.println( “responseBody “+responseBody);
bw.close();
br.close();
s.close();

[Bryon Davis]

The 609 error indicates that there was “Timeout waiting for a TCP API request”.

The “/sendmsg?user=admin&passwd=mdp&cat=1&enc=1&priority=3&modem=0&to=%22xxxxxxxx%22&text=Hellow.” request must end with a carriage return and linefeed. Otherwise the iSMS will wait for more data and eventually timeout.

[fleure fleure]

thank you Bryon, i try this also but a have the same error ( Err: 609).

[Bryon Davis]

Hi fleure,
There is a Java API example at the link below:

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

Hopefully with this example and removing the %20 between / and sendmsg (see your other post) will resolve the issue.

Regards,
Bryon

[Bryon Davis]

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,
Bryon

[fleure fleure]

i can’t send sms with tcp api , cas you help me please. ( i use java code for sending sms with tcp socket).

[fleure fleure]

can you help me please,
I try to send a sms with tcp socket with the java code but I still have a return err: 609.
here is the message I send:

/%20sendmsg?user=admin&passwd=mdp&cat=1&enc=1&priority=3&modem=0&to=%22xxxxxxxx%22&text=Hellow.

with xxxxxxxx is msisdn number.

thank you.

[fleure fleure]

can you help me please, j’essaye d’envoyer un sms avec une socket tcp avec le code java mais j’ai toujours un retour err: 609. voici le message que j’envoie:
I try to send a sms with tcp socket with the java code but I still have a return err: 609.
here is the message I send:
/%20sendmsg?user=admin&passwd=mdp&cat=1&enc=1&priority=3&modem=0&to=%22xxxxxxxx%22&text=Hellow.

with xxxxxxxx is msisdn number.

thank you.

[fleure fleure]

I have a problem with sending SMS via TCP socket. I always get an error 609.
Thank you for helping me to solve this problem.

[fleure fleure]

j’ai un probléme d’envoie de sms via socket TCP. je recois toujours une erreur 609. Merci de m’aider à régler ce probléme.
I have a problem with sending SMS via TCP socket. I always get an error 609.
Thank you for helping me to solve this problem.

[Bryon Davis]

Hi 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,
Bryon

[Bryon Davis]

Hi 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:

SF100 v1.51.28
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF100/1.51.28/SF100-u-v1.51.28-25Nov2014.zip

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.zip

Regards,
Bryon

[Arnd –]

Hi all,
I have an issue if I use the HTTP API to send a message. The ‘+’ character of the phone number is lost.
FW: 1.51.28
International numbers are allowed.

Example API:
http://192.168.2.1:81/sendmsg?user=admin&passwd=admin&cat=1&to=”+49175xxxxxxx”&text=”Test-Text”

The message will not be send. In the logs I find the following:

SMS Failure Logs
Dec 11 16:05:08 modem: faillog: [FAILED TO] : 49175xxxxxxx : [MSG] : “Test-Text”

SMS Live Log
Dec 11 16:01:34 modem: livelog: [SEND] : AT+CMGS=49175xxxxxxx
Dec 11 16:01:35 modem: livelog: [RECV] :
>
Dec 11 16:01:35 modem: livelog: [SEND] : “Test-Text”
Dec 11 16:02:35 modem: livelog: [SEND] : AT+CMGS=49175xxxxxxx
Dec 11 16:02:36 modem: livelog: [RECV] :
>
Dec 11 16:02:36 modem: livelog: [SEND] : “Test-Text”
Dec 11 16:03:36 modem: livelog: [SEND] : AT+CMGS=49175xxxxxxx
Dec 11 16:03:37 modem: livelog: [RECV] :
>
Dec 11 16:03:37 modem: livelog: [SEND] : “Test-Text”
Dec 11 16:04:37 modem: livelog: [SEND] : AT+CMGS=49175xxxxxxx
Dec 11 16:04:38 modem: livelog: [RECV] :
>
Dec 11 16:04:38 modem: livelog: [SEND] : “Test-Text”
Dec 11 16:05:08 modem: livelog: [SEND] : AT+CFUN=0
Dec 11 16:05:09 modem: livelog: [SEND] : AT+CFUN=0
Dec 11 16:05:10 modem: livelog: [RECV] :
+CME ERROR: 515
OK
Dec 11 16:05:10 modem: livelog: [SEND] : Modem Reset successful
Dec 11 16:05:13 modem: livelog: [SEND] : ATE0
Dec 11 16:05:16 modem: livelog: [RECV] :
OK

If I send a message via the web interface the ‘+’ character is available and all looks OK:

SMS Live Log
Dec 11 16:06:08 modem: livelog: [SEND] : AT+CMGS=+49175xxxxxxx
Dec 11 16:06:09 modem: livelog: [RECV] :
>
Dec 11 16:06:09 modem: livelog: [SEND] : test
Dec 11 16:06:13 modem: livelog: [RECV] :
+CMGS: 106

Do I have to change some settings?….

Thanks,
Arnd

[Ashley Farrugia]

Hello Guys,

I am trying to send a message over the 160 SMS character threshold, and the GSM modem is receiving this as two separate messages. Is there anyway I can identify or concatenate the two received messages, so that I can combine the message at application level or they can be shown through the web-api as one message.

I have so far, upgraded the firmware to 1.51.28 and enabled PDU mode, but this does not seem to have made any difference. I would be grateful if you can give me some guidance on resolving this.

Thanks,

Ashley

[Sebastien Imbeault]

I try to access to incoming messsage from a previously message sent by a user account in iSMS Server. But it’s impossible to see any incomings message.

Only admin user can get access to incomings message.

Logically, i need to see incoming message from the same number than reply to my message from my normal user account. And if it’s not possible, then let’s the possibility to set an option to see incomings message or not without admin access….

I dont know what’s the best solution, but API do the same problem and i dont have any solution for moment…. can you help me !

• This topic was modified 10 years, 6 months ago by Sebastien Imbeault.

[Kirk Bennett]

It would be really really really cool to be able to pass back (send) an outgoing text message when the iSms posts a Non-Polling Receive to my application.

It would be really really cool if each modem had it’s own separate Sms API on the 400 and 800 units so I could post to different applications based on specific modem (phone number).

It would be really cool if the iSms supported Ssl so I could use over the internet without having to write my own “middleware” for security.

[Rob Watkins]

Hi Byron, thanks for quick reply! That firmware upgrade has fixed the non-polling receive API errors, but unfortunately I’m still getting truncation of the incoming SMSes.

I get: Line 1<CRLF>Line 2<CRLF>
When I should be getting I getting: Line 1<CRLF>Line 2<CRLF>Line 3

In SMS Settings I have:

ASCII 7-bit Configuration\Character Set: 3GPP 23.038

All other checkboxes are off. (I have also tried with the Extended ASCII 8-bit (ISO-8859-1) checked).

This is the recent entries in the live log:

May 15 16:40:04 modem: livelog: [RECV] : 
+CMT: "+447590354018",,"14/05/15,16:39:59+04",145,4,0,0,"+447785016005",145,34
7934,R10,
MAX:74.9dB LAeq 15MAY

May 15 16:40:04 modem: livelog: [RECV] : +CMT: "+447590354018",,"14/05/15,16:39:59+04",145,4,0,0,"+447785016005",145,34
7934,R10,
MAX:74.9dB LAeq 15MAY

May 15 16:40:04 modem: livelog: [SEND] : AT+CNMA
May 15 16:40:05 modem: livelog: [RECV] : 
OK

As you can see there is a spurious blank line after “15MAY” which should contain data – mobile phones receiving messages from the same source do show this line.

Very obscure! Hope you can help.

EDIT: Actually, on this blog platform you CAN’T see the second blank line after 15MAY but I assure you it’s there on the live log!

EDIT 2: I retrieved the log with curl, and the extra blank line is just a normal 0D0A sequence, at least in the web page.

Rob

• This reply was modified 10 years, 11 months ago by Rob Watkins.
• This reply was modified 10 years, 11 months ago by Rob Watkins.
• This reply was modified 10 years, 11 months ago by Rob Watkins.
• This reply was modified 10 years, 11 months ago by Rob Watkins.

[Bryon Davis]

Hi Rob,
To fix you non-polling receive API, please update to firmware version 1.51.25. See the links below.

SF100 v1.51.25
https://webfiles.multitech.com/engineering/unofficial-releases/iSMS%20(Formerly%20SMSFinder)/Firmware/SF100/1.51.25/SF100-u-v1.51.25-13Jan2014.zip

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.zip

When 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=line1line2line3

With 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;033

I tested the above sendmsg requests and both successfully sent messages with 3 lines with no gaps between them.

Regards,
Bryon