User's Extension rings constantly, until phone (5410) is unplugged?

[whiteEEnerd]

I have a user who says their extension will ring for no reason constantly until they unplug the phone. According to the user nothing shows up on the screen any different from when they are not receiving a call. The user has mentioned that it has rang for as long as 10 minutes before while he tried to figure out what the problem was.

Does anyone have any idea what this could be? I've never been at the phone when this has happened, but the user says it has happened 3 times now. This is a new IP500 switch that uses 4 analog trunk lines and all of the sets are 5410 digital sets.

Thanks!

 

[TomMills]

had this once for a 5402,once has unplugged and cleared it, what makes it happen again? incoming call?

 

[whiteEEnerd]

It appears to be happening randomly, hasn't really happened enough yet to figure out the cause.

I forgot to mention, that while it is ringing you can still pick up the handset and get a dial tone. The ringing continues, but goes softer when you pick up the handset. It goes back to it's previous volume when you put the handset down.

 

[TomMills]

is this on an expansion module? to fix i downgraded and re upgraded the exp module, this was on a 406 3.2something

 

[tlpeter]

Seen it on 4.0
Did not see it happen on 4.1 (yet )

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[jamie77]

I've seen calls get stuck on 4.0.7 on 2 sites. Only thing to clear was systems reset.

Haveb't seen since upgrading those sites.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Football is not a matter of life and death-It is far more important!!!!

 

[BillIT]

I had this happen once, I deleted the port, using Manager, to solve it. It was an IP406, but could be the same solution in IP500.

Bill

 

[whiteEEnerd]

Thanks for the suggestions guys. The system is running 4.1(12) for what that is worth.

I went to the business today and was unable to get the situation they described to occur. However I can now open up system status remotely, so the next time they have the problem they are supposed to call us and we'll see if we can find anything weird in system status.

A little bit more about the problem, they say it happened one time when they had one call, then got another call. One extension picked up the first call, another extension picked up the second call. the second extension put the second call on hold. the first extension then finished with the first call, and picked up the second call. This is when the first extension started ringing for no apparent reason.

 

[gregl45]

I have seen this with 4.1(9). Do you have bridged appearances? The only way I could make it stop was to remove the bridged appearance buttons and it has not happened since.

 

[B657]

I had this and it was down to the fact that call waiting was on.

Is call waiting on? Try disabling it.

 

[whiteEEnerd]

The users all have 4 line appearances.

Call Waiting is on, except the "Answer Call Waiting on Hold (analogue)" is actually checked, even though it doesn't matter since they are all digital sets.

 

[whiteEEnerd]

Could this have anything to do with the button setup? I only have 2 "Appearance Appearance" buttons, and 4 "Line Appearance" buttons. I cut the Appearance Appearance down to 2 so I could fit all 4 line appearances on the 5410 main page. They say it usually happens when they get 2 or more calls at once. Would it have anything to do with that?

Also, maybe the analog lines are sticking? I read that in another post.

 

[ronromano]

I have seen this all the way back to 3.1. It definitly has something to do with bridged appearences. Some how this one user has it happen once in a while. Fixed with reboot. Fortunatly it does not happen often.

http://www.nu-tel.com

 

[SuperJenks]

Its a quarky issue that I have also seen. I have never been able to put a thumb on due to its infrequent occurences. Uplugging the phone never helped. A system reset was necessary to clear the problem. This has occured on 412's and 406's running 3.2.xx and 4.0. I cant say I've seen it on a 500.

 

[tgrenier]

Try logging the phone out and back in again when this happens. I had a similar problem where unplug/replug didn't fix it, but relog did. Of course this is just an immediate fix and may not prevent it from happening again.