Page 1 of 1

Hangup Being Requested Twice

PostPosted: Wed Apr 20, 2016 2:47 pm
by ajax1515
What we are seeing is that a channel is being hung-up and then there is a request to hang-up again... this seems to only happen on calls that have been transferred from one server to another (fill calls) via IAX2

It's only a notice but we're trying really hard to get rid of all potential issues server wide.

Executing [h@default:1] AGI("SIP/carrier1-00009a8f", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----28-----23") in new stack
[Apr 20 15:38:29] -- <SIP/carrier1-00009a8f>AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... -28-----23 completed, returning 0
[Apr 20 15:38:29] -- Hungup 'IAX2/dial5-5313'
[Apr 20 15:38:29] == Spawn extension (default, 192*168*001*025*8600073, 1) exited non-zero on 'SIP/carrier1-00009a8f'
[Apr 20 15:38:29] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 20 15:38:29] NOTICE[17201]: manager.c:3405 action_hangup: Request to hangup non-existent channel: SIP/carrier1-00009a8f

Does anyone have any idea what might be causing this double request?

Re: Hangup Being Requested Twice

PostPosted: Tue Jul 19, 2016 7:19 pm
by williamconley
Every phone call has (at least) two legs. When one of these legs reaches to another server, it is treated differently. If you get a notice that a call terminated (not a warning), you should not try to get rid of the notice. It's entirely possible (perhaps likely, even) that this termination attempt covers the eventuality that an error in the system will leave a leg of a call "open", and this event is there to be very sure this does not happen.

It occurs during the "h" extension which is designed to clean up and update all logs. This is why I say it's likely just a validation of "no longer live". If you check, this extension is in EVERY vicidial context in the dialplan. Not an accident. It's a catch-all agi script that does everything related to "this call has terminated".

If you look, you'll find a perl script, running in a "screen" (screen -list to see them) that is listening on port 4577. That's the script being called and it handles the Magic that is Vicidial.

But: I'm guessing. (Haven't looked specifically.) 8-)