Difference between revisions of "MOIntro"

From SMS Wiki
Jump to: navigation, search
(New page: In some instances having a virtual, dedicated SMS number is required to receive incoming (MO) messages. These cases are mostly important for business/corporate users who want to collect in...)
 
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
In some instances having a virtual, dedicated SMS number is required to receive incoming (MO) messages. These cases are mostly important for business/corporate users who want to collect information from their partners, employees or customers. The applications are limitless but some of them include:
+
With our service you can collect incoming SMS messages from your customers and have these messages forwarded directly to your application using a common '''HTTP-POST''' protocol. Here a several examples:  
−
* Non-premium SMS campaigns - The benefit is that you can be set up in about 3-5 business days at cost 5-10 times lower than having a dedicated premium SMS number
+
 
−
* Pooling (publish your dedicated number and collect opinion from your customers)
+
* Voting
−
* Marketing (giveaways, contests. In return you get consent from your customers to send them SMS advertising)
+
* VoIP Call origination
−
* Medical trials (clinical trials) - ask members of the panel to SMS their results to your dedicated SMS number. Collected information goes straight into your database - for ultimate efficiency.  
+
* Customer support
−
* Call-back long distance - Publish your virtual SMS number overseas. Your customers then send a number of the person in USA they want to talk to your virtual SMS number. The number of the sender and the number of the other party are then sent to your application and a voice call is established at a low international tariff between these two numbers.
+
* Sales reporting
−
Virtual SMS number can be associated with any Enterprise account. Once this is done, all messages received by your number will be forwarded into your Inbox. They can also be, simultaneously, forwarded to an application (HTTP), email account, another mobile phone or any combination of these devices.
+
* Instant Messaging
 +
* Telemetry and many more
 +
 
 +
To receive text messages, senders need a number to which they can send them. There are two options for you to receive incoming messages. You can use a  
 +
* Shared short or long code or
 +
* Dedicated [[VirtualSMS]] or dedicated short code
 +
 
 +
Please contact us to discuss which option would work the best in your situation.
 +
 
 +
Incoming SMS messages are first directed into your account (Inbox). From there, these messages can be collected by your application in two ways: Push and Pull
 +
 
 +
'''1. Push'''
 +
 
 +
Messages received in your account are forwarded to you using email or HTTP-POST. This is the preferred method as you get messages immediately after they have been received. For this process to work you need to expose an HTTP-POST listener on your web server and let us know its URL. The downside of this method is in case your URL changes (for example you have dynamic IP address) forwarding to your application will stop as we will unable to locate the URL that was provided - for as long as you do not update the URL with new IP address. Also, this method is sensitive to firewall settings (you will need to expose the web server which may be behind the the firewall - make sure the port is open).
 +
See below links for details on using HTTP-POST:
 +
 
 +
* [[MO HTTP]]
 +
* [[MO HTTPS]]
 +
 
 +
PLEASE NOTE - YOUR APPLICATION MUST IMPLEMENT HTTP-POST processing NOT HTTP-GET
 +
 
 +
''Step-By-Step Process to Get You Going''
 +
* We assume that you already created an account and have sending using API working
 +
* Create HTTP-POST listener in your server. Make sure it is on a publicly accessible web server (i.e. external services can access your application)
 +
* Login to your account and click on the Contact Us link. Paste the URL into the body of your message and request that we configure your account
 +
* Once you receive confirmation of this completion, you will be able to receive messages in your application
 +
 
 +
 
 +
'''2. Pull'''
 +
 
 +
Your application can also collect messages from your online account in periodic intervals. This is preferred if you do not have an application that can be exposed to the Internet or if your IP address changes often so that it is not practical to keep updating your IP/URL settings. The downside is that you need to poll for new messages every so often (no more than 2 minute intervals are allowed), which means that delivery to your application may be slightly delayed.
 +
 
 +
There are two methods for getting your messages.
 +
 
 +
Using SOAP method GetNewInboxMessages or using standard POP3 protocol.  
 +
 
 +
 
 +
*[[MO POP3 |POP3 ]]
 +
*[[MO_SOAP |SOAP]]
 +
 
 +
 
 +
----
 +
[[APIs | back]]

Latest revision as of 09:48, 5 October 2013

With our service you can collect incoming SMS messages from your customers and have these messages forwarded directly to your application using a common HTTP-POST protocol. Here a several examples:

  • Voting
  • VoIP Call origination
  • Customer support
  • Sales reporting
  • Instant Messaging
  • Telemetry and many more

To receive text messages, senders need a number to which they can send them. There are two options for you to receive incoming messages. You can use a

  • Shared short or long code or
  • Dedicated VirtualSMS or dedicated short code

Please contact us to discuss which option would work the best in your situation.

Incoming SMS messages are first directed into your account (Inbox). From there, these messages can be collected by your application in two ways: Push and Pull

1. Push

Messages received in your account are forwarded to you using email or HTTP-POST. This is the preferred method as you get messages immediately after they have been received. For this process to work you need to expose an HTTP-POST listener on your web server and let us know its URL. The downside of this method is in case your URL changes (for example you have dynamic IP address) forwarding to your application will stop as we will unable to locate the URL that was provided - for as long as you do not update the URL with new IP address. Also, this method is sensitive to firewall settings (you will need to expose the web server which may be behind the the firewall - make sure the port is open). See below links for details on using HTTP-POST:

PLEASE NOTE - YOUR APPLICATION MUST IMPLEMENT HTTP-POST processing NOT HTTP-GET

Step-By-Step Process to Get You Going

  • We assume that you already created an account and have sending using API working
  • Create HTTP-POST listener in your server. Make sure it is on a publicly accessible web server (i.e. external services can access your application)
  • Login to your account and click on the Contact Us link. Paste the URL into the body of your message and request that we configure your account
  • Once you receive confirmation of this completion, you will be able to receive messages in your application


2. Pull

Your application can also collect messages from your online account in periodic intervals. This is preferred if you do not have an application that can be exposed to the Internet or if your IP address changes often so that it is not practical to keep updating your IP/URL settings. The downside is that you need to poll for new messages every so often (no more than 2 minute intervals are allowed), which means that delivery to your application may be slightly delayed.

There are two methods for getting your messages.

Using SOAP method GetNewInboxMessages or using standard POP3 protocol.



back

Retrieved from "http://docs.upsidewireless.com/index.php?title=MOIntro&oldid=3311"