cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Cisco Community Designated VIP Class of 2020

772
Views
0
Helpful
5
Replies
Highlighted
Contributor

Galaxy S5 Jabber for Android 9.6.1 and on-premise IMP 10.0.1 ?

The release notes state Cisco hasn't tested Jabber for Android 9.6.1 with the Samsung Galaxy S5 .

 

Can anyone state they have used Jabber for Android 9.6.1 with the Galaxy S5 with IMP 10x inside their network?

 

We are on WiFi and see the following error message in the log file at sing in.  The user is unable to connect;

 

 

Here is the Jabber log from Android;

05-30 16:10:40.023 23239 26604 I         :     Ucm 90 Config Version: 0.10.(0.1-snapshot)
05-30 16:10:40.023 23239 26604 I         : *****************************
05-30 16:10:40.023 23239 26604 I         : INFO [0x7e6ac028] [m9-config/src/UcmConfigQueryImpl.cpp(68)] [csf.config] [UcmConfigQueryImpl] - using SRV Records
05-30 16:10:40.023 23239 26604 I         : INFO [0x7e6ac028] [/Ucm90ConfigProviderWrapperImpl.cpp(126)] [service-discovery] [mapUcm90ProviderOperationToUcm90ConfigQueryOperation] - Mapping CSFUnified Ucm90 operation: ONLY_USE_CACHE to ucm90 library operation: ONLY_USE_CACHE
05-30 16:10:40.023 23239 26604 W         : WARN [0x7e6ac028] [9-config/src/UcmConfigQueryImpl.cpp(161)] [csf.config] [fetchXmlFileSet] - Cache information unavailable.
05-30 16:10:40.023 23239 26604 W         : WARN [0x7e6ac028] [9-config/src/UcmConfigQueryImpl.cpp(275)] [csf.config] [fetchXmlFileSet] - No information available after doing a fetch.
05-30 16:10:40.023 23239 26604 I         : INFO [0x7e6ac028] [9-config/src/UcmConfigQueryImpl.cpp(280)] [csf.config] [fetchXmlFileSet] - Time taken to complete the ucm-config library fetchXmlFileSet(): 0 seconds.
05-30 16:10:40.023 23239 26604 I         : INFO [0x7e6ac028] [r/Ucm90ConfigProviderWrapperImpl.cpp(75)] [service-discovery] [authenticate] - Ucm90 Library Returned with Code FAILED_TO_READ_THE_CACHE
05-30 16:10:40.023 23239 26604 I         : INFO [0x7e6ac028] [DnsServiceResourceRecordProvider.cpp(53)] [csf.config] [deInitialize] - CSF Provided DNS Library De-initialized!
05-30 16:10:40.023 23239 26604 I         : INFO [0x7e6ac028] [gretriever/Ucm90ConfigRetriever.cpp(108)] [service-discovery] [retrieveConfigImpl] - resultCode FAILED_CONFIGURATION_ERROR
05-30 16:10:40.023 23239 26604 W         : WARN [0x7e6ac028] [ver/Ucm90ConfigRetrievalManager.cpp(269)] [service-discovery] [mapUcm90ResultCodeToServiceDiscoveryResult] - CUCM Result : Failed - CUCM connection error.
05-30 16:10:40.023 23239 26604 I         : INFO [0x7e6ac028] [ationdiscovery/DiscoveryLogUtils.cpp(38)] [service-discovery] [LogServiceInformationVect] -
05-30 16:10:40.023 23239 26604 I         : No Service Discovery DNS records have been found.
05-30 16:10:40.023 23239 26604 I         : INFO [0x7e6ac028] [vices/impl/DiscoveryHandlerImpl.cpp(277)] [service-discovery] [evaluateServiceDiscoveryResult] - ServiceDiscoveryHandlerResult return code FAILED_UCM90_CONNECTION
05-30 16:10:40.023 23239 26604 I         : INFO [0x7e6ac028] [vices/impl/DiscoveryHandlerImpl.cpp(449)] [service-discovery] [handleFailedDiscoveryResult] - Handling failed discovery result.
05-30 16:10:40.033 23239 26604 I         : INFO [0x7e6ac028] [vices/impl/DiscoveryHandlerImpl.cpp(202)] [service-discovery] [getFallbackAuthenticatorId] - Looking for a fallback Authenticator.
05-30 16:10:40.033 23239 26604 I         : INFO [0x7e6ac028] [ore/ServiceDiscoveryConfigStore.cpp(165)] [service-discovery] [getValue] - ServiceDiscoveryConfigStore: getValue() found no value mapped to key: fallbackauthenticator
05-30 16:10:40.033 23239 23239 I         : INFO [0x40018154] [common/CertificateValidityCache.cpp(172)] [csf.cert] [clear] - Clearing accepted and rejected certificates from memory
05-30 16:10:40.033 23239 23239 W         : WARN [0x40018154] [vices/impl/DiscoveryHandlerImpl.cpp(484)] [service-discovery] [callOnFailedDiscoveryResultOnDispatcherThread] - Discovery Failure -> (id) name :: (1003) ServiceDiscoveryCannotConnectToCucmServer
05-30 16:10:40.033 23239 23239 W         : WARN [0x40018154] [vices/impl/DiscoveryHandlerImpl.cpp(487)] [service-discovery] [callOnFailedDiscoveryResultOnDispatcherThread] -
05-30 16:10:40.033 23239 23239 W         :
05-30 16:10:40.033 23239 23239 W         : ** Discovery has failed. Calling Callback! **
05-30 16:10:40.033 23239 23239 I JABBER.LIFECYCLE.ForceDiscoveryCallback: [OnDiscoveryFailed]
05-30 16:10:40.033 23239 23239 I JABBER.LIFECYCLE.ForceDiscoveryCallback: [OnDiscoveryFailed] error code = 1003
05-30 16:10:40.033 23239 23239 I JABBER.LIFECYCLE.ServiceDiscoveryManager: [updateServiceDiscoveryState] from DISCOVERING to FAILED
05-30 16:10:40.033 23239 23239 I JABBER.JABBER.SignInActivity: [stopLoading]
05-30 16:10:40.033 23239 23239 I JABBER.JABBER.SignInActivity: [dismiss progressDialog]
05-30 16:10:40.043 23239 23239 I         : INFO [0x40018154] [es/jcfcoreutils/src/ScopedTimer.cpp(166)] [scoped-timer] [pop] -
05-30 16:10:40.043 23239 23239 I         :  ** BEGIN TIMER TRACE **
05-30 16:10:40.043 23239 23239 I         :
05-30 16:10:40.043 23239 23239 I         :  ASYNC FLOWS CAPTURED:
05-30 16:10:40.043 23239 23239 I         :  DiscoveryHandler::Discover
05-30 16:10:40.043 23239 23239 I         :
05-30 16:10:40.043 23239 23239 I         :  -- Thread Id - 1073840468 --
05-30 16:10:40.043 23239 23239 I         :  00:00:00.000.015   + DiscoveryHandler::Discover
05-30 16:10:40.043 23239 23239 I         :  00:00:00.002.628   - DiscoveryHandler::Discover (00:00:00.002.613)
05-30 16:10:40.043 23239 23239 I         :  00:00:05.093.833   + DiscoveryHandler::callOnFailedDiscoveryResultOnDispatcherThread
05-30 16:10:40.043 23239 23239 I         :  00:00:05.093.848    + DiscoveryHandler::callOnAuthenticationFailedDiscoveryResultOnDispatcherThread_clearingcertcache
05-30 16:10:40.043 23239 23239 I         :  00:00:05.093.952    - DiscoveryHandler::callOnAuthenticationFailedDiscoveryResultOnDispatcherThread_clearingcertcache (00:00:00.000.104)
05-30 16:10:40.043 23239 23239 I         :  00:00:05.111.128   - DiscoveryHandler::callOnFailedDiscoveryResultOnDispatcherThread (00:00:00.017.295)
05-30 16:10:40.043 23239 23239 I         :
05-30 16:10:40.043 23239 23239 I         :  -- Thread Id - 2120925224 --
05-30 16:10:40.043 23239 23239 I         :  00:00:00.001.622   + DiscoveryHandler::DiscoverImpl
05-30 16:10:40.043 23239 23239 I         :  00:00:00.144.379    + ServiceDiscoveryHandler::Discover
05-30 16:10:40.043 23239 23239 I         :  00:00:00.233.598     + ServiceDiscoveryHandler::determineIsWebexCustomerFromCache
05-30 16:10:40.043 23239 23239 I         :  00:00:00.233.829     - ServiceDiscoveryHandler::determineIsWebexCustomerFromCache (00:00:00.000.231)
05-30 16:10:40.043 23239 23239 I         :  00:00:00.233.990     + ServiceDiscoveryHandler::makeUcm90BasedDiscovery
05-30 16:10:40.043 23239 23239 I         :  00:00:00.234.226      + ServiceDiscoveryHandler::saveServiceDiscoveryResult
05-30 16:10:40.043 23239 23239 I         :  00:00:00.234.262       + ServiceDiscoveryHandler::writeToCache
05-30 16:10:40.043 23239 23239 I         :  00:00:00.235.218       - ServiceDiscoveryHandler::writeToCache (00:00:00.000.956)
05-30 16:10:40.043 23239 23239 I         :  00:00:00.237.476      - ServiceDiscoveryHandler::saveServiceDiscoveryResult (00:00:00.003.250)
05-30 16:10:40.043 23239 23239 I         :  00:00:05.091.117     - ServiceDiscoveryHandler::makeUcm90BasedDiscovery (00:00:04.857.127)
05-30 16:10:40.043 23239 23239 I         :  00:00:05.092.152    - ServiceDiscoveryHandler::Discover (00:00:04.947.773)
05-30 16:10:40.043 23239 23239 I         :  00:00:05.092.173    + DiscoveryHandler::evaluateServiceDiscoveryResult
05-30 16:10:40.043 23239 23239 I         :  00:00:05.092.353     + DiscoveryHandler::handleFailedDiscoveryResult
05-30 16:10:40.043 23239 23239 I         :  00:00:05.095.831     - DiscoveryHandler::handleFailedDiscoveryResult (00:00:00.003.478)
05-30 16:10:40.043 23239 23239 I         :  00:00:05.095.842    - DiscoveryHandler::evaluateServiceDiscoveryResult (00:00:00.003.669)
05-30 16:10:40.043 23239 23239 I         :  00:00:05.095.852   - DiscoveryHandler::DiscoverImpl (00:00:05.094.230)
05-30 16:10:40.043 23239 23239 I         :
05-30 16:10:40.043 23239 23239 I         :  ** END TIMER TRACE **
05-30 16:10:40.053 23239 23239 E ViewRootImpl: sendUserActionEvent() mView == null

 

 

Everyone's tags (1)
5 REPLIES 5
Beginner

Could you confirm whether the

Could you confirm whether the CUCM server is configured as hostname, FQDN or IP Address. The latest version of Android client has issues in connecting when the server name is configured as hostname. It is Google defect.

Contributor

That fixed it! Under CUAdmin

That fixed it!

 

Under CUAdmin > System > Server we have hostname, not the FQDN or ip address.  I changed it to ip address, then utils system restart on the IM&P nodes.

Once I fixed that and the SIP Profile to SIP Profile for Mobile Devices they could connect with a Galaxy S3. 

Beginner

Great to hear that. Please

Great to hear that. Please rate helpful posts, and mark the thread as answered so that this will help others.

 

 

HTH

Nirmal Issac

Contributor

Under which setting chaning

Under which setting chaning from hostname to ip address would fix it?  I'm not clear if that is the problem I am hitting or not from the log file.

Under CCMAdmin > System > Server we are using ip address

Under User Management > User Settings > UC Service > CTI is IP addresses and IM&P is hostname

 

I recall changing from hostname to ip address might cause certificate trust warnings?

Cisco Employee

Hi JasonWhat about other

Hi Jason

What about other Android phones? Are they able to login?

There is an Android limitation https://code.google.com/p/android/issues/detail?id=8030

Android devices cannot resolve hostname , they can work with either FQDN or IP Address

Please try changing the hostname of your IM&P to either IP or Hostname under UC Service-->IM&P

To overcome the hostname issues on Android, we recommend the following:

Use FQDN on the CUPS/Cisco IM&P Cluster Topology page, use FQDN on the CCMCIP and TFTP server settings

To avoid any certificate warnings, it is recommended to have FQDN everywhere please refer http://www.cisco.com/c/en/us/support/docs/unified-communications/unified-presence/116917-technote-certificate-00.html

 

CreatePlease to create content
Content for Community-Ad
FusionCharts will render here