[asterisk-bugs] [Asterisk 0016548]: [patch][regression] Macro executes "h" extension instead of exiting
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jan 29 02:26:41 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16548
======================================================================
Reported By: hajekd
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 16548
Category: Applications/app_dial
Reproducibility: always
Severity: major
Priority: normal
Status: confirmed
Target Version: 1.6.0.22
Asterisk Version: 1.6.0.20
JIRA: SWP-642
Regression: Yes
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-01-05 15:51 CST
Last Modified: 2010-01-29 02:26 CST
======================================================================
Summary: [patch][regression] Macro executes "h" extension
instead of exiting
Description:
Latest version 1.6.0.20 does not correctly hangup calls. We have some
dialplan under extension h which ends with cmd Hangup. Asterisk continue in
dialplan even after calling cmd Hangup. This is not the case with 1.6.0.19
and earlier. This is causing some issues with CDR, etc.
In this example, macro hangupcall is called twice!
- Executing [h at macro-dial:1] Macro("SIP/501-00000003", "hangupcall") in
new stack
-- Executing [s at macro-hangupcall:1] ResetCDR("SIP/501-00000003", "w")
in new stack
-- Executing [s at macro-hangupcall:2] NoCDR("SIP/501-00000003", "") in
new stack
-- Executing [s at macro-hangupcall:3] GotoIf("SIP/501-00000003",
"1?skiprg") in new stack
-- Goto (macro-hangupcall,s,6)
-- Executing [s at macro-hangupcall:6] GotoIf("SIP/501-00000003",
"1?skipblkvm") in new stack
-- Goto (macro-hangupcall,s,9)
-- Executing [s at macro-hangupcall:9] GotoIf("SIP/501-00000003",
"1?theend") in new stack
-- Goto (macro-hangupcall,s,11)
-- Executing [s at macro-hangupcall:11] Hangup("SIP/501-00000003", "") in
new stack
== Spawn extension (macro-hangupcall, s, 11) exited non-zero on
'SIP/501-00000003' in macro 'hangupcall'
== Spawn extension (macro-dial, h, 1) exited non-zero on
'SIP/501-00000003'
== Spawn extension (macro-dial, s, 8) exited non-zero on
'SIP/501-00000003' in macro 'dial'
== Spawn extension (macro-exten-vm, s, 9) exited non-zero on
'SIP/501-00000003' in macro 'exten-vm'
== Spawn extension (from-internal, 502, 1) exited non-zero on
'SIP/501-00000003'
-- Executing [h at from-internal:1] Macro("SIP/501-00000003",
"hangupcall") in new stack
-- Executing [s at macro-hangupcall:1] ResetCDR("SIP/501-00000003", "w")
in new stack
-- Executing [s at macro-hangupcall:2] NoCDR("SIP/501-00000003", "") in
new stack
-- Executing [s at macro-hangupcall:3] GotoIf("SIP/501-00000003",
"1?skiprg") in new stack
-- Goto (macro-hangupcall,s,6)
-- Executing [s at macro-hangupcall:6] GotoIf("SIP/501-00000003",
"1?skipblkvm") in new stack
-- Goto (macro-hangupcall,s,9)
-- Executing [s at macro-hangupcall:9] GotoIf("SIP/501-00000003",
"1?theend") in new stack
-- Goto (macro-hangupcall,s,11)
-- Executing [s at macro-hangupcall:11] Hangup("SIP/501-00000003", "") in
new stack
== Spawn extension (macro-hangupcall, s, 11) exited non-zero on
'SIP/501-00000003' in macro 'hangupcall'
== Spawn extension (from-internal, h, 1) exited non-zero on
'SIP/501-00000003'
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0016106 [patch] Hangup extension executed twice...
======================================================================
----------------------------------------------------------------------
(0117358) hajekd (reporter) - 2010-01-29 02:26
https://issues.asterisk.org/view.php?id=16548#c117358
----------------------------------------------------------------------
Why we should force users to do that? 1.6.0.20 introduces big change in
dialplan behaviour. By the way, my dialplan is from standard freepbx, so
all freepbx users will be afected when they upgrade asterisk. They will
suffer with double CDR records.
Issue History
Date Modified Username Field Change
======================================================================
2010-01-29 02:26 hajekd Note Added: 0117358
======================================================================
More information about the asterisk-bugs
mailing list