Session Border Controller (SBC)
Create SBC User
VSM requires a user account to be created on the AudioCodes SBC device. This user account is required to run CLI and API commands.
AudioCodes SBC users can be created via one of the following options:
- Local User Option
- Active Directory Option
- RADIUS User Option (Coming soon!)
Local User Option
Browse to SBC, navigate to Setup >> Administration >> Local Users .
Click New button to create new user
Enter User details using the following table
Local User Information
Field | Value | Comments |
---|---|---|
Index | Enter any number between 1 and 99 | |
Username | Enter username to be used by VSM | |
Password | Enter password | |
User Level | Choose Monitor | |
SSH Public Key | Leave Blank | |
Status | New | |
Password Age | 0 | Setting password age to 0 so it will never expire |
Web Session Limit | Leave default | Default value is 5 |
CLI Session Limit | Leave default | Default value is -1 |
Web Session Timeout | Leave default | Default value 15 |
Block Duration | Leave default | Default value 60 |
Click Apply
Log out from SBC.
Log back in again using the new created account, make sure you can Login successfully.
Log out again and login using an Admin account to complete next steps.
Active Directory User Option
This option is applicable only if Active Directory is integrated with AudioCodes SBC and is used for users login authentication.
To create a new User on Active Directory ask your Active Directory Administrator to create a User for AudioCodes SBC and ensure the Active Directory Admin puts the user in the same group as other Users with Monitor Level Access to AudioCodes SBC.
Your Active Directory Administrator needs to make sure the new AudioCodes SBC user is in the correct Group ,this group should be different from AudioCodes Administrators group.
RADIUS User Option (Coming soon!)
This option is applicable only if the RADIUS Server is used to manage AudioCodes SBC Users.
To create a new User on RADIUS Server ask your RADIUS Server Administrator to create a User with Access Level 50 (Monitor Level) for AudioCodes SBC.
SNMP Configuration
SNMP configuration is required as part of Audio Codes SBC Monitoring. SNMP can be configured as V2 or V3 based on customer requirements.
SNMP Version 2 Option
Browse to the SBC, Navigate to Setup >> Administration >> SNMP Community Settings
Parameter | Value | Comments |
---|---|---|
Read-only | Enter Snmp Community String | Up to 5 Read-only SNMP Strings can be configured |
Read-Write | Leave Blank | VSM needs only Read-only SNMP String |
Trap Community String | Enter Trap Community String | This can be the same as the Read-only SNMP Community String |
Trap Manager Host Name | Leave Blank | |
Activity Trap | Select Enable from drop down List |
Navigate to SETUP >> ADMINISTRATION >> SNMP Trap Destinations
Fill SNMP Trap Destinations with the following details:
Parameter | Value | Comments |
---|---|---|
Check Box | Check the check box next to SNMP Manager | |
IP ADDRESS | Enter VSM Probe IP Address | |
TRAP PORT | Default is 162 | |
TRAP User | Choose v2cParams |
SNMP Version 3 Option
Browse to the SBC, Navigate to SETUP >> ADMINISTRATION >> SNMP V3 Users
Click New
Use the following table to configure SNMP V3:
Parameter | Value | Comments |
---|---|---|
Index | Defines an index number for the new table row. | Each row must be configured with a unique index. |
User Name | Name of SNMP v3 user | |
Authentication Protocol | Choose one of the following options [0] None (default) | |
Privacy Protocol | Choose one of the following options [0] None (default) | |
Authentication Key | Enter Authentication Key | Key String must be at least six characters |
Privacy Key | Enter Privacy Key | |
Group | Choose Read-Only group from drop down |
Navigate to SETUP >> ADMINISTRATION >> SNMP Trap Destinations
Fill SNMP Trap Destinations with the following details:
Parameter | Value | Comments |
---|---|---|
Check Box | Check the check box next to SNMP Manager | |
IP ADDRESS | Enter VSM Probe IP Address | |
TRAP PORT | Default is 162 | |
TRAP User | Choose SNMP V3 user created earlier |
If you are suing SNMP V3 for Traps, please ensure that the trap user is administered in the VSM Equipment Location for this device.
Click here for documentation on adding SNMP V3 trap users in VSM
Syslog Configuration
Browse to the SBC then Navigate to Troubleshoot >> Logging Settings
Fill in the fields using the information in the below table:
Field | Value |
---|---|
Enable Syslog | Choose Enable from Drop Down List |
Syslog Server IP | Enter IP Address of VSM Probe |
Syslog Server Port | Default is 514 |
Log Severity Level | Choose Informational from the drop down List |
Syslog CPU Protection | Choose Enabled from drop down list |
Syslog Optimization | Choose Enabled from drop down list |
VoIP Debug Level | Choose Basic |
Debug Level High Threshold | Leave Default |
Activity Types to Report | Choose what operations (activities) performed on SBC to be reported in syslog . Select All checkbox will check all activities. |
CDR Configuration (coming soon)
VSM uses the RADIUS Server option to retrieve CDR data.
Browse to the SBC, Navigate to IP Network >> RADIUS & LDAP >> RADIUS Servers
Click New to ad New RADIUS Server
Fill in the details using the following information:
Field | Value |
---|---|
Index | Defines an index number for the new table row. |
IP Address | Enter IP Address of VSM Probe |
Authentication Port | Change it to 0, to prevent authentication attempts to VSM Probe |
Accounting Port | Change it to 1813 |
Shared Secret | Enter the text string for secret key, the same need to be used on VSM when adding AudioCodesSBC |
Click Apply
Navigate to Setup >> Administration >> Authentication Server
If no other RADIUS servers are configured for authentication make sure the following fields are configured:
Field | Value |
---|---|
Use Local Users Database | When No Auth Server Defined - This is the default configuration |
Behaviour upon Authentication Server Timeout | Verify Access Locally - This is the default value, restart is required if any other value was selected before |
Use RADIUS foe Web/Telnet Login | Disable |
RADIUS Response Timeout sec | Change it to 5 |
Navigate to Troubleshoot >> Call Detail Record >> Call Detail Record Settings
Fill in the RADIUS Settings using the following table:
Field | Value | Comments |
---|---|---|
Enable RADIUS Access Control | Select Enable form Drop Down List | SBC needs to be restarted for this change to take effect |
RADIUS Accounting Type | At Setup & Release | |
AAA Indications | Leave Default None |
AudioCodes can use only OAMP Interface (default) or Control Interface to send RADIUS traffic
Only one Control Interface can be configured ,otherwise RADIUS Communication will fail
Web Portal Configuration
Add AudioCodes Session Border Controller
Log in to the VSM web portal using your VSM credentials and password.
For your customer, select Service Desk > Equipment Locations. Right-click on the Equipment Location that will serve this particular AudioCodes SBC and select ‘Manage Equipment’
At the bottom of the ‘Manage Equipment’ page click on the ‘Add Equipment’ button.
A form will open which you can populate with the equipment details as per table the table below
Select the Vendor 'AudioCodes LTD' and Product 'Session Border Controller (SBC)'
Web Portal – Add AudioCodes SBC Field Description
Field | Setting |
---|---|
Vendor | AudioCodes LTD |
Product | Session Border Controller (SBC) |
Equipment Name | Friendly Name for this SBC |
Username | Enter Username |
Password | Enter Password |
IP Address / Host Name | IP Address of SBC |
Site | Free text field, this information will be included in alarm notifications from the VSM Workflow. |
RADIUS Configuration (coming soon)
Check the 'Receive RADIUS Call Accounting' checkbox to collect CDR information from the Ribbon SBC
RADIUS call Accounting
Field | Settings |
---|---|
Shared Secret | Enter the text string for secret key , the same need to be the same configured on Ribbon SBC |
Source IP Address | Enter SBC IP Address that will be used to send CDR information to VSM |
SNMP
Complete the Equipment tab and then click on the ‘SNMP Query’ tab.
Click on the down arrow, and select the SNMP version you wish VSM to use for querying the Ribbon SBC:
SNMP V2
AudioCodes SBC SNMP V2 Field Descriptions
Fields | Setting |
Version | V2 |
SNMP Community String | Community String as administered on the AudioCodes SBC |
SNMP V3
AudioCodes SBC SNMP V3 Field Description
Fields | Setting |
Version | V3 |
Username | SNMP V3 Username |
Authentication Protocol | SHA (recommended) |
Authentication Password | Password |
Privacy Protocol | DES (recommended) |
Privacy Password | Password |
Test Access
Once all fields are populated Click on the Test Access button. This will test that VSM can connect to the CUBE using the settings you have entered:
Both SSH and SNMP should return success. If not, troubleshoot the configuration.
- The SSH test ensures the VSM probe can connect to, and log in using the account configured.
- The SNMP test ensures an SNMP query can be run.
Once testing is successful, click Add.