[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
Leandro Dardini (JIRA)
noreply at issues.asterisk.org
Sat Feb 28 13:23:34 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-24795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leandro Dardini updated ASTERISK-24795:
---------------------------------------
Attachment: fulldebug
This is the complete debug log to help you triage the issue. The call has been done from extension 110-DEVEL, calling extension 104 that is routed to an external number using a gosub to another context using the goto statement. The call is then parked by dialing *7 and then recovered from parking lot with *8. The callerID shown is _X. instead of the dialed number.
If the external number is dialed directly, the callerID shown is correct.
> 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: Resources/res_parking
> Affects Versions: 12.8.1, 13.2.0
> Environment: CentOS 6 64 bit
> Reporter: Leandro Dardini
> Assignee: Leandro Dardini
> 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