TallPBX
- Thread starter smn
- Start date
There is nothing wrong with using AI to write code when you have the experience to guide it, evaluate its output, and recognize mistakes. Like operating a forklift, using a powerful tool safely requires knowledge and training. Giving someone access to that tool does not automatically qualify them to use it.
I use AI myself, and I accept AI-assisted pull requests when the contributor understands the code they are submitting, has tested it, and can explain their decisions. The contributor remains responsible for the quality and correctness of the work, regardless of how it was produced.
My concern is with people submitting code they do not understand and cannot properly assess. In experienced hands, AI is a powerful development tool. Without the knowledge to identify and correct its mistakes, it can introduce serious problems.
When an admin "impersonates," they are not impersonating a tenant directly. They impersonate a user, and everything that user can see (including that user's tenant context) comes along for the ride.
What is a tenant
A tenant is an organization or customer on the phone system — for example, a company that uses the PBX. Each tenant keeps its own extensions, SIP accounts, and phone settings separate from every other tenant. Two tenants can even use the same extension numbers without clashing, because each one's data stays in its own space.
Admins and impersonation
Admins impersonate users, not tenants. So when an admin impersonates someone, they see exactly what that user sees, including that user's tenant membership. This is how an admin steps into the portal as a customer experiences it.
The two types of tenants
There are two types of tenants: customer and default.
Customer tenants are opened only to the users granted membership in that tenant (and to admins, who can enter one by impersonating a member).
The default tenant is only available to admins. It holds the resources that belong to the system itself, like the default SIP realm. If you do not need the multi-tenant feature, you would run the whole PBX here.
This project looks really promising, especially for such an early stage of development!
The architecture and initial features look very interesting. The only thing I'd really love to see is a REST API for external integrations and automation.
I'd be more than happy to give TallPBX a try and provide feedback!
Keep up the great work!
The architecture and initial features look very interesting. The only thing I'd really love to see is a REST API for external integrations and automation.
I'd be more than happy to give TallPBX a try and provide feedback!
Keep up the great work!
Getting this error on a fresh install:
Code:
[OK] Your project is now ready in /var/www/tallpbx
Whats Next?
===========
* For more detailed documentation, see the https://roadrunner.dev
* To run the application, use the following command: $ rr serve
Configuring FreeSWITCH mod_xml_curl
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package freeswitch-mod-json-cdr
Unable to complete the required APT command after waiting for the package manager lock.
Wait for unattended upgrades to finish, fix any reported package error, then re-run the installer.
✗ TALL Stack (Laravel, Livewire, Tailwind, DaisyUI) failed (exit code: 1)
Stopping because the application setup failed. Fix the reported error and re-run the installer.