-
+
+EnvayaSMS may be unable to connect to your development web server if it is blocked by a firewall on your computer, +or if your computer has a IP address that's inaccessible from your phone's network. +
+ ++If your Android phone is on the same Wi-Fi network as your development web server, configure the firewall on +your development computer to allow incoming connections to your web server, then simply enter your computer's IP address +in EnvayaSMS as the Server URL. +
++If you're testing with the phone's mobile data connection, or if your phone and development computer are on different +Wi-Fi networks, the IP address of your development web server is likely inaccessible to the phone. +
++To allow the phone to connect to your development computer, you can set up a reverse SSH tunnel between your +development computer and a server with a public IP address. +
++To set up a reverse SSH tunnel, you can either: + +
ssh -R to connect to your own server accessible from the public internet. For example:
+ssh -R 0.0.0.0:8765:localhost:80 [user]@[host]+
+This sets up port 8765 on host to forward to port 80 on your local development computer.
+Then you can use http://[host]:8765/ as the Server URL in EnvayaSMS, and it will be
+forwarded to http://localhost on your development server.
+
+Note: In order for SSH port forwarding to work, you will need to set GatewayPorts yes in the /etc/sshd_config file
+on the public server.
+
diff --git a/.phrozn/entries/history/index.twig b/.phrozn/entries/history/index.twig index 1cb0bef..067d4d6 100755 --- a/.phrozn/entries/history/index.twig +++ b/.phrozn/entries/history/index.twig @@ -2,27 +2,25 @@ id: history title: History --- -Version 2.0-rc2 (2011/09/29) +Version 2.0 (2011/10/01)
Then your network would look like this:
-
+
diff --git a/.phrozn/entries/index.twig b/.phrozn/entries/index.twig
index 4fdd136..88566f5 100755
--- a/.phrozn/entries/index.twig
+++ b/.phrozn/entries/index.twig
@@ -6,7 +6,8 @@ layout: default.twig
-
+
+
EnvayaSMS is a SMS and MMS gateway running entirely as an Android app.
@@ -51,9 +52,13 @@ It works wherever the phone can receive SMS messages and access the Internet
In order to deploy EnvayaSMS, you will need a messaging plan for your phone, and the phone itself. - EnvayaSMS is compatible with many old or inexpensive Android phones, e.g. the LG GT540, currently $120 on Amazon.com. + EnvayaSMS is compatible with many old or inexpensive Android phones, e.g. the LG GT540, currently $120 on Amazon.com.
++ Before deploying EnvayaSMS, you can test EnvayaSMS without an Android phone + by installing EnvayaSMS on an emulated phone on your computer. Learn more... +
- + Install EnvayaSMS Now \ No newline at end of file diff --git a/.phrozn/entries/install/index.twig b/.phrozn/entries/install/index.twig index c604a68..7ecd6df 100755 --- a/.phrozn/entries/install/index.twig +++ b/.phrozn/entries/install/index.twig @@ -1,21 +1,26 @@ id: install title: Installing EnvayaSMS --- -Before installing EnvayaSMS, ensure that you have the following prerequisites: +In order to install and deploy EnvayaSMS, you will need the following prerequisites:+Note: If you don't have these prerequisites yet, you can test EnvayaSMS on your computer. +
-
+
Important: After EnvayaSMS is enabled, it will forward all SMS messages regardless of whether the EnvayaSMS app is open. If you want to use SMS normally again, return to EnvayaSMS' settings screen -and uncheck "Enable EnvayaSMS". -
+and uncheck "Enable EnvayaSMS". + +If you're testing EnvayaSMS with an Android phone that you're also using for normal communication, +you can enable "Test mode" on the settings screen so that EnvayaSMS only handles SMS messages +from particular phone numbers.
POST /sg/app HTTP/1.1 X-Request-Signature: sAemG31uRllk/K9xck2WRNaF/WI= -Content-Length: 96 +Content-Length: 120 Content-Type: application/x-www-form-urlencoded Host: 192.168.70.1:3000 Connection: Keep-Alive -from=6505551234&message_type=sms&message=test&version=2&phone_number=16505551212&action=incoming +from=6505551234&message_type=sms&message=test&version=2&phone_number=16505551212 +&action=incoming×tamp=1317506831000
An incoming MMS message with an image/jpeg part and a text/plain part with message 'Test':
Checking for outgoing SMS messages:
diff --git a/.phrozn/entries/test/index.twig b/.phrozn/entries/test/index.twig new file mode 100755 index 0000000..4390aa0 --- /dev/null +++ b/.phrozn/entries/test/index.twig @@ -0,0 +1,46 @@ +id: test +title: Testing EnvayaSMS +--- + +
+
+If you don't yet have an Android phone, you can test EnvayaSMS in an emulated phone on your computer.
+
+With this method, you can test EnvayaSMS for free +and figure out if EnvayaSMS will work for your project +without needing to get an actual phone or subscribe to mobile service. +
++The following steps explain how to set up EnvayaSMS on an Android Virtual Device: +
+localhost as the Server URL (since this would refer to the AVD itself). Instead, use your computer's IP address on the local network, as shown by the ipconfig
+ or ifconfig utilities.
+ 
+ To simulate incoming SMS on the emulator:
+ localhost:5554sms send [phonenumber] [text message] to send messages to the emulator.+Of course, you can also test EnvayaSMS by connecting a real Android phone to your development web server. +For more information, see the FAQ. +
diff --git a/.phrozn/layouts/default.twig b/.phrozn/layouts/default.twig index 109bb1f..20f40b2 100755 --- a/.phrozn/layouts/default.twig +++ b/.phrozn/layouts/default.twig @@ -26,6 +26,8 @@ · Install · + Test + · How it Works · API Reference diff --git a/.phrozn/media/avd.png b/.phrozn/media/avd.png new file mode 100755 index 0000000..47f9dfe Binary files /dev/null and b/.phrozn/media/avd.png differ diff --git a/.phrozn/media/screenshot-main.png b/.phrozn/media/screenshot-main.png index e9cfc46..d7ad3c7 100755 Binary files a/.phrozn/media/screenshot-main.png and b/.phrozn/media/screenshot-main.png differ diff --git a/.phrozn/media/screenshot-market.png b/.phrozn/media/screenshot-market.png index 32f7a20..d6c3e03 100755 Binary files a/.phrozn/media/screenshot-market.png and b/.phrozn/media/screenshot-market.png differ diff --git a/.phrozn/media/screenshot-pending.png b/.phrozn/media/screenshot-pending.png new file mode 100755 index 0000000..1478847 Binary files /dev/null and b/.phrozn/media/screenshot-pending.png differ diff --git a/.phrozn/media/screenshot-settings.png b/.phrozn/media/screenshot-settings.png index 2eb02d3..d2b8ed6 100755 Binary files a/.phrozn/media/screenshot-settings.png and b/.phrozn/media/screenshot-settings.png differ diff --git a/.phrozn/media/telnet.png b/.phrozn/media/telnet.png new file mode 100755 index 0000000..f60b546 Binary files /dev/null and b/.phrozn/media/telnet.png differ diff --git a/.phrozn/media/topology.png b/.phrozn/media/topology.png index 881fe98..fbffeec 100755 Binary files a/.phrozn/media/topology.png and b/.phrozn/media/topology.png differ diff --git a/.phrozn/styles/site.css b/.phrozn/styles/site.css index 50ade16..433f147 100755 --- a/.phrozn/styles/site.css +++ b/.phrozn/styles/site.css @@ -55,7 +55,7 @@ dd #container { margin: 0 auto; - width: 700px; + width: 650px; } h1 { margin-top:0; font-size: 42px; color: #6b9412; margin-bottom: 3px; } h1 .small { font-size: 20px; color:#666; } @@ -74,7 +74,7 @@ hr { border: 0; width: 80%; border-bottom: 1px solid #aaa} .button { text-decoration:none; - display:block;margin:0 auto;width:200px;background:#6b9412;color:white;padding:8px;font-weight:bold;text-align:center; + display:block;width:200px;background:#6b9412;color:white;padding:8px;font-weight:bold;text-align:center; } a.button:hover @@ -87,7 +87,7 @@ img border:0px; } -.faq_links li +li { padding-bottom:5px; } @@ -100,4 +100,5 @@ img .faq_links a:hover { text-decoration:underline; -} \ No newline at end of file +} + diff --git a/community/index.html b/community/index.html index dc6bfa5..8881e77 100755 --- a/community/index.html +++ b/community/index.html @@ -26,6 +26,8 @@ · Install · + Test + · How it Works · API Reference diff --git a/faq/index.html b/faq/index.html index b551302..d5b4f16 100755 --- a/faq/index.html +++ b/faq/index.html @@ -26,6 +26,8 @@ · Install · + Test + · How it Works · API Reference @@ -47,6 +49,9 @@+EnvayaSMS may be unable to connect to your development web server if it is blocked by a firewall on your computer, +or if your computer has a IP address that's inaccessible from your phone's network. +
+ ++If your Android phone is on the same Wi-Fi network as your development web server, configure the firewall on +your development computer to allow incoming connections to your web server, then simply enter your computer's IP address +in EnvayaSMS as the Server URL. +
++If you're testing with the phone's mobile data connection, or if your phone and development computer are on different +Wi-Fi networks, the IP address of your development web server is likely inaccessible to the phone. +
++To allow the phone to connect to your development computer, you can set up a reverse SSH tunnel between your +development computer and a server with a public IP address. +
++To set up a reverse SSH tunnel, you can either: + +
ssh -R to connect to your own server accessible from the public internet. For example:
+ssh -R 0.0.0.0:8765:localhost:80 [user]@[host]+
+This sets up port 8765 on host to forward to port 80 on your local development computer.
+Then you can use http://[host]:8765/ as the Server URL in EnvayaSMS, and it will be
+forwarded to http://localhost on your development server.
+
+Note: In order for SSH port forwarding to work, you will need to set GatewayPorts yes in the /etc/sshd_config file
+on the public server.
+
diff --git a/history/index.html b/history/index.html index 8366490..27c3677 100755 --- a/history/index.html +++ b/history/index.html @@ -26,6 +26,8 @@ · Install · + Test + · How it Works · API Reference @@ -40,27 +42,25 @@
Then your network would look like this:
-
+
diff --git a/index.html b/index.html
index 17d6402..bea41f8 100755
--- a/index.html
+++ b/index.html
@@ -26,6 +26,8 @@
·
Install
·
+ Test
+ ·
How it Works
·
API Reference
@@ -44,7 +46,8 @@
-
+
+
In order to deploy EnvayaSMS, you will need a messaging plan for your phone, and the phone itself. - EnvayaSMS is compatible with many old or inexpensive Android phones, e.g. the LG GT540, currently $120 on Amazon.com. + EnvayaSMS is compatible with many old or inexpensive Android phones, e.g. the LG GT540, currently $120 on Amazon.com.
++ Before deploying EnvayaSMS, you can test EnvayaSMS without an Android phone + by installing EnvayaSMS on an emulated phone on your computer. Learn more... +
- + Install EnvayaSMS Now diff --git a/install/index.html b/install/index.html index 26938ef..6446382 100755 --- a/install/index.html +++ b/install/index.html @@ -26,6 +26,8 @@ · Install · + Test + · How it Works · API Reference @@ -39,21 +41,26 @@+Note: If you don't have these prerequisites yet, you can test EnvayaSMS on your computer. +
-
+
Important: After EnvayaSMS is enabled, it will forward all SMS messages regardless of whether the EnvayaSMS app is open. If you want to use SMS normally again, return to EnvayaSMS' settings screen -and uncheck "Enable EnvayaSMS". -
+and uncheck "Enable EnvayaSMS". + +If you're testing EnvayaSMS with an Android phone that you're also using for normal communication, +you can enable "Test mode" on the settings screen so that EnvayaSMS only handles SMS messages +from particular phone numbers.
POST /sg/app HTTP/1.1 X-Request-Signature: sAemG31uRllk/K9xck2WRNaF/WI= -Content-Length: 96 +Content-Length: 120 Content-Type: application/x-www-form-urlencoded Host: 192.168.70.1:3000 Connection: Keep-Alive -from=6505551234&message_type=sms&message=test&version=2&phone_number=16505551212&action=incoming +from=6505551234&message_type=sms&message=test&version=2&phone_number=16505551212 +&action=incoming×tamp=1317506831000
An incoming MMS message with an image/jpeg part and a text/plain part with message 'Test':
Checking for outgoing SMS messages:
diff --git a/styles/site.css b/styles/site.css index 50ade16..3847768 100755 --- a/styles/site.css +++ b/styles/site.css @@ -55,7 +55,7 @@ dd #container { margin: 0 auto; - width: 700px; + width: 650px; } h1 { margin-top:0; font-size: 42px; color: #6b9412; margin-bottom: 3px; } h1 .small { font-size: 20px; color:#666; } @@ -74,7 +74,7 @@ hr { border: 0; width: 80%; border-bottom: 1px solid #aaa} .button { text-decoration:none; - display:block;margin:0 auto;width:200px;background:#6b9412;color:white;padding:8px;font-weight:bold;text-align:center; + display:block;width:200px;background:#6b9412;color:white;padding:8px;font-weight:bold;text-align:center; } a.button:hover @@ -87,7 +87,7 @@ img border:0px; } -.faq_links li +li { padding-bottom:5px; } diff --git a/test/index.html b/test/index.html new file mode 100755 index 0000000..e01ce14 --- /dev/null +++ b/test/index.html @@ -0,0 +1,110 @@ + + + + + +
+
+ 
+
+
+If you don't yet have an Android phone, you can test EnvayaSMS in an emulated phone on your computer.
+
+With this method, you can test EnvayaSMS for free +and figure out if EnvayaSMS will work for your project +without needing to get an actual phone or subscribe to mobile service. +
++The following steps explain how to set up EnvayaSMS on an Android Virtual Device: +
+localhost as the Server URL (since this would refer to the AVD itself). Instead, use your computer's IP address on the local network, as shown by the ipconfig
+ or ifconfig utilities.
+
+ To simulate incoming SMS on the emulator:
+ localhost:5554sms send [phonenumber] [text message] to send messages to the emulator.+Of course, you can also test EnvayaSMS by connecting a real Android phone to your development web server. +For more information, see the FAQ. +
+ + + + +