I ran into this issue and thought I'd pass it on. Using Cisco's bonjour gateway feature in 7.4, I found I could make use of Airplay through the Photo App but nothing else. Working with Apple, we found that the service string for AppleTV being looked for in iOS (6.1?) devices has changed from: _airplay._tcp.local. to _raop._tcp.local.
After creating a new profile for this string, the iOS device became aware of the ATV and now is able to work with it. The ATV looks to be advertising both types. I assume the PhotosApp was the only app that I found still looking for the older service name. Cisco is has documented this as bug: CSCue54207. I'm not really sure this rises to the level of a bug as any change in any advertised service string would require a the WLC to be aware of it. The workaround is easy enough, one just adds the correct string as a new service (max of 64 btw). I'd still prefer to be able to use DNS-SD for AppleTV (across subnets) or generically a more 'enterprise' friendly protocol over this feature, but given the lack of those, this feature looks to be the best option in our environment. However, when a service needs this type of network infrastructure glue, things can get messy as it inserts a network operations group into a service they don't have much control of. I'd be interested in anyone else's experience with this feature, especially if in production. -- Garry Peirce Networkmaine, University of Maine System ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
