Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1540
Views
0
Helpful
4
Replies

Jabber 9.0.2 Samsung G2 Android 4.0.3 CUCM 7.1.5 Working 0.0.0

Charles Rayer
Level 1
Level 1

‎10-25-2012 07:27 AM - edited ‎03-16-2019 01:53 PM

I am trying to get jabber working on Android phones.

Call Manager 7.1.5

I've got it working for iPhones, I have it working for the Samsung Note 2 running Android 4.1.1

But I can't get it working with the Samsung Galaxy 2. I've tried with Jabber versions 9.0.2 and 8.6, but they both don't complete the setup process.

I get the message:

"Please check your Internet Calling Settings and try again. If the problem persists, contact your system administrator"

I've tried with a unique (BOTJAMES) account, also with a known good account (BOTCHARLES), but both fail. I've tried the BOTJAMES account in the Samsung Note 2 and it works fine.

As far as I can see it's purely the device, which is running Android 4.0.3

I looked at the compatible devices in the installation notes of Jabber and it didn't even mention the Note 2 or Android 4, so I discounted them as badly out of date.

Thanks for reading, hope you can help

Labels:
0 Helpful
4 Replies 4

Charles Rayer
Level 1
Level 1

‎10-29-2012 04:44 AM

I've now tried with 2 different Galaxy 2's just in case there was a random fault with one, but they both fail to connect.

So has literally no-one got this working or is able to comment? Really?

0 Helpful

barry
Level 7
Level 7
In response to Charles Rayer

‎10-29-2012 06:42 AM

Hi Charles

There are a couple of gotachas getting the Jabber for Android client working with CUCM.

1. You MUST reboot the entire CUCM cluster after adding the COP file that enables the Android phone type. Whilst you can add a new device without a reboot on CUCM, the clients will not reconnect until you have done it.

2. Check your DNS. The phone must be able to resolve whatever you have got configured as the CUCM Server Name or address. As an example if you have "CUCM1" configured in CUCM, (System -> Server) then the smart phone must be able to resolve "CUCM1" to the IP Address of CUCM. Even if you add the IP address of the CUCM server on the Jabber client, it MUST be able to resolve the host name. This is the commonest problem I see on these installations.

If you really want to get down and dirty on this, you have run a network packet capture on CUCM (from the cli).

"utils network capture"

you can specify the IP address of your smartphone and look at all communications between them. This will normally give you a very good steer on what is going wrong.

As an aside, I've never tested your exact phone model,but have connected a number of other Samsung and HTC handsets with no issue.

HTH Barry

Barry Hesk

Intrinisic Network Solutions

0 Helpful

Charles Rayer
Level 1
Level 1
In response to barry

‎10-29-2012 11:48 AM

Hi Barry,

Thanks a lot, you've put me on the right track.

I captured from the non-working device and got this:

admin:utils network capture host ip 10.200.96.4

Executing command with options:

size=128                count=1000              interface=eth0

src=                    dest=                   port=

ip=10.200.96.4

18:14:41.583358 IP 10.200.96.4.50336 > CM1.tftp:  55 RRQ "BOTJAMES.cnf.xml" octet tsize 0 blksize 512 timeout 5

18:14:41.583807 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.585774 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.585868 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.587958 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.588023 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.590757 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.590810 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.592500 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.592577 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.594289 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.594345 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.601226 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.601278 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.603037 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.603092 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.606912 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.606968 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.611532 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.611589 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.615006 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.615060 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.616707 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.616763 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.618578 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.618635 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.622073 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.622128 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.626277 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.626334 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.628009 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.628062 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.629748 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.629812 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.636355 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.636418 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.640093 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.640148 IP CM1.42871 > 10.200.96.4.50336: UDP, length 516

18:14:41.642801 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:41.642857 IP CM1.42871 > 10.200.96.4.50336: UDP, length 288

18:14:41.644368 IP 10.200.96.4.50336 > CM1.42871: UDP, length 4

18:14:42.965730 IP 10.200.96.4.47650 > CM1.5060: S 1705289537:1705289537(0) win 14600

18:14:42.965794 IP CM1.5060 > 10.200.96.4.47650: S 2292017916:2292017916(0) ack 1705289538 win 5792

18:14:42.967706 IP 10.200.96.4.47650 > CM1.5060: . ack 1 win 3650

18:14:42.967967 IP 10.200.96.4.47650 > CM1.5060: F 1:1(0) ack 1 win 3650

18:14:42.968496 IP CM1.5060 > 10.200.96.4.47650: F 1:1(0) ack 2 win 1448

18:14:42.970057 IP 10.200.96.4.47650 > CM1.5060: . ack 2 win 3650

18:14:43.002250 IP 10.200.96.4.37511 > CM1.5060: S 3592600546:3592600546(0) win 14600

18:14:43.002286 IP CM1.5060 > 10.200.96.4.37511: S 2287905187:2287905187(0) ack 3592600547 win 5792

18:14:43.005482 IP 10.200.96.4.37511 > CM1.5060: . ack 1 win 3650

Control-C pressed

I have searched the tftp server for a BOTJAMES file but didn't find it. I understand these files are deleted ater they are downloaded, and I did get BOTJAMES wokring on another device. So I created a new BOTxxx device and couldn't find that either.

Will do some more tests tomorrow, but if you have any ideas I would greatly appreciate.

Here is capture from a working device (BOTCRAYER):

admin:utils network capture host ip 10.200.96.2

Executing command with options:

size=128                count=1000              interface=eth0

src=                    dest=                   port=

ip=10.200.96.2

18:11:27.713740 IP 10.200.96.2.45826 > CM1.5060: S 2093555951:2093555951(0) win 14600

18:11:27.714667 IP CM1.5060 > 10.200.96.2.45826: S 2066644068:2066644068(0) ack 2093555952 win 5792

18:11:27.715625 IP 10.200.96.2.45826 > CM1.5060: . ack 1 win 229

18:11:27.737605 IP 10.200.96.2.45826 > CM1.5060: F 1:1(0) ack 1 win 229

18:11:27.737691 IP CM1.5060 > 10.200.96.2.45826: F 1:1(0) ack 2 win 1448

18:11:27.739244 IP 10.200.96.2.45826 > CM1.5060: . ack 2 win 229

18:11:27.769038 IP 10.200.96.2.46140 > CM1.5060: S 3322192713:3322192713(0) win 14600

18:11:27.769078 IP CM1.5060 > 10.200.96.2.46140: S 2068019935:2068019935(0) ack 3322192714 win 5792

18:11:27.770587 IP 10.200.96.2.46140 > CM1.5060: . ack 1 win 229

18:11:28.245800 IP 10.200.96.2.46140 > CM1.5060: . 1:1449(1448) ack 1 win 229

18:11:28.245835 IP CM1.5060 > 10.200.96.2.46140: . ack 1449 win 2172

18:11:28.250362 IP 10.200.96.2.46140 > CM1.5060: P 1449:2015(566) ack 1 win 229

18:11:28.250394 IP CM1.5060 > 10.200.96.2.46140: . ack 2015 win 2896

18:11:28.254032 IP 10.200.96.2.46140 > CM1.5060: . 2015:3463(1448) ack 1 win 229

18:11:28.254056 IP CM1.5060 > 10.200.96.2.46140: . ack 3463 win 3620

18:11:28.254212 IP 10.200.96.2.46140 > CM1.5060: P 3463:4234(771) ack 1 win 229

18:11:28.254230 IP CM1.5060 > 10.200.96.2.46140: . ack 4234 win 4344

18:11:28.255158 IP CM1.5060 > 10.200.96.2.46140: P 1:380(379) ack 4234 win 4344

18:11:28.258032 IP 10.200.96.2.46140 > CM1.5060: . ack 380 win 245

18:11:28.261628 IP CM1.5060 > 10.200.96.2.46140: P 380:695(315) ack 4234 win 4344

18:11:28.263428 IP 10.200.96.2.46140 > CM1.5060: . ack 695 win 262

18:11:31.791070 IP CM1.5060 > 10.200.96.2.46140: P 695:1819(1124) ack 4234 win 4344

18:11:31.792766 IP CM1.5060 > 10.200.96.2.46140: . 1819:3267(1448) ack 4234 win 4344

18:11:31.792784 IP CM1.5060 > 10.200.96.2.46140: P 3267:3296(29) ack 4234 win 4344

18:11:31.846096 IP 10.200.96.2.46140 > CM1.5060: . ack 1819 win 297

18:11:31.851065 IP 10.200.96.2.46140 > CM1.5060: . ack 1819 win 297

18:11:31.851386 IP 10.200.96.2.46140 > CM1.5060: . ack 3296 win 342

18:11:31.885816 IP 10.200.96.2.46140 > CM1.5060: . 4234:5682(1448) ack 3296 win 342

18:11:31.887070 IP 10.200.96.2.46140 > CM1.5060: P 5682:6256(574) ack 3296 win 342

18:11:31.887094 IP CM1.5060 > 10.200.96.2.46140: . ack 6256 win 5068

18:11:31.891048 IP CM1.5060 > 10.200.96.2.46140: P 3296:3675(379) ack 6256 win 5068

18:11:31.947546 IP 10.200.96.2.46140 > CM1.5060: . ack 3675 win 388

18:11:31.959605 IP 10.200.96.2.46140 > CM1.5060: P 6256:6694(438) ack 3675 win 388

18:11:31.999504 IP CM1.5060 > 10.200.96.2.46140: . ack 6694 win 5068

Control-C pressed

0 Helpful

Charles Rayer
Level 1
Level 1
In response to Charles Rayer

‎11-16-2012 02:49 AM

I'm still hoping for some positive input on this, though the project has gone on the back burner a bit I still have to cpmplete it.

Has anyone got any success stories regards Android and Jabber and CUCM please? If so, what kit are you using and versions are you running?

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents