Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: anandapriyan on April 13, 2017, 10:55:05 AM
-
Team,
Can you please suggest me the [b]difference [/b]between [b]Hardware [/b]and [b]software [/b][b]reason [/b][b]codes [/b]? .
If the [b]new [/b][b]not ready reason code[/b](eg : [b]Break[/b]) is created in the [b]CME[/b].
It will come under [b]software reason codes[/b] or [b]Hardware reason codes[/b] ?. Kindly looking forward for your possible solutions.
-
I think the o ne you mentioned comes under software reason code ... all actions under the ACtion codes folder
where as hardware failure codes will be different, like server not reachable/event error
-
Thanks for your reply. Yes i also think it comes under [b]software [/b][b]reason [/b][b]codes[/b]. But in the [b]SQL developer[/b] it shows as the [b]Hardware [/b][b]reason [/b][b]codes[/b] when executing the [b]queries [/b]. Kindly looking forward for your suggestions
-
What are Hardware Reason Codes?? Or what do you understand by it?
Actions created on CME are done in order for agents to have more options on WDE for example, you can filter them by some WDE options config. This is Software Reason Codes, belong only to Genesys.
If by HW you mean, sending to the Legacy PBX, like an Avaya or Alcatel for example, what it does is to send those codes to the PBX so you have a full match. However, will depend on your legacy PBX capabilities and your configurations. Is it usually not a default integration work mode.
-
[quote author=anandapriyan link=topic=10276.msg46674#msg46674 date=1492440329]
But in the [b]SQL developer[/b] it shows as the [b]Hardware [/b][b]reason [/b][b]codes[/b] when executing the [b]queries [/b]. [/quote]
Which queries??? Where? There is no such information on Genesys side
-
[b]cav[/b], I think he's talking about reports in GIM and GI2/Insights. @anandapriyan, are you?
In GI2 there's a filter called "[b]Reason Code Type[/b]" which has 3 values ; [u]HARDWARE, SOFTWARE, NO_VALUE[/u].
My understanding is that it won't show in different "Reason" attribute, Hardware or software is only a "flag" of the Reason provided.
Anyway, not really clear in Genesys Docs what's a hardware reason code... I know software will overwrite any hardware reason, but not sure where the hardware reason comes from?!
Here's two documentation link talking about this data dimension ;
https://docs.genesys.com/Documentation/GIM/8.5.0/User/GIMPopAgent
https://docs.genesys.com/Documentation/GIM/8.5.0/PDMOra/Table-RESOURCE_STATE_REASON#REASON_TYPE_CODE
Hope this helps.
-
From a WFM ticket:
[code]
So, for instance, WFM will be able to match the reason code of '4' with either of the following scenarios:
################################################
Software Reason
12:33:16.2860 [0] 8.0.006.01 distribute_response: message EventAgentNotReady
AttributeTimeinuSecs 722000
AttributeTimeinSecs 1284680404 (09:40:04)
AttributeThisDN '1111'
AttributeThisQueue '2000'
AttributeAgentWorkMode 6 (WalkAway)
AttributeAgentID '2111'
AttributeReason [37] 00 02 00 00..
'ReasonCode' '4'
'ReasonCode' 4
AttributeReferenceID 1
#################################################
Hardware Reason
@09:40:04.7220 [0] 8.0.006.01 distribute_event: message EventAgentNotReady
AttributeExtensions [72] 00 02 01 00..
'ReasonCode' 4
'AgentSessionID' '...
AttributeEventSequenceNumber 0000000000089bfa
AttributeTimeinuSecs 722000
AttributeTimeinSecs 1284680404 (09:40:04)
AttributeThisDN '1111'
AttributeThisQueue '2000'
AttributeAgentWorkMode 6 (WalkAway)
AttributeAgentID '2111'
[/code]
So, yes, the location of the attributes define each type, same as when you work with PBX reason codes.
-
Thanks for sharing. Good to know.
(For the flag, I was talking about GIM Database.)
-
Thanks for your reply. Yes I was talking about the Gi2 reports. when we do the voice interactions and put the agent in the not ready state it shows as Software reasons. But when we do the email interactions and put the agent in the not ready state it shows as Hardware reasons. Kindly looking forward for your suggestions.
-
Same concept... Is because where the data is attached
Enviado de meu E6633 usando Tapatalk