HP-UX C SIP Stack Programmer's Guide (Novembery 2007)

Creating an Application 37
Configuration
Sample Code
The following code demonstrates how to instruct the call-leg layer to print only
INFO and ERROR messages to the Log.
/*==========================================================================*/
RvSipStackCfg stackCfg;
RvSipStackInitCfg(sizeof(stackCfg), &stackCfg));
stackCfg.callLogFilters = RVSIP_LOG_INFO_FILTER | RVSIP_LOG_ERROR_FILTER;
/*==========================================================================*/
Sample Code
The following code demonstrates how to set the Log filters for all layers of the
SIP Stack simultaneously. In this sample, each layer is instructed to print only
the DEBUG and WARN messages to the Log.
/*==========================================================================*/
RvSipStackCfg stackCfg;
RvSipStackInitCfg(sizeof(stackCfg), &stackCfg);
stackCfg.defaultLogFilters = RVSIP_LOG_DEBUG_FILTER | RVSIP_LOG_WARN_FILTER;
/*==========================================================================*/
Note For more information about working with the Log, see the the SIP Stack
Log chapter.
RVSIP_LOG_ERROR_FILTER An error such as faulty application behavior,
insufficient allocations, or illegal network
activity. These errors are identified and handled
by the SIP Stack.
RVSIP_LOG_LOCKDBG_FILTER The details of all the locking operations of the
Stack.
RVSIP_LOG_ENTER_FILTER Indicates that an API function was called. This
filter effects the logging of the Core and ADS
modules only.
RVSIP_LOG_LEAVE_FILTER Indicates that an API function call was
completed. This filter effects the logging of the
Core and ADS modules only.
Table 4-1 Log Filters