[asterisk-bugs] [JIRA] (ASTERISK-28298) ARI: endpoints of tech IAX2 have wrong state

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28298:
------------------------------------------

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.

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.

> ARI: endpoints of tech IAX2 have wrong state
> --------------------------------------------
>
>                 Key: ASTERISK-28298
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28298
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2, Resources/res_ari_endpoints
>    Affects Versions: 13.8.2, 13.24.1, 16.1.1
>         Environment: {noformat:title=ARI /ari/asterisk/info:}
> {
>   "build": {
>     "os": "Linux",
>     "kernel": "3.16.0-6-amd64",
>     "machine": "x86_64",
>     "options": "OPTIONAL_API",
>     "date": "2019-02-05 08:31:13 UTC",
>     "user": "root"
>   },
>   "system": {
>     "version": "13.24.1",
>     "entity_id": "00:50:56:9b:ac:40"
>   },
>   "config": {
>     "name": "deacsrewk12",
>     "default_language": "en",
>     "setid": {
>       "user": "",
>       "group": ""
>     }
>   },
>   "status": {
>     "startup_time": "2019-02-20T11:00:27.028+0100",
>     "last_reload_time": "2019-02-20T11:00:27.028+0100"
>   }
> }
> {noformat}
>            Reporter: Stefan Repke
>            Severity: Minor
>
> Given Asterisk is (re)started and some IAX2 endpoints connect and register very soon with Asterisk.
> Then ARI endpoints shows these endpoints with state {{unknown}} instead of {{online}}.
> All other sources show them as online, like:
> * AMI action {{IAXpeerlist}}
> * CLI {{iax2 show peers}}
> * CLI {{database show}}
> If IAX2 register later, then ARI shows these endpoints with correct state.
> Example data:
> {noformat:title=IAX2 registration for username=301}
> 11:00:26.855 --> (Call=44/0     Seq=0/0): IAX REGREQ  timestamp:8086591 retry:false (1) Frameinfo: USERNAME=301 REFRESH=60
> 11:00:26.955 --> (Call=44/0     Seq=0/0): IAX REGREQ  timestamp:8086591 retry:false (2) Frameinfo: USERNAME=301 REFRESH=60
> 11:00:26.956 <-- (Call=44/16163 Seq=1/0): IAX REGAUTH timestamp:16      retry:false (0) Frameinfo: USERNAME=301 AUTHMETHODS=2 CHALLENGE=..
> 11:00:26.957 --> (Call=44/16163 Seq=1/1): IAX REGREQ  timestamp:8086893 retry:false (0) Frameinfo: USERNAME=301 MD5 RESULT=.. REFRESH=60
> 11:00:26.957 <-- (Call=44/16163 Seq=2/1): IAX REGACK  timestamp:17      retry:false (0) Frameinfo: CALLING NUMBER=301 CALLING NAME=PMR USERNAME=301 REFRESH=60
> 11:00:26.957 --> (Call=44/16163 Seq=2/2): IAX ACK     timestamp:17      retry:false (0) Frameinfo:
> {noformat}
> {noformat:title=ARI /ari/endpoints}
> [
>   {
>     "technology": "IAX2",
>     "resource": "301",
>     "state": "unknown",
>     "channel_ids": []
>   },
>   {
>     "technology": "IAX2",
>     "resource": "316",
>     "state": "unknown",
>     "channel_ids": []
>   },
>   ..
> ]
> {noformat}
> {noformat:title=ARI /ari/endpoints/IAX2/301}
> {
>   "technology": "IAX2",
>   "resource": "301",
>   "state": "unknown",
>   "channel_ids": []
> }
> {noformat}
> {noformat:title=ARI /ari/deviceStates/IAX2%2f301}
> {
>   "name": "IAX2/301",
>   "state": "UNKNOWN"
> }
> {noformat}
> {noformat:title=AMI Action IAXpeerlist}
> --> Action='IAXpeerlist', actionid='4223#1933833398_65#'
> <-- Response='Success', ActionID='1933833398_65#', EventList='start', Message='IAX Peer status list will follow'
> <-- Event='PeerEntry', ActionID='1933833398_65#', Channeltype='IAX', ObjectName='312', ChanObjectType='peer', IPaddress='..', Mask='(null)', Port='59655', Dynamic='yes', Trunk='no', Encryption='no', Status='OK (1 ms)'
> <-- Event='PeerEntry', ActionID='1933833398_65#', Channeltype='IAX', ObjectName='301', ChanObjectType='peer', IPaddress='..', Mask='(null)', Port='60289', Dynamic='yes', Trunk='no', Encryption='no', Status='OK (1 ms)'
> ..
> <-- Event='PeerlistComplete', ActionID='1933833398_65#', EventList='Complete', ListItems='41'
> {noformat}



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