This is YOUR page! Feel free to add missing information, content, links, etc.
|
Extending VoIP to Wireless LANsRegister NowTaping Date: March 27, 2008
Air Date: May 1, 2008
Agenda:Segment 1: Technical Challenges and Business Drivers
Segment 2: How ready is your Wireless? Guest: Larry Ross, TME WNBU
Segment 3: Mobile Voice Potential with Mike Coffin from VoiceCon 2008
Segment 4: Voice over Wireless Deployment Reality and the Wireless Control System (WCS)
Six Challenges to doing Voice over Wireless LAN:
1. Quality of Service
2. Wireless is a Shared Resource
3. Roaming and Re-Authentication
4. Increased Support Requirements
5. End User expectations
6. Clients are evolving
Two Analysis Tools- Cisco Spectrum Analyzer (formerly Cognio)
- Air Magnet Laptop Analyzer
Training Opportunity with Global Knowledge (class designed by our two guests Mike Coffin & Larry Ross)
Links: Wireless VoIP on the Cisco SiteCisco Unified Wireless IP Phone 7921G802.11n - Ready for BusinessCisco Certified Wireless TrainingAre you a Cisco Partner selling Wireless Solutions? Join the
Wireless Partners Collaborative Workspace!Nokia handheld design guide at Cisco
Nokia Design Guide including the intellisync client
Non-TechWiseTV Video Programs: Extending Unified Communications to Mobile Workers (Video overview of Cisco Mobile Unified Communications applications along with a step-by-step approach of how to mobilize Cisco Unified Communications for mobile workers on campus or on the road).
Mobility TV: How to successfully Design, Deploy, Manage and Troubleshoot Voice over WLAN
On Demand Now: Learn the critical design and deployment factors that must be considered when adding voice communications over wireless networks to help make sure end-user satisfaction, a smooth and easy implementation, and air-tight security.
Download Valuable Documents:Voice over Wireless at a GlanceDesign Principles for Voice over WLANIs your Wireless LAN ready for Voice?Voice over WLAN 4.1 Validated Design GuideMac Find Script as mentioned on the show:#!/usr/bin/perlmy %cards;my %ips;open(ARP,"arp -an|") || die "Couldn't open arp table: $!\n";print "Put on the cornbread while I look up the OUIs.";while(<ARP>) {chomp;my $addr = $_;my $ip = $_;$addr =~ s/.* ([\d\w]+:[\d\w]+:[\d\w]+):.*/$1/;$addr =~ s/\b([\d\w])\b/0$1/g;$addr =~ s/:/-/g;next unless $addr =~ /..-..-../;$ip =~ s/.*?(\d+\.\d+\.\d+\.\d+).*/$1/;print ".";$cards{$addr}||=`curl -sd 'x=$addr' http://standards.ieee.org/cgi-bin/ouisearch`;($cards{$addr} =~ /Sorry!/) && ($cards{$addr} = "Unknown OUI: $addr");$ips{$ip} = $addr;}print "\n";for(keys(%ips)) {$cards{$ips{$_}} =~ s/.*.hex.\s+([\w\s\,\.]+)\n.*/$1/s;print "$_ -> $cards{$ips{$_}}\n";}Finding Rogue AP's
- Download a copy of NMAP, SScan or your favorite port scanned
- Inform your security folks you are scanning for rogue AP with a port scanner (if applicable)
- Scan your internal RFC 1918 IP address space for port 80
Normally a hit on this will be a rogue