Instead of back-up alerting, could you change your Listed Directory Number (main inbound DID) to a VDN, then vector all calls to a hunt / skill comprised of those who would be sharing attendant duties? You could give them login acces to control call flow, plus, this opens up more measurement opportunities for the 'managerials'.
As far as the question fron
wellco (Vendor)
29 Jun 05 8:08
"Oreypecos...quick question? I see how to activate "attnd backup alerting" but do not see where to add stations that we want to be backup stations?"
You put a "attendant queue calls feature button".
The adment manual also says
"You can assign the attendant backup alerting only to multiappearance
telephones that have a client room class of service (COS) set to No. For
more information, refer to ‘‘Class of Service’’ on page 554.
n If you have not yet defined a Trunk Answer Any Station (TAAS) feature
access code, you need to define one and provide the feature access code to
each of the attendant backup users. For more information, refer to ‘‘Feature
Access Code’’ on page 643.
As far as using a VDN, the best way to go would be using Attendant Vectoring. Just putting a regular 302 attdt console extension in a regular hunt group will cause problems.
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.