If you find yourself still trying to get incoming calls working after several hours (like me), be advised that the default DID settings on voip.ms will not work. You merely have to set up a sub-account and make sure to set the authentication type as user/password authentication. Add your DID's to the sub-account and authenticate with the accountnumber_subaccount convention and use the password you created when setting up the sub-account.
Best posts made by u2communications
-
RE: Setting up a SIP trunk in FreePBX 13
Latest posts made by u2communications
-
RE: Using Vultr for FreePBX 13
@jaredbusch, Awesome as usual Jared. Though mine looks very different - no zones button. I just went to the Networks tab and added my WAN subnet as Trusted (Excluded from Firewall) and I'm all set. I can't believe I didn't see that!
-
RE: Using Vultr for FreePBX 13
This has been super helpful! I started out with the CyberLynk hosting which was nice, but a lot costlier. It included some commercial modules but Vultr is cheaper enough to pay for them fairly quickly. I do have one annoying issue I haven't solved though. I set this up from my home office and I can reach the web gui from there, but can't get to it from my office network. For the life of me I can't find anyplace to allow/block access to the gui. Any ideas?
-
RE: Setting up a SIP trunk in FreePBX 13
If you find yourself still trying to get incoming calls working after several hours (like me), be advised that the default DID settings on voip.ms will not work. You merely have to set up a sub-account and make sure to set the authentication type as user/password authentication. Add your DID's to the sub-account and authenticate with the accountnumber_subaccount convention and use the password you created when setting up the sub-account.