MESSAGES: Difference between revisions

From VoIPmonitor.org
(Created page with "MESSAGE method is an extension to the Session Initiation Protocol (SIP) that allows the transfer of Instant Messages. Since the MESSAGE request is an extension to SIP, it inh...")
 
(Add distributed architecture configuration location section)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
MESSAGE method is an extension to the Session Initiation Protocol (SIP) that allows the transfer of Instant Messages.  Since the MESSAGE request is an extension to SIP, it inherits all the request routing and security features of that protocol.  MESSAGE requests carry the content in the form of MIME body parts.  MESSAGE requests do not themselves initiate a SIP dialog; under normal usage each Instant Message stands alone, much like pager messages.  MESSAGE requests may be sent in the context of a dialog initiated by some other SIP request.
== SIP MESSAGE Method ==


http://tools.ietf.org/html/rfc3428
The SIP MESSAGE method is an extension to SIP for transferring instant messages. It inherits SIP's routing and security features. Messages carry content as MIME body parts and typically stand alone without initiating a dialog, similar to pager messages. They can also occur within an existing dialog.
 
[http://tools.ietf.org/html/rfc3428 RFC 3428]


[[File:messages.png]]
[[File:messages.png]]
=== Required Configuration ===
Enable in '''/etc/voipmonitor.conf''':
# Enable or disable the analysis and storage of SIP MESSAGE requests. The default is 'yes'.
# THIS METHOD IS USED EXCLUSIVELY FOR CARRYING TEXT MESSAGES (INSTANT MESSAGING) OVER SIP.
sip-message = yes
=== Configuration Location in Distributed Architecture ===
In distributed/client-server deployments, the location where you must configure <code>sip-message</code> depends on your <code>packetbuffer_sender</code> configuration:
{| class="wikitable"
|-
! Mode !! Configuration Location !! Processing Location
|-
| '''<code>packetbuffer_sender = yes</code>''' (Packet Mirroring) | Central server | Central server processes raw packets from remote sensors
|-
| '''<code>packetbuffer_sender = no</code>''' (Local Processing) | Remote sensor | Each sensor processes packets locally before sending CDRs to central server
|}
To determine where to configure <code>sip-message</code>:
;1. Check the <code>packetbuffer_sender</code> setting on your remote sensors:
<syntaxhighlight lang="bash">
grep packetbuffer_sender /etc/voipmonitor.conf
</syntaxhighlight>
;2. If <code>packetbuffer_sender = yes</code>:
* Configure <code>sip-message</code> on the **central server's** <code>/etc/voipmonitor.conf</code>
* Restart the voipmonitor service on the central server
;3. If <code>packetbuffer_sender = no</code> (or not set):
* Configure <code>sip-message</code> on the **remote sensor's** <code>/etc/voipmonitor.conf</code>
* Restart the voipmonitor service on the remote sensor(s)
For detailed information on distributed architectures and configuration locations, see [[Sniffer_distributed_architecture]].
=== GUI Usage ===
Access via '''GUI > SIP Messages''' to view, filter, or delete these messages. Stored messages include text content for review and analysis.
=== AI Summary for RAG ===
'''Summary:''' This article describes the SIP MESSAGE method for instant messaging in VoIPmonitor. It covers its purpose per RFC 3428, default-enabled configuration in voipmonitor.conf, and GUI access for viewing and managing messages. In distributed architectures, configure <code>sip-message</code> on the central server if <code>packetbuffer_sender=yes</code> (Packet Mirroring), or on remote sensors if <code>packetbuffer_sender=no</code> (Local Processing).
'''Keywords:''' SIP MESSAGE, instant messaging, RFC 3428, voipmonitor.conf, text messages, MIME, dialog-independent, distributed architecture, packetbuffer_sender, central server, remote sensor, configuration location
'''Key Questions:'''
* What is the SIP MESSAGE method used for?
* How do I enable or disable SIP MESSAGE processing in VoIPmonitor?
* Where can I view SIP MESSAGE requests in the GUI?
* Does SIP MESSAGE initiate a dialog?
* What RFC defines the SIP MESSAGE extension?
* Where do I configure sip-message in distributed architecture?
* Should I configure sip-message on central server or remote sensor?

Latest revision as of 20:18, 5 January 2026

SIP MESSAGE Method

The SIP MESSAGE method is an extension to SIP for transferring instant messages. It inherits SIP's routing and security features. Messages carry content as MIME body parts and typically stand alone without initiating a dialog, similar to pager messages. They can also occur within an existing dialog.

RFC 3428

Required Configuration

Enable in /etc/voipmonitor.conf: 

# Enable or disable the analysis and storage of SIP MESSAGE requests. The default is 'yes'.
# THIS METHOD IS USED EXCLUSIVELY FOR CARRYING TEXT MESSAGES (INSTANT MESSAGING) OVER SIP.
sip-message = yes

Configuration Location in Distributed Architecture

In distributed/client-server deployments, the location where you must configure sip-message depends on your packetbuffer_sender configuration:

Mode Configuration Location Processing Location
Central server | Central server processes raw packets from remote sensors
Remote sensor | Each sensor processes packets locally before sending CDRs to central server

To determine where to configure sip-message:

1. Check the packetbuffer_sender setting on your remote sensors
grep packetbuffer_sender /etc/voipmonitor.conf
2. If packetbuffer_sender = yes
  • Configure sip-message on the **central server's** /etc/voipmonitor.conf
  • Restart the voipmonitor service on the central server
3. If packetbuffer_sender = no (or not set)
  • Configure sip-message on the **remote sensor's** /etc/voipmonitor.conf
  • Restart the voipmonitor service on the remote sensor(s)

For detailed information on distributed architectures and configuration locations, see Sniffer_distributed_architecture.

GUI Usage

Access via GUI > SIP Messages to view, filter, or delete these messages. Stored messages include text content for review and analysis.

AI Summary for RAG

Summary: This article describes the SIP MESSAGE method for instant messaging in VoIPmonitor. It covers its purpose per RFC 3428, default-enabled configuration in voipmonitor.conf, and GUI access for viewing and managing messages. In distributed architectures, configure sip-message on the central server if packetbuffer_sender=yes (Packet Mirroring), or on remote sensors if packetbuffer_sender=no (Local Processing).

Keywords: SIP MESSAGE, instant messaging, RFC 3428, voipmonitor.conf, text messages, MIME, dialog-independent, distributed architecture, packetbuffer_sender, central server, remote sensor, configuration location

Key Questions:

  • What is the SIP MESSAGE method used for?
  • How do I enable or disable SIP MESSAGE processing in VoIPmonitor?
  • Where can I view SIP MESSAGE requests in the GUI?
  • Does SIP MESSAGE initiate a dialog?
  • What RFC defines the SIP MESSAGE extension?
  • Where do I configure sip-message in distributed architecture?
  • Should I configure sip-message on central server or remote sensor?
Retrieved from "https://www.voipmonitor.org/doc/index.php?title=MESSAGES&oldid=7315"