https://wiki.seasteading.org/api.php?action=feedcontributions&user=75.94.154.157&feedformat=atomSeasteading - User contributions [en]2024-03-29T15:41:12ZUser contributionsMediaWiki 1.31.1https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=905User:Heath/PBX2008-06-05T03:38:23Z<p>75.94.154.157: /* Peering */</p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
Current version doesn't do GSM. Mainly because I have no idea how to do it.<br />
<br />
The only thing on here that's going to be non-obvious to the person familiar to Asterisk is the MELP stuff. Basically MELP is a 2400bps codec. It's very similar to LPC10 except you don't sound like a robot. The quality is pretty good. I wouldn't mind using it for all of my calls. Using MELP with IAX2 makes for a very low bandwidth channel. In trunking mode, IAX2 only has protocol overhead on the first 1 or 2 calls. After that, it starts to become trivial. Since LPC10 and MELP are so similar in structure, Asterisk can be tricked into thinking that MELP is actually LPC10. Using the reference code, I've gotten a codec_melp to load, but it just crashes. Unfortunately, this isn't an ultimate solution because the code I did (making the reference code reentrant) can't be released into the wild. That would be beyond "purely philosophical" inquiry and Compandent (the patent holder) could sue me into oblivion. Fortunately, they sell serial modules that can do multiple MELP channels.<br />
<br />
== Why all the trouble with MELP? ==<br />
Without MELP, there are other options.<br />
* LPC10 - Problem: makes you sound like a robot... it's pretty scary<br />
* g723.1 (still using VoIP) - Problem: doubles the amount of bandwidth needed<br />
* HF phone relay - Problem: bad sound quality<br />
* Satellite phone - Problem: expensive, quality not as good, annoying latency<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMRNB - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan-mobile<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol - good jitterbuffer that can be tweaked for dealing with packet loss/latency<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Two serial MELPe hardware modules $1000 (This could be way off)<br />
* Far end server colocation $400/month<br />
* Total: $6200<br />
* Recurring: $400 per month plus cost of minutes<br />
* Doesn't include wiring because that depends entirely on the layout of the structure.<br />
* Amplifiers will be necessary in some situations.<br />
<br />
This scheme supports 24 POTS lines. One could fit 3 or 4 of those cards in each server, so it scales pretty well.<br />
<br />
Obviously, the rack and UPS can be avoided if space is already provided by existing infrastructure. I leave it in here for the purpose of offering a complete solution.<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Misc Features ==<br />
* Faxing: Even with T.38 (Fax over IP), 14400bps are needed. It's not clear that this will always be available. Store-and-forward should be used to fall back on when network conditions are poor. Regular T.30 fax will work fine internally. Externally, it is absolutely 100% completely impossible to get regular faxing to work.<br />
* SMS works with a properly installed chan_mobile<br />
* Video will only be possible internally<br />
* Voicemail is trivial to setup with Asterisk. Usually works out of the box with chosen provisioning software.<br />
* Intercom - chan_alsa provides the ability to dial the sound card. "HI. I'M GEORGE ZIMMER, FOUNDER AND CEO OF THE MEN'S WAREHOUSE..."<br />
* Emergency/911 - trivial dialplan work<br />
<br />
== Network Access ==<br />
For external communication, I think the phone system should try this sequence...<br />
* Any good opportunistic bandwidth ('stead is in port and has access to wifi)<br />
* Packet HF - so that it gets low latency bandwidth if possible<br />
* Satellite<br />
* Analog HF channel for emergency backup<br />
<br />
I could use some good advice here from a networking guru.<br />
<br />
== Peering ==<br />
This is beyond the scope of this page, but a few points:<br />
* Industry is changing rapidly.<br />
* Peering between seastead communities is just a matter of settling on which system to use.<br />
* Systems include: E164 (ENUM), DUNDi, VPF (Voice Peering Fabric, uses ENUM)<br />
* Peering directly with carriers won't be possible for small seastead communities. They will just have to use a regular service provider. They don't want to go to the trouble unless you can provide them with a substantial number of routes.<br />
<br />
For peering between seastead communities, DUNDi is the most suited to decentralization. It has the disadvantage of little to no adoption as of this writing. Also, it only works with Asterisk.<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Bluetooth (cough) security<br />
* VoIP security not all that great in the open source world, but reasonable security can be achieved.<br />
<br />
== Instructions ==<br />
* Build servers. Insert Digium card/s.<br />
* Load the ups/servers/patch panels into the rack.<br />
* Connect power; connect servers to switch<br />
* Load Debian or Ubuntu Server onto the servers.<br />
* See Software Installation Procecure below...<br />
* Install your favorite billing/provisioning software - I leave this open since there's a bazillion ways to do it.<br />
* Connect the system to the LAN/WAN<br />
* Order a dedicated server, nothing special.<br />
* Install Debian, then Asterisk, like we did before<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+iax.conf Follow these instructions] to connect to the colo server<br />
* Subscribe to server per minute voip providers and configure them on the dedicated server<br />
* Create dialplan<br />
<br />
== Software Installation Procedure ==<br />
<br />
<pre><br />
<br />
# Copypasta from voip-info.org<br />
apt-get install linux-headers-`uname -r` bison openssl libssl-dev libeditline0 libeditline-dev libedit-dev<br />
apt-get install gcc make g++ php5-cli mysql-common libmysqlclient15-dev libnewt-dev dialog<br />
apt-get install libspeex1 libspeex-dev libvorbis-dev libcurl3-dev unixodbc mysql-server php5-mysql<br />
apt-get install vim sox nmap ngrep iftop iptraf elinks lynx festival festvox-kallpc8k lighttpd<br />
apt-get install libspandsp1 libspandsp-dev bluetooth libbluetooth2-dev libbluetooth bluez-utils blues-pin<br />
apt-get install phpmyadmin<br />
<br />
# Installation<br />
cd /usr/src<br />
wget http://downloads.digium.com/pub/asterisk/asterisk-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/zaptel/zaptel-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/libpri/libpri-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/asterisk/asterisk-addons-1.4-current.tar.gz<br />
wget http://www.chan-mobile.org/downloads/chan_mobile-1.4.x.patch<br />
svn co https://agx-ast-addons.svn.sourceforge.net/svnroot/agx-ast-addons agx-ast-addons<br />
svn co https://appconference.svn.sourceforge.net/svnroot/appconference appconference<br />
tar -zxvf libpri*<br />
tar -zxvf zaptel*<br />
tar -zxvf asterisk*<br />
tar -zxvf appconference*<br />
cd libpri ; make ; make install ; cd ..<br />
cd zaptel ; ./configure ; make menuselect ; make ; make install ; make config ; cd ..<br />
/etc/init.d/zaptel/start<br />
cd `ls | grep asterisk-1.4 | grep -v addons | head -n 1`<br />
./configure ; make menuselect ; make ; make install ; make samples ; make config ; cd ..<br />
cd `ls | grep asterisk-1.4 | grep addons | head -n 1`<br />
patch -p0 < ../chan_mobile-1.4.x.patch<br />
./configure ; make menuselect ; make ; make install ; make samples ; cd ..<br />
cd appconference/trunk<br />
make ; make install ; cd ../../<br />
cd ast-agx-addons/trunk<br />
./build.sh ; cd ../../<br />
/etc/init.d/asterisk start<br />
<br />
dialog --clear "Do United States software patents apply to you?" 0 0<br />
case $? in 1)<br />
dialog --msgbox --clear "Download the g729 and g729 codecs appropriate for your architecture." 0 0<br />
lynx "http://asterisk.hosting.lv/#bin"<br />
mv codec_g72* /usr/lib/asterisk/modules/<br />
mkdir melptemp ; cd melptemp<br />
wget ftp://maya.arcon.com/melp/melp1.2.tar.gz<br />
tar -zxvf melp1.2.tar.gz<br />
mv makefile Makefile<br />
cp melp.c melp.c.backup<br />
cat melp.c | sed -e 's/void main/int main/g' > melp2.c<br />
cat melp2.c | sed -e 's/,fp_in/,stdin/g' | sed -e 's/,fp_out/,fp_out/,stdout/g' > melp.c ; rm melp2.c<br />
make OSTYPE=linux<br />
cp melp /usr/bin/<br />
echo '#!/bin/bash\n\nmelp -a -i /dev/null -o /dev/null' > /usr/bin/melp_enc<br />
echo '#!/bin/bash\n\nmelp -s -i /dev/null -o /dev/null' > /usr/bin/melp_dec<br />
chmod a+x /usr/bin/melp_*<br />
cd ..<br />
esac<br />
<br />
</pre></div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=904User:Heath/PBX2008-06-05T03:34:12Z<p>75.94.154.157: </p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
Current version doesn't do GSM. Mainly because I have no idea how to do it.<br />
<br />
The only thing on here that's going to be non-obvious to the person familiar to Asterisk is the MELP stuff. Basically MELP is a 2400bps codec. It's very similar to LPC10 except you don't sound like a robot. The quality is pretty good. I wouldn't mind using it for all of my calls. Using MELP with IAX2 makes for a very low bandwidth channel. In trunking mode, IAX2 only has protocol overhead on the first 1 or 2 calls. After that, it starts to become trivial. Since LPC10 and MELP are so similar in structure, Asterisk can be tricked into thinking that MELP is actually LPC10. Using the reference code, I've gotten a codec_melp to load, but it just crashes. Unfortunately, this isn't an ultimate solution because the code I did (making the reference code reentrant) can't be released into the wild. That would be beyond "purely philosophical" inquiry and Compandent (the patent holder) could sue me into oblivion. Fortunately, they sell serial modules that can do multiple MELP channels.<br />
<br />
== Why all the trouble with MELP? ==<br />
Without MELP, there are other options.<br />
* LPC10 - Problem: makes you sound like a robot... it's pretty scary<br />
* g723.1 (still using VoIP) - Problem: doubles the amount of bandwidth needed<br />
* HF phone relay - Problem: bad sound quality<br />
* Satellite phone - Problem: expensive, quality not as good, annoying latency<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMRNB - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan-mobile<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol - good jitterbuffer that can be tweaked for dealing with packet loss/latency<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Two serial MELPe hardware modules $1000 (This could be way off)<br />
* Far end server colocation $400/month<br />
* Total: $6200<br />
* Recurring: $400 per month plus cost of minutes<br />
* Doesn't include wiring because that depends entirely on the layout of the structure.<br />
* Amplifiers will be necessary in some situations.<br />
<br />
This scheme supports 24 POTS lines. One could fit 3 or 4 of those cards in each server, so it scales pretty well.<br />
<br />
Obviously, the rack and UPS can be avoided if space is already provided by existing infrastructure. I leave it in here for the purpose of offering a complete solution.<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Misc Features ==<br />
* Faxing: Even with T.38 (Fax over IP), 14400bps are needed. It's not clear that this will always be available. Store-and-forward should be used to fall back on when network conditions are poor. Regular T.30 fax will work fine internally. Externally, it is absolutely 100% completely impossible to get regular faxing to work.<br />
* SMS works with a properly installed chan_mobile<br />
* Video will only be possible internally<br />
* Voicemail is trivial to setup with Asterisk. Usually works out of the box with chosen provisioning software.<br />
* Intercom - chan_alsa provides the ability to dial the sound card. "HI. I'M GEORGE ZIMMER, FOUNDER AND CEO OF THE MEN'S WAREHOUSE..."<br />
* Emergency/911 - trivial dialplan work<br />
<br />
== Network Access ==<br />
For external communication, I think the phone system should try this sequence...<br />
* Any good opportunistic bandwidth ('stead is in port and has access to wifi)<br />
* Packet HF - so that it gets low latency bandwidth if possible<br />
* Satellite<br />
* Analog HF channel for emergency backup<br />
<br />
I could use some good advice here from a networking guru.<br />
<br />
== Peering ==<br />
This is beyond the scope of this page, but a few points:<br />
* Industry is changing rapidly.<br />
* Peering between seastead communities is just a matter of settling on which system to use.<br />
* Systems include: E164 (ENUM), DUNDi, VPF (Voice Peering Fabric, uses ENUM)<br />
<br />
For peering between seastead communities, DUNDi is the most suited to decentralization. It has the disadvantage of little to no adoption as of this writing. Also, it only works with Asterisk.<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Bluetooth (cough) security<br />
* VoIP security not all that great in the open source world, but reasonable security can be achieved.<br />
<br />
== Instructions ==<br />
* Build servers. Insert Digium card/s.<br />
* Load the ups/servers/patch panels into the rack.<br />
* Connect power; connect servers to switch<br />
* Load Debian or Ubuntu Server onto the servers.<br />
* See Software Installation Procecure below...<br />
* Install your favorite billing/provisioning software - I leave this open since there's a bazillion ways to do it.<br />
* Connect the system to the LAN/WAN<br />
* Order a dedicated server, nothing special.<br />
* Install Debian, then Asterisk, like we did before<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+iax.conf Follow these instructions] to connect to the colo server<br />
* Subscribe to server per minute voip providers and configure them on the dedicated server<br />
* Create dialplan<br />
<br />
== Software Installation Procedure ==<br />
<br />
<pre><br />
<br />
# Copypasta from voip-info.org<br />
apt-get install linux-headers-`uname -r` bison openssl libssl-dev libeditline0 libeditline-dev libedit-dev<br />
apt-get install gcc make g++ php5-cli mysql-common libmysqlclient15-dev libnewt-dev dialog<br />
apt-get install libspeex1 libspeex-dev libvorbis-dev libcurl3-dev unixodbc mysql-server php5-mysql<br />
apt-get install vim sox nmap ngrep iftop iptraf elinks lynx festival festvox-kallpc8k lighttpd<br />
apt-get install libspandsp1 libspandsp-dev bluetooth libbluetooth2-dev libbluetooth bluez-utils blues-pin<br />
apt-get install phpmyadmin<br />
<br />
# Installation<br />
cd /usr/src<br />
wget http://downloads.digium.com/pub/asterisk/asterisk-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/zaptel/zaptel-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/libpri/libpri-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/asterisk/asterisk-addons-1.4-current.tar.gz<br />
wget http://www.chan-mobile.org/downloads/chan_mobile-1.4.x.patch<br />
svn co https://agx-ast-addons.svn.sourceforge.net/svnroot/agx-ast-addons agx-ast-addons<br />
svn co https://appconference.svn.sourceforge.net/svnroot/appconference appconference<br />
tar -zxvf libpri*<br />
tar -zxvf zaptel*<br />
tar -zxvf asterisk*<br />
tar -zxvf appconference*<br />
cd libpri ; make ; make install ; cd ..<br />
cd zaptel ; ./configure ; make menuselect ; make ; make install ; make config ; cd ..<br />
/etc/init.d/zaptel/start<br />
cd `ls | grep asterisk-1.4 | grep -v addons | head -n 1`<br />
./configure ; make menuselect ; make ; make install ; make samples ; make config ; cd ..<br />
cd `ls | grep asterisk-1.4 | grep addons | head -n 1`<br />
patch -p0 < ../chan_mobile-1.4.x.patch<br />
./configure ; make menuselect ; make ; make install ; make samples ; cd ..<br />
cd appconference/trunk<br />
make ; make install ; cd ../../<br />
cd ast-agx-addons/trunk<br />
./build.sh ; cd ../../<br />
/etc/init.d/asterisk start<br />
<br />
dialog --clear "Do United States software patents apply to you?" 0 0<br />
case $? in 1)<br />
dialog --msgbox --clear "Download the g729 and g729 codecs appropriate for your architecture." 0 0<br />
lynx "http://asterisk.hosting.lv/#bin"<br />
mv codec_g72* /usr/lib/asterisk/modules/<br />
mkdir melptemp ; cd melptemp<br />
wget ftp://maya.arcon.com/melp/melp1.2.tar.gz<br />
tar -zxvf melp1.2.tar.gz<br />
mv makefile Makefile<br />
cp melp.c melp.c.backup<br />
cat melp.c | sed -e 's/void main/int main/g' > melp2.c<br />
cat melp2.c | sed -e 's/,fp_in/,stdin/g' | sed -e 's/,fp_out/,fp_out/,stdout/g' > melp.c ; rm melp2.c<br />
make OSTYPE=linux<br />
cp melp /usr/bin/<br />
echo '#!/bin/bash\n\nmelp -a -i /dev/null -o /dev/null' > /usr/bin/melp_enc<br />
echo '#!/bin/bash\n\nmelp -s -i /dev/null -o /dev/null' > /usr/bin/melp_dec<br />
chmod a+x /usr/bin/melp_*<br />
cd ..<br />
esac<br />
<br />
</pre></div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=658User:Heath/PBX2008-06-02T04:04:24Z<p>75.94.154.157: </p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
Current version doesn't do GSM. Mainly because I have no idea how to do it.<br />
<br />
The only thing on here that's going to be non-obvious to the person familiar to Asterisk is the MELP stuff. Basically MELP is a 2400bps codec. It's very similar to LPC10 except you don't sound like a robot. The quality is pretty good. I wouldn't mind using it for all of my calls. Using MELP with IAX2 makes for a very low bandwidth channel. In trunking mode, IAX2 only has protocol overhead on the first 1 or 2 calls. After that, it starts to become trivial. Since LPC10 and MELP are so similar in structure, Asterisk can be tricked into thinking that MELP is actually LPC10. Using the reference code, I've gotten a codec_melp to load, but it just crashes. Unfortunately, this isn't an ultimate solution because the code I did (making the reference code reentrant) can't be released into the wild. That would be beyond "purely philosophical" inquiry and Compandent (the patent holder) could sue me into oblivion. Fortunately, they sell serial modules that can do multiple MELP channels.<br />
<br />
== Why all the trouble with MELP? ==<br />
Without MELP, there are other options.<br />
* LPC10 - Problem: makes you sound like a robot... it's pretty scary<br />
* g723.1 (still using VoIP) - Problem: doubles the amount of bandwidth needed<br />
* HF phone relay - Problem: bad sound quality<br />
* Satellite phone - Problem: expensive, quality not as good, annoying latency<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMRNB - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan-mobile<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol - good jitterbuffer that can be tweaked for dealing with packet loss/latency<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Two serial MELPe hardware modules $1000 (This could be way off)<br />
* Far end server colocation $400/month<br />
* Total: $6200<br />
* Recurring: $400 per month plus cost of minutes<br />
* Doesn't include wiring because that depends entirely on the layout of the structure.<br />
* Amplifiers will be necessary in some situations.<br />
<br />
This scheme supports 24 POTS lines. One could fit 3 or 4 of those cards in each server, so it scales pretty well.<br />
<br />
Obviously, the rack and UPS can be avoided if space is already provided by existing infrastructure. I leave it in here for the purpose of offering a complete solution.<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Misc Features ==<br />
* Faxing: Even with T.38 (Fax over IP), 14400bps are needed. It's not clear that this will always be available. Store-and-forward should be used to fall back on when network conditions are poor. Regular T.30 fax will work fine internally. Externally, it is absolutely 100% completely impossible to get regular faxing to work.<br />
* SMS works with a properly installed chan_mobile<br />
* Video will only be possible internally<br />
* Voicemail is trivial to setup with Asterisk. Usually works out of the box with chosen provisioning software.<br />
* Intercom - chan_alsa provides the ability to dial the sound card. "HI. I'M GEORGE ZIMMER, FOUNDER AND CEO OF THE MEN'S WAREHOUSE..."<br />
<br />
== Network Access ==<br />
For external communication, I think the phone system should try this sequence...<br />
* Any good opportunistic bandwidth ('stead is in port and has access to wifi)<br />
* Packet HF - so that it gets low latency bandwidth if possible<br />
* Satellite<br />
* Analog HF channel for emergency backup<br />
<br />
I could use some good advice here from a networking guru.<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Bluetooth (cough) security<br />
* VoIP security not all that great in the open source world, but reasonable security can be achieved.<br />
<br />
== Instructions ==<br />
* Build servers. Insert Digium card/s.<br />
* Load the ups/servers/patch panels into the rack.<br />
* Connect power; connect servers to switch<br />
* Load Debian or Ubuntu Server onto the servers.<br />
* [http://www.chan-mobile.org/?page_id=4 Use these instructions] in conjunction with the following step.<br />
* [http://www.voip-info.org/tiki-index.php?page=Asterisk+Linux+Debian Follow these instructions] - Easy if you've done it a few times.<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf Follow these instructions] - Have a friend nearby to take your aggression out on.<br />
* Call Digium to purchase g729 licenses. They'll help with installation as well.<br />
* Install my MELPe hacks.<br />
* Install your favorite billing/provisioning software - I leave this open since there's a bazillion ways to do it.<br />
* Connect the system to the LAN/WAN<br />
* Order a dedicated server, nothing special.<br />
* Install Debian, then Asterisk, like we did before<br />
* Have colo personnel install MELPe hardware, then install MELPe hacks<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+iax.conf Follow these instructions] to connect to the colo server<br />
* Subscribe to server per minute voip providers and configure them on the dedicated server<br />
* Create dialplan<br />
<br />
Using a colo is avoidable if enough bandwidth is available. Will TSI one day be the termination point for HF?</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User_talk:Heath/PBX&diff=656User talk:Heath/PBX2008-06-02T03:19:32Z<p>75.94.154.157: </p>
<hr />
<div>Any electricians want to enlighten me as to what I mean by "~1000 available power" ?<br />
<br />
==Headset==<br />
Hi Heath, do you know of a wireless headset that doesn't echo with asterisk? It seems impossible... [[User:Joep|Joep]] 01:33, 1 June 2008 (UTC)<br />
: If I had to guess, the jitterbuffer is creating too much latency (as of 1.4 it's automatic for SIP and IAX2). You probably already tried turning down the mic? As long as the mic is close to the earpiece, it's difficult to control.<br />
<br />
== Scratch pad for more specific instructions ==<br />
<br />
<pre><br />
<br />
# Copypasta from voip-info.org<br />
apt-get install linux-headers-`uname -r` bison openssl libssl-dev libeditline0 libeditline-dev libedit-dev<br />
apt-get install gcc make g++ php5-cli mysql-common libmysqlclient15-dev libnewt-dev<br />
apt-get install libspeex1 libspeex-dev libvorbis-dev libcurl3-dev unixodbc mysql-server php5-mysql<br />
apt-get install vim sox nmap ngrep iftop iptraf elinks lynx festival festvox-kallpc8k lighttpd<br />
apt-get install libspandsp1 libspandsp-dev<br />
<br />
# Installation<br />
cd /usr/src<br />
wget http://downloads.digium.com/pub/asterisk/asterisk-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/zaptel/zaptel-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/libpri/libpri-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/asterisk/asterisk-addons-1.4-current.tar.gz<br />
wget http://downloads.sourceforge.net/appconference/appconference-2.0.1.tar.gz<br />
tar -zxvf libpri*<br />
tar -zxvf zaptel*<br />
tar -zxvf asterisk*<br />
tar -zxvf appconference*<br />
cd libpri ; make ; make install ; cd ..<br />
cd zaptel ; ./configure ; make menuselect ; make ; make install ; make config ; cd ..<br />
/etc/init.d/zaptel/start<br />
cd `ls | grep asterisk-1.4 | grep -v addons | head -n 1`<br />
./configure ; make menuselect ; make ; make install ; make samples ; make config ; cd ..<br />
cd `ls | grep asterisk-1.4 | grep addons | head -n 1`<br />
./configure ; make menuselect ; make ; make install ; make samples ; cd ..<br />
cd appconference/trunk<br />
make ; make install ; cd ../../<br />
/etc/init.d/asterisk start<br />
<br />
</pre></div>75.94.154.157https://wiki.seasteading.org/index.php?title=User_talk:Heath/PBX&diff=655User talk:Heath/PBX2008-06-02T03:14:34Z<p>75.94.154.157: </p>
<hr />
<div>Any electricians want to enlighten me as to what I mean by "~1000 available power" ?<br />
<br />
==Headset==<br />
Hi Heath, do you know of a wireless headset that doesn't echo with asterisk? It seems impossible... [[User:Joep|Joep]] 01:33, 1 June 2008 (UTC)<br />
: If I had to guess, the jitterbuffer is creating too much latency (as of 1.4 it's automatic for SIP and IAX2). You probably already tried turning down the mic? As long as the mic is close to the earpiece, it's difficult to control.<br />
<br />
== Scratch pad for more specific instructions ==<br />
# Copypasta from voip-info.org<br />
apt-get install linux-headers-`uname -r` bison openssl libssl-dev libeditline0 libeditline-dev libedit-dev<br />
apt-get install gcc make g++ php5-cli mysql-common libmysqlclient15-dev libnewt-dev<br />
apt-get install libspeex1 libspeex-dev libvorbis-dev libcurl3-dev unixodbc mysql-server php5-mysql<br />
apt-get install vim sox nmap ngrep iftop iptraf elinks lynx festival festvox-kallpc8k lighttpd<br />
apt-get install libspandsp1 libspandsp-dev<br />
<br />
# Installation<br />
cd /usr/src<br />
wget http://downloads.digium.com/pub/asterisk/asterisk-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/zaptel/zaptel-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/libpri/libpri-1.4-current.tar.gz<br />
wget http://downloads.digium.com/pub/asterisk/asterisk-addons-1.4-current.tar.gz<br />
wget http://downloads.sourceforge.net/appconference/appconference-2.0.1.tar.gz<br />
tar -zxvf libpri*<br />
tar -zxvf zaptel*<br />
tar -zxvf asterisk*<br />
tar -zxvf appconference*<br />
cd libpri ; make ; make install ; cd ..<br />
cd zaptel ; ./configure ; make menuselect ; make ; make install ; make config ; cd ..<br />
/etc/init.d/zaptel/start<br />
cd `ls | grep asterisk-1.4 | grep -v addons | head -n 1`<br />
./configure ; make menuselect ; make ; make install ; make samples ; make config ; cd ..<br />
cd `ls | grep asterisk-1.4 | grep addons | head -n 1`<br />
./configure ; make menuselect ; make ; make install ; make samples ; cd ..<br />
cd appconference/trunk<br />
make ; make install ; cd ../../<br />
/etc/init.d/asterisk start</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Communications&diff=650Communications2008-06-02T00:49:27Z<p>75.94.154.157: /* External */</p>
<hr />
<div>== Internal ==<br />
<br />
'''Wireless phone system -'''<br />
GSM/Bluetooth/WIFI accesspoints feeding into a PBX such as Asterisk.<br />
<br />
'''Paging system -''' <br />
"Smart system" where everyone wears a transponder so the communications system knows where to page/ring you?<br />
<br />
'''Fire/Life Safety systems''' - Detection and Warning<br />
<br />
'''Entertainment -''' Internal Fiberoptic network to move large quantities of data - movies, etc? Cable TV analog<br />
<br />
== External ==<br />
<br />
'''Satellite Communications''' Satcomms could cover phone, internet and TV. Our current provider at my 'remote location' is all SatBased to the UK. We have a sat Modem, and on the London end our VOIPS connect to a call manager and Public Internet\Phone is provided in this way as well. Costs about 60k a year for a very well sustained (no double sale of bandwidth) 4mb up/dn and can serve 300 people easily. The price of this will come down as the technology for Seasteading goes up.<br />
<br />
'''Phone -''' The only way to ensure access to phone access globally is via [[satellite]] or radio relay (digital or analog). When a platform is close enough to shore to be above the radio horizon, regular wireless links such as WiFi and GSM can be used.<br />
<br />
'''Internet -''' The same goes for Internet access, however using HF radio is considerably more cumbersome.<br />
<br />
'''Satellite Entertainment''' TV/Radio<br />
<br />
Multiple dishes?<br />
<br />
'''High Frequency Radio (2-30MHz)''' - HF is a worldwide option for phone and network access, however it has several problems that limit its usefulness. It does have the advantage of low latency.<br />
<br />
* Requires large antennas (30+ meters or longer)<br />
* Requires a lot of equipment.<br />
* Use of encryption is heavily restricted.<br />
* Establishing reliable links is difficult. [http://en.wikipedia.org/wiki/Automatic_link_establishment Automatic Link Establishment] (ALE) is a possible solution to this.<br />
<br />
'''Troposcatter''' [http://en.wikipedia.org/wiki/Troposcatter Over the horizon communications]<br />
<br />
Range is something like 100 to 1200 miles. [http://goliath.ecnext.com/coms2/gi_0199-5769172/RADYNE-TROPOSCATTER-MODEMS-BREAK-NEW.html Data rate to 40 Mbps]<br />
<br />
Possible 'Pirate' Radio Station(s)?<br />
<br />
'''GMDSS System''' <br />
Global Maritime Distress Signal System, SOLAS requirement<br />
<br />
'''VHF-FM Radio Marine Band 156-158 MHz'''<br />
SOLAS requirements to maintain a listening watch on distress frequencies<br />
<br />
Coordinate small boat activities around SeaStead, each small boat equipped with one of these too. <br />
<br />
Relatively small radios, low power (~25w ERP), small antennas (2 meters or less in length, max. Handhelds ~8" long)<br />
<br />
'''VHF-AM Radio Aircraft Band 118-136MHz'''<br />
<br />
Coordinating air traffic inbound and outbound.<br />
<br />
Several frequencies: Departure/Approach, Tower (landing), Ground (ground movement), coordination frequencies<br />
<br />
Air Traffic Control radar<br />
<br />
Air Navigation aids? [http://en.wikipedia.org/wiki/VHF_omnidirectional_range VOR]/[http://en.wikipedia.org/wiki/Distance_measuring_equipment DME]/ [http://en.wikipedia.org/wiki/TACAN TACAN] or rely on [http://en.wikipedia.org/wiki/GPS GPS]?<br />
<br />
<br />
'''Tactical Radios - Trunked 800 MHz systems'''? Used for: <br />
<br />
Firefighting / EMS<br />
<br />
Maintenance<br />
<br />
Defense<br />
<br />
Law Enforcement?<br />
<br />
Need to investigate frequency propagation through structures. <br />
<br />
<br />
'''Other radios''' - Ability to monitor/speak on military frequencies, ie <br />
<br />
30-70 MHz FM (Military Tactical Net);<br />
<br />
220-400 MHz AM (Military aviation band), etc?<br />
<br />
"Company" radios for SeaStead operations, similar to business-band frequencies (VHF-FM High at 150MHz or UHF-FM at 450-470MHz and/or [http://en.wikipedia.org/wiki/Trunked_radio_system 800 MHz trunked system]. Will probably require robust encryption.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=470User:Heath/PBX2008-05-31T19:26:55Z<p>75.94.154.157: /* Instructions */</p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
Current version doesn't do GSM. Mainly because I have no idea how to do it.<br />
<br />
The only thing on here that's going to be non-obvious to the person familiar to Asterisk is the MELP stuff. Basically MELP is a 2400bps codec. It's very similar to LPC10 except you don't sound like a robot. The quality is pretty good. I wouldn't mind using it for all of my calls. Using MELP with IAX2 makes for a very low bandwidth channel. In trunking mode, IAX2 only has protocol overhead on the first 1 or 2 calls. After that, it starts to become trivial. Since LPC10 and Asterisk are so similar, Asterisk can be tricked into thinking that MELP is actually LPC10. Using the reference code, I've gotten a codec_melp to load, but it just crashes. Unfortunately, this isn't an ultimate solution because the code I did (making the reference code reentrant) can't be released into the wild. That would be beyond "purely philosophical" inquiry and Compandent (the patent holder) could sue me into oblivion. Fortunately, they sell serial modules that can do multiple MELP channels.<br />
<br />
== Why all the trouble with MELP? ==<br />
Without MELP, there are other options.<br />
* LPC10 - Problem: makes you sound like a robot... it's pretty scary<br />
* g723.1 (still using VoIP) - Problem: doubles the amount of bandwidth needed<br />
* HF phone relay - Problem: bad sound quality<br />
* Satellite phone - Problem: expensive, quality not as good<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMRNB - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan-mobile<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol - good jitterbuffer that can be tweaked for dealing with packet loss/latency<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Two serial MELPe hardware modules $1000 (This could be way off)<br />
* Far end server colocation $400/month<br />
* Total: $6200<br />
* Recurring: $400 per month plus cost of minutes<br />
* Doesn't include wiring because that depends entirely on the layout of the structure.<br />
* Amplifiers will be necessary in some situations.<br />
<br />
This scheme supports 24 POTS lines. One could fit 3 or 4 of those cards in each server, so it scales pretty well.<br />
<br />
Obviously, the rack and UPS can be avoided if space is already provided by existing infrastructure. I leave it in here for the purpose of offering a complete solution.<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Bluetooth (cough) security<br />
* VoIP security not all that great in the open source world, but reasonable security can be achieved.<br />
<br />
== Instructions ==<br />
* Build servers. Insert Digium card/s.<br />
* Load the ups/servers/patch panels into the rack.<br />
* Connect power; connect servers to switch<br />
* Load Debian or Ubuntu Server onto the servers.<br />
* [http://www.chan-mobile.org/?page_id=4 Use these instructions] in conjunction with the following step.<br />
* [http://www.voip-info.org/tiki-index.php?page=Asterisk+Linux+Debian Follow these instructions] - Easy if you've done it a few times.<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf Follow these instructions] - Have a friend nearby to take your aggression out on.<br />
* Call Digium to purchase g729 licenses. They'll help with installation as well.<br />
* Install my MELPe hacks.<br />
* Install your favorite billing/provisioning software - I leave this open since there's a bazillion ways to do it.<br />
* Connect the system to the LAN/WAN<br />
* Order a dedicated server, nothing special.<br />
* Install Debian, then Asterisk, like we did before<br />
* Have colo personnel install MELPe hardware, then install MELPe hacks<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+iax.conf Follow these instructions] to connect to the colo server<br />
* Subscribe to server per minute voip providers and configure them on the dedicated server<br />
* Connect to them via _X.,1,Dial(sip/myprovider/${EXTEN})<br />
<br />
Using a colo is avoidable if enough bandwidth is available. Will TSI one day be the termination point for HF?</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=469User:Heath/PBX2008-05-31T19:25:32Z<p>75.94.154.157: </p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
Current version doesn't do GSM. Mainly because I have no idea how to do it.<br />
<br />
The only thing on here that's going to be non-obvious to the person familiar to Asterisk is the MELP stuff. Basically MELP is a 2400bps codec. It's very similar to LPC10 except you don't sound like a robot. The quality is pretty good. I wouldn't mind using it for all of my calls. Using MELP with IAX2 makes for a very low bandwidth channel. In trunking mode, IAX2 only has protocol overhead on the first 1 or 2 calls. After that, it starts to become trivial. Since LPC10 and Asterisk are so similar, Asterisk can be tricked into thinking that MELP is actually LPC10. Using the reference code, I've gotten a codec_melp to load, but it just crashes. Unfortunately, this isn't an ultimate solution because the code I did (making the reference code reentrant) can't be released into the wild. That would be beyond "purely philosophical" inquiry and Compandent (the patent holder) could sue me into oblivion. Fortunately, they sell serial modules that can do multiple MELP channels.<br />
<br />
== Why all the trouble with MELP? ==<br />
Without MELP, there are other options.<br />
* LPC10 - Problem: makes you sound like a robot... it's pretty scary<br />
* g723.1 (still using VoIP) - Problem: doubles the amount of bandwidth needed<br />
* HF phone relay - Problem: bad sound quality<br />
* Satellite phone - Problem: expensive, quality not as good<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMRNB - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan-mobile<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol - good jitterbuffer that can be tweaked for dealing with packet loss/latency<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Two serial MELPe hardware modules $1000 (This could be way off)<br />
* Far end server colocation $400/month<br />
* Total: $6200<br />
* Recurring: $400 per month plus cost of minutes<br />
* Doesn't include wiring because that depends entirely on the layout of the structure.<br />
* Amplifiers will be necessary in some situations.<br />
<br />
This scheme supports 24 POTS lines. One could fit 3 or 4 of those cards in each server, so it scales pretty well.<br />
<br />
Obviously, the rack and UPS can be avoided if space is already provided by existing infrastructure. I leave it in here for the purpose of offering a complete solution.<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Bluetooth (cough) security<br />
* VoIP security not all that great in the open source world, but reasonable security can be achieved.<br />
<br />
== Instructions ==<br />
* Build servers. Insert Digium card/s.<br />
* Load the ups/servers/patch panels into the rack.<br />
* Connect power; connect servers to switch<br />
* Load Debian or Ubuntu Server onto the servers.<br />
* [http://www.chan-mobile.org/?page_id=4 Use these instructions] in conjunction with the following step.<br />
* [http://www.voip-info.org/tiki-index.php?page=Asterisk+Linux+Debian Follow these instructions] - Easy if you've done it a few times.<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf Follow these instructions] - Have a friend nearby to take your aggression out on.<br />
* Call Digium to purchase g729 licenses. They'll help with installation as well.<br />
* Install my MELPe hacks.<br />
* Install your favorite billing/provisioning software.<br />
* Connect the system to the LAN/WAN<br />
* Order a dedicated server, nothing special.<br />
* Install Debian, then Asterisk, like we did before<br />
* Have colo personnel install MELPe hardware, then install MELPe hacks<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+iax.conf Follow these instructions] to connect to the colo server<br />
* Subscribe to server per minute voip providers and configure them on the dedicated server<br />
* Connect to them via _X.,1,Dial(sip/myprovider/${EXTEN})<br />
<br />
Using a colo is avoidable if enough bandwidth is available. Will TSI one day be the termination point for HF?</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=468User:Heath/PBX2008-05-31T18:54:18Z<p>75.94.154.157: /* Instructions */</p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
Current version doesn't do GSM. Mainly because I have no idea how to do it. Don't know how to do the bluetooth stuff either.<br />
<br />
The only thing on here that's going to be non-obvious to the person familiar to Asterisk is the MELP stuff. Basically MELP is a 2400bps codec. It's very similar to LPC10 except you don't sound like a robot. The quality is pretty good. I wouldn't mind using it for all of my calls. Using MELP with IAX2 makes for a very low bandwidth channel. In trunking mode, IAX2 only has protocol overhead on the first 1 or 2 calls. After that, it starts to become trivial. Since LPC10 and Asterisk are so similar, Asterisk can be tricked into thinking that MELP is actually LPC10. Using the reference code, I've gotten a codec_melp to load, but it just crashes. Unfortunately, this isn't an ultimate solution because the code I did (making the reference code reentrant) can't be released into the wild. That would be beyond "purely philosophical" inquiry and Compandent (the patent holder) could sue me into oblivion. Fortunately, they sell serial modules that can do multiple MELP channels.<br />
<br />
== Why all the trouble with MELP? ==<br />
Without MELP, there are other options.<br />
* LPC10 - Problem: makes you sound like a robot... it's pretty scary<br />
* g723.1 (still using VoIP) - Problem: doubles the amount of bandwidth needed<br />
* HF phone relay - Problem: bad sound quality<br />
* Satellite phone - Problem: expensive, quality not as good<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMRNB - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol - good jitterbuffer that can be tweaked for dealing with packet loss/latency<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Two serial MELPe hardware modules $1000 (This could be way off)<br />
* Far end server colocation $400/month<br />
* Total: $6200<br />
* Recurring: $400 per month plus cost of minutes<br />
* Doesn't include wiring because that depends entirely on the layout of the structure.<br />
* Amplifiers will be necessary in some situations.<br />
<br />
This scheme supports 24 POTS lines. One could fit 3 or 4 of those cards in each server, so it scales pretty well.<br />
<br />
Obviously, the rack and UPS can be avoided if space is already provided by existing infrastructure. I leave it in here for the purpose of offering a complete solution.<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Bluetooth (cough) security<br />
* VoIP security not all that great in the open source world, but reasonable security can be achieved.<br />
<br />
== Instructions ==<br />
* Build servers. Insert Digium card/s.<br />
* Load the ups/servers/patch panels into the rack.<br />
* Connect power; connect servers to switch<br />
* Load Debian or Ubuntu Server onto the servers.<br />
* [http://www.voip-info.org/tiki-index.php?page=Asterisk+Linux+Debian Follow these instructions] - Easy if you've done it a few times.<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf Follow these instructions] - Have a friend nearby to take your aggression out on.<br />
* Call Digium to purchase g729 licenses. They'll help with installation as well.<br />
* Install my MELPe hacks.<br />
* Install your favorite billing/provisioning software.<br />
* Connect the system to the LAN/WAN<br />
* Order a dedicated server, nothing special.<br />
* Install Debian, then Asterisk, like we did before<br />
* Have colo personnel install MELPe hardware, then install MELPe hacks<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+iax.conf Follow these instructions] to connect to the colo server<br />
* Subscribe to server per minute voip providers and configure them on the dedicated server<br />
* Connect to them via _X.,1,Dial(sip/myprovider/${EXTEN})<br />
<br />
Using a colo is avoidable if enough bandwidth is available. Will TSI one day be the termination point for HF?</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=467User:Heath/PBX2008-05-31T18:13:06Z<p>75.94.154.157: /* Instructions */</p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
Current version doesn't do GSM. Mainly because I have no idea how to do it. Don't know how to do the bluetooth stuff either.<br />
<br />
The only thing on here that's going to be non-obvious to the person familiar to Asterisk is the MELP stuff. Basically MELP is a 2400bps codec. It's very similar to LPC10 except you don't sound like a robot. The quality is pretty good. I wouldn't mind using it for all of my calls. Using MELP with IAX2 makes for a very low bandwidth channel. In trunking mode, IAX2 only has protocol overhead on the first 1 or 2 calls. After that, it starts to become trivial. Since LPC10 and Asterisk are so similar, Asterisk can be tricked into thinking that MELP is actually LPC10. Using the reference code, I've gotten a codec_melp to load, but it just crashes. Unfortunately, this isn't an ultimate solution because the code I did (making the reference code reentrant) can't be released into the wild. That would be beyond "purely philosophical" inquiry and Compandent (the patent holder) could sue me into oblivion. Fortunately, they sell serial modules that can do multiple MELP channels.<br />
<br />
== Why all the trouble with MELP? ==<br />
Without MELP, there are other options.<br />
* LPC10 - Problem: makes you sound like a robot... it's pretty scary<br />
* g723.1 (still using VoIP) - Problem: doubles the amount of bandwidth needed<br />
* HF phone relay - Problem: bad sound quality<br />
* Satellite phone - Problem: expensive, quality not as good<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMRNB - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol - good jitterbuffer that can be tweaked for dealing with packet loss/latency<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Two serial MELPe hardware modules $1000 (This could be way off)<br />
* Far end server colocation $400/month<br />
* Total: $6200<br />
* Recurring: $400 per month plus cost of minutes<br />
* Doesn't include wiring because that depends entirely on the layout of the structure.<br />
* Amplifiers will be necessary in some situations.<br />
<br />
This scheme supports 24 POTS lines. One could fit 3 or 4 of those cards in each server, so it scales pretty well.<br />
<br />
Obviously, the rack and UPS can be avoided if space is already provided by existing infrastructure. I leave it in here for the purpose of offering a complete solution.<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Bluetooth (cough) security<br />
* VoIP security not all that great in the open source world, but reasonable security can be achieved.<br />
<br />
== Instructions ==<br />
* Build servers. Insert Digium card/s.<br />
* Load the ups/servers/patch panels into the rack.<br />
* Connect power; connect servers to switch<br />
* Load Debian or Ubuntu Server onto the servers.<br />
* [http://www.voip-info.org/tiki-index.php?page=Asterisk+Linux+Debian Follow these instructions] - Easy if you've done it a few times.<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf Follow these instructions] - Have a friend nearby to take your aggression out on.<br />
* Call Digium to purchase g729 licenses. They'll help with installation as well.<br />
* Install my MELPe hacks.<br />
* Install your favorite billing software<br />
* Connect the system to the LAN/WAN<br />
* Order a dedicated server, nothing special.<br />
* Install Debian, then Asterisk, like we did before<br />
* Have colo personnel install MELPe hardware, then install MELPe hacks<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+iax.conf Follow these instructions] to connect to the colo server<br />
* Subscribe to server per minute voip providers and configure them on the dedicated server<br />
* Connect to them via _X.,1,Dial(sip/myprovider/${EXTEN})<br />
<br />
Using a colo is avoidable if enough bandwidth is available. Will TSI one day be the termination point for HF?</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=466User:Heath/PBX2008-05-31T17:32:02Z<p>75.94.154.157: </p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
Current version doesn't do GSM. Mainly because I have no idea how to do it. Don't know how to do the bluetooth stuff either.<br />
<br />
The only thing on here that's going to be non-obvious to the person familiar to Asterisk is the MELP stuff. Basically MELP is a 2400bps codec. It's very similar to LPC10 except you don't sound like a robot. The quality is pretty good. I wouldn't mind using it for all of my calls. Using MELP with IAX2 makes for a very low bandwidth channel. In trunking mode, IAX2 only has protocol overhead on the first 1 or 2 calls. After that, it starts to become trivial. Since LPC10 and Asterisk are so similar, Asterisk can be tricked into thinking that MELP is actually LPC10. Using the reference code, I've gotten a codec_melp to load, but it just crashes. Unfortunately, this isn't an ultimate solution because the code I did (making the reference code reentrant) can't be released into the wild. That would be beyond "purely philosophical" inquiry and Compandent (the patent holder) could sue me into oblivion. Fortunately, they sell serial modules that can do multiple MELP channels.<br />
<br />
== Why all the trouble with MELP? ==<br />
Without MELP, there are other options.<br />
* LPC10 - Problem: makes you sound like a robot... it's pretty scary<br />
* g723.1 (still using VoIP) - Problem: doubles the amount of bandwidth needed<br />
* HF phone relay - Problem: bad sound quality<br />
* Satellite phone - Problem: expensive, quality not as good<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMRNB - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol - good jitterbuffer that can be tweaked for dealing with packet loss/latency<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Two serial MELPe hardware modules $1000 (This could be way off)<br />
* Far end server colocation $400/month<br />
* Total: $6200<br />
* Recurring: $400 per month plus cost of minutes<br />
* Doesn't include wiring because that depends entirely on the layout of the structure.<br />
* Amplifiers will be necessary in some situations.<br />
<br />
This scheme supports 24 POTS lines. One could fit 3 or 4 of those cards in each server, so it scales pretty well.<br />
<br />
Obviously, the rack and UPS can be avoided if space is already provided by existing infrastructure. I leave it in here for the purpose of offering a complete solution.<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Bluetooth (cough) security<br />
* VoIP security not all that great in the open source world, but reasonable security can be achieved.<br />
<br />
== Instructions ==<br />
* Build servers. Insert Digium card/s.<br />
* Load the ups/servers/patch panels into the rack.<br />
* Connect power; connect servers to switch<br />
* Load Debian or Ubuntu Server onto the servers.<br />
* [http://www.voip-info.org/tiki-index.php?page=Asterisk+Linux+Debian Follow these instructions] - Easy if you've done it a few times.<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf Follow these instructions] - Have a friend nearby to take your aggression out on.<br />
* Install my MELPe hacks.<br />
* Install your favorite billing software<br />
* Connect the system to the LAN/WAN<br />
* Order a dedicated server, nothing special.<br />
* Install Debian, then Asterisk, like we did before<br />
* Have colo personnel install MELPe hardware, then install MELPe hacks<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+iax.conf Follow these instructions] to connect to the colo server<br />
* Subscribe to server per minute voip providers and configure them on the dedicated server<br />
* Connect to them via _X.,1,Dial(sip/myprovider/${EXTEN})<br />
<br />
Using a colo is avoidable if enough bandwidth is available. Will TSI one day be the termination point for HF?</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=465User:Heath/PBX2008-05-31T17:21:58Z<p>75.94.154.157: /* Security */</p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
Current version doesn't do GSM. Mainly because I have no idea how to do it. Don't know how to do the bluetooth stuff either.<br />
<br />
The only thing on here that's going to be non-obvious to the person familiar to Asterisk is the MELP stuff. Basically MELP is a 2400bps codec. It's very similar to LPC10 except you don't sound like a robot. The quality is pretty good. I wouldn't mind using it for all of my calls. Using MELP with IAX2 makes for a very low bandwidth channel. In trunking mode, IAX2 only has protocol overhead on the first 1 or 2 calls. After that, it starts to become trivial. Since LPC10 and Asterisk are so similar, Asterisk can be tricked into thinking that MELP is actually LPC10. Using the reference code, I've gotten a codec_melp to load, but it just crashes. Unfortunately, this isn't an ultimate solution because the code I did (making the reference code reentrant) can't be released into the wild. That would be beyond "purely philosophical" inquiry and Compandent (the patent holder) could sue me into oblivion. Fortunately, they sell serial modules that can do multiple MELP channels.<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMRNB - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Two serial MELPe hardware modules $1000 (This could be way off)<br />
* Far end server colocation $400/month<br />
* Total: $6200<br />
* Recurring: $400 per month plus cost of minutes<br />
* Doesn't include wiring because that depends entirely on the layout of the structure.<br />
* Amplifiers will be necessary in some situations.<br />
<br />
This scheme supports 24 POTS lines. One could fit 3 or 4 of those cards in each server, so it scales pretty well.<br />
<br />
Obviously, the rack and UPS can be avoided if space is already provided by existing infrastructure. I leave it in here for the purpose of offering a complete solution.<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Bluetooth (cough) security<br />
* VoIP security not all that great in the open source world, but reasonable security can be achieved.<br />
<br />
== Instructions ==<br />
* Build servers. Insert Digium card/s.<br />
* Load the ups/servers/patch panels into the rack.<br />
* Connect power; connect servers to switch<br />
* Load Debian or Ubuntu Server onto the servers.<br />
* [http://www.voip-info.org/tiki-index.php?page=Asterisk+Linux+Debian Follow these instructions] - Easy if you've done it a few times.<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf Follow these instructions] - Have a friend nearby to take your aggression out on.<br />
* Install my MELPe hacks.<br />
* Install your favorite billing software<br />
* Connect the system to the LAN/WAN<br />
* Order a dedicated server, nothing special.<br />
* Install Debian, then Asterisk, like we did before<br />
* Have colo personnel install MELPe hardware, then install MELPe hacks<br />
* [http://www.voip-info.org/wiki/index.php?page=Asterisk+config+iax.conf Follow these instructions] to connect to the colo server<br />
* Subscribe to server per minute voip providers and configure them on the dedicated server<br />
* Connect to them via _X.,1,Dial(sip/myprovider/${EXTEN})<br />
<br />
Using a colo is avoidable if enough bandwidth is available. Will TSI one day be the termination point for HF?</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=431User:Heath/PBX2008-05-30T22:30:59Z<p>75.94.154.157: </p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMR - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Far end server colocation $400/month<br />
<br />
== Dependencies ==<br />
* Existing network/Internet<br />
* Cool/dry/secure area<br />
* ~1000 watts available power<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Not all that great in the open source world, but reasonable security can be achieved.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=430User:Heath/PBX2008-05-30T22:23:29Z<p>75.94.154.157: /* Equipment/Costs */</p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMR - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
* Far end server colocation $400/month<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Not all that great in the open source world, but reasonable security can be achieved.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=429User:Heath/PBX2008-05-30T22:16:59Z<p>75.94.154.157: /* Useful protocols */</p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMR - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX2 - Lightweight VoIP protocol<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Not all that great in the open source world, but reasonable security can be achieved.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=428User:Heath/PBX2008-05-30T22:16:31Z<p>75.94.154.157: /* Compression */ stupid error</p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade compression for minimizing bandwidth consumption<br />
* AMR - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX - Lightweight VoIP protocol<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Not all that great in the open source world, but reasonable security can be achieved.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=427User:Heath/PBX2008-05-30T20:17:21Z<p>75.94.154.157: /* Security */</p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade encryption for minimizing bandwidth consumption<br />
* AMR - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX - Lightweight VoIP protocol<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* IAX2 has an aes128 option<br />
* Not all that great in the open source world, but reasonable security can be achieved.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:Heath/PBX&diff=426User:Heath/PBX2008-05-30T20:11:16Z<p>75.94.154.157: </p>
<hr />
<div>{{Proposal}}<br />
This is probably the only area that I can call myself an expert in.<br />
<br />
Asterisk can be made to build a tricked out phone system of any size at a trivial cost.<br />
<br />
Ultimately, this page will be a set of config files, patches and dependencies for building such a system.<br />
<br />
== Compression ==<br />
* MELP/MELPe - Military grade encryption for minimizing bandwidth consumption<br />
* AMR - What cellphones use<br />
* g723.1/g729 - What voip phones use<br />
* iLBC/speex - Open source low-bitrate codecs<br />
<br />
== Useful protocols ==<br />
* Bluetooth will be implemented via chan_bluetooth or chan_cellphone<br />
* GSM will be implemented with a commercial gateway.<br />
* Regular POTS service can be done using hardware<br />
* SIP - VoIP protocol<br />
* IAX - Lightweight VoIP protocol<br />
<br />
== Equipment/Costs ==<br />
* At least a P4 2.4 2GB server with a focus on reliability (solid disk, passive cooling if possible) $1000<br />
* Backup server/load balancer $1000<br />
* Half decent switch $300<br />
* Digium AEX2460E Analog Card 6x4 FXS + Echo can $1800<br />
* g729 licenses $100<br />
* 20U Rack $500<br />
* Rackmount UPS $500<br />
<br />
== Asterisk ==<br />
* Used to switch calls<br />
* Used to translate between various protocols<br />
* Used to perform IVR functionality such as voicemail<br />
<br />
== Security ==<br />
* Not all that great in the open source world, but reasonable security can be achieved.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Photovoltaics&diff=425Photovoltaics2008-05-30T19:40:20Z<p>75.94.154.157: /* Tracking */</p>
<hr />
<div>Photovoltaics is a technology that converts sunlight into electricity. Over the last few years they have become much more efficient and when used in locations with lots of sun can be used to power a normal sized American home almost year around.<br />
<br />
== Typical Module ==<br />
* 190 watts<br />
* 61.8" x 37.5"<br />
* 127 watts/m^2<br />
* $900~<br />
* $4.70/watt~<br />
<br />
Actual performance obviously depends on the amount sunlight it gets. Some need direct sunlight before the voltage gets close to peak performance. Mono-crystalline modules are better at squeezing out more power in less than ideal conditions.<br />
<br />
== Tracking ==<br />
Many off-the-shelf systems exists for tracking the sun for maximum efficiency. A typical tracker arranges several modules in an array, and the surface pivots on a pole not unlike a sunflower.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Proposals&diff=197Proposals2008-05-28T20:59:36Z<p>75.94.154.157: New page: If you wish to share a specific implementation of a seastead component, or perhaps and entire platform, create the page under your username, then link to it from here from the appropriate ...</p>
<hr />
<div>If you wish to share a specific implementation of a seastead component, or perhaps and entire platform, create the page under your username, then link to it from here from the appropriate category.<br />
<br />
For example, if you have a plan for a complete hybrid power system, create a page called "User:MyUsername/10_Kilowatt_Integrated_Power_System"<br />
<br />
== Etiquette ==<br />
User design pages should be left to the original creator. Only make changes for things like spelling/math, and only if you're sure you're right.<br />
<br />
Otherwise, criticize or comment on the proposal in the articles talk page.<br />
<br />
== Content ==<br />
Example layout<br />
* Overview - Describe the system you've designed.<br />
* Conditional Requirements - e.g. "This power system requires the platform to be very stable."<br />
* Costs - Breakdown of cost estimates and a total if possible.<br />
* Material Availability - Where to get the items necessary for the system.<br />
<br />
== Structures ==<br />
* [[User:Joep/PillarStead]]<br />
<br />
== Power Systems ==</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Energy_Storage&diff=191Energy Storage2008-05-28T20:40:54Z<p>75.94.154.157: Copypasta'd a bunch of stuff from the book</p>
<hr />
<div>For now, the most mature technology for storing energy appears to be electrochemical batteries. While they are expensive, the alternatives (flywheels, ultracapacitors, redox batteries, creating hydrogen to power fuel cells) are generally still experimental. However, redox batteries are rapidly approaching usefulness.<br />
<br />
== Electrochemical Batteries ==<br />
<br />
== Vanadium Redox Batteries ==<br />
<br />
== Hydrides ==<br />
<br />
== Flywheels ==<br />
<br />
== Supercapacitors ==<br />
<br />
== Gravity Battery ==<br />
<br />
== Hydrogen ==</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Main_Page&diff=186Main Page2008-05-28T20:36:57Z<p>75.94.154.157: /* Energy */</p>
<hr />
<div>Welcome! Please start with [[About the Seasteading Wiki]]. Much more information can be found in [http://seasteading.org/seastead.org/commented/paper/index.html Seasteading: A Practical Guide to Homesteading the High Seas].<br />
[[Image:Seastead.jpg|right|175px]]<br />
==Ocean environment==<br />
* [[Wave|Waves]]<br />
* [[Current]]<br />
* [[Wind]]<br />
* [[Politics]]<br />
* [[Piracy]]<br />
* [[Biofouling]]<br />
<br />
==Structure designs==<br />
* [[Structure requirements]]<br />
* [[PintStead]]<br />
* [[Spar]]<br />
* [[Transportation]]<br />
* [[Floors]]<br />
* [[Recycled Plastic Bottles]]<br />
* [[Pictures]]<br />
<br />
==Energy==<br />
* [[Growing algae]] <br />
* [[Wind turbines]] <br />
* [[Photovoltaics]] <br />
* [[Nuclear]]<br />
* [[OTEC]]<br />
* [[Wave Power]]<br />
* [[Energy Storage]]<br />
<br />
==Infrastructure==<br />
* [[Fresh water]]<br />
* [[Food]] <br />
* [[Government]]<br />
* [[Shelter]]<br />
* [[Communications]]<br />
* [[Medical and Health Care]]<br />
* [[Small Scale Medicine]]<br />
* [[Defense]]<br />
* [[Waste Disposal]]<br />
* [[Appliances]]<br />
* [[Facilities]]<br />
* [[Transportation Modalities]]<br />
* [[Environment, Health and Safety]]<br />
<br />
==The Market==<br />
* [[Other projects]]<br />
* [[Seastead ventures]]<br />
* [[Publicity]]<br />
* [[Cost of building BayStead]]<br />
<br />
==Locations==<br />
* [[San Francisco Bay]]<br />
* [[Mediterranean Sea]]<br />
* [[South China Sea]]<br />
* [[South Pacific]]<br />
* [[Australia]]<br />
* [[New Zealand]]</div>75.94.154.157https://wiki.seasteading.org/index.php?title=User:75.94.154.157&diff=163User:75.94.154.1572008-05-28T17:53:26Z<p>75.94.154.157: New page: I'm User:heath when I forget to login.</p>
<hr />
<div>I'm [[User:heath]] when I forget to login.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Small_Scale_Medicine&diff=162Small Scale Medicine2008-05-28T17:51:42Z<p>75.94.154.157: </p>
<hr />
<div>Single platforms and smaller communities will have to make compromises.<br />
<br />
== Literature ==<br />
* The WHO publishes tons of information on this.<br />
<br />
{{stub}}</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Small_Scale_Medicine&diff=161Small Scale Medicine2008-05-28T17:49:43Z<p>75.94.154.157: New page: Single platforms and smaller communities will have to make compromises. {{stub}}</p>
<hr />
<div>Single platforms and smaller communities will have to make compromises.<br />
<br />
{{stub}}</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Main_Page&diff=160Main Page2008-05-28T17:45:55Z<p>75.94.154.157: /* Infrastructure */</p>
<hr />
<div>Welcome! Please start with [[About the Seasteading Wiki]]. Much more information can be found in [http://seasteading.org/seastead.org/commented/paper/index.html Seasteading: A Practical Guide to Homesteading the High Seas].<br />
[[Image:Seastead.jpg|right|175px]]<br />
==Ocean environment==<br />
* [[Wave|Waves]]<br />
* [[Current]]<br />
* [[Wind]]<br />
* [[Politics]]<br />
* [[Piracy]]<br />
* [[Biofouling]]<br />
<br />
==Structure designs==<br />
* [[PintStead]]<br />
* [[Spar]]<br />
* [[Transportation]]<br />
* [[Floors]]<br />
* [[Recycled Plastic Bottles]]<br />
* [[Pictures]]<br />
<br />
==Energy==<br />
* [[Growing algae]] <br />
* [[Wind turbines]] <br />
* [[Photovoltaics]] <br />
* [[Nuclear]]<br />
* [[OTEC]]<br />
* [[Wave Power]]<br />
<br />
==Infrastructure==<br />
* [[Fresh water]]<br />
* [[Food]] <br />
* [[Government]]<br />
* [[Shelter]]<br />
* [[Communications]]<br />
* [[Medical and Health Care]]<br />
* [[Small Scale Medicine]]<br />
* [[Defense]]<br />
* [[Waste Disposal]]<br />
* [[Appliances]]<br />
* [[Facilities]]<br />
* [[Transportation Modalities]]<br />
* [[Environment, Health and Safety]]<br />
<br />
==The Market==<br />
* [[Other projects]]<br />
* [[Seastead ventures]]<br />
* [[Publicity]]<br />
* [[Cost of building BayStead]]<br />
<br />
==Locations==<br />
* [[San Francisco Bay]]<br />
* [[Mediterranean Sea]]<br />
* [[South China Sea]]<br />
* [[South Pacific]]<br />
* [[Australia]]<br />
* [[New Zealand]]</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Talk:Transportation&diff=129Talk:Transportation2008-05-28T08:17:17Z<p>75.94.154.157: New page: A section about helipad standards would be really useful. ~~~~</p>
<hr />
<div>A section about helipad standards would be really useful. [[Special:Contributions/75.94.154.157|75.94.154.157]] 08:17, 28 May 2008 (UTC)</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Photovoltaics&diff=128Photovoltaics2008-05-28T08:11:19Z<p>75.94.154.157: </p>
<hr />
<div>Photovoltaics is a technology that converts sunlight into electricity. Over the last few years they have become much more efficient and when used in locations with lots of sun can be used to power a normal sized American home almost year around.<br />
<br />
== Typical Module ==<br />
* 190 watts<br />
* 61.8" x 37.5"<br />
* 127 watts/m^2<br />
* $900~<br />
* $4.70/watt~<br />
<br />
Actual performance obviously depends on the amount sunlight it gets. Some need direct sunlight before the voltage gets close to peak performance. Mono-crystalline modules are better at squeezing out more power in less than ideal conditions.<br />
<br />
== Tracking ==<br />
Many off-the-shelf systems exists for tracking the sun for maximum efficiency. A typical tracker arranges several modules in a circular shape, and the surface pivots on a pole not unlike a sunflower.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Medical_and_Health_Care&diff=127Medical and Health Care2008-05-26T18:37:55Z<p>75.94.154.157: </p>
<hr />
<div>'''Need for Medical Capability'''<br />
<br />
Due to the isolation of the SeaScape (at least part of the time), evacuation of the injured may not be feasible. Further, the potential for a medical disaster such as a fire, or aircraft crash, must be considered. Hyperbaric oxygen therapy should be available for treatment of diving injuries and other appropriate injuries.<br />
<br />
For example, if the SeaStead was off the coast West Africa (say, Angola) the nearest large cities would be Luanda, Angola; Kinshasa, Congo (Zaire); and Windhoek, Namibia - none of which could handle a severe accident or illness, at least not with first-world medicine. Further, it's possible that all three cities would be beyond flight range of any aircraft onboard. For this reason, the SeaScape needs to be self-sufficient medically.<br />
<br />
Health and Medical facilities, and care, will have to adapt to the numbers of people in the SeaStead, and their relative risk factors (ie, workers will require more trauma than retirees, who will require more long-term monitoring).<br />
<br />
<br />
'''Potential for Revenue Generation'''<br />
<br />
One potential income stream for a SeaStead is specialty medical treatment clinics, a sort of medical tourism. Facilities for this would fall into the commercial realm and are not discussed here.<br />
== General Requirements ==<br />
<br />
Medical facilities should be located centrally, but don't require prime locations such as ocean views. If possible, they should be located where motion of the structure is minimized. Power requirements will have to be accommodated, for imaging technologies (Xray, CT scan, MRI, etc) and airflow must be controlled to afford isolation in the event of an infectious disease. Dental care will be required in addition to medical care. <br />
<br />
Disposal of medical waste (biohazards) will be required.<br />
<br />
All willing residents would be examined (including blood-typing) in the event that blood transfusions would be necessary. Rather than stock (and dispose of unused) blood products, the use of 'walking donors' will provide the required levels of blood.<br />
<br />
<br />
== Technology ==<br />
<br />
Electronic records exclusively will be maintained, so no chart storage areas will be necessary. All medical spaces will require network access. All medical personnel must be available by page at all times in the event of an emergency. Suitable workstations (tablets, micro-computers, interfaces to monitors and pharmacy dispensing machine (pixis), access to imaging studies (pacs), access to lab reports, etc will be necessary, but will also have to be secure. An automated inventory system for medical supplies, with interfaces to a resupply (ordering) system is needed.<br />
<br />
Automated lab equipment would provide a low-manpower method of blood and urine chemistry, microbiology lab services, etc.<br />
<br />
In addition to the on-site medical personnel, high-bandwidth connectivity with 3-D cameras should be available for telemedicine. While various imaging modalities will be available (X-ray, CT, MRI, Ultrasound) these will be examined by qualified radiologists via telemedicine. <br />
<br />
<br />
<br />
== '''Required Staffing - Full Time''' ==<br />
<br />
With an estimated 10,000 person population, the following medical professionals might be needed:<br />
<br />
Family Physician (Internal medicine, OB/GYN, Pediatrics)<br />
<br />
Emergency Physician (doubles as general physician), hyperbaric medicine qualified.<br />
<br />
Physician Assistants (2) (General Medicine)<br />
<br />
In addition to the full-time staffing certain specialties may be needed only sometimes (say, for a two-week period every quarter). Such specialties include Cardiology, Nephrology, Dermatology, Ophthalmology/Optometry, etc.<br />
<br />
<br />
== Surgical Staff ==<br />
Because there would (hopefully) not be a need for extensive surgical coverage, full-time resident surgeons would be difficult to retain (due to lost skills from inactivity). However, surgical coverage is necessary at least part-time, when the SeaStead is out of range of acceptable medical facilities. This coverage would necessarily include:<br />
<br />
A general (thoracic) surgeon, who could also assists on orthopedic surgery, and an <br />
<br />
Orthopedic surgeon, who could assist on general surgery.<br />
<br />
Also required would be two anesthesiologists (MD) or nurse-anesthesiologists (CRNA), and two surgical nurses. Should surgery be necessary the other physicians or physician-assistants could assist as necessary.<br />
<br />
<br />
== Dental Care ==<br />
A patient population of 10,000 would require two full-time dentists, with an assistant each, and dental lab capacity. <br />
Dentists (2)<br />
<br />
Dental Assistant (2) with lab capabilities<br />
<br />
<br />
== Other Medical Staff ==<br />
<br />
General Nurse (phlebotomist, X-ray tech)<br />
<br />
CT / MRI Technician<br />
<br />
Pharmacy Technician (operating under a physicians license)<br />
<br />
Medical Assistant (4)<br />
<br />
Firefighter / Paramedics (6-8) with expanded or full scope of practice. These can be dual-trained firefighter/paramedics with specialty training in dive rescue/recovery. All should also be qualified as hyperbaric chamber attendants and at least three should be hyperbaric chamber operators<br />
<br />
Medical Administrator / Office Manager<br />
<br />
<br />
==Medical Space Requirements==<br />
<br />
<br />
Waiting Area<br />
<br />
Medical Exam Rooms (2)<br />
<br />
Medical Procedures Room<br />
<br />
Birthing suite (dependent on population)<br />
<br />
Casting room (it's messy)<br />
<br />
Dental Exam rooms (2) and Dental Xray room, Dental Lab (also very messy)<br />
<br />
Optometric exam room (with slit lamp, etc).<br />
<br />
X-Ray (should be portable and digital)<br />
<br />
CT scanner (requires shielding)<br />
<br />
MRI scanner (requires shielding)<br />
<br />
Hyperbaric Chamber (at least 4-place)<br />
<br />
Laboratory (wet lab equipment)<br />
<br />
Pharmacy <br />
<br />
Surgical suites (2)<br />
<br />
Scrub room<br />
<br />
Surgical changing room, rest room and shower<br />
<br />
Surgical supply room<br />
<br />
General supply room (in medical area) with space for mechical systems (medical oxygen concentrator, medical suction, etc) and storage for rapidly needed supplies. <br />
<br />
Rest room (male, female)<br />
<br />
Ward areas (two, five beds each, with rest rooms including shower and bath)<br />
<br />
Utility Room (contaminated storage)<br />
<br />
Storage area (inactive storage of approximately 3800 cubic feet (107 cubic meters)(approximately the size of a large ISO shipping container) - SWAG<br />
<br />
== External Links ==<br />
[http://www.who.int/topics/essential_medicines/en/ WHO List of Essential Medicines]</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Communications&diff=126Communications2008-05-26T16:00:28Z<p>75.94.154.157: /* Internal */</p>
<hr />
<div>== Internal ==<br />
<br />
'''Wireless phone system -'''<br />
<br />
'''Paging system -''' <br />
"Smart system" where everyone wears a transponder so the communications system knows where to page/ring you?<br />
<br />
'''Fire/Life Safety systems''' - Detection and Warning<br />
<br />
'''Entertainment -''' Internal Fiberoptic network to move large quantities of data - movies, etc? Cable TV analog<br />
<br />
== External ==<br />
<br />
'''Satellite Communications'''<br />
<br />
'''Internet'''<br />
<br />
'''Phone -''' HF Radio using PPP with VOIP/IAX2/MELPe would be extremely cumbersome to setup, but is doable (might require bonding which makes it even crazier). MELPe is a military codec operating at 600/1200/2400 bps. With PPP/IAX2 you have very little networking overhead. The quality of MELP is hard to describe, but with carefully tweaked jitterbuffer settings, cell phone quality should be possible. The advantage is that you avoid the annoying lag. This setup would require an extremely hacked Asterisk.<br />
<br />
<br />
'''Satellite Entertainment''' TV/Radio<br />
<br />
Multiple dishes?<br />
<br />
'''High Frequency Radio''' - 2-30MHz<br />
<br />
Worldwide Coverage, very large antennas (30+ meters long, or longer?)<br />
<br />
Possible 'Pirate' Radio Station(s)?<br />
<br />
'''GMDSS System''' <br />
Global Maritime Distress Signal System, SOLAS requirement<br />
<br />
'''VHF-FM Radio Marine Band 156-158 MHz'''<br />
SOLAS requirements to maintain a listening watch on distress frequencies<br />
<br />
Coordinate small boat activities around SeaStead, each small boat equipped with one of these too. <br />
<br />
Relatively small radios, low power (~25w ERP), small antennas (2 meters or less in length, max. Handhelds ~8" long)<br />
<br />
'''VHF-AM Radio Aircraft Band 118-136MHz'''<br />
<br />
Coordinating air traffic inbound and outbound.<br />
<br />
Several frequencies: Departure/Approach, Tower (landing), Ground (ground movement), coordination frequencies<br />
<br />
Air Traffic Control radar<br />
<br />
Air Navigation aids? [http://en.wikipedia.org/wiki/VHF_omnidirectional_range VOR]/[http://en.wikipedia.org/wiki/Distance_measuring_equipment DME]/ [http://en.wikipedia.org/wiki/TACAN TACAN] or rely on [http://en.wikipedia.org/wiki/GPS GPS]?<br />
<br />
<br />
'''Tactical Radios - Trunked 800 MHz systems'''? Used for: <br />
<br />
Firefighting / EMS<br />
<br />
Maintenance<br />
<br />
Defense<br />
<br />
Law Enforcement?<br />
<br />
Need to investigate frequency propagation through structures. <br />
<br />
<br />
'''Other radios''' - Ability to monitor/speak on military frequencies, ie <br />
<br />
30-70 MHz FM (Military Tactical Net);<br />
<br />
220-400 MHz AM (Military aviation band), etc?<br />
<br />
"Company" radios for SeaStead operations, similar to business-band frequencies (VHF-FM High at 150MHz or UHF-FM at 450-470MHz and/or [http://en.wikipedia.org/wiki/Trunked_radio_system 800 MHz trunked system]. Will probably require robust encryption.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Communications&diff=125Communications2008-05-26T16:00:13Z<p>75.94.154.157: /* External */</p>
<hr />
<div>== Internal ==<br />
<br />
'''Wireless phone system -'''<br />
HF Radio using PPP with VOIP/IAX2/MELPe would be extremely cumbersome to setup, but is doable (might require bonding which makes it even crazier). MELPe is a military codec operating at 600/1200/2400 bps. With PPP/IAX2 you have very little networking overhead. The quality of MELP is hard to describe, but with carefully tweaked jitterbuffer settings, cell phone quality should be possible. The advantage is that you avoid the annoying lag. This setup would require an extremely hacked Asterisk.<br />
<br />
'''Paging system -''' <br />
"Smart system" where everyone wears a transponder so the communications system knows where to page/ring you?<br />
<br />
'''Fire/Life Safety systems''' - Detection and Warning<br />
<br />
'''Entertainment -''' Internal Fiberoptic network to move large quantities of data - movies, etc? Cable TV analog<br />
<br />
== External ==<br />
<br />
'''Satellite Communications'''<br />
<br />
'''Internet'''<br />
<br />
'''Phone -''' HF Radio using PPP with VOIP/IAX2/MELPe would be extremely cumbersome to setup, but is doable (might require bonding which makes it even crazier). MELPe is a military codec operating at 600/1200/2400 bps. With PPP/IAX2 you have very little networking overhead. The quality of MELP is hard to describe, but with carefully tweaked jitterbuffer settings, cell phone quality should be possible. The advantage is that you avoid the annoying lag. This setup would require an extremely hacked Asterisk.<br />
<br />
<br />
'''Satellite Entertainment''' TV/Radio<br />
<br />
Multiple dishes?<br />
<br />
'''High Frequency Radio''' - 2-30MHz<br />
<br />
Worldwide Coverage, very large antennas (30+ meters long, or longer?)<br />
<br />
Possible 'Pirate' Radio Station(s)?<br />
<br />
'''GMDSS System''' <br />
Global Maritime Distress Signal System, SOLAS requirement<br />
<br />
'''VHF-FM Radio Marine Band 156-158 MHz'''<br />
SOLAS requirements to maintain a listening watch on distress frequencies<br />
<br />
Coordinate small boat activities around SeaStead, each small boat equipped with one of these too. <br />
<br />
Relatively small radios, low power (~25w ERP), small antennas (2 meters or less in length, max. Handhelds ~8" long)<br />
<br />
'''VHF-AM Radio Aircraft Band 118-136MHz'''<br />
<br />
Coordinating air traffic inbound and outbound.<br />
<br />
Several frequencies: Departure/Approach, Tower (landing), Ground (ground movement), coordination frequencies<br />
<br />
Air Traffic Control radar<br />
<br />
Air Navigation aids? [http://en.wikipedia.org/wiki/VHF_omnidirectional_range VOR]/[http://en.wikipedia.org/wiki/Distance_measuring_equipment DME]/ [http://en.wikipedia.org/wiki/TACAN TACAN] or rely on [http://en.wikipedia.org/wiki/GPS GPS]?<br />
<br />
<br />
'''Tactical Radios - Trunked 800 MHz systems'''? Used for: <br />
<br />
Firefighting / EMS<br />
<br />
Maintenance<br />
<br />
Defense<br />
<br />
Law Enforcement?<br />
<br />
Need to investigate frequency propagation through structures. <br />
<br />
<br />
'''Other radios''' - Ability to monitor/speak on military frequencies, ie <br />
<br />
30-70 MHz FM (Military Tactical Net);<br />
<br />
220-400 MHz AM (Military aviation band), etc?<br />
<br />
"Company" radios for SeaStead operations, similar to business-band frequencies (VHF-FM High at 150MHz or UHF-FM at 450-470MHz and/or [http://en.wikipedia.org/wiki/Trunked_radio_system 800 MHz trunked system]. Will probably require robust encryption.</div>75.94.154.157https://wiki.seasteading.org/index.php?title=Communications&diff=124Communications2008-05-26T15:57:53Z<p>75.94.154.157: /* Internal */</p>
<hr />
<div>== Internal ==<br />
<br />
'''Wireless phone system -'''<br />
HF Radio using PPP with VOIP/IAX2/MELPe would be extremely cumbersome to setup, but is doable (might require bonding which makes it even crazier). MELPe is a military codec operating at 600/1200/2400 bps. With PPP/IAX2 you have very little networking overhead. The quality of MELP is hard to describe, but with carefully tweaked jitterbuffer settings, cell phone quality should be possible. The advantage is that you avoid the annoying lag. This setup would require an extremely hacked Asterisk.<br />
<br />
'''Paging system -''' <br />
"Smart system" where everyone wears a transponder so the communications system knows where to page/ring you?<br />
<br />
'''Fire/Life Safety systems''' - Detection and Warning<br />
<br />
'''Entertainment -''' Internal Fiberoptic network to move large quantities of data - movies, etc? Cable TV analog<br />
<br />
== External ==<br />
<br />
'''Satellite Communications'''<br />
<br />
'''Internet'''<br />
<br />
'''Satellite Entertainment''' TV/Radio<br />
<br />
Multiple dishes?<br />
<br />
'''High Frequency Radio''' - 2-30MHz<br />
<br />
Worldwide Coverage, very large antennas (30+ meters long, or longer?)<br />
<br />
Possible 'Pirate' Radio Station(s)?<br />
<br />
'''GMDSS System''' <br />
Global Maritime Distress Signal System, SOLAS requirement<br />
<br />
'''VHF-FM Radio Marine Band 156-158 MHz'''<br />
SOLAS requirements to maintain a listening watch on distress frequencies<br />
<br />
Coordinate small boat activities around SeaStead, each small boat equipped with one of these too. <br />
<br />
Relatively small radios, low power (~25w ERP), small antennas (2 meters or less in length, max. Handhelds ~8" long)<br />
<br />
'''VHF-AM Radio Aircraft Band 118-136MHz'''<br />
<br />
Coordinating air traffic inbound and outbound.<br />
<br />
Several frequencies: Departure/Approach, Tower (landing), Ground (ground movement), coordination frequencies<br />
<br />
Air Traffic Control radar<br />
<br />
Air Navigation aids? [http://en.wikipedia.org/wiki/VHF_omnidirectional_range VOR]/[http://en.wikipedia.org/wiki/Distance_measuring_equipment DME]/ [http://en.wikipedia.org/wiki/TACAN TACAN] or rely on [http://en.wikipedia.org/wiki/GPS GPS]?<br />
<br />
<br />
'''Tactical Radios - Trunked 800 MHz systems'''? Used for: <br />
<br />
Firefighting / EMS<br />
<br />
Maintenance<br />
<br />
Defense<br />
<br />
Law Enforcement?<br />
<br />
Need to investigate frequency propagation through structures. <br />
<br />
<br />
'''Other radios''' - Ability to monitor/speak on military frequencies, ie <br />
<br />
30-70 MHz FM (Military Tactical Net);<br />
<br />
220-400 MHz AM (Military aviation band), etc?<br />
<br />
"Company" radios for SeaStead operations, similar to business-band frequencies (VHF-FM High at 150MHz or UHF-FM at 450-470MHz and/or [http://en.wikipedia.org/wiki/Trunked_radio_system 800 MHz trunked system]. Will probably require robust encryption.</div>75.94.154.157