1. SSH the SBC
create a session in the putty .As the following pciture show.
you can save the session position as you want .
Then open the session .
2. Login
The username and password are the same as web . please enter them to login.
3. Enter the commands
admin@SBC1000 enable#
More detailed calls commands as below,
Remote packet capture supported versions.
Start of remote packet capture support for versions: 1/2.9x.1.9 or 1./2.9x.2.0 and later, versions after 29th May 2018.
Preparations
1. By default, remote packet capture will capture the incoming and outgoing packets of all network ports of the sbc, and then send them to the remote packet capture server through the specified interface. The processing power of the packet capture server is related to the performance of the computer, if the packet traffic is too large the server will not be able to handle it, resulting in packet loss of the captured messages. Therefore,
a. make sure that the bandwidth between the remote packet capture server and the sbc is sufficient to avoid packet loss.
b. It is not recommended to capture packets when there are a large number of calls, and if you want to capture packets when there are a large number of calls, it is recommended to filter the port range (for example, only capture the specified sip signalling port) or IP address to limit the capture traffic to a reasonable range.
c. Long-term packet capturing will have some impact on sbc performance.
d, ping the server's ip address before grabbing the packet, then sbc to get the server's mac address, so that sbc can not get the server's mac address because of remote packet capture failure.
If the server stops grabbing packets, sbc's remote packet capture will stop automatically (heartbeat timeout) soon.
If you do not operate the web for a long time, sbc's web will automatically log out, but will not affect the packet capture.
Do not pair more than 2 sbc remote packet captures to a single service port, it is not conducive to message analysis.
2. The network port on the SBC used for remote packet capture is placed on the same LAN as the packet capture server. It is best to connect with a Gigabit switch and make sure that the network between the SBC and the packet capture server is connected.
3. Place
the executable in a directory on the packet capture server and ensure that the disk where the directory is located has enough storage space to hold the files generated by the packet capture.
By default, the packet file is placed in the packet folder in the same directory as pcap_server.exe.
Steps
1. Open pcap_server.exe
Double click to open pcap_server.exe, which opens with the following display.
2. Access localhost:9090
Open your browser and type in localhost:9090 to enter the following screen
3. Add configurations
Click to add a configuration
If you want to change the configuration, you can do so by clicking on Edit Configuration.
4. Select the configurrations of the capture
Click on Select Configuration, select the configuration you want to capture and then click on Start Capturing Packet
As you see, the remote packet capture is ready to recieve the packet capture message from sbc.
5. Enable remote capture on sbc GUI
Firstly, enter the packet capture server IP address and port number
Note , the configuration port selected by the remote server is the same.
Secondly ,specify the interface for transmitting packet capture messages.
Thirdly, set the port for local transmission of SBC messages .
Note,do not conflict with the rtp port, SIP listening port and management port.
Finally, set the server heartbeat port
Note,the same as the heartbeat port set by the remote packet capture server.
6. Start capture
Enter the filter criteria according to the actual situation, and finally click on Start Packet Capture.
7. Check the capture process
Back to the GUI of localhost:9090 . You can see the live data changes from the packet capture.
8. Place documents
The package file is placed in the package folder in the same directory as pcap_server.exe, and the configuration file is placed in the config file.
9. Stop capture
Once the packet capture is complete, click stop & download on the sbc web to stop the capture before.Then going to localhost:9090 and clicking the stop capture button to end the capture.
Steps
1. Preparations
Connect the computer and SBCs Admin port to the same switch and set the computer's address as 192.168.1.3 and mask as 255.255.255.0.
2. Select the TFTP path
Open the tftp tool, select 192.168.1.3 for the IP, and select the folder for the path.
3. Login the device through COM port
4. Restart the device
Connect the serial cable to Console, restart the device, and print the countdown input "start" on the serial port. The time is very short and requires quick input. After successful input of 'start', the serial port will enter “sunix # mode”.
5. Set as flash mode
After entering the sunxi # mode, enter the following command to set the loading parameters.
6. Load flash files
The device automatically loads the flash file, and the serial port prints a lot“###”。
Upon seeing 'upgrade succ!', the loading is complete. Then power off and power on to restart SBC.
7. Restart the device
After the SBC1000 is up, connect to the Admin port and log in to 192.168.11.1.
8. Upgrade the app on the web
Inform Dinstar technicians of the current system version and they will provide a suitable version.
Overview
Customers expect to be able to query CDRs from SBC and export them to PC for storage.SBC has been designed with various scenarios in mind to meet the diversified needs of customers.There are three ways to export CDRs in SBC, which correspond to different scenarios, please refer to the documentation for details.
Methods
Export CDR manually
On the Overview-CDR page, click "Export" in the upper right corner and select the desired content to export.
Export local CDRs automatically
1. In Service--CDR, tick "Local DB" and select the storage type.
2. In Service--CDR, click "Local CDRs exported automatically" to set the rules for automatic export.
Upload the CDRs to CDR server automatically
1 In Service—CDR, Tick "CDR Server".
3.2 In Service—CDR, Click "+Add" in the CDR server list to add a CDR server.
Backgrouds
What is HA ? The high availability Active-Standby.
Steps
1. Modify the management port IP of SBC
System--Network page Modify the management port IP of SBC, so that SBC_A & SBC_B have different management IPs and are connected under the same switch.
Tips: The version of the 2 SBCs of HA should be the same. If the versions are different, please upgrade to the same version.
2. Get the SBC HA Licence
2.1 Get the current licences of SBC_A and SBC_B.
Way 1: SSH to SBC, input 'en', then input 'show license' to check the licence.
Way 2: System--License page to see the current license.
2.2 Copy the current License information of the 2 SBCs to Dinstar technician and apply HA License to the salesperson.
2.3 Dinstar Business will provide HA Licence for SBC_A & SBC_B.
2.4 SBC's System--License page, upload the new HA Licence.
Tip: The licences of SCB_A & SBC_B are different and must be corresponded according to the SN. Reboot after uploading License to take effect.
3. Active and Standby Configure
Service--Active and Standby-- Active and Standby Configuration.
Demo SBC IP: SBC_A: 172.28.3.70 , SBC_B: 172.28.3.80
3.1 SBC_A setting Active and Standby Configuration.
Tips: Fill in the IP and SN of SBC_B, and default the other parameters.
3.2 SBC_B setting Active and Standby Configuration.
Tips: Fill in the IP and SN of SBC_A, and default the other parameters.
4. View HA information
That's all the basic configuration for SBC HA, 5 minutes after configuration, HA should be working. View HA info:
Way 1: SSH login, type 'en' and then 'show ha info' to view.
Way 2: You can also view the web page (only supported in newer versions).
If the network is good, you can configure BFD detect. Will detect and switch faster.
Tips：This is optional configuration, not required.
If you need to unplug the service port to switch to master/standby, you can configure Network Port Detection. After configuring Network Port Detection, you need to configure the switching rules with a weight value of 10.
Tips：This is optional configuration, not required.
1. SBC Interface Description
1.1 SBC1000/SBC300 provides 5 network ports, which are MGMT, GE0, GE1, GE2, and GE3, among which MGMT is the management port, and the default IP of MGMT is 192.168.11.1. The default IP of GE0, GE1, GE2, and GE3 are 192.168.12.1, 192.168.13.1, 192.168.14.1, 192.168.15.1.
1.2 SBC3000 provides two network ports, GE0 and GE1. GE1 is the management port, the default IP address of GE1 is 192.168.11.1, and the default IP address of GE0 is 192.168.12.1.
By default, you can only connect to the SBC through the management network port, and other network ports cannot be accessed. If you need to log in SBC through other network port, please enter the web page through the management network port first, and then enable "Allowed to access GEx" in the "Security--Access Control" page. Set the access privileges for ping and SSH in this page as well.
1. Setting the SBC interface IP
2.1 Interface Connection
Power on the device and connect the computer directly to the management port of the device with a network cable. The default IP of the management port is 192.168.11.1 with mask 255.255.255.0. Set the IP of your computer to 192.168.11.X segment with mask 255.255.255.0.
In the browser, use https to access https://192.168.11.1, the default username is admin and the password is admin@123#.
2.2: Change the network interface address
System - network page, select the corresponding interface symbols to modify the IP address, or click "+add" to add the interface IP address (including VLAN fields)
Tips: After modifying the address, you need to reboot the device to take effect.
Tips: Please obtain IP information from your local network technician.
3. Service parameter settings
3.1 Collate configuration information
3.1.1 Sort out the logical structure of the Service of the SBC, for example: Enables two-way calls between IPPBX and IMS. IPPBX == (GE1) SBC (GE0) == IMS
3.1.2 IP and port for IPPBX; IP and port for IMS.
3.1.3 Other functional requirements.
Question: Access Network, Core SIP Trunk and Access SIP Trunk, what is the difference?
Access Network: connects to the internal network device and is used to connect or register terminals such as softphones, IADs, IP phones, etc.
Core SIP Trunk: connects to SIP server and supports registration connection.
Access SIP Trunk: Non-registered connection, such as connection to MTG, DAG.
3.2 add TransPort Endpoint
service--TransPort Endpoint page, add the TransPort Endpoint.
Tip: To add an interface: port, you can add multiple TransPort Endpoints with different ports to an interface for different purposes. For example, GE0:5070 is used for Core SIP Trunk to connect to IPPBX side, and GE0:5080 is used for Access Network to receive extension registration.
3.3 add Access SIP Trunk
Service--Access SIP Trunk page, click ‘+add' to add Access SIP Trunk, add name, then select "media infterface", "TransPort Endpoint", and then set the remote IP: port. After that, submit/save-apply will take effect.
3.4 add Core SIP Trunk
Service--Core SIP Trunk page, click '+add' to add Access SIP Trunk, add name, then select "media infterface", "TransPort Endpoint", and then set the remote IP: port. After that, submit/save-apply will take effect.
3.5 Add routing for inbound and outbound calls
Add inbound routing, call source select added access trunks, destination select added and core trunks! Implement IMS==>SBC==>IPPBX.
Add outbound routing, call source selects added core trunks, destination selects added and access trunks! Implement IMS<==SBC<==IPPBX.
3.6 save&apply and call verify
When all settings are complete, you must click save&apply to take effect.
Then initiate a call for verification.
4. Others
4.1 This document was edited on 2023.8.14. The web and interface of the SBC will be different before 2023.
4.2 This document is just a simple case to illustrate the basic configuration of the SBC, different usage scenarios will have different configurations.
If you encounter difficulties in configuration, please gather the required information and inform Dinstar technical staff.
If there is a problem with the call after configuration, please get the network packet, or log to Dinstar technical staff.
Overview
There are various ways to connect SBCs to IP devices for various scenarios. This document explains the various ways in which SBCs can be connected to IP devices.
Methods
I.Agent registration
Usage Scenarios:
The IPPBX is on the corporate intranet and is required to accept registrations from other extensions coming from the public network. For security reasons, extensions are not allowed to connect directly to the IPPBX and the SBC acts as a proxy server. The logical structure is as follows:
Extension - (access network) SBC (Core SIP Trunk) - IPPBX
Configuration:
Service—TransPort_Endpoint, Configure the transport endpoint.
Note: The Access Network endpoint needs to enable "Dedicated To Access Network".
Service—Access_Network, Configure the access network, select interfaces, and transmission endpoints.
Service—Core_SIP_Trunk, Configure Core SIP Trunks for connecting to the IPPBX.
Service—Routing_Profile—Call_Routing, Configure routing to set up a bi-directional route for "Access Network == Core SIP Trunk".
1.5 Set the registration information in the extension to the SBC's access network IP: port; after the SBC agent will forward the registration message to the IPPBX.
II. SBC's SIP account registration to IPPBX
Usage Scenarios:
For example, when connecting to IMS, SBC registration to IMS is required.
Configuration:
2.1 Service—SIP Account, Add the SIP account.
2.2 Service—Core SIP Trunk, Add IMS information and select the previously added SIP account in the "SIP Account" parameter.
Note: Registration must be done using a Core SIP Trunk, if set in an access trunk, no registration will be initiated.
III. SBC registration to IPPBX (single account)
Usage Scenarios:
If the SBC is on the intranet and the IPPBX is on the public network. You can have the SBC register with the IPPBX to establish a connection.
Configuration:
3.1 Service-Core SIP Trunk/Access Trunk, set IPPBX IP: port, tick Registration, add IPPBX account password.
Note: Enable registration in Core SIP Trunk/Access Trunk will initiate registration with remoteIP:port, after successful registration, the trunk status will be "true", while registration failure will show "false".
IV. SBC and IP_Device IP Connection
Usage Scenarios:
SBC and IP_Device can directly interface via IP trunk when they are on the same LAN or both have public IP.
Configuration:
4.1 Service-Core SIP Trunk/Access Trunk, Just fill in the remoteIP:port directly.
Note: After Core SIP Trunk/Access Trunk is configured, if Keepalive is not enabled, the default Trunk status is "true", if Keepalive is enabled, the trunk status will be displayed according to the heartbeat detection result.
V. IP_Device Registration to SBC
Usage Scenarios:
If the SBC has a fixed public IP and the IP_Device is on a private network, or if the IP_Device's IP is subject to change, the IP_Device can be registered to the SBC.
Configuration:
5.1 Service-Core SIP Trunk/Access Trunk, Trunk mode set to Dynamic, And set the username, authentication ID, password, etc.
5.2 IP_Device acts as a SIP client and fills in the trunk IP, port, username and password in the SBC. IP_Device will initiate registration with the SBC.
Remarks: SBC will detect the registration of IP_Device, the Trunk status will be "true" after successful registration, if there is no registration or the registration fails, the Trunk status will be "false".
1. System Patches
1.1 install libcap-progs
Check whether it has been installed. If the following print is displayed, it indicates that it is supported and no additional installation is required
setcap -h
1.2 install hwinfo
Check whether it has been installed. If the following print is displayed, it indicates that it is supported and no additional installation is required
hwinfo -h
if donot install, it will hint and show command of install
apt install hwinfo
1.3 install libblkid-devel
Check whether it has been installed. If the following print is displayed, it indicates that it is supported and no additional installation is required
apt-show-versions | grep blkid
apt-get install libblkid-dev
2. upload SBC8000 firmware to server
the latest firmware is SBC8000_2.94.2.0.deb till 2023.06.27
please upload the firmware to ubuntu server.
3. install SBC8000
in the demo, we upload firmware in folder /usr/src and so the install command is as below
dpkg -i sbc8000_2.94.2.0.deb
please note it will require enter user name and user group when install and we can enter root username and root group . if canot install with root ,please create a user first and the user must have root authority
4. restart sbc
sudo systemctl restart quickstart
5. access SBC8000
access it with https and port is 1081 and default user/password is admin/admin@123#
it will require to force change password when log in first time
6. provide SBC inforamtion to dinstar team
provide current SBC information to dinstar team to get license key.
please input the license key in red part.
7. change dsp file
7.1 confirm current etherent port of using
ip addr
7.2 change dsp file
vim /home/sbc/etc/sbc/voice_dsp.ini
change the default configuration to current etherent port then save
7.3 restart dsp process
sudo systemctl stop board
sudo systemctl start board
7.4 export the dsp file
access the dsp folder and export lic.dat file to dinstar team.
cd /home/sbc/tmp/
ls -al
please note the size of file lic.dat should be 2048 .if it show 0, it means has issue .please confirm if set etherent port correct or restart dsp process again.
if the dsp file still is 0, please try to run those command
sudo chmod 600 lic.dat
sudo /home/sbc/bin/dsp /tmp/voice_dsp.ini 0
sudo systemctl stop board
sudo systemctl start board
sudo systemctl restart quickstart
8. upload the dsp authorization file
8.1 renama the dsp file to lic.datout
dinstar team will provide a dsp authorization file base on lic.dat file and please rename it to lice.datout
8.2 upload the file to folder /home/sbc/etc/sbc/
cd /home/sbc/etc/sbc/
in the demo, we upload the file via tftp
8.3 change authority for the file
sudo chmod 600 lic.datout
9. restart dsp process
sudo systemctl stop board
sudo systemctl start board
access SBC8000 to confirm the authorization. it means dsp authorization success if the MFU show green
10. upgrade SBC
we can upgrade the SBC by command
sudo dpkg -i xxx.deb
xxx.deb means the name of newer SBC8000 fireware
11. uninstall SBC
check current firmware of installion SBC8000
sudo dpkg --get-selections | grep sbc
root@shawntest:~# sudo dpkg --get-selections | grep sbc
dinstar-softsbc deinstall
sbc8000 install
root@shawntest:~#
then uninstall the SBC8000
sudo dpkg -l sbc8000
sbc8000@linux:~> dpkg -l sbc8000
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii sbc8000 2.94.1.1 amd64 dinstar sbc8000 package
sbc8000@linux:~>
1. System Patches
1.1 install libcap-progs
Check whether it has been installed. If the following print is displayed, it indicates that it is supported and no additional installation is required
setcap -h
installation command
yum install libcap-progs
1.2 install hwinfo
Check whether it has been installed. If the following print is displayed, it indicates that it is supported and no additional installation is required
hwinfo -h
installation command
yum install hwinfo
1.3 install libblkid-devel
Check whether it has been installed. If the following print is displayed, it indicates that it is supported and no additional installation is required
rpm -qa | grep libblkid
installation command
yum install libblkid
2. upload SBC8000 firmware to server
the latest firmware is sbc8000-2.94.2.0psp1-1.x86_64.rpm till 2023.11.16
please upload the firmware to centos server.
we can download on the link
Index of /Firmware/SBC8000/CentOS/
3. install SBC8000
log in home folder and install SBC8000
installation command
sudo rpm -ivh sbc8000-2.94.2.0psp1-1.x86_64.rpm
please note it will require enter user name and user group when install and we can enter root username and root group . if canot install with root ,please create a user first and the user must have root authority
4. restart sbc
sudo systemctl restart quickstart
5. access SBC8000
access it with https and port is 1081 and default user/password is admin/admin@123#
it will require to force change password when log in first time
6. provide SBC inforamtion to dinstar team
provide current SBC information to dinstar team to get license key.
please input the license key in red part.
7. change dsp file
7.1 confirm current etherent port of using
ip addr
7.2 change dsp file
vim /home/sbc/etc/sbc/voice_dsp.ini
change the default configuration to current etherent port then save
7.3 restart dsp process
sudo systemctl stop board
sudo systemctl start board
7.4 export the dsp file
access the dsp folder and export lic.dat file to dinstar team.
cd /home/sbc/tmp/
ls -al
please note the size of file lic.dat should be 2048 .if it show 0, it means has issue .please confirm if set etherent port correct or restart dsp process again.
if the dsp file still is 0, please try to run those command
sudo chmod 600 lic.dat
sudo /home/sbc/bin/dsp /tmp/voice_dsp.ini 0
sudo systemctl stop board
sudo systemctl start board
sudo systemctl restart quickstart
8. upload the dsp authorization file
8.1 renama the dsp file to lic.datout
dinstar team will provide a dsp authorization file base on lic.dat file and please rename it to lice.datout
8.2 upload the file to folder /home/sbc/etc/sbc/
cd /home/sbc/etc/sbc/
in the demo, we upload the file via tftp
8.3 change authority for the file
sudo chmod 600 lic.datout
9. restart dsp process
sudo systemctl stop board
sudo systemctl start board
access SBC8000 to confirm the authorization. it means dsp authorization success if the MFU show green
10. upgrade SBC
we can upgrade the SBC by command
sudo rpm -ivh --force xxx.rpm
xxx.rpm means the name of newer SBC8000 fireware
11. uninstall SBC
check current firmware of installion SBC8000
rpm -qa | grep sbc
then uninstall the SBC8000
sudo rpm -e sbc8000-3.94.1.1-1.x86_64
