Limitations and Restrictions in Cisco Jabber for Android

Document created by Cisco Documentation Team on Dec 8, 2015Last modified by Manasa Boya on Aug 7, 2017
Version 15Show Document
  • View in full screen mode

 

Limitations and Restrictions in Cisco Jabber for Android


Limitations

  •   
    The following limitations apply to all devices:  
    •   

      Because of a limitation of Cisco Unity Connection, the voicemail server cannot display the URI for a missed call. This issue occurs if you decline an incoming Cisco Jabber call that was placed from a URI, and then that caller is diverted to voicemail. If the caller's contact information contains only a URI, the voicemail server displays the caller as Unknown. If the contact information contains a URI and a directory number, the voicemail server displays the directory number for that contact.   

         

    •   

      If you play music with a third-party application in the background, and make or receive a Cisco Jabber for Android video call, the music does not pause or resume after the video call ends. To work around this issue, you can open the third-party application to pause or resume the music.   

         

    •    

      If you make a Cisco Jabber for Android call using Expressway for Mobile and Remote Access over a 2G, 3G, or 4G network, you may experience audio quality issues.   

         

    •    

      If you use Cisco AnyConnect Secure Mobility Client, MobilePASS one-time password generator from SafeNet, and Cisco Jabber for Android on the same device, you may       experience problems due to compatibility issues between these applications. For example, during a Cisco Jabber for Android call, you may hear no audio or one-way audio, or you may experience delays if you transfer the call.   

         

    •    

      If you use Cisco Samsung AnyConnect Secure Mobility Client, use a version later than 4.0.01128. Earlier versions may cause connection problems.   

         

    •    

      Some users who have migrated to Common Identity server have an issue signing into Cisco Jabber. These users receive an "Incorrect username or password" error message when they enter their username and password. To resolve the issue, see knowledge base article.         

         

       
      
  •   
    The following limitations apply to Android OS 4.0 and later:  
    •    

      Because of a limitation of Android OS 4.0 and later, Cisco Jabber cannot register to Cisco Unified Communications Manager on some devices. Cisco is working with select device manufacturers to resolve this issue at the Android OS level.   

         

    •    

      Because of a limitation with Android OS 4.1.2 and later on some devices, you may experience issues if you perform the following steps:   

          

          

      After you complete these steps, the native Android phone application no longer shows you the dialog box that allows you to select another voice application. Instead, you can only make calls through the native Android Phone application.   

         

      1.     

        Call from the native Android phone application.

             

      2.     

        Select Jabber (or another voice application) from the dialog box.    

             

      3.     

        Select Always to indicate that you always want to use Cisco Jabber (or another voice application) to make calls.    

             

       
      
  •   

    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.  

      

  •    

    In a Mobile and Remote Access non-SSO environment, when Jabber loses its connection to the Cisco VCS Expressway server there is an interval of 120 seconds between sending connection requests. This is to prevent multiple requests to the server from multiple clients. During this 120-seconds interval, even if your network connection is active, Jabber remains inactive.

       

  •    

    There is an audio quality issue in Samsung devices with chipset Exynos 7580. The audio becomes unclear when the device screen is off. Here is the device list:

           

       
    •      

      Samsung Galaxy A3 2016

           

    •      

      Samsung Galaxy A5 2016

           

    •      

      Samsung Galaxy A7 2016

           

    •      

      Samsung Galaxy S5 Neo

           

    •      

      Samsung Galaxy J7

           

    •      

      Samsung Galaxy View

           

  •    

    In Samsung devices, when you install Jabber for the first time, Jabber is put in the unmonitored apps list automatically, which means it won't be put to sleep while running in the background. However, if you upgrade the Jabber version, you have to add it to unmonitored apps list manually.

       

 
 

Restrictions

The following restrictions apply to all devices:
  • HTTP basic SAML SSO authentication—Sign in fails when switching users with the Reset Jabber option. Reset Cisco Jabber, quit the application fully in the Android OS, and try again.

     

  • Because of the large number of third-party applications that support the tel:// URI feature, we cannot guarantee interoperability of this feature on all third-party applications. In some third-party applications, this feature allows you to click a tel:// link and select Cisco Jabber for Android to call.

     

  • When transferring a file, the filename cannot exceed 168 characters (including extension). If you attempt to send a file with a longer name, you are notified that you have exceeded 168 characters.

     

  • Security Survivable Remote Site Telephony (SRST) is not supported in Cisco Jabber for Android Release 10.6.

     

  • If the Cisco Unified Communications Manager version is 11.0 and later, and you don't accept an invalid certificate when prompted within 10 seconds, for some HTTPS connections, the function of your application may be affected. You may have some issues such as, not being able to download some configuration from the server, or not being able to connect to the phone service or the voicemail.

     

  • Only for users on SSO account Jabber stops working if the Android Webview is reset, upgraded, or restarted.

     

  • During file transfer, only files with JPEG file format are compressed.

     

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

     

 


Attachments

    Outcomes