07-01-2009 10:50 AM - edited 03-18-2019 11:17 PM
New CUMA 7 install and I can't get the CUCM enterprise adapter to pass config test. It fails with a web services error. I have used numerous ID's for the web services config and verified that the users have the proper access. All other Adapters pass their config tests. The version of CUCM is 7.0(1) right now.
Any Ideas?
Solved! Go to Solution.
07-01-2009 03:58 PM
How many CUCM servers you configured in the adapter? If you configured two, make sure "AXL Web Service" is running on both.
Michael
07-03-2009 07:38 AM
ASA is security option. If you are testing CUMA/CUMC, you don't need ASA.
Check System Management > Network Properties. If you don't have ASA, just put the IP address of CUMA in "Proxy Host Name"
Michael
07-01-2009 03:58 PM
How many CUCM servers you configured in the adapter? If you configured two, make sure "AXL Web Service" is running on both.
Michael
07-02-2009 05:23 AM
That did it! Thanks.
Now if I can just get the service to start. I used the basic security config in the install guide witha trust_all security context. Are there other certificates that need to be loaded before the service will run? I also still have to configure my ASA as a proxy...could that be why it doesn't start?
07-03-2009 07:38 AM
ASA is security option. If you are testing CUMA/CUMC, you don't need ASA.
Check System Management > Network Properties. If you don't have ASA, just put the IP address of CUMA in "Proxy Host Name"
Michael
07-14-2009 01:26 PM
So that allowed the server to start. Now I have the client loaded on my BB 8820 and when I launch the client it prompts me to accept provisioning for my user ID, but when I enter my password it says it cannot contact the Mobility server.
Any thoughts?
07-14-2009 07:19 PM
We need to understand your network topology.
Does BB talk to your CUMA server directly? Or the BB talks to a proxy server/ASA?
Michael
07-14-2009 07:39 PM
Well at this point I don't have the ASA configured yet, so the proxy is pointing at the mobility server itself. We have a BES server on the inside of our network.
07-15-2009 04:41 AM
If BB talks to CUMA directly, it should be very straight forward.
From Internet, try to telnet to the CUMA client port (you may find out from CUMA Admin > System Management > Network Properties). See if you can connect to the client port. (by default it's 5443)
BTW, is your CUMA server accessible from Internet?
Michael
07-15-2009 04:46 AM
No the CUMA server is not accessible from the internet right now. I'm assuming that is where the ASA proxy comes in...right?
Thanks
07-15-2009 05:51 AM
Also, not sure if it matters but...our BES server can talk to internal servers directly, so would the proxy be needed?
07-15-2009 09:35 AM
If CUMA server is not accessible from the internet, you'll need an ASA.
BES server is out of the picture when BB connects to CUMA.
Michael
07-15-2009 10:02 AM
Thanks for the information. So what hostname does the client use to connect from the outside to the CUMA server, and where does it get that information from? Does it come with the install package downloaded from the CUMA server and is it the proxy configuration that it's derived from?
07-15-2009 01:02 PM
The client connects to the FQDN of the ASA. You manually enter the FQDN on CUMC on BB.
Michael
07-15-2009 01:32 PM
I see, so after I successfully log into the client on the BB I will be able to enter options (ie. the FQDN of the ASA)? I'm a little confused, I don't see any configuration options available before logging in, and without the options how can it successfully log me in?
07-15-2009 07:13 PM
It depends on provisioning methods.
If you're using manual provisioning, you'll see a screen like attached. You may enter the FQDN of the ASA.
If you're using BES to provision, the server URL will be auto-populated with the value configured in CUMA > System Management > Network Properties.
Michael
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide