[VoiceOps] Broadworks/Polycom/Webex Conferences and DTMF issues

[Scott Berkman]

Broadworks itself does not act on the media (especially the DTMF) in any way
under normal circumstances.  The DTMF negotiation will usually occur
directly between the end phone (Polycom here) and the Level 3 media gateway
that transitions the call to the PSTN.  I'd recommend you take a capture on
your furthest point out towards Level 3 (outside of BroadWorks) and also
have the conference provider take a capture on their end as the call comes
in.  Then you go to Level 3 with the proof that something bad is happening
within their network or after they pass off to the PSTN, and they can either
fix the issue or change the routing.

 

                -Scott

 

From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Dawson, Robert
Sent: Tuesday, March 16, 2010 2:34 PM
To: Carlos Alcantar; VoiceOps
Subject: Re: [VoiceOps] Broadworks/Polycom/Webex Conferences and DTMF issues

 

Broadworks

 

From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Carlos Alcantar
Sent: Tuesday, March 16, 2010 1:14 PM
To: VoiceOps
Subject: Re: [VoiceOps] Broadworks/Polycom/Webex Conferences and DTMF issues

 

What type of pbx are these polycom's connected to?

 

 

Carlos Alcantar

Race Telecommunications, Inc.

101 Haskins Way

South San Francisco, CA 94080

P: 650.649.3550 x143

F: 650.649.3551

E: carlos at race.com

 

 

 

From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Robin Rodriguez
Sent: Tuesday, March 16, 2010 10:06 AM
To: VoiceOps
Subject: Re: [VoiceOps] Broadworks/Polycom/Webex Conferences and DTMF issues

 

 

On Mar 16, 2010, at 10:49 AM, Dawson, Robert wrote:

 

G.711/RFC2833/L3

 

 

Have you engaged L3 yet on this issue? If not get them on the phone, armed
with your own captures showing appropriate RFC2833 event duration and if you
yell loud enough they'll setup the instrumentation on their network to trap
it. My guess, L3 isn't terming the call themselves and at some point the
converting RFC2833 to inband to hand off to the eventual term carrier, and
that carrier is accepting the call via a Sonus which is mucking it up.

 

and yes been there done that.

--
Robin D. Rodriguez
Ifbyphone, Inc.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20100316/873c0021/attachment.html>