[cisco-voip] Unity Overlapping DNs

[Jason Aarons (US)]

I'm thinking Bunny Killer.

 

Watch the video/read the help and let's see what others say...if no
replies I'd open a TAC case -jason

 

http://www.ciscounitytools.com/Applications/Unity/RemoveSubscriberProper
tiesFromAD/RemoveSubscriberPropertiesFromAD.html

 

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Adam Blomfield
Sent: Monday, March 08, 2010 9:23 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Unity Overlapping DNs

 

I am working with a customer that has several other business units that
also use Cisco Unity. Digital Networking had made the Unity servers
aware of each other, but this had never been a problem until recently
when they were assigned a DID range that overlapped with one of those
used by the other division. When they went to import mailboxes Unity
said that the DTMF Access ID already existed. I know that Dialing
Domains can be used to overcome this scenario, so I went to their Unity
server and on the Primary Location page I changed the Dialing Domain
from None to a unique value. I am still unable to add users as the
exisitng users from the other server still show up in the DTMFAccessID
and GlobalSubscribers tables. How can I reinitialize everything to get
rid of these unwanted users?

-Adam




-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100308/a49d7545/attachment.html>