VAA - Visual Auto Attendant- is an overlay on Contact Center

[tomekandos]

I have simple questions:
Is VAA - Visual Auto Attendant an overlay on Contact Center?
Is VAA able to rule internal connections?
In two processors systems is necessary use 2 VAA servers?

[frank]

VAA is a Visual Auto Attendant by itself, nothing to do within the contact center, but you can add it front of the contact center, or after if you have overflow routes.
What do you mean by can it rule internal connections?
2 VAA is only used for High Availability of the VAA itself.

[tomekandos]

VAA is a Visual Auto Attendant by itself, nothing to do within the contact center, but you can add it front of the contact center, or after if you have overflow routes.
What do you mean by can it rule internal connections?
2 VAA is only used for High Availability of the VAA itself.

So is VAA extended version of Automated Attendant?
By "internal call" I mean connection from one to another extension within PABX (OXE)- i.e call between entities, from guest room to reception (in hotel).

[frank]

OXE has a VAA in itself which works with CCD if you want an exit for callers in queue
OXE has a VAA within the A4645 which is basically an IVR Menu which you can use externally or internally
Then you have the VAA Software which has a graphical interface, and allows easier design, and include incoming caller ID filters, schedule, and some other gadgets..
You can use all those 3 auto attendant with external or internal calls