SIP OPTIONS/SUBSCRIBE/NOTIFY: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
== Required configuration == | == Required configuration == | ||
* you need to enable | * you need to enable its processing in the sensor's /etc/voipmonitor.conf | ||
See this part of the voipmonitor.conf and adjust it. | See this part of the voipmonitor.conf and adjust/add it. | ||
# | # Controls the analysis of SIP OPTION, SUBSCRIBE, NOTIFY messages. They can be stored to a PCAP file, seen in SIP Opt. Active, or also stored to the Database. | ||
# Default is 'no'. Options include 'yes', 'nodb', and 'no'. | |||
sip-options = no | sip-options = no | ||
# | # Controls whether to store SIP OPTIONS messages to disk. Note that in situations of high traffic, this could overload the file system. Default is 'no'. | ||
#save-sip-options = no | |||
save-sip- | |||
# | # Enable or disable the analysis and storage of SIP SUBSCRIBE requests. Default is 'no'. | ||
sip-subscribe = no | |||
# Controls whether to store SIP SUBSCRIBE messages to disk. Like OPTIONS, this could overload the system in high-traffic scenarios. Default is 'no'. | |||
#save-sip-subscribe = no | |||
# Enable or disable the analysis and storage of SIP NOTIFY requests. Default is 'no'. | |||
sip-notify = no | sip-notify = no | ||
# store NOTIFY to disk | |||
save-sip-notify = no | # Controls whether to store SIP NOTIFY messages to disk. This is similar to OPTIONS and SUBSCRIBE in that it can overload the system in high-traffic scenarios. Default is 'no'. | ||
#save-sip-notify = no | |||
== The GUI Usage == | == The GUI Usage == | ||
* in the '''GUI->SIP Opt.,Subsc.,Notify''' you can see/filter/delete these types of the SIP OPTIONS/SUBSCRIBE/NOTIFY messages | * in the '''GUI->SIP Opt.,Subsc.,Notify''' you can see/filter/delete these types of the SIP OPTIONS/SUBSCRIBE/NOTIFY messages | ||
Latest revision as of 21:19, 20 June 2024
- this feature is disabled by default because it can overload the database or storage
Required configuration
- you need to enable its processing in the sensor's /etc/voipmonitor.conf
See this part of the voipmonitor.conf and adjust/add it.
# Controls the analysis of SIP OPTION, SUBSCRIBE, NOTIFY messages. They can be stored to a PCAP file, seen in SIP Opt. Active, or also stored to the Database. # Default is 'no'. Options include 'yes', 'nodb', and 'no'. sip-options = no # Controls whether to store SIP OPTIONS messages to disk. Note that in situations of high traffic, this could overload the file system. Default is 'no'. #save-sip-options = no # Enable or disable the analysis and storage of SIP SUBSCRIBE requests. Default is 'no'. sip-subscribe = no # Controls whether to store SIP SUBSCRIBE messages to disk. Like OPTIONS, this could overload the system in high-traffic scenarios. Default is 'no'. #save-sip-subscribe = no # Enable or disable the analysis and storage of SIP NOTIFY requests. Default is 'no'. sip-notify = no # Controls whether to store SIP NOTIFY messages to disk. This is similar to OPTIONS and SUBSCRIBE in that it can overload the system in high-traffic scenarios. Default is '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