AdminGuide:Service:Paging/en - Cronologia

Troccoli il 21:12, 25 set 2022

2022-09-25T21:12:36Z

← Versione meno recente		Versione delle 21:12, 25 set 2022
Riga 13:		Riga 13:
	KalliopePBX lets you define an arbitrary number of "paging groups". Each one is independent from the others and is fully configurable when it comes to permissions, choice of destinations, mode of operation, and messages.		KalliopePBX lets you define an arbitrary number of "paging groups". Each one is independent from the others and is fully configurable when it comes to permissions, choice of destinations, mode of operation, and messages.

	An extension can make a call to a code comprised of a paging service prefix (set when enabling the service in the ~~[[AdminGuide:GUI:OperatingMenu:NumberingPlan/en\|~~numbering plan]], by default *53) followed by the paging group number (set in the configuration page for the group). If authentication is necessary, KalliopePBX will play the "Password" audio file and the user will need to input a PIN (the one set in the group configuration or their personal one) followed by #. If authentication is successful the paging group will be activated according to its configuration, detailed in the following section.		An extension can make a call to a code comprised of a paging service prefix (set when enabling the service in the numbering plan, by default *53) followed by the paging group number (set in the configuration page for the group). If authentication is necessary, KalliopePBX will play the "Password" audio file and the user will need to input a PIN (the one set in the group configuration or their personal one) followed by #. If authentication is successful the paging group will be activated according to its configuration, detailed in the following section.

	== Configuration ==		== Configuration ==

Troccoli il 13:30, 20 set 2022

2022-09-20T13:30:53Z

← Versione meno recente		Versione delle 13:30, 20 set 2022
Riga 3:		Riga 3:


	~~<div class="mw-translate-fuzzy">~~
	<div class="noautonum" style="float: right">__TOC__</div>		<div class="noautonum" style="float: right">__TOC__</div>
	== Paging service ==		== Paging service ==
	* Introduced with firmware version 4.3.1		* Introduced with firmware version 4.3.1
	~~</div>~~		[[File:Paging.png\|miniatura]]

	~~<div class="mw-translate-fuzzy">~~
	== Description ==		== Description ==
	The paging service lets a user send a live or prerecorded audio message to multiple destinations simultaneously, with the option of having devices answer automatically when they receive the message. This service is used to make informative or emergency announcements.		The paging service lets a user send a live or prerecorded audio message to multiple destinations simultaneously, with the option of having devices answer automatically when they receive the message. This service is used to make informative or emergency announcements.
	~~</div>~~

	KalliopePBX lets you define an arbitrary number of "paging groups". Each one is independent from the others and is fully configurable when it comes to permissions, choice of destinations, mode of operation, and messages.		KalliopePBX lets you define an arbitrary number of "paging groups". Each one is independent from the others and is fully configurable when it comes to permissions, choice of destinations, mode of operation, and messages.
Riga 18:		Riga 15:
	An extension can make a call to a code comprised of a paging service prefix (set when enabling the service in the [[AdminGuide:GUI:OperatingMenu:NumberingPlan/en\|numbering plan]], by default *53) followed by the paging group number (set in the configuration page for the group). If authentication is necessary, KalliopePBX will play the "Password" audio file and the user will need to input a PIN (the one set in the group configuration or their personal one) followed by #. If authentication is successful the paging group will be activated according to its configuration, detailed in the following section.		An extension can make a call to a code comprised of a paging service prefix (set when enabling the service in the [[AdminGuide:GUI:OperatingMenu:NumberingPlan/en\|numbering plan]], by default *53) followed by the paging group number (set in the configuration page for the group). If authentication is necessary, KalliopePBX will play the "Password" audio file and the user will need to input a PIN (the one set in the group configuration or their personal one) followed by #. If authentication is successful the paging group will be activated according to its configuration, detailed in the following section.

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

	~~<div class="mw-translate-fuzzy">~~
	Paging groups can be created and edited in the PBX -> Paging groups page.		Paging groups can be created and edited in the PBX -> Paging groups page.
	<!--The configurable settings for each group are listed [[AdminGuide:GUI:OperatingMenu:Paging/en\|here]].-->		<!--The configurable settings for each group are listed [[AdminGuide:GUI:OperatingMenu:Paging/en\|here]].-->
	~~</div>~~

	~~Nella seguente tabella sono descritti i parametri di configurazione di ciascun gruppo sono~~:		The following table describes the configuration parameters of each group are:
	{\| 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'''
	\|-		\|-
	\|~~Nome~~ \|\|~~Identificativo assegnato al gruppo di~~ Paging\|\| ~~Alfanumerico~~		\|Name \|\|Identifier assigned to the Paging group\|\| Alphanumeric
	\|-		\|-
	\|~~Numero~~\|\| ~~Selezione del servizio di~~ Paging\|\| ~~Numerico~~		\|Number\|\| Selection of Paging Service\|\| Numeric
	\|-		\|-
	\|~~Identificativo chiamante~~\|\|Display Name ~~per le chiamate verso i terminali di destinazione~~\|\| ~~Alfanumerico~~		\|Caller ID\|\|Display Name for calls to destination terminals\|\| Alphanumeric
	\|-		\|-
	\|'''~~Modalità~~'''\|\|~~Modalità di funzionamento del gruppo di~~ Paging\|\|Live/Unattended		\|'''Modality'''\|\|Mode of operation of the Paging group\|\|Live/Unattended
	\|-		\|-
	\|~~File audio~~\|\| ~~File audio contenente un messaggio preregistrato che viene riprodotto ai terminali di destinazione del gruppo~~. ~~Viene utilizzato~~ in ~~modo differente nel caso di modalità~~ Live o Unattended		\|Audio file\|\| Audio file containing a prerecorded message that is played at the destination terminals of the group. It is used differently in the case of Live or Unattended mode
	\|-		\|-
	\|~~Numero di ripetizioni~~\|\|~~Numero di volte che il messaggio preregistrato deve essere riprodotto prima che il~~ PBX ~~termini automaticamente la chiamata~~(~~configurabile solo nella modalità~~ "Unattended")\|\|~~Numerico~~(0 ~~indica che il messaggio deve essere riprodotto~~ in ~~ciclo continuo~~)		\|Repetitions number\|\|Number of times the prerecorded message must be played before the PBX automatically ends the call (configurable only in "Unattended" mode)\|\|Numeric (0 indicates that the message is to be played in a continuous loop)
	\|-		\|-
	\|~~Metodo di risposta automatica~~\|\|Header ~~da aggiungere alle chiamate effettuate verso i terminali di destinazione al fine di specificare la richiesta di risposta automatica~~\|\|~~Configurazione manuale~~/Call-Info/Header Alert-Info		\|Automatic response method\|\|Header to be added to calls made to destination terminals in order to specify the automatic response request\|\|Manual configuration/Call-Info/Header Alert-Info
	\|-		\|-
	!colspan="3" \|<div style = 'text-align: center> '''Account'''		!colspan="3" \|<div style = 'text-align: center> '''Account'''
	\|-		\|-
	\|~~Interno~~\|\|~~Terminali di destinazione del~~ Paging\|\|		\|Extension\|\|Paging target terminals\|\|
	\|-		\|-
	\|Account\|\|~~Account~~ SIP ~~associato all'interno~~\|\|		\|Account\|\|SIP account associated with the extension\|\|
	\|-		\|-
	!colspan="3" \| <div style = 'text-align: center> '''~~Controllo di accesso~~'''		!colspan="3" \| <div style = 'text-align: center> '''Access control'''
	\|-		\|-
	\|~~Interno~~\|\|~~Interno chiamante~~\|\|"~~Qualsiasi interno~~"/~~Interno~~		\|Extension\|\|Caller extension \|\|"Any extension"/Extension
	\|-		\|-
	\|~~Tipo di~~ PIN\|\| ~~Modalità di autenticazione richiesta~~\|\|~~Nessuno~~/~~Personalizzato~~/ ~~PIN dei servizi proprio di ciascun interno abilitato~~.		\|PIN type\|\| Authentication mode required \|\|None/Custom/ Authentication mode required.
	\|-		\|-
	\|~~Valore del~~ Pin\|\| \|\|~~Alfanumerico~~		\|Pin value\|\| \|\|Alphanumeric
	\|}		\|}

	~~<div class~~=~~"mw-translate-fuzzy">~~		===Modality===
	The operating mode of the paging groups: can be set as either "Live" or "Unattended".		The operating mode of the paging groups: can be set as either '''"Live"''' or '''"Unattended"'''.
	In Live mode the extension making the call to the paging group will remain on call as the sole speaker; at the end of the call, they will hang up, and the calls to all destinations will themselves end.		In Live mode the extension making the call to the paging group will remain on call as the sole speaker; at the end of the call, they will hang up, and the calls to all destinations will themselves end.
	In Unattended mode the PBX hangs up the call made from the extension to the paging group and, after a few moments, proceeds to contact all destinations and play the message set under the "Audio file" item.		In Unattended mode the PBX hangs up the call made from the extension to the paging group and, after a few moments, proceeds to contact all destinations and play the message set under the "Audio file" item.

	The audio file will be used differently depending on whether the mode is set to "Live" or "Unattended":		The audio file will be used differently depending on whether the mode is set to '''"Live"''' or '''"Unattended"''':
	* Live: the message is played before the caller begins communication with the group. This can be used to mark the beginning of an announcement.		* '''Live''': the message is played before the caller begins communication with the group. This can be used to mark the beginning of an announcement.
	* Unattended: the message is played to all destinations in the paging group. Depending on the following setting (Number of repetitions), the message can be played once or multiple times.		* '''Unattended''': the message is played to all destinations in the paging group. Depending on the following setting (Number of repetitions), the message can be played once or multiple times.

	In Unattended mode a second call to the group number will stop message playback regardless of the number of repetitions set.		In Unattended mode a second call to the group number will stop message playback regardless of the number of repetitions set.
	~~</div>~~

	'''N.B.:''': the second call does not need to be made from the extension that activated the service as long as it is enabled to use the service according to the rules described below.		'''N.B.:''': the second call does not need to be made from the extension that activated the service as long as it is enabled to use the service according to the rules described below.

Troccoli il 13:20, 20 set 2022

2022-09-20T13:20:54Z

← Versione meno recente		Versione delle 13:20, 20 set 2022
Riga 3:		Riga 3:


			<div class="mw-translate-fuzzy">
	<div class="noautonum" style="float: right">__TOC__</div>		<div class="noautonum" style="float: right">__TOC__</div>
	== Paging service ==		== Paging service ==
	* Introduced with firmware version 4.3.1		* Introduced with firmware version 4.3.1
			</div>

			<div class="mw-translate-fuzzy">
	== Description ==		== Description ==
	The paging service lets a user send a live or prerecorded audio message to multiple destinations simultaneously, with the option of having devices answer automatically when they receive the message. This service is used to make informative or emergency announcements.		The paging service lets a user send a live or prerecorded audio message to multiple destinations simultaneously, with the option of having devices answer automatically when they receive the message. This service is used to make informative or emergency announcements.
			</div>

	KalliopePBX lets you define an arbitrary number of "paging groups". Each one is independent from the others and is fully configurable when it comes to permissions, choice of destinations, mode of operation, and messages.		KalliopePBX lets you define an arbitrary number of "paging groups". Each one is independent from the others and is fully configurable when it comes to permissions, choice of destinations, mode of operation, and messages.
Riga 14:		Riga 18:
	An extension can make a call to a code comprised of a paging service prefix (set when enabling the service in the [[AdminGuide:GUI:OperatingMenu:NumberingPlan/en\|numbering plan]], by default *53) followed by the paging group number (set in the configuration page for the group). If authentication is necessary, KalliopePBX will play the "Password" audio file and the user will need to input a PIN (the one set in the group configuration or their personal one) followed by #. If authentication is successful the paging group will be activated according to its configuration, detailed in the following section.		An extension can make a call to a code comprised of a paging service prefix (set when enabling the service in the [[AdminGuide:GUI:OperatingMenu:NumberingPlan/en\|numbering plan]], by default *53) followed by the paging group number (set in the configuration page for the group). If authentication is necessary, KalliopePBX will play the "Password" audio file and the user will need to input a PIN (the one set in the group configuration or their personal one) followed by #. If authentication is successful the paging group will be activated according to its configuration, detailed in the following section.

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

	Paging groups can be created and edited in the PBX -> Paging groups page. The configurable settings for each group are listed [[AdminGuide:GUI:OperatingMenu:Paging/en\|here]].		<div class="mw-translate-fuzzy">
			Paging groups can be created and edited in the PBX -> Paging groups page.
			<!--The configurable settings for each group are listed [[AdminGuide:GUI:OperatingMenu:Paging/en\|here]].-->
			</div>

			Nella seguente tabella sono descritti i parametri di configurazione di ciascun gruppo sono:
			{\| class="wikitable"
			! <div style = 'text-align: left> '''Parametro''' !! <div style = 'text-align: left> '''Descrizione''' !! <div style = 'text-align: left> '''Valore'''
			\|-
			\|Nome \|\|Identificativo assegnato al gruppo di Paging\|\| Alfanumerico
			\|-
			\|Numero\|\| Selezione del servizio di Paging\|\| Numerico
			\|-
			\|Identificativo chiamante\|\|Display Name per le chiamate verso i terminali di destinazione\|\| Alfanumerico
			\|-
			\|'''Modalità'''\|\|Modalità di funzionamento del gruppo di Paging\|\|Live/Unattended
			\|-
			\|File audio\|\| File audio contenente un messaggio preregistrato che viene riprodotto ai terminali di destinazione del gruppo. Viene utilizzato in modo differente nel caso di modalità Live o Unattended
			\|-
			\|Numero di ripetizioni\|\|Numero di volte che il messaggio preregistrato deve essere riprodotto prima che il PBX termini automaticamente la chiamata(configurabile solo nella modalità "Unattended")\|\|Numerico(0 indica che il messaggio deve essere riprodotto in ciclo continuo)
			\|-
			\|Metodo di risposta automatica\|\|Header da aggiungere alle chiamate effettuate verso i terminali di destinazione al fine di specificare la richiesta di risposta automatica\|\|Configurazione manuale/Call-Info/Header Alert-Info
			\|-
			!colspan="3" \|<div style = 'text-align: center> '''Account'''
			\|-
			\|Interno\|\|Terminali di destinazione del Paging\|\|
			\|-
			\|Account\|\|Account SIP associato all'interno\|\|
			\|-
			!colspan="3" \| <div style = 'text-align: center> '''Controllo di accesso'''
			\|-
			\|Interno\|\|Interno chiamante\|\|"Qualsiasi interno"/Interno
			\|-
			\|Tipo di PIN\|\| Modalità di autenticazione richiesta\|\|Nessuno/Personalizzato/ PIN dei servizi proprio di ciascun interno abilitato.
			\|-
			\|Valore del Pin\|\| \|\|Alfanumerico
			\|}

			<div class="mw-translate-fuzzy">
	The operating mode of the paging groups: can be set as either "Live" or "Unattended".		The operating mode of the paging groups: can be set as either "Live" or "Unattended".
	In Live mode the extension making the call to the paging group will remain on call as the sole speaker; at the end of the call, they will hang up, and the calls to all destinations will themselves end.		In Live mode the extension making the call to the paging group will remain on call as the sole speaker; at the end of the call, they will hang up, and the calls to all destinations will themselves end.
Riga 27:		Riga 70:

	In Unattended mode a second call to the group number will stop message playback regardless of the number of repetitions set.		In Unattended mode a second call to the group number will stop message playback regardless of the number of repetitions set.
			</div>

	'''N.B.:''': the second call does not need to be made from the extension that activated the service as long as it is enabled to use the service according to the rules described below.		'''N.B.:''': the second call does not need to be made from the extension that activated the service as long as it is enabled to use the service according to the rules described below.

Troccoli il 16:34, 28 gen 2022

2022-01-28T16:34:53Z

← Versione meno recente		Versione delle 16:34, 28 gen 2022
Riga 7:		Riga 7:
	* Introduced with firmware version 4.3.1		* Introduced with firmware version 4.3.1

	=== Description ===		== Description ==
	The paging service lets a user send a live or prerecorded audio message to multiple destinations simultaneously, with the option of having devices answer automatically when they receive the message. This service is used to make informative or emergency announcements.		The paging service lets a user send a live or prerecorded audio message to multiple destinations simultaneously, with the option of having devices answer automatically when they receive the message. This service is used to make informative or emergency announcements.

S.vistoli il 09:27, 9 gen 2020

2020-01-09T09:27:06Z

← Versione meno recente		Versione delle 09:27, 9 gen 2020
Riga 12:		Riga 12:
	KalliopePBX lets you define an arbitrary number of "paging groups". Each one is independent from the others and is fully configurable when it comes to permissions, choice of destinations, mode of operation, and messages.		KalliopePBX lets you define an arbitrary number of "paging groups". Each one is independent from the others and is fully configurable when it comes to permissions, choice of destinations, mode of operation, and messages.

	An extension can make a call to a ~~selection~~ comprised of a paging service prefix (set when enabling the service in the [[AdminGuide:GUI:OperatingMenu:NumberingPlan/en\|numbering plan]], by default *53) followed by the paging group number (set in the configuration page for the group). If authentication is necessary, KalliopePBX will play the "Password" audio file and the user will need to input a PIN (the one set in the group configuration or their personal one) followed by #. If authentication is successful the paging group will be activated according to its configuration, detailed in the following section.		An extension can make a call to a code comprised of a paging service prefix (set when enabling the service in the [[AdminGuide:GUI:OperatingMenu:NumberingPlan/en\|numbering plan]], by default *53) followed by the paging group number (set in the configuration page for the group). If authentication is necessary, KalliopePBX will play the "Password" audio file and the user will need to input a PIN (the one set in the group configuration or their personal one) followed by #. If authentication is successful the paging group will be activated according to its configuration, detailed in the following section.

	== Configuration ==		== Configuration ==

S.vistoli il 09:46, 8 gen 2020

2020-01-08T09:46:40Z

← Versione meno recente		Versione delle 09:46, 8 gen 2020
Riga 3:		Riga 3:


	<div class="~~noutonum~~" style="float: right">__TOC__</div>		<div class="noautonum" style="float: right">__TOC__</div>
	== Paging service ==		== Paging service ==
	* Introduced with firmware version 4.3.1		* Introduced with firmware version 4.3.1

S.vistoli il 11:51, 26 feb 2019

2019-02-26T11:51:18Z

← Versione meno recente		Versione delle 11:51, 26 feb 2019
Riga 28:		Riga 28:
	In Unattended mode a second call to the group number will stop message playback regardless of the number of repetitions set.		In Unattended mode a second call to the group number will stop message playback regardless of the number of repetitions set.

	'''N.B.:''': the second ~~calls~~ does not need to be made from the extension that activated the service as long as it is enabled to use the service according to the rules described below.		'''N.B.:''': the second call does not need to be made from the extension that activated the service as long as it is enabled to use the service according to the rules described below.

	Access control specifies the permissions necessary to use the service. You can specify one or more access rules of the form, specifying which extensions can use the service (one, more than one, or any) and if an activation PIN is required.		Access control specifies the permissions necessary to use the service. You can specify one or more access rules of the form, specifying which extensions can use the service (one, more than one, or any) and if an activation PIN is required.

S.vistoli il 11:50, 26 feb 2019

2019-02-26T11:50:21Z

← Versione meno recente		Versione delle 11:50, 26 feb 2019
Riga 18:		Riga 18:
	Paging groups can be created and edited in the PBX -> Paging groups page. The configurable settings for each group are listed [[AdminGuide:GUI:OperatingMenu:Paging/en\|here]].		Paging groups can be created and edited in the PBX -> Paging groups page. The configurable settings for each group are listed [[AdminGuide:GUI:OperatingMenu:Paging/en\|here]].

	The operating ~~'''~~mode~~'''~~ of the paging groups: can be set as either "Live" or "Unattended".		The operating mode of the paging groups: can be set as either "Live" or "Unattended".
	In Live mode the extension making the call to the paging group will remain on call as the sole speaker; at the end of the call, they will hang up, and the calls to all destinations will themselves end.		In Live mode the extension making the call to the paging group will remain on call as the sole speaker; at the end of the call, they will hang up, and the calls to all destinations will themselves end.
	In Unattended mode the PBX hangs up the call made from the extension to the paging group and, after a few moments, proceeds to contact all destinations and play the message set under the "Audio file" item.		In Unattended mode the PBX hangs up the call made from the extension to the paging group and, after a few moments, proceeds to contact all destinations and play the message set under the "Audio file" item.

S.vistoli il 11:49, 26 feb 2019

2019-02-26T11:49:29Z

← Versione meno recente		Versione delle 11:49, 26 feb 2019
Riga 23:		Riga 23:

	The audio file will be used differently depending on whether the mode is set to "Live" or "Unattended":		The audio file will be used differently depending on whether the mode is set to "Live" or "Unattended":
	** Live: the message is played before the caller begins communication with the group. This can be used to mark the beginning of an announcement.		* Live: the message is played before the caller begins communication with the group. This can be used to mark the beginning of an announcement.
	** Unattended: the message is played to all destinations in the paging group. Depending on the following setting (Number of repetitions), the message can be played once or multiple times.		* Unattended: the message is played to all destinations in the paging group. Depending on the following setting (Number of repetitions), the message can be played once or multiple times.

	In Unattended mode a second call to the group number will stop message playback regardless of the number of repetitions set.		In Unattended mode a second call to the group number will stop message playback regardless of the number of repetitions set.

S.vistoli: Pagina sostituita con 'Paging groups can be created and edited in the PBX -> Paging groups page. The configurable settings for each group are listed here.'

2019-02-26T09:31:29Z

Pagina sostituita con 'Paging groups can be created and edited in the PBX -> Paging groups page. The configurable settings for each group are listed here.'

← Versione meno recente		Versione delle 09:31, 26 feb 2019
Riga 16:		Riga 16:
	== Configuration ==		== Configuration ==

	~~<div class="mw-translate-fuzzy">~~		Paging groups can be created and edited in the PBX -> Paging groups page. The configurable settings for each group are listed [[AdminGuide:GUI:OperatingMenu:Paging/en\|here]].
	Paging groups can be created and edited in the PBX -> Paging groups page. The configurable settings for each group are:

	* '''Name''': an identifier for the paging group.
	* '''Number''': the selection that is appended to the paging service prefix (set in the [[AdminGuide:GUI:OperatingMenu:~~NumberingPlan~~/en\|~~numbering plan~~]]).
	* The '''caller identifier''': this is used as the display name for calls to the destination terminals.
	* The operating '''mode''' of the paging groups: can be set as either "Live" or "Unattended".
	** Live: the extension making the call to the paging group will remain on call as the sole speaker; at the end of the call, they will hang up, and the calls to all destinations will themselves end.
	** Unattended: the PBX hangs up the call made from the extension to the paging group and, after a few moments, proceeds to contact all destinations and play the message set under the "Audio file" item.
	* '''Audio file''': the prerecorded message that is played to the group. It will be used differently depending on whether the mode is set to "Live" or "Unattended":
	** Live: the message is played before the caller begins communication with the group. This can be used to mark the beginning of an announcement.
	** Unattended: the message is played to all destinations in the paging group. Depending on the following setting (Number of repetitions), the message can be played once or multiple times.
	* '''Number of repetitions''': this setting is only configurable when the mode is set to "Unattended" and controls the number of times the prerecorded message is played before the PBX automatically ends the call. Setting this to 0 means the message is played indefinitely. In "Unattended" mode, a second call to the group will stop playback regardless of this setting. N.B.: the second call does not need to be made from the extension that activated the service as long as it is enabled according to the rules detailed below.
	* '''Automatic answer method''': this setting controls which header, if any, is added to calls made to the destination terminals in order to specify the automatic response request. The choice of header depends on the terminals themselves, as different terminals may require different notification modes. There are three options:
	** Manual: the PBX does not specify any header, and the configuration for automatic response must be made statically on the individual terminals.
	** Header Call-Info: the header "Call-Info: <sip:127.0.0.1>;answer-after=0" is added.
	** Header Alert-Info: the header "Alert-Info: <http://127.0.0.1>;info=alert-autoanswer;delay=0" is added.
	* '''Accounts''': list of destination terminals in the paging group. N.B.: destinations are individual SIP accounts, so for extensions linked to multiple accounts you can choose to which of these the call is made.
	* '''Access control''': the permissions necessary to use the service. You can specify one or more access rules of the form:
	** Extension: the calling extension, or "Any extension"
	** Type of PIN: the required authentication. The possible values are:
	*** None: no PIN is required.
	*** Custom: a specific PIN is required. This can be set in the following column (PIN value). This PIN can be the same or different ones for each extension.
	*** Extension service PIN: The service PIN for the extension is required.

	~~An example of '''''ACL''''' is:~~
	~~{\| class="wikitable"~~
	\|-
	~~! Extension !! Type of PIN !! Value of PIN~~
	\|-
	~~\| 101 (Extension 101) \|\| None \|\|~~
	\|-
	~~\| 102 (Extension 102) \|\| Extension service PIN \|\|~~
	\|-
	~~\| Any \|\| Custom \|\| 123123~~
	\|-
	\|}
	In this example, extension 101 can activate the service (or deactivate it if it is set to "Unattended") without needing to input any PIN. Extension 102 can use the service after dialing their service PIN, while all other extensions need to dial 123123.
	~~</div>~~

	The operating '''mode''' of the paging groups: can be set as either "Live" or "Unattended".		The operating '''mode''' of the paging groups: can be set as either "Live" or "Unattended".