[Asterisk-Users] VoicePulse DTMF Problems Anyone?

[Michael Stearne]

On 6/11/05, Rich Adamson <radamson at routers.com> wrote:
> >
> > I am wondering if anyone else is experiencing similar issues.  I
> > believe the problem lies with VoicePulse because we are using them for
> > IAX connections.  I don't believe its a bandwidth problem on my
> > network (cable) because I have tried the same exact system/config
> > everything on another network (T1) and the same digit dropping
> > continues to happen. This is happening with a load of 1 call.
> >
> > Is this problem with VoicePulse?  Is anyone else experiencing it?  Can
> > anyone recommend a more reliable company?
> 
> In most previous cases, dtmf issues have been related to how you
> define your interfaces. For sip definitions, use dtmfmode=rfc2833.
> 
> Some itsp's have an issue with asterisk in that a completed "iax" call
> to an asterisk IVR is considered an "answered" call, and therefore
> expect dtmf tones to be passed to the endpoints. In this case, the
> dtmf tones are expected to be generated by the phone and passed
> to the IVR as inband audio tones. I'm not a voicepulse user, so don't
> know if they have some particular problem or not.
> 
> 
> My system has iax trunks from multiple itsp providers, multiple
> iax links to other companies that we work with, a variety of sip
> phones (each defined with rfc2833), and multiple analog pstn lines.
> We don't have a problem (cvs-head) with an IVR that starts out as:

Rich,

Thanks for the input.  I am just using the default Asterisk settings
for IAX so I would think in that case I wouldn't be the only person
experiencing this.  What I did was set up an account with BroadVoice
and setup a SIP connection.  After trying about 15 times, this new
connection has gotten every digit pressed.  When we started developing
3 weeks ago the VoicePulse IAX setup I have was catching all the
digits I would press. It seems only lately that the same setup has
gotten worse (although at certain times it works well).

It does seem to me the problem was probably due to some network issues
at VoicePulse.

Thanks,
Michael