Hi Sharon,
Thanks for the reply. I tried the suggestion to set a different IP in the hosts file.
I was able to use the HOSTS file to point skype cce to a different IP.
Please have a look at the following log entry, the same error occurs on a different address.
Is this because our SSL certificate is rejected by the skype servers?
our certificate has the following chain;
Thx
Martin
-------- root
Issuer: CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE
Subject: CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE
----------- intermdiate 1
Subject: CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US
------------- intermediate 2
Subject: CN=GoGetSSL RSA DV CA, O=GoGetSSL, L=Riga, C=LV
------------ our skype cce edge certificate
Subject: CN=sip-cce.koerber.digital, OU=GoGetSSL Multi-Domain SSL, OU=Domain Control Validated
----------------------------------- cce log --------------
TL_ERROR(TF_CONNECTION) [edgepool\connyun-cce05]0890.0A04::10/25/2019-12:36:11.669.00002002 (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(470)) [987096081] $$begin_record
Severity: error
Text: Receive operation on the connection failed
Local-IP: 192.168.179.201:5061
Peer-IP: 52.112.233.9:36677
Peer: sipfed.online.lync.com:36677
Connection-ID: 0x100
Transport: M-TLS
Result-Code: 0x80072746
Data: fqdn="sipfed.online.lync.com";ip-address="52.112.233.9";peer-type="SharedAddressProvider";winsock-code="10054";winsock-info="The peer forced closure of the connection"
$$end_record
