Get Hunt-Group AUX Status of Users

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • hofmad
    Hot Shot
    • Sep 2014
    • 14

    Get Hunt-Group AUX Status of Users

    Hi all,

    is there a way to get the AUX Status of Hunt-Group Members using WTI? Either by checking every member extension or by checking the Hunt Group itself?

    Thanks
  • flynn1
    Brainiac
    .
    • Jun 2011
    • 82

    #2
    You have to check each agent individually.

    Initial condition:
    • Agent 50700 is logged in at 50502, in Aux Work mode with Reason Code 2.
    Code:
    Sending WTI request to AES using method: /api/fe/v1/GetAgentState
    {"device": "50502:CM181::0"}
    ======== Incoming WTI Response =============
    
    {"GetAgentStateResponse": {
            "pendingReasonCode": 0,
            "workMode": "auxWork",
            "talkState": "idle",
            "agentStateList": {"agentStateEntry": {
                    "agentInfo": {"agentInfoItem": {
                            "agentState": "agentNotReady",
                            "pendingAgentState": "agentNull"
                    }},
                    "loggedOnState": true
            }},
            "reasonCode": 2
    }}
    In this example, I used the (Third Party) Device ID of the station, but I could have used the AgentID in the same format (50700:CM181::0)

    Comment

    • hofmad
      Hot Shot
      • Sep 2014
      • 14

      #3
      Hi flynn1

      I know about the Agent Login IDs and their AuxWork Mode in Skills.
      But I talk about the "Hunt Position Busy" Button on SIP phones with "normal" Hunt Groups (no ACD).

      Comment

      • flynn1
        Brainiac
        .
        • Jun 2011
        • 82

        #4
        I haven't come across Hunt Position Busy before and the only information I can see is that it is a button that can be configured on SIP stations. DMCC (and therefore WTI) do not provide first-party support for SIP stations. Therefore, WTI has no access to the button or its associated lamp.

        Unless pressing the button has some sort of third-party effect (e.g starts a call or shows up in a Snapshot or Query command) then you will not be able to access it via WTI.

        Martin

        Comment

        Loading