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?
We've had the same problem with FW version 3.3.1. We've noticed that it only happens when the call is terminated through a hunt group. There was some sort of a reINVITE that triggered a weird ring back tone in the middle of the call. Polycom support has acknowledged the issue and suggested to downgrade to 3.2.4, but as you probably know, the structure of the configuration files is different in the pre 3.3.x FW. The next FW version is scheduled to be released in July. We are still trying to come up with a work around. Brad Anouar | Anywhere (310) 360-2028 | Corporate (800) 942-4700 | www.broadcore.com<http://www.broadcore.com/> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Pete E Sent: Friday, June 03, 2011 10:54 AM To: voiceops at voiceops.org Subject: [VoiceOps] Polycom ghost ringing 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?
@Christian, no, I mean that while the user is on the phone they hear the far end party mixed with ringback tone in their ear. @Brad, we have not correlated it with hunt groups or even on incoming calls. We've only been able to capture it a couple of times and the times we have seen it, it has coincided with a slew of spanning tree activity on the LAN. Could be coincidence, but I am thinking there is an indirect correlation. Clearly the spanning tree is not SIP (and we are not seeing a 180 Ringing or other message that might confuse the phone) and is not inband ringback in RTP, but I am thinking it might be causing the phone to to wig out, though this is pure speculation. We also have the same concerns about file structure. On Fri, Jun 3, 2011 at 3:00 PM, Brad Anouar <Brad at broadcore.com> wrote:
We?ve had the same problem with FW version 3.3.1. We?ve noticed that it only happens when the call is terminated through a hunt group. There was some sort of a reINVITE that triggered a weird ring back tone in the middle of the call. Polycom support has acknowledged the issue and suggested to downgrade to 3.2.4, but as you probably know, the structure of the configuration files is different in the pre 3.3.x FW. The next FW version is scheduled to be released in July. We are still trying to come up with a work around.
*Brad Anouar** ** *| Anywhere (310) 360-2028 | Corporate (800) 942-4700 | www.broadcore.com
*From:* voiceops-bounces at voiceops.org [mailto: voiceops-bounces at voiceops.org] *On Behalf Of *Pete E *Sent:* Friday, June 03, 2011 10:54 AM
*To:* voiceops at voiceops.org *Subject:* [VoiceOps] Polycom ghost ringing
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?
Hi Pete, According to the only capture we have, you are right. Neither in-band nor out-of-band traffic that would cause such behavior was present. I'm going to go back and check to see if there was any STP activity during the time of the incident. It could've been easily ignored since we only have one capture. I will also check to find out if the affected clients are all using the same type of switch. I will then post the findings. What type of switch do your affected customers use? Regards, Brad Anouar | Anywhere (310) 360-2028 | Corporate (800) 942-4700 | www.broadcore.com<http://www.broadcore.com/> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of PE Sent: Friday, June 03, 2011 12:27 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Polycom ghost ringing @Christian, no, I mean that while the user is on the phone they hear the far end party mixed with ringback tone in their ear. @Brad, we have not correlated it with hunt groups or even on incoming calls. We've only been able to capture it a couple of times and the times we have seen it, it has coincided with a slew of spanning tree activity on the LAN. Could be coincidence, but I am thinking there is an indirect correlation. Clearly the spanning tree is not SIP (and we are not seeing a 180 Ringing or other message that might confuse the phone) and is not inband ringback in RTP, but I am thinking it might be causing the phone to to wig out, though this is pure speculation. We also have the same concerns about file structure. On Fri, Jun 3, 2011 at 3:00 PM, Brad Anouar <Brad at broadcore.com<mailto:Brad at broadcore.com>> wrote: We've had the same problem with FW version 3.3.1. We've noticed that it only happens when the call is terminated through a hunt group. There was some sort of a reINVITE that triggered a weird ring back tone in the middle of the call. Polycom support has acknowledged the issue and suggested to downgrade to 3.2.4, but as you probably know, the structure of the configuration files is different in the pre 3.3.x FW. The next FW version is scheduled to be released in July. We are still trying to come up with a work around. Brad Anouar | Anywhere (310) 360-2028<tel:%28310%29%20360-2028> | Corporate (800) 942-4700<tel:%28800%29%20942-4700> | www.broadcore.com<http://www.broadcore.com/> From: voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org> [mailto:voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>] On Behalf Of Pete E Sent: Friday, June 03, 2011 10:54 AM To: voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: [VoiceOps] Polycom ghost ringing 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?
Typically Linksys (SRW or SFE), but we are also finding that customers plug in other various stuff (which appears to be the source of the spanning tree). On Fri, Jun 3, 2011 at 3:56 PM, Brad Anouar <Brad at broadcore.com> wrote:
Hi Pete,
According to the only capture we have, you are right. Neither in-band nor out-of-band traffic that would cause such behavior was present. I?m going to go back and check to see if there was any STP activity during the time of the incident. It could?ve been easily ignored since we only have one capture. I will also check to find out if the affected clients are all using the same type of switch. I will then post the findings. What type of switch do your affected customers use?
Regards,
*Brad Anouar** ** *| Anywhere (310) 360-2028 | Corporate (800) 942-4700 | www.broadcore.com
*From:* voiceops-bounces at voiceops.org [mailto: voiceops-bounces at voiceops.org] *On Behalf Of *PE *Sent:* Friday, June 03, 2011 12:27 PM *To:* voiceops at voiceops.org *Subject:* Re: [VoiceOps] Polycom ghost ringing
@Christian, no, I mean that while the user is on the phone they hear the far end party mixed with ringback tone in their ear.
@Brad, we have not correlated it with hunt groups or even on incoming calls. We've only been able to capture it a couple of times and the times we have seen it, it has coincided with a slew of spanning tree activity on the LAN. Could be coincidence, but I am thinking there is an indirect correlation. Clearly the spanning tree is not SIP (and we are not seeing a 180 Ringing or other message that might confuse the phone) and is not inband ringback in RTP, but I am thinking it might be causing the phone to to wig out, though this is pure speculation. We also have the same concerns about file structure.
On Fri, Jun 3, 2011 at 3:00 PM, Brad Anouar <Brad at broadcore.com> wrote:
We?ve had the same problem with FW version 3.3.1. We?ve noticed that it only happens when the call is terminated through a hunt group. There was some sort of a reINVITE that triggered a weird ring back tone in the middle of the call. Polycom support has acknowledged the issue and suggested to downgrade to 3.2.4, but as you probably know, the structure of the configuration files is different in the pre 3.3.x FW. The next FW version is scheduled to be released in July. We are still trying to come up with a work around.
*Brad Anouar** ** *| Anywhere (310) 360-2028 | Corporate (800) 942-4700 | www.broadcore.com
*From:* voiceops-bounces at voiceops.org [mailto: voiceops-bounces at voiceops.org] *On Behalf Of *Pete E *Sent:* Friday, June 03, 2011 10:54 AM
*To:* voiceops at voiceops.org *Subject:* [VoiceOps] Polycom ghost ringing
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?
After discussing your Hunt Group theory we may have some examples that occurred this way. We will try to validate and see if there is any commonality there. What types of switches are your customers using? On Fri, Jun 3, 2011 at 3:59 PM, PE <peeip989 at gmail.com> wrote:
Typically Linksys (SRW or SFE), but we are also finding that customers plug in other various stuff (which appears to be the source of the spanning tree).
On Fri, Jun 3, 2011 at 3:56 PM, Brad Anouar <Brad at broadcore.com> wrote:
Hi Pete,
According to the only capture we have, you are right. Neither in-band nor out-of-band traffic that would cause such behavior was present. I?m going to go back and check to see if there was any STP activity during the time of the incident. It could?ve been easily ignored since we only have one capture. I will also check to find out if the affected clients are all using the same type of switch. I will then post the findings. What type of switch do your affected customers use?
Regards,
*Brad Anouar** ** *| Anywhere (310) 360-2028 | Corporate (800) 942-4700 | www.broadcore.com
*From:* voiceops-bounces at voiceops.org [mailto: voiceops-bounces at voiceops.org] *On Behalf Of *PE *Sent:* Friday, June 03, 2011 12:27 PM *To:* voiceops at voiceops.org *Subject:* Re: [VoiceOps] Polycom ghost ringing
@Christian, no, I mean that while the user is on the phone they hear the far end party mixed with ringback tone in their ear.
@Brad, we have not correlated it with hunt groups or even on incoming calls. We've only been able to capture it a couple of times and the times we have seen it, it has coincided with a slew of spanning tree activity on the LAN. Could be coincidence, but I am thinking there is an indirect correlation. Clearly the spanning tree is not SIP (and we are not seeing a 180 Ringing or other message that might confuse the phone) and is not inband ringback in RTP, but I am thinking it might be causing the phone to to wig out, though this is pure speculation. We also have the same concerns about file structure.
On Fri, Jun 3, 2011 at 3:00 PM, Brad Anouar <Brad at broadcore.com> wrote:
We?ve had the same problem with FW version 3.3.1. We?ve noticed that it only happens when the call is terminated through a hunt group. There was some sort of a reINVITE that triggered a weird ring back tone in the middle of the call. Polycom support has acknowledged the issue and suggested to downgrade to 3.2.4, but as you probably know, the structure of the configuration files is different in the pre 3.3.x FW. The next FW version is scheduled to be released in July. We are still trying to come up with a work around.
*Brad Anouar** ** *| Anywhere (310) 360-2028 | Corporate (800) 942-4700 | www.broadcore.com
*From:* voiceops-bounces at voiceops.org [mailto: voiceops-bounces at voiceops.org] *On Behalf Of *Pete E *Sent:* Friday, June 03, 2011 10:54 AM
*To:* voiceops at voiceops.org *Subject:* [VoiceOps] Polycom ghost ringing
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?
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?
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
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
participants (3)
-
Brad＠broadcore.com -
matthew＠corp.crocker.com -
peeip989＠gmail.com