Skip to main content

Route Outbound Trunk by Extension

Posted by jlindler on Wed, 08/23/2017

Looking through the forum, I assume in order to route specific trunks by the extension I will need a custom extension. Is this correct, or am I missing a setting?


Submitted by thirdlane on Wed, 08/23/2017 Permalink

It depends on what you want to do. Would adding a prefix to a route where you would assign the trunk and having extension dial it be enough, or you want to force calls from a particular extension or a group of extensions to a specific trunk?

Submitted by jlindler on Mon, 08/28/2017 Permalink

Alex... I'm looking to do the latter... "force calls from a particular extension or a group of extensions to a specific trunk".

Submitted by eeman on Thu, 08/31/2017 Permalink

you can still do this the same way. lets say you make pattern _71*NXXNXXXXXX to use trunk2. You could easily modify the digitmap/dialplan on those devices to take a 10 digit number and add 71* in front of it, etc. each device does it differently but that is a matter of looking up the manuals for those devices. I did this for someone's ATA that went to some call box. They wanted to force its traffic out a specific trunk, so we altered the 1xxxxxxxxxx and xxxxxxxxxx patters to prepend the extra digits.

Submitted by thirdlane on Thu, 08/31/2017 Permalink

If you don't mind creating and using your own script for dialing out, you could add tag to the extensions (advanced tab on the extension page), and then do whatever you need in the script. i.e. prepend digits based on the tag presence, or just use tag as the "prepend digits" and have the route defined accordingly.