I actually meant to take that out before copy and pasting. It was
just a zany option I tried to see if things would get better but they
didn't.
I will post a bug later this week about this.
On 3/30/07, Kevin P. Fleming [EMAIL PROTECTED] wrote:
Justin Tunney wrote:
rfc2833compensate=yes
Why
Justin Tunney wrote:
rfc2833compensate=yes
Why do you have this turned on? This setting is _ONLY_ for receiving
RFC2833 DTMF from pre-1.4 Asterisk servers, it should never be used for
any other SIP endpoint.
___
--Bandwidth and Colocation provided by
Hello mailing list,
I have been porting one of my Asterisk boxes to 1.4 and I have
encountered a nasty DTMF problem. What happens is someone might come
in to my IVR and enter 12345 and what will actually come through
could be along the lines of 12234445. Sometimes it works, sometimes
it
Also, I am not using a zaptel timer. Could this possibly be causing
problems with DTMF??
I really don't know for certain but here's what I experienced: When
calling out asterisk gives the option to allow called numbers to
transfer by hitting the '#' by putting 'T' (or 't'?) as an option in
I can report that with asterisk 1.2.13, internal SIP calls work
perfectly but (in my particular case) my asterisk box cannot recognize
DTMF digits when it receives a call via our SIP provider. we are both
using rfc2833 and I have tried relaxdtmf=yes/no
when i use an internal sip extension and
Erick Perez wrote:
I can report that with asterisk 1.2.13, internal SIP calls work
perfectly but (in my particular case) my asterisk box cannot recognize
DTMF digits when it receives a call via our SIP provider. we are both
using rfc2833 and I have tried relaxdtmf=yes/no
when i use an internal
On 11/9/06, mail-lists [EMAIL PROTECTED] wrote:
Erick Perez wrote:
I can report that with asterisk 1.2.13, internal SIP calls work
perfectly but (in my particular case) my asterisk box cannot recognize
DTMF digits when it receives a call via our SIP provider. we are both
using rfc2833 and I
Asterisk People,
I'm currently using Asterisk and with a SIP voip provider and I'm
having problems where DTMF input in my IVR app is getting corrupted
intermittently.
For example, if someone enters 1025, it may come though correctly as
1025, or it may come trough as 10025, or 100255. DTMF
Justin Tunney wrote:
Asterisk People,
I'm currently using Asterisk and with a SIP voip provider and I'm
having problems where DTMF input in my IVR app is getting corrupted
intermittently.
For example, if someone enters 1025, it may come though correctly as
1025, or it may come trough as 10025,
Migrating to 1.4 is not an option. I don't know what that is, but I
doubt my voip provider supports it.
On 11/8/06, Kristian Kielhofner [EMAIL PROTECTED] wrote:
Have you tried 1.4 with vldtmf?
___
--Bandwidth and Colocation provided by
Hey, Justin:
Justin Tunney wrote:
Asterisk People,
I'm currently using Asterisk and with a SIP voip provider and I'm
having problems where DTMF input in my IVR app is getting corrupted
intermittently.
For example, if someone enters 1025, it may come though correctly as
1025, or it may
11 matches
Mail list logo
