New Webmail Software!

We have just rolled out a new webmail package based on the RoundCube software. We hope that this new interface will be faster, easier, and generally a better experience for everyone.

Why the sudden change? We have relied on the horde software for many years now to deliver a consistent webmail interface to our users, and it has served well. However, the version of Horde we have been running all these years is long out of development, new features are not being developed, security issues are not being corrected, and the entire platform relies on version 4 of the PHP scripting language, which is long out of date as well. Because of all these issues, we have had to maintain a webserver running antiquated software, for the sole purpose of keeping horde running. These issues, and many more have caused us to decide to retire horde over the next few weeks.

We evaluated several new webmail packages, including the newest release of Horde itself. Consistently, people preferred RoundCube by a wide margin. If you have any question, don’t hesitate to contact us via email at support@amplex.net.

Migrating Address Books from Horde to Roundcube

Since we are about ready to take the new webmail service live, I thought it best I detail out the procedure for copying your address book from the old webmail service, over to the new one. Unfortunately, since horde will only export to CSV (comma separated values) format, and roundcube will only import from vCard format, an intermediate step is needed. Follow these steps and you should have no trouble:

1) Get the data out of horde.

You will need to login to the old webmail service first, which has been moved to: oldwebmail.amplex.net

Sign in as you normally would, and go to the address book. Click on “Import/Export” at the top, and the very bottom of this page is a button that simply says, “export.” Click it, you will be prompted to download a file, this is your contacts list. Save it someplace where you can find it, because you will be opening it in a bit.

And you are done with old-webmail, you can sign out at anytime.

2) Convert the data to vCard format.

This file contains your address book in CSV format, but we need it to be in vCard format for the new webmail software. First you need to open this file, I recomend using notepad to open it, but any text editor will do.

Open the conversion tool in a new window by clicking here.

You want to copy the entre contents of the file and paste it into step 1 of the conversion tool. If you are using notepad you can click on edit, then select all, to highlight all the data in the file at once. Once you have copied all the text, paste it into the conversion tool, step 1.

Click on Step 2, you probably won’t have to change anything here, I didn’t.

Click on step 3, the text you see should be your address book, converted to vCard format. Highlight all of it, and copy it. Open a new text editor window, and paste all of the data inside. Save this file as something you can find easily, because next you will upload the list into the new webmail system.

3) Important to Roundcube

Now you should have the data in a format that the new webmail software can understand. First you will need to login to the new webmail software by clicking here.

Click on Address Book at the top, then select the import contacts icon, which should be the forth one from the left at the top of the address book page. Browse for the new file you have created, and click import. With a little luck, you have just moved your address book over to the new webmail!

4) Issues?

Having trouble? Please feel free to send a support request to support@amplex.net, asking us to try to migrate your address book for you. Please understand, we expect to get a lot of these, so it may be several days before we can complete your request, please be patient.

Guidelines for providers offering VOIP service over Amplex’s network

Amplex provides service to customers using a fixed position wireless technology.  The network is capable of providing excellent performance for voice services – provided that the guidelines in this post are followed.  Failure to follow these recommendations will likely result in poor call quality and significant customer dissatisfaction.

#1. Before selling or purchasing voice services please check with Amplex to determine if the existing Internet service is appropriate.   We do not recommend deploying VoIP services to locations served by 900Mhz or 802.11 equipment.  In some cases we may be able to upgrade service to accommodate VoIP services.   Significant costs may be encountered if  additional height is needed for the antenna.  The type of equipment in use can not be determined by looking at our invoices – you must contact us.

#2. Notify Amplex of the IP address(es) of the service providers VOIP gateway.  Amplex runs a ‘Quality of Service’ (QoS) enabled network.  This means that we classify and prioritize traffic flowing over the network.   For traffic entering the network at our external borders (from the Internet) any existing QoS is reset to default priority. Traffic is then classified into several categories.  For the purpose of this discussion RTP (the voice part of a IP call) from KNOWN PROVIDERS is set to high priority (DSCP 46).   If you notify Amplex of the VOIP gateway address we will mark traffic as high priority. As of the publication date Buckeye Telesystems is the only provider to have supplied this information.

#3. Notify Amplex of the amount of traffic at the customer location that is needed for the number of call sessions * codec bandwidth.  Based on this information we will enable and set a high priority CIR (committed information rate) for the desired amount of bandwidth. Do not request more bandwidth than is needed as excessive bandwidth reservations will negatively affect other network traffic.

#4). Set the correct DSCP headers in outgoing RTP traffic.   Outgoing traffic to be handled as high priority is determined by the CPE (Amplex’s Customer Premise Equipment) based on the low latency bit of the DSCP header – specifically bit 3 of the 6 bit DSCP header.  We suggest using DSCP code point 46 (or 101110 in binary, some equipment may refer to this as ‘EF’ for Expedited Forwarding).  Note that DSCP is a 6 bit field that is part of an 8 bit IP header.  Equipment that requests a 8 bit value should use 10111000 as a binary value.  Either the customer VIOP gateway or the SIP phones must set DSCP appropriately.

#5)  The customer router MUST clear, at a minimum, the low latency bit of the DSCP field of all non-voice traffic. Failure to accomplish this step will allow other common traffic (SCP, SSH, video) to consume high priority upload bandwidth resulting in poor call quality.  Manipulation of the DSCP values can be handled by many business class routers and firewalls. We have found the Juniper SRX series to be cost effective and capable.

#6.  Check with Amplex to verify that we are seeing traffic flowing in the high priority queue of the radio, in both directions, during a VOIP call.

Following these guidelines should result in a quality VOIP experience. If you are considering either purchasing or selling voice service over Amplex’s network we strongly encourage you to ensure that the VOIP provider and your internal networking team (or consultant) is capable of understanding and following the recommendations in this whitepaper.

Send questions or comments to support@amplex.net

Why does my router keep locking up?

Alternate title:  Why do you keep telling me I have a virus when my Internet quits working?

Home routers are technically not really routers at all – they are network address translation (NAT) boxes.  So what is NAT and why do I care?

NAT was developed in order to conserve address space.  NAT is used in consumer routers as it conserves address space, is easy to configure, and provides some firewall protection to the computers.

How NAT works is pretty simple.  The router (what we are going to call the NAT box) has an outside and a inside interface.  The ‘outside’ is the side connected to the Internet.  The ‘inside’ is the side connected to the computers in your house.

For demonstration purposes lets have 2 computers that we call “A” and “B” in the house.

When computer A connects to a site on the Internet the router makes an entry in the NAT table that says “computer A is talking to Google”.  Computer B wants to connect to Yahoo.  The router makes an entry in it’s NAT table to remember that B is talking to Yahoo.  So far so good.  When responses come back from Google the router knows that ‘Google’ traffic goes to computer A and that “Yahoo” traffic goes to computer B.  The router now has 2 entries in it’s NAT table – one for computer A to Google and one for computer B to Yahoo.  Computer A now goes to a different site – this adds another entry in the NAT table.

So – each new connection from a computer to a site on the Internet uses up one slot in the NAT table (actually it uses several as web pages are composed of multiple images, text, advertising, etc.).  Most consumer routers have NAT tables that can hold a few thousand entries.  How does the router decide when to discard the NAT table entries?  If the connection between the computer is terminated cleanly (the TCP protocol has a way to do this) the entries are removed from the NAT table. Entries that are not cleanly terminated (and some protocols do not have a method to indicate they are done transferring data) are eventually timed out of the table.  Many routers will also start discarding the oldest entries if the NAT table is full or close to full.

So what happens when the NAT table is full?  The router no longer has a place to store information required to process the data coming back from the Internet.  The computer will not be able to establish a connection and the connection will time out.  Since web sites are actually composed of many items when the NAT table is nearly full parts of the page may load while the remainder loads slowly or not at all.  Some routers (that don’t expire entries when the NAT table in nearly full) will appear to lock up at this point and need to be rebooted.  Others will reboot spontaneously or recover if the computers are shut off.

So why would a NAT table be full?  The most common reasons a NAT table is full (or overloaded) is that the computers are trying to talk to too many sites and/or the connections are not being properly terminated (and therefore not being removed from the NAT table).  What kinds of software tries to talk to large numbers of computers on the Internet? Peer-to-Peer file sharing and Viruses.  Let’s take each one separately.

Peer-to-Peer networks are programs that enable you to share files from your computer with others on the Internet who would like to download them.  This is most commonly used for (illegally, but that’s another matter) downloading music and video files from others.  The Wikipedia page has a good description of how peer-to-peer networks work. Depending on the configuration of the peer-to-peer software the program may not limit the number of computers it is sharing files with and/or may not limit the amount of bandwidth being used.  All of the programs we have seen have options for limiting the number of concurrent connections and the amount of bandwidth.  We suggest setting those as low as possible if you are having lockup issues.

Viruses:  Pretty much by definition viruses try to propagate themselves by attacking other computers. Once a computer has been taken over by a virus or other malware it is impossible to say what it is going to do – but they often try establishing so many connections that they quickly overload the NAT table.

So what is Amplex looking at when I call in? Amplex also uses NAT in our customer premise equipment (CPE). The NAT table in our equipment is limited to 4096 entries. When a customer calls in with a connection issue one of the first things we check is to see if the NAT table in the CPE is full. If it is and the customer says they are not running file sharing we are going to assume it is a virus issue. If you are running file sharing we are going to suggest turning it off or adjusting it’s settings.

When we tell you we are seeing signs of virus activity it is not that we are looking at your computer or even seeing the specific traffic . We are seeing the large number of entries in the NAT table of the CPE.

How does an end user figure out which computer is causing the problem? It can be difficult as viruses do their best to hide themselves. Easiest is usually to try turning off one computer at a time and see if the problem goes away. Keep in mind more than one computer may be infected.

But but but.. we don’t want Amplex to do NAT.  I want to have a transparent connection to the Internet! Ok – no problem, just let us know. You will need to understand how to set a static IP address on your router. Please research how to do that before contacting us and we will happily disable NAT on our CPE.

Update on new tower sites

Seems like projects always take longer than they should.   In any case…

The Gibsonburg site is up and running.   I am not completely happy with the coverage area we are getting from the 2.4Ghz sector at the site but the 5.7Ghz transmitter is working very well.    As soon as we have the funds we will swap the 2.4 for a couple of sectors which should improve coverage in the area.

The Dirlam Road site just east of Bowling Green is up and running – we will be converting many of the 900Mhz customers south of SugarRidge and/or north-east of the Bays Rd tower to the new site over the next couple of weeks.   This will result in a significant performance increase for those customers.

Rising Sun is on the back burner for the winter – I do not expect to have equipment at Rising Sun until spring 2010.

The North Baltimore / Hoytville site is a project for late December or early January – funding and weather may delay this though.