Match local extension first, before attempting to match rule in outbound routes.

[sfr33man2]

If I have local extensions that match an outbound rule, how would I make a call go to the local extension first IF it exists, and if not, proceed to look for a rule match in outbound routes?

 

[wardmundy]

Most use a prefix to route calls to an outbound trunk, e.g.


4442445 -> internal call

9|4442445 -> strip off 9 and route as external call

 

[jroper]

Hi

If I have local extensions that match an outbound rule, how would I make a call go to the local extension first IF it exists, and if not, proceed to look for a rule match in outbound routes?

The system kind of does that all by itself.

From my not entirely reliable memory, asterisk when dialling will go for the most precise match on number dialled first. By definition, and extension is going to be pretty exact, so will always select the extension first.

Outbound routes are usually less precise, e.g 1NXX. may be a valid route, therefore, less precise than say extension 11003 which also matches 1nxx.

Hope my rambling explanation clears it up for you.

Joe

 

[sfr33man2]

Thanks for your response. Then something is awry. I have two extensions, one is 5556661111, and the other is 5556662222. 5556661111 dials 5556662222, and while watching the CLI, it matches the NXXNXXXXXX rule one the OB trunk and attempts to pass it through my SIP trunk. Unfortunately I must have OB rules that match internal extensions on this box, or I would start there. Any suggestions on where to go from here?

 

[jroper]

Hi

That's an unusually high number of digits for an extension.

It may be helpful to explain a little further what you are trying to achieve, as there may be a more suitable methodology.

Joe