[asterisk-bugs] [Asterisk 0012258]: Call forwarding scenario with Playback() causes dispositions to be reversed
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Mar 31 20:16:08 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12258
======================================================================
Reported By: blitzrage
Assigned To: murf
======================================================================
Project: Asterisk
Issue ID: 12258
Category: CDR/General
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
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: 03-19-2008 00:25 CDT
Last Modified: 03-31-2008 20:16 CDT
======================================================================
Summary: Call forwarding scenario with Playback() causes
dispositions to be reversed
Description:
After looking at the disposition of some CDRs after doing a call forwarding
scenario, it seems the dispostion of the two channels are reversed.
Scenario as follows:
|- CHAN 1 -| |----- CHAN 2 -----|
PSTN -> GW -> SIP -> Asterisk -> Playback() -> SIP -> Dial(SIP/GW2) ->
PSTN
A dispostion of ANSWERED is always encountered on the 2nd channel CDR
record, even when not ringing, but the first CDR record remains at NO
ANSWER.
By removing the Playback(), both channels have the disposition of NO
ANSWER.
======================================================================
----------------------------------------------------------------------
blitzrage - 03-31-08 20:16
----------------------------------------------------------------------
Qwell: correct, which is why I removed the Playback() altogether for the
customer I was seeing this on, but the ANSWERED disposition seemed to be
reversed.
However, this is no longer an issue for me, and since I can't seem to find
the CDR records that this is bug is related to, I'm just gonna close it
until I run into it again.
Issue History
Date Modified Username Field Change
======================================================================
03-31-08 20:16 blitzrage Note Added: 0084827
======================================================================
More information about the asterisk-bugs
mailing list