FreePBX outbound call routing

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

[JaredBusch]

And make sure you have no caller ID specified in your trunk. I cannot ever say that enough.

Yes it will bitch about it. Ignore it.

[brandon220]

I do have caller ID specified in the trunk as it shows in my attached image above. I has not given any error messages or anything. Seems to be working correctly. What is the recommended way to handle outbound CID?

[JaredBusch]

@brandon220 said in FreePBX outbound call routing:

I do have caller ID specified in the trunk as it shows in my attached image above. I has not given any error messages or anything. Seems to be working correctly. What is the recommended way to handle outbound CID?

I always recommend to only specify the CID in the outbound route. You can potentially have many CID needing specified on a single trunk depending on routing.

The trunk is not supposed to override, but bugs and errors happen. If it is not specified, then it can not override.

[brandon220]

@jaredbusch I will make the change later today. I would rather follow the best practices and methods. I have zero issues with that. It is definitely different than using POTS lines because that is what I was used to with legacy systems. I've learned a TON since first installing FreePBX last year. Wish I would have tried it a long time ago.