Genesys CTI User Forum > Genesys-related Development

[SOLVED] Can't attach ReasonCode to AttributeExtensions on AgentNotReady Event

<< < (3/3)

gstkein:
There are switch specific guides for this, for example the One for Avaya specifies to add a keyvaluepair ReasonCode -> integer

to a KeyValueCollection and set it as the extensions of the request, so in theory an integer value should work.

luchosrock:
Thank you for your responses  :)

But how can a desktop application using the .NET Platform SDK inform the ReasonCode as an Extension attribute. I tried sending the integer on my RequestAgentNotReady with no results (at least from my debugger):

[code]
reqAgentNotReady.Extensions = New KeyValueCollection
reqAgentNotReady.Extensions.Add("ReasonCode", reasonCode)

response = Me.protocolManagementService(TServerString).Request(reqAgentNotReady, TimeSpan.FromSeconds(15))
[/code]

My guess is that the ReasonCode should be informed on the response. Is that correct?

gstkein:
Your code seems fine, I think that shares the code with the switch, not sure if it should show in the response.

To show the code in the response, you could try adding the "ReasonCode", code pair to the reqAgentNotReady.Reasons as well
you can add to the reqAgentNotReady.Reasons the key "Reason" with the description.

luchosrock:
Thanks @gstkein, You are right!

I can see now the ReasonCode sent by the desktop application on the SIPServer logs (at least is received by the SIPServer)

If everything works well, I will mark this thread as solved (by changing the topic name to [SOLVED] ..... ahahaha)

Regards,
---
EDIT: I'll mark this as solved since the integration I was looking for worked fine. Thanks to all for your kind help.

gstkein:
I´m glad I could help :)

Navigation

[0] Message Index

[*] Previous page