I have Asterisk running on a Raspberry Pi that talks to a VASQ gateway, with a small Python service on the same Pi forwarding AMI events to our cloud-based campaign manager. Answered calls report fine but when a call is simply left ringing the “no-answer” status never reaches the central server, so campaign statistics remain wrong. The break seems to be somewhere between Asterisk’s event stream and the Python handler on the Pi, yet I’m open to any finding you uncover. You’ll join me through AnyDesk (or your preferred remote desktop tool), dive into the dial-plan, AMI permissions and Python callbacks, reproduce the issue with a couple of test calls, then patch the logic so missed calls are reported instantly. I can provide full Asterisk verbose logs, Python traces and SSH access while we work. The session is expected to last no more than two hours; the sooner we start, the better. Deliverable • Before the session ends, the cloud dashboard must correctly display the “no-answer” status for a test call that rings out. Acceptance criterion Once we see that status update in real time, the job is complete. Share your earliest availability and any specific tools you’ll want on hand (tcpdump, pjsip logger, etc.) so we can get started right away.