FreePBX outbound call routing
-
@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.
-
-
-
-
Both trunks are registered in VOIP.MS and show online in the FreePBX dashboard. Inbound calls are working with no issues.
-
I only see one trunk's SIP server settings.
Are both trunks on
houston.voip.ms? That will not work, I can get technical about it, but just trust me. Put one onhouston2.voip.msYou will have to change the DID inside voip.ms also.
This is one reason why I started out at the beginning of this thread questioning why you have multiple trunks. I have had to deal with this also because of desired separated billing.
-
@brandon220 said in FreePBX outbound call routing:
Is this on the trunk or the outbound route?
If trere is any dialed number manipulation on the trunk, delete all of it.
-
Ok... I will do that now. I will report back.
-
@jaredbusch There is no manipulation on the trunk.
