Jump to content

ACD Wallboard Queue - Agents Status in JSON


Recommended Posts

In the past versions I was able to use the JSON requests to get the agent status of an ACD.


Example: http://localhost/rest/user/user@domain/wallboard/queue_extension.


The structure used to include a parameter 'logged_agents', but right now with V66+ it appears it has been removed or changed.
Is there a way for the PBX to continue sending this parameter or can you recommend a different way of obtaining this information?
I know on the administrator side you can view the status while inside the ACD or the wallboard application, but we were hoping to continue exporting the data into an external page.
Thank you

Link to comment
Share on other sites

Looks like that query returns the same results. I'm referencing the https://doc.vodia.com/docs/rest-api-acd-info document and this is the parameter we used to work with:

Example:
GET https://192.168.1.11/rest/user/45@example/wallboard/73

Returns:
{acds: {…}, logged_agents: Array(3), agents: Array(3), current: Array(0), history: Array(3)}
JSON object break down:

--

This is what gets returned now.

https://pbx.com/rest/user/manager@pbx.pbx.com/wallboard/253
http://pbx.com/rest/user/manager@pbx.pbx.com/wallboard/253

{
    "acds": {
        "253": {
            "managers": [
                "11",
                "12",
                "manager"
            ],
            "redirect": {
                "waiting": 0,
                "ringing": 0,
                "anonymous": 0
            },
            "hangup": {
                "waiting": 0,
                "ringing": 0
            },
            "exit": {
                "user": 0,
                "admin": 0,
                "max-calls": 0,
                "application": 0,
                "other": 0
            },
            "duration": {
                "sum": {
                    "ivr": 0,
                    "ring": 0,
                    "talk": 0,
                    "hold": 0,
                    "idle": 0
                },
                "average": {
                    "ivr": 0,
                    "ring": 0,
                    "talk": 0,
                    "hold": 0,
                    "idle": 0
                }
            },
            "calls": {
                "count": 0,
                "completed": 0
            }
        }
    },
    "agents": [
        {
            "account": "11",
            "name": "User Agent 1",
            "dnd": false,
            "login": true,
            "jumpin": true,
            "work": {
                "begin": 1615525200.0,
                "end": 1615611600.0,
                "now": 1615537452.898,
                "segments": []
            },
            "calls": 0,
            "missed": 0,
            "duration": {
                "talk": 0,
                "hold": 0,
                "idle": 0
            },
            "average": {
                "talk": 0,
                "hold": 0,
                "idle": 0
            }
        },
        {
            "account": "12",
            "name": "User Agent 2 .",
            "dnd": false,
            "login": true,
            "jumpin": true,
            "work": {
                "begin": 1615525200.0,
                "end": 1615611600.0,
                "now": 1615537452.898,
                "segments": []
            },
            "calls": 0,
            "missed": 0,
            "duration": {
                "talk": 0,
                "hold": 0,
                "idle": 0
            },
            "average": {
                "talk": 0,
                "hold": 0,
                "idle": 0
            }
        }
    ],
    "current": [],
    "history": []
}

---

In this example i have two agents, 11/12, logged into queue 253. The results are different from the example and i'm seeing this new parameter for each agent:

"login": true

Is this how agents will be tracked as logged in/out going forward? The document isn't that old, recently updated in February. We just want to make sure the method stays the same going forward so we can eliminate the guesswork of future builds.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...