FreePBX outbound call routing
-
@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.
-
@ccwtech Once I get everything fine-tuned I will be making test calls to the PSAP to ensure everything is correct since I just added the new trunk and DIDs last night.
-
@brandon220 said in FreePBX outbound call routing:
@ccwtech Once I get everything fine-tuned I will be making test calls to the PSAP to ensure everything is correct since I just added the new trunk and DIDs last night.
Before you do a test call, find out the non-emergency dispatch number and see if that is allowed and/or what the procedure is that they want you to follow. I know some PSAP's do this differently than others.
-
@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.
You do not need a different TRUNK you only need a different DID.
Edit: But yes, I forgot you are using different trunks for billing reasons..
-
I am having difficulty implementing this and not sure why. I have 3 extensions that I want to use the alternate trunk. In the outbound routes, I put 6x in the caller id field as shown in the examples. The three extensions are 60, 61, and 62. When I try to make an outbound call, I get an "all circuits busy" message. Inbound calls flow to the correct ring group. What am I missing?
-
@brandon220 said in FreePBX outbound call routing:
I am having difficulty implementing this and not sure why. I have 3 extensions that I want to use the alternate trunk. In the outbound routes, I put 6x in the caller id field as shown in the examples. The three extensions are 60, 61, and 62. When I try to make an outbound call, I get an "all circuits busy" message. Inbound calls flow to the correct ring group. What am I missing?
Use 6[012] instead of 6X just to be safe if you are specifically only wanting to use it on 60, 61, and 62.
Specify the outbound CIDBeyond that, it should be a 100% match for the other outbound routes. Same trunks and everything.
-
Outbound CID is specified with the 10 digit number <aaabbbcccc>. I changed the numbers to 6[012] and am trying a call now....
-
Still getting the error message... It makes no sense.
-
-
-
I’m enroute to a potential PBX client meeting. Remind me about this thread later
-
Now they are getting all circuits busy from all extensions on outbound calls. Inbound calls are fine. This is driving me nuts.
-
@brandon220 said in FreePBX outbound call routing:
Now they are getting all circuits busy from all extensions on outbound calls. Inbound calls are fine. This is driving me nuts.
Because you are doing things wrong, obviously.
Stop reacting and changing things.
Post your, redacted, trunk setup.
Then post your outbound routes list.
Then you outbound route detail. -
It has been working fine for months. The only thing I changed yesterday was the CID on the outbound but put it back after it made no difference.
