Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: madadam on March 09, 2011, 06:11:49 AM

Title: Multi-tenant clusters and call routing
Post by: madadam on March 09, 2011, 06:11:49 AM
I've been trying to come up with a simple solution to multi-tenant set up.

I've set up a number of clusters, some of which can call each other, call groups, custom apps etc by setting the "Tenants to include" field in the tenant definition.

However even if you include the default tenant group used to define the dialplan routes they still cannot dial out.

I've defined a number of dialplans in the Routes for each of the types of telephone numbers in Australia. These include emergency numbers, local numbers, long-distance numbers, premium numbers, mobile numbers, information numbers and international numbers.

Now I don't want to have to define all that again for each and every tenant - that would leave me with way too many route definitions.

Is there a better way of doing this for multi-tenant use?

Thanks,

Adam
Title: Re: Multi-tenant clusters and call routing
Post by: SARK devs on March 09, 2011, 10:30:09 PM
Hi there

Quote
Is there a better way of doing this for multi-tenant use?

Multi-Tenant was developed specifically for buildings with multiple corporations sharing a single PBX.   In general they don't wish to share resources, although of course the model does not extend to the actual trunks, because most such enterprises use multiple shared PRI or fat leased line to ship calls.

What many users do is to create one general route with multiple dial plans in it and then simply copy that for each new tenant.  Still others use a different SIP or IAX trunk for each tenant so they don't even share at the account level (this makes billing very easy for the landlord because it is effectively pushed back to the carrier).   The largest single site that I'm curently aware of that uses this feature had around 300 end-points across forty-odd occupants last time I looked.  The dial plan at that site is admittedly large but it isn't unmanageable. 

Including other tenants in a tenant definition only allows the tenant to dial the included tenants' extensions, it doesn't allow the tenant to use the included tenants' routes.

That's how it works I'm afraid.

Kind Regards

S

 


   
Title: Re: Multi-tenant clusters and call routing
Post by: madadam on March 10, 2011, 03:12:26 AM
Thanks guys.

OK so has any cleverdick got a single entry dial-plan for Australia that covers most telephone numbers?

For the moment I'm just using this dialplan: "_13. _18. _6XXXXXXX _8XXXXXXX _9XXXXXXX _02XXXXXXXX _03XXXXXXXX _04XXXXXXXX _07XXXXXXXX _08XXXXXXXX _0011."

Have I forgotten something (don't allow 1900 numbers)? Can I do it better?

Cheers,

Adam
Title: Re: Multi-tenant clusters and call routing
Post by: madadam on March 15, 2011, 05:04:59 AM
For the moment I'm just using this dialplan: "_13. _18. _6XXXXXXX _8XXXXXXX _9XXXXXXX _02XXXXXXXX _03XXXXXXXX _04XXXXXXXX _07XXXXXXXX _08XXXXXXXX _0011."

I've now tightened this up to:

Code: [Select]
000 911 999 _1[38]XXXX _1[38]XXXXXXXX _[689]XXXXXXX _0[23478]XXXXXXXX _0011.
Title: Re: Multi-tenant clusters and call routing
Post by: Teviot on March 16, 2011, 05:17:55 AM
I've now tightened this up to:

Code: [Select]
000 911 999 _1[38]XXXX _1[38]XXXXXXXX _[689]XXXXXXX _0[23478]XXXXXXXX _0011.

In Australia I don't think you need the 911 or 999 included in you dial plan.

Also I think you have missed a little with regards to you 13 & 18 numbers. My susgestion is below

Code: [Select]
000 _1[38]XXXX _1[38]00XXXXXXXX _[689]XXXXXXX _0[23478]XXXXXXXX _0011.
I am not aware of any 18XXXX numbers in Australia. Maybe you could educate me here
Title: Re: Multi-tenant clusters and call routing
Post by: madadam on March 16, 2011, 08:59:50 AM
In Australia I don't think you need the 911 or 999 included in you dial plan.

I just added them for thoroughness for system users who might be in/from US or UK.

Quote
I am not aware of any 18XXXX numbers in Australia. Maybe you could educate me here

No, you're quite right there are no 6 digit 18xxxx numbers but there are apparently 7 digit numbers. Perhaps all 13, 1300, 1800 numbers can be expressed as "1[38]xxx.". What do you think?

Adam
Title: Re: Multi-tenant clusters and call routing
Post by: Teviot on March 16, 2011, 09:38:09 AM
Perhaps all 13, 1300, 1800 numbers can be expressed as "1[38]xxx.". What do you think?

I personally would use this
Code: [Select]
_1[38]X.
Either yours or mine would do the job. If not then a small modification is all that is required.

No, you're quite right there are no 6 digit 18xxxx numbers but there are apparently 7 digit numbers.
Adam

18 numbers to the best of my knowledge are 10 digits unless you know of some numbers that I don't

Code: [Select]
1800XXXXXX
Title: Re: Multi-tenant clusters and call routing
Post by: madadam on March 17, 2011, 04:38:58 AM
Thanks for your suggestions.

You might find this article on Wikipedia useful:

http://en.wikipedia.org/wiki/Telephone_numbers_in_Australia (http://en.wikipedia.org/wiki/Telephone_numbers_in_Australia)

Cheers,

Adam