07-02-2023 06:59 AM
Does Cisco Expressway X14.3 work without a license?
I have installed and configured Cisco Expressway X14.3 according to the official Cisco guide, but when I login, I get the following error:
Discovery Outcome Failure: FAILED_EDGE_CONNECTION
Domain Controller The specified domain either does not exist or could not be contacted.
The Cisco Jabber works on the internal network. But when using Cisco Expressway X14.3 (External Network), the above error is encountered.
Is this problem due to not having a license?
07-02-2023 11:51 AM
If you’re using the Expressway for MRA you do not need any license.
07-02-2023 02:27 PM - edited 07-02-2023 02:29 PM
Thanks Roger
I did not find anything in the Cisco documentation about MRA being free. Can you give the Cisco official reference regarding MRA being free?
So what could be the cause of the error in EDGE?
I have installed Cisco Expressway X14.3 on two different projects but in both I got the following error:
Discovery Outcome Failure: FAILED_EDGE_CONNECTION
Domain Controller The specified domain either does not exist or could not be contacted.
I used the Collaboration Solutions Analyzer (CSA) tool which didn't show me any errors.
The components of my system are as follows:
CUCM 14.0.1.13900-155
CUP 14.0.1.13900-8
CUC 14.0.1.13900-70
Cisco Expressway X14.3
07-02-2023 08:55 PM
There is no licenses required for MRA. Licenses are required only for device registration, Rich media Session. Where did you find this error ?
Does your Jabber works ? What error you received when trying to login from jabber.
Can you explain a little more about your setup ? is this a single nic or dual nic ? Collect the logs from both expressway E and C, analyze them using CSA.
07-02-2023 11:43 PM - edited 07-03-2023 03:44 AM
Thanks Nithin
Jabber works well on the internal network.
But I encounter an error when using Expressway E to login from the external network.
-----------------
The components of my system are as follows:
CUCM 14.0.1.13900-155 - Evaluation mode with 88 days remaining
CUP 14.0.1.13900-8 - Evaluation mode with 88 days remaining
CUC 14.0.1.13900-70 - Evaluation mode with 88 days remaining
Cisco Expressway X14.3 - Evaluation mode
Cisco Jabber v14.1.4
-----------------
internal DNS:
service: _cuplogin
protocol: _tcp
port number: 8443
host offering: cup.bcc...
service: _cisco-uds
protocol: _tcp
port number: 8443
host offering: cucm.bcc...
nslookup = ok
_cisco-uds._tcp.bcc...
_cuplogin._tcp.bcc...
-----------------
Click on the images and click on the zoom icon to view the images in high quality.
Jabber login error screenshot (external network - when using Expressway E)
When I logout and login several times, I get the following error:
CSA Checker:
Expressway C
Expressway E
07-03-2023 01:13 AM
If you could please provide better quality screen shots it would help us to help you. When you add a picture to you post please use this button in the tool bar.
If you paste the picture directly into the post, which I think that you have done, the picture quality is severely degraded.
07-03-2023 07:55 AM - edited 07-03-2023 07:55 AM
Is your external domain (which you used in the _collab-edge SRV record) configured in Exp-C and enabled for CUCM and IM&P?
Have you configured CUCM and IMP in the Exp-C?
It seems, that your config of the Expressways is not complete.
07-03-2023 02:34 AM - edited 07-03-2023 02:50 AM
Thanks Roger.
To see the images in high quality, if you click on one of the images and then click on the zoom icon, you can see the images in high quality.
I have put the images in order, first click on the first image and then zoom and then you can use the arrow keys to view the images in order.
or:
I have uploaded high quality images. After clicking on the image, you can right-click and then click "Open image in new tab" to display the image in very high quality.
07-03-2023 09:43 AM
Thanks b.winter
Yes, I have done all these configurations and checked again. They are currently "Active".
--------------------
Click on the images and click on the zoom icon to view the images in high quality.
---------------------
I tested Cisco Jabber in three stage:
1. empty password
2. wrong password
3. correct password
07-03-2023 08:25 PM
Collect logs from both expressway E and C recreate the issue and analyze the logs on CSA log analyzer.
follow the guide for collecting logs.
From the Pics you Shared i can see warning "failed to update key ". Click on view and you will find the steps to fix it. This has to be done from the CLI.
07-03-2023 11:12 PM
Apart from what @Nithin Eluvathingal said, is Exp-C able to resolve the SRV record for "_cisco-uds"?
You don't need the SRV record for "_cuplogin" and you shouldn't use it anymore either.
07-04-2023 02:17 AM
Generate the PRT from jabber and analyze it on CSA. @b.winter mentioned service: _cuplogin is no more needed. remove it from internal.
I hope you collected the logs from E and C as mentioned in the guide which i shared.
07-04-2023 01:40 AM
Thanks Nithin, b.winter
I fixed all the errors. But the problem was not solved.
The alarm was cleared from Expressway E.
Expressway C Status = OK - No alarm
Expressway E Status = OK - No alarm
CSA Tool results:
Expressway C log = OK - No error
Expressway E log = OK - No error
SRV Checker = OK
07-04-2023 01:57 AM
Are you still not able to open this link in your browser:
If yes, then maybe check the FW, if it is getting blocked there.
What about my other point: Is EXP-C able to resolve the "_cisco-uds" SRV?
If it is not able to resolve it, than EXP-C won't find the CUCM cluster and therefore, the first HTTP request Jabber sends (the URL you try in browser) will fail.
If the CSA sees no errors in the EXP logs, then try to upload a fresh Jabber PRT.
And in the domain settings in EXP-C:
For MRA you don't the settings "Expressway registrations" and "XMPP Federation" to be "On". Set them to "Off".
What about the certificate of the CUCM? Have you signed the Tomcat-Certificate of the CUCM and then added the CA(s) to the trusted certs in EXP-C?
When you added CUCM and IMP in the EXP-C, did you set "TLS verfiy" --> "On"? If yes, set it to "Off" and refresh the servers.
07-09-2023 06:02 AM
Thanks Nithin, b.winter
I installed version 14.0, all problems were solved and the 90days license was activated.
I couldn't fix the 14.3 problem.
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