Bizfon 2000 Guida Utente
Bizfon Manual II: Administrator's Guide
Administrator’s Menus
Bizfon2000 and Bizfon4000 (SW Version 4.1.x)
16
Hardware Status
The Hardware Status table displays a list of the hardware devices
present and currently available on the Bizfon board. The hardware
device version number and additional comments about its state are
indicated here.
present and currently available on the Bizfon board. The hardware
device version number and additional comments about its state are
indicated here.
Fig. II-22: Hardware Status page
SIP Registration Status
The SIP Registration Status is a table displaying the SIP registration
information of the Bizfon extensions.
information of the Bizfon extensions.
The table contains a list of all the registered extensions of Bizfon, SIP
registration name for each extension, addresses of SIP servers where
they are registered (if applicable), whether or not it is registered for each
extension, and the registration date and time. By clicking on the row
heading, the table will be sorted by the selected column. When sorting
(ascending or descending), arrows will be displayed next to the column
heading.
registration name for each extension, addresses of SIP servers where
they are registered (if applicable), whether or not it is registered for each
extension, and the registration date and time. By clicking on the row
heading, the table will be sorted by the selected column. When sorting
(ascending or descending), arrows will be displayed next to the column
heading.
The links inside the table will link you to the
page where the SIP registration settings may be altered.
The Detected Connection Type field displays the connection type
Bizfon currently is acting in (direct connection or behind NAT). If Bizfon
is acting behind NAT, the NAT machine IP address is also displayed.
Bizfon currently is acting in (direct connection or behind NAT). If Bizfon
is acting behind NAT, the NAT machine IP address is also displayed.
The Registered IP Lines table lists the IP lines and remote extensions
registered on the Bizfon. The table indicates the actual IP addresses of
the remote devices, the usernames by which the devices have been
registered on the Bizfon, as well as the registration status information.
registered on the Bizfon. The table indicates the actual IP addresses of
the remote devices, the usernames by which the devices have been
registered on the Bizfon, as well as the registration status information.
The SIP Trunks to Slave Devices and SIP Trunks to Master Devices
tables list the SIP tunnels between local and the remote Bizfons (see
tables list the SIP tunnels between local and the remote Bizfons (see
). The SIP Trunks to Slave Devices table lists those
trunks where local Bizfon acts as a master. The SIP Trunks to Master
Devices table lists those trunks where local Bizfon acts as a slave.
Devices table lists those trunks where local Bizfon acts as a slave.
Fig. II-23: SIP Registration Status page
IP Routing Configuration
Routing is used to relay information across the Internet from a source to a destination. Along the way, at least one intermediate node is typically
encountered. Routing is different than bridging. The main difference between bridging and routing is that bridging operates at the OSI Data Link
Layer (Level Two Media Access Control Layer) and routing operates at OSI Network Layer (Level Three).
encountered. Routing is different than bridging. The main difference between bridging and routing is that bridging operates at the OSI Data Link
Layer (Level Two Media Access Control Layer) and routing operates at OSI Network Layer (Level Three).
Bizfon’s IP Routing service allows you to route IP packets from one destination to another (or to a specified router) through Bizfon or a Bizfon VPN.
The IP Routing Configuration page is used to make IP Static, IP Policy and VPN routes for IP packets routing. This page consists of three tables.
Entries in the tables are color coded according to the state of the route. For example, yellow indicates disabled routes, green indicates successful
routes and red indicates routes with an error.
Entries in the tables are color coded according to the state of the route. For example, yellow indicates disabled routes, green indicates successful
routes and red indicates routes with an error.