|
|
Joined: Jan 2012
Posts: 3
Member
|
OP
Member
Joined: Jan 2012
Posts: 3 |
We just deployed a Cisco VOIP solution and ran fine for about 5 days and then had massive amounts of clocking issues.
We replaced the cisco equipment (had a spare) and line tests indicate that our house cabling is sound.
We are set to get timing from the line (Verizon in this case) and here is the interesting part. The issue spikes during business hours and thats whether my users are online or not.
Any ideas?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Jul 2003
Posts: 766
Member
|
|
Member
Joined: Jul 2003
Posts: 766 |
Well this one sounds like a clocking issue. you need to be getting your clock for timing the T1 from the carrier.
|
|
|
|
|
Joined: Jul 2003
Posts: 766
Member
|
|
Member
Joined: Jul 2003
Posts: 766 |
Well this one sounds like a clocking issue. you need to be getting your clock for timing the T1 from the carrier.
example:
interface serial 0
service-module t1 clock source line
|
|
|
|
|
Joined: Mar 2008
Posts: 54
Member
|
|
Member
Joined: Mar 2008
Posts: 54 |
If your haven't already done so, start with show controllers T1 from the command line. This will allow you to verify your settings as well as see the error counts. For reference, here is the output from a working system: #sh controll T1
T1 0/3/0 is up.
Applique type is Channelized T1
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Version info Firmware: 20100222, FPGA: 13, spm_count = 0
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Data in current interval (190 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
|
|
|
|
|
Joined: Nov 2006
Posts: 43
Member
|
|
Member
Joined: Nov 2006
Posts: 43 |
If you have two different clock sources (e.g. an AT&T PRI on port 0 and a Sprint MPLS T1 on port 1)on a two port VWIC card, you will have to change one of the circuits to self clocking. Otherwise you will have massive slip second errors and circuits failing.
"Waiting for my implantable virtual-reality/full tactile suite video satphone, because it will be the next best thing to being there."
|
|
|
|
|
Joined: Sep 2004
Posts: 194
Member
|
|
Member
Joined: Sep 2004
Posts: 194 |
Agreed...See what errors show.
The errors will tell the tale.
Good luck.
CCNA
CCNA Voice
MCSE W2K3
Security +
CS1000 5.5
Toshiba
Comdial
Avaya
Mitel
Norstar
|
|
|
|
Forums84
Topics94,284
Posts638,768
Members49,765
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
