How to use Advanced Logging SPL to trace a specific call in debugs
(Doc ID 2214188.1)
Last updated on MARCH 12, 2021
Applies to:Net-Net OS - Version E-Cz7.3.0 to E-Cz7.4.0 [Release E-Cz7.0]
Information in this document applies to any platform.
With regular sipd debugs, the SBC logs all traffic passing through the system when sipd debugs is enabled.
If a big amount of calls are being processed by the SBC at that time, it will fill up the logfiles (like log.sipd and sipmsg.log) and eventually will start overwrite new data once the maximum amount of logfiles are full. This could lead to the call trying to be traced to be missed and overwritten with new data.
Advanced Logging is introduced in ECZ730m2 and later to help on this matter.
Advanced Logging allows targeted logging by over riding log levels, so that only a specific SIP request and its related messages are logged. The system matches criteria that you configure to determine which requests to log. The system also logs all messages related to the request, such as any responses, in-dialog messages, media, timers, and so on. Advanced Logging supports multiple matching criteria for incoming requests and rate limiting. Advanced log files are smaller than debug files because the system logs only the specified number of matches in the specified period of time. Since the files are smaller, Advanced Logging uses fewer system resources than debug logging. To make searching easier, the system labels each log.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document