3 Configurations on Web Interface
SBC3000 Session Border Controller
Copyright©2011-2018 Dinstar
21
Figure 3-10 Register Status
Table 3-10 Register Status
Status
Registering
：
SBC3000 has received the registration request send by terminal user, and is processing
the request;
Registered
：
The terminal user has been successfully registered and is in validity period
Username
The username of the terminal user, which will be used during registration
Name
Name (source): refers to the name of the access network where the registered terminal user is from;
Name (destination): refers to the name of the core network’s SIP trunk where the registration goes
to
Reg.
Interval
Register Interval (source): the interval of registering to SBC3000 by terminal user
Register Interval (destination): the interval of registering to core network’s SIP trunk by SBC3000
IP
Addr./NAT
IP Addr./NAT (source): the IP address and NAT address of terminal user
IP Addr./NAT (destination): the IP address and NAT address of core network’s SIP trunk
Attack List
On the
Overview
Attack List
page, the source, IP address and interface of attacks to SBC3000 are shown.
Figure 3-11 Attack List
Table 3-11 Attack List
Source
The source of an attack inflicted on SBC3000, for example, DDoS/DoS attacks
IP: Port
The IP address of the attack source, or the destination port that is attacked
Interface
The SBC3000 device’s network interface that is attacked, for example, GE1
Traffic
The traffic of the attack.
When the traffic here mounts to the traffic threshold set on the
Security
Security
Policy
page, the action such as ‘Drop’ or ‘Flow Limited’ will be executed.
Action
Log Record
: when the security policy is triggered and takes effect, the attack event is
recorded in a log
Flow Limited
: when the security policy is triggered and takes effect, the traffic of peer IP
address or the set local port is limited, and those packets whose traffics exceed are dropped
