hangupcause.c:140 hangupcause_read: Unable to find info

[IPchicken]

Hi, we've just installed a new vicidial(standalone server), everything is working well but there is just one issue that the customer hang up is not being detected, so the agent doesn't realize if the call has hung up in soft phone.

Hope you can help me with this issue.

Code: Select all

[Aug  7 01:36:56]   == Spawn extension (default, 8600051, 1) exited non-zero on 'Local/8600051@default-00000040;2'
[Aug  7 01:36:56] WARNING[3162][C-00000091]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
[Aug  7 01:36:56]     -- Executing [h@default:1] AGI("Local/8600051@default-00000040;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------)") in new stack
[Aug  7 01:36:56]     -- <Local/8600051@default-00000040;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------) completed, returning 0
[Aug  7 01:36:57]   == Manager 'sendcron' logged on from 127.0.0.1
[Aug  7 01:36:57] NOTICE[3233]: manager.c:4413 action_hangup: Request to hangup non-existent channel: Local/8600051@default-00000040;2
[Aug  7 01:36:57]   == Manager 'sendcron' logged on from 127.0.0.1
[Aug  7 01:36:57]     -- Manager 'sendcron' from 127.0.0.1, hanging up channel: Local/58600051@default-00000041;2
[Aug  7 01:36:57]   == Spawn extension (default, 58600051, 1) exited non-zero on 'Local/58600051@default-00000041;2'
[Aug  7 01:36:57] WARNING[3173][C-00000093]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
[Aug  7 01:36:57]     -- Executing [h@default:1] AGI("Local/58600051@default-00000041;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------------)") in new stack
[Aug  7 01:36:57]     -- <Local/58600051@default-00000041;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------------) completed, returning 0
[Aug  7 01:36:57]   == Spawn extension (default, 8309, 3) exited non-zero on 'Local/58600051@default-00000041;1'
[Aug  7 01:36:57] WARNING[3172][C-00000094]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
[Aug  7 01:36:57]     -- Executing [h@default:1] AGI("Local/58600051@default-00000041;1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------------)") in new stack
[Aug  7 01:36:57]     -- <Local/58600051@default-00000041;1>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------------) completed, returning 0


VERSION: 2.14b0.5
BUILD: 190724-1603
Revision: 3130

I have using Vicibox 8.1.2 as a standalone server

[williamconley]

Agents are informed that the calls have hung up by the Vicidial system showing "HUNGUP" in the agent screen's top right corner IF the Vicidial system is configured properly.

If you have edited your .conf files or have an improper Carrier configuration, the Vicidial system may not be aware of the hangup, and that image may not be shown.

However: Your example has nothing to do with this situation. The examples you've shown show termination of an agent session. This often results in the Vicidial system requesting a call to be terminated that has already been terminated, resulting in the error you see. Normal operation, however, not really an error. The system just doesn't bother to check if all channels have been terminated and then "only terminate the still live channels". They just request all channels be terminated and let the ones that are already gone .. fail.

So your example code is unrelated to the problem you asserted.

If you provide an example of ONE test call (no other traffic on the system) from beginning to end ... that may prove useful. Not 3000 lines of unrelated code, just one FULL call.

[ambiorixg12]

You need to make a SIP trace and verify if the BYE request sent by the remote party it is received, I suggest you test with one single call and sip set debug on

This link explain the call termination process in SIP https://tools.ietf.org/html/rfc3261#page-90