How about the ability to Clone a route
Or maybe define global
Or maybe define global outbound routes. All of our customers have the same outbound route setup (well - should have). Trunk, pattern, time etc. same same same. Custom routes should have precedence and maybe an option to disallow a customer to use the global routes (forgot to pay their bill).
For inbound routes I would prefer aliases. That is, you can specify a DID to use the same inbound route as another DID. A more elegant solution would be to first create a named inbound route and then assign DIDs to the route.
/Ole
fyi about the alias, its the
fyi about the alias, its the most preferred method of defining behaviors (define it once and use goto's so you only have to change it once). The only downside is that your cdr will show the final number not the original number. You really don't have to wait for that to get coded. That's a 1 line goto script to create for your script library.
Global routes
Would like to add a vote for globally defined routes as well. I just made a change in all our routes by hand editing (could be dangerous) in outbound.includes.
99% our our MT customers have the same routes - and would need the ability to shut them off.
Thinking out loud here... Could this be accomplished with one macro that sends all outbound calls to a tenant which is setup primarily for outbound routing? e.g.
exten => s,1,Dial(Local/${MACRO_EXTEN}@outgoing-${OUTBOUND_ROUTES})
where OUTBOUND_ROUTES is the tenant ID setup to do the outbound routing.
no that cannot be done.
no that cannot be done. Other, prior, requested features now make this not possible including concurrent call restrictions. Other much older features such as grouping CDR by tenant would stop working and all the calls would show up as just 1 tenant. Changing someone's outbound route is the wrong way to shut off a tenant. You need to review the tenant settings section of pbx manager.
I vote for that!