QueueMemberStatusEvent InCall Status Not Updating

[gertdreyer]

When subscribing to QueueMemberStatusEvent to the InCall Status is never updated and stays false. It can be observed that the other data changes.

Versions:
Asterisk 16.5.1
.NetCore 3.1

Events are subscribed to with:

manager.QueueMemberStatus += queueMemberUpdate;

Event Handler:

  private static void queueMemberUpdate(object sender, QueueMemberStatusEvent e)
        {
            if (e.InCall)
            {
            }
        }

[Deantwo]

In your queues.cfg config file, have you set eventmemberstatus = yes on the queue? If you don't, the QueueMemberStatusEvent event will not be raised.

Edit: Nevermind. That option was removed in Asterisk version 12. [1]

[Deantwo]

Which version of AsterNET are you using?

[Deantwo]

AsterNET doesn't do anything special with the InCall value, it just takes the value given by Asterisk.

AsterNET/Asterisk.2013/Asterisk.NET/Manager/Event/AbstractQueueMemberEvent.cs

Line 114 in 53b3a95

public bool InCall { get; set; }

The Asterisk documentation doesn't seem to mention anything special about it.
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+ManagerEvent_QueueMemberStatus

Is InCall always false or does it just never change from the initial value? What have you observed it as?

I have never used the InCall boolean value myself. I just use the Status integer value to get the status of the member.

[gertdreyer]

Originally we were on the latest NuGet version (v1.3.0) however we are currently using the master branch (c23d932).

Ultimately we succeeded with the InCall status. On the master branch it was available on the QueueMemberEvent. There was a small bug in the version determining regex. On our Asterisk 16 install the version result was prefixed with "Output: "

[gertdreyer]

Pull request #256 contains the improvement on the regex.

[gertdreyer]

This is still not resolved as the working approach is not optimal as we can only determine InCall from the QueueMemberEvent which requires a QueueStatusAction. This is thus a polling approach and not a Subscription Approach. However I believe it may be an Asterisk/PJSIP issue as the ManagerReader never has a QueueMemberEvent with an InCall property that is true. I will attempt this on a Asterisk 18 install in the next two weeks.

[Deantwo]

This is still not resolved as the working approach is not optimal as we can only determine InCall from the QueueMemberEvent which requires a QueueStatusAction. This is thus a polling approach and not a Subscription Approach.

Like I said, you can use Status to determine if the member is in a call. That is what I use in my application.

However I believe it may be an Asterisk/PJSIP issue as the ManagerReader never has a QueueMemberEvent with an InCall property that is true. I will attempt this on a Asterisk 18 install in the next two weeks.

Yeah if it also doesn't work with the newest Asterisk version, I would suggest filing a bug report with Asterisk.

But I don't have the resources right now to check the exact messages that Asterisk is sending to AsterNET, so I don't know if InCall is even transmitted or updated in the events.

[gertdreyer]

We are using Status as well but that only reports Interface state (InUse, NotInUse, etc) and reflects the same status across queues. Our use case is a bit more specific as we have users that are members to multiple queues and we wish to be able to identify on which queue the member is currently in a call.

From my debugging I am quite sure this asterisk version never transmits updates to InCall on this event.
Will update once I was able to test on newer asterisk and either resolve the issue or lodge a bug with them.

[Deantwo]

We are using Status as well but that only reports Interface state (InUse, NotInUse, etc) and reflects the same status across queues. Our use case is a bit more specific as we have users that are members to multiple queues and we wish to be able to identify on which queue the member is currently in a call.

I am not sure that is even possible. But people on the Asterisk forums know more about it than me.

I at least don't think that is what InCall is used to identify. I assume it is just a quick alterative to checking Status or maybe an old backward compatible version of it. Ringinuse seem to be the same.
But I don't know the history of Asterisk, so I can't tell you why these assumingly redundant values exist.