t VICIDIAL is hanging up the agent channel and session

[ambiorixg12]

For me this looks like a bug, but VICIDIAL is hanging up the local channel and SIP agent channel, if I click on the hangup button on the agent interface. I tested with manual calls

-- Manager 'sendcron' from 127.0.0.1, hanging up channel: Local/8600051@default-00000002;1


Manager 'sendcron' logged on from 127.0.0.1
[May 19 15:43:27] -- Manager 'sendcron' from 127.0.0.1, hanging up channel: SIP/100-00000002
[May 19 15:43:27] -- Hungup 'DAHDI/pseudo-1515890444'



This cause the agent be kicked out of the Agent interface


Fresh install single server

ISO : ViciBox_v9.x86_64-9.0.1.iso MD5 d9caaf9b37dd1b4d33eb4230250919fa

VERSION: 2.14-753a
BUILD: 200518-0828
© 2020 ViciDial Group

[ambiorixg12]

I installed version ViciBox v9.x86_64-9.0.r2.iso and it looks to be fixed, the reason why I'm posting this issue is because the official vicidial website, have the link with the ISO file for the buggy version

[carpenox]

operator error

[mflorell]

This was a bug introduced on Friday and reversed in svn/trunk last night(Tuesday). Upgrade to the latest svn/trunk and it should be fixed. Still have to track down exactly what caused it, but shouldn't be a problem if you are using the latest svn/trunk revision as of this morning.

[ambiorixg12]

operator error

definitely not an operator error I tested it myself twice, and the Matt post confirm it is not that kind of error

[carpenox]

yea i have the latest SVN version so couldnt replicate it, i apologize :p

[mflorell]

I found the bug that was causing this issue and have fixed it in svn/trunk this morning.

[ambiorixg12]

I found the bug that was causing this issue and have fixed it in svn/trunk this morning.

Good to hear that, it is posible to know what was causing this issue ?

[mflorell]

Agent screen volume controls are causing Asterisk crashes with versions 13 and higher, so we've defaulted them to off now for agents logged into Asterisk 13 dialers(There is an options.php setting to turn them back on if desired). This caused a problem with the agent channel not being populated as it should which had caused the bug from 2 weeks ago.