5340e chooses when to ring or not (ringer sound only.)

[dg]

Hi all,
This has been bugging me now for a while - my 5340e on my desk sometimes just doesn't have audio while 'ringing.' The light blinks and the display shows an inbound call, but there's no 'ring.' It's not muted and the volume is set to a pretty good level. Without doing anything, perhaps the next call will ring. It's random.

We're on (unfortunately) StreamLine adapters, and I have experienced some pretty weird power related issues with them in the past, so perhaps that's the case here. The phone otherwise works fine, and I've had no other reports from any of the other 140 users.

It's a fairly difficult issue to test as there's no a/b scenario to verify. It just decides when it wants to misbehave on its own.

Has anyone else experienced this? Is it a known issue? Is there a fix?

TIA,
-dg

[dg]

Hi folks,
I thought I might bring this up again as we're still experiencing this issue and haven't found any resolution yet.

Basically we'll see the light blinking on inbound call, but there's no audible ring tone. This doesn't happen on every call, and it only affects one or two of our 140 phones (though it's not limited to any one phone.) Then perhaps the next one rings just fine, without having changed anything. It's random. Power-cycling/rebooting the phoneset doesn't help. I've even swapped phone sets for a given extension and the -replacement- phone doesn't ring either. The only thing I've found that "seems" to work is to completely blow out the whole extension and rebuild it, but that's really not practical to do every time. I've rebooted the 3300's and the Streamlines, and that also "appears" to work, but as it's random, the issue invariably crops up again somewhere else.

Any wizards have any clues on how we might squash this bug?

TIA,
-dg

[ralph]

Per chance are the users on the speaker phones when it happens?  That would cause that.
Try setting your ring type to "Ring Cont" and see if that makes a difference.

Ralph

[Boris]

I have a customer site doing this as well.  It is a mixture of phones, where some are ACD Agents and some are not.  At first, we thought only the ACD Agents were experiencing the issue, but then discovered that non-acd phones are doing it as well.  Mitel has a known bug for the ACD agent issue that requires an upgrade to fix it.  This is still an issue on the non-acd phones.

[dg]

I finally got word from our VAR that they believe Mitel has a fix for this. We're going to do an update next Wednesday and see if that fixes it. I'm not sure if this is just a bug fix patch or a full upgrade/update yet as I haven't actually seen the bulletin... I'll report back next week to confirm.
-dg

[ralph]

What version of software is this happening on?

Ralph

[dg]

I'm running
Release 7.1 PR1
Active 13.1.0.36
CC_relink 43.1.0.32_SP2

[chuckletech]

dg,

We are waiting for your repport!

I can confirm the Bug on 5330e and on 5320, On ACD and non-ACD user.



    Release level: 7.1
    Active software load: 13.1.0.33
    Inactive software load: Not available.
    System relink: No relink has been applied.
    Call Control relink: No relink has been applied.
    Platform: CX-II, 512MB of RAM

Thanks for feedback

[dg]

We're going to do an update/upgrade tonight (the details of the release version are unknown as of yet.)

I'll report back in a bit. As folks have become used to this, they've stopped reporting it.

-dg

dg,

We are waiting for your repport!

I can confirm the Bug on 5330e and on 5320, On ACD and non-ACD user.



    Release level: 7.1
    Active software load: 13.1.0.33
    Inactive software load: Not available.
    System relink: No relink has been applied.
    Call Control relink: No relink has been applied.
    Platform: CX-II, 512MB of RAM

Thanks for feedback

[dg]

We updated to 7.2 SP1 PR1
Load 13.2.1.27
Call control relink 43.2.1.14_SP1
last Wednesday 5/19/16

So far, I have to assume the update fixed the problem. Given that it has been ongoing for several months though, it is possible nobody has reported any issues. I'll send out another message and ask if it is truly fixed! Yay.

-dg