CCMP Windows 2003 Enterprise

[rhobab]

I have installed Cisco Unified Contact Center Managent Portal version 8.0.1 on a Windows Server 2003 R2 Enterprise Edition. The CCMP connects fine to the AW but when I try configuring the connection to the Call Manager it always fails with error 503 Server unavailable. This happens whether I use the AXL user created on Call Manager or the Call Manager administrator.

I have the same scenario installed in a lab environment working fine the only diference being the operating system which is Windows Server 2003 R2 Standard Edition.

All help appreciated

[jonathan.charlton]

If you try navigating to the AXL URL using a web browser does AXL report that it is functioning ok?

I presume that this is connecting to a different Call Manager to that which you have tested in your lab? Does AXL on the Call Manager you are trying to connect to retrieve traffic from any other applications?

I picked this up from the web which may be related...

The new throttling mechanism takes into account the dynamic state of Cisco Unified Communications Manager. It considers the number of outstanding change notifications across the Cisco Unified Communications Manager cluster at any given time. If a node has more than 1,500 outstanding change notifications, AXL stops processing write requests until the outstanding change notifications are below 1,500. During throttling, HTTPS Status-Code: 503 Service Unavailable response and sets AXL performance counters which can be viewed using RTMT. When a 503 Service Unavailable response is returned, Cisco recommends that the application sleep for a number of seconds or milliseconds (as determined by the developer) to allow pending write requests to be processed. The application should then continue submitting requests.

From: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/devguide/7_0_1/ccmdvCh1.html

[rhobab]

Hi Jonathan

In the LAB environment - From my pc and from the server in the lab i can access the https://cm_ip:8443/axl  address in internet explorer.

In the Production environment - From my pc i can access the https://cm_ip:8443/axl but cannot from the server. The server gives an error of not being connected to the internet.

Thanks

Victor

[jonathan.charlton]

I am not aware of anything in R2 that could cause a connectivity issue like this.

You could try disabling the Windows Firewall but I would be suprised if that has anything to do with your problem. Are there any other machines wired to the same switch that you can test connectivity to the Call Manager with?

[rhobab]

I changed some Internet Explorer settings and I can now coneect to https://cm_ip:8443/axl from my pc and the server. CCMP now give error 599.

[slavr]

Can you please confirm what is the server locale for CCMP?

If it is not English-US it is very likely that this is the issue.

The documentation does state that that the installation platform should be set to English-US.

If the server locale is not English-US please set the system to this locale, restart and test once again.

[rhobab]

Hi

I have checked and corrected the locale. It now does not give the error but still does not bring up the connection to the Call Manager. These connections remain red.

[slavr]

Maybe you have checked theese things?

     Is the AXL service strated on UCM?

     Does the UCM user have the correct priviliges?

[rhobab]

Yes I have confirmed that the AXL service is started and that the UCM user has the correct privileges. I have even tried with the ccmadministrator.

[rhobab]

Hi

Just to give a feed back. This issue has been finally solved. The server OS had to be reinstalled and with the Region / locale set to English US. This seems to be very important seeing as CCMP does not work otherwise.