<div dir="ltr">Just says 'registering'... we did a packet trace and it just shows an invite and a couple of refers, but no responses to it...<div><br></div><div><br></div><div><br></div><div>Jonathan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 24, 2015 at 4:34 PM, Ryan Huff <span dir="ltr"><<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Are you able to see the physical phone during the event? What is the physical phone's behavior? </p>
<p dir="ltr">Does the physical phone show un regestered or does the phone show the new ccm/tftps addresses eventhough it doesn't register?</p>
<p dir="ltr">Whst load version on the 8851's?</p><span class="im HOEnZb">
<p dir="ltr">Thanks,</p>
<p dir="ltr">Ryan</p>
<br><br>-------- Original Message --------<br>From: Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>><br></span><span class="im HOEnZb">Sent: Friday, April 24, 2015 04:19 PM<br>To: "Chris Ward (chrward)" <<a href="mailto:chrward@cisco.com" target="_blank">chrward@cisco.com</a>><br>Subject: Re: [cisco-voip] Cisco 8851 not failing over to backup circuit...<br></span><div class="HOEnZb"><div class="h5">CC: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><br><div dir="ltr">Cranked the MTU to 1500, no change, dropped it down to 1100, no change... they will not register over the backup link... we have confirmed full connectivity over this link...<div><br></div><div><br></div><div>Jonathan</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 24, 2015 at 11:22 AM, Chris Ward (chrward) <span dir="ltr"><<a href="mailto:chrward@cisco.com" target="_blank">chrward@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">VPN registration issues usually point to MTU issues. Or at least packet or fragments due to MTU issues. I suspect there is a different in packet size during the
registration of these two devices or capabilities that affects packet size.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">When the primary link is down, you could run some ping tests while setting the ping size to 1X00 and setting the DF bit as well, this will help you find the max
size packet with overhead that can fit over the tunnel. Typically VPN tunnels take at least 80 bytes of overhead, so the largest MTU I would expect you could fit over the tunnel would be 1420.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I would try and adjust your tunnel MTU down to 1400 or even 1300 just as a test to see if it helps. (In my demo setups with EZVPN tunnels, I can only use 1350
max) Also, are your VPN endpoints able to fragment packets or clear DF bits so that they can fragment large packets? If you can clear df-bit at the interface, that may help move some of the larger packets through IF they have the DF-bit set.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#44546a">+Chris<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#44546a">TME - Unity Connection and MediaSense<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cisco-voip [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Jonathan Charles<br>
<b>Sent:</b> Friday, April 24, 2015 11:44 AM<br>
<b>To:</b> Charles Goldsmith<span><br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Cisco 8851 not failing over to backup circuit...<u></u><u></u></span></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">MTU was set to 1440, we set it to Auto, no change... <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Jonathan<u></u><u></u></p>
</div>
</div><div><div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Thu, Apr 23, 2015 at 10:13 PM, Charles Goldsmith <<a href="mailto:wokka@justfamily.org" target="_blank">wokka@justfamily.org</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">What's your MTU over the backup VPN? I've seen odd issues on some<br>
networks with different providers and MTU and fragmenting packets<br>
always caused issues until the MSS was set.<br>
<br>
I'm not sure why this would affect the 8851's, but we've noticed some<br>
other oddities with the 8851's. For instance, computers with intel<br>
nic's behind the phone have issues after we apply config, and we<br>
narrowed it down to intel gigabit master slave mode setting on the<br>
driver, at least, setting that to slave instead of auto resolves the<br>
problem. Otherwise, you have to reboot the phone a couple of times to<br>
get consistent connection through the 8851. Phones are connected to a<br>
2960 with a basic config, nothing out of the ordinary.<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><br>
On Thu, Apr 23, 2015 at 6:35 PM, Jonathan Charles <<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>> wrote:<br>
> We have CUCM 8.6.2 with Cisco 8851, Cisco 8831 phones at a remote location;<br>
> they are connected over MPLS and a Peplink Balance VPN as a backup.<br>
><br>
> When we yank the MPLS, the 8831 registers with CUCM and works fine.... the<br>
> 8851s do NOT.<br>
><br>
> Any reason the 8851 would act differently?<br>
><br>
><br>
><br>
><br>
> Jonathan<br>
><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal">> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">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><br>
><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>