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.
Hub 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 process.
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.