Update to page with info public should know to be able to counteract/prevent bad people from accessing your voice mail or tricking you :

http://www.bbc.com/travel/blog/20110725-travellers-vulnerable-to-hacking-of-information w this quote:

..."have you ever wondered how easy it might be for someone to hack into your mobile phone voice mail?

Turns out it’s frighteningly easy. In many cases, all a perpetrator needs is your mobile phone number and a cheap or free “spoofing” service widely available online. (Just google “caller ID spoofing” to learn specifics.)

In a nutshell, caller ID spoofing services make calls appear to be coming from any number a hacker chooses. This means they could use the service to fool your mobile phone voicemail system into thinking that a call is coming from your phone, and potentially providing access to your saved messages."

The BBC article is on the web today 4-Sept-2011 at10:04am;

and this quote from the FCC about how it works [called caller id spoofing]:

"Caller ID service, however, is susceptible to fraud.  Using a practice known as “caller ID spoofing,” callers can deliberately falsify the telephone number and/or name relayed as the Caller ID information to disguise the identity of the calling party.  For example, identity thieves who want to collect sensitive information such as your bank account or other financial account numbers, your social security number, your date of birth or your mother’s maiden name, sometimes use caller ID spoofing to make it appear as though they are calling from your bank, credit card company, or even a government agency."

but spoofing caller id is illegal:

" Quote also from FCC article including the following sections :

 Truth in Caller ID Act of 2009

The Truth in Caller ID Act of 2009, which was signed into law Dec. 22, 2010, prohibits caller ID spoofing for the purposes of defrauding or otherwise causing harm.  In June 2010, The Federal Communications Commission (FCC) adopted rules implementing the Truth in Caller ID Act.

The FCC’s rules:

  • Prohibit any person or entity for transmitting misleading or inaccurate caller ID information with the intent to defraud, cause harm, or wrongfully obtain anything of value.
  • Subject violators to a penalty of up to $10,000 for each violation of the rules..
  • Exempt authorized activities by law enforcement agencies and situations where courts have authorized caller ID manipulation to occur."
  • article at:
  • fcc.gov/guides/caller-id-and-spoofing
  • rest of FCC info:
  • Tips for Consumers
  • Don’t give out personal information in response to an incoming call.  Identity thieves are clever – they often pose as representatives of banks, credit card companies, creditors, or government agencies to get people to reveal their account numbers, Social Security numbers, mother’s maiden names, passwords and other identifying information.
  • If you get an inquiry from a company or government agency seeking personal information, don’t provide it.  Instead, hang up and call the phone number on your account statement, in the phone book, or on the company’s or government agency’s website to find out if the entity that supposedly called you actually needs the requested information from you.
  • Please let the FCC know about ID spoofers by calling 1-888-CALL-FCC or  filing a complaint at fcc.gov/complaints.
  • FCC Caller ID Rules for Telemarketers
  • Even before passage of the Truth in Caller ID Act, FCC rules required telemarketers to pass accurate caller ID information. FCC rules specifically require that a telemarketer:
  • transmit or display its telephone number or the telephone number of the seller on whose behalf the telemarketer is calling, and, if possible, its name or the name and telephone number of the company for which it is selling products or services.
  • display a telephone number that you can call during regular business hours to ask to no longer be called. This rule applies even to companies that already have an established business relationship with you.
  • For violations of these rules, the FCC can seek a monetary fine. If the violator is not an FCC licensee, the FCC must first issue a warning and the telemarketer may be fined only for violations committed after the warning.
  • Rules for Blocking and Unblocking Your Telephone Number
  • The FCC’s Caller ID rules protect the privacy of the person calling by requiring telephone companies to make available free, simple, and uniform per-line blocking and unblocking procedures. These rules give you the choice of delivering or blocking your telephone number for any interstate (between states) call you make. (The FCC does not regulate blocking and unblocking of intrastate calls.)
  • Per-call blocking – To block your phone number and name from appearing on a recipient’s Caller ID unit on a single phone call, dial *67 before dialing the phone number. Your number will not be sent to the other party. You must redial *67 each time you place a new call.
  • Per-line blocking – Some states allow customers to select per-line blocking. With this option, your telephone number will be blocked for every call you make on a specific line – unless you use the per-line unblocking option. If you use per-line blocking and want your number to be transmitted to the called party, dial *82 before you dial the number you are calling. You must re-dial *82 each time you place a call.
  • Blocking your name – Some Caller ID services also transmit the name of the calling party. If you request that your phone number be concealed, FCC rules require that a telephone company also conceal your name.
  • 800 number/toll-free calls – When you dial a toll-free number the party you call is able to identify your telephone number using a telephone network technology called Automatic Number Identification (ANI). Requesting that your caller ID be blocked when you call 800, 888, 877, 866, and 855 numbers may not prevent the people who answer such calls from seeing your phone number and name.  FCC rules, however, prevent parties that own toll-free numbers from reusing or selling the telephone numbers identified through ANI without the subscriber’s consent.
  • Emergency Calls – Telephone companies may transmit numbers of subscribers requesting privacy if the call is to a public agency’s emergency telephone line or in conjunction with 911 or poison control services.
  • Blocking tips for consumers - look before you dial
  • To block your telephone number for any call, dial *67 before dialing the telephone number.
  • To unblock your number for any call (if you have a blocked line), dial *82 before dialing the telephone number.
  • Filing a Complaint
  • If you have caller ID and receive a call from a telemarketer without the required caller ID information, if you suspect that Caller ID information has been falsified, or you think the rules for protecting the privacy of your telephone number have been violated, you can file a complaint with the FCC. There is no charge for filing a complaint. You can file your complaint using an their online website. You can also file your complaint with the FCC’s Consumer Center by calling 1-888-CALL-FCC (1-888-225-5322) voice or 1-888-TELL-FCC (1-888-835-5322) TTY; faxing 1-866-418-0232; or writing to:
  • Federal Communications Commission
  • Consumer & Governmental Affairs Bureau
  • Consumer Inquiries and Complaints Division
  • 445 12th Street, SW
  • Washington, D.C. 20554.
  • The best way to provide all the information the FCC needs to process your complaint is to thoroughly complete the online complaint form. When you open the online complaint form, you will be asked a series of questions that will take you to the particular section of the form you need to complete. If you do not use the online complaint form, your complaint, at a minimum, should indicate:
  • your name, address, email address and phone number where you can be reached;
  • the names and phone numbers of any companies involved with your complaint;
  • the type of service that you are complaining about;
  • the telephone number or account number for any service you are complaining about;
  • the date of any bill you are complaining about, the amount of the disputed charges, and the amount of any refund you have received;
  • a brief description of the event or action you are complaining about; and
  • the resolution you are seeking, such as a credit or refund or a clearer explanation of the charge(s).
  • For More Information
  • For information about other telecommunications issues, visit the FCC’s website for consumers and government affairs, or contact the FCC’s Consumer Center using the information provided for filing a complaint."[end quotes from FCC public website for purpose teaching public].
Original webite/content to create emergency communications in a crisis:
This site is intended to offer practical how to instructions on how to create 'ad-hoc' systems that communicate computer to computer or handheld-to-handheld in situations where the internet has been blocked by governments or is not accessible. I have studied many sources in compiling this info and it began with the PC World article that was on Google news this am. I have copied some of many sources and I pray that the powers that be over copyright look the other way as in some cases I have copied more than 100 words. This is a public service intnded to help the people in any nation who experience an internet blackout for political reasons,censorship of liberty or oppressive regimes. I have attributed the sources and you should read the entire articles when possible. I know when using handheld devices that opening links is not do-able often so I am writing it all here that I consider relevant and necessary to set up a bypass system to communicate.
Sometimes in any endeavour the way to go forward is to go backward a bit and regroup. Update: remember an ad-hoc connection connects via other devices and it is not the preferred method. It is better to connect directly to your modem AND to secure your netwrok with a password and encryption. Unsecured networks are not safe. The main reason for this site was to provide helpful advice for those who are in unusual circumstances and have to create a connection sort of on their own. I was thinking in emergencies like for campers etc.

This quote from PC World article:
And this advice from PCWorld:

Remember when you stashed your old modems in the closet because you thought you might need them some day? In the event of a total communications blackout--as we're seeing in Egypt, for example--you'll be glad you did. Older and simpler tools, like dial-up Internet or even ham radio, could still work, since these "abandoned" tech avenues aren't being policed nearly as hard.

In order to get around the total shutdown of all of the ISPs within Egypt, several international ISPs are offering dial-up access to the Internet to get protesters online, since phone service is still operational. It's slow, but it still works--the hard part is getting the access numbers without an Internet connection to find them.

Unfortunately, such dial-up numbers can also be fairly easily shut down by the Egyptian government, so you could also try returning to FidoNet--a distributed networking system for BBSes that was popular in the 1980s."[end quote]
And  Diahinia software /download might work for you:
"Daihinia™ is a tool for WiFi. It turns a simple Ad-Hoc network into a Multi-hop Ad-Hoc network. Multi-hop Ad-Hoc networks offer a higher level of flexibility than the usual Infrastructure Mode: in Infrastructure Mode all the computers have to be in the range of the Access Point, while in Multi-hop Ad-Hoc networks they have to be within one another's range."
You could download Dahinia for wifi at:
  And using Pidgin -universal chat app might be a solution since chat works on IRC. Quoting their website:
"Pidgin is a chat program which lets you log in to accounts on multiple chat networks simultaneously. This means that you can be chatting with friends on MSN, talking to a friend on Google Talk, and sitting in a Yahoo chat room all at the same time.
Pidgin runs on Windows, Linux, and other UNIX operating systems. Looking for Pidgin for OS X? Try Adium!
  Pidgin is compatible with the following chat networks out of the box: AIM, ICQ, Google Talk, Jabber/XMPP, MSN Messenger, Yahoo!, Bonjour, Gadu-Gadu, IRC, Novell GroupWise Messenger, QQ, Lotus Sametime, SILC, SIMPLE, MXit, MySpaceIM, and Zephyr. It can support many more with plugins."[end quote]
...download app from:
and works for these languages:
Pidgin is translated into many different languages, thanks to the generous contributions of our volunteer translators.
This is NOT alphabetical so read all:
Afrikaans,Albanian,American English,Arabic,Armenian,Australian English,Azerbaijani, Belarusian Latin ,Bengali,Bokmal Norwegian,Bosnian,British English,Bulgarian,Canadian English,Catalan, Chinese,Czech,Danish,Dutch Flemish ,Dzongkha,English,Esperanto,Estonian,Euskera(Basque) ,Finnish,French,Galician,Georgian,German,Greek,Gujarati,Hebrew,Hindi,Hong Kong Chinese,Hungarian,Indonesian,Irish,Italian,Japanese,Kannada,Khmer,Korean,Kurdish,Lao ,Lithuanian,Macedonian,Malay ,Marathi,Mongolian,Myanmar (Burmese),Nepali,Norwegian Nynorsk ,Occitan,Oriya,Pashto,Persian,Polish,Portuguese,Portuguese-Brazil,Punjabi,Romanian,Russian ,Serbian,Serbian,Simplified Chinese,Sinhala,Slovak,Slovenian,Spanish,Swahili,Swedish,Tamil,Telugu,Thai,Traditional Chinese,Turkish,Ukranian,Urdu,Valencian-Catalan."
And about how easy it is for governments to intercept wifi is in this article by the Electronic Frontier Foundation [EFF] about Surveillance Self-defense:

Wireless networking is now a ubiquitous means of connecting computers to each other and to the Internet. The primary privacy concern with Wi-Fi is the interception of the communications you send over the air. In some cases, wireless routers might also store a small amount of information about your computer, such as its name and the unique number assigned to its networking card (MAC address).

Wireless networks are particularly vulnerable to eavesdropping — in the end, "wireless" just means "broadcasting your messages over the radio," and anyone can intercept your wireless signal unless you use encryption. Listening in on unencrypted Wi-Fi communications is easy: almost any computer can do it with simple packet-sniffing software. Special expertise or equipment isn't necessary.

Even worse, the legal protections for unencrypted wireless communications are unclear. Law enforcement may be able to argue that it does not need a wiretap order to intercept unencrypted wi-fi communications because there is an exception to the rules requiring such orders when the messages that are being intercepted are "readily accessible to the public." Basically, any communication over the radio spectrum that isn't transmitted by your phone company and isn't scrambled or encrypted poses a privacy risk.

Encrypting a Wireless Network

If you want to protect your wireless communications from the government or anyone else, you must use encryption! Almost all wireless Internet access points come with WEP (Wired Equivalent Privacy) or WPA (Wi-Fi Protected Access) encryption software installed to encrypt the messages between your computer and the access point, but you have to read the manual and figure out how to use it. WEP is not great encryption (and we recommend strong, end-to-end encryption for sensitive communications regardless of the transmission medium), and practiced hackers can defeat it very quickly, but it's worth the trouble to ensure that your communications will be entitled to the legal protections of the Wiretap Act. WPA is much stronger than WEP, but it still only covers the first step your packets will take across the Internet.

When Using Open Wi-Fi

If you're using someone else's "open" — unencrypted — wireless access point, like the one at the coffee shop, you will have to take care of your own encryption using the tools and methods described in other sections. Tor is especially useful for protecting your wireless transmissions. If you don't use Tor, and even if you do, you should also always use application-level encryption over open wireless, so no one can sniff your passwords.[end quote]
As it exists @9:49 AM 2/2/2011
Article at:https://ssd.eff.org/tech/wifi./.
So another way to create a work-around is to turn your own computer into a web server. If you have an old computer with Microsoft 95/98/xp/me these are instructions from Microsoft [old computers that have been offline for a while might not be as detectable by governments for a while, giving you time to do this. Quoting Microsoft { I have the 'right' I think, since I have spent a small fortune on several Microsoft OS-computers.} :Setting your computer so others could dial into it to communicate or access the internt; instructions from Microsoft 
for Microsoft OS on older computers:
Configuring Your Computer's Modem

To install and configure a modem, follow the manufacturer's installation instructions that are included with your modem.

Install the Dial-Up Networking and Dial-Up Networking Server Components

To install the Dial-Up Networking component, follow these steps:
Double-click My Computer.
If there is a Dial-Up Networking folder in My Computer, Dial-Up Networking is already installed. Skip to the "To install the Dial-Up Networking Server Component" section. If there is no Dial-Up Networking folder, continue with these steps.
Click Start, point to Settings, click Control Panel, and then double-click the Add/Remove Programs icon.
On the Windows Setup tab, click Communications in the Components box, and then click Details.
Click to select the Dial-Up Networking check box, and then click OK.
Click OK.
To install the Dial-Up Networking Server component, use the following steps.
Windows 95

NOTE: These steps assume that you have already installed Microsoft Plus! for Windows 95.
Click Start, point to Settings, click Control Panel, and then double-click the Add/Remove Programs icon.
On the Install/Uninstall tab, click Microsoft Plus! for Windows 95, and then click Add/Remove.
Click Add/Remove.
Click to select the Dial-Up Networking Server check box, and then click Continue.
Windows 98/Windows Me

Click Start, point to Settings, click Control Panel, and then double-click the Add/Remove Programs icon.
On the Windows Setup tab, double-click Communications.
Click to select the Dial-Up Networking Server or Dial-Up Server check box, and then click OK.
Back to the top
Configuring Your Computers' Network Properties

To share resources by using Dial-Up Networking, both computers need to use the following network components:
Client for Microsoft Networks
Dial-Up Adapter
A network protocol that is common to both computers
The common protocol can be either NetBEUI or IPX/SPX-compatible. 

In addition, the File and Printer Sharing for Microsoft Networks feature must be enabled on the computer that is to be the server. To verify that this is enabled, click File and Printer Sharing in Network properties.
Verifying Network Settings

To make sure that your computers are using the proper network settings, follow these steps:
Click Start, point to Settings, click Control Panel, and then double-click the Network icon.
Examine the list of installed network components. If any of the necessary components that are listed above are not installed, click Add to install them.
Verifying the Computer Name

After the necessary components are installed, click the Identification tab in Network properties and verify that the computer name is valid. It must be a unique name that is no more than 14 characters long and does not contain spaces or any of these characters:
/ \ * , . "
Also, make sure that the workgroup name is the same on both computers.
Back to the top
Enable the Server

To configure a computer to be a Dial-Up Networking server, follow these steps:
In My Computer, double-click the Dial-Up Networking folder.
On the Connections menu, click Dial-Up Server.
Click Allow Caller Access.
If you want to require remote users to enter a password when they connect to your computer by using Dial-Up Networking, click Change Password, and then type the password you want to use.
Click OK.
To allow others to use resources on your computer, you must share those resources. To read information about sharing resources, read the following topics in Windows Help and then share the resources you want other to be able to use:
"Use a Network"
"Sharing a folder or printer"
Your computer and shared resources can now be accessed by Microsoft Windows for Workgroups 3.11, Windows 95, Windows 98, Windows Me, and Microsoft Windows NT 3.1 and 3.5 clients.
Back to the top
Dial a Server (for a Client Connection)

For additional information about configuring Dial-Up Networking to dial a Dial-Up Networking server, click the article number below to view the article in the Microsoft Knowledge Base:
145843  How to Connect to a Remote Server
Back to the top
For additional information about the Dial-Up Networking Server component, click the article number below to view the article in the Microsoft Knowledge Base:
137820/"  Microsoft Plus! Readme.txt File Contents (2 of 2)
From :http://support.microsoft.com/kb/139710
at it exists @9:38 AM 2/2/2011
And how to set up your computer as web server so other computers could connect by dialing up your computer these instructions for Apache from the Streisand project. Quoting their website:

"How to set up a web server from the Streisand project to create workaround to interent censorship or blockade:
9:23 AM 2/2/2011; Quoting:
"Translations : ar en, da, fr, de, nl, pl, sp, sw, sr, ch

To keep the flow of information running, and to route around censorship, here are some guidelines on how to set up a mirror of a few videos that the world needs to know about.

This is how censorship on the web works: The government finds out about a site, then adds it to a filterlist. Now, this is of course very easy to circumvent. You just move the site to a new IP-number or change the URL to it. To be one step ahead of the censors, we use the famous Streisand Effect to work around the problem. The Streisand effect stipulates that the more someone tries to censor content on the internet, the more it is copied. It works for the 2000 Wikileaks mirrors, and it works for almost any project. There are maybe 2 billion computers in the world to choose from, because you can be a mirror too.

Go back.

Lets do it!

First you need an internet connection. A pretty lousy one will actually do, and a home connection is sufficient given that there are lots of them.

Second you need a web server. On Linux you have the excellent Apache server, which on Debian/Ubuntu is installed and started up with the command sudo apt-get install apache2. On most Mac OS versions it is already installed, and you activate it in the preferences for network/sharing. On Windows, I am not sure how to do this (please comment!).

Forward ports in your home router if you have one. You want port 80 to go to the local IP-number of your web server.

est the web server to see that it functions. First you simply type http://localhost in your browser, and you should see a page saying “Apache has been set up successfully” or similar. Then try to access it from the internet, to see if your port forwarding works.

Copy the mirror files and unzip them in the directory that Apache points to. On Linux it usually default points to /var/www where you can put the files. On a Mac, it is somewhere in your home folder (if I remember correctly). Please also put the original zip file in the directory, so that others can copy your mirror. Streisand effect is recursive, you know, just like a fractal.

Once the files, including the index.php, is in that specific directory, the mirror should work to push traffic on the interwebs. Ask your friends to try it out. If it does not work, consult an Apache manual.

Congratulations. You have participated in the machinery of internet politics and contributed to the impossibility of government censorship.

Add your location to us by announcing it in our chat channels. Also, feel free to discuss with internauts in the #streisand on irc.telecomix.org (Tor and I2P connections available, instructions at Telecomix chat)."
And another method is FidoNet. Quoting wikileaks info:
FidoNet instructions/ and UUCP instructions:
"FidoNet is a worldwide computer network that
 is used for communication between bulletin board systems"...
 Until 1994 with the arrival of commercial Internet, Fidonet was the only non Compuserve, Minerva or Prodigy methodology for most of the world's population to 
send email to and from the Milnet, Arpanet and Minitel networks."..
FidoNet was historically designed to use modem-based dial-up (POTS) access between bulletin board systems, and much of its policy and structure reflected this.
The FidoNet system officially referred only to transfer of Netmail—the individual private messages between people using bulletin boards—including the protocols and standards with which to support it. A netmail message would contain the name of the person sending, the name of the intended recipient, and the respective FidoNet addresses of each. The FidoNet system was responsible for routing the message from one system to the other (details below), with the bulletin board software on each end being responsible for ensuring that only the intended recipient could read it. Due to the hobbyist nature of the network, any privacy between sender and recipient was only the result of politeness from the owners of the FidoNet systems involved in the mail's transfer. It was common, however, for system operators to reserve the right 
to review the content of mail that passed through their system."..
Geographic structure
FidoNet is politically organized into a tree structure, with different parts of the tree electing their respective coordinators. The FidoNet hierarchy consists of Zones, Regions, Networks, Nodes and Points broken down more-or-less geographically.
The highest level is the Zone, which is largely continent-based:
Zone 1 is North America
Zone 2 is Europe, Former Soviet Union Countries, and Israel
Zone 3 is Australasia
Zone 4 is Latin America (except Puerto Rico)
Zone 5 is Africa
Zone 6 is Asia (excluding Israel and the Asian parts of Russia, which are listed in Zone 2) -- On 26 July 2007 Zone 6 was removed, and all remaining nodes were moved to Zone 3.Each zone is broken down into regions, which are broken down into nets, which consist of individual nodes. Zones 7-4095 are used for "othernets"; groupings of nodes which use Fido-compatible software to carry their own independent message areas without being in any way controlled by FidoNet's political structure. Using un-used zone numbers would ensure that each network would have a unique set of addresses, avoiding potential routing conflicts and ambiguities for systems that belonged to more than one network."...

FidoNet addresses
FidoNet addresses explicitly consist of a Zone number, a Network number (or region number), and a Node number. They are written in the form Zone:Network/Node[4]. The FidoNet structure also allows for semantic designation of region, host, and hub status for particular nodes, but this status is not directly indicated by the main address.
For example, consider a node located in Tulsa, Oklahoma, USA with an assigned node number is 918, located in Zone 1 (North America), Region 19, and Network 170. The full FidoNet address for this system would be 1:170/918. The region was used for administrative purposes, and was only part of the address if the node was listed directly underneath the Regional Coordinator, rather than one of the networks that were used to divide the region further."...
Routing of FidoNet mail
In a theoretical situation, a node would normally forward messages to a hub. The hub, acting as a distribution point for mail, might then send the message to the Net Coordinator. From there it may be sent through a Regional Coordinator, or to some other system specifically set up for the function. Mail to other zones might be sent through a Zone Gate.
For example, a FidoNet message might follow the path:
1:170/918 (node) to 1:170/900 (hub) to 1:170/0 (net coordinator) to 1:19/0 (region coordinator) to 1:1/0 (zone coordinator). From there, it was distributed 'down stream' to the destination node(s)."...
Part of the objective behind the formation of local nets was to implement cost reduction plans by which all messages would be sent to one or more hubs or hosts in compressed form (ARC was nominally standard, but PKZIP is universally supported); one toll call could then be made during off-peak hours to exchange entire message-filled archives with an out-of-town uplink for further redistribution."...In practice, the FidoNet structure allows for any node to connect directly to any other, and node operators would sometimes form their own toll-calling arrangements on an ad-hoc basis, allowing for a balance between collective cost saving and timely delivery. For instance, if one node operator in a network offered to make regular toll calls to a particular system elsewhere, other operators might arrange to forward all of their mail destined for the remote system, and those near it, to the local volunteer. Operators within individual networks would sometimes have cost-sharing arrangements, but it was also common for people to volunteer to pay for regular toll calls either out of generosity, or to build their status in the community.
This ad-hoc system was particularly popular with networks that were built on top of FidoNet. Echomail, for instance, often involved relatively large file transfers due to its popularity. If official FidoNet distributors refused to transfer Echomail due to additional toll charges, other node operators would sometimes volunteer. In such cases, Echomail messages would be routed to the volunteers' systems instead."...Technical specifications
FidoNet contained several technical specifications for compatibility between systems. The most basic of all was FTS-0001, with which all FidoNet systems were required to comply as a minimal requirement. FTS-0001 defined:
Handshaking - the protocols used by mailer software to identify each other and exchange meta information about the session.
Transfer protocol (XMODEM) - the protocols to be used for transferring files containing FidoNet mail between systems.
Message format - the standard format for FidoNet messages during the time which they were exchanged between systems.
Other specifications that were commonly used provided for echomail, different transfer protocols and handshake methods (e.g.: Yoohoo/Yoohoo2u2, EMSI), file compression, nodelist format, transfer over reliable connections such as the Internet (Binkp), and other aspects."...Zone mail hour
Since computer bulletin boards historically used the same telephone lines for transferring mail as were used for dial-in human users of the BBS, FidoNet policy dictates that at least one designated line of each FidoNet node must be available for accepting mail from other FidoNet nodes during a particular hour of each day.[5]
"Zone Mail Hour," as it was named, varies depending on the geographic location of the node, and was designated to occur during the early morning. The exact hour varies depending on the time zone, and any node with only one telephone line is required to reject human callers. In practice, particularly in later times, most FidoNet systems tend to accept mail at any time of day when the phone line is not busy, usually during night."...Arguably the most important piece of software on a DOS-based Fido system was the FOSSIL driver, which was a small device driver which provided a standard way for the Fido software to talk to the modem.[6] This driver needed to be loaded before any Fido software would work. An efficient FOSSIL driver meant faster, more reliable connections.
Mailer software was responsible for transferring files and messages between systems, as well as passing control to other applications, such as the BBS software, at appropriate times. The mailer would initially answer the phone and, if necessary, deal with incoming mail via FidoNet transfer protocols. If the mailer answered the phone and a human caller was detected rather than other mailer software, the mailer would exit, and pass control to the BBS software, which would then initialise for interaction with the user. When outgoing mail was waiting on the local system, the mailer software would attempt to send it from time to time by dialing and connecting to other systems who would accept and route the mail further. Due to the costs of toll calls which often varied between peak and off-peak times, mailer software would usually allow its operator to configure the optimal times in which to attempt to send mail to other system.'...BBS software was used to interact with human callers to the system. BBS software would allow dial-in users to use the system's message bases and write mail to others, locally or on other BBSes. Mail directed to other BBSes would later be routed and sent by the mailer, usually after the user had finished using the system. Many BBSes also allowed users to exchange files, play games, and interact with other users in a variety of ways (i.e.: node to node chat).
A scanner/tosser application, such as FastEcho, FMail, TosScan and Squish, would normally be invoked when a BBS user had entered a new FidoNet message that needed to be sent, or when a mailer had received new mail to be imported into the local messages bases. This application would be responsible for handling the packaging of incoming and outgoing mail, moving it between the local system's message bases and the mailer's inbound and outbound directories. The scanner/tosser application would generally be responsible for basic routing information, determining which systems to forward mail to."...Several DOS based legacy FidoNet Mailers such as FrontDoor, Intermail, MainDoor and D'Bridge from the early 1990s can still be run today under Windows without a modem, by using the freeware NetFoss Telnet FOSSIL driver, and by using a Virtual Modem such as NetSerial. This allows the mailer to "Dial" an IP address or hostname via Telnet, rather than dialing a real POTS phone number. There are similar solutions for Linux such as MODEMU (modem emulator) which has limited success when combined with DOSEMU (DOS emulator). Mail Tossers such as FastEcho and FMail are still used today under both Windows and Linux/DOSEMU.

File queue in qcc, the ncurses UI for qico. The addresses are made-up.
There are several modern Windows based FidoNet Mailers available today with source code, including Argus, Radius, and Taurus. MainDoor is another Windows based Fidonet mailer, which also can be run using either a modem or directly over TCP/IP. Two popular free and open source software FidoNet mailers for Unix-like systems are the binkd (cross-platform, IP-only, uses the binkp protocol) and qico (supports modem communication as well as the IP protocol of ifcico and binkp."...
FidoNet availability

While the use of FidoNet has dropped dramatically compared with its use up to the mid-1990s, it is still used in Russia and former republics of the USSR. Some BBSes, including those that are now available for users with Internet connections via telnet, also retain their FidoNet netmail and echomail feeds.
Some of FidoNet's echomail conferences are available via gateways with the Usenet news hierarchy using software like UFGate. There are also mail gates for exchanging messages between Internet and FidoNet. "..
.Also this info from a link to wikileaks article about how to use UUCP to communicate. Quoting: :"
"UUCP is an abbreviation for Unix-to-Unix Copy. The term generally refers to a suite of computer programs and protocols allowing remote execution of commands and transfer of files, email and netnews between computers. Specifically, UUCP is one of the programs in the suite; it provides a user interface for requesting file copy operations. The UUCP suite also includes uux (user interface for remote command execution), uucico (communication program), uustat (reports statistics on recent activity), uuxqt (execute commands sent from remote machines), and uuname (reports the uucp name of the local system).
Although UUCP was originally developed on and is most closely associated with Unix, UUCP implementations exist for several other operating systems, including Microsoft's MS-DOS, Digital's VAX/VMS, Commodore's AmigaOS, and Mac OS."... UUCP uses the computers' modems to dial out to other computers, establishing temporary, point-to-point links between them. Each system in a UUCP network has a list of neighbor systems, with phone numbers, login names and passwords, etc. When work (file transfer or command execution requests) is queued for a neighbor system, the uucico program typically calls that system to process the work. The uucico program can also poll its neighbors periodically to check for work queued on their side; this permits neighbors without dial-out capability to participate.
Today, UUCP is rarely used over dial-up links, but is occasionally used over TCP/IP.[1][2]
One example of the current use of UUCP is in the retail industry by Epicor CRS Retail Systems for transferring batch files between corporate and store systems via TCP and dial-up on SCO OpenServer, Red Hat Linux, and Microsoft Windows (with Cygwin).[citation needed] The number of systems involved, as of early 2006, ran between 1500 and 2000 sites across 60 enterprises. UUCP's longevity can be attributed to its low/zero cost, extensive logging, native failover to dialup, and persistent queue management."...
UUCP was originally written at AT&T Bell Laboratories, by Mike Lesk, and early versions of UUCP are sometimes referred to as System V UUCP.[when?] The original UUCP was rewritten by AT&T researchers Peter Honeyman, David A. Nowitz, and Brian E. Redman and the rewrite is referred to as HDB or HoneyDanBer uucp which was later enhanced, bug fixed, and repackaged as BNU UUCP ("Basic Network Utilities").
None of these versions were distributed with source code, which inspired Ian Lance Taylor to write a new version from scratch. [3] Taylor UUCP was released under the GNU General Public License and became the most stable and bug free version."...UUCP was also implemented for non-UNIX operating systems, most-notably MS-DOS systems. Packages such as UUSLAVE/GNUCICO (John Gilmore, Garry Paxinos, Tim Pozar), UUPC (Drew Derbyshire) and FSUUCP (Christopher Ambler of IODesign, - ".web" tld of the 1990s), brought early Internet connectivity to personal computers, expanding the network beyond the interconnected university system."... FSUUCP formed the basis for many BBS packages such as Galacticomm's Major BBS and Mustang Software's Wildcat! BBS to connect to the UUCP network and exchange email and Usenet traffic. As an example, UFGATE (John Galvin, Garry Paxinos, Tim Pozar) was a package that provided a gateway between networks running Fidonet and UUCP protocols.
FSUUCP was notable for being the only other implementation of Taylor's enhanced 'i' protocol, a significant improvement over the standard 'g' protocol used by most UUCP implementations."...UUCP for mail routing

The uucp and uuxqt capabilities could be used to send e-mail between machines, with suitable mail user interface and delivery agent programs. A simple uucp mail address was formed from the adjacent machine name, an exclamation mark or bang, followed by the user name on the adjacent machine. For example, the address barbox!user would refer to user user on adjacent machine barbox."...
Mail could furthermore be routed through the network, traversing any number of intermediate nodes before arriving at its destination. Initially, this had to be done by specifying the complete path, with a list of intermediate host names separated by bangs. For example, if machine barbox is not connected to the local machine, but it is known that barbox is connected to machine foovax which does communicate with the local machine, the appropriate address to send mail to would be foovax!barbox!user.
User barbox!user might publish their UUCP email address in a form such as …!bigsite!foovax!barbox!user. This directs people to route their mail to machine bigsite (presumably a well-known and well-connected machine accessible to everybody) and from there through the machine foovax to the account of user user on barbox. Many users would suggest multiple routes from various large well-known sites, providing even better and perhaps faster connection service from the mail sender...
]Bang path
An email address of this form was known as a bang path. Bang paths of eight to ten machines (or hops) were not uncommon in 1981, and late-night dial-up UUCP links would cause week-long transmission times. Bang paths were often selected by both transmission time and reliability, as messages would often get lost. Some hosts went so far as to try to "rewrite" the path, sending mail via "faster" routes—this practice tended to be frowned upon.
The "pseudo-domain" ending .uucp was sometimes used to designate a hostname as being reachable by UUCP networking, although this was never formally in the Internet root as a top-level domain. This would not have made sense anyway, because the DNS system is only appropriate for hosts reachable directly by TCP/IP. Additionally, uucp as a community administers itself and does not mesh well with the administration methods and regulations governing the DNS; .uucp works where it needs to; some hosts punt mail out of SMTP queue into uucp queues on gateway machines if a .uucp address is recognized on an incoming SMTP connection..
]UUCPNET and mapping

UUCPNET was the name for the totality of the network of computers connected through UUCP. This network was very informal, maintained in a spirit of mutual cooperation between systems owned by thousands of private companies, universities, and so on. Often, particularly in the private sector, UUCP links were established without official approval from the companies' upper management. The UUCP network was constantly changing as new systems and dial-up links were added, others were removed, etc.
The UUCP Mapping Project was a volunteer, largely successful effort to build a map of the connections between machines that were open mail relays and establish a managed namespace. Each system administrator would submit, by e-mail, a list of the systems to which theirs would connect, along with a ranking for each such connection. These submitted map entries were processed by an automatic program that combined them into a single set of files describing all connections in the network. These files were then published monthly in a newsgroup dedicated to this purpose. The UUCP map files could then be used by software such as "pathalias" to compute the best route path from one machine to another for mail, and to supply this route automatically. The UUCP maps also listed contact information for the sites, and so gave sites seeking to join UUCPNET an easy way to find prospective neighbors.
...Connections with the Internet

Many uucp hosts, particularly those at universities, were also connected to the Internet in its early years, and e-mail gateways between Internet SMTP-based mail and UUCP mail were developed. A user at a system with UUCP connections could thereby exchange mail with Internet users, and the Internet links could be used to bypass large portions of the slow UUCP network. A "UUCP zone" was defined within the Internet domain namespace to facilitate these interfaces.
With this infrastructure in place, UUCP's strength was that it permitted a site to gain Internet e-mail and Usenet connectivity with only a dial-up modem link to another cooperating computer. This was at a time when true Internet access required a leased data line providing a connection to an Internet Point of Presence, both of which were expensive and difficult to arrange. By contrast, a link to the UUCP network could usually be established with a few phone calls to the administrators of prospective neighbor systems. Neighbor systems were often close enough to avoid all but the most basic charges for telephone calls.
...Decline [in some cases but still usable]

UUCP usage began to die out with the rise of ISPs offering inexpensive SLIP and PPP services. The UUCP Mapping Project was formally shut down late in 2000.
The UUCP protocol has now mostly been replaced by the Internet TCP/IP based protocols SMTP for mail and NNTP Usenet news.
Usenet traffic was originally transmitted over the UUCP protocol using bang paths. These are still in use within Usenet message format Path header lines. They now have only an informational purpose, and are not used for routing, although they can be used to ensure that loops do not occur. In general, this form of e-mail address has now been superseded by the "@ notation", even by sites still using UUCP...
Last uses and legacy

One surviving feature of UUCP is the chat file format, largely inherited by the expect software package.
UUCP was in use over special-purposes high cost links (e.g., marine satellite links) long after its disappearance elsewhere[4], and still remains in legacy use.
In the mid 2000's, UUCP over TCP/IP (often encrypted, using the SSH protocol[2]) was proposed for use when a computer doesn't have any fixed IP addresses but is still willing to run a standard mail transfer agent (MTA) like Sendmail or Postfix.
Bang paths are still in use within the Usenet network, though not for routing; they are used to record the nodes through which a message has passed, rather than to direct where it will go next.
"Bang path" is also used as an expression for any explicitly specified routing path between network hosts. That usage is not necessarly limited to uucp, IP routing, email messaging, or Usenet."[end quote]
 Another method is using the package rtmpdump to upload videos to Al Jazeera news network. Remember Al Jazeera began with journalists who had worked for BBC and their content is also in English. When you are in oppressive regime you want to communicate with those who are not in it but outside the continental boundaries to get help. I have read some of their news in English when they covered the Democratic Convention that was in Denver --they seem good journalists to me. Quoting:
.Uploading to Aljazeera news a video :
How to Record the Al Jazeera Livestream using rtmpdump
found at:
You need rtmpdump:
The package libssl-dev is needed to compile rtmp.
Use the following command to record audio and videostream:
./rtmpdump-2.3/rtmpdump -v -r rtmp://livestfslivefs.fplive.net/livestfslive-live/ -y "aljazeera_en_veryhigh?videoId=747084146001&lineUpId=&pubId=665003303001&playerId=751182905001&affiliateId=" -W "http://admin.brightcove.com/viewer/us1. -p "http://english.aljazeera.net/watch_now/ -a "aljazeeraflashlive-live?videoId=747084146001&lineUpId=&pubId=665003303001&playerId=751182905001&affiliateId=" | mplayer - -dumpstream -dumpfile aljazeera.mpeg

from instructions on a link at:
http://www.pcworld.com/article/218155/get_internet_access_when_your_government_shuts_it_down.html/ " [end quote]
as it exists @10:05 AM 2/2/2011.
And another method is what is called "hamRadio" but no pork in it! Or also called 'packet radio" or amateur radio [ I think] using radio frequencies via satellite to transmit audio. Kenwood and Alinco make handheld/mobile radios with builtin TNC [terminal node controller]  which connects directly to serial ports of computers or terminal [of  mainframe] without the need of a modem or internet connection and these emit a PTT [turn the transmitter on] signal. Also a "Bell 202" modem does that and 2.4 GHz on Wlan which overlaps amateur radio band but has no encryption and has to be open to anyone receiving it.Also the "AX25" provides automated data routing between keyboards computer-to-computer without internet access and is part of these : NET/ROM,TheNET,ROSE,FlexNet,TexNet. AX25 is a protocol for amatuer radio or MARS band and must be left on constantly supplied with power .
Emergency communication channels that use 'packet radio" which I think is amatuer radio:
from wikileaks list of packet radios; save for reference. Quoting the list of what is called packet radio frequencies::
"Satellite Based

Note: Satellites that are transmit only or that are currently inoperative are not listed.
Callsign Alias Uplink Frequency Downlink Frequency Satellite Features
ARISS 145.99 MHz 145.80 MHz International Space Station Do not connect
Send UNPROTO packets as CQ via ARISS
PECHO-12 145.86 MHz 435.15 MHz AO-51 (Echo) 9600 baud
PECHO-12 1268.7 MHz 435.15 MHz AO-51 (Echo) 9600 baud
PECHO-12 1268.7 MHz 2401.2 MHz AO-51 (Echo) 9600 baud

Callsign Alias Frequency City Coordinates Features
VA3BAL BAL 145.630 MHz Ballantrae 44°01'28.80?N 79°21'00?W X1J node links to RMSBAL and BBSBAL
VA3RBW PTALEX 145.010 MHz Pt. Alexander 46°07'36?N 77°34'04?W KA-Node & TNC BBS for Outpost
VE3CON-7[1] WESTON 145.030 MHz Toronto 43°41'39?N 79°31'13?W TCP/IP, BBS, HF 14.105 Network 105[2]
VE3INF-7[1] ACTON 145.050 MHz Acton 43°37'57?N 80°1'31?W TCP/IP, BBS
VE3LSR BARRIE 145.070 MHz Barrie
VE3MIS-7 MISBPQ 144.970 MHz Mississauga 43°41'38?N 79°39'44?W BPQMailChat
VE3NRR PEM 145.010 MHz Pembroke 45°50'07?N 77°09'58?W X1J4
VE3PKG-7 HALTON 145.610 MHz Georgetown 43°40'50?N 79°59'31?W TCP/IP, BBS, email, URL- ve3pkg.dyndns.org
VE3PRC-7[1] PARC 145.010 MHz Brampton 43°39'9.66?N 79°44'27.24?W
VE3STP-7 STPAT 145.010 MHz Mount St. Patrick 45°18'29?N 76°54'14?W K-Net node
VE3UCR-1 FOY 145.010 MHz Foymount 45°25'43?N 77°18'19?W X1J4
VE3ZDA-7 ONA105 145.770 MHz Lisgar (Mississauga) 43°35'15?N 79°46'39?W TCP/IP, BBS, HF 14.105 Network 105[2]
...United States of America

Callsign Alias Frequency City Coordinates Features
KL7AA-1 ANC 145.010 MHz Anchorage
KL7AA-7 ANCBBS 145.010 MHz Anchorage BBS
KL7AA-8 AARC 145.010 MHz Anchorage Part of ANCBBS
KL7ION-2 EAGLE 145.010 MHz Eagle River
KL7AIR-2 AARC 145.010 MHz Elmendorf AFB
KL7GG-1 NEST 145.050 MHz Anchorage
KL7IKX-10 DPD 145.050 MHz Anchorage (south)
KL7GG-2 ERAK 147.360 MHz Eagle River 9600 Baud
KL7AA-8 AARC 147.960 MHz Anchorage Part of ANCBBS
KL7IKX-3 #EMLNK 147.960 MHz Anchorage (South)
KL7JFU-2 VALLEY 147.960 MHz Palmer
KL7AIR-3 147.960 MHz Elmendorf AFB
KL7AA-4 DD 444.050 MHz Anchorage
KL7ION-4 EAGLE4 444.050 MHz Anchorage
KL7AA-8 AARC 3.605 MHz (LSB) Anchorage HF 300 baud
Callsign Alias Frequency City Coordinates Features
W7MOT-6 WHTNKS 145.710 Buckeye 1200b, NET/ROM, Links to UNION2,
W7MOT-13 #WHTNK 438.975 Buckeye 9600b, Backbone to #MESIP, RS-232 to WHTNKS,
W7MOT-8 ELDEN 145.010 Flagstaff 1200b, NET/ROM, Links to PRC and HEBER,
Callsign Alias Frequency City Coordinates Features
KF6DQU-9 BANNER 145.05 Grass Valley 95945 K-NET AX.25 1200 Baud
KF6DQU-4 ROUGH 145.05 Rough and Ready 95975 X1J4 AX.25 1200 Baud 9600 Baud
KE6I[3] 145.73 MHz Berkeley 9600 Baud
KE6I[3] 433.43 MHz Berkeley 9600 Baud
N6RME-1[3] 145.07 MHz Diamond Springs
KG6BAJ[3] 145.09 MHz Grass Valley
WA6LIE-10 145.69 MHz City of Salinas 1200 baud RMS Packet
K6BJ-10 441.50 MHz City of Santa Cruz 1200 baud RMS Packet
N0ARY-1[3] 145.93 MHz San Jose 37.160, -121.908
N0ARY-1[3] 433.37 MHz San Jose 37.160, -121.908 9600 Baud
K6BJ-10 145.01 MHz City of Santa Cruz 1200 baud RMS Packet
K6BJ-10 145.71 MHz City of Santa Cruz 9600 baud RMS Packet
WA6EWV-1[3] 144.97 MHz Lake Tahoe (South)
KD6MTU 145.750 MHz Redding, (Serving Shasta, Tehama, and Trinity Counties) BBS Telnet AX.25/TCP-IP 1200 Baud/soon Uhf 9600 Baud
Callsign Alias Frequency City Coordinates Features
KC0VOA-5 MADI 145.01 ASPEN 1200 BAUD TheNet X1j4, TALK
Callsign Alias Frequency City Coordinates Features
KD1RY-2 145.03 MHz Bethel BBS
Callsign Alias Frequency City Coordinates Features
WN3DHI-2 145.010 MHz Mims FlexNet
WN3DHI-4 145.010 MHz Mims
N4ZKF-5 DABFLA 145.050 MHz FM Daytona Beach BPQ32 Wide Area Node 1200 baud Coordinated
N4ZKF-5 DABFLA 14.098 MHz LSB Daytona Beach BPQ32 Wide Area Node 300 baud
N4ZKF-4 DABBBS 145.050 MHz FM Daytona Beach FBB Full Service 1200 baud BBS
N4ZKF-7 DBCH 145.770 MHz FM Daytona Beach WX1J Wide Area SEDAN Node 1200 baud
AI4RI-10 145.050 MHz FM Daytona Beach Winlink 2000 Packet Radio Gateway 1200 baud
Callsign Alias Frequency City Coordinates Features
KR9U FWDXA 144.910 Mhz FM Fort Wayne 1200 Baud DX Packet Cluster (Telnet: dxc.kr9u.net)
KA9LCF BBS1 145.050 MHz FM Auburn 1200 Baud FBB District 3 Local Area BBS
KA9LCF BBS2 145.530 MHz FM Auburn 1200 Baud FBB District 3 Wide Area BBS
KA9LCF BBS3 430.550 MHz FM Auburn 9600 Baud FBB District 3 Wide Area BBS
KA9LCF-6 145.530 Mhz FM Auburn 1200 Baud FBB District 3 Wide Area Node/Digipeater
KC9ANF-7 145.530 Mhz FM Columbia City 1200 Baud District 3 KA-Node
KC9ANF-8 145.530 Mhz FM Columbia City 1200 Baud District 3 Digipeater
W9INX-1 145.530 MHz FM Fort Wayne 1200 Baud District 3 NETROM Node & Digipeater
KF9NU-8 145.530 MHz FM Peru 1200 Baud District 3 Digipeater
WC9AR-4 INWTLY 145.530 Mhz FM
TX PL131.8
South Whitley 1200 Baud District 3 K-NET Network Node
WC9AR-7 145.530 Mhz FM
TX PL131.8
South Whitley 1200 Baud District 3 KA-Node
WC9AR-8 145.530 Mhz FM
TX PL131.8
South Whitley 1200 Baud District 3 Digipeater
KB9LDZ-7 145.530 MHz FM Wabash 1200 Baud District 3 KA-Node
KB9LDZ-8 145.530 Mhz FM Wabash 1200 Baud District 3 Digipeater
K9CWD-7 145.530 MHz FM Warsaw 1200 Baud District 2 KA-Node
K9CWD-8 145.530 Mhz FM Warsaw 1200 Baud District 2 Digipeater
W9EBN-7 145.530 MHz FM Marion 1200 Baud District 6 KA-Node
W9EBN-8 145.530 Mhz FM Marion 1200 Baud District 6 Digipeater
KC9JIH-7 LEHIGH 145.050 MHz FM Mitchell 3844.83N/08628.19W TheNET 2.08b 1200 baud Wide Area Node Coordinated IPC www.n9lya.com
N9LYA-7 IN105 145.050 MHz FM Mitchell 3844.43N/08628.33W BPQ32 Wide Area Node 1200 baud Coordinated IPC www.n9lya.com
N9LYA-7 IN105 3.598 MHz LSB Mitchell 3844.43N/08628.33W BPQ32 HF Node 300 baud Coordinated IPC www.n9lya.com
W9OTR-7 LYABBS 145.010 MHz FM Mitchell 3844.43N/08628.33W MSYS Wide Area Node 1200 baud Coordinated IPC www.n9lya.com
N9LYA-7 IN105 432.250 MHz FM Mitchell 3844.43N/08628.33W MSYS Local Node 9600 baud Coordinated IPC www.n9lya.com
N9LYA-7 IN105 226.600 MHz FM Mitchell 3844.43N/08628.33W MSYS Wide Area Node 1200 baud Coordinated IPC www.n9lya.com
N9LYA-7 IN105 147.555 MHz FM Mitchell 3844.43N/08628.33W MSYS Wide Area Node 1200 baud Coordinated IPC BBS Forwarding www.n9lya.com
N9LYA-7 IN105 14.105 MHz LSB Mitchell 3844.43N/08628.33W MSYS Node 300 baud Coordinated IPC www.n9lya.com
K9UY-7 NOIRAM 145.050 MHz FM Indianapolis 3949.54N/08609.39W TheNET 2.08b Wide Area Node 1200 baud Coordinated IPC www.n9lya.com
W9HU-7 MARION 147.555 MHz FM Indianapolis 3949.54N/08609.39W TheNET 208b Wide Area Node 1200 baud Coordinated IPC Packet BBS forwarding. www.n9lya.com
KC9DDP-7 HANSON 432.250 MHz FM Mitchell 3844.83N/08628.19W TheNET 2.08b Local Node 9600 baud Coordinated IPC www.n9lya.com
W9OTR-7 INLAW 144.930 MHz FM Mitchell 3844.43N/08628.33W MSYS Wide Area Node 1200 baud Coordinated IPC IDHLS Emergency Statewide Emergency Freq. www.n9lya.com
...New Mexico
Callsign Alias Frequency City Coordinates Features
KC5CNT-9 ROWE 145.01 ROWE TheNET NODE Active: 6/09
NK5W RIOBBS 145.01 Rio Rancho VHF BBS running MSYS Active: 6/09
KR5NM-1 BUCK 145.01 RUIDOSO Active: 6/09
K5BEN-1 CLOUDY 145.01 CLOUDCROFT Active: 6/09
W5URD LAMOSC 145.01 GRANTS MT. TAYLOR Active: 6/09
N5FAZ-4 ELP 145.01 N. EL PASO NORTH EL PASO Active: 6/09
W5DIG-11 CAPILA 145.01 BELEN CAPILA PEAK Active: 6/09
NM5ML-11 MMTN 145.01 SOCORRO Active: 6/09
[edit]New York
Callsign Alias Frequency City Coordinates Features
N2NOV-4 ARECS 145.070 MHz Staten Island TCP/IP JNOS BBS
...North Carolina
Callsign Alias Frequency City Coordinates Features
WB4IUY-7 51.160 MHz Youngsville 1200 Baud
W4RAL-6 145.010 MHz Clayton 1200 Baud
W4RAL-5 145.010 MHz Rolesville 1200 Baud
WB4IUY-7 145.030 MHz Youngsville 1200 Baud
K2IMO-1 145.030 MHz Wilson 1200 Baud - BBS
K2IMO 145.030 MHz Wilson 1200 Baud
W4RAL-5 147.540 MHz Rolesville 1200 Baud
W4RAL-7 147.540 MHz Zebulon 1200 Baud
W4RAL 147.540 MHz Rolesville 1200 Baud
W4RAL 223.700 MHz Rolesville 9600 Baud - User Access
WB4IUY-7 223.700 MHz Rolesville 9600 Baud - User Access
W4RAL-5 441.000 MHz Rolesville 9600 Baud
Callsign Alias Frequency City Coordinates Features
N8XIX-12 MECH 50.640, 145.010, 440.100 Mechanicsburg 40°05.23' N 83°34.11' W BBS, CHAT, WINLINK
K8QIK-2 LANSW1 50.640, 145.090, 145.530, 223.660, 431.025, 440.500, 446.976 Lancaster 39°43.85' N 82°35.65' W
K8QIK-12 LAN01 145.010 Lancaster TheNet X1J4
K8QIK-14 #LANU1 440.500 Lancaster TheNet X1J4
KB8UVN-5 CMHSW2 50.640, 144.970, 223.420, 223.660, 440.100, 446.625 Worthington 40°08.07' N 83°03.68' W WINLINK
KB8UVN-7 CMHSW3 145.630, 223.420, 440.100, 446.625 Worthington 40°05.54' N 83°00.72' W BBS, CHAT, DXCluster
KB8UVN-11 CMHSW4 50.640, 145.010, 223.420, 223.660, 446.625 Johnstown 40°08.26' N 82°43.09' W
W8CQK-1 BATTEL 144.930, 223.660, 446.625 Columbus 39°59.23' N 83°01.17' W BBS
WB6RHW-1 DC 144.390 Roseburg 43.11.7N 123.07.04W Features
Callsign Alias Frequency City Coordinates Features
W3PGH-7 144.910 MHz Pittsburgh
KS3R-1 144.910 MHz Pittsburgh BBS
Callsign Alias Frequency City Coordinates Features
W0HU-4 JERS 145.05 MHz Salt Lake City 1200 Baud TheNet X1j4, TALK
W0HU-5 SMTN 145.01 MHz Draper 1200 Baud TheNet X1j4, TALK
Callsign Alias Frequency City Coordinates Features
Virginia Digital Network 145.730 MHz Statewide Primary User Frequency 1200 Baud
Virginia Digital Network 441.050 MHz Statewide 'high speed' backbone 9600 Baud
Virginia Digital Network 446.075 MHz Statewide 'low speed' backbone 1200 Baud
Callsign Alias Frequency City Coordinates Features
KE9PW-5 446.425 MHz Green Bay 9600 Baud TCP/IP
...See also

List of APRS nodes
List of hsmm nodes
Packet radio

^ a b c Southern Ontario Packet Radio Association

^ a b HF Packet Network NET105
^ a b c d e f g Packet Sysops of Northern California BBS List" [end quote]
as they exist @8:59 AM 2/2/2011.

I pray this info helps a lot of people communicate with families , friends,resources, friendly governments; and that is it used for good and not evil. And that it is used to sustain human life everywhere. I realize it will take someone with a lot of knowledge of computers or a lot of patience and determination to set these up. Ask anyone in any military [active duty or retired] if they served with communications in military? if so, enlist their help. GOD's blessings on you as you set up communication channels that sustain human life ans ensure the liberties GOD gives. It is written ;where The Spirit of THE LORD is, there is liberty."

22-June-2011@4:13pm; This page and acct is owned by Gloria Poole [me] of Missouri. And I also added all content to it.See my profile and links for more information. You may contact me via my landline phone in Missouri, or via my  google numbers, or my cell phones, or by email or postal mail. I moved to Missouri  from Colorado on Oct 31, 2009; and I divorced a second time in Oct 2007 and removed the Pappas name from my name forevermore, by signed order Judge in District Court at divorce final decree, FYI./s/ Gloria Poole of Missouri. Updated by me Gloria Poole,RN, artist at my own apt in Missouri on 19 th July 2015 at 5:06pm. Updated slightly by me Gloria Poole,RN,artist of Missouri on 1 April 2016 at 3:11pm Updated slightly on 18th March 2017 at 3:15pm by me Gloria Poole,RN,artist of /in Missouri where I have lived since Oct 31, 2009.