Microsft Graph rest API beta: Audio routing group API does not work as expected

%3CLINGO-SUB%20id%3D%22lingo-sub-2210122%22%20slang%3D%22en-US%22%3EMicrosft%20Graph%20rest%20API%20beta%3A%20Audio%20routing%20group%20API%20does%20not%20work%20as%20expected%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2210122%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%3CP%3E%26nbsp%3BWe%20are%20reviewing%20the%20set%20of%20graph%20API%20that%20is%20used%20to%20configure%20participant%20audio%20path%20in%20a%20group%20call%3A%3C%2FP%3E%3CP%3EThere%20are%203%20participants%20in%20the%20group%20call%3A%20bot(is%20removed%20from%20default%20audio%20group%20when%20Answering%20the%20call)%2C%20teams%20user%20A%20and%20teams%20user%20B.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGet%3A%26nbsp%3B%3CSPAN%3EGET%20%2Fcommunications%2Fcalls%2F%7Bid%7D%2FaudioRoutingGroups%20does%20not%20work%20if%20there%20is%20no%20Id%20tagged%20onto%20the%20request%2C%20i.e.%20cannot%20enumerate%20existing%20routing%20groups.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAdd%3A%26nbsp%3B%20appears%20being%20completed%20successfully%20but%20does%20nothing%20to%20the%20audio%20path.%20we%20tried%20the%20following%20scenarios%3A%3C%2FSPAN%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EAdd%3A%20source%20%22bot%22%20and%20receiver%20%22user%20A%22.%20The%20test%20result%20indicates%20user%20B%20is%20still%20able%20to%20hear%20%22bot%22%20playing%20prompts.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EAdd%3A%20source%20%22user%20A%22%20and%20receiver%20%22user%20B%22.%20The%20test%20result%20indicates%20user%20A%20and%20user%20B%20is%20still%20able%20to%20hear%20%22bot%22%20playing%20prompts.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECould%20anyone%20clarify%20what%20is%20the%20expected%20behavior%20for%20this%20set%20of%20API%3F%20Does%20it%20work%20at%20all%3F%20or%20work%20for%20certain%20scenarios%20then%20what%20scenarios%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMany%20thanks%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJosie%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2210122%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAPI%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20Graph%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi there,

 We are reviewing the set of graph API that is used to configure participant audio path in a group call:

There are 3 participants in the group call: bot(is removed from default audio group when Answering the call), teams user A and teams user B.

 

Get: GET /communications/calls/{id}/audioRoutingGroups does not work if there is no Id tagged onto the request, i.e. cannot enumerate existing routing groups.

 

Add:  appears being completed successfully but does nothing to the audio path. we tried the following scenarios:

  • Add: source "bot" and receiver "user A". The test result indicates user B is still able to hear "bot" playing prompts.
  • Add: source "user A" and receiver "user B". The test result indicates user A and user B is still able to hear "bot" playing prompts.

 

Could anyone clarify what is the expected behavior for this set of API? Does it work at all? or work for certain scenarios then what scenarios?

 

Many thanks,

 

Josie

 

0 Replies