Azure Communication Service - Call End Reason code : 410, subcode : 3112

Arunkumar Sundaram 20 Reputation points
2023-07-26T18:35:43.59+00:00
Hello Team,
We are using Azure Communication Services (ACS) for enabling meeting experience within our application.(angular application) 
We could able to create call agent, join the call with group id and Subscribe To Call. This was working fine. 
Suddenly we are getting into an issue - the meeting gets disconnected with the code 410 and 3112. There are no exceptions thrown. 
Screen print of the console for your reference is 

Few code blocks are mentioned below- 
<Code Start>
this.call = this.callAgent.join({ groupId: this.groupID });
this.subscribeToCall(this.call);

async subscribeToCall(call: any) {
    let rcImage: string = '';
    try { if (call.state === 'Connected')
        {      
        }        
			else if (call.state === 'Disconnected')
        {
          //This code block get executes
	      console.log(`Call ended, call end reason=			{code=${call.callEndReason.code}, subCode=${call.callEndReason.subCode}}`);
        }
      });
    } 
	catch (error) 
		{
      	console.error(`Failed in Subscribe the call${error}`);
      }
  }
<Code end>
We tried updating all the azure related packages to the latest version, but no luck.
Requested your assistance on this issue. Thanks

Azure Communication Services
Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
684 questions
{count} votes

1 answer

Sort by: Most helpful
  1. VenkateshDodda-MSFT 18,441 Reputation points Microsoft Employee
    2023-07-31T09:08:22.98+00:00

    @Arunkumar Sundaram Thanks for sharing the requested information.

    I have looked at the backend logs for above shared specific call id and we see that call got disconnected due to MediaWhitelistingIssue/410.0/3112.0 issue,

    As mentioned in the documentation Prepare your organization network for Azure Communication service make sure that you have configured your organization firewall by whitelisting the mentioned IP's.

    If you are still facing the issue, I would suggest you raise support ticket to Azure communication service team to check and assist you further.

    Hope this helps,