" /> SIP Server Agent No Answer Reason code - Genesys CTI User Forum

Author Topic: SIP Server Agent No Answer Reason code  (Read 2224 times)

Offline mduran22

  • Full Member
  • ***
  • Posts: 108
  • Karma: 5
SIP Server Agent No Answer Reason code
« on: September 29, 2016, 11:52:41 PM »
Advertisement
I have configured SIP Server no answer options and everything is working as it should. When the Agent doesn't answer SIP Server sends an EventAgentNotReady with a extension attribute KVP of 'ReasonCode':'no-answer (see log below).

I looked through the doc but there doesn't seem to be an option to change the value. Anyone know if changing this value is possible?

@14:46:52.0440 [0] 8.1.101.75 distribute_event: message EventAgentNotReady
AttributeExtensions [77] 00 02 00 00..
'ReasonCode' 'no-answer'
'AgentSessionID' '6DPJ32734117L78P5UBDBJ3KRK0000DD'
AttributeEventSequenceNumber 00000000000009ae
AttributeCustomerID 'Resources'
AttributeTimeinuSecs 44000
AttributeTimeinSecs 1475185612 (14:46:52)
AttributeAgentWorkMode 0 (Unknown)
AttributeThisQueue '3696'
AttributeAgentID '7151'
AttributeThisDN '+19097932853;ext=7151'

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: SIP Server Agent No Answer Reason code
« Reply #1 on: September 30, 2016, 01:25:45 AM »
What for?

Enviado de meu E6633 usando Tapatalk


Offline Tambo

  • Sr. Member
  • ****
  • Posts: 456
  • Karma: 5
Re: SIP Server Agent No Answer Reason code
« Reply #2 on: September 30, 2016, 10:21:51 AM »
if the call is not answered and the reason code is not answered then i agree with Cav why ? what do you want to change it to ?

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: SIP Server Agent No Answer Reason code
« Reply #3 on: September 30, 2016, 10:27:37 AM »
There is no option to change the value itself, but you can turn this feature off in general.

Offline mduran22

  • Full Member
  • ***
  • Posts: 108
  • Karma: 5
Re: SIP Server Agent No Answer Reason code
« Reply #4 on: September 30, 2016, 06:18:07 PM »
We currently have logic and reporting set up to use a different value ('RONA') through an Avaya TServer, so to make the transition easier I was hoping to match the current logic.

I checked with Support and they confirmed that it is hard coded.

There is the option to send it either in AttributeExtensions or AttributeReasons.