[asterisk-bugs] [Asterisk 0014347]: Transfer executes callers channel in wrong context

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Jan 30 02:45:50 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14347 
====================================================================== 
Reported By:                alesz
Assigned To:                otherwiseguy
====================================================================== 
Project:                    Asterisk
Issue ID:                   14347
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0.5 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-27 06:58 CST
Last Modified:              2009-01-30 02:45 CST
====================================================================== 
Summary:                    Transfer executes callers channel in wrong context
Description: 
hen call is transfered using blind or attended transfer using dtmf code
defined in features.conf or using phone transfer (tested on GXP2000 and
polycom 330) it appears callers channel goes to same context as callee's
last context instead of continuing on typed in extension in context defined
by TRANSFER_CONTEXT global variable.
Callee-s channel hangups ok.

Using Asterisk 1.6.0.5 & Freepbx 2.5.1.1. This started happening somewhere
around 1.6.0.3-rc1.

workaround: manually send call to correct context using goto. does not
work with consecutive transfers: first > second > third

====================================================================== 

---------------------------------------------------------------------- 
 (0099115) alesz (reporter) - 2009-01-30 02:45
 http://bugs.digium.com/view.php?id=14347#c99115 
---------------------------------------------------------------------- 
Thanks for testing. I tried this on 1.6.0.3 and it works the same way as
yours. Then I dug a little deeper and found the issue I think is
responsible for this behavior. Try to add h extension in transfer context
like:

[transfer]
exten => h,1,Playback(hello-world)
exten => _600X,1,Answer
exten => _600X,n,Playback(vm-goodbye)
exten => _600X,n,Hangup

when I make a blind transfer, caller first hears hello-world and then
goodbye. I am not sure if this is expected behavior?

Call trace:
-- SIP/13-08441000 answered SIP/338607316-b7614218
-- Started music on hold, class 'default', on SIP/338607316-b7614218
-- <SIP/13-08441000> Playing 'pbx-transfer.gsm' (language 'en')
-- Stopped music on hold on SIP/338607316-b7614218
-- Executing [h at transfers:1] Playback("SIP/338607316-b7614218",
"hello-world") in new stack
-- <SIP/338607316-b7614218> Playing 'hello-world.gsm' (language 'en')
-- Executing [6000 at transfers:1] Answer("SIP/338607316-b7614218", "") in
new stack
-- Executing [6000 at transfers:2] Playback("SIP/338607316-b7614218",
"vm-goodbye") in new stack
-- <SIP/338607316-b7614218> Playing 'vm-goodbye.gsm' (language 'en')
-- Executing [6000 at transfers:3] Hangup("SIP/338607316-b7614218", "") in
new stack
 Spawn extension (transfers, 6000, 3) exited non-zero on
'SIP/338607316-b7614218' 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-30 02:45 alesz          Note Added: 0099115                          
======================================================================




More information about the asterisk-bugs mailing list