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

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250837#comment-250837 ] 

Asterisk Team commented on ASTERISK-28868:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> 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)