And what would happen if they call each other?
They would have a phone call or not?
Nothing wrong with that, that's why we all do this work.
In the CDR's you can see who calls who, so if you receive complaints from
one tenant about an
abusive other tenant you can easily proof this via the CDR's and
remove the abusing tenant's account from SipX.
Or do you have another reason to want to block the calling between
tenants?
Best regards / Mit freundlichen Grüßen / Sincères salutations
Paul Scheepens
> ----- Message from Keith Gearty <[email protected]> on Fri, 10
> Jul 2009 10:02:49 +0100 -----
>
> To:
>
> [email protected]
>
> cc:
>
> 'heros' <[email protected]>, [email protected]
>
> Subject:
>
> Re: [sipx-users] R: Multitenanancy
>
> Todd Hodgen wrote:
> I don?t see a method of having a centralized receptionist for this
> application. Many times a multi-tenant application will be for
> shared resources ? like receptionist. Like Fax machines, etc.
>
> One other aspect of Multi-tenant applications is a common use of
> trunks. In this example, you would need 50 sets of trunks to
> facilitate the application. In a true Multi-tenant application,
> your trunks are a shared resource, which is what provides much of
> the cost benefit.
>
> I think it would be difficult to support this application with
> today?s feature set.
> Maybe I'm misunderstanding this thread, but it seems to me the
> original poster wants to create an environment in which multiple
> companies share the same SipXecs server and the same SIP trunk with
> incoming calls directed at a shared receptionist. SipXecs provides
> this functionality by default, because its as if all the extensions
> belonged to one company. So as the original poster says, the only
> issue is preventing extensions belonging to different tenants from
> calling each other.
>
> There's no direct way to do that in SipXecs, but some SIP phones (eg
> the Snom 3xx) allow you to set a regular expression (although they
> call it a dial plan) to define what is and what isn't a valid
> number. You could use that to allow calls to extensions belonging
> to a particular tenant or the outside line, but no one else.
> Although its a phone setting, it can be configured in a phone group
> in SipXecs and then distributed to the phones through auto-provisioning.
>
> Alternatively, don't overlook the simplicity of giving each user a
> list of the extensions he's allowed to dial, and not telling him
> about the ones he's not allowed to dial.
>
> Best regards,
> Keith._______________________________________________
> sipx-users mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
