VDN override always applies to attendant VDNs.

To provide the most flexibility possible, there are no restrictions placed on the vector that is assigned to a VDN. A non attendant vector can be assigned to an attendant VDN and an attendant vector can be assigned to a non attendant VDN. Obviously, doing so is not recommended. Assigning an attendant vector to a non attendant VDN severely restricts processing for basic call vectoring since only limited vectoring commands are available in attendant vectors. Assigning a non attendant vector to an attendant VDN also severely restricts attendant vectoring since the attendant-specific commands are not available in basic call vectoring. In addition, it removes basic call vectoring information from attendant VDNs. Also, there are no restrictions in vector chaining between attendant and non attendant vectors (for example, using the goto vector or route-to number commands).