Monitoring

• STUN Server Statistics—You can display statistics for the STUN server using the ACLI show mbcd stun command when the STUN server has been enabled. However, if the STUN server has not been enabled since the last system reboot, the command does not appear and no statistics will be displayed.
• STUN Protocol Tracing—You can enable STUN protocol tracing two ways: by configuration or on demand.
  • By configuration—The Oracle® Enterprise Session Border Controller’s STUN protocol trace file is called stun.log, which is classified as a call trace. This means that when the system configuration’s call-trace parameter is set to enabled, you will obtain STUN protocol information for the system. As with other call protocol traces, tracing data is controlled by the log-filter in the system configuration.
  • On demand—Using the ACLI notify mbcd log or notify mbcd debug commands, you enable protocol tracing for STUN. Using notify mbcd debug sets the STUN log level to TRACE. You can turn off tracing using the notify mbcd onlog or notify mbcd nodebug commands. Using notify mbcd nodebug returns the STUN log level back to its configured setting.