The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco Jabber for iPhone and iPad is available from the Apple App Store.
Cisco supports Cisco Jabber for iPhone and iPad on the following iOS devices:
The device must be able to access the corporate network using Wi-Fi or VPN.
iOS support: iOS 7
iPhone: supported (optional)
iPad: Supported (optional)
For a successful deployment, you must ensure that your environment meets the Cisco Jabber for iPhone and iPad software requirements.
Cisco Jabber for iPhone and iPad supports the following on-premises servers:
The DVO-R feature is only available on iPhone and it requires:
Note |
Cisco Unified Communications Manager IM and Presence is formerly known as Cisco Unified Presence. |
Cisco WebEx Meetings Server version 1.5 or later
The Apple iOS On-Demand VPN feature requires certificate-only authentication. If you set up the a (ASA) without certificate-only authentication, the user must manually initiate the AnyConnect VPN connection as needed.
The iOS device must be able to access the corporate network, servers, and telephony endpoints using a VPN client, such as Cisco AnyConnect Secure Mobility Client.
Cisco Jabber for iPhone and iPad supports the following cloud-based servers:
You can use the following directory servers with Cisco Jabber for iPhone and iPad.
Note |
Cisco Unified Communications Manager User Data Services (UDS) is not supported for directory integration in this release. |
Use one of the following sources for Lightweight Directory Access Protocol (LDAP):
Cisco WebEx Messenger Contact Service
Cisco Jabber for iPhone and iPad is compatible with the VoiceOver screen reader. Users who require screen readers should always use the most recent version to ensure the best possible user experience.
You can navigate Cisco Jabber for iPhone and iPad using Assistive Touch.
Minimum requirement for low-bandwidth availability: G.729a.
Users can turn Low Bandwidth mode on and off in the client settings if they experience voice quality issues.
Normal mode supports G.711 and G.729a.
Low Bandwidth mode supports G.729a only.
H.264/AVC
Note |
Cisco does not support visual voicemail with G.729. However, users can access their voice messages using G.729 and the Call Voicemail feature. |
If you deploy Phone Services, the mobile device must be able to connect to the corporate network using voice-ready Wi-Fi.
For optimal user experience when using Cisco Jabber over your corporate Wi-Fi network, Cisco recommends that you:
For more information, see:
Bluetooth use can cause voice quality and connectivity issues.
If users connect to the network remotely, the mobile device must be able to connect to the corporate network using a solid, high-bandwidth VPN connection. Video and audio quality is dependent on connection quality and cannot be guaranteed.
The client uses the ports and protocols listed in the following table. If you plan to deploy a firewall between the client and a server, you must configure the firewall to allow these ports and protocols.
Note |
There are no TCP/IP services enabled in the client. |
Port | Protocol | Description |
---|---|---|
Inbound | ||
16384 to 32766 | UDP | Receives Real-Time Transport Protocol (RTP) media streams for audio and video. You set these ports in Cisco Unified Communications Manager. |
Outbound | ||
69 | UDP | Connects to the Trivial File Transfer Protocol (TFTP) server. |
6970 | HTTP | Connects to the TFTP server to download client configuration files. |
80 | TCP (HTTP) |
Connects to services such as Cisco WebEx Meeting Center for meetings or Cisco Unity Connection for voicemail. |
389 | UDP / TCP | Connects to an LDAP directory service. |
3268 | TCP | Connects to a Global Catalog server for contact searches. |
443 | TCP (HTTPS) |
Connects to services such as such as Cisco WebEx Meeting Center for meetings or Cisco Unity Connection for voicemail. |
636 | LDAPS | Connects securely to an LDAP directory service. |
3269 | LDAPS | Connects securely to the Global Catalog server. |
5060 | TCP |
Provides Session Initiation Protocol (SIP) call signaling. |
5061 | TCP | Provides secure SIP call signaling. |
5222 | TCP (XMPP) |
Connects to Cisco Unified Presence or Cisco Unified Communications Manager IM and Presence for instant messaging and presence. |
5269 | XMPP | XMPP federation. |
8191 | TCP | Connects to the local port to provide Simple Object Access Protocol (SOAP) web services. |
8443 | HTTPS | 8443 is the port for web access to Cisco Unified Communications Manager and includes connections for the following: |
16384 to 32766 | UDP | Sends RTP media streams for audio and video. |
53 | DNS | Provides hostname resolution. |
3804 | TCP | Issues Locally Significant Certificates (LSC) to IP phones. This is the listening port for Cisco Unified Communications Manager Certificate Authority Proxy Function (CAPF) enrollment. |
The device COP file adds the TCT/TAB device type to Cisco Unified Communications Manager . To obtain the device COP file, do the following:
Learn about audio and video performance for Cisco Jabber for iPhone and iPad.
The following data is based on testing in a lab environment. This data is intended to provide an idea of what you can expect in terms of bandwidth usage. The content in this topic is not intended to be exhaustive or to reflect all media scenarios that might affect bandwidth usage.
The following table describes bit rates for audio:
Codec | Codec bit rate (kbits per second) |
Network Bandwidth Utilized (kbits per second) |
---|---|---|
g.711 | 64 | 80 |
g.722.1 | 32 | 48 |
g.722.1 | 24 | 40 |
g.729a | 8 | 24 |
Resolution | Pixels | Bit rate (kbits per second) with g.711 audio |
---|---|---|
w144p | 256 x 144 | 290 |
w288p | 512 x 288 | 340 |
w360p | 640 x 360 | 415 |
You specify the maximum payload bit rate in Cisco Unified Communications Manager in the Region Configuration window. This maximum payload bit rate does not include packet overhead, so the actual bit rate used is higher than the maximum payload bit rate you specify.
The client uses the maximum audio bit rate.
The client allocates the remaining bit rate as follows: The maximum video call bit rate minus the audio bit rate.
Upload speed | Audio | Audio + Interactive Video (Main Video) |
---|---|---|
125 kbps under VPN |
At bandwidth threshold for g.711. Insufficient bandwidth for video. Sufficient bandwidth for g.729a and g.722.1. |
Insufficient bandwidth for video. |
290 kbps |
Sufficient bandwidth for any audio codec. |
256 x144 at 20 fps |
415 kbps |
Sufficient bandwidth for any audio codec. |
640 x 360 at 20 fps |
Note that VPN increases the size of the payload, which increases the bandwidth consumption.
The client uses video rate adaptation to negotiate optimum video quality. Video rate adaptation dynamically increases or decreases video bit rate throughput to handle real-time variations on available IP path bandwidth.
Users should expect video calls to begin at lower resolution and scale upwards to higher resolution over a short period of time. The client saves history so that subsequent video calls should begin at the optimal resolution.
Cisco Unified Communications Manager lets you define one port range for the client. The client divides this port range equally and uses the lower half for audio calls and the upper half for video calls. For example, you define a port range of 1000 to 3000 in Cisco Unified Communications Manager. The client uses a port range of 1000 to 2000 for audio calls and a port range of 2000 to 3000 for video calls.
To access the SIP Profile Configuration window, select .
The Start Media Port field defines the lowest port available to the client. The Stop Media Port field defines the highest port available. See the SIP Profile Configuration topic in the Cisco Unified Communications Manager documentation for more information.
Users can launch the client from web browsers to perform one of the following tasks:
The following table lists the cross-launch URLs that you can use in third-party applications to start Cisco Jabber conversations.
Function | Cross-Launch URL | Prerequisites |
---|---|---|
Call a phone number | ciscotel://<phone_number> |
Cisco Unified Communications Manager account |
Start a chat session | One of the following accounts: |