Summary: | ASTERISK-16068: language resets during blind transfer | ||
Reporter: | Maciej Krajewski (jamicque) | Labels: | |
Date Opened: | 2010-05-07 03:53:07 | Date Closed: | 2011-07-26 14:39:32 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/Transfers |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | I've noticed that when B side of the call makes a blindxfer the language played in phone is always in English despite of the set variables on the channels. Here is my example dialplan: exten => h,2,Hangup exten => t,1,Hangup exten => T,1,Hangup exten => _.,1,Set(CHANNEL(language)=pl) exten => _.,2,Set(LANGUAGE()=pl) exten => 11,3,Dial(SIP/test003,20,Tt) exten => 12,3,Dial(SIP/test004,20,Tt) exten => 13,3,Dial(SIP/test005,20,Tt) exten => _.,n,Hangup and here are the logs: -- Executing [11@CALLEX:1] Set("SIP/test005-00000021", "CHANNEL(language)=pl") in new stack -- Executing [11@CALLEX:2] Set("SIP/test005-00000021", "LANGUAGE()=pl") in new stack -- Executing [11@CALLEX:3] Dial("SIP/test005-00000021", "SIP/test003,20,Tt") in new stack == Using SIP RTP TOS bits 136 == Using SIP RTP CoS mark 4 == Using SIP VRTP TOS bits 136 == Using SIP VRTP CoS mark 4 == Using UDPTL TOS bits 136 == Using UDPTL CoS mark 4 -- Called test003 -- SIP/test003-00000022 is ringing -- SIP/test003-00000022 answered SIP/test005-00000021 -- Started music on hold, class 'default', on SIP/test005-00000021 -- <SIP/test003-00000022> Playing 'pbx-transfer.gsm' (language 'en') | ||
Comments: | By: Leif Madsen (lmadsen) 2011-07-26 14:39:26.629-0500 Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions If this is still an issue, please open a new issue so it can be re-triaged appropriately. Thanks! |