mirror of
https://github.com/cwinfo/envayasms.git
synced 2024-12-04 20:45:32 +00:00
add community page, merge comparison into faq
This commit is contained in:
Jesse Young
parent
d457c857a2
commit
62c9965238
17
.phrozn/entries/community/index.twig
Executable file
17
.phrozn/entries/community/index.twig
Executable file
@ -0,0 +1,17 @@
|
||||
id: community
|
||||
title: Community
|
||||
---
|
||||
|
||||
<h4>Contribute to EnvayaSMS</h4>
|
||||
|
||||
<p>
|
||||
To contribute to EnvayaSMS as a developer, just <a href='http://github.com/youngj/EnvayaSMS'>fork the project on github</a>,
|
||||
work on your copy and send pull requests.
|
||||
</p>
|
||||
|
||||
<h4>Email</h4>
|
||||
|
||||
<p>
|
||||
To contact the EnvayaSMS developers, email <a href='sms-developers@envaya.org'>sms-developers@envaya.org</a>.
|
||||
</p>
|
||||
|
||||
@ -1,66 +0,0 @@
|
||||
id: comparison
|
||||
title: Comparison to Alternative Methods
|
||||
---
|
||||
<p>
|
||||
SMS gateways can be created using several alternative methods, including hosted services (e.g. Twilio, Tropo, Clickatell),
|
||||
connecting GSM phones/modems to a computer (e.g. FrontlineSMS, RapidSMS, Kannel),
|
||||
and partnering directly with mobile operators.
|
||||
</p>
|
||||
|
||||
<table class='comparison_table'>
|
||||
<thead>
|
||||
<tr>
|
||||
<td> </td>
|
||||
<th>Benefits</th>
|
||||
<th>Drawbacks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<th>Hosted services</th>
|
||||
<td>
|
||||
<ul><li>High message throughput
|
||||
<li>Easy to deploy</ul>
|
||||
</td>
|
||||
<td>
|
||||
<ul><li>No local numbers in many countries
|
||||
<li>Usually no MMS support</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Connecting modem<br /> to computer</th>
|
||||
<td>
|
||||
<ul><li>Can work with inexpensive phone</li></ul>
|
||||
</td>
|
||||
<td>
|
||||
<ul><li>Expensive hardware costs
|
||||
<li>Lots of moving parts to keep working
|
||||
<li>Very difficult for non-technical users to deploy
|
||||
<li>Low message throughput
|
||||
<li>No MMS support</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Partnering with<br />mobile operators</th>
|
||||
<td>
|
||||
<ul>
|
||||
<li>High message throughput
|
||||
<li>Can provide free service to users via shortcode</ul>
|
||||
</td>
|
||||
<td>
|
||||
<ul><li>Usually very expensive
|
||||
<li>Requires operator approval
|
||||
<li>Long setup time</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<p>
|
||||
EnvayaSMS is ideal for situations where no hosted services with local numbers are available in
|
||||
a particular country, or when it is necessary to receive MMS messages.
|
||||
</p>
|
||||
<p>
|
||||
EnvayaSMS likely has lower throughput than hosted services or partnering with mobile operators, but should
|
||||
be able to forward up to a few thousand messages per phone per day.
|
||||
</p>
|
||||
@ -1,6 +1,80 @@
|
||||
id: faq
|
||||
title: Frequently Asked Questions
|
||||
---
|
||||
|
||||
<h4>
|
||||
Instead of implementing a SMS gateway as an Android app, why not use X instead? (where X = Twilio, Tropo, Clickatell, FrontlineSMS, RapidSMS, Kannel, etc.)
|
||||
</h4>
|
||||
|
||||
<p>
|
||||
The existing alternative methods for creating SMS gateways can generally be categorized as
|
||||
hosted services (e.g. Twilio, Tropo, Clickatell), connecting GSM phones/modems to a computer (e.g. FrontlineSMS, RapidSMS, Kannel),
|
||||
and partnering directly with mobile operators.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The table below summarizes the major benefits and drawbacks of each of these methods for creating an SMS gateway:
|
||||
</p>
|
||||
|
||||
<table class='comparison_table'>
|
||||
<thead>
|
||||
<tr>
|
||||
<td> </td>
|
||||
<th>Benefits</th>
|
||||
<th>Drawbacks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<th>Hosted services</th>
|
||||
<td>
|
||||
<ul><li>High message throughput
|
||||
<li>Easy to deploy</ul>
|
||||
</td>
|
||||
<td>
|
||||
<ul><li>No local numbers in many countries
|
||||
<li>Usually no MMS support</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Connecting modem<br /> to computer</th>
|
||||
<td>
|
||||
<ul><li>Can work with inexpensive phone</li></ul>
|
||||
</td>
|
||||
<td>
|
||||
<ul><li>Expensive hardware costs
|
||||
<li>Lots of moving parts to keep working
|
||||
<li>Very difficult for non-technical users to deploy
|
||||
<li>Low message throughput
|
||||
<li>No MMS support</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Partnering with<br />mobile operators</th>
|
||||
<td>
|
||||
<ul>
|
||||
<li>High message throughput
|
||||
<li>Can provide free service to users via shortcode</ul>
|
||||
</td>
|
||||
<td>
|
||||
<ul><li>Usually very expensive
|
||||
<li>Requires operator approval
|
||||
<li>Long setup time</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<p>
|
||||
EnvayaSMS is ideal for situations where no hosted services with local numbers are available in
|
||||
a particular country, or when it is necessary to receive MMS messages.
|
||||
</p>
|
||||
<p>
|
||||
EnvayaSMS likely has lower throughput than hosted services or partnering with mobile operators, but should
|
||||
be able to forward up to a few thousand messages per phone per day.
|
||||
</p>
|
||||
|
||||
|
||||
<h4>
|
||||
What phones are compatible with EnvayaSMS?
|
||||
</h4>
|
||||
@ -48,12 +122,12 @@ but anyone is welcome to contribute to improve it.
|
||||
|
||||
<p>
|
||||
The source code for EnvayaSMS was originally based on <a href='https://github.com/niryariv/kalsms/'>KalSMS</a>, an open-source project
|
||||
started by Nir Yariv in 2010 that introduced the idea of a simple SMS gateway implemented entirely as an Android app.
|
||||
started by Nir Yariv in 2010. KalSMS introduced the idea of a simple SMS gateway implemented entirely as an Android app.
|
||||
EnvayaSMS is a complete rewrite that shares little code with KalSMS.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
EnvayaSMS builds upon the idea of KalSMS by adding many new features that would be necessary for anyone deploying an SMS gateway in the field,
|
||||
EnvayaSMS builds upon the idea of KalSMS by adding many new features that are necessary when deploying an SMS gateway in the field,
|
||||
such as sending more than 100 messages per hour, authenticating the phone to the server, and retrying forwarding messages after transient errors.
|
||||
For a complete list of changes, see the <a href='/history/'>History</a> page.
|
||||
</p>
|
||||
|
||||
@ -29,11 +29,11 @@
|
||||
·
|
||||
<a {% if entry.id == 'serverapi' %}class='active'{% endif %} href='/serverapi/'>API Reference</a>
|
||||
·
|
||||
<a {% if entry.id == 'comparison' %}class='active'{% endif %} href='/comparison/'>Comparison</a>
|
||||
·
|
||||
<a {% if entry.id == 'faq' %}class='active'{% endif %} href='/faq/'>FAQ</a>
|
||||
·
|
||||
<a {% if entry.id == 'history' %}class='active'{% endif %} href='/history/'>History</a>
|
||||
·
|
||||
<a {% if entry.id == 'community' %}class='active'{% endif %} href='/community/'>Community</a>
|
||||
</div>
|
||||
|
||||
<h2>{{ entry.title }}</h2>
|
||||
|
||||
@ -80,4 +80,9 @@ hr { border: 0; width: 80%; border-bottom: 1px solid #aaa}
|
||||
a.button:hover
|
||||
{
|
||||
text-decoration:underline;
|
||||
}
|
||||
|
||||
img
|
||||
{
|
||||
border:0px;
|
||||
}
|
||||
78
community/index.html
Executable file
78
community/index.html
Executable file
@ -0,0 +1,78 @@
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<meta charset='utf-8'>
|
||||
<title>EnvayaSMS: Community</title>
|
||||
<link rel='stylesheet' type='text/css' href='/styles/site.css' />
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<a href="http://github.com/youngj/EnvayaSMS"><img style="position: absolute; top: 0; right: 0; border: 0;" src="http://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png" alt="Fork me on GitHub" /></a>
|
||||
|
||||
<div id="container">
|
||||
|
||||
<a style='float:left' href="/"><img src='/media/icon.png' height='72' width='72' style='margin-right:10px' /></a>
|
||||
<h1 style='padding-top:13px'><a href="/">EnvayaSMS</a>
|
||||
|
||||
<span class="small">
|
||||
SMS gateway for Android
|
||||
</span>
|
||||
|
||||
</h1>
|
||||
|
||||
<div class='menu' style='clear:both;padding-top:5px'>
|
||||
<a href='/'>Home</a>
|
||||
·
|
||||
<a href='/install/'>Install</a>
|
||||
·
|
||||
<a href='/how/'>How it Works</a>
|
||||
·
|
||||
<a href='/serverapi/'>API Reference</a>
|
||||
·
|
||||
<a href='/faq/'>FAQ</a>
|
||||
·
|
||||
<a href='/history/'>History</a>
|
||||
·
|
||||
<a class='active' href='/community/'>Community</a>
|
||||
</div>
|
||||
|
||||
<h2>Community</h2>
|
||||
|
||||
|
||||
<h4>Contribute to EnvayaSMS</h4>
|
||||
|
||||
<p>
|
||||
To contribute to EnvayaSMS as a developer, just <a href='http://github.com/youngj/EnvayaSMS'>fork the project on github</a>,
|
||||
work on your copy and send pull requests.
|
||||
</p>
|
||||
|
||||
<h4>Email</h4>
|
||||
|
||||
<p>
|
||||
To contact the EnvayaSMS developers, email <a href='sms-developers@envaya.org'>sms-developers@envaya.org</a>.
|
||||
</p>
|
||||
|
||||
|
||||
|
||||
<div class="footer">
|
||||
get the source code on GitHub : <a href="http://github.com/youngj/EnvayaSMS">youngj/EnvayaSMS</a>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
|
||||
<script type="text/javascript">
|
||||
|
||||
var _gaq = _gaq || [];
|
||||
_gaq.push(['_setAccount', 'UA-25868450-2']);
|
||||
_gaq.push(['_trackPageview']);
|
||||
|
||||
(function() {
|
||||
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
|
||||
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
|
||||
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
|
||||
})();
|
||||
|
||||
</script>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@ -34,6 +34,8 @@
|
||||
<a href='/faq/'>FAQ</a>
|
||||
·
|
||||
<a href='/history/'>History</a>
|
||||
·
|
||||
<a href='/community/'>Community</a>
|
||||
</div>
|
||||
|
||||
<h2>Comparison to Alternative Methods</h2>
|
||||
|
||||
@ -29,16 +29,90 @@
|
||||
·
|
||||
<a href='/serverapi/'>API Reference</a>
|
||||
·
|
||||
<a href='/comparison/'>Comparison</a>
|
||||
·
|
||||
<a class='active' href='/faq/'>FAQ</a>
|
||||
·
|
||||
<a href='/history/'>History</a>
|
||||
·
|
||||
<a href='/community/'>Community</a>
|
||||
</div>
|
||||
|
||||
<h2>Frequently Asked Questions</h2>
|
||||
|
||||
<h4>
|
||||
|
||||
<h4>
|
||||
Instead of implementing a SMS gateway as an Android app, why not use X instead? (where X = Twilio, Tropo, Clickatell, FrontlineSMS, RapidSMS, Kannel, etc.)
|
||||
</h4>
|
||||
|
||||
<p>
|
||||
The existing alternative methods for creating SMS gateways can generally be categorized as
|
||||
hosted services (e.g. Twilio, Tropo, Clickatell), connecting GSM phones/modems to a computer (e.g. FrontlineSMS, RapidSMS, Kannel),
|
||||
and partnering directly with mobile operators.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The table below summarizes the major benefits and drawbacks of each of these methods for creating an SMS gateway:
|
||||
</p>
|
||||
|
||||
<table class='comparison_table'>
|
||||
<thead>
|
||||
<tr>
|
||||
<td> </td>
|
||||
<th>Benefits</th>
|
||||
<th>Drawbacks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<th>Hosted services</th>
|
||||
<td>
|
||||
<ul><li>High message throughput
|
||||
<li>Easy to deploy</ul>
|
||||
</td>
|
||||
<td>
|
||||
<ul><li>No local numbers in many countries
|
||||
<li>Usually no MMS support</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Connecting modem<br /> to computer</th>
|
||||
<td>
|
||||
<ul><li>Can work with inexpensive phone</li></ul>
|
||||
</td>
|
||||
<td>
|
||||
<ul><li>Expensive hardware costs
|
||||
<li>Lots of moving parts to keep working
|
||||
<li>Very difficult for non-technical users to deploy
|
||||
<li>Low message throughput
|
||||
<li>No MMS support</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Partnering with<br />mobile operators</th>
|
||||
<td>
|
||||
<ul>
|
||||
<li>High message throughput
|
||||
<li>Can provide free service to users via shortcode</ul>
|
||||
</td>
|
||||
<td>
|
||||
<ul><li>Usually very expensive
|
||||
<li>Requires operator approval
|
||||
<li>Long setup time</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<p>
|
||||
EnvayaSMS is ideal for situations where no hosted services with local numbers are available in
|
||||
a particular country, or when it is necessary to receive MMS messages.
|
||||
</p>
|
||||
<p>
|
||||
EnvayaSMS likely has lower throughput than hosted services or partnering with mobile operators, but should
|
||||
be able to forward up to a few thousand messages per phone per day.
|
||||
</p>
|
||||
|
||||
|
||||
<h4>
|
||||
What phones are compatible with EnvayaSMS?
|
||||
</h4>
|
||||
|
||||
@ -85,12 +159,12 @@ but anyone is welcome to contribute to improve it.
|
||||
|
||||
<p>
|
||||
The source code for EnvayaSMS was originally based on <a href='https://github.com/niryariv/kalsms/'>KalSMS</a>, an open-source project
|
||||
started by Nir Yariv in 2010 that introduced the idea of a simple SMS gateway implemented entirely as an Android app.
|
||||
started by Nir Yariv in 2010. KalSMS introduced the idea of a simple SMS gateway implemented entirely as an Android app.
|
||||
EnvayaSMS is a complete rewrite that shares little code with KalSMS.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
EnvayaSMS builds upon the idea of KalSMS by adding many new features that would be necessary for anyone deploying an SMS gateway in the field,
|
||||
EnvayaSMS builds upon the idea of KalSMS by adding many new features that are necessary when deploying an SMS gateway in the field,
|
||||
such as sending more than 100 messages per hour, authenticating the phone to the server, and retrying forwarding messages after transient errors.
|
||||
For a complete list of changes, see the <a href='/history/'>History</a> page.
|
||||
</p>
|
||||
|
||||
@ -29,11 +29,11 @@
|
||||
·
|
||||
<a href='/serverapi/'>API Reference</a>
|
||||
·
|
||||
<a href='/comparison/'>Comparison</a>
|
||||
·
|
||||
<a href='/faq/'>FAQ</a>
|
||||
·
|
||||
<a class='active' href='/history/'>History</a>
|
||||
·
|
||||
<a href='/community/'>Community</a>
|
||||
</div>
|
||||
|
||||
<h2>History</h2>
|
||||
|
||||
@ -29,11 +29,11 @@
|
||||
·
|
||||
<a href='/serverapi/'>API Reference</a>
|
||||
·
|
||||
<a href='/comparison/'>Comparison</a>
|
||||
·
|
||||
<a href='/faq/'>FAQ</a>
|
||||
·
|
||||
<a href='/history/'>History</a>
|
||||
·
|
||||
<a href='/community/'>Community</a>
|
||||
</div>
|
||||
|
||||
<h2>How it Works</h2>
|
||||
|
||||
@ -29,11 +29,11 @@
|
||||
·
|
||||
<a href='/serverapi/'>API Reference</a>
|
||||
·
|
||||
<a href='/comparison/'>Comparison</a>
|
||||
·
|
||||
<a href='/faq/'>FAQ</a>
|
||||
·
|
||||
<a href='/history/'>History</a>
|
||||
·
|
||||
<a href='/community/'>Community</a>
|
||||
</div>
|
||||
|
||||
<h2></h2>
|
||||
|
||||
@ -29,11 +29,11 @@
|
||||
·
|
||||
<a href='/serverapi/'>API Reference</a>
|
||||
·
|
||||
<a href='/comparison/'>Comparison</a>
|
||||
·
|
||||
<a href='/faq/'>FAQ</a>
|
||||
·
|
||||
<a href='/history/'>History</a>
|
||||
·
|
||||
<a href='/community/'>Community</a>
|
||||
</div>
|
||||
|
||||
<h2>Installing EnvayaSMS</h2>
|
||||
|
||||
@ -29,11 +29,11 @@
|
||||
·
|
||||
<a class='active' href='/serverapi/'>API Reference</a>
|
||||
·
|
||||
<a href='/comparison/'>Comparison</a>
|
||||
·
|
||||
<a href='/faq/'>FAQ</a>
|
||||
·
|
||||
<a href='/history/'>History</a>
|
||||
·
|
||||
<a href='/community/'>Community</a>
|
||||
</div>
|
||||
|
||||
<h2>Server API Reference</h2>
|
||||
|
||||
@ -80,4 +80,9 @@ hr { border: 0; width: 80%; border-bottom: 1px solid #aaa}
|
||||
a.button:hover
|
||||
{
|
||||
text-decoration:underline;
|
||||
}
|
||||
|
||||
img
|
||||
{
|
||||
border:0px;
|
||||
}
|
||||
Loading…
Reference in New Issue
Block a user