Business Communicator for Android

Business Communicator for Android Product Guide Release 9.3.0 Document Version 1

Copyright Notice Copyright 2012 BroadSoft, Inc. All rights reserved. Microsoft, MSN, Windows, and the Windows logo are registered trademarks of Microsoft Corporation. Other product names mentioned in this document may be trademarks or registered trademarks of their respective companies and are hereby acknowledged. This document is printed in the United States of America. PAGE 2

Table of Contents 1 Features... 1 1.1 Log In... 1 1.2 Main View... 3 1.3 Contact List... 3 1.3.1 General... 3 1.3.2 Add Contact Manually... 6 1.3.3 BroadWorks Enterprise Directory Search... 7 1.3.4 Contact Card... 9 1.4 Presence... 11 1.5 Instant Messaging... 13 1.5.1 Chat... 13 1.5.2 Chat Tab... 14 1.5.3 Missed Chat Notification... 15 1.6 XMPP Multi-Device... 16 1.7 Voice Calls... 17 1.7.1 General... 17 1.7.2 Missed Calls... 19 1.7.3 Message Waiting Indicator (MWI) and Voice Mail Access... 20 1.7.4 Business Line Call-Back and Call-Through... 22 1.7.5 Contact Name Lookup for Incoming Calls and Call Logs... 23 1.7.6 Three-Way Calling... 23 1.7.7 Call Transfer... 26 1.8 BroadWorks Call History... 27 1.9 BroadWorks Service Management... 28 1.10 Call Modes... 29 1.11 Other Features... 30 1.11.1 Version Control... 30 1.11.2 Privacy Management... 30 1.11.3 Help Pages... 30 1.11.4 Firewalls and NATs... 30 1.11.5 Automatic Sign In... 30 1.11.6 Settings... 30 2 System Requirements... 32 PAGE III

Table of Figures Figure 1 Credentials for Sign In... 2 Figure 4 Contact List... 4 Figure 5 Context Menu for Buddies List Contact... 5 Figure 6 Adding Contacts... 6 Figure 7 Presence Authorization Pop-up Dialog... 7 Figure 8 Enterprise Directory Search Results... 8 Figure 9 Buddies List Contact Card... 9 Figure 10 Enterprise Directory Search Contact Card... 10 Figure 11 Presence... 11 Figure 12 Personal Message... 12 Figure 13 Chat View (Depends on Device This View is from Samsung Galaxy)... 13 Figure 14 Chat Tab... 14 Figure 15 Missed Chat... 15 Figure 16 Call Tab... 17 Figure 17 Audio Call... 18 Figure 19 Missed Calls... 19 Figure 20 Voice Mail Notification... 20 Figure 21 Call Tab Enter Number... 21 Figure 22 Business Line Call-Back and Call-Through... 22 Figure 23 Three-Way Calling (Adding Third Party)... 23 Figure 24 Three-Way Calling (Selecting Conference)... 24 Figure 25 Three-Way Calling (Participants)... 25 Figure 26 Transfer... 26 Figure 27 BroadWorks Call Logs... 27 Figure 28 BroadWorks Service Management on Android... 28 Figure 29 Call Modes... 29 Figure 30 Settings View... 31 PAGE IV

1 Features 1.1 Log In This section lists and describes end-user functionality in the Business Communicator Android client. Note that most functionality, such as presence and chat, requires an Application Server. On the Login screen, the user can type in their IP Centrex user name and password or SIP user name and password, depending on whether BroadWorks Device Management is used. User names are saved so that the next time the user logs in, they can simply select the correct user name in the combination box. The first time the user starts the client, the application asks for the user s identity (user name and password) and displays a Login screen with the following elements (using two fields divided by a graphical divider). The top field says user name and lower field says password. Tapping either one opens the virtual keyboard. When both fields are filled, the Sign-in button is available. The following is a list of the Login window fields: Phone number This is an editable combination box. The current phone number is automatically filled for first start up. Password This is a text field with password masking. Show password This check box is unchecked by default. The written password appears instead of just stars. This is reset to unchecked each time the user opens the client. Sign in automatically This is a check box, which is only available if user name and password are provided. It is unchecked by default. The user is able to turn it on only if the Remember Password is checked. Remember password This is a check box. Sign in button If Remember password is not checked, this screen is shown each time the client is started, with only the Phone number automatically filled. If Remember password is checked, this screen is shown with all credentials automatically filled. By tapping Sign in, the user sees the contact list. PAGE 1

Figure 1 Credentials for Sign In A loading animation appears each time the client is launched. When the network connection has been lost, the client returns to the Login screen. Once the network connection has been recovered, the client performs an auto-login. The Reference Client Login is shown in the following figure. PAGE 2

1.2 Main View The main view contains a number of tabs that provide information about the contacts and communications options in the top bar as follows: Contacts Call Chat Call history The Contacts tab provides information about presence-enabled contacts only. In addition to these contacts, the user can also separately use the native address book where contacts do not have to be presence-enabled. The client supports landscape mode. The client also follows the silent mode that has been set for the device and as a result, an incoming Voice Over Internet Protocol (VoIP) call alerts the user the same way as an incoming CS call. The client also supports background mode, which means that it can receive calls and chat messages while in the background, and it indicates this to the user using the notification bar. For more information on the notification bar, see sections 1.5.3 Missed Chat Notification and 1.7.2 Missed Calls. Native address book integration is also supported, allowing an end user to choose between native CS calls and VoIP calls when placing a call using the native address book. 1.3 Contact List 1.3.1 General The Contacts tab only shows information about presence-enabled contacts. A presenceenabled contact can be any user with any type of XMPP address. It can be another Business Communicator user or a user with any other XMPP-compliant client. Furthermore, it can be a user from the same or a different service provider. Below the top tabs, there is a pill button that is used to display two lists: Buddies and Directory. The Buddies list provides all of the user s XMPP contacts, whereas the Directory list provides the company contacts in the BroadWorks enterprise directory. On the right side of the buttons, is the search icon. Note that for the Buddies list, the search icon is disabled. The Buddies list shows each contact s presence, name, presence status, as well as free text. A long press on a contact opens the context menu, whereas a short press opens the contact card. PAGE 3

Figure 2 Contact List The following Contact List management features are available: Start preferred communication via the context menu View a contact card Add, edit, or remove a contact Synchronize contacts with the Business Communicator PC client or other clients using XMPP (since the contacts in the Buddies list are stored on an XMPP server and are retrieved when the client logs in) PAGE 4

The context menu opens after a long press on a contact; the context menu contains the following options for the Buddies list: VoIP call Chat Contact card Delete contact Unsubscribe Figure 3 Context Menu for Buddies List Contact PAGE 5

1.3.2 Add Contact Manually There is an add contact icon, and also the hard key menu has an option for Add. Pressing add opens a contact card in edit mode (that is, adding contact). The add contact view shows the required text fields to add an XMPP contact to a Buddies list. The view can be cancelled by pressing the back button or Cancel. The presence subscription that automatically results, after adding a contact, is always bi-directional for simplicity. After the invited contact accepts the presence subscription, both are allowed to see each other s presence. Figure 4 Adding Contacts In addition, when others are adding the user as a contact, a presence authorization popup dialog appears to allow the user to accept or reject the presence invitation. Accepting the invitation adds the inviting person to the contact list (as shown in the following figure). PAGE 6

Figure 5 Presence Authorization Pop-up Dialog 1.3.3 BroadWorks Enterprise Directory Search The client supports an enterprise directory search of the BroadWorks enterprise directory. This is available in a separate pill button in the Contacts tab, where the search function is enabled. Tapping the search icon opens the search view, and after the search, the enterprise directory search results list displays the name and number. There are also filtering options to search a native address book, an enterprise directory, or both. Note that an XMPP contact list cannot be searched. The default starting screen for a search appears when the user presses the search icon. Typing any of character starts the filtering process through contacts from both the XMPP contacts and Directory listing. Pressing the back key minimizes the keyboard, hides the search bar, and empties the search result. The following figure shows an example of search results: PAGE 7

Figure 6 Enterprise Directory Search Results There is no hard key menu in the directory search results listing view. A long press on the name opens context menu and hides keyboard but keeps search bar with characters while a short press opens the contact card. The context menu contains the following options for the Directory list: VoIP call Contact card PAGE 8

1.3.4 Contact Card A contact card from a Buddies list shows the presence, name of the contact, presence text, as well as, free text. The contact s phone number appears and then pressing either the voice call icon makes a voice call to that contact. Tapping the Chat button opens the Instant Messaging (IM) view with that contact while the hard key menu shows the Remove and Edit buttons. Tapping Remove confirms the action from the user through a pop-up dialog while Edit opens the edit mode. Figure 7 Buddies List Contact Card PAGE 9

In the enterprise directory search results list the contact card is a different, as shown in the following figure. The contact card shows the contact s name and phone number. The Call buttons can be used to choose what type of a call is placed. Note that Chat is not available. For a Directory contact, there is the Add to contacts option, (which opens the native phone book Add Contact view), as well as an Add to IM buddies option. Figure 8 Enterprise Directory Search Contact Card PAGE 10

1.4 Presence Presence status for a contact is shown in the contact list. However, to see a contact s presence status, the contact must have an XMPP address. Users can set their own presence status from the Chat tab. They can select a presence icon (avatar), set their presence status, as well as, type a personal free-text message. A user s Own presence status can be selected from the pop-up menu available when pressing the user s Own status icon at the bottom left-hand corner of the screen. The user can choose the presence status from the following alternatives: Online Chatty Away Extended Away Busy Offline The hard key menu contains the Start new chat, Mark all as Read, Settings, About, and Sign out options. The Settings option opens a new view with the settings the user can toggle on or off. For more information about call settings, see section 1.9 BroadWorks Service Management and for general settings, see section 1.11.6 Settings. The About screen shows information about the client, for example, the version number Sign out exits and closes the client. Figure 9 Presence PAGE 11

Tapping the pencil icon beside the free text field makes the keyboard appear and then the user can change the free text by editing it and then tapping the Update button to save it. The text is updated immediately and appears below the display name. In addition, the user s phone number is shown below the editable fields. Figure 10 Personal Message PAGE 12

1.5 Instant Messaging 1.5.1 Chat Instant messaging with a contact can be started from the contact list by simply selecting the chat item from the context menu or from the contact card, as well as going to the Chat tab. Having selected the contact to chat with, the user can start typing the first message. The IM view shows the name of the recipient on the top bar and there is a presence icon before the name. The recipient is presented in the bubble from the left and the user is presented in the bubble from the right. Smileys can be added to messages by typing the corresponding character codes and by selecting from the smiley icon (the smiley is displayed graphically in the message area). Figure 11 Chat View (Depends on Device This View is from Samsung Galaxy) PAGE 13

1.5.2 Chat Tab The Chat tab shows all chats made with any contact since the last login. If user A chats with user B many times, their discussions appear as one item in the list. Tapping the name opens the chat view (IM view) where new messages can be typed, (and note that old messages are not shown in this release). New incoming messages are indicated with an icon to the right of the name. The icon remains next to name until the message is read. A long press on a contact opens the context menu (same as for the Buddies list). The chats are listed so that newest ones are always on top. The chats are not in alphabetical order and are always listed with the most recent first. In the hard key menu, the option is Close chat. Figure 12 Chat Tab PAGE 14

1.5.3 Missed Chat Notification All notifications (missed calls, new messages, and so on) are handled through the notification bar, and a new message (IM) is also displayed on the notification bar. If there are many new messages from different senders, tapping on this item opens the chat view. If there is only one or many new messages from the same sender, tapping the item opens the IM view. Figure 13 Missed Chat PAGE 15

1.6 XMPP Multi-Device Business Communicator Release 9.3.0 provides support for users with multiple devices, following the XMPP specifications. This is comprised of several features as follows: Chat invitations sent to the user are received in 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. Getting 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 sharing presence invitation in one client is also recognized by another client and both clients start receiving the presence updates. A new presence subscription made in one client is recognized in another, with the latest after the next login. 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 of the same user, it only shows one request to the user. Removing a contact from the contact list in one device is recognized in another client, with the latest after next the login, and the contact list is updated (contact removed) in the other client as well. If a user has many devices, each device can have a different status when shown to the end user. However, watchers in the contact list always see the updates in the following priority order: Busy Chatty Online Away Extended away Offline For example, this means that if one client publishes a Busy status and another client publishes another status, watchers see the user as Busy. PAGE 16

1.7 Voice Calls 1.7.1 General A voice call can be started from the contact list by selecting the item from the context menu, or by using the contact card, or from the call history. Another way is to use the Call tab, as shown in the following figure. The Call tab displays a dial pad and a text field that is used to enter numbers. There are two buttons below the dial padthe top text field also has a delete button that when pressed, deletes one character at a time. Figure 14 Call Tab After pressing either of the call buttons, a call dialog appears and the contact s phone starts ringing. PAGE 17

The following call control actions are available for a voice call: Adjust the volume Generate DTMF tones with the dial pad Mute the microphone Hold the call Hang up the call Start conference call Transfer call Figure 15 Audio Call An incoming call is indicated with a ring tone and a notification in the top bar PAGE 18

1.7.2 Missed Calls If a user has missed calls, then the notification bar in Android displays a note. By clicking a missed call, the user is directed to the Call History screen, as shown in the following figure. All notifications (missed calls, new messages, and so on) are handled through the notification bar. Figure 16 Missed Calls PAGE 19

1.7.3 Message Waiting Indicator (MWI) and Voice Mail Access If a user has pending voice mails (VM), then the notification bar in Android displays an icon and text You have XX pending voice mail messages. By clicking the voice mail notification, the application dials the voice mail access number directly and the user can listen to the VM messages. All notifications (missed calls, new messages, and so on) are handled through the notification bar. Figure 17 Voice Mail Notification PAGE 20

Voice mail is also accessible with a long-press of the dial pad key 1 (similar to a regular mobile keyboard). When voice mail messages are available, the key 1 changes its color. In addition, it shows the VM notification in the global notification area, described previously. The number of new voice mails changes depending on how many are opened or are new. The VM icon in the notification area has a badge associated with it, which shows the number of new messages. Figure 18 Call Tab Enter Number PAGE 21

1.7.4 Business Line Call-Back and Call-Through Mobile Communicator allows the user to originate a circuit-switched call using their business line identity. This is done using the basic call-back functionality on BroadWorks or the call-through functionality available with BroadWorks Mobility. Basic call-back is only available if the user has BroadWorks Anywhere or Remote Office assigned. The application checks to see whether one of these two services is provisioned with a phone number that matches the mobile number. And if it is provisioned this way, it provides the user with the option to make calls using the call-back feature. Call-through functionality is available if the Mobility service is assigned to the user s BroadWorks profile. Call-through provides a more natural dialing experience. When a call is placed in this mode, the client communicates transparently with BroadWorks to obtain a temporary Intermediate Routing Number (IMRN). The client then calls the IMRN and connects the user directly to the destination identifying the call with the user s business line identity. Figure 19 Business Line Call-Back and Call-Through PAGE 22

1.7.5 Contact Name Lookup for Incoming Calls and Call Logs Whenever the incoming call does not have a calling name associated with it, Mobile Communicator can perform a local contact search. If the number matches one of the contacts on the mobile phone contact list, the name is shown on the incoming call screen along with the alert. Whenever the user retrieves their call logs/history and the call log does not have a calling name associated with it, the client does a lookup in the local contacts and populates the name if a match is found. 1.7.6 Three-Way Calling Business Communicator supports network SIP-based conference calls with up to three participants (Three-Way). While on a two-way call, the user can add a third party by using the Conference button. This opens the address book on the device to search for and select the new participant. Figure 20 Three-Way Calling (Adding Third Party) The supported mode is Blind Conference calling. The third party receives a call and is joined to the conference automatically when they pick up. The Attended Conference mode, which prompts the third party to join or decline, is not supported in this version. Once the conference is established, the participants are shown on the Device screen. PAGE 23

Figure 21 Three-Way Calling (Selecting Conference) PAGE 24

Figure 22 Three-Way Calling (Participants) PAGE 25

1.7.7 Call Transfer The client supports transferring VoIP calls to another party. Two modes of transfer are supported: Attended Call User selects Talk First from the menu and a second call is placed with the selected contact. If the call is successfully established, the user can talk with the third party privately, before completing the transfer, by pressing the Transfer call button again. Unattended Call User selects Transfer from the menu, the second party is transferred to the selected contact, and the current user is dropped from the call. Figure 23 Transfer PAGE 26

1.8 BroadWorks Call History The client supports the basic BroadWorks Call History. Using a drop-down menu, the Call History can be set to show all calls, received calls, dialed calls, and missed calls. In the list of calls, there are symbols indicating if a call was incoming or outgoing. The list of the call items consists of an icon showing what kind of call it was (a green arrow means incoming, a blue arrow means outgoing, and a red arrow means missed). It also shows the name, number, Unavailable status for the caller and below the name it shows the number, if available. To the right, the user can see the date called and the time the call was initiated. Tapping an item on the list opens the contact card where a call can be made to that number. Figure 24 BroadWorks Call Logs PAGE 27

1.9 BroadWorks Service Management The client supports the following Service Management features allowing supplementary services to be turned on or off using the native client Preferences window: Call Forwarding Do Not Disturb Remote Office BroadWorks Anywhere Remote Office Hide Caller ID Simultaneous Ring Personal Own Phone Number Figure 25 BroadWorks Service Management on Android PAGE 28

1.10 Call Modes The client supports several modes for making the outgoing calls. These are controlled through Settings/Call Settings/Outgoing Calls. Calls placed via mobile Calls are placed using the Android native dialer via the mobile CS network. Calls placed via Call-Back service Call are made using the BroadWorks Call-Back service. This works with BroadWorks Release 17.0 and higher via the BroadWorks Anywhere or Remote Office setting. Calls placed via VoIP Calls are made using BroadWorks VoIP service. Always Ask This displays a prompt to the user when initiating a new call to select the desired mode Call-through functionality is available if the Mobility service is assigned to the user s BroadWorks profile. Call-through provides a more natural dialing experience. When a call is placed in this mode, the client communicates transparently with BroadWorks to obtain a temporary IMRN. The client then calls the IMRN and connects the user directly to the destination identifying the call with the user s business line identity. The default mode after installing the client is the VoIP mode. Figure 26 Call Modes PAGE 29

1.11 Other Features 1.11.1 Version Control Version control is supported using Android market mechanisms. When a new release is available, the old version is removed from the market place and users of the previous version are notified about the update possibility. 1.11.2 Privacy Management Business Communicator supports authentication with a user name and password for different services and servers requiring authentication. For convenience, the end user can save their user name and password for different realms. When an end user adds a contact to the contact list, those contacts receive a New Subscriber dialog asking whether they will allow the end user to see their presence or not. This information is stored in the contact s presence policies. At any time, the user can edit the presence policies selections per contact. They are stored on the server. However, this feature requires a compatible presence server. 1.11.3 Help Pages The client supports a web-based help that can be launched from Preferences. 1.11.4 Firewalls and NATs The client supports rport (RFC 3581) for NAT traversal and also to use the client behind a firewall. However, the client is assumed to be used mainly with a session border controller (SBC) that also provides support for NAT traversal for several key features, such as calling, which are currently unlikely to work without SBC. 1.11.5 Automatic Sign In 1.11.6 Settings The user can choose to automatically sign in with Business Communicator with a default account when the client is started. Together with the functionality to automatically start Business Communicator at system start up, this makes it easy for the user to remember to sign in and be available for communication. The Settings view lists the following items, which can be configured by an end user: Language Remember password Sign in automatically, (which is disabled until Remember Password is checked) Call settings (for information about BroadWorks Service Management, see section 1.9 BroadWorks Service Management) Credentials BroadWorks Mobility settings PAGE 30

Figure 27 Settings View PAGE 31

2 System Requirements Business Communicator Release 9.3 for Android can be run on any Android 2.2, 2.3, 3.2, and Android 4 device in the market today. While it is possible to also run the client on Android 2.1, to some extent there are some platform shortcomings, for example, with camera handling, which causes that operating system (OS) version to be unsupported in this release. Android 3.2 has not yet been fully validated, although no major issues have been identified. The client has been validated on the following reference devices: Samsung Galaxy SIII Samsung Galaxy SII Samsung Galaxy S Samsung Galaxy S2 Samsung Galaxy Nexus Samsung Nexus S Motorola Droid Bionic Motorola Droid X Motorola Droid 2 Sony Xperia PLAY Sony Xperia S Huawei T20 HTC Thunderbolt HTC Vivid HTC Sensation PAGE 32