I call through pstn2voip provider to my asterisk. I use alaw codec with dtmfmode=inbound.
The problem is that dtmf codes are being decoded so that every
keypress is doubled.
I press ‘1’ exactly once and I get 11. In asterisk/full log I get:
DEBUG[25492]: Launching 'WaitExten’
VERBOSE[25492]: – Executing WaitExten(“SIP/a.b.c.d-0814f820”, “5”) in new stack
DEBUG[25492]: Sending dtmf: 49 (1), at a.b.c.d
DEBUG[25492]: Oooh, got something to jump out with (‘1’)!
DEBUG[25492]: Sending dtmf: 49 (1), at a.b.c.d
a.b.c.d = IP address of my pstn2voip provider
You could have a synk. problem. Try checking your master. Set the master(1) synk. to the port from where you receive the clock.
[quote=“czar”]I call through pstn2voip provider to my asterisk. I use alaw codec with dtmfmode=inbound.
The problem is that dtmf codes are being decoded so that every
keypress is doubled.
I press ‘1’ exactly once and I get 11. In asterisk/full log I get:
DEBUG[25492]: Launching 'WaitExten’
VERBOSE[25492]: – Executing WaitExten(“SIP/a.b.c.d-0814f820”, “5”) in new stack
DEBUG[25492]: Sending dtmf: 49 (1), at a.b.c.d
DEBUG[25492]: Oooh, got something to jump out with (‘1’)!
DEBUG[25492]: Sending dtmf: 49 (1), at a.b.c.d
a.b.c.d = IP address of my pstn2voip provider
I’m a n00b to Asterisk and recently switched our system from using IAX2 to SIP. Incoming callers will attempt to dial an extension (e.g., 107) and instead will be redirected to another extension (e.g., 110 or 111). I think the problem is that the incoming caller presses “1” once and asterisk thinks that it has been pressed twice or three times. Is there a way to slow Asterisk down so it doesn’t interpret one keypress as two?
ZZI tried setting “relaxdtmf=yes” in sip.conf, but that didn’t help.
When running Asterisk with verbose set to 10, the following message appears during the call, which seems like it might be relevant:
Jan 19 15:39:04 DEBUG[17440]: channel.c:1134 ast_settimeout: Scheduling timer at 0 sample intervals
just a thought- perhaps you are getting double-dtmf because other dtmf is being sent also. Try setting dtmfmode=info or dtmfmode=rfc2833 (more likely rfc). see if that helps?
if it is inband there may be nothing you can do about it. Other DTMF processing down the line (ie at provider) may be processing dtmf and giving a dtmf echo so you actually hear each digit twice (stranger things have happened)