Cisco WLC and whatsapp delay message

[nicoles29879]

Hi all,

this is my environment, one vWLC (rele 8.1) and many 2700 ap connected in flexconnected, one ssid with web auth with customized (internal to wlc) captive portal.

This is my issue checked: when we put the mobile phone samsung in sleep, after 15 - 25 minute the message from whatsapp are delayed (send and received).

i try to change the session timeout, idle timeout (global and on wlan) but i can't find solution on this problem.

Now i will try to sniff the traffic from the client.

Someone solve this issue..??

[Lhausklsg]

Sound more like a client issue.

Did you try an iPhone as well? Did you run a debug client already?

[nicoles29879]

i solve the problem...

[hromanoc.]

Hi Nicole,

How did you solve it?

[nicoles29879]

Check the firewall port and destination ip connectivity to whatsapp cidr.

after this the problem disappear...

destination port to open:

TCP: 4244,5222,5223,5228,5242
TCP/UDP: 59234, 50318
UDP: 3478,45395

destination ip to check

31.13.64.51/32 31.13.65.49/32 31.13.66.49/32 31.13.67.51/32 31.13.68.52/32 31.13.69.240/32 31.13.70.49/32 31.13.71.49/32 31.13.72.52/32 31.13.73.49/32 31.13.74.49/32 31.13.75.52/32 31.13.76.81/32 31.13.77.49/32 31.13.78.53/32 31.13.80.53/32 31.13.81.53/32 31.13.82.51/32 31.13.83.51/32 31.13.84.51/32 31.13.85.51/32 31.13.86.51/32 31.13.87.51/32 31.13.88.49/32 31.13.90.51/32 31.13.91.51/32 31.13.92.52/32 31.13.93.51/32 31.13.94.52/32 31.13.95.63/32 50.22.198.204/30 50.22.210.32/30 50.22.210.128/27 50.22.225.64/27 50.22.235.248/30 50.22.240.160/27 50.23.90.128/27 50.97.57.128/27 75.126.39.32/27 108.168.171.224/27 108.168.174.0/27 108.168.176.192/26 108.168.177.0/27 108.168.180.96/27 108.168.254.65/32 108.168.255.224/32 108.168.255.227/32 157.240.0.53/32 157.240.2.53/32 157.240.3.53/32 157.240.7.54/32 158.85.0.96/27 158.85.5.192/27 158.85.46.128/27 158.85.48.224/27 158.85.58.0/25 158.85.61.192/27 158.85.224.160/27 158.85.233.32/27 158.85.249.128/27 158.85.254.64/27 169.44.36.0/25 169.44.57.64/27 169.44.58.64/27 169.44.80.0/26 169.44.82.96/27 169.44.82.128/27 169.44.82.192/26 169.44.83.0/26 169.44.83.96/27 169.44.83.128/27 169.44.83.192/26 169.44.84.0/24 169.44.85.64/27 169.45.71.32/27 169.45.71.96/27 169.45.87.128/26 169.45.169.192/27 169.45.182.96/27 169.45.210.64/27 169.45.214.224/27 169.45.219.224/27 169.45.237.192/27 169.45.238.32/27 169.45.248.96/27 169.45.248.160/27 169.46.52.224/27 169.47.5.192/26 169.53.29.128/27 169.53.48.32/27 169.53.71.224/27 169.53.250.128/26 169.53.252.64/27 169.53.255.64/27 169.54.2.160/27 169.54.44.224/27 169.54.51.32/27 169.54.55.192/27 169.54.193.160/27 169.54.210.0/27 169.54.222.128/27 169.55.67.224/27 169.55.69.128/26 169.55.74.32/27 169.55.75.96/27 169.55.126.64/26 169.55.210.96/27 169.55.235.160/27 173.192.162.32/27 173.192.219.128/27 173.192.222.160/27 173.192.231.32/27 173.192.234.96/27 173.193.198.96/27 173.193.205.0/27 173.193.230.96/27 173.193.230.128/27 173.193.230.192/27 173.193.239.0/27 174.36.208.128/27 174.36.210.32/27 174.36.251.192/27 174.37.199.192/27 174.37.217.64/27 174.37.231.64/27 174.37.243.64/27 174.37.251.0/27 179.60.192.51/32 179.60.193.51/32 179.60.195.51/32 184.173.136.64/27 184.173.147.32/27 184.173.161.64/32 184.173.161.160/27 184.173.173.116/32 184.173.179.32/27 185.60.216.53/32 185.60.218.53/32 192.155.212.192/27 198.11.193.182/31 198.11.251.32/27 198.23.80.0/27 208.43.115.192/27 208.43.117.79/32 208.43.122.128/27 2607:f0d0:1b01:d4::/64 2607:f0d0:1b02:14d::/64 2607:f0d0:1b04:32::/64 2607:f0d0:1b04:bb::/64 2607:f0d0:1b04:bc::/64 2607:f0d0:1b06::/64 2607:f0d0:1b06:4::/64 2607:f0d0:1e01:b1::/64 2607:f0d0:2102:229::/64 2607:f0d0:2601:37::/64 2607:f0d0:3003:1bc::/64 2607:f0d0:3003:1cd::/64 2607:f0d0:3004:136::/64 2607:f0d0:3004:174::/64 2607:f0d0:3005:183::/64 2607:f0d0:3005:1a3::/64 2607:f0d0:3006:84::/64 2607:f0d0:3006:af::/64 2607:f0d0:3801:38::/64 2607:f0d0:3801:14b::/64 2607:f0d0:3802:48::/64 2a03:2880:f200:c5:face:b00c::167/128 2a03:2880:f200:1c5:face:b00c::167/128 2a03:2880:f201:c5:face:b00c::167/128 2a03:2880:f202:c4:face:b00c::167/128 2a03:2880:f203:c5:face:b00c::167/128 2a03:2880:f204:c5:face:b00c::167/128 2a03:2880:f205:c5:face:b00c::167/128 2a03:2880:f206:c5:face:b00c::167/128 2a03:2880:f207:c5:face:b00c::167/128 2a03:2880:f208:c5:face:b00c::167/128 2a03:2880:f209:c5:face:b00c::167/128 2a03:2880:f20a:c5:face:b00c::167/128 2a03:2880:f20b:c5:face:b00c::167/128 2a03:2880:f20c:c6:face:b00c::167/128 2a03:2880:f20d:c5:face:b00c::167/128 2a03:2880:f20e:c5:face:b00c::167/128 2a03:2880:f20f:c6:face:b00c::167/128 2a03:2880:f210:c5:face:b00c::167/128 2a03:2880:f211:c5:face:b00c::167/128 2a03:2880:f212:c5:face:b00c::167/128 2a03:2880:f213:c5:face:b00c::167/128 2a03:2880:f213:80c5:face:b00c::167/128 2a03:2880:f214:c5:face:b00c::167/128 2a03:2880:f215:c5:face:b00c::167/128 2a03:2880:f216:c5:face:b00c::167/128 2a03:2880:f217:c5:face:b00c::167/128 2a03:2880:f218:c3:face:b00c::167/128 2a03:2880:f219:c5:face:b00c::167/128 2a03:2880:f21a:c5:face:b00c::167/128 2a03:2880:f21b:c5:face:b00c::167/128 2a03:2880:f21c:c5:face:b00c::167/128 2a03:2880:f21c:80c5:face:b00c::167/128 2a03:2880:f21f:c5:face:b00c::167/128 2a03:2880:f221:c5:face:b00c::167/128 2a03:2880:f222:c5:face:b00c::167/128 2a03:2880:f223:c5:face:b00c::167/128 2a03:2880:f225:c4:face:b00c::167/128 2a03:2880:f226:c6:face:b00c::167/128 2a03:2880:f227:c5:face:b00c::167/128

if you solved..give me point PLEASE :)

[jmprats]

I have the same problem, too

Any solution

Thanks

[hromanoc.]

Hi jmprats,

I still have the same problem i contacted Cisco TAC but the issue continue. Just to know, what is your currently enviroment (APs+WLC)?

Thanks!

[jmprats]

Yes, AP's+WLC

[hromanoc.]

Right now, we have the same issue with whatsapp since we added a WLC in the network (2 weeks ago).

WLC: AIR-CT2504

APs: AIR-CAP3702E-A-K9

The were no problem when we used the same APs but in autonomus mode (without the WLC).

[George Stefanick]

I would do a client debug and see what is going on. 

[jmprats]

It seems to happen with Apple, Android, full battery and less ...

the user complains that this does not happen with other access points (at home, ...) , so it seems that it is a problem of our wifi

[George Stefanick]

To fully understand the issue you will need to study that device. Debugs and reproduce the problem ..

[Leo Laohoo]

the user complains that this does not happen with other access points (at home, ...)

I seriously doubt this is a wireless issue.  This statement alone points to a wired networked issue with the back end process.  I mean, sure, we know there is/are AP/APs and WLC involved but what about proxy servers, firewalls, load balancers, etc.  Anyone of these can cause application-based delay with delivery.

[jmprats]

Debugging in the firewall, there are blocked ports

I enabled tcp 5222-5223 and 5228

I need to do more testing but it seems works!

[Hai Cheng Xu]

Did you guys turn off the background data update ? We were using wechat facing same issue with whatsapp,after turn off backgroud data update in cell phone.it is ok now