Installation of the On Site Server (OSS) rev 1.1 Step #1 - Initial Connection to the OSS Having plugged in power and an ethernet cable in the eth0 interface (see diagram below) you can connect to the unit on VLAN4 using a browser pointed at the address https://10.0.4.1. To access VLAN4 either provision this as an interface on your PC or configure a port on your ethernet switch to have PVID of 4 and be a member of VLAN4. The OSS will provide DHCP on VLAN4 for your PC. As an alternate to using VLAN4 you can use the standard untagged network. If you attach a monitor to the VGA socket of the OSS it will list the IP address of eth0 (and other interfaces) on the screen. If the IP address of eth0 were 192.168.1.25 then from your PC point a browser at https://192.168.1.25 to see the login screen. At the login screen enter the following: User => btpbx Password => btpbx123(you should change this from the default once you are logged in) Once logged in you will see a menu with a variety of options. The next step is to set up the network, so select that from the menu and we need to define the networking mode in which the unit will be deployed. Step #2 - Network Configuration The OSS is shipped in network mode 5 to make initial access simple, it is almost never deployed in this mode so the first step is to configure the network for your application. The OSS has two physical ethernet interfaces, looking at the back of the unit the one on the left is eth1, the one on the right eth0. Both interfaces are used in all modes except mode 5 where only eth0 is needed. VLANs are used to deploy the phones in the majority of modes. If you have never used VLANS before, not to worry the unit makes them virtually invisible to you and they greatly simplify the deployment of the a VoIP system. In all modes except mode 5 the OSS also performs the vital but complex task of bandwidth shaping and data prioritization to get the best possible Bluestone Telecommunications, Inc page 1
audio quality on phone calls. This is VITAL if you expect a VoIP system to perform reliably but is rarely done correctly in most VoIP deployments., the OSS automates the process. In modes 1,2 and 3 the OSS is the router, firewall and PBX for the site. No other firewall/router is required, although other DHCP servers are handled in some of those modes. Mode 4 is the so called transparent mode. In this mode the OSS extracts the VoIP traffic from the WAN connection and passes all other traffic on to an external router/firewall. The effect is to wrap any existing infrastructure in a skin that handles all of the VoIP traffic and pass through all other traffic transparently. This requires a minimum of two static WAN IPs. Mode 5 is the NAT mode, used if the OSS is to be deployed behind an existing router/firewall. In this mode the advanced traffic shaping and data prioritization cannot be used, you will need to perform this function elsewhere. The table below is a summary of the five available modes (obviously the OSS provides voice functionality in all modes): Mode Mode 1 Mode 2 Mode 3 Mode 4 Mode 5 Comment Untagged LAN only, DHCP server on untagged. Phones are deployed on the untagged LAN. PCs and other hosts are deployed on the untagged LAN network. Untagged + VLAN4, DHCP servers on untagged and VLAN4 Phones are deployed on VLAN4. PCs and other hosts are deployed on the untagged LAN network. Untagged + VLAN4, DHCP server on VLAN4, DHCP client on untagged Phones are deployed on VLAN4. PCs and other hosts are deployed on the untagged LAN network + use external DHCP server The OSS is an ethernet bridge VLAN8 has shaped WAN to third party router/firewall VLAN4 with DHCP for phones untagged VLAN0 is unused by the OSS The OSS is a DHCP client on untagged VLAN4 with DHCP for phones Bluestone Telecommunications, Inc page 2
Changing Mode From the above determine which mode best suits your needs and select that mode from the drop down menu. Once you have confirmed that you are changing mode you will be taken through a wizard that requires: 1. You define the WAN interface with the usual IP, Netmask etc 2. You define the LAN a. If you are in a mode that provides DHCP on untagged then define the subnet you want to use. b. VLAN4 usually needs very little setup but you can change the address range if necessary. Once the interfaces have been configured the unit will perform an interface reset this can take a minute or two. If you have changed to or from mode 4 then you will need to reboot the server. Select the reboot option from menu and re login once the unit is back up. This concludes the network configuration. Step #3 Define the host name On the main menu select Admin, a screen will appear that allows you to define the hostname. It is essential that this be configured correctly otherwise you will not be able to define your PBX setup from the cloud configuration servers. The URLs of all OSS units are of the form : companyname.ossxx.btcfg.com eg acme.oss10.btcfg.com. The interface allows you to enter the company name you were given by Bluestone s tech support and select if you are in the oss10, oss20 etc domain (it is also possible that this was already configured for you.) Once the unit s name has been changed you will need to wait a few minutes for it to be entered into Bluestone s DNS servers. You can test if the name is active by accessing the device using its URL from a browser ie enter https://acme.oss10.btcfg.com into you browser and you should see the login screen. Step #4 Set up Bandwidth Shaping On the main menu select BW Shaping note if you in mode 5 you can disregard this step. There is functionality built into the unit that measures the upstream bandwidth of your Internet connection, we need to know this accurately for the shaping to work. Only the upstream bandwidth is measured as we can only shape upstream traffic. (Aside: Once packets from the downstream traffic have arrived at the OSS there is nothing that any shaping scheme can do about it, so shaping is not applicable here). The inital figure in the Set Upstream BW test box shows what the current setting is. Press the Measure button and give the unit 30 secs or so to make the measurement. The result is Bluestone Telecommunications, Inc page 3
displayed and also written to the BW Shaping text box. At this point no changes have been made to the actual shaping, that does not happen until you press the Update button. It is strongly recommended that you don t modify the measured number and just press Update. This concludes the set up of bandwidth shaping. Putting the Phones on VLAN4 If you select mode 2, 3 or 4 then you will need to do two things: 1. Make sure that the Ethernet switch you are using has VLAN4 enabled and that this VLAN is available on all ports that the phones are connected to. 2. The phones themselves have been configured for VLAN4 operation. Polycom Under the main setup menu of the phone go to: Ethernet Menu => VLAN Menu => VLAN ID Enter 4 in the test box and reboot the phone. Grandstream Under the main setup menu of the phone go to: Config => Layer 2 QoS => 802.1Q VLAN Tag Enter 4 in the test box and reboot the phone. Bluestone Telecommunications, Inc page 4
Appendix A - Ports used by the OSS The following is a list of the ports used by the OSS Port Comment 22 SSH 53 DNS. 80 HTTP 123 NTP 443 HPPTS 3306 MySQL 5060/1 SIP 16384 16638 RTP If you are in modes 1 > 3 and you want to forward port 22 to another device and not cause problems to the OSS then you do this: Enter the IP address of the Bluestone configuration server that serves your account as the source address. Currently that is most likely to be mygui.btcfg.com which resolves to 162.243.97.23 you must only enter IP addresses not URLs as the source address. Set the invert to yes this will result in all connections being routed to your target EXCEPT the one from mygui.btcfg.com which will continue to connect to the OSS. Bluestone Telecommunications, Inc page 5