I am learning the VoIP domain and I chose VitalPBX as my learning ground since it seems very promising for the market. I got a DID from the VoIP.ms provider and I want to connect their server to mine running VitalPBX. I can’t find any tutorial or any clue to my project on the forum or on the internet in general. I started to practice via Freepbx at the beginning and on this platform I was doing the registration via the creation of the extension but on your software, I seem to understand that the connection and authentication is done via the implementation of a trunk. I don’t know if an expert of the platform or a user willing to share his knowledge would like to help me to understand the VitalPBX methodology. Thank you in advance for any answer to this rather large question and sorry for the way I express myself I speak mainly French.
I must have the wrong search method… So if I understand correctly the whole tutorial content is in the VitalPBX blog and not in the Forum. I will correct this in the future and look in the right place. I have a question for you though. I noticed that VitalPBX offers a free training at the following link;
I have an old Cisco 7941 at home, is it possible to configure sip and register it with Vital PBX or does the platform not support old devices like this one. If this is the case, would you have an inexpensive model that would allow me to take advantage of all the features of Vital PBX to recommend?
Yes I know, but I see the experience more as a challenge knowing that the method is unusual. In which perspective is the 7941 the worst device? With this one I learned how to update the firmware and transfer the configuration files by TFTP. Is the way to do it completely different with more recent hardware. I think I understood that most phones now offer a graphical interface for configuration but otherwise?
Start from the bottom of the ladder. No point if trying to jump straight to the top. First learn the basics and then continue on from there.
TFTP is garbage. You shouldn’t support phones that only support TFTP provisioning. Start with http provisioning, once you figured it out, continue to https provisioning and then https with apache auth. Never ever ever go back to TFTP.
That’s true, but you would still want them to be provisioned instead of configuring each device by hand.