Differences

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

--- userdoc:tt_ip_phone_provisioning [2018/03/01 12:41]
droemel [IP Phone Provisioning]
+++ userdoc:tt_ip_phone_provisioning [2021/06/26 04:24]
mkeuter [Phone Template Syntax]
@@ Line 190: / Line 190: @@
 | ''@EXT@'' | Extension as defined in ''massdeployment.conf'' |
 | ''@CID_NAME@'' | CallerID name optionally defined in ''massdeployment.conf'', defaults to ''@EXT@'' |
+| ''@CID_NUM@'' | CallerID num optionally defined in ''massdeployment.conf'' with a ''<xxx>'' suffix in ''@CID_NAME@'', defaults to ''@EXT@'' |
 | ''@PASSWORD@'' | SIP password as defined in ''massdeployment.conf'' |
 | ''@ACCOUNT@'' | SIP account as defined in ''massdeployment.conf'' or auto-generated |
@@ Line 196: / Line 197: @@
 | ''@EXT1-6@'' | ''@EXT1@'' matches ''@EXT@'' above, ''@EXT2@'' to ''@EXT6@'' are defined using a \\ semi-colon delimited extension/cid_name in ''massdeployment.conf'' |
 | ''@CID_NAME1-6@'' | ''@CID_NAME1@'' matches ''@CID_NAME@'' above, ''@CID_NAME2@'' to ''@CID_NAME6@'' are defined using a \\ semi-colon delimited extension/cid_name in ''massdeployment.conf'' |
+| ''@CID_NUM1-6@'' | ''@CID_NUM1@'' matches ''@CID_NUM@'' above, ''@CID_NUM2@'' to ''@CID_NUM6@'' are defined using a \\ ''<xxx>'' suffix in '@CID_NAME@'' in ''massdeployment.conf'' |
 | ''@PASSWORD1-6@'' | ''@PASSWORD1@'' matches ''@PASSWORD@'' above, ''@PASSWORD2@'' to ''@PASSWORD6@'' default to ''@PASSWORD@'' \\ or are defined using a semi-colon delimited password in ''massdeployment.conf'' |
 | ''@ACCOUNT1-6@'' | ''@ACCOUNT1@'' matches ''@ACCOUNT@'' above, ''@ACCOUNT2@'' to ''@ACCOUNT6@'' default to auto-generated \\ or are defined using a semi-colon delimited account in ''massdeployment.conf'' |
@@ Line 277: / Line 279: @@
 !!Tip ->!! If your IP Phone does not support the DHCP "option-66" (tftp-server) feature, you must manually define the provisioning URL in the phone's web interface. Some vendors like Cisco are using additional custom DHCP options like 159 + 160.
-!!Tip ->!! If you need to use a different DHCP server (tested with a Windows Server 2008R2), you could also try to test DHCP option 60 (Vendor Class Identifier - sent by the phone (e.g. ''snom300'')) and option 43 (sent by the server) which can encapsulate the option 66 setting. The phones must be able to send option 60 and understand option 43 though (tested with Snom 300 phones with newer firmware!).\\ [[http://www.ingmarverheij.com/microsoft-vendor-specific-dhcp-options-explained-and-demystified/|Link]] ((Windows-only program to encapsulate the string => at the bottom of the page)), e.g. [[http://wiki.snom.com/Features/Auto_Provisioning/DHCP/Options|Snom options]]
+!!Tip ->!! If you need to use a different DHCP server (tested with a Windows Server 2008R2), you could also try to test DHCP option 60 (Vendor Class Identifier - sent by the phone (e.g. ''snom300'' or ''yealink'')) and option 43 (sent by the server) which can encapsulate the option 66 setting. The phones must be able to send option 60 and understand option 43 though (tested with Snom 300 phones with newer firmware and Yealink phones!).\\ [[http://www.ingmarverheij.com/microsoft-vendor-specific-dhcp-options-explained-and-demystified/|Link]] ((Windows-only program to encapsulate the string => at the bottom of the page)), e.g. [[http://wiki.snom.com/Features/Auto_Provisioning/DHCP/Options|Snom options]]
 !!Tip ->!! If your IP Phone does not support HTTP/HTTPS provisioning, TFTP may be used by placing the provisioning files in the ''/mnt/kd/tftpboot/'' directory. In this case sub-directories within ''tftpboot'' like with HTTP mostly don't work!.