BroadWorks XSP enables you to remotely reconfigure the Sonus
The Sonus
This Best Practice defines the steps necessary to use Sonus
Sections included:
This step is completed by a BroadWorks administrator.
Broadworks Device Management Configuration involves two steps:
Administrator configuration creates a device profile type and is performed by a Broadworks administrator. It should be completed before proceeding to BroadWorks Provisioning.
This is performed by the BroadWorks Administrator on request, with inputs provided by Sonus. It creates the device profile type which can used later for provisioning.
Following information is provided to BroadWorks:
File Name | File Type | Authentication Mode | Authentication Type | Description |
---|---|---|---|---|
|
| User Name and Password | Digest | Configuration file for SBC1000 |
|
| User Name and Password | Digest | Software Application for SBC1000 |
|
| User Name and Password | Digest | Boot Image for SBC1000 |
|
| User Name and Password | Digest | Configuration file for SBC2000 |
|
| User Name and Password | Digest | Software Application for SBC2000 |
|
| User Name and Password | Digest | Boot Image for SBC2000 |
|
| User Name and Password | Digest | Indicates whether the configuration should be imported fully or partially. It is used by both SBC 1000 and SBC 2000. This file contains only one of the following two words. config_type : <type> where type can be either full or partial and passphrase should be the same passphrase that used during configuration backup operation.
Example: config_type: partial |
|
| User Name and Password | Digest | Contains the software release name and the firmware release name pertaining to the software and firmware in the XSP directory, SBC checks this file before downloading and updating the software. SW=5.0.0 Boot Image=3.1.60 BUILD_NUMBER=3xx BUILD_VERSION=5.0.0 |
With the above information the Admin performs the following steps for creating the device profiles.
Create Device management tag set example : SBC1000_dm-Tags, SBC2000_dm-Tags. All the tags that will be defined by Sonus will be under this.
Device profile represent the devices itself. Device profile will be named -SBC2000_dm.
Following options will be set:
Option | Value selected |
---|---|
Device Access File Format | SBC2000_config.xml |
Repository File Format | SBC2000_config-%BWTIMESTAMP%.xml |
File Category | Dynamic Per-Type |
File Customization | Administrator and User |
Enable Caching | NO |
File Authentication | User Name and Password |
MAC Address in | Not Applicable for system configuration file |
HTTP Authentication | Digest |
Allowed Access Protocols | HTTPS |
Following options will be set:
Option | Value selected | Notes |
---|---|---|
Device Access File Format |
| |
Repository File Format | %BWFQDEVICEID%.xml | This is an ID uniquely identifying a device (Fully Qualified Device ID). |
File Category | Dynamic Per-Device | |
File Customization | Administrator and User | |
Enable Caching | NO | |
File Authentication | User Name and Password | |
MAC Address in | HTTP Request URI | |
HTTP Authentication | Digest | |
Allowed Access Protocols | HTTPS |
Options for static files - boot image and firmware image will be set.
Option | Value selected |
---|---|
Device Access File Format |
|
Repository File Format |
|
File Category | Static |
File Customization | Administrator and User |
Enable Caching | NO |
File Authentication | User Name and Password |
MAC Address in | Not Applicable |
HTTP Authentication | Digest |
Allowed Access Protocols | HTTPS |
After the device type is configured, BroadWorks will provide Sonus with the following information:
The above information will be used for Broadworks Provisioning and SBC configuration (File URL).
BroadWorks Provisioning involves the following steps:
BroadWorks Provisioning requires an authenticated user. The SIP NOTIFY message will be sent to this user.
Click Add to add an Auto Configuration User.
Click OK to create the new user.
Click OK.
Click OK to return to the User Profile.
Click OK to return to Utilities.
Device profile instance defines the template for the device type. Multiple device profile types can be created for a device type. This configuration specifies the profile instance name and sets the username and password for using this profile.
The following steps are for creating a custom template for your deployments
The tags are identified by a keyword starting and ending with "%" character (for example, "%BWMACADDRESS%). A tag name is case sensitive. There are predefined set of tags defined by Broadworks Device Management; the first two characters of the tags start with "BW". Tags are replaced with the actual parameter values in the configuration files. Some configuration settings can be generic (i.e., domain name, Time Zone, DNS server) and are applicable to many devices. Some configuration settings are specific to each node (i.e., Device Name, IP address). System tags are created for system-wide use; device-specific tags are created for individual nodes.
System Tags example
Tag | Parameter Value |
---|---|
%DOMAIN_NAME% | sonus.net |
%TIME_ZONE% | Pacific |
%PRIMARY_DNS% | 134.56.113.11 |
%SECONDARY_DNS% | 134.56.112.12 |
Device Specific Tags example
Tag | Parameter Value |
---|---|
%DEVICE_NAME% | nebulous |
%ETH1_PRIMARY_IP% | 134.56.216.214 |
%FILE_DS_TCA_HIGH% | 10000 |
%FILE_DS_TCA_LOW% | 5000 |
%CPU_TCA_HIGH% | 90 |
%CPU_TCA_LOW% | 70 |
To add these tags:
Select the device profile type created and click Edit.
The Configure Device Profile Modify Page is displayed. From this Page, select Custom Tags. On the custom Tags page, click Add to provision each device tag.
Values should be assigned to all the Tags defined.
Template files contains tags, these tags are replaced with actual values specified in the above step and a configuration file will be generated.
System Template Files. These configuration template files are specific to a profile and the configuration file generated can be used by all the users registered for this profile. Only one configuration file will be generated for each profile type. For example, when the system template file tags are replaced for SBC2000-TCA-profile, SBC2000_config.xml
file is generated. This file can be used by all SBC2000 nodes registered for this profile type.
Device Template Files. This configuration template is specific to a node and the configuration file generated can only be used by that node. A new device profile configuration will be generated for each device.
Both the system template and device template files should be added.
Rebuild options generates the configuration file replacing the tag values.
Template File Format | Configuration File |
---|---|
|
|
Static Files are added similarly.
Add users to the profile instance.
For detailed information about configuring the Sonus
Before downloading files from BroadWorks XSP configure the following:
All configuration is completed through the WebUI.
Click OK.
Click OK.
Click OK to save changes.
View the Authenticated User Contact Registrant Table with the new entry.
Click OK to save changes
View the new Authenticated User Remote Authorization entry.
Click Ok.
Click OK.
View the new Broadsoft server entry.
When a SIP device sends a REGISTER request, the TO and FROM headers must match the provisioned AoR. The next steps will modify the FROM header to equal the TO header.
Click OK.
Two XSP Certificates are supplied by Broadsoft. Install the Certificates as follows:
Repeat step 4 to import the second XSP Certificate.
The step enables you to configure the SBC to download configuration files from the Broadsoft server automatically when a SIP NOTIFY message is received. The files are downloaded according to the configuration options in the WebUI's AutoConfiguration setup as follows:
Click Apply. Updates are performed in the following order: Boot Image, Firmware, and Configuration Update. The system reboots following configuration.
This step is completed by a BroadWorks administrator.
Click Reset the Phones to start the Download from the XSP server.