<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>geeez, next they'll be asking you to add " cablelength long 0db" to your config. ;)<span><br><br><span name="x"></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 (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Go0se" <me@go0se.com><br><b>To: </b>"Mike King" <me@mpking.com>, "Cisco VoIPoE List" <cisco-voip@puck.nether.net><br><b>Sent: </b>Thursday, August 26, 2010 11:00:15 AM<br><b>Subject: </b>Re: [cisco-voip] PRI Clocking<br><br>You should expect a PRI to ALWAYS ALWAYS ALWAYS run clean. Faxing is<br>especially susceptive to errors/failure across a PRI that has errors. And<br>you should ALWAYS clock off of the TELCO. That is ridiculous that they<br>suggested you provide an internal clock for a PRI. Do you have your network<br>clock participate and network clock select correct? <br><br>Thanks,<br><br>Go0se<br><br>My blog:<br>http://atc.go0se.com<br><br>--------------------------------------------<br>Help Hopegivers International<br>Feed the orphans of Haiti and India<br>http://www.hopegivers.org<br>--------------------------------------------<br><br>-----Original Message-----<br>From: cisco-voip-bounces@puck.nether.net<br>[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Mike King<br>Sent: Thursday, August 26, 2010 9:41 AM<br>To: Cisco VoIPoE List<br>Subject: [cisco-voip] PRI Clocking<br><br>Just for someone to check my sanity.<br>I'm having the standard argument with Telco today (We don't see anything,<br>it must be your equipment)<br><br>I have a PRI that I've had complaints of dropped calls.<br><br>I go an check the log on the 2921 router, and see this (Across 3 different<br>dates, just one posted for brevity)<br><br>092856: Jul 30 2010 09:49:36.861 EDT: %MARS_NETCLK-3-HOLDOVER:<br>Entering Holdover for Controller T1 0/0/0<br>092857: Jul 30 2010 09:49:38.613 EDT: %LINK-3-UPDOWN: Interface<br>Serial0/0/0:23, changed state to down<br>092858: Jul 30 2010 09:49:47.113 EDT: %MARS_NETCLK-3-HOLDOVER_TRANS:<br>Holdover timer exceeded for Controller T1 0/0/0<br>092859: Jul 30 2010 09:49:47.113 EDT: %MARS_NETCLK-3-CLK_TRANS:<br>Network clock source transitioned from priority 1 to priority 10<br>092861: Jul 30 2010 09:57:23.612 EDT: %LINK-3-UPDOWN: Interface<br>Serial0/0/0:23, changed state to up<br>092863: Jul 30 2010 09:57:32.112 EDT: %MARS_NETCLK-3-CLK_TRANS:<br>Network clock source transitioned from priority 10 to priority 1<br><br>I also have CRC's on the serial0/0/0:23 (not a whole lot, just some)<br><br>Telco of course says they've pulled PM's and see nothing. I've been pushing<br>the issue with my Telco Rep, and he's suggested that since it seems to be a<br>clocking issue (His words) that maybe we should set our PRI to internal<br>clocking.<br><br>I reset the counters on my serial interface, and in the past 2 days, I've<br>recieved 1 CRC. I've also not had the PRI drop any calls. (Or the whole PRI<br>drop, which is what I assume from those log messages)<br><br><br>I have another circuit at a different site, I reset it's counters at the<br>same time 48 hours ago, and It had this today (also I don't have any reports<br>of dropped calls, just problems faxing)..<br>12 runts, 0 giants, 0 throttles<br>32 input errors, 32 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort<br><br>My question is this:<br><br>Is it Normal to have some number of CRC's on a PRI?<br>My personal experience is to ALWAY clock off Telco, and you should not have<br>any errors on my lines. Am I wrong with this assumption?<br><br>Mike<br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br><br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>