Page 1 of 1

Networking restrictions exist for AST_VDadapt.pl?

PostPosted: Thu Feb 01, 2024 3:44 pm
by njr
Hello all,

I'm running into an issue trying to use the inbound queue abandon part of VST_VDadapt.pl and an ABANDON_HOPPER_URL to process calls that abandon before talking to an agent with a custom script of mine (just the usual, PHP and non-agent API call).

vicidial_url_log shows it running every minute, url_type is abandonchk. However, url_response is always
Code: Select all
<RESPONSE EMPTY>...etc...connection refused!

Checking the pl I see that it's using wget. If I run wget with the same parameters from the command line, it seems to work fine.
Also, if I run
Code: Select all
/usr/share/astguiclient/AST_VDadapt.pl --campaign=camp --debugX
from a terminal, it also works fine, and vicidial_url_log shows a successful URL response.

So, is there some kind of permission restriction or other network restriction imposed onto the scripts run from...I guess cron? Or I guess really ADMIN_keepalive_ALL.pl?
Is there some other reason why this would fail when running automatically but work when I run the script manually from the same server? Actually, perhaps relevant, but how do I know which server is actually running AST_VDadapt.pl? I'm testing it on the one that I'm sending the initial na_callurl to and in that context /agc/abandon_check_queue.php seems to work fine.

The last bit of weirdness that I could imagine being possibly related in that in the logs showing that the requests fail, wget is resolving the FQDN to the local IP instead of the public IP. However, this also seems to work fine from the command line. I also tried http vs https and they both function in terminal and fail in automated script.

Any insight or ideas appreciated. Thanks!

Re: Networking restrictions exist for AST_VDadapt.pl?

PostPosted: Thu Feb 01, 2024 4:38 pm
by njr
Well I should have trusted my gut more on this one. Changing from the FQDN to the public IP of the server seems to work.

Why? No clue. Any insight appreciated.