Abstract: Directory services schema for telephone call management. The schema facilitates the development of call routing rules as one or more instances of one or more classes. Once created, the rules can be propagated to all other director services servers, and any subsequent updates and system changes are readily propagated to maintain optimum call system management. The rules can be stored in a routing table allowing administrators to define phone routes for various scenarios. System hardware/software changes can be managed using distinguished names and automatically propagated (or replicated) to the other directory services servers on an enterprise network. The architecture includes a schema component for generating a directory services schema, and a call routing component that routes telephone calls according to call routing rules defined by the directory services schema. The rules can be processed in combination with policies of usage attributes and phone number patterns/ranges to manage call routing.

Abstract: Directory services schema for telephone call management. The schema facilitates the development of call routing rules as one or more instances of one or more classes. Once created, the rules can be propagated to all other director services servers, and any subsequent updates and system changes are readily propagated to maintain optimum call system management. The rules can be stored in a routing table allowing administrators to define phone routes for various scenarios. System hardware/software changes can be managed using distinguished names and automatically propagated (or replicated) to the other directory services servers on an enterprise network. The architecture includes a schema component for generating a directory services schema, and a call routing component that routes telephone calls according to call routing rules defined by the directory services schema. The rules can be processed in combination with policies of usage attributes and phone number patterns/ranges to manage call routing.