TAPI and Active Directory
Updated: January 21, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Server 8 Beta
TAPI and Active Directory
Active Directory is the extensible and scalable directory service for Windows Server 2003 operating systems. TAPI-based programs use Active Directory to facilitate H.323-based IP telephony calls and multicast conferencing.
Active Directory publishes the locations of all TAPI application directory partitions on the network and provides the directory store for TAPI program-specific data. In Active Directory, application directory partitions store and replicate static or dynamic program-specific data. TAPI-based programs can use TAPI application directory partitions to store and retrieve information to facilitate H.323-based IP telephony calls and multicast conferencing.
TAPI provides transparent translation from user or computer names to IP addresses. When you place an H.323-based IP telephony call, you can specify a computer name or a user name, rather than an IP address, because TAPI application directory partitions publish user names, computer names, and IP addresses, and TAPI can translate user or computer names to IP addresses.
For multicast conferencing, TAPI application directory partitions publish information about active users and IP multicast conferences in progress. Information about active users includes the users' names, computer names, and IP addresses. Information about conferences in progress includes the conferences' names, descriptions, times, and originators.
You can create TAPI application directory partitions in one of two ways:
By using the Tapicfg command-line tool. You can also use this command to remove or display TAPI application directory partitions and to set default TAPI application directory partitions. For more information, see Tapicfg.
By selecting the Typical setup for a first server option when running the Configure Your Server Wizard to configure the first domain controller in a domain. When you select this option, the Tapicfg command runs transparently to create a TAPI application directory partition called MSTAPI.DomainName. This application directory partition is set as the default for the domain. For more information about the prerequisites for using this option, see Typical setup for a first server.
For more information about application directory partitions, see Application directory partitions. For more information about the H.323 IP protocol and the telephony service provider that supports it, see H.323 IP telephony calls.
If Internet Locator Service (ILS) is needed to support certain programs, you can continue to use ILS servers in your organization because telephony clients running Windows Server 2003 operating system can query either ILS servers or TAPI application directory partitions.