<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div style="RIGHT: auto"><SPAN style="RIGHT: auto">yep, All ones equal carrier lost for a time adter initial turn up.<BR style="RIGHT: auto" class=yui-cursor></SPAN></div>
<DIV></DIV>
<DIV> </DIV>
<div style="RIGHT: auto">Rick<VAR id=yui-ie-cursor></VAR><BR><BR></div>
<DIV style="FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt">
<DIV style="FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt">
<DIV dir=ltr><FONT size=2 face=Arial>
<DIV style="BORDER-BOTTOM: #ccc 1px solid; BORDER-LEFT: #ccc 1px solid; PADDING-BOTTOM: 0px; LINE-HEIGHT: 0; MARGIN: 5px 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; HEIGHT: 0px; FONT-SIZE: 0px; BORDER-TOP: #ccc 1px solid; BORDER-RIGHT: #ccc 1px solid; PADDING-TOP: 0px" class=hr contentEditable=false readonly="true"></DIV><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Lelio Fulgenzi <lelio@uoguelph.ca><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Matthew Loraditch <MLoraditch@heliontechnologies.com> <BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> Cisco VOIP <cisco-voip@puck.nether.net> <BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Friday, July 13, 2012 11:00 AM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [cisco-voip] D channel errors - carrier or us?<BR></FONT></DIV><BR>
<DIV id=yiv414496624>
<STYLE type=text/css>#yiv414496624 p {margin:0;}</STYLE>
<DIV>
<DIV style="FONT-FAMILY: Verdana; COLOR: #000000; FONT-SIZE: 10pt">k, thanks for the hint. i'll have to push them to help resolve this intermittent issue.<SPAN><BR><BR><SPAN></SPAN>---<BR>Lelio Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>Cooking with unix is easy. You just sed it and forget it. <BR> - LFJ (with apologies to Mr. Popeil)<BR><SPAN></SPAN><BR></SPAN><BR>
<DIV style="BORDER-BOTTOM: #ccc 1px solid; BORDER-LEFT: #ccc 1px solid; PADDING-BOTTOM: 0px; LINE-HEIGHT: 0; MARGIN: 5px 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; HEIGHT: 0px; FONT-SIZE: 0px; BORDER-TOP: #ccc 1px solid; BORDER-RIGHT: #ccc 1px solid; PADDING-TOP: 0px" class=hr contentEditable=false readonly="true"></DIV><B>From: </B>"Matthew Loraditch" <MLoraditch@heliontechnologies.com><BR><B>To: </B>"Lelio Fulgenzi" <lelio@uoguelph.ca>, "Cisco VOIP" <cisco-voip@puck.nether.net><BR><B>Sent: </B>Friday, July 13, 2012 10:24:32 AM<BR><B>Subject: </B>RE: [cisco-voip] D channel errors - carrier or us?<BR><BR>
<STYLE><!--
#yiv414496624
_filtered #yiv414496624 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}
_filtered #yiv414496624 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}
_filtered #yiv414496624 {font-family:Verdana;panose-1:2 11 6 4 3 5 4 4 2 4;}
#yiv414496624
#yiv414496624 p.yiv414496624MsoNormal, #yiv414496624 li.yiv414496624MsoNormal, #yiv414496624 div.yiv414496624MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"serif";}
#yiv414496624 a:link, #yiv414496624 span.yiv414496624MsoHyperlink
{color:blue;text-decoration:underline;}
#yiv414496624 a:visited, #yiv414496624 span.yiv414496624MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
#yiv414496624 p
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"serif";}
#yiv414496624 p.yiv414496624MsoAcetate, #yiv414496624 li.yiv414496624MsoAcetate, #yiv414496624 div.yiv414496624MsoAcetate
{margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"sans-serif";}
#yiv414496624 span.yiv414496624object
{}
#yiv414496624 span.yiv414496624EmailStyle19
{font-family:"sans-serif";color:#1F497D;}
#yiv414496624 span.yiv414496624BalloonTextChar
{font-family:"sans-serif";}
#yiv414496624 .yiv414496624MsoChpDefault
{font-size:10.0pt;}
_filtered #yiv414496624 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv414496624 div.yiv414496624WordSection1
{}
--></STYLE>
<DIV class=yiv414496624WordSection1>
<div class=yiv414496624MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt">Those errors from the router in my experience are 99/100 times a carrier issue. Occasionally it can be your extended demarks or patch cables, and on that 100<SUP>th</SUP> time it could be hardware but I’d go with the carrier as a first look</SPAN></div>
<div class=yiv414496624MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt"> </SPAN></div>
<DIV>
<div class=yiv414496624MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 10pt"> </SPAN></div>
<div class=yiv414496624MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt">Matthew G. Loraditch – CCNP-Voice, CCNA, CCDA<BR></SPAN><SPAN style="COLOR: #1f497d; FONT-SIZE: 9pt"><BR>1965 Greenspring Drive</SPAN><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt"><BR></SPAN><SPAN style="COLOR: #1f497d; FONT-SIZE: 9pt">Timonium, MD 21093</SPAN><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt"><BR></SPAN><SPAN style="COLOR: #1f497d; FONT-SIZE: 9pt"><BR>voice. 410.252.8830<BR>fax. 410.252.9284 <BR><BR><A href="http://twitter.com/heliontech" rel=nofollow target=_blank><SPAN style="COLOR: blue">Twitter</SPAN></A> | <A href="http://www.facebook.com/#%21/pages/Helion/252157915296" rel=nofollow target=_blank><SPAN style="COLOR: blue">Facebook</SPAN></A> | <A href="http://www.heliontechnologies.com/" rel=nofollow target=_blank><SPAN style="COLOR: blue">Website</SPAN></A> | <A
href="mailto:support@heliontechnologies.com?subject=Technical%20Support%20Request" rel=nofollow target=_blank ymailto="mailto:support@heliontechnologies.com?subject=Technical%20Support%20Request"><SPAN style="COLOR: blue">Email Support</SPAN></A></SPAN><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt"></SPAN></div>
<div style="MARGIN-BOTTOM: 12pt" class=yiv414496624MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt"> </SPAN></div></DIV>
<div class=yiv414496624MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt"> </SPAN></div>
<DIV>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<div class=yiv414496624MsoNormal><B><SPAN style="FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Lelio Fulgenzi<BR><B>Sent:</B> Friday, July 13, 2012 10:20 AM<BR><B>To:</B> Cisco VOIP<BR><B>Subject:</B> [cisco-voip] D channel errors - carrier or us?</SPAN></div></DIV></DIV>
<div class=yiv414496624MsoNormal> </div>
<DIV>
<div style="MARGIN-BOTTOM: 12pt" class=yiv414496624MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10pt"><BR>Over the last few months, I've had sporadic D channel errors. Am I correct in suspecting carrier issues? Typically, if it's a problem on our end, we'd see other errors like unregistered gateways, etc.</SPAN></div>
<DIV style="MARGIN-LEFT: 30pt">
<div class=yiv414496624MsoNormal><SPAN class=yiv414496624object><SPAN style="COLOR: black; FONT-SIZE: 10pt">Jul 13 04</SPAN></SPAN><SPAN style="COLOR: black; FONT-SIZE: 10pt">:34:46 iptccm105.cs.uoguelph.ca 2274: : : 842: <SPAN class=yiv414496624object>Jul 13 08</SPAN>:34:46.717 UTC : %CCM_RTMT-RTMT-2-RTMT-ERROR-ALERT: RTMT Alert Name:MgcpDChannelOutOfService Detail: MGCP DChannel is out-of-service. D-Channel-Out-Of-Service status in gateway device(s): S0/DS1-0@sda0002fce0933c, S0/DS1-0@sda0002fce09322, S0/DS1-0@sda000164165b07, S0/DS1-0@sda000164165b04, S0/DS1-0@sda0002fce09321, S0/DS1-0@sda0002fce0933a, S0/DS1-0@sda0002fce09339, S0/DS1-0@sda0002fce09324 App ID:Cisco AMC Service Cluster ID: Node ID:iptccm105</SPAN></div></DIV>
<div style="MARGIN-BOTTOM: 12pt" class=yiv414496624MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10pt"><BR>I don't have any more log details from the 6608 ports, but the one port on our 3945 had this information in the logs at the time:</SPAN></div>
<DIV style="MARGIN-LEFT: 30pt">
<div style="MARGIN-BOTTOM: 12pt" class=yiv414496624MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10pt">Jul 13 2012 04:33:58.335: %CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to down (AIS detected)<BR>Jul 13 2012 04:33:58.391: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller T1 0/0/0<BR>Jul 13 2012 04:34:00.335: %LINK-3-UPDOWN: Interface Serial0/0/0:23, changed state to down<BR>Jul 13 2012 04:34:08.643: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller T1 0/0/0<BR>Jul 13 2012 04:34:08.643: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10<BR>Jul 13 2012 04:35:07.332: %CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to up<BR>Jul 13 2012 04:35:09.332: %LINK-3-UPDOWN: Interface Serial0/0/0:23, changed state to up<BR>Jul 13 2012 04:35:17.644: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1</SPAN></div></DIV>
<div class=yiv414496624MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10pt">Should I be looking in CallManager logs for more information at this time?<BR><BR><BR>---<BR>Lelio Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>Cooking with unix is easy. You just sed it and forget it. <BR> - LFJ (with apologies to Mr. Popeil)<BR><BR><BR></SPAN></div></DIV></DIV></DIV></DIV></DIV><BR>_______________________________________________<BR>cisco-voip mailing list<BR><A href="mailto:cisco-voip@puck.nether.net" ymailto="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><BR><BR><BR></DIV></DIV></div></body></html>