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

For Subsystem configuration options, refer to Applying Log Profile and Saving Log Profile.

Creating Subsystem Logging

If Default was selected in the Log Level menu, the Global Logging Level configuration will be assumed for the associated Log Destination.

  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.Media Stream Control Service. Enables media control streaming mode for audio, fax and media transmission.
    Alarm Service. Provides alarms/events rendered in the system.Network Services. Provides network services, such as managing the DHCP server and client.
    Analog Manufacturing Test Tool. Not used for production.Operating System Logs. Provides logging details for system operations.
    BMP. UX own/property service used by the SBC Edge WebUI's Real Time Monitor view.Platform Management. Manages the supported platforms for the SBC Edge.
    CAS Protocol. Proves CAS protocol support through FXS, FXO, E&M, and
    R2 signaling interfaces.
    Radius Management Service. Provides authentication services for Radius Authentication Server(s).
    Call Routing Service. Routes calls through signaling groups, which enables calls
    to be carried between ports and protocols (i.e., ISDN to SIP).
    Resource Management. Manages the resource consumption in the SBC Edge, including DSPs, SIP sessions, channel usage, etc.
    Certificate Security Manager. Manages the Signed certificate on the SBC Edge, including generating, importing, and exporting server certificates.Security. Manages security on the SBC through a number of methods.
    Common Call Control. Provides protocol neutral call and signaling handling, and call transfers.SIP Stack Service. Normalizes signaling and media negotiation to internal messages.
    Common Transport Service. Used for transport connections by subsystems such as SIP, Radius, and BMP.SNMP. Manages Simple Network Management Protocol (SNMP) on the SBC Edge.
    Configuration System. Manages all facets of the SBC Edge configuration, including configuration options in the Easy Configuration Wizard and options available under the Settings tab in the WebUI.Statistics & Live Info. Presents statistics for the SBC Edge, such as Call Detail Records (CDRs), DSP Module, Active Directory, MSTI, and IPsec.
    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.)Survivable Branch Appliance. Switches Lync VoIP calls from the network to the PSTN within the Application Solution Module (ASM) that hosts the Microsoft SBA component.
    Dynamic Hosts. Allows resolution of the FQDN/Host name in case of dynamic IP changes.System Health Monitoring. Monitors the health of the system for module/cards, ports and signaling groups.
    Hosts. Enables configuration of FQDN/Host name and IP address.System I/O Service. Used for device management such as TDM time slots, LED status, I2C bus, etc.
    Split DNS. Enables Domain Specific DNS Server (Split-DNS) to resolve FQDNs.System Timer Service. Unused.
    ISDN Protocol. Supports ISDN on the SBC Edge DS1 interface; each DS1 interface
    can be configured for T1 or E1. 
    Telephony Interface Process. Manages interfaces, such as FXS, FXO, T1-PSTN, and BRI.
    License Management Service. Provides licenses for features and supplementary services.Trap Service (SNMP). Used for SNMP and Traps.
    Logging System. Troubleshoots issues such as call signaling, call quality and performance by collecting activity logs from its subsystems.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.