vicidial.org

Dears,

Info about my Install

VERSION: 2.9-441a
BUILD: 140612-1628
© 2014 ViciDial Group

I have been using ViciDial for years now. I have this strange issue,

Inbound calls do not seem to work. Anything that routes through the AGI seems to hangUp the call immediately. I am able to ring the extensions from dialplan directly (Dial SIP/EXTEN), but anything going over agi-DID_route.agi seems immediately hangup.

I am sure its not an Asterisk issue, rather to do something with the agi. Here is a trace,

Please help !

Code: Select all

    -- Executing [7053003@trunkinbound:1] AGI("SIP/10.10.10.10-00000064", "agi-DID_route.agi") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
<SIP/10.10.10.10-00000064>AGI Tx >> agi_request: agi-DID_route.agi
<SIP/10.10.10.10-00000064>AGI Tx >> agi_channel: SIP/10.10.10.10-00000064
<SIP/10.10.10.10-00000064>AGI Tx >> agi_language: en
<SIP/10.10.10.10-00000064>AGI Tx >> agi_type: SIP
<SIP/10.10.10.10-00000064>AGI Tx >> agi_uniqueid: 1556554916.125
<SIP/10.10.10.10-00000064>AGI Tx >> agi_version: 1.8.23.0-1_centos5.go RPM by demian@goautodial.com
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callerid: 047053000
<SIP/10.10.10.10-00000064>AGI Tx >> agi_calleridname: unknown
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callingpres: 0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callingani2: 0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callington: 0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callingtns: 0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_dnid: 7053003
<SIP/10.10.10.10-00000064>AGI Tx >> agi_rdnis: unknown
<SIP/10.10.10.10-00000064>AGI Tx >> agi_context: trunkinbound
<SIP/10.10.10.10-00000064>AGI Tx >> agi_extension: 7053003
<SIP/10.10.10.10-00000064>AGI Tx >> agi_priority: 1
<SIP/10.10.10.10-00000064>AGI Tx >> agi_enhanced: 0.0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_accountcode:
<SIP/10.10.10.10-00000064>AGI Tx >> agi_threadid: 47311749626176
<SIP/10.10.10.10-00000064>AGI Tx >>
    -- <SIP/10.10.10.10-00000064>AGI Script agi-DID_route.agi completed, returning 0
    -- Executing [7053003@trunkinbound:2] Hangup("SIP/10.10.10.10-00000064", "") in new stack
  == Spawn extension (trunkinbound, 7053003, 2) exited non-zero on 'SIP/10.10.10.10-00000064'
    -- Executing [h@trunkinbound:1] AGI("SIP/10.10.10.10-00000064", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
AGI Tx >> agi_network: yes
AGI Tx >> agi_network_script: call_log--HVcauses--PRI-----NODEBUG-----16---------------
<SIP/10.10.10.10-00000064>AGI Tx >> agi_request: agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------
<SIP/10.10.10.10-00000064>AGI Tx >> agi_channel: SIP/10.10.10.10-00000064
<SIP/10.10.10.10-00000064>AGI Tx >> agi_language: en
<SIP/10.10.10.10-00000064>AGI Tx >> agi_type: SIP
<SIP/10.10.10.10-00000064>AGI Tx >> agi_uniqueid: 1556554916.125
<SIP/10.10.10.10-00000064>AGI Tx >> agi_version: 1.8.23.0-1_centos5.go RPM by demian@goautodial.com
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callerid: 047053000
<SIP/10.10.10.10-00000064>AGI Tx >> agi_calleridname: unknown
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callingpres: 0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callingani2: 0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callington: 0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_callingtns: 0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_dnid: 7053003
<SIP/10.10.10.10-00000064>AGI Tx >> agi_rdnis: unknown
<SIP/10.10.10.10-00000064>AGI Tx >> agi_context: trunkinbound
<SIP/10.10.10.10-00000064>AGI Tx >> agi_extension: h
<SIP/10.10.10.10-00000064>AGI Tx >> agi_priority: 1
<SIP/10.10.10.10-00000064>AGI Tx >> agi_enhanced: 0.0
<SIP/10.10.10.10-00000064>AGI Tx >> agi_accountcode:
<SIP/10.10.10.10-00000064>AGI Tx >> agi_threadid: 47311749626176
<SIP/10.10.10.10-00000064>AGI Tx >>
    -- <SIP/10.10.10.10-00000064>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0
<SIP/10.10.10.10-00000064>AGI Tx >> HANGUP



Here is the dump of my FastAGI

Code: Select all

2019-04-29 22:57:24|VDfastAGI|begin|+++++++++++++++++ FastAGI Start ++++++++++++++++++++++++++++++++++++++++
2019-04-29 22:57:24|VDfastAGI|begin|Perl Environment Dump:
2019-04-29 22:57:24|VDfastAGI|begin|0|--debug
2019-04-29 22:57:24|VDfastAGI|begin|URL HVcauses: |PRI|NODEBUG|16|||0|
2019-04-29 22:57:24|VDfastAGI|begin|AGI Environment Dump:
2019-04-29 22:57:24|VDfastAGI|begin| -- accountcode =
2019-04-29 22:57:24|VDfastAGI|begin| -- callerid = 045867400
2019-04-29 22:57:24|VDfastAGI|begin| -- calleridname = unknown
2019-04-29 22:57:24|VDfastAGI|begin| -- callingani2 = 0
2019-04-29 22:57:24|VDfastAGI|begin| -- callingpres = 0
2019-04-29 22:57:24|VDfastAGI|begin| -- callingtns = 0
2019-04-29 22:57:24|VDfastAGI|begin| -- callington = 0
2019-04-29 22:57:24|VDfastAGI|begin| -- channel = SIP/10.10.10.10-000000ac
2019-04-29 22:57:24|VDfastAGI|begin| -- context = trunkinbound
2019-04-29 22:57:24|VDfastAGI|begin| -- dnid = 7053003
2019-04-29 22:57:24|VDfastAGI|begin| -- enhanced = 0.0
2019-04-29 22:57:24|VDfastAGI|begin| -- extension = h
2019-04-29 22:57:24|VDfastAGI|begin| -- language = en
2019-04-29 22:57:24|VDfastAGI|begin| -- network = yes
2019-04-29 22:57:24|VDfastAGI|begin| -- network_script = call_log--HVcauses--PRI-----NODEBUG-----16---------------
2019-04-29 22:57:24|VDfastAGI|begin| -- priority = 1
2019-04-29 22:57:24|VDfastAGI|begin| -- rdnis = unknown
2019-04-29 22:57:24|VDfastAGI|begin| -- request = agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------
2019-04-29 22:57:24|VDfastAGI|begin| -- threadid = 47311598836032
2019-04-29 22:57:24|VDfastAGI|begin| -- type = SIP
2019-04-29 22:57:24|VDfastAGI|begin| -- uniqueid = 1556564243.199
2019-04-29 22:57:24|VDfastAGI|begin| -- version = 1.8.23.0-1_centos5.go RPM by demian@goautodial.com
2019-04-29 22:57:24|VDfastAGI|begin|AGI Variables: |1556564243.199|SIP/10.10.10.10-000000ac|h|SIP|045867400|
2019-04-29 22:57:24|VDfastAGI|call_log|Process to run: |agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------|call_log|END|
2019-04-29 22:57:24|VDfastAGI|call_log||CALL HUNG UP|
2019-04-29 22:57:24|VDfastAGI|call_log|URL HVcauses: |PRI|NODEBUG|16|||0|
2019-04-29 22:57:24|VDfastAGI|call_log||DELETE from live_inbound where uniqueid IN('1556564243.199','1556564243.199') and server_ip='10.10.10.10'|
2019-04-29 22:57:24|VDfastAGI|call_log|+++++ CALL LOG HUNGUP: |1556564243.199|SIP/10.10.10.10-000000ac|h|2019-04-29 22:57:24|min:     1.38|
2019-04-29 22:57:24|VDfastAGI|call_log|DEBUG: NODEBUG
2019-04-29 22:57:24|VDfastAGI|call_log|VD_hangup : 045867400 SIP/10.10.10.10-000000ac 1 0
2019-04-29 22:57:24|VDfastAGI|call_log||SELECT lead_id,callerid,campaign_id,alt_dial,stage,UNIX_TIMESTAMP(call_time),uniqueid,status,call_time,phone_code,phone_number,queue_position FROM vi
cidial_auto_calls where uniqueid = '1556564243.199' or callerid = '045867400' limit 1;|
2019-04-29 22:57:24|VDfastAGI|call_log|VD hangup: no VDAC record found: 1556564243.199 045867400



What does the agiout logfile output look like for this call?

Also, you are running code that is almost 5 years old, we would strongly suggest upgrading to the most recent svn/trunk revision. There are serious bugs and security exploits in the code you are using.

circuit wrote:Dears,

Info about my Install

VERSION: 2.9-441a
BUILD: 140612-1628
© 2014 ViciDial Group

I note in the dumps that you're likely using goautodial. Please post your installer with full version (and a link to the installation instructions you used if this is not a Vicidial installation .iso installer).

I also note you did not post the configuration information for the inbound call. If misconfigured, inbound calls will terminate in this manner. If the DID does not exist, it will default to the "default" DID (if it's still there). Whether the default DID or a configured DID, if the DID is misconfigured to an impossible destination, "hangup" is the result. The logs (as suggested by Matt) should clue you in as to what happened and why. But a very common failure is configuring the DID to route to "ingroup" and failing to configure a valid ingroup below the route section in the DID configuration (which is obviously required).