asterisk users - Oct 2009 - DTMF problems during a message play

I'm using the latest asterisk-1.4.26.2 and no zaptel trunks used, all SIP. 

I have one user that is having problems once he connects to asterisk. 
He's dialing from his home phone (pstn) to a Vitelity DID (SIP Trunk) 
which goes to my asterisk  IVR. 

If he presses a dtmf during any message, the press is ignored unless the 
press was a #, 0 or *.  Otherwise, he needs to wait for the message to 
stop before the press is hear.

I've tried all the suggestions found searching the wiki, so I ask here 
if there is something else I can try.  The Vitelity trunk is set up as:

dtmfmode=rfc2833
disallow=all
allow=ulaw

Thanks, Bart
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bhfisher.vcf
Type: text/x-vcard
Size: 249 bytes
Desc: not available
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20091001/5f514489/attachment.vcf

Barton Fisher wrote:
> I'm using the latest asterisk-1.4.26.2 and no zaptel trunks used, all
SIP.
> I have one user that is having problems once he connects to asterisk.
> He's dialing from his home phone (pstn) to a Vitelity DID (SIP Trunk)
> which goes to my asterisk  IVR.
> If he presses a dtmf during any message, the press is ignored unless the
> press was a #, 0 or *.  Otherwise, he needs to wait for the message to
> stop before the press is hear.
The problem could be at your provider's system, perhaps you should try
to submit a support ticket. I know Vitelity had different gateways with
different DTMF configurations.

Also... it would be too much bad luck, but I had a bad chinese phone
phone with a bad -row- in the DTMF keyboard, it worked with the telco as
the detection was more relaxed, but not with our old PBX.
> dtmfmode=rfc2833
> disallow=all
> allow=ulaw
Over ulaw you could try to use inband, or auto... your millage may vary.


-- 
Iv?n Stepaniuk
Alba Fot?nica S.L.