Reference13r3:Concept App RCC

From innovaphone wiki
Jump to navigation Jump to search
There are also other versions of this article available: Reference13r1 | Reference13r3 (this version)

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. The RCC-App can also be used to control a Softphone-App. This is useful in Terminal-Server/Citrix environments, where the Softphone-App is installed local PC of the user and controlled from the Citrix/Terminal-Server using the RCC-App.

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 13r3 or higher)
  • the myApps communications client
  • license: App(phone)

Additional requirements to control a mobility-device

  • license: Mobility (or UC license)
  • PBX Mobility object

Additional requirements to control a Softphone-App

  • license: App(softphone)

How to get the app to a PBX user

Mobility device

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

Softphone-App controlled by RCC-App

Configure a Softphone-App for each user and additional RCC-App as device in the PBX/Objects device list. The device hardware-ID of the RCC-App must be the same as the device hardware-ID of the Softphone-App, but must additionally start with rcc-. This rcc- string is ignored by the RCC-App, resulting in RCC-commands for the remaining device-name (that equals that of the Softphone-App). If you already use a RCC-App for a mobile device you have to create an additional RCC-App for the control of the Softphone-App

RCC SoftphonApp devices

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.

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.

Environments

The following features per environment were tested.

Feature RDP Client[1][2] Citrix Microsoft Teams Parallels
Calls
Incoming test pending test pending
Outgoing test pending test pending
Audio test pending [3] test pending
Video limitation[4] test pending [5] test pending
Application Sharing
Share limitation[6] test pending [7] test pending
Watch limitation[4] test pending [7] test pending
Other
Windows Notification[8] [9] test pending test pending
Recording [10] test pending [10] test pending
3party Conference [10] test pending [10] test pending
Call transfer [10] test pending [10] test pending
  1. Tested with Windows native RDP Client, Terminals RDP Software
  2. You are not allowed to bring your USB devices (audio/video) into the session. The local devices should be connected to your local client.
  3. If you have active calls in both solutions both solution will use the audio equipment
  4. 4.0 4.1 If your video (SoftphoneApp at your local client) is undocked it will pop up in front of the full-screen session if you have the popup in the viewpoint in your last local call.
    Attention: A resize of the popup will bring it to the background and a new local call is needed, to store the window position for the next call. Otherwise you need multiple screens for a smart handling
  5. Only one application can access your camera at the same time
  6. You need an undocked Video popup (SoftphoneApp at your local client) to see the control elements without to leave the session. You can not share single applications that are started in your remote session. You can only share the full screen.
  7. 7.0 7.1 You need an undocked Video popup (SoftphoneApp at your local client) or a docked myApps to see the control elements to start a sharing.
  8. Only with Windows myApps launcher
  9. It is possible to enable Windows-Notifications also in full-screen applications
  10. 10.0 10.1 10.2 10.3 10.4 10.5 Will be handled by the local SoftphoneApp, the RCCApp will only end the control messages to the local SoftPhoneApp

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.
  • RCC app control of a SoftphoneApp is designed to allow people working in TerminalServer/Citrix environment to control a softphone app running on a PC, it has not been tested to control softphone app running on smartphone device. There are reports on iOS that it does not work when myApps is running in the background and there is no workaround/fix for this. We don't recommend using RCC APP to control softphone apps running on myAPPS in mobile devices.

Known Problems

Known Problems

Related Articles

Comparison SoftphoneApp PhoneApp RCC App