Polycom has introduced a fix on 3.2.5b. However, for those who prefer not to downgrade from a 3.3.x, 3.3.2 is scheduled for the end of July. Brad Anouar ?|?Anywhere (310) 360-2028 | Corporate (800) 942-4700 | www.broadcore.com -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Matthew S. Crocker Sent: Tuesday, June 07, 2011 11:20 AM To: PE Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] Polycom ghost ringing On the transfer if you push the transfer hard key then the blind softkey it should transfer fine without the ghost ring. We have the exact some issue with Polycom 3.3.0 on Bworks R17 ----- Original Message -----
From: "PE" <peeip989 at gmail.com> To: voiceops at voiceops.org Sent: Tuesday, June 7, 2011 2:11:43 PM Subject: Re: [VoiceOps] Polycom ghost ringing
Working with Polycom, we have been able to replicate this issue with some regularity (not 100% of the time, but approx 75%). It is related to transferring of calls. So far, here's what we know:
To Replicate:
1. User A receives and answers a call 2. User A does a warm transfer to User B 3. While User B is still ringing, User A hangs up (the call is transferred to B) 4. User A's hears ringing mixed into their next call.
Then the problem does NOT occur if:
- User B answers (actual warm transfer) before User A hangs up - User A presses the transfer key (a second time) instead of hanging up - User A uses the Blind transfer key
Additionally, if/when the problem does occur, if User A places the call on hold then picks it up, the ringing stops (the reINVITE appears to clear it).
On Fri, Jun 3, 2011 at 1:54 PM, Pete E <peeip989 at gmail.com> wrote:
Back in January there were a couple of posts related to "ghost ringing" on Polycom phones. At the time the workaround seemed to be to downgrade to v3.3.0 (we're on 3.3.1). Looking at the release notes on 3.3.1 it looks like the .0 release was pretty buggy and therefore we'd rather not downgrade to it. Polycom has not acknowledged (to us) that they even know about the problem. Does anyone know if any headway has been made in actually fixing the issue?
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops