Internet subscriber remote address

[j.bilodeau]

Unity 4.0.3. I'm trying to import via Unity tool new internet subscriber users with csv file. Unity tells me that my remote address (SMTP:xxxx)is duplicate. That's true but I have always done that and no problem. Is there something new? Those subscribers are users that does not have voice mail but required to be reach by Call handler. Many thanks.

[navinger]

You're right, the Unity Bulk Import wizard won't allow you to create new Internet subscribers via csv file that have the same remote address. This looks like a defect. However, the Unity SA will let you do this. So if you don't have too many Internet subscribers to create, you can use the SA to create them one at a time.

Is the SMTP address a valid email address, or is it some kind of dummy placeholder for the CSV import? If it's a placeholder, then you can still use the CSV file with different remote addresses, like SMTP:xxx1, SMTP:xxx2, ...

Nancy

[navinger]

Well now... There's a defect alright, but turns out the defect is against the SA for allowing the duplicate remote addresses. Remote address maps to the AD targetAddress. AD targetAddress for a Contact is effectively a mailbox (really, a pointer to one, i.e. the unique depository for that object). Exchange will throw an error if you address to a Contact which has a duplicate targetAddress with another object.

Here's the release note enclosure for CSCea06910 (which talks about AMIS, Bridge, and VPIM subscribers, but the same holds for Internet subscribers):

Symptom:

When Unity subscriber addresses message to a Bridge, AMIS or VPIM subscriber,

the message is immediately returned non-deliverable. The following warning(s)

appears in the Application Event Viewer on the Exchange Server:

Event Type: Warning

Event Source: MSExchangeIS

Event Category: General

Event ID: 9514

Date:

Time:

User: N/A

Computer:

Description:

Two objects in the Directory have the same proxy -

/DC=COM/DC=/OU=

unit>/CN=BRIDGE___

and /DC=COM/DC=/OU=/CN=.

For more information, click http://www.microsoft.com/contentredirect.asp.

Condition:

This behavior can occur on Cisco Unity servers after adding a Bridge, AMIS or

VPIM subscriber via the Cisco Unity Administrator for which another subscriber

object and associated AD Contact already exist within the same Active Directory

forest having the same Unity Delivery Location association and the same remote

mailbox value.

The Cisco Unity Administrator does not prevent such a duplicate object from

being created. But when a message is addressed to either the new or pre-

existing

duplicate, the symptoms described above will occur.

Workaround:

Find the subscribers with conflicting Delivery Location and remote mailbox

values. Correct one of the objects so that the Delivery Location and remote

mailbox for each are correct, and the combination of these two values is

not identical.

Note: Except for a few special cases, regular Unity subscribers with

mailboxes do NOT have a remoteaddress. This is expected.

For Cisco Unity 4.0(1) and later, the Cisco Unity Directory Walker tool

(dbwalker) version 3.0.59 and later will identify duplicate remoteaddresses

in the global subscriber table. This includes the version released with

Cisco Unity 4.0(3), and the newest version can always be obtained from

www.ciscounitytools.com.

The Cisco Unity Data Link Explorer can also be used to idenify subscribers

in the global directory with duplicate remoteaddress values by doing the

following:

-Start>Programs>Unity>Cisco Unity Tools Depot

-Select View>Query Builder

-type the following command in the input window:

-----------------------

select

p.remoteaddress,

p.alias,

p.displayname

from

globalsubscriber as p,

globalsubscriber as q

where

p.remoteaddress = q.remoteaddress and

p.alias != q.alias

order by p.remoteaddress

-----------------------

-Click the 'Execute' button

[j.bilodeau]

Thanks for the info. I did change manually the remote adress on my csv file. Due to the fact that there is a case open, I understand that it will be corrected (it use to work). Am I right?(I have other implementation to do..)

[lindborg]

The fact that it used to let you do this is a bug - it wont be changed to work the way it did before (i.e. it shouldn't be allowed to create duplicate SMTP addresses here).

[j.bilodeau]

Thanks Jeff. What about my customers with release 4.0.2. that will upgrade to 4.0.3.? Do you think there will be problems with it?

[lindborg · Accepted solution]

The upgrade wont care about this - it'll upgrade fine.