AdminGuide:Service:AutoProvisioning/en - Cronologia

Troccoli il 21:07, 25 set 2022

2022-09-25T21:07:08Z

← Versione meno recente		Versione delle 21:07, 25 set 2022
Riga 1:		Riga 1:
	<languages />		<languages />
	~~<div class="mw-translate-fuzzy">~~
	Return to [[AdminGuide:Service/en\|AdminGuide:Service]]		Return to [[AdminGuide:Service/en\|AdminGuide:Service]]
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	===Description===		===Description===
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	The Auto Provisioning service generates the configuration file necessary for the correct operation of a device and transfers them to your phones. This file also contains information on the account and extension linked to the phone.		The Auto Provisioning service generates the configuration file necessary for the correct operation of a device and transfers them to your phones. This file also contains information on the account and extension linked to the phone.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	== Configuration ==		== Configuration ==
	This section collects all the configurations needed to perform auto-provisioning of a telephone device.		This section collects all the configurations needed to perform auto-provisioning of a telephone device.
	You can also consult the <u>[[AdminGuide:Service:AutoProvisioning:DeviceList/en\|list built-in devices for auto-provisioning]]</u>		You can also consult the <u>[[AdminGuide:Service:AutoProvisioning:DeviceList/en\|list built-in devices for auto-provisioning]]</u>
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	==Device list==		==Device list==
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	[[File:Provisioning.png\|miniatura]]		[[File:Provisioning.png\|miniatura]]
	This page contains the list of all devices for which provisioning file generation has been configured.		This page contains the list of all devices for which provisioning file generation has been configured.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	The following table lists the configurable parameters for each device.		The following table lists the configurable parameters for each device.
	~~</div>~~

	{\| class="wikitable"		{\| class="wikitable"
Riga 91:		Riga 77:
	This page shows the list of templates on the KalliopePBX.		This page shows the list of templates on the KalliopePBX.

	~~<div class="mw-translate-fuzzy">~~
	It is necessary to select a template for each phone model for which you wish to generate a provisioning file.		It is necessary to select a template for each phone model for which you wish to generate a provisioning file.
	~~</div>~~

	{\| class="wikitable"		{\| class="wikitable"

Troccoli: Creata pagina con "The following table lists the configurable parameters for each model."

2022-09-20T14:18:07Z

Creata pagina con "The following table lists the configurable parameters for each model."

← Versione meno recente		Versione delle 14:18, 20 set 2022
Riga 214:		Riga 214:

	==Template==		==Template==
	~~La generazione del~~ file ~~di configurazione per uno specifico dispositivo viene effettuata~~ a ~~partire da un~~ template ~~associato alla marca/modello di telefono che si intende utilizzare~~.~~<br>~~		The configuration file for a specific device is generated from a template for the brand and model of the phone.

	~~Il formato del~~ template ~~dipende dalla marca/modello del telefono utilizzato ma anche eventualmente dalla versione del~~ firmware ~~installata sul dispositivo~~. ~~<br>~~		The template format depends on the brand and model of the phone as well as the version of its firmware.

	~~Nella definizione del~~ template ~~è possibile utilizzare dei placeholder che il KalliopePBX sostituirà automaticamente in fase di generazione del~~ file. ~~<br>~~		When defining a template it is possible to use placeholders that Kalliope will automatically replace when generating the file.
	~~Questi placeholder includono~~:
	*~~Attributi del~~ KalliopePBX (~~ad es~~. ~~porta~~ SIP UDP/TCP ~~del centralino~~)		These placeholders include:
	*~~Attributi dell’account~~/~~interno associato al telefono~~ (~~ad es~~. ~~credenziali~~ SIP, ~~nome~~, ~~cognome~~, etc.)		* KalliopePBX attributes (e.g. SIP UDP/TCP port of the PBX);
	*~~Attributi del telefono~~ (~~ad es~~. ~~parametri di rete~~, ~~credenziali di accesso~~, etc.) ~~<br>~~		* attributes of the extension/account linked to the phone (e.g. SIP credentials, first name, last name, etc.);
			* phone attributes (e.g. network parameters, access credentials, etc.).


Riga 234:		Riga 235:
	All generated files are also visible in the File Manager.		All generated files are also visible in the File Manager.

	~~Per indicare al telefono quale protocollo deve essere utilizzato per scaricare il~~ file ~~di configurazione oltre all’indirizzo~~ IP (~~ed eventuale~~ path) ~~del~~ server ~~di provisioning esistono diverse modalità la cui configurazione e ordine di esecuzione dipende dal modello di telefono utilizzato~~. ~~Le modalità comunemente disponibili sono le seguenti~~:		To tell the phone which protocol should be used to download the configuration file in addition to the IP address (and possible path) of the provisioning server, there are several modes whose configuration and execution order depend on the phone model used. The commonly available methods are as follows:
	*'''SIP PnP''': ~~il telefono all’avvio invia un messaggio~~ SIP SUBSCRIBE ~~ad un indirizzo~~ multicast. ~~Se sul~~ KalliopePBX ~~il servizio~~ SIP PnP ~~è abilitato il~~ PBX ~~risponde con una~~ SIP NOTIFY ~~contenente l’IP address del~~ TFTP server ~~da utilizzare~~. ~~Questa modalità non è utilizzabile nel caso di~~ KalliopePBX ~~multitenant~~.		*'''SIP PnP''': the phone at startup sends a SIP SUBSCRIBE message to a multicast address. If on the KalliopePBX the SIP PnP service is enabled, the PBX responds with a SIP NOTIFY containing the TFTP server's IP address to be used. This mode cannot be used in the case of multitenant KalliopePBX.
	*'''Redirection Server''': ~~il telefono all’avvio prova a contattare il~~ Redirection Server ~~del produttore~~. ~~Se il~~ MAC Address ~~del telefono è stato inserito il telefono viene rediretto al~~ server ~~indicato per il~~ download ~~del~~ file ~~di configurazione~~. In ~~questa modalità è possibile utilizzare uno qualsiasi dei protocolli disponibili~~ (~~in base al parametro configurato sul~~ redirection server).		*'''Redirection Server''': the phone at startup tries to contact the manufacturer's Redirection Server. If the phone's MAC Address is entered, the phone is redirected to the indicated server to download the configuration file. In this mode, you can use any available protocols (depending on the parameter configured on the redirection server).
	*'''DHCP OPTION 66''': ~~nel caso in cui~~ in ~~fase di assegnazione dell’indirizzo~~ IP il DHCP Server ~~comunichi al telefono anche la~~ DHCP Option 66 ~~contenente l’URL da contattare~~ (~~incluso il protocollo da utilizzare~~), ~~il telefono utilizzerà questa informazione per effettuare il~~ download ~~del~~ file ~~di configurazione~~.		*'''DHCP OPTION 66''': in the case when assigning the IP address, the DHCP Server also communicates to the phone the DHCP Option 66 containing the URL to be contacted (including the protocol to be used), the phone will use this information to make the download of the configuration file.
	*'''~~Manuale~~''': ~~è possibile avviare la configurazione anche manualmente dal telefono o dalla~~ WEB GUI ~~inserendo il protocollo da utilizzare e l’IP~~ address (~~oltre eventualmente al~~ path).		*'''Manual''': you can also start the configuration manually from the phone or the WEB GUI by entering the protocol to be used and the IP address (as well as the path, if necessary).

Troccoli: Creata pagina con "==List of device models== miniatura This page contains the list of all models defined on KalliopePBX. Some models are distributed with t..."

2022-09-20T14:13:26Z

Creata pagina con "==List of device models== miniatura This page contains the list of all models defined on KalliopePBX. Some models are distributed with t..."

← Versione meno recente		Versione delle 14:13, 20 set 2022
Riga 191:		Riga 191:
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! ~~Parametro~~ !! ~~Descrizione~~ !! ~~Valore~~		! Parameter!! Description!! Value
	\|-		\|-
	\|colspan="3"\| <div style = 'text-align: center; color: transparent> -		\|colspan="3"\| <div style = 'text-align: center; color: transparent> -
	\|-		\|-
	\| ~~Marca del dispositivo~~ \|\| ~~Marca del dispositivo per cui si sta definendo il~~ redirection server \|\| Snom / Yealink / Escene		\| Device brand \|\| Brand of the device for which the redirection server is being defined \|\| Snom / Yealink / Escene
	\|-		\|-
	!colspan="3"\| <div style = 'text-align: left> '''''~~Credenziali~~'''''		!colspan="3"\| <div style = 'text-align: left> '''''Credentials'''''
	\|-		\|-
	\| Username\|\|~~Utente per l’autenticazione sul~~ server ~~RPS del produttore~~ \|\| ~~Stringa~~		\| Username\|\|User for authentication on the manufacturer's RPS server \|\| String
	\|-		\|-
	\| Password\|\| Password ~~per l’autenticazione sul~~ server ~~RPS del produttore~~ \|\| ~~Stringa~~		\| Password\|\| Password for authentication on the manufacturer's RPS server \|\| String
	\|-		\|-
	!colspan="3"\| <div style = 'text-align: left> '''''~~Impostazioni~~'''''		!colspan="3"\| <div style = 'text-align: left> '''''Settings'''''
	\|-		\|-
	\| ~~Abilitato~~\|\| ~~Consente di disabilitare il~~ redirection server ~~senza perderne la configurazione~~ \|\| Si / No		\| Enabled \|\| Allows you to disable the redirection server without losing its configuration \|\| Yes / No
	\|-		\|-
	\| ~~Nome~~\|\| ~~Nome del~~ redirection server ~~da creare~~ (se SNOM) ~~o da utilizzare~~ (~~nel caso~~ Yealink / Escene) \|\| ~~Stringa~~		\| Name\|\| Name of the redirection server to be created (if SNOM) or to be used (in the case of Yealink / Escene) \|\| String
	\|-		\|-
	\| ~~Indirizzo di provisioning~~\|\| ~~Nel caso~~ SNOM URL ~~a cui viene effettuata la redirezione~~ (~~ad es.~~ https://192.168.0.100/provisioning/ ) \|\| ~~Stringa~~		\| Provisioning address\|\| In the case SNOM URL to which the redirection is made. (example: https://192.168.0.100/provisioning/ ) \|\| String
	\|}		\|}

Troccoli: Creata pagina con "Once a file has been generated, it must be transferred to the phone. KalliopePBX provides the following file transfer protocols: *'''TFTP''': files are available directly in t..."

2022-09-20T14:12:24Z

Creata pagina con "Once a file has been generated, it must be transferred to the phone. KalliopePBX provides the following file transfer protocols: *'''TFTP''': files are available directly in t..."

Mostra modifiche

Troccoli: Creata pagina con "Once the template has been defined, you must specify the MAC address of the device and the account/extensions you wish to link it to."

2022-09-20T14:00:00Z

Creata pagina con "Once the template has been defined, you must specify the MAC address of the device and the account/extensions you wish to link it to."

← Versione meno recente		Versione delle 14:00, 20 set 2022
Riga 31:		Riga 31:
	</div>		</div>

	~~<div~~ class="mw-~~translate~~-~~fuzzy~~">		{\| class="wikitable"
	~~Once a~~ file has been ~~generated~~, ~~it must~~ be ~~transferred~~ to the ~~phone~~. ~~KalliopePBX provides~~ the ~~following~~ file ~~transfer protocols:~~		\|-
	*TFTP: files are available directly in the ~~root of~~ the ~~TFTP server~~ for ~~single~~-~~tenant~~ KalliopePBX. ~~For multitenant KalliopePBX, you must add~~ the ~~Tenant UUID~~ to the ~~path (e~~.g. <~~tenant_uuid~~>~~/snom370~~-~~0004167898B1.htm~~).		! Parameter !! Description !! Value
	*HTTP ~~/ HTTPS:~~ the ~~files are published on http(s~~)~~://~~<~~ip_address~~>~~/provisioning/ for single~~-~~tenant KalliopePBX. For multitenant KalliopePBX~~, ~~you must add~~ the ~~Tenant UUID to~~ the ~~path (e.g~~. ~~http~~(s):~~//<ip_address~~>~~/provisioning/~~<~~tenant_uuid~~>/).		\|-
	~~</div>~~		\|colspan="3"\| <div style = 'text-align: center; color: transparent> -
			\|-
			\| Enabled \|\| Allows you to disable the generation of the provisioning file associated with the device \|\| Yes / No
			\|-
			!colspan="3"\| <div style = 'text-align: left> '''''Device model'''''
			\|-
			\| Brand \|\| List of manufacturers for which at least one device model has been defined \|\| Brand
			\|-
			\|Model\|\| List of devices associated with the selected manufacturer \|\| Model
			\|-
			\| Template\|\| List of templates associated with the selected template \|\| Template
			\|-
			!colspan="3"\| <div style = 'text-align: left> '''''Redirection Server'''''
			\|-
			\| Redirection Server for provisioning \|\| List of redirection servers defined for the selected manufacturer \|\| Redirection Server
			\|-
			\| Provisioned on the redirection server\|\| Read-only field indicates whether the provisiong on the redirection server was successful \|\| Yes / No
			\|-
			!colspan="3"\| <div style = 'text-align: left> '''''Device configuration'''''
			\|-
			\| MAC Address \|\| MAC address of the device (formats that are accepted AABBCCDDEEFF, AA:BB:CC:DD:EE:FF, AA-BB-CC-DD-EE-FF) \|\| MAC Address
			\|-
			\| Notes \|\| Free field containing annotations about the device \|\| String
			\|-
			\| Enable DHCP \|\| Set the placeholder value %%IPADDRMODE%% to on/off for this device. The placeholder may be used in the template to generate the configuration file with the with the required network settings. \|\| Si / No
			\|-
			\| IP Address \|\| Set the placeholder value %%IPADDR%% for this device. The placeholder may be used in the template to generate the configuration file with the required network settings. \|\| IP Address
			\|-
			\| Subnetwork mask \|\| Set the placeholder value %%IPNETMASK%% for this device. The placeholder may be used in the template to generate the configuration file with the required network settings. \|\| Subnet Mask
			\|-
			\| Gateway \|\| Set the placeholder value %%IPGATEWAY%% for this device. The placeholder may be used in the template to generate the configuration file with the required network settings.\|\| IP Address
			\|-
			\| DNS1 \|\| Set the placeholder value %%IPDNS1%% for this device. The placeholder may be used in the template to generate the configuration file with the required network settings. \|\| IP Address
			\|-
			\| DNS2\|\| Set the placeholder value %%IPDNS2%% for this device. he placeholder may be used in the template to generate the configuration file with the required network settings. \|\| IP Address
			\|-
			\| Username \|\| Set the placeholder value %%PHONEUSERNAME%% for this device. The placeholder may be used in the template to set the phone login credentials. This same value will be used by KalliopePBX to drive the phone when a KalliopeCTI PRO application is associated with the device. \|\| String
			\|-
			\| Password\|\| Set the placeholder value %%PHONEPASSWORD%% for this device. The placeholder may be used in the template to set the phone login credentials. This same value will be used by KalliopePBX to drive the phone when a KalliopeCTI PRO application is associated with the device. \|\| String
			\|-
			!colspan="3"\| <div style = 'text-align: left> '''''Remote control'''''
			\|-
			\| Address \|\| If defined, specifies the IP address at which the phone's web interface can be reached (by the PBX) (in HTTP) in order to perform remote control (via the KalliopeCTI Pro application) <br>If empty, the PBX will use the IP address from which the account associated with this device is registered at the SIP level \|\| IP Address
			\|-
			\| Port \|\| Same as the previous field, but related to the port on which the phone web interface is visible by the PBX. \|\| Integer (range 1-65535)
			\|-
			!colspan="3"\| <div style = 'text-align: left> '''''Device user'''''
			\|-
			\| Account \|\| Account and internal correspondent associated with the device (dynamic placeholders are calculated from this association).<br> If the account is not associated the configuration file is not generated and the device is entered as Disabled. \|\| Account
			\|-
			\|}

	~~<div class~~=~~"mw-translate-fuzzy">~~		==Template list==
	~~All generated files are also visible in the~~ File ~~Manager~~.		[[File:Lista template.png\|miniatura]]
	~~</div>~~		This page shows the list of templates on the KalliopePBX.

	<div class="mw-translate-fuzzy">		<div class="mw-translate-fuzzy">

Troccoli il 13:56, 20 set 2022

2022-09-20T13:56:18Z

Mostra modifiche

S.vistoli il 08:19, 8 gen 2020

2020-01-08T08:19:20Z

← Versione meno recente		Versione delle 08:19, 8 gen 2020
Riga 7:		Riga 7:
	===Description===		===Description===

	~~<div class="mw-translate-fuzzy">~~
	The Auto Provisioning service generates the configuration file necessary for the correct operation of a device and transfers them to your phones. This file also contains information on the account and extension linked to the phone.		The Auto Provisioning service generates the configuration file necessary for the correct operation of a device and transfers them to your phones. This file also contains information on the account and extension linked to the phone.
	</~~div>~~
			The provisioning devices can be configured in the [[AdminGuide:GUI:OperatingMenu:AutoProvisioning/en\|AutoProvisioning]] page.

	The configuration file for a specific device is generated from a template for the brand and model of the phone.		The configuration file for a specific device is generated from a template for the brand and model of the phone.

FuzzyBot: Aggiornamento come da nuova versione della pagina di origine

2020-01-08T08:19:17Z

Aggiornamento come da nuova versione della pagina di origine

← Versione meno recente		Versione delle 08:19, 8 gen 2020
Riga 7:		Riga 7:
	===Description===		===Description===

			<div class="mw-translate-fuzzy">
	The Auto Provisioning service generates the configuration file necessary for the correct operation of a device and transfers them to your phones. This file also contains information on the account and extension linked to the phone.		The Auto Provisioning service generates the configuration file necessary for the correct operation of a device and transfers them to your phones. This file also contains information on the account and extension linked to the phone.
			</div>

	The configuration file for a specific device is generated from a template for the brand and model of the phone.		The configuration file for a specific device is generated from a template for the brand and model of the phone.

Silvia il 10:46, 14 mag 2018

2018-05-14T10:46:23Z

← Versione meno recente		Versione delle 10:46, 14 mag 2018
Riga 32:		Riga 32:
	There are several modes for telling the phone which protocol to use to download configuration files. Their configuration and order of execution depends on the model of the phone. The currently available modes are:		There are several modes for telling the phone which protocol to use to download configuration files. Their configuration and order of execution depends on the model of the phone. The currently available modes are:

	*SIP PnP: upon starting up the phone sends a SIP SUBSCRIBE message tp a multicast address. If SIP PnP is enabled on KalliopePBX, the PBX will reply with a SIP NOTIFY message containing the IP address of the TFTP server to use. This mode is not available for multitenant KalliopePBX.		*SIP PnP: upon starting up the phone sends a SIP SUBSCRIBE message to a multicast address. If SIP PnP is enabled on KalliopePBX, the PBX will reply with a SIP NOTIFY message containing the IP address of the TFTP server to use. This mode is not available for multitenant KalliopePBX.
	*Redirection server: upon starting up the phone attempts to contact the redirection server of the manufacturer. If the MAC address of the phone has been inserted, the phone will be redirected to the specified server to download the configuration file. With this mode, you can use any of the available protocols (based on the parameter configured on the redirection server).		*Redirection server: upon starting up the phone attempts to contact the redirection server of the manufacturer. If the MAC address of the phone has been inserted, the phone will be redirected to the specified server to download the configuration file. With this mode, you can use any of the available protocols (based on the parameter configured on the redirection server).
	*DHCP OPTION 66: if when assigning the IP address the DHCP server sends the DHCP option 66 containing the URL to connect to (including the protocol to use), the phone will use this to download the configuration file.		*DHCP OPTION 66: if when assigning the IP address the DHCP server sends the DHCP option 66 containing the URL to connect to (including the protocol to use), the phone will use this to download the configuration file.
	*Manual: you can manually start the configuration from the phone or the web GUI by inserting the protocol and the IP address (as well as the path if necessary).		*Manual: you can manually start the configuration from the phone or the web GUI by inserting the protocol and the IP address (as well as the path if necessary).

Silvia il 10:42, 14 mag 2018

2018-05-14T10:42:43Z

← Versione meno recente		Versione delle 10:42, 14 mag 2018
Riga 25:		Riga 25:
	Once a file has been generated, it must be transferred to the phone. KalliopePBX provides the following file transfer protocols:		Once a file has been generated, it must be transferred to the phone. KalliopePBX provides the following file transfer protocols:
	*TFTP: files are available directly in the root of the TFTP server for single-tenant KalliopePBX. For multitenant KalliopePBX, you must add the Tenant UUID to the path (e.g. <tenant_uuid>/snom370-0004167898B1.htm).		*TFTP: files are available directly in the root of the TFTP server for single-tenant KalliopePBX. For multitenant KalliopePBX, you must add the Tenant UUID to the path (e.g. <tenant_uuid>/snom370-0004167898B1.htm).
	*HTTP / HTTPS: the files are published on http(s)://<ip_address>/provisioning/ for single-tenant KalliopePBX. For multitenant KalliopePBX, you must add the UUID ~~tenant~~ to the path (e.g. http(s)://<ip_address>/provisioning/<tenant_uuid>/).		*HTTP / HTTPS: the files are published on http(s)://<ip_address>/provisioning/ for single-tenant KalliopePBX. For multitenant KalliopePBX, you must add the Tenant UUID to the path (e.g. http(s)://<ip_address>/provisioning/<tenant_uuid>/).