CUC 7.1 with CUCM 10.5

[Ahmad Kefaya]

Dear All,

I have CUC 7.1 and CUCM 10.5 i make integration as SCCP is working, But when i try to add CUCM as AXL Servers give me this error "Failed to send message to remote AXL server. Please check error log for more details."

How i can solve this problem ??

Best Regards

[Venkatesh Perumal]

Hi,

was this setup working fine for you earlier, or is this a new config ? check the below configs!

check if the Cisco AXL Web Service is activated in CUCM from servicability page

make sure that the CUCM AXL userid and password MUST be the same as the one used in CUC

also check if you configured the controlled devices to the AXL_Admin Application User account

Regards,

Venkatesh

[Ahmad Kefaya]

Dear venperum,

I checkd everythings, But it's not working Also...

Regards,

[Chris Deren]

Is your AXL user assigned to the AXL API user group?

Make sure you do not use any special characters in your password.

What if you specify your CUCM admin account (master one you login with) as the axl user?

[Ahmad Kefaya]

Dear Chris,

-Yes it's assign to AXL API group.

-i don't have any special characters in my password.

-i don't understand the last point ?

Regards,

[Chris Deren]

For the last point I suggested to use your master CUCM username as the AXL user, i.e. ccmadministrator, admin, etc. whatever you have defined as master application account on CUCM.

If that does not work you may need to look through AXL logs.

Side question, are you attempting to bring in users from CUCM to UCXN?  Ideally you would use LDAP for which you would not need to define any AXL integration.

Chris

[Ahmad Kefaya]

i try to use my master username & password as AXL user, but is not working.

Yes i attempting to bring user from CUCM ?

But, how i can check the AXL logs ?

Regards,

[Aman Soi]

Make sure you are using the correct AXL username that is it is case sensitive.

regds,

aman

[Ahmad Kefaya]

Dear Aman,

i use it as case sensitive, Also not working..

Regards,

[Aman Soi]

Hi Ahmad,

I was just checking the bug which could be related to the problem u are facing.I suggest opening TAC case.

CUCM 10.0 AXL backward compatibility with Unity Connection

CSCun04092

Description

Symptom:
When integrating CUCM 10.0.1 with Unity Connection prior to 10.0 (8.5, 8.6, 9.1 releases have been tested) in Unity Connection administration will see the following error message:
"Failed to send message to remote AXL server. Please check error log for more details."
No integration of CUCM with Unity Connection is possible because the administrator is unable to save the AXL configuration for the phone system.

Checking the AXL logs on CUCM shows the following:

2014-02-09 08:29:36,322 INFO [http-bio-443-exec-10] filters.TimingFilter - Received request 1385556941727 from ucxnservice at IP XXX.XXX.XXX.XXX
2014-02-09 08:29:36,358 DEBUG [http-bio-443-exec-10] wrappers.RequestHeaderWrapper - Inside Request Header Wrapper
2014-02-09 08:29:36,359 WARN [http-bio-443-exec-10] wrappers.RequestHeaderWrapper - Client sent an unsupported header, SOAPAction= [null], attempting to auto correct.
2014-02-09 08:29:36,359 WARN [http-bio-443-exec-10] wrappers.RequestHeaderWrapper - SOAPAction header correction needed: Version is malformed or missing
2014-02-09 08:29:36,360 WARN [http-bio-443-exec-10] wrappers.RequestHeaderWrapper - SOAPAction header correction needed: Api is malformed or missing
2014-02-09 08:29:36,378 ERROR [http-bio-443-exec-10] filters.NormalizeHeaderFilter - Uncaught exception
java.lang.IllegalArgumentException: Was not able to normalize http request header: SOAPAction is invalid.

This issue is not observed when integrating Unity Connection 10.0 with CUCM 10.0

Conditions:
CUCM 10.0 integrated with Unity Connection below and including 9.1.2 via AXL

Workaround:
None

regds,

aman

[Chris Deren]

Venkatesh provided excellent time (+5) in addition CUC 7 is compatible with CUCM 5+ as seen here using SCCP:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/compatibility/matrix/cucsccpmtx.html

Also, there should be devices assigned to the AXL user, simply ensure the credentials match on both sides and that the credentials policy does not force the password to expire, etc.