iChat Support

Aruba Employee
Q:

What is iChat feature and it's use case?



A:

Introduction:

When any Bonjour device sends out a mDNS response packet, AirGroup solution terminates that packet and updates its cache entries along with the device details. Such devices are identified as AirGroup Servers on a Mobility controller. When any Bonjour device sends out a mDNS query packet, AirGroup solution again terminates such packet and sends out a unicast response post cache entry lookup. Such devices are identified as Airgroup Users.

 

Some services use mDNS response packet to announce a user arrival and iChat is one of them. A new user entry will not be able to identify the existing user if the announcement packet(response packet) is not multicast. Hence the typical solution we use for airplay and other services does not hold good for iChat. The mDNS multicast response propagation allows services to multicast the response packet(it's a L2 multicast with service id "_presence._tcp"). This allows the existing users to instantly see a new user when a new user logs in. The mDNS response packet for iChat or Messages Application is multicast across all VLANs that are trunked in the controller.

 

How it works:

 

How to enable from WebUI:

How to enable from CLI:

(Aruba7210) (config) #airgroup service chat ?

disable                 disable service

enable                  enable service

(Aruba7210) (config) #airgroup service chat enable

 

 

Version history
Revision #:
2 of 2
Last update:
‎07-06-2015 05:10 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.