Need Feedback On The Use Of AMI Events Generated By MESSAGE Requests

Home » Uncategorized » Need Feedback On The Use Of AMI Events Generated By MESSAGE Requests
Uncategorized 7 Comments

–000000000000cbeb58059d4c637c Content-Type: text/plain; charset=”UTF-8″

For those of you who actually process SIP MESSAGE requests… Do you use any of the AMI events generated by the “Message/ast_msg_queue” channel?
We want to change that channel to an “internal” channel that doesn’t generate AMI events (for performance reasons) but we need to know if anyone’s using them first.

Thanks!

7 thoughts on - Need Feedback On The Use Of AMI Events Generated By MESSAGE Requests

  • Hello,

    I use UserEvents generated by the Message/ast_message_queue channel with the UserEvent application.

    Regards

    Jean

    Le 29/01/2020 à 20:31, George Joseph a écrit :

  • –00000000000097f0de059d5d2380
    Content-Type: text/plain; charset=”UTF-8″
    Content-Transfer-Encoding: quoted-printable

    Thanks Jean. We’re looking at alternatives.

  • –000000000000ea32ed059d5d2d01
    Content-Type: text/plain; charset=”UTF-8″

    Do you use any aspects of the channel itself in the user events, or merely the contents of the user event and what you’ve placed in it?

  • Le 30/01/2020 à 16:33, Joshua C. Colp a écrit :
    We only use the contents of the user event. These contents are populated with data from the MESSAGE and MESSAGE_DATA functions.

  • Same question as I sent to Jean Aunis then – do you use any of the channel data or strictly the user event part?

  • –000000000000a7d715059e038b66
    Content-Type: text/plain; charset=”UTF-8″
    Content-Transfer-Encoding: quoted-printable

    Here’s a copy of the commit message which should explain things…

    message.c: Add option to suppress the Message channel AMI and ARI events

    In order to reduce the amount of AMI and ARI events generated,
    the global “Message/ast_msg_queue” channel can be set to suppress
    it’s normal channel housekeeping events such as “Newexten”,
    “VarSet”, etc. This can greatly reduce load on the manager
    and ARI applications when the Digium Phone Module for Asterisk
    is in use. To enable, set “hide_messaging_ami_events” in
    asterisk.conf to “yes” In Asterisk versions <18, the default
    is "no" preserving existing behavior. Beginning with
    Asterisk 18, the option will default to "yes".

    NOTE: This change does not affect UserEvents or the ARI
    TextMessageReceived events.

    * Added the “hide_messaging_ami_events” option to asterisk.conf.

    * Changed message.c to set the AST_CHAN_TP_INTERNAL property on
    the “Message/ast_msg_queue” channel if the option is set in
    asterisk.conf. This suppresses the reporting of the events.