Summary: | ASTERISK-13141: Transfer AMI event missing "TargetChannel" and "TargetUniqueid" | ||
Reporter: | Chris Maciejewski (chris-mac) | Labels: | |
Date Opened: | 2008-11-30 04:54:14.000-0600 | Date Closed: | 2008-12-08 05:57:00.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/Transfers |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
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@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 | ||
Comments: | By: Jason Parker (jparker) 2008-12-02 17:19:01.000-0600 Without console output (normal and sip debug), it is going to be extremely difficult if not impossible to figure out what's going on. By: Chris Maciejewski (chris-mac) 2008-12-07 14:05:46.000-0600 I am sorry, but can't reproduce this "bug" any more. Perhaps it was a problem with my AMI backend, or bug was resolved by some other patch I applied recently. We should close this issue now. Regards, Chris |