[asterisk-bugs] [Asterisk 0013992]: Transfer AMI event missing "TargetChannel" and "TargetUniqueid"
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Dec 8 05:57:00 CST 2008
The following issue has been CLOSED
======================================================================
http://bugs.digium.com/view.php?id=13992
======================================================================
Reported By: chris-mac
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13992
Category: Channels/chan_sip/Transfers
Reproducibility: have not tried
Severity: minor
Priority: normal
Status: closed
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1
SVN Revision (number only!): 158757
Disclaimer on File?: N/A
Request Review:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 2008-11-30 04:54 CST
Last Modified: 2008-12-08 05:57 CST
======================================================================
Summary: Transfer AMI event missing "TargetChannel" and
"TargetUniqueid"
Description:
Sometimes (1 out of about 20 transfers) when doing a transfer (via SIP
'REFER' method - not via asterisk Dial(xxx,xxx,tT) feature) Event sent to
AMI client is missing "TargetChannel" and "TargetUniqueid" data. As shown
below:
[Event] => Transfer
[Privilege] => call,all
[TransferMethod] => SIP
[TransferType] => Blind
[Channel] => SIP/dev-sip.tele500.com-082c2ec8
[Uniqueid] => 1228041534.69
[SIP-Callid] => eucfqzhdwxstcmg at 78.105.1.131
[TargetChannel] =>
[TargetUniqueid] =>
[TransferExten] => 1776
[TransferContext] => transfer
This break call tracking logic I am trying to build with AMI.
Kind regards,
Chris
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2008-12-08 05:57 snuffy Status new => closed
======================================================================
More information about the asterisk-bugs
mailing list