Debug inbound without console
Posted: Wed Apr 10, 2019 5:07 pm
So I'm trying to diagnose a sudden SIP 404 issue and we don't have access to asterisk's console.
Our carrier says they are sending the call without any issue and apparently the server is responding 404, however the DID was working just fine. The DID with an issue is an int'l number, but any US based number will work just fine.
I have access to a copy of asterisk's database via replication.
Is there a way to log the incoming calls to an external address (different host) or view asterisk's logs from ViciDial GUI? To be able to review the number pattern and adjust dialplans accordingly.
Some possible ideas that I have are:
* Point the incoming carrier to a different custom context to only do a curl or AGI or some application cmd to an external host with the incoming DID dialed.
* Point the incoming carrier to a different custom context and have it do a AGI(call_log) to save it to the database.
* Any other method available within [trunkinbound] context to allow/view logs of incoming calls that didnt match a DID ?
The DID default is active so as far as I read agi-DID_route.agi at the very least is should be logging the call in vicidial_did_log or call_log or something, shouldn't it?
Thanks.
EDIT:
VERSION: 2.14-679a
BUILD: 180618-2300
Asterisk 1.8
Version: 2.14b0.5
SVN Version: 3006
DB Schema Version: 1549
DB Schema Update Date: 2018-07-10 21:11:03
Our carrier says they are sending the call without any issue and apparently the server is responding 404, however the DID was working just fine. The DID with an issue is an int'l number, but any US based number will work just fine.
I have access to a copy of asterisk's database via replication.
Is there a way to log the incoming calls to an external address (different host) or view asterisk's logs from ViciDial GUI? To be able to review the number pattern and adjust dialplans accordingly.
Some possible ideas that I have are:
* Point the incoming carrier to a different custom context to only do a curl or AGI or some application cmd to an external host with the incoming DID dialed.
* Point the incoming carrier to a different custom context and have it do a AGI(call_log) to save it to the database.
* Any other method available within [trunkinbound] context to allow/view logs of incoming calls that didnt match a DID ?
The DID default is active so as far as I read agi-DID_route.agi at the very least is should be logging the call in vicidial_did_log or call_log or something, shouldn't it?
Thanks.
EDIT:
VERSION: 2.14-679a
BUILD: 180618-2300
Asterisk 1.8
Version: 2.14b0.5
SVN Version: 3006
DB Schema Version: 1549
DB Schema Update Date: 2018-07-10 21:11:03