FreePBX outbound call routing

[JaredBusch]

@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.

[brandon220]

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.

[brandon220]

[brandon220]

[brandon220]

[brandon220]

Both trunks are registered in VOIP.MS and show online in the FreePBX dashboard. Inbound calls are working with no issues.

[JaredBusch]

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 on houston2.voip.ms

You 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.

[JaredBusch]

@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.

[brandon220]

Ok... I will do that now. I will report back.

[brandon220]

@jaredbusch There is no manipulation on the trunk.

[JaredBusch]

@brandon220 said in FreePBX outbound call routing:

@jaredbusch There is no manipulation on the trunk.

Ok, so next step. Let's get rid of all that shit. I hate the dial pattern wizard. People have no idea what any of it means and it just makes things confusing.

Tell me how are your users supposed to be dialing the phone?

[brandon220]

@jaredbusch They just pick up the phone and dial a 10-digit number. No prefix. No special anything.

[brandon220]

I changed the trunk to houston2 and now outbound calls are flowing..... I wish I would have known that would cause an issue. I'm learning though and that is what matters. Edit: I did change it inside voip.ms before I changed it in FreePBX. That trunk was NOT registered. It was yesterday.

[JaredBusch]

@brandon220 said in FreePBX outbound call routing:

@jaredbusch They just pick up the phone and dial a 10-digit number. No prefix. No special anything.

This means the only dial pattern you want is NXXNXXXXXX for normal US calling. and 011. for international calling.

How is your dialing mode setup on VoIP.ms?

As you can see if you are set to NANPA, then you do not need to prepend a 1, but it will work if you do.
If you are set to E164, then you are required to send the 1.

Because of this, I simply always send the 1 on the NXXNXXXXXX line.

[brandon220]

Voip.ms is set like your example on NANPA for both trunks.

[JaredBusch]

@brandon220 said in FreePBX outbound call routing:

Voip.ms is set like your example on NANPA for both trunks.

Then, all you want are those two lines as I have above.

[brandon220]

@jaredbusch Ok. Making those changes now.

[brandon220]

All is good now. I REALLY APPRECIATE the assistance. I wish I would have used separate trunks paths from the beginning and avoided the mess. It was a learning experience for sure. I will monitor it and see if anything changes. Again, thank you.

[JaredBusch]

@brandon220 said in FreePBX outbound call routing:

All is good now.

Not quite. You cannot dial 911 yet.

[JaredBusch]

Make a new outbound route.

Name it SAS_e911 or Parish_e911 appropriately.
Mark it as an emergency route, and specify the caller ID that is tied to your address in VoIP.ms's system. Also check the override extension option.

Setup the following two dial patterns. The first is a test to the voip.ms system. the second is the real one.

Finally, make sure the outbound routes for e911 are ordered above all other outbound routes. This way you know that they were processed first.