AdminGuide:Service:BossSecretaryFilter/en - Cronologia

Troccoli: Pagina sostituita con 'or'

2022-04-20T08:32:27Z

Pagina sostituita con 'or'

← Versione meno recente		Versione delle 08:32, 20 apr 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">~~
	<div class="noutonum" style="float: right">__TOC__</div>		<div class="noutonum" style="float: right">__TOC__</div>
	== Description ==		== Description ==
	This service lets one or more users ('''secretaries''') intercept calls to another extension ('''boss'''). Only the secretaries (and, optionally, other bosses in a customizable group) will be able to directly contact a boss on their extension.		This service lets one or more users ('''secretaries''') intercept calls to another extension ('''boss'''). Only the secretaries (and, optionally, other bosses in a customizable group) will be able to directly contact a boss on their extension.
	The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.		The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~		The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.
	The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	The service can be enabled or disabled on a group level (for all secretaries) or just for one. In practice, a boss enabling the service will usually enable it for all secretaries, while individual secretaries can choose to enter or exit the service. Even if the boss has not enabled the service, a secretary can do so for their own extension.		The service can be enabled or disabled on a group level (for all secretaries) or just for one. In practice, a boss enabling the service will usually enable it for all secretaries, while individual secretaries can choose to enter or exit the service. Even if the boss has not enabled the service, a secretary can do so for their own extension.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	The boss/secretary service can be enabled by dialing the corresponding codes. The service can be enabled on a group level with the activation code (by default '''521''') followed by the extension number of the boss. KalliopePBX will confirm the activation by playing the "Saved" audio file. The service can be enabled for a specific secretary by adding to the global code followed by the extension number of the secretary. KalliopePBX will confirm the activation by playing the "Saved" audio file.		The boss/secretary service can be enabled by dialing the corresponding codes. The service can be enabled on a group level with the activation code (by default '''521''') followed by the extension number of the boss. KalliopePBX will confirm the activation by playing the "Saved" audio file. The service can be enabled for a specific secretary by adding to the global code followed by the extension number of the secretary. KalliopePBX will confirm the activation by playing the "Saved" audio file.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	Similarly, the service can be disabled by dialing the deactivation code (by default '''520''') followed by the extension number of the boss. KalliopePBX will confirm the activation by playing the "Saved" audio file. The service can be disabled for a specific secretary by adding to the global code followed by the extension number of the secretary. KalliopePBX will confirm the activation by playing the "Saved" audio file.		Similarly, the service can be disabled by dialing the deactivation code (by default '''520''') followed by the extension number of the boss. KalliopePBX will confirm the activation by playing the "Saved" audio file. The service can be disabled for a specific secretary by adding to the global code followed by the extension number of the secretary. KalliopePBX will confirm the activation by playing the "Saved" audio file.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	There is also a code to invert the state of the service (by default '''52'''). Similarly to activation/deactivation, the code must be followed by the extension number of the boss to act on a group level, while the state of the service can be inverted for an individual secretary by adding to the global code followed by the extension number of the secretary. In both cases, KalliopePBX will confirm the activation by playing the "Saved" audio file.		There is also a code to invert the state of the service (by default '''52'''). Similarly to activation/deactivation, the code must be followed by the extension number of the boss to act on a group level, while the state of the service can be inverted for an individual secretary by adding to the global code followed by the extension number of the secretary. In both cases, KalliopePBX will confirm the activation by playing the "Saved" audio file.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	These codes can only be used from a phone linked to an extension that belongs to the boss/secretary group.		These codes can only be used from a phone linked to an extension that belongs to the boss/secretary group.

Riga 38:		Riga 23:

	The service can be globally enabled and the service codes can be changed in the PBX -> [[AdminGuide:Service:NumberingPlan/en\|Numbering plan]] page.		The service can be globally enabled and the service codes can be changed in the PBX -> [[AdminGuide:Service:NumberingPlan/en\|Numbering plan]] page.
	~~</div>~~

	~~<div class="mw-translate-fuzzy">~~
	The configuration of the Director-Secretary groups is done in the panel '''Director-Secretary Groups'''.		The configuration of the Director-Secretary groups is done in the panel '''Director-Secretary Groups'''.
	The parameters to be configured for the groups are as follows:		The parameters to be configured for the groups are as follows:
	~~</div>~~

	{\| class="wikitable"		{\| class="wikitable"
Riga 89:		Riga 71:
	\|}		\|}

	~~<div class="mw-translate-fuzzy">~~
	== Interoperability ==		== Interoperability ==
	When enabling/disabling the service from the phone, it can be useful to have a key (with Busy Lamp Field) that lets you verify the state of the service.		When enabling/disabling the service from the phone, it can be useful to have a key (with Busy Lamp Field) that lets you verify the state of the service.
	~~</div>~~

	For monitoring, KalliopePBX sends SIP NOTIFY messages to communicate changes of state. The phone must send a SIP SUBSCRIBE message to request this information.		For monitoring, KalliopePBX sends SIP NOTIFY messages to communicate changes of state. The phone must send a SIP SUBSCRIBE message to request this information.

FuzzyBot: Aggiornamento come da nuova versione della pagina di origine

2022-04-20T08:05:47Z

Aggiornamento come da nuova versione della pagina di origine

← Versione meno recente		Versione delle 08:05, 20 apr 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">
	<div class="noutonum" style="float: right">__TOC__</div>		<div class="noutonum" style="float: right">__TOC__</div>
	== Description ==		== Description ==
	This service lets one or more users ('''secretaries''') intercept calls to another extension ('''boss'''). Only the secretaries (and, optionally, other bosses in a customizable group) will be able to directly contact a boss on their extension.		This service lets one or more users ('''secretaries''') intercept calls to another extension ('''boss'''). Only the secretaries (and, optionally, other bosses in a customizable group) will be able to directly contact a boss on their extension.
	The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.		The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.
			</div>

	The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.		<div class="mw-translate-fuzzy">
			The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.
			</div>

			<div class="mw-translate-fuzzy">
	The service can be enabled or disabled on a group level (for all secretaries) or just for one. In practice, a boss enabling the service will usually enable it for all secretaries, while individual secretaries can choose to enter or exit the service. Even if the boss has not enabled the service, a secretary can do so for their own extension.		The service can be enabled or disabled on a group level (for all secretaries) or just for one. In practice, a boss enabling the service will usually enable it for all secretaries, while individual secretaries can choose to enter or exit the service. Even if the boss has not enabled the service, a secretary can do so for their own extension.
			</div>

			<div class="mw-translate-fuzzy">
	The boss/secretary service can be enabled by dialing the corresponding codes. The service can be enabled on a group level with the activation code (by default '''521''') followed by the extension number of the boss. KalliopePBX will confirm the activation by playing the "Saved" audio file. The service can be enabled for a specific secretary by adding to the global code followed by the extension number of the secretary. KalliopePBX will confirm the activation by playing the "Saved" audio file.		The boss/secretary service can be enabled by dialing the corresponding codes. The service can be enabled on a group level with the activation code (by default '''521''') followed by the extension number of the boss. KalliopePBX will confirm the activation by playing the "Saved" audio file. The service can be enabled for a specific secretary by adding to the global code followed by the extension number of the secretary. KalliopePBX will confirm the activation by playing the "Saved" audio file.
			</div>

			<div class="mw-translate-fuzzy">
	Similarly, the service can be disabled by dialing the deactivation code (by default '''520''') followed by the extension number of the boss. KalliopePBX will confirm the activation by playing the "Saved" audio file. The service can be disabled for a specific secretary by adding to the global code followed by the extension number of the secretary. KalliopePBX will confirm the activation by playing the "Saved" audio file.		Similarly, the service can be disabled by dialing the deactivation code (by default '''520''') followed by the extension number of the boss. KalliopePBX will confirm the activation by playing the "Saved" audio file. The service can be disabled for a specific secretary by adding to the global code followed by the extension number of the secretary. KalliopePBX will confirm the activation by playing the "Saved" audio file.
			</div>

			<div class="mw-translate-fuzzy">
	There is also a code to invert the state of the service (by default '''52'''). Similarly to activation/deactivation, the code must be followed by the extension number of the boss to act on a group level, while the state of the service can be inverted for an individual secretary by adding to the global code followed by the extension number of the secretary. In both cases, KalliopePBX will confirm the activation by playing the "Saved" audio file.		There is also a code to invert the state of the service (by default '''52'''). Similarly to activation/deactivation, the code must be followed by the extension number of the boss to act on a group level, while the state of the service can be inverted for an individual secretary by adding to the global code followed by the extension number of the secretary. In both cases, KalliopePBX will confirm the activation by playing the "Saved" audio file.
			</div>

			<div class="mw-translate-fuzzy">
	These codes can only be used from a phone linked to an extension that belongs to the boss/secretary group.		These codes can only be used from a phone linked to an extension that belongs to the boss/secretary group.

Riga 23:		Riga 38:

	The service can be globally enabled and the service codes can be changed in the PBX -> [[AdminGuide:Service:NumberingPlan/en\|Numbering plan]] page.		The service can be globally enabled and the service codes can be changed in the PBX -> [[AdminGuide:Service:NumberingPlan/en\|Numbering plan]] page.
			</div>

			<div class="mw-translate-fuzzy">
	The configuration of the Director-Secretary groups is done in the panel '''Director-Secretary Groups'''.		The configuration of the Director-Secretary groups is done in the panel '''Director-Secretary Groups'''.
	The parameters to be configured for the groups are as follows:		The parameters to be configured for the groups are as follows:
			</div>

	{\| class="wikitable"		{\| class="wikitable"
Riga 44:		Riga 62:
	\|}		\|}

	~~For monitoring, KalliopePBX sends SIP NOTIFY messages~~ to ~~communicate changes of state~~. The ~~phone must send a SIP SUBSCRIBE message~~ to ~~request~~ this ~~information~~.		===Failovers===
			Here failover actions are defined in case one of the overflow causes occurs for calls diverted to secretaries. The additional failover action "Forward to Director" is provided for this service.

	{\| class="wikitable"		{\| class="wikitable"
Riga 70:		Riga 89:
	\|}		\|}

			<div class="mw-translate-fuzzy">
	== Interoperability ==		== Interoperability ==
	When enabling/disabling the service from the phone, it can be useful to have a key (with Busy Lamp Field) that lets you verify the state of the service.		When enabling/disabling the service from the phone, it can be useful to have a key (with Busy Lamp Field) that lets you verify the state of the service.
			</div>

			For monitoring, KalliopePBX sends SIP NOTIFY messages to communicate changes of state. The phone must send a SIP SUBSCRIBE message to request this information.

			This operation is normally executed by configuring a BLF-type function key.

	The object that needs to be monitored is <code>bs<boss_extension></code> to monitor the state of the service on a group level and <code>bs<boss_extension>*<secretary_extension></code> to monitor the state of the service for a secretary in a specific group. The state of the service on a group level will be active when is is enabled for at least one secretary.		The object that needs to be monitored is <code>bs<boss_extension></code> to monitor the state of the service on a group level and <code>bs<boss_extension>*<secretary_extension></code> to monitor the state of the service for a secretary in a specific group. The state of the service on a group level will be active when is is enabled for at least one secretary.

	Other than monitoring the state the service, it is also possible to invert it by pressing the corresponding function key.		Other than monitoring the state the service, it is also possible to invert it by pressing the corresponding function key.

	The key to control the service on a group level is usually enabled on the boss' phone, while the keys for specific extension are enabled on the secretary's phone.		The key to control the service on a group level is usually enabled on the boss' phone, while the keys for specific extension are enabled on the secretary's phone.
Riga 81:		Riga 106:
	The keys can be configured for all members of the group to accommodate specific requirements (e.g. the boss might wish to set the state of specific secretaries or let the secretaries set the state on a group level).		The keys can be configured for all members of the group to accommodate specific requirements (e.g. the boss might wish to set the state of specific secretaries or let the secretaries set the state on a group level).

			=== Examples ===

	==== On SNOM ====		==== On SNOM ====
	[[File:~~Snom_boss_secretary~~.png\|miniatura]]		[[File:Snom fork2mobile.png\|miniatura]]
	* Through the web GUI, you can configure function keys with:		* Through the web GUI, you can configure function keys with:
	<code>		<code>
	Account: ''select the account from the drop-down (if only one account is configured on the phone, it will be the first in the list)''		Account: ''select the account from the drop-down (if only one account is configured on the phone, it will be the first in the list)''

	Type: BLF		Type: BLF

	value: bs<boss_extension> / bs<boss_extension>*<secretary_extension>		value: bs<boss_extension> / bs<boss_extension>*<secretary_extension>

	</code>		</code>

	* Or you can directly edit the configuration file or the template:		* Or you can directly edit the configuration file or the template:
Riga 127:		Riga 154:
	memorykey.%%id%%.line=%%line_id%%>		memorykey.%%id%%.line=%%line_id%%>

	memorykey.%%id%%.value=bs<boss_extension> / bs<boss_extension>*<secretary_extension>		memorykey.%%id%%.value=bs<boss_extension> / bs<boss_extension>*<secretary_extension>

	memorykey.%%id%%.type=16		memorykey.%%id%%.type=16

	</code>		</code>

	where ''%%id%%'' is the ID of the key to configure		where ''%%id%%'' is the ID of the key to configure
Riga 145:		Riga 172:

	memorykey.1.type = 16		memorykey.1.type = 16

	~~memorykey.1.pickup_value = %NULL%~~

	~~Return to [[AdminGuide:Service/en\|AdminGuide:Service]]~~

	memorykey.1.pickup_value = %NULL%		memorykey.1.pickup_value = %NULL%

Troccoli il 08:00, 20 apr 2022

2022-04-20T08:00:50Z

← Versione meno recente		Versione delle 08:00, 20 apr 2022
Riga 29:		Riga 29:
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! <div style = 'text-align: left> '''~~Parametro~~''' !! <div style = 'text-align: left> '''~~Descrizione~~''' !! <div style = 'text-align: left> '''~~Valore~~'''		! <div style = 'text-align: left> '''Parameter''' !! <div style = 'text-align: left> '''Description''' !! <div style = 'text-align: left> '''Value'''
	\|-		\|-
	\|colspan="3"\| <div style = 'text-align: center; color: transparent> -		\|colspan="3"\| <div style = 'text-align: center; color: transparent> -
	\|-		\|-
	\| ~~Abilitato~~ \|\| ~~Consente di disabilitare un gruppo direttore~~/~~segretaria senza perderne la configurazione~~ \|\| Si / No		\| Enabled \|\| Lets you disable a boss/secretary filter without losing its configuration. \|\| Yes / No
	\|-		\|-
	\| ~~Nome~~\|\| ~~Identificativo del gruppo direttore~~ / ~~segretaria~~ \|\| ~~Alfa-numerico~~		\| Name \|\| Boss/secretary group identifier. \|\| Alphanumeric
	\|-		\|-
	\| ~~Permetti chiamate da altri direttori~~\|\| ~~Se questa opzione è abilitata gli interni dichiarati come direttori~~ in ~~altri gruppi direttore-segretaria possono contattare direttamente il direttore evitando il filtro delle segretarie~~ \|\| Si / No		\| Allow calls from other bosses \|\| If this option is enabled, extensions labeled as bosses in other groups will be able to call the boss directly without passing through the filter. \|\| Yes / No
	\|-		\|-
	\| ~~Seleziona il direttore~~\|\| ~~Interno le cui chiamate verranno deviate sulle segretarie~~ \|\| ~~Interno~~		\| Select boss \|\| The extension whose calls will be intercepted by the secretaries. \|\| Extension
	\|-		\|-
	\| ~~Aggiungi segretaria~~\|\| ~~Consente di definire la lista degli interni su cui verranno deviate le chiamate del direttore~~.\|\| ~~Interno~~		\| Add secretary \|\| The list of extensions that will intercept the calls to the boss. \|\| Extension
	\|}		\|}

Riga 47:		Riga 47:

	{\| class="wikitable"		{\| class="wikitable"
	!colspan="3"\| <div style = 'text-align: left> '''~~Trabocchi~~'''		!colspan="3"\| <div style = 'text-align: left> '''Failovers'''
	\|-		\|-
	! <div style = 'text-align: left> '''~~Parametro~~''' !! <div style = 'text-align: left> '''~~Descrizione~~''' !! <div style = 'text-align: left> '''~~Valore~~'''		! <div style = 'text-align: left> '''Parameter''' !! <div style = 'text-align: left> '''Description''' !! <div style = 'text-align: left> '''Value'''
	\|-		\|-
	\| ~~Interno~~		\| Extension
	\|colspan="2"\| ~~Azione di trabocco su chiamate provenienti da un interno~~ (~~anche remoto~~)		\|colspan="2"\| Failover action on calls from extensions (including remote extensions).
	\|-		\|-
	\| ~~Esterno~~		\| External
	\|colspan="2"\| ~~Azione di trabocco sulle chiamate provenienti dall'esterno~~		\|colspan="2"\| Failover action on calls from external numbers.
	\|-		\|-
	\| ~~Trasferimento~~		\| Transfer
	\|colspan="2"\| ~~Azione di trabocco sui trasferimenti di chiamata~~		\|colspan="2"\| Failover action on call transfers.
	\|-		\|-
	\| Timeout (sec.) \|\| ~~Tempo alla scadenza del quale viene eseguita l’azione di trabocco configurata~~ in ~~caso di nessuna risposta (nessuna segretaria risponde entro il timeout~~) \|\| ~~Numerico~~		\| Timeout (sec.) \|\| Interval of time at the end of which the configured failover action will be executed if the call is not answered (no secretary picks up the call in time). \|\| Numeric
	\|-		\|-
	\| ~~Nessuna risposta~~ \|\| ~~La chiamata è considerata senza risposta alla scadenza del timeout~~ \|\|rowspan="3"\| ~~Inoltra al direttore~~ / ~~Riaggancia~~ / ~~Selezione personalizzata~~ /		\| No answer \|\| The call is considered unanswered after the specified time has passed. \|\|rowspan="3"\| Forward to the boss / Hang up / Custom selection / Ask for selection / External number / Extension / Group / Queue / Checktime / IVR / Voicemail / MeetMe room
	~~Chiedi selezione~~ / ~~Numero esterno~~ / ~~Interno~~ / ~~Gruppo~~ / ~~Coda~~ / ~~Controllo orario~~ / IVR / ~~Casella vocale~~ / ~~Stanza~~ MeetMe
	\|-		\|-
	\| ~~Occupato~~ \|\| ~~Tutti gli interni delle segretarie risultano occupati~~. ~~L’interno è considerato occupato se è stato raggiunto il~~ Busy Level ~~impostato per l’interno oppure se il terminale invia il SIP Response~~ 486 Busy Here		\| Busy \|\| All secretary extensions are busy. The extension is considered busy if the configured Busy Level has been reached, or if the terminal sends a 486 Busy Here SIP Response.
	\|-		\|-
	\| ~~Non Disponibile~~ \|\| ~~Tutti gli interni delle segretarie risultano non disponibili~~. ~~L’interno è considerato non disponibile se il terminale non è registrato o non è raggiungibile~~ a ~~livello IP oppure se il terminale invia il SIP Response~~ 480 Temporarily Unavailable		\| Not available \|\| All secretary extensions are unavailable. The extension is considered busy if the terminal is not registered or not reachable at an IP level, or if the terminal sends a 480 Temporarily Unavailable SIP Response.
	\|-		\|-
	\|}		\|}

	~~This operation is normally executed by configuring~~ a ~~BLF-type function~~ key.		== Interoperability ==
			When enabling/disabling the service from the phone, it can be useful to have a key (with Busy Lamp Field) that lets you verify the state of the service.

	The object that needs to be monitored is <code>bs<boss_extension></code> to monitor the state of the service on a group level and <code>bs<boss_extension>*<secretary_extension></code> to monitor the state of the service for a secretary in a specific group. The state of the service on a group level will be active when is is enabled for at least one secretary.		The object that needs to be monitored is <code>bs<boss_extension></code> to monitor the state of the service on a group level and <code>bs<boss_extension>*<secretary_extension></code> to monitor the state of the service for a secretary in a specific group. The state of the service on a group level will be active when is is enabled for at least one secretary.

Troccoli il 07:57, 20 apr 2022

2022-04-20T07:57:19Z

← Versione meno recente		Versione delle 07:57, 20 apr 2022
Riga 6:		Riga 6:
	== Description ==		== Description ==
	This service lets one or more users ('''secretaries''') intercept calls to another extension ('''boss'''). Only the secretaries (and, optionally, other bosses in a customizable group) will be able to directly contact a boss on their extension.		This service lets one or more users ('''secretaries''') intercept calls to another extension ('''boss'''). Only the secretaries (and, optionally, other bosses in a customizable group) will be able to directly contact a boss on their extension.
			The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.

	The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.		The secretaries have the task of answering calls, checking whether the boss is available, and, if necessary, forwarding them to the boss.
Riga 21:		Riga 22:
	== Configuration ==		== Configuration ==

	The service can be globally enabled and the service codes can be changed in the PBX -> [[AdminGuide:~~GUI:OperatingMenu~~:NumberingPlan/en\|Numbering plan]] page.		The service can be globally enabled and the service codes can be changed in the PBX -> [[AdminGuide:Service:NumberingPlan/en\|Numbering plan]] page.

	~~Boss/secretary~~ groups ~~can~~ be configured in the ~~PBX applications -> [[AdminGuide:GUI~~:~~OperatingMenu:BossSecretaryFilter\|Boss/secretary filter]] page.~~		The configuration of the Director-Secretary groups is done in the panel '''Director-Secretary Groups'''.
			The parameters to be configured for the groups are as follows:

	== ~~Interoperability~~ ==		{\| class="wikitable"
	~~When enabling~~/~~disabling the service from the phone, it can be useful to have a key (with Busy Lamp Field) that lets you verify the state of the service~~.		\|-
			! <div style = 'text-align: left> '''Parametro''' !! <div style = 'text-align: left> '''Descrizione''' !! <div style = 'text-align: left> '''Valore'''
			\|-
			\|colspan="3"\| <div style = 'text-align: center; color: transparent> -
			\|-
			\| Abilitato \|\| Consente di disabilitare un gruppo direttore/segretaria senza perderne la configurazione \|\| Si / No
			\|-
			\| Nome\|\| Identificativo del gruppo direttore / segretaria \|\| Alfa-numerico
			\|-
			\| Permetti chiamate da altri direttori\|\| Se questa opzione è abilitata gli interni dichiarati come direttori in altri gruppi direttore-segretaria possono contattare direttamente il direttore evitando il filtro delle segretarie \|\| Si / No
			\|-
			\| Seleziona il direttore\|\| Interno le cui chiamate verranno deviate sulle segretarie \|\| Interno
			\|-
			\| Aggiungi segretaria\|\| Consente di definire la lista degli interni su cui verranno deviate le chiamate del direttore.\|\| Interno
			\|}

	For monitoring, KalliopePBX sends SIP NOTIFY messages to communicate changes of state. The phone must send a SIP SUBSCRIBE message to request this information.		For monitoring, KalliopePBX sends SIP NOTIFY messages to communicate changes of state. The phone must send a SIP SUBSCRIBE message to request this information.

	~~This operation is normally executed by configuring~~ a ~~BLF~~-~~type function key.~~		{\| class="wikitable"
			!colspan="3"\| <div style = 'text-align: left> '''Trabocchi'''
			\|-
			! <div style = 'text-align: left> '''Parametro''' !! <div style = 'text-align: left> '''Descrizione''' !! <div style = 'text-align: left> '''Valore'''
			\|-
			\| Interno
			\|colspan="2"\| Azione di trabocco su chiamate provenienti da un interno (anche remoto)
			\|-
			\| Esterno
			\|colspan="2"\| Azione di trabocco sulle chiamate provenienti dall'esterno
			\|-
			\| Trasferimento
			\|colspan="2"\| Azione di trabocco sui trasferimenti di chiamata
			\|-
			\| Timeout (sec.) \|\| Tempo alla scadenza del quale viene eseguita l’azione di trabocco configurata in caso di nessuna risposta (nessuna segretaria risponde entro il timeout) \|\| Numerico
			\|-
			\| Nessuna risposta \|\| La chiamata è considerata senza risposta alla scadenza del timeout \|\|rowspan="3"\| Inoltra al direttore / Riaggancia / Selezione personalizzata /
			Chiedi selezione / Numero esterno / Interno / Gruppo / Coda / Controllo orario / IVR / Casella vocale / Stanza MeetMe
			\|-
			\| Occupato \|\| Tutti gli interni delle segretarie risultano occupati. L’interno è considerato occupato se è stato raggiunto il Busy Level impostato per l’interno oppure se il terminale invia il SIP Response 486 Busy Here
			\|-
			\| Non Disponibile \|\| Tutti gli interni delle segretarie risultano non disponibili. L’interno è considerato non disponibile se il terminale non è registrato o non è raggiungibile a livello IP oppure se il terminale invia il SIP Response 480 Temporarily Unavailable
			\|-
			\|}

	~~The object that needs to be monitored~~ is ~~<code>bs<boss_extension></code> to monitor the state of the service on~~ a group level and <code>bs<boss_extension>*<secretary_extension></code> to monitor the state of the service for a secretary in a specific group. The state of the service on a group level will be active when is is enabled for at least one secretary.		This operation is normally executed by configuring a BLF-type function key.

	Other than monitoring the state the service, it is also possible to invert it by pressing the corresponding function key.		The object that needs to be monitored is <code>bs<boss_extension></code> to monitor the state of the service on a group level and <code>bs<boss_extension>*<secretary_extension></code> to monitor the state of the service for a secretary in a specific group. The state of the service on a group level will be active when is is enabled for at least one secretary.

			Other than monitoring the state the service, it is also possible to invert it by pressing the corresponding function key.

	The key to control the service on a group level is usually enabled on the boss' phone, while the keys for specific extension are enabled on the secretary's phone.		The key to control the service on a group level is usually enabled on the boss' phone, while the keys for specific extension are enabled on the secretary's phone.
Riga 46:		Riga 87:
	Account: ''select the account from the drop-down (if only one account is configured on the phone, it will be the first in the list)''		Account: ''select the account from the drop-down (if only one account is configured on the phone, it will be the first in the list)''

	Type: BLF		Type: BLF

	value: bs<boss_extension> / bs<boss_extension>*<secretary_extension>		value: bs<boss_extension> / bs<boss_extension>*<secretary_extension>

	</code>		</code>

	* Or you can directly edit the configuration file or the template:		* Or you can directly edit the configuration file or the template:
Riga 86:		Riga 127:
	memorykey.%%id%%.line=%%line_id%%>		memorykey.%%id%%.line=%%line_id%%>

	memorykey.%%id%%.value=bs<boss_extension> / bs<boss_extension>*<secretary_extension>		memorykey.%%id%%.value=bs<boss_extension> / bs<boss_extension>*<secretary_extension>

	memorykey.%%id%%.type=16		memorykey.%%id%%.type=16

	</code>		</code>

	where ''%%id%%'' is the ID of the key to configure		where ''%%id%%'' is the ID of the key to configure
Riga 104:		Riga 145:

	memorykey.1.type = 16		memorykey.1.type = 16

			memorykey.1.pickup_value = %NULL%

			Return to [[AdminGuide:Service/en\|AdminGuide:Service]]

	memorykey.1.pickup_value = %NULL%		memorykey.1.pickup_value = %NULL%

Silvia: Creata pagina con "Return to AdminGuide:Service"

2018-04-17T09:14:44Z

Creata pagina con "Return to AdminGuide:Service"

← Versione meno recente		Versione delle 09:14, 17 apr 2018
Riga 1:		Riga 1:
	<languages />		<languages />
			Return to [[AdminGuide:Service/en\|AdminGuide:Service]]


	<div class="noutonum" style="float: right">__TOC__</div>		<div class="noutonum" style="float: right">__TOC__</div>
	== Description ==		== Description ==

Silvia: Creata pagina con "Example:"

2018-02-26T11:25:17Z

Creata pagina con "Example:"

← Versione meno recente		Versione delle 11:25, 26 feb 2018
Riga 93:		Riga 93:
	and ''%%line_id%%'' is the ID of the corresponding account (1 if the account is the only one on the phone).		and ''%%line_id%%'' is the ID of the corresponding account (1 if the account is the only one on the phone).

	~~Esempio~~:		Example:

	<code>		<code>

Silvia: Creata pagina con "and ''%%line_id%%'' is the ID of the corresponding account (1 if the account is the only one on the phone)."

2018-02-26T11:25:04Z

Creata pagina con "and ''%%line_id%%'' is the ID of the corresponding account (1 if the account is the only one on the phone)."

← Versione meno recente		Versione delle 11:25, 26 feb 2018
Riga 91:		Riga 91:
	where ''%%id%%'' is the ID of the key to configure		where ''%%id%%'' is the ID of the key to configure

	e ''%%line_id%%'' ~~è l’identificativo dell’account associato il valore è~~ 1 ~~se sul telefono è presente un solo~~ account)		and ''%%line_id%%'' is the ID of the corresponding account (1 if the account is the only one on the phone).

	Esempio:		Esempio:

Silvia: Creata pagina con "where ''%%id%%'' is the ID of the key to configure"

2018-02-26T11:24:51Z

Creata pagina con "where ''%%id%%'' is the ID of the key to configure"

← Versione meno recente		Versione delle 11:24, 26 feb 2018
Riga 89:		Riga 89:
	</code>		</code>

	~~Dove~~ ''%%id%%'' ~~è l’identificativo del tasto da configurare~~		where ''%%id%%'' is the ID of the key to configure

	e ''%%line_id%%'' è l’identificativo dell’account associato il valore è 1 se sul telefono è presente un solo account)		e ''%%line_id%%'' è l’identificativo dell’account associato il valore è 1 se sul telefono è presente un solo account)

Silvia: Creata pagina con "memorykey.%%id%%.value=bs / bs*"

2018-02-26T11:24:28Z

Creata pagina con "memorykey.%%id%%.value=bs<boss_extension> / bs<boss_extension>*<secretary_extension>"

← Versione meno recente		Versione delle 11:24, 26 feb 2018
Riga 83:		Riga 83:
	memorykey.%%id%%.line=%%line_id%%>		memorykey.%%id%%.line=%%line_id%%>

	memorykey.%%id%%.value=bs<~~interno_direttore~~> / bs<~~interno_direttore~~>*<~~interno_segretaria~~>		memorykey.%%id%%.value=bs<boss_extension> / bs<boss_extension>*<secretary_extension>

	memorykey.%%id%%.type=16		memorykey.%%id%%.type=16

Silvia: Creata pagina con "* Or you can directly edit the configuration file or the template:"

2018-02-26T11:24:08Z

Creata pagina con "* Or you can directly edit the configuration file or the template:"

← Versione meno recente		Versione delle 11:24, 26 feb 2018
Riga 78:		Riga 78:
	</code>		</code>

	* ~~Oppure modificando direttamente il~~ file ~~di configurazione o il~~ template ~~in questo modo~~:		* Or you can directly edit the configuration file or the template:

	<code>		<code>