• Quick Installation Guide
  • Step by Step
  • Admin User Guide
01. Introduction
  • Presence of the Machine
02. Hardware Requirement
03. Acquire the Software
04. System Configuration
05. Recover System via RAID
06. FAQ

The Presence of the Running Machine on the Internet

Everything has a start, and has an end.

Deploying a server over the Internet is different from setting up a local server without being revealed to outside people. For a server to be unknown on the Internet by fully-qualified hostname, it requires some registration processes. Furthermore, since the server is known to the public, some security measures should have been taken to avoid the abuse of the server.

This package includes basic elements for network operation, for example, DNS, FTP, firewall, backup storage server, VPN (Virtual Private Network) and Email .

We start from the introduction on Domain name registration with the following diagram:

1. Purchase domain name from the “vendor for domain name registration”

The “Domain Name Registration Vendor” usually will provide a Web interface for you to query your desired domain name. You may find some of the domain names you like have been acquired by other people. It is necessary for you need to find a domain name that is not being occupied. And then make the purchase of the domain name from the “Domain Name Registration Vendor” to complete this step.

2. Purchase Internet bandwidth and obtain “static” IP addresses from your local ISP (internet service provider).

Usually, the ISP will give you a set of IP addresses that may include a list of public IP addresses, the netmask, and the default Gateway. This IP information will be used when you install the software and configure your server. You shall keep the information in a safe place once you obtain that from your ISP.

3. Find a legitimate “DNS host provider”

It is to host your domain name (which you get from step 2) and the associated static IP address (which you get from step 3) record so that everybody on Internet can use your domain name to reach your server. Usually, the “DNS host provider” will provide a Web interface to allow you to input your domain name and the mapped IP address record into their hosted server. This step is completed after you have entered the data into the web page.

4. Update the record at the “Domain Name Registration Vendor” server with the IP addresses of the “DNS host provider”.

At this step, you need to access the website provided by “Domain Name Registration Vendor”. If you do not know the DNS server’s IP addresses of your “DNS host provider”, you can do as follows at your Windows command prompt (the command prompt is reached through Start > Run > cmd), issue the command

  C:\>nslookup DNS-server- name-from-your-provider

The system will respond with the IP address of your “DNS host provider”. Usually, you need to find two IP addresses of the two DNS servers provided by “DNS host provider” (one is called primary DNS host server, the other is secondary DNS host server). The two IP addresses will be entered into the record in the place of “Domain Name Registration Vendor”. We suggest using primary DNS server and secondary server from different places. The Azblink server package also provides DNS server. But to allow people all over the world can query your domain, you should have your domain name placed in different DNS servers to alleviate the load.

5. Wait until it is in effect.

In general, it needs 24 hours to 72 hours to have your domain name record of the server populated across the world so that people can use domain name to access your server.
Those are the general steps as long as you want to have your own private server(s) on Internet.


Basic Web Setting

After the system installation be finished, take the CD out, reboot the machine, and then start the basic network setting for the system.

There are two modes to configure the host, one is console mode on the local host, and the other is Web interface mode on Client. You can choose the one you like or just by the network environment of that time.

Console Mode --- configure on local host

A. Input account and password to login into console configuration interface.


B. You will see 7 options after login in

 1. IP Address:
 2. Netmask:
 3. Default Gateway:
 4. Save and Reboot
 5. Reset to CD setting (DHCP) and Reboot
 6. View Current Active Values
 7. Exit without Saveing Changes

C. Is there any fixed ip ready for configuration?

  Yes, type fixed IP address, Netmask and Default Gateway into option 1.2.3. severally. You can use up
  and down arrow to choose the option who needs edit, and then press enter to configure. After option 1.2.3
  be correctly configured, you can use option 4 to save these changes and reboot the machine. (If you have
  no idea about the Netmask and Default Gateway, you can just refer to the Completion List provided by your

  No, if there is a DHCP server providing the IP assignment services in your network, you can just use option6
  to check the IP address assigned by the system. After checking eth0, please write down the IP address, and
  remember to use option 7 to quit the Console interface.

D. By the IP address you set or the one obtained from DHCP, you can view the configuration page of the
   system host via Web browser on remote Client.

※ DHCP server exists in your network, but if you find eth0 shown as IP when you check current system value, please check if your network cables plug into wrong place (eh0 and eth1 may been exchanged), or if there are some problems on other equipments. (Refer to Q&A in the manual)

Web interface Mode --- configure at sub-network

A. Is the host, which you installed system on, connected by other hosts?

  Yes, please confirm the host is the only DHCP sever (that is to say the network should not have other
  DHCP servers, e.g. IP distributor), and then start from C.

  No, please complete basic network configuration according to B’s instruction.

B. A network cable makes host’s eth1 port and the Hub connected. And use another cable to connect to
  Hub, let the other end of this cable link to a common Client computer.

C. Choose one Client computer from the sub-network which connected to the system host.

D. Open command prompt on the Client (suppose it’s a Windows machine), type “ipconfig” and then press
 “Enter” button, check whether the Default Gateway is or not?

  Yes, just close the command prompt, enter into next step.

  No, type “ipconfig/release” to release the old IP in your computer, and then type “ipconfig/renew” to get
  new assigned IP.
  (If you are still unable to obtain new IP, please check if the network has other DHCP sever or not, or maybe
  TCP/IP of this Client does not use the mode of “Obtain an IP Address Automatically”.)

E. Open your Browser, and type at the address bar to link. When you visit the page at the
  first time, you will see 4 items;

  Host Name:Please set Host Name for this host.
  Admin Password:Default password is admin123.
  New Admin Password:Please set new password.
  Confirm Password:Please confirm your new password.

F. After you enter into system page, go to System>>Network, choose Internet or PPPoE depending on the

  Choose Internet. At the Internet Interface, mostly, you should set the values for IP address / Netmask /
  Default Gateway and then submit, restart your machine and you will find it already connected to Internet.

  Choose PPPoE. If you use PPPoE, remember to check the checkbox of “Turn on PPPoE”. Fill in the account
  and password provided by ISP and submit, reboot your computer, then you can connect to the network.
  (Please refer to the sections of Configuration and Q&A in Quick Installation Guide if you have any questions.)


Basic Concept

There are many protocols involved with voice communication. We just briefly mention some of them. This phone system can be used without any other plug-in cards for pure VoIP ( voice over IP ) application. To interface with other legacy PBX or analog phones, it needs other interface cards unless those equipments are also provided with communication methods via Ethernet interfaces.

For simplicity, we just identify those phones by the communications protocols. For instance, for those phones running SIP ( Session Initialization Protocol ), we call them “SIP phones”; those phones running IAX protocol are called IAX phones no matter they are “software” or “hardware” phones.

SIP is a protocol developed by IETF ( Internet Engineering Task Force ); IAX ( Inter-Asterisk eXchange ) protocol is initially developed by an open source PBX server Asterisk. Usually when we go by the name “IAX”, actually we mean “IAX2” because the original version of IAX protocol was deprecated. We will use the term “SIP phones” or “IAX phones” in this document to represent those end-user devices or programs.

Many vendors are providing hardware SIP phones. Thus, it is easier to have SIP phones stand-by online all the time instead of using PCs.  But deploying a SIP server behind a firewall with NAT is with some problems. SIP uses UDP port 5060 for establishing initial connection and this can be overcome via “port forwarding” if it is behind a firewall. But it uses UDP ports 8000 to 30000 for RTP ( Real-time Transmission Protocol ) streams for voice. So, usually you only can use “Full NAT” by exposing that server to the network outside firewall instead of just opening a few ports.  Even if you deploy SIP server on the same machine with firewall, we still do not recommend that you open SIP access to the public network because so many ports need to be open for access.

Instead, it only needs to open UDP port 4569 for IAX phones while connecting from the network outside firewall. Please keep this firewall issue in mind.

Before we get into more details, we start with the basic topology for establishing a phone system network.

The diagram below is very simple configuration: SW is the voice communication server and several “phone client programs” are connecting to SW so that they can “call” each other if the system is being properly configured.

For example, if the extension number of A is 7111 and B is 7112, user at A can dial 7112 to reach user at B. If B is not answering the phone, you will have choice to do some configuration at SW to allow A to leave messages to B.

Consider the case that you might want to reach the users on another server. Thus, the following scheme might be considered to use. In the diagram below, SW1 and SW2 are voice servers,  A, B, C, D are phone clients where A and B are connecting to SW1, C and D are connecting to SW2.

Since each server can be configured independently, at SW1, you might have

Extension number of A:  7111
Extension number of B:  7112

Similarly, on SW2, you also can have

Extension number of C:  7111
Extension number of D:  7112

The two systems SW1 and SW2 are working independently initially so that A can dial 7112 to reach B at SW1 whereas C can also dial 7112 to reach D at SW2. But there is demand that A at SW1 wants to reach D at SW2. At this moment, the links between SW1 and SW2 need to be established so that phone calls from SW1 can reach SW2 and phone calls from SW2 can reach SW1 like the following diagram indicated.

At SW1, it can be configured that “371” needs to be dialed at first if you want to reach SW2.  Thus, for user A, if 7112 is dialed, user B will be reached; if 3717112 is dialed, user D will be reached.  Similarly at SW2, you can have similar dial plan by specifying which “digits” need to be dialed at first to reach the other server. Of course, it is necessary that SW1 and SW2 should allow the calls from other server to come in by releasing some authentication methods.  We will introduce how to do that via our Web GUI.  At this moment, we only focus on “thinking” how to do planning. In the diagram above, if SW1 and SW2 belong to different companies, it is okay that each of them can have different dial plans. But if they belong to the same company, it is necessary to have a global consistent dial plan so that it is easier to tell the users about “which number” to dial.

The following diagram is that we complicate the scenario by introducing more voice servers. On each node of SW1, SW2, SW3, and SW4, it has its own plan to dial to the other servers directly. The “red link arrow” in the diagram stands for “who can place the calls toward another”.  Sometimes, it is unavoidable to have configuration like this if SW1, SW2, SW3, and SW4 are under the administration of different people across different companies.

But inside the same company, you probably should consider the following diagram by using hierarchy structure. SW0 controls where to route the placed calls to the destination server and all the other servers just forward the calls to SW0 if the phone calls are not destined to where they are originated.  But the drawback is: if SW0 fails, none of the phone calls can be across the servers.

Those things shall be considered clearly if you are dealing with a large amount of users.  Voice communication is different from Email; it is almost real-time application so that it is easily subject to the processing power of CPUs or bandwidth of the network. And it is somewhat involved with the dial plan to avoid that the users need to dial very long digits to reach the others.