[asterisk-bugs] [Asterisk 0018936]: When transferring a call using the REFER command with replaces enabled, Asterisk drops the call.
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Mar 8 06:14:21 CST 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18936
======================================================================
Reported By: ltc
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18936
Category: Channels/chan_sip/Transfers
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!): 309808
Request Review:
======================================================================
Date Submitted: 2011-03-07 14:10 CST
Last Modified: 2011-03-08 06:14 CST
======================================================================
Summary: When transferring a call using the REFER command
with replaces enabled, Asterisk drops the call.
Description:
When transferring a call using the REFER command with replaces enabled,
Asterisk drops the call with "SIP/2.0 481 Call leg/transaction does not
exist". I have tried performing this on 1.4 SVN, 1.8.3, Trunk SVN 309404,
and 1.8 SVN 309808. All have produced the same result. I have attached the
debug logs with core and sip debugging on. Unfortunately I do not have a
way to perform a successful transfer with REFER to compare against. Line
432 is where the REFER starts. Chan_sip.c starts to process the REFER but
then later drops it on line 538 with the "SIP/2.0 481 Call leg/transaction
does not exist".
======================================================================
----------------------------------------------------------------------
(0132717) davidw (reporter) - 2011-03-08 06:14
https://issues.asterisk.org/view.php?id=18936#c132717
----------------------------------------------------------------------
Either that trace is incomplete, or Asterisk is correctly rejecting the
REFER. There is no previous instance of
21756586-526e-452e-ba52-d404e9d9781e in the trace.
Could you possibly be trying to use Asterisk as a proxy, rather than a
back to back user agent?
REFER does work when done properly.
Issue History
Date Modified Username Field Change
======================================================================
2011-03-08 06:14 davidw Note Added: 0132717
======================================================================
More information about the asterisk-bugs
mailing list