Trust Relationships Between Domains; Symposium Tapi Sp Domain Considerations - Nortel TAPI User Manual

Trust relationships between domains

In large networks, or in networks where you want to create separate domains for
different departments or for security reasons, you can establish multiple domains.
You can designate trust relationships between domains to provide members of one
domain with access to the resources of another domain without having to logon to
separate domains. The type of trust relationship you designate varies according to
network and security requirements.
For example, you can create a domain for the sales department and another
domain for the accounts department. You can provide users of the accounts
domain with access to resources in the sales domain, without granting access to
accounts resources to users in the sales domain. In this scenario you can create a
one-way trust relationship between these domains. Domain controllers for the
sales domain trust users logged on to the accounts domain, but users logged on to
the sales domain are not trusted by domain controllers for the accounts domain.
However, if you also want to allow access to the accounts domain to users logged
on to the sales domain, you can create a two-way trust relationship between the
domains. On Windows 2000 and Windows Server 2003 networks, you can
designate a two-way trust relationship between two domains.

Symposium TAPI SP domain considerations

Before establishing TAPI services and installing Symposium TAPI SP, one must
understand the domain and security requirements of the network. Microsoft
recommends two-way trust relationships for TAPI services. However, some
customer requirements can dictate one-way trust relationships for security
purposes. This section provides two sample trust relationship configurations for
Symposium TAPI SP in a multidomain network.
Network Managers Guide for Symposium TAPI Service Provider for Succession, release 3.0
Chapter 3 Preparing the TAPI environment 59