Good day.
We need the development of a number verification service using Asterisk.
Let me clarify immediately – a standard Asterisk core, without web interfaces like FreePBX or others.
The result should be a configured server that receives verification numbers from clients, and the digits to be voiced when calling the appropriate number.
The outcome must be recorded in a local MySQL database, and an API request should be sent to the billing server to log the successful call.
There may be multiple clients.
The approximate algorithm is as follows:
There is already a website managing clients. When a client activates the service, this website sends an API request to Asterisk with the following parameters:
Next, the client should be able to send API requests to Asterisk, providing the number to verify and the digits to be announced.
Asterisk makes the call, plays the greeting, and announces the verification digits. After each attempt, the following should be done:
Asterisk may produce errors in cases such as:
It is necessary to monitor the call result, and if the call fails due to provider issues (e.g., the subscriber does not answer, is out of coverage, busy, hung up, or if our number is blocked due to non-payment, or if there are no available trunks), then a retry should be made using another number from the array, and this incident should be separately logged.
It is recommended to implement the scripts in PHP. The operating system should be CentOS. Installing Asterisk on the server is also part of the project.
Budget: 27000 UAH Deadline: 20 days
Good day, we are a team of programmers who can do this, we have already done similar projects and can answer all your questions, I think it's better to talk on the phone or in messages.
Budget: 25000 UAH Deadline: 20 days
**Good afternoon. My name is Maria. I have carefully studied your project. Ready to execute.**
📞 **Algorithm of the service operation**
1. **Receiving a request from the client:**
- The client sends an API request to the server with parameters:
- Client identifier and authorization token.
- Voice files (greetings and digits) or instructions to use standard ones.
- Number of digits to be voiced.
- Trunk identifier for the call.
- Array of numbers from which calls can be made.
- URL for WebHook with results.
2. **Initiating the call:**
- The server verifies the client's authorization.
- Selects a number from the provided array.
- Initiates a call via Asterisk, using the chosen trunk.
- Voices the greeting and confirmation digits.
3. **Processing results:**
- Records the call result in the MySQL database.
- Sends the result to the billing server.
- Sends the result to the client via WebHook (if URL is provided).
4. **Error handling:**
- In case of a failed call due to provider issues (e.g., number blocked), the service:
- Attempts to make a call from another number in the array.
- Records the incident in the database.
**Ready to discuss details!**
Budget: 27000 UAH Deadline: 30 days
Hello, I am implementing your task for experience.
...................
....,..............
...................
...................
It is necessary to perform the update, transfer, and configuration of Laravel projects to a new server, ensuring stable operation, security, protection against exploits, and correct functioning of all services after migration. 1. Main tasks Prepare the new server for operation. Transfer project files, databases, configurations, and cron jobs. Update server software. Configure a secure environment for Laravel. Check compatibility of PHP, Laravel, Composer packages, and dependencies. Ensure protection against known exploits, malicious requests, and unauthorized access. Set up SSL certificates. Check the functionality of the websites after the transfer. 2. Transfer of Laravel projects For each project, it is necessary to: Transfer project files. Transfer the database. Transfer the .env configuration. Set directory access permissions: storage bootstrap/cache Check functionality: homepage; admin panel; authorization; forms; API; file uploads; email sending; cron jobs; queue workers.3. Security and protection It is necessary to implement basic and application-level protection: close root access via SSH; configure SSH access only via keys; change the default SSH port if necessary; configure the firewall; allow only necessary ports; install Fail2Ban; hide service versions of Nginx/Apache/PHP; restrict access to .env, .git, backup files, log files; set correct file permissions; check projects for malicious files; check Composer packages for known vulnerabilities; update dependencies if it does not break functionality; configure protection against SQL injection, XSS, CSRF, and path traversal; check the correctness of Laravel APP_ENV and APP_DEBUG; set APP_DEBUG=false in production; configure rate limiting for critical endpoints; check access to storage/uploads; configure protection against PHP execution in upload directories; check access rights to admin panels. 4. SSL and domains It is necessary to: Install SSL certificates. Configure automatic SSL renewal. Enable redirect from HTTP to HTTPS. Check the correct operation of websites via HTTPS. 5. Backup It is necessary to configure backup: project files; databases; .env files; uploaded media; cron configurations; Nginx/Apache configurations. Backup should be performed automatically on a schedule. It is preferable to store copies separately from the main server. 6. Post-transfer verification After migration, it is necessary to check: absence of 500/403/404 errors; absence of critical errors in Laravel logs. 9. Result of execution After the work is completed, there should be: Laravel projects successfully transferred to the new server; websites are functioning stably; SSL is configured; the server is protected with basic security settings; access to critical files is restricted; backup is configured; cron and queues are operational; the old server can be turned off after final verification.
We have a dedicated server on Hetzner with a website on Docker (+ Laravel framework) Contact with the developers has been lost Need to: - restore and change server access (probably SSH) - recommend a storage location and set up a full server backup with easy recovery, probably not on Hetzner for security - fix the logo that is not displaying for some reason (it's unclear why the file has become inaccessible) Important - there is no website backup, and there is no room for error. We will only consider experienced specialists.
