Benutzerhandbuch - UC Mobile & iPhone Settings

UC-Mobile and iPhone Settings

From iPhone Settings → UC-Mobile, the user can allow UC-Mobile to access:

Contacts
Microphone
Camera
Notifications
Cellular Data

It is recommended that UC-Mobile have access to all of the resources in the previous list. In addition, the user can configure the type of notifications they want to get with UCMobile:

Allow Notifications
Show in Notification Center
Sounds
Badge App Icon
Show on Lock Screen
It is recommended for all of the items in the previous list to be enabled. In addition, it is recommended to configure the option Alert style when unlocked to “Alerts”.

Search

UC-Mobile supports search in UC-Mobile 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 upon receiving an incoming call, and searching for a display name corresponding to an unknown number.

UC-Mobile for iOS also supports search in an LDAP-compatible directory like Microsoft Exchange. If the device email and contact applications are synchronized with Microsoft Exchange or a compatible email provider, UC-Mobile can look up contacts from the directory Global Address List (GAL). This search is available through Contacts, Local Address Book, All Contacts with Groups, Groups, and GAL.

Push Notifications

UC-Mobile introduces support for Push Notifications for Incoming Calls.

NOTE: This feature is available in preview mode only. Customers can install and try the functionality in a lab environment; however, the feature is not available for deployment to end users in a production environment.

The feature leverages support on the Placetel UC One Application Server to send Push Notifications to mobile applications over Apple Push Notification services, using the Placetel UC One Push Notification Server to send the messages to Google and Apple servers.

Mobile client applications use push notifications to get alerted for incoming calls and accept the call as VoIP.

When there is new call, Placetel UC One 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 notification for new voice mail.

Multi Device Support

UC-Mobile 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 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 sent from the server to all of the user’s clients indicating that the subscription was terminated. 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 contact list in one device is recognized in another client and the contact list is updated (that is, the contact is removed) in the other client as well.

Other Features

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 using the native dialer)
For more information on the functionalities that are available in your version of the client, contact your service provider.

Version Control

Version control is supported using the App Store mechanism. When a new release is available, the old version is removed from the App Store and users of the previous version are notified about the update possibility.

Privacy Management

UC-Mobile 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 NATs

The client supports rport (RFC 3581) for Network Address Translation (NAT) traversal and for 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 (which is currently unlikely to work without an SBC).

Failover and Failback

The client supports failover and failback mechanisms for all used protocols: Xsi, XMPP, and SIP. This feature is used to:

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.

Acronyms and Abbreviations