Witness Symposium DN Calls 1

[mte0910]

We are using witness with CT Connect to monitor when an agent receives a call. Those get recorded without any issue.

The problem is when the agent receives a DN call. CT Connect is getting a message from Symposium Link that states the agent is in a not ready condition. This is technically true, the agent is not ready for a Symposium routed call; however, this is not enough information for the witness server to know to record the DN conversation.

Has anyone seen this, and if so, does any one have a solution?

 

[DancingDave]

Have you set AST against the sceondary DN? If not, MLSM won't send info on events to any registered third parties i.e. Witness CR

DD