The primary API for sending and receiving SMS and MMS messages with NowSMS is HTTP-based. Because the API is HTTP based, applications that wish to send or receive messages via NowSMS do not have to run on the same physical server, they can interface with NowSMS over a network. This page contains links to additional information that describes the raw HTTP interface, as well as links to example scripts for PHP, Java and command-line interfacing with NowSMS. Note that in addition to these APIs, NowSMS also supports the SMPP protocol, allowing SMS clients to connect to NowSMS as an SMPP server for both sending and receiving SMS messages. For MMS clients, NowSMS also supports the MM1, EAIF, MM3 (SMTP), MM4 and MM7 protocols for both sending and receiving MMS messages. Note: The Command Line Interface is particularly useful because you can easily spawn a command line script to interface with NowSMS.
HTTP Protocol Information
PHP Scripts
Java Examples
Command Line Interface
Thursday, 29 July 2010
Now SMS/MMS API Information
For technical questions related to this post, please visit the NowSMS Discussion Forum.
Posted by
Brett Warthen
at
Thursday, July 29, 2010
0
comments
Labels: API
Tuesday, 18 May 2010
SMPP Receipt Message ID Tracking Over Multiple Connections
One of the standard capabilities of NowSMS is the automatic mapping of receipt message IDs when routing messages to an upstream SMSC connection.
For technical questions related to this post, please visit the NowSMS Discussion Forum.
Posted by
Brett Warthen
at
Tuesday, May 18, 2010
0
comments
Labels: delivery receipts, SMPP
Wednesday, 12 May 2010
NowSMS Update - Interim Release 2010.05.07
An interim update release of NowSMS is available for download at http://www.nowsms.com/download/nowsmsupdate.zip.
For technical questions related to this post, please visit the NowSMS Discussion Forum.
Posted by
Brett Warthen
at
Wednesday, May 12, 2010
1 comments
Labels: update
Wednesday, 28 April 2010
Operator MMSC Accounting - Detecting Roaming Subscribers
One important consideration when charging for MMS messages is whether or not the user is roaming. The NowSMS MMSC can provide this information to the MMS accounting callbacks, however the requisite information is not included in the MMS accounting callbacks by default.
For technical questions related to this post, please visit the NowSMS Discussion Forum.
Posted by
Brett Warthen
at
Wednesday, April 28, 2010
0
comments
Labels: accounting callbacks, operator MMSC, roaming
Thursday, 22 April 2010
NowSMS and SSL Certificates - 2048 Bit Key
It is believed that increased computing power will make the commonly used 1024-bit keys possible to break by 2011. There is a side effect in switching to the larger keys that some old web browsers don't support > 1024 bit keys. I can't find a good reference that tells me which versions of which browsers, but this is something to keep in mind.
We've rebuilt the NowSMS SSL library to generate 2048 bit keys when generating a new certificate signing request (CSR). An update can be downloaded at http://www.nowsms.com/download/smsssl.zip.
To install the update, stop the NowSMS services and exit NowSMS.
Unfortunately, the change to 2048 bit key requirements will cause problems for renewals for customers that already have an SSL certificate signed by a certificate authority (CA).
When your renewal time comes up, many CAs will not renew your certificate until you switch to a 2048 bit key.
However, if you generate a new server certificate request with NowSMS, this forces the existing certificate to be immediately invalidated, which may cause problems for existing clients during the certificate renewal process. (This problem is not specific to NowSMS ... many web server administrators are facing similar problems.)
If you face this renewal issue with NowSMS, follow this procedure:
- Locate and backup the following NowSMS files (in either Program Files\NowSMS for Windows XP/2003 or ProgramData\NowSMS for Windows Vista/7/2008):
SSL.CRT
SSL.CSR
SSL.CA
SSL.INI
SSL.KEY - On the "SSL/TLS" page of NowSMS, select the option to "Generate Server Certificate".
- You will be warned that doing this will invalidate your existing certificate. If you have backed up the files that I mentioned above, select "Yes" to continue.
- After the new certificate signing request has been generated, copy the new versions of SSL.CRT, SSL.CSR, SSL.INI and SSL.KEY to a different location for backup. (Note: There will not be an SSL.CA file as this file will not exist until you get your signed certificate back from the CA.)
- Put the old backup copies of these files, including SSL.CA, back in the appropriate NowSMS directory.
- Use the new SSL.CSR to request a signed certificate from your CA. When you get the signed certificate back from the CA, save it as SSL.CA.
- Copy the new version of these files, including SSL.CA to the appropriate NowSMS directory and restart the NowSMS services.
For technical questions related to this post, please visit the NowSMS Discussion Forum.
Posted by
Brett Warthen
at
Thursday, April 22, 2010
1 comments
Labels: SSL/TLS


