FreePBX outbound call routing
-
@ccwtech said in FreePBX outbound call routing:
@brandon220 said in FreePBX outbound call routing:
@dashrender The reason for the separate trunks is for separate billing for phone service. Granted it is a minimal amount, they still argue over who is paying for what. It is comical to me because they did not split the cost of the phones and the system itself.
Doesn't your ITSP have the ability to show # of minutes from each trunk?
The point would be to only have 1 trunk.
-
@brandon220 said in FreePBX outbound call routing:
@dashrender This might be the easiest. They only have 2-digit extensions. of the 30 extensions, only 4 or 5 would need alternate routes. I'm still pondering this method.
Not the easiest, but the proper option. This is how it is designed to work.
-
@jaredbusch Now I just have to sit down and figure out how to set it up so that it works correctly. So far, they love everything about the system compared to what they had before. The best is how much the phone bills went down. I still have a couple numbers to port over.
-
@Dashrender Lets say my extensions that will use the special route are 60 through 65 - would my dial pattern start with the extension number? That is what I'm guessing by the image you posted above. I do not use codes to grab an "outside line" like dialing 9 then the number. They have however learned to follow the number with # so the call goes out faster.
-
@brandon220 said in FreePBX outbound call routing:
@Dashrender Lets say my extensions that will use the special route are 60 through 65 - would my dial pattern start with the extension number? That is what I'm guessing by the image you posted above. I do not use codes to grab an "outside line" like dialing 9 then the number. They have however learned to follow the number with # so the call goes out faster.
The part that @Dashrender highlighted will hold this
6[0-5]it has nothing to do with the dialpattern. -
@jaredbusch Ok. I have to figure out where to insert the extensions for the route.
-
@brandon220 said in FreePBX outbound call routing:
@jaredbusch Ok. I have to figure out where to insert the extensions for the route.
Huh?
You nmake a new outbound route. setup the normal pattern match, and then add the extension pattern in the final box. done.
Nothing to figure out.
If your extensions are not in a group, you need to either rearrange extensions to put them all together, or you have to duplicate the pattern match in the route for each extension.
-
I could be reading into this wrong.... Do I need to prepend the dialed number with a number to force the calls out a specific trunk?
-
@brandon220 said in FreePBX outbound call routing:
I could be reading into this wrong.... Do I need to prepend the dialed number with a number to force the calls out a specific trunk?
No. look at the screenshot again..
-
The extensions are not in a group.
-
@brandon220 said in FreePBX outbound call routing:
The extensions are not in a group.
K. screenshot inc...
-
@jaredbusch said in FreePBX outbound call routing:
@brandon220 said in FreePBX outbound call routing:
The extensions are not in a group.
K. screenshot inc...
Assuming you have to prepend a 1 (missed the last box there oops) and you make your users dial a 10 digit number always (NXXNXXXXXX) and you want extensions 59,63,42,55 to use this route.
-
@jaredbusch That makes sense now. What was confusing me was the 11xx in the first image. Your example does not include the xx. I will try this afternoon and see what happens.
-
@brandon220 said in FreePBX outbound call routing:
@jaredbusch That makes sense now. What was confusing me was the 11xx in the first image. Your example does not include the xx. I will try this afternoon and see what happens.
011.is for international calling.It means match
011and any number of digits afterwards. -
@brandon220 said in FreePBX outbound call routing:
@jaredbusch That makes sense now. What was confusing me was the 11xx in the first image. Your example does not include the xx. I will try this afternoon and see what happens.
I speficially narrowed my example to make you understand.
But you will potentially need many more dial patterns.
For example. what I gave you above will not enable the users to dial 911.
-
I typically make a 911 route separate from all the rest of the routes.
-
Yes. It makes sense now. I was trying to make it more difficult. Your examples make it all clear. Thank you.
-
Here is the St Louis e911 route from the above screenshot.
Note that I do a pattern match on the extension of
51XXbecause all St Louis extensions are 5100-5199.
The first pattern is the VoIP.ms test number for e911. The second match is simply 911.
The caller ID is forced and this DID in VoIP.ms portal has the physical address for the St. Louis Office.
-
I set up separate e911 addresses in the portal as well. The system covers 3 buildings on 1 city block. I know they are not set up geographically different as yours are but wanted to make sure each group goes out the appropriate trunk - hence the reason for my question. Your examples are very informative.
-
@brandon220 said in FreePBX outbound call routing:
I set up separate e911 addresses in the portal as well. The system covers 3 buildings on 1 city block. I know they are not set up geographically different as yours are but wanted to make sure each group goes out the appropriate trunk - hence the reason for my question. Your examples are very informative.
It's also good to register your VOIP with your local PSAP. Most of them have online registration forms, you can use the same form if they have one for cellular phones.
