It also doesn't work with regular vectoring with a route-to attd extension. It appears CM recognizes it's always going to the attd-group, but I'm happy with this solution and understand why. Thanks for your help Kyle!
VDN with attendant vectoring is enabled. Could the restriction be present when attendant vectoring is set to "yes"? Eventually all calls within the vector go to the attd-group.
I had a number of agents (via Avaya one-X Agent version 2.5.60315.0) reporting the problem, that they couldn't transfer calls to the attendants. The problem also appears when physically doing the same on the IP Phone. It's exactly how it is described on this Avaya support page: Link
Customer...
With "list trace station xxxx" no coverage path, but I noticed something else:
This logged off station did have EC500 enabled: "station extension" and "phone number" were the same and as a result of this I got the "busy signal".
I described my first post/ question in this thread wrongly and it...
We would like to have a busy signal when somebody is calling a logged off station (out-of-service). At this time people get a transition tone and keep waiting and nobody is answering. Is it possible to have this system wide? I know one phone gets the busy tone when out-of-service and almost the...
I would like to know if it’s possible having all the buttons from one expansion module copied to another station with such a module. We are on CM 7.1 and generally use Avaya 9608 stations. Hope anyone can help me with this.
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.