Re: Multi-tenancy options for Hosted provider

[James Aimonetti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

https://en.wikipedia.org/wiki/Wildcard_DNS_record perhaps?

On 05/17/2013 06:59 AM, Alex A wrote:
> Hi All,
>
> I was wondering to get a few suggestions from community on the
> Kazoo project I have a questions about multi-tenancy using mutiple
> SIP domains. There is a bit of concern about this type of
> architecture because a lot of devices being about to support this
> without a proper resolvable DNS entry matching the domain
>
> Some devices in the field support Outbound proxy values which are
> different from the SIP domain. In this case, these devices will
> work with this type of multi-tenant setup once you would configure
> the endpoint with: SIP Domain: tenant.myprovider.com
> Outboundproxy: opensips.myprovider.com
>
> HOWEVER there is a LOT of equipment out there, that resolves to
> the SIP domain(or host) when deciding about where to send traffic
> to (outboundproxy parameter is either missing or disabled by
> default) ; thus forcing the hosted provider to either:
>
> 1) Create a real DNS entry for tenant.myprovider.com - that would
> create management headaches (DNS propagation time, administration
> overhead once you start to really scale etc..)
>
> 2) Tweaking endpoint devices to force the use of outbound proxy -
> in this some instances it is supported, it some it is not (thus
> rendering these endpoints unusable)...
>
> Is there any alternative best practices for multi-tenancy setup?
> Potentially use of a single domain, and unique URI and dialplans
> for each customer? Maybe some alternative DNS setup for
> myprovider.com?
>
> Thank you in advance. Any suggestions would be greatly
> appreciated...
>
> Alex.
>


- --
James Aimonetti
Distributed Systems Engineer / DJ MC_

2600hz | http://2600hz.com
sip:ja...@2600hz.com
tel: 415.886.7905
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRllgTAAoJENc77s1OYoGgPE0H+wfM8TyZLl6yFb4gdf2w6izq
+p8RpZDVAkBNEwHeGgMlms8Y3AGbymCG/+mOaxgqC5BR9X+F29zpH7A4Urz6xtzi
aOWSjnxskzVZ4UXSahqPfmYupnYdrPGizhh702r0XaLSdJcRNKeRnIKYJL0qUeZj
M+HcjsKIOUkx5Y1f3y7jAQuOQrp8XbywUxEv6ykC0WlY7xcr74RoBt/sY18HefO9
BCvpst/gdo2BQYbqL8BidPlisJnXmqAqZMPwCzHi2uDgWdYp6Hkjhz9khQS/fwTk
VN9a2mb4AYFPxluAxugIbSiVoGjNRrLKZsoKVj1RzN2m2G/dF9rVbv0K+breitI=
=ddtq
-----END PGP SIGNATURE-----

[Alex A]

Thank you for the suggestion, James.  

I will definitely look into this. 

Regards,

Alex.

sip:...@2600hz.com

[Joan Jou i Buch]

Hi,
I has been testing create a dns catchall in my DNS sever and it runs
very good.
Example; create a domain mykazoo.com and catchall DNS a record like
*.mykazoo.com pointing my kazoo server IP.
Then you can test ping somethinkyouwant.mykazoo.com and it is poniting
kazoo server IP.

Joan Jou



El 17/05/2013 15:59, Alex A escribi�:

> You received this message because you are subscribed to the Google
> Groups "2600hz-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to 2600hz-users...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Darren Schreiber]

Don't forget that your phones are now pointed to a single server if you do
this. Either you have to own the networking gear and have the ability to
hot-swap the IPs behind the scenes or you should be using a primary and
secondary outbound proxy on any device you can so that if the primary
proxy fails your secondary picks up the slack.

--
Darren Schreiber
CEO / Co-Founder


visit: www.2600hz.com <http://www.2600hz.com/>
sip:dar...@2600hz.com


tel: 415-886-7901




Note: Please do not send support requests to Darren directly. Please use
sup...@2600hz.com

[Alex A]

Thank you all for the input. 

On Fri, May 17, 2013 at 9:59 AM, Alex A <ale...@gtanetworkconsulting.com> wrote:

Hi All,

I was wondering to get a few suggestions from community on the Kazoo project

I have a questions about multi-tenancy using mutiple SIP domains. There is a bit of concern about this type of architecture because a lot of devices being about to support this without a proper resolvable DNS entry matching the domain

Some devices in the field support Outbound proxy values which are different from the SIP domain. In this case, these devices will work with this type of multi-tenant setup once you would configure the endpoint with:

SIP Domain: tenant.myprovider.com 

Outboundproxy: opensips.myprovider.com 

HOWEVER there is a LOT of equipment out there, that resolves to the SIP domain(or host) when deciding about where to send traffic to (outboundproxy parameter is either missing or disabled by default) ; thus forcing the hosted provider to either: 

1) Create a real DNS entry for tenant.myprovider.com - that would create management headaches (DNS propagation time, administration overhead once you start to really scale  etc..)

2) Tweaking endpoint devices to force the use of outbound proxy - in this some instances it is supported, it some it is not (thus rendering these endpoints unusable)... 

Is there any alternative best practices for multi-tenancy setup? 

Potentially use of a single domain, and unique URI and dialplans for each customer?

Maybe some alternative DNS setup for myprovider.com? 

Thank you in advance. 

Any suggestions would be greatly appreciated... 

Alex.

--
You received this message because you are subscribed to the Google Groups "2600hz-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-users...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Phone: +1-416-649-3670 x 1001

[Darren Schreiber]

What did you end up deciding?

[Alex A]

We are currently in planning stage hence considering multiple options however no solid decision yet.

Thank you again.