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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PRI Clock Source

Status
Not open for further replies.

bixtool

Programmer
Mar 4, 2009
51
US
Running out of ideas: IP412 SCN with 4 sites, having intermittent one-sided conversations across SCN, external calls, and incoming calls. Replaced 412 three weeks ago, ran fine for several weeks and now is back to the same issues. Network looks fine, Avaya tier 3 has looked over config and found no problems. Our focus this week is do we have a timing issue? They have two PRI's one in slot A and one in B, two different carriers, one local and one long distance. One is set to network and the other fallback. Could having two different carriers be causing some confusion in our 412 switch with the clock source? If so has anyone had symtoms like these across the board? Just need some ideas, pulling out all of my hair on this one. Thanks!
 
If you use ip phones then i say routing.




ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
They are all digital and analog phones with a few IP phones.
 
Can you give a little more info on the topology? You have a 412 at the main site, what's at the 3 remotes? Do all calls from remote sites go through the main site PRI's?

The Network and Fallback settings sound right to me...calls to or from the main site (that don't cross the SCN) from digital or analog phones, do they experience one-way conversation? If not then you can stop looking at the PRIs.

IP Phones or not, the network ccan still be causing the issues. What type of network is it...VPN, T1, MPLS etc?
 
Three of the remotes have a 406 and one a 412, all at 4.2.20. All calls go through the main site PRI's. The one-sided calls are an issue whether dialing directly in/out from the main site, and also across the SCN extension to extension, basically all around. As far as the network, all sites are connected by MM fiber directly back to the main site since this is a campus setting. The SCN is on it's own network separated from the data, no one site has more issues than another. Rebooting the main 412 seems to fix the issue for a couple of days to several weeks, that is what has us focusing on other possible issues, our logic is why would rebooting only the main IP412 fix a network issue? This setup worked seemlessly for several years until about 6 months ago. No changes were made around the time it popped up. Thanks for your help.
 
what are you routing the calls over?

is it VPN?

have you upgraded any software? does the VPN stay established? seems the RTP is getting lost.

when you changed the 412 did you also replace the VCM? maybe that has developed a fault? its either going to work or it isnt normally, but its worth investigating.

do you have some traces when the calls go bandy?

perhaps your ISP is causing the issue?

I had a similar problem with an ISP when they would automatically re-route traffic over different pipes due to congestion and the RTP gets lost.

do some trace routes across your network from one router to the public ip of the other and see if you can see any differences before and after the issue occurs.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top