Reference13r1:Concept App RCC: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
[[Category:Concept|Apps]] | [[Category:Concept|Apps]] | ||
<!-- Keywords: rcc | <!-- Keywords: remote, call, control, remotecallcontrol, rcc, myapps --> | ||
The RCC App provides | The RCC App provides ability to remote control softphones including CTI functionality. | ||
=Features= | == Applies To == | ||
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.) | |||
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 | * 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 | * see and manage favorites, 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 | ||
=Requirements= | == Requirements == | ||
* innovaphone PBX | * innovaphone PBX | ||
* | * V13r1sr8 | ||
* myApps communications client | |||
* license | * license | ||
= | == Configuration == | ||
===GSM=== | |||
* 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 '''GSM number of the user''' where the mobile-myAPPs is installed | |||
* add Mobility as Object, a meaningful name for the displayed application icon and as App "rcc" (3) | |||
* 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=== | |||
To omit (expensive) GSM-calls, follow below described setup for remote initiated VoIP calls: | |||
* 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]] | |||
[[image:rcc_app_icons.png]] | |||
== Restrictions == | |||
* 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= | == Known Issues == | ||
= Related Articles = | == Related Articles == | ||
*[[Reference10:PBX/Objects/Edit_Forks]] | |||
Revision as of 09:35, 18 February 2020
The RCC App provides ability to remote control softphones including CTI functionality.
Applies To
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.
Features
- integration in myApps
- handle incoming and outgoing calls by mouse click
- search and find other users by name or phone number (using API com.innovaphone.search)
- see and manage favorites, see their presence information
- list of recently contacted people
- provides API com.innovaphone.phone to other apps in myApps
- call transfer
Requirements
- innovaphone PBX
- V13r1sr8
- myApps communications client
- license
Configuration
GSM
- 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 GSM number of the user where the mobile-myAPPs is installed
- add Mobility as Object, a meaningful name for the displayed application icon and as App "rcc" (3)
- 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
To omit (expensive) GSM-calls, follow below described setup for remote initiated VoIP calls:
- 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.
Restrictions
- No search for local smartphone phonebook contacts of the mobile device
- No video and no application sharing
- Twin Phones should be disabled