Author Topic: EventAgentNotReady  (Read 1916 times)

Offline Campfire

  • Jr. Member
  • **
  • Posts: 73
  • Karma: 0
  • If you must blink, do it now.
EventAgentNotReady
« on: May 19, 2016, 09:55:22 AM »
Hi,

Am new to genesys.. I am coming across the EventAgentNotReady for one of the DNs when the agent is actually not going on a call. Does that mean that the agent's status was change by him or due to any other problem?

Offline Tambo

  • Sr. Member
  • ****
  • Posts: 456
  • Karma: 5
Re: EventAgentNotReady
« Reply #1 on: May 19, 2016, 01:10:22 PM »
can you post SIP / Tserver logs?

Offline Dionysis

  • Sr. Member
  • ****
  • Posts: 408
  • Karma: 8
Re: EventAgentNotReady
« Reply #2 on: May 19, 2016, 03:09:07 PM »
In the EventAgentNotReady log message look for an "AttributeReferenceID".

Like this:
@16:32:14.4557 [0] 8.1.101.74 distribute_response: message EventAgentNotReady
        AttributeExtensions    [53] 00 01 00 00..
                'AgentSessionID'        '01K2DP379KBAN64S28IH4PTAES46GAPC'
        AttributeEventSequenceNumber    00000000188fbb27
        AttributeCustomerID    'something'
        AttributeTimeinuSecs    455698
        AttributeTimeinSecs    1463639534 (16:32:14)
        AttributeReason [26] 00 01 00 00..
                'workmode'      'Some reason'
-->  AttributeReferenceID    11
        AttributeAgentWorkMode  0 (Unknown)
        AttributeAgentID        'agentname'
        AttributeThisDN '1000'

Then search back in the logs for that reference ID, which will lead you to the request which triggered the event.  That will tell you what requested the agent to be not ready.  If there is no reference ID, then the not ready event was not triggered by a request and was likely triggered by SIP / T Server itself for some reason. 
« Last Edit: May 19, 2016, 03:10:58 PM by Dionysis »

Offline Campfire

  • Jr. Member
  • **
  • Posts: 73
  • Karma: 0
  • If you must blink, do it now.
Re: EventAgentNotReady
« Reply #3 on: May 20, 2016, 05:15:01 AM »
Hi Dionysis,

Many thanks  :)