[asterisk-bugs] [JIRA] (ASTERISK-26565) chan_unistim on 11, 13, 14 placing call on hold temporarily locks up set

[Jason (JIRA)]

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

Jason commented on ASTERISK-26565:
----------------------------------

I should add I have been applying these to the 11, and 14 strains, but 11 is now so broken, that I think someone should make a decision to either support unistim in 11, or take it out altogether, as it appears it's only supported from 14.1.1 now? 

 warning: implicit declaration of function ‘ast_queue_hold’ 
-And isn't in main/channel.c   ...ouch. 

But ooh323 doesn't work with Nortel commercial equipment, whereas the dumped h323 (NuFone) functions perfectly. So.. Drop chan_unistim from 11 and 13? as there's a fork in the road now. Nortel unistim sets and no businss-grade H323, or no Nortel unistim, just sip and others, and functioning H323. 

I appreciate your work in this, but I'm struggling to keep continuity with the kindly provided patch. ;( 

Oh what to do. The battle of millions of features that half-work, against fewer which work stably.. Hmnn. 

> chan_unistim on 11, 13, 14 placing call on hold temporarily locks up set
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-26565
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26565
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_unistim
>    Affects Versions: 11.24.1, 13.12.1, 14.1.1
>         Environment: Debian Linux x86 Intel, Debian Linux ARMh/ARMl
>            Reporter: Jason
>            Assignee: Igor Goncharovsky
>         Attachments: ASTERISK-26565-v1.diff
>
>
> With a Nortel i2002 (also tested on unknown i2001) places or receives a call, and an audio path is brought up (as in, audio is transmitted and/or received from an application or another channel), eg: a call is established, pressing the hold button properly sets up a bridge of MOH to the other side (they hear music), a caller in this example. At this point, the Nortel set is locked. Icons indicate a call is on hold, but no further buttons effect any function. Looking at debug messages, when the switchhook is pressed, even repeatedly, a message is generated on every press: 
> "WARNING[2075] chan_unistim.c: Close call without sub"
> Interestingly, when the other end of the call hangs-up, the icon on the Nortel set indicates such, but remains locked. The UDP/RTP ports are still held at this point. But, placing a call to the same locked-up set, from any functioning channel, unlocks the set, and CLID etc are there, and ringing away. Answering the call, (on the Nortel set) it's all back to normal, and after parties hang up, both/all UDP/RTP ports are properly released. 
> (Note: ports being released is dependent on the patch from ASTERISK-26561 which fixed this on 7 November, 2016.) This is repeatable on three Nortel sets, acoss releases. 



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