Steve is right... the short answer is Unity is not configured for tenant services application which is what you're trying to do here. I'm currently working with some folks on specing out the changes to Unity necessary to handle this and, of course, multiple alpha directories is near the top of the list. Overlapping numbering plans, however, is pretty far down on my list, frankly, since it raises the complexity bar by an order of magnitude from an admin and a call routing standpoint. For instance when a call forwards from extension 4000 there needs to be a second piece of data that indicates to Unity WHICH extension 4000 this might be... a potential tar pit if sites are not using segmented ports or something really straight forward.
The agenda for tenant services I'm pushing is a model where you have several small tenants being serviced by one large Unity and switch deployment where numbering plans are unique across all users across all tenants. Tenants can be segmented from one another, admin duties can be segmented/restricted on a per-tenant basis (i.e. having tenant specific admin duties), segmented audio text applications, definable exit destinations for all conversations (i.e. subscribers bailing from their message retrieval conversation go somewhere definable instead of the opening greeting), etc... If you have a situation where you need several different switch integrations and overlapping numbering plans, that would seem to call for multiple Unity servers in my mind.
But, of course, I'm open to argument... now's the time since I'm plinking away at this requirements definition...
Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)
