[asterisk-bugs] [JIRA] (ASTERISK-23397) AMI Park when not specifying TimeoutChannel causes announcement and call back to channel specified in Channel argument

Jonathan Rose (JIRA) noreply at issues.asterisk.org
Wed Apr 9 14:09:18 CDT 2014


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

Jonathan Rose commented on ASTERISK-23397:
------------------------------------------

I've also been doing some comparison between the 1.8-11 behaviors of parking against 12's. For the most part, it's behaving as I would expect.  The only real discrepency is that as Rusty noted, in Asterisk 12 the Parked channel in a manager park action gets an announcement.  It shouldn't and I'll fix that.

With regard to the channel attempting to dial itself... this isn't really a bug or a change from 11.  There is no way to test the equivalent manager action of a channel being parked without a timeout channel against versions prior to 12. What can be said about this though is that this is the same behavior as what happens when a channel parks itself using the park extension (700 at parkedcalls by default). It might be more ideal to say that this channel was parked by no channel rather than itself, but to implement such a behavior would require a significant amount to change parking so that a call can be parked without having a channel that was responsible for parking it. I'd be very loathe to try and eliminate that requirement on account of possible ripple effects that extend to Stasis and timeouts. It's probably possible to just deal with the timeout dial while still having the channel be considered as its own parker though.

Right now, in keeping with the historical behavior (or at least the historical behavior since r334840 was pushed back in 2011), AnnounceChannel would be more of a new feature request. Really, it's hard to say how such a thing would even work since playing audio to an active channel is something that may or may not be possible at any given time.  It was pulled from 1.8 because the method used at the time was causing crashes that would have been quite difficult to mitigate. What we could do is something similar to how the park and announce application handles announcements... instead of having a channel that you announce to, you could specify a dial string to announce to, and if that dial string is successfully dialed then the announcement is made.

> AMI Park when not specifying TimeoutChannel causes announcement and call back to channel specified in Channel argument
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23397
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23397
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Features/Parking
>    Affects Versions: 12.0.0, 12.1.0
>            Reporter: Denis
>            Severity: Minor
>         Attachments: call_101_102_cel.xls, call_101_102_cli_messages.txt, call_101_102_events.txt, debug, t_conf.xls, t_extensions.xls, t_sippeus.xls
>
>
> I`ve seen fixed issue with this header on ASTERISK-15127, but absolutely the same bug in 12.1.0-rc1 release. MOH and parkslot number announcment goes to one channel.



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



More information about the asterisk-bugs mailing list