Tamar

Tamar — Tamar Telecommunications Driver for Beacon Tamar is the implementation half of the Beacon call-forwarding stack. It targets one specific upstream — Tamar Telecommunications' control panel (www.tamartelecommunications.co.uk/phonedivert/...) — and implements Beacon's CallForwardingService contract by reading and writing the hunt-group editor. Architecture - Beacon defines CallForwardingService and ships no driver. - Tamar hooks beacon/loaded and binds a concrete HuntgroupCallForwardingService into Beacon's container. Other code calling beacon()-get(CallForwardingService::class) then gets a real, working forwarding service. Tamar never touches Beacon's namespace internals — it depends on the public interface, the abstract base class, and Beacon's container hook. Swapping Tamar for a different driver (a SIP API client, a vendor SDK wrapper) is just a question of registering a different binding on beacon/loaded. How the integration works The upstream is a session-cookie-authenticated HTML admin. There is no public API, so the driver shapes its calls the same way a human admin would point a browser at it: 1. Login. POST the credentials to /customer-login/ (form id login).