Solved: Problems with 7936 in Call Manager 4.3

ma.romero · ‎05-25-2009

Hi,

I have installed a Ip Phone 7936 in a cluster of call manager 4.3, and I have one problem into access to the corporate directory. The 7936 show me in the screen "server not found".

I used a LDAP of the Call Manager.

I create a user that controller this Phone.

The phone is functionally correctly except the access of Corporative Directory.

Somebody can hepl me?

Thanks for all.

a greeting.

nesharm2 · ‎05-26-2009

check a previous post.

Might be related to firmware or bug

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=IP%20Telephony&topicID=.ee6c829&fromOutline=&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dde62a7

View solution in original post

nesharm2 · ‎05-26-2009

Just curious did we run the exe for the new firmware ? or you downloaded zip file.

On the phone device page can you try putting the new phone load name and reset the phone.

do you see any error in event viewer-->application logs ? if yes let me know the event id

View solution in original post

nesharm2 · ‎05-26-2009

I found this on CCO may be its related to the issue

This problem arises when the Corporate Directory in use is not the default Corporate Directory that ships with the Cisco Unified Communications Manager(CallManager). Cisco Unified IP Conference Station 7936 does not support Custom Corporate Directory. It only supports the default /CCMCIP/xmldirectory.asp.

Cisco Unified IP Conference Station 7936 does not support all XML tags listed in the IP Phone Services SDK. Also, it does not support the URLs and action tags used specifically by the ldapsearch.asp included with the Cisco IP Phone Services SDK.

In order to overcome this problem, in the Custom Corporate Directory, use the same XML format, script flow, HTML method and action as used by the default Corporate Directory that comes with Cisco Unified Communications Manager(CallManager).

http://www.cisco.com/en/US/products/hw/phones/ps379/products_tech_note09186a0080994299.shtml

View solution in original post

nesharm2 · ‎05-26-2009

check a previous post.

Might be related to firmware or bug

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=IP%20Telephony&topicID=.ee6c829&fromOutline=&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dde62a7

ma.romero · ‎05-26-2009

Thanks for all

ma.romero · ‎05-26-2009

Now, the new firmware is installed but i have a new problem.

When push buttom that it say "Corp Dir", it show me a message that say: "error condition".

What is the meaning of that?

nesharm2 · ‎05-26-2009

What is firmware that you loaded ?

Does the phone shows upgraded phone load ?

ma.romero · ‎05-26-2009

The firmware is: cmterm_7936.3-3-20-0, this is the latest version to Call Manager 4.3

nesharm2 · ‎05-26-2009

Just curious did we run the exe for the new firmware ? or you downloaded zip file.

On the phone device page can you try putting the new phone load name and reset the phone.

do you see any error in event viewer-->application logs ? if yes let me know the event id

ma.romero · ‎05-26-2009

I downloaded the exe file, and install in Call Manager 4.3. It can see that the new firmware is installed in the server.

I enter in the administration web page of the 7936 and i can see that the firmware of the phone is the same that i installed.

In the Event Viewer i don't see nothing.

Only appear Errors that the ID 3, but it is a registered and unregistered phones.

The phone is working ok, only i can't access to the Corporative Directory or LDAP of Call Manager to find other partners.

The LDAP is local and default.

The URLs are with IP's.

No use DNS.

nesharm2 · ‎05-26-2009

I found this on CCO may be its related to the issue

This problem arises when the Corporate Directory in use is not the default Corporate Directory that ships with the Cisco Unified Communications Manager(CallManager). Cisco Unified IP Conference Station 7936 does not support Custom Corporate Directory. It only supports the default /CCMCIP/xmldirectory.asp.

Cisco Unified IP Conference Station 7936 does not support all XML tags listed in the IP Phone Services SDK. Also, it does not support the URLs and action tags used specifically by the ldapsearch.asp included with the Cisco IP Phone Services SDK.

In order to overcome this problem, in the Custom Corporate Directory, use the same XML format, script flow, HTML method and action as used by the default Corporate Directory that comes with Cisco Unified Communications Manager(CallManager).

http://www.cisco.com/en/US/products/hw/phones/ps379/products_tech_note09186a0080994299.shtml

ma.romero · ‎05-26-2009

I know this case.

But my Call Manager is configuring with a LDAP by default, this is the url:

- http:///CCMCIP/authenticate.asp

- http:///CCMCIP/xmldirectory.asp

- http:///CCMCIP/GetTelecasterHelpText.asp

The 7936 hasn't access to the local LDAP and it shows "error condition" when i enter in to "Corp Dir".

ma.romero · ‎05-26-2009

The rest of the phones of the cluster have access to the Corporative LDAP.

7940,7961,...All except the Conference Station 7936

ma.romero · ‎05-28-2009

Hi again,

Do I Have to install a plugin for connect with the Corporative directory?

For example, to Customer Directory is need.

ma.romero · ‎06-03-2009

Hi nesharm2,

Finally I resolve this case. I explain it in the next lines.

I have a cluster of Call Manager 4.3, one publisher and one subscriber. I install the "User Locale" to the language Spain, because, the installation in the client is in Spain and they choosen the language.

I try that the 7936 access to the Corporativer Directory and it failed, because in the System Parameters the User Locale are in Spain. I changed the User Locale to Unites States and English and the 7936 get to Corporative Directory.

It is probably that the 7936 not support other language that only is English and it is the reason by it can't access to the Corporate Directory.

I looking this bug y "bug toolkit" and i didn't find nothing.

I saw the bug of XML files, but nothing of this.