AdminGuide:BasicConcepts:Outbound lines/en - Cronologia

Troccoli il 15:31, 19 set 2022

2022-09-19T15:31:51Z

← Versione meno recente		Versione delle 15:31, 19 set 2022
Riga 17:		Riga 17:
	The '''outbound identity''' is the extension number used to derive the CLID for outbound calls (according to the corresponding calling number manipulation table). The '''Outbound Identity''' can be explicitly set for failover actions, while it is automatically assigned for call smade from a SIP account or for transferred/forwarded calls:		The '''outbound identity''' is the extension number used to derive the CLID for outbound calls (according to the corresponding calling number manipulation table). The '''Outbound Identity''' can be explicitly set for failover actions, while it is automatically assigned for call smade from a SIP account or for transferred/forwarded calls:

	; Calls made by a SIP account		* ''' Calls made by a SIP account'''
	: The outbound identity is set to the extension linked to the SIP Account.		: The '''outbound identity''' is set to the extension linked to the SIP Account.
	; Calls forwarded by a device (telephone-driven call forwarding)		* '''Calls forwarded by a device''' (telephone-driven call forwarding)
	: Same as above.		: Same as above.
	; Calls forwarded using the KalliopePBX (unconditional) call forwarding service		* '''Calls forwarded using the KalliopePBX (unconditional) call forwarding service'''
	: The outbound identity is set to the forwarding extension number.		: The outbound identity is set to the forwarding extension number.
	; Transferred calls (using KalliopePBX star-codes or telephone functions)		* '''Transferred calls''' (using KalliopePBX star-codes or telephone functions)
	: The outbound identity is set equal to the transferring extension number.		: The outbound identity is set equal to the transferring extension number.

Troccoli il 12:23, 20 apr 2022

2022-04-20T12:23:20Z

← Versione meno recente		Versione delle 12:23, 20 apr 2022
Riga 41:		Riga 41:

	It is also possible to configure multiple gateways and VoIP terminations or trunks simultaneously. Through this page you can:		It is also possible to configure multiple gateways and VoIP terminations or trunks simultaneously. Through this page you can:
	* [[AdminGuide:BasicConcepts:~~Outbound lines~~:~~VoIP Domain~~/en\|add a VoIP domain or edit an existing one]];		* [[AdminGuide:BasicConcepts:Outbound_lines:Dominio_VoIP/en\|add a VoIP domain or edit an existing one]];
	* [[AdminGuide:BasicConcepts:Outbound_lines:Gateway/en\|add a physical gateway or edit an existing one]];		* [[AdminGuide:BasicConcepts:Outbound_lines:Gateway/en\|add a physical gateway or edit an existing one]];
	* [[AdminGuide:BasicConcepts:~~Outbound lines~~:~~VoIP Termination~~/en\|add a VoIP termination or edit an existing one]];		* [[AdminGuide:BasicConcepts:Outbound_lines:Terminazione_VoIP/en\|add a VoIP termination or edit an existing one]];
	* [[AdminGuide:BasicConcepts:~~Outbound lines~~:~~VoIP Trunk~~/en\|add a VoIP trunk or edit an existing one]].		* [[AdminGuide:BasicConcepts:Outbound_lines:Trunk_VoIP/en\|add a VoIP trunk or edit an existing one]].

	The difference between '''VoIP terminations''' and '''trunks''' is due to the fact that with the former every registration/authentication account corresponds to a single phone number, while with the latter it is possible to use a range of numbers with the same authentication credentials, which usually share a common root.		The difference between '''VoIP terminations''' and '''trunks''' is due to the fact that with the former every registration/authentication account corresponds to a single phone number, while with the latter it is possible to use a range of numbers with the same authentication credentials, which usually share a common root.

Troccoli: Creata pagina con "It is also possible to configure multiple gateways and VoIP terminations or trunks simultaneously. Through this page you can: * AdminGuide:Service:Dominio_VoIP/en|add a VoIP..."

2022-04-20T10:10:10Z

Creata pagina con "It is also possible to configure multiple gateways and VoIP terminations or trunks simultaneously. Through this page you can: * AdminGuide:Service:Dominio_VoIP/en|add a VoIP..."

← Versione meno recente		Versione delle 10:10, 20 apr 2022
Riga 41:		Riga 41:

	It is also possible to configure multiple gateways and VoIP terminations or trunks simultaneously. Through this page you can:		It is also possible to configure multiple gateways and VoIP terminations or trunks simultaneously. Through this page you can:
	* [[AdminGuide:BasicConcepts:Outbound lines:VoIP Domain\|add a VoIP domain or edit an existing one]];		* [[AdminGuide:BasicConcepts:Outbound lines:VoIP Domain/en\|add a VoIP domain or edit an existing one]];
	* [[AdminGuide:BasicConcepts:~~Outbound lines~~:Gateway\|add a physical gateway or edit an existing one]];		* [[AdminGuide:BasicConcepts:Outbound_lines:Gateway/en\|add a physical gateway or edit an existing one]];
	* [[AdminGuide:BasicConcepts:Outbound lines:VoIP Termination\|add a VoIP termination or edit an existing one]];		* [[AdminGuide:BasicConcepts:Outbound lines:VoIP Termination/en\|add a VoIP termination or edit an existing one]];
	* [[AdminGuide:BasicConcepts:Outbound lines:VoIP Trunk\|add a VoIP trunk or edit an existing one]].		* [[AdminGuide:BasicConcepts:Outbound lines:VoIP Trunk/en\|add a VoIP trunk or edit an existing one]].

	The difference between '''VoIP terminations''' and '''trunks''' is due to the fact that with the former every registration/authentication account corresponds to a single phone number, while with the latter it is possible to use a range of numbers with the same authentication credentials, which usually share a common root.		The difference between '''VoIP terminations''' and '''trunks''' is due to the fact that with the former every registration/authentication account corresponds to a single phone number, while with the latter it is possible to use a range of numbers with the same authentication credentials, which usually share a common root.

Troccoli: Creata pagina con "The difference between '''VoIP terminations''' and '''trunks''' is due to the fact that with the former every registration/authentication account corresponds to a single phone..."

2022-04-20T09:36:53Z

Creata pagina con "The difference between '''VoIP terminations''' and '''trunks''' is due to the fact that with the former every registration/authentication account corresponds to a single phone..."

← Versione meno recente		Versione delle 09:36, 20 apr 2022
Riga 41:		Riga 41:

	It is also possible to configure multiple gateways and VoIP terminations or trunks simultaneously. Through this page you can:		It is also possible to configure multiple gateways and VoIP terminations or trunks simultaneously. Through this page you can:
	* [[AdminGuide:~~Service~~:~~Dominio_VoIP/en~~\|add a VoIP domain or edit an existing one]];		* [[AdminGuide:BasicConcepts:Outbound lines:VoIP Domain\|add a VoIP domain or edit an existing one]];
	* [[AdminGuide:~~Service~~:Gateway~~/en~~\|add a physical gateway or edit an existing one]];		* [[AdminGuide:BasicConcepts:Outbound lines:Gateway\|add a physical gateway or edit an existing one]];
	* [[AdminGuide:~~Service~~:~~Terminazione_VoIP/en~~\|add a VoIP termination or edit an existing one]];		* [[AdminGuide:BasicConcepts:Outbound lines:VoIP Termination\|add a VoIP termination or edit an existing one]];
	* [[AdminGuide:~~Service~~:~~Trunk_VoIP/en~~\|add a VoIP trunk or edit an existing one]].		* [[AdminGuide:BasicConcepts:Outbound lines:VoIP Trunk\|add a VoIP trunk or edit an existing one]].

	The difference between '''VoIP terminations''' and '''trunks''' is due to the fact that with the former every registration/authentication account corresponds to a single phone number, while with the latter it is possible to use a range of numbers with the same authentication credentials, which usually share a common root.		The difference between '''VoIP terminations''' and '''trunks''' is due to the fact that with the former every registration/authentication account corresponds to a single phone number, while with the latter it is possible to use a range of numbers with the same authentication credentials, which usually share a common root.

Troccoli: Creata pagina con "The following table shows the columns in the list of outbound lines. {| class="wikitable" |- ! Column !! Description !! Value |- | '''Enabled''' || Shows whether the outbound..."

2022-04-20T09:14:08Z

Creata pagina con "The following table shows the columns in the list of outbound lines. {| class="wikitable" |- ! Column !! Description !! Value |- | '''Enabled''' || Shows whether the outbound..."

← Versione meno recente		Versione delle 09:14, 20 apr 2022
Riga 33:		Riga 33:
	Except when explicitly set by a failover action, the choice of outbound routing class is automatically derived from the '''outbound identity'''.		Except when explicitly set by a failover action, the choice of outbound routing class is automatically derived from the '''outbound identity'''.

	~~<div class~~=~~"mw-translate-fuzzy">~~		== Configuration ==
	~~; Calls made by a SIP account~~		Lines can be configured in the VoIP Gateways and Domains panel.
	~~: The outbound identity is set to the extension linked to~~ the ~~SIP Account~~.		[[File:Linee in uscita.png\|miniatura]]
	~~; Calls forwarded by a device (telephone-driven call forwarding)~~		The "Gateways and VoIP Domains" screen collects the configuration of all input/output lines from the PBX.
	: ~~Same as above~~.
	~~; Calls forwarded using the KalliopePBX (unconditional) call forwarding service~~
	: The ~~outbound identity is set to~~ the ~~forwarding extension number.~~
	~~; Transferred calls (using KalliopePBX star-codes or telephone functions)~~
	~~: The outbound identity is set equal to~~ the ~~transferring extension number~~.
	~~</div>~~

	KalliopePBX ~~supporta sia gateway fisici~~ (~~che interconnettono la rete telefonica interna a linee analogiche~~, ~~ISDN o~~ GSM) ~~che terminazioni e trunk~~ VoIP, ~~in entrambi i casi sfruttando il protocollo~~ standard SIP.		KalliopePBX supports both physical gateways (which interconnect the internal telephone network to analog, ASDN, or GSM lines) and VoIP terminations and trunks, using the standard SIP protocol.

	~~Possono essere configurati più gateway e più terminazioni o trunk~~ VoIP ~~contemporaneamente~~. ~~Tramite questa schermata è possibile effettuare le seguenti operazioni~~:		It is also possible to configure multiple gateways and VoIP terminations or trunks simultaneously. Through this page you can:
	* [[AdminGuide:~~BasicConcepts:Outbound lines~~:Dominio_VoIP\|~~Aggiungere un dominio~~ VoIP ~~(o modificarne uno esistente)~~]]		* [[AdminGuide:Service:Dominio_VoIP/en\|add a VoIP domain or edit an existing one]];
	* [[AdminGuide:~~BasicConcepts:Outbound lines~~:Gateway\| ~~Aggiungere un~~ gateway ~~fisico (o modificarne uno esistente)~~]]		* [[AdminGuide:Service:Gateway/en\|add a physical gateway or edit an existing one]];
	* [[AdminGuide:~~BasicConcepts:Outbound lines~~:Terminazione_VoIP\|~~Aggiungere una terminazione~~ VoIP ~~(o modificarne uno esistente)~~]]		* [[AdminGuide:Service:Terminazione_VoIP/en\|add a VoIP termination or edit an existing one]];
	* [[AdminGuide:~~BasicConcepts~~:~~Outbound lines:Trunk~~ VoIP~~\|Aggiungere un~~ trunk ~~VoIP (o modificarne uno esistente)~~]]		* [[AdminGuide:Service:Trunk_VoIP/en\|add a VoIP trunk or edit an existing one]].

	~~La differenza tra~~ '''~~terminazione~~ VoIP''' e '''~~trunk~~''' ~~è data dal fatto che nel primo caso, ad ogni~~ account ~~di registrazione/autenticazione corrisponde un unico numero telefonico~~, ~~mentre nel secondo caso si ha che~~ a ~~fronte di una unica credenziale di autenticazione~~, ~~è possibile utilizzare un arco di numeri che solitamente condividono un radicale comune~~.		The difference between '''VoIP terminations''' and '''trunks''' is due to the fact that with the former every registration/authentication account corresponds to a single phone number, while with the latter it is possible to use a range of numbers with the same authentication credentials, which usually share a common root.

	'''~~NOTA~~:''' ~~Per poter creare una terminazione~~ VoIP ~~o un~~ trunk ~~è necessario prima creare un '''dominio~~ VoIP~~''' a cui associarlo~~.		'''N.B.:''' to create a VoIP termination or trunk, it is necessary to first create a VoIP domain to link it to.

	~~Nella tabella seguente sono descritte le colonne della lista delle linee di uscita~~.		The following table shows the columns in the list of outbound lines.
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! ~~Colonna~~ !! ~~Descrizione~~ !! ~~Valore~~		! Column !! Description !! Value
	\|-		\|-
	\| '''~~Abilitato~~''' \|\| ~~Indica se la linea di uscita risulta abilitata o no~~ \|\| [[File:Abilitato.png\|sinistra]] ~~Abilitato~~ <br><br> [[File:Non_abilitato.png\|sinistra]] ~~Non abilitato~~		\| '''Enabled''' \|\| Shows whether the outbound line is enabled or disabled. \|\| [[File:Abilitato.png\|sinistra]] Enabled <br><br> [[File:Non_abilitato.png\|sinistra]] Disabled
	\|-		\|-
	\| '''~~Nome~~''' \|\| ~~Il nome simbolico assegnato alla linea~~ \|\| -		\| '''Name''' \|\| The name assigned to the line. \|\| -
	\|-		\|-
	\| '''~~Identificativo~~''' \|\| ~~Identificativo univoco assegnato alla linea~~. ~~Nel caso di trunk o terminazioni~~ VoIP ~~è lo~~ username ~~di autenticazione~~ \|\| -		\| '''Identifier''' \|\| Unique identifier assigned to the line. For VoIP terminations or trunks, this is the username for authentication. \|\| -
	\|-		\|-
	\| '''~~Tipo~~''' \|\| ~~Se non si tratta di un~~ gateway ~~fisico indica il tipo di linea~~ \|\| Trunk <br><br> ~~Terminazione~~ VoIP		\| '''Type''' \|\| If it is not a physical gateway, this specifies the type of line. \|\| Trunk <br><br> VoIP terminal
	\|-		\|-
	\| '''~~Stato~~''' \|\| ~~Nel caso di gateway fisici con registrazione in ingresso disabilitata lo stato raggiungibile~~ / ~~non raggiungibile indica se il~~ peer ~~risponde o meno ai messaggi~~ SIP OPTIONS. ~~Se la registrazione è abilitata indica invece se la registrazione da parte del~~ gateway ~~è stata completata con successo~~.<br>		\| '''State''' \|\| For physical gateways with inbound registration disabled, the reachable/unreachable state shows whether or not the peer responds to SIP OPTIONS messages. If registration is enabled, it shows whether or not registration was completed successfully on the part of the gateway.<br>
	~~Nel caso di domini~~ VoIP ~~lo stato raggiungibile~~ / ~~non raggiungibile indica se il~~ peer ~~risponde o meno ai messaggi~~ SIP OPTIONS.<br>		For VoIP domains, the reachable/unreachable state shows whether or not the peer responds to SIP OPTIONS messages.<br>
	~~Nel caso di trunk e terminazioni~~ VoIP ~~con abilitata registrazione remota lo stato raggiungibile~~ / ~~non raggiungibile indica se la registrazione ha avuto successo~~. ~~Se la registrazione remota è disabilitata viene visualizzato lo stato Statico~~. ~~<br>~~<br>		For VoIP terminations and trunks with remote registration enabled, the reachable/unreachable state shows whether or not the registration was successful. If remote registration is disabled, the static state is shown.<br>
	~~Lo stato in sospeso compare solo se un elemento è stato aggiunto ma la configurazione non è stata ancora applicata~~<br>		The suspended state will only be shown if an element has been added but not yet configured.<br>
	\|\| [[File:ledVerde.png\|sinistra]] ~~Raggiungibile~~ <br><br> [[File:ledRosso.png\|sinistra]] ~~Non raggiungibile~~ <br><br> [[File:ledGrigio.png\|sinistra]] ~~In sospeso~~ <br><br> [[File:ledAzzurro.png\|sinistra]] ~~Statico~~		\|\| [[File:ledVerde.png\|sinistra]] Reachable <br><br> [[File:ledRosso.png\|sinistra]] Unreachable <br><br> [[File:ledGrigio.png\|sinistra]] Suspended <br><br> [[File:ledAzzurro.png\|sinistra]] Static
	\|-		\|-
	\| '''RTT''' \|\| Round-Trip Time ~~di un pacchetto~~ SIP ~~tra centralino e~~ gateway ~~o tra centralino e dominio~~/server ~~VoIP dell’operatore~~		\| '''RTT''' \|\| Round-Trip Time of a SIP packet between PBX and gateway or PBX and VoIP domain/server of the operator.
	\|\| ~~Valore espresso~~ in ms		\|\| Value in ms
	\|-		\|-
	\| '''~~Mostra~~''' \|\| ~~Visibile se NON è acquisito il~~ [[~~Interfaccia generale~~\|lock]]. ~~Cliccando sul simbolo si possono visualizzare~~ in ~~sola lettura le impostazioni della linea~~ \|\| [[File:Lente.png\|sinistra]]		\| '''Show''' \|\| Visible if [[AdminGuide:GUI/en\|lock]] has NOT been acquired. Clicking the icon will show the line settings in read-only mode. \|\| [[File:Lente.png\|sinistra]]
	\|-		\|-
	\| '''~~Modifica~~''' \|\| ~~Visibile solo se acquisito il~~ [[~~Interfaccia generale~~\|lock]]. ~~Cliccando sul simbolo si entra nella pagina di modifica della linea~~ \|\| [[File:Matita.png\|sinistra]]		\| '''Edit''' \|\| Visible only if [[AdminGuide:GUI/en\|lock]] has been acquired. Clicking the icon will open the line modification page. \|\| [[File:Matita.png\|sinistra]]
	\|-		\|-
	\| '''~~Elimina~~''' \|\| ~~Visibile solo se acquisito il~~ [[~~Interfaccia generale~~\|lock]]. ~~Cliccando sul simbolo si elimina la linea~~ \|\| [[File:Cestino.png\|sinistra]]		\| '''Delete''' \|\| Visible only if [[AdminGuide:GUI/en\|lock]] has been acquired. Clicking the icon will delete the line. \|\| [[File:Cestino.png\|sinistra]]
	\|}		\|}

FuzzyBot: Aggiornamento come da nuova versione della pagina di origine

2022-04-20T08:56:49Z

Aggiornamento come da nuova versione della pagina di origine

← Versione meno recente		Versione delle 08:56, 20 apr 2022
Riga 7:		Riga 7:

	"Outbound and inbound lines" are all the SIP lines through which the PBX can make and receive calls to and from external numbers, i.e. not an internal service or extension (local SIP account).		"Outbound and inbound lines" are all the SIP lines through which the PBX can make and receive calls to and from external numbers, i.e. not an internal service or extension (local SIP account).

	~~These lines are configured in the [[AdminGuide:GUI:Gateway&VoIPDomains/en\|Gateway and VoIP Domains]] panel.~~

	== Calls to external numbers ==		== Calls to external numbers ==
Riga 34:		Riga 32:

	Except when explicitly set by a failover action, the choice of outbound routing class is automatically derived from the '''outbound identity'''.		Except when explicitly set by a failover action, the choice of outbound routing class is automatically derived from the '''outbound identity'''.

			<div class="mw-translate-fuzzy">
			; Calls made by a SIP account
			: The outbound identity is set to the extension linked to the SIP Account.
			; Calls forwarded by a device (telephone-driven call forwarding)
			: Same as above.
			; Calls forwarded using the KalliopePBX (unconditional) call forwarding service
			: The outbound identity is set to the forwarding extension number.
			; Transferred calls (using KalliopePBX star-codes or telephone functions)
			: The outbound identity is set equal to the transferring extension number.
			</div>

			KalliopePBX supporta sia gateway fisici (che interconnettono la rete telefonica interna a linee analogiche, ISDN o GSM) che terminazioni e trunk VoIP, in entrambi i casi sfruttando il protocollo standard SIP.

			Possono essere configurati più gateway e più terminazioni o trunk VoIP contemporaneamente. Tramite questa schermata è possibile effettuare le seguenti operazioni:
			* [[AdminGuide:BasicConcepts:Outbound lines:Dominio_VoIP\|Aggiungere un dominio VoIP (o modificarne uno esistente)]]
			* [[AdminGuide:BasicConcepts:Outbound lines:Gateway\| Aggiungere un gateway fisico (o modificarne uno esistente)]]
			* [[AdminGuide:BasicConcepts:Outbound lines:Terminazione_VoIP\|Aggiungere una terminazione VoIP (o modificarne uno esistente)]]
			* [[AdminGuide:BasicConcepts:Outbound lines:Trunk VoIP\|Aggiungere un trunk VoIP (o modificarne uno esistente)]]

			La differenza tra '''terminazione VoIP''' e '''trunk''' è data dal fatto che nel primo caso, ad ogni account di registrazione/autenticazione corrisponde un unico numero telefonico, mentre nel secondo caso si ha che a fronte di una unica credenziale di autenticazione, è possibile utilizzare un arco di numeri che solitamente condividono un radicale comune.

			'''NOTA:''' Per poter creare una terminazione VoIP o un trunk è necessario prima creare un '''dominio VoIP''' a cui associarlo.

			Nella tabella seguente sono descritte le colonne della lista delle linee di uscita.
			{\| class="wikitable"
			\|-
			! Colonna !! Descrizione !! Valore
			\|-
			\| '''Abilitato''' \|\| Indica se la linea di uscita risulta abilitata o no \|\| [[File:Abilitato.png\|sinistra]] Abilitato <br><br> [[File:Non_abilitato.png\|sinistra]] Non abilitato
			\|-
			\| '''Nome''' \|\| Il nome simbolico assegnato alla linea \|\| -
			\|-
			\| '''Identificativo''' \|\| Identificativo univoco assegnato alla linea. Nel caso di trunk o terminazioni VoIP è lo username di autenticazione \|\| -
			\|-
			\| '''Tipo''' \|\| Se non si tratta di un gateway fisico indica il tipo di linea \|\| Trunk <br><br> Terminazione VoIP
			\|-
			\| '''Stato''' \|\| Nel caso di gateway fisici con registrazione in ingresso disabilitata lo stato raggiungibile / non raggiungibile indica se il peer risponde o meno ai messaggi SIP OPTIONS. Se la registrazione è abilitata indica invece se la registrazione da parte del gateway è stata completata con successo.<br>
			Nel caso di domini VoIP lo stato raggiungibile / non raggiungibile indica se il peer risponde o meno ai messaggi SIP OPTIONS.<br>
			Nel caso di trunk e terminazioni VoIP con abilitata registrazione remota lo stato raggiungibile / non raggiungibile indica se la registrazione ha avuto successo. Se la registrazione remota è disabilitata viene visualizzato lo stato Statico. <br><br>
			Lo stato in sospeso compare solo se un elemento è stato aggiunto ma la configurazione non è stata ancora applicata<br>
			\|\| [[File:ledVerde.png\|sinistra]] Raggiungibile <br><br> [[File:ledRosso.png\|sinistra]] Non raggiungibile <br><br> [[File:ledGrigio.png\|sinistra]] In sospeso <br><br> [[File:ledAzzurro.png\|sinistra]] Statico
			\|-
			\| '''RTT''' \|\| Round-Trip Time di un pacchetto SIP tra centralino e gateway o tra centralino e dominio/server VoIP dell’operatore
			\|\| Valore espresso in ms
			\|-
			\| '''Mostra''' \|\| Visibile se NON è acquisito il [[Interfaccia generale\|lock]]. Cliccando sul simbolo si possono visualizzare in sola lettura le impostazioni della linea \|\| [[File:Lente.png\|sinistra]]
			\|-
			\| '''Modifica''' \|\| Visibile solo se acquisito il [[Interfaccia generale\|lock]]. Cliccando sul simbolo si entra nella pagina di modifica della linea \|\| [[File:Matita.png\|sinistra]]
			\|-
			\| '''Elimina''' \|\| Visibile solo se acquisito il [[Interfaccia generale\|lock]]. Cliccando sul simbolo si elimina la linea \|\| [[File:Cestino.png\|sinistra]]
			\|}

S.vistoli: Creata pagina con "; Calls made by a SIP account : The outbound identity is set to the extension linked to the SIP Account. ; Calls forwarded by a device (telephone-driven call forwarding) : Sam..."

2019-06-28T14:54:12Z

Creata pagina con "; Calls made by a SIP account : The outbound identity is set to the extension linked to the SIP Account. ; Calls forwarded by a device (telephone-driven call forwarding) : Sam..."

← Versione meno recente		Versione delle 14:54, 28 giu 2019
Riga 19:		Riga 19:
	The '''outbound identity''' is the extension number used to derive the CLID for outbound calls (according to the corresponding calling number manipulation table). The '''Outbound Identity''' can be explicitly set for failover actions, while it is automatically assigned for call smade from a SIP account or for transferred/forwarded calls:		The '''outbound identity''' is the extension number used to derive the CLID for outbound calls (according to the corresponding calling number manipulation table). The '''Outbound Identity''' can be explicitly set for failover actions, while it is automatically assigned for call smade from a SIP account or for transferred/forwarded calls:

	; ~~Chiamate eseguite da un~~ account ~~SIP~~		; Calls made by a SIP account
	: ~~L''''identità di uscita''' assegnata è l'interno a cui è assegnato l'account~~ SIP.		: The outbound identity is set to the extension linked to the SIP Account.
	; ~~Chiamate inoltrate da un dispositivo~~		; Calls forwarded by a device (telephone-driven call forwarding)
	: ~~Come sopra~~.		: Same as above.
	; ~~Chiamate inoltrate usando il servizio di inoltro di chiamata~~ (~~incondizionato~~) ~~di KalliopePBX~~		; Calls forwarded using the KalliopePBX (unconditional) call forwarding service
	: ~~L''''identità di uscita''' assegnata è il numero dell'interno inoltrante~~.		: The outbound identity is set to the forwarding extension number.
	; ~~Chiamate trasferite~~ (~~usando i codici di~~ KalliopePBX ~~o le funzionalità del telefono~~)		; Transferred calls (using KalliopePBX star-codes or telephone functions)
	: ~~L''''identità di uscita''' assegnata è il numero dell'interno trasferente~~.		: The outbound identity is set equal to the transferring extension number.

	In all these cases, if the caller requests to present itself as anonymous (according to the different [[AdminGuide:Service:CLIR/en\|CLIR]] supported methods), the outbound identity retains the extension number throughout all the lifetime of the call, and the actual calling number restriction is performed when placing the call to the outbound line (or to the destination SIP accounts for local calls).		In all these cases, if the caller requests to present itself as anonymous (according to the different [[AdminGuide:Service:CLIR/en\|CLIR]] supported methods), the outbound identity retains the extension number throughout all the lifetime of the call, and the actual calling number restriction is performed when placing the call to the outbound line (or to the destination SIP accounts for local calls).

S.vistoli il 14:54, 28 giu 2019

2019-06-28T14:54:07Z

← Versione meno recente		Versione delle 14:54, 28 giu 2019
Riga 18:		Riga 18:
	=== Outbound identity ===		=== Outbound identity ===
	The '''outbound identity''' is the extension number used to derive the CLID for outbound calls (according to the corresponding calling number manipulation table). The '''Outbound Identity''' can be explicitly set for failover actions, while it is automatically assigned for call smade from a SIP account or for transferred/forwarded calls:		The '''outbound identity''' is the extension number used to derive the CLID for outbound calls (according to the corresponding calling number manipulation table). The '''Outbound Identity''' can be explicitly set for failover actions, while it is automatically assigned for call smade from a SIP account or for transferred/forwarded calls:
	; ~~Calls made by a~~ SIP ~~account~~
	: ~~The outbound identity is set to the extension linked to the~~ SIP ~~Account~~.		; Chiamate eseguite da un account SIP
	; ~~Calls forwarded by a device (telephone-driven call forwarding)~~		: L''''identità di uscita''' assegnata è l'interno a cui è assegnato l'account SIP.
	: ~~Same as above~~.		; Chiamate inoltrate da un dispositivo
	; ~~Calls forwarded using the KalliopePBX~~ (~~unconditional~~) ~~call forwarding service~~		: Come sopra.
	: ~~The outbound identity is set to the forwarding extension number~~.		; Chiamate inoltrate usando il servizio di inoltro di chiamata (incondizionato) di KalliopePBX
	; ~~Transferred calls~~ (~~using~~ KalliopePBX ~~star-codes or telephone functions~~)		: L''''identità di uscita''' assegnata è il numero dell'interno inoltrante.
	: ~~The outbound identity is set equal to the transferring extension number~~.		; Chiamate trasferite (usando i codici di KalliopePBX o le funzionalità del telefono)
			: L''''identità di uscita''' assegnata è il numero dell'interno trasferente.

	In all these cases, if the caller requests to present itself as anonymous (according to the different [[AdminGuide:Service:CLIR/en\|CLIR]] supported methods), the outbound identity retains the extension number throughout all the lifetime of the call, and the actual calling number restriction is performed when placing the call to the outbound line (or to the destination SIP accounts for local calls).		In all these cases, if the caller requests to present itself as anonymous (according to the different [[AdminGuide:Service:CLIR/en\|CLIR]] supported methods), the outbound identity retains the extension number throughout all the lifetime of the call, and the actual calling number restriction is performed when placing the call to the outbound line (or to the destination SIP accounts for local calls).

	=== Outbound routing class ===		=== Outbound routing class ===
	The '''outbound routing class''' defines the actual handling of the call, i.e. whether or not it is allowed, and if so the sequence of outbound lines to be used to perform the call.		The '''outbound routing class''' defines the actual handling of the call, i.e. whether or not it is allowed, and if so the sequence of outbound lines to be used to perform the call.

	Except when explicitly set by a failover action, the choice of outbound routing class is automatically derived from the '''outbound identity'''.		Except when explicitly set by a failover action, the choice of outbound routing class is automatically derived from the '''outbound identity'''.

Silvia il 09:27, 10 apr 2018

2018-04-10T09:27:54Z

← Versione meno recente		Versione delle 09:27, 10 apr 2018
Riga 30:		Riga 30:

	=== Outbound routing class ===		=== Outbound routing class ===
	The '''outbound routing class''' defines the actual handling of the call, i.e. whether it is allowed ~~or not~~, and ~~(in the former case)~~ the sequence of outbound lines to be used to perform the call.		The '''outbound routing class''' defines the actual handling of the call, i.e. whether or not it is allowed, and if so the sequence of outbound lines to be used to perform the call.

	Except when explicitly set by a failover action, the choice of outbound routing class is automatically derived from the '''outbound identity'''.		Except when explicitly set by a failover action, the choice of outbound routing class is automatically derived from the '''outbound identity'''.

Silvia il 08:39, 6 mar 2018

2018-03-06T08:39:20Z

← Versione meno recente		Versione delle 08:39, 6 mar 2018
Riga 27:		Riga 27:
	: The outbound identity is set equal to the transferring extension number.		: The outbound identity is set equal to the transferring extension number.

	In all these cases, if the caller requests to present itself as anonymous (according to the different [[AdminGuide:Service:CLIR/en\|CLIR]] supported methods), the outbound identity retains the extension number throughout all the lifetime of the call, and actual calling number restriction is performed when placing the call to the outbound line (or to the destination SIP accounts~~, in case of internal~~ calls).		In all these cases, if the caller requests to present itself as anonymous (according to the different [[AdminGuide:Service:CLIR/en\|CLIR]] supported methods), the outbound identity retains the extension number throughout all the lifetime of the call, and the actual calling number restriction is performed when placing the call to the outbound line (or to the destination SIP accounts for local calls).

	=== Outbound routing class ===		=== Outbound routing class ===