Android Phone - MyRoom & Other Features
MyRoom is an always available and a permanent room that you can use to chat with anyone that joins.
MyRoom is accessible using the MyRoom icon in the Tab bar.
You can add more participants using the add participants icon or they can join your room from your contact card. Once participants join the chat room, they can tap on the Call button of that screen to automatically join the conference.
MyRoom uses your permanent chat room, permanent collaboration room, and a conference bridge (audio or video). All MyRoom sessions start as chats but a call can be added to the session while in progress.
Others join your room by clicking your name on their Contacts list and selecting Join Room from the contact card.
You can dial into other contact’s MyRoom audio bridge from the directory contact card.
This Guest Client feature is specifically intended for users outside of the company. UCOne Android Phone users can invite Guest Client users to their MyRoom by selecting “Copy Guest Join Link” from the MyRoom menu button on the top right corner. The copied link delivery is outside the scope of UC-One (that is, email).
Guest users can join a session with audio in the web browser by requesting a Call Back using the provided dial-in number and conference PIN. They can also use group chat and sharing inside the web browser. However, guest clients do not have the private chat possibility and they can see the chat history of messages that occurred after they joined the session.
The MyRoom owner is prompted to accept or reject guest client users joining MyRoom sessions.
A Guest Client user invitation can be revoked by selecting “Reset Guest Link” from the MyRoom menu button.
UC-One Android Phone supports search in UC-One Android Phone Contacts and Contact Directories. The search is performed in a separate input field in the Contacts tab. Depending on the selected filter (All, Online, Local Address Book, or Directories), search results display contacts only from the current selected category.
In addition to results from the Enterprise Directory the search is also performed in several more search sources:
- User’s Personal Phone List
- Group’s Common Phone List
- Enterprise’s Common Phone List
The enhanced search is applied for both contacts searching initiated by the user and when receiving an incoming call, at which point the application performs a search for a display name corresponding to caller’s number.
Push Notifications for Calls
UC-One Android Phone supports for Push Notifications for Incoming Calls.
The feature leverages support on the Placetel Application Server to send Push Notifications to mobile applications over Google Cloud Messaging services.
Mobile client applications use push notifications to get alerted for incoming calls and accept the call as VoIP.
When there is new call, Placetel sends a push notification to the client, which is presented to the user as either OS-specific visual notification or in the user interface of the client application.
From a user experience standpoint, accepting a call works in the same way for both pushenabled clients and non-push-enabled clients. On Android, the call is presented to the user with an application-specific Incoming Call screen with Answer and Decline buttons.
Outgoing VoIP calls are performed with SIP registration on demand, which is transparent to the user. The SIP registration is done only when the user initiates the VoIP call.
In addition to push notifications for new calls, the solution also supports push notifications for new voice mail.
Multi Device Support
UC-One Android Phone provides support for users with multiple devices. This includes several features:
- Chat invitations are sent to all devices. Before the session is accepted, messages are sent to all devices, and once answered, the chat messages go to the device that has sent a reply message.
- Retrieving one’s own presence notifications, when another client updates the user’s presence. The client updates its own status based on the information it receives from the server.
- Accepting a shared presence invitation in one client is also recognized by another client, and both clients start receiving presence updates.
- A new presence subscription made in one client is recognized in another. If the contact blocks the invitation, there are presence notifications from the server to all of the user’s clients indicating that the subscription was terminated, and this information is shown to the user. If the client receives two presence authorization requests from two or more devices for the same user, it only shows one request to the user.
- Removing a contact from a Contacts list in one device is recognized in another client, and the Contacts list is updated (that is, the contact is removed) in the other client as well.
Deployment Configurations for IM&P, Audio, and Video
The mobile client can be deployed in several different configurations, based on configuration file parameters as follows:
- Primarily as an IM&P client only (no audio or video support)
- Primarily as a soft client with audio only (no IM&P or video)
- Primarily as a soft client with audio and video (no IM&P)
- Primarily as a Unified Communications (UC) client with audio only (that is, IM&P and audio but no video)
- Primarily as a UC client with audio, video, and IM&P
- Click To Dial (Call Back and Call Through with the native dialer)
For more information regarding which functionalities are available in your version of the client, contact your service provider.
Version control is supported using the Android market mechanisms. When a new release is available, the old version is removed from the market and users of the previous version are notified about the update possibility.
UC-One Android Phone supports authentication with a user name and password for different services and servers requiring authentication. For convenience, the end user can save a user name and password for different realms.
When the end user adds contacts to the Contacts list, these contacts receive a New Subscriber dialog asking whether they allow the end user to see their presence. This information is stored in this contact’s presence policies.
At any time, the user can edit the presence policies, (which are stored on the server). The user can see all contacts that are allowed to view the user’s presence (white list) and users that are not allowed to view the user’s presence (blacklist). This feature requires a compatible presence server.
Firewalls and Network Address Translations
The client supports rport (RFC 3581) for Network Address Translation (NAT) traversal and using the client behind a firewall. However, it is assumed that the client is mainly used with a session border controller (SBC), which also provides support for NAT traversal for several key features, such as calling (that is, currently unlikely to work without an SBC).
Failover and Failback
The client supports failover and failback mechanisms for all of the used protocols: Xsi, XMPP, and SIP. This feature adds:
- Detect multiple connection endpoints (per protocol)
- Order connection points by priority
- Connect to the highest priority connection point
- Reconnect to the next connection point by priority one (if there is a problem with the primary connection point)
- Provide a failback mechanism to switch back to the primary, (which is the highest priority connection point)
Secure VoIP Communication
The client supports secure VoIP communication, using encrypted call negotiation and media streams. Mandatory, preferred, and optional secure modes are supported.
The client has the ability to mark audio and video streams with Differentiated Services Code Point (DSCP) or Type of Service (ToS) flags using the Quality of Service (QoS) capabilities of the network equipment.
Emergency Call Address Change Service
Depending on service provider settings, a special dialog can be shown at login asking if the physical address should be updated. If not, login proceeds normally. If the user replies “yes”, a web browser opens with the possibility to update the physical address for emergency calls. Once the address update is complete, the user can return to the client and continue with the login.
Depending on service provider settings, a separate Emergency Call Address Change Service (ECACS) menu item may also be visible in the application. This menu item allows the ECACS service to be invoked at any time after login.
Acronyms and Abbreviations
|APN||Access Point Name|
|ACD||Automatic Call Distribution|
|CLIP||Calling Line Identification Presentation|
|CLIR||Calling Line Identification Restriction|
|DSCP||Differentiated Services Code Point|
|ECACS||Emergency Call Address Change Service|
|HTTP||Hypertext Transfer Protocol|
|HTTPS||Hypertext Transfer Protocol Secure Sockets|
|IM&P||Instant Messaging and Presence|
|IMRN||IP Multimedia Routing Number|
|NAT||Network Address Translation|
|PBX||Private Branch Exchange|
|PIN||Personal Identification Number|
|QoS||Quality of Service|
|RCS||Rich Communication Suite|
|RTCP||Real-Time Control Protocol|
|SBC||Session Border Controller|
|SIM||Subscriber Identity Module|
|SIP||Session Initiation Protocol|
|ToS||Type of Service|
|URI||Uniform Resource Identifier|
|URL||Uniform Resource Locator|
|VoIP||Voice Over IP|
|VPN||Virtual Private Network|
|XMPP||Extensible Messaging and Presence Protocol|
|Xsi||Xtended Services Interface|