Kalliope CTI Mobile/en - Cronologia

Troccoli il 20:59, 25 set 2022

2022-09-25T20:59:45Z

FuzzyBot: Aggiornamento come da nuova versione della pagina di origine

2022-09-25T20:54:26Z

Aggiornamento come da nuova versione della pagina di origine

← Versione meno recente		Versione delle 20:54, 25 set 2022
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:
Riga 33:		Riga 34:
	** '''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)
			</div>

	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:		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:

Troccoli il 09:28, 23 mar 2022

2022-03-23T09:28:19Z

← Versione meno recente		Versione delle 09:28, 23 mar 2022
Riga 42:		Riga 42:

	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:		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		* '''Google''': https://firebase.google.com/docs/cloud-messaging/concept-options#messaging-ports-and-your-firewall
	* Apple: https://support.apple.com/en-ph/HT203609		* '''Apple''': https://support.apple.com/en-ph/HT203609

	~~Translated with www.DeepL.com/Translator (free version)~~

	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 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).

Troccoli: Creata pagina con "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 ded..."

2022-02-22T17:57:12Z

Creata pagina con "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 ded..."

← Versione meno recente		Versione delle 17:57, 22 feb 2022
Riga 52:		Riga 52:

	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>		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>
	* [[~~Kalliope CTI Mobile Android~~\|KalliopeCTI Mobile Android app manual]]		* [[Kalliope_CTI_Mobile_Android/en\|KalliopeCTI Mobile Android app manual]]
	* [[~~Kalliope CTI Mobile IOS~~\|KalliopeCTI Mobile app IOS Manual]]		* [[Kalliope_CTI_Mobile_IOS/en\|KalliopeCTI Mobile app IOS Manual]]

Troccoli: Creata pagina con "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 eac..."

2022-02-22T14:14:01Z

Creata pagina con "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 eac..."

← Versione meno recente		Versione delle 14:14, 22 feb 2022
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:
Riga 30:		Riga 29:
	** 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:

	~~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~~:
	* Google: https://firebase.google.com/docs/cloud-messaging/concept-options#messaging-ports-and-your-firewall		* Google: https://firebase.google.com/docs/cloud-messaging/concept-options#messaging-ports-and-your-firewall
	* Apple: https://support.apple.com/en-ph/HT203609		* 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~~).		Translated with www.DeepL.com/Translator (free version)

			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).

	~~<div class="mw-translate-fuzzy">~~		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).
	~~'''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.''
	~~</div>~~

	~~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>		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>
	* [[Kalliope CTI Mobile Android\|~~Manuale~~ KalliopeCTI Mobile app ~~Android~~]]		* [[Kalliope CTI Mobile Android\|KalliopeCTI Mobile Android app manual]]
	* [[Kalliope CTI Mobile IOS\|~~Manuale~~ KalliopeCTI Mobile app IOS]]		* [[Kalliope CTI Mobile IOS\|KalliopeCTI Mobile app IOS Manual]]

Troccoli il 13:59, 22 feb 2022

2022-02-22T13:59:59Z

← Versione meno recente		Versione delle 13:59, 22 feb 2022
Riga 2:		Riga 2:
	<div class="noutonum" style="float: right">__TOC__</div>		<div class="noutonum" style="float: right">__TOC__</div>

	~~<div class="mw-translate-fuzzy">~~
	~~<div class="noutonum" style="float: right">__TOC__</div>~~
	==Introduction==		==Introduction==
	<!--[[File:kcti_appstore.png\|180x324px\|right\|thumb\|\|KalliopeCTI on the App Store]]-->		<!--[[File:kcti_appstore.png\|180x324px\|right\|thumb\|\|KalliopeCTI on the App Store]]-->
	For those who need to always be on call, Kalliope has designed the KalliopeCTI mobile app for Android and iOS.		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.		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.
	~~</div>~~

	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.		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.
Riga 20:		Riga 17:
	KalliopeCTI mobile is available on [https://play.google.com/store/apps/details?id=it.netresults.kalliopeservice Google Play] and the [https://itunes.apple.com/it/app/kalliope-cti/id1108203678?mt=8 App Store].		KalliopeCTI mobile is available on [https://play.google.com/store/apps/details?id=it.netresults.kalliopeservice Google Play] and the [https://itunes.apple.com/it/app/kalliope-cti/id1108203678?mt=8 App Store].

	~~Visualizza l'informativa sul~~ [https://www.kalliopepbx.com/images/NetResults_GDPR_-_Informativa_APP.21.03.pdf ~~Trattamento dei dati personali degli utenti~~ ]		View the policy on [https://www.kalliopepbx.com/images/NetResults_GDPR_-_Informativa_APP.21.03.pdf Processing of personal data of users ]

	'''N.B.''': Each extension can only be linked to <u>one</u> KCTI account.		'''N.B.''': Each extension can only be linked to <u>one</u> KCTI account.

FuzzyBot: Aggiornamento come da nuova versione della pagina di origine

2022-02-16T15:02:30Z

Aggiornamento come da nuova versione della pagina di origine

Mostra modifiche

S.vistoli il 11:24, 19 feb 2020

2020-02-19T11:24:05Z

← Versione meno recente		Versione delle 11:24, 19 feb 2020
Riga 12:		Riga 12:
	* '''''Click-to-call:''''' the call will be handled through the desk phone associated with your extension;		* '''''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;		* '''''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 ~~(<u>currently available only on iOS</u>)~~.		* '''''Softphone:''''' using an integrated SIP telephone engine, your smartphone will register to KalliopePBX like any other IP client.

	KalliopeCTI mobile is available on [https://play.google.com/store/apps/details?id=it.netresults.kalliopeservice Google Play] and the [https://itunes.apple.com/it/app/kalliope-cti/id1108203678?mt=8 App Store].		KalliopeCTI mobile is available on [https://play.google.com/store/apps/details?id=it.netresults.kalliopeservice Google Play] and the [https://itunes.apple.com/it/app/kalliope-cti/id1108203678?mt=8 App Store].

S.vistoli il 07:50, 19 ago 2019

2019-08-19T07:50:30Z

← Versione meno recente		Versione delle 07:50, 19 ago 2019
Riga 60:		Riga 60:
	* Resuming a paused call may sometimes fail.		* Resuming a paused call may sometimes fail.

	~~<div class="mw-translate-fuzzy">~~
	== Android specifications ==		== Android specifications ==
	* Requires Android ~~4.1~~ or later		* Requires Android 6 or later
	* ~~Laungages~~: Italian, English		* Languages: Italian, English
	* The product is only available in association with a KalliopePBX® V4 VoIP PBX		* The product is only available in association with a KalliopePBX® V4 VoIP PBX
	* Minimum KalliopePBX firmware version: 4.6.0 (does not support softphone mode)		* Minimum KalliopePBX firmware version: 4.6.0 (does not support softphone mode)
Riga 69:		Riga 68:
	* Integrates native Connection Service libraries in order to guarantee that the softphone is always reachable even when the terminal is on standby		* Integrates native Connection Service libraries in order to guarantee that the softphone is always reachable even when the terminal is on standby
	* Requres a KalliopeCTI Pro license to use GSM™ mode and a KalliopeCTI Phone license to use both GSM™ and Softphone modes		* Requres a KalliopeCTI Pro license to use GSM™ mode and a KalliopeCTI Phone license to use both GSM™ and Softphone modes
	~~</div>~~

	===== N.B. =====		===== N.B. =====

FuzzyBot: Aggiornamento come da nuova versione della pagina di origine

2019-08-19T07:50:08Z

Aggiornamento come da nuova versione della pagina di origine

← Versione meno recente		Versione delle 07:50, 19 ago 2019
Riga 60:		Riga 60:
	* Resuming a paused call may sometimes fail.		* Resuming a paused call may sometimes fail.

			<div class="mw-translate-fuzzy">
	== Android specifications ==		== Android specifications ==
	* Requires Android 4.1 or later		* Requires Android 4.1 or later
Riga 68:		Riga 69:
	* Integrates native Connection Service libraries in order to guarantee that the softphone is always reachable even when the terminal is on standby		* Integrates native Connection Service libraries in order to guarantee that the softphone is always reachable even when the terminal is on standby
	* Requres a KalliopeCTI Pro license to use GSM™ mode and a KalliopeCTI Phone license to use both GSM™ and Softphone modes		* Requres a KalliopeCTI Pro license to use GSM™ mode and a KalliopeCTI Phone license to use both GSM™ and Softphone modes
			</div>

	===== N.B. =====		===== N.B. =====

← Versione meno recente		Versione delle 20:59, 25 set 2022
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™)
Riga 34:		Riga 33:
	** '''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)
	~~</div>~~

	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:		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: