[asterisk-bugs] [JIRA] (ASTERISK-24795) When a call is dialed using a gosub to a different context using the switch/goto statement and the call is parked, recovering the call gives a wrong callerid

Derek Bolichowski (JIRA) noreply at issues.asterisk.org
Sat Mar 28 22:01:34 CDT 2015


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

Derek Bolichowski edited comment on ASTERISK-24795 at 3/28/15 9:59 PM:
-----------------------------------------------------------------------

I am a client of the person who reported the issue. 
We have tried using the "o" dialing option in extensions.ael. This does the opposite of what is required. 

Ex: if I call 5195551111 from 5195552222 and park the call, upon pickup the caller ID shows 5195552222 as this is how "o" is defined -- use original caller ID in all contexts. 

According to the developer, the "b" option will not work for this issue. 

Would it help if I provided our extensions.ael for review?


was (Author: derekb):
I am a client of the person who reported the issue. 
We have tried using the "o" dialing option in extensions.ael. This does the opposite of what is required. 

Ex: if I call 5195551111 from 5195552222 and park the call, upon pickup the caller ID shows 5195551111 as this is how "o" is defined -- use original caller ID in all contexts. 

According to the developer, the "b" option will not work for this issue. 

Would it help if I provided our extensions.ael for review?

> When a call is dialed using a gosub to a different context using the switch/goto statement and the call is parked, recovering the call gives a wrong callerid
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24795
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24795
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/pbx_ael, Resources/res_parking
>    Affects Versions: 11.12.0, 12.8.1, 13.2.0
>         Environment: CentOS 6 64 bit
>            Reporter: Leandro Dardini
>            Assignee: Rusty Newton
>            Severity: Minor
>         Attachments: fulldebug
>
>
> Using AEL language, If an extension calls a number XXX and then park the call, the number XXX being dialed is saved in the parking lot. When the call parked is recovered, the number XXX is transmitted to the calling extension using RPID. If the extension calls the number using a context reached using a gosub and in that context a switch statement is used, the number XXX is lost and being replaced by internal dialplan data, like SW_549_SIP or _X.
> Probably the application breaking the RPID is the "Goto".
> This bad behavior can be tested using this minimal diaplan:
> {code}
> context doDialing {
>         _X. => {
>             Set(a=5);
>             switch (${a}) {
>               case 1: NoOp(one);
>                    break;
>               case 2: NoOp(two);
>                    break;
>               case 3: NoOp(three);
>                    break;
>               case 4: NoOp(four);
>                    break;
>               case 5: NoOp(five);
>                        break;
>             }
>             Dial(SIP/onlytest/998474638374);
>         }
> }
> context internal {
>     104 => {
>        gosub(doDialing,104,1);
>     } 
>     *7 => {
>         Park();
>     }
>  
>     *8 => {
>         ParkedCall();
>     }
> }
> {code}
> And dialing from an extension in the "internal" context the number 104, then transferring to *7 and then recovering the call with *8
> This is the output of the CLI during the call:
> {code}
>     -- Executing [104 at authenticated:1] Gosub("SIP/110-DEVEL-00000016", "doDialing,104,1") in new stack
>     -- Executing [104 at doDialing:1] MSet("SIP/110-DEVEL-00000016", "~~EXTEN~~=104") in new stack
>     -- Executing [104 at doDialing:2] Set("SIP/110-DEVEL-00000016", "a=5") in new stack
>     -- Executing [104 at doDialing:3] Goto("SIP/110-DEVEL-00000016", "sw_4335_5,10") in new stack
>     -- Goto (doDialing,sw_4335_5,10)
>     -- Executing [sw_4335_5 at doDialing:10] NoOp("SIP/110-DEVEL-00000016", "five") in new stack
>     -- Executing [sw_4335_5 at doDialing:11] Goto("SIP/110-DEVEL-00000016", "_X.,4") in new stack
>     -- Goto (doDialing,_X.,4)
>     -- Executing [_X. at doDialing:4] NoOp("SIP/110-DEVEL-00000016", "Finish switch_doDialing_4335") in new stack
>     -- Executing [_X. at doDialing:5] Dial("SIP/110-DEVEL-00000016", "SIP/onlytest/998474638374") in new stack
> {code}
> When getting back the call with *8 the callerid connected appears to be "_X.". 
> This doesn't happen if the call is made without using the switch/goto statement. This doesn't happen if the call is made without using the gosub. This doesn't happen if the dialed number transmit RPID once reconnected.



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



More information about the asterisk-bugs mailing list