Summary:ASTERISK-18616: Call Forward executes callers channel in wrong context
Reporter:Alex Celi (alexceli)Labels:
Date Opened:2011-09-23 13:53:02Date Closed:2011-09-26 09:34:42
Versions: Frequency of
Environment:Call Forward executes callers channel in wrong context Worked Ok in Asterisk 1.8.4Attachments:
Description:When call is transfered using "Forward All" using phone transfer (tested on Polycom 550) it appears callers channel goes to "default" context instead of continuing on same context.
Callee-s channel hangups.

Using Asterisk 1.8.6

workaround: manually send call to correct context using Dial 6677.

   -- Executing [t@entrantes:5] Dial("DAHDI/2-1", "SIP/401,45,Ttm") in new stack
 == Begin MixMonitor Recording DAHDI/2-1
 == Using SIP RTP CoS mark 5
   -- Called SIP/401
   -- Started music on hold, class 'default', on DAHDI/2-1
[Sep 23 13:47:29] WARNING[17604]: mp3/interface.c:216 decodeMP3: Junk at the beginning of frame 49443303
   -- Got SIP response 302 "Moved Temporarily" back from
   -- Now forwarding DAHDI/2-1 to 'SIP/6677::::UDP@' (thanks to SIP/401-0000000d)
 == Using SIP RTP CoS mark 5
[Sep 23 13:47:29] NOTICE[17604]: app_dial.c:858 do_forward: Not accepting call completion offers from call-forward recipient SIP/
 == Using SIP RTP CoS mark 5
[Sep 23 13:47:29] NOTICE[15336]: chan_sip.c:22058 handle_request_invite: Call from '' ( to extension '6677' rejected because extension not found in context 'default'.
   -- SIP/ is circuit-busy
 == Everyone is busy/congested at this time (1:0/1/0)

Direct call to 6677 works.

Creating a "default" context (no existent yet) in my dialplan works.
Comments:By: Leif Madsen (lmadsen) 2011-09-26 09:34:42.875-0500

This is a configuration issue. You need to set the FORWARD_CONTEXT channel variable.