This section explains how the SBC manages STIR/SHAKEN operations logging.

The SBC creates a separate log file named "stirmsg.log" to record all STIR/SHAKEN transactions. This effectively separates STIR/SHAKEN logs from SIPD (Session Initiation Protocol Daemon) logs and facilitates the collection of STIR/SHAKEN details without adversely impacting the performance of the SBC.

You use this file for STIR/SHAKEN troubleshooting purposes. It can be especially useful when troubleshooting encrypted transactions using TLS 1.2 later TLS 1.3. You can display the contents of this log from the ACLI using the following command.

ORACLE#show logfile /opt/logs/stirmsg.log

You can configure the verbosity level of these STIR/SHAKEN logs:

• Set the log level for SIPD to debug and logType to STIR to get STIR logs in log.sipd.

  ORACLE#log-level sipd debug STIR

• Reset the log level for SIPD to no-debug for logtype STIR.

  ORACLE#log-level sipd notice STIR