AdminGuide:Service:CLIR/en - Cronologia

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

2018-04-17T09:03:36Z

Creata pagina con "Return to AdminGuide:Service"

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

FuzzyBot: Aggiornamento come da nuova versione della pagina di origine

2018-04-17T09:03:10Z

Aggiornamento come da nuova versione della pagina di origine

← Versione meno recente		Versione delle 09:03, 17 apr 2018
Riga 1:		Riga 1:
	<languages />		<languages />
			Torna a [[AdminGuide:Service]]


	<div class="noutonum" style="float: right">__TOC__</div>		<div class="noutonum" style="float: right">__TOC__</div>
	==Calling Line Identification Restriction (CLIR)==		==Calling Line Identification Restriction (CLIR)==

Silvia il 09:32, 10 apr 2018

2018-04-10T09:32:39Z

← Versione meno recente		Versione delle 09:32, 10 apr 2018
Riga 36:		Riga 36:
	Even if CLIR is enabled, it is still necessary to send the identity of the calling party to the provider. If this doesn't happen, the provider will normally reject the outbound call. This information can be sent through P-Asserted-Identity Header or Remote-Party Header.		Even if CLIR is enabled, it is still necessary to send the identity of the calling party to the provider. If this doesn't happen, the provider will normally reject the outbound call. This information can be sent through P-Asserted-Identity Header or Remote-Party Header.

	These headers must be enabled in the configuration of the outbound trunks (Gateways and VoIP Domains -> Trunk). The accepted format for the headers is usually the one suggested in the configuration page. If there are issues, you should check the required configuration with ~~you~~ service provider.		These headers must be enabled in the configuration of the outbound trunks (Gateways and VoIP Domains -> Trunk). The accepted format for the headers is usually the one suggested in the configuration page. If there are issues, you should check the required configuration with your service provider.

	To prevent these headers from being overwritten, it is necessary to disable COLP in the outbound trunk configuration.		To prevent these headers from being overwritten, it is necessary to disable COLP in the outbound trunk configuration.

Silvia il 08:17, 6 mar 2018

2018-03-06T08:17:38Z

← Versione meno recente		Versione delle 08:17, 6 mar 2018
Riga 20:		Riga 20:
	In order to use the service, it must be enabled in the numbering plan (where you can also edit the service codes).		In order to use the service, it must be enabled in the numbering plan (where you can also edit the service codes).

	Whether the service is enabled or disabled, as well as the default behavior, must be specified for each extension (~~possibly~~ through extension templates). Other than the default behavior for calls between extensions and calls to external numbers, the settings for each extension include the option to hide the caller ID if the calling device sends a Privacy: id SIP Header.		Whether the service is enabled or disabled, as well as the default behavior, must be specified for each extension (this can be done through extension templates). Other than the default behavior for calls between extensions and calls to external numbers, the settings for each extension include the option to hide the caller ID if the calling device sends a Privacy: id SIP Header.

	===Interoperability===		===Interoperability===

Silvia il 08:16, 6 mar 2018

2018-03-06T08:16:47Z

← Versione meno recente		Versione delle 08:16, 6 mar 2018
Riga 18:		Riga 18:
	===Configuration===		===Configuration===

	In order to use the service, it must be enabled in the numbering plan (where ~~it is~~ also ~~possible to~~ edit the service codes).		In order to use the service, it must be enabled in the numbering plan (where you can also edit the service codes).

	Whether the service is enabled or disabled, as well as the default behavior, must be specified for each extension (possibly through extension templates). Other than the default behavior for calls between extensions and calls to external numbers, the settings for each extension include the option to hide the caller ID if the calling device sends a Privacy: id SIP Header.		Whether the service is enabled or disabled, as well as the default behavior, must be specified for each extension (possibly through extension templates). Other than the default behavior for calls between extensions and calls to external numbers, the settings for each extension include the option to hide the caller ID if the calling device sends a Privacy: id SIP Header.

Silvia: Creata pagina con "Even if CLIR is enabled, it is still necessary to send the identity of the calling party to the provider. If this doesn't happen, the provider will normally reject the outboun..."

2018-02-26T10:35:53Z

Creata pagina con "Even if CLIR is enabled, it is still necessary to send the identity of the calling party to the provider. If this doesn't happen, the provider will normally reject the outboun..."

← Versione meno recente		Versione delle 10:35, 26 feb 2018
Riga 34:		Riga 34:
	* VoIP Provider		* VoIP Provider

	~~Nel caso in cui il servizio~~ CLIR ~~sia abilitato è necessario comunque inviare al~~ provider l'~~identità del numero chiamante.<br>~~		Even if CLIR is enabled, it is still necessary to send the identity of the calling party to the provider. If this doesn't happen, the provider will normally reject the outbound call. This information can be sent through P-Asserted-Identity Header or Remote-Party Header.
	~~Se questo non avviene di norma il~~ provider ~~rifiuterà la chiamata in uscita~~.~~<br>~~
	~~Questa informazione può essere inviata tramite~~ P-Asserted-Identity Header o Remote-Party Header.~~<br>~~		These headers must be enabled in the configuration of the outbound trunks (Gateways and VoIP Domains -> Trunk). The accepted format for the headers is usually the one suggested in the configuration page. If there are issues, you should check the required configuration with you service provider.
	~~L'invio di questi header deve essere abilitato nella configurazione del trunk di uscita~~ (~~Gateway e Domini~~ VoIP -> Trunk).~~<br>~~
	~~Il formato accettato per gli header è normalmente quello suggerito nel pannello di configurazione~~.~~<br>~~		To prevent these headers from being overwritten, it is necessary to disable COLP in the outbound trunk configuration.
	~~Nel caso di problemi è necessario verificare con il proprio~~ provider ~~la configurazione richiesta~~. ~~<br>~~
	~~Per evitare che questi header vengano sovrascritti è inoltre necessario impostare la modalità invio~~ COLP ~~a disabilitato (sempre nella configurazione del~~ trunk ~~di uscita)~~.

Silvia: Creata pagina con "Calls between extensions do not require additional configuration, while outbound calls might, depending on the type of outbound line."

2018-02-26T10:35:16Z

Creata pagina con "Calls between extensions do not require additional configuration, while outbound calls might, depending on the type of outbound line."

← Versione meno recente		Versione delle 10:35, 26 feb 2018
Riga 30:		Riga 30:
	* the Privacy: id SIP header is added.		* the Privacy: id SIP header is added.

	~~Per le chiamate tra interni non sono necessarie ulteriori configurazioni mentre per le chiamate in uscita possono esere necessarie alcune modifiche~~		Calls between extensions do not require additional configuration, while outbound calls might, depending on the type of outbound line.
	~~in base alla tipologia di linea di uscita~~.

	* VoIP Provider		* VoIP Provider

Silvia: Creata pagina con "* the user part of the From URI is replaced with anonymous (e.g. sip:anonymous@:); * the user part of the Contact Header is replaced with..."

2018-02-26T10:35:03Z

Creata pagina con "* the user part of the From URI is replaced with anonymous (e.g. sip:anonymous@<telephone_ip_address>:<telephone_port>); * the user part of the Contact Header is replaced with..."

← Versione meno recente		Versione delle 10:35, 26 feb 2018
Riga 26:		Riga 26:
	When CLIR is enabled, SIP signaling is modified as follows:		When CLIR is enabled, SIP signaling is modified as follows:

	*~~viene sostituito la~~ user part ~~del~~ From URI ~~con~~ anonymous (~~ad es~~. sip:anonymous@<~~ip_address_telefono~~>:<~~porta_telefono~~>)		* the user part of the From URI is replaced with anonymous (e.g. sip:anonymous@<telephone_ip_address>:<telephone_port>);
	*~~viene sostituito la~~ user part ~~del~~ Contact Header ~~con~~ anonymous (~~ad es~~. sip:anonymous@<ip_address_registrar>:<~~porta_registrar~~>)		* the user part of the Contact Header is replaced with anonymous (e.g. sip:anonymous@<ip_address_registrar>:<registrar_port>);
	*~~viene aggiunto l'header SIP~~ Privacy: id		* the Privacy: id SIP header is added.

	Per le chiamate tra interni non sono necessarie ulteriori configurazioni mentre per le chiamate in uscita possono esere necessarie alcune modifiche		Per le chiamate tra interni non sono necessarie ulteriori configurazioni mentre per le chiamate in uscita possono esere necessarie alcune modifiche

Silvia: Creata pagina con "When CLIR is enabled, SIP signaling is modified as follows:"

2018-02-26T10:34:48Z

Creata pagina con "When CLIR is enabled, SIP signaling is modified as follows:"

← Versione meno recente		Versione delle 10:34, 26 feb 2018
Riga 24:		Riga 24:
	===Interoperability===		===Interoperability===

	~~Quando viene abilitato il servizio~~ CLIR ~~la segnalazione~~ SIP ~~viene modificata come segue~~:		When CLIR is enabled, SIP signaling is modified as follows:

	*viene sostituito la user part del From URI con anonymous (ad es. sip:anonymous@<ip_address_telefono>:<porta_telefono>)		*viene sostituito la user part del From URI con anonymous (ad es. sip:anonymous@<ip_address_telefono>:<porta_telefono>)

Silvia: Creata pagina con "===Interoperability==="

2018-02-26T10:34:35Z

Creata pagina con "===Interoperability==="

← Versione meno recente		Versione delle 10:34, 26 feb 2018
Riga 22:		Riga 22:
	Whether the service is enabled or disabled, as well as the default behavior, must be specified for each extension (possibly through extension templates). Other than the default behavior for calls between extensions and calls to external numbers, the settings for each extension include the option to hide the caller ID if the calling device sends a Privacy: id SIP Header.		Whether the service is enabled or disabled, as well as the default behavior, must be specified for each extension (possibly through extension templates). Other than the default behavior for calls between extensions and calls to external numbers, the settings for each extension include the option to hide the caller ID if the calling device sends a Privacy: id SIP Header.

	===~~Interoperabilità~~===		===Interoperability===

	Quando viene abilitato il servizio CLIR la segnalazione SIP viene modificata come segue:		Quando viene abilitato il servizio CLIR la segnalazione SIP viene modificata come segue: