[asterisk-bugs] [JIRA] (ASTERISK-28333) StasisEnd event makes wrong timestamp value
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Wed Aug 28 11:49:52 CDT 2019
[ https://issues.asterisk.org/jira/browse/ASTERISK-28333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asterisk Team updated ASTERISK-28333:
-------------------------------------
Target Release Version/s: 17.0.0
> StasisEnd event makes wrong timestamp value
> -------------------------------------------
>
> Key: ASTERISK-28333
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28333
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_stasis
> Affects Versions: 16.2.1
> Reporter: sungtae kim
> Assignee: sungtae kim
> Severity: Minor
> Target Release: 13.26.0, 16.3.0, 17.0.0
>
>
> The timestamp for the StasisEnd event uses ast_json_timeval(ast_tvnow(), NULL). But this makes wrong timestamp.
> Because other ari event(ChannelDestroyed) uses channel's timestamp, sometimes the StasisEnd's timestamp is later than ChannelDestroyed event which is not correct.
> It is very tiny timestamp different(0.002 sec), but it makes hard to use(depends on) the event's timestamp.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list