[asterisk-bugs] [Asterisk 0007904]: Transfer capability is inherited by a channel after being transfered via atxfer

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Jan 14 07:28:12 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=7904 
====================================================================== 
Reported By:                k-egg
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   7904
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   major
Priority:                   high
Status:                     confirmed
Asterisk Version:           1.2.11 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             09-08-2006 06:37 CDT
Last Modified:              01-14-2008 07:28 CST
====================================================================== 
Summary:                    Transfer capability is inherited by a channel after
being transfered via atxfer
Description: 
PhoneA calls PhoneB (221)
by Dial("mISDN/12-1", "mISDN/1/221|15|tr")
PhoneA is not allowed to initiate transfers at that time.
PhoneB is allowed to.

PhoneB transfers PhoneA to PhoneC(208) (attended trans) 
by Dial("Local/208 at isdn-nt-1-bcec,2", "mISDN/8/208|15|")

now PhoneA now is allowed to initiate transfers: 

for example:
exten => 1,1,Playback(tt-monkeys)
cli output: 
- Started music on hold, class 'default', on Local/208 at isdn-nt-1-bcec,1
    -- Playing 'pbx-transfer' (language 'de')
    -- Executing Playback("Local/1 at macro-dial_intern-e687,2",
"tt-monkeys") in new stack
    -- Playing 'tt-monkeys' (language 'en')



Is this a bug? a feature? or designed to behave like this?
wondering...

kegg
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0010198 Important vulnerability after native tr...
related to          0010897 Parked call inherits transfer capability
====================================================================== 

---------------------------------------------------------------------- 
 sergee - 01-14-08 07:28  
---------------------------------------------------------------------- 
otherwiseguy,

option T is a cruel option.

I think that the case you wrote about isn't a bug.


Then you use option T, caller is able to perfom transfer and callee is
not.

Let's imagine situation:

'A' calls 'B', then 'A' transfers call to 'C'. The final Call looks like
'C' -> 'B'. From asterisk's point of view 'C' is a caller, and 'C' inherits
A's capabilities. So if 'A' was able to transfer and 'B' wasn't, then in
the resulting call ('C' -> 'B') 'C' would be able to transfer and 'B' still
wouldn't.

This logic is a little bit complex, but i don't see anything wrong with it 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-14-08 07:28  sergee         Note Added: 0076879                          
======================================================================




More information about the asterisk-bugs mailing list