Table A-7 describes the attributes of the DirXML-pbxAudixSubscriber object.
Adding Audix support to the current Avaya driver requires the driver to access and manipulate PBX subscriber objects. This is performed by extending the eDirectory schema to include a DirXML-pbxAudixSubscriber object. For Audix support, the driver uses add, change and remove work order commands. Other important information includes:
The Audix server is separate from the extension server, so you must specify a new site object for the Audix server.
The Audix server supports different commands, so the Avaya driver supports an Audix type of access. The new DirXML-AccessType is audix and the new actions supported are add, change, remove and AudixEmulate.
The Avaya driver does not synchronize manual changes made on the Audix server to the Identity Vault.
The Avaya driver makes no attempt to see if there is a corresponding extension on an add command. The creation of extension and subscriber objects are independent of one another and can be done in any order.
Because the Audix server is separate and very different than the extension server, separate work order commands are provided for Audix support. Any successful actions and errors resulting from work orders are reported back through the work order. Work order commands are add, change, and remove.
On an add command, the driver checks to see if the Subscriber Extension object is on the the PBX Audix server. If the object already exists, the driver generates an error and reports it back in the work order.
On a change command, the driver checks to see if the Subscriber object already exists. If it does not, the driver generates an error and reports it back through the work order.
On a delete command, the driver checks to see if the subscriber object is already there. If it is not, the driver generates an error and reports it in the work order.
Table A-7 pbxAudixSubscriber Object Attributes