Skip to main content

Outbound Route matching

Posted by jason@demand.co.za on Wed, 06/12/2013

Hey

We've got Thirdlane 6.1.1.12 installed; and our outbound routes are set up as follows:

http://imgur.com/OH16UNN,cANZTZ3#0

However on Thirdlane 7.0.1.124 when we configure the routes in the same way:

http://imgur.com/OH16UNN,cANZTZ3#1

and dialing a "_+27." number; the call will continuously match the "_+." outbound route instead of matching the more specific "_+27." route.

Any idea how I can get it to honor the more specific route?


Submitted by eeman on Wed, 06/12/2013 Permalink

fundamentally this pattern is flawed since your internal extensions would match some of these right? I mean any length of digits of 2 or more length starting with a 1 or 2 etc.. thats really a bad practice to utilize. At the very least shouldnt it be _1XXX. just to prevent recursive inclusion search order issues?

as far as most specific to least specific, asterisk does work that way, except when you chose to use a realtime database instead of a configuration file for configs. It no longer loads all the routes into memory and finds a more specific route. Instead it searches the database for the first possible match.

Submitted by jason@demand.co.za on Thu, 06/13/2013 Permalink

Generally we start out extensions at 2 so 200 for example, and then we do more specific matching of routes on our gateways; so we haven't had a need to do more strictly defined routes on the PBX box itself.

But your second paragraph answers my questions. Thanks.