MS Teams - DHCP Configuration for Teams SIP Gateway
DHCP Configuration for Teams SIP Gateway (Poly & Yealink 3PIP Devices)
1. Required DHCP Options for Microsoft Teams SIP Gateway
-------------------------------------------------------
Microsoft Teams SIP Gateway requires specific DHCP options so legacy 3PIP desk phones (Poly & Yealink) can locate the Teams provisioning service automatically.
Poly: Option 160 – Provisioning server URL
Yealink: Option 66 – Provisioning server URL
Both: Option 42 – NTP Server
2. Microsoft Teams SIP Gateway Provisioning URLs
------------------------------------------------
Americas: http://noam.ipp.sdg.teams.microsoft.com
EMEA: http://emea.ipp.sdg.teams.microsoft.com
APAC: http://apac.ipp.sdg.teams.microsoft.com
3. Configuring DHCP Option 66 (Yealink)
--------------------------------------
Use Option 66 when provisioning Yealink devices for Teams SIP Gateway.
Steps:
- Open DHCP Manager
- Navigate to Scope Options
- Configure Option 066 – Boot Server Host Name
- Enter provisioning URL
4. Configuring DHCP Option 160 (Poly)
------------------------------------
Use Option 160 when provisioning Poly devices.
Steps:
- Open DHCP Manager
- Add Option 160 – String
- Enter Teams SIP Gateway provisioning URL
- Ensure LLDP is enabled
5. Option 42 (NTP Server)
-------------------------
Example: pool.ntp.org
6. Device Behavior for Teams SIP Gateway
---------------------------------------
Devices will:
- Contact the provisioning server
- Download firmware
- Display Teams SIP Gateway sign-in UI
7. Troubleshooting Notes
------------------------
Poly:
- Switch between https:// and http:// if issues occur
- Ensure LLDP is enabled
General:
- Reboot phone after DHCP changes
- Validate DHCP delivery via ipconfig /all, logs, packet captures
8. Example DHCP Option Configurations
-------------------------------------
Poly:
Option 160: http://noam.ipp.sdg.teams.microsoft.com
Option 42: pool.ntp.org
Yealink:
Option 66: http://noam.ipp.sdg.teams.microsoft.com
Option 42: pool.ntp.org