Is there a way to 'tenant' SIP trunks on the MiVB? I have not found anything in the programming where you can designate them as part of a tenant.
Only thing i can think of is to use COR to restrict it?
What has been your experience with ways around it if it's not possible?
With SIP trunk lines, I've noticed that once phones are in their own tenants (ex tenant 2) so they can control their own night key, that for some reason DIDs that are pointing to a hunt group don't follow the Call Rerouting Always alternative Night modes for the tenants. I'm thinking its because the SIP trunks are actually part of Tenant 1 and are not following the tenant 2's night key. Is this correct thinking?
Are there ways around that?
Only thing i can think of is to use COR to restrict it?
What has been your experience with ways around it if it's not possible?
With SIP trunk lines, I've noticed that once phones are in their own tenants (ex tenant 2) so they can control their own night key, that for some reason DIDs that are pointing to a hunt group don't follow the Call Rerouting Always alternative Night modes for the tenants. I'm thinking its because the SIP trunks are actually part of Tenant 1 and are not following the tenant 2's night key. Is this correct thinking?
Are there ways around that?