[asterisk-bugs] [JIRA] (ASTERISK-24613) Wrong NewExten Manager Event sent directly after features.conf Blind Transfer

Matt King, M.A. Oxon. (JIRA) noreply at issues.asterisk.org
Wed Jan 21 07:52:35 CST 2015


    [ https://issues.asterisk.org/jira/browse/ASTERISK-24613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224593#comment-224593 ] 

Matt King, M.A. Oxon. commented on ASTERISK-24613:
--------------------------------------------------

Um, why has this gone back to 'Waiting for feedback'?

The requested debug level logs have been supplied.

> Wrong NewExten Manager Event sent directly after features.conf Blind Transfer
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-24613
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24613
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.0.0, 13.0.1, 13.0.2
>         Environment: Linux server 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
>            Reporter: Maciej Cygan
>            Assignee: Maciej Cygan
>         Attachments: manager.txt, output.txt
>
>
> I have checked if similar issue was already raised but i was not able to find any, if however similar issue was reported i do apologise in advance for raising duplicate. 
> Issue: Wrong AppData and Application is sent in the NewExten event on the first Newexten after a blind transfer. 
> Instead of showing the correct Application and AppData for the new extension and priority, it shows the last Application and AppData from the old extension before the transfer.
> Here is an example, showing how to reproduce the error.
> Extensions.conf :
> {noformat}
> ;TEST CONFIG
> [main]
> exten => _2XXX,1,NoOp(This is the first priority of ${EXTEN})
> exten => _2XXX,n,NoOp(This is the second priority of ${EXTEN} - about to dial SIP/1${EXTEN:1})
> exten => _2XXX,n,Dial(SIP/1${EXTEN:1},,rotwh)
> exten => _2XXX,n,Hangup
> {noformat}
> To reproduce this error you will need 3 phones ( 1001,1005,1007 ).
> Order of exectuion:
> 1007 calls 2001
> 1001 blind transfers to 2005, which dials SIP/1005
> Directly after the transfer, Asterisk log shows the correct dialplan execution in the console output:
> {noformat}
>     -- Executing [2005 at main:1] NoOp("SIP/1007-0000000b", "This is the first priority of 2005") in new stack
>     -- Executing [2005 at main:2] NoOp("SIP/1007-0000000b", "This is the second priority of 2005 - about to dial SIP/1005") in new stack
>     -- Executing [2005 at main:3] Dial("SIP/1007-0000000b", "SIP/1005,,rotwh") in new stack
> {noformat}
> however this is what I get in the first NewExten event output during this execution:
> {noformat}
> Event: Newexten
> Privilege: call,all
> Channel: SIP/1007-0000001d
> ChannelState: 6
> ChannelStateDesc: Up
> CallerIDNum: 1007
> CallerIDName: 1007
> ConnectedLineNum: 1001
> ConnectedLineName: 1001
> AccountCode: 
> Context: main
> Exten: 2005
> Priority: 1
> Uniqueid: 1418398132.45
> Extension: 2005
> Application: Dial
> AppData: SIP/1001,,rotwh
> {noformat}
> The Application and AppData is wrong.  It should read:
> {noformat}
> Application: NoOp
> AppData: This is the first priority of 2005
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list