A Jabber user is being prompted to trust the Expressway-E certificate when using Mobile and Remote Access. The administrator has validated that the Expressway-E certificate is being trusted by the machine running the Jabber client.
What else can be done to solve this problem?
When deploying an Expressway Core and Expressway Edge cluster for mobile and remote access, which TLS verity subject name must be configured on the Expressway-E UC traversal zone?
D18912E1457D5D1DDCBD40AB3BF70D5D
Refer to the exhibit showing logs from the Expressway-C, a copy of the Expressway-E certificate, and the UC traversal zone configuration for the Expressway-C. An office administrator is deploying mobile and remote access and sees an issue with the UC traversal zone. The zone is showing "TLS negotiation failure". What is causing this issue?
Refer to the exhibit.
An Expressway-C and Expressway-E are configured for B2B calling and the Expressway- E zone is set to TLS Verify Currently, calls do not reach the Expressway-C. The Traversal Client zone on the Expressway-C for B2B reports the information in the exhibit for the Peer 1 address.
Which action resolves this error?