Limitations and Restrictions in Cisco Jabber for iPhone and iPad

Document created by Cisco Documentation Team on Dec 8, 2015Last modified by Nisha Uthaman on Aug 10, 2017
Version 6Show Document
  • View in full screen mode
 

Limitations and Restrictions in Cisco Jabber for iPhone and iPad

Limitations and   Restrictions

All    Platforms

       
  •      

    Due to a     defect in Apple iOS version 9.3.x, in some versions of iPhone, the Cisco Jabber     client doesn't ring for an incoming call sometimes when the device is locked.     

         

  •      

    Cisco     Jabber for mobile clients do not show Favorite icon for users with Phone Only     account.     

         

  •      

    When Cisco     Jabber is suspended and receives an incoming call or chat, the iOS does not     wake up Cisco Jabber. The call or instant message appears on the device after     several minutes or when Cisco Jabber is taken to the foreground. As a     workaround, reset the network settings using      Settings > General >        Reset > Reset Network Settings in the iOS     device.     

         

  •      

    In phone-only     mode, if there are more than 2000 contacts in the native address book, then     there may be performance issues when loading the native address book.     

         

  •      

    Users can no     longer edit their Phone Services servers manually, except when they are in     hybrid cloud mode. In hybrid deployments, administrators can configure the     Phone Services servers to be editable.     

         

  • The first usage of Secure     Phone functionality must be on the corporate network or VPN to ensure proper     certificate installation.    
  • Voice recognition for voicemail PIN is highly sensitive to the background noise and may interpret background noise as user input when the user doesn't input anything. Refer to System Administration Guide for Cisco Unity Connection to disable this function. https://www.cisco.com/c/en/us/support/unified-communications/unity-connection/products-maintenance-guides-list.html    
  • Certificate validation     windows pop up when the certificate on Cisco Unified Communications Manager is     issued by an intermediate certificate authority. Use a certificate that is     signing with the root rather than an intermediate certificate authority.    
  •      

    From 10.5     release onwards, all the Cisco Jabber account related files, including     Configuration, Contacts, Credentials, History, Logs, Photo and so on, are not     backed up on the iCloud and iTunes due to privacy reasons.     

         

  •      

    Creating     and Configuring Devices for Users in Cisco Unified Communications Manager 11.0     — If you are creating devices for users in Cisco Unified Communications Manager     11.0, you can now specify a key order as RSA Only, EC Only, EC Preferred, or     RSA Backup. However, the EC Only option is not currently supported by Cisco     Jabber, and if you select it, the client fails to connect to the server.     

         

  •      

    With Jabber     running in the background, if users try moving between networks; for example,     from WiFi to to 3G, the client disconnects from the servers. It can take up to     11 minutes to reconnect and can lead to missed calls.     

         

  •      

    There is a     known issue with signing into Cisco Jabber for some users who have migrated to     Common Identity. If users receive an Incorrect user name or password error     message when entering their username and password, see the following knowledge     base article,            https://cisco-support.webex.com/guest/articles/en_US/Troubleshooting/WBX000019555/myr=false.         

         

  •     

    The UDS proxy feature does work with OpenLDAP. This is a Cisco     Unified Communications Manager limitation. You can only configure UDS proxy     feature when Microsoft Active Directory is used.    

        

    

iPhone

         
  •      
    Due to some     limitations when Cisco Jabber for iPhone and iPad is running on iOS, Configure     the Single Number Reach (SNR) feature within Cisco Unified Communications     Manager for users that require 100% reliability in call notifications. The     limitations include:     
    •       

      iOS may       shut down Cisco Jabber and other applications that are running in the       background to preserve resources. While the client attempts to relaunch, there       is a possibility that calls may be missed.      

            

    •       

      The       device sometimes switches connection from the Wi-Fi data network to the mobile       voice network while the device is in Sleep mode. Incoming calls may be missed       due to this issue. To prevent this issue, go to the iPhone Settings and turn       off        Cellular Data or alternatively turn on        SNR.      

            

    •       

      The VPN       can disconnect when Connect-On-Demand is enabled and the user changes networks.       Cisco Jabber for iPhone and iPad may take up to 11 minutes to reconnect through       the VPN. This issue can lead to missing incoming calls. After Cisco Jabber for       iPhone and iPad reconnects, users who have voicemail enabled in their account       receive voicemail notifications for any missed calls that went to voicemail. To       minimize the time to reconnect, users can bring the app to the foreground after       changing connection environments.      

            

          
         
  •      

           Cisco WebEx Meetings— If the meeting siteType is ORION, then Cisco Jabber for iPhone and iPad cannot start WebEx Meeting over Expressway for Mobile and Remote Access network.

         

  •      

    If Cisco Jabber on iPhone is unable to reach the primary subscriber due to packet loss, it does not failover to secondary CM node. For more information, see CSCux83785.

         

  •      
    If you are     setting up Dial via Office - Reverse (DVO-R) on Cisco Unified Communications     Manager consider the following:     
    •       

      The       feature only applies to iPhone; it is not supported on iPad or iPod Touch       devices because it requires that the device can access a mobile network.      

            

    •       

      You can       make DvO-R calls over Expressway for Mobile and Remote Access when you are       outside corporate network. DVO-R is supported over Cisco Expressway X8.7 and       Cisco Unified Communications Manager 11.0(1a)SU1.      

            

    •       

      DVO       enabled devices may encounter issues registering with Cisco Unified       Communications Manager 8.6 and above. Resetting the device from the Cisco       Unified Communications Manager administrative interface fixes this issue.      

            

    •       

      The       feature requires Cisco Unified Communications Manager Release 8.6.2 SU4, 9.1.2,       or 10.x.      

            

    •       

      The       feature cannot be used in conjunction with the Secure Call feature. Secure       calls cannot be established if DVO-R is enabled.      

            

    •       

      Due to a       limitation with Cisco Unified Communications Manager, if the user places a       DVO-R call to an invalid phone number over a SIP trunk, the user hears several       seconds of silence instead of an audio message stating the number was invalid.      

            

          
         
  •      

    If the user     is on a Cisco Unified Communications Manager call and receives an incoming     mobile call, iPhone starts ringing and prompts the user to answer or decline     the mobile call. At the same time, the Cisco Unified Communications Manager     call on Cisco Jabber goes on hold automatically.     

         

  •      

    To ensure that     you do not miss incoming Cisco Jabber chats and calls, go to      iOS       Settings > Notification Center and check that the     Cisco Jabber sound setting is turned on.     

         

  •      

    If you receive     a Cisco Unified Communication Manager call, while placing a VoIP call, Cisco     Jabber for iPhone and iPad sends the incoming call to voicemail. If you do not     have voicemail, Cisco Jabber for iPhone and iPad ignores the call.     

         

  •      

    The maximum     number of participants for ad-hoc conferences is limited to three; this is the     maximum number of calls for TCT devices. The maximum participants for ad-hoc     conference is configured on Cisco Unified Communication Manager in      Service Parameter       Configuration > Clusterwide Parameters > Maximum Ad Hoc Conference       Required.     

         

  • Voice and video quality     over non-corporate Wi-Fi or mobile data networks cannot be guaranteed.    
  •      

    The quality of     video calls varies depending on the network connection. Cisco Technical     Assistance Center (TAC) cannot troubleshoot video quality when you use 3G     networks to connect Cisco Jabber for iPhone and iPad with Cisco AnyConnect     Secure Mobility Client or another VPN client.     

         

  •      

    If you receive     an incoming call on your iPhone, the iPhone automatically disables the     microphone for all other applications, and there is no time to inform your     current caller that you need to take another call. If you accept the new     incoming call, your Cisco Jabber for iPhone and iPad Cisco Unified     Communications Manager call is automatically placed on hold, and you cannot     return to it until you end the iPhone call. To work around this issue, decline     the call and then tap Resume so that your current caller can hear you again. If     your device is locked, quickly press the On/Off Sleep/Wake button twice to     decline the call, and then tap Resume.     

         

  • SIP Digest Authentication     is not supported.    
  •      

    Cisco Unified     Communications Manager as a directory source is capable of scaling to 50% of     the device capacity that a Cisco Unified Communications Manager node can     handle.     

         

  •      

    When the     device is in Do Not Disturb (DND) mode and locked, then it vibrates upon     receiving a Cisco Jabber call.     

         

  •     

    With iOS 10 and Jabber 11.8, you cannot receive call notifications     on Apple Watch because CallKit can’t work with Apple Watch. This is an Apple     iOS limitation.     

        

  •     

    When in the background for a few hours, Jabber relaunches without     notification.    

        

    

iPad

       
  •      

    When users     transition between networks, their availability status may not be accurate.     

         

  •      

    Cisco Jabber     for iPhone and iPad supports interoperability and optimal video quality with     Cisco TelePresence System (CTS) devices if you use a TelePresence or video     bridge to connect the devices. The number of devices that you can use for     joining a video call will be determined by the Multipoint Control Unit (MCU)     and settings defined for the conference bridge.     

          

    For the best     video experience when establishing a direct video call between Cisco Jabber for     iPhone and iPad and a CTS device, use the required versions and settings.     Otherwise, video quality in Cisco Jabber for iPhone and iPad is impacted;     resulting video quality may include low frame-rate video with high or     increasing latency, lack of lip synchronization, or excessive video     artifacting. For more information, see      CSCtx47090.     

           

             
    Required versions and settings for CTS interoperability       
    VCS call control environment:        

    All CTS devices must be using 1.9.1(68) or a later firmware         version.        

            
    Cisco Unified Communications Manager call control environment:        
    •          

      All CTS devices must be using 1.9.1(68) or a later firmware          version.         

                

    •          
      Create Media Regions for iPad and CTS by following these steps:                  
      1.            

        Provision two media regions with the first region for CTS using           a maximum video call bit rate of 32000 Kbps and second region for iPad using a           maximum video call bit rate of 768 Kbps.           

                   

      2.            

        Create a region relationship from the CTS region to the iPad           region, described in step 1, using a maximum video call bit rate of 512 Kbps.           

                   

                
                
            
    To verify your VCS firmware and hardware codec versions, check        the Device information screen in the Cisco TelePresence System Administration.       
          

    Consult the     Cisco Unified Communications Manager Administration documentation for details     about setup.     

         

  •      

    You cannot     block contacts who are within your own organization.     

         

  •      

    You cannot     join a conference call if the call is placed by a Cisco WebEx Messenger user     from a group chat started on his or her computer.     

         

  •      

    If you     delete a group of contacts on another device other than an iPad, they may still     appear in Cisco Jabber for iPhone and iPad. You will need to sign out and sign     in for the changes to take effect.     

         

  •      

    If you start     an action, such as signing in or tapping      WebEx Meeting to start a meeting, and then bring     Cisco Jabber for iPhone and iPad to the background before the action is     completed, you cannot successfully complete the action.     

         

  •      

    If you tap      WebEx Meeting to start a meeting, a meeting     invitation is sent when either the meeting starts or 30 seconds has elapsed.     

         

  • When on a Cisco Jabber     call and you put Cisco Jabber to the background, sometimes the call indicator     will show Cisco Jabber recording, depending on the iOS versions.    
    

Performance and Behavior Notes

Multiple Resource Login

When a user signs in to multiple instances of the client at the same time, the chat feature behaves as follows:
  • The first incoming chat message is sent to all the clients.
  • The first client to reply to the incoming chat message gets all the subsequent messages. The other clients do not get these subsequent incoming messages.
  • If the client does not use the chat feature for 5 minutes, the next incoming message is sent to all the clients again.
 

Attachments

    Outcomes