<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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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'>Cisco is recommending 1.4.1<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>Jason B<br><b>Sent:</b> Tuesday, January 25, 2011 3:04 PM<br><b>To:</b> Ki Wi<br><b>Cc:</b> 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><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Are you by chance using SR1? I had all kinds of these type problems with 1.3.4SR1 on 7921 and 7925 IP Phones a few months ago. I was advised by TAC to use 1.3.3 and stay away from 1.3.4SR1 because all the bugs. Based on my limited and painful experience with 1.3.4, I would recommend going to 1.3.3 unless 1.3.5 has been released. I haven't checked back lately.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The particular I bug I was seeing was </span><span style='font-size:11.0pt'>CSCti62253</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jason</span><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Tue, Jan 25, 2011 at 6:04 AM, Ki Wi <<a href="mailto:kiwi.voice@gmail.com">kiwi.voice@gmail.com</a>> wrote:<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><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></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>