[asterisk-bugs] [Asterisk 0014611]: [patch] SIP Attended Transfer fails
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Mar 10 19:30:28 CDT 2009
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=14611
======================================================================
Reported By: klaus3000
Assigned To: mmichelson
======================================================================
Project: Asterisk
Issue ID: 14611
Category: Channels/chan_sip/Interoperability
Reproducibility: have not tried
Severity: minor
Priority: normal
Status: resolved
Asterisk Version: 1.4.23
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2009-03-05 11:10 CST
Last Modified: 2009-03-10 19:30 CDT
======================================================================
Summary: [patch] SIP Attended Transfer fails
Description:
Hi!
The attended trasfer fails in the following scenario:
PBX: Aterisk 1.4.23
Extensions: 1, 2 and 3
Extension 2 call extension 1.
Extension 1 puts extension 2 on hold.
Extension 1 calls extension 3.
Extension 1 put extensions 3 on hold.
Extension 1 refers extension 3 to extension 2
--> Asterisk sends NOTIFY with message/sipfrag:
SIP/2.0 481 Call leg/transaction does not exist
and the transfer fails.
The failure happens only if the REFER is sent to extension 3. If
extensions 1 refers extension 2 to extension 3, then everything works
fine.
I have tested with recent SNOM and eyebeam clients - same result, transfer
does not work.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-03-10 19:30 svnbot Status assigned => resolved
2009-03-10 19:30 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list