Creating and Modifying Subsystem Logging

Through the Subsystem Configuration table, you are able to create or modify Subsystem Logging.

The log format for the  includes the container name with the subsystem. See the following example: [2020-11-24 15:54:36,947] 3573 0001 swelite-sc-6cb6fb599-cbgg8.com.sonus.sbc.sip ERROR (SlbInterfaceLayer.cpp:2958) - "PerformSlbServiceDiscoveryUsingKubeApi:"

Creating Subsystem Logging

1. In the WebUI, click the Settings tab.

2. In the left navigation pane, go to Logging Configuration > Subsystems.

   Subsystem Configuration

   

3. Click the Create Subsystem ( ) icon at the top of the Subsystem Configuration page.

   Subsystem Configuration

   

4. From the Subsystem Name drop down list, select a Subsystem Name to log.

   Subsystem Name Options

    

   Subsystems Supported

   Subsystems Supported
   Active Directory Service. Communicates with the AD server for user authentication.
   Alarm Service. Provides alarms/events rendered in the system.
   Analog Manufacturing Test Tool. Not used for production.
   BMP. UX own/property service used by the SBC Edge Portfolio WebUI's Real Time Monitor view.
   CAS Protocol. Proves CAS protocol support through FXS, FXO, E&M, and R2 signaling interfaces.
   Call Admission Control. Limits the number of calls for a signaling group across the entire cluster. Note: Applicable only to the .
   Call Routing Service. Routes calls through signaling groups, which enables calls to be carried between ports and protocols (i.e., ISDN to SIP).
   Certificate Security Manager. Manages the Signed certificate on the SBC Edge Portfolio, including generating, importing, and exporting server certificates.
   Cloud Network Service. Allocates and associates the public IP address (configured through the network segment) to the media and signaling components. The Cloud Network Service also moves the public IP address from the old active SLB to the new active SLB during an SLB failover. Note: Applicable only to the .
   Common Call Control. Provides protocol neutral call and signaling handling, and call transfers.
   Common Transport Service. Used for transport connections by subsystems such as SIP, Radius, and BMP.
   Configuration System. Manages all facets of the SBC Edge Portfolio configuration, including configuration options in the Easy Configuration Wizard and options available under the Settings tab in the WebUI.
   Core Switching/Routing. Routes calls between Signaling Groups (each signaling group represents a device or system). A signaling group describes the source call and points to a route (Call Route table, which can contain on or more Call Route entries.)
   DSP Tone Generator. Used for debugging the TPAD library of the SBX core library.
   DSP Transcoder. Used for debugging the XPAD DSP library of the SBX core library.
   Dynamic Hosts. Allows resolution of the FQDN/Host name in case of dynamic IP changes.
   EVAgent. Provides a view of the current connection and the remote UI state of the EdgeView connection.
   Hosts. Enables configuration of FQDN/Host name and IP address.
   Split DNS. Enables Domain Specific DNS Server (Split-DNS) to resolve FQDNs.
   ISDN Protocol. Supports ISDN on the SBC Edge Portfolio DS1 interface; each DS1 interface can be configured for T1 or E1.
   Logging System. Troubleshoots issues such as call signaling, call quality and performance by collecting activity logs from its subsystems.
   Media Stream Control Service. Enables media control streaming mode for audio, fax and media transmission.
   Media System. Hosts media interfaces and configures the media plane to receive and send media. Interfaces with the signaling component, which controls media port allocation and media resource activation. Note: Applicable only to the .
   Operating System Logs. Provides logging details for system operations.
   Platform Management. Manages the supported platforms for the SBC Edge Portfolio.
   Radius Management Service. Provides authentication services for Radius Authentication Server(s).
   Resource Management. Manages the resource consumption in the SBC Edge Portfolio, including DSPs, SIP sessions, channel usage, etc.
   Security. Manages security on the SBC through a number of methods.
   Signaling Load Balancer. Handles incoming and outgoing signaling traffic. Note: Applicable only to the .
   SIP Stack Service. Normalizes signaling and media negotiation to internal messages.
   SNMP. Manages Simple Network Management Protocol (SNMP) on the SBC Edge Portfolio.
   Statistics & Live Info. Presents statistics for the SBC Edge Portfolio, such as Call Detail Records (CDRs), DSP Module, Active Directory, MSTI, and IPsec.
   Survivable Branch Appliance. Monitors the communication between the SBC and the Microsoft Survivable Branch Appliance (SBA)/Application Solution Module (ASM) module.
   System Health Monitoring. Monitors the health of the system for module/cards, ports and signaling groups.
   System I/O Service. Used for device management such as TDM time slots, LED status, I2C bus, etc.
   System Timer Service. Unused.
   Telephony Interface Process. Manages interfaces, such as FXS, FXO, T1-PSTN, and BRI.
   Trap Service (SNMP). Used for SNMP and Traps.
   User Authentication Service. Authenticates user and grants access/permissions.

5. From the Log Level drop down list, select a logging level to use for this subsystem. For log level definitions, refer to Supported Logging Levels.

   Modify Subsystem Name

   

6. From the Log Destination drop down list, select a location to send the log from the Log Destination menu. Refer to Managing Local Logs and Managing Remote Log Servers.

   Modify Log Destination

   
7. Click OK.

Modifying a Subsystem Logging

1. In the WebUI, click the Settings tab.
2. In the left navigation pane, go to Logging Configuration > Subsystems.

3. Click the expand () Icon next to the entry you wish to modify.

   Modify Subsystem Configuration

   
4. Edit the entry properties as required, see details above.
5. Click Apply.