FreePBX and VOIP.MS
-
I added 3 DID trunks to a FreePBX install over the weekend. I used @JaredBusch guide and had no issues. The guide shows adding 1 trunk. I set up each trunk individually and put the voip.ms username and password for each. Is that the correct way? I was not sure. They seem to be working fine and call quality is very good. I keep thinking I may have set it up incorrectly. I also changed the option in the account management to tell them I am terminating in a PBX.
-
You just need 1 truck for each POP location you have DIDs on, then inbound routes for each DND.
e.g. If your DIDs are on chicago4.voip.ms then you have a single trunk to chicago4.voip.ms and inbound routes for each DID.
-
@brandon220 said in FreePBX and VOIP.MS:
I added 3 DID trunks to a FreePBX install over the weekend. I used @JaredBusch guide and had no issues. The guide shows adding 1 trunk. I set up each trunk individually and put the voip.ms username and password for each. Is that the correct way? I was not sure. They seem to be working fine and call quality is very good. I keep thinking I may have set it up incorrectly. I also changed the option in the account management to tell them I am terminating in a PBX.
You only use one trunk per POP. All the DID will flow over it.
You handle the call routing per DID with inbound routes.
-
Likely your first trunk is working and the inbound routes are all using it. If you remove the second and third trunk, I bet it still works the same.
-
I was reading on the voip.ms wiki and thought the way you all are describing is the way it should have been done. I just was unsure on how to implement. I will make the changes.
-
@brandon220 said in FreePBX and VOIP.MS:
I was reading on the voip.ms wiki and thought the way you all are describing is the way it should have been done. I just was unsure on how to implement. I will make the changes.
It's definitely a challenge coming from old POTS days, one line/connection = one phone number. It's definitely more like T1's, single connection, many DIDs.
