Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Call Manager AD Integration 3.3(2)

I am building a test Call Manager.

I have a test AD domain however it is Cornerstone.IT.

A dot IT instead of dot COM

I go to add the plug-in

I put in my

hostname: NY71.Cornerstone.IT (I also tried just using the IP)

default port

port: 389

DN= cn=Administrator, cn=Users, dc=cornerstone, dc=it

correct and tested adminstrator password

Cisco DN= ou=Cisco, dc=cornerstone, dc=it

User search= cn=Users, dc=cornerstone, dc=it

User Creation= cn=Users, dc=cornerstone, dc=it

Domain Name= dc=cornerstone, dc=it

User Search Attribute= sAMAccountName

I can send screen shots if you like.

Anyway when I hit next I get

"Setup failed to connect. Please enter your hostname, port number, Directory Administrator DN and password again!"

Does Call Manager integrate with .IT?

Is only .COM supported?

Am I missing something?

Any thoughts?

5 REPLIES
Community Member

Re: Call Manager AD Integration 3.3(2)

Hi,

1) Check if your DNS Server is working properly

2) Check VLANs is working properly

2) Add the Call Manager server to the Domain

4) Login to Call Manager with an user with permissions to write to AD

3) If not sure that DNS Server is doing name resolution properly, instead of hostname: NY71.Cornerstone.IT, place the ip address of the AD Server.

Hope it helps

MP

Community Member

Re: Call Manager AD Integration 3.3(2)

I tested DNS and can ping FQN from CM box

I am on a flat 24 port switch, no VLANs or AUX VLANs

Call Manager is in Domain

I am logged in as Administrator. That was one test I used to re-test the password

I also tried just the IP address

Still no go.

Thanks for the input.

Community Member

Re: Call Manager AD Integration 3.3(2)

I've been down this road. I had to use the credentials of our enterprise admin account vice our domain admin account. FYI - We did this and were not happy. Also, if you uninstall this, do not do it through add/remove programs. When you load the plug-in, you will no longer see your DC Directory on the call manager, it will point to the blank Cisco OU you created for the AD plug-in.

Cisco Employee

Re: Call Manager AD Integration 3.3(2)

This should work, we have customers using .info and .net.

Can you make an LDAP connection to the DC from the CCM server using something like LDP.exe from the resource kit?

If you still can't get it going, please open a case with TAC.

Community Member

Re: Call Manager AD Integration 3.3(2)

I just did the LDP.exe

And it connected to the LDAP server..

One odd thing I noticed.

If I fill out the hostname page with Cornerstone.com the next page comes up

cn=Administrator, cn=Users, dc=MyCompany, dc=com

And it needs a manual change.

If I put in .Net, info, org, de, uk, tv, us...

I get the same response

cn=Administrator, cn=Users, dc=MyCompany, dc=com

with a dot dc=com

But when I put in cornerstone.it I get

cn=Administrator, cn=Users, dc=cornerstone,dc=it

and the dc's are automatically changed. For every other extension I tried it did not autofill the DC.

I changed the .IT to a .COM for a goof and it seemed to connect but I got a response back.

Cisco Directory Configuration DN="Cisco, dc=cornerstone,dc=com":no such object found in the directory! Please enter the value again.

So it seems to connect to the server, however it seems to treat .IT differently.

ld = ldap_open("ny71", 389);

Established connection to ny71.

Retrieving base DSA information...

Result <0>: (null)

Matched DNs:

Getting 1 entries:

>> Dn:

1> currentTime: 2/19/2003 23:3:48 Eastern Standard Time Eastern Daylight Time;

1> subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=Cornerstone,DC=IT;

1> dsServiceName: CN=NTDS Settings,CN=NY71,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Cornerstone,DC=IT;

3> namingContexts: CN=Schema,CN=Configuration,DC=Cornerstone,DC=IT; CN=Configuration,DC=Cornerstone,DC=IT; DC=Cornerstone,DC=IT;

1> defaultNamingContext: DC=Cornerstone,DC=IT;

1> schemaNamingContext: CN=Schema,CN=Configuration,DC=Cornerstone,DC=IT;

1> configurationNamingContext: CN=Configuration,DC=Cornerstone,DC=IT;

1> rootDomainNamingContext: DC=Cornerstone,DC=IT;

16> supportedControl: 1.2.840.113556.1.4.319; 1.2.840.113556.1.4.801; 1.2.840.113556.1.4.473; 1.2.840.113556.1.4.528; 1.2.840.113556.1.4.417; 1.2.840.113556.1.4.619; 1.2.840.113556.1.4.841; 1.2.840.113556.1.4.529; 1.2.840.113556.1.4.805; 1.2.840.113556.1.4.521; 1.2.840.113556.1.4.970; 1.2.840.113556.1.4.1338; 1.2.840.113556.1.4.474; 1.2.840.113556.1.4.1339; 1.2.840.113556.1.4.1340; 1.2.840.113556.1.4.1413;

2> supportedLDAPVersion: 3; 2;

12> supportedLDAPPolicies: MaxPoolThreads; MaxDatagramRecv; MaxReceiveBuffer; InitRecvTimeout; MaxConnections; MaxConnIdleTime; MaxActiveQueries; MaxPageSize; MaxQueryDuration; MaxTempTableSize; MaxResultSetSize; MaxNotificationPerConn;

1> highestCommittedUSN: 51212;

2> supportedSASLMechanisms: GSSAPI; GSS-SPNEGO;

1> dnsHostName: ny71.Cornerstone.IT;

1> ldapServiceName: Cornerstone.IT:ny71$@CORNERSTONE.IT;

1> serverName: CN=NY71,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Cornerstone,DC=IT;

2> supportedCapabilities: 1.2.840.113556.1.4.800; 1.2.840.113556.1.4.1791;

1> isSynchronized: TRUE;

1> isGlobalCatalogReady: TRUE;

-----------

131
Views
0
Helpful
5
Replies
CreatePlease to create content