<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" 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 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@font-face
{font-family:Verdana;
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-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have had similar issues with one way voice for certain phones
or locations.<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'>The solution has been to excluded network addresses from the
DHCP pool. I have many customers using the Cisco DHCP off of a 28XX with no
issues. The key is to exclude address. It doesn’t know how to do it itself and
will actually give out the router ip address. <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:10.0pt;font-family:"Arial","sans-serif";
color:black'>Semper Fidelis,</span><span style='font-size:10.0pt;font-family:
"Arial","sans-serif";color:black'><o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:black'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Arial","sans-serif";
color:black'>Dustin Fowler</span></b><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:black'><br>
</span><b><span style='font-size:8.0pt;font-family:"Verdana","sans-serif";
color:#7F7F7F'>Senior Cisco Consultant</span></b><span style='font-size:8.0pt;
font-family:"Verdana","sans-serif";color:#7F7F7F'><br>
</span><b><span style='font-size:8.0pt;font-family:"Verdana","sans-serif";
color:#0084A8'><img width=84 height=40 id="Picture_x0020_1"
src="cid:image001.jpg@01C8E5FE.ED07E2B0"
alt="cid:image001.gif@01C8D09B.0C46BD50"></span></b><span style='font-size:
8.0pt;font-family:"Verdana","sans-serif";color:#0084A8'><o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:8.0pt;font-family:"Verdana","sans-serif";
color:#788D1F'>Email:</span></b><b><span style='font-size:8.0pt;font-family:
"Verdana","sans-serif";color:#1F497D'> </span></b><b><span style='font-size:
8.0pt;font-family:"Verdana","sans-serif";color:#0084A8'><a
href="mailto:dfowler@data-corporation.com"><span style='font-family:"Calibri","sans-serif";
color:#0084A8'>dustin.s.fowler@gmail.com</span></a></span></b><b><span
style='font-size:8.0pt;font-family:"Verdana","sans-serif";color:#008DB4'><br>
</span></b><i><span style='font-size:8.0pt;font-family:"Arial","sans-serif";
color:#C94429'>"KEEPING YOUR BUSINESS HIGHLY AVAILABLE"</span></i><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 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"'> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Todd Franklin<br>
<b>Sent:</b> Sunday, July 13, 2008 8:30 PM<br>
<b>To:</b> Steve G<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Phone System Outages<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Yes, the 2801 at each location
is for SRST and 911 issues.<br>
All IP phones have the same default gateway. It might be the 2801 or a
3560, I will have to confirm tomorrow when I am back at the office. I
think the 2801 is doing DHCP server duties, something I need to get off of it.<o:p></o:p></p>
<div>
<p class=MsoNormal>On Sun, Jul 13, 2008 at 11:20 AM, Steve G <<a
href="mailto:smgustafson@gmail.com">smgustafson@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal>This may be an obvious question, but why is there a 2801 at
each location? is it for SRST/911 purposes? Do all IP Phones
have the same default gateway, or do they look to their respective 2801s
to provide routing for them?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:#888888'>Steve<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal>On Sun, Jul 13, 2008 at 8:07 AM, Todd Franklin <<a
href="mailto:toddnh65@gmail.com" target="_blank">toddnh65@gmail.com</a>>
wrote:<o:p></o:p></p>
<p class=MsoNormal>Interesting thought. The 2801 did have some sort of
notice about a duplicate DHCP entry or some such thing....unfortunately,
everything was happening so fast, and there is that need to JUST FIX IT,that
there isn't a lot of time to write stuff down or gather relevant stats. <br>
<br>
Looks like I will be doing further research!!<br>
<br>
Todd<br>
<br>
I think it might be time to set up my cisco gear so it logs relevant happenings
to a syslogger on one of my linux/doze boxes. <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<div>
<p class=MsoNormal>On Sun, Jul 13, 2008 at 12:50 AM, Jonathan Charles <<a
href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>>
wrote:<o:p></o:p></p>
<p class=MsoNormal>One-way audio is almost always a routing issue, my guess is
that you<br>
have a duplicate route to a subnet or a duplicate IP taking over a key<br>
layer-3 routed interface.<br>
<br>
<br>
<br>
Jonathan<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
On Sat, Jul 12, 2008 at 7:42 AM, Todd Franklin <<a
href="mailto:toddnh65@gmail.com" target="_blank">toddnh65@gmail.com</a>>
wrote:<br>
> Environment:<br>
><br>
> CCM 4.1, Unity version 4 also.<br>
> 3560s, 2801s. 6 buildings all linked by fiber. Each building
has a 2801<br>
> and 3560.<br>
> Total phone count: 60, mostly 7940s, some 7912s, a few 7960s.<br>
><br>
> All fiber runs back to main location where it joins the network through<br>
> GBICs on 3560s.<br>
> At the main location we have a PRI that goes into a 2801.<br>
><br>
> Problem: 3 times in the last year, we will get a situation that goes
like<br>
> this:<br>
> Pressing 9 to dial out, and dialing your number: Phone shows call is<br>
> completed, starts counting the seconds, but you hear nothing.<br>
> If we call another extension internally, they will hear us but we cannot<br>
> hear them.<br>
> If someone calls in from outside and gets the auto attendant, no input is<br>
> accepted, the attendant just keeps going. (i.e. Press 2 for this,
she just<br>
> keeps going, you can press as many buttons as you like, no change).<br>
><br>
> The solution seems to be to reboot the main 2801 with the PRI. I am
not<br>
> sure why this would cure internal extension-to-extension calls, but it<br>
> does. My facility runs 24 hours a day, so a reboot is never a good
thing.<br>
><br>
> Where should I start looking? Broadcast storms? Is this a sort
of known<br>
> bug that Cisco might have fixed somewhere? Anything in Unity or CCM
I<br>
> should look at? Counters on ports?<br>
><br>
> Would appreciate any direction at all!<br>
><br>
> Todd<br>
><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal>> _______________________________________________<br>
> cisco-voip mailing list<o:p></o:p></p>
<div>
<p class=MsoNormal>> <a href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a><o:p></o:p></p>
</div>
<p class=MsoNormal>> <a
href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<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><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>