[asterisk-bugs] [JIRA] (ASTERISK-26678) chan_sip: AMI Events - PeerStatus does not show time parameter

Rusty Newton (JIRA) noreply at issues.asterisk.org
Thu Jan 5 21:24:10 CST 2017


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

Rusty Newton updated ASTERISK-26678:
------------------------------------

    Description: 
When connecting to the manager, the PeerStatus event does not show the paramenter time.

I am connecting to the asterisk manager interface and receiving events. But in a particular event, of my interest, peerStatus (ManagerEvent_PeerStatus - Asterisk Documentation), I wait for the Time argument as described in the Asterisk 13 Documentation, however this argument doesn't come from the event. Looking at the Asterisk code to try to understand the reason, I verified there was an error using the json module in stasis_endpoints file. I made changes and the Time argument was in the PeerStatus event as expected.

The Time field will come only when the status is "Reachable" or "Lagged", and if the sip has the attribute "qualify" equal to "yes". But it's not happening. In channels/chan_sip.c, in handle_response_peerpoke function, on line 23902, pingtime is an integer and in main/stasis_endpoints.c, in the *peerstatus_to_ami function, on line 155 the expected result to the Time value in json is a string, but in fact it's coming as an integer. So the Time value will be always null and it won't come out in the event.

  was:
When connecting to the manager, the PeerStatus event does not show the paramenter time.

I am connecting to the asterisk manager interface and receiving events. But in a particular event, of my interest, peerStatus (ManagerEvent_PeerStatus - Asterisk Documentation), I wait for the Time argument as described in the Asterisk 13 Documentation, however this argument doesn't come from the event. Looking at the Asterisk code to try to understand the reason, I verified there was an error using the json module in stasis_endpoints file. I made changes and the Time argument was in the PeerStatus event as expected.


> chan_sip: AMI Events - PeerStatus does not show time parameter
> --------------------------------------------------------------
>
>                 Key: ASTERISK-26678
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26678
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.5.0
>         Environment: CentOS release 6.8, jansson 2.9
>            Reporter: Diego Souza
>            Assignee: Unassigned
>            Severity: Minor
>
> When connecting to the manager, the PeerStatus event does not show the paramenter time.
> I am connecting to the asterisk manager interface and receiving events. But in a particular event, of my interest, peerStatus (ManagerEvent_PeerStatus - Asterisk Documentation), I wait for the Time argument as described in the Asterisk 13 Documentation, however this argument doesn't come from the event. Looking at the Asterisk code to try to understand the reason, I verified there was an error using the json module in stasis_endpoints file. I made changes and the Time argument was in the PeerStatus event as expected.
> The Time field will come only when the status is "Reachable" or "Lagged", and if the sip has the attribute "qualify" equal to "yes". But it's not happening. In channels/chan_sip.c, in handle_response_peerpoke function, on line 23902, pingtime is an integer and in main/stasis_endpoints.c, in the *peerstatus_to_ami function, on line 155 the expected result to the Time value in json is a string, but in fact it's coming as an integer. So the Time value will be always null and it won't come out in the event.



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



More information about the asterisk-bugs mailing list