[asterisk-bugs] [Asterisk 0011740]: DTMF problem on 1.4.17
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Feb 7 11:18:04 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11740
======================================================================
Reported By: gserra
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11740
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: minor
Priority: normal
Status: new
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: 01-11-2008 05:55 CST
Last Modified: 02-07-2008 11:18 CST
======================================================================
Summary: DTMF problem on 1.4.17
Description:
Hi,
when a call is being passed over from AS5400 via PRI to SIP into asterisk,
dtmf is working in 1.4.11 but not on 1.4.17
======================================================================
----------------------------------------------------------------------
aragon - 02-07-08 11:18
----------------------------------------------------------------------
Hi Dimas
I was a little hasty in saying my problems with atxfer and automon were
fixed.
I did not test both analog zap and ISDN PRI scenarios until today after
your patch.
Your patch fixed a problem using atxfer and automon on analog PSTN zap
lines BUT did not fix the same problem on a PRI circuit I am using for my
tests.
Outgoing PRI I am able to do an attended transfer or automon perfectly but
on incoming PRI calls I cannot get the atxfer or automon codes to work.
Instead of recording the call on the incoming call when I press my DTMF
*999 the caller hears the DTMF tones and the call is never recorded. Same
applies to atxfer when I dial *2.
I tested this exact scenario on a SIP trunk and it works perfectly
incoming and outgoing so I don't think this is a configuration problem.
I have absolutely no idea what would cause the incoming PRI call to behave
in this way.
Your patch fixed this problem on my analog lines, but not PRI so I suspect
a bug somewhere.
Issue History
Date Modified Username Field Change
======================================================================
02-07-08 11:18 aragon Note Added: 0081851
======================================================================
More information about the asterisk-bugs
mailing list