[asterisk-bugs] [JIRA] (ASTERISK-28868) app_alarmreceiver: does not call "eventcmd" with events as arguments or piping

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-28868:
--------------------------------------

    Assignee: Paul Langner
      Status: Waiting for Feedback  (was: Triage)

Patches are only viewable once attached after a signed license agreement has been accepted.

As well to have them included in the fastest way possible they can be placed on Gerrit[1] for code review and inclusion after the license agreement is signed as well. If this isn't done then it is up to someone else to go through the process.

[1] https://wiki.asterisk.org/wiki/display/AST/Gerrit+Usage

> app_alarmreceiver: does not call "eventcmd" with events as arguments or piping
> ------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28868
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28868
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Applications/app_alarmreceiver
>    Affects Versions: 16.10.0
>         Environment: All
>            Reporter: Paul Langner
>            Assignee: Paul Langner
>            Severity: Minor
>         Attachments: app_alarmreceiver.c
>
>
> alarmreceiver.conf documentation states that app_alarmreceiver.c will pipe the alarm events to the user application specified by eventcmd in alarmreceiver.conf, yet it does not do this, and only calls the eventcmd program with no arguments, and no piping (Lines 154-158).
> To solve this issue, a command string needs to be created consisting of the user command specified by eventcmd, followed by the list of events, passed as command-line arguments, and this string called upon hang-up.  This is better than piping, as typically the events need to be parsed into human-readable form prior to e-mailing, etc. - which is easily done in a bash script.
> Up to this point, the approach (without fixing the issue) has been to enable writing individual events to the /tmp directory and then having the program specified in eventcmd search this directory for the most recent file, and then parse this to obtain the event.



--
This message was sent by Atlassian JIRA
(v6.2#6252)