[asterisk-users] Odd Read App Issues
Robert Broyles
robert at poornam.com
Thu Feb 26 13:17:59 CST 2009
I turned on DTMF debugging. It looks like the extra digits coming in are
less than the minimum duration of 100ms
Anyone know how to force that minimum duration?
[Feb 26 12:15:07] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '1'
received on SIP/carrier-c4022740
[Feb 26 12:15:07] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '1' on SIP/carrier-c4022740
[Feb 26 12:15:07] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '1'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:07] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '1' on SIP/carrier-c4022740
[Feb 26 12:15:07] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '1'
received on SIP/carrier-c4022740
[Feb 26 12:15:07] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '1' on SIP/carrier-c4022740
[Feb 26 12:15:07] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '1'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:07] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '1' on SIP/carrier-c4022740
[Feb 26 12:15:07] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '1'
received on SIP/carrier-c4022740
[Feb 26 12:15:07] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '1' on SIP/carrier-c4022740
[Feb 26 12:15:07] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '1'
received on SIP/carrier-c4022740, duration 20 ms
[Feb 26 12:15:07] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '1' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '2'
received on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '2' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '2'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:08] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '2' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '2'
received on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '2' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '2'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:08] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '2' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '2'
received on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '2' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '2'
received on SIP/carrier-c4022740, duration 20 ms
[Feb 26 12:15:08] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '2' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '3'
received on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '3' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '3'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:08] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '3' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '3'
received on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '3' on SIP/carrier-c4022740
[Feb 26 12:15:08] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '3'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:08] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '3' on SIP/carrier-c4022740
[Feb 26 12:15:09] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '4'
received on SIP/carrier-c4022740
[Feb 26 12:15:09] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '4' on SIP/carrier-c4022740
[Feb 26 12:15:09] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '4'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:09] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '4' on SIP/carrier-c4022740
[Feb 26 12:15:09] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '4'
received on SIP/carrier-c4022740
[Feb 26 12:15:09] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '4' on SIP/carrier-c4022740
[Feb 26 12:15:09] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '4'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:09] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '4' on SIP/carrier-c4022740
[Feb 26 12:15:10] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '5'
received on SIP/carrier-c4022740
[Feb 26 12:15:10] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '5' on SIP/carrier-c4022740
[Feb 26 12:15:10] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '5'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:10] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '5' on SIP/carrier-c4022740
[Feb 26 12:15:10] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '5'
received on SIP/carrier-c4022740
[Feb 26 12:15:10] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '5' on SIP/carrier-c4022740
[Feb 26 12:15:10] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '5'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:10] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '5' on SIP/carrier-c4022740
[Feb 26 12:15:10] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '6'
received on SIP/carrier-c4022740
[Feb 26 12:15:10] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '6' on SIP/carrier-c4022740
[Feb 26 12:15:10] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '6'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:10] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '6' on SIP/carrier-c4022740
[Feb 26 12:15:11] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '6'
received on SIP/carrier-c4022740
[Feb 26 12:15:11] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '6' on SIP/carrier-c4022740
[Feb 26 12:15:11] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '6'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:11] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '6' on SIP/carrier-c4022740
[Feb 26 12:15:11] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '7'
received on SIP/carrier-c4022740
[Feb 26 12:15:11] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '7' on SIP/carrier-c4022740
[Feb 26 12:15:11] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '7'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:11] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '7' on SIP/carrier-c4022740
[Feb 26 12:15:11] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '7'
received on SIP/carrier-c4022740
[Feb 26 12:15:11] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '7' on SIP/carrier-c4022740
[Feb 26 12:15:11] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '7'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:11] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '7' on SIP/carrier-c4022740
[Feb 26 12:15:12] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '8'
received on SIP/carrier-c4022740
[Feb 26 12:15:12] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '8' on SIP/carrier-c4022740
[Feb 26 12:15:12] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '8'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:12] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '8' on SIP/carrier-c4022740
[Feb 26 12:15:12] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '8'
received on SIP/carrier-c4022740
[Feb 26 12:15:12] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '8' on SIP/carrier-c4022740
[Feb 26 12:15:12] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '8'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:12] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '8' on SIP/carrier-c4022740
[Feb 26 12:15:12] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '8'
received on SIP/carrier-c4022740
[Feb 26 12:15:12] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '8' on SIP/carrier-c4022740
[Feb 26 12:15:12] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '8'
received on SIP/carrier-c4022740, duration 20 ms
[Feb 26 12:15:12] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '8' on SIP/carrier-c4022740
[Feb 26 12:15:13] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '9'
received on SIP/carrier-c4022740
[Feb 26 12:15:13] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '9' on SIP/carrier-c4022740
[Feb 26 12:15:13] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '9'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:13] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '9' on SIP/carrier-c4022740
[Feb 26 12:15:13] DTMF[3564]: channel.c:2280 __ast_read: DTMF begin '9'
received on SIP/carrier-c4022740
[Feb 26 12:15:13] DTMF[3564]: channel.c:2284 __ast_read: DTMF begin
ignored '9' on SIP/carrier-c4022740
[Feb 26 12:15:13] DTMF[3564]: channel.c:2212 __ast_read: DTMF end '9'
received on SIP/carrier-c4022740, duration 100 ms
[Feb 26 12:15:13] DTMF[3564]: channel.c:2265 __ast_read: DTMF end
passthrough '9' on SIP/carrier-c4022740
After further testing, it seems to only be a problem when the same digit
is entered 2 times or more in a roll.
Any of the digits received with duration of 20ms aren't supposed to be
there, but they show up anyway.
Can someone else check this on their system, and see if this is a problem?
--
Regards,
Robert Broyles
Brent Davidson wrote:
> Robert Broyles wrote:
>> Okay. I'm using this all over SIP Trunking with Vitelity.
>> Any other suggestions?
>> --
>> Regards,
>> Robert Broyles
>>
>>
>>
>>
>> Eric Wieling, Asteria Solutions Group wrote:
>>> Robert Broyles wrote:
>>>
>>>> So I'm using the READ() application within an IVR, and having a strange
>>>> issue, and wondering if anyone else has had this problem.
>>>>
>>>> When calling from an outside line, and entering the digits during the
>>>> read() part of my dialplan, it's accepting some of the digits twice,
>>>> though it's only keyed in once.
>>>>
>>>> When testing the dialplan internally, it accepts only the digits that I
>>>> key in.
>>>>
>>>> Anyone else experienced this?
>>>>
>>>
>>> Yes. Most of the time it is either because I put relaxdtmf=yes in
>>> zapata.conf or because my rxgain is too low on that port.
>>>
>>>
> I've seen an issue similar to this when the sip peer was providing
> DTMF over multiple encodings at the same time. Usually, it's when
> Asterisk is expecting DTMF via inband, but the peer is sending inband
> and either INFO or rfc2833. What do you have the dtmfmode= line set
> to in your sip.conf?
> ------------------------------------------------------------------------
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
DISCLAIMER : This email and any files transmitted with it are property of Poornam Info Vision Pvt. Ltd. This email contains confidential information intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090226/ce696922/attachment.htm
More information about the asterisk-users
mailing list