[asterisk-bugs] [Asterisk 0010915]: Problems when doing an attended and unattended transfer with Thomson Phones

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Oct 8 13:27:30 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10915 
====================================================================== 
Reported By:                ramonpeek
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10915
Category:                   Channels/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.12.1  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-08-2007 11:34 CDT
Last Modified:              10-08-2007 13:27 CDT
====================================================================== 
Summary:                    Problems when doing an attended and unattended
transfer with Thomson Phones
Description: 
When doing an attended transfer (party A -> B -> C) the phones A & B start
ringing after they finished the active call, but there is no audio
(ghostcalls)

When doing an unattended transfer the phone B (transferrer) start ringing
immediatly after transfering the party A to C.
====================================================================== 

---------------------------------------------------------------------- 
 ramonpeek - 10-08-07 13:27  
---------------------------------------------------------------------- 
I've been looking into the blind-transfer issue for a bit..
I cannot seem to find any reason why Asterisk should inform the
transferrer of a succesfull transfer using a second INVITE request.

The RFC says;
"Unless stated otherwise, the protocol for emitting and responding to
   a REFER request are identical to those for a BYE request in [1].  The
   behavior of SIP entities not implementing the REFER (or any other
   unknown) method is explicitly defined in [1]."

So why is Asterisk sending that second (re-)invite but also send a BYE?

Could anyone please clarify?
Since I don't mind blaming the manufacturer but then I better be correct
in my reply saying; the phone should accept and acknowledge that second
INVITE. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-08-07 13:27  ramonpeek      Note Added: 0071654                          
======================================================================




More information about the asterisk-bugs mailing list