SMS Gateway Integration (Text Messaging) for website
$100-300 USD
Paid on delivery
We are building an ecommerce site in ASP.NET 2.0/C# which requires a connection to an SMS gateway provider.
We are looking for a programmer to integrate the SMS api from our wireless partner with our C# solution, which we are coding separately.?
## Deliverables
Project Type
--------------
SMS Gateway Integration (Text Messaging)
Timeframe
------------
3? weeks
Project Description
---------------------
We are building an ecommerce site in ASP.NET 2.0/C# which requires a connection to an SMS gateway provider.
We are looking for a programmer to integrate the SMS api from our wireless partner with our C# solution, which we are coding separately.?
Payment bonus
---------------
We are looking for a high quality product and will consider up to a 25% bonus for excellent work.
This bonus is completely at our discretion and will be paid if we are very happy with the work.
Guidelines to make us very happy:
- Finish work before the deadline.
- Have no obvious errors/bugs in the deliverables and high quality, safe, well documented code.
- Provide us with good communication - make sure we know what is going on!
Project details
---------------
Project is in ASP.NET 2.0/C#? (definitely no VB)
Project requestor (us) has 7 years of software experience at a major US software developer.
Our SMS wireless partner is Upside Wireless ([[url removed, login to view]][1]).
Developer docs:
<[url removed, login to view]>
We will most likely use the HTTP-POST api:
<[url removed, login to view]>
<[url removed, login to view]>
<[url removed, login to view]>
<[url removed, login to view]>
Please let us know what experience you have with SMS gateways, if any.
General Functionality
-----------------------
This project will create a bridge between our customized C# logic and Upside Wireless's api.
Logic to implement:
? Send SMS through the HTTP-POST API
? Receive SMS through the HTTP-POST API
? Populate/extract data from our customized classes (e.g. string m_strMessageToSend, m_SMSCarrier, etc)
? Ability to detect when messages are too long and send composite messages instead (e.g. first message = 160 chars, second message = 120 chars etc)
? Error handling for message failure
? Message receipt tracking/resending? (determine whether the sms reached the subscriber and resend it if necessary - this should be http-api based)
? Logging messages (we will provide the database api /DAL, you just write the C# logging function to call it)
Deliverables
----------------
Working application that implements the details listed in the General Functionality section of this bid
Full suite of NUnit tests to validate all send/receive SMS scenarios and all error handling. ([[url removed, login to view]][2])
Source code and data files for all of the above
A short design-time description of what will be built, BEFORE coding starts
Example of what we want
-------------------------------------------------
We should be able to perform something like the following (not necessarily exactly like this though):
SMSMessage smsMessage = new SMSMessage();
[url removed, login to view](strUserPhoneNo, userCarrier, strMessage);
[url removed, login to view]();
As an example for receiving a message, we would probably have an [url removed, login to view] page which would process parameters such as phonenumber, message contents, carrier, etc, and then call something like ProcessMessage() (we would write this last call ourselves).
Legal requirements
--------------------
Note: The full contract will replace <ourcompany> with our full company name once we agree to work together.
Project contents are defined as any material or knowledge including but not limited to: source code, data modeling, documents, data files, and communication between programmer(s) and <ourcompanyname>.
All work done on this project becomes the intellectual and legal property of <ourcompanyname> (a <ourstate> Limited Liability Company in the United States).
All work on this project is to be Copyright 2008 <ourcompanyname>.
Absolutely no project contents may be shared with any outside parties, unless at the specific request of <ourcompany>.
No project contents may be used on any other projects except for future projects for <ourcompany>.
Open source modules may be used in the software; however, ALL open source modules must be submitted for review and approval to <ourcompany> before use.
Open source development tools may be used if the use does not conflict with the tool's license.
Other Requirements
-------------------
Before coding, we require approval of the coder's proposed written design.
The code should be as bug-free as possible; at a minimum, all of the NUnit tests should pass without errors.
Technical requirements
-----------------------
There is no user interface to build in this project, nor any database implementation work.
We only need programmatic access to the module.
The source code should have adequate block-level documentation, e.g. explaining what a class/function does, or explaining non-obvious logic.
All external calls should be protected by try/catch/finally statements.
C# variable names should have the following notation:
Hungarian notation for basic types
e.g.
string strMyString;
int nMyInt;
bool fMyFlag;
member variables have m_ prefix
PascalNotation for class names
camelNotation for variable names
E.g.
MyClass myObject = new MyClass();
myObject.m_strMemberString = "assigning to member string";
Project ID: #3830567