Differenze tra le versioni di "AdminGuide:Service:Fork2Mobile/en"

Versione attuale delle 08:56, 20 apr 2022

Altre lingue:

English
italiano

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. This service is available for direct calls and calls to groups, but not for calls to queues.

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 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 unconditional forward to a mobile device are two:

with Fork2Mobile the mobile number is preconfigured and cannot be changed when activating the service;
with Fork2Mobile all accounts linked to the user will ring at the same time as the mobile phone until one terminal answers, while with unconditional forward the call will be diverted exclusively to the mobile phone.

The Fork2Mobile service can be enabled and disabled in three ways:

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 under the number dialing box. Clicking the icon will enable the service, shown by the icon changing to . 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 Mobile: tap the icon on the lower right, then the icon. When the service is active the icon will change to . Clicking on the icon again will disable the service. If the service has been disabled for the extension, tapping the icon will not change its state.

When the service is enabled and the user answers from their mobile phone, they will hear the following audio message: "Press 1 to accept the call."

If the user presses 1 they will answer and other calls will be canceled.

If the user presses any other number the call to the mobile phone will be concluded and the other terminals will keep ringing.

If the user does not press anything after 15 seconds (e.g. if the call was transferred to voicemail on the mobile device), the call will be hung up.

Configuration

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 numbering plan.

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 and invert the state of the service.

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 forkm<extension>. The same key will also be set up to call the code to enable/disable the service (by default *50*).

Examples

On SNOM

Through the web GUI, you can configure function keys with:

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

value: forkm<extension>

Or you can directly edit the configuration file or the template:

<fkey idx="%%id%%" context="%%line_id%%" label="" perm="">blf sip:forkm<extension>@%%KPBX_IP_ADDRESS%%;user=phone</fkey>

where %%id%% is the ID of the key to configure and %%line_id%% is the ID of the corresponding account (1 if the account is the only one on the phone).

Example:

<fkey idx="0" context="1" label="forking2mobile 105" perm="">blf sip:forkm105@192.168.23.112</fkey>

On YEALINK

Through the web GUI, you can configure DSS keys with:

Type BLF

Value: forkm<extension>

Line: The line associated with the account (Line 1 if the account is the only one on the phone)

Or you can directly edit the configuration file or the template:

memorykey.%%id%%.line=%%line_id%%>

memorykey.%%id%%.value=forkm<extension>

memorykey.%%id%%.type=16

where %%id%% is the ID of the key to configure

and %%line_id%% is the ID of the corresponding account (1 if the account is the only one on the phone).

Example:

memorykey.2.line = 1

memorykey.2.value = forkm105

memorykey.2.type = 16

memorykey.2.pickup_value = %NULL%

memorykey.2.xml_phonebook = %NULL%

@@ Riga 1: / Riga 1: @@
 <languages />
+Return to [[AdminGuide:Service/en|AdminGuide:Service]]
 <div class="noutonum" style="float: right">__TOC__</div>
 == 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.
 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:
@@ Riga 12: / Riga 15: @@
 * with Fork2Mobile all accounts linked to the user will ring at the same time as the mobile phone until one terminal answers, while with unconditional forward the call will be diverted exclusively to the mobile phone.
-Operativamente l’attivazione/disattivazione del servizio Fork2Mobile può essere effettuata in '''3 modalità''':
+The Fork2Mobile service can be enabled and disabled in '''three ways''':
-* '''Da telefono''': il servizio viene attivato digitando il codice di attivazione (default '''*501'''). Il KalliopePBX conferma l’attivazione del servizio riproducendo il file audio “''Salvato''”. Analogamente la disattivazione avviene digitando il codice relativo (default '''*500'''). In questo caso il KalliopePBX conferma la disattivazione con il messaggio “''Grazie''”. Esistono anche dei codici che consentono di commutare lo stato (default '''*50*''') e verificare lo stato del servizio (default '''*509'''). Questi codici possono essere utilizzati esclusivamente da un dispositivo associato all’interno su cui deve essere effettuata l’attivazione / disattivazione.
+* '''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.
-* '''Da KalliopeCTI Desktop (in tutte le modalità)''': se il servizio Fork2Mobile è attivo per l’interno, sotto la casella di composizione del numero appare l’icona [[File:Kcti fork2mobile off.png|30px]]. Cliccando sull'icona il servizio viene attivato e l’icona diventa [[File:Kcti fork2mobile on.png|30px]]. La disattivazione viene effettuata cliccando nuovamente sull'icona. Posizionando il puntatore del mouse sull'icona è anche possibile visualizzare il numero mobile utilizzato dal servizio.
+* '''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]]
-* '''Da KalliopeCTI Mobile''': l’attivazione viene effettuata cliccando sul simbolo della ruota dentata [[File:Mobile tools.png|30px]] nell'angolo in basso a destra e quindi cliccando sull'icona [[File:Mobile fork2mobile off.png|30px]] che identifica il Servizio Fork2Mobile. Quando il servizio è attivo l’icona si modifica [[File:Mobile fork2mobile on.png|30px]]. Per disattivare il servizio è sufficiente cliccare nuovamente sull'icona. Se il servizio è disattivato per l’interno cliccando sull'icona non cambierà lo stato dell’icona stessa.
+* '''From KalliopeCTI Mobile''': tap the [[File:Mobile tools.png|30px]] icon on the lower right, then the [[File:Mobile fork2mobile off.png|30px]] icon. When the service is active the icon will change to [[File:Mobile fork2mobile on.png|30px]]. Clicking on the icon again will disable the service. If the service has been disabled for the extension, tapping the icon will not change its state.
-Quando è attivo il servizio e l'utente risponde sul telefono cellulare, viene riprodotto al chiamato il seguente messaggio audio “''premere 1 per accettare la chiamata''”.
+When the service is enabled and the user answers from their mobile phone, they will hear the following audio message: "''Press 1 to accept the call.''"
-Se l'utente digita 1 viene messo in comunicazione con il chiamante e le altre chiamate vengono cancellate.
+If the user presses 1 they will answer and other calls will be canceled.
-Se l'utente digita un altro numero la chiamata verso il cellulare viene conclusa e gli altri terminali continuano a squillare.
+If the user presses any other number the call to the mobile phone will be concluded and the other terminals will keep ringing.
-Nel caso in cui l'utente non digiti nulla (come nel caso in cui la chiamata sia trasferita alla casella vocale dell’operatore mobile) dopo un timeout di 15 secondi la chiamata viene riagganciata.
+If the user does not press anything after 15 seconds (e.g. if the call was transferred to voicemail on the mobile device), the call will be hung up.
-== Configurazione ==
+== Configuration ==
-Il servizio Fork2Mobile è sempre attivo a livello globale. Per abilitare il servizio per lo specifico interno è però necessario inserire il numero mobile nel pannello dell’interno.
+Fork2Mobile is always globally enabled. Specific extensions can be enabled by inserting the mobile number in the configuration page for that extension.
-L’abilitazione dei codici di attivazione / disattivazione da telefono e l’eventuale modifica sono gestiti nel [[Piano di numerazione|Piano di Numerazione]].
+The service codes can be enabled/disabled/changed in the [[AdminGuide:Service:NumberingPlan/en|numbering plan]].
-== Interoperabilità con dispositivi di terze parti ==
+== Interoperability ==
-Quando l’attivazione / disattivazione del servizio viene effettuata da telefono può essere molto utile avere a disposizione un tasto (con campo lampade) che consenta di verificare lo stato del servizio ed eventualmente commutarne lo stato.
+When enabling/disabling the service from the phone, it can be useful to have a key (with Busy Lamp Field) that lets you verify and invert the state of the service.
-Per quanto riguarda il monitoraggio, il KalliopePBX invia dei messaggi SIP NOTIFY per comunicare i cambi di stato del servizio. Il telefono dovrà inviare una SIP SUBSCRIBE per richiedere l’invio delle informazioni di stato.
+For monitoring, KalliopePBX sends SIP NOTIFY messages to communicate changes of state. The phone must send a SIP SUBSCRIBE message to request this information.
-Questa operazione è normalmente effettuata configurando un tasto funzione di tipo BLF. L’oggetto da monitorare è forkm<interno>. Sullo stesso tasto viene anche automaticamente impostata la chiamata al codice di commutazione (default *50*) per attivare / disattivare il servizio.
+This operation is normally executed by configuring a BLF-type function key. The object that needs to be monitored is forkm<extension>. The same key will also be set up to call the code to enable/disable the service (by default *50*).
-=== Esempi di configurazione ===
+=== Examples ===
-==== Su SNOM ====
+==== On SNOM ====
 [[File:Snom fork2mobile.png|miniatura]]
-* Operando tramite la web gui di configurazione configurare Function keys con
+* Through the web GUI, you can configure function keys with:
 <code>
-Account: ''selezionare dalla tendina l’account che stiamo utilizzando (se c’è un solo account configurato sul telefono è il primo della lista)''
+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
-value: forkm<interno>
+value: forkm<extension>
 </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>
-<fkey idx="%%id%%" context="%%line_id%%" label="" perm="">blf sip:forkm<interno>@%%KPBX_IP_ADDRESS%%;user=phone</fkey>
+<fkey idx="%%id%%" context="%%line_id%%" label="" perm="">blf sip:forkm<extension>@%%KPBX_IP_ADDRESS%%;user=phone</fkey>
 </code>
-Dove  ''%%id%%''  è l’identificativo del tasto da configurare
+where ''%%id%%'' is the ID of the key to configure and ''%%line_id%%'' is the ID of the corresponding account (1 if the account is the only one on the phone).
-E  ''%%line_id%%''  è l’identificativo dell’account associato (il valore è 1 se sul telefono è presente un solo account)
-Esempio:
+Example:
 <code><fkey idx="0" context="1" label="forking2mobile 105" perm="">blf sip:forkm105@192.168.23.112</fkey></code>
-==== Su YEALINK ====
+==== On YEALINK ====
 [[File:yealink_fork2mobile.png|miniatura]]
-* Operando tramite la web gui di configurazione configurare DSS Key con
+* Through the web GUI, you can configure DSS keys with:
 <code>
 Type BLF
-Value: forkm<interno>
+Value: forkm<extension>
-Line: La linea associata all’account che stiamo utilizzando (Line 1 se sul telefono è presente un solo account)
+Line: The line associated with the account (Line 1 if the account is the only one on the phone)
 </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>
 memorykey.%%id%%.line=%%line_id%%>
-memorykey.%%id%%.value=forkm<interno>
+memorykey.%%id%%.value=forkm<extension>
 memorykey.%%id%%.type=16
@@ Riga 90: / Riga 92: @@
 </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)
+and ''%%line_id%%'' is the ID of the corresponding account (1 if the account is the only one on the phone).
-Esempio:
+Example:
 <code>