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

About AXL service and 2 CUCM servers

Hi everybody!

 

I hope anyone can help me. 

 

We have 2 CUCM servers (.20 & .21). We use AXL service in order to receive information from a AVAYA Device (Duvoice, for Voicemail and som hotel services, like Check-in-out/name of the host). 

 

Integration was friendly, but from one moment we detected that CUCM is no longer updating information from Duvoice.

I already checked that AXL service is active, in the Serviciability apart.

-I'd like to know, where can i restart de AXL service

-and, is the AXL service must be enable in both? or just 1 server. I saw a documen from Cisco where it says that it should be enable in one node, but I don't know if by "node" they mean "server" or what? This is the link http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/8_5_1/admin/Serviceability/sasrvact.html

 

I hope anybody can help me, any further information will be great.

 

Thank You in advance!

1 ACCEPTED SOLUTION

Accepted Solutions

To troubleshoot your AXL

To troubleshoot your AXL problems, I'd start at the client end. You could enable AXL logs on CUCM and look at them via RTMT, but from my experience, the client is the easiest place to diagnose problems.

 

As to which servers to run the AXL service on: It depends. If your AXL requests are just read-only, then you can run them on a subscriber fine. But if they're read/write, then there's not much point in running them on anything other than the publisher, as the publisher is the only server in a cluster that can make write changes to the database.

 

GTG

 

PS - I do know that some small changes are done in a mesh-type manner.

Please rate all helpful posts.
1 REPLY

To troubleshoot your AXL

To troubleshoot your AXL problems, I'd start at the client end. You could enable AXL logs on CUCM and look at them via RTMT, but from my experience, the client is the easiest place to diagnose problems.

 

As to which servers to run the AXL service on: It depends. If your AXL requests are just read-only, then you can run them on a subscriber fine. But if they're read/write, then there's not much point in running them on anything other than the publisher, as the publisher is the only server in a cluster that can make write changes to the database.

 

GTG

 

PS - I do know that some small changes are done in a mesh-type manner.

Please rate all helpful posts.
70
Views
0
Helpful
1
Replies
CreatePlease to create content