One read-only YMCS connection shows every Yealink phone your enterprise manages, lets you tie each YMCS site — or any single phone — to the right customer company and location, and previews exactly what an import would do. Import and up/down monitoring are built and stay off until SmartChoice switches them on.
A YMCS enterprise run by an MSP holds phones for many customers, sorted into YMCS sites that rarely match anyone's billing names. Importing them blind puts phones under the wrong customer. SmartTile does it in the right order: see everything, map it, preview it — then import. SmartTile's agent only ever reads YMCS; it never changes anything there. BETA: discovery, mapping and the import preview work today; the import itself and phone up/down monitoring are built, tested and switched off platform-wide until SmartChoice turns them on for your rollout.
Every phone and room device YMCS manages: name, model, MAC, serial, firmware, YMCS site and status — online, offline or not reported. Filter by site, model, status and mapping; search name, MAC or serial.
Every YMCS site with its phone count and a suggested SmartTile location, matched by name only among the locations you manage. Phones in no site are counted so none are missed.
Tie a YMCS site to Company → Organization → Location (organizations optional, pickers cascade). Any phone can be set on its own or left out — its own mapping beats the site's.
For every phone: create, link to a device already in SmartTile (same MAC or serial in that company), already imported, or skipped with the reason — unmapped, needs a location, left out, or outside your companies. Writes nothing.
When enabled, ticked phones become VoIP Phone devices at their mapped location with Yealink, model, serial, MAC and firmware filled in (from YMCS provenance). A phone already watched by ping or SNMP is linked, not duplicated.
When enabled, every 3 min: offline or not reported for 2 polls → DOWN; missing from a list that still returns phones for 3 polls → DOWN; state history written and the normal outage ticket path applies.
| Setting | What it controls |
|---|---|
| Yealink for this company | Test, discover, map and preview for that company — off by default |
| Pause / Resume | Stops one connection; nothing is read from YMCS |
| Import + status polling | Super admin, Engine Safety — off by default; Import answers "switched off" until then |
| Platform switch | Super admin, Engine Safety; plus a server kill switch |
/v2/tokenOAuth2 client credentials (Basic AccessKey ID:Secret); token cached until it expires/v2/dm/listSitesTest (count only) and discovery: every site, 500 per page/v2/dm/models?deviceType=1|3Discovery: model names for phones and room devices/v2/dm/listDevicesTest (count only), discovery, preview — and, once enabled, every status poll; 100 per pagetimestamp and nonce, as YMCS requires. SmartTile only ever connects to the three Yealink regional addresses — never a typed URL — over https, with redirects refused and the address checked to be public.| Preview | Why |
|---|---|
| Create | Mapped to a location you manage; no matching device in that company |
| Link | A device with the same MAC or serial already exists in that company — it is linked, never duplicated |
| Already imported | This YMCS phone is already a SmartTile device |
| Unmapped · Needs location | Map its YMCS site, or pick a location for this phone |
| Left out · Outside your companies | Excluded on purpose, or mapped to a company you do not manage |
The YMCS client has no write call. SmartTile cannot change a phone, a site or a setting in YMCS.
AccessKey ID and Secret encrypted at rest, never returned, never logged, never in the transaction log.
A connection belongs to one company. A mapping's company always comes from its location, and changing an existing mapping needs both companies in your scope.
Company admins, resellers and super admins. Every connection change, test, mapping, exclusion and refused import is written to the transaction log.
Import answers "switched off" (and logs the refusal) until SmartChoice enables it; the import always re-reads YMCS and your saved mappings, never the browser's list.
Once polling is on, a failed or empty listing never marks a phone DOWN: after 5 failed polls UP phones turn grey (UNKNOWN) and SmartChoice's NOC is e-mailed.
| Question | Answer |
|---|---|
| When will phones open tickets? | When SmartChoice switches import + status polling on and the phones are imported. Then an offline phone follows the normal outage path into your ITSM system — Kaseya (Autotask, BMS), Freshservice, ServiceNow, Jira Service Management, Rev.io, HaloPSA, ConnectWise PSA, Zendesk, NinjaOne, ManageEngine, Ivanti, Freshdesk. |
| Are reboots detected? | YMCS exposes no uptime counter, so only a reboot long enough to show offline in YMCS is caught. |