Caller Input reset after upgrade to Unity 5.x

Unanswered Question
Nov 14th, 2007

We upgraded from Unity 4.2 to Unity 5.0(1) about a month ago. We have recieved about 5 - 6 calles from users stating that a caller when attempting to "0" out to an operator would receive the default error message that no operator was available. We would the find and fix that the Caller input call handler was set to the default "operator" which we do not use and was set correctly prior to the upgrade. After a few complaints we discovered that there were several dozen user that were reset.

Has anyone seen this behavior or something like it?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)


This Discussion