SIP OPTIONS/SUBSCRIBE/NOTIFY: Difference between revisions

From VoIPmonitor.org
Jump to navigation Jump to search
No edit summary
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
* this feature is disabled by default because it can overload the database
== SIP OPTIONS, SUBSCRIBE, and NOTIFY Messages ==


== Required configuration ==
This feature processes SIP OPTIONS (qualify pings), SUBSCRIBE, and NOTIFY messages. It is disabled by default to prevent database or storage overload in high-traffic scenarios.


* you need to enable the processing in the sensor
=== Required Configuration ===


Enable processing in '''/etc/voipmonitor.conf'''. Adjust or add these settings:


See this part of the voipmonitor.conf and adjust it.
# Controls the analysis of SIP OPTIONS, 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'.
  # analyze sip OPTION messages, default NO
  sip-options = no
  sip-options = no
  # store OPTIONS to disk (in extreme traffic it might overload file system), default 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-options = no
   
   
  # analyze sip SUBSCRIBE messages, default NO
  # Enable or disable the analysis and storage of SIP SUBSCRIBE requests. Default is 'no'.
  sip-subscribe =  no
  sip-subscribe = no
  # store SUBSCRIBE to disk (in extreme traffic it might overload file system), default 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
  save-sip-subscribe = no
   
   
  # analyze sip NOTIFY messages, default 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 (in extreme traffic it might overload file system), default 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
  save-sip-notify = no


To enable OPTIONS pings (qualify evaluation), set '''sip-options = yes'''.
=== GUI Usage ===
Access via '''GUI > SIP Opt., Subsc., Notify''' to view, filter, or delete these messages.
* '''Settings''': Configure max OK qualify duration (default: 2000ms) and additional OK response codes (e.g., 404).
* '''Active/Stored Views''': Green records indicate OK (no timeout exceeded, 200 OK response). Red records show failures (other responses or timeouts).
* '''Alerts''': Use "SIP Opt/Sub/Notify Qualify" alert type for red records.
This setup allows monitoring OPTIONS pings like heartbeat checks for availability, providing statistics similar to ICMP ping (e.g., latency, response codes).
=== AI Summary for RAG ===
'''Summary:''' This article covers enabling and using SIP OPTIONS (qualify pings), SUBSCRIBE, and NOTIFY in VoIPmonitor. It explains default disabled state to avoid overload, configuration options in voipmonitor.conf, and GUI features for viewing, settings, and alerts.


== The GUI Usage ==
'''Keywords:''' SIP OPTIONS, qualify ping, SUBSCRIBE, NOTIFY, voipmonitor.conf, GUI settings, alerts, storage overload, response codes, latency monitoring


* in the '''GUI->SIP Opt.,Subsc.,Notify''' you can see/filter/delete these types of the SIP messages
'''Key Questions:'''
* Why is SIP OPTIONS processing disabled by default?
* How do I enable SIP OPTIONS for qualify pings?
* What configuration options control storage of these messages?
* How can I view and filter OPTIONS/SUBSCRIBE/NOTIFY in the GUI?
* How do I set up alerts for failed qualify pings?
* What do green and red records mean in the SIP Opt. views?
* How does this feature help monitor endpoint availability without ICMP?

Latest revision as of 13:28, 10 November 2025

SIP OPTIONS, SUBSCRIBE, and NOTIFY Messages

This feature processes SIP OPTIONS (qualify pings), SUBSCRIBE, and NOTIFY messages. It is disabled by default to prevent database or storage overload in high-traffic scenarios.

Required Configuration

Enable processing in /etc/voipmonitor.conf. Adjust or add these settings: 

# Controls the analysis of SIP OPTIONS, 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

To enable OPTIONS pings (qualify evaluation), set sip-options = yes.

GUI Usage

Access via GUI > SIP Opt., Subsc., Notify to view, filter, or delete these messages.

  • Settings: Configure max OK qualify duration (default: 2000ms) and additional OK response codes (e.g., 404).
  • Active/Stored Views: Green records indicate OK (no timeout exceeded, 200 OK response). Red records show failures (other responses or timeouts).
  • Alerts: Use "SIP Opt/Sub/Notify Qualify" alert type for red records.

This setup allows monitoring OPTIONS pings like heartbeat checks for availability, providing statistics similar to ICMP ping (e.g., latency, response codes).

AI Summary for RAG

Summary: This article covers enabling and using SIP OPTIONS (qualify pings), SUBSCRIBE, and NOTIFY in VoIPmonitor. It explains default disabled state to avoid overload, configuration options in voipmonitor.conf, and GUI features for viewing, settings, and alerts.

Keywords: SIP OPTIONS, qualify ping, SUBSCRIBE, NOTIFY, voipmonitor.conf, GUI settings, alerts, storage overload, response codes, latency monitoring

Key Questions:

  • Why is SIP OPTIONS processing disabled by default?
  • How do I enable SIP OPTIONS for qualify pings?
  • What configuration options control storage of these messages?
  • How can I view and filter OPTIONS/SUBSCRIBE/NOTIFY in the GUI?
  • How do I set up alerts for failed qualify pings?
  • What do green and red records mean in the SIP Opt. views?
  • How does this feature help monitor endpoint availability without ICMP?
Retrieved from "https://www.voipmonitor.org//doc/index.php?title=SIP_OPTIONS/SUBSCRIBE/NOTIFY&oldid=5704"