Differenze tra le versioni di "Kalliope CTI Mobile/en"

Da Kalliope Wiki.
Jump to navigation Jump to search
 
(4 versioni intermedie di 2 utenti non mostrate)
Riga 23: Riga 23:
[[File:Playstore.png|180x408px]] [[File:Kcti appstore.png|180px]]
[[File:Playstore.png|180x408px]] [[File:Kcti appstore.png|180px]]


<div class="mw-translate-fuzzy">
== Initial configuration: ==
== Initial configuration: ==
In order to use the KalliopeCTI mobile app you must first:
In order to use the KalliopeCTI mobile app you must first:
* Enable "KCTI Mobile App" in the [[AdminGuide:GUI:OperatingMenu:Accounts/en|account]] settings (N.B.: only one account per extension may be enabled to use the mobile app)
* Enable "KCTI Mobile App" in the [[AdminGuide:BasicConcepts:Extensions_and_SIP_accounts/en|account]] settings (N.B.: only one account per extension may be enabled to use the mobile app)
* Assign one of the following KalliopeCTI licenses to the user:
* Assign one of the following KalliopeCTI licenses to the user:
** KalliopeCTI Pro license -> enables the use of the KalliopeCTI mobile app only in callback mode (GSM™)
** KalliopeCTI Pro license -> enables the use of the KalliopeCTI mobile app only in callback mode (GSM™)
** KalliopeCTI Phone license -> enables the use of the KalliopeCTI mobile app in both softphone and callback mode
** KalliopeCTI Phone license -> enables the use of the KalliopeCTI mobile app in both softphone and callback mode
* If you wish to externally access the company network with the mobile app, you will need to publish the following KalliopePBX ports:
* If you wish to externally access the company network with the mobile app, you will need to publish the following KalliopePBX ports ('''PLEASE NOTE: It is recommended to '''not expose the central unit's SIP service on the public in a direct way''' that can be reached from arbitrary IPs, but to use a Session Border Controller that can properly protect the central unit from intrusion attempts from outside):
** '''TCP 5039''' port for CTI services
** '''TCP 5039''' port for CTI services
** '''TCP 5222''' port for XMPP chat services
** '''TCP 5222''' port for XMPP chat services
** '''UDP for SIP service''' port as configured in the "SIP settings" page (only for softphone mode, default value is '5060')
** '''UDP for SIP service''' port as configured in the "SIP settings" page (only for softphone mode, default value is '5060')
** '''UDP 10000-20000 ports''' interval for RTP streams (only for softphone mode)
** '''UDP 10000-20000 ports''' interval for RTP streams (only for softphone mode)  


KalliopePBX must be able to send messages to the iOS and Android push notification servers. To enable this, you must open the following ports on the firewall:
Also, '''it is necessary that the KalliopePBX can send messages to the push notification servers of Apple and Google''', so the reachability by the KalliopePBX of the following addresses must be guaranteed:
* IOS:
* iOS: '''api.push.apple.com''' (HTTPS, port TCP/443)
  host: gateway.push.apple.com
* Android: '''fcm.googleapis.com''' (HTTPS, port TCP/443)
  porta: 2195
  protocollo: TCP
* Android:
  host: fcm.googleapis.com
  porta: 443
  protocollo: TCP
</div>


Inoltre '''è indispensabile che il KalliopePBX possa inviare i messaggi i server di push notification di Apple e Google''' e quindi dovrà essere garantita la raggiungibilità da parte del KalliopePBX dei seguenti indirizzi:
Since these hosts may resolve different IPs over time, it is recommended that no filters be applied to HTTPS traffic exiting KalliopePBX.
* iOS: '''api.push.apple.com''' (HTTPS, porta TCP/443)
* Android: '''fcm.googleapis.com''' (HTTPS, porta TCP/443)


Vito che questi host possono risolvere nel tempo IP diversi, è raccomandato che non siano applicati filtri al traffico HTTPS uscente da KalliopePBX.
In addition, in order for mobile devices running the KalliopeCTI Mobile APP to receive notifications, they must be connected and reachable by the sending services. For more information about the flows that must be ensured, please refer to the official documentation of:
* '''Google''': https://firebase.google.com/docs/cloud-messaging/concept-options#messaging-ports-and-your-firewall
* '''Apple''': https://support.apple.com/en-ph/HT203609


Inoltre, affinché i dispositivi mobili su cui è in esecuzione l'APP KalliopeCTI Mobile possano ricevere le notifiche, è necessario che questi siano connessi e raggiungibili dai servizi di invio. Per ulteriori informazioni sui flussi che devono essere garantiti, fare riferimento alla documentazione ufficiale di:
NOTE: In order to avoid abnormal behavior in sending incoming/ending call notifications to clients, it is necessary that each user is logged in on a single device, because each SIP account (and therefore associated user) can be associated with a unique Firebase token (used to identify the recipient of the notifications).  
* Google: https://firebase.google.com/docs/cloud-messaging/concept-options#messaging-ports-and-your-firewall
* Apple: https://support.apple.com/en-ph/HT203609


'''NOTA''': Per evitare comportamenti anomali nell'invio ai client delle notifiche di chiamata in arrivo/terminata è necessario che ciascun utente sia loggato su un solo device, perché ad ogni account SIP (e quindi utente associato) può essere associato un unico token Firebase (utilizzato per identificare il destinatario delle notifiche).  
NOTE: In case the central unit SIP service is exposed on a different IP than the CTI connection IP, or on a different port than the standard one (5060), it is necessary to set on the KalliopePBX one or both of the following custom placeholders within the Provisioning panel: '''%%_KPHONE_SIP_REGISTRAR_IP%%''' and '''%%_KPHONE_SIP_REGISTRAR_PORT%%%'''. This configuration is normally necessary when the SIP service is exposed to the public through a Session Border Controller that uses a different IP from the one on which the PBX is reachable, while it is not necessary if the PBX and the SBC are natted on the same public IP, each one for the ports of its competence (TCP/5039 and TCP/5222 for the CTI and Chat components, towards Kalliope, and SIP + RTP for voice, towards the SBC).


<div class="mw-translate-fuzzy">
More and specific informations regarding the configuration and use of the KalliopeCTI Mobile app in the two operating systems Android and IOS can be found on the following dedicated pages:<br>
'''N.B.''': ''if you wish to use softphone mode, it is strongly suggested that you do not directly publish the PBX but rather use a '''SBC device''' that interfaces with the public. In this case, you will need to set the custom placeholder '''%%_KPHONE_SIP_REGISTRAR_IP%%''' with the public IP address assigned to the SBC.''
* [[Kalliope_CTI_Mobile_Android/en|KalliopeCTI Mobile Android app manual]]
</div>
* [[Kalliope_CTI_Mobile_IOS/en|KalliopeCTI Mobile app IOS Manual]]
 
Le informazioni dettagliate specifiche riguardo la configurazione e l'uso dell'app KalliopeCTI Mobile nei due sistemi operativi Android e IOS sono disponibili sulle seguenti pagine dedicate:<br>
* [[Kalliope CTI Mobile Android|Manuale KalliopeCTI Mobile app Android]]
* [[Kalliope CTI Mobile IOS|Manuale KalliopeCTI Mobile app IOS]]

Versione attuale delle 20:59, 25 set 2022

Altre lingue:

Introduction

For those who need to always be on call, Kalliope has designed the KalliopeCTI mobile app for Android and iOS.

The KalliopeCTI mobile app is an optional product that lets you access telephone and UC services even outside your office through your extension number, using the company lines.

To guarantee stability and improve conversation quality, KalliopeCTI mobile lets you choose how to handle your calls: based on data traffic availability, you can choose whether to use the GSM network or use the app in softphone mode.

KalliopeCTI mobile lets you call using three different modes:

  • Click-to-call: the call will be handled through the desk phone associated with your extension;
  • Call-back: call from your smartphone using Kalliope lines;
  • Softphone: using an integrated SIP telephone engine, your smartphone will register to KalliopePBX like any other IP client.

KalliopeCTI mobile is available on Google Play and the App Store.

View the policy on Processing of personal data of users

N.B.: Each extension can only be linked to one KCTI account.

Playstore.png Kcti appstore.png

Initial configuration:

In order to use the KalliopeCTI mobile app you must first:

  • Enable "KCTI Mobile App" in the account settings (N.B.: only one account per extension may be enabled to use the mobile app)
  • Assign one of the following KalliopeCTI licenses to the user:
    • KalliopeCTI Pro license -> enables the use of the KalliopeCTI mobile app only in callback mode (GSM™)
    • KalliopeCTI Phone license -> enables the use of the KalliopeCTI mobile app in both softphone and callback mode
  • If you wish to externally access the company network with the mobile app, you will need to publish the following KalliopePBX ports (PLEASE NOTE: It is recommended to not expose the central unit's SIP service on the public in a direct way that can be reached from arbitrary IPs, but to use a Session Border Controller that can properly protect the central unit from intrusion attempts from outside):
    • TCP 5039 port for CTI services
    • TCP 5222 port for XMPP chat services
    • UDP for SIP service port as configured in the "SIP settings" page (only for softphone mode, default value is '5060')
    • UDP 10000-20000 ports interval for RTP streams (only for softphone mode)

Also, it is necessary that the KalliopePBX can send messages to the push notification servers of Apple and Google, so the reachability by the KalliopePBX of the following addresses must be guaranteed:

  • iOS: api.push.apple.com (HTTPS, port TCP/443)
  • Android: fcm.googleapis.com (HTTPS, port TCP/443)

Since these hosts may resolve different IPs over time, it is recommended that no filters be applied to HTTPS traffic exiting KalliopePBX.

In addition, in order for mobile devices running the KalliopeCTI Mobile APP to receive notifications, they must be connected and reachable by the sending services. For more information about the flows that must be ensured, please refer to the official documentation of:

NOTE: In order to avoid abnormal behavior in sending incoming/ending call notifications to clients, it is necessary that each user is logged in on a single device, because each SIP account (and therefore associated user) can be associated with a unique Firebase token (used to identify the recipient of the notifications).

NOTE: In case the central unit SIP service is exposed on a different IP than the CTI connection IP, or on a different port than the standard one (5060), it is necessary to set on the KalliopePBX one or both of the following custom placeholders within the Provisioning panel: %%_KPHONE_SIP_REGISTRAR_IP%% and %%_KPHONE_SIP_REGISTRAR_PORT%%%. This configuration is normally necessary when the SIP service is exposed to the public through a Session Border Controller that uses a different IP from the one on which the PBX is reachable, while it is not necessary if the PBX and the SBC are natted on the same public IP, each one for the ports of its competence (TCP/5039 and TCP/5222 for the CTI and Chat components, towards Kalliope, and SIP + RTP for voice, towards the SBC).

More and specific informations regarding the configuration and use of the KalliopeCTI Mobile app in the two operating systems Android and IOS can be found on the following dedicated pages: