Telephony & collaboration plugins

Run AI across your phones and meeting rooms too.

Eldric connects to the PBX, SIP phones, and collaboration platforms your organisation already runs: Asterisk, Snom and Yealink handsets, and Microsoft Teams. One credential per platform, not per handset.

See the datacenter picture Ask for a platform we haven't listed
4 plugins shipped · catalog expanding

A vendor plugin gives Eldric read and (where the vendor's controller permits) write access into the gear it covers. The agent layer can then reason across the fleet — "which firewall rules changed this week," "which UPSes are running on battery," "which switches haven't been patched in 90 days." The platform you already run stays exactly where it is; Eldric just gets a voice into it.

Telephony & VoIP

3 plugins
Asterisk

Asterisk (ARI)

The open-source PBX — channels, bridges, endpoints, and Stasis applications — through the Asterisk REST Interface.

platformPBX
Snom

Snom phones

Snom SIP desk phones and DECT base stations, through the Snom web API.

directSIP · DECT
Yealink

Yealink phones

Yealink SIP desk phones, video phones, DECT, and conference-room endpoints, through the Yealink web API.

directSIP · video · DECT

Collaboration

1 plugin
Microsoft

Teams

Microsoft Teams — channels, meetings, calls, presence, and admin policies — through the Microsoft Graph Teams endpoints.

platformchat · meetings · calls

When this fits, when it doesn't.

The telephony-plugin layer is built for organisations who want their AI to understand the fleet they already operate — not for organisations who want Eldric to replace their existing fleet management.

Right fit
  • Your operations team uses one of these vendor platforms today (or a mix of them).
  • You want AI in the loop for triage, drift detection, change-window prep, capacity planning, postmortem narrative.
  • You want a vendor that respects "my data stays inside my perimeter" — Eldric never ships fleet telemetry to a cloud.

Probably not the right fit

  • You expect Eldric to replace your network management plane. It doesn't — it reads from yours and reasons across it.
  • Your fleet is a single vendor and the vendor's own AI assistant already covers your use case.
  • You want push-button automation with no human review. Plugin writes go through an approval workflow by default; auto-write is opt-in per plugin per environment.

Missing a vendor? Tell us — the catalog is expanding and the candidate list is open.