Created by: Dimitris Kilias on 04-09-2013 01:41:10 AM Dear all,
We are trying to configure Cisco Media Sense to work in our lab environment. We have experienced an error during the configuration and would like to have some help if possible. The error occurs at both servers (UCS-E and UCS C200 VM) in which we have installed Mediasense. At both installations, we have a problem configuring Mediasense to connect to our Call Manager. After the step of assigning the AXL user and the IP of the Call Manager, the response is that it doesn’t find any CM Servers as a call control service provider. In the trouble shooting tips of Mediasense there is no any relevant info of how to solve this issue. At a later step, there is option to set up again the CM interface, but again we get the same error. I believe that we have configured the CM as it is described in the document in order to be ready for the interfacing with Mediasense. Moreover, the VG is communicating with CM with a SIP Trunk and this is also tested and working properly. The connections between the Mediasense Servers and CM are with IP (no dns names), and are all in the same subnet/vlan. Connectivity has been checked and is OK. Also, if we change the password of the CM AXL user, Mediasense recognizes the change and gives and error, and thus at least up to this step the configuration seems fine. The configuration that we are using are: CM is version 8.5.1 Mediasense is version 9.1 VG where the E-140S is installed is ISR 2911 The VM Server is a UCS-C200 M2 Esxi is 5.0 If you can, please review the error messages and help us to resolve this issue to finalize the installation.
Thank you very much for any help
BR
Dimitrios Kilias
Subject: RE: New Message from Dimitris Kilias in MediaSense (MediaSense) - Technical Replied by: David Lender on 04-09-2013 12:21:07 PM CDN does not provide support for Installation and Configuration issues, if you are a Cisco Partner you can use the PDI HelpDesk for Configuration issues.
I didn't understand this statement: "Also, if we change the password of the CM AXL user, Mediasense recognizes the change and gives and error, and thus at least up to this step the configuration seems fine." Could you say what the behavior was before and after you changed that password?
I'm not sure that you are having this same problem, but in the past, when people had trouble getting the AXL connection to work, the solution was to ensure that the AXL Service is enabled in CUCM. It isn't enabled by default.
I didn't understand this statement: "Also, if we change the password of the CM AXL user, Mediasense recognizes the change and gives and error, and thus at least up to this step the configuration seems fine." Could you say what the behavior was before and after you changed that password?
I'm not sure that you are having this same problem, but in the past, when people had trouble getting the AXL connection to work, the solution was to ensure that the AXL Service is enabled in CUCM. It isn't enabled by default.
Could you try that and let us know if it helped?
Thanks, Jeff W.
Dear Jeff,
AXL service is enabled in CUCM. Moreover, we have other applications that are using AXL to interact with the CUCM, and they are working properly.
Regarding the specific error, if I type a wrong password or an unkown username in Mediasense Configuration menu, it responses that the AXL credentials are wrong. If I enter correct username and password, then I get the error that there are no call control servers.
In that case, I am not sure what the problem is. Could you please open a case at the PDI help desk as suggested by David, and provide the API Service logs and the Configuration Service logs? We need to see the content of the messages being exchanged between the MediaSense node and the UCM node.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
