Make sure you can boot to your disk and allow the system to fully load before attempting to make configuration changes in the web management console. This takes you to a login screen that requires you to enter the web admin credentials configured earlier. These applets can be rearranged and also you can add or drop by selecting the Dashboard Applet Admin from the menu on the left side of the screen.
The first item to configure is the network settings found in the Network sub tab under the System menu. Most of the information seen above in figure 4 should auto-populate because of the steps taken during the initial setup.
Select this link, change the system to Static and ensure that the proper IP address and network mask are in their respective fields. Now would be the time to log into your router or gateway and reserve this address in DHCP or switch everything to static. Arguably, the most important part of the system is the extension configuration module. These are assigned to various devices from IP phones to softphones. To configure your extensions, select PBX from the top menu and Extensions from the menu on the left.
You will notice that there are several settings however, most I will leave untouched. As seen in figure 5, pick a display name for this extension. When you have a DID from a provider, this is how you will map it to an extension.
This will also automatically create an inbound route for your DID. Most of the items you see in figure 7 should remain at default. Change the secret to something a little easier to input but still secure Elastix creates one automatically but it is very lengthy. Enable your voicemail and choose a numerical password to access your messages as in figure 8 above. The Voicemail Password should be longer and more complex than the example above to prevent unwanted parties from accessing your mailbox.
The VmX Locater is a feature that provides call routing options. The user can input one of the numbers above to send the call to a different destination based on the definitions shown in Figure 8. After completing the setup of the extension, click the Submit button at the bottom of the page and then click on the red box that appears at the top of the page that you are directed to, that says Apply Config , to lock changes. Take this time to configure as many additional extensions as needed.
Next, return to the extension and optionally, click the new link near the top of the page to configure Follow Me settings. The Follow Me feature is very useful if you are in and out of the office a lot, as it will ring additional phones defined in the Follow-Me List, based on the time set in the Initial Ring Time.
Towards the bottom of the page, you can also specify a location to route the call if the call goes unanswered. Change these settings to meet your needs and be sure to save the settings. An example is shown in figure 9 below.
Your devices should now all be able to communicate with each other on the LAN. In the next step, I will connect our trunking provider in this case VoIP Innovations for origination and termination though feel free to select any provider you like. Keep in mind, the settings will likely be vastly different for another provider.
Sometimes it is necessary to contact support for the trunk provider, in order to gather the credentials you need in order to connect to the outside world. Under the PBX tab, go to the Trunks page on the left. You can set a number for the Outbound Caller ID or leave it blank depending on how your extensions and outbound routes are configured.
Do not worry about adding dial patterns here as this will be configured in the final step. Finally, go to Outbound Routes, found on the left side of the PBX area and proceed to setup a new route. Give this route a name and define your caller ID, if required. Make sure to configure dial patterns as seen in figure Pick the SIP account you configured earlier under the trunk sequence area and hit save. In this setup, I only used one IP phone. Each phone will be slightly different but the premise is the same.
Essentially, most phones just need to know the IP of the PBX server and a few other network settings. Authentication is made by providing credentials for a configured extension, that includes the number extension and a password. This is one way to effectively utilize the Follow Me feature found in Elastix. By configuring additional devices such as mobile devices or tablets, you can easily reach others when they are out of the office and not tethered to a desk.
ZoiPer is incredibly simple to setup with most systems. You add an account under the Config menu, give it a name, plugin an extension and password and the device should register with your PBX as long as you are on the LAN. To connect when on another network or using mobile data, input the public address of your network into the Outbound proxy setting to always stay connected.
If you have issues, it is most likely a port forwarding issue inside your router. Casually, this means it provides the capability to process text-based data for instant messaging services and presence detection plus some other valuable features alongside the VoIP services accommodated by an Asterisk based PBX. The system is developed under the GNU license and has been adapted to fit a handful of systems built under the same model, for example Elastix. The software is produced as an open source platform and is free to use as is all well, most supporting software.
The community is quite large meaning that bugs are quickly rectified and documentation is readily available for most applications. The only problem lies in the fact that many tutorials that are written assume the implementer has experience with these systems; as such, we will go through the entire process by filling in the blanks that most others miss. Sure, guides are available for installing the application but a presumption of technical experience with these systems is implied.
We are going to assume this is a complex casserole and your experience is limited to the microwave. You can do this one of two ways. One such way is to log into Elastix with the credentials you created during the installation, as documented in our Elastix guide. Another way to accomplish this task is to use a terminal client like PuTTy Figure 13 to access the software directly. Elastix is accessible using Secure Shell SSH , a secure protocol for accessing a shell session meaning you can access the command line for the Elastix software.
Type the IP address of the Elastix machine, as seen in Figure 13 above, when connected to the network where the machine resides and click the Open button. The command seen above following the ' ' allows you to login to MySQL with the username root. The password created during the Elastix install must be entered at the next prompt.
This means you are done with the database creation. Not so bad, right? After completing this step, login to the Elastix console with your web browser of choice. On the top most menu bar, click the tab that reads IM.
A message should a appear that states the OpenFire service is not active so click the blue link to begin configuring the application and a screen similar to the one in Figure 14 will appear. At this point, you have completed configuration of the server. If you used Active Directory, the users in your system should populate and you will be able to assign each an account.
In order to use OpenFire, you need to install Spark so you can take advantage of the UC features, such as instant messaging and presence. Download the file and install the application, preferably to a default location. The Spark splash screen can be seen in Figure This is pretty straightforward - login by using a name and password combination created in the console for a user of choice. Other people on the system may be found after logging in by clicking the Contacts tab at the top of the window and Add Contact.
Type the requested user name into the User Name field then hit the Add button. Use the admin login and password assword which hopefully you wrote down for thee Elastix GUI. You at least should now have a functioning system tthat allows you to follow the many other guidesdes that take you through configuration and setup off your you Elastix System.
The majority of these issues will be down to the machine you are using and how you set it up to boot of CD. OK , I have checked with another bootable CD and it boots, what else is wrong? As mentioned in this guide, you may not have used the correct mode to burn the CD. Have a look at the CD via another workstation. Does the disk show one file on it with the extension. ISO or does it show a number of files.
If it only shows one file with the. Take time to read about ISO images and burning them. This is not just an Elastix thing, but this will hold you in good stead for many other systems that require you to burn a bootable CD from an ISO image. One of the other major issues that occurs is that the CD that you have created, whilst burnt correctly may not work in another CD Drive, especially if the machine is quite old and used heavily before it was decommissioned from its previous use.
As such the CD Drive is slightly out of alignment or its lens is a bit dirty. One of the tricks performed in this case is to burn the CD at a much slower speed than the default maximum e. Purposely burn the CD at say 4x.
Yes it will be excruciating in the length of time it takes, but it may end up with a CD that works. Give it a try.
I have commenced the installation program but it appears to hang soon after the initial Elastix screen after I pressed enter After the initial screen, it basically determines the hardware in your system, which includes the hard drive controller. It also makes use of your memory in your machine to load its initial image. If you have a memory fault especially one that is in the high range of the memory , this will cause unexpected errors that generally no one can provide you correct answers on.
The only test is to find a quality memory test routine or if you some spare memory, switch it out. This issue does not occur often, but can happen. The other main issue that does occur is that the Centos system that Elastix uses fails to detect the Hard Drive controller or worst still, hangs the machine whilst doing so.
Elastix tries to maintain an up to date Centos distribution, but like all things, testing takes time, and also it is not good practice to always live on the knives edge using the latest and greatest of every product.
There are some things you can try yourself though, usually via the BIOS of the machine. One of the things to be aware of is that each machine manufacturer is trying to achieve maximum benchmarks with their system. Try changing these settings and see if it resolves the issue. As an example the Enhanced mode may not be compatible with the standard Linux drivers. The same goes for machines that have a RAID mode.
Try turning it off and see if this resolves the issue. Agreed you may want RAID, but you are trying to analyse where your issue is at the moment.
You can proceed with the install and take a look at the other end and possibly learn how to add a driver to suit your network card. If you are lucky, you might be able to use a DKMS enabled driver drivers are normally compiled into the kernel, but DKMS is available for some cards as a loadable module , but it varies on each card manufacturer whether they support this.
Agreed you may not have the spare slot available, and in this case it is understandable, and this will require your time to resolve the issue if immediately resolvable.
Most Linux people recognise this as an important point when selecting hardware to make sure that the Network card is supported and also the hard disk subsystem as well.
I keep about 10 x Realtek cards sitting in a box at all times, buying them when I see them or removing them from systems that are being decommissioned. How do I fix? This is usually a PBCAK issue problem between chair and keyboard and there is very little this document or Elastix or anyone else is going to be able to help with.
The recommendation is to hit the Elastix forums. There are guides on the Internet telling you how to reset the root password, but for each Linux distribution and each boot loader this is different. Remember you are looking for the instructions that are for Centos 5 and Grub as the bootloader.
If your system is in production, make sure you have all the backups you can on a remote system. It sounds like you typed the URL at the linux prompt. This is not where you type this URL. The Elastix system does not include a graphical operating system, and does not include a browser. If you have done this, then you may not be use to products like Elastix and many other hundreds of server products that run on Linux where it contains mainly a server product with a Web Service to configure it or modify it.
You may wonder why this is done this way, and this is make the system as sleek and responsive as possible. The use of minimal services running on the server reduces the possibility of non-essential services causing issues with the main core system, in this case your PBX system. This is why Elastix and Asterisk are not built to run on Windows, and why PBX systems should not run on a Windows platform or even a Linux graphical desktop system.
This reduces these sorts of issues. This also reduces the chances that security issues occur with less components, and also the possibility that a virus will bring your PBX system to a halt. Troubleshooting — how do I solve the issue quickly? Unless your experience is extensive, and I mean working with it almost every day, you are possibly not going to solve your issue quickly.
No matter how good you are at solving issues, you are going to be frustrated that it had to be your system that has failed to install. This frustration clouds your thinking, your belief that the system you have chosen specifically for this purpose, has let you down. This troubleshooting of your system now needs your time and not your speed in trying to resolve the issue.
It means working through it methodically and not making assumptions, otherwise you are unlikely to solve your issue. It is no good picking up a CD that you think was bootable, that you last used 6 months ago and appears to have coffee stains on it, and assuming it still works.
If your issue is with the network card, do the research and find out whether it is supported by Centos, and what version it was introduced. Find out what version you have in your Elastix system. Disable that second onboard Network card, and see if this resolves the issue. Again this practice is not just related to resolving your Elastix install issue, but also any other issue you may have with your Elastix system.
The amount of experienced people that fail to go back to basics to resolve issues are large in numbers Upgrading your system One of the things that everyone seems to be driven to do after they have installed their Elastix system is upgrade everything they can.
Most of the stable releases are released because they have been tested. If something basic is not working, then something else is wrong. Performing a YUM update is in most cases not going to make it magically work. In many cases you could be introducing a new issue. The upgrade mechanism should be used when you know the issue that you have is going to be fixed i.
You need to be aware that Elastix is made up of hundreds of components, including dependencies in the Linux operating system, which also have dependencies on the actual hardware of the system. Whilst a lot of time goes into looking for bugs, it is not a perfect world.
0コメント