Thanks to everyone for your input. Don, the incoing trunk COR is okay for the service observe. AVAYAfreakje, that's sort of what I thought maybe, but then why does the hunt group station form have an option for selecting service observe? I cannot find anything about that in AVAYA's...
First, thanks for your response. All of the members have the correct COR for the service observe. The hunt group itself also has the correct COR. It sure seems odd. I may try changing the COR to an even less restrictive COR and see what happens, even though the COR it has allows for the...
This is so you can enter a descriptive name for the reason, which can then display on the agent's CallMaster terminal (if the terminal has a display and button programmed for displaying the reason).
The hunt group is set for service observe. The COR is a valid service observe COR. The hunt group has one group extension. A fast busy is received when attempting to service observe the hunt group extension. Nobody else is service observing the group extension. I'm figuring the problem is...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.