Unify — 3 prefixes (MA-L) across two distinct legal entities

The slug vendor-unify is a name collision, not a single company: the IEEE OUI registry holds three MA-L blocks whose organization names contain "Unify," and they belong to two unrelated firms. Two prefixes — 60:DB:EF and 00:1A:E8 — are registered to "Unify Software and Solutions GmbH & Co. KG" at Otto-Hahn-Ring 6, Munich 81739, Germany, the former Siemens Enterprise Communications / unified-communications division now owned by Mitel. The third, 00:02:08, is registered to "Unify Networks, Inc." in Santa Clara, California — a separate, unrelated networking-equipment company. Any vendor page must keep these apart rather than merging them under one brand. The German Unify is the substantive one for asset-classification purposes: its hardware is enterprise IP telephony — OpenScape Desk Phone IP (35G/55G in SIP and HFA/CorNet-IP variants), OpenScape CP-series phones, OpenScape DECT and WLAN handsets, and the HiPath/OpenScape UC platforms behind them. There is a documented data-quality trap on 00:1A:E8: because that block dates to the Siemens era and was shared with legacy Siemens wireless access points, Extreme Networks NAC systems have been observed misclassifying Unify VoIP desk phones as "Wireless Access Points," which can drive wrong VLAN placement and policy enforcement until the NAC fingerprint is corrected. As with all OUI data, IEEE publishes no registration dates; any "date registered" seen on third-party lookup tools is a database artifact, not an IEEE fact.

IEEE assignment (Unify Software and Solutions)

60:DB:EF and 00:1A:E8 → Unify Software and Solutions GmbH & Co. KG, Otto-Hahn-Ring 6, Munich 81739, DE [Confirmed] — enrichment/registries/oui.csv (lines 137, 8196); maclookup.app/vendors/unify-software-and-solutions-gmbh-co-kg

IEEE assignment (Unify Networks)

00:02:08 → Unify Networks, Inc., 3160 De La Cruz Blvd., Santa Clara, CA 95054, US [Confirmed] — enrichment/registries/oui.csv (line 5847). NOTE: a separate, unrelated legal entity from the German Unify; do not merge.

Registry / block size

all three are MA-L (24-bit OUI, ~16M addresses each) [Confirmed] — enrichment/registries/oui.csv; maclookup.app

Other registries

no matching entries in mam.csv (MA-M) or oui36.csv (MA-S) [Confirmed] — enrichment/registries/mam.csv, oui36.csv (searched, zero hits)

Registration date

Unknown — IEEE publishes NO assignment/registration date in its OUI data; the cached registry CSVs contain no date column. Third-party tool maclookup.app shows 2006-12-30 (00:1A:E8) and 2023-03-22 (60:DB:EF), but those are database artifacts, NOT IEEE facts and must not be presented as IEEE registration dates. [Confirmed that no IEEE date exists] — enrichment/registries/oui.csv; maclookup.app/vendors/unify-software-and-solutions-gmbh-co-kg

Company status (Unify Software and Solutions)

active as a brand, now part of Mitel; acquisition by Mitel completed October 2023 [Confirmed] — mitel.com/unify-now-part-mitel; futurumgroup.com (Mitel completes acquisition of Unify)

Company lineage (Unify Software and Solutions)

traces to Siemens Enterprise Communications; JV with The Gores Group (51%) formed 2008; rebranded "Unify" October 2013; acquired by Atos (~€340–366M, completed January 2016); acquired by Mitel (completed October 2023) [Confirmed] — en.wikipedia.org/wiki/Unify_(company); atos.net 2016-01-20 press release; mitel.com/unify-now-part-mitel

Company status (Unify Networks, Inc.)

Unknown — not researched in this pass; registry record only [Unknown] — enrichment/registries/oui.csv (line 5847)

Device types (Unify Software and Solutions)

enterprise IP telephony — OpenScape Desk Phone IP (35G/55G; SIP and HFA/CorNet-IP), OpenScape CP-series desk phones, OpenScape DECT handsets/infrastructure, OpenScape WLAN Phone WL4; UC platforms OpenScape Voice/4000/Business, HiPath [Confirmed] — wiki.unify.com/wiki/Devices; wiki.unify.com/wiki/OpenScape_Desk_Phone_IP

Notable products

OpenScape and HiPath unified-communications lines; Circuit (SaaS team collaboration, discontinued under Mitel) [Confirmed] — wiki.unify.com/wiki/Devices; mitel.com/unify-now-part-mitel

Data trap (00

1A:E8): block dates to the Siemens era and was shared with legacy Siemens wireless access points; Extreme Networks NAC has been documented misclassifying Unify VoIP desk phones as "Wireless Access Points," fixed by cloning/modifying the NAC fingerprint definition. Real operational/security risk for VLAN placement and policy enforcement. [Confirmed; single community-thread source] — community.extremenetworks.com/t5/extremecontrol/wrong-device-type-assigned-to-unify-voip-phone-in-nac/m-p/98605

Security context

Unify documents VoIP security practices (TLS, SRTP, SPE, PKI) on HiPath/OpenScape; no CVE or threat-actor abuse of this OUI range surfaced in this pass [Likely] — wiki.unify.com/wiki/VoIP_Security

Website

https://www.mitel.com (current, post-acquisition); legacy product docs at https://wiki.unify.com remain accessible as of June 2026 [Confirmed] — mitel.com/unify-now-part-mitel; wiki.unify.com/wiki/Devices

IANA Reference

none — no IANA RFC reference applies to OUI assignments; column stays blank [Confirmed]

Analyst note

a 60:DB:EF / 00:1A:E8 OUI on a globally-administered address identifies genuine (German) Unify enterprise telephony hardware, but 00:1A:E8 is ambiguous with legacy Siemens APs — verify device type, don't infer it from the OUI alone. 00:02:08 is a different company entirely.