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!

BCM 50 crack nose / sets blink

Status
Not open for further replies.

jsaad

IS-IT--Management
Jun 20, 2002
1,396
US
I have a BCM 50 R3. customer is complaining when they use IP trunks of excessive static noise and the phone flashes/blinks all keys. CO Trunk and ext to ext dialing is fine. Network has been tested and rebooted to confirm connectivity.

Thinking of a reboot perhaps or a failing HDD?
 
Check alarms?

I would always reboot first on strange issues or lockups etc then start tickets etc.


________________________________________
small-logo-sig.png


=----(((((((((()----=
Toronto, Canada

Add me to LinkedIN
 
Site is at 3.0 and is fully patched. weird stuff always has been happening here. A lot of power outages and I put in a large UPS earlier this year. this time multiple phones on the main KSU would have a loud static noise when making an intercom call and some phones would go dead, lamp and keys would flash and then come back....only during an intercom call. A call on a trunk would be fine. I swapped over to some spare extension ports with no trouble after some test calls and will monitor.
 
If you have to power it off, then look at the hard drive inside the unit. If it's a Maxtor disk, then expect it to be failing.

I have attached a guide on what to do.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
This does not sound like a failing hard drive to me.

Static only when using IP trunks would almost certainly be related to network connectivity problems (either bandwidth issues or some other network issues).

Loud static noise when making intercom calls on digital phones could be either an incorrect companding law selected for the phone(s) (ulaw instead of alaw or vice versa) or data corruption on the B channel (not very likely). The system could select an incorrect law if it mis-detects the phone type (e.g., NA vs. global set). Corrupt B channel data could be due to noise introduced on the connection of the MBM (DSM16 or DSM32). Both problems could be caused by a DSM module or its cable. If the digital phones that have this problem are connected to a DSM module, consider replacing the cable that connects the module to the BCM50 (you would need a shielded cable of the correct length) or replacing the DSM module itself (which could be partially failing). A quick test that you could do - move the phones to digital ports on the BCM50 and test if the issue goes away.
 
That's a fair point about the drive, but it wouldn't do any harm to take the cover off the BCM 50 and check it's clean. I've known a number of systems to get very dirty and full of muck from the fans over the years. Using an air spray or even a hoover as well as checking the fan is OK is worth looking at.

The BCM 400 is a good example on how bad a circuit board can get if left untouched.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
Thanks for the good advice. as it turns out the ports on the processor that were flaky. I moved the phones in question to the DSM32 mod and it cleared up.

We are going to schedule a maintenance window to clean out that cabinet and potentially replace the disk. I can hear disk spinning.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top