[Home]

Summary:ASTERISK-13625: DIALEDTIME and TIMEOUT(absolute) in attended transfer doesn't work as expected
Reporter:Konrad Rozycki (krdian)Labels:
Date Opened:2009-02-23 04:43:03.000-0600Date Closed:2009-06-10 12:15:58
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Resources/res_features
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:After upgrade from 1.4.21.1 to 1.4.23.1 i see that DIALEDTIME is set properly on destination channel after attended transfer. Also TIMEOUT(absolute) is canceled on celler channel (show channel says "Time to hangup: 0") after transfer.

****** ADDITIONAL INFORMATION ******

Platform: CentOS 5.2 x86_64

Dumping Info For Channel: Local/206@agents-transfer-d4b4,2:
================================================================================
Info:
Name=               Local/206@agents-transfer-d4b4,2
Type=               Local
UniqueID=           1235329046.97537
CallerID=           B72555
CallerIDName=       test
DNIDDigits=         (N/A)
RDNIS=              (N/A)
State=              Up (6)
Rings=              0
NativeFormat=       0x8 (alaw)
WriteFormat=        0x8 (alaw)
ReadFormat=         0x8 (alaw)
1stFileDescriptor=  -1
Framesin=           0
Framesout=          4
TimetoHangup=       0
ElapsedTime=        0h0m1s
Context=            agents
Extension=          h-TRANSFER
Priority=           5
CallGroup=          
PickupGroup=        
Application=        DumpChan
Data=               (Empty)
Blocking_in=        (Not Blocking)

Variables:
AEXT=293
DB_RESULT=293
DURATION=97
CALLTIME=1
DIALEDTIME=1
ANSWEREDTIME=0
BRIDGEPEER=SIP/2061-15b97d30
DIALEDPEERNUMBER=2061
DIALEDPEERNAME=SIP/2061-15b97d30
DIALSTATUS=ANSWER
AVAILSTATUS=0
AVAILORIGCHAN=SIP/2061
AVAILCHAN=SIP/2061-15e79f80
AGENT_ID=2061
EXT=2061
AGISTATUS=SUCCESS
AGENT_STATE=IDLE
AGENT_EXTEN=2061
CALL_TYPE=TRANSFER
BRIDGEDPEERID=1235329046.97537
TRANSFERERNAME=Local/2066@agents-8edd,1
GLOBAL_UID=1235328950.97510
START_TIME=1235328950
TABSOLUTE=7200
QNAME=test
DNIS=B72555
================================================================================
Comments:By: Konrad Rozycki (krdian) 2009-02-23 10:14:31.000-0600

Sorry, i forgot about queue_log_atxfer patch which i added for logging attended transfers in queue_log. Anyway will be nice to see this feature merged into 1.4 :)
By: Joshua C. Colp (jcolp) 2009-02-23 10:24:15.000-0600

Only bug fixes get merged into the 1.4 tree I'm afraid. So is your patch actually causing this issue?
By: Konrad Rozycki (krdian) 2009-02-23 15:38:37.000-0600

Thank You for answer.
No, it is not. I so hope this patch can fix this issue. I've patched 1.4.21 before with this patch and queue_log_atxfer patch fixed attended transfer in app_queue same issue.
Additionally i found similar issue: http://bugs.digium.com/view.php?id=13185. Probably that issue is relative to mine.
By: Leif Madsen (lmadsen) 2009-06-10 12:15:58

Since issue 13185 was closed by russell as too invasive of a change, and that this issue is related to it, I'm going to close this issue unless someone can think of a good approach here, or if the reporter can provide some sort of patch that would resolve this. Thanks!