Atlas project production

ShoreTel to Directory Sync

Tracks the active telephony-to-directory alignment path backed by `Push-ShoreTelToAD.sh`, while preserving uncertainty about exact field direction, cadence, and target model.

Internal-only entry. Do not publish externally without review.

Type: Field Tool
Lifecycle: Active
Last touched: 2026-03-26
Visibility: Internal

Purpose

Keep ShoreTel or Mitel telephony data aligned with district directory information.

Current state

Active script evidence exists in Aether, but the exact synchronized fields and final target direction remain partially unresolved. Current posture is continuity-valid with implementation details still needing formal confirmation.

Next step

Confirm direction of flow, target directory, synchronized field set, and scheduler ownership.

Interfaces

Inputs

ShoreTel or Mitel data
directory helper libraries

Outputs

aligned directory or telephony data

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Contributes in this stage.

Human Interfaces

Not in scope.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

Approved district directory or telephony source data should define the intended record state.
The sync should remain scoped to communications-system metadata, not broader HR authority.

Safe handling

Protect staff extension and telephony metadata.
Limit access to directory helper configs and run logs.

Operational notes

Reliability posture

Concrete script evidence exists, but exact direction of flow and field mapping still require validation.

Observability

script logs
manual telephony and directory review

Security and privacy

Internal communications-system data and staff directory details; internal only.

Dependencies

Upstream

telephony data availability
directory helper scripts
operational runtime

Downstream

directory accuracy for telephony context

Ownership

Owners

Technology Services

Users

Technology Services

ShoreTel to Directory Sync

Operational Notes

The registry points to Push-ShoreTelToAD.sh as the concrete implementation evidence.
Behavior classification: telephony-directory enrichment or alignment sync; this is not treated as a full identity-provisioning system.
This connector is still conservative in Atlas because its field-level direction is not yet fully validated.
Failure affects directory or telephony alignment and can complicate operational support.

Registry Alignment

Mapped registry entry: INT-049
Registry clarified: there is a real script-backed workflow behind the inventory name, even though its field-level contract still needs confirmation.
Validation gaps: Confirm direction of flow, target directory, and the exact synchronized field set.