Hello,

i am using the newest DMCC .NET API with the Protocol Version 6.3.3 and i am unable to set Reason Codes above 9 during a
SetAgentState request.
I get "invalidAgentState" as a response.

Is this a limitation of the API?

There are a number of configuration changes in Communication Manager necessary to utilize two digit reason codes. Please see this FAQ:

https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/general/index.gsp?tab=general&accordion=faq-970

The DMCC (TSAPI, JTAPI, CVLAN and DLG) APIs supports both one and two digit reason codes. I anticipate you will find that the Communication Manager changes are not in place to support two digit reason codes. to use single digit reason codes when Communication Manager is configured for two digit reason codes, pre-pend a 0 onto the value where necessary (when they are being treated as ascii values).

Thank you! We have found some differences in the suggested Configuration and will try that out tomorrow.