Forum Discussion
Calling resources on Trusted Application API for Skype Business Online shows CallbackUriUnreachable
Are you still seeing issues with callback? The callback is configured at the application level and you should be able to set that up from the Skype for Business online application registration portal
https://skypeappregistration.azurewebsites.net/appregistration
If you don’t see the callback Uri in the tenant admin shell that is expected.
Could you share your traces if you are still seeing issues with callback we could see what is happening there and help with debugging further.
I'm in the same situation. I did success via skypeappregistration.azurewebsites.net/appregistration. But callback url doesn't set in result of powershell. How do I gets other debug information?
- Renukha RajaramanMar 24, 2017Former Employee
Hi Keji,
The callback is not shown in the endpoint in the Tenant Admin shell and that is expected.
If you have used the registration portal and registered a callback url. You should be good.
Could you also share your http request and response headers we can look into why the callback fails.
You can also look into the X-MS-Client diagnostics code in your response header. Its base 64 encode.
Let me know if this helps.
- Apr 19, 2017
Hi,
I found root cause. Currently, Some Trusted Application API can run in US region of Office 365. My Office 365 tenant in Japan region. In non US region, I got error when call REST API.
Could you roll out this API to any regions? I want to this API on any regions. - Patrick HoganMar 28, 2017Copper Contributor
I'm facing the same problem, I used the registration tool and the callback URI was registered in New-CsOnlineApplicationEndpoint . Here is my X-MS-ClientDiagnostics:
T3BlcmF0aW9uQ29udGV4dC1PdXRnb2luZ0h0dHBSZXF1ZXN0RXhjZXB0aW9uTWVzc2FnZT1Db3VsZCBub3QgZ2V0IE9BdXRoIEVWTyB0b2tlbi4gTWVzc2FnZTogQUFEU1RTNTAwMDE6IFRoZSBhcHBsaWNhdGlvbiBuYW1lZCBodHRwczovL2V2ZW50cy5nZXJpcm1lLmNvbS5iciB3YXMgbm90IGZvdW5kIGluIHRoZSB0ZW5hbnQgbmFtZWQgOTg5ZDA1M2EtZThhYi00ODAwLWE0ZGEtZGJiZjAzYjQzY2NiLiAgVGhpcyBjYW4gaGFwcGVuIGlmIHRoZSBhcHBsaWNhdGlvbiBoYXMgbm90IGJlZW4gaW5zdGFsbGVkIGJ5IHRoZSBhZG1pbmlzdHJhdG9yIG9mIHRoZSB0ZW5hbnQgb3IgY29uc2VudGVkIHRvIGJ5IGFueSB1c2VyIGluIHRoZSB0ZW5hbnQuICBZb3UgbWlnaHQgaGF2ZSBzZW50IHlvdXIgYXV0aGVudGljYXRpb24gcmVxdWVzdCB0byB0aGUgd3JvbmcgdGVuYW50Lg0KVHJhY2UgSUQ6IDI5ZDViOTY4LWRmYzMtNDA3ZS1hNjI4LTk4MGIyYjdhMGIwMA0KQ29ycmVsYXRpb24gSUQ6IDAwNTFiMWY5LWIzOTQtNDMwNy1hMzlmLTIyNjJmOGVkMmM3MQ0KVGltZXN0YW1wOiAyMDE3LTAzLTI4IDE3OjIxOjMyWi1FcnJvckNvZGU9QmFkUmVxdWVzdC1FcnJvclN1YkNvZGU9Q2FsbGJhY2tVcmlVbnJlYWNoYWJsZS1FcnJvckRlYnVnUHJvcGVydGllcz1lcnJvclJlcG9ydElkPSI0NDgwZDk5NGY1ODg0ZTEyYjQzN2RlOTM0YTA0YzJlZiIKLUNvcnJlbGF0aW9uSWQ9MjE0NzQ4NDQzNi1IdHRwTWV0aG9kPVBPU1QtU3RhdHVzQ29kZT00MDAtVXJpUGF0aD0vcGxhdGZvcm1zZXJ2aWNlL3YxL2FwcGxpY2F0aW9ucy8yMzgyMDA3ODExL2NvbW11bmljYXRpb24vbWVzc2FnaW5nSW52aXRhdGlvbnMtVXJpUXVlcnlQYXJhbWV0ZXJzPT9lbmRwb2ludElkPXNpcDpza3lwZWZvcnRoZXdpbnMxQHRlbmZvbGRpbmMub25taWNyb3NvZnQuY29tLVVzZXJBZ2VudD1za3lwZWZvcnRoZXdpbnMxLUxhdGVuY3k9MjE4LjczOTktVGltZXN0YW1wPTEvMS8wMDAxIDg6MDA6MDAgQU0tQ2xpZW50SWQ9ZGI5MmJhN2QtYWI3ZC00ZWIwLTg2ZTUtMjgwYjM3MTc5MzJhLUNsaWVudE5hbWU9c2t5cGUgZm9yIHRoZSB3aW5zLUVuZHBvaW50SWQ9c2lwOnNreXBlZm9ydGhld2luczFAdGVuZm9sZGluYy5vbm1pY3Jvc29mdC5jb20tVGVuYW50SWQ9OTg5ZDA1M2EtZThhYi00ODAwLWE0ZGEtZGJiZjAzYjQzY2NiLU1hY2hpbmU9QkwyMFIwMkZFUzAxLmluZnJhLmx5bmMuY29tLUZvcm1hdFZlcnNpb249UGxhdGZvcm1TZXJ2aWNlIDEuNC1SZXF1ZXN0ZWRWZXJzaW9uPTAt
- Renukha RajaramanMar 28, 2017Former Employee
Just checking if you did the step for tenant admin consent as this is the exception that we are seeing when we decode the X-Ms-ClientDiagnostics
OperationContext-OutgoingHttpRequestExceptionMessage=Could not get OAuth EVO token. Message: AADSTS50001: The application named https://events.gerirme.com.br was not found in the tenant named 989d053a-e8ab-4800-a4da-dbbf03b43ccb. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.
Trace ID: 29d5b968-dfc3-407e-a628-980b2b7a0b00
Correlation ID: 0051b1f9-b394-4307-a39f-2262f8ed2c71
Timestamp: 2017-03-28 17:21:32Z-ErrorCode=BadRequest-ErrorSubCode=CallbackUriUnreachable-ErrorDebugProperties=errorReportId="4480d994f5884e12b437de934a04c2ef"
-CorrelationId=2147484436-HttpMethod=POST-StatusCode=400-UriPath=/platformservice/v1/applications/2382007811/communication/messagingInvitations-UriQueryParameters=?endpointId=sip:skypeforthewins1@tenfoldinc.onmicrosoft.com-UserAgent=skypeforthewins1-Latency=218.7399-Timestamp=1/1/0001 8:00:00 AM-ClientId=db92ba7d-ab7d-4eb0-86e5-280b3717932a-ClientName=skype for the wins-EndpointId=sip:skypeforthewins1@tenfoldinc.onmicrosoft.com-TenantId=989d053a-e8ab-4800-a4da-dbbf03b43ccb-Machine=BL20R02FES01.infra.lync.com-FormatVersion=PlatformService 1.4-RequestedVersion=0-Meanwhile I will try to pull logs off the server for this one and see if we have more information. We are working on improving debuggability for callback failures in general.
Will get back with updates. Thanks
- Mar 26, 2017
Hi Renukha,
Thanks. However S4B doesn't accessing to my callback url. (Of course, my callback url can access).
A callback access doesn't show in my web server's access log.