SMS Wiki - User contributions [en]

CSharp Sending SMS

2008-06-24T16:21:31Z

207.81.129.251:

The following sample code is running at [http://api.upsidewireless.com/samples/csharp/ SOAP Sampler]

A complete set of examples can be downloaded from: [http://api.upsidewireless.com/samples/csharp/SOAP%20Sampler.zip SOAP API Usage Sample Code]

=== Sending a Plain SMS ===

The basis of sending a message is to pass in the authentication token and signature along with the message parameters. A SoapException will be thrown if a serious error occurs and an SMS result object will be returned in less serious conditions.

Default.aspx.cs
<source lang="csharp">

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using com.upsidewireless.api.sms;
using System.Web.Services.Protocols;

public partial class SMS_Default : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{

}
protected void sendButton_Click(object sender, EventArgs e)
{
SMS sms = new SMS();

string token = "";
if (Session["token"] != null)
{
token = (string)Session["token"];
}

string signature = "";
if (Session["signature"] != null)
{
signature = (string)Session["signature"];
}
// If sending URLs special characters like "-", "+", "/" MUST be replaced with their safe equivalents (for example %2f).
string recipient = recipientTextBox.Text;

string message = messageTextBox.Text;

SmsEncoding encoding = SmsEncoding.Seven;
switch (encodingDropDownList.SelectedValue)
{
case "Seven":
encoding = SmsEncoding.Seven;
break;

case "Sixteen":
encoding = SmsEncoding.Sixteen;
break;
}
try
{
SMSSendResult result = sms.Send_Plain(token, signature, recipient, message, encoding);

if (result.isOk)
{
resultsMultiView.SetActiveView(resultSuccessView);
trackingIdLabel.Text = result.trackingId;
}
else
{
resultsMultiView.SetActiveView(resultsSMSErrorView);

blockedLabel.Text = result.BlockedReason;
invalidCountryCodeCheckBox.Checked = result.invalidCountryCode;
emptyMessageCheckBox.Checked = result.messageIsEmpty;
tooManySplitsCheckBox.Checked = result.tooManyMessages;
}
}
catch (SoapException error)
{
resultsMultiView.SetActiveView(resultsErrorView);
errorLabel.Text = error.Detail.InnerText;
}
}
}

</source>

Default.aspx
<source lang="asp">
<%@ Page Language="C#" MasterPageFile="~/MasterPage.master" AutoEventWireup="true"
CodeFile="Default.aspx.cs" Inherits="SMS_Default" Title="Send Plain SMS" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="Server">
<table>
<tr>
<td align="right">
<asp:Label ID="recipientLabel" runat="server" Text="Recipient:"></asp:Label></td>
<td>
<asp:TextBox ID="recipientTextBox" runat="server"></asp:TextBox></td>
</tr>
<tr>
<td valign="top">
<asp:Label ID="Label1" runat="server" Text="Message:"></asp:Label></td>
<td>
<asp:TextBox ID="messageTextBox" runat="server" Rows="6" TextMode="MultiLine"></asp:TextBox></td>
</tr>
<tr>
<td valign="top">
<asp:Label ID="Label2" runat="server" Text="Encoding:"></asp:Label></td>
<td>
<asp:DropDownList ID="encodingDropDownList" runat="server">
<asp:ListItem Value="Seven">Seven (GSM7)</asp:ListItem>
<asp:ListItem Value="Sixteen">Unicode</asp:ListItem>
</asp:DropDownList></td>
</tr>
<tr>
<td colspan="2" align="right">
<asp:Button ID="sendButton" runat="server" Text="Send" OnClick="sendButton_Click" /></td>
</tr>
</table>
<asp:MultiView ID="resultsMultiView" runat="server">
<asp:View ID="resultSuccessView" runat="server">
Operation Successful<br />
Message Tracking ID:<asp:Label ID="trackingIdLabel" runat="server" Text="Label"></asp:Label></asp:View>
<asp:View ID="resultsSMSErrorView" runat="server">
<div style="border: solid 1px #c00; padding: 20px; margin: 10px;">
The operation was not successful for the following reasons:<br />
<asp:Label ID="blockedLabel" runat="server" Text="Label" Font-Bold="True"></asp:Label><br />
<asp:CheckBox ID="invalidCountryCodeCheckBox" runat="server" Text="Invalid Country Code" /><br />
<asp:CheckBox ID="tooManySplitsCheckBox" runat="server" Text="Message too long" /><br />
<asp:CheckBox ID="emptyMessageCheckBox" runat="server" Text="Message is Empty" /></div>
</asp:View>
<asp:View ID="resultsErrorView" runat="server">
<div style="border: solid 1px #c00; padding: 20px; margin: 10px;">
<asp:Label ID="Label3" runat="server" Text="An error has occurred when calling this function:"></asp:Label>
<asp:Label ID="errorLabel" runat="server" Text="Label" Font-Bold="True"></asp:Label></div>
</asp:View>
</asp:MultiView><br />
</asp:Content>
</source>

----
[[APIs | back]]

CSharp Sending SMS

2008-06-24T16:14:21Z

207.81.129.251:

APIs

2008-06-16T18:40:39Z

207.81.129.251:

EnterpriseSMS API offers simple and efficient method for connecting corporate applications to the global SMS networks without having to deal with telecom contracts, routing and complex messaging protocols. Upside runs a highly reliable, redundant, telecommunications platform called SideWinderSMS which connects to all global SMS networks. The EnterpriseSMS API attaches to this proprietary platform and exposes minimal set of functions needed to deliver your messages to any mobile phone on the Planet. Similarly, mobile originated messages (such as replies) can be delivered to your application using the same method.

Your applications can take advantage of this common and well understood protocol to send and receive messages as per your business requirements.

== How to Start ==
To use the API you must have an account with Upside Wireless service and the account must be configured to allow API access. To get going

* Click [http://reseller.upsidewireless.com/RegEditNonLogon.do here] to create a new account
* Click on the Contact Us link in your account to request API upgrade
* Depending on your location and application other requirements may be needed - we will discuss them with you and advise

Once your account is setup you can proceed to add SMS capability to your application. We highly recommend that you first visit [http://api.upsidewireless.com/ EnterpriseSMS API home] and manually invoke the API. See an example [[Send Plain Example | here]]. This will help you quickly understand the requirements.

== How to Send SMS Messages using SOAP ==
* [[MT HTTP | Introduction]]
* [[Authentication | Authentication]]
* Examples
** [[PHP Sending SMS | Send SMS using PHP]]
** [[Java Sending SMS via SOAP | Send SMS using Java]]
** [[CSharp Sending SMS | Send SMS using C#]]
** [[Phyton Sending SMS | Send SMS using Phyton]]
* [[Tips SOAP | Tips for Sending SMS using SOAP]]

== How to Process Incoming SMS Messages ==
* [[MOIntro | Introduction]]
* [[VirtualSMS | VirtualSMS]]
* Examples
** [[PHP Receiving SMS | Receive SMS using PHP]]
** [[Java Receiving SMS | Receive SMS using Java]]
** [[CSharp Receiving SMS | Receive SMS using C#]]

== Other ==
* [[ Carrier_codes | Carrier Codes]] (USA and Canada)
* [[ Tariff | Tariffs]] for Premium SMS
* Global [http://reseller.upsidewireless.com/networkList.do Network Coverage List]

* [[User Management]]
* [[Settings]]

== How to Send SMS Messages using SMTP ==
''This section discusses initiating SMS sending requests using SMTP interface (email to SMS). We recommend that you first review the SOAP method as it offers richer functionality and better security/authentication.''

'''SMTP Interface'''
* [[MT SMTP | Introduction]]
** [[MT SMTP Auth]]
** [[MT Web Text]]
** [[MT IP Address]]
* Examples
** [[PHP Sending SMS via SMTP | PHP]]
** [[Java Sending SMS via SMTP | Java]]
** [[CSharp Sending SMS via SMTP | C#]]

'''Integration with Zimbra (SMTP Method)'''

While we strongly recommend that you integrate Zimbra using SOAP, we provide an example of how some of our customers integrated using the SMTP method. You can download it [http://api.upsidewireless.com/samples/zimbra/zimbra-zimlet-smtp.zip here].

----
[[Main Page | back]]

MT SMTP Auth

2007-05-11T21:05:40Z

207.81.129.251:

Sending SMS messages by SMTP Auth is fairly straightforward. Essentially, your application will send your username and password as authentication credentials when connecting to our SMTP server. Your application will submit your account credentials in plain text.

SMTP host name: '''smtp.upsidewireless.com'''

There is a second phase of authentication that occurs internally, verification of the senders email address. It must be in the form of '''username@smtp.upsidewireless.com''' where you would replace 'username' with your actual username (for example jsmith@smtp.upsidewireless.com).

If the sender email address is not exactly as specified above, you will receive the following error: "503 Incorrect Authentication for Specified Email Address"

The message format is as follows:

The "To:" field must be in the following format '''+NNNNNNNN@smtp.upsidewireless.com''' where the 'N's are replaced with the number you wish to send to. The number must be in [[international format]].

The "Subject:" field contains parameters for modifying the contents of the message to further compress the text while maintaining human readability. The parameters are comma separated and correlate the the following options: a = abbreviate certain words, p = delete prepositions, c = delete spaces. If you leave the subject empty, the message will be sent without any compression being applied. For more information please consult the [[SMS compression options]] page.

The "Body:" of your message can be any length, however your account settings and network will determine how long each SMS message ends up and how much of text is sent by splitting the message into the maximum number of parts you indicated in your account. In general the message will be split into pieces that have roughly 150-160 characters in them.

Once your application has authenticated with our server and sent the message, your message will be routed. If the route is successful, the credits for that message will be deducted from your account.

Please refer to the list below for examples of applications that send using SMTP Auth.

* Send SMS from your C# application
* Send SMS from your PHP application
* Send SMS from your Java application

MT SMTP Auth

2007-05-11T21:05:15Z

207.81.129.251:

Sending SMS messages by SMTP Auth is fairly straightforward. Essentially, your application will send your username and password as authentication credentials when connecting to our SMTP server. Your application will submit your account credentials in plain text.

SMTP host name: '''smtp.upsidewireless.com'''

There is a second phase of authentication that occurs internally, verification of the senders email address. It must be in the form of '''username@ipipi.com''' where you would replace 'username' with your actual username (for example jsmith@ipipi.com).

If the sender email address is not exactly as specified above, you will receive the following error: "503 Incorrect Authentication for Specified Email Address"

The message format is as follows:

The "To:" field must be in the following format '''+NNNNNNNN@smtp.upsidewireless.com''' where the 'N's are replaced with the number you wish to send to. The number must be in [[international format]].

The "Subject:" field contains parameters for modifying the contents of the message to further compress the text while maintaining human readability. The parameters are comma separated and correlate the the following options: a = abbreviate certain words, p = delete prepositions, c = delete spaces. If you leave the subject empty, the message will be sent without any compression being applied. For more information please consult the [[SMS compression options]] page.

The "Body:" of your message can be any length, however your account settings and network will determine how long each SMS message ends up and how much of text is sent by splitting the message into the maximum number of parts you indicated in your account. In general the message will be split into pieces that have roughly 150-160 characters in them.

Once your application has authenticated with our server and sent the message, your message will be routed. If the route is successful, the credits for that message will be deducted from your account.

Please refer to the list below for examples of applications that send using SMTP Auth.

* Send SMS from your C# application
* Send SMS from your PHP application
* Send SMS from your Java application

PHP Sending SMS

2007-05-11T19:57:49Z

207.81.129.251: New page: Please see the receiving example as it contains code for sending as well.

Please see the receiving example as it contains code for sending as well.

Settings

2007-05-11T19:57:16Z

207.81.129.251: New page: Coming Soon

Coming Soon

Main Page

2007-05-11T17:45:59Z

207.81.129.251: add global network coverage list

[[APIs]]

[http://reseller.upsidewireless.com/networkList.do Global Network Coverage List]

Examples And Concepts

2007-03-09T09:34:08Z

207.81.129.251:

=== SOAP API Usage ===
Every function of the SOAP API that requires authentication must pass in Authentication Parameters, to acquire a set of Authentication Parameters, please use the API found at: http://api.upsidewireless.com/soap/Authentication.asmx

=== Sending SMS ===

=== Receiving SMS ===
The method of receiving Inbound SMS messages is by way of HTTP POST. A few variables are passed in the body of the POST.
* name
* sender
* data
* carriercode << For shortcode accounts only
* inboundnumber << For Dedicated accounts only

In order to receive an SMS you must first register a URL in your account. Your account must be enabled to allow adding of URLs. Once your account has the registered URL set up, you will then need to forward all inbound SMS messages to that URL.

APIs

2007-03-09T09:32:03Z

207.81.129.251:

Upside Wireless HTTP APIs are located at [http://api.upsidewireless.com/ http://api.upsidewireless.com/]

* API Security
* Ease of Use
* Restrictions
* Intro to MO APIs (Mobile Originated - incoming from a mobile phone)
** MO POP3
** [[MO HTTP]]
** MO HTTPS
* Intro to MT APIs (Mobile Terminated - outgoing to a mobile phone)
** MT HTTP
** MT SMTP
*** [[MT SMTP Auth]]
*** MT Web Text
*** MT IP Address
* User Management
* Settings
* [[Examples And Concepts | Examples and General Concepts]]
** PHP
*** Sending SMS
*** Receiving SMS
** Java
*** Sending SMS
*** Receiving SMS
** [[CSharp_Overview | C# (Overview)]]
*** [[CSharp Sending SMS | Sending SMS]]
*** [[CSharp Receiving SMS | Receiving SMS]]

This is a patrolled change

Examples And Concepts

2007-03-09T09:26:08Z

207.81.129.251: New page: === Sending SMS === === Receiving SMS === The method of receiving Inbound SMS messages is by way of HTTP POST. A few variables are passed in the body of the POST. * name * sender * data *...

=== Sending SMS ===

=== Receiving SMS ===
The method of receiving Inbound SMS messages is by way of HTTP POST. A few variables are passed in the body of the POST.
* name
* sender
* data
* carriercode << For shortcode accounts only
* inboundnumber << For Dedicated accounts only

In order to receive an SMS you must first register a URL in your account. Your account must be enabled to allow adding of URLs. Once your account has the registered URL set up, you will then need to forward all inbound SMS messages to that URL.

APIs

2007-03-09T09:22:05Z

207.81.129.251:

* API Security
* Ease of Use
* Restrictions
* Intro to MO APIs (Mobile Originated - incoming from a mobile phone)
** MO POP3
** [[MO HTTP]]
** MO HTTPS
* Intro to MT APIs (Mobile Terminated - outgoing to a mobile phone)
** MT HTTP
** MT SMTP
*** [[MT SMTP Auth]]
*** MT Web Text
*** MT IP Address
* User Management
* Settings
* [[Examples And Concepts | Examples and General Concepts]]
** PHP
*** Sending SMS
*** Receiving SMS
** Java
*** Sending SMS
*** Receiving SMS
** [[CSharp_Overview | C# (Overview)]]
*** [[CSharp Sending SMS | Sending SMS]]
*** [[CSharp Receiving SMS | Receiving SMS]]

This is a patrolled change

CSharp Receiving SMS

2007-03-09T09:20:13Z

207.81.129.251:

This example is a .NET Generic Handler. It demonstrates the reception of an inbound (HTTP Forwarded) SMS.

To emulate an inbound SMS forwarded via HTTP POST, please see the code block following the HTTP Handler code.

Echo.ashx
<pre>
<%@ WebHandler Language="C#" Class="Echo" %>

using System;
using System.Web;
using System.Web.Services.Protocols;
using com.upsidewireless.api.sms;

public class IncomingMessage
{
public string username;
public string sender;
public string contents;
public SmsEncoding encoding;
public string carrierCode;
public string recipient;
}

public class OutgoingMessage
{
public string dedicatedNumber;
public string recipient;
public string carrierCode;
public string contents;
public SmsEncoding encoding;

public override string ToString()
{
return "[" + recipient + "]";
}
}

public class Echo : IHttpHandler
{

System.Diagnostics.EventLog evenLogger = new System.Diagnostics.EventLog("SMS Echo");

public Echo()
{
evenLogger.Source = "SMS Echo Test";
}

public void ProcessRequest(HttpContext context)
{
// This sample will respond to incoming HTTP POSTs and send back to the sender the same text that was sent
string requestType = context.Request.RequestType;
switch (requestType)
{
case "POST":

IncomingMessage incomingMessage = buildIncomingMessage(context);
OutgoingMessage outgoingMessage = processIncomingMessage(incomingMessage);
sendMessage(outgoingMessage);

context.Response.Write("Successfully sent echo back to: " + outgoingMessage);
break;

default:
context.Response.Write("This handler only accepts HTTP operations of type POST");
break;
}
}

private OutgoingMessage processIncomingMessage(IncomingMessage incomingMessage)
{
// TODO Build an OutgoingMessage object based on data contained within the incomingMessage.
OutgoingMessage result = new OutgoingMessage();

string message = "Time:" + DateTime.Now + "\n";
message += "Username:" + incomingMessage.username + "\n";
message += "From:" + incomingMessage.sender + "\n";
message += "To:" + incomingMessage.recipient + "\n";
message += "Encoding:" + incomingMessage.encoding.ToString() + "\n";
message += "Carrier Code:" + incomingMessage.carrierCode + "\n";
message += "Message:" + incomingMessage.contents;

result.recipient = incomingMessage.sender;
result.contents = message;
result.encoding = incomingMessage.encoding;
result.carrierCode = incomingMessage.carrierCode;
result.dedicatedNumber = incomingMessage.recipient;

return result;
}

private IncomingMessage buildIncomingMessage(HttpContext context)
{
IncomingMessage result = new IncomingMessage();

result.username = context.Request.Form["name"];
result.sender = context.Request.Form["sender"];
result.contents = context.Request.Form["data"];
string encodingString = context.Request.Form["encoding"];
result.carrierCode = context.Request.Form["carriercode"];
result.recipient = context.Request.Form["inboundnumber"];

SmsEncoding smsEncoding = SmsEncoding.Seven;

// we need to convert the encoding over to a strongly typed variable
switch (encodingString)
{
case "Sixteen":
smsEncoding = SmsEncoding.Sixteen;
break;
}

result.encoding = smsEncoding;

evenLogger.WriteEntry("Incoming Message Received", System.Diagnostics.EventLogEntryType.Information, 500, 0);

return result;
}

private void sendMessage(OutgoingMessage outgoingMessage)
{
// TODO: be sure to change the data stored within the resource before using this function!

string token = Resources.UpsideWirelessCredentialsResource.token;
string signature = Resources.UpsideWirelessCredentialsResource.signature;

SMS sms = new SMS();

try
{
SMSSendResult result = null;

if (String.IsNullOrEmpty(outgoingMessage.carrierCode) || String.IsNullOrEmpty(outgoingMessage.dedicatedNumber))
{
// standard routing
result = sms.Send_Plain(token, signature, outgoingMessage.recipient, outgoingMessage.contents, outgoingMessage.encoding);
}
else
{
// dedicated routing
result = sms.Send_Plain_Dedicated(token, signature, outgoingMessage.recipient, outgoingMessage.contents, outgoingMessage.encoding, outgoingMessage.carrierCode, outgoingMessage.dedicatedNumber, 0.0);
}

if (result.isOk)
{
evenLogger.WriteEntry("Sent SMS: " + outgoingMessage, System.Diagnostics.EventLogEntryType.Information, 0, 0);
}
else
{
evenLogger.WriteEntry("Unable to send SMS: " + outgoingMessage, System.Diagnostics.EventLogEntryType.Error, 1000, 0);
}
}
catch (SoapException e)
{
evenLogger.WriteEntry("Fatal: Unable to send SMS: " + outgoingMessage + " Exception: " + e.Detail.InnerText, System.Diagnostics.EventLogEntryType.Error, 5000, 0);
}
}

public bool IsReusable
{
get
{
return false;
}
}

}
</pre>

HTTP_POST_Emulator.htm
<pre>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Inbound SMS HTTP POST Forwarding Emulator</title>
</head>
<body>
<form method="post" action="http://api.upsidewireless.com/samples/csharp/Echo.ashx"
target="Echo">
<table align="center">
<tr>
<td align="right">
Username</td>
<td>
<input name="name" type="text" id="name" /></td>
</tr>
<tr>
<td align="right">
Sender</td>
<td>
<input name="sender" type="text" id="sender" value="+1" /></td>
</tr>
<tr>
<td align="right">
Message</td>
<td>
<input name="data" type="text" id="data" value="Hello" /></td>
</tr>
<tr>
<td align="right">
Carrier Code</td>
<td>
<input name="carriercode" type="text" id="carriercode" /></td>
</tr>
<tr>
<td align="right">
Inbound Number</td>
<td>
<input name="inboundnumber" type="text" id="inboundnumber" /></td>
</tr>
<tr>
<td colspan="2" align="right">
<input type="submit" name="Submit" value="Submit" /></td>
</tr>
</table>
</form>
</body>
</html>

</pre>

CSharp Overview

2007-03-09T09:17:07Z

207.81.129.251:

A complete set of examples can be downloaded from: [http://api.upsidewireless.com/samples/csharp/SOAP%20Sampler.zip SOAP API Usage Sample Code]

The Sample code is also running at the following location: [http://api.upsidewireless.com/samples/csharp/Default.aspx SOAP API Excerciser]

CSharp Overview

2007-03-09T09:14:53Z

207.81.129.251: New page: A complete set of examples can be downloaded from: [http://api.upsidewireless.com/samples/csharp/SOAP%20Sampler.zip SOAP API Usage Sample Code]

A complete set of examples can be downloaded from: [http://api.upsidewireless.com/samples/csharp/SOAP%20Sampler.zip SOAP API Usage Sample Code]

Main Page

2007-03-09T09:12:21Z

207.81.129.251:

[[APIs]]

Global Network Coverage List

CSharp Receiving SMS

2007-03-09T09:12:06Z

207.81.129.251: New page: This example is a .NET Generic Handler. It demonstrates the reception of an inbound (HTTP Forwarded) SMS. Echo.ashx <pre> <%@ WebHandler Language="C#" Class="Echo" %> using System; using...

This example is a .NET Generic Handler. It demonstrates the reception of an inbound (HTTP Forwarded) SMS.

Echo.ashx
<pre>
<%@ WebHandler Language="C#" Class="Echo" %>

using System;
using System.Web;
using System.Web.Services.Protocols;
using com.upsidewireless.api.sms;

public class IncomingMessage
{
public string username;
public string sender;
public string contents;
public SmsEncoding encoding;
public string carrierCode;
public string recipient;
}

public class OutgoingMessage
{
public string dedicatedNumber;
public string recipient;
public string carrierCode;
public string contents;
public SmsEncoding encoding;

public override string ToString()
{
return "[" + recipient + "]";
}
}

public class Echo : IHttpHandler
{

System.Diagnostics.EventLog evenLogger = new System.Diagnostics.EventLog("SMS Echo");

public Echo()
{
evenLogger.Source = "SMS Echo Test";
}

public void ProcessRequest(HttpContext context)
{
// This sample will respond to incoming HTTP POSTs and send back to the sender the same text that was sent
string requestType = context.Request.RequestType;
switch (requestType)
{
case "POST":

IncomingMessage incomingMessage = buildIncomingMessage(context);
OutgoingMessage outgoingMessage = processIncomingMessage(incomingMessage);
sendMessage(outgoingMessage);

context.Response.Write("Successfully sent echo back to: " + outgoingMessage);
break;

default:
context.Response.Write("This handler only accepts HTTP operations of type POST");
break;
}
}

private OutgoingMessage processIncomingMessage(IncomingMessage incomingMessage)
{
// TODO Build an OutgoingMessage object based on data contained within the incomingMessage.
OutgoingMessage result = new OutgoingMessage();

string message = "Time:" + DateTime.Now + "\n";
message += "Username:" + incomingMessage.username + "\n";
message += "From:" + incomingMessage.sender + "\n";
message += "To:" + incomingMessage.recipient + "\n";
message += "Encoding:" + incomingMessage.encoding.ToString() + "\n";
message += "Carrier Code:" + incomingMessage.carrierCode + "\n";
message += "Message:" + incomingMessage.contents;

result.recipient = incomingMessage.sender;
result.contents = message;
result.encoding = incomingMessage.encoding;
result.carrierCode = incomingMessage.carrierCode;
result.dedicatedNumber = incomingMessage.recipient;

return result;
}

private IncomingMessage buildIncomingMessage(HttpContext context)
{
IncomingMessage result = new IncomingMessage();

result.username = context.Request.Form["name"];
result.sender = context.Request.Form["sender"];
result.contents = context.Request.Form["data"];
string encodingString = context.Request.Form["encoding"];
result.carrierCode = context.Request.Form["carriercode"];
result.recipient = context.Request.Form["inboundnumber"];

SmsEncoding smsEncoding = SmsEncoding.Seven;

// we need to convert the encoding over to a strongly typed variable
switch (encodingString)
{
case "Sixteen":
smsEncoding = SmsEncoding.Sixteen;
break;
}

result.encoding = smsEncoding;

evenLogger.WriteEntry("Incoming Message Received", System.Diagnostics.EventLogEntryType.Information, 500, 0);

return result;
}

private void sendMessage(OutgoingMessage outgoingMessage)
{
// TODO: be sure to change the data stored within the resource before using this function!

string token = Resources.UpsideWirelessCredentialsResource.token;
string signature = Resources.UpsideWirelessCredentialsResource.signature;

SMS sms = new SMS();

try
{
SMSSendResult result = null;

if (String.IsNullOrEmpty(outgoingMessage.carrierCode) || String.IsNullOrEmpty(outgoingMessage.dedicatedNumber))
{
// standard routing
result = sms.Send_Plain(token, signature, outgoingMessage.recipient, outgoingMessage.contents, outgoingMessage.encoding);
}
else
{
// dedicated routing
result = sms.Send_Plain_Dedicated(token, signature, outgoingMessage.recipient, outgoingMessage.contents, outgoingMessage.encoding, outgoingMessage.carrierCode, outgoingMessage.dedicatedNumber, 0.0);
}

if (result.isOk)
{
evenLogger.WriteEntry("Sent SMS: " + outgoingMessage, System.Diagnostics.EventLogEntryType.Information, 0, 0);
}
else
{
evenLogger.WriteEntry("Unable to send SMS: " + outgoingMessage, System.Diagnostics.EventLogEntryType.Error, 1000, 0);
}
}
catch (SoapException e)
{
evenLogger.WriteEntry("Fatal: Unable to send SMS: " + outgoingMessage + " Exception: " + e.Detail.InnerText, System.Diagnostics.EventLogEntryType.Error, 5000, 0);
}
}

public bool IsReusable
{
get
{
return false;
}
}

}
</pre>

APIs

2007-03-09T09:09:57Z

207.81.129.251:

* API Security
* Ease of Use
* Restrictions
* Intro to MO APIs (Mobile Originated - incoming from a mobile phone)
** MO POP3
** [[MO HTTP]]
** MO HTTPS
* Intro to MT APIs (Mobile Terminated - outgoing to a mobile phone)
** MT HTTP
** MT SMTP
*** [[MT SMTP Auth]]
*** MT Web Text
*** MT IP Address
* User Management
* Settings
* Examples
** PHP
*** Sending SMS
*** Receiving SMS
** Java
*** Sending SMS
*** Receiving SMS
** [[CSharp_Overview | C# (Overview)]]
*** [[CSharp Sending SMS | Sending SMS]]
*** [[CSharp Receiving SMS | Receiving SMS]]

This is a patrolled change

Main Page

2007-03-01T21:12:26Z

207.81.129.251:

[[APIs]]
Global Network Coverage List

APIs

2007-03-01T21:11:20Z

207.81.129.251:

* API Security
* Ease of Use
* Restrictions
* Intro to MO APIs (Mobile Originated - incoming from a mobile phone)
** MO POP3
** [[MO HTTP]]
** MO HTTPS
* Intro to MT APIs (Mobile Terminated - outgoing to a mobile phone)
** MT HTTP
** MT SMTP
*** [[MT SMTP Auth]]
*** MT Web Text
*** MT IP Address
* User Management
* Settings
* Examples
** PHP
*** Sending SMS
*** Receiving SMS
** Java
*** Sending SMS
*** Receiving SMS
** C#
*** Sending SMS
*** Receiving SMS

This is a patrolled change

SMS compression options

2007-03-01T01:50:51Z

207.81.129.251: New page: '''Delete prepositions''' If you select this option email messages will be stripped of words such as "the", "a", and similar short words. '''Delete spaces''' If you select this option em...

'''Delete prepositions'''
If you select this option email messages will be stripped of words such as "the", "a", and similar short words.

'''Delete spaces'''
If you select this option email messages will be stripped of spaces. Every word will start with a capital letter.

'''Abbreviate'''
If you select this option long words will be replaced with abbreviations. For example: information=info, you=U, four=4, for=4 and so on. Click here to send us your favorite abbreviations to be included in our compression engine.

MT SMTP Auth

2007-03-01T01:49:41Z

207.81.129.251:

Sending SMS messages by SMTP Auth is fairly straightforward. Essentially, your application will send your username and password as authentication credentials when connecting to our SMTP server. Your application will submit your account credentials in plain text.

SMTP host name: '''ipipi.com'''

There is a second phase of authentication that occurs internally, verification of the senders email address. It must be in the form of '''username@ipipi.com''' where you would replace 'username' with your actual username (for example jsmith@ipipi.com).

If the sender email address is not exactly as specified above, you will receive the following error: "503 Incorrect Authentication for Specified Email Address"

The message format is as follows:

The "To:" field must be in the following format '''+NNNNNNNN@sms.ipipi.com''' where the 'N's are replaced with the number you wish to send to. The number must be in [[international format]].

The "Subject:" field contains parameters for modifying the contents of the message to further compress the text while maintaining human readability. The parameters are comma separated and correlate the the following options: a = abbreviate certain words, p = delete prepositions, c = delete spaces. If you leave the subject empty, the message will be sent without any compression being applied. For more information please consult the [[SMS compression options]] page.

The "Body:" of your message can be any length, however your account settings and network will determine how long each SMS message ends up and how much of text is sent by splitting the message into the maximum number of parts you indicated in your account. In general the message will be split into pieces that have roughly 150-160 characters in them.

Once your application has authenticated with our server and sent the message, your message will be routed. If the route is successful, the credits for that message will be deducted from your account.

Please refer to the list below for examples of applications that send using SMTP Auth.

* Send SMS from your C# application
* Send SMS from your PHP application
* Send SMS from your Java application

MT SMTP Auth

2007-03-01T01:49:05Z

207.81.129.251: New page: Sending SMS messages by SMTP Auth is fairly straightforward. Essentially, your application will send your username and password as authentication credentials when connecting to our SMTP se...

Sending SMS messages by SMTP Auth is fairly straightforward. Essentially, your application will send your username and password as authentication credentials when connecting to our SMTP server. Your application will submit your account credentials in plain text.

SMTP host name: '''ipipi.com'''

There is a second phase of authentication that occurs internally, verification of the senders email address. It must be in the form of '''username@ipipi.com''' where you would replace 'username' with your actual username (for example jsmith@ipipi.com).

If the sender email address is not exactly as specified above, you will receive the following error: "503 Incorrect Authentication for Specified Email Address"

The message format is as follows:

The "To:" field must be in the following format '''+NNNNNNNN@sms.ipipi.com''' where the 'N's are replaced with the number you wish to send to. The number must be in [[international format]].

The "Subject:" field contains parameters for modifying the contents of the message to further compress the text while maintaining human readability. The parameters are comma separated and correlate the the following options: a = abbreviate certain words, p = delete prepositions, c = delete spaces. If you leave the subject empty, the message will be sent without any compression being applied. For more information please consult the [[SMS compression options]] page.

The "Body:" of your message can be any length, however your account settings and network will determine how long each SMS message ends up and how much of text is sent by splitting the message into the maximum number of parts you indicated in your account. In general the message will be split into pieces that have roughly 150-160 characters in them.

Once your application has authenticated with our server and sent the message, your message will be routed. If the route is successful, the credits for that message will be deducted from your account.

Please refer to the list below for examples of applications that send using SMTP Auth.

Send SMS from your C# application
Send SMS from your PHP application
Send SMS from your Java application

APIs

2007-03-01T01:11:52Z

207.81.129.251: Added the smtp auth link

* API Security
* Ease of Use
* Restrictions
* MO APIs (Mobile Originated - incoming from a mobile phone)
** MO POP3
** MO HTTP
** MO HTTPS
* MT APIs (Mobile Terminated - outgoing to a mobile phone)
** MT HTTP
** MT SMTP
*** [[MT SMTP Auth]]
*** MT Web Text
*** MT IP Address
* User Management
* Settings
* Examples
** PHP
*** Sending SMS
*** Receiving SMS
** Java
*** Sending SMS
*** Receiving SMS
** C#
*** Sending SMS
*** Receiving SMS

This is a patrolled change