Once the software has been installed, the Vodia PBX will run as a service. To access it, use a browser and enter the PBX's url like http://localhost or http://pbx.com etc.
Note: If there is a firewall running on the system, be sure that it allows access to HTTP as well as the other ports of the system.
The login screen will be displayed as shown below:
It is critical that the system administrator login be protected. We recommend that you choose a high-security password. The password is stored in a hashed format so it cannot be read from the global configuration file.
Multiple Administrators And Various Login Levels
Vodia PBX needed to address an old problem. There are usually several persons taking care about the system. Giving them all the same username and password is a bad idea, just like giving everyone the master key for the building. As employees join and leave companies, they must have their own credentials for logging into the system.
The setting is found at the Admin level >
There are now three levels:
The “Super Administrator” is what we know from before. It can have full control over the PBX, including managing other administrators. When upgrading to 5.0.4, this account will stay the same.
The “system administrator” is similar to the super administrator, but cannot create, change or delete the super administrator or other system administrator accounts. There can be many system administrators, each one of them with their own password.
The “domain administrator” is similar to what was previously known as domain administrator permission of an extension. Those domain administrators can be set up in the domain properties by the system or super administrators, and each domain can have multiple domain administrators.
Domain administrators don’t count anymore against the account licenses. This was a problem with the previous concept, as usually one account had to be sacrificed for administration purposes. Also, the system administrators doesn't count against the license.
The Vodia PBX has three main login levels - administrator, domain administrator, and user portal - which provide access to different web interfaces.
- To login as administrator for access to everything, enter "admin" in account and then give the admin password and press the button or the enter key. You will enter the admin interface, where you can change system level settings, including making new domains, security settings etc. From here you can also enter a particular domain from a list - by simply clicking on the domain - to make domain level changes. The admin interface:
- To login as domain administrator, enter the account and password for a particular domain and press the button or the enter key. However, the domain level is usually entered from the admin level as stated above. From the admin level, simply click on any domain (from the domain list) that you want to enter. You will enter the domain interface, where you can change domain level settings, including making new accounts like, extensions, auto-attendants, hunt groups, conferences, trunks etc. (provided the license allows it). You can also go back from the domain level to the admin level by simply clicking on the Switch to Admin button found on the top left of the domain level interface. From the domain level, you can also change settings of any user (extension) and other accounts or even enter any user portal. The domain interface:
- To login to your user portal, enter the extension number of the user portal you want to enter and the corresponding password and press the button or the enter key. You will enter the user portal, where you can change user level settings, including your name, your email address, your picture, buttons of your phone connected to this extension, your sip and web passwords (if the admin allows it), your address book, activesync settings to sync your address book to the Outlook Exchange Server (go to Activesync for more details), your voice mail, call history and many other settings. On the home page of your user portal, you can use the WAC (Web Attendant Console) which allows you to see the presence status of other extensions and accounts as well as lets you manipulate the active calls. It also lets you make calls from your connected phone or even from the browser through WebRTC. Go to WAC for more details. The User Portal interface:
Logging in for the first time after install
After you successfully installed the snomONE on Windows, Linux or Mac OS system, you want to login to the PBX web interface. To do that you simply open your favorite web browser and type http://localhost on the address bar. At this point, generally, you will see the login page for the PBX.
In some cases, you will see a different web page or you may not see any valid page at all. There are few simple reasons for that and it is easy to find a solution once we understand the reason.
- The HTTP(s) ports (port 80 and/or 443) is used by another program on your computer. This is the most common case.
- The LDAP port (port 389) is in use.
- SIP ports (port 5060 and/or 5061) are in use.
In these cases, unfortunately, PBX does not write the errors to the log file. But, since the issue is well understood we can always resolve it.
How to find out which port is in use
You can find out which port is in use by following the below procedure.
- Start command prompt on Windows or a Terminal/Console on the non-Windows system.
- Navigate to the PBX's working directory.
- On Windows enter
.\pbxctrl.exe --dir . --no-daemon --log 9
- On Linux enter
./pbxctrl --dir . --no-daemon --log 9
- Press enter
This will start the PBX application and write the log to the console. From the log, we can see which port is really causing the problem. Once we know the issue, we can use one of the below methods to resolve it.
There are 2 ways to resolve this issues.
- By changing the default ports to something different.
- The PBX uses a configuration file called pbx.xml. You can find this file under the installation folder. You can open this file under your favorite editor and change the following parameters
- ip_http_port - The default value is 80. Change it to something else, say 8080
- ip_https_port - The default value is 443. Change it to something else, say 8081
- ip_ldap_port - The default value is 389. Change it to something else, say 8082
- ip_sip_udp_port - The default is 5060. Change it to something else, say 5080
- ip_sip_tcp_port - The default is 5061. Change it to something else, say 5081
- Note: It is advisable to stop the PBX service, if running before making the above changes. Also, you can make this change one at a time and see if that fixes the issue.
- For example, you can change the ip_http_port to 8080, save the pbx.xml file, start the service and try to login to http://localhost:8080. If this works, then you can make the other changes on using the PBX web interface itself.
- By knowing what other services/programs are running on your system.
- This approach is bit difficult if the user is not aware of their environment properly. But the usual suspects are web servers, like the IIS(Windows), Apache(non-Windows), SIP based softphones etc. So you can turn them off and then restart the PBX to see if you can login to the PBX web interface.
By following one of the above approaches, you should be able to login to the PBX web interface. If you still have issues, then you should contact the VAR/Distributor. Also, http://forum.snomone.com has a lot of information that can help resolve your installation & configuration issues.
Password Reset for the PBX
To reset the login password for the Vodia PBX there are series of steps as below:-
- Go to your working directory of the Vodia PBX (which is usually in
- First things first, please take a backup of the
pbx.xmlfile in any other file of your choice.
emacseditor open the
pbx.xmlfile and search for "pass" (meaning Password). This file may look a little confusing to look at. P.S: Shortcuts to look for (words) quickly using emacs is
/using vi editor
- After it has been found, delete the long sequence of random alphanumerics highlighted below:
- And please keenly observe the changes made above, so that it looks like:-
- Most importantly, save the changes made and restart your PBX for this action to take effect. If that seems like a big impact to the hot servers, this process can be done later as the restart of the PBX is necessary and cannot be skipped.
- Lastly, try to log back in with the original username created, and no password (password field should be kept blank). If you cannot, then something went amiss and the entire process has to be repeated once more. (One of the times when backed up
pbx.xmlcan have your back).
- Also, now you can enter a new password in the Admin > Settings > Security > General > Administrator Login.