Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sip Trunk Tenanting

Status
Not open for further replies.

Tinos

Technical User
Nov 5, 2014
710
BW
Hi all.
Since SIP trunks cant be tenanted I note from the forum that a work around would be to assign tenants to particular COR groups and use Route Lists.
I am failing to understand how such a setup is done.
Please explain to me how you dedicate a tenant to a COR.
 
Can we start by asking what you are attempting to achieve by this?

i.e. What is the issue if they both have full access to all of the trunks?

**********************************************
What's most important is that you realise ... There is no spoon.
 
The idea is to have Sip Trunks belong to one tenant and PRI to another tenant.
Basically separating trunks between to companies.
 
Well that changes things significantly. You should have mentioned the PRI previously

How many CORs do you currently use for restrictions or do you not have any restrictions?

For Example, I use 10 CORs and Routes as a standard
[ol 1]
[li]Mitel Default - fully restricted[/li]
[li]Overseas/international[/li]
[li]National[/li]
[li]411(NA)[/li]
[li]Toll free[/li]
[li]Local[/li]
[li]Flexible/Spare[/li]
[li]611 (NA) trouble routes to our office[/li]
[li]9911 (NA) 4 digit 911[/li]
[li]911 (NA) Panic 911[/li]
[/ol]


**********************************************
What's most important is that you realise ... There is no spoon.
 
I would like to understand how I can map a tenant to its own COR in order to confine the tenant to a particular Sip Trunk.
Example: Tenant 1 to use only PRI for outgoing and Tenant2 to use only SIP for outgoing.
COR groups are as you mentioned above.
I have Routes 1-10 for Sip and 11-20 for PRI.
How do I make the separation of trunks for outgoing between the tenants?
 
you cant do that using tenants
what you can do is setup routes to be using specific CORS and then set cors agains users to only allow them out via the appropriate trunk

here is a very simplified explanation

company A
Ext 2001 has cor 2
rt 2 = cor 2 using company A trunk
Cor GRP 2 has cor 12 disallowed

company B
Ext 3001 has cor 12
rt 12 = cor 12 using company B trunk
Cor GRP 12 has cor 2 disallowed

ARS digits dialled 0 + 10 digits goes to LIST 2

List 2 has 1st choice rt 2, 2nd choice rt 12

when ext 2001 dials 0+10 digits it is allowed out via Rt2
when ext 3001 ddials 0+10 digits it is barred from Rt2 but alllowed out via Rt12




If I never did anything I'd never done before , I'd never do anything.....

 
Noted but where are you allowing and or disallowing COR ?
 
cor groups
2 - 12 ( means that 12 is disallowed from cor group 2)

i think then you may need assistance from someone that understands ARS on Mitel

If I never did anything I'd never done before , I'd never do anything.....

 
If you are using the restrictions like I posted above and your ARS is designed accordingly, I would design like this

Tenant SIP uses CORs 1-10
Tenant PRI uses CORs 11-20

COR Groups 1-10 block 11-20
COR Groups 11-20 block 1-10

Routes 1-10 use COR GRPs 1-10
Routes 11-20 use COR GRPs 11-20

Route list
1 - 1/11
2 - 2/12
3 - 3/13
Etc

**********************************************
What's most important is that you realise ... There is no spoon.
 
Hi kwbMitel. You are exactly on track but I still don't get blocking is done when yous block in the below:
COR Groups 1-10 block 11-20 <---- how am I blocking 11-20?
COR Groups 11-20 block 1-10 <---- how am I blocking 1-10?
 
COR Groups are used to determine which CORs assigned to devices are restricted

COR Groups 1-10 would contain members 11-20
COR Groups 11-20 would contain members 1-10

My cor groups would look like this in this instance (my numbers always go to 64 because I restrict everything and then allow by removing the CORs of the devices)

Code:
Group   Members            Group   Members
  1      1-64                11      1-64
  2      1,3-64              12      1-11,13-64
  3      1,4-64              13      1-11,14-64
  4      1,5-64              14      1-11,15-64
  5      1,6-64              15      1-11,16-64
  6      1,7-64              16      1-11,17-64
  7      1,8-64              17      1-11,18-64
  8      11-64               18      1-10
  9      11-64               19      1-10
 10      11-64               20      1-10

**********************************************
What's most important is that you realise ... There is no spoon.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top