Connecting to the web-based manager or CLI
There are two methods to connect to the FortiVoice unit:
- use the web-based manager, a graphical user interface (GUI), from within a web browser
- use the command line interface (CLI), an interface similar to DOS or UNIX commands, from a Secure Shell (SSH) or Telnet terminal
Access to the CLI and/or web-based manager is not yet configured if:
- you are connecting for the first time
- you have just reset the configuration to its default state
In these cases, you must access either interface using the default settings.
|
If the above conditions do not apply, access the web UI using the IP address, administrative access protocol, administrator account and password already configured, instead of the default settings. |
After you connect, you can use the web-based manager or CLI to configure basic network settings and access the CLI and/or web-based manager through your network. However, if you want to update the firmware, you may want to do so before continuing. See System Information widget.
|
|
Until the FortiVoice unit is configured with an IP address and connected to your network, you may prefer to connect the FortiVoice unit directly to your management computer, or through a switch, in a peer network that is isolated from your overall network. However, isolation is not required. |
This topic includes:
Connecting to the web-based manager
To connect to the web-based manager using its default settings, you must have:
- a computer with an RJ-45 Ethernet network port
- a web browser such as Microsoft Internet Explorer version 6.0 or greater, or a recent version of Mozilla Firefox
- a crossover network cable
Default settings for connecting to the web-based manager
|
Network interface |
port1 |
|
URL |
|
|
Name |
admin |
|
Password |
(none) |
To connect to the web-based manager
- On your management computer, configure the Ethernet port with the static IP address 192.168.1.2 with a netmask of 255.255.255.0.
- Using the Ethernet cable, connect your computer’s Ethernet port to the FortiVoice unit’s port1.
- Start your browser and go to https://192.168.1.99/admin.
To support HTTPS authentication, the FortiVoice unit ships with a self-signed security certificate, which it presents to clients whenever they initiate an HTTPS connection to the FortiVoice unit. When you connect, depending on your web browser and prior access of the FortiVoice unit, your browser might display two security warnings related to this certificate:
- The certificate is not automatically trusted because it is self-signed, rather than being signed by a valid certificate authority (CA). Self-signed certificates cannot be verified with a proper CA, and therefore might be fraudulent. You must manually indicate whether or not to trust the certificate.
- The certificate might belong to another website. The common name (CN) field in the certificate, which usually contains the host name of the website, does not exactly match the URL you requested. This could indicate server identity theft, but could also simply indicate that the certificate contains a domain name while you have entered an IP address. You must manually indicate whether this mismatch is normal or not.
Both warnings are normal for the default certificate.
- Verify and accept the certificate, either permanently (the web browser will not display the self-signing warning again) or temporarily. You cannot log in until you accept the certificate.
For details on accepting the certificate, see the documentation for your web browser.
- In the Name field, type
admin, then click Login. (In its default state, there is no password for this account.)Login credentials entered are encrypted before they are sent to the FortiVoice unit. If your login is successful, the web UI appears. To continue by updating the firmware, see System Information widget. Otherwise, to continue by following the configuration wizard.
Connecting to the CLI
Using its default settings, you can access the CLI from your management computer in two ways:
- a local serial console connection
- an SSH connection, either local or through the network
To connect to the CLI using a local serial console connection, you must have:
- a computer with a serial communications (COM) port
- the RJ-45-to-DB-9 serial or null modem cable included in your FortiVoice package
- terminal emulation software, such as HyperTerminal for Microsoft Windows
To connect to the CLI using an SSH connection, you must have:
- a computer with an RJ-45 Ethernet port
- a crossover Ethernet cable
- an SSH client, such as PuTTY
Default settings for connecting to the CLI by SSH
|
Network Interface |
port1 |
|
IP Address |
192.168.1.99 |
|
SSH Port Number |
22 |
|
Name |
admin |
|
Password |
(none) |
|
|
If you are not connecting for the first time, nor have you just reset the configuration to its default state or restored the firmware, administrative access settings may have already been configured. In this case, access the CLI using the IP address, administrative access protocol, administrator account and password already configured, instead of the default settings . |
|
|
The following procedure uses Microsoft HyperTerminal. Steps may vary with other terminal emulators. |
To connect to the CLI using a local serial console connection
- Using the RJ-45-to-DB-9 or null modem cable, connect your computer’s serial communications (COM) port to the FortiVoice unit’s console port.
- Verify that the FortiVoice unit is powered on.
- On your management computer, start HyperTerminal.
- On Connection Description, enter a Name for the connection and select OK.
- On Connect To, from Connect using, select the communications (COM) port where you connected the FortiVoice unit.
- Select OK.
-
Select the following Port settings and select OK.
Bits per second
9600
Data bits
8
Parity
None
Stop bits
1
Flow control
None
- Press Enter.
The terminal emulator connects to the CLI and the CLI displays a login prompt.
- Type
adminand press Enter twice. (In its default state, there is no password for this account.)The CLI displays a prompt, such as:
FortiVoice #
- Type
adminand press Enter twice. (In its default state, there is no password for this account.)The CLI displays the following text:
Type ? for a list of commands.
You can now enter commands.
The following procedure uses PuTTy. Steps may vary with other SSH clients.
To connect to the CLI using an SSH connection
- On your management computer, configure the Ethernet port with the static IP address 192.168.1.2 with a netmask of 255.255.255.0.
- Using the Ethernet cable, connect your computer’s Ethernet port to the FortiVoice unit’s port1.
- Verify that the FortiVoice unit is powered on.
- On your management computer, start your SSH client.
- In Host Name (or IP Address), type
192.168.1.99. - In Port, type
22. - From Connection type, select SSH.
- Select Open.
The SSH client connects to the FortiVoice unit.
The SSH client may display a warning if this is the first time you are connecting to the FortiVoice unit and its SSH key is not yet recognized by your SSH client, or if you have previously connected to the FortiVoice unit but it used a different IP address or SSH key. If your management computer is directly connected to the FortiVoice unit with no network hosts between them, this is normal.
- Click Yes to verify the fingerprint and accept the FortiVoice unit’s SSH key. You cannot log in until you accept the key.
The CLI displays a login prompt.
- Type
adminand press Enter twice. (In its default state, there is no password for this account.)The CLI displays the following text:
Type ? for a list of commands.You can now enter commands.