Using the AMI action, AudioFork doesn't disconnect after call is complete

[jmordica]

When the channel no longer exists, shouldn't this kill the AudioFork (close the websocket connection)? Or do you always have to do a StopAudioFork?

Thanks!

[mustafalii]

Seeing a similar issue, although I'm seeing that the AudioFork is closed, but the TCP Ports (associated with the WS connection) on the asterisk server get stuck in a CLOSE-WAIT state and are never properly closed.

Any ideas what the issue might be here? @nadirhamid

[amilcarsilvestre]

I have the same behavior here, the connections stay stuck in the CLOSE_WAIT state forever.

I think it's a bug unrelated to this one, should I open a new issue, @nadirhamid ?

[amilcarsilvestre]

Just one more piece of information, this bug that leaves all connections stuck in CLOSE_WAIT was introduced by this commit ec71ebe

[nadirhamid]

I have the same behavior here, the connections stay stuck in the CLOSE_WAIT state forever.

I think it's a bug unrelated to this one, should I open a new issue, @nadirhamid ?

I think this is all valuable insight, although it's tough to say whether the CLOSE_WAIT issue is related to @jmordica's concern or not. I think it would be best to open another issue for this.

I will be looking into fixing some of these issues in the next build.

Thanks for your input.