With HTTP trigger Agent state "Not Ready" when talking
I have a problem with Agent state as "Not Ready" when they receive a call from UCCX.
My agent states are as fallows: Ready -> (when phone rings) Reserved -> (Call answered) Not Ready ->(call ends) Ready
I have UCCX application that uses HTTP Trigger as a starting point. The phone number that needs to be dialed is passed passed through the HTTP trigger, the number is dialed using the "Place Call Step" new contact is created. When it is answered it is passed to "Select Resource" the contact used is the one from the Place Call step, "CSQ Target" is CSQ.
The call is forwarded to agent or queued correctly.
When I look at the agents in the Supervisor software "Contact Enterprise Call History" section I'm noticing that CSQ is missing. (Usually if the trigger is JTAPI this section would display: Route Point, CSQ, Agent. In my case it only displays Agent.) (see attached images)
I'm wondering if this is a problem but I'm not sure how to resolve it.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...