How to Integrating PSTN Number with Azure Communication Service for Call Event Triggering

Question

I currently have a PSTN number configured within Microsoft Teams, allowing me to make both outbound and inbound PSTN calls. However, I have encountered an issue where this PSTN number is not visible within Azure Communication Service. I am seeking guidance on the specific steps required to integrate my PSTN number with Azure Communication Service.

My primary objective is to link my PSTN number with Azure Communication Service to facilitate the publication of configured events such as "Call Started," "Call Ended," and "Incoming Call" This integration will enable the triggering of configured webhooks as needed."

It's important to note that these PSTN calls are exclusively received and made through the Microsoft Teams only.

Answer 1

@Sai Shashank Thanks for your patience on this. I have checked with Azure Communication Service engineering team and sharing the below.

currently this is an unsupported scenario. Events for a team's PSTN number is not available in ACS.

I would suggest you raise a feedback request using this link here. Our engineering team actively monitor and check the feasibility on implementing it accordingly.

Feel free to reach back to me if you have any further questions on this.

Answer 2

Currently, we are developing an ACS-to-ACS call solution for one of our customers, and while the call placement is working perfectly fine, we have encountered an issue when trying to add a PSTN number to an existing ACS-to-ACS call. Specifically, we are faced with error code 400. Our solution utilizes the Frontend SDK (@azure/communication-calling) to create a peer-to-peer call. Could you kindly provide your insights on how to resolve this issue? Your assistance would be greatly appreciated.

Answer 3

We’re creating a peer-to-peer ACS→ACS call from the frontend using @azure/communication-calling.Then we’re trying to add a PSTN participant to that same call. But adding PSTN numbers is only supported through the Call Automation / Server SDKs, not from a client SDK peer-to-peer session. Than how to fix it.