Files

Howard Enos ce52a62ff1 sync: auto-sync from HOWARD-HOME at 2026-04-22 15:41:54

Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-04-22 15:41:54

2026-04-22 15:41:55 -07:00

3.1 KiB

Raw Blame History

Yealink Phones — Valleywide (VWP)

Last updated: 2026-04-22 (Howard) YMCS portal: https://us.ymcs.yealink.com/manager/sip-product/sipManage Customer account: Valleywide Plastering (VWP) Public WAN IP (site): 98.168.18.21

All 16 devices are Yealink SIP-T54W color IP phones (OUI 805e0c and 44dbd2, both Yealink). Added to the YMCS device management platform on 2026-04-22.

Inventory

Already provisioned / seen online previously (5)

Phones in this group have reached a SIP registrar at least once. Currently showing Offline in YMCS — possibly powered off, unplugged, or waiting on next provisioning fetch.

#	MAC	YMCS Label	Last-seen Device IP	Private IP	Notes
1	`805e0cdd755b`	SIP-T54W (default)	96.86.0.70	192.168.0.130	Needs user / extension assignment
2	`805e0cdd6d01`	`214-ValleyWidePlastering`	96.86.0.70	192.168.0.140	Extension 214 — user TBD
3	`44dbd26f6a36`	SIP-T54W (default)	96.86.0.75	192.168.0.54	Different registrar IP than the .70 group — verify intended target
4	`805e0c78958e`	SIP-T54W (default)	96.86.0.45	192.168.0.222	Different registrar IP than the .70 group — verify intended target
5	`805e0cdd71b1`	`Reception`	96.86.0.70	192.168.0.17	Front desk phone

Pending (11)

Added to the YMCS inventory but have not yet contacted the provisioning server. These either haven't been plugged in, aren't getting DHCP, or are blocked from reaching the YMCS service URL.

#	MAC
6	`805e0cdd73bd`
7	`805e0c6aa890`
8	`805e0cdd6cf9`
9	`805e0cdd7453`
10	`805e0cdd73b7`
11	`805e0cdd7559`
12	`805e0cdd6cf5`
13	`805e0cdd6fb5`
14	`805e0cdd7441`
15	`805e0cdd6509`
16	`805e0c7896b8`

Observations / open items

Two different last-seen registrar IPs among the Offline group: 96.86.0.70 (three phones + reception), 96.86.0.75 (one phone), 96.86.0.45 (one phone). Confirm all three are legitimate (PBX failover / different tenant routing) vs. stale config on the outlier phones.
Only two phones are labelled (214-ValleyWidePlastering, Reception). Label the remaining 14 in YMCS with extension + user once assigned — makes diagnostic triage much faster.
Private IPs spread across 192.168.0.0/24 (.17, .54, .130, .140, .222) — confirm these are DHCP reservations or static assignments on the UDM so the phone subnet is stable.
Pending phones need first-boot provisioning — once plugged in on VWP's LAN with internet, they should auto-fetch config from YMCS. If any stay Pending after being plugged in, check: DHCP option 66 / DNS for YMCS reachability, firewall egress to *.yealink.com, and whether the phone firmware supports current YMCS handshake.

Reference

Yealink YMCS (US): https://us.ymcs.yealink.com/manager/sip-product/sipManage
OUI check: 805e0c, 44dbd2 — both Yealink Network Technology Co., Ltd.
Related: clients/valleywide/README.md (infrastructure overview), clients/valleywide/session-logs/2026-04-22-hp-server-nvram-corruption-emergency.md

3.1 KiB Raw Blame History