Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Clock slips

Status
Not open for further replies.

AlexLD

IS-IT--Management
Joined
Aug 5, 2011
Messages
138
Location
US
We are getting regular clock slips one our PRIs connected to one of our IP500 systems. Here's the detail.

We had a 406V2 and it has slips from the very beginning, the carriers fiddled and it was reduced to on occasional slip. We replaced the 406 with a 500 about 2 years ago and all was well (PRI 48 in a legacy card carrier). Over the past 4 months we have been having issues with dropped calls on the PRI, after finally getting our users to identify the issue we traced it down to clock slips on one of the PRIs, we will call this PRI 2. PRI1 is the network clock source, PRI2 is set to fallback. Which ever line is the network source is fine and whichever is the fallback/unsuitable won't work. Since one carrier is a CLEC and the other is a long distance provider, neither is providing the local loop, the LEC (Verizon) is doing that. Both PRI vendors claim they must be the clock source, but it is my understanding that there can only be one clock source on the IP Office unit. The latest from the vendor is that the line is clear up to the NIU and that from the NIU to the CSU it is not passing the 1:8 test. This of course makes sense because the clock is slipping. I keep demanding that they send someone out to verify that the clocks on the two PRIs are in sync, but they both claim this is not possible. Am I stuck in a catch 22?
 
Are you running 8.0?
I have seen three systems already with yellow alarms.
Two on the new PRI and one in a legacy card carrier.

BAZINGA!

I'm not insane, my mother had me tested!

 
I have seen that on systems with broken ports on a 406V2, replace hardware

If it ain't dutch it ain't much
 
Are both PRI setup to Network?

Put PRI1 in Network and PRI2 to Fallback, if the error still occurs then do it viceversa.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
Well, it turned out to be the PRI24 cards and I assume how they interact with the two carriers. I pulled out the PRI24s and tested them individually and they work properly on another IP500 in a legacy card carrier. On this system each would work fine if the other PRI was unplugged. I swapped the two PRI24s for a PRI48 and now the PRI clocks are in sync. Has anyone had this issue before? Seems strange to me but I'm glad that it is at last fixed.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top