Bug running around

[martinduchesneau]

Hi,

The team I work with and I have run in a few cases of bugs running around different systems for our customers. Most of them are using 0x32 systems with various versions. The bug we're facing is sort of "jamming" of 1 telephone in the system. We can't take/make calls, acces voicemail, use of any buttons and functions are not possible.

We tried unplugging the phone, plugging it back in, same result, we changed the phones at first and sent the "deffective one" to repair only to find out they are not defective. We changed the phone's acces port, we changed the pair from Equipment to jack and nothing seems to fix thgis bug.

Strangest thing about it all is, this bug affects not only one phone, but each one on the system, one at a time. So one day phone x is in trouble, the next day phone y shows the same issue, while x is returned to normal.

Has anyone already faced this issue? It's rather odd since this happens to clients that have been up and running stable for many months/years and no changes were made to their config. Is there a possible virus infection for Norstar systems?

Thanks for the help

 

[endlesswinter]

If this is 6.1 there was a "call park bug" that would freeze up the phones.

 

[curlycord]

No it cant makes calls and various software....

Go to maintenance and check for any odd alarms.

Reboot system to clear some bugs.
If it does not fix your issue then do a Startup and reprogram from scratch as that will clear all bugs.

 

[RikRodgers]

If it's only 1 phone, I'd probably check for a stuck button first, especially when you say you've sent them in for repair, and thay test ok.

 

[phoneguy427]

Try disabling the port and re enabling it. I had that problem on mics 5.0.

 

[sprucegrover]

I've had the same issue with 5.0 & 6.1 and thought it was gone. Last week, same issue in XC7.1. With my case, it was everything appearing normal, but no talk path, and incoming calls would continue to hear ring-back tone even after set was answered.
I have always been able to resolve the individual troubles by either 1. unplug and restore the set to service or 2. disable & re-enable the set in maintenance or 3. turn on set relocation, swap the set with another, wait until they both are up and working, and then replace the sets to original location (this always seemed to work best). Never got any helpful information from ITAS aven when they were called with a defective set on a MICS that was available to dial into. They never seemed interested.

 

[lugerlover]

could try and refresh template.Unplug old set-plug in any other model number"other model is key" let it intailize then plug in original...Only draw back will be is you will need to reprog feature buttons

 

[Runako]

I had the same problem, on the older 6.1 software, upgrade to 7.0 and this should fix your problem.

 

[DMilden]

Have the same problem with a site. Upgraded to 7.1 software for other PRI issues but still have the feature bug. Only way I have found to resolve it is power down system.

 

[martinduchesneau]

Ok thanks for all the feedback, I'm glad to see I'm not the only one with such problems. However no clear solution is available from what I understand.

One thing I forgot to mention about the systems (I apologize) is that they both run with MCK1000 for a branch office in another town not too far away (please don't discuss the idea of switching to BCM and Ip solution). People move around between the branch office and headquarters with their phones since it's the same system. We've noticed the problem occurs only on phones in the headquarter that used to be in the branch office. We have no issue in the branch office tough.

We are using version 7.1 on one of the systems (we have to cases with this problem) and Pri link (recently updated to this config) and we have had this issue since then, I guess it has to do with that.

For the other system also using MCK1000 but older version and regular lines, it started happening recently. No maintainance was done on it for nearly a year before the problem started showing up so I find it rather odd.

Anyway we have lots of hints to work with right now so we'll look into it. Thanks for all the replies.

 

[curlycord]

Maybe a failed upgrade to 7.1 on the first site?

What is version on second site?

I still like my first suggestions.