[asterisk-bugs] [Asterisk 0011917]: Not getting answers from get_data in a call-file call
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Feb 4 14:23:46 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11917
======================================================================
Reported By: mavetju
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11917
Category: Resources/res_agi
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.4.17
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 02-04-2008 06:46 CST
Last Modified: 02-04-2008 14:23 CST
======================================================================
Summary: Not getting answers from get_data in a call-file
call
Description:
When I setup a call via a call-file and then drop into an AGI script, the
function GET DATA doesn't return DTMF keys. With the same AGI script called
directly (i.e. without the call-file) the function GET DATA does return
DTMF keys.
======================================================================
----------------------------------------------------------------------
mavetju - 02-04-08 14:23
----------------------------------------------------------------------
As requested: The DTMF is seen by asterisk:
[Feb 5 07:18:47] DEBUG[13833] rtp.c: Sending dtmf: 52 (4), at
202.83.178.13
[Feb 5 07:18:47] DTMF[13833] channel.c: DTMF end '4' received on
SIP/lvl04.barnet.com.au-01446250, duration 100 ms
[Feb 5 07:18:47] DTMF[13833] channel.c: DTMF end accepted with begin '4'
on SIP/lvl04.barnet.com.au-01446250
[Feb 5 07:18:47] DTMF[13833] channel.c: DTMF end passthrough '4' on
SIP/lvl04.barnet.com.au-01446250
[Feb 5 07:18:47] DEBUG[13833] chan_zap.c: Ending VLDTMF digit '4'
Just to remind, the issue here is that is happening on a call initiated by
a call-file.
Issue History
Date Modified Username Field Change
======================================================================
02-04-08 14:23 mavetju Note Added: 0081685
======================================================================
More information about the asterisk-bugs
mailing list