Differences

This shows you the differences between two versions of the page.

--- voice:phones:yealink:yealink_prov [2014/12/13 14:31]
gcooper
+++ voice:phones:yealink:yealink_prov [2015/03/17 16:08] (current)
gcooper
@@ Line 1: / Line 1: @@
 ====== Yealink Phone Provisioning ======
-Yealink FTP Server: ftp://ftp.yealink.com/RPS/T4X/
+**Yealink FTP Server**: ftp://ftp.yealink.com/RPS/T4X/
+===== DHCP =====
+**Windows DHCP Server**: http://www.3cx.com/sip-phones/dhcp-option-66/
+  * Not all Yealink firmware supports RPS
+  * RPS is supported on brand new phones
+  * You can also use DHCP Option 66 to pass a provisioning URL to a Yealink phone
+    * Be patient when reprovisioning as it sometimes takes a few minutes and the phone may reboot again
+    * Use the same URL as with RPS
+      * FreePBX Commercial EPM example URL: http://192.168.50.30:84
 ===== Yealink Redirection and Provisioning Service (RPS) =====
-Web Page: http://www.888voip.com/rps-redirection-and-provisioning-service-by-yealink/
+**Web Page**: http://www.888voip.com/rps-redirection-and-provisioning-service-by-yealink/
-User Guide: http://www.888voip.com/downloads/yealink/YealinkRedirectionandProvisioningService(RPS)UserManual-V1.0-ENG.pdf
+**User Guide**: http://www.888voip.com/downloads/yealink/YealinkRedirectionandProvisioningService(RPS)UserManual-V1.0-ENG.pdf
-Web Interface: https://rps.yealink.com
+**Web Interface**: https://rps.yealink.com
 Yealink RPS is a free service that redirects a Yealink phone to provision itself.
@@ Line 17: / Line 28: @@
 :!: Four types of URL are supported: http, https, ftp and tftp.
-:!: Not all firmwares support RPS.  When troubleshooting, suspect this first!
+:!: **Not all firmwares support RPS.**  When troubleshooting, suspect this first!
+===== FreePBX Commercial End Point Management =====
+:!: The firmwares downloaded by the FreePBX EPM do not support RPS as of 12/13/14.
+:!: You can get the phones to change VLANs with auto-provisioning setttings.
+  - New phone boots (has RPS-compatible firmware)
+  - Phone gets IP address from DHCP server on 'data' LAN (untagged)
+  - Phone contacts RPS and gets a provisioning URL
+  - Phone gets configuration from provisioning server
+  - Phone downloads and upgrades its firmware from the provisioning server (if newer)
+  - Phone reboots into proper VLAN with proper configuration
+  - Phone gets IP address via DHCP from PBX DHCP server
+  - Phone registers extension with PBX
+Configuration settings needed with phones on a separate VLAN but sharing a CAT5 cabling plant (using the switches in the phones):
+<file>
+network.lldp.enable = 0
+network.vlan.dhcp_enable = 0
+network.vlan.internet_port_vid = nnn
+network.vlan.internet_port_priority = 5
+network.vlan.internet_port_enable = 1
+</file>
+:!: LLDP may confuse the phone VLAN functionality.  It did on a Zyxel GS1910-24HP switch.

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools