COLT Circuit not resyncing after reboot.

[TomMills]

Hello you gorgeous lot,

Did a new install today. Go me.

IP500V2, 8.1(67), about 100 IP handsets, another 100 DB turrets. 60 channels Qsig to IPC DB system, 60 channels BT ISDN, 60 channels from COLT.

After a reboot, the BT circuits and Qsig all resync ok, but the COLT circuit stays out of service until you pull the cables and plug them back in.

Clocking from one BT, fallback on t'other. COLT both set to unsuitable. Must admit, writing this now i should have tried clocking from the COLT but can try that tomorrow.

Not a major issue as unplugging sorts it, but a bit annoying none the less, would like to get to the bottom of it if poss.

Any ideas?

http://www.twitter.com/tem1985

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[amriddle01]

You do tend to have to clock from both when it's 2 providers, sometimes it's fine but it can cause issues like this and then both need to clock



"No problem monkey socks

 

[TomMills]

Oh really? I've always been told one clocking source per system plus one fallback, no exceptions.

interesting.

http://www.twitter.com/tem1985

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[amriddle01]

That is the general rule, however if it's causing synch issues and it helps....why not



"No problem monkey socks

 

[TomMills]

I'm going way back to 3.2/4.0 territory, but I remember having more than one clock source causing reboots.

Happy to give it a whirl though, already ballsed up the partners PA handset by being a div with bridged appearances so a few unwanted reboots wouldn't be a problem I imagine.

At least the hold music is behaving itself.

http://www.twitter.com/tem1985

APSS/ACIS/ACSS-SME
not arrogant, just succinct.