MarceloSchoen

> You might want to look at > > * [[PolicyRecordingBot]Server Internal Error. DiagCode: 3002#7106 #664](https://github.com/microsoftgraph/microsoft-graph-comms-samples/issues/664) > > Sounds like the same problem. The solution provided there might help you...

> You should be able to retrieve Call IDs / Call Chain IDs / Scenario IDs and timestamps as well. Then some of the Microsofties reading the issue can check...

My most detailed info on this { "@odata.type": "#microsoft.graph.commsNotifications", "value": [ { "@odata.type": "#microsoft.graph.commsNotification", "changeType": "updated", "resource": "/app/calls/811f5100-686a-45c5-a7be-b355b5d3d847", "resourceUrl": "/communications/calls/811f5100-686a-45c5-a7be-b355b5d3d847", "resourceData": { "@odata.type": "#microsoft.graph.call", "state": "establishing", "chatInfo": { "@odata.type": "#microsoft.graph.chatInfo",...

> Hey buddy, > > I had the EXACT same issue just now. The problem was NOT the certificate. Because it did work with this cert a couple of days...

> Assuming you generated your own self signed certificate, you did this against a domain. The DNS configuration of that domain needs the following two records (Not sure if no....

> Assuming you generated your own self signed certificate, you did this against a domain. The DNS configuration of that domain needs the following two records (Not sure if no....

> @MarceloSchoen Please check that the InstancePublicPort value is correct. For the most recent call attempt on 19 April 2024, I see this error in telemetry (where _ServiceFQDN_ is the...

> > @MarceloSchoen Please check that the InstancePublicPort value is correct. For the most recent call attempt on 19 April 2024, I see this error in telemetry (where _ServiceFQDN_ is...

> DiagCode: 500#3002.@ is related to an issue with your certificate. Check the certificate is valid. I have the same thing here, certificate is valid ( otherwise the whole call...