Bizfon 2000 Guida Utente

Bizfon Manual II: Administrator's Guide  

Administrator’s Menus 

Bizfon2000 and Bizfon4000 (SW Version 4.1.x) 

 

 

VoIP Carrier Wizard – Page 3 contains the following VoIP 
Carrier access code selection components: 
The  Access Code text field requires a digit combination by 
dialing, which the corresponding VoIP Carrier will be 
reached. 
The Route Incoming Calls To drop down list allows you to 
select an extension (or Auto Attendant) on the Bizfon where 
incoming calls from the configured VoIP Carrier should be 
routed to. 
The Failover to PSTN checkbox selection will route the call 
to the PSTN through local FXO line in case the VoIP Carrier 
is not available. When this checkbox is selected, an 
additional entry will be added to the 

 table. This 

maintains digit transmission to the local PSTN when an IP 
call towards the configured VoIP Carrier cannot be 
established. 

 A warning message will appear when the 

defined Access Code already exists in the Call Routing table 
or causes a conflict with entries already in the Call Routing 
table. In this case, when continuing through the VoIP Carrier 
Wizard, the existing entry in the Call Routing table will 
automatically be overwritten by the new settings. 

 

Fig. II-136: VoIP Carrier Wizard page 3 

 

RADIUS (Remote Authentication Dial In User Service) specifies the RADIUS protocol used for authentication, authorization and accounting, to 
differentiate, to secure and to account for the users. The RADIUS Server provides the option for a caller from/through Bizfon to pass authentication 
and to be able to dial a specific number.  

When a RADIUS client is enabled on the Bizfon, and according to the configuration of AAA Required option (see 

 table), the RADIUS 

server will be used to authenticate user and/or to account for the call. This can be accomplished by automatic detection of the caller’s number or a 
customized login prompt where the caller is expected to enter a username and password.   

Transactions between the client and the RADIUS server are authenticated through the use of a shared Secret Key, which is never sent over the 
network. In addition, user passwords are encrypted when sent between the client and RADIUS server to eliminate the possibility of a party viewing 
an unsecured network where they could determine a user's password. If no response from the RADIUS Server is returned after the Receive Timeout 
expires, the request is resent numerous times as defined in the Retry Count list. The client can also forward requests to an alternate server(s) if the 
primary server is down or unreachable.  An alternate server can be used after a number of failed tries to the primary server. 

Once the RADIUS server receives the request, it determines if the sending client is valid.  A request from a client that the RADIUS server does not 
recognize must be silently discarded.  If the client is valid, the RADIUS server consults a database of users to find the user whose name matches the 
request. The user entry in the database contains a list of requirements (username, password, etc.) that must be met to give access to the user. If all 
conditions are met, the user gets access to the Bizfon Network. 
The RADIUS Client Settings page contains the Enable RADIUS Client checkbox that enables RADIUS client on the Bizfon.  

 The RADIUS Client cannot be disabled if there is at least one route with RADIUS Authentication and Authorization or RADIUS 

Accounting values configured in the AAA Required drop down list at the 

 table. In order to be able to disable the RADIUS Client on the 

Bizfon, appropriate routes should be removed first. 
 
The other RADIUS Client settings are divided into three groups: