[Home]

Summary:ASTERISK-29972: Duplicated ARI events
Reporter:Vitor Gomes Faria (vgfaria)Labels:
Date Opened:2022-03-16 08:00:38Date Closed:2022-03-16 08:00:39
Priority:MinorRegression?
Status:Closed/CompleteComponents:Applications/General
Versions:18.6.0 Frequency of
Occurrence
Related
Issues:
Environment:Asterisk 18.6.0 running on CentOS 7. I have an application with python registring a app on asterisk to read events and send de ARI commands.Attachments:
Description:Hi Guys,
Im trying to previne problems with recorders in my asterisk, my dialplan is all using ARI reading de events and doing what i have to do.
But now im trying to read two specifie events RecordingStarted and RecordingFinished and for those cases i ever receive two simultaneous events with the same information.
I am starting the recorder on a bridge with two channels, i tried start de recorder without channels to see whats happen but the same occurre.
In the ari debug i see two events , i have just one application registred on ARI.

ARI DEBUG:

<--- Sending ARI event to 127.0.0.1:47266 --->
{
 "type": "RecordingFinished",
 "timestamp": "2022-03-16T09:27:20.443-0300",
 "recording": {
   "name": "temp/0500000012347491424898",
   "format": "wav",
   "state": "done",
   "target_uri": "bridge:adb4343c-e46b-465a-ad80-cc2d1b3d1f8e",
   "duration": 19
 },
 "asterisk_id": "08:00:27:8e:4e:31",
 "application": "dialer"
}
<--- Sending ARI event to 127.0.0.1:47266 --->
{
 "type": "RecordingFinished",
 "timestamp": "2022-03-16T09:27:20.443-0300",
 "recording": {
   "name": "temp/0500000012347491424898",
   "format": "wav",
   "state": "done",
   "target_uri": "bridge:adb4343c-e46b-465a-ad80-cc2d1b3d1f8e",
   "duration": 19
 },
 "asterisk_id": "08:00:27:8e:4e:31",
 "application": "dialer"

The problem with this is that I can't tell the events apart and I double-flow for those events.
This is normal ? Why does it happen?
Comments:By: Asterisk Team (asteriskteam) 2022-03-16 08:00:39.490-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
By: Asterisk Team (asteriskteam) 2022-03-16 08:00:39.653-0500

We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum.

The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors.

If this issue is actually a bug please use the Bug issue type instead.

Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker.

Thanks!

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