Differences

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

--- userdoc:tt_ip_phone_provisioning [2015/01/30 09:57]
abelbeck [Reload Action Script (optional)]
+++ userdoc:tt_ip_phone_provisioning [2021/06/26 07:33] (current)
abelbeck
@@ Line 169: / Line 169: @@
 | ''pjsip_file='' | Generated pjsip file name, defaults to ''astlinux-phoneprov-pjsip.conf'' |
 | ''sql_enable='' | Either 'yes' or 'no' to automatically create 'phoneprov' SQLite3 table, defaults to ''yes'' |
+| ''sip_driver='' | Either 'sip' or 'pjsip' to define a column in 'phoneprov' SQLite3 table, defaults to ''sip'' |
 ^ The [general] context advanced user variable definitions: ^^
@@ Line 189: / 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'' as a ''<nnn>'' suffix in ''@CID_NAME@'', defaults to ''@EXT@'' (e.g. ''201/Alice_DECT<101>'') |
 | ''@PASSWORD@'' | SIP password as defined in ''massdeployment.conf'' |
 | ''@ACCOUNT@'' | SIP account as defined in ''massdeployment.conf'' or auto-generated |
@@ Line 195: / 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 \\ ''<nnn>'' 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 200: / Line 203: @@
 !!Note ->!! The optional CID_Name in ''massdeployment.conf'' must NOT contain quotes or spaces, use underscores "_", they will be mapped to spaces.
+!!Note ->!! For the optional CID_NUM variable(s) !!AstLinux 1.4.3 or later!! is required. It let's you override the ''CALLERID(num)'' independant from the extension with a ''<nnn>'' suffix in ''CID_NAME'' and it stored in the SQL database as ''cid_num''.
 !!Note ->!! Auto-generated account names, with optional ''auto_account_case'' case, result in the format:
@@ Line 229: / Line 234: @@
   [dialplan2]
   exten => @EXT@,hint,SIP/@ACCOUNT@
 ===== Reload Action Script (optional) =====
@@ Line 236: / Line 240: @@
 The optional "''/mnt/kd/phoneprov-reload.script''" action script will be called when "Reload Dialplan/SIP" is checked.
-By default, and "''/mnt/kd/phoneprov-reload.script''" does not exist, when "Reload Dialplan/SIP" is checked the following commands are executed:
+By default, when "''/mnt/kd/phoneprov-reload.script''" does not exist, and when "Reload Dialplan/SIP" is checked, the following commands are executed:
   asterisk -rx "dialplan reload" >/dev/null
   asterisk -rx "sip reload" >/dev/null
-You can customize these actions by creating a "''/mnt/kd/phoneprov-reload.script''" script, for example the following script will replicate the default action:
+You can customize these actions by creating a "''/mnt/kd/phoneprov-reload.script''" script. For example the following script will replicate the default action:
   #!/bin/sh
@@ Line 248: / Line 252: @@
   asterisk -rx "sip reload" >/dev/null
+If you require reloading ''fop2'' or pjsip related asterisk modules, you can do that with this custom script.
 !!Note ->!! Be sure to make your "''/mnt/kd/phoneprov-reload.script''" executable using the ''chmod'' command via the CLI.
@@ Line 274: / Line 279: @@
 Restart **DNS & DHCP** (dnsmasq) and reboot the IP Phone to apply any ''/mnt/kd/dnsmasq.static'' file changes.
 !!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'' 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!.