Login
From Bizfon Wiki
Configuring the PBX can be done either by calling Feature Codes or by logging into the web interface of the PBX. Calling feature codes controls only a few user features like do not disturb; if you want to have full access to the PBX features you have to use a web browser and log into the PBX from there.
You can use a standard web browser for the communication with the PBX. Where ever inside or outside of your network you can connect to the web port of the PBX, you can log in to the PBX. The PBX uses http sessions to keep track of the context that the user is in. The session identifier is stored as a temporary cookie in your web browser. Usually those cookies are allowed today, if that is not the case you need to allow it. If you like, you can also set a permanent cookie. If you check the flag at the bottom of the page, the PBX will ask the browser to set a permanent cookie which will be used for authentication the next time you log in.
To get a login prompt, just enter the address of the web server of the PBX. By default, this will be port 80, which is the default port of the system. If you want to log on to the local system, just use the address http://localhost.
The PBX also supports the secure transport https. If you use this transport layer, the data between the PBX and the web browser is transported using the secure https protocol (see the documentation on https in the Internet). The PBX will usually offer a certificate that will cause an alert on the local web browser. Please ignore the alert or add it to the trusted certificates of your web browser. To log on to the secure connection, use a login prompt like "https://localhost". By default, the PBX will run the service on port 443, but during the installation you may put it on any other port that you like.
There are three ways to log in. There is a selection box where you can tell the system how you want to log in. If you choose "automatic", then the PBX will first try to log you is as system administrator, if that is not possible it will try domain administrator, and if that does not work it will try to log you in as user.
The first way is to log in as system administrator. In this mode, you have access to all resources of the PBX. There is exactly one system administrator mode. Because of this, you should make sure that the login information is kept in a safe place. By default, the login name is "admin" and the password is empty.
The second way to log in is as domain administrator. In contrast to the system administrator, there may be several accounts that have the permission to act as domain administrator, even within one domain. The password in this mode is the password for this extension, which is the same as the SIP password (but not the PIN code).
To log in as domain administrator, you must enter the username and domain name in the "user@domain" form and enter the password, for example "123@test.com". If you have just one domain, you may omit the domain name after the "@" sign. If you have more than one domain and omit the domain name, the system will automatically append a "@localhost" behind the account name.
The domain administrator flag is used to control the permissions of the extension. If the flag is set to true, the web interface will accept the user's login (same as their extension registration) and allow them to change the settings of the domain.
The third mode to log you in is the user mode. The login for this is similar to the domain administrator mode, but you are just taken to a different web page and you can make only changes in your account’s realm.
By default, the PBX will select a predefined language for you. The system administrator can define what language should be presented as the standard language. You may override this in the user's settings or on the domain level as a domain settings. If you explicitly want to specify your language, you can also use the selection box in the login screen.
If the PBX could not allocate the port that you specified as http port, you need to locate the port number. This situation can happen for example if another web service already took the port. In these situations you can use the Windows command line command netstat -a -p to locate the process and find out which TCP ports it has allocated. Usually you are then able to log in. The first thing that you should do then is select another port that is available, so that after a restart the PBX will be able to allocate the specified port.
