Hi All, a client has requested that some of the extensions dial out using x trunk and other use y trunk, the 2 trunks are different identities/providers or what ever, but have a single tenant in TL.
So basically ext 100 to 200 need to dial out via trunk x and extension 200 to 300 (say a different office or what ever) must then dial out with trunk y.
I see the trunk patters, and i see custom trunks but im not 100% sure how i can do this within the interface without going under the hood. (i don't mind doing this... just would rather use the interface)
The pattern matching is on the destination number, and i need some sort of condition on the source... any, any thoughts?
Use the Goto command, not the
Use the Goto command, not the Dial command, by doing your own coding for a new script.
the downside to splitting them up into different tenants will be dial-by-name-directory. This won't span multiple tenants.
You could do a bunch of custom coding using the custom tag entry in each extension to store information about which trunk to use. I would try to avoid using different providers for each department. Honestly sourced based routing is a backwards concept anyway. You want to route based on who you are calling and what your rate is to call that area much more than who made the call.
ok, this works
I read a few other posts and see all the issues with this, but i managed to put something in place that works - you just have to edit the outbound.include file
;
[outgoing-unrestricted-TenantA]
ignorepat => ${DIALOUT}
include => outgoing-emergency-TenantA
exten => _XXXX.,1,Macro(tl-dialout-1-trunk,,SIP/TrunkName,,,) ; Outbound Calls
; exten => _60XX,1,Goto(from-inside-TenantA,${EXTEN},1) ; == This is TenantA ==
exten => _70XX,1,Goto(from-inside-TenantB,${EXTEN},1) ; Dial ext on TenantB
exten => _80XX,1,Goto(from-inside-TenantC,${EXTEN},1) ; Dial ext on TenantC
exten => _90XX,1,Goto(from-inside-TenantD,${EXTEN},1) ; Dial ext on TenantD
;
This way the mailbox, timeout and invalids etc all work fine.
or you can make a script that
or you can make a script that works so you dont have to edit outbound.include manually
Sorry, dont follow....
How, would you tell it to use the script on dialing out (in stead of a trunk)?
Can you make the script "type" as a trunk???
Please let me know.. i would rather do it this way.
I'm pondering this - and thinking maybe a better way would be to:
Create a tenant per "department" and assign a trunk for (regular _XXXX.) dialled numbers.
Then for each tenant create a set of outbound routs... like:
_80XX - use trunk A
_90XX - use trunk B
Each tenant would then omit the route that does not pertain them them. (would be internal by default.)
You see the way we need it set up is that each department need to use their own trunk, but be able to dial each other on their extension numbers. The departments will have extension ranges, ie. sales will start with 90... and have 2 number after that. 9001, 9002 and so on.
So the question becomes how do i make a trunk to another tenant? I see custom trunks, what the dial command?
(There are going to be around 15 "departments" at the end, each with their own billing for outbound calls, so i don't really want to get the setup wrong in the first place. (All the same company))
Any advice there Eric?