AdminGuide:Service:Fork2Mobile/en - Cronologia

Troccoli il 08:56, 20 apr 2022

2022-04-20T08:56:32Z

← Versione meno recente		Versione delle 08:56, 20 apr 2022
Riga 35:		Riga 35:
	Fork2Mobile is always globally enabled. Specific extensions can be enabled by inserting the mobile number in the configuration page for that extension.		Fork2Mobile is always globally enabled. Specific extensions can be enabled by inserting the mobile number in the configuration page for that extension.

	The service codes can be enabled/disabled/changed in the [[AdminGuide:~~GUI:OperatingMenu~~:NumberingPlan/en\|numbering plan]].		The service codes can be enabled/disabled/changed in the [[AdminGuide:Service:NumberingPlan/en\|numbering plan]].

	== Interoperability ==		== Interoperability ==

S.vistoli il 10:30, 27 feb 2019

2019-02-27T10:30:09Z

← Versione meno recente		Versione delle 10:30, 27 feb 2019
Riga 3:		Riga 3:


	~~<div class="mw-translate-fuzzy">~~
	<div class="noutonum" style="float: right">__TOC__</div>		<div class="noutonum" style="float: right">__TOC__</div>
	== Description ==		== Description ==
	The '''Fork2Mobile''' service forwards calls to an extension to a mobile number linked to the extension. This service is useful for users who wish to receive calls even when they are away from their workstation.		The '''Fork2Mobile''' service forwards calls to an extension to a mobile number linked to the extension. This service is useful for users who wish to receive calls even when they are away from their workstation. This service is available for direct calls and calls to groups, but not for calls to queues.
	~~</div>~~

	When this service is enabled, KalliopePBX presents the inbound call not only to the accounts linked to the extension but also to a predefined mobile number. Once communication with the mobile phone has been established, KalliopePBX first verifies whether the call has actually been answered (and not, for example, sent to voicemail) and then bridges the original inbound call with the new one to the mobile phone. The other devices will stop ringing once the call is answered. The call to the mobile number follows the outbound routing rules associated to the extension and the caller ID will be the one shown whenever the extension makes calls to the public network. The call to the mobile phone will not therefore include any information on the original calling party.		When this service is enabled, KalliopePBX presents the inbound call not only to the accounts linked to the extension but also to a predefined mobile number. Once communication with the mobile phone has been established, KalliopePBX first verifies whether the call has actually been answered (and not, for example, sent to voicemail) and then bridges the original inbound call with the new one to the mobile phone. The other devices will stop ringing once the call is answered. The call to the mobile number follows the outbound routing rules associated to the extension and the caller ID will be the one shown whenever the extension makes calls to the public network. The call to the mobile phone will not therefore include any information on the original calling party.

FuzzyBot: Aggiornamento come da nuova versione della pagina di origine

2019-02-27T10:29:16Z

Aggiornamento come da nuova versione della pagina di origine

← Versione meno recente		Versione delle 10:29, 27 feb 2019
Riga 3:		Riga 3:


			<div class="mw-translate-fuzzy">
	<div class="noutonum" style="float: right">__TOC__</div>		<div class="noutonum" style="float: right">__TOC__</div>
	== Description ==		== Description ==
	The '''Fork2Mobile''' service forwards calls to an extension to a mobile number linked to the extension. This service is useful for users who wish to receive calls even when they are away from their workstation.		The '''Fork2Mobile''' service forwards calls to an extension to a mobile number linked to the extension. This service is useful for users who wish to receive calls even when they are away from their workstation.
			</div>

	When this service is enabled, KalliopePBX presents the inbound call not only to the accounts linked to the extension but also to a predefined mobile number. Once communication with the mobile phone has been established, KalliopePBX first verifies whether the call has actually been answered (and not, for example, sent to voicemail) and then bridges the original inbound call with the new one to the mobile phone. The other devices will stop ringing once the call is answered. The call to the mobile number follows the outbound routing rules associated to the extension and the caller ID will be the one shown whenever the extension makes calls to the public network. The call to the mobile phone will not therefore include any information on the original calling party.		When this service is enabled, KalliopePBX presents the inbound call not only to the accounts linked to the extension but also to a predefined mobile number. Once communication with the mobile phone has been established, KalliopePBX first verifies whether the call has actually been answered (and not, for example, sent to voicemail) and then bridges the original inbound call with the new one to the mobile phone. The other devices will stop ringing once the call is answered. The call to the mobile number follows the outbound routing rules associated to the extension and the caller ID will be the one shown whenever the extension makes calls to the public network. The call to the mobile phone will not therefore include any information on the original calling party.

Silvia il 07:18, 8 mag 2018

2018-05-08T07:18:17Z

← Versione meno recente		Versione delle 07:18, 8 mag 2018
Riga 18:		Riga 18:
	* '''From the phone''': the service can be enabled by dialing the activation code (by default '''501'''). KalliopePBX will confirm the activation by playing the "Saved" audio file. Similarly, the user can deactivate the service by dialing the deactivation code (by default '''500'''). KalliopePBX will confirm the deactivation by playing the "Thank you" audio file. There are also codes to invert (by default '''50''') and to verify the state of the service (by default '''*509'''). These codes can only be used from a phone linked to the extension on which the service is being enabled/disabled.		* '''From the phone''': the service can be enabled by dialing the activation code (by default '''501'''). KalliopePBX will confirm the activation by playing the "Saved" audio file. Similarly, the user can deactivate the service by dialing the deactivation code (by default '''500'''). KalliopePBX will confirm the deactivation by playing the "Thank you" audio file. There are also codes to invert (by default '''50''') and to verify the state of the service (by default '''*509'''). These codes can only be used from a phone linked to the extension on which the service is being enabled/disabled.

	* '''From KalliopeCTI Desktop (all versions)''': if Fork2Mobile is enabled for the extension, you can find the ~~icon~~ [[File:Kcti fork2mobile off.png\|30px]] under the number dialing box. Clicking the icon will enable the service, shown by the icon changing to [[File:Kcti fork2mobile on.png\|30px]]. Clicking on the icon again will disable the service. Hovering the cursor on the icon will display the mobile number used by the service.		* '''From KalliopeCTI Desktop (all versions)''': if Fork2Mobile is enabled for the extension, you can find the [[File:Kcti fork2mobile off.png\|30px]] icon under the number dialing box. Clicking the icon will enable the service, shown by the icon changing to [[File:Kcti fork2mobile on.png\|30px]]. Clicking on the icon again will disable the service. Hovering the cursor on the icon will display the mobile number used by the service.
	[[File:Kcti fork2mobile tooltip.png]]		[[File:Kcti fork2mobile tooltip.png]]

Silvia il 07:16, 8 mag 2018

2018-05-08T07:16:34Z

← Versione meno recente		Versione delle 07:16, 8 mag 2018
Riga 9:		Riga 9:
	When this service is enabled, KalliopePBX presents the inbound call not only to the accounts linked to the extension but also to a predefined mobile number. Once communication with the mobile phone has been established, KalliopePBX first verifies whether the call has actually been answered (and not, for example, sent to voicemail) and then bridges the original inbound call with the new one to the mobile phone. The other devices will stop ringing once the call is answered. The call to the mobile number follows the outbound routing rules associated to the extension and the caller ID will be the one shown whenever the extension makes calls to the public network. The call to the mobile phone will not therefore include any information on the original calling party.		When this service is enabled, KalliopePBX presents the inbound call not only to the accounts linked to the extension but also to a predefined mobile number. Once communication with the mobile phone has been established, KalliopePBX first verifies whether the call has actually been answered (and not, for example, sent to voicemail) and then bridges the original inbound call with the new one to the mobile phone. The other devices will stop ringing once the call is answered. The call to the mobile number follows the outbound routing rules associated to the extension and the caller ID will be the one shown whenever the extension makes calls to the public network. The call to the mobile phone will not therefore include any information on the original calling party.

	However, if the KalliopeCTI Mobile app is active and connected, KalliopePBX will send the original calling number to the app, which then ~~informs~~ the user. This way, the user can see who is calling them before choosing whether or not to answer.		However, if the KalliopeCTI Mobile app is active and connected, KalliopePBX will send the original calling number to the app, which then displays it to the user. This way, the user can see who is calling them before choosing whether or not to answer.

	The difference between this service and [[AdminGuide:Service:UnconditionalForward/en\|unconditional forward]] to a mobile device are two:		The difference between this service and [[AdminGuide:Service:UnconditionalForward/en\|unconditional forward]] to a mobile device are two:

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

2018-04-17T09:23:13Z

Creata pagina con "Return to AdminGuide:Service"

← Versione meno recente		Versione delle 09:23, 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 il 11:35, 13 mar 2018

2018-03-13T11:35:58Z

← Versione meno recente		Versione delle 11:35, 13 mar 2018
Riga 15:		Riga 15:
	* '''From the phone''': the service can be enabled by dialing the activation code (by default '''501'''). KalliopePBX will confirm the activation by playing the "Saved" audio file. Similarly, the user can deactivate the service by dialing the deactivation code (by default '''500'''). KalliopePBX will confirm the deactivation by playing the "Thank you" audio file. There are also codes to invert (by default '''50''') and to verify the state of the service (by default '''*509'''). These codes can only be used from a phone linked to the extension on which the service is being enabled/disabled.		* '''From the phone''': the service can be enabled by dialing the activation code (by default '''501'''). KalliopePBX will confirm the activation by playing the "Saved" audio file. Similarly, the user can deactivate the service by dialing the deactivation code (by default '''500'''). KalliopePBX will confirm the deactivation by playing the "Thank you" audio file. There are also codes to invert (by default '''50''') and to verify the state of the service (by default '''*509'''). These codes can only be used from a phone linked to the extension on which the service is being enabled/disabled.

	* '''From KalliopeCTI Desktop (all versions)''': if Fork2Mobile is enabled for the extension, you can find the icon [[File:Kcti fork2mobile off.png\|30px]] under the number ~~composition~~ box. Clicking the icon will enable the service, shown by the icon changing to [[File:Kcti fork2mobile on.png\|30px]]. Clicking on the icon again will disable the service. Hovering the cursor on the icon will display the mobile number used by the service.		* '''From KalliopeCTI Desktop (all versions)''': if Fork2Mobile is enabled for the extension, you can find the icon [[File:Kcti fork2mobile off.png\|30px]] under the number dialing box. Clicking the icon will enable the service, shown by the icon changing to [[File:Kcti fork2mobile on.png\|30px]]. Clicking on the icon again will disable the service. Hovering the cursor on the icon will display the mobile number used by the service.
	[[File:Kcti fork2mobile tooltip.png]]		[[File:Kcti fork2mobile tooltip.png]]

Silvia: Creata pagina con "Example:"

2018-02-27T09:06:04Z

Creata pagina con "Example:"

← Versione meno recente		Versione delle 09:06, 27 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-27T09:05:46Z

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 09:05, 27 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-27T09:05:32Z

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

← Versione meno recente		Versione delle 09:05, 27 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)