Open itisslizz opened 6 years ago
There was a problem validating the certificate presented by your service: The expected DNS identity of the remote endpoint was 'cloud-rtc.luware.com' but the remote endpoint provided DNS claim 'luware.com'.
What are the values of the Subject Name and Subject Alternative Name list of your server certificate?
Thanks, Stephen
Thank you for the response. Subject: CN = *.luware.com O = Luware AG L = Zürich S = ZH C = CH
Subject Alternative Name: DNS Name=*.luware.com DNS Name=luware.com
So the exact DNS Name of cloud-rtc.luware.com needs to be in the Subject Alternative Name of the certificate?
Thanks, Marc
@itisslizz
Yes, the "cloud-RTC.luware.com" DNS name needs to be added to the end of the SAN list. We do not yet have wild-card support for bot certificates. Thanks.
After deploying the HueBot on an azure instance the bot doesn't answer the call. Checking the logs it seems it receives the call and returns accept, however the call ends before that?
Response to incoming call:
Incoming Callback:
Any Ideas where the issue lies? Only change I did was changing the workerrole to a Standard_D2 vmsize. Thanks