Sinch Community

Hi Dylan, There is no reporting API directly. However we do issue a DICE for each call if you implement a callback server (configurable in your dashboard application settings) and receive the details for each call you make. https://developers.sinch.com/docs/voice/api-reference/voice/tag/Callbacks/#tag/Callbacks/operation/dice   ... View more

Hi Dylan, Yes this is a limitation of conferencing being regional. You will have to have your Sinch Client started in the region the PSTN origination leg is in for it connect to the conference in that region. There could be creative ways around such as sending an out of band push that could then start the client before doing the conference callout,  however it would be outside of the scope of the Voice SDK. ... View more

Hi After checking the logs. I have looked at the logs and the URL in the ICE for the conferenceCallout portion of the call  https://calling-use1.api.sinch.com/calling/v1/calls the region contained in  calling-<region> should also be used in the in-app client.   So https://ocra-use1.api.sinch.com should be used here. It is the incoming PSTN leg that defines which reason to use.  This is due to the regional scope of conferences and the originating PSTN leg creates the conference so it will be anchored there. ... View more

Hi, I want to examine your conferences across regions I need to isolate your conference name, can you use another one than 2000000033938953 for a single test? Thanks ... View more

Hi I have looked and each conference leg is started in two different regions. This is due to GeoIP lookup between the IP you use to start the callout and the IP of the in-app Voice SDK client being considered as different regsions. As outlined here: https://developers.sinch.com/docs/voice/api-reference/#conference-calls Important! Conference rooms have regional scope. If you want to connect multiple participants from different regions (Continents) on the same conference, you must “force” all members to be on the same region. This can be done by selecting the same Sinch Voice API regional endpoints for Callout requests and/or the Sinch In-App regional endpoint/hostname to be used on your Mobile or Web Apps.   You can work around this, please try the following: Can you change your in-app client URL to:  https://ocra-apse1.api.sinch.com And the callout use: https://calling-apse1.api.sinch.com/calling/v1   ... View more

Great.  Please do reach out if you face any integration challenges, either in this forum (start a new thread) or via a ticket here: https://tickets.sinch.com/servicedesk/customer/portal/31/create/1313 Select RTC-Voice as the product. ... View more

1. Yes you should. Please keep in mind the regional scope of Conferences when connecting your clients.   Conference calls / scope https://developers.sinch.com/docs/voice/api-reference/#conference-calls   Calling API https://developers.sinch.com/docs/in-app-calling/overview/#sinch-in-app-global--regional-hostnamesendpoints   In-app clients https://developers.sinch.com/docs/in-app-calling/overview/#sinch-in-app-global--regional-hostnamesendpoints   2. custom field is not supported currently in conferenceCallout to destination type: username   3. Which error is it? Can you give me an example   ... View more

  1. Yes the same conference id. Keep in mind the regional scope of conferences if your callout and sdk client are based in different regions.    Calling API https://developers.sinch.com/docs/voice/api-reference/#api-quick-reference https://developers.sinch.com/docs/in-app-calling/overview/#sinch-in-app-global--regional-hostnamesendpoints   2. Custom headers in call out are not compatible with headers to in-app clients.     3. Which error does it return?     ... View more