With two (or more) trunks from same provider, all outgoing calls are on last trunk created

this description is much to vague to be actionable. If you believe there is a bug, please provide specific information describing how one might reproduce that bug or otherwise a description that can be clearly followed up upon. From what is written I don't really understand what your issue is or if it is an operator mis-configuration vs. a problem in the system.

Feel free to reopen the bug if something more specific can be provided.

thanks

Actually it was in part a "brain fart" but there really is an underlying problem. Let's say you have two trunks from the same provider that represent individual accounts. You can route incoming calls to the desired extensions according to the DID number but because outgoing calls are only screened by patterns, you can't say (for example) that all calls originating from extensions 200-249 should always use trunk A and never trunk B (or trunk B only if A is congested), while extensions 250-299 should always use trunk B and never trunk A (or A only if B is congested), especially if you want both groups to be able to dial calls "normally." What's really needed, I think, is some kind of "permissions" system, where extensions have or don't have permission to access any given route or trunks.

(Feel free to close this again, just wanted to further explain what I believe is the root problem. Perhaps this should be more along the lines of a feature request, but I'm not sure exactly what to request.)

I think this is a duplicate (route calls based on calling extension). But I haven't had my espresso yet so I won't close it as such. But in the future - this is a feature request, not a bug.

For the anonymous reporter: for now, you can do what you want by putting extensions in their own context and then only including routes with the desired trunks in those contexts where you want them to have access.

Dupe of #461

Milestone 2.2 deleted