summaryrefslogtreecommitdiff
path: root/BUGS
diff options
context:
space:
mode:
authorMatt Jordan <mjordan@digium.com>2015-12-13 13:09:42 -0600
committerMatt Jordan <mjordan@digium.com>2015-12-31 21:27:39 -0600
commit9cdf3ec19d998dc5ae1dbfdc728588a30a724dbc (patch)
treef6ab2795215bfd6cbe054506e66ee551ed0579d3 /BUGS
parent410c5ee0fc5f1ba8bc25ca6e2cdc11527f36b1b7 (diff)
res_pjsip_history: Add a module that provides PJSIP history for debugging
This patch adds a new module, res_pjsip_history, that provides a slightly better way of debugging SIP message traffic on a busy Asterisk system. The existing mechanisms all rely on passively dumping a SIP message to the CLI. While this is perfectly fine for logging purposes and well controlled environments, on many installations, the amount of SIP messages Asterisk receives will quickly swamp the CLI. This makes it difficult to view/capture those messages that you want to diagnose in real time. This patch provides another way of handling this. When enabled, the module will store SIP message traffic in memory. This traffic can then be queried at leisure. In order to make the querying useful, a CLI command has been implemented, 'pjsip show history', that supports a basic expression syntax similar to SQL or other query languages. A small number of useful fields have been added in this initial patch; additional fields can easily be added in later improvements. Those fields are: - number: The entry index in the history - timestamp: The time the message was recieved - addr: The source/destination address of the message - sip.msg.request.method: The request method - sip.msg.call-id: The Call-ID header Note - this is a resurrection of the module initially proposed on Review Board here: https://reviewboard.asterisk.org/r/4053/ Change-Id: I39bd74ce998e99ad5ebc0aab3e84df3a150f8e36
Diffstat (limited to 'BUGS')
0 files changed, 0 insertions, 0 deletions