Difference between revisions of "SIP OPTIONS/SUBSCRIBE/NOTIFY"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | * this feature is disabled by default because it can overload the database | + | * this feature is disabled by default because it can overload the database or storage |
== Required configuration == | == Required configuration == | ||
− | * you need to enable the processing in the sensor | + | * you need to enable the processing in the sensor's /etc/voipmonitor.conf |
Line 26: | Line 26: | ||
== The GUI Usage == | == The GUI Usage == | ||
− | * in the '''GUI->SIP Opt.,Subsc.,Notify''' you can see/filter/delete these types of the SIP messages | + | * in the '''GUI->SIP Opt.,Subsc.,Notify''' you can see/filter/delete these types of the SIP OPTIONS/SUBSCRIBE/NOTIFY messages |
Revision as of 13:36, 12 April 2019
- this feature is disabled by default because it can overload the database or storage
Required configuration
- you need to enable the processing in the sensor's /etc/voipmonitor.conf
See this part of the voipmonitor.conf and adjust it.
# analyze sip OPTION messages, default NO sip-options = no # store OPTIONS to disk (in extreme traffic it might overload file system), default NO save-sip-options = no # analyze sip SUBSCRIBE messages, default NO sip-subscribe = no # store SUBSCRIBE to disk (in extreme traffic it might overload file system), default NO save-sip-subscribe = no # analyze sip NOTIFY messages, default NO sip-notify = no # store NOTIFY to disk (in extreme traffic it might overload file system), default NO save-sip-notify = no
The GUI Usage
- in the GUI->SIP Opt.,Subsc.,Notify you can see/filter/delete these types of the SIP OPTIONS/SUBSCRIBE/NOTIFY messages