Reference13r1:Concept App RCC: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
 
(14 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[Category:Concept|Apps]]
<!-- Keywords: remote, call, control, remotecallcontrol, rcc, myapps -->
<!-- Keywords: remote, call, control, remotecallcontrol, rcc, myapps -->
The RCC App provides ability to remote control softphones including CTI functionality.
The RCC App provides the user with CTI functionality.<br>
 
With the RCC App you can control your mobile phone.<br>
== Applies To ==
You can initiate outbound calls and answer inbound calls by mouse click.
This information applies to
* V13r1sr8 and up
 
== More Information ==
The SoftphoneAPP is always bound to the executing device and so calls are always initiated at the device where the app is started. There's no fix device assignment via MAC-adress as for deskphones.
 
This article documents how to do remote call control of myAPPs-mobile softphone.
<!--
=== Use cases ===
 
RCC to the own extension number can be used in several different scenarios:
 
Call control via myApps at the smartphone or other devices via PC and vice versa.


Initiate calls with myApps at the PC (browser, terminal server or any myApps capable device) and  deliver audio to another device (deskphone, 3rd-party phone, myApps on your smartphone, myApps in terminalserver environments local PC with myApps etc.)
=Features=
 
* integration in myApps communications client
Usability of push mechanism to wake-up standby myAPPs-mobile.
 
-----------------
 
RCC to your own extension number can be used in severall different scenarios.
 
Controlling a call from your myApps on your smartphone or other device from your PC and vice versa.
 
You can start your a call in myApps on your PC, (browser, terminal server or any myApps capable device) but have the audio delivered to another device (deskphone, 3rd-party phone, myApps on your smartphone, myApps in terminalserver environments local PC with myApps etc.)
 
The Push mechanism to myApps or myPBX on Mobile devices will be used to wake-up the smartphone that is in standby mode.
 
-->
 
== Features ==
* integration in myApps
* handle incoming and outgoing calls by mouse click
* search and find other users by name or phone number (using API [http://sdk.innovaphone.com/doc/reference.htm#APIs com.innovaphone.search])
* search and find other users by name or phone number (using API [http://sdk.innovaphone.com/doc/reference.htm#APIs com.innovaphone.search])
* see and manage favorites, see their presence information
* see and manage your favorite contacts, see their presence information
* list of recently contacted people
* list of recently contacted people
* provides API [http://sdk.innovaphone.com/doc/reference.htm#APIs com.innovaphone.phone] to other apps in myApps
* provides API [http://sdk.innovaphone.com/doc/reference.htm#APIs com.innovaphone.phone] to other apps in myApps
* call transfer
* call transfer
* RCC App uses PBX API "RCC" ([http://sdk.innovaphone.com/doc/appwebsocket/RCC.htm])


== Requirements ==
=Requirements=
* innovaphone PBX
* innovaphone PBX (version 13r1 or higher)
* V13r1sr8
* the myApps communications client
* myApps communications client
* license: App(phone) plus Mobility (or UC license)
* license
* PBX Mobility object


== Configuration ==
=How to get the app to a PBX user=
The PBX administrator must add a Mobility object if not already done.<br>
At the user object the PBX administrator must configure "Fork". Here two fields are to be configured:
* Mobility/Object: The Mobility object's Long Name must be entered here
* Mobility/Device: A name must be entered here. This is the name of the RCC app which will displayed in myApps (e.g. "Mobile phone")
Finally the PBX administrator must assign required licenses to the user and allow app type "rcc". This can also be done via config template if several users are to be configured.


===GSM===
The remaining steps are done by the user itself:<br>
Once the PBX administrator has done this the user opens myApps, opens the Profile app and opens page "call diversions". In section "Mobility" the user can enter the (mobile) phone number of the device which is to be controlled via RCC app. In the drop-down list "App" the entry "rcc" must be selected.<br>
Now the user will find the RCC app (e.g. "Mobile phone") in "All apps".


* step to AdminUI and search for user object to be adjusted (1)
=Working principle=
* within the column "Fork" at the respective user (2), create a forking to the '''GSM number of the user''' where the mobile-myAPPs is installed
==Initiating calls==
* add Mobility as Object, a meaningful name for the displayed application icon and as App "rcc" (3)
On the UI of the RCC app you can enter a phone number you want to call to. By clicking the dial button a call is initiated towards your own (mobile) phone number (the number you configured in your profile/mobility settings). Your phone starts ringing. When answering this call the PBX starts another call to your destination number. You will hear ringback tone. Note: Your destination will not see your (mobile) phone number, but your PBX internal phone number.
* enable use of the rcc app at the user e.g. via ConfigTemplate (5)
* a light blue phone app icon with the above chosen name is displayed within the users main app overview. Put it to homescreen if wanted.
* App start shows same UI as for "regular" phone app
* Upon dialing of any contact, PBX will set up a call to the GSM number of the mobile and, if accepted, another call to the destination, both calls will then be connected.


===VoIP===
=Restrictions=
To omit (expensive) GSM-calls, follow below described setup for remote initiated VoIP calls:
* RCC app does not add video or application sharing to your calls. Available media types are defined by the telephony endpoints. If your (mobile) phone devices is a GSM phone there will be audio only.
* step to AdminUI and search for user object to be adjusted (1)
* within the column "Fork" at the respective user (2), create a forking to the '''internal extension number''' of user
* Note: if a GSM-forking is already active, you should configure a higher delay than for GSM. You may also disable the VoIP-forking.
* add Mobility as Object, a meaningful name for the displayed application icon and as App "rcc" (4)
* enable use of the rcc app at the user e.g. via ConfigTemplate (5)
* a light blue phone app icon with the above chosen name is displayed within the users main app overview. Put it to homescreen if wanted.
* App start shows same UI as for "regular" phone app
* Upon dialing of any contact, PBX will set up a VoIP-call to the mobile and, if accepted, another call to the destination, both calls will then be connected.


[[image:rcc_config.png]]
== Known Problems ==


[[image:rcc_app_icons.png]]
[[:Category:Problem App RCC|Known Problems]]
 
[[Category:Concept|Apps]]
== Restrictions ==
[[Category:Concept_App_RCC]]
* No search for local smartphone phonebook contacts of the mobile device
* No video and no application sharing
* Twin Phones should be disabled
 
== Troubleshooting ==
 
== Known Issues ==
 
== Related Articles ==
*[[Reference10:PBX/Objects/Edit_Forks]]

Latest revision as of 15:34, 6 August 2020

The RCC App provides the user with CTI functionality.
With the RCC App you can control your mobile phone.
You can initiate outbound calls and answer inbound calls by mouse click.

Features

  • integration in myApps communications client
  • search and find other users by name or phone number (using API com.innovaphone.search)
  • see and manage your favorite contacts, see their presence information
  • list of recently contacted people
  • provides API com.innovaphone.phone to other apps in myApps
  • call transfer
  • RCC App uses PBX API "RCC" ([1])

Requirements

  • innovaphone PBX (version 13r1 or higher)
  • the myApps communications client
  • license: App(phone) plus Mobility (or UC license)
  • PBX Mobility object

How to get the app to a PBX user

The PBX administrator must add a Mobility object if not already done.
At the user object the PBX administrator must configure "Fork". Here two fields are to be configured:

  • Mobility/Object: The Mobility object's Long Name must be entered here
  • Mobility/Device: A name must be entered here. This is the name of the RCC app which will displayed in myApps (e.g. "Mobile phone")

Finally the PBX administrator must assign required licenses to the user and allow app type "rcc". This can also be done via config template if several users are to be configured.

The remaining steps are done by the user itself:
Once the PBX administrator has done this the user opens myApps, opens the Profile app and opens page "call diversions". In section "Mobility" the user can enter the (mobile) phone number of the device which is to be controlled via RCC app. In the drop-down list "App" the entry "rcc" must be selected.
Now the user will find the RCC app (e.g. "Mobile phone") in "All apps".

Working principle

Initiating calls

On the UI of the RCC app you can enter a phone number you want to call to. By clicking the dial button a call is initiated towards your own (mobile) phone number (the number you configured in your profile/mobility settings). Your phone starts ringing. When answering this call the PBX starts another call to your destination number. You will hear ringback tone. Note: Your destination will not see your (mobile) phone number, but your PBX internal phone number.

Restrictions

  • RCC app does not add video or application sharing to your calls. Available media types are defined by the telephony endpoints. If your (mobile) phone devices is a GSM phone there will be audio only.

Known Problems

Known Problems

Retrieved from "https://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_RCC&oldid=56613"