I have a feature request for you to take a look at if you have the time. We have the need to allow tenant to tenant calls on our MTE thirdlane using the tenants DID’s. taking a poke around I have found that if I edit the outbound.include file and add the following line into the [outgoing-$tenant] context my requirement works e.g.
However there are potentially 2 issues with this method (I’m sure you can think of many more )…
1) This file could get overwritten on a config change
2) I don’t know what the resource impact of doing this would be, because as I see it the file include command presumably eats up memory for every tenant so the bigger your tenant list/DDI list the worse the server gets effected.
An alternative idea that I think would be safer from a resource perspective would be to do the following:
Edit the build template to add the line:
include => inbound-include
Add a context reference to the top of the file:
This method would obviously need any other files that reference #include inbound.include to be change to use include => inbound-include
What do you think? Is this a viable option would the context idea work for inbound.include ? this way I think you could also add logic for a “allow tenant to tenant DID calls” check box somewhere under the tenant or global PBX settings and do some test logic for that value. Let me know if this is something you would consider adding in the future..