<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.userinput
{mso-style-name:userinput;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7921g/6_0/english/deployment/guide/7921dply.pdf">http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7921g/6_0/english/deployment/guide/7921dply.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>page 105 discusses how to setup the 792X phone to syslog via the usb to a laptop (I recommend Kiwi SyslogD).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jason Aarons (US) <br><b>Sent:</b> Tuesday, January 25, 2011 7:03 AM<br><b>To:</b> 'Ki Wi'; Cisco VoIP List<br><b>Subject:</b> RE: [cisco-voip] 7921G suffering from dropped calls while roaming between AP<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I would encourage long term moving to the A band, it has more non-overlapping channels with less pollution/interference. Given that you should plan/site survey for 5Ghz. I would look into AutoRF to verify you don’t have any channel/power problems. If you want to stick with the 2.4GHz b/g I would consider looking at Cisco CleanAir where the silicon/asic has built in spectrum analysis.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I would put a laptop on the 7921 SSID and use IP Communicator and test if you can roam, do you have multiple controllers? Did you use the WCS to audit they are setup identical?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>There were firmware bugs with 1.3.4, change the load to 1.3.4sr2 or 1.4.1 or latest sccp load<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Unified Wireless Deployment Guide<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7921g/6_0/english/deployment/guide/7921dply.pdf">http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7921g/6_0/english/deployment/guide/7921dply.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Windows 7 netsh command line and Network Monitor 3.3 have some ways to debug the wireless client;<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For example, to start a trace for the WLAN scenario, create a CAB file with a formatted report, capture network traffic, and store the files with the name WLANTest in the C:\Tshoot folder, the netsh command is netsh trace start scenario=WLAN capture=yes report=yes tracefile=c:\tshoot\WLANtest.etl<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Then use the free Microsoft Network Monitor 3.3 or higher to view the .etl file<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="http://forum.persianadmins.ir/showthread.php?p=48918">http://forum.persianadmins.ir/showthread.php?p=48918</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Other netsh commands;<o:p></o:p></p><p class=MsoNormal>netsh wlan show networks mode=bssid<o:p></o:p></p><p class=MsoNormal>netsh trace show status<o:p></o:p></p><p class=MsoNormal>netsh show wlan all<o:p></o:p></p><p class=MsoNormal>netsh wlan show interface<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Microsoft Network Monitor 3.4 download<o:p></o:p></p><p class=MsoNormal><a href="http://www.microsoft.com/downloads/en/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en#SystemRequirements">http://www.microsoft.com/downloads/en/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en#SystemRequirements</a><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Ki Wi<br><b>Sent:</b> Tuesday, January 25, 2011 6:05 AM<br><b>To:</b> Cisco VoIP List<br><b>Subject:</b> [cisco-voip] 7921G suffering from dropped calls while roaming between AP<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Hey guys, <o:p></o:p></p></div><div><p class=MsoNormal>I need a little help here. We have lots of newly provision 7921G in the environment running ver 1.3.4. WPA2/AES/LEAP/CCKM turned on. WLC is on latest 7.0.98.0. The LAN switches are mostly on 2960S or cat4500 with sup6lite. <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>I have read around but doesn't really find much information on how to troubleshoot this issue. I'm aware that 7921G with version older than 1.3.4 will need to do full reregistration when it roams to the new AP and some roaming issues with older sup engine.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>My colleague actually troubleshoot this issue and he changed the wireless phone to scan for channel 1/6/11 only (on b/g) , we disabled the A as it seems like we have a poor coverage with 802.11a. Customer reported that they tested with 2 phones (one with new setting , one with existing setting), the phone with new setting doesn't suffer any dropped calls at all. I find it too amazing to believe so I'm wondering does anyone have similar experience before? We have other large sites which doesn't suffer this issue. Honestly, I don't think that's going to be the solution as it requires us to drill down into low level configuration and manipulate how the phone to scan for AP in specific channels. <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Cheers, <o:p></o:p></p></div><div><p class=MsoNormal>Ki Wi<o:p></o:p></p></div></div></body></html>
<HTML><BODY><P><hr size=1></P>
<a href="http://dimensiondata.stream57.com/04141pm/"><span style='color:blue;text-decoration:none'><img border=0 src="http://image.exct.net/lib/feed16797d620d/i/2/8c665b10-9.gif" alt=DDIPT></span></a>
<P><STRONG>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</STRONG></P></BODY></HTML>